blob is not defined

I get an error when trying to validate a blob from a input file, regardless or whether it is empty or not.
import {blob,object} from 'valibot'
import {decode} from 'decode-formdata'

const schema = object({file: blob()})
const data = decode(formData, {files:['file']})
const result = safeParse(schema, data)

ReferenceError: Blob is not defined
     at Object._parse (file:///C:/repo/node_modules/.pnpm/valibot@0.19.0/node_modules/valibot/dist/index.js:570:30)
     at Object._parse (file:///C:/repo/node_modules/.pnpm/valibot@0.19.0/node_modules/valibot/dist/index.js:2130:31)
     at Proxy.safeParse (file:///C:/repo/node_modules/.pnpm/valibot@0.19.0/node_modules/valibot/dist/index.js:3689:25)
     at default (C:/repo/src/routes/+page.server.ts:34:42)
     at runMicrotasks (<anonymous>)
     at processTicksAndRejections (node:internal/process/task_queues:96:5)
     at async Module.handle_action_json_request (C:/repo/node_modules/.pnpm/@sveltejs+kit@1.25.0_svelte@4.2.1_vite@4.4.9/node_modules/@sveltejs/kit/src/runtime/server/page/actions.js:57:16)
     at async resolve (C:/repo/node_modules/.pnpm/@sveltejs+kit@1.25.0_svelte@4.2.1_vite@4.4.9/node_modules/@sveltejs/kit/src/runtime/server/respond.js:415:18)
     at async Object.handle (C:/repo/src/hooks.server.ts:17:10)
     at async Module.respond (C:/repo/node_modules/.pnpm/@sveltejs+kit@1.25.0_svelte@4.2.1_vite@4.4.9/node_modules/@sveltejs/kit/src/runtime/server/respond.js:282:20)

The problem is that your runtime is not aware of Blob. Can you describe where and how you execute Valibot? According to MDN, Blob should by available in all modern browsers as well as in Deno and Node.js. Could it be that you are using an old version of Node.js?

I am on node16, that is most likely the problem.
Is it possible to set minimum requirements for this package?

Please try to add an polyfill on your own first. But it is a good hint. If that's the problem, we should mention it in our docs once we add the API reference to it.

I will add a note to our source code to document this in the long run.


feature_modification_sops_node

1.标准运维任务节点表单问题

Codecov Report

Merging #20 (a13ea72) into v2.6.x_develop (327a9fc) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop      #20   +/-   ##
===============================================
  Coverage           51.31%   51.31%
===============================================
  Files                 688      688
  Lines               36364    36364
===============================================
  Hits                18660    18660
  Misses              17704    17704

Continue to review full report at Codecov.

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


Cannot use private IP address as it is either allocated to a resource or being cleaned up.

Describe the bug
Whenever we define a second ingress, or remove all of the ingresses and try to create a new ingress, we get the following error:
Log:

application-gateway-ingress-controller-ingress-azure-9bf4b95b8r ingress-azure E0430 17:37:43.416766       1 controller.go:132] Error mutating App Gateway config from k8s event. network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="ApplicationGatewayFrontendIPStaticPrivateIPAddressNotAvailable" Message="FrontendIpConfiguration /subscriptions/SUBSCRIPTION_ID/resourceGroups/k8s/providers/Microsoft.Network/applicationGateways/k8s-appgateway/frontendIPConfigurations/AzureVnet-feip2 cannot use private IP address <IP_ADDRESS> as it is either allocated to a resource or being cleaned up." Details=[]

To Reproduce
Steps to reproduce the behavior:

Install controller
Create a AGW
Create the following ingress (this will result in a nice ingress):

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test
  annotations:
    kubernetes.io/ingress.class: azure/application-gateway
    appgw.ingress.kubernetes.io/appgw-ssl-certificate: "mycert"
    appgw.ingress.kubernetes.io/use-private-ip: "true"
spec:
  rules:
  - host: guestbook.test-k8s.mydomain.com
    http:
      paths:
      - backend:
          serviceName: frontend
          servicePort: 80

Repeat step #3. The ingress will look normal, but the error (ApplicationGatewayFrontendIPStaticPrivateIPAddressNotAvailable) will appear.

Ingress Controller details
Version: 1.2.0-rc1
pod describe:
kdp application-gateway-ingress-controller-ingress-azure-9bf4b95b8r
Name:           application-gateway-ingress-controller-ingress-azure-9bf4b95b8r
Namespace:      cpt
Priority:       0
Node:           aks-cpt-34239724-vmss000000/<IP_ADDRESS>
Start Time:     Thu, 30 Apr 2020 17:17:01 +0200
Labels:         aadpodidbinding=application-gateway-ingress-controller-ingress-azure
                app=ingress-azure
                pod-template-hash=9bf4b78c7
                release=application-gateway-ingress-controller
Annotations:    prometheus.io/port: 8123
                prometheus.io/scrape: true
Status:         Running
IP:             <IP_ADDRESS>
IPs:            <none>
Controlled By:  ReplicaSet/application-gateway-ingress-controller-ingress-azure-9bf4b78c7
Containers:
  ingress-azure:
    Container ID:   docker://a6697e2d36a2a92f2c26a8c29444606fa20e69c77d49f1540910854ef89a39b6
    Image:          azure-application-gateway/kubernetes-ingress:1.2.0-rc1
    Image ID:       docker-pullable://azure-application-gateway/kubernetes-ingress@sha256:dd95b2feaf24e7ba6773452fb842d0eba5a6ea8a5d19bf22035fdcad78b18941
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Thu, 30 Apr 2020 17:17:03 +0200
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:8123/health/alive delay=15s timeout=1s period=20s #success=1 #failure=3
    Readiness:      http-get http://:8123/health/ready delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment Variables from:
      application-gateway-ingress-controller-cm-ingress-azure  ConfigMap  Optional: false
    Environment:
      AZURE_CONTEXT_LOCATION:  /etc/appgw/azure.json
      AGIC_POD_NAME:           application-gateway-ingress-controller-ingress-azure-9bf4b95b8r (v1:metadata.name)
      AGIC_POD_NAMESPACE:      cpt (v1:metadata.namespace)
    Mounts:
      /etc/appgw/azure.json from azure (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from application-gateway-ingress-controller-sa-ingress-azure-tobqzbq (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  azure:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/kubernetes/azure.json
    HostPathType:  File
  application-gateway-ingress-controller-sa-ingress-azure-tobqzbq:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  application-gateway-ingress-controller-sa-ingress-azure-tobqzbq
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

Hello,
I'm also facing the exact same error.

What is your AGW config @flmarins ?

What is your AGW config @flmarins ?
This is the template deployed for the AGW, WAF_V2
{     "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",     "contentVersion": "<IP_ADDRESS>",     "parameters": {},     "variables": {         "appGwID": "[resourceId('Microsoft.Network/applicationGateways', 'egp-u-aks-agw')]"     },     "resources": [         {             "type": "Microsoft.Network/applicationGateways",             "apiVersion": "2019-04-01",             "name": "egp-u-aks-agw",             "location": "westeurope",             "dependsOn": [],             "tags": {},             "properties": {                 "backendAddressPools": [                     {                         "name": "appGatewayBackendPool"                     }                 ],                 "backendHttpSettingsCollection": [                     {                         "name": "appGatewayBackendHttpSettings",                         "properties": {                             "Port": 80,                             "Protocol": "Http",                             "CookieBasedAffinity": "disabled",                             "connectionDraining": {                                 "enabled": false,                                 "drainTimeoutInSec": 1                             }                         }                     }                 ],                 "frontendIPConfigurations": [                     {                         "name": "appGatewayFrontendIP",                         "properties": {                             "publicIPAddress": {                                 "id": "/subscriptions/SubId/resourceGroups/RgAks/providers/Microsoft.Network/publicIPAddresses/egp-u-aks-agw-pip"                             }                         }                     }                 ],                 "frontendPorts": [                     {                         "name": "appGatewayFrontendPort",                         "properties": {                             "Port": 80                         }                     }                 ],                 "gatewayIPConfigurations": [                     {                         "name": "appGatewayFrontendIP",                         "properties": {                             "subnet": {                                 "id": "/subscriptions/SubId/resourceGroups/RgVnet/providers/Microsoft.Network/virtualNetworks/External_Network/subnets/External_Network_AKS_AGW"                             }                         }                     }                 ],                 "httpListeners": [                     {                         "name": "appGatewayHttpListener",                         "properties": {                             "FrontendIpConfiguration": {                                 "Id": "[concat(variables('appGwID'), '/frontendIPConfigurations/appGatewayFrontendIP')]"                             },                             "FrontendPort": {                                 "Id": "[concat(variables('appGwID'), '/frontendPorts/appGatewayFrontendPort')]"                             },                             "Protocol": "http",                             "SslCertificate": null                         }                     }                 ],                 "sku": {                     "name": "WAF_v2",                     "tier": "WAF_v2",                     "capacity": 2                 },                 "requestRoutingRules": [                     {                         "Name": "rule1",                         "properties": {                             "RuleType": "Basic",                             "httpListener": {                                 "id": "[concat(variables('appGwID'), '/httpListeners/appGatewayHttpListener')]"                             },                             "backendAddressPool": {                                 "id": "[concat(variables('appGwID'), '/backendAddressPools/appGatewayBackendPool')]"                             },                             "backendHttpSettings": {                                 "id": "[concat(variables('appGwID'), '/backendHttpSettingsCollection/appGatewayBackendHttpSettings')]"                             }                         }                     }                 ]             }         }     ],     "outputs": {         "applicationGateway": {             "type": "Object",             "value": "[reference('egp-u-aks-agw')]"         }     } }

Having the same problem. I noticed today that I get this error when creating a private frontend ip using the Azure Portal. So might now be a AGIC specific issue.

I'm also having this issue with a newly deployed AppGW, AKS Cluster & AGIC.
error: network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="ApplicationGatewayFrontendIPStaticPrivateIPAddressNotAvailable" Message="FrontendIpConfiguration /subscriptions/604665e1-18a1-4c68-b160-f1a48be5c014/resourceGroups/rg-contoso-dev-networking-appgateways/providers/Microsoft.Network/applicationGateways/appgw-7490e25be7cbd2a7/frontendIPConfigurations/appgw-7490e25be7cbd2a7-private-ipconf cannot use private IP address <IP_ADDRESS> as it is either allocated to a resource or being cleaned up.

Frontend config:
[
   {
      "PrivateIPAllocationMethod":"Dynamic",
      "PublicIPAddress":{
         "Id":"/subscriptions/604665e1-18a1-4c68-b160-f1a48be5c014/resourceGroups/rg-contoso-dev-networking-appgateways/providers/Microsoft.Network/publicIPAddresses/appgw-df0ddae6e805dbcc-pip"
      },
      "ProvisioningState":"Succeeded",
      "Type":"Microsoft.Network/applicationGateways/frontendIPConfigurations",
      "Name":"appgw-df0ddae6e805dbcc-public-ipconf",
      "Etag":"W/\"fb1ccc50-d7d5-41bd-90e4-e491222a9aa7\"",
      "Id":"/subscriptions/604665e1-18a1-4c68-b160-f1a48be5c014/resourceGroups/rg-contoso-dev-networking-appgateways/providers/Microsoft.Network/applicationGateways/appgw-df0ddae6e805dbcc/frontendIPConfigurations/appgw-df0ddae6e805dbcc-public-ipconf"
   },
   {
      "PrivateIPAddress":"<IP_ADDRESS>",
      "PrivateIPAllocationMethod":"Static",
      "Subnet":{
         "Id":"/subscriptions/604665e1-18a1-4c68-b160-f1a48be5c014/resourceGroups/rg-contoso-dev-networking/providers/Microsoft.Network/virtualNetworks/vnet-contoso-dev-01/subnets/AppGatewaySubnet"
      },
      "ProvisioningState":"Succeeded",
      "Type":"Microsoft.Network/applicationGateways/frontendIPConfigurations",
      "Name":"appgw-df0ddae6e805dbcc-private-ipconf",
      "Etag":"W/\"fb1ccc50-d7d5-41bd-90e4-e491222a9aa7\"",
      "Id":"/subscriptions/604665e1-18a1-4c68-b160-f1a48be5c014/resourceGroups/rg-contoso-dev-networking-appgateways/providers/Microsoft.Network/applicationGateways/appgw-df0ddae6e805dbcc/frontendIPConfigurations/appgw-df0ddae6e805dbcc-private-ipconf"
   }
]

Hey all - this is a fix outside of AGIC that we've completed and are testing right now. We expect to roll out the fix within the next couple weeks, please check back on this thread for more updates. I'll close this thread when the fix is fully rolled out.

Is there any workaround at this time or do we have to use the public IP for any new sites published through the AppGW?

Is there any workaround at this time or do we have to use the public IP for any new sites published through the AppGW?

I’m able to create multiple entries for the same private ip using different hostname, however if you delete all configurations using the private ip you will need to provision a new private ip in the AppGw to use again

Thanks. That is better than recreating the AppGW.

Wanted to update this thread to let everyone know that the fix for this has been rolled out; all new AppGWs should not encounter this issue and only a subset of existing AppGWs which were in a specific state previously would run into this issue. Please test your private IP scenarios; if you're still experiencing issues with using the private IP, try changing to a different private IP address. If that's not possible or you still run into issues, please create a support ticket through Azure Portal and we'll be able to fix things accordingly.

I still run in this error, even in new VNET & AGW setups.

@sbkg0002 - please create a support ticket through Portal and a support engineer will be able to help you there.

I did, it appears that you should use the first usable IP of the subnet as a static AGW IP.

After changing the IP address of the App GW it was working for a few days, but now the issue appears again. I just changed the IP address again and afterwards it was back working. So it seems the issue is not fully fixed yet. Besides that, I cannot use several IP addresses from the VNet as App GW IP, since they are all allegedly "either allocated or being cleaned up", even though they are not in use at all.

This is still a problem, I've been encountering it for moths while developing Azure CLI to deploy environments that include an AGW. While creating script its often very typical to deploy an asset (such as AGW), delete the asset (or Resource Group), and then redeploy to test modifications.
The offending command is: az network application-gateway frontend-ip create

Experiencing the same problems, seems that the issue hasn't been fixed yet. I've deployed the Application Gateway a few days ago.

Hi, I'm also having the same issue. I tried switching to another IP and that worked, however if I see that other people tried that before and encountered the same problem again after a while with the new IP, I'm afraid I cannot consider that a "proper solution".
And if otherwise the only resolution mentioned here is "ask a service engineer", I'm wondering what they can do?

@mscatyao , I also experienced. Resolved by changing front end address, but based on comments I expect to have to do this again.  What does it take to get this ticket reopened (or a new issue) and a proper fix?

@mscatyao , I also experienced this issue, resolved by changing front end private ip address, I have 9 different environments with 9 different application gateways and in all of them i have the same issue, what does it take to get this ticket reopened (or a new issue) and a proper fix?

poke

Hi, I just update to AGIC to version 1.5.0 today and encounter the issue again:
Unable to reserve private IP as it is already in use. Please select a different private IP.

Still experiencing this issue. will create a new issue.

Experiencing this today, probably because I deleted an AKS instance and created it again with the same name a few minutes later :P
Terraform timed out during the deletion step, so it's possible I created it before the deletion was truly finished


Restructuring Gradle Build #2 - Fixing the unnitentional dependency on the Ant build

Most of the PR focuses around fixing the dependency that the build had on the native Ant build having been run first.
Key fixes:

dist task has been added to root project
Fixed publishing in all subproejcts
Add java-main which got missed in the first round of restructuring
language build now uses a GradleBuild task to defer evalutaion of dependencies that is required for calling the Ant build
Fixed the naming of JAR artifacts in compiler-java as well as some missing files from the JARs.
Added support for automatic coying *.plugin files in subprojects.

Outstanding issues:

module.xml files
OSGI

Can one of the admins verify this patch? (see README)

@ysb33r I was able to build successfully! Nice job!
One thing I encountered: in the builtByGradle/distribution/repo/ folder I'm seeing _version_ folders from the template repository in runtime.

Another thing is that the Ant build creates a BUILDID file in the distribution folder that contains the (short) Git commit id of the current HEAD of the Git repository that is being used to build things. The same ID is also replaced in the common/src/com/redhat/ceylon/common/Versions.java file.
Look at the defcurrentcommit task in dist/build.xml for how we do that. (We run git rev-parse --short HEAD)
But it should also be possible to define the buildid on the command line when executing the gradlew build command in case we're trying to build plain sources (not from a Git repository). In case of Ant we do this by passing -Dbuildid=XXXX on the command line.
(We haven't done this for ant, but an error message if no Git repository was found and also no -Dbuildid was passed would be great)

Also missing from the root distribution folder are: contrib, LICENSE-ASL, LICENSE-GPL-CP, NOTICE, README.md, samples and templates. These can simply be copied from dist.

Hah, you actually improved something: in our distribution the bin/ceylon-compile-js.plugin file is missing!
From my previous comment I failed to mention the dist/bin folder. It's contents should also be copied to the distribution's bin folder. (We're missing bin/ceylon-format.plugin)

The following remarks are not errors but requests. I wonder if it would be possible to add the following build "aliases" somehow? So people don't have to learn too many new things at once and can just change "ant xxx" to "./gradlew xxx" and keep on working:

dist - builds the distribution
clean-sdk - calls ant clean in the ../ceylon-sdk folder
sdk - calls ant publish ide-quick in the ../ceylon-sdk folder
clean-ide - calls ant clean in the ../ceylon-.formatter, ../ceylon.tool.converter.java2ceylon, ../ceylon-ide-common, ../ceylon-ide-eclipse and ../ceylon-ide-intellij folders
eclipse - calls ant publish ide-quick in the ../ceylon-.formatter, ../ceylon.tool.converter.java2ceylon, ../ceylon-ide-common and ../ceylon-ide-eclipse folders
intellij - calls ant publish ide-quick in the ../ceylon-.formatter, ../ceylon.tool.converter.java2ceylon, ../ceylon-ide-common and ../ceylon-ide-intellij folders
clean-all - same as calling clean locally as well as clean-sdk and clean-ide

I assume that at some point in time we'll convert all of them to Gradle, but for now this would be great.

On the last one. Indeed. There is already a dist in the root project. Even if I rename that to distribution, someone could type ./gradlew dist and it will keep working.
I'll add the others to the root project as well. Generally in Gradle people prefer to use camel-case for task names rather than snake-case. I think there was talk on the Gradle dev ML about disallowing tasks with certain non-word characters. I'll test to see if the dashes will work though.

Also missing from the root distribution folder are: contrib, LICENSE-ASL, LICENSE-GPL-CP, NOTICE, README.md, samples and templates. These can simply be copied from dist.

slaps forehead - I thought I added that.

From my previous comment I failed to mention the dist/bin folder. It's contents should also be copied to the distribution's bin folder. (We're missing bin/ceylon-format.plugin)

That's been taken care of in next PR

One thing I encountered: in the builtByGradle/distribution/repo/ folder I'm seeing version folders from the template repository in runtime.

Fixed by eff8cd2e72229aa885e93db0b34e190b4818fa5e

But it should also be possible to define the buildid on the command line when executing the gradlew build command in case we're trying to build plain sources (not from a Git repository). In case of Ant we do this by passing -Dbuildid=XXXX on the command line.

Covered by d661aa7cc220dcb5fd9ee961db39a0c01d7c7be3

(We haven't done this for ant, but an error message if no Git repository was found and also no -Dbuildid was passed would be great)

Covered by 1ce7a3b83612df3b6f98286093146c34990b63a6


gender country, changes, plot and table not matching

in our meeting we saw that gender by country table had 2 entries, but plot had more.

I think this is fixed. Closing.


Add 'expired' method to Signed class

Description of issue or feature request:
Add a method of Signed metadata class returning information about metadata expiration given a reference time.
Current behavior:
Signed class already contains expires, a metadata expiration datetime object.
Expected behavior:
A method exists that checks the 'expires' attribute against a reference time.
def is_expired(self, reference_time: float) -> bool

tuf.formats already provides some convertion functions:
https://github.com/theupdateframework/tuf/blob/2c360d0538f73a59854add867234f48a47f7d9a3/tuf/formats.py#L616
https://github.com/theupdateframework/tuf/blob/2c360d0538f73a59854add867234f48a47f7d9a3/tuf/formats.py#L646

Is a UNIX timestamp the preferred type for reference_time? Rather than a raw expiration string or a Python datetime object?

What's the intended use case? Would any of the datatypes be more convenient for the caller, that is which datatype would require the least preliminary conversion?
I lean towards making reference_time a datetime object, for consistency with the type of the Metadata expires field. And I'd also make reference_time optional and default to datetime.now().

Fully agreed with both comments. I have a WIP patch that takes a datetime object for reference_time and defaults to datetime.now() when no reference_time is passed.
I believe the motivating use-case is expiration checks in the experimental client, so I'll wait for @sechkova to comment on whether a datetime object is useful.

No strong preferences, the client will use whatever  we choose :)
I agree with using datetime objects plus the datetime module seems to be less platform dependent than time (which can be used to return UNIX time).
Let's make sure we enforce UTC times everywhere.


Apply model tester

Ticket
#269
Problem description
Continue with #271 , apply ModelTester class to all the tests/models test
What's changed

Apply ModelTaster class to all the tests/models test
This comment mention the convert bf16 problem, and after I doing apply, I think the better site to convert bf16 is in the _load_model & _load_inputs stage, so I remove convert bf16 code from set_model_* & set_input_*
Remove old usage of record_property("torch_ttnn", (model, input, output)

This PR needs to merge #271 first

@swimdi one concern about this change is that out intension with model tests was to try to keep models in as pristine state as possible. We wanted users to see from tests that they can take a model and just run it by just adding a single line to compile it.
I ask to keep this into consideration. I assume its not possible to sit on both chairs and assume that the change you made is the only way to achieve the desired outcome (trace both inference and training via common infrastructure). But I want to check with you, in case you have ideas on how to minimize impact on models even more.

@ayerofieiev-tt  Or if I just let the testcase implement test_model_eval & test_model_train function, and the testcase is generated from template, which can just register detail function like set_model_eval / append_fake_loss_function, would this modify better?
# tests/models/test_xxx.py
class ThisTester(ModelTester):
  def __init__(self, model_name, mode):
    self.model_name = model_name
    self.mode = mode
    self.model = xxx
    self.inputs = xxx

  def test_model_eval(self, as_ttnn=False, option=None):
    model = self.model
    inputs = self.inputs
    # code of set model & input as eval
    if as_ttnn == True:
        model = self.compile_model(model, option)
    # code of run model
    # code of get result
  def test_model_train(self, as_ttnn=False, option=None):
    ...

If make sure load model & inputs deterministic then its code can put in test_model_eval & test_model_train (but will load model & inputs again in compile_and_run)

Hi @kevinwuTT I think the current code can also do the thing you say

Can also pass record_property to avoid running fixture
use test_model(self, as_ttnn=True, option=option) will do the torch compile

@swimdi
This will still require importing and modifying the test file around ModelTester right? My example was only relying on importing torch_ttnn which is what users who install the torch_ttnn package will do. ModelTester will be used for developers like us. I believe the ttnn package doesn't expose modules used for developing/testing like the check_pcc function for example. That means we can't use the test files outside of the testing environment. If we can re-use the model test files that will be nice. Otherwise, we will probably have to come up with some "demos" that are separate from tests. I was just wondering if you have any ideas if this is possible with ModelTester.

Hi @kevinwuTT,
Or I cancel the ModelTester class and flatten its inherit to all the test by using template?
For example, the test_mnist.py will be like this
import torch
import pytest
import torch_ttnn
from torchvision import transforms, datasets
from torch.utils.data import DataLoader

import torch.nn as nn
import torch.nn.functional as F

# adapted from https://github.com/pytorch/examples/blob/main/mnist/main.py
class MnistModel(torch.nn.Module):
    def __init__(self):
        super(MnistModel, self).__init__()
        self.conv1 = nn.Conv2d(1, 32, 3, 1)
        self.conv2 = nn.Conv2d(32, 64, 3, 1)
        self.dropout1 = nn.Dropout(0.25)
        self.dropout2 = nn.Dropout(0.5)
        self.fc1 = nn.Linear(9216, 128)
        self.fc2 = nn.Linear(128, 10)

    def forward(self, x):
        x = self.conv1(x)
        x = F.relu(x)
        x = self.conv2(x)
        x = F.relu(x)
        x = F.max_pool2d(x, 2)
        x = self.dropout1(x)
        x = torch.flatten(x, 1)
        x = self.fc1(x)
        x = F.relu(x)
        x = self.dropout2(x)
        x = self.fc2(x)
        output = F.log_softmax(x, dim=1)
        return output

class ThisTester:
    def __init__(self, model_name, mode):
        if mode not in ["train", "eval"]:
            raise ValueError(f"Current mode is not supported: {mode}")
        self.model_name = model_name
        self.mode = mode
        self.model = self._load_model()
        self.inputs = self._load_inputs()

    def _load_model(self):
        model = MnistModel()
        model = model.to(torch.bfloat16)
        return model

    def _load_inputs(self):
        transform = transforms.Compose([transforms.ToTensor()])
        test_dataset = datasets.MNIST(root="./data", train=False, transform=transform, download=True)
        dataloader = DataLoader(test_dataset, batch_size=1)
        test_input, _ = next(iter(dataloader))
        test_input = test_input.to(torch.bfloat16)
        return test_input

    def test_model_train(self, as_ttnn=False, option=None):
        # Fixing the random seed for reproducibility to ease debugging.
        #
        # Training processes involve more randomness compared to evaluation,
        # such as random initialization of weights.
        # Setting a fixed random seed is crucial for consistent testing
        # and debugging during the training process.
        torch.manual_seed(99)
        model = self.model
        model.train()
        model.zero_grad()

        # Eliminating randomness from Dropout to ensure consistent results.
        #
        # This is necessary for comparing the two training rounds:
        # one using PyTorch native code and the other using the PyTorch Dynamo TT backend.
        # Without this, the results would differ, making it impossible to compare the two implementations.
        for layer in model.modules():
            if isinstance(layer, torch.nn.Dropout):
                layer.p = 0  # Set dropout probability to 0

        inputs = self.inputs
        # Setting input tensor's `requires_grad` attribute to true.
        #
        # This allows us to use the gradient of the input as the golden result for the training process.
        # For further details, refer to the file `conftest.py` regarding the rationale behind.
        inputs.requires_grad_(True)

        if as_ttnn == True:
            model = torch.compile(model, backend=torch_ttnn.backend, options=option)
        outputs = model(inputs)
        loss = torch.mean(outputs)
        loss.backward()
        # Again, use the gradient of the input (`test_input.grad`) as the golden result for the training process.
        results = inputs.grad
        return results

    @torch.no_grad()
    def test_model_eval(self, as_ttnn=False, option=None):
        model = self.model.eval()
        inputs = self.inputs
        if as_ttnn == True:
            model = torch.compile(model, backend=torch_ttnn.backend, options=option)
        outputs = model(inputs)
        results = outputs
        return results

    def test_model(self, as_ttnn=False, option=None):
        if self.mode == "train":
            return self.test_model_train(as_ttnn, option)
        elif self.mode == "eval":
            return self.test_model_eval(as_ttnn, option)
        else:
            raise ValueError(f"Current mode is not supported: {self.mode}")

@pytest.mark.parametrize(
    "mode",
    ["train", "eval"],
)
def test_mnist_train(record_property, mode):
    model_name = "Mnist"
    record_property("model_name", f"{model_name} {mode}")

    tester = ThisTester(model_name, mode)
    results = tester.test_model()

    record_property("torch_ttnn", (tester, results))

And it will be generated by template like this
default_set_model_train = """
model.train()
model.zero_grad()

# Eliminating randomness from Dropout to ensure consistent results.
#
# This is necessary for comparing the two training rounds:
# one using PyTorch native code and the other using the PyTorch Dynamo TT backend.
# Without this, the results would differ, making it impossible to compare the two implementations.
for layer in model.modules():
    if isinstance(layer, torch.nn.Dropout):
        layer.p = 0  # Set dropout probability to 0
return model
"""

def export_model_test(file_path, load_model, load_input, set_model_train = default_set_model_train, ...):
    ...

mnist_load_model = """
model = MnistModel()
model = model.to(torch.bfloat16)
return model
"""

mnist_load_inputs = """
...
"""

export_model_test("test_mnist.py", load_model = mnist_load_model, load_input = mnist_load_inputs)


Add Rest Maturity Level 2 rule and rephrasing HATEOAS rule

This change solves #55 and adds more direct guidance to strive for REST Maturity Level 2 instead of Level 3.

I like you changes. Please go on to merge.
:+1:

:+1:

:+1:

Finally we put it to rest (for now) :smile:

For now, we have not seen a good reason to implement HATEOAS in an API.


cmake changes to build gpu support for windows

cmake changes to build gpu support for windows.
For this to work you need to have the code changes from:
https://github.com/tensorflow/tensorflow/pull/5051

Can one of the admins verify this patch?

corporate cla: Microsoft

re-submitted with a different user to clear cla:
https://github.com/tensorflow/tensorflow/pull/5074


[hi] Homepage hyperlinks Updated

Fixes #40370
I have successfully updated the code, Now the hyperlinks on the homepage are opening in a new tab ✅.

Hello @Jai-Solania-29, thank you for your contribution.
Is there a specific value add with this change other than opening the linked website on a new tab?
Was the value add/change discussed over an issue/PR and has it been agreed upon to affect this change only to these two specific pages of the documentation by any maintainer/reviewer/approver?
As one of the maintainers for Kubernetes documentation, I'd recommend that you follow the below steps:

close this PR with the /close command and first discuss whether this change is required over an issue.
Also, understand where this change needs to be applied i.e. the scope of the change. You have applied it to a single page & I'm sure there are more pages that have this same issue.
Open an umbrella PR for the English localisation AFTER agreement and get it approved + reviewed.
Make the changes for Hindi localization via another umbrella PR.
We will then need to notify other localisations to follow suite.

Explicit hold to avoid accidental merges.
/hold

Thank you @divya-mohan0209, I will follow the suggested steps ✅

/close


Support for openHAB 2.2

This PR adds support for openHAB 2.2 by replacing the WebSocket listener with repeated polling over the REST API.
It also fixes the parsing of the sitemap to work with new responses.
Note:
philklei basically did all the work. I (for now) just removed the Rollershutter changes from his fork and changes the status code check to check for 200.

Thank you for your pull request but i have just released new repository to support openHAB2 coded in Typescript covered by unit test and with the new plugin structure. For now it supports only switch but in the next days i add more types. This is the link.

That looks great. Thanks a lot for your work. I'll be sure to check it out as soon as more accessories are supported!


Remove the network info from Swap screen

Instead, use the small icons in the corner of each coin.

https://zpl.io/qyZk58N

Let's not do this now.
It might also be incorrect because the user would have no way to change to another chain (it can be correct because we could decide to make the user go back and navigate and then tap on a token from another chain for such usage). But not now.

Just additional info regarding swap networks -
The LiFi API supports these networks, which are not available in AlphaWallet:

OKXChain Mainnet (66)
Harmony Mainnet Shard 0<PHONE_NUMBER>)
Moonriver (1285)
Moonbeam (1284)
Celo Mainnet (42220)
Fuse Mainnet (122)

Since we are limited to same-chain swaps for now, should we remove them from the list of networks, or just leave them be?

remove them from the list of networks

Do you mean to not show them as destination options? Definitely remove them for now :)


Add Finnish translations

Proposing Finnish translations. I continued the translations mentioned in issue #223.
This commit has issues, not all the translations are very fluent. Consider this version for review, but there's definitely room for improvement. I also post this here so that it gets visibility and perhaps some people can help in improving this.
This is the best I can do with just Transifex, but some of these aren't very good Finnish. For example the modifier left is translated as vasemmall(e/a). That's because the modifier is used in different contexts and a different form of the word would be needed. Roughly: "to the left" is "vasemmalle", "on the left" is "vasemmalla".
This and other issues can maybe be solved with the grammar system, but I haven't yet studied how that works.

Currently grammar works with way_name and rotary_name values only but why not to extend it somehow to process whole phrase or a new keyword? Anyway this could be done in a new pull request but this one should be finished with ChangeLog update :wink:

I would say either way is good. The current Finnish in this PR isn't fluent at all places but it's understandable. So I guess it's better than nothing.
Maybe it boils down to the quality ambitions of this project and the release schedule. If the quality ambition is very high and a release is approaching, then I wouldn't include this PR yet. If the approach is more that any value added is good (and can be improved later) or no release is right behind the corner, then I would say that this can go now as it is and once #240 is in, then Finnish (and other) strings can be improved.
So I think I'm throwing the ball right back at ya :smile:


How to solve CocoaPods could not find compatible versions for pod "rnmapbox-maps":

[!] CocoaPods could not find compatible versions for pod "rnmapbox-maps":
In Podfile:
rnmapbox-maps (from ../node_modules/@rnmapbox/maps)
Specs satisfying the rnmapbox-maps (from ../node_modules/@rnmapbox/maps) dependency were found, but they required a higher minimum deployment target.

"@rnmapbox/maps" -> "^10.0.0-beta.28",
Podfile
platform :ios, ‘10.0’
$RNMapboxMapsImpl = ‘mapbox’
pre_install do |installer|
$RNMapboxMaps.pre_install(installer)
end
post_install do |installer|
$RNMapboxMaps.post_install(installer)
end

Pls use beta 49 . 50-52 published without podfile


User preferences

Add permanent preferences with options to:

Disable automatic results on page load (enhancing privacy)
Set default number of results in the sidebar

Has been solved with commit 29e37cb


InvalidParameterValueException: Uploaded file must be a non-empty zip

What happened?
From @komalali
Hi! I have noticed a recurring error as I've worked on drift detection.
Context:

I have a stack that uses the aws-serverless template: stack
It is deployed in the dev-sandbox account, so every night a number of these resources are cleaned up
The following day, when I run drift detection and remediation, the first remediation fails. link

aws:lambda:Function (fn):
    error: 1 error occurred:
    	* creating Lambda Function (fn-a91d018): operation error Lambda: CreateFunction, https response error StatusCode: 400, RequestID: b2589290-ab14-4526-a65c-3b90fabeb5e2, InvalidParameterValueException: Uploaded file must be a non-empty zip

The following drift run/remediation succeeds.
Example
The source is very simple:
https://github.com/pulumi/deploy-demos/blob/main/pulumi-programs/drift-test/index.ts
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as apigateway from "@pulumi/aws-apigateway";

// A Lambda function to invoke
const fn = new aws.lambda.CallbackFunction("fn", {
    callback: async (ev, ctx) => {
        return {
            statusCode: 200,
            body: new Date().toISOString(),
        };
    }
})

// A REST API to route requests to HTML content and the Lambda function
const api = new apigateway.RestAPI("api", {
    routes: [
        { path: "/", localPath: "www"},
        { path: "/date", method: "GET", eventHandler: fn },
    ]
});

// The URL at which the REST API will be served.
export const url = api.url;

Output of pulumi about
$ pulumi about
 Logging in using access token from PULUMI_ACCESS_TOKEN
 CLI
 Version      3.109.0
 Go Version   go1.22.0
 Go Compiler  gc

 Plugins
 NAME            VERSION
 aws             6.25.1
 aws-apigateway  2.4.0
 awsx            2.5.0
 docker          4.5.1
 docker          3.6.1
 nodejs          unknown

 Host
 OS       debian
 Version  11.9
 Arch     x86_64

 This project is written in nodejs: executable='/usr/bin/node' version='v18.17.1'

 Backend
 Name           pulumi.com
 URL            https://app.pulumi.com/komal-pulumi-corp
 User           komal-pulumi-corp
 Organizations  komal-pulumi-corp, service-provider-test-org, komal-testing-123, pulumi-test, pulumi
 Token type     personal

 Dependencies:
 NAME                    VERSION
 @pulumi/aws-apigateway  2.4.0
 @pulumi/aws             6.25.1
 @pulumi/awsx            2.5.0
 @pulumi/pulumi          3.109.0
 @types/node             18.19.24
 typescript              4.9.5

 Pulumi locates its logs in /tmp by default
 warning: Failed to get information about the current stack: No current stack

Additional context
We tried a few times to reproduce locally but failed to do so, while it reproduces pretty consistently with deployments. This seems quite surprising. There's a bit going about drift detection but when all is said and done deployments is simply performing this operation over a state that tracks a lambda and a cloud that has the lambda removed:
pulumi update --refresh --skip-preview --yes

Pulumi refreshes and drops the lambda from state, then decides to Create the lambda, which should succeed but does not.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

From @komalali : okay I have some new information. I ran 2 separate deployments, pulumi refresh and pulumi update instead of 1 remediate-drift which does the pulumi update --refresh. When I run them as 2 separate deployments I don't get the error.

using the automation API for go as well:
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0 stdout: Updating (dev.ap-northeast-1.firehose):
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0   pulumi:pulumi:Stack: (same)
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0     [urn=urn:pulumi:dev.ap-northeast-1.firehose::<redacted>::pulumi:pulumi:Stack::<redacted>-dev.ap-northeast-1.firehose]
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0     > pulumi:pulumi:StackReference: (read)
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         [id=dev.us-west-2.global]
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         [urn=urn:pulumi:dev.ap-northeast-1.firehose::<redacted>::pulumi:pulumi:StackReference::global]
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         name: "dev.us-west-2.global"
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0     ~ aws:lambda/function:Function: (update)
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         [id=dev-<redacted>-processor-365fe5e]
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         [urn=urn:pulumi:dev.ap-northeast-1.firehose::<redacted>::aws:lambda/function:Function::dev-<redacted>-processor]
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         [provider=urn:pulumi:dev.ap-northeast-1.firehose::<redacted>::pulumi:providers:aws::firehose-ap-northeast-1::ea66edb7-3c1c-4604-b1dc-42030393052b]
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0       - code: archive(assets:3e11bfc) {
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0         }
<redacted>-release-scheduler cnp1sl6p1qbs70d46850/main/479e594bcbaf4d3b9f3249417b21f8a0       + code: archive(file:10e3b68) { /app/downloads/lc-firehose-lambda.zip }

* updating urn:pulumi:dev.ap-northeast-1.firehose::<redacted>::aws:lambda/function:Function::<redacted>-processor: 1 error occurred:
* updating Lambda Function (dev-<redacted>-365fe5e) code: operation error Lambda: UpdateFunctionCode, https response error StatusCode: 400, RequestID: 6f2b719d-8766-4e14-b8d5-d2367a98dfa2, InvalidParameterValueException: Uploaded file must be a non-empty zip

seems to work intermittently
pulumi: 3.108.0
aws: 6.24.0

I opened this a couple weeks back and it appeared resolved but is rearing its ugly head again
https://github.com/pulumi/pulumi-aws/issues/3478

I am also struggling with this error happening intermittently. I have not been able to replicate it yet.

We are also seeing this issue on creating and updating Lambda function code.
As a test, I created an aws.s3.BucketObjectv2 component with the same asset. And the uploaded file is indeed empty (22 bytes).
The issue seems to go away if I restart my machine. But does eventually come back.

The zip files that get uploaded are stored in ${tmp}/pulumi-asset-${hash}, where the hash is based on the file contents of what should be in the zip, but sometimes these files end up being empty (22B file, running unzip -l ${file} outputs zipfile is empty.

The AssetArchive to upload gets stored as zip file in ${TEMP}/pulumi-asset-${HASH}, with ${HASH} based on the contents of the archive. When we run pulumi update --refresh and the zip files are not present yet, they get created in ${TEMP} but are empty. Presumably the name is derived from the existing state. If we then run a pulumi update that needs to do changes, it will fail with the empty zip error. Since deployments run with an empty temp folder, it reproduces all the time there, whereas locally you might have the correctly formed zip from the previous update.
triage-empty-zip main% ls -ahl /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
zsh: no matches found: /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
triage-empty-zip main% pulumi update --refresh --stack dev
Previewing update (dev)

View in Browser (Ctrl+O): https://app.pulumi.com/v-julien-pulumi-corp/triage-pulumi-empty-zip/dev/previews/5600a2f8-7845-477b-9348-be5846e9f152

     Type                    Name                         Plan       Info
     pulumi:pulumi:Stack     triage-pulumi-empty-zip-dev
     ├─ aws:iam:Role         iam_for_lambda
 ~   └─ aws:lambda:Function  fn                           update     [diff: ~code]

Resources:
    ~ 1 to update
    2 unchanged

Do you want to perform this update? no
confirmation declined, not proceeding with the update
triage-empty-zip main% ls -ahl /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
-rw-------  1 julien  staff    22B Mar 18 21:19 /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-4271ac265fd6fbf363faa1a179cec1a6174963b9bc656f4fb989f3b502ecaf2a
-rw-------  1 julien  staff    22B Mar 18 21:19 /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-92b616411729aeb8d8bbb0c1d5e5c9b305ebffa1e0563a2286eefc658220c23e

Those 22B files are empty zip files.
If we run without --refresh, the zip gets created correctly
triage-empty-zip main% rm /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
triage-empty-zip main% ls -ahl /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
zsh: no matches found: /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
triage-empty-zip main% pulumi update --stack dev
Previewing update (dev)

View in Browser (Ctrl+O): https://app.pulumi.com/v-julien-pulumi-corp/triage-pulumi-empty-zip/dev/previews/0c1d95bc-27f1-4d90-907b-add516e73a52

     Type                    Name                         Plan       Info
     pulumi:pulumi:Stack     triage-pulumi-empty-zip-dev
 ~   └─ aws:lambda:Function  fn                           update     [diff: ~code]

Resources:
    ~ 1 to update
    2 unchanged

Do you want to perform this update? no
confirmation declined, not proceeding with the update
triage-empty-zip main% ls -ahl /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-*
-rw-------  1 julien  staff   201B Mar 18 21:19 /var/folders/lv/czktcqg963q26_khyypypmkm0000gn/T/pulumi-asset-92b616411729aeb8d8bbb0c1d5e5c9b305ebffa1e0563a2286eefc658220c23e

Note the fileize of 201B this time around.

Yes!
Can confirm refresh was what caused it for us.
Can also confirm running refresh reliably reproduces the issue.

Local reproduction:

Deploy a lambda (note that the newly created ${TEMP}/pulumi-asset-${HASH} file is larger than 22B)
Delete ${TEMP}/pulumi-asset-${HASH}
Edit the code of the lambda
pulumi up --refresh --stack dev (this will re-create the file for the previous hash, but as an empty zip file)
Revert the code edit (code needs to be exactly as in step 1, so the hash matches)
pulumi up --stack dev

The last step will attempt to upload the empty zip file.

I haven't been able to repro on the original program from @komalali as it does not create ${TMPDIR}/pulumi-asset-${HASH} files but instead stores literal JS code in the Pulumi state file. So there might be several issues here.
After some experimentation I was able to reproduce based on this program:
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as apigateway from "@pulumi/aws-apigateway";

const cfg = new pulumi.Config();

const archive = cfg.require("archive");

const assumeRole = aws.iam.getPolicyDocument({
    statements: [{
        effect: "Allow",
        principals: [{
            type: "Service",
            identifiers: ["lambda.amazonaws.com"],
        }],
        actions: ["sts:AssumeRole"],
    }],
});

const iamForLambda = new aws.iam.Role("iam_for_lambda", {
    name: "iam_for_lambda",
    assumeRolePolicy: assumeRole.then(assumeRole => assumeRole.json),
});

const fn = new aws.lambda.Function("fn", {
    role: iamForLambda.arn,
    code: new pulumi.asset.FileArchive(archive),
    handler: "index.test",
    runtime: "nodejs18.x",
})

export const lambdaARN = fn.arn;

Calling refresh is not necessary for the repro. It looks like pulumi up clobbers the temp files for assets referenced from state but not user program.
#!/usr/bin/env bash

set -euo pipefail

export AWS_PROFILE=devsandbox

# Clean slate.
pulumi destroy --yes
rm -rf $TMPDIR/*pulumi*asset*

# Provision a1.zip
pulumi config set archive ./a1/a1.zip
pulumi up --skip-preview --yes
pulumi stack export --file a1.json
md5 $TMPDIR/*pulumi*asset*

# Provision a2.zip
pulumi config set archive ./a2/a2.zip
pulumi up --skip-preview --yes
md5 $TMPDIR/*pulumi*asset*

# Create a discontinuity between cloud and local state.
pulumi stack import --file a1.json

# Lose the temp asset files.
rm $TMPDIR/*pulumi*asset*

# Refresh is not necessary.
# pulumi refresh --yes

# See if we can update again.
pulumi up --yes --skip-preview

# This clobbers the asset for a1.zip.
md5 $TMPDIR/*pulumi*asset*

pulumi config set archive ./a1/a1.zip
pulumi up --yes --skip-preview # FAILS HERE

| 5.43.0 | no repro   |
|  6.2.0 | no repro   |
|  6.5.0 | no repro   |
|  6.6.0 | no repro   |
|  6.6.1 | reproduces |
|  6.7.0 | reproduces |
| 6.10.0 | reproduces |

I have confirmed that https://github.com/pulumi/pulumi/pull/14007 caused the change in behavior by interacting in an unexpected way with the asset-handling code in the bridge. Building 6.6.1 of the provider against v3.90.1 of pulumi/pkg with 14007 reverted yields a pulumi-resource-aws provider where the problem no longer reproduces.

I have passed on https://github.com/pulumi/pulumi/issues/15729 to the core team, the evidence is that it's likely once we have that fixed we can remediate the issue here. Thanks for your patience everyone.

Still awaiting a pulumi release (v3.111.1 does not contain the fix yet).

Looks like it was included in the latest release


why not add this to the official extension index?

I only have that question :)

I cant. If someone with permission adds it though that would be great.

@arenatemp You can add at AUTOMATIC1111/stable-diffusion-webui-extensions.

done


Add cookie for GOVUK-ABTest-Benchmarking

Background
We are going to be running a new A/B test for the GOV.UK benchmarking
task. In this A/B test, which should last less than 1 week, we will be
adding a tracking library so we understand how users interact with the
new navigation pages we have exposed for Education content.
Changes
In this commit we add rules to set the ABTest-Benchmarking cookie based
on a few things.
On vcl_recv:

If the user visits GOV.UK with a parameter like
?ABTest-Benchmarking=B, we will use that value to set the header
accordingly, so the application knows what variant to render (and set
the Vary header appropriately);
If the user already has a cookie set, we use that value in the
header, so the application knows what variant to render (and set
the Vary header appropriately);
Finally, for anyone else, we always put them in the A bucket,
because we only want to track users in the benchmarking test and no
one else.

On vcl_deliver, on the first visit, we set the cookie and make sure
it expires after 7 days.
Trello: https://trello.com/c/NJ6O76BR/281-heatmap-tracking

Thanks @suzannehamilton . I've sent an email so the cookies page gets updated. I will add a trello card so we chat about naming of things related to A/B tests.


Roboports

Your roboports to not send out bots for construction until the orange logistical squares touch.

it is working fine for me


camera make-check fails : Problem with XML-RPC requests ?

I have downloaded the library source code, and am trying to get the camera module to work. C-make and make run fine, but when make check gives the following errors :
$ make check
[  5%] Built target gtest
[ 60%] Built target o3d3xx_camera
[ 60%] Built target o3d3xx_camera_shared
[ 65%] Built target gtest_main
[100%] Built target o3d3xx-camera-tests
[==========] Running 43 tests from 6 test cases.
[----------] Global test environment set-up.
[----------] 17 tests from Camera_Tests
[ RUN      ] Camera_Tests.Ctor
[       OK ] Camera_Tests.Ctor (0 ms)
[ RUN      ] Camera_Tests.GetXMLRPCURLPrefix
[       OK ] Camera_Tests.GetXMLRPCURLPrefix (0 ms)
[ RUN      ] Camera_Tests.GetAllParameters
[       OK ] Camera_Tests.GetAllParameters (380 ms)
[ RUN      ] Camera_Tests.GetParameter
[       OK ] Camera_Tests.GetParameter (1326 ms)
[ RUN      ] Camera_Tests.GetSWVersion
[       OK ] Camera_Tests.GetSWVersion (36 ms)
[ RUN      ] Camera_Tests.GetApplicationList
[       OK ] Camera_Tests.GetApplicationList (25 ms)
[ RUN      ] Camera_Tests.RequestSession
[       OK ] Camera_Tests.RequestSession (60 ms)
[ RUN      ] Camera_Tests.CancelSession
[       OK ] Camera_Tests.CancelSession (74 ms)
[ RUN      ] Camera_Tests.Heartbeat
[       OK ] Camera_Tests.Heartbeat (130 ms)
[ RUN      ] Camera_Tests.SetOperatingMode
[       OK ] Camera_Tests.SetOperatingMode (138 ms)
**[ RUN      ] Camera_Tests.GetDeviceConfig
/home/localuser/ros_ifm/libo3d3xx/modules/camera/test/o3d3xx-camera-tests.cpp:182: Failure
Value of: 32
Expected: params.size()
Which is: 30
unknown file: Failure
C++ exception with description "_Map_base::at" thrown in the test body.
[  FAILED  ] Camera_Tests.GetDeviceConfig (703 ms)**
[ RUN      ] Camera_Tests.ActivateDisablePassword
[       OK ] Camera_Tests.ActivateDisablePassword (667 ms)
[ RUN      ] Camera_Tests.SetDeviceConfig
[       OK ] Camera_Tests.SetDeviceConfig (2738 ms)
[ RUN      ] Camera_Tests.DeviceConfig_JSON
[       OK ] Camera_Tests.DeviceConfig_JSON (104 ms)
[ RUN      ] Camera_Tests.GetNetParameters
[       OK ] Camera_Tests.GetNetParameters (577 ms)
[ RUN      ] Camera_Tests.NetConfig
[       OK ] Camera_Tests.NetConfig (577 ms)
[ RUN      ] Camera_Tests.NetConfig_JSON
[       OK ] Camera_Tests.NetConfig_JSON (583 ms)
[----------] 17 tests from Camera_Tests (8121 ms total)

[----------] 4 tests from SpatialFilterTest
[ RUN      ] SpatialFilterTest.SpatialFilterConfig_General
[       OK ] SpatialFilterTest.SpatialFilterConfig_General (702 ms)
[ RUN      ] SpatialFilterTest.GetSpatialFilterParameters
[       OK ] SpatialFilterTest.GetSpatialFilterParameters (2160 ms)
[ RUN      ] SpatialFilterTest.GetSpatialFilterParameterLimits
[       OK ] SpatialFilterTest.GetSpatialFilterParameterLimits (1966 ms)
[ RUN      ] SpatialFilterTest.SpatialFilterConfig_JSON
[       OK ] SpatialFilterTest.SpatialFilterConfig_JSON (1837 ms)
[----------] 4 tests from SpatialFilterTest (6665 ms total)

[----------] 2 tests from General_Tests
[ RUN      ] General_Tests.Exceptions
[       OK ] General_Tests.Exceptions (0 ms)
[ RUN      ] General_Tests.Version
[       OK ] General_Tests.Version (0 ms)
[----------] 2 tests from General_Tests (0 ms total)

[----------] 1 test from ImportExport_Tests
[ RUN      ] ImportExport_Tests.ImportExportApp
[       OK ] ImportExport_Tests.ImportExportApp (1357 ms)
[----------] 1 test from ImportExport_Tests (1357 ms total)

[----------] 4 tests from TemporalFilterTest
[ RUN      ] TemporalFilterTest.TemporalFilterConfig_General
[       OK ] TemporalFilterTest.TemporalFilterConfig_General (695 ms)
[ RUN      ] TemporalFilterTest.GetTemporalFilterParameters
[       OK ] TemporalFilterTest.GetTemporalFilterParameters (1977 ms)
[ RUN      ] TemporalFilterTest.GetTemporalFilterParameterLimits
[       OK ] TemporalFilterTest.GetTemporalFilterParameterLimits (2032 ms)
[ RUN      ] TemporalFilterTest.TemporalFilterConfig_JSON
[       OK ] TemporalFilterTest.TemporalFilterConfig_JSON (1950 ms)
[----------] 4 tests from TemporalFilterTest (6654 ms total)

[----------] 15 tests from AppImagerTest
[ RUN      ] AppImagerTest.CopyDeleteApplication
[       OK ] AppImagerTest.CopyDeleteApplication (1323 ms)
[ RUN      ] AppImagerTest.CreateApplication
[       OK ] AppImagerTest.CreateApplication (936 ms)
[ RUN      ] AppImagerTest.ChangeAppNameAndDescription
[       OK ] AppImagerTest.ChangeAppNameAndDescription (986 ms)
[ RUN      ] AppImagerTest.EditApplication
[       OK ] AppImagerTest.EditApplication (949 ms)
[ RUN      ] AppImagerTest.GetAppParameters
[       OK ] AppImagerTest.GetAppParameters (1520 ms)
[ RUN      ] AppImagerTest.AppConfig
[       OK ] AppImagerTest.AppConfig (1777 ms)
[ RUN      ] AppImagerTest.AppConfig_JSON
[       OK ] AppImagerTest.AppConfig_JSON (1713 ms)
[ RUN      ] AppImagerTest.GetAvailableImagerTypes
[       OK ] AppImagerTest.GetAvailableImagerTypes (1512 ms)
[ RUN      ] AppImagerTest.ChangeImagerType
[       OK ] AppImagerTest.ChangeImagerType (2811 ms)
**[ RUN      ] AppImagerTest.GetImagerParameters
/home/localuser/ros_ifm/libo3d3xx/modules/camera/test/o3d3xx-app-imager-tests.cpp:265: Failure
Expected: params.at("EnableFastFrequency") doesn't throw an exception.
  Actual: it throws.
[  FAILED  ] AppImagerTest.GetImagerParameters (1928 ms)**
[ RUN      ] AppImagerTest.GetImagerParameterLimits
[       OK ] AppImagerTest.GetImagerParameterLimits (2830 ms)
**[ RUN      ] AppImagerTest.ImagerConfig
/home/localuser/ros_ifm/libo3d3xx/modules/camera/test/o3d3xx-app-imager-tests.cpp:419: Failure
Expected: cam_->SetImagerConfig(im.get()) doesn't throw an exception.
  Actual: it throws.
[  FAILED  ] AppImagerTest.ImagerConfig (1911 ms)**
[ RUN      ] AppImagerTest.ImagerConfigValueOutOfRange
[       OK ] AppImagerTest.ImagerConfigValueOutOfRange (3448 ms)
[ RUN      ] AppImagerTest.ImagerConfig_JSON
[       OK ] AppImagerTest.ImagerConfig_JSON (1622 ms)
[ RUN      ] AppImagerTest.Exposure
[       OK ] AppImagerTest.Exposure (3885 ms)
[----------] 15 tests from AppImagerTest (29153 ms total)

[----------] Global test environment tear-down
[==========] 43 tests from 6 test cases ran. (51950 ms total)
[  PASSED  ] 40 tests.
[  FAILED  ] 3 tests, listed below:
[  FAILED  ] Camera_Tests.GetDeviceConfig
[  FAILED  ] AppImagerTest.GetImagerParameters
[  FAILED  ] AppImagerTest.ImagerConfig

 3 FAILED TESTS
make[3]: *** [test/CMakeFiles/check] Erreur 1
make[2]: *** [test/CMakeFiles/check.dir/all] Erreur 2
make[1]: *** [test/CMakeFiles/check.dir/rule] Erreur 2
make: *** [check] Erreur 2

After digging into the code, I guess that the following function calls (in camera.cpp) fail :
cam_-> GetImagerParameters()
cam_-> SetImagerParameters()
But then it goes down to XML-RPC, that I know nothing about.
Any ideas on what could have gone wrong ? I haven't even edited anything yet...
My setup : Ubuntu 14.04, camera O3D303. The camera runs fine with ifmVisionAssistantV1.2.7 (with wine).

This is almost certainly due to a mismatch in a supported version of libo3d3xx and the on-camera firmware. Please see the main README and reference the software compatibility matrix. As of today, I'd suggest using the latest version of libo3d3xx (0.4.1) and firmware version 1.4.1639.
To update your camera, can use o3d3xx-reboot -r. Then hit the camera's internal http server (by default: http://<IP_ADDRESS>:8080. From there you will be greeting with a web interface where you can upload the firmware file. You can find 1.4.1639 in the firmware directory of this source distribution.

First, thanks a lot for your fast reply !
I downloaded the library with git clone https://github.com/lovepark/libo3d3xx.git, so it should be the last version.
3d3xx-dump gives "IFM_Software": "1.1.288", so that may be the issue indeed, I'll try updating the firmware.

I had to git clone again (I guess my version was outdated already) but now it worked !
Thanks !

Stable versions are available here. Running from the HEAD will always be considered living on the edge. At some point, maybe once we hit 1.0, we can start releasing binaries.

Hmm.. Ok, I followed these instructions but you're right, it's safer to keep a stable version.
It would be nice to have test binaries equivalent to ifmVision Assistant...

Since the releases are just annotated tags, and you have already cloned the repo, you have the stable tag on your machine already. You can checkout the particular tag of interest and build from there. I guess I need to update the docs for o3d3xx-ros to reflect this. Thanks for pointing it out.


Fake news detection web application

Description
A web application built using flask to check the reality of a news article based on US 2016 presidential election
Type of change
Choosing one or more options from the following as per the nature of your Pull request.

NOTE: These boxes can be checked using [X]

[ ] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)

[x] Documentation Update

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[x] I have added a working sample/screenshot of the script.

As requested all the requirements are fulfilled along with the removal of errors.Please give it a go.I hope you like it

Hello my request hasnt been merged yet.May i know if any issue is pertaining

Are you working on it? @asiskumarroy

Okay will do the following
On Wed, 7 Oct 2020, 00:45 Tushar Nankani<EMAIL_ADDRESS>wrote:

Are you working on it? @asiskumarroy https://github.com/asiskumarroy
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Python-World/Python_and_the_Web/pull/234#issuecomment-704497481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTZ7U6YR2HMKPUOFGZATJDSJNUEPANCNFSM4SCPS5OA
.

As per your request the changes has been made.Please have a look
On Wed, 7 Oct 2020 at 05:06, Asis Kumar Roy<EMAIL_ADDRESS>wrote:

Okay will do the following
On Wed, 7 Oct 2020, 00:45 Tushar Nankani<EMAIL_ADDRESS>wrote:

Are you working on it? @asiskumarroy https://github.com/asiskumarroy
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Python-World/Python_and_the_Web/pull/234#issuecomment-704497481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTZ7U6YR2HMKPUOFGZATJDSJNUEPANCNFSM4SCPS5OA
.

The changes has been made.Please have a look.

Removing the pipeline will lead to gross errors and it will be quite difficult to mention it in the readme and the reader might not be able to understand how to generate it.I suggest its better be there

Please do let me know if I can be of any help further.

Ok will do
On Wed, 14 Oct 2020, 20:10 Ravishankar Chavare<EMAIL_ADDRESS>wrote:

@chavarera requested changes on this pull request.
In Scripts/Miscellaneous/Fake_news_web/Requirements.txt
https://github.com/Python-World/Python_and_the_Web/pull/234#discussion_r504733519
:

@@ -0,0 +1,4 @@
+language: python 3.7

add used module list in requirements.txt with help of pip freeze
pip freeze list>requirements.txt
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Python-World/Python_and_the_Web/pull/234#pullrequestreview-508420772,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTZ7U55TYBPJHTFZODRBH3SKWZ7VANCNFSM4SCPS5OA
.

The requirements.txt has been updated as per the request.
It has been updated using the command pip freeze list>requirements.txt which adds all the module list.
Do let me know about further changes
Thanks in advance.

@allcontributors please add @asiskumarroy for code


update to bag_migrate branch of isaac_msgs

This PR should be held until the following ones are merged:

https://github.com/nasa/isaac_msgs/pull/2
https://github.com/nasa/astrobee/pull/494

I'm frankly not sure when the ISAAC bag migration CI test will start to pass on GitHub. (Like it might need the astrobee PR to be merged into master first?)

I noticed the diff information was stale and changed the base branch to 'master' then back to 'develop' to try and get the diff to be update, as a workaround for https://github.com/isaacs/github/issues/750 . Didn't seem to work.

Looks like a new PR is needed for this now that the other PRs have been merged.


Pod antiaffinity by default

Cloudnative-pg does apply podAntiAffinity rules by default to try to spread different instances across the cluster. I believe it would be a nice default for the operator.

@rubasace hi! did not get, why are you mentioning cnpg?


(WIP) Add support for mainnet.

Accompanying PR to the https://github.com/o1-labs/zkapp-cli/pull/564

some initial feedback:

I don't like making the network id (yet another) global variable. It should just be a property of the Mina instance
It was a deliberate choice to not have different network ids in signFields() and the in-circuit signature verification. The concept of a network id is domain-specific to transaction signing and has no place in a general-purpose signing API. So let's revert using it there.

some initial feedback:

Thank you!

I don't like making the network id (yet another) global variable. It should just be a property of the Mina instance

I thought about it as well but then the networkId is required in different places and to not evaluate complete mina.ts while importing and limiting access to whatever getters I thought to make it with global one. Will think more on it then.

It was a deliberate choice to not have different network ids in signFields() and the in-circuit signature verification. The concept of a network id is domain-specific to transaction signing and has no place in a general-purpose signing API. So let's revert using it there.

By reverting it you mean setting it back to 'testnet' value or set it to 'mainnet' to deliver these changes after HF?

@mitschabaude can you also please help me in understanding unit tests failures.
The pipeline for 88025a4 failed with invalid signature, then next commit dfbea22 failed by another issue, this time mina-signer, not o1js, but there were no changes that could have fix initial failure.
Then I committed fix 8a6e3c3 and all is green.
Do you have any idea why rev:88025a4 could have fail that time?

Do you have any idea why rev:88025a4 could have fail that time?

I think it was an edge case test failure. I have copied the failing test case and will investigate it

By reverting it you mean setting it back to 'testnet' value or set it to 'mainnet' to deliver these changes after HF?

Set it back! "testnet" / "mainnet" is meaningless for these signatures, because they have nothing to do with networks


Looking for some direction for new PRs...

Hey Guys,
I'm looking to see what you might want help with. I think I could flesh out some examples, look into making some of your components stateless, maybe connect the examples to redux to show a prototype for the more complex "dumb" components. I'd also like to add certain syntactic/structural changes according to the linters I've been used to but I don't want to make any PRs before getting a blessing. My team is currently using a lot of this so I'd like to flesh some things out as we do.

In general we are open to any kind of contributions! Many of us are on vacation right now so the feedback loop may me a bit slow though.

Hi @ebgranger, our team at @NYCPlanning is doing the same. @andycochran is a Foundation contributor on our team as well. Which component are you looking at starting with? We'd like to get ResponsiveNavigation better documented and address things like #23.

We'd like to make this library stateless because there are so many things to consider case-by-case when writing stateful components. I have been planning on removing the ResponsiveNavigation completely.

@crisu83 why remove it? I'm modeling my thinking about this around React-SemanticUI integration, where everything is a component. ResponsiveNavigation requires JS, it'd be nice to have a component for it.

@allthesignals The reason to remove it would be simplicity and to make maintenance easier for us. I suspect that the needs for such components cannot be generalized enough to be a part of this library.


folds.mat  is for what?

I want to understand the folds.mat .

That's for cross-validation:
https://github.com/yuanming-hu/fc4/blob/master/datasets.py#L128


Fix clippy warnings as of Rust 1.81

TEST=cargo test
TEST=cargo clippy

GitHub UI is confusing, sorry for pinging you, Dennis!


New feature: Unioning source data

Are you a current Fivetran customer?
Yes, Pawel Ngei, Pattern Brands
What change(s) does this PR introduce?

Introduce the ability to union data from multiple schemas databases, as per https://github.com/fivetran/dbt_klaviyo/pull/11 (for Klaviyo)
Based on the Facebook Ads Source plugin: https://github.com/fivetran/dbt_facebook_ads_source/pull/18

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[x] No  (please provide explanation how the change is non breaking below.)

Is this PR in response to a previously created Issue

[ ] Yes, Issue [link issue number here]
[x] No

How did you test the PR changes?

[ ] CircleCi
[x] Other (please provide additional testing details below)

Pattern Brands data, two datasets from Facebook Ads connector with Snowflake.
IMPORTANT: Our data didn't generate anything in the stg_facebook_ads__app_link model, you might want to test it on another dataset.
Select which warehouse(s) were used to test the PR

[ ] BigQuery
[ ] Redshift
[x] Snowflake
[ ] Postgres
[ ] Databricks
[ ] Other (provide details below)

IMPORTANT: This one really needs tests on all the other warehouses / SQL flavors. I was able to test the changes on Snowflake, but everything else I just guessed.
:building_construction:
Feedback
Will need to remember to add a Readme note about the basic_ad table to the last plugin it's not advertised enough. I added it to the current readme.
Needs to be tested on other Warehouses / SQL flavors, new auto-generated docs and the packages.yml change once the _source plugin is published. Added a basic Changelog, you might want to build on it.

Thanks again so much for putting the effort into this PR @pawelngei! There are a few minor changes (tests and formatting updates) that I am going to apply before we include this in a live version of the package. Therefore I am changing the base branch to be a working branch that I will apply these updates to.
Thanks so much!


ssh keys

My organization has disabled generating ssh keys , hence the crc fails now. Please let me know how to manually handle this by copying the ssh keys to the crc folder.
General information

OS:   macOS
Hypervisor: hyperkit
Did you run crc setup before starting it (Yes/No)?- yes

CRC version
CodeReady Containers version: 1.19.0+94b0362
Steps to reproduce

crc start

Actual
INFO Creating CodeReady Containers VM for OpenShift 4.6.3...
Failed to connect to the CRC VM with SSH -- host might be unreachable: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  (x295)

@praveenkumar @guillaumerose Do we generate the certs using the hosts ssh tools?

@praveenkumar @guillaumerose Do we generate the certs using the hosts ssh tools?

Please provide a full startup output log. We need to understand what happened in previous steps.

Please provide a full startup output log. We need to understand what happened in previous steps.

We use go function to generate the ssh key. I believe the error is due to something else.

We use go function to generate the ssh key. I believe the error is due to something else.

We use go function to generate the ssh key

wanted to confirm this as I also believed so, as we would have no
access to those tools on Windows anyway.

I believe the error is due to something else.

Full output log required.
On Wed, Jan 20, 2021 at 4:22 PM Guillaume Rose<EMAIL_ADDRESS>wrote:

We use go function to generate the ssh key. I believe the error is due to something else.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop!
[ Better Understanding Involves Learning and Doing ]

We use go function to generate the ssh key

wanted to confirm this as I also believed so, as we would have no
access to those tools on Windows anyway.

I believe the error is due to something else.

Full output log required.
On Wed, Jan 20, 2021 at 4:22 PM Guillaume Rose<EMAIL_ADDRESS>wrote:

We use go function to generate the ssh key. I believe the error is due to something else.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop!
[ Better Understanding Involves Learning and Doing ]

Might be generation of RSA keys which is disabled, maybe 1.21 which uses ECDSA ssh keys would be better. If we really can't generate new keys, we could keep using the 'default' key which is part of the bundle.

Might be generation of RSA keys which is disabled, maybe 1.21 which uses ECDSA ssh keys would be better. If we really can't generate new keys, we could keep using the 'default' key which is part of the bundle.

Yes, thats correct . I was able to generate ssh keys until the recent org policy change. Please let me know how i can keep the default ssh key as part of the bundle. My understanding is that the ssh keys will be generated in the folder @ /Users/af71194/.crc/machines/crc when we run crc start. I tried to copy my ssh key generated from the org security tool named venafi , but it removes those ssh keys once the crc starts.

Yes, thats correct . I was able to generate ssh keys until the recent org policy change. Please let me know how i can keep the default ssh key as part of the bundle. My understanding is that the ssh keys will be generated in the folder @ /Users/af71194/.crc/machines/crc when we run crc start. I tried to copy my ssh key generated from the org security tool named venafi , but it removes those ssh keys once the crc starts.

We still need the full debug log after a crc delete; crc start --log-level debug to get a better understanding of what is happening.

We still need the full debug log after a crc delete; crc start --log-level debug to get a better understanding of what is happening.

1.21 was just released if you want to give it a try.

1.21 was just released if you want to give it a try.

af71194@LC02CHB58MD6R ~ % crc version
CodeReady Containers version: 1.19.0+94b0362
OpenShift version: 4.6.3 (embedded in executable)
af71194@LC02CHB58MD6R ~ % crc delete; crc start --log-level debug
Do you want to delete the OpenShift cluster? [y/N]: y
Deleted the OpenShift cluster
DEBU CodeReady Containers version: 1.19.0+94b0362
DEBU OpenShift version: 4.6.3 (embedded in executable)
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
WARN A new version (1.21.0) has been published on https://cloud.redhat.com/openshift/install/crc/installer-provisioned
INFO Checking if podman remote executable is cached
DEBU Currently podman remote is not supported
INFO Checking if goodhosts executable is cached
DEBU goodhost executable already cached
INFO Checking minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
INFO Checking if running as non-root
INFO Checking if HyperKit is installed
DEBU Running '/Users/af71194/.crc/bin/hyperkit -v'
DEBU Found hyperkit version v0.20200224-44-gb54460
INFO Checking if crc-driver-hyperkit is installed
DEBU Checking if crc-driver-hyperkit is installed
DEBU Running '/Users/af71194/.crc/bin/crc-driver-hyperkit version'
DEBU Found crc-driver-hyperkit version 0.12.10
INFO Checking file permissions for /etc/hosts
DEBU Checking if /etc/hosts ownership/permissions need to be adjusted after crc upgrade
Checking file: /Users/af71194/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_hyperkit_4.6.3.crcbundle ...
INFO Checking size of the disk image /Users/af71194/.crc/cache/crc_hyperkit_4.6.3/crc.qcow2 ...
INFO Creating CodeReady Containers VM for OpenShift 4.6.3...
Found binary path at /Users/af71194/.crc/bin/crc-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address <IP_ADDRESS>:52129
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(crc) Calling .GetMachineName
(crc) Calling .DriverName
Running pre-create checks...
(crc) Calling .PreCreateCheck
(crc) Calling .GetConfigRaw
Creating machine...
(crc) Calling .Create
(crc) DBG | clean start, hyperkit pid file doesn't exist: /Users/af71194/.crc/machines/crc/hyperkit.pid
(crc) DBG | Using hyperkit binary from /Users/af71194/.crc/bin/hyperkit
(crc) DBG | Starting with cmdline: BOOT_IMAGE=(hd0,gpt1)/ostree/rhcos-b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/vmlinuz-4.18.0-193.28.1.el8_2.x86_64 rhcos.root=crypt_rootfs random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.platform.id=qemu rd.luks.options=discard ostree=/ostree/boot.1/rhcos/b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/0
(crc) DBG | Trying to execute /Users/af71194/.crc/bin/hyperkit -A -u -F /Users/af71194/.crc/machines/crc/hyperkit.pid -c 4 -m 9216M -s 0:0,hostbridge -s 31,lpc -U c3d68012-0208-11ea-9fd7-f2189899ab08 -s 1:0,virtio-blk,file:///Users/af71194/.crc/machines/crc/crc.qcow2,format=qcow -s 2,virtio-sock,guest_cid=3,path=/Users/af71194/.crc/machines/crc -s 3,virtio-rnd -l com1,autopty=/Users/af71194/.crc/machines/crc/tty,log=/Users/af71194/.crc/machines/crc/console-ring -f kexec,/Users/af71194/.crc/cache/crc_hyperkit_4.6.3/vmlinuz-4.18.0-193.28.1.el8_2.x86_64,/Users/af71194/.crc/cache/crc_hyperkit_4.6.3/initramfs-4.18.0-193.28.1.el8_2.x86_64.img,earlyprintk=serial BOOT_IMAGE=(hd0,gpt1)/ostree/rhcos-b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/vmlinuz-4.18.0-193.28.1.el8_2.x86_64 rhcos.root=crypt_rootfs random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.platform.id=qemu rd.luks.options=discard ostree=/ostree/boot.1/rhcos/b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/0
(crc) Calling .GetConfigRaw
(crc) Calling .DriverName
(crc) Calling .DriverName
Waiting for machine to be running, this may take a few minutes...
(crc) Calling .GetState
(crc) DBG | hyperkit pid from json: 87162
Machine is up and running!
Machine successfully created
Created /Users/af71194/.crc/machines/crc/.crc-exist
(crc) Calling .GetState
(crc) DBG | hyperkit pid from json: 87162
DEBU Waiting until ssh is available
DEBU retry loop: attempt 0
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 1
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 2
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 3
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 4
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

af71194@LC02CHB58MD6R ~ % crc version
CodeReady Containers version: 1.19.0+94b0362
OpenShift version: 4.6.3 (embedded in executable)
af71194@LC02CHB58MD6R ~ % crc delete; crc start --log-level debug
Do you want to delete the OpenShift cluster? [y/N]: y
Deleted the OpenShift cluster
DEBU CodeReady Containers version: 1.19.0+94b0362
DEBU OpenShift version: 4.6.3 (embedded in executable)
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
WARN A new version (1.21.0) has been published on https://cloud.redhat.com/openshift/install/crc/installer-provisioned
INFO Checking if podman remote executable is cached
DEBU Currently podman remote is not supported
INFO Checking if goodhosts executable is cached
DEBU goodhost executable already cached
INFO Checking minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
INFO Checking if running as non-root
INFO Checking if HyperKit is installed
DEBU Running '/Users/af71194/.crc/bin/hyperkit -v'
DEBU Found hyperkit version v0.20200224-44-gb54460
INFO Checking if crc-driver-hyperkit is installed
DEBU Checking if crc-driver-hyperkit is installed
DEBU Running '/Users/af71194/.crc/bin/crc-driver-hyperkit version'
DEBU Found crc-driver-hyperkit version 0.12.10
INFO Checking file permissions for /etc/hosts
DEBU Checking if /etc/hosts ownership/permissions need to be adjusted after crc upgrade
Checking file: /Users/af71194/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_hyperkit_4.6.3.crcbundle ...
INFO Checking size of the disk image /Users/af71194/.crc/cache/crc_hyperkit_4.6.3/crc.qcow2 ...
INFO Creating CodeReady Containers VM for OpenShift 4.6.3...
Found binary path at /Users/af71194/.crc/bin/crc-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address <IP_ADDRESS>:52129
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(crc) Calling .GetMachineName
(crc) Calling .DriverName
Running pre-create checks...
(crc) Calling .PreCreateCheck
(crc) Calling .GetConfigRaw
Creating machine...
(crc) Calling .Create
(crc) DBG | clean start, hyperkit pid file doesn't exist: /Users/af71194/.crc/machines/crc/hyperkit.pid
(crc) DBG | Using hyperkit binary from /Users/af71194/.crc/bin/hyperkit
(crc) DBG | Starting with cmdline: BOOT_IMAGE=(hd0,gpt1)/ostree/rhcos-b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/vmlinuz-4.18.0-193.28.1.el8_2.x86_64 rhcos.root=crypt_rootfs random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.platform.id=qemu rd.luks.options=discard ostree=/ostree/boot.1/rhcos/b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/0
(crc) DBG | Trying to execute /Users/af71194/.crc/bin/hyperkit -A -u -F /Users/af71194/.crc/machines/crc/hyperkit.pid -c 4 -m 9216M -s 0:0,hostbridge -s 31,lpc -U c3d68012-0208-11ea-9fd7-f2189899ab08 -s 1:0,virtio-blk,file:///Users/af71194/.crc/machines/crc/crc.qcow2,format=qcow -s 2,virtio-sock,guest_cid=3,path=/Users/af71194/.crc/machines/crc -s 3,virtio-rnd -l com1,autopty=/Users/af71194/.crc/machines/crc/tty,log=/Users/af71194/.crc/machines/crc/console-ring -f kexec,/Users/af71194/.crc/cache/crc_hyperkit_4.6.3/vmlinuz-4.18.0-193.28.1.el8_2.x86_64,/Users/af71194/.crc/cache/crc_hyperkit_4.6.3/initramfs-4.18.0-193.28.1.el8_2.x86_64.img,earlyprintk=serial BOOT_IMAGE=(hd0,gpt1)/ostree/rhcos-b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/vmlinuz-4.18.0-193.28.1.el8_2.x86_64 rhcos.root=crypt_rootfs random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.platform.id=qemu rd.luks.options=discard ostree=/ostree/boot.1/rhcos/b0ce903752d15965417ddab65b8a8718e28ba8c1c0cf96b5764e8f1ba1b56503/0
(crc) Calling .GetConfigRaw
(crc) Calling .DriverName
(crc) Calling .DriverName
Waiting for machine to be running, this may take a few minutes...
(crc) Calling .GetState
(crc) DBG | hyperkit pid from json: 87162
Machine is up and running!
Machine successfully created
Created /Users/af71194/.crc/machines/crc/.crc-exist
(crc) Calling .GetState
(crc) DBG | hyperkit pid from json: 87162
DEBU Waiting until ssh is available
DEBU retry loop: attempt 0
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 1
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 2
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 3
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
output  :  - sleeping 1s
DEBU retry loop: attempt 4
DEBU About to run SSH command:
exit 0
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

i can try 1.21 if ssh issue can be resolved

i can try 1.21 if ssh issue can be resolved

This is the initial connection to the VM which is failing, which is using pre-created keys, so I don't think this is related to ssh key generation.

This is the initial connection to the VM which is failing, which is using pre-created keys, so I don't think this is related to ssh key generation.

thanks , may i please know how i run update crypto policy from my Mac OS , i am doing some google now.

thanks , may i please know how i run update crypto policy from my Mac OS , i am doing some google now.

DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:

Right. I see the same ... the key pivoting is not even occuring yet.
What is enforcing this policy? Is there a tool on the machine that captures SSH sessions and keys?

DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:

Right. I see the same ... the key pivoting is not even occuring yet.
What is enforcing this policy? Is there a tool on the machine that captures SSH sessions and keys?

We use the Golang ssh client. I don't see how update-crypto-policies --set LEGACY can solve this. :thinking:

We use the Golang ssh client. I don't see how update-crypto-policies --set LEGACY can solve this. :thinking:

@ckvtvm-arch  is the crc daemon running? I see that you are using network-mode vsock, which requires this daemon to run for networking, so I prefer to make sure it's actually running :)

@ckvtvm-arch  is the crc daemon running? I see that you are using network-mode vsock, which requires this daemon to run for networking, so I prefer to make sure it's actually running :)

Yes, crc daemon is running. but the ssh keys are not getting generated due to some security policy. let me ask the security architect in my meeting tomorrow

Yes, crc daemon is running. but the ssh keys are not getting generated due to some security policy. let me ask the security architect in my meeting tomorrow

somehow it started working now. i am closing it now..

somehow it started working now. i am closing it now..

Yes, crc daemon is running. but the ssh keys are not getting generated due to some security policy.

I highly doubt this is caused by a company policy as our code would be unaware of this, unless low-level inspection would be performed. This might have been an edge case where the VM was started, but the key pivot did not get performed properly, but a restart expects this to be present?
Anyway ... more information would have been needed but got closed before this. Marking as invalid

Yes, crc daemon is running. but the ssh keys are not getting generated due to some security policy.

I highly doubt this is caused by a company policy as our code would be unaware of this, unless low-level inspection would be performed. This might have been an edge case where the VM was started, but the key pivot did not get performed properly, but a restart expects this to be present?
Anyway ... more information would have been needed but got closed before this. Marking as invalid

sorry

sorry

But it looks like crc is able to bypass the security policy. if i try to sshgen , i get a message saying that ssh keys cannot be generated and i have to generate the keys via venafi !

not sure what the resoltuion is in that case. You say CRC can bypass but you need to generate keys yourself? If so, you placed them manually in the ~/,crc/machines folder?
if our code fals to generate the keys it wil fail very hard and there is no way to recover this.

But it looks like crc is able to bypass the security policy. if i try to sshgen , i get a message saying that ssh keys cannot be generated and i have to generate the keys via venafi !

not sure what the resoltuion is in that case. You say CRC can bypass but you need to generate keys yourself? If so, you placed them manually in the ~/,crc/machines folder?
if our code fals to generate the keys it wil fail very hard and there is no way to recover this.

we have been able to repro the scenario, with the same error message, when the vsock network method is used and the daemon wasn't running. As this will prevent CRC from being able to communicate and start the initial key rotation,

we have been able to repro the scenario, with the same error message, when the vsock network method is used and the daemon wasn't running. As this will prevent CRC from being able to communicate and start the initial key rotation,

I cannot create ssh keys from my organization laptop, but my question was how CRC is able to create it with the security policy in place. Anyway i believe that the issue was may be due to the daemon not running as you pointed out as i frequently experience network issues.

I cannot create ssh keys from my organization laptop, but my question was how CRC is able to create it with the security policy in place. Anyway i believe that the issue was may be due to the daemon not running as you pointed out as i frequently experience network issues.


Some map models are not properly lit

Some map models are not properly lit:

That rings a bell but I don't remember what.
I was playing on Der Bunker (still 0.54.0 based if I'm right) while using 0.54.1 engine.

Regression introduced by me in 56d0d83ca64d0712a315d6637a3dfb0ccf74a5ab.

The way it looks makes me think that the grid light is not used when there is no lightmap, even if there is a grid light, so the model ends fullbright.


Why use sudo?

Hi, I noticed the following command is prefixed with sudo. It seems not good to use root privilege. Actually in the docker container, you can get root access, so no need to give it host's root privilege. Agree?
sudo docker-compose up

The docker daemon needs to do a lot of things which really require root rights.

Running containers (and applications) with Docker implies running the Docker daemon. This daemon currently requires root privileges, and you should therefore be aware of some important details.

see: https://docs.docker.com/engine/security/security/

If you just use docker-compose up, do you get errors? In my environment, it just works. Yes, the docker daemon currently requires root privilege, but the docker-compose is kind of some clients of the docker daemon, it doesn't need root privilege.

Ubuntu 14.04.4 LTS
Run docker-compose up without sudo gets:
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

docker-compose is a set of python scripts, create containers will call docker run actually.
What is your operating system?

I'm using OS X. I don't think this is an issue OS dependently. Maybe your error is caused by this.
I know the docker-compose calls docker run, and I think both of them don't need root privilege. You can see the official guide, and in there they just use
$ docker-compose up

The examples in the README assume that your are in production, usually Linux, not OS X.
Are there any evidence to prove that the user is not root in the official guide?
I know docker containers can be created without sudo in OS X, but it depends on a VM. Maybe you should check out the user privileges of docker deamon in your VirtualBox.

Yes, the $ sign is an evidence. Note the official guid use the $ sign, which means it's not a root user. If it's a '#' sign, it means a root user.


eth/api: update execution apis to latest spec

ref https://ethereum.github.io/execution-apis/api-documentation/
ref https://geth.ethereum.org/docs/interacting-with-geth/rpc

Codecov Report

Merging #204 (0526a3e) into main (bb0ebde) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   99.76%   99.76%
=======================================
  Files          73       73
  Lines        4336     4336
=======================================
  Hits         4326     4326
  Misses         10       10

Impacted Files
Coverage Δ

lib/eth/api.rb
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


"undefined method `sum' for nil:NilClass" error when i click on "Solvency" page/menu item

Guys, any idea how to fix this problem? Is this configuration issue?
It is happening on my local installation of Peatio, which i fetched yesterday

Hi @allenmillen
Check https://github.com/rubykube/peatio/issues/73.

Same problem. Already run 'rake solvency:liability_proof' before start server, but error still be there.