Quora indo

Developer: @naufaldi
Description: Adding Login Page Quora Indo, There are two version. Mobile & Dekstop, bcs its different , adding two of them.
Design Source: if available
Screenshoots
Attach screenshoots if necessary, attach the before and the after if it's a bug fixing.
If it's new design, please attach for mobile and desktop screenshoots.
TODOS

[ done ] Add screenshots on screenshoots directory (if new design)
[ done ] Update the list in readme.md (if new design)
[done ] Add in src/index.html (if new design)
[done ] Change the author text and link (if new design)

@mazipan please review
// If it's a bugfix, please mention the slicer on readme.md.

also, pls add label "hacktoberfest" for counting as PR 😂

Conflict nih, please fix the conflict ya

sudah mas @mazipan

@all-contributors please add @naufaldi for code


weather descriptions

add weather descriptions for 5 more countries in weather data

finland
germany
poland
czechia
france

@cieslarmichal this is not done, would you like to open this?

@00thirdeye00  reopened


🌸 Enable @objc @implementation in the form approved by SE-0436

Cherry-picks #73128, #73309, #74135, #74161, and #74801 to release/6.0. In combination, these changes implement the approved design for SE-0436 and add it as a normal language feature.

@swift-ci please test


Update service-gateway-enterprise-manage-ssas.md

Added a line (178) explaining how the effectiveusername of the dataset owner is sent as the UPN by the gateway.
PG confirmed this: https://web.yammer.com/main/org/microsoft.com/threads/eyJfdHlwZSI6IlRocmVhZCIsImlkIjoiMjE5MTQzNjE0OTM5OTU1MiJ9

@arthiriyer
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Looks good, thanks!
#sign-off


Deploy state legend storybook (#2389)

Pull request opened by the merge tool on behalf of #2389

Merged in 99a40226b4a511f2175bc9c00244523d21089ca6


Doesn't work with  3.5.2

None of sketch measure works for me correctly on 3.5.2. Bellow are some recordings of what happens.

Update last version

Yep, that worked for me

Worked, thanks.


Question regarding rampage_idr.sh comments

Hi,
From what I understand, rampage_idr.sh should be run with the bed files resulting from two separate rampage_peaks runs (eg two replicates).
However, lines 8 and 9 of rampage_idr.sh state:
 peaks_a_bed=$1  # Rampage dumplicates marked bam file.
 peaks_b_bed=$2  # long-RNA-seq control bam file.

but peaks_a_bed should actually be (for example) rampage_peaks_1.bed and peaks_b_bed should be rampage_peaks_2.bed, correct? Not bamfiles and not rampage/control.
This may be an obvious question but I would like to be sure so that I run the pipeline correctly.
Thanks!

The documentation https://github.com/ENCODE-DCC/long-rna-seq-pipeline/tree/master/dnanexus/rampage considering the rampage_idr applet, and also the flowchart seems to confirm your understanding to be correct. Thank you for pointing out the error in the comments considering the inputs of the script, I will fix that. If you have any other questions, I am happy to help!


499 reported in nginx reverse proxy

HTTP code 499 usually is seen in NGINX's logs. Being a web server, NGINX 499 is able to identify that the problem is not in the server itself, or the entity which sent the request. HTTP error 499 simply means that the client shut off in the middle of processing the request through the server.

When requesting home page of admin UI, main index is loaded, but resources not, e.g. /_/assets/index.e13041a6.js is failed to load. From log of nginx, it reported 499 and then 504:
 - - [24/Oct/2022:07:39:32 +0800] "GET /_/assets/index.e13041a6.js HTTP/1.1" 504 562 "http://xxxxx/_/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36 OPR/82.0.4227.23"
 - - [24/Oct/2022:10:27:06 +0800] "GET /_/assets/index.e13041a6.js HTTP/1.1" 499 0 "http://xxxxx/_/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36 OPR/82.0.4227.23"

It works when I requesting the original IP with port.

I'm not sure what could cause this. As you quoted, 499 is usually returned for example on client-side timeouts (the 504 also seems to confirms it), but I'm not sure why.
Since it works when accessing it with the IP, then most likely it is misconfiguration of the nginx proxy. Could you post here your nginx config or try the example one from https://pocketbase.io/docs/going-to-production/#deploy-behind-reverse-proxy.
I'll move the issue to Q&A discussion.


Some docs updates

Summary
This extracts the updates to the drivers, problems, and properties submodules which were included in #921 to be merged separately.
Changes to the vibrational stack aspects of these modules are left in the aforementioned PR since those actually make sense to be in there :+1:
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 85.813%

Files with Coverage Reduction
New Missed Lines
%

qiskit_nature/drivers/second_quantization/psi4d/psi4driver.py
2
84.43%

qiskit_nature/second_q/drivers/psi4d/psi4driver.py
2
83.05%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
17439

Relevant Lines:
20322

💛  - Coveralls


Expose csv-parse options in body parser

I'd like to be able to set some of the options of the csv parser used internally by csv-parse, especially relax_column_count.
I know that I can override some of the default options with request headers, but not everything is exposed and not everything should be left to the client to decide
(reposted from https://github.com/restify/node-restify/issues/1167)

Sounds like we need to give more ability to pass through options to the underlying parser - this sounds reasonable to me.

Seems like we should tackle this as part of #7

Migrating back to https://github.com/restify/node-restify/issues/1167


Search doesn't work for small substrings

Duplicate I think.  Since search not working at all now.  Closing.


docs: fix wrong config emitTokensOnly link at cli emitTokensOnly

Closes #
📝 Description

Add a brief description

I found wrong link at cli emitTokensOnly and fixed it.
( I'm really enjoying this library, thanks for maintaining. )
⛳ Current behavior (updates)
The shortcut for config emitTokensOnly doesn't work correctly.
🚀 New behavior

Please describe the behavior or changes this PR adds

The shortcut for config emitTokensOnly works correctly.
https://github.com/user-attachments/assets/3914602c-d045-4fd2-960f-0511fb3ba142
💣 Is this a breaking change (Yes/No):
No
📝 Additional Information

@Danji-ya Could you fix these too:

outExtension
jsxFramework
strictTokens


deisctl list Fails with Vagrant/Virtualbox

I have followed the steps in the installation guide to set up Deis on Vagrant (in fact, I have done so before on a different machine and been successful), but after I export DEISCTL_TUNNEL=<IP_ADDRESS> and run deisctl list, I get: Error: failed initializing SSH client: timed out while initiating SSH connection. I tried deleting the deis folder and removing all VMs and starting from the top, but to no avail. The only major difference between this machine and the one on which I was successful (that I can think of) is that I am ssh-ing into the one on which I am receiving the error.
Attempts to ssh<EMAIL_ADDRESS>hang. ssh-add -L returns (what I assume is) the correct key.
Steps:

Install VirtualBox.
Install Vagrant (and vagrant-triggers plugin).
Clone the repository.
make discovery-url
vagrant up
Install deisctl.
eval $(ssh-agent -s) (I actually used backticks instead of $() but I can't figure out this markdown escaping nonsense).
ssh-add ~/.vagrant.d/insecure_private_key
export DEISCTL_TUNNEL=<IP_ADDRESS>
deisctl list
Error: failed initializing SSH client: timed out while initiating SSH connection

Considering that ssh-ing directly to the box fails, something could be up with the VMs or the network. What's the output of vagrant status?

deis-01 running (virtualbox)
deis-02 running (virtualbox)
deis-03 running (virtualbox)

Try vagrant ssh-config deis-01. Probably it allocated a different port.

So now I can ssh into deis-01 (you were correct, it was a different port and I had to use <IP_ADDRESS> for the IP address). I still get an error when I try to deisctl list though, any ideas there?

export DEISCTL_TUNNEL=<IP_ADDRESS>:2222 (or whatever port was assigned for SSH) might get deisctl working. Although note that if the vagrant boxes didn't get assigned <IP_ADDRESS>-102 as IPs, then the test domain local3.deisapp.com won't work.

You should ensure that vagrant says that is creates a host network and a nat network when you first start. You can then do vagrant ssh deis-01 ip addr to see what IP the first node has, that starts with 172. Use this as the tunnel IP.
I also had to accept through my firewall, the connection outbound to the 172-network.

It says Adapter 1: nat and Adapter 2: hostonly when booting. After vagrant ssh deis-01 and ip a, I get two network adapters: eth0 has an inet address of <IP_ADDRESS>, and eth1 has an inet the `172.~~~

I'd say the next step is to run vagrant ssh-config and then try ssh -t ~/.vagrant/insecure_key<EMAIL_ADDRESS>or whichever key the ssh-config command specifies is being used. If that doesn't work, you have a general connectivity problem to virtual machines on you machine. If it works, then you should seek a way to in detail log the ssh command that deisctl actually runs and ensure you have the identical version to your deis version. You can also read https://github.com/deis/deis/issues/2727 which comes up with having a too-low vagrant version being the issue.

10.x network doesn't work because it's a private network with VirtualBox and not exposed to your host machine. The NAT network is used to download things from the internet and it's natted at the host kernel level.

vagrant ssh-config tells me HostName <IP_ADDRESS>; is that the expected output?
ssh -t ~/.vagrant.d/insecure_private_key<EMAIL_ADDRESS>doesn't seem like the correct syntax; it complains that it can't resolve the hostname, but the hostname it says it can't resolve is the private key.

Let me test this locally.

Here's vagrant ssh-config
vagrant ssh-config
Host deis-01
  HostName <IP_ADDRESS>
  User core
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile /Users/henrik.feldt/.vagrant.d/insecure_private_key
  IdentitiesOnly yes
  LogLevel FATAL

I can reproduce your local error, here's what I did to make it work:
➜  deis-vagrant git:(docs/cadvisor) ✗ ssh -t /Users/henrik.feldt/.vagrant.d/insecure_private_key<EMAIL_ADDRESS>-p 2222
ssh: Could not resolve hostname /Users/henrik.feldt/.vagrant.d/insecure_private_key: nodename nor servname provided, or not known
➜  deis-vagrant git:(docs/cadvisor) ✗ ssh -i /Users/henrik.feldt/.vagrant.d/insecure_private_key<EMAIL_ADDRESS>-p 2222
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
89:90:6d:99:45:f2:1c:cf:9e:b6:b5:45:74:df:27:15.
Please contact your system administrator.
Add correct host key in /Users/henrik.feldt/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/henrik.feldt/.ssh/known_hosts:54
RSA host key for [<IP_ADDRESS>]:2222 has changed and you have requested strict checking.
Host key verification failed.
➜  deis-vagrant git:(docs/cadvisor) ✗ vim /Users/henrik.feldt/.ssh/known_hosts
➜  deis-vagrant git:(docs/cadvisor) ✗ sed -i '' 54d /Users/henrik.feldt/.ssh/known_hosts
➜  deis-vagrant git:(docs/cadvisor) ✗ ssh -i /Users/henrik.feldt/.vagrant.d/insecure_private_key<EMAIL_ADDRESS>-p 2222
The authenticity of host '[<IP_ADDRESS>]:2222 ([<IP_ADDRESS>]:2222)' can't be established.
RSA key fingerprint is 89:90:6d:99:45:f2:1c:cf:9e:b6:b5:45:74:df:27:15.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[<IP_ADDRESS>]:2222' (RSA) to the list of known hosts.
<EMAIL_ADDRESS>password:

➜  deis-vagrant git:(docs/cadvisor) ✗ ssh -i /Users/henrik.feldt/.vagrant.d/insecure_private_key<EMAIL_ADDRESS>-p 2222
Last login: Sat Mar  7 21:40:19 2015 from <IP_ADDRESS>
 * *    *   *****    ddddd   eeeeeee iiiiiii   ssss
*   *  * *  *   *     d   d   e    e    i     s    s
 * *  ***** *****     d    d  e         i    s
*****  * *    *       d     d e         i     s
*   * *   *  * *      d     d eee       i      sss
*****  * *  *****     d     d e         i         s
  *   *****  * *      d    d  e         i          s
 * *  *   * *   *     d   d   e    e    i    s    s
***** *****  * *     ddddd   eeeeeee iiiiiii  ssss

Welcome to Deis			Powered by CoreOS
core@deis-01 ~ $ exit
logout
Connection to <IP_ADDRESS> closed.
➜  deis-vagrant git:(docs/cadvisor) ✗

So ssh-ing into coreos wasn't my problem (I can do that with vagrant ssh deis-01), my problem is not being able to run deisctl list. Given that I can ssh in to the coreos vm, do you have any ideas for how I can go about logging the ssh command that deisctl runs? I tried finding commands in the source but to no avail.

@Californian, what do you have set for DEISCTL_TUNNEL?

<IP_ADDRESS>

Did you try adding the key to ssh-agent and setting DEISCTL_TUNNEL to the host and port specified by vagrant?
$ eval $(ssh-agent)
$ ssh-add ~/.vagrant.d/insecure_private_key
$ export DEISCTL_TUNNEL=<IP_ADDRESS>:2222
$ deisctl list

So that gets deisctl list working, but when I try to install it hangs after<EMAIL_ADDRESS>loaded. I assume this is because it is not using <IP_ADDRESS> for the tunnel address, so any thoughts on how to debug why using that address is not working (or how to resolve the hanging another way)?

I assume this is because it is not using <IP_ADDRESS> for the tunnel address

Probably not--if deisctl is able to talk to a node in the cluster, then deisctl start platform doesn't care about addressing. If start platform hangs, it often indicates a fleet/etcd error internal to the cluster. I would ensure that fleetctl list-machines from one of the nodes shows all 3 to be healthy, try the command again, and then look through journalctl logs for fleet to see if errors show up.
As far as why vagrant didn't allocate our preferred IP address range, I've seen this happen in the case of collisions, where I already had a vagrant / VirtualBox VM using that address, when I've tried to use vagrant / VMware as well, or if VirtualBox's own network interfaces are somehow stale or incorrect. I can't say for sure that's what you're seeing, but my troubleshooting steps in this case are usually to 1) shut down all VirtualBox instances, and 2) remove the VirtualBox network bridges and dhcp servers:
$ VBoxManage list hostonlyifs
$ VBoxManage hostonlyif remove vboxnet1
$ VBoxManage hostonlyif remove vboxnet1
$ VBoxManage list dhcpservers
$ VBoxManage remove --netname HostInterfaceNetworking-vboxnet1

VirtualBox will recreate them the next time you start a VM, which--at least for me--usually fixes the assignment of <IP_ADDRESS>.

fleetctl list-machines gives me  20 or so alternating INFO/ERROR lines:
INFO client.go:291: Failed getting response from http://<IP_ADDRESS>:4001/: too many redirects
ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 100ms
then
Error retrieving list of active machines: timeout reached
As for this removal business, I tried removing all the network bridges and dhcp servers. That went...interestingly. I'm not sure if I wasn't supposed to remove things suffixed vboxnet0, but something or other crashed the server while in the middle, so after rebooting I uninstalled vagrant and virtualbox, deleted ~/VirtualBox VMs and deis/.vagrant, rebooted, reinstalled, deleted hostonlyif vboxnet1, vagrant upd, ssh-added the insecure private key, exported the 172 address for the tunnel, and got the same timeout result. I then tried exporting the 127...:2222 address again and got the above INFO/ERROR responses when doing deisctl list, which is strange because, as I mentioned, that previously worked.
Does this tell you anything? I don't know where to debug from here.

@Californian Based on your debugging and your output, I would suspect that the VMs can't communicate with each other over the private network. What does ifconfig report on the VMs? That will confirm @mboersma's suspicion that they're getting addresses that aren't routable to each other. This would also explain why etcd can't communicate, and why your deisctl start hangs - there's effectively only one machine in your cluster, the one deisctl is talking to.

VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet1

It's important that all DHCP servers are removed from VBox - we can't tell which one vboxnet1 is in that particular instance.
Either way, I think an ifconfig would be helpful.

Now VBoxManage list dhcpservers returns nothing no matter what (there was one at some point, but it's now gone and won't come back even after vagrant up).
Here is the ifconfig output for each machine.
deis-01
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fe8e:e1da  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:8e:e1:da  txqueuelen 1000  (Ethernet)
        RX packets 1048  bytes 119206 (116.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 780  bytes 103379 (100.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fea8:de2d  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:a8:de:2d  txqueuelen 1000  (Ethernet)
        RX packets 8302  bytes 1263214 (1.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10734  bytes 2386768 (2.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 3139  bytes 560126 (546.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3139  bytes 560126 (546.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

deis-02
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fe8e:e1da  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:8e:e1:da  txqueuelen 1000  (Ethernet)
        RX packets 879  bytes 99886 (97.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 661  bytes 82058 (80.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fef8:cc0f  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:f8:cc:0f  txqueuelen 1000  (Ethernet)
        RX packets 6618  bytes 1592794 (1.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5109  bytes 790712 (772.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 6097  bytes 1186419 (1.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6097  bytes 1186419 (1.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

deis-03
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fe8e:e1da  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:8e:e1:da  txqueuelen 1000  (Ethernet)
        RX packets 874  bytes 99543 (97.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 656  bytes 81788 (79.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fe5c:6e7c  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:5c:6e:7c  txqueuelen 1000  (Ethernet)
        RX packets 4530  bytes 888491 (867.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3515  bytes 517268 (505.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 2980  bytes 599476 (585.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2980  bytes 599476 (585.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

@Californian That looks OK now. Can you give it another go?

Also, cat /etc/environment and confirm the public and private IPs.

Oh wow that did work! I had to use <IP_ADDRESS>:2222 for the tunnel, but it installed and is now starting. Thank you!
I suppose you can close this issue (though it is still confusing to me that I can't use <IP_ADDRESS>, an IP address that will now be burned into my memory).

I had to use <IP_ADDRESS>:2222 for the tunnel, but it installed and is now starting.

Glad to hear you're up and running, but still dumbfounded as to why you can't route to that IP. By any chance, are you on a local (wired or wireless) network which assigns IP addresses in that range? I'm wondering if traffic to the VM is getting routed out to another network instead of using the local bridge.
ifconfig on your workstation should confirm or refute this.

My workstation runs Arch, so this is the output of ip a instead.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp26s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:0a:f7:1a:75:90 brd ff:ff:ff:ff:ff:ff
3: enp26s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:0a:f7:1a:75:92 brd ff:ff:ff:ff:ff:ff
4: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 34:40:b5:8c:5a:db brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/26 brd <IP_ADDRESS> scope global enp6s0
       valid_lft forever preferred_lft forever
    inet6 fe80::6701:5559:2816:9b9e/64 scope link
       valid_lft forever preferred_lft forever
5: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 34:40:b5:8c:5a:dc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d2d4:9f9e:e93a:cdaa/64 scope link tentative
       valid_lft forever preferred_lft forever
6: enp0s29u1u1u5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:8c:5a:de brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global enp0s29u1u1u5
       valid_lft forever preferred_lft forever
    inet6 fe80::73df:524:258e:160e/64 scope link
       valid_lft forever preferred_lft forever
9: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::aca7:69d4:eddf:a9b9/64 scope link
       valid_lft forever preferred_lft forever

deis register doesn't work. I assume this is related to the same root issue, but perhaps that is better-suited to a new bug?

I assume this is related to the same root issue, but perhaps that is better-suited to a new bug?

That won't work if you can't connect to the VMs via <IP_ADDRESS>, since local3.deisapp.com resolves to <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>.

Yeah I thought that was the implication above from @mboersma. How do I work around that?

Yeah I thought that was the implication above from @mboersma. How do I work around that?

Honestly, I'm not sure. I was going to suggest that you edit ~/.ssh/config and add entries for the VMs so you can refer to them by name, but that doesn't help if you don't have a wildcard DNS record to point to them. And /etc/hosts doesn't work for wildcard domains...
Figuring out why <IP_ADDRESS> doesn't route to the VM on your machine is the blocker. Unfortunately, I'm out of ideas :(

Should there be more than one hostonlyif?

Yes, typically you'll have vboxnet0 and vboxnet1 after running vagrant up with Deis.

Ah well I only have one, maybe that's part of the problem. I had two at some point in this process (vboxnet0 with an IP address I can't remember and vboxnet1 with the 172 address), but now it's just vboxnet0 with the 172 address.

I started everything from scratch, including removing a bunch of hidden folders with data for vagrant/virtualbox, and after vagrant up, I get the following.
VBoxManage list hostonlyifs
Name:            vboxnet0
GUID:            786f6276-656e-4074-8000-0a0027000000
DHCP:            Disabled
IPAddress:       <IP_ADDRESS>
NetworkMask:     <IP_ADDRESS>
IPV6Address:     fe80:0000:0000:0000:aca7:69d4:eddf:a9b9
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-vboxnet0

Name:            vboxnet1
GUID:            786f6276-656e-4174-8000-0a0027000001
DHCP:            Disabled
IPAddress:       <IP_ADDRESS>
NetworkMask:     <IP_ADDRESS>
IPV6Address:     fe80:0000:0000:0000:ff57:ffa8:308b:9f68
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:01
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-vboxnet1

VBoxManage list dhcpservers
NetworkName:    HostInterfaceNetworking-vboxnet0
IP:             <IP_ADDRESS>
NetworkMask:    <IP_ADDRESS>
lowerIPAddress: <IP_ADDRESS>
upperIPAddress: <IP_ADDRESS>
Enabled:        Yes

@Californian were you able to sort out the VirtualBox bridge issue here? I'm not sure what else to try for troubleshooting.

I'm closing this as there doesn't seem to be anything here that Deis can address.


Add video signature and owner verification to erase duplicates from youtube video imported

Hello,
I don't know where to post my suggestion, I think it is very necessary to get more value on the product.
I've just discovered the rapid growing website and project odysee (lbry) with grat and intuitive design !
Steps to Reproduce

Open odysee.com search for a video that is also on youtube.com and has many views
Click on this video and see the related videos at right side of the screen
You will see many duplicates of the videos published by different odysee accounts

Maybe it's not the website who handle this... A way to suggest this to the odysee team that works on backend ?

Thanks for filing the issue. Some content may not have copyright and owners are encouraged to submit reports of any value copyright claims.


Unable to see server numbers

I found a bug on the bot.ejs page, the server number is not displayed and yet there is the code in the page

Thank you for your feedback. It appears that the server number is not displayed on the bot.ejs page due to the absence of the botdata.serverCount variable in the codebase.
This feature relies on an older implementation, and I may not fully remember its workings. It was intended to use our API, which might not have been fully developed. As a result, the function seems inactive, reserved for potential updates.


Portainer issue in creating endpoint with Docker option (Docker API)

**Issue:
Portainer issue in creating endpoint with Docker option (Docker API) to access remote device (Raspberry Pi)
Bug description
Trying to create Portainer endpoint for the direct Docker API option but fails with below error:
http error: Unable to initiate communications with endpoint (err=Cannot connect to the Docker daemon at tcp://192.16x.x.xx:2375. Is the docker daemon running?) (code=500)
Expected behavior
End point should be successfully created.
Portainer Logs
This is what I get:
http error: Unable to initiate communications with endpoint (err=Cannot connect to the Docker daemon at tcp://192.16x.x.xx:2375. Is the docker daemon running?) (code=500)
Steps to reproduce the issue:

I already had portainer setup on my Windows machine for Linux enviornment with following commands:
docker volume create portainer_data
docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

On my Raspberry Pi (remote device - IP address is 192.16x.x.xx - x is to hide actual ip) I exposed Docker API using below instructions:
Updated /lib/systemd/system/docker.service to include following:
ExecStart=/usr/bin/dockerd -H fd:// -H=tcp://192.16x.x.xx:2375 --containerd=/run/containerd/containerd.sock
sudo systemctl daemon-reload
sudo service docker restart

On my windows machine browser I can access images and container JSON available on my Pi using :
http://192.16x.x.xx:2375/images/json
http://192.16x.x.xx:2375/containers/json
On Windows power shell, when I do "docker -H 192.16x.x.xx:2375 info" , I get below in output description:
Client:
Context:    default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
compose: Docker Compose (Docker Inc., 2.0.0-beta.1)
scan: Docker Scan (Docker Inc., v0.8.0)
Server:
Containers: 12
Running: 1
Paused: 0
Stopped: 11
Images: 10
Server Version: 20.10.6

Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc io.containerd.runc.v2 io.containerd.runtime.v1.linux
Default Runtime: runc
Init Binary: docker-init
containerd version: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 5.10.17-v7+
Operating System: Raspbian GNU/Linux 10 (buster)
OSType: linux
Architecture: armv7l
CPUs: 4
Total Memory: 924.2MiB
Name: raspberrypi
ID: PBBE:KOC4:WJW4:Y4FP:ROIT:XRWN:A5VC:7JBB:5FSY:6PP4:YF7G:UFI6
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
WARNING: API is accessible on http://192.16x.x.xx:2375 without encryption.
Access to the remote API is equivalent to root access on the host.

Now on my windows machine. with my local ip address http://192.16y.y.y:9000/#!/endpoints/new , I try to create endpoint with DOcker (Directly connect to the Docker API) option and it says unable to communicate with end point. Portainer log says:
http error: Unable to initiate communications with endpoint (err=Cannot connect to the Docker daemon at tcp://192.16x.x.xx:2375. Is the docker daemon running?) (code=500)

With above I think, docker APIs on my Pi is correctly exposed but I am not able to create the endpoint on my portainer.

Please suggest what I might be doing wrong ?
Thanks in advance.
Technical details:

Portainer version: 2.5.0
Docker version (managed by Portainer): refer above log
Kubernetes version (managed by Portainer): NA
Platform (windows/linux): Windows Docker enviornment
Command used to start Portainer (docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce ):
Browser:
Use Case (delete as appropriate): POC for business use case
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
NA

wrong tsl cert ?

wrong TLS cert ?

Thanks for checking. No, I have not enabled TLS in this config.

did you add these?

sorry, I can't help you

OH! I wonder - what's the IP address range that your Docker desktop system is using? if its the same as the IP range you're using externally, things like this can happen.

the other thing I'd try, is to make a Debian cmdline container on Docker desktop, and see if you can ping your RPI (or even better, docker run --rm -it docker  -H 192.16x.x.xx:2375 info - (so it runs where your Portainer container is running) - so see if you can connect from there.


Multiple "content_for" calls should concatenate

Currently, when you call content_for twice on a page the second call will overwrite the content captured for the first one. It would be more useful if they concatenated, just like the behaviour of content_for in Rails. Consider this example that would be made possible:
<% content_for :head do %>
   <link ref="...">
<% end %>

And somewhere else you could do:
<% content_for :head do %>
   <script src="...">
<% end %>

And then put a single <%= content_for :head %> in the layout.
It would actually be a very simple change in nanoc/helpers/capturing.rb. Just replace line 45 with this:
if @store[item.identifier][name] then
  @store[item.identifier][name] << content
else
  @store[item.identifier][name] = content
end

This wouldn’t work out of the box without breaking backwards compatibility, but it could work with a param like :append:
<% content_for :head, append: true do %>
   <script src="...">
<% end %>

vs
<% content_for :head, append: false do %>
   <script src="...">
<% end %>

vs
<% content_for :head do %>
   <script src="...">
<% end %>

(default: replace rather than append)

Do you think anybody uses the current behaviour of calling content_for twice with the same symbol, which would erase the contents of first call? I find it hard to imagine a use case for that. I think most people simply call it once so the issue never arises, so a warning of the changed behaviour in the upgrade notes would suffice. Of course, if I'm overlooking a way in which the current behaviour might be useful, then adding it as an option would be better.

It’s not possible to change the current behavior without breaking backwards compatibility, and since Nanoc 4 is so close to a final release, this behavior is not going to change before Nanoc 5.0.

FYI, I’d certainly welcome a PR that adds the new functionality (in a backwards-compatible way); it’ll end up in Nanoc 4.1 if you do so!

Ok, I don't mind making a PR, but I really don't like adding a parameter for an option for which no one can think of a use case. I'm fine with using the 1-line monkey patch until the behaviour can change in 5.0

I’m OK with a change in behavior in 5.0!

Can't you add an :append parameter that's opt-in? Would keep the default behavior untouched while enabling the new use case

I would say the current default behaviour is broken so we should remove it. Overwriting content is unexpected and especially confusing because the Rails call of the same name behaves differently. But if there is anyone who can think of a use case for the current behaviour I'm interested to hear it.

I don't know Rails but well thinking about it I would say I doubt people use the current content_for helper twice per page :)
Since it's a helper and not a core functionality I would say it could be viewed as a bug that should be fixed without waiting for 5.0?

This behaviour has been around since Nanoc 2.x, and it’s intentional, so calling it a bug and changing the behaviour won’t work.
What could be considered a bug is that the current behaviour silently overwrites previous content. I’m OK with a change that makes it raise an exception rather than overwrite content.

Yes!

:+1:

So until Nanoc 5.0, we're heading towards an :append additional parameter?

For now, I've just added addressed the silent overwriting behaviour in the pull request. Adding an additional parameter temporarily did not seem worth the trouble.

See #744 for an implementation of #content_for where the behavior is customisable (error, append, overwrite).


Added global properties to DBC class

As per user request in #70

Could you do a tester a favor and add a testcase for the assignment on globalproperties?

Will do, still a wip


https://lispkit.org links dead

I can't take a look at https://lispkit.org , is it's link broken or the website not ready ?

There is not currently a website at lispkit.org, though the domain is owned by @AeroNotix. Also see #47.

Closing this in favour of #47.
Thanks!


[WIP] Test and deployment integration

@colinbate brunch-typescript is now used by few developers. Thank you for your job and your implication.
To help futures improvements and help others developers to contribute on this plugin, I would like add test integration and deployment integration with Travis.
npm test runs simply ESLint to check that code is formatted and respect our standard (for a best readable).
Next, I would like an auto-deployment with Travis CI.
Example :

A contributor works on a feature or a fix. A PR is sent.
Travis runs test. Tests have positive result.
A contributor merges this PR. He check if package.json version is correctly incremented and add a Git tag wit the same value.
Travis runs again the test, check that Git tag as same value as package.json version and deploys then on NPM.

@colinbate Can you help me to fix the last error thrown by ESLint.

Hopefully that changeset should do it.

You may also want to add an .editorconfig file with the tab and line ending preferences. This will help others maintain consistency.

@colinbate Good recommendation. Please, give me your opinion on this file.


chefdk.rb: don't install on high sierra

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[ ] The commit message includes the cask’s name and version.

Doing this since there’s no download for it on the website. Can anyone on High Sierra confirm if manually installing the Sierra version works?

Installs ok on High Sierra.
Do we need to use #{MacOS.version} in the URL? All three "versions" have the same sha256.

https://github.com/caskroom/homebrew-cask/pull/39320


Nilan <-> Waveshare RS485-ethernet <-> HA Nilan integration 'failed to connect' error.

Hi again and sorry for bothering with stupid questions (perhaps)
My setup:
Nilan EC CTS602
Waveshare RS485 TO ETH (B) converter https://www.waveshare.com/wiki/RS485_TO_ETH_(B)
Raspberry Pi 3 and Home Assistant running in container
Nilan integration installed from HACS
When trying to add integration, I get 'Failed to connect' error:

I've managed to set up my waveshare converter (or at least I thinks so):

Loggin gives following:
'2022-12-20 00:14:37.435 ERROR (MainThread) [pymodbus.client.sync] Connection to (<IP_ADDRESS>, 502) failed: timed out'
I'm quite sure that this has something to do with my waveshare configs? First I thought that this problem is caused by running HA in container and mapping not workin between container and host. But then found out that Host <-> HA running in container have all the ports opened as a 'default' I guess.
When loggin in to my router settings, I can see waveshare IP in the ARP/RARP Table.
Perhaps some of you who has managed to get this integration work with waveshare could help. All the help is highly appreciated and hopefully even rewarded in the end.

Hi, failed to connect means that no data was exchanged. Check if you can ping it through HA.

Did that on host (raspberry os) and no answer. As well my laptop couldn’t get answer. So the problem must be with the converter network settings. Too tired to go on, have to continue tomorrow if time schedules allow. Thanks for the help 👍

Configuration is identical to mine and for me it works. Sharewave and Raspberry HA are connected to same switch.

Well, some time it's good to take a break and continue later. During the day I was trying to figure out what could be the problem.  Third chapter of ip should have been 0 but I typed 1. So changing those three ip adresses in VirCom configuration tool made it work and I could connect Nilan with no problems.
There's some strange behaviour still goin on. Temperatures and other items are jumping like crazy and some times shows 'unknown'. I also had to remove and reinstall integration before anything showed up. I'm not sure but perhaps my other raspberry running openHAB parallel to this could cause some weird stuff. It's still stable and shows everything like before. But this is one step forward and great approvement! Thanks for all the help.

Well that was a short run. Don't know what I messed (perhaps configurations.yaml and logger rows were bad). So I deleted those rows and restarted HA (couple of times). Now nothing and this is what I found from Nilan logs in the frontend:
2022-12-20 23:33:20.249 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Nilan for nilan
File "/config/custom_components/nilan/init.py", line 39, in async_setup_entry
File "/config/custom_components/nilan/device.py", line 60, in setup
File "/config/custom_components/nilan/device.py", line 124, in get_machine_type
My own fault but you learn from your mistakes, right? I know this is not topic related but perhaps someone else can get few tips of these posts.. Like I have done thousand times when faced a problem and have started googling around.

What is the question? I think you should remove the other device from the modbus, you can NOT have multiple hosts on modbus RTU since this creates a competition conflict. This error comes from not being able to read the register.

If your Modbus bridge supports multiple TCP masters you could add your other solution like that, provided they have different IP addresses.

What is the question? I think you should remove the other device from the modbus, you can NOT have multiple hosts on modbus RTU since this creates a competition conflict. This error comes from not being able to read the register.

My bad (again). I thought that Nilan controller is the master and other devices are slaves (like local control panel + other devices connected via modbus). So my assumption was that there could be more than one device and all could run parallel at the same time causing no problem to each other. I will remove my other Raspberry with RS485 - usb converter as soon as I’m familiar enough with HA.
Mistakes happen and learning takes time..

And By-the-way you should check the validity of your configuration.yaml from developer tools


[Candidate 1v1 Modern Warfare ZH v1] Map name needs changing

Issue Description
Map name is unacceptable. Modern Warfare is abstract in map context and does not describe a place.
Expected behavior
Map name fits the overall style of Official Maps and ReLaX Maps.

I don't really get what is wrong with such a name.

Modern Warfare does not refer to a map location or map situation. The terminology feels disconnected from a map.

I have no idea how to name it and I am bit scared which map name changes are coming next.
Don't think any name should refer to a map location or map situation.
Can only think of something with Green then, like Green battleground or similar.
Any ideas?

So, my suggestions are the following:

Green Battleground
Autumn Farmlands
Fertile Countryside

Autumn Farmlands looks very good I think.

Better, will rename!

Abandoned Farms it is now!

Fixed with https://github.com/xezon/GeneralsRankedMaps/commit/8e8751f7df7370d814ae670cd1041492da7dcad0


Support notNullByDefault annotations in compiled classes

There is a possible case that particular package-level annotation is available in compiled package-info.java. We need to support that.

Done


MF-571 - Add batch things-channels connection modification

Signed-off-by: Darko Draskovic<EMAIL_ADDRESS>What does this do?
Adds working things-channels connection PUT and DELETE batch request via checkbox list of things and channels.
Have you included tests for your changes?
No.
Did you document any new/modified functionality?
No.

Codecov Report

Merging #588 into ui will decrease coverage by 0.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##               ui     #588      +/-   ##
==========================================
- Coverage   86.86%   86.69%   -0.18%
==========================================
  Files          62       62
  Lines        3381     3381
==========================================
- Hits         2937     2931       -6
- Misses        305      310       +5
- Partials      139      140       +1

Impacted Files
Coverage Δ

ws/api/transport.go
80% <0%> (-7.06%)
:arrow_down:

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 f80b531...d651693. Read the comment docs.

LGTM


Adding more info

Adding my website and twitter account.

Thanks for adding your info!

Thanks for adding your info!


Mediaqueries upTo documentation correct?

Description
In the Mediaqueries page ( https://get.foundation/sites/docs/media-queries.html) > heading Javascript,
it is stated beneath the line that says
"// ↓ True for "medium" or larger"
Foundation.MediaQuery.is('medium down'); Foundation.MediaQuery.upTo('medium');
Should the line above this not be:  "// ↓ True for "medium" or SMALLER"
...
Possible Solution

...
Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title and template are correctly filled.

You are correct. Thanks for catching this. A PR which fixes this is very welcome.

Hi While investigating this i found there is more not working correctly or documented unintuitive
I made a small test script on a resize listener
console.log('is (medium up)', Foundation.MediaQuery.is('medium up'));
console.log('is (medium only)', Foundation.MediaQuery.is('medium only'));
console.log('is (medium down)', Foundation.MediaQuery.is('medium down'));
console.log('atLeast (medium)', Foundation.MediaQuery.atLeast('medium'));
console.log('only (medium) ', Foundation.MediaQuery.only('medium'));
console.log('upto (medium)', Foundation.MediaQuery.upTo('medium'));

On a small breakpoint this results in:
MediaQuery.current =  small
is (medium up) true
is (medium only) false
is (medium down) false
atLeast (medium) false
only (medium)  false
upto (medium) true
Obviously the first three are wrong when in small breakpoint, (medium up) should result in false.
and (medium down) should return  true
when the screensize is in medium this is logged:
MediaQuery.current =  medium
is (medium up) true
is (medium only) true
is (medium down) true
atLeast (medium) true
only (medium)  true
upto (medium) true
Which was throwing me off because i assumed 'upTo medium' was not 'including medium'. i was expecting upTo(medium) to be false when in medium. There is no way of telling the breakpoint is smaller then 'medium' from the context of 'medium'

Obviously the first three are wrong when in small breakpoint, (medium up) should result in false

This is currect, small is small up which, Foundation Sites is mobile first.

Obviously the first three are wrong when in small breakpoint, (medium up) should result in false

This is correct, small is small up which, Foundation Sites is mobile first.

What is correct? that (medium up) should result in false? or is it supposed to return true when in small breakpoint?

We should check that in detail. There was some confusion regarding this in the past. Which exact version of Foundation Sites do you use?

"foundation-sites": "6.6.0",
i can agree that Foundation.MediaQuery.is('medium') will result in true when on a small screen because F6 is mobile first.
But Foundation.MediaQuery.is('medium up'), NB: the UP, can't logically be true then imho.
Looking in foundation.util.mediaQuery.js i can see on #191 that 'down' is defined as atLeast(size). My guess is that up and down are wrongly swapped (line #191 and #195)

"foundation-sites": "6.6.0",

Ok, 6.6.3 is the latest / newest version. I think we fixes related issue in the releases before this.

The comments in the code also state that when there is no modifier (up, only or down) given atLeast() will be used as fallback. the actual code doesn't do that. it will fallBack to upTo();
I could make a MR to fix this.... if it is indeed wrong.

We should check that in a separate issue with a proper codepen and testcases as so far the tests do not fail. Or we do not have tests that cover this.


Audio PR - Augmentation support [ Spectrogram ]

Add Spectrogram augmentation support in MIVisionX
Introduce layouts as NHW, NFT, NTF for audio cases

@kiritigowda Synced PR branch with ToT


Add restart deployment and spawn job actions

@joaquimrocha  tested with the new changes and the code also makes more sense now, thanks


[2.1.2] Fails on Windows Vagrant Guest with Powershell Permissions

vagrant: 1.9.2 that ships with winrm 2.1.2
I was testing the new vagrant version 1.9.2 but I am having some issue with the newer winrm gem deployed with the new vagrant.
The following code works well on vagrant 1.8.x and 1.9.x before 1.9.2 that I believe ships with winrm 1.8.1
 exec { 'ExecutionPolicy-64bit':
        command   => 'Powershell.exe Set-ExecutionPolicy RemoteSigned',
        logoutput => true,
        unless    => 'Powershell.exe Get-ExecutionPolicy | C:\Windows\System32\findstr.exe RemoteSigned'
      }

Set-ExecutionPolicy : Windows PowerShell updated your execution policy
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: successfully, but the setting is overridden by a policy defined at a more
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: specific scope.  Due to the override, your shell will retain its current
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: effective execution policy of Bypass. Type "Get-ExecutionPolicy -List" to view
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: your execution policy settings. For more information please see "Get-Help
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: Set-ExecutionPolicy".
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: At line:1 char:1
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: + Set-ExecutionPolicy RemoteSigned
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns:     + CategoryInfo          : PermissionDenied: (:) [Set-ExecutionPolicy], Sec
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns:    urityException
==> admin_win2012r2: Notice: /Stage[main]/Admin/Exec[ExecutionPolicy-64bit]/returns:     + Fully

We recently started to set the execution policy to bypass for elevated powershell commands. The default policy on windows 2008R2 is Restricted which prevents users from running any scripts (local or remote). Windows 2012R2 changed that to RemoteSigned.
For automation scenarios we find bypass provides a better experience across the board by not blocking any scripts at all. That said, there is also a good argument to change this to RemoteSigned.
At any rate, you may be able to now omit this command all together. However, if you are trying to change the machine wide default policy you can set a scope to LocalMachine and wrap the command in a try to avoid the error about the local scope.


Do not automatically scale on Linux & Windows

See discussion https://github.com/DISTRHO/DPF/issues/311

I was just about to push this haha. you forgot to remove the now unused fHasScaleFactor variable. I will do that myself.

Done in 8f77ae04f7d6b978b2a6dffd92686d394ce7b9f0

I was just about to push this haha. you forgot to remove the now unused fHasScaleFactor variable. I will do that myself.

Great, I was lazy to check that. Thanks!


Avoid panic when kubeconfig is empty in online mode

When the KRM function is used in online mode (OFFLINE=false) and the KUBECONFIG is empty (because I want to build the kube config from the rest.InClusterConfig()), it panics.
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/google/k8s-digester/cmd/function.createResourceFn.func1(0xc00046c680)
	github.com/google/k8s-digester/cmd/function/function.go:58 +0x348
...

So added a check to only set the kubeconfig when the kubeconfigs slice is not empty.

Thanks for your contribution @arnabmaji !


wifibox on a Dell XPS with Atheros not starting

Hello,
I saw wifibox in the latest FreeBSD Quarterly Report and and excited to use it!
I'm on:

FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #67 main-n255572-bf46c0a9ae4e: Tue May 10 21:23:49 EDT 2022     root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

With:
none3@pci0:2:0:0:       class=0x028000 rev=0x32 hdr=0x00 vendor=0x168c device=0x003e subvendor=0x1a56 subdevice=0x143a
    vendor     = 'Qualcomm Atheros'
    device     = 'QCA6174 802.11ac Wireless Network Adapter'
    class      = network

And I installed wifibox-alpine-ath10k-20220430 (I'm pretty sure it's an ath10k)
I configured bhyve.confg with:
passthru=2/0/0

I then did sudo service wifibox onestart.
I see the following every few seconds:

2022-06-11T18:23:56-0400 WARN  The PPT device could not be destroyed

I'm unable to ping anything (not sure if I should be able to ping anything).
I looked in /var/run/wifibox/appliance/log and there are no logs.  I also did ps auxww | grep bhy and there are not running bhyve instances.
In /var/log/messages I see:
Jun 11 18:23:41 bsdell kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
Jun 11 18:23:42 bsdell kernel: ppt0: detached
Jun 11 18:23:42 bsdell kernel: pci2: <network> at device 0.0 (no driver attached)
Jun 11 18:23:48 bsdell kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
Jun 11 18:23:49 bsdell kernel: ppt0: detached
Jun 11 18:23:49 bsdell kernel: pci2: <network> at device 0.0 (no driver attached)
Jun 11 18:23:55 bsdell kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
Jun 11 18:23:56 bsdell kernel: ppt0: detached
Jun 11 18:23:56 bsdell kernel: pci2: <network> at device 0.0 (no driver attached)

One thing to note is that I currently use a USB dongle for my wifi, and I started the machine with the dongle installed and then unplugged it before starting wifibox.
Any thoughts on what's going on?  Can I acquire any more details for you or try anything?
Thank you.

Which model XPS do you have? I own a 9360 (Intel NIC, swapped to Atheros) & 9380 (Atheros NIC) and wifibox works beautifully with both.
Are your ports & binaries sync'ed to compatible versions?

Hi @orbitz and thanks for giving this project a try!  Could you please set logging to debug level in $ETCDIR/wifibox/core.conf and show us what is logged in /var/log/wifibox.log ?  I do not think that the USB dongle would cause any problem, but it is indeed better to be removed first.

Here is the output with debug:
2022-06-12T11:31:07-0400 INFO  VM manager launched
2022-06-12T11:31:07-0400 INFO  Gathering necessary configuration files for launching the guest
2022-06-12T11:31:07-0400 INFO  Pulling bhyve options from guest-specific configuration file
2022-06-12T11:31:07-0400 INFO  Pulling bhyve options from configuration file
2022-06-12T11:31:07-0400 DEBUG cpus=1, memory=128M, passthru=2/0/0, console=no
2022-06-12T11:31:07-0400 INFO  Guest console is not configured to use
2022-06-12T11:31:07-0400 INFO  Passthru device is configured: 2/0/0
2022-06-12T11:31:07-0400 INFO  PPT driver is configured for pci2:0:0 device
2022-06-12T11:31:07-0400 INFO  tap interface is configured: tap2
2022-06-12T11:31:07-0400 INFO  Pulling WPA Supplicant control options from configuration file
2022-06-12T11:31:07-0400 DEBUG wpa_ctrl.enabled=yes
2022-06-12T11:31:07-0400 INFO  wpa_supplicant.conf will be mounted writable
2022-06-12T11:31:07-0400 INFO  Launching guest wifibox from /usr/local/share/wifibox with grub-bhyve
2022-06-12T11:31:07-0400 DEBUG Arguments:  -S -M 128M -r host  -d /usr/local/share/wifibox wifibox
2022-06-12T11:31:07-0400 DEBUG [grub-bhyve] Error opening terminal: unknown.
2022-06-12T11:31:07-0400 INFO  Destroying guest wifibox
2022-06-12T11:31:08-0400 INFO  Destroying bhyve PPT device: pci2:0:0
2022-06-12T11:31:08-0400 DEBUG [devctl] devctl: Failed to clear pci2:0:0 driver: Device not configured
2022-06-12T11:31:08-0400 WARN  The PPT device could not be destroyed
2022-06-12T11:31:08-0400 DEBUG exit_code=1
2022-06-12T11:31:08-0400 INFO  grub-bhyve failed to start, signaling restart after 5 seconds
2022-06-12T11:31:14-0400 DEBUG Program started as /usr/local/sbin/wifibox, with arguments: stop

I'm not sure if this matters but I have not enabled wifibox to start on boot.  I've been testing it where I manually start it.  Is that OK?  The FreeBSD wiki page implies that for passthru to work maybe it needs to be a configuration at boot?
https://wiki.freebsd.org/bhyve/pci_passthru

@thesunexpress  I have a Dell XPS 9370.  I'm not sure exactly how to tell if everything is synced properly.  I am on the kernel commit I mentioned, which is a month or so old at this point.

Thanks!  It seems that grub-bhyve could not start up for some reason, that is why there is no bhyve process as well.  Let me try to understand what is going on there, I have not seen such errors before.

Looks like this has something to do with the TERM environment variable.  What is the value of that in your case?  That is, could you please post the output for the echo $TERM command?  That is xterm for me, and it is working.

I'm not sure if this matters but I have not enabled wifibox to start on boot. I've been testing it where I manually start it. Is that OK? The FreeBSD wiki page implies that for passthru to work maybe it needs to be a configuration at boot?

Ideally, it does not require you to configure the start on boot.  Everything should be handled automatically unless stated otherwise in the manual page.  For example, AMD-Vi has to be configured before trying to run Wifibox but that is documented.

My $TERM is screen

Okay, let me summarize the situation here.  You launch wifibox via screen through sudo locally.  Is there any non-standard configuration setting present on your system?

Technically I'm using tmux, and my terminal emulator is st as well.  I don't know if I have any non-standard configuration.  Anything specific I should look for?

Based on the grub-bhyve error message, this is an ncurses initialization problem.  Thus I believe that anything that has any impact on the terminal definitions (termcap, terminfo, etc.) or the version of ncurses used might cause this.  Which ncurses version do you use?  Is it from the base or from the Ports Collection?  It would be good to see which libncurses.so the grub-bhyve binary is linked to.  For example, the following command could tell this:
$ ldd $(whereis grub-bhyve | cut -d ':' -f2) | fgrep ncurses
        libncurses.so.8 => /lib/libncurses.so.8 (0x800742000)

I am currently trying to reproduce your problem but without success so far.

I was able to reproduce the problem to some degree by moving away all the termcap files.  I am inclined to think that the same could also happen if the termcap database is corrupted.  I booted a 14.0-CURRENT-20220610-e50e40684aa-256063 snapshot and Wifibox just worked as expected.  Based on that, it should not be specific to 14-CURRENT, however, the specific version you showed in the description might have problems with termcap.

So my kernel was out of alignment with my pkgs database, so I fixed that, but it dosen't appear to have resolved the issue.  I can confirm that the ncurses lib that grub-bhyve uses (libncursesw.so.9) exists.  I can also run grub-bhyve by hand (I get a help screen) so at least that suggests to me that it can find its libraries.  I'm now on:

FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #68 main-n256081-987d26ee3f7a:

I don't know how to verify the termcap situation.  I'm compiling my own kernel, installing world, etcupdate yadda.  Everything else works.  I'll play with it some more tomorrow.
Thank you for the quick responses.  Let me know if there is anything else you'd like me to do to test.

Also, I do not know if this matters, but I have my own ubuntu and alpine bhyve VMs (which I have not been running during this due to a vmm conflict), but they run fine for me, I imagine they are using grub-bhyve as well.

I tried to analyze the behavior of grub-bhyve with the help of truss(1).  Looks like ncurses is not utilized all the time only if tmux is in use.  Have you tried to launch wifibox without using tmux?  Also, it would be interesting to see the truss(1) output of the problematic command itself.  Maybe only the way how grub-bhyve is used with wifibox causes the trouble.
# truss -o /tmp/grub-bhyve.truss.log /usr/local/sbin/grub-bhyve -S -M 128M -r host -d /usr/local/share/wifibox wifibox
# bhyvectl --vm=wifibox --destroy

When launched in a tmux-hosted terminal, the following could be noticed:
# grep -F termcap /tmp/grub-bhyve.truss.log
open("/root/.termcap.db",O_RDONLY|O_CLOEXEC,00)  ERR#2 'No such file or directory'
open("/root/.termcap",O_RDONLY|O_CLOEXEC,00)     ERR#2 'No such file or directory'
open("/usr/share/misc/termcap.db",O_RDONLY|O_CLOEXEC,00) = 4 (0x4)

@thesunexpress I have a Dell XPS 9370. I'm not sure exactly how to tell if everything is synced properly. I am on the kernel commit I mentioned, which is a month or so old at this point.

Neat, you've got the model right in between my 2 XPS 93xx. Looks like it has the same soldered NIC on the motherboard.
The reason I ask is this:  Whilst testing between FreeBSD 13-STABLE & 14-CURRENT, along with wifibox versions 0.5 and 0.6, specifically testing functionality, stress & intentionally breaking it, I came across situations where console logs like yours:
kernel: ppt0 mem 0xdc000000-0xdc1fffff irq 18 at device 0.0 on pci2
kernel: ppt0: detached
kernel: pci2: <network> at device 0.0 (no driver attached)
What became apparent is that any time the kernel sources & ports were far enough out of sync, vmm.ko (at least so far as what ends up copied into /boot/modules/) and would break and dump. Console would be spammed with a attach/detach loop that looked very similar to what you've got going on. I'm annoyed with myself  that I didn't save those logs for comparison now.
Using -STABLE / -CURRENT meant I'd be commonly using the most recent source & ports (pretty much 0-day).
Curious you are having some problems, for me it works out of the box without so much as a peep other than initial bhyve.conf & wpa_supplicant.conf configuration; your NIC is effectively identical to mine.

@pgj
orbitz@bsdell ~> grep -F termcap /tmp/grub-bhyve.truss.log
fstatat(AT_FDCWD,"/etc/termcap",{ mode=-r--r--r-- ,inode=930947,size=212544,blksize=131072 },0x0) = 0 (0x0)
fstatat(AT_FDCWD,"/usr/share/misc/termcap",{ mode=-r--r--r-- ,inode=930947,size=212544,blksize=131072 },0x0) = 0 (0x0)

I also tried running outside of tmux in two ways:

Just in an st window
Via dmenu.

No luck.

@orbitz would it be possible to share the complete log file somehow?  It would be interesting to see what else grub-byhve tries to do besides accessing the termcap files which eventually leads to the failure.  By the way, when running the command by itself, do you get the Error opening terminal: unknown. error message?

@thesunexpress I think this problem is not specific to the actual hardware, it appears to be a software configuration issue or bug.  We did not even get to the point to try to run the VM due to the failure of grub-bhyve.

I switched from using the service to running wifibox by hand.  Good news:  It started!  Bad news, no luck on connecting to wifi and after a bunch of starts and stops, my system became unstable and stopped responding and I had to reboot.

Jun 14 00:30:24 wifibox daemon.warn wpa_passthru[971]: /var/run/wpa_supplicant/wlan0 is not available, skipping.
Jun 14 00:30:24 wifibox daemon.info wpa_passthru[971]: Waiting for PID 999 to stop.

So clearly there is a problem there, not sure what.  (does the /usr/local/etc/wifibox/wpa_supplicant/wpa_supplicant.conf file need any specific privs?)

These logs are after I restarted and ran start again.  I still have my wifi dongle plugged in so could be conflicting there

I rebooted without the dongle and started wifibox.
Jun 14 00:39:36 wifibox cron.info crond[1002]: crond (busybox 1.34.1) started, log level 8
Jun 14 00:39:36 wifibox daemon.info : starting pid 1062, tty '/dev/ttyS0': '/sbin/getty -L ttyS0 115200 vt100'

wifibox.log
2022-06-13T20:39:19-0400 DEBUG Program started as /usr/local/sbin/wifibox, with arguments: start
2022-06-13T20:39:19-0400 INFO  Begin: wifibox start
2022-06-13T20:39:19-0400 DEBUG assert loaded: kmod=vmm, kmod_file=vmm.ko
2022-06-13T20:39:19-0400 DEBUG Kernel module vmm is not loaded
2022-06-13T20:39:19-0400 DEBUG Kernel module vmm was loaded successfully
2022-06-13T20:39:19-0400 DEBUG assert hardware support present: iommu=1, amdvi=0
2022-06-13T20:39:19-0400 DEBUG Backends reported by bhyve:
2022-06-13T20:39:19-0400 DEBUG [bhyve] ahci
2022-06-13T20:39:19-0400 DEBUG [bhyve] ahci-hd
2022-06-13T20:39:19-0400 DEBUG [bhyve] ahci-cd
2022-06-13T20:39:19-0400 DEBUG [bhyve] e1000
2022-06-13T20:39:19-0400 DEBUG [bhyve] dummy
2022-06-13T20:39:19-0400 DEBUG [bhyve] hda
2022-06-13T20:39:19-0400 DEBUG [bhyve] fbuf
2022-06-13T20:39:19-0400 DEBUG [bhyve] amd_hostbridge
2022-06-13T20:39:19-0400 DEBUG [bhyve] hostbridge
2022-06-13T20:39:19-0400 DEBUG [bhyve] lpc
2022-06-13T20:39:19-0400 DEBUG [bhyve] nvme
2022-06-13T20:39:19-0400 DEBUG [bhyve] passthru
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-9p
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-blk
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-console
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-input
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-net
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-rnd
2022-06-13T20:39:19-0400 DEBUG [bhyve] virtio-scsi
2022-06-13T20:39:19-0400 DEBUG [bhyve] uart
2022-06-13T20:39:19-0400 DEBUG [bhyve] xhci
2022-06-13T20:39:19-0400 INFO  Creating bridge interface: wifibox0
2022-06-13T20:39:19-0400 DEBUG [ifconfig] wifibox0
2022-06-13T20:39:19-0400 INFO  Linking tap interface to wifibox0: tap2
2022-06-13T20:39:19-0400 INFO  Waiting for bhyve to start up
2022-06-13T20:39:19-0400 DEBUG Program started as /usr/local/sbin/wifibox, with arguments: _manage_vm
2022-06-13T20:39:19-0400 DEBUG assert daemonized: parent=daemon
2022-06-13T20:39:19-0400 INFO  VM manager launched
2022-06-13T20:39:19-0400 INFO  Gathering necessary configuration files for launching the guest
2022-06-13T20:39:19-0400 INFO  Pulling bhyve options from guest-specific configuration file
2022-06-13T20:39:19-0400 INFO  Pulling bhyve options from configuration file
2022-06-13T20:39:19-0400 DEBUG cpus=1, memory=128M, passthru=2/0/0, console=no
2022-06-13T20:39:19-0400 INFO  Guest console is not configured to use
2022-06-13T20:39:19-0400 INFO  Passthru device is configured: 2/0/0
2022-06-13T20:39:19-0400 INFO  PPT driver is configured for pci2:0:0 device
2022-06-13T20:39:20-0400 INFO  tap interface is configured: tap2
2022-06-13T20:39:20-0400 INFO  Pulling WPA Supplicant control options from configuration file
2022-06-13T20:39:20-0400 DEBUG wpa_ctrl.enabled=yes
2022-06-13T20:39:20-0400 INFO  wpa_supplicant.conf will be mounted writable
2022-06-13T20:39:20-0400 INFO  Launching guest wifibox from /usr/local/share/wifibox with grub-bhyve
2022-06-13T20:39:20-0400 DEBUG Arguments:  -S -M 128M -r host  -d /usr/local/share/wifibox wifibox
2022-06-13T20:39:20-0400 INFO  Launching guest wifibox from /usr/local/share/wifibox with bhyve
2022-06-13T20:39:20-0400 DEBUG Arguments:  -c 1 -m 128M -AHP -u -S  -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/usr/local/share/wifibox/disk.img -s 4:1,virtio-9p,config=/usr/local/etc/wifibox,ro -s 4:2,virtio-9p,wpa_config=/usr/local/etc/wifibox/wpa_supplicant -s 4:3,virtio-9p,var=/var/run/wifibox/appliance -s 5:0,e1000,tap2 -s 6:0,passthru,2/0/0 wifibox
2022-06-13T20:39:20-0400 DEBUG [bhyve] rdmsr to register 0x140 on vcpu 0
2022-06-13T20:39:20-0400 DEBUG [bhyve] rdmsr to register 0x64d on vcpu 0
2022-06-13T20:39:20-0400 DEBUG [bhyve] rdmsr to register 0x64e on vcpu 0
2022-06-13T20:39:20-0400 DEBUG [bhyve] rdmsr to register 0x34 on vcpu 0
2022-06-13T20:39:20-0400 INFO  Guest wifibox has started up
2022-06-13T20:39:20-0400 INFO  Guest is managed by PID 2615
2022-06-13T20:39:20-0400 INFO  Bringing up WPA pass-through
2022-06-13T20:39:20-0400 INFO  Control interface: /var/run/wpa_supplicant
2022-06-13T20:39:20-0400 INFO  Found guest IP address: <IP_ADDRESS>
2022-06-13T20:39:21-0400 INFO  Control interface group: 0
2022-06-13T20:39:21-0400 INFO  WLAN devices: [p2p_dev_wlan0
wlan0]
2022-06-13T20:39:21-0400 INFO  Hooking up <IP_ADDRESS>:1201 as /var/run/wpa_supplicant/p2p-dev-wlan0
2022-06-13T20:39:21-0400 INFO  Hooking up <IP_ADDRESS>:1200 as /var/run/wpa_supplicant/wlan0
2022-06-13T20:39:21-0400 INFO  End: wifibox start

When running, I can see that the /var/run/wpa_supplicant files exist, however running wpa_cli status times out
orbitz@bsdell ~> wpa_cli status
Selected interface 'wlan0'
'STATUS' command timed out.
orbitz@bsdell ~> sudo wpa_cli status
Selected interface 'wlan0'
'STATUS' command timed out.

I think first we should make sure that the wireless device is created on the VM.  To check this, I would recommend you to enable the console in bhyve.conf and try the wifibox console command (you can login as root there with a blank password).  Then post the output of the lsmod and ifconfig commands to see what is going on inside.  You can even try to launch wpa_supplicant in the foreground.

Is the wifibox0 interface configured properly on the host?  Can you ping the guest on <IP_ADDRESS>?

Thanks for the logs.  You will have to assign an IP address for the wifibox0 interface and ensure that it can be routed.  This could either be done via DHCP or statically, that is up to your local configuration.  For example, dhclient wifibox0 could be used to try DHCP.

Is that the case even if I can't ping <IP_ADDRESS>?

Yes, I believe so.  The guest has the "virtual" <IP_ADDRESS> IP address which is not visible on the host.  On the host there shall be an IP address on the same network (<IP_ADDRESS>/24) to communicate with the guest.  dhclient can get an IP address with the wifibox0 interface from udhcp running on the guest, as well as configure the default gateway to point to <IP_ADDRESS>.

IT'S WOOOORKIIIIIIIIIIIIIIIIING!  Wooo, thank you!
I'm still not sure why I need to run wifibox rather than via the service.

Question, what is the relationship between my existing wpa_supplicant.conf file and the one for wifibox.  Is it fine to just copy my host wpa_supplication.conf file to the /usr/local/etc/wifibox configuration?

Another question:  I use bhyve to run VMs for work and I have the following pf.conf:
nat on wlan0 from <IP_ADDRESS>/8 to any -> (wlan0)
nat on wlan0 from <IP_ADDRESS>/24 to !<IP_ADDRESS>/24 -> (wlan0)

Should there be any issue with running wifibox and my other linux vm's at the same time?  I know wifibox doesn't like it if I start my linux VMs first because of the vmm kernel module.  And I suppose I can just turn wlan0 into wifibox0?
Thank you

Question, what is the relationship between my existing wpa_supplicant.conf file and the one for wifibox. Is it fine to just copy my host wpa_supplicant.conf file to the /usr/local/etc/wifibox configuration?

Yes, it should be just fine to use the same file -- it will be actually processed by the same program but on a different platform.

Should there be any issue with running wifibox and my other linux vm's at the same time? I know wifibox doesn't like it if I start my linux VMs first because of the vmm kernel module.

This should work, I also have other bhyve-based VMs besides wifibox locally.  What Wifibox does not like is when it needs to revive the PCI pass-through after the ACPI resume event.  That is when the vmm(4) has to be unloaded and then re-loaded to restore the functionality.   When other guests use vmm(4) at the same time it cannot and will not be unloaded.  But it can safely co-exist with others.

I suppose I can just turn wlan0 into wifibox0?

Yes, that is right.

I still need to confirm, but I think it's turning the console on that allows running via service.

@orbitz I have seen that you closed the issue: did you eventually solve the problem with grub-bhyve?  It would be still nice to understand what could have caused it but it may show up at other users.

@pgj  I closed the issue for the main problem: getting it working.  I'll do some testing with turning console back off and see if it has trouble starting again.  I'm not sure why the console setting change that behaviour, though.  Note: this happened even during bootup, now that I have wifibox enabled on startup.

By the way, just to clarify (I am still looking for ways to reproduce the problem): how do you turn on and off the console?  Is this about the settings in /etc/ttys or is it something else?

The option in bhyve.conf.  Again, I still need to confirm, but so far it seems like if console is no then I hit this issue, and if it's yes, I don't.

Ah, now it makes sense (to some extent).  On your system, grub-bhyve does not have a tty allocated when Wifibox is launched as a service and it fails.  When the Wifibox console is turned on, a null-modem device is assigned as the tty so ncurses can work happily.


How to use options in CLI?

Looking at the source code the only accepted options with the provided html-pdf, all that is accepted is:
    html-pdf source.html destination.pdf
see: https://github.com/marcbachmann/node-html-pdf/blob/master/bin/index.js


SwipePanel not working in Framework7 2.0.0-beta.8

Hello, I'm newbie, I'm using Framework7 2.0.0-beta.8, it has a bug that the "swipePanel" function does not work.

Hello,
Have you tested on the latest version : Framework7-2.0.0-beta.17 ?

Update to latest beta

Framework7-2.0.0-beta.17, not working in android cordova.


Migrating problems with pg_search to Heroku

Hey everyone,
I'm having problems with migrating an existing Rails 2.3.17 app to Heroku. It works totally fine with my custom EC2 Rails stack but on Heroku Cedar with Postgres 9.1 I can't seem to get it to work.
In my Gemfile I have:
gem "pg","~> 0.14.1"
gem "pg_search", "~> 0.2.1"

In my model I have:
class User < ActiveRecord::Base
    include PgSearch
    pg_search_scope :search_by_full_name, :against => [:first_name, :last_name, :login]

When I run it in the console:
ayl$ heroku run console production
Running `console production` attached to terminal... up, run.6486
Loading production environment (Rails 2.3.17)
> User.search_by_full_name("asdf")
NoMethodError: undefined method `search_by_full_name' for #<Class:0x00000004cd41b0>
	from /app/vendor/bundle/ruby/1.9.1/gems/activerecord-2.3.17/lib/active_record/base.rb:2002:in `method_missing'
	from (irb):1
	from /usr/local/bin/irb:12:in `<main>'

I've been beating my head against the wall trying to figure this out to no avail... Help?

Closing this out because it is old and deals with an outdated version of pg_search. Feel free to open a new issue if anything similar comes up again with the latest versions. Thanks!


Heads-up: 8u222-b03 will include cacerts backport from JDK 11

See: http://hg.openjdk.java.net/jdk8u/jdk8u-dev/jdk/rev/cac1aa619936
It'll be included in the next tagged build in jdk8u/jdk8u. I expect this to cause issues for the hg-git mirror job. ETA a week from now.

Will you remove the option from the adoptopenjdk build script then?

Will you remove the option from the adoptopenjdk build script then?

Once we confirm it's the same list, yes

@karianna can this be closed now?

@johnoliver Should we remove the option from the build scripts?

File in jdk8u is the same as the one that was in jdk11u (until today - was removed in https://github.com/AdoptOpenJDK/openjdk-jdk11u/commit/f27021a230a82a2d5eeda7859fb08586a0872456 thus causing breaks on Windows JDK8u builds today


Speed up CI with "official" docker caching (available with github actions)

Is your enhancement request related to a problem? Please describe.
CI could always be faster...
great speedups were already introduced with:
https://github.com/apache/pulsar/pull/10001
Describe the solution you'd like
I'm not sure but maybe looking into some infos/details documented here (directly and in linked articles) may help to speed up further:

Hi, I wrote the article mentioned above which has been outdated and superseded by another Evil Martians’ article.
TL;DR — Docker has published an official action docker/build-push-action which has an option to make Docker use GitHub Cache API directly as a cache storage. With this settings my build time dropped from 5 minutes to 1 minute.
          cache-from: type=gha
          cache-to: type=gha,mode=max

source: comment of @dtinth, on Oct 27, 2021
in github/actions/cache/docker caching
https://github.com/actions/cache/issues/31#issuecomment-952545077

cc @lhotari is this helpful for our current CI workflow?

cc @lhotari is this helpful for our current CI workflow?

@tisonkun No.

Closing since docker images are cached in the current workflow.


feat(hypr): use swappy for screenshots

https://youtu.be/J1L1qi-5dr0

I don't think I will implement this. Less is more.


Load images into Lona

Hi,
I was wondering how we can load images via the Img tag in Lona. i tried to use the example below, but nothing is displayed on the screen.
self.nodes = [
       Div(
            Img(src="image.png")
)
]

is this the right way to do it or there is another way ?
Many thanks!

Hi @eldjoko,
yes, this is the right way, but you need a view that actually serves image.png. You can add the image to your static files and add change src to /static/image.png, or you create a generic view that returns a lona.FileResponse containing image.png.
Static files are more for images that change rarely, a more generic mechanism using lona.FileResponses are more suitable for changing media files. I can provide you a simple prototype for both.

Thank you! yeah! a sample prototype would be helpful
i tried to do:
STATIC_FILES = [
         StaticFile(name='image', path='/static/image.png')
]

but this didn't work.

@eldjoko: Sorry it took me so long. I made an example for you that contains both solutions I proposed.
#!/usr/bin/env python

import os

from lona import App, View, FileResponse, NotFoundError
from lona.static_files import StaticFile
from lona.html import HTML, H1, Img, P

app = App(__file__)

@app.route('/media/<path:.*>', interactive=False)
class MediaFileViwe(View):
    def handle_request(self, request):
        path = request.match_info['path']

        if not os.path.exists(path):
            raise NotFoundError

        return FileResponse(path)

@app.route('/')
class ImageView(View):
    STATIC_FILES = [
        StaticFile(
            name='logo.svg',
            path='doc/content/logo.svg',
            url='logo.svg',
        ),
    ]

    def handle_request(self, request):
        return HTML(
            H1('Images'),

            P('Static Image'),
            Img(src=f'{self.server.settings.STATIC_URL_PREFIX}logo.svg'),

            P('Media Image'),
            Img(src='/media/doc/content/logo.svg'),
        )

app.run()

@eldjoko: Do you need any additional help? Can I close this issue?

@fscherf Safe to close. thank you for your help for the examples!!!


Route component doesn't update component upon store update

I am new to react, react-router, redux and react-redux. I am trying to connect() route component to store like this.
export default connect(mapStateToProps, null)(UserPage);
<Router>
  <Route path="/" component={HomePage} />
  <Route path="/user" component={UserPage} />
</Router>

But when store is updated the UserPage component doesn't not re-render and get props.
Please help me solve it. Thanks

See this guide: https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/guides/blocked-updates.md


Adding support for GCD dev server in datastore package.

Enabling

set_default_dataset_id() support for DATASTORE_DATASET environment
variable name
gcloud.datastore.Connection.API_BASE_URL override for
DATASTORE_HOST environment variable name

Fixes #650.

@tseaver Note the super-hacky way to test the import time class constant definition. I'd love a better way if anything comes to mind (I think about a module level constant, but this still happens at import time)

I tested and confirmed this works with gcd

Coverage remained the same at 100.0% when pulling d2aaab844cb2f4fb527eb108dc23edc9f5f3285c on dhermes:fix-650 into 8e68a20cce2306f055557362b0c4a34909a36d1e on GoogleCloudPlatform:master.

I'm not sure about doing stuff at import time.  Could we add a class method to update the various constants, and then call it from within set_defaults(), IFF the environment variable is present?

I like the idea but am worried about the interdependence between the modules.
It may be possible to just use a api_base_url() class method since the base class never uses API_BASE_URL and our only use in datastore code is
api_base=(base_url or cls.API_BASE_URL),

We could change build_api_url() to an instance method (the only non-test caller already dispatches through the instance) and then have set_defaults() (or its minions) stamp the GCD version on the constructed connection instance.  I don't think that introduces any new coupling.

The issue is that people may make a Connection in another way than set_default_connection().

Then they can set the attribute on that instance (or pass it to the constructor, if we think supporting it is important enough).

@tseaver PTAL
I didn't need to interact with set_default_...() since DATASTORE_HOST is used for this while DATASTORE_DATASET is used for the actual string ID.

Coverage remained the same at 100.0% when pulling b9aaf101c122c2671b2ddd431900a55eb4730680 on dhermes:fix-650 into 8e68a20cce2306f055557362b0c4a34909a36d1e on GoogleCloudPlatform:master.

@tseaver How do you like this approach for #573?

LGTM.  I like the instance attr / method approach.