unable to access the URL and unable to expose port after the integration build is successfully deployed.

Here, I have used a simple code to expose the REST url as i mentioned below

when I run the Kamel command for the same REST code, the build got successful and shown message like "Listening on: http://<IP_ADDRESS>:8080", below I have shared the screenshot for the same.

But Iam not able to access the url as mentioned above, I have tried different ways to access like
http://<IP_ADDRESS>:8080/hello
http://localhost:8080/hello
http://<IP_ADDRESS>:8080/hello in web browser as well as in postman, still no use.
later I got to know that we need to expose the port in docker to access the actual 8080 port, so i tried below mentioned command to expose outside the docker "docker run -it -p 8080:8080  " but every time iam getting same error as shown below

I want to know where i am doing wrong and how can i resolve this.

What you are looking for is port forwarding https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/
Camel-K should have created a service automatically for you.
You can check it with the next command:
kubectl get svc -n <your-namespace-here>
NAME       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
rest-dsl   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    82s

In the previous example, the service rest-dsl is listening on port 80 so assuming that you would like to access your application from port 8080 on your local machine, the  corresponding port-forward command is then:
kubectl port-forward svc/rest-dsl 8080:80 -n <your-namespace-here>

The code of the integration that I used:
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.Exchange;

public class RestDSL extends RouteBuilder {

    @Override
    public void configure() throws Exception {
    	rest()
    		.get("/hello")
    		.to("direct:hello");
        from("direct:hello")
        	.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
            .transform().simple("Hello, Camel K");
    }
}

Thank you @essobedo, It started working with your command, I have tried many ways to expose the port but none of them are worked, thank you for your dedication to resolve my issue and now I am able to expose the port and able to access it, Thank you so much.

I have a question, do we need to run "kubectl port-forward svc/rest-dsl 8080:80 -n " command every time when ever we want to expose the above "RestDSL" class? is there any other way to expose while using the "kamel run "command itself.?
the issue with this is, if the code has changed then the port-forwarder is stopping immediately, so need to start again every time to access the url.

Well, this is required if you're on a local cluster such as Minikube or the like. With the port-forward, you'll be able to "see" the Kubernetes service which otherwise is not available. In a real environment, you should be able to access the service OOTB.

Just to avoid misunderstanding, if your goal is to access your service from localhost, port-forward will always be needed whatever the cluster used behind (local or not)

If your goal is to access your rest end point from outside the K8s cluster, you will need to add an ingress https://kubernetes.io/docs/concepts/services-networking/ingress/


won't compile

in downsampler there is for loop so output_shot
got multiple drivers
--                                              output_shot <= shot;
and  in scopeio 1shot generate block, this parameter is is missing
at downsampler:
inputs  => inputs,

I think it's fixed.

yes fixed


Take into account MongoClient's write concern (#1053)

Looks good.  thanks for the patch.

you are welcome


Unable to import Enums from Prisma generated with Deno

Bug description
I'm using Enum on schema, on vscode intellisense it's everything ok. But when running deno run --unstable --watch --allow-net --allow-read --allow-env ./src/index.ts throw this error:
error: Uncaught SyntaxError: The requested module '../../generated/client/deno/edge.ts' does not provide an export named 'Role' import { Prisma, Role } from "../../generated/client/deno/edge.ts";

How to reproduce

Copy schema
Run: deno run -A npm:prisma db push
Run:  deno run -A npm:prisma generate --data-proxy
Copy code provided
Run: deno run --unstable --watch --allow-net --allow-read --allow-env index.ts

Expected behavior
No response
Prisma information

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["deno", "clientExtensions"]
  output          = "../generated/client"
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DATABASE_URL_DIRECT")
}

model User {
  id         Int        @id @default(autoincrement())
  username   String    @unique
  role       Role       @default(USER)
  createdAt  DateTime   @default(now())
  updatedAt  DateTime   @updatedAt
}

enum Role {
  USER
  ADMIN
  OWNER
}

import { Role } from "../generated/client/deno/edge.ts";

const test = "USER";

if (test === Role.USER) {
  console.log("USER");
} else {
  console.log("ADMIN");
}

Environment & setup

OS: Ubuntu 20.04
Database: PostgreSQL
Deno version:

deno 1.33.3 (release, x86_64-unknown-linux-gnu)
v8 <IP_ADDRESS>
typescript 5.0.4

Prisma Version
"prisma": "^4.14.0"

I can confirm this is inconvenience to me as I have to write on my own

Similar issue: https://github.com/prisma/prisma/issues/18015

Can confirm, I was able to reproduce this on 5.1.1
Steps I took:
$ deno run npm:prisma init
# copied schema
# copied code
$ deno run -A npm:prisma generate (--data-proxy - data-proxy doesn't seem to influence this)
$ deno run main.ts

Hey I'm facing the same issue, have you found the solution ?


Intent for this implementation - will it only be an Intermediate language?

Summary of the new feature / enhancement
Shifting this to a new topic, since I originally put the below idea/comments in a different issue which was related to parallel execution only because I was tagged in that specific issue.

https://github.com/PowerShell/DSC/issues/395#issuecomment-2048311646

The original concern was related to how we would do cross resource references for things like dependson.

I had seen some examples where multiple levels of nesting (of languages) e.g. functions are embedded in yaml or json and this was concerning for me, since it's not inviting for me to write/author and maintain. I can understand that if the intent was for this to be an intermediate language, then that would perhaps be required, however I wanted to get an idea on this up front.
Can we please plan now to have an authoring experience based on Bicep Language? People can still use yaml or json, however I feel like the advantages of Bicep is extremely compelling.
More on why I think this is important.

Bicep utilizes "symbolic-name" for cross referencing resources
Bicep has a rich set of functions, ~many~ most of which are implemented within Bicep itself and doesn't rely on the ARM engine
Bicep is designed to build to json
Bicep has custom types and an extensibility model
simple/clean Bicep language for Configurations

avoids embedding other languages in json/yaml Etc.

simple/clean Bicepparam files for ConfigurationData

Some examples

Radius have taken to extend Bicep in a way that would exactly meet the need that I am interested in this core tool of DSC to be extended.

https://github.com/radius-project/radius
https://github.com/radius-project/bicep

More specifically, here is a prototype for the extension of Bicep in a way that does not reply on ARM (Resource Manager) at all.

https://github.com/anthony-c-martin/bicep-local-providers

Extension types included as part of this example/concept:

github
kubernetes
utils

example 2 above is the main reason for writing this thread/idea/feature request and I really hope this could get some traction

tagging @anthony-c-martin in case you can get the opportunity to chat with @SteveL-MSFT or @mgreenegit if you haven't had the chance to share each sides of your visions on Configuration Management.
I hope that it's possible for this to be more of a case of not if but when.
I know resources are limited, so perhaps this just becomes a community project up front?

Proposed technical implementation details (optional)
for simplicity I will link to the above utils sample in the:

https://github.com/anthony-c-martin/bicep-local-providers/tree/main/samples/utils

using 'script.bicep'

// This sample only works on an OS with bash installed
param name = 'Anthony'
param platform = 'bash'

provider utils

param name string
param platform 'bash' | 'powershell'

resource sayHelloWithBash 'Script' = if (platform == 'bash') {
  type: 'bash'
  script: replace(loadTextContent('./script.sh'), '$INPUT_NAME', name)
}

resource sayHelloWithPowerShell 'Script' = if (platform == 'powershell') {
  type: 'powershell'
  script: replace(loadTextContent('./script.ps1'), '$INPUT_NAME', name)
}

output stdout string = (platform == 'bash') ? sayHelloWithBash.stdout : sayHelloWithPowerShell.stdout

@brwilkinson would you mind if we scheduled time for deeper discussion?

@mgreenegit did you have a chance to talk with @anthony-c-martin?


[AppService] Updated linuxFxVersion configuration for linux apps.

Resolves #11257
History Notes:
[AppService -- functionapp] (az functionapp create) Updated the way linuxFxVersion and container image name were being set for linux function apps.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

@Hazhzeng @ankitkumarr Can you take a look when you have time?
@pragnagopa FYI

add to S166. Hi @qwordy  could you pls review this PR? thanks.

@gzuber PR ready to merge？

@qwordy This should be good to merge, thanks!


jsx-uses-vars and no-unused-vars causes false warning

I'm filing this one here, though it could be something that will need followup elsewhere.
<EMAIL_ADDRESS><EMAIL_ADDRESS>Given the following code:
import React from 'react';
import foo from 'foo';

export const AccessibilityDecorator = foo((config, Wrapped) => {
	return class t extends React.Component {
		render = () => {
			return <Wrapped />;
		}
	};
});

And the following .eslintconfig.json:
{
	"parser": "babel-eslint",
	"plugins": [
		"babel",
		"react"
	],
	"extends": ["plugin:react/recommended"],
	"rules": {
		"no-unused-vars": 1
	}
}

The following warning is given:
  4:44  warning  'config' is defined but never used  no-unused-vars

Expected output:  No warning.
The default behavior of eslint is to only warn on unused parameters that come after the last used parameter.  jsx-uses-vars flags Wrapped as used but it leaves config marked as unused.  Should this be picked up automatically by eslint?  Or, will this require some heroics on the part of the react plugin to find these and fix them?

Why on earth is render a class field instead of an instance method?

Separately, I would expect config to be left marked as unused, because it is unused - the default settings for no-unused-vars, for the "args" setting is indeed after-used, but I would assume this is something eslint can figure out.
If it's not figuring it out, then I think that's a bug in no-unused-vars - specifically, it might have to wait to do its checking on program exit to ensure all the variables have time to be marked as used.

It was just a minimal sample, that's all. It's not reflective of any actual code.  I will cross-file this to eslint.

fwiw, I made a PR with eslint that fixes this issue, so I'll close this.


JSONP newline compatibility

Awesome extension! But I encountered a problem about JSONP;
Data structure like this:

for some reason, our background player add a newline here.
Here is the link.
Can you help with this problem, thanks.

This should definitely work, I'll take a look.
Thanks!


Parallels 16, issues with host connected to Shared network

Hi,
I just wanted to give a quick heads up, I assume this is due to a bug in parallels 16. after Upgrading to 16 I ran into the following message when trying to start the docker-machine instance:
Starting "docker"...
Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'

I check the UI and the option is enabled, I also tried with prlsrvctl net set Shared --connect-host-to-net on, however the Bound To: is no where to be found.
If I remove the check in isSharedConnected() just for testing and it seems to work fine, so I suspect it's a issue with the output from the command.
I will also raise the issue on the parallels forum

I am also experiencing this issue. @MadsJakobsen mind sharing where isSharedConnected() is so I can see if removing the check fixes my issue as well?

Hi @matttarantino the code is here: https://github.com/Parallels/docker-machine-parallels/blob/865d31df2dacb3534d6a6260b973184652cee67b/parallels_darwin.go#L790
I ended up changing it to the following snippet below, just as a workaround, and then followed the build instructions https://github.com/Parallels/docker-machine-parallels#build-from-source:
func isSharedConnected() (bool, error) {
	return true, nil
}

@MadsJakobsen Could you please show the output of the command prlsrvctl net info Shared in your case, when you don't have Bound to: there?

@legal90 here is the output from prlsrvctl net info Shared:
Network ID: Shared
Type: shared
Parallels adapter:
	IPv4 address: <IP_ADDRESS>
	IPv4 subnet mask: <IP_ADDRESS>
	Host assign IP v6: off
	IPv6 address: fdb2:2c26:f4e4::1
	IPv6 subnet mask: ffff:ffff:ffff:ffff::
DHCPv4 server:
	Server address: <IP_ADDRESS>
	IP scope start address: <IP_ADDRESS>
	IP scope end address: <IP_ADDRESS>
DHCPv6 server:
	Server address: fdb2:2c26:f4e4::
	IP scope start address: fdb2:2c26:f4e4::
	IP scope end address: fdb2:2c26:f4e4:0:ffff:ffff:ffff:ffff

NAT server:

Here is a screen shot of my preferences dialog:

Thanks, @MadsJakobsen ! Everything looks fine except that the line Bound To: vnic0 is missing. I guess, all the rest also works fine for you, e.q. the Mac host actually has a virtual interface with <IP_ADDRESS> assigned, so in can access the boot2docker VM.
@andreydanin @romankulikov Could you please check if that's the normal behavior, or a bug?
Meanwhile, I'll change the regex to accept the line Parallels adapter: instead of Bound To: (it should work for all currently supported versions of Parallels Desktop)

@legal90 The this is that Parallels is now using Apple's API to create a "vnic" analog on host and there will be no interface named vnic0. Now macOS creates own interface and plugs it into the bridge:
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether f6:5c:89:49:bf:64
inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
inet6 fe80::808:8f9a:6bd9:121e%bridge100 prefixlen 64 secured scopeid 0xf
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en3 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 14 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
What if check presence of IP address instead of searching vnic0?

What if check presence of IP address instead of searching for vnic0? (If I understand right, docker's script searches for vnic interface)

Currently we just search for Bound To: in the output of prlsrvctl net info Shared substring: https://github.com/Parallels/docker-machine-parallels/blob/865d31df2dacb3534d6a6260b973184652cee67b/parallels_darwin.go#L796
We can easily change it to something else pointing that the network interface for the Shared network is actually enabled on the host (like the checkbox "Connect Mac to this network" in GUI).  Can I use Parallels adapter: string for that?

@legal90 could be a bit better to find  ip-address in
Network ID: Shared
Type: shared
Parallels adapter:
IPv4 address: <IP_ADDRESS>
and then check presence of IP on host (by grepping output of ifconfig)

@dskr99 OK, thanks! I'll check how we can do that

Sorry that it took longer than I initially expected.
I sent a PR with the fix according to what @dskr99 suggested above: https://github.com/Parallels/docker-machine-parallels/pull/96

@MadsJakobsen the fix is released in v2.0.0 : https://github.com/Parallels/docker-machine-parallels/releases/tag/v2.0.0
Could you please verify it in your environment?

I installed the new release and now anytime I try to bring up a machine, my laptop kernel panics and reboots. I am on Big Sur beta 10, Parallels 16. How can I help troubleshoot?

@matttarantino Please create a problem report with technical details and send me it's number.

I installed the new release and now anytime I try to bring up a machine, my laptop kernel panics and reboots. I am on Big Sur beta 10, Parallels 16. How can I help troubleshoot?

@matttarantino are you using the Parallels hypervisor? I had the same behaviour with Big Sur beta, the fan would spin up and macOS would panic right after launching a VM. There is an issue on the Parallels forum describing the behaviour, the fix suggested is to use the Apple hypervisor: https://forum.parallels.com/threads/macos-big-sur-got-panic-when-i-tried-to-open-a-macos-client-in-pd-16.350681/

I still seem to be having this issue, even with the updated binary:
❯ /usr/local/bin/docker-machine-driver-parallels --version
docker-machine-driver-parallels version 2.0.0, build

 ~/go/src/github.com/Parallels/docker-machine-parallels  on master                                                   at 14:57:04
❯ minikube start --driver parallels --v=12 --alsologtostderr
I1017 14:58:43.784281   37217 out.go:191] Setting JSON to false
I1017 14:58:43.839760   37217 start.go:103] hostinfo: {"hostname":"Lukes-MBP","uptime":8798,"bootTime":1602934325,"procs":535,"os":"darwin","platform":"darwin","platformFamily":"","platformVersion":"11.0","kernelVersion":"20.1.0","virtualizationSystem":"","virtualizationRole":"","hostid":"d5ae727a-f8f2-31ee-b874-4e907b0c5115"}
W1017 14:58:43.839897   37217 start.go:111] gopshost.Virtualization returned error: not implemented yet
I1017 14:58:43.915169   37217 out.go:109] 😄  minikube v1.14.0 on Darwin 11.0
😄  minikube v1.14.0 on Darwin 11.0
I1017 14:58:43.915599   37217 notify.go:126] Checking for updates...
W1017 14:58:43.916391   37217 start.go:629] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
I1017 14:58:43.916479   37217 driver.go:288] Setting default libvirt URI to qemu:///system
W1017 14:58:43.916535   37217 start.go:629] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
I1017 14:58:43.983706   37217 out.go:109] ✨  Using the parallels driver based on existing profile
✨  Using the parallels driver based on existing profile
I1017 14:58:43.983730   37217 start.go:272] selected driver: parallels
I1017 14:58:43.983736   37217 start.go:680] validating driver "parallels" against &{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.13.1.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.13@sha256:4d43acbd0050148d4bc399931f1b15253b5e73815b63a67b8ab4a5c9e523403f Memory:6000 CPUs:2 DiskSize:20000 VMDriver: Driver:parallels HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:<IP_ADDRESS>/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio KubernetesConfig:{KubernetesVersion:v1.19.2 ClusterName:minikube APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:<IP_ADDRESS>/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.19.2 ControlPlane:true Worker:true}] Addons:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ExposedPorts:[]}
I1017 14:58:43.983857   37217 start.go:691] status for parallels: {Installed:true Healthy:true Running:true NeedsImprovement:false Error:<nil> Fix: Doc:}
I1017 14:58:43.990526   37217 start_flags.go:353] config:
{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.13.1.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.13@sha256:4d43acbd0050148d4bc399931f1b15253b5e73815b63a67b8ab4a5c9e523403f Memory:6000 CPUs:2 DiskSize:20000 VMDriver: Driver:parallels HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:<IP_ADDRESS>/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio KubernetesConfig:{KubernetesVersion:v1.19.2 ClusterName:minikube APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:<IP_ADDRESS>/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.19.2 ControlPlane:true Worker:true}] Addons:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ExposedPorts:[]}
I1017 14:58:43.990763   37217 iso.go:119] acquiring lock: {Name:mk45f8ab748431965bd9281354b3b2ed7b00f949 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.068201   37217 out.go:109] 👍  Starting control plane node minikube in cluster minikube
👍  Starting control plane node minikube in cluster minikube
I1017 14:58:44.068232   37217 preload.go:97] Checking if preload exists for k8s version v1.19.2 and runtime docker
W1017 14:58:44.384071   37217 preload.go:118] https://storage.googleapis.com/minikube-preloaded-volume-tarballs/preloaded-images-k8s-v6-v1.19.2-docker-overlay2-amd64.tar.lz4 status code: 403
I1017 14:58:44.384202   37217 profile.go:150] Saving config to /Users/lukecarrier/.minikube/profiles/minikube/config.json ...
I1017 14:58:44.384246   37217 cache.go:92] acquiring lock: {Name:mkd19943c233563d7217b57d0674ed0410895b9d Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384263   37217 cache.go:92] acquiring lock: {Name:mk086733abeed5318d0d196c52c85ecb593bc3d4 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384317   37217 cache.go:92] acquiring lock: {Name:mkcc70f764cde4164cbc83a535e723c19a61b032 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384351   37217 cache.go:92] acquiring lock: {Name:mk447ed5121c38da1a826473ea32258b36775042 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384374   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/kubernetesui/metrics-scraper_v1.0.4 exists
I1017 14:58:44.384396   37217 cache.go:81] cache image "kubernetesui/metrics-scraper:v1.0.4" -> "/Users/lukecarrier/.minikube/cache/images/kubernetesui/metrics-scraper_v1.0.4" took 165.227µs
I1017 14:58:44.384382   37217 cache.go:92] acquiring lock: {Name:mk7aa389682d9ab831dcf6a99c6bd805b80ca7b1 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384411   37217 cache.go:66] save to tar file kubernetesui/metrics-scraper:v1.0.4 -> /Users/lukecarrier/.minikube/cache/images/kubernetesui/metrics-scraper_v1.0.4 succeeded
I1017 14:58:44.384411   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/coredns_1.7.0 exists
I1017 14:58:44.384391   37217 cache.go:92] acquiring lock: {Name:mk8a76249a2d0bcad08475091af6d825cabe44bc Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384430   37217 cache.go:92] acquiring lock: {Name:mkd69cbae263dcda2c4b9995c763187c5d8c8be7 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384432   37217 cache.go:92] acquiring lock: {Name:mkd91b698dbe201641c6f42efecbf7b2fa808595 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384440   37217 cache.go:81] cache image "k8s.gcr.io/coredns:1.7.0" -> "/Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/coredns_1.7.0" took 194.788µs
I1017 14:58:44.384469   37217 cache.go:66] save to tar file k8s.gcr.io/coredns:1.7.0 -> /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/coredns_1.7.0 succeeded
I1017 14:58:44.384527   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/pause_3.2 exists
I1017 14:58:44.384546   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-apiserver_v1.19.2 exists
I1017 14:58:44.384516   37217 cache.go:92] acquiring lock: {Name:mkf08d1882aeb2623d18ec34284505f4b97b7235 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384555   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-controller-manager_v1.19.2 exists
I1017 14:58:44.384566   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-proxy_v1.19.2 exists
I1017 14:58:44.384572   37217 cache.go:81] cache image "k8s.gcr.io/kube-controller-manager:v1.19.2" -> "/Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-controller-manager_v1.19.2" took 196.376µs
I1017 14:58:44.384570   37217 image.go:168] retrieving image: k8s.gcr.io/etcd:3.4.13-0
I1017 14:58:44.384584   37217 cache.go:66] save to tar file k8s.gcr.io/kube-controller-manager:v1.19.2 -> /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-controller-manager_v1.19.2 succeeded
I1017 14:58:44.384562   37217 cache.go:81] cache image "k8s.gcr.io/kube-apiserver:v1.19.2" -> "/Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-apiserver_v1.19.2" took 139.903µs
I1017 14:58:44.384651   37217 cache.go:66] save to tar file k8s.gcr.io/kube-apiserver:v1.19.2 -> /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-apiserver_v1.19.2 succeeded
I1017 14:58:44.384585   37217 cache.go:81] cache image "k8s.gcr.io/kube-proxy:v1.19.2" -> "/Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-proxy_v1.19.2" took 156.917µs
I1017 14:58:44.384665   37217 cache.go:66] save to tar file k8s.gcr.io/kube-proxy:v1.19.2 -> /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-proxy_v1.19.2 succeeded
I1017 14:58:44.384546   37217 cache.go:81] cache image "k8s.gcr.io/pause:3.2" -> "/Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/pause_3.2" took 252.801µs
I1017 14:58:44.384706   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/kubernetesui/dashboard_v2.0.3 exists
I1017 14:58:44.384709   37217 cache.go:66] save to tar file k8s.gcr.io/pause:3.2 -> /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/pause_3.2 succeeded
I1017 14:58:44.384381   37217 cache.go:92] acquiring lock: {Name:mk118104d814002afd26a3c6422f88e6845f7142 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I1017 14:58:44.384720   37217 cache.go:81] cache image "kubernetesui/dashboard:v2.0.3" -> "/Users/lukecarrier/.minikube/cache/images/kubernetesui/dashboard_v2.0.3" took 253.344µs
I1017 14:58:44.384737   37217 cache.go:66] save to tar file kubernetesui/dashboard:v2.0.3 -> /Users/lukecarrier/.minikube/cache/images/kubernetesui/dashboard_v2.0.3 succeeded
I1017 14:58:44.384616   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-scheduler_v1.19.2 exists
I1017 14:58:44.384759   37217 cache.go:81] cache image "k8s.gcr.io/kube-scheduler:v1.19.2" -> "/Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-scheduler_v1.19.2" took 420.802µs
I1017 14:58:44.384776   37217 cache.go:66] save to tar file k8s.gcr.io/kube-scheduler:v1.19.2 -> /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/kube-scheduler_v1.19.2 succeeded
I1017 14:58:44.384819   37217 cache.go:100] /Users/lukecarrier/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v3 exists
I1017 14:58:44.384835   37217 cache.go:81] cache image "gcr.io/k8s-minikube/storage-provisioner:v3" -> "/Users/lukecarrier/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v3" took 501.666µs
I1017 14:58:44.384847   37217 cache.go:66] save to tar file gcr.io/k8s-minikube/storage-provisioner:v3 -> /Users/lukecarrier/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v3 succeeded
I1017 14:58:44.384911   37217 cache.go:182] Successfully downloaded all kic artifacts
I1017 14:58:44.384937   37217 start.go:314] acquiring machines lock for minikube: {Name:mk0ae7102c593fd4daad5441b1e460a5752c0018 Clock:{} Delay:500ms Timeout:13m0s Cancel:<nil>}
I1017 14:58:44.384961   37217 image.go:176] daemon lookup for k8s.gcr.io/etcd:3.4.13-0: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
I1017 14:58:44.385015   37217 start.go:318] acquired machines lock for "minikube" in 65.805µs
I1017 14:58:44.385042   37217 start.go:90] Provisioning new machine with config: &{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.13.1.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.13@sha256:4d43acbd0050148d4bc399931f1b15253b5e73815b63a67b8ab4a5c9e523403f Memory:6000 CPUs:2 DiskSize:20000 VMDriver: Driver:parallels HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:<IP_ADDRESS>/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio KubernetesConfig:{KubernetesVersion:v1.19.2 ClusterName:minikube APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:<IP_ADDRESS>/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.19.2 ControlPlane:true Worker:true}] Addons:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ExposedPorts:[]} &{Name: IP: Port:8443 KubernetesVersion:v1.19.2 ControlPlane:true Worker:true}
I1017 14:58:44.385165   37217 start.go:127] createHost starting for "" (driver="parallels")
I1017 14:58:44.457137   37217 out.go:109] 🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
I1017 14:58:44.457409   37217 start.go:164] libmachine.API.Create for "minikube" (driver="parallels")
I1017 14:58:44.457503   37217 client.go:165] LocalClient.Create starting
I1017 14:58:44.457614   37217 main.go:118] libmachine: Reading certificate data from /Users/lukecarrier/.minikube/certs/ca.pem
I1017 14:58:44.457695   37217 main.go:118] libmachine: Decoding PEM data...
I1017 14:58:44.457724   37217 main.go:118] libmachine: Parsing certificate...
I1017 14:58:44.457856   37217 main.go:118] libmachine: Reading certificate data from /Users/lukecarrier/.minikube/certs/cert.pem
I1017 14:58:44.457919   37217 main.go:118] libmachine: Decoding PEM data...
I1017 14:58:44.457939   37217 main.go:118] libmachine: Parsing certificate...
I1017 14:58:44.458008   37217 main.go:118] libmachine: executing: /usr/local/bin/prlctl --version
I1017 14:58:44.588721   37217 main.go:118] libmachine: executing: /usr/local/bin/prlsrvctl info --license
I1017 14:58:44.742470   37217 main.go:118] libmachine: Found Parallels Desktop version: &{%!d(string=) %!d(string=) [16 0 1] 3 %!d(string=16.0.1)}, edition: pro
I1017 14:58:44.742500   37217 main.go:118] libmachine: executing: /usr/local/bin/prlsrvctl net info Shared
I1017 14:58:44.904974   37217 cache.go:134] opening:  /Users/lukecarrier/.minikube/cache/images/k8s.gcr.io/etcd_3.4.13-0
I1017 14:58:45.046274   37217 client.go:168] LocalClient.Create took 588.734206ms
I1017 14:58:47.046647   37217 start.go:130] duration metric: createHost completed in 2.661389288s
I1017 14:58:47.046665   37217 start.go:81] releasing machines lock for "minikube", held for 2.661559776s
W1017 14:58:47.046688   37217 start.go:377] error starting host: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
I1017 14:58:47.046841   37217 cli_runner.go:110] Run: docker container inspect minikube --format={{.State.Status}}
W1017 14:58:47.172287   37217 cli_runner.go:148] docker container inspect minikube --format={{.State.Status}} returned with exit code 1
I1017 14:58:47.172356   37217 delete.go:46] couldn't inspect container "minikube" before deleting: unknown state "minikube": docker container inspect minikube --format={{.State.Status}}: exit status 1
stdout:

stderr:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
I1017 14:58:47.172552   37217 cli_runner.go:110] Run: podman container inspect minikube --format={{.State.Status}}
I1017 14:58:47.172578   37217 delete.go:46] couldn't inspect container "minikube" before deleting: unknown state "minikube": podman container inspect minikube --format={{.State.Status}}: exec: "podman": executable file not found in $PATH
stdout:

stderr:
W1017 14:58:47.172620   37217 start.go:382] delete host: Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
W1017 14:58:47.172759   37217 out.go:145] 🤦  StartHost failed, but will try again: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
🤦  StartHost failed, but will try again: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
I1017 14:58:47.172772   37217 start.go:392] Will try again in 5 seconds ...
I1017 14:58:52.172967   37217 start.go:314] acquiring machines lock for minikube: {Name:mk0ae7102c593fd4daad5441b1e460a5752c0018 Clock:{} Delay:500ms Timeout:13m0s Cancel:<nil>}
I1017 14:58:52.173081   37217 start.go:318] acquired machines lock for "minikube" in 94.272µs
I1017 14:58:52.173106   37217 start.go:90] Provisioning new machine with config: &{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.13.1.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.13@sha256:4d43acbd0050148d4bc399931f1b15253b5e73815b63a67b8ab4a5c9e523403f Memory:6000 CPUs:2 DiskSize:20000 VMDriver: Driver:parallels HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:<IP_ADDRESS>/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio KubernetesConfig:{KubernetesVersion:v1.19.2 ClusterName:minikube APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:<IP_ADDRESS>/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.19.2 ControlPlane:true Worker:true}] Addons:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ExposedPorts:[]} &{Name: IP: Port:8443 KubernetesVersion:v1.19.2 ControlPlane:true Worker:true}
I1017 14:58:52.173206   37217 start.go:127] createHost starting for "" (driver="parallels")
I1017 14:58:52.248505   37217 out.go:109] 🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
I1017 14:58:52.248643   37217 start.go:164] libmachine.API.Create for "minikube" (driver="parallels")
I1017 14:58:52.248682   37217 client.go:165] LocalClient.Create starting
I1017 14:58:52.248742   37217 main.go:118] libmachine: Reading certificate data from /Users/lukecarrier/.minikube/certs/ca.pem
I1017 14:58:52.248799   37217 main.go:118] libmachine: Decoding PEM data...
I1017 14:58:52.248815   37217 main.go:118] libmachine: Parsing certificate...
I1017 14:58:52.248913   37217 main.go:118] libmachine: Reading certificate data from /Users/lukecarrier/.minikube/certs/cert.pem
I1017 14:58:52.248954   37217 main.go:118] libmachine: Decoding PEM data...
I1017 14:58:52.248969   37217 main.go:118] libmachine: Parsing certificate...
I1017 14:58:52.249016   37217 main.go:118] libmachine: executing: /usr/local/bin/prlctl --version
I1017 14:58:52.360967   37217 main.go:118] libmachine: executing: /usr/local/bin/prlsrvctl info --license
I1017 14:58:52.503807   37217 main.go:118] libmachine: Found Parallels Desktop version: &{%!d(string=) %!d(string=) [16 0 1] 3 %!d(string=16.0.1)}, edition: pro
I1017 14:58:52.503845   37217 main.go:118] libmachine: executing: /usr/local/bin/prlsrvctl net info Shared
I1017 14:58:52.729787   37217 client.go:168] LocalClient.Create took 481.081952ms
I1017 14:58:54.729932   37217 start.go:130] duration metric: createHost completed in 2.556630723s
I1017 14:58:54.729952   37217 start.go:81] releasing machines lock for "minikube", held for 2.556781393s
W1017 14:58:54.730112   37217 out.go:145] 😿  Failed to start parallels VM. Running "minikube delete" may fix it: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
😿  Failed to start parallels VM. Running "minikube delete" may fix it: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
I1017 14:58:54.798594   37217 out.go:109]

W1017 14:58:54.798804   37217 out.go:145] ❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
W1017 14:58:54.798841   37217 out.go:145]

W1017 14:58:54.798889   37217 out.go:145] 😿  If the above advice does not help, please let us know:
😿  If the above advice does not help, please let us know:
W1017 14:58:54.798922   37217 out.go:145] 👉  https://github.com/kubernetes/minikube/issues/new/choose
👉  https://github.com/kubernetes/minikube/issues/new/choose
I1017 14:58:54.870998   37217 out.go:109]

I tried building from source but even after verifying it was the first copy of the driver in my PATH and commenting out both of the checks I couldn't get it working. Particularly strangely, if this is the version it's using I don't see why this expression wouldn't match:
❯ /usr/local/bin/prlsrvctl net info Shared
Network ID: Shared
Type: shared
Parallels adapter:
	IPv4 address: <IP_ADDRESS>
	IPv4 subnet mask: <IP_ADDRESS>
	Host assign IP v6: off
	IPv6 address: fdb2:2c26:f4e4::1
	IPv6 subnet mask: ffff:ffff:ffff:ffff::
DHCPv4 server:
	Server address: <IP_ADDRESS>
	IP scope start address: <IP_ADDRESS>
	IP scope end address: <IP_ADDRESS>
DHCPv6 server:
	Server address: fdb2:2c26:f4e4::
	IP scope start address: fdb2:2c26:f4e4::
	IP scope end address: fdb2:2c26:f4e4:0:ffff:ffff:ffff:ffff

NAT server:

@LukeCarrier according to the error message you've got, you are still using the old version of docker-machine-driver-parallels:

Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'

In v2.0.0 we've changed the phrase Please, enable this option to Please, ensure this option is set :
https://github.com/Parallels/docker-machine-parallels/pull/96/files#diff-36e7efdbaacec2bf1d02ae428610b099fe59d07102fa975abd660cf924f35633R51
Please, make sure that the executable docker-machine-driver-parallels in your PATH is pointing to the latest v2.0.0. You can check it this way:
$ which docker-machine-driver-parallels
/usr/local/bin/docker-machine-driver-parallels

$ /usr/local/bin/docker-machine-driver-parallels --version
docker-machine-driver-parallels version 2.0.0, build d640c38

I can see the difference in the text and I agree with your assessment, even after unlinking the Homebrew installed docker-machine-parallels and copying my own binary to /usr/local/bin/docker-machine-driver-parallels I still see the same error:
❯ which docker-machine-driver-parallels
/usr/local/bin/docker-machine-driver-parallels

❯ /usr/local/bin/docker-machine-driver-parallels --version
docker-machine-driver-parallels version 2.0.0, build d35f911

❯ minikube start --driver parallels
😄  minikube v1.14.0 on Darwin 11.0
✨  Using the parallels driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🤦  StartHost failed, but will try again: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
😿  Failed to start parallels VM. Running "minikube delete" may fix it: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'

❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'

😿  If the above advice does not help, please let us know:
👉  https://github.com/kubernetes/minikube/issues/new/choose

I figured it was just using a different binary, so I deleted it and tried again:
❯ rm -f /usr/local/bin/docker-machine-driver-parallels

❯ minikube start --driver parallels
😄  minikube v1.14.0 on Darwin 11.0
✨  Using the parallels driver based on existing profile

🤷  Exiting due to PROVIDER_PARALLELS_NOT_FOUND: The 'parallels' provider was not found: exec: "docker-machine-driver-parallels": executable file not found in $PATH
💡  Suggestion: Install docker-machine-driver-parallels
📘  Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/parallels/

Even stranger:
❯ strings ~/go/bin/docker-machine-driver-parallels | grep 'Please, enable this option'

I'm missing something, any ideas?

As if this wasn't baffling enough:
❯ curl -L -o /usr/local/bin/docker-machine-driver-parallels https://github.com/Parallels/docker-machine-parallels/releases/download/v2.0.0/docker-machine-driver-parallels && chmod +x /usr/local/bin/docker-machine-driver-parallels
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   655  100   655    0     0   2538      0 --:--:-- --:--:-- --:--:--  2538
100 12.3M  100 12.3M    0     0  1088k      0  0:00:11  0:00:11 --:--:-- 1760k

 ~                                                    took 12s  at 19:58:45
❯ minikube start --driver parallels
😄  minikube v1.14.0 on Darwin 11.0
✨  Using the parallels driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🤦  StartHost failed, but will try again: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'
🔥  Creating parallels VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
😿  Failed to start parallels VM. Running "minikube delete" may fix it: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'

❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: precreate: Your Mac host is not connected to Shared network. Please, enable this option: 'Parallels Desktop' -> 'Preferences' -> 'Network' -> 'Shared' -> 'Connect Mac to this network'

😿  If the above advice does not help, please let us know:
👉  https://github.com/kubernetes/minikube/issues/new/choose

@LukeCarrier I found what's the reason of this.
Unlike docker-machine, minikube doesn't actually do RPC calls of PreCreateCheck, Create and other methods from our driver. Instead, it calls them from the vendored dependency (as a library), which is still locked to v1.3.0:
https://github.com/kubernetes/minikube/blob/a282354419135221325414c1d8d03f3bd37b58e3/go.mod#L8
That's why you still see this issue and the old-styled text in logs.
@medyagh, could you please tell if it's the expected behavior? If so - it looks weird that minikube requires the user to install the driver binary to PATH, but doesn't actually use it 🤔

@LukeCarrier @medyagh I found the root cause of this issue on minikube side and submitted the fix: https://github.com/kubernetes/minikube/pull/9494

@legal90 thanks for the prompt follow up, really appreciate it. These integrations are a large part of the reason I became a customer so it’s great to see they’re so well maintained.

The final fix is release in minikube v1.15.0: https://github.com/kubernetes/minikube/releases/tag/v1.15.0
Please note that starting since v1.15.0 minikube has the parallels driver built-in, so you don't need a separate binary docker-machine-driver-parallels for minikube anymore.


FTP to NAS drive

I have tried to set the FTP to my network drive (ReadyNAS) but I am getting a certificate untrusted error.
I have tried adding set ssl:verify-certificate false to one of the scripts as a test but it says its an unknown command!
any assistance gratefully received

this is the error
cd: Fatal error: Certificate verification: Not trusted (2A:F1:93:C7:A2:7C:C5:6A:1A:03:D9:9C:48:F2:1D:75:8E:F0:48:38)
put: images/20191022/allsky-20191022.mp4: Fatal error: Certificate verification: Not trusted (2A:F1:93:C7:A2:7C:C5:6A:1A:03:D9:9C:48:F2:1D:75:8E:F0:48:38)

The option should work if you add it there for example:
lftp "$PROTOCOL"://"$USER":"$PASSWORD"@"$HOST":"$MP4DIR" -e "ssl:verify-certificate false; set net:max-retries 1; put $TIMELAPSE; bye"
Have you tried to SSH to the destination directly? ssh <user>@<NAS_IP_address>. It may ask you if you want to add this host as a trusted host.

Ok thanks I will give it a go
Dave Wilkes
On Tue, Oct 22, 2019 at 11:59 PM +0100, "Thomas Jacquin"<EMAIL_ADDRESS>wrote:
The option should work if you add it there for example:
lftp "$PROTOCOL"://"$USER":"$PASSWORD"@"$HOST":"$MP4DIR" -e "ssl:verify-certificate false; set net:max-retries 1; put $TIMELAPSE; bye"
Have you tried to SSH to the destination directly? ssh @<NAS_IP_address>. It may ask you if you want to add this host as a trusted host.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I get this with that line in!
pi@allsky:~/allsky/scripts $ cd: Fatal error: Certificate verification: Not trusted (2A:F1:93:C7:A2:7C:C5:6A:1A:03:D9:9C:48:F2:1D:75:8E:F0:48:38)
Unknown command `ssl:verify-certificate'.
if i try ssh to the nas i get connection refused
i think there is an issue with the nas tbh when i connect with a web browser it shows an ssl error and the ip address in the certificate is nothing like what it should be. also reading up on these nas drives there are lot of people with certificate issues. i will look at another option. i see someone has used drop box!

I gave up on the ReadyNAS they are not updating it anymore so will not fix their poor SSL setup.
i have now configured it to SFTP to my web hosted SFTP server and all works well.

I am facing the same issue with fritz.nas (NAS at Fritz.Box from AVM).
Since it is not possible to accept the certificate, FTP-uploads are not possible.
At the same time internal recording stops.
It seems there is no way to correct the problem, by disabling uploads or setting ftp-settings.sh to default.

It seems there is no way to correct the problem, by disabling uploads or setting ftp-settings.sh to default.

You can disable upload by setting UPLOAD_IMG to false in config.sh

Because it is ftp and not sftp, I changed the settings as describes a lot of threads ago:
I replaced
lftp "$PROTOCOL"://"$USER":"$PASSWORD"@"$HOST":"$IMGDIR" -e "set net:max-retries 1; set net:timeout 20; put $FILENAME-resize.$EXTENSION; bye" &
by
lftp "$PROTOCOL"://"$USER":"$PASSWORD"@"$HOST":"$IMGDIR" -e "set ssl:verify-certificate false; set net:max-retries 1; set net:timeout 20; put $FILENAME-resize.$EXTENSION; bye" &
in scripts/saveImageDay.sh, scripts/saveImageNight.sh and scripts/timelapse.sh
now ftp works, but the image is permanently written into the root folder of the ftp-server.
settings like IMGDIR='allsky' are ignored.

I had same problem - would only save to root of host (external server, not internal NAS) when set ssl:verify-certificate false. The sftp/certificate thing, especially when dealing with self-signed is a PITA. But bypassing is not a good solution (ie. opens you up to man-in-middle attacks).
Managed to resolve by doing this (and not using ssl:verify-certificate false):
Create RC file (put in /home/pi/.lftp/rc ):
#######################
RC file
set ssl:ca-file "/home/pi/.lftp/cert_rasc_webnames.crt"

set ssl:check-hostname no
#########################
Create cert file in /home/pi/.lftp/ called cert_rasc_webnames.crt (and make own/grp "pi"
Get content for Cert file from:
openssl s_client -showcerts -connect example.com:21 -starttls ftp
replace example.com with the host name of your ftp server and change the port number if different.
This will return a bunch of information, the bit we are interested in is under Certificate chain section. Copy the certificate which is the text which starts -----BEGIN CERTIFICATE----- and ends -----END CERTIFICATE----- and paste into a new file under  ~/.lftp eg. mycert.crt so you now have a file that reads:
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
Hope this helps. I did a manual sftp command from terminal window, before and after, to verify it was working.
DaveNL

This issue is from an older release of the AllSky software. If you think it might still be relevant, please submit a new issue.
Also, this appears to be related to certain NAS devices, not to the AllSky software.

To file upload.sh inserted "echo set ssl:verify-certificate false" after line 120 fixed the problem

@mpinnuck You shouldn't change the upload.sh file.  The Wiki page on Troubleshooting uploads describes where you can put the "echo set ssl:verify-certificate false" line where it won't get overwritten every time you update Allsky.

Thanks, added to LFTP_COMMANDS in ftp-settings.sh

"Have you tried to SSH to the destination directly? ssh @<NAS_IP_address>. It may ask you if you want to add this host as a trusted host."
This worked for me!!


Reactivity tutorial

Not sure if this version will build on github. Failing locally but it seems to be related to cached files.

Updated, addressed existing feedback and added a new step (After the update) and removed the hasChanged() step.
Still need to:

Add replace sample code on intro & recap pages with something more interesting.

Also, make sure the correct file is selected for all steps.

Not sure if it's GH's bad UI that hides comments, but there are several un-addressed comments in the middle

Grr... yeah, apparently I pushed changes that hid the previous conversations. Some of which I never saw in the first place. Not sure how that worked.

OK, think I addressed the previously unaddressed comments, made sure the right file was selected, and made sure each component file exports the component class, for consistency.
Steve asked for some sample changes to the shouldUpdate() and maybe the requestUpdate() steps. I'm not sure whether those changes are doable in our timeframe, but I definitely don't have the brainpower to handle them today.

Ping on this one @sorvell @e111077 ... I'm still hoping to get this one in...

reviewing now

Updated step 5, added new end samples, and addressed other feedback.


Log interface for History and Persister

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature, docs update

What is the current behavior? (You can also link to an open issue here)
Logging levels can only be changed through code.

What is the new behavior (if this is a feature change)?
Logging level can be set through environment variables or via enpoints

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Is there any issue related to this PR in other repository? (such as dojot/dojot)

Other information:

It seems a bit strange because we have 2 log level configuration endpoints, but both set these settings in the same place. Is this correct?


#426 - Macro Names Vanishing / Still not working

Trying a new Ace3 lib install to see if that fixes:
#426 - Macro Names Vanishing
Does still not working for me.
Greetings

Closing as its a duplicate of #426


How to add code snippet

Its really awesome, I didn't find any process to add code snippet. How can I do it?

You can create your own addon for that: https://github.com/orthes/medium-editor-insert-plugin/wiki/v2.x-Custom-addons
The most important function is CustomAddon.prototype.add which is called when you click on the addon button. There you can do whatever you want.

Thank you so much


Spell check test broken on Bionic (and others)

I'm not sure why (yet), but test_spell_check appears to fail on Bionic and Fedora 29. Seems to be running (and passing) on Travis, though.
The console output is much too long to paste in here, but after installing python3-enchant, pytest breaks on this test every time.
For now, I'm going to skip this test for Fedora packaging since it appears broken on Ubuntu as well, but I wanted to file an issue to follow-up on this later.

Yeah, the dictionary shipped with various Ubuntu versions is different. I haven't found a good way to get deterministic results. Any ideas are welcome :wink:

#114 will get the tests passing for now, but it isn't a solution. Enchant 2 has a mechanism for supporting local configurations, but Bionic doesn't have Enchant 2. For Travis specifically, we could modify the "user" dictionary, but that doesn't really give us much over the existing solution.
Beyond continuing with the current approach (which is working), the only thing I can think of is either bundling or downloading a common dictionary instead of relying on the distribution-provided one...

Okay, this is a little deeper than I thought. Somehow, setting filterwarnings to error is causing the spellcheck test to pass. Removing the error mode from DeprecationWarning (either default or ignore) makes the test fail. I think this may be a bug in pylint or astroid, and I think Fedora rawhide has the fix, because it fails in the same way Bionic does when I remove the error mode as described.
In any case, there are quite a few additional tokens (namely ones currently in backticks in comments) that would need to be added to get things passing in Fedora rawhide.


Improve resolver error messages referencing workspace members

Some clear improvements here, but I'm disappointed there's basically no coverage for resolution failures involving workspace members — we'll need to add a bunch more test coverage before this can be merged with confidence.

Closing in favor of #6092


Typescript style-only imports are not resolving correctly

VSCode Version: Version 1.24.1 (1.24.1)
OS Version: macOS 10.13.5

Steps to Reproduce:

use tsc to transpile (using TS 3.0.0-dev.20180603) project with dynamic import like:
private static _defaultDb: import("abstracted-firebase").RealTimeDB;

run tsc with the following tsconfig.json:
{
  "compilerOptions": {
    "declaration": true,
    "module": "esnext",
    "target": "es2017",
    "lib": ["es2017", "esnext.asynciterable", "es2015.reflect"],
    "moduleResolution": "node",
    "sourceMap": true,
    "noImplicitAny": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "outDir": "./dist/esnext",
    "removeComments": false,
    "typeRoots": ["./node_modules/@types"]
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules/**/*"<EMAIL_ADDRESS>}

No errors are reported but if you go into the .d.ts file where the import existed you'll find a transpilation similar to:
    protected _db: import("../../../../../../Users/ken/mine/forest-fire/firemodel/src/decorators/schema").RealTimeDB;

Does this issue occur when all extensions are disabled?: Yes

This issue was moved to Microsoft/TypeScript#25358


nodename nor servname provided, or not known

When trying to publish to an elasticmq queue using the AWSSDK (.net Core), the call eventually times out and returns: 'nodename nor servname provided, or not known'. Any ideas what it is exactly asking for, it doesn't seem to match any config options?

Can you post some example code to reproduce the problem?

If you still have this issue and are able to provide an example please reopen.


Add hover help for the 'trace' launch config attribute

Since the 'trace' attribute is now documented here, we should add proper hover help too.

@roblourens I've added this description:

In node2 it has different semantics, it can be 'true' or 'verbose', where 'true' only writes to a file. This is because I've given up on making this output readable to anyone else, and I have another tool for sourcemap path debugging, the .scripts command. Maybe we should just add 'true' as a valid value so it doesn't get underlined?

Is 'true' of type string or a boolean?
For me the type of 'trace' is string and I did not bother to create a schema for the individual values (because they can be combined in any way). The value is not validated and will not result in errors.
So a 'true' (as a string is not problem).
However, if we agree on a string type, I suggest that we use something more self-explanatory like 'on', 'off', instead of 'true' and 'false'.
And I could replace my 'all' by 'verbose'.

true is a boolean here. What I expect people to do most of the time is to use "trace": true and upload the log file to github, and I thought a boolean would be simpler for that case than some other string. "verbose" is useful to me but probably not many other people.

I've changed the schema to support "boolean" | "string".
And the description is now:

I get a "Property trace is not allowed" hover text now. Has trace been eliminated as a property?

@onethread no, trace hasn't been eliminated.
I assume you are using VS Code stable (1.10.2), correct? trace was not an official attribute in VS Code version < 1.11.
In 1.11 it will become an official attribute. You can try it already in the Insiders build.

@weinand Ah that makes more sense now. It is listed in the official docs, though. Thanks for clearing that up.


doc: update doc of pouch with kubernetes deploying

Signed-off-by: Starnop<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
update doc of pouch with kubernetes deploying
Ⅱ. Does this pull request fix one issue?

None
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

:exclamation: No coverage uploaded for pull request base (0.5.x@89ac7b0). Click here to learn what that means.
The diff coverage is n/a.

LGTM


Import of Antlr grammars for reuse

Add a feature so you can reuse Antlr grammar definitions.

Will not happen.
Nitra parsing algorithm too different.

This does not prevent import of ANTLR grammars with little manual rework.

Sirinath. Maybe you try yourself to write such a converter?

This is not my strong suite but there a lot of grammars written in ANTLR. Iff we can just import them it will make life a lot easier than re implementing from scratch.


Expose a new TurboLog.debugLoggingEnabled API that apps can enable to see debug logs

Address #21 through an explicit API.

@joemasilotti Looking at this more, I think it makes more sense to go with an explicit API to enable debug logging, which is also how the turbo-android library works. And it's more flexible in that you don't have to build from Xcode to see debug logs via process args. Planning to merge this soon, but let me know if you have any feedback.

LGTM! Great idea.


Stuck in form

Since I was curious how to save the "webspaces" (see https://github.com/sulu/sulu-demo/pull/106#issuecomment-2199758276) I had to make some changes to make this bundle to work - composer & some security constants. But now I'm stuck. Form doesnt save. do:sch:up was done... Latest Sulu 2.6.4 used.

Please advice.

after adding the contents of securitytxt_admin.yaml to routes_admin. yaml I get it to work.

Not sure if I can follow. Do you want to add a new feature to this bundle? Any help needed?

Thank you for that offer.
Since I'm working on a project with two webspaces I tried to evaluate how to make webspace specific settings. I wanted to see how you'd solved the problem with the 'missing' webspace in the demo pr. Got your bundle wo work after some tweaks but I'm not sure whether doing the same or using just snippets. Seems confusing to me to see both settings elements in the list within one webspace.


Release 0.1.0 part 1/3: README

Is this a bug fix or adding new feature?
new feature
What is this PR about? / Why do we need it?
new release
What testing is done?

/lgtm
/approve


Issues training VSR from scratch

Hi, I'm having some issues in getting good results when training the VSR only model from scratch.
This is a screenshot of the decoder eval curves for the (full training LRS only 438h).
The gray one is starting with your base_23h checkpoint -> which immediately starts learning well
The orange one  without loading any weights -> much slower learning
And the purple one is with my retraining on the 23h set.

You can see that my version of the 23h training is not good, as it's on par as just starting from zero.
also the WER on my 23h model is 1.01, not 0.96 as yours.
Am I missing something when doing the pretraining on the 23h set?
This is the code I am using, with everything else set as the default you provide in your config files.
python train.py
  exp_dir=./exp/repretrain
  exp_name=repretrain
  data.modality="video"
  trainer.gpus=2
  data.dataset.root_dir=preparation/prepro2
  data.dataset.train_file=lrs3_train_transcript_lengths_seg24s_0to100.csv
  data.dataset.val_file=lrs3_test_transcript_lengths_seg24s.csv
  data.dataset.test_file=lrs3_test_transcript_lengths_seg24s.csv
  optimizer.lr=0.0002

This is the curves I get during the 23h pretraining

Follow-up in case any other have the same issue.
I think the issues was with the "batch size" in terms of number of GPU used.
In my case I was using just 2 GPUs, while the Author said he was using 32 GPUs, which matters.
I solved by using gradient_accumulation=10 during the train of the 23h model and for the full 438h model, and now trains as it should.

Follow-up in case any other have the same issue.
I think the issues was with the "batch size" in terms of number of GPU used. In my case I was using just 2 GPUs, while the Author said he was using 32 GPUs, which matters.
I solved by using gradient_accumulation=10 during the train of the 23h model and for the full 438h model, and now trains as it should.

Hi my friend
Thank you for sharing your solution
I have a question, may you can help me
I want to train VSR on a Persian dataset created by myself.
i used vsr_trlrs3_23h_base.pth as pre-trained ckeckpoint and trained VSR model on a persian dataset with 10 seconds duration of each video.
But the trained model only learnd 1 text, and produced exactly the same text for every input videos in the inference time.
what is the problem?


sync/atomic: Load and Store don't use exclusive mode assembly instructions in arm64 weak memory model

What version of Go are you using (go version)?

$ go version
1.12.4

Does this issue reproduce with the latest release?
Maybe，I have not verified.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
arm64

If there are any special considerations?
Load and Store use non-exclusive mode instructions LDARW, LDAR, STLRW, STLR，
instead of using exclusive mode instructions LDAXRW, STLXRW like CAS.
The store in amd64 also uses the exclusive XCHGL.
In my application on arm64, atomic.StoreInt32() may have failed.
But I don't have a simple demo to reproduce it now.
I want to ask if there are any special considerations?
Waiting for your reply urgently.
Thank you !

Thank you for this report @WangLeonard!
Kindly pinging @cherrymui @randall77.

Thanks @WangLeonard and @odeke-em.
/cc @4ad, who I believe this was authored a good portion of this in golang.org/cl/7142.
If you can't provide an example of failing code, could you please provide more details about the failure you encountered?

Current go documentation does not specify any memory order guarantees made by the atomic operations, but there is some agreements on the memory order. Please refer to this CL https://go-review.googlesource.com/c/go/+/189417/ and this discussion https://groups.google.com/forum/#!msg/golang-dev/vVkH_9fl1D8/azJa10lkAwAJ.
The reason why CAS uses exclusive mode Load/Store instructions is to guarantee multiple opeations of a single process are atomic accesses. But there is no obvious reason that we have to use exclusive load/store instructions for atomic Load/Store.
Could you share why do you think need to use exclusive mode instructions?
Can you help to check your code to confirm whether it follows the rule "you shouldn't mix atomic and non-atomic accesses for a given memory word."? By the way, we also don't guarantee the memory order among atomic and non-atomic access on different memory.
Additional notes: The following is a description of these instructions in the arm architecture reference manual.
LDAR: Load-Acquire Register derives an address from a base register value, loads a 32-bit word or 64-bit doubleword from memory, and writes it to a register
STLR: Store-Release Register stores a 32-bit word or a 64-bit doubleword to a memory location, from a register.
LDAXR: Load-Acquire Exclusive Register derives an address from a base register value, loads a 32-bit word or 64-bit doubleword from memory, and writes it to a register. The memory access is atomic. The PE marks the physical address being accessed as an exclusive access.
STLXR: Store-Release Exclusive Register stores a 32-bit word or a 64-bit doubleword to memory if the PE has exclusive access to the memory address, from two registers, and returns a status value of 0 if the store was successful, or of 1 if no store was performed.The memory access is atomic.

import(
"runtime"
"sync/atomic"
"time"
)

var num int32
var total int32

func wrap1(ch chan bool){
    go func(){
        for{
            // if num is 0, change to 1.
            if atomic.CompareAndSwapInt32(&num,0,1){
                ch <- true
            }
           // Do something.
           time.Sleep(time.Millisecond)
        }
    }()
}

func wrap2(ch chan bool){
    runtime.LockOSThread()
    for range ch {
        // Do something.
        ans := 0
        for i:=0;i<10000;i++{
            ans++
        }
        // change num to 0.
        atomic.StoreInt32(&num,0)
        //atomic.AddInt32(&total,1)
        //  fmt.Println("Done!",total)

    }
}

func main(){
    ch := make(chan bool,1)
    wrap1(ch)
    wrap1(ch)
    wrap1(ch)
    wrap2(ch)
}

@toothrot @zhangfannie
my program looks like the above, but this demo can't reproduce my problem, this is just a simplified version， my application will be more complicated, add some cgo and syscall，more concurrent etc.
I added some positioning and found that when there is a problem with the application,
The state of wrap2's goroutine is Gwaiting,
The reason is waitReasonChanReceive,
The value of num is 1,
So suspected to be atomic.StoreInt32 failed.
my environment is arm64 V8 , linux.
For the problem variable, only one part of the program does not use atomic, but can be considered as a deadcode, will this affect the compiler?

I can't reproduce at Go1.13.1
package main

import (
        "log"
        "runtime"
        "sync/atomic"
        "time"
)

var num int32

func wrap1(ch chan bool) {
        go func() {
                for {
                        // if num is 0, change to 1.
                        if atomic.CompareAndSwapInt32(&num, 0, 1) {
                                ch <- true
                        }
                        // Do something.
                        log.Print("wrap1")
                        time.Sleep(time.Millisecond)
                }
        }()
}

func wrap2(ch chan bool) {
        runtime.LockOSThread()

        for range ch {
                time.Sleep(time.Millisecond)
                atomic.StoreInt32(&num, 0)
                log.Print("wrap2")
        }
}

func main() {
        ch := make(chan bool, 1)
        wrap1(ch)
        wrap2(ch)
}

2019/11/19 14:50:37 wrap1
2019/11/19 14:50:37 wrap1
2019/11/19 14:50:37 wrap2
2019/11/19 14:50:37 wrap1
2019/11/19 14:50:37 wrap1
2019/11/19 14:50:37 wrap2
……

@mengzhuo
Yes, this demo can't reproduce the problem, just to simplify the scenario that describes the application.
Now just guessing from some phenomena and states, and I changed StoreInt32 to CompareAndSwapInt32 to seem to solve this problem, I am still confirming.

@WangLeonard what is the problem?

The state of wrap2's goroutine is Gwaiting,
The reason is waitReasonChanReceive,
The value of num is 1,
So suspected to be atomic.StoreInt32 failed.

Why? It could be that the atomic store succeeded, then the CAS in wrap1 succeeded, but the scheduler hasn't woken the wrap2 goroutine.

I want to mention that GCC also generates LDAR/STLR for atomic load/store.
uint64_t Load64(uint64_t *p)              { return __atomic_load_n (p, __ATOMIC_SEQ_CST); }
void     Store64(uint64_t *p, uint64_t v) { __atomic_store_n (p, v, __ATOMIC_SEQ_CST); }

Load64:
.LFB0:
	.cfi_startproc
	ldar	x0, [x0]
	ret
	.cfi_endproc

Store64:
.LFB1:
	.cfi_startproc
	stlr	x1, [x0]
	ret
	.cfi_endproc

@cherrymui
I just suspect that StoreInt32 failed. This is a rather strange question.
For what you said the scheduler hasn't woken the wrap2 goroutine.
Because I used LockOSThread, I counted the number of executions of the three locations in the schedule() function:
before stoplockedm() 、 after stoplockedm()、startlockedm(gp)
found that:
before stoplockedm = after stoplockedm +1
before stoplockedm = startlockedm(gp)+1
And these three values no longer increase  when a bug occurs.
So I guess chan is not written when a bug occurs,
wrap2 goroutine not put into the local runnable queue,
schedule() can not find this G to M execution.
When I can reproduce the problem or locate other reasons, I will provide more information.
Thank you!


Swipe or place a card Functionality not working

Hi,
first of all thank you for this wonderful project. I got the phoniebox working so far. RFID (Neuftech) scanner works fine but i cant use the "swipe or place" option properly. When i place the card it just starts the audiofile to play for  a second and then stops. The green light of the reader indicates it still recognizes the card lying on it.  Swiping works flawlessly. Any idea ?
Version
2.3 - 2425890 - master
Edition
Classic edition (barebones)
Thanks,
Apunkt

What’s the output of tail -n 200 /var/log/syslog?

Place does not work with Neuftech readers. They only support Swipe.
Reason: Neuftech only gives a single event when a new card is placed.
You will need to change the reader to RDM6300.
Or MFRC522 - but that uses a different NFC standard.

hi, guys. thank you for answering. I will stick to the neuftech as the RDM6300 needs some kind of voltage altering through an additional board. usb is so comfortable :-)


Auth token fix

Current version deletes auth token on logout. This renders any auth token based API integrations broken after the user logs out.

Lots of users today are expecting this logout functionality to work as its currently implemented.
Perhaps you can propose another solution that handles your case and everyone else's?

Just updated this branch with a new setting REST_AUTH_TOKEN_PERSISTENT that would allow the user to change the default behavior. I also apologize, this branch has some of my throttle class code. My fork got jumbled up a bit with the new fork. If the #83 is merged first, then it shouldn't be an issue.

In the summary you mention that if a user logs out, their API integrations will also lose access. Wouldn't it be better to issue separate tokens for each integration/app instead of sharing one token for web access and all other access? Like the way Gitlab and Github handle it.

I'm currently using session authentication for my web app and auth tokens for my API. My original plan was to use a library like you mentioned but DRF auth tokens are one-to-one with the user object (source).
Do you have a library recommendation? This seems like the preferred built-in way to use API keys but I'm open to suggestions.

Hi @steverecio,
Apologies for the delay. Have you considered using Knox ? It allows for multiple tokens per user. I can't think of a reason why also using JWT tokens would not work since they are stateless.

Hi @steverecio,
After some consideration I think think this approach adds yet another flag to solve a problem that can be solved more elegantly using JWTs (JWTs are stateless so you can issue multiple per user and blacklist independently). Given that I'm going to close this PR.
Apologies for the run around and the big delay!
Michael


Test web browser video performance

Because of #3

I tested... I can't remember. At least 1080p video, if not 4K. Seemed fine.


fix: Remove decommissioned config reference.

Description
As per title.

This is no longer required because it was fixed in a new PR for deployment to the new environment.


check the workflow in the jupyter notebook

This one is a duplicate of another ticket so it can be closed.


Added custom tabs. MVP.

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4225  👈
#4224
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @anikiki and the rest of your teammates on  Graphite


Duplicate Azure DevOps Build as GitHub Action

Take the work being done in Azure DevOps currently and migrate it to do the same thing in GitHub actions.

Done!


Export to XML

Is it possible to add functionality to export table data to XML?

It should be fairly simple I guess, converting either from raw JSON or the generated CSV output. However it's not something we have inte pipeline at the moment so if this is something you need now, I'd suggest making a pull request. But I'll leave this issue open as I think it's something we should support in the future:)


JSONAPIDocument public

The public init method is not accessible;
due to:
ResourceCollection initializer is inaccessible due to 'internal' protection level
Can we make it public?
public init(document: JSONAPIDocument) {  }

I'm not maintaining this library anymore. The project that used this was shelved and I'm too busy with other work, so I cannot afford to spend time on this anymore.
The community is continuing development of Spine at jsonapi-ios/Spine. Feel free to use that fork, and submit pull-requests or open issues there.


Update The server.js to be more friendly.

The server, while running, should print out the following -
If you want to save space on your computer, use one of these deployments -

Vercel Deployment - 'deploymant link'
GitHub Pages Deployment - 'deployment link'

Will be done soon

Issue Closed and all the changes commited.


Unable to find PR

'[' -n /github/workspace ']'
cd /github/workspace
tfsec --format=json .
echo 'tfsec violations were identified, running commenter...'
tfsec violations were identified, running commenter...
commenter
Starting the github commenter...
The commenter failed with the following error:
PR number [8] not found for DSC/github_actions

This is my workflow:
name: tfsec-pr-commenter
on:
  pull_request:
jobs:
  tfsec:
    name: tfsec PR commenter
    runs-on: [ self-hosted ]

    steps:
      - name: Clone repo
        uses: actions/checkout@master

      - name: tfsec
        uses<EMAIL_ADDRESS>        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}

Am I missing something?

Hey @nascit - that seems strange - can I just confirm you're running it in the DSC/github_actions repo and that the GITHUB_TOKEN you're using does have permissions against it?
might be worth changing it to
with:
   github_token: ${{ github.token }}

which is the automatically generated token and should definitely have the correct permissions to read PRs

The error comes from github commenter:
https://github.com/owenrumney/go-github-pr-commenter/blob/605aaddf11ea687ceb97f619f1ee0dd9b4f21cb3/commenter/connector.go#L35
I'm using GHES, possibly it only supports github.com ?

Hey @nascit  - I'm assuming that's Github Enterprise server and it's self-hosted? If this is the case then I think I just need to support passing in API URL.
Are you happy to be a bit of tester for this if I add the feature?

Yes, I'd love to test that

I am also getting this error. I had this running without issue for over a month and these started popping up recently

Hey - apologies for the [huge] delay on this - the underlying library is being tested with GHE this week then I'll update this to use it

I also run into that problem on GHES with self-hosted runner:

The commenter failed with the following error:
failed to create a new commenter. PR number [number] not found for [repo-name]

Is there any fix in the pipeline or workaround? Thanks a lot.

As I'm also encountering the same issue with Github Enterprise, I'm also available to test out stuff. Thank you!

@owenrumney Could you please take a look at #77 - is this similar to your idea?
I tested the change with my GitHub Enterprise environment. However, I run the commenter outside of GitHub Actions workflows (long story, need to orchestrate everything with Jenkins). Would appreciate a second pair of eyes on the PR.
Feedback from real GitHub Enterprise + GitHub Actions users is much appreciated!

The commenter failed with the following error:
failed to create a new commenter. PR number [139] not found for #redacted#
`

Sorry @tzeappa - it was a silly typo on my side. Updated the PR - can you please give it another go?

I'm running the action from command line, not from GitHub Actions workflow, and pass the following variables:
INPUT_GITHUB_TOKEN=<my-github-token> GITHUB_REPOSITORY=<my-repository> GITHUB_API_URL="https://github.<my-company>.com/api/v3" GITHUB_EVENT_PATH=<path-to-event-json> GITHUB_WORKSPACE=<workspace-folder> INPUT_SOFT_FAIL_COMMENTER=true ./commenter

GITHUB_EVENT_PATH variable would work only if you apply #76 as well.

Tested today invoking through a reusable workflow (Github Enterprise), resulting in failed to create a new commenter. PR number [34] not found. I can confirm the PR exists.
When invoking in a non-reusable workflow it works as intended.

@nikonet thanks for the update. Just to confirm - are you saying that you can successfully publish the comments to a PR in GtHub Enterprise repo if you use default shell / non-reusable workflow?
If reusable workflow is the only remaining issue, I would try to set GITHUB_API_URL variable explicitly (use https://github.<my-company>.com/api/v3 as a value). I suspect that can be the issue because of the following:

Any environment variables set in an env context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the env context, see "Context and expression syntax for GitHub Actions."

Yes, I can publish through a reusable-workflow as long as I do not use bash as shell. Meaning the tfsec-pr-commenter is invoked in the reusable workflow entirely. I'm not sure if it works if using bash in a non-reusable workflow.

      - name: Set Github Enterprise URL
        id: set-env-variables
        run: |
          echo "GITHUB_API_URL=https://github.<my-company>.com/api/v3" >> $GITHUB_ENV
      - name: tfsec PR Commentor
        uses<EMAIL_ADDRESS>        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}

I tried this and this is still failing. Is there something wrong I have done?

@nikonet thanks for the update. Just to confirm - are you saying that you can successfully publish the comments to a PR in GtHub Enterprise repo if you use default shell / non-reusable workflow?
If reusable workflow is the only remaining issue, I would try to set GITHUB_API_URL variable explicitly (use https://github.<my-company>.com/api/v3 as a value). I suspect that can be the issue because of the following:

Any environment variables set in an env context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the env context, see "Context and expression syntax for GitHub Actions."

name: tfsec PR Commentor
uses<EMAIL_ADDRESS>with:
github_token: ${{ secrets.GITHUB_TOKEN }}

No still getting "error failed to create a new commenter. PR number [260] not found" after trying above line, kindly suggest.


[Feature Request] Watch for changes in "compile_commands.json" and "compile_flags.txt"

Currently only restart VSCode to make clangd re-read "compile_commands.json" and "compile_flags.txt"

Good idea. The most obvious way I can think of is put a bool stale() method on CompilationDatabase.

Currently only restart VSCode to make clangd re-read "compile_commands.json" and "compile_flags.txt"

Well there's a command Restart the clangd language server which is slightly less bad but still the file should just be watched properly.

@ChristianKuehnel

This was done in https://github.com/llvm/llvm-project/commit/98993193e9037345ad13720a62974064a5f3d953 and some related commits.

This was done in https://github.com/llvm/llvm-project/commit/98993193e9037345ad13720a62974064a5f3d953 and some related commits.

Note this issue's functionality of restarting when compile_commands.json was removed at some point in favor of just "hot reload" at file level. Details are in https://github.com/clangd/vscode-clangd/issues/300#issuecomment-2348016329.
I think you can vote there if want option to have clangd restart functionality back also.


[AutoPR] deviceprovisioningservices/resource-manager

Created to accumulate context: deviceprovisioningservices/resource-manager

(message created by the CI based on PR content)


Upgrading to 2024.2.2 Issue

Devs,
Just attempted to run an upgrade from 2023.45.1 to 2024.2.2 and I ran into the following Perl issue with Net-SSLeay:

duration: 2690.974
name: cpan install Digest::CRC
result: true
start_time: '10:26:18.870233
cmd_|-remnux-perl-packages-exiftool_|-cpan install Image::ExifTool_|-run:
id: remnux-perl-packages-exiftool
run_num: 824
sls: remnux.perl-packages.exiftool
changes: {}
comment: 'One or more requisite failed: remnux.perl-packages.net-ssleay.remnux-perl-packages-net-ssleay-install'
duration: 0.007
name: cpan install Image::ExifTool
result: false
--
\ 13:53:58 GMT\nRunning install for module 'Net::SSLeay'\nChecksum for /root/.cpan/sources/authors/id/C/CH/CHRISN/Net-SSLeay-1.94.tar.gz
\ ok\n'YAML' not installed, will not store persistent state\nConfiguring C/CH/CHRISN/Net-SSLeay-1.94.tar.gz
\ with Makefile.PL\nDo you want to run external tests?\nThese tests will
\ fail if you do not have network connectivity. [n] n\n*** If there are
\ build errors, test failures or run-time malfunctions,\n    try to use the
\ same compiler and options to compile your OpenSSL,\n    Perl, and Net::SSLeay.\n
Warning: No success on command[/usr/bin/perl Makefile.PL INSTALLDIRS=site]\n
\  CHRISN/Net-SSLeay-1.94.tar.gz\n  /usr/bin/perl Makefile.PL INSTALLDIRS=site
\ -- NOT OK"
comment: Command "cpan install Net::SSLeay" run
duration: 3446.299
name: cpan install Net::SSLeay
result: false

Full Saltstack log:
saltstack.log
grep'ed down results:
errfiltered.log
I was able to do clean install on a new Ubuntu 20.04.6 (Mate) VM last night using the addon mode with no issues. Not really sure why upgrading is giving me issues with this.
when I run just cpan it runs the following:

Loading internal logger. Log::Log4perl recommended for better logging
Sorry, we have to rerun the configuration dialog for CPAN.pm due to
some missing parameters. Configuration will be written to
<</home/{user}/.cpan/CPAN/MyConfig.pm>>

CPAN.pm requires configuration, but most of it can be done automatically.
If you answer 'no' below, you will enter an interactive dialog for each
configuration option instead.

Would you like to configure as much as possible automatically? [yes]

Did something possible get reset with this package that I need to reconfigure before trying to run the upgrade again? I am not confirming any changes at this point till I can do some more research and make sure that going through these choice menus won't possibly screw up the installation process further.
EDIT: /home/{user}/.cpan/CPAN/MyConfig.pm only has 1; in it which may be a config written by the net-ssleay.sls in the salt.
Thanks and cheers!

Another thing, the following is in the CPAN MyConfig.pm for root:

$CPAN::Config = {
'applypatch' => q[],
'auto_commit' => q[0],
'build_cache' => q[100],
'build_dir' => q[/root/.cpan/build],
'build_dir_reuse' => q[0],
'build_requires_install_policy' => q[yes],
'bzip2' => q[/usr/bin/bzip2],
'cache_metadata' => q[1],
'check_sigs' => q[0],
'cleanup_after_install' => q[0],
'colorize_output' => q[0],
'commandnumber_in_prompt' => q[1],
'connect_to_internet_ok' => q[1],
'cpan_home' => q[/root/.cpan],
'ftp_passive' => q[1],
'ftp_proxy' => q[],
'getcwd' => q[cwd],
'gpg' => q[/usr/bin/gpg],
'gzip' => q[/usr/bin/gzip],
'halt_on_failure' => q[0],
'histfile' => q[/root/.cpan/histfile],
'histsize' => q[100],
'http_proxy' => q[],
'inactivity_timeout' => q[0],
'index_expire' => q[1],
'inhibit_startup_message' => q[0],
'keep_source_where' => q[/root/.cpan/sources],
'load_module_verbosity' => q[none],
'make' => q[/usr/bin/make],
'make_arg' => q[],
'make_install_arg' => q[],
'make_install_make_command' => q[/usr/bin/make],
'makepl_arg' => q[INSTALLDIRS=site],
'mbuild_arg' => q[],
'mbuild_install_arg' => q[],
'mbuild_install_build_command' => q[./Build],
'mbuildpl_arg' => q[--installdirs site],
'no_proxy' => q[],
'pager' => q[/usr/bin/less],
'patch' => q[/usr/bin/patch],
'perl5lib_verbosity' => q[none],
'prefer_external_tar' => q[1],
'prefer_installer' => q[MB],
'prefs_dir' => q[/root/.cpan/prefs],
'prerequisites_policy' => q[follow],
'recommends_policy' => q[1],
'scan_cache' => q[atstart],
'shell' => q[/bin/bash],
'show_unparsable_versions' => q[0],
'show_upload_date' => q[0],
'show_zero_versions' => q[0],
'suggests_policy' => q[0],
'tar' => q[/usr/bin/tar],
'tar_verbosity' => q[none],
'term_is_latin' => q[1],
'term_ornaments' => q[1],
'test_report' => q[0],
'trust_test_report_history' => q[0],
'unzip' => q[/usr/bin/unzip],
'urllist' => [q[http://www.cpan.org/]],
'use_prompt_default' => q[0],
'use_sqlite' => q[0],
'version_timeout' => q[15],
'wget' => q[/usr/bin/wget],
'yaml_load_code' => q[0],
'yaml_module' => q[YAML],
};
1;
END

Could something possibly overwrote the user config causing it to require reconfiguration?

It looks like the actual cause of the error is on line 66026:
# [ERROR   ] stderr: /usr/local/bin/openssl: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
Use of uninitialized value $output in scalar chomp at Makefile.PL line 425.
Use of uninitialized value $output in pattern match (m//) at Makefile.PL line 428.
Use of uninitialized value $output in pattern match (m//) at Makefile.PL line 431.
Use of uninitialized value $output in concatenation (.) or string at Makefile.PL line 440.
*** OpenSSL version test failed
    (`' has been returned)
    Either you have bogus OpenSSL or a new version has changed the version
    number format. Please inform the authors!
# [ERROR   ] retcode: 1

Could you let me know what version of openssl is installed (if any) currently in that VM?

@digitalsleuth Apt says 1.1.1f. When I try to anything with openssl like help or version it tells me:

openssl: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory.

Guess my libssl.so.3 somehow disappeared. I'll try doing a re-install of openssl and see if that fixes it.

I tried the same process (brand new Ubuntu Mate 20.04.6, fully updated). Default OpenSSL for me is 1.1.1f as well, with no REMnux installed. Attempted the exiftool install with no issues.
Before re-installing, you could try running sudo ldconfig to see if that resolves the openssl issue. If it does, I can account for that in the state file.

Oops, sorry buddy I didn't wait and already am trying a reinstall now.
I also think I might have installed the latest OpenSSL (3.x) from their site or git to be more current and had the APT repo package installed as well, but I'm not sure on that since I can't get a version.
Quick question though, If I do reinstall OpenSSL but using the git to install 3.x again, do you know if REMnux has any dependencies that require 1.1.1 to operate? Just curious since 1.1.1 hit its last release back in 2018 and its LTS/EOL was back in September of 2023.
Cheers!

UPDATE 1: I tried uninstalled the APT package and trying the command again and this error still persists. So I'm not sure if there is another package somewhere that the link in /usr/local/bin is referencing that the system is looking to and it doesn't have this required file? Hopefully a clean install will fix it.

UPDATE 3: Reinstall didn't fix it but did get me the latest version at least. A quick Google-fu and found a suggestion to try sudo ldconfig /usr/local/lib64/. So I ran the command and it seems to have fixed it. and seems to be working with no libssl.so issues.
Trying another REMnux upgrade now that is fixed! Will let you know how it goes.

Oops. Don't think I did try with sudo.

If you're already trying again, simply try the sudo ldconfig command without /usr/local/lib64/ to see if that resolves the issue first.

I'm running some testing now, I'll let you know how it goes, hopefully it resolves this issue.

Sounds good. Also appears the latest stable version available for OpenSSL is 3.2.0 but I guess when I did a git clone for the build I made, it pulled down 3.3.0-dev. So I might pull 3.2.0 to build and install so I at least have a stable version. I like current but I'm not looking to use the dev version of it if I don't have to.

So, I have tried about 10 different ways to intentionally make this break, but I've been unable to duplicate the error. Are you using the ISO downloaded from the Ubuntu page, or is it one you had previously built but are installing REMnux into? If it's a previous build, there may have been an error induced by an upgrade to the SSL package. Even after the successful install, the openssl version is still 1.1.1f.
I'll manually install openssl 3+ to see the best way to account for that in the future, but in order to get everything to work during the install, I would recommend temporarily removing openssl 3, then installing it after completion (provided you want/need version 3+).

I downloaded and used the ISO from Ubuntu Mate's site to build the system I am using.
For about a week I had an issue with my box locking up on the login screen after boot before even being able to put in a password. Not sure what was the cause but I removed 3.0 from my system, tried a few tweaks and I guess something worked because it's back working again. Long story short, I'm back to just having 1.1.1f on my system for now till I can make sure it wasn't having both that might have been a part of what messed it up.
I haven't tried running an update yet since then but I'll do that this morning to see if it is working again now that I only have 1.1.1f installed.

If you take a peek over at the salt-state repo and the new issue I just opened (remnux/salt-states#274) I guess uninstalling OpenSSL v3 fixed my issue with that. That problem doesn't seem to be giving me any more issue with the update/upgrade process. And whatever issue I was having with Radare during the upgrade/upgrade process, I seemed to have figured out a work around to make it work. So I'll close this issue out since my original issue seems to be fixed.
Thanks Digital for taking some time to see if you can figure it out!
Cheers!


EpollDatagramChannel avoid getOption

Motivation:
EpollDatagramChannel uses getOption in the isActive method. getOption is backed by a relatively large conditional if/else if block and this conditional checking can be avoided in the epoll transport.
Modifications:

Add EpollDatagramChannelConfig#getActiveOnOpen and use this in EpollDatagramChannel

Result:
Conditional checking due to getOption is removed from EpollDatagramChannel.

4.1 (0befcd8) 4.0 (3b65e7e)