add to Enter vehicle details

@sanjaypoyzer
At the end of the section, could you add 'If required for enforcement purposes, a local authority may also ask for make, model and colour of the vehicle'
this was raised to us as part of gating template and we were told that without this information a user can challenge a parking ticket

Yep. Can add this.

@EUzkuraityte Is this still a thing if we're using the DVLA API?

we need to upload V5 - for compliance with our policy

@joanneSouthern Can we get the policy changed?

@sanjaypoyzer just to continue the original thread..
We maybe able to use VES API for this info and to calculate the permit price but we need a-to give user the option not to use it b-if reg not found or if the user chooses not to use VES look up, we need the fields to capture this info

not with elections coming up, it would take too long

@sanjaypoyzer here are the responses we got. Councils want to be using none or a combination of the listed items to calculate the permit price (4.1) and for enforcement purposes (4.2). The prototype should allow councils to localise this functionality and request this information from the user via VES API or manually.
4.1 What vehicle details do you need to ask the user via a VES API or manually to calculate the permit price?

Vehicle make
Vehicle colour
Vehicle registration number (entered by the user)
Vehicle model
Year of manufacture
Cylinder capacity
CO2 emissions
Fuel type
None

4.1 What vehicle details do you need to ask the user via a VES API or manually for enforcement purposes?

Vehicle make
Vehicle colour
Vehicle registration number (entered by the user)
Vehicle model
Vehicle status
None

Let's dig in further to why councils need this information so that we can explain to users.

@joanneSouthern @GWSunderland @OxfordshireCountyCouncil @danblundell
would you be able to provide a bit more info / reasoning on why we're asking users to give vehicle information for enforcement purposes? What's the underpinning need here?

I believe we collect this to help enforcement officers determine whether a permit is genuine.  The make, model and colour is not displayed on our permit but enforcement officers can access this information to verify the authenticity of a permit if they suspect one has been tampered with.

@EUzkuraityte So to confirm, DVLA's API response should include:

Vehicle make
Vehicle colour

As the below screenshot shows, the records do not include a "Vehicle model" entry.
Why do councils need "Vehicle status" for enforcement?

@sanjaypoyzer
I can confirm that my car is black ;)

@sanjaypoyzer Yes, i think this sounds correct. I assume that if a car is not taxed, then it's not legal to drive it, hence, need to know the status.

@EUzkuraityte So does that mean if the car is not taxed the council will not issue it with a permit? What about if it has a SORN?

@sanjaypoyzer we can ask Colin on Monday about what they do with SORNs, but I don't think we've observed any users having a car and wanting a parking permit for an off road car..

If it's SORN, it can't be on the road can it? So it wouldn't need a permit?

Weird, I wrote that question, then had that same thought and thought I deleted it before submitting. Obviously I'm just going crazy.
Still, would be good to know what happens if the car isn't taxed. I assume they refuse the permit?

@sanjaypoyzer I just got an email from DVLA re: use of VES API and they've been a little slow with shifting the service onto the new platform. Therefore, they're not able to take onto even one new RP. We'll have a catch up in a few month's time but it definitely does not align with our timescales and we won't be able to have this functionality in time.
In light of this, can we:
1 change this page to introduce additional information fields as drop downs
2 introduce an option for the user to go to DVLA site and check this information if they don't have it ready
3 Update this page to that it no longer says we received this info from DVLA
I'm copying in @lizziebruce for this as she can advice on the content copy for both of these pages

What I'm creating, as I understand it from above discussion...
https://verify-local-patterns.herokuapp.com/service-patterns/parking-permit/example-service/enter-reg

Field label copy for:
Vehicle make
Vehicle colour
Instructions for the user to go to DVLA site and check this information if they don't have it ready

https://verify-local-patterns.herokuapp.com/service-patterns/parking-permit/example-service/confirm-vehicle-details
3. delete "we received this info from DVLA" (and replace with something else?)

So...
Enter reg page
For councils who want extra enforcement details:

[Not done the drop down functionality. Need @sanjaypoyzer / dev help with this!
Car make – is this drop down / free text / autotext?
Car colours: Beige, black, blue, bronze, brown, buff, cream, gold, green, grey, ivory, maroon, orange, pink, purple, red, silver, turquoise, white and yellow.]
For councils that don't it's still:

Confirm vehicle details page
For councils who want extra enforcement details:

For councils that don't it's still:

@lizziebruce amazing work! The only bit that I'd change is not showing the confirm vehicle details page for councils that don't ask additional details as the user would not have entered anything prior ..

@EUzkuraityte thanks! Should this screen simply say confirm registration number then, or alternatively there be functionality for the reg number they input to appear on the previous screen for them to check, i.e. in case of typos etc?

@lizziebruce I think we probs don't need an entire page just to confirm what they've just entered. Would go with your latter proposition or just adding the reg number to the 'check before you pay' page.

@EUzkuraityte thanks, let's get @sanjaypoyzer involved for councils that don't need additional details. Just to doublecheck, are there 2 options or 3? My content fix was for scenarios 1. and 2. below but it from your comments it sounds like either there could be 1. 2. and 3. or that it's only 1. and 3.

Council asks for make and colour from user
Council looks up make and colour from DVLA and asks user to confirm
Council doesn't ask for or look up make and colour

Northumberland, at the moment we just ask for the reg, however we like the fact the DVLA brings back make and colour, it provides a extra check to the users that they have entered the correct reg

@joanneSouthern The DVLA API won't be available in the timescales of this project.
In response to Lizzie's 3 options, the option 2 will not be available - So there will only be option 1 and 3.

@sanjaypoyzer hey, this issue wasn't showing up on the Project Board. @Egle couldn't find it either. Then we moved a different card and it suddenly showed up! Something similar happened with a CT issue this morning. Does Github have weevils?

Fixed but need Sanjay's help with the Next button coding.
Council requires make and colour

Next screen is

Council doesn't

Skips confirm details screen but can check reg number on this later screen

@lizziebruce Come grab me to work on this if you want, or put in a pull request and I'll take a look.

@sanjaypoyzer I've added this on the prototype now (sorry was editing master so no PR). The Next button goes to the next screen as per below.
Ask for make colour

Don't ask for make colour

Ideally the No radio button on the Confirm details screen should take the user back to the Enter reg page. But it doesn't at the moment.

@EUzkuraityte FYI here's the vehicle makes & colours dropdown functionality that Sanjay has added:

Ok for larger things like this, we really need to have a review process with PRs.
I don't think there's any need for a confirm vehicle details in either instance here.

@sanjaypoyzer But it's all screenshotted out in the issue above with you tagged on it... You should have commented then that you didn't think it was the right approach.

closing this as we no longer recommend asking users for the additional info


Add MD5 checksum for datasets

Description
Each dataset loader should have an argument check_MD5 (set to False by default) that performs MD5 checksum of the downloaded dataset.

Do the md5 checksums already exist for these database provided by the original papers or will we be generating them ourselves?
Currently we don't seem to have them.
If we are using them to validate that the datasets are the same as used in the referenced papers we need to their original md5 checksums.
If we are using them to validate that the download was not corrupted, generating them ourselves will be fine.

Original datasets do not come with a checksum, unfortunately.
We will have to generate checksums from a version we download from their original URLs:

wn18, fb15k:  https://www.hds.utc.fr/everest/doku.php?id=en:transe [DEAD LINK - compute the MD5 stright from our datasets.]
fb15k-237: https://www.microsoft.com/en-us/download/details.aspx?id=52312
wn18RR: DettmersMS018 https://github.com/TimDettmers/ConvE/blob/master/WN18RR.tar.gz
YAGO3-10  https://github.com/TimDettmers/ConvE/blob/master/YAGO3-10.tar.gz
WN11 & FB13: https://cs.stanford.edu/people/danqi/data/nips13-dataset.tar.bz2

Just noticed the check_md5hash argument is not documented in docstrings.
Can you please amend?


Redirect /verify-auth(-azure)?/.* to /.*

Logic LGTM

https://github.com/rancher/dashboard/pull/2240


Resource 'ciscoise_network_access_authentication_rules' does not support nested children blocks

Environment:
ISE version and patch: ISE 3.1 patch 4
Terraform version: 1.3.1
ISE provider version: 0.6.10-beta
OS version: MacOS 12.6
Affected resources
The same nested logic described below should apply to all of the following resources:

ciscoise_network_access_policy_set
ciscoise_device_administration_policy_set
ciscoise_network_access_authentication_rules
ciscoise_network_access_authorization_rules
ciscoise_device_administration_authentication_rules
ciscoise_device_administration_rules

Describe the bug
The ISE Authentication and Authorization Policies support creation of multiple AND/OR condition matching blocks. As such, the TF resource needs to support creation of the same structure.
When attempting to create a new AuthC Policy, TF return an error for multiple unsupported arguments:
│ Error: Unsupported argument
│
│   on policy.tf line 329, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  329:         dictionary_name  = "Radius"
│
│ An argument named "dictionary_name" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 330, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  330:         attribute_name  = "NAS-Port-Type"
│
│ An argument named "attribute_name" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 331, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  331:         operator = "equals"
│
│ An argument named "operator" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 332, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  332:         attribute_value = "Ethernet"
│
│ An argument named "attribute_value" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 337, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  337:         dictionary_name  = "Network Access"
│
│ An argument named "dictionary_name" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 338, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  338:         attribute_name  = "EapAuthentication"
│
│ An argument named "attribute_name" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 339, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  339:         operator = "equals"
│
│ An argument named "operator" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on policy.tf line 340, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  340:         attribute_value = "EAP-TLS"
│
│ An argument named "attribute_value" is not expected here.

Example code
resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
  provider = ciscoise.ise31-2
  parameters {
    identity_source_name = ciscoise_id_store_sequence.iss-ad-cert.item[0].name
    if_auth_fail         = "REJECT"
    if_process_fail      = "DROP"
    if_user_not_found    = "REJECT"
    policy_id = "b8731cac-dba3-43bc-ac2b-f3205e01e8c1"
    rule {
      default    = "false"
      name       = var.authc-policy-eaptls
      rank       = 0
      state      = "enabled"
      condition {
        condition_type = "andBlock"
        is_negate = "false"
      children {
        dictionary_name  = "Radius"
        attribute_name  = "NAS-Port-Type"
        operator = "equals"
        attribute_value = "Ethernet"
        is_negate      = "false"
      }
      children {
        dictionary_name  = "Network Access"
        attribute_name  = "EapAuthentication"
        operator = "equals"
        attribute_value = "EAP-TLS"
        is_negate = "false"
      }
    }

OpenAPI call resulting in '201 Created' response
{
        {
            "rule": {
                "default": false,
                "name": "Dot1x EAP-TLS",
                "rank": 0,
                "state": "enabled",
                "condition": {
                    "conditionType": "ConditionAndBlock",
                    "isNegate": false,
                    "children": [
                        {
                            "conditionType": "ConditionAttributes",
                            "isNegate": false,
                            "dictionaryName": "Radius",
                            "attributeName": "NAS-Port-Type",
                            "operator": "equals",
                            "attributeValue": "Ethernet"
                        },
                        {
                            "conditionType": "ConditionAttributes",
                            "isNegate": false,
                            "dictionaryName": "Network Access",
                            "attributeName": "EapAuthentication",
                            "operator": "equals",
                            "attributeValue": "EAP-TLS"
                        }
                    ]
                }
            },
            "identitySourceName": "ISS_AD_Cert",
            "ifAuthFail": "REJECT",
            "ifUserNotFound": "REJECT",
            "ifProcessFail": "DROP"
        }
}

Additional context
Policy Sets, Authentication, and Authorization policies support multiple levels of nesting, so the TF resources needs to support the same.
Here is an example of the GET API output for a nested OR block within the same policy.
{
    "version": "1.0.0",
    "response": {
        "rule": {
            "default": false,
            "id": "ce68e2e9-1526-45c2-b025-925d80725d22",
            "name": "Dot1x EAP-TLS",
            "hitCounts": 0,
            "rank": 0,
            "state": "enabled",
            "condition": {
                "link": null,
                "conditionType": "ConditionAndBlock",
                "isNegate": false,
                "children": [
                    {
                        "link": null,
                        "conditionType": "ConditionAttributes",
                        "isNegate": false,
                        "dictionaryName": "Radius",
                        "attributeName": "NAS-Port-Type",
                        "operator": "equals",
                        "dictionaryValue": null,
                        "attributeValue": "Ethernet"
                    },
                    {
                        "link": null,
                        "conditionType": "ConditionAttributes",
                        "isNegate": false,
                        "dictionaryName": "Network Access",
                        "attributeName": "EapAuthentication",
                        "operator": "equals",
                        "dictionaryValue": null,
                        "attributeValue": "EAP-TLS"
                    },
                    {
                        "link": null,
                        "conditionType": "ConditionOrBlock",
                        "isNegate": false,
                        "children": [
                            {
                                "link": null,
                                "conditionType": "ConditionAttributes",
                                "isNegate": false,
                                "dictionaryName": "Radius",
                                "attributeName": "User-Name",
                                "operator": "equals",
                                "dictionaryValue": null,
                                "attributeValue": "user1"
                            },
                            {
                                "link": null,
                                "conditionType": "ConditionAttributes",
                                "isNegate": false,
                                "dictionaryName": "Radius",
                                "attributeName": "User-Name",
                                "operator": "equals",
                                "dictionaryValue": null,
                                "attributeValue": "user2"
                            }
                        ]
                    }
                ]
            }
        },
        "identitySourceName": "ISS_AD_Cert",
        "ifAuthFail": "REJECT",
        "ifUserNotFound": "REJECT",
        "ifProcessFail": "DROP",
        "link": {
            "rel": "self",
            "href": "https://ise31-2.ise.trappedunderise.com/api/v1/policy/network-access/policy-set/b8731cac-dba3-43bc-ac2b-f3205e01e8c1/authentication/ce68e2e9-1526-45c2-b025-925d80725d22",
            "type": "application/json"
        }
    }
}

@aussietexan , please try it with 0.6.11-beta and let us know if it is working for you.

Hi @fmunozmiranda. I tried using the same example code above to create the AuthC rule with the 0.6.11-beta code and now I get a 400 error.
│ Error: Failure when executing CreateNetworkAccessAuthenticationRule
│
│   with ciscoise_network_access_authentication_rules.mm-authc-eaptls,
│   on policy.tf line 309, in resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls":
│  309: resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
│
│ error with operation CreateNetworkAccessAuthenticationRule
│ {
│   "message" : "request has bad input format in the body",
│   "code" : 400
│ }

@fmunozmiranda. I noticed that the documentation was updated to included the 'condition_type' in the nested children block, so I updated my TF code as follows. It still returns the same 400 error.
TF Code
resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
  provider = ciscoise.ise31-2
  parameters {
    identity_source_name = ciscoise_id_store_sequence.iss-ad-cert.item[0].name
    if_auth_fail         = "REJECT"
    if_process_fail      = "DROP"
    if_user_not_found    = "REJECT"
    policy_id = "8c73e8d8-1c3c-477b-8b6f-d58952d490f2"
    rule {
      default    = "false"
      name       = var.authc-policy-eaptls
      rank       = 0
      state      = "enabled"
      condition {
        condition_type = "andBlock"
        is_negate = "false"
      children {
        condition_type = "ConditionAttrs"
        dictionary_name  = "Radius"
        attribute_name  = "NAS-Port-Type"
        operator = "equals"
        attribute_value = "Ethernet"
        is_negate      = "false"
      }
      children {
        condition_type = "ConditionAttrs"
        dictionary_name  = "Network Access"
        attribute_name  = "EapAuthentication"
        operator = "equals"
        attribute_value = "EAP-TLS"
        is_negate = "false"
      }
    }
  }
}
}

API body that returns 201 Created response
{
            "rule": {
                "default": false,
                "name": "Dot1x EAP-TLS",
                "rank": 0,
                "state": "enabled",
                "condition": {
                    "conditionType": "ConditionAndBlock",
                    "isNegate": false,
                    "children": [
                        {
                            "conditionType": "ConditionAttributes",
                            "isNegate": false,
                            "dictionaryName": "Radius",
                            "attributeName": "NAS-Port-Type",
                            "operator": "equals",
                            "attributeValue": "Ethernet"
                        },
                        {
                            "conditionType": "ConditionAttributes",
                            "isNegate": false,
                            "dictionaryName": "Network Access",
                            "attributeName": "EapAuthentication",
                            "operator": "equals",
                            "attributeValue": "EAP-TLS"
                        }
                    ]
                }
            },
            "identitySourceName": "ISS_AD_Cert",
            "ifAuthFail": "REJECT",
            "ifUserNotFound": "REJECT",
            "ifProcessFail": "DROP"
        }

Hi @aussietexan do you have a valid request body (functional on api, tested in postman or something like that) for this resource?
if you have it, should you pass it?

Hi @fmunozmiranda , the response I posted above has an example request body for the API that returns a '201 Created' response when used in Postman.

Hey @aussietexan, I think the problem is in your condition_type values it seems that accepted values are:

ConditionAttributes
ConditionAndBlock
ConditionOrBlock
Could you tested with those changes?

Hi @fmunozmiranda , I updated my TF code to use those values rather than the values in the documentation (https://registry.terraform.io/providers/CiscoISE/ciscoise/latest/docs/resources/network_access_policy_set#nested-schema-for-parametersconditionchildren) and both the Policy Set and AuthC Policy resources worked correctly.
Please update the documentation to reflect the correct accepted values.
Example TF code
resource "ciscoise_network_access_policy_set" "wired-mm-test" {
  provider = ciscoise.ise31-2
  depends_on = [
    ciscoise_network_device_group.ndg_mm
  ]
  parameters {
    default     = "false"
    name         = "Wired_MM_TEST"
    description = "Wired Monitor Mode TEST"
    rank         = 0
    is_proxy    = "false"
    service_name = "MAB_EAP-TLS"
    state        = "enabled"
    condition {
      condition_type = "ConditionAndBlock"
      is_negate = "false"
      children {
        condition_type = "ConditionAttributes"
        is_negate = "false"
        dictionary_name  = "Radius"
        attribute_name  = "NAS-Port-Type"
        operator = "equals"
        attribute_value = "Ethernet"
      }
      children {
        condition_type = "ConditionAttributes"
        is_negate = "false"
        dictionary_name  = "DEVICE"
        attribute_name  = "Deployment Stage"
        operator = "equals"
        attribute_value = "Deployment Stage#Monitor Mode"
      }
    }
  }
}

resource "ciscoise_network_access_authentication_rules" "mm-authc-eaptls" {
  provider = ciscoise.ise31-2
  parameters {
    identity_source_name = ciscoise_id_store_sequence.iss-ad-cert.item[0].name
    if_auth_fail         = "REJECT"
    if_process_fail      = "DROP"
    if_user_not_found    = "REJECT"
    policy_id = ciscoise_network_access_policy_set.wired-mm-test.parameters[0].id
    rule {
      default    = "false"
      name       = var.authc-policy-eaptls
      rank       = 0
      state      = "enabled"
      condition {
        condition_type = "ConditionAndBlock"
        is_negate = "false"
      children {
        condition_type = "ConditionAttributes"
        dictionary_name  = "Radius"
        attribute_name  = "NAS-Port-Type"
        operator = "equals"
        attribute_value = "Ethernet"
        is_negate      = "false"
      }
      children {
        condition_type = "ConditionAttributes"
        dictionary_name  = "Network Access"
        attribute_name  = "EapAuthentication"
        operator = "equals"
        attribute_value = "EAP-TLS"
        is_negate = "false"
      }
    }
  }
}
}

Thanks for feedback, I will update documentation in next realese.


wrong "UPDATE SELECTION" button color

General summary

wrong "UPDATE SELECTION" button color
Expected behaviour

button should be white text on green background

Actual behaviour

button is black text on green background

Steps to reproduce

Open media picker
Select a media

Client(s) notification(s)

Follow the Material Design guidelines : https://material.io/guidelines/style/color.html#color-color-palette


Rectify ports across Beacon Node and Execution clients to match defaults

Todos

[ ] Validator

[ ] Lodestar
[ ] Teku
[ ] Lighthouse

[ ] Consensus Layer

[ ] Lodestar
[ ] Teku
[ ] Lighthouse

[ ] Execution Layer

[ ] Nethermind

Problem
Person 1:
Just checked the configuration of LightHouse and we should change port mappings from 9001 back to 9000 (default value) as well
Configure Server: https://docs.gnosischain.com/node/guide/configure-server#allow-consensus-client-port-9000 :white_check_mark:
https://docs.gnosischain.com/node/guide/beacon/lighthouse#2-docker-compose replace 9001 with 9000 :warning:
List of LH CLI args: https://github.com/sigp/lighthouse/blob/stable/boot_node/src/cli.rs#L26
Person 2:
I think there are inconsistencies in the docs that can cause a degraded behavior of the Gnosis Chain validators. One of the heaviest I’ve seen:

Recommend to enable UFW allowing port 30303 the default used by Nethermind
When configuring Nethermind you recommend setting DiscoveryPort to 30304 so if someone enables UFW the port won’t be reached as there is no allow rule for that port
In Nethermind configuration you open 30304 TCP and UDP to the host (although both are blocked by UFW if enabled), BUT you are not setting P2PPort so it’s using the default configuration 30303. So for TCP incoming connections Nethermind will expect them to happen in 30303 while you are exposing 30304 so is not possible to reach.

If you want people to be able to configure Nethermind you should either rollback all to 30303  or:

Add UFW rule for 30304 instead of 30303
Set P2PPort to 30304

Without this changes Nethermind loose all peers connections after few hours

I'll be picking up on this


Flutter will not let me dive in

`Launching lib\main.dart on ONEPLUS A5000 in debug mode...
Running Gradle task 'assembleDebug'...
√ Built build\app\outputs\apk\debug\app-debug.apk.
error: closed
Installing build\app\outputs\apk\app.apk...
Error: ADB exited with exit code 1
Performing Streamed Install

adb: connect error for write: closed
Error launching application on ONEPLUS A5000.`

Hello People,
i am trying to start programming ... but Android Studio / Flutter SDK is givig me this output.
Can you please help me?
Mato

Have you tried flutter doctor -v?

Hi @mato37,
Did you follow all the steps on how to install Flutter ? It's not clear from the description which OS you are trying to run Flutter on. Please visit above link once again corresponding to OS you are on and see if you have all steps covered.
Also, there's similar open issue describing your case, 51690 which has various solutions you can try on. See if any of them works for you.
Thanks.

flutter doctor -v

where do i type it in?

@mato37 run that command from root path of your flutter project. Also check the issue link I referred in my earlier comment and see if any of those solutions work for you.

This might be an issue related to USB Debugging mode on the device,  as can be seen with, adb: connect error for write: closed
this happens in Chinese manufacturer phones such as OnepLus, Xiaomi, Oppo they have a second option for USB Debugging write or similar,  apart from allow USB Debugging. @mato37  please check your developer options on your phone and ensure all settings related to USB Debugging are turned on.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Extension issue

Issue Type: Bug
Extension Name: vsliveshare
Extension Version: 1.0.2048
OS Version: Linux x64 5.3.0-46-generic
VSCode version: 1.44.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Hey @lucasjorge944 , could you provide some more details about the issue?

Closing this issue due to inactivity and lack of actionable details. Please re-open it if you're still encountering an issue. Thanks!


Implement configurable archetypes

Now, implement config hooks as described in https://github.com/vitonsky/charmix/issues/4


Database not being fully setup on install

I'm currently trying to install this plugin in an existing Backstage instance, and it appears that the database isn't being fully configured properly.  This is the error that is coming out of the logs, which seems to indicate that one of the necessary tables was not created when the database was initialized.
[1] 2024-02-19T16:11:15.988Z backstage error Request failed with status 500 SELECT sum(time_saved), team, template_name from ts_template_time_savings group by team, template_name; - no such table: ts_template_time_savings type=errorHandler code=SQLITE_ERROR stack=SqliteError: SELECT sum(time_saved), team, template_name from ts_template_time_savings group by team, template_name; - no such table: ts_template_time_savings
[1]     at Database.prepare (/Users/jebentier/invoca/invoca-backstage/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
[1]     at Client_BetterSQLite3._query (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/dialects/better-sqlite3/index.js:35:34)
[1]     at executeQuery (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/execution/internal/query-executioner.js:37:17)
[1]     at Client_BetterSQLite3.query (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/client.js:154:12)
[1]     at Runner.query (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/execution/runner.js:141:36)
[1]     at ensureConnectionCallback (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/execution/internal/ensure-connection-callback.js:13:17)
[1]     at Runner.ensureConnection (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/execution/runner.js:318:20)
[1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[1]     at async Runner.run (/Users/jebentier/invoca/invoca-backstage/node_modules/knex/lib/execution/runner.js:30:19)
[1]     at DatabaseOperations.getAllStats (/Users/jebentier/invoca/invoca-backstage/node_modules/@tduniec/backstage-plugin-time-saver-backend/src/database/databaseOperations.ts:157:22)
[1]     at TsApi.getAllStats (/Users/jebentier/invoca/invoca-backstage/node_modules/@tduniec/backstage-plugin-time-saver-backend/src/api/apiService.ts:66:25)
[1]     at <anonymous> (/Users/jebentier/invoca/invoca-backstage/node_modules/@tduniec/backstage-plugin-time-saver-backend/src/service/router.ts:89:16)

When I look at the packages/backend/db/timesaver.sqlite, I can see that the init.js was flagged as having run successfully:

I'm currently running with the following package versions installed:
@tduniec/backstage-plugin-time-saver-common: 0.1.1
@tduniec/backstage-plugin-time-saver: 0.1.6
@tduniec/backstage-plugin-time-saver-backend: 0.1.7
Any help is greatly appreciated, this plugin will be very useful in getting ROI data on our Backstage implementation.

Hey,
thanks for interest in this plugin!
Unfortunatelly I haven’t prepared plugin to work with SQLite, it is required to set it up on postgres.
Can you check with postgresDB and let me know ?

Ah, thanks I didn't realize this only worked with a postgresql database. I can confirm that it works on postgresql. I'm curious what the issue is with getting the database working with SQlite? I see that there is a default being set on the id field, but I've never seen that done for any other plugin database.

Yes, I will include this also to work on SQLite since I can see the demand is bigger than expected. :)
I hole you like the plugin, Feedback is more than welcomed :)

🤔 I know this isn't related to the original issue, but I'm now getting an error on page load when attempting to use postgres. The error is theme.applyStyles is not a function

Thank you for the quick response. I did find a fix for it that didn't require blowing away my entire yarn.lock, which was to run yarn upgrade-interactive in order to force all installations of @backstage/theme to the latest 0.5.0 version. The plugin is now successfully loading the UI. Thank you for the help with this.

Thank you very much for all the helpfulness here, I really appreciate it. I'm currently trying to run the migrate action through the API so that previously run tasks can be imported into the time savings database, and I'm getting the following error:
Error selecting data:
            select spec from scaffolder.tasks where id=$1
             - relation \"scaffolder.tasks\" does not exist","name":"error","plugin":"timesaver","position":"31","routine":"parserOpenTable","service":"backstage","severity":"ERROR","stack":"error:
            select spec from scaffolder.tasks where id=$1
             - relation \"scaffolder.tasks\" does not exist
    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:287:98)
    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
    at readableAddChunk (node:internal/streams/readable:341:9)
    at Readable.push (node:internal/streams/readable:278:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

Have y'all seen this before?

I see where the issue is, let me fix that for such use case.

Can you test this version of plugin ?
<EMAIL_ADDRESS>

@toma2395 That's worked! Thank you so much for the quick fix here!

Can we close the issue ?

Yea we can go ahead and close the issue and track SQlite support separately. Thank you for all the help on this.


crc setup loop

Hi all,
Trying to setup crc on Windows 10 Pro [Version 10.0.19041.1052] and am having an issue with the crc setup command.
When I run it I get the following output...
C:\Users\ChrisBeech>crc setup
INFO Checking if crc-admin-helper executable is cached
INFO Checking for obsolete admin-helper executable
INFO Checking if running on a supported CPU architecture
INFO Checking minimum RAM requirements
INFO Checking if running in a shell with administrator rights
INFO Checking Windows 10 release
INFO Checking Windows edition
INFO Checking if Hyper-V is installed and operational
INFO Checking if crc-users group exists
INFO Checking if current user is in Hyper-V group and crc-users group
INFO Adding current user to group
INFO Will run as admin: adding current user to crc-users group
Please reboot your system and run 'crc setup' to complete the setup process

...the problem is that when I reboot and run it again, it gives me exactly the same output!
I'm going round in circles and can't seem to figure out why.
Any ideas?
Chris

Is your machine domain joined?

My user account is an Azure AD account, so it's joined to AAD.

Duplicate of #2446 and was fixed in #2494 , we'll have a new release this week which will have that fix.

Closing this since it's a duplicate.
Duplicate of #2446


Broken link

In the list: "Inspect - Get AWS stack info in JSON."

Thanks for reporting @kalinchernev 👍
Seems like this repo was moved. I fixed the broken link with this one: https://github.com/seek-oss/serverless-plugin-inspect.


Make sure changing the light state doesn't spam the server

first happened when i replaced the python stuff with php. i turned on a light and then turned it off. and it started flickering the light. turning in on and off really fast. i commented out the code in the server and that made it stop flickering the light. i fixed some bugs with it not setting the target_state to -1....
it seems to be fixed... but i checked the network tab after turning a light on and it looked like it was spamming server requests to the api for the lights. i suspect it has to do with not caching the lights data locally... i might need to do more debugging for how it pushes collection items.... or otherwise just make sure it's safe to control the lights with the new stuff and that it's never going to do the flickering doom thing again....

i'm fairly confident this isn't happening. it seems to be ok to use the new interface to control the lights. though now i'm not sure if it didn't seem to break updating the ui... some lights had been turned on but it didn't show up in the ui until i refreshed....


Could not find module npm:prettycron when selecting  Cronjob as Workload

Steps to Reproduce:

Deploy Workload.
Select Run on a cron schedule as Workload Type

Results:
0:252 Uncaught Error: Could not find module `npm:prettycron` imported from `shared/helpers/pretty-cron`
    at 0:252
    at u (0:263)
    at a.findDeps (0:173)
    at u (0:267)
    at a.findDeps (0:173)
    at u (0:267)
    at requireModule (0:29)
    at i (0:150198)
    at i (0:150198)
    at n._extractDefaultExport (0:188719)

Version - 2.1 master 9/20
Verified fixed


Update fs2-core to 2.4.1

Updates co.fs2:fs2-core from 2.2.2 to 2.4.1.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-core" } ]

labels: library-update, semver-minor

Codecov Report

Merging #1236 into master will increase coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1236      +/-   ##
==========================================
+ Coverage   80.97%   81.07%   +0.09%
==========================================
  Files          55       55
  Lines        1009     1009
  Branches       42       42
==========================================
+ Hits          817      818       +1
+ Misses        192      191       -1

Impacted Files
Coverage Δ

core/src/main/scala/io/finch/Endpoint.scala
72.22% <0.00%> (+0.55%)
:arrow_up:

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 5137cc4...176fb6f. Read the comment docs.


IndexError: list index out of range

Traceback (most recent call last):
  File "/Users/gordio/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 303, in on_activated
    callback.on_activated(v)
  File "/Users/gordio/Library/Application Support/Sublime Text 3/Packages/OmniSharp/listeners/server_runner.py", line 12, in on_activated
    omnisharp.create_omnisharp_server_subprocess(view)
  File "/Users/gordio/Library/Application Support/Sublime Text 3/Packages/OmniSharp/lib/omnisharp.py", line 247, in create_omnisharp_server_subprocess
    solution_path = current_solution_or_project_json_folder(view) #current_solution_or_folder(view)
  File "/Users/gordio/Library/Application Support/Sublime Text 3/Packages/OmniSharp/lib/helpers.py", line 73, in current_solution_or_project_json_folder
    parentpath = sublime.active_window().folders()[0] #assume parent folder is opened that contains all project folders eg/Web,ClassLib,Tests
IndexError: list index out of range

And in "realtime" I check:
>>> sublime.active_window().folders()
[]

Is this because you've just one csharp file open and not a folder with a project in it?

Yep. It's when Sublime opened from file/terminal/programm (like Unity3D or Alfred).
And path exist only if sublime open project or directory (from terminal, ex subl ./).

yeah i figured people would be editing stuff for whole projects.
i guess it should handle single files too.
if the folders()[0] is empty it should return the path of the single open
file. if you fancy contributing feel free as I dont have time to look at
this right now
On 14 January 2015 at 10:24, Oleg Gordienko<EMAIL_ADDRESS>wrote:

Yep. It's when Sublime opened from file/terminal/programm (like Unity3D or
Alfred).
And path exist only if sublime open project or directory (from terminal,
ex subl ./).
--
Reply to this email directly or view it on GitHub
https://github.com/OmniSharp/omnisharp-sublime/issues/104#issuecomment-69896262
.

PR for this is #105

Should be done now with 1.9.1 release

same issue here


Arguments tab defaults to collapsed when debugging

I'm not %100 sure if this is the place for this issue. However, I don't think it's a general issue with VS Code because of what was said in this issue.
Environment data
VS Code version:  1.17.2
Python Extension version:  0.7.0
Python Version:   3.6.2
OS and version:    Windows 10 Home, 1703
Actual behavior
When debugging, the "Arguments" tab inside VARIABLES defaults to closed.

Expected  behavior
Arguments are pretty important, perhaps this should default to open, like it does for local variables? Or at least have an option to toggle this behaviour.
Steps to reproduce:
Debug any Python program
Logs
Output from Python output panel

Output from Console window (Help->Developer Tools menu)

@AdamBJ
Apologies for the late response. We've been working on a new Python debugger.
Please could you test this issue with the new experimental debugger in the latest version of the extension.
Open your existing .vscode/launch.json and change the setting "type":"python" to "type":"pythonExperimental"
Note: The Arguments tab will not be available, however we do have other tabs such as Variables.


Fix Docker architecture tag set by bazel

What this PR does / why we need it:
This tags the Docker images correct when building multiarch images
Which issue this PR fixes:
fixes #2987
Special notes for your reviewer:
I had to update the Bazel Docker helper to support setting this. This also deprecated v1 manifests which is why the Nginx ingress is updated also.
Release note:

Tag the Docker image with the correct `architecture` attribute

/kind bug

Can we add a corresponding check to the validation functions in our release tool to make sure this is set correctly in the final images? Conscious of the runAsUser issue we had previously.
Also, does this handle the case where arm has two variants, v7 and v8?
Does the os_version field also need setting? I'm not sure how this translates into Docker layers 👀

i don't think OS needs setting as it defaults to Linux, I don't see us building Windows containers very soon?
For ARM it doesn't specifically set it, which unless we don't support v6 I don't think is an issue. As reference I inspected arm32v7/debian and it only sets the architecture to arm but no arm version constraint.
Will make a PR for the release tool too.

@munnerz turns out I was incorrect cpu_variant only exists on container_pull and not container_image as it seems to only exist in manifest lists and not images

/lgtm


[Feature] Optimize guid queries (Update) [OSF-7462]

Purpose
Updates #6842, #6803
h/t @cwisecarver
Changes

Put annotations on in the managers
Expose previously exposed (with .as_manager magick) queryset methods on manager
Set _default_manager on (most) models to have the Mixins included in related fields' mro

Side effects
<Node>.forks, <Node>.logs, etc. are still being inefficient. AbstractNode is a TypedModel, and overriding the _default_manager leads to save calls on untyped objects. Inheriting from TypedModelManager on AbstractNodeManager did not change this. To be fixed, along with OSFUserManager, in a follow-up PR.
Ticket
[OSF-7462]

lgtm :shipit:


Exposes property derived MySQL datasource so sparkstreaming can use it

The only thing ZipkinMySQLStorageProperties is used for is creating a
datasource. This exposes that so that the logic doesn't have to be copy
pasted into zipkin-sparkstreaming.

see https://github.com/openzipkin/zipkin-sparkstreaming/pull/14


Clarifications about SS instructions in Machine mode

Here says " the Use of Zicfiss in M-mode is not supported? But what's the exact bahavior when execute Zicfiss instructions in Machine mode?
First, For sspush/sspopchk instructions, Should they be considered as Zipmop instructions?
Second, For ssamoawap.W/D instructions, here says:

Does it mean that as long as in machine mode, executing ssamoswap instrcution will cause store/AMO access fault?  Is it possible that the mstatus.mprv ==1 && mstatus.mpp == 2'b01， then the ssamoswap instruction is considered to be executed in Supervisor  mode?

The section 2.3 defines a term called xSSE that determines if Zicfiss is enabled at a privilege mode and the table 1 shows how xSSE is determined. Instructions that are encoded using MOPs/C.MOPs are listed in section 2.1. When xSSE is 0, these revert to their ZImop/Zcmop specified behavior. The behavior of ssamoswap is specified in section 2.7 by the pseudocode in listing 2.7. When MPRV is 1 all memory accesses in M-mode are with effective privilege determined by MPP. The MPRV behavior does not change for ssamoswap,

The section 2.3 defines a term called xSSE that determines if Zicfiss is enabled at a privilege mode and the table 1 shows how xSSE is determined. Instructions that are encoded using MOPs/C.MOPs are listed in section 2.1. When xSSE is 0, these revert to their ZImop/Zcmop specified behavior. The behavior of ssamoswap is specified in section 2.7 by the pseudocode in listing 2.7. When MPRV is 1 all memory accesses in M-mode are with effective privilege determined by MPP. The MPRV behavior does not change for ssamoswap,

Close, #225 solved this.


Implement .add( controller ) & its use for custom Controllers.

See example of a custom controller in example.html.
Fixes #4.
I stripped out everything unessential. It's just add( controller ) and a couple examples.
You can include parameters when adding:
gui.add( controller, params );
Currently a parameter called liClass lives here.

Param
Type
Default
Description

[params]
Object

[params.liClass]
String

class name appended to controller's li row.

This was needed to avoid more special cases in assigning li row class, which is done just after controller class is squared away in GUI.js.

Hi.
I've just started using this library and seems like this PR is a huge thing for my use case.
what is needed in order for this to be published?


x/tools/go/ssa/ssautil: panic on Go 1.10.4 with go/packages

I encountered this weird issue while converting https://github.com/mvdan/unparam to go/packages. You can see the CI status here, where 1.11.1 is green, yet 1.10.4 is red: https://travis-ci.org/mvdan/unparam/builds/439236099
I've boiled it down to this piece of code: https://play.golang.org/p/vUTgArM21wJ
To reproduce, run:
cat >main.go <<EOF
package main

import (
        "golang.org/x/tools/go/packages"
        "golang.org/x/tools/go/ssa/ssautil"
)

func main() {
        cfg := &packages.Config{Mode: packages.LoadSyntax}
        pkgs, err := packages.Load(cfg, "main.go")
        if err  != nil {
                panic(err)
        }
        prog, _ := ssautil.Packages(pkgs, 0)
        prog.Build()
}
EOF
go get -d -u golang.org/x/tools/go/ssa/ssautil
go run main.go

Locally, on go version devel +165ebaf97b Sun Oct 7 02:36:02 2018 +0000 linux/amd64, the commands above succeed.
Here is the behavior with 1.10.4 - I'm using a Docker image to ensure that it's easy to reproduce for everyone. Funnily enough, I could not reproduce it on my Linux system with a binary installation of 1.10.4.
$ docker run -it golang:1.10.4-stretch bash
# [ commands above ]
# go run main.go
panic: no type for *ast.CompositeLit @ /usr/local/go/src/errors/errors.go:10:10

goroutine 967 [running]:
golang.org/x/tools/go/ssa.(*Package).typeOf(0xc4237b6060, 0x7207a0, 0xc42021d9c0, 0x0, 0x0)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2377 +0x1be
golang.org/x/tools/go/ssa.(*builder).addr(0xc4229c7d00, 0xc420098140, 0x7207a0, 0xc42021d9c0, 0x1, 0x0, 0x0)
        /go/src/golang.org/x/tools/go/ssa/builder.go:351 +0xb82
golang.org/x/tools/go/ssa.(*builder).expr0(0xc4229c7d00, 0xc420098140, 0x721020, 0xc4202346e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc420838f80, ...)
        /go/src/golang.org/x/tools/go/ssa/builder.go:603 +0x1cf2
golang.org/x/tools/go/ssa.(*builder).expr(0xc4229c7d00, 0xc420098140, 0x721020, 0xc4202346e0, 0x0, 0x0)
        /go/src/golang.org/x/tools/go/ssa/builder.go:530 +0x289
golang.org/x/tools/go/ssa.(*builder).stmt(0xc4229c7d00, 0xc420098140, 0x720d60, 0xc420234700)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2045 +0x194c
golang.org/x/tools/go/ssa.(*builder).stmtList(0xc4229c7d00, 0xc420098140, 0xc42000f4c0, 0x1, 0x1)
        /go/src/golang.org/x/tools/go/ssa/builder.go:790 +0x59
golang.org/x/tools/go/ssa.(*builder).stmt(0xc423510d00, 0xc420098140, 0x720620, 0xc4201ddcb0)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2102 +0x2646
golang.org/x/tools/go/ssa.(*builder).buildFunction(0xc423510d00, 0xc420098140)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2195 +0x2f1
golang.org/x/tools/go/ssa.(*builder).buildFuncDecl(0xc423510d00, 0xc4237b6060, 0xc4201ddce0)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2225 +0xf4
golang.org/x/tools/go/ssa.(*Package).build(0xc4237b6060)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2341 +0x7f9
golang.org/x/tools/go/ssa.(*Package).(golang.org/x/tools/go/ssa.build)-fm()
        /go/src/golang.org/x/tools/go/ssa/builder.go:2260 +0x2a
sync.(*Once).Do(0xc4237b608c, 0xc420263f98)
        /usr/local/go/src/sync/once.go:44 +0xbe
golang.org/x/tools/go/ssa.(*Package).Build(0xc4237b6060)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2260 +0x4c
golang.org/x/tools/go/ssa.(*Program).Build.func1(0xc422865c70, 0xc4237b6060)
        /go/src/golang.org/x/tools/go/ssa/builder.go:2244 +0x2b
created by golang.org/x/tools/go/ssa.(*Program).Build
        /go/src/golang.org/x/tools/go/ssa/builder.go:2243 +0x11a
exit status 2

The original panic was different; I'm pasting the start of it below. However, since both only happen on 1.10 and this is the minimised case of the original panic, I'm pretty sure they are the same bug.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x629bb6]
goroutine 1232 [running]:
golang.org/x/tools/go/ssa.(*Program).packageLevelValue(0xc425fe14a0, 0x0, 0x0, 0x90e8e0, 0x78ad40)
	/home/travis/gopath/src/golang.org/x/tools/go/ssa/source.go:189 +0x26
golang.org/x/tools/go/ssa.(*builder).expr0(0xc4200d7d00, 0xc4237b97c0, 0x78bbc0, 0xc4228b39a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc427f443e0, ...)
	/home/travis/gopath/src/golang.org/x/tools/go/ssa/builder.go:684 +0x1fce

Since it only happens on 1.10, this might be a bug in a package in the standard library like go/types. I haven't investigated further.
Unfortunately, this does make using go/packages in my tool quite painful. I'd rather not drop support for Go 1.10 just yet.
/cc @ianthehat @alandonovan

The doc comment for ssautil.Packages says "a set of packages loaded from source syntax". This is admittedly not very clear, but it means you need to use Mode: packages.LoadAllSyntax in go/packages.
Both the documentation and the way in which the error is reported could certainly be improved.

You're right; I should have noticed that. I agree that the docs could be a bit clearer, and that it would be great if ssautil errored sooner with a more obvious message.
I got confused by how this succeeded on 1.11, and failed on 1.10 under some circumstances. I guess I was getting lucky somehow.

The root cause is that go/packages' go1.10 "fallback" loads the entire program from source because go1.10 list doesn't generate export data; however, it doesn't bother to type-check function bodies of imports in this mode since the function types are all that it needs. However, the SSA builder assumes that when a package has syntax trees, they have been type checked, and consequently it panics when it finds function bodies without type information.
https://go-review.googlesource.com/c/tools/+/141686  contains a fix.

Does this mean that it's entirely reasonable for me to use LoadSyntax instead of LoadAllSyntax if I'm not interested in the SSA form of the dependencies?

Yes.


Update command does not work with Lightning Components

Steps to reproduce:

Create a lightning component with at least a controller (JS).
Update the controller.js file (located in the Lightning folder).
Execute update command.
See the output below.

Did you get deploy / upload to work? I cannot I get the same error Progress Status Failed whenever I attempt to deploy or upload a project with a Lightning Component.


Add govcloud as an isolated region

This is what we did to support GovCloud. We also added some pipeline changes but they are not backward compatible.

@dlapiduz your commit was merged here. Not sure why GitHub didn't detect the merge. Thanks for the PR!


includeCSIDE in template getbcext

I am utilizing the https://aka.ms/getbcext template so I can restore a database using the SQL Developer edition (as my backup is over 10GB)
Is there a way to get the flag to includeCSIDE in the template
Otherwise, if there is a way to see the script being used to create the container/have it connected to a SQL developer instance on the host, I would greatly appreciate it.

https://aka.ms/getnavext is for NAV and BC using C/AL - won't work for later versions of BC
I haven't tried it for a very long time.
You can also read https://freddysblog.com/2021/02/28/running-business-central-in-docker-using-sql-on-the-host/ to learn about how to run a container using SQL on the host.
There are several other blog posts on the subject on my blog.

Hi @freddydk - I was using both ARMs, so I accidently copied the wrong link in my request.
https://aka.ms/getnavext installs NAV inside a container, and connects to the database on the host VM, but there are no shortcuts for inside the container to access C/SIDE.
What I ended up doing was creating my own script to create a NAV container (on the VM), and it had the -includeCSIDE flag.
Would be nice to have that in the ARM template so we could use it without having to create our own container after the fact.

strange...
The parameter is defined here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/getnavext.json#L277
The variable is assigned here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/getnavext.json#L467
And transferred to initialize here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/getnavext.json#L1122
It is received as a parameter here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/initialize.ps1#L24
And the value is written into c:\demo\settings.ps1 here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/initialize.ps1#L128
Settings script is imported here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/SetupNavContainer.ps1#L17
The the parameter for New-NavContainer is set here: https://github.com/microsoft/nav-arm-templates/blob/c694cfde1f1495af5461f0d8242a1bb08edfaf49/SetupNavContainer.ps1#L308
So, somewhere, the chain breaks...
Could you check settings.ps1 - what is the line with includeCside - is it yes or no?
You could also try to modify c:\demo\SetupNavContainer.ps1 and insert a
$params | out-host
right before the try statement in line 363 and see what parameters are transferred to new-navcontainer?

Any more info on this?


Fill-in AFNI skull-stripping mask

See poldracklab/mriqc#552, poldracklab/mriqc#554, poldracklab/fmriprep#659.

The fully automated process consists of three steps:

Preprocessing of volume to remove gross spatial image non-uniformity artifacts and reposition the brain in a reasonable manner for convenience.
Expand a spherical surface iteratively until it envelopes the brain. This is a modified version of the BET algorithm: Fast robust automated brain extraction, by Stephen M. Smith, HBM 2002 v 17:3 pp 143-155
Modifications include the use of:

outer brain surface
expansion driven by data inside and outside the surface
avoidance of eyes and ventricles
a set of operations to avoid the clipping of certain brain areas and reduce leakage into the skull in heavily shaded data
two additional processing stages to ensure convergence and reduction of clipped areas.
use of 3d edge detection, see Deriche and Monga reference in 3dedge3 -help.

The creation of various masks and surfaces modeling brain and portions of the skull

Common examples of usage:

o 3dSkullStrip -input VOL -prefix VOL_PREFIX
   Vanilla mode, should work for most datasets.
o 3dSkullStrip -input VOL -prefix VOL_PREFIX -push_to_edge
   Adds an agressive push to brain edges. Use this option
   when the chunks of gray matter are not included. This option
   might cause the mask to leak into non-brain areas.
o 3dSkullStrip -input VOL -surface_coil -prefix VOL_PREFIX -monkey
   Vanilla mode, for use with monkey data.
o 3dSkullStrip -input VOL -prefix VOL_PREFIX -ld 30
   Use a denser mesh, in the cases where you have lots of
   csf between gyri. Also helps when some of the brain is clipped
   close to regions of high curvature.

Tips:
 I ran the program with the default parameters on 200+ datasets.
 The results were quite good in all but a couple of instances, here
 are some tips on fixing trouble spots:

 Clipping in frontal areas, close to the eye balls:
    + Try -push_to_edge option first.
      Can also try -no_avoid_eyes option.
 Clipping in general:
    + Try -push_to_edge option first.
      Can also use lower -shrink_fac, start with 0.5 then 0.4
 Problems down below:
    + Piece of cerebellum missing, reduce -shrink_fac_bot_lim
      from default value.
    + Leakage in lower areas, increase -shrink_fac_bot_lim
      from default value.
 Some lobules are not included:
    + Use a denser mesh. Start with -ld 30. If that still fails,
    try even higher density (like -ld 50) and increase iterations
    (say to -niter 750).
    Expect the program to take much longer in that case.
    + Instead of using denser meshes, you could try blurring the data
    before skull stripping. Something like -blur_fwhm 2 did
    wonders for some of my data with the default options of 3dSkullStrip
    Blurring is a lot faster than increasing mesh density.
    + Use also a smaller -shrink_fac is you have lots of CSF between
    gyri.
 Massive chunks missing:
    + If brain has very large ventricles and lots of CSF between gyri,
    the ventricles will keep attracting the surface inwards.
    This often happens with older brains. In such
    cases, use the -visual option to see what is happening.
    For example, the options below did the trick in various
    instances.
        -blur_fwhm 2 -use_skull
    or for more stubborn cases increase csf avoidance with this cocktail
        -blur_fwhm 2 -use_skull -avoid_vent -avoid_vent -init_radius 75
    + Too much neck in the volume might throw off the initialization
      step. You can fix this by clipping tissue below the brain with
             @clip_volume -below ZZZ -input INPUT
      where ZZZ is a Z coordinate somewhere below the brain.

 Large regions outside brain included:
   + Usually because noise level is high. Try @NoisySkullStrip.

Make sure that brain orientation is correct. This means the image in
AFNI's axial slice viewer should be close to the brain's axial plane.
The same goes for the other planes. Otherwise, the program might do a lousy
job removing the skull.

Did any of those options seem useful to you? Blurring at 2 didn't do much, blurring at 4 had huge chunks of skull, and -use_skull caused a crash. 3dmask_tool only partially filled in the ventricles but didn't touch the spaces between gyri.


Toaster doesn't work with nested views (ui.router)

I have a problem with my toaster, when i go to the parent view, the toaster disappears immediately.
function save(){
    return Service.updateServ()
        .then(function(){
            toaster.success('msg');
            $state.go('index.main');
        });
}

This is my partial solution, but i need to show my toaster in her parent too. Here I show the toaster, and after that the toaster is fade out, the callback go to my parent view.
toaster.success({
    title: 'msg',
    body: 'another msg',
    onHideCallback: function(){
        $state.go('index.main');
    }
 });

Sorry for not putting the code in gist, In This case copy paste was faster.
.state('index', {
    abstract: true,
    url: '/',
    templateUrl: 'components/common/content.html',
    resolve: {
        loadPlugin: function($ocLazyLoad) {
            return $ocLazyLoad.load([
                {
                    name: 'toaster',
                    files: ['../bower_components/AngularJS-Toaster/toaster.min.js',
                            '../bower_components/AngularJS-Toaster/toaster.min.css']
                }
            ]);
        }
    }
})
.state('contratantes.main', {
    url: '/anotherUrl',
    templateUrl: 'app/contratantes/contratantes.html',
})
.state('contratantes.edit', {
    url: '/:type/',
    templateUrl: 'app/contratantes/contratantes.edit.html',
})

You haven't included your <toaster-container></toaster-container>, but I suspect from the behavior you are seeing that your container element is living inside html that is being modified by state changes.  You should use one container, placed outside html that is affected by your router.

Thanks :D that's was the problem, excuse me for not answering soon.

Perfect!


🐛 Query builder load for bytea relations fails with exception

No duplicates 🥲.

[X] I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?
When an entity has a RefersTo relation with bytea key (wrapped in a ValueInterface), querying it with load will result in cycle crashing with the following exception:
[Cycle\Database\Exception\StatementException]
SQLSTATE[22021]: Character not in repertoire: 7 ERROR:  invalid byte sequence for encoding "UTF8": 0xf0 0x1f 0xc9 0x6a

Lazy loading a single relation works fine.
Version
ORM 2.0.1
PHP 8.0

Found the reason why this happening: https://github.com/cycle/database/blob/11cf9d606092b87dd0a2566021ec729abaa3713c/src/Driver/Driver.php#L488.
When the driver binds the parameter, it uses the binary value as is, which is string.
This could be resolved if we first wrap the value to its corresponding ValueInterface according to the column typecast, where we handle the rawType.
I will try to add a repro case later this week.


[in_app_purchase] App crashes on buyNonConsumable

When I call the method buyNonConsumable the app crashes. The credentials dialog is shown on my system home screen.
The error which I get is:

Unsupported value: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" of type NSError
*** Assertion failure in -[FlutterStandardWriter writeValue:], FlutterStandardCodec.mm:330
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Unsupported value for standard codec'
*** First throw call stack:
(0x186a6d9d8 0x19adf3b54 0x18697c50c 0x187c76878 0x105b3f148 0x105b3f790 0x105b3c72c 0x105066eb4 0x105064f7c 0x105b3c694 0x1052dc038 0x1055db41c 0x10557a81c 0x10557ced4 0x1869ee3e0 0x1869edfe4 0x1869ed4c4 0x1869e7850 0x1869e6ba0 0x19d74f598 0x1892d82f4 0x1892dd874 0x104a6d564 0x1866c5568)
libc++abi.dylib: terminating with uncaught exception of type NSException

thread 1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
frame #0: 0x00000001b29ac84c libsystem_kernel.dylib__pthread_kill + 8 libsystem_kernel.dylib__pthread_kill:
->  0x1b29ac84c <+8>:  b.lo   0x1b29ac868               ; <+36>
0x1b29ac850 <+12>: stp    x29, x30, [sp, #-0x10]!
0x1b29ac854 <+16>: mov    x29, sp
0x1b29ac858 <+20>: bl     0x1b2989f5c               ; cerror_nocancel
Target 0: (Runner) stopped.

I don't understand what caused this to happen, it used to work before.
There was a similar issue two years ago, but this PR seemed to have fixed it.
Am I the only one having this problem right now?
UPDATE
After more investigating it seems that everything works fine up to version 0.1.1 of in_app_purchase_ios.
0.1.1+1 seems to have introduced this bug, which is this PR

Same issue with consumables.
See issue #85960

Hi @hiddenfloret
Thanks for filing the issue, I can reproduce the crash with the latest iOS platform package added (in_app_purchase_ios: ^0.1.2+1) in the pubspec.yaml

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 12.0 21A5268h darwin-x64, locale
    en-GB)
    • Flutter version 2.2.3 at /Users/tahatesser/Code/flutter_stable
    • Framework revision f4abaa0735 (5 days ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS
      14.6
    • macOS (desktop)        • macos                     • darwin-x64     •
      macOS 12.0 21A5268h darwin-x64
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 91.0.4472.114

• No issues found!

I have the same issue when calling:
...buyNonConsumable(purchaseParam: ...)...

@stefanschaller there is currently a fix open on this issue and it should be merged soon.

@stefanschaller there is currently a fix open on this issue and it should be merged soon.

Awesome! Thanks for the fast response. Love it :D

I'm using "in_app_purchases" package and having the same issue. But seems the solution would be use the "in_app_purchases_ios". Do I have to use both packages? Why can't we have the fix on "in_app_purchase" package it self ?

@inshaf You don't have to import both packages manually as in_app_purchase_ios is already in in_app_purchase. Just keep the version of in_app_purchase in pubspec.yaml up to date.
To reset the in_app_purchase in order to have the newest one, I always delete the directory .simlinks under ios in my project and then I run the program again. Flutter will load then reload the .simlinks directory and hopefully with the newest chages. To be sure that it is using the latest in_app_purchase_ios which is 0.1.2+2 you can also check Pubspec.lock and search the version of the in_app_purchase package.

@hiddenfloret thanks for reply. I checked the "pub spec.lock" and found  "in_app_purchase_ios 0.1.2+1". But still I'm getting following error when I purchase consumable item on the sandbox.
Unsupported value: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" of type NSError
*** Assertion failure in -[FlutterStandardWriter writeValue:], FlutterStandardCodec.mm:330
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Unsupported value for standard codec'

@hiddenfloret thanks for reply. I removed .simlinks folder and ran it again. But it got "0.1.2+1".
It is not upgrading to in_app_purchase_ios to 0.1.2+2 ( I have the latest version of in_app_purchase 1.0.6 ). Not sure how to upgrade to the latest one

@inshaf Hm weird. Have you also done a pub get before running it? Usually a pub get updates for me the .lock file.
Alternatively maybe try specifying the ios package in pubspec.yaml like this: in_app_purchase_ios: 0.1.2+2
And then delete the .symlinks and build again.

@hiddenfloret I have placed "in_app_purchase_ios: ^0.1.2+2" in pubspec.yaml and now it is working :) thanks for the support


Use Bevy's parallel iterators rather than rayon

Rapier uses Rayon's parallel iterators to parallelize the engine (through the macros par_iter! and par_iter_mut!, which either calls .iter() or .par_iter() (or the mutable equivalents).
But Bevy also has parallel iterators: Query has .par_iter() and .par_iter_mut() and it uses Bevy's own runtime to parallelize the queries.
Are there plans to make use of this?
A potential issue is that QueryParIter oddly doesn't implement Iterator. In this example one sees that it's expected to write
sprites
        .par_iter_mut()
        .for_each(|(mut transform, velocity)| {
            transform.translation += velocity.extend(0.0);
        });

Rather than
for (mut transform, velocity) in sprites.par_iter_mut() {
    transform.translation += velocity.extend(0.0);
};

Which I don't know why exactly; but other than that, it seems in principle possible to have a pluggable backend for parallel iteration.
(I opened this issue here because I think it only makes sense to expose this on bevy_rapier but maybe it should be moved to the main Rapier repository)

Something like this would have to be behind a feature flag - my game makes heavy use of async task pools to the point where using par_iter in a normal system is nearly always slower than a normal iter.

Now that's interesting. Do you know why this happens? Why is rayon's threadpool faster in this case?

@dlight It's not that one thread pool is faster than another's, I'm just using a lot of threads so adding even more will just hurt performance instead of help it.

This kind of change would need quite thorough performance comparison, both for high and low amount of objects, as well as contention test (when other systems are running)


AWS support for backup storage

Currently we only support GCE ((kubernetes.io/gce-pd) PV as backup storage.
AWS support is a MUST HAVE to make etcd operator more accessible to cloud users. Specifically, we are planning to support types of storage on AWS for backup data.

EBS (kubernetes.io/aws-ebs) as PV. We have the PV code path there. It's not very hard to add support for it.
S3. We need to refactor the serverSnap() and writeSnap() path into interface and support other types of storage as well. Then we can implement S3 support for it.

Dup of #340

I can take a look at adding AWS-EBS support. On quick inspection it doesn't look terribly difficult
https://github.com/coreos/etcd-operator/blob/15cfbabda50c0a073276bbe1c6edf00fc4ec527c/pkg/util/k8sutil/backup.go#L40

Also controller currently crashes waiting on PVC poll
time="2016-11-04T22:59:02Z" level=error msg="fail to poll PVC (etcd-cluster-pvc): timed out waiting for the condition"
panic: timed out waiting for the condition

goroutine 16 [running]:
panic(0x18dc520, 0xc420101660)
	/usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/coreos/etcd-operator/pkg/controller.(*Controller).Run.func2(0xc420258180, 0xc42039df20)
	/go/src/github.com/coreos/etcd-operator/pkg/controller/controller.go:143 +0x4e4
created by github.com/coreos/etcd-operator/pkg/controller.(*Controller).Run
	/go/src/github.com/coreos/etcd-operator/pkg/controller/controller.go:154 +0x2e9

@lachie83 Can you file an issue for it separately? That is a bug we should fix.

@xiang90 @lachie83
See https://github.com/coreos/etcd-operator/issues/305

@lachie83
If you would like to fix the PVC poll issue, please let me know. Other than that, I will fix it by next week.
And sure, feel free to ping me when you have a PR for the AWS PV support.

Took a look through the code and it is already implemented via the pv-provisioner arg. I've tested and it works on AWS. The only issue is that the default deployment doesn't have it by default. LMK how you would like to handle this and I can submit a PR.
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: etcd-operator
spec:
  replicas: 1
  template:
    metadata:
      labels:
        name: etcd-operator
    spec:
      containers:
      - name: etcd-operator
        image: quay.io/coreos/etcd-operator
        command:
        - "/bin/sh"
        - "-c"
        - "/usr/local/bin/etcd-operator --pv-provisioner=kubernetes.io/aws-ebs"
        env:
        - name: MY_POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace

kubectl get pods,pvc
NAME                                READY     STATUS    RESTARTS   AGE
po/etcd-cluster-0000                1/1       Running   0          57s
po/etcd-cluster-0001                1/1       Running   0          50s
po/etcd-cluster-0002                1/1       Running   0          34s
po/etcd-cluster-backup-tool-3bj8k   1/1       Running   0          51s
po/etcd-operator-649933782-cdn1c    1/1       Running   0          2m
NAME                   STATUS    VOLUME                                     CAPACITY   ACCESSMODES   AGE
pvc/etcd-cluster-pvc   Bound     pvc-c84c344b-a31a-11e6-a2ff-0295f91dc779   1Gi        RWO           57s

@xiang90 -- Sure thing. #342

@lachie83 OK. So it seems to me that we:

have a separate deployment for AWS
make the operator smart about the infra: detect it is running on AWS. (how?)

Closed with a PR adding a AWS specific deployment file and updating readme file.


undefined local variable or method `rocket_job_mission_control' for

rocketjob_mission_control (4.3.0) app/views/rocket_job_mission_control/dirmon_entries/_form.html.erb:66:in `block in
also at
rocketjob_mission_control (4.3.0) app/views/rocket_job_mission_control/servers/index.html.erb:18
rocketjob versions:
gem 'rocketjob', '6.0.0.rc3'
gem 'rocketjob_mission_control', '4.3.0'

To use the Rocket Job v6 release candidates, please point to the RJMC code base on GitHub. We are still working on RJMC v6. As soon as we can get RJMC v6 out, we will also publish Rocket Job v6.0.
We have this line in our Gemfile:
gem "rocketjob_mission_control", git: "https://github.com/reidmorrison/rocketjob_mission_control"

Strange scenario here, when I use:
gem 'rocketjob', '5.4.1'
gem 'rocketjob_mission_control', '5.0.1'

I get:
NameError: uninitialized constant RocketJob::Plugins::Job::Model::Boolean
  load_missing_constant at /home/opentraderx/.rvm/gems/jruby-<IP_ADDRESS>/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:550
          const_missing at /home/opentraderx/.rvm/gems/jruby-<IP_ADDRESS>/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:195
                  Model at /home/opentraderx/.rvm/gems/jruby-<IP_ADDRESS>/gems/rocketjob-5.4.1/lib/rocket_job/plugins/job/model.rb:42
            module_eval at org/jruby/RubyModule.java:3255

when I use:
gem 'rocketjob', '6.0.0.rc3'
gem 'rocketjob_mission_control', git: "https://github.com/reidmorrison/rocketjob_mission_control"

I get:
couldn't find file 'jquery3' with type 'application/javascript'

Which versions of rocketjob and rocket_job_mission_control are working well with eachother?

Same error that I reported first when I use:
gem 'rocketjob', '6.0.0.rc3'
gem 'rocketjob_mission_control', git: "https://github.com/reidmorrison/rocketjob_mission_control", ref: '840a0f5de44795a30354ce4e72823bbd8c743e8a'

@reidmorrison what versions are you running in production?

@reidmorrison Any thoughts on the working version number combination for rocketjob and mission control?

This still exists, I created #83 which fixes.


Port randomly stops working.

Version
Microsoft Windows [Version 10.0.22621.1192]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04
Other Software
nginx version: nginx/1.18.0 (Ubuntu)
Repro Steps
I am unsure how to reproduce this. The issue occurs randomly and is fixed by a restart of either WSL or the application listening on the port.
Expected Behavior
The port should continue to be accessible in Windows.
Actual Behavior
Randomly, all ports become inaccessible on Windows and require me to restart the applications listening on the port.
I have both an nginx server on 80/443 that runs on startup and a NextJS (Node) http server on 3000, both of which are no longer reachable from Windows.
Within WSL, there are no issues whatsoever, in Windows, however, the requests time out (see curl logs below).
I cannot reproduce the error consistently, as it occurs after seemingly random time while working spanning from almost instantly (one request) to several minutes, after which requests suddenly time out.
Diagnostic Logs
WSL:
curl localhost
<html>
<head><title>301 Moved Permanently</title></head>
...
</html>

Windows (Git Bash):
curl localhost
curl: (7) Failed to connect to localhost port 80 after 2235 ms: Couldn't connect to server

The same holds for port 3000.

WSL:
sudo netstat -tulpn

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN      27/nginx: master pr
tcp        0      0 <IP_ADDRESS>:80              <IP_ADDRESS>:*               LISTEN      27/nginx: master pr
tcp        0      0 <IP_ADDRESS>:39603         <IP_ADDRESS>:*               LISTEN      111/node
tcp        0      0 <IP_ADDRESS>:1123          <IP_ADDRESS>:*               LISTEN      470/TabNine
tcp        0      0 <IP_ADDRESS>:49152         <IP_ADDRESS>:*               LISTEN      715/TabNine-deep-lo
tcp6       0      0 :::3000                 :::*                    LISTEN      6096/node
tcp6       0      0 :::81                   :::*                    LISTEN      -
tcp6       0      0 :::80                   :::*                    LISTEN      27/nginx: master pr
tcp6       0      0 :::8081                 :::*                    LISTEN      -
tcp6       0      0 :::8529                 :::*                    LISTEN      -
udp        0      0 <IP_ADDRESS>:323           <IP_ADDRESS>:*                           -
udp6       0      0 ::1:323                 :::*                                -

Windows Resource Monitor:
Nothing listening on :80 (:443/:3000)

Same issue here:
# wsl -v
Version WSL : <IP_ADDRESS>
Version du noyau : <IP_ADDRESS>
Version WSLg : 1.0.48
Version MSRDC : 1.2.3770
Version direct3D : 1.608.2-61064218
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
version Windows : 10.0.25284.1000

# lsb_release -a
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy

Looks like #9508 issue. Fix is in testing, according to  https://github.com/microsoft/WSL/issues/9508#issuecomment-1405903487

Thanks @elsaco
@jeengbe, this issue occurs after multiple ports are bound and subsequently one of the ports is released. Depending on the overlap of existing <port, protocol, family, address> binds the effects can vary.
/dupe #9508

@jeengbe, I forgot to mention. If you're not on WSL 1.1.0 then please re-open this issue. #9508 only applies to 1.1.0

@pmartincic Yeah that's correct.

@pmartincic I can confidently say that there are no other applications attempting to bind on the same port, if that's what you mean

I only meant to convey that the effects of the bug is variable depending on what combination of port/addresses/protocol/family are being bound in WSL. If you had port 22 bound on TCP4&6, UDP4&6 for example.


Can't build Arpack in Julia

julia> using LsqFit
[ Info: Precompiling LsqFit [2fda8390-95c7-5789-9bda-21331edee243]
ERROR: LoadError: No deps.jl file could be found. Please try running Pkg.build("Arpack").
Currently, the build command might fail when Julia has been built from source
and the recommendation is to use the official binaries from julialang.org.
For more info see https://github.com/JuliaLinearAlgebra/Arpack.jl/issues/5.

julia> Pkg.build("Arpack")
  Building Arpack → `~/.julia/packages/Arpack/cu5By/deps/build.log`
┌ Error: Error building `Arpack`:
│ ERROR: LoadError: LibraryProduct(nothing, ["libarpack"], :libarpack, "Prefix(/home/suhr/.julia/packages/Arpack/cu5By/deps/usr)") is not satisfied, cannot generate deps.jl!
│ Stacktrace:
│  [1] error(::String) at /nix/store/kh9x1nnrxmkk231nkpp952pqjknm7pnh-julia-1.0.4/lib/julia/sys.so:?
│  [2] #write_deps_file#152(::Bool, ::Function, ::String, ::Array{LibraryProduct,1}) at /home/suhr/.julia/packages/BinaryProvider/TcAwt/src/Products.jl:414
│  [3] (::getfield(BinaryProvider, Symbol("#kw##write_deps_file")))(::NamedTuple{(:verbose,),Tuple{Bool}}, ::typeof(write_deps_file), ::String, ::Array{LibraryProduct,1}) at ./none:0
│  [4] top-level scope at none:0
│  [5] include_relative(::Module, ::String) at /nix/store/kh9x1nnrxmkk231nkpp952pqjknm7pnh-julia-1.0.4/lib/julia/sys.so:?
│  [6] include(::Module, ::String) at /nix/store/kh9x1nnrxmkk231nkpp952pqjknm7pnh-julia-1.0.4/lib/julia/sys.so:?
│  [7] include(::String) at ./client.jl:392
│  [8] top-level scope at none:0
│ in expression starting at /home/suhr/.julia/packages/Arpack/cu5By/deps/build.jl:74
└ @ Pkg.Operations /build/source/usr/share/julia/stdlib/v1.0/Pkg/src/Operations.jl:1096

nix run nixpkgs.nix-info -c nix-info -m output:
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.71, NixOS, 19.09pre192418.e19054ab3cd (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3`
 - channels(root): `"home-manager, nixos-19.09pre192418.e19054ab3cd"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I believe @tbenst had some success with it in https://github.com/NixOS/nixpkgs/issues/54634#issuecomment-481785619

Yes I did indeed!

Having to use FHS is really unfortunate. I hope there's a better way.

@suhr here's a non-FHS solution:
{pkgs, stdenv, ...}:

with pkgs;
let
  julia = julia_11;
  d = version: "v${lib.concatStringsSep "." (lib.take 2 (lib.splitString "." version))}";
  extraLibs = [
    # IJulia.jl
    mbedtls
    zeromq3
    # ImageMagick.jl
    imagemagickBig
    # HDF5.jl
    hdf5
    # Cairo.jl
    cairo
    gettext
    pango.out
    glib.out
    # Gtk.jl
    gtk3
    gdk_pixbuf
    # GZip.jl # Required by DataFrames.jl
    gzip
    zlib
    # GR.jl # Runs even without Xrender and Xext, but cannot save files, so those are required
    xorg.libXt
    xorg.libX11
    xorg.libXrender
    xorg.libXext
    glfw
    freetype
    # Flux.jl
    cudatoolkit
    linuxPackages.nvidia_x11
    git gitRepo gnupg autoconf curl
    procps gnumake utillinux m4 gperf unzip
    libGLU_combined
    xorg.libXi xorg.libXmu freeglut
    xorg.libXext xorg.libX11 xorg.libXv xorg.libXrandr zlib
    ncurses5 stdenv.cc binutils
    # Arpack.jl
    arpack
    gfortran.cc
    (pkgs.runCommand "openblas64_" {} ''
      mkdir -p "$out"/lib/
      ln -s ${openblasCompat}/lib/libopenblas.so "$out"/lib/libopenblas64_.so.0
    '')
  ];
in
stdenv.mkDerivation rec {
  name = "julia-env";
  version = julia.version;
  nativeBuildInputs = [ makeWrapper cacert git pkgconfig which ];
  buildInputs = [
    julia
    /* jupyterEnv  # my custom jupyter */
  ] ++ extraLibs;
  phases = [ "installPhase" ];
  installPhase = ''
    export CUDA_PATH="${cudatoolkit}"
    export LD_LIBRARY_PATH=${lib.makeLibraryPath extraLibs}
    # pushd $JULIA_PKGDIR/${d version}
    makeWrapper ${julia}/bin/julia $out/bin/julia \
        --prefix LD_LIBRARY_PATH : "$LD_LIBRARY_PATH" \
        --prefix LD_LIBRARY_PATH ":" "${linuxPackages.nvidia_x11}/lib" \
        --set CUDA_PATH "${cudatoolkit}" \
        --set JULIA_PKGDIR $JULIA_PKGDIR
        # --set JULIA_LOAD_PATH $JULIA_PKGDIR/${d version}
  '';
}

I have this saved to /Computer/packages/julia.nix, and also have the following saved to /home/tyler/.config/nixpkgs/overlays.nix:
[
(self: super: {
  cudatoolkit = super.cudatoolkit_10_0;
  cudnn_cudatoolkit = super.cudnn_cudatoolkit_10_0;
  julia = super.callPackage /Computer/packages/julia.nix { };
})
]

Hope this helps, and appreciate any suggested improvements!

I don't need all of the other stuff, I just want to get Arpack installed so I can use Gadfly, so I wrote the following default.nix:
with import <nixpkgs> {};

stdenv.mkDerivation rec {
  name = "julia-env";
  version = julia_11.version;
  buildInputs = [
    julia_11
    arpack
    gfortran.cc
    (pkgs.runCommand "openblas64_" {} ''
      mkdir -p "$out"/lib/
      ln -s ${openblasCompat}/lib/libopenblas.so "$out"/lib/libopenblas64_.so.0
    '')
  ];
}

and using ]add Arpack in the julia within my nix-shell:
[nix-shell:~/Projects/documentation/synthetic]$ type julia
julia is /nix/store/rf86v5scp515l92gb5fff6rsjy25r2i1-julia-1.1.1/bin/julia

still yields me:
  Building Arpack → `~/.julia/packages/Arpack/zCmTA/deps/build.log`
┌ Error: Error building `Arpack`:
│ [ Info: Downloading https://github.com/JuliaBinaryWrappers/Arpack_jll.jl/releases/download/Arpack-v3.5.0+2/Arpack.v3.5.0.x86_64-linux-gnu-libgfortran4.tar.gz to /home/aloysius/.julia/packages/Arpack/zCmTA/deps/usr/downloads/Arpack.v3.5.0.x86_64-linux-gnu-libgfortran4.tar.gz...
│ ERROR: LoadError: LibraryProduct(nothing, ["libarpack"], :libarpack, "Prefix(/home/aloysius/.julia/packages/Arpack/zCmTA/deps/usr)") is not satisfied, cannot generate deps.jl!
│ Stacktrace:
│  [1] error(::String) at /nix/store/rf86v5scp515l92gb5fff6rsjy25r2i1-julia-1.1.1/lib/julia/sys.so:?
│  [2] #write_deps_file#152(::Bool, ::Function, ::String, ::Array{LibraryProduct,1}) at /home/aloysius/.julia/packages/BinaryProvider/kcGxO/src/Products.jl:414
│  [3] (::getfield(BinaryProvider, Symbol("#kw##write_deps_file")))(::NamedTuple{(:verbose,),Tuple{Bool}}, ::typeof(write_deps_file), ::String, ::Array{LibraryProduct,1}) at ./none:0
│  [4] top-level scope at none:0
│  [5] include_relative(::Module, ::String) at /nix/store/rf86v5scp515l92gb5fff6rsjy25r2i1-julia-1.1.1/lib/julia/sys.so:?
│  [6] include(::Module, ::String) at /nix/store/rf86v5scp515l92gb5fff6rsjy25r2i1-julia-1.1.1/lib/julia/sys.so:?
│  [7] include(::String) at ./client.jl:403
│  [8] top-level scope at none:0
│ in expression starting at /home/aloysius/.julia/packages/Arpack/zCmTA/deps/build.jl:74
[19:03:41] ######################################################################## 100.0%
└ @ Pkg.Operations /build/source/usr/share/julia/stdlib/v1.1/Pkg/src/Operations.jl:1075

On inspection it has downloaded Arpack in deps/usr/download and the sha256 sums match so is this more broken than before?

@karetsu you still need to use makeWrapper on julia or else it won't find libarpack

@tbenst even with my default.nix looking like the below it still happens
with import <nixpkgs> { };

let
  targets = [
    julia_11
    arpack
    gfortran.cc
    (pkgs.runCommand "openblas64_" { } ''
      mkdir -p "$out"/lib/
      ln -s ${openblasCompat}/lib/libopenblas.so "$out"/lib/libopenblas64_.so.0
    '')
  ];
in stdenv.mkDerivation rec {
  name = "julia-env";
  version = julia_11.version;
  nativeBuildInputs = [ makeWrapper ];
  buildInputs = targets;
  installPhase = ''    export LD_LIBRARY_PATH=${lib.makeLibraryPath targets}
    makeWrapper ${julia}/bin/julia $out/bin/julia \
      --prefix LD_LIBRARY_PATH : "$LD_LIBRARY_PATH" \      --prefix JULIA_PKGDIR $JULIA_PKGDIR
  '';
}

@tbenst my bad, I was using nix-shell rather than nix-build. Building it then dropping into the shell works fine. Consider the previous comment redacted.

@karetsu also note that you may want to specify julia_11 and not wrap julia (1.0). Did you get it working? if so please post for others, thanks!

@tbenst yes, it even worked with julia (not just julia_11) and I'm now happily using gadfly. I did notice that after the nix-build type julia still was odd so the steps I went through were the following:

created default.nix with the content posted below
run nix-build in the directory it was created in
run /nix/store/*julia-env/bin/julia
]add Gadfly
using Gadfly (make sure everything is all compiled and nice)

After this I did not need to use julia-env which was in /nix/store/ but ofc should I want to change minor version of julia at some point I would need to use it again to recompile Arpack.jl
default.nix
with import <nixpkgs> { };

let
  extraLibs = [
    arpack
    gfortran.cc
    (pkgs.runCommand "openblas64_" { } ''
      mkdir -p "$out"/lib/
      ln -s ${openblasCompat}/lib/libopenblas.so "$out"/lib/libopenblas64_.so.0
    '')
  ];
in stdenv.mkDerivation rec {
  name = "julia-env";
  version = julia.version;
  nativeBuildInputs = [ makeWrapper cacert git pkgconfig which ];
  buildInputs = [ julia_11 ] ++ extraLibs;
  phases = "installPhase";
  installPhase = ''
    export LD_LIBRARY_PATH=${lib.makeLibraryPath extraLibs}
    makeWrapper ${julia}/bin/julia $out/bin/julia \
        --prefix LD_LIBRARY_PATH : "$LD_LIBRARY_PATH" \
        --set JULIA_PKGDIR $JULIA_PKGDIR
  '';
}

I'm certain this is not the idiomatic nix way to do it but all I needed was a compiled Arpack and then everything else is suitable within my standard julia install.

hmm you really want the two versions to match, or else you may have undefined behavior where julia 1.0 and 1.1 differ:
with import <nixpkgs> { };

let
  extraLibs = [
    arpack
    gfortran.cc
    (pkgs.runCommand "openblas64_" { } ''
      mkdir -p "$out"/lib/
      ln -s ${openblasCompat}/lib/libopenblas.so "$out"/lib/libopenblas64_.so.0
    '')
  ];
in stdenv.mkDerivation rec {
  name = "julia-env";
  version = julia.version;
  nativeBuildInputs = [ makeWrapper cacert git pkgconfig which ];
  buildInputs = [ julia_11 ] ++ extraLibs;
  phases = "installPhase";
  installPhase = ''
    export LD_LIBRARY_PATH=${lib.makeLibraryPath extraLibs}
    makeWrapper ${julia_11}/bin/julia $out/bin/julia \
        --prefix LD_LIBRARY_PATH : "$LD_LIBRARY_PATH" \
        --set JULIA_PKGDIR $JULIA_PKGDIR
  '';
}

ah yes, that was a typo sorry (tried changing it back to _11 for posting) but I would think that those who would do it properly will use this as their daily driver version of julia so yours should be the one used.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-can-we-build-a-julia-derivation-with-tests-disabled/8052/1

LsqFit installs cleanly and with tests passing on v1.0.5, v1.5.4, and v1.6.1. It does not work on v1.0.4, but it is marked as insecure and should be replaced anyway with v1.0.5 which will work. Closing as this most likely was somehow resolved upstream in the Julia package ecosystem. My personal guess is that we have JLLs to thank.


chore: remove unnecessary stack trace log when adding services

Issue #, if available:
aws-amplify#4283
Description of changes:
The unnecessary stack traces that were displayed through the console when a user tried to run amplify add  without initializing amplify first was because of a lacking try/catch block which displays only the error message, so I added that onto the parts where the addition of services was being called.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Some things to note about the implementations and the results:

This solution didn't seem to work for amplify add function or amplify add hosting. I believe there should be some extra steps towards making sure that works, but I wasn't able to find them.
I wasn't really sure on how I would go about testing this solution, given that it's related console output.

With regards to writing tests:
You may be able to write tests which call executeAmplifyCommand() and pass in some context object that you manually create. Since context.print.error() is called whenever an error message is printed to the console, you could create a mock error() function on your custom context object, then spy on when that mock function is called and what arguments it's called with.
For example, your tests could create a mock context object that looks something like this:
const mockContext = {
  ...
  print: {
    error: jest.fn(),
  },
  ...
};

then pass that mock context object into executeAmplifyCommand() in your test and spy on the outcome like:
it('...', async () => {
  ...
  await executeAmplifyCommand(mockContext);
  expect(mockContext.print.error).toHaveBeenCalledTimes(1);
  ...
});

Other test files throughout the repo test for expected console output this way. This is also how I tested for console output in #4 , but I haven't gotten feedback on that PR yet, so I'm not sure if this is the best way to do this or not.
What do others think about this?

Ahh makes sense, I forgot to check other files to see similar applications on getting that tested, thank you for pointing that out!
Yeah, that's why I haven't left a review on your PR, I want to make sure I have a better understanding of the tests that we create.

This pull needs to target aws-amplify/amplify-cli master.
Also, it seems like there's a lot of duplicate code here. Is this a good time to refactor that?

This pull needs to target aws-amplify/amplify-cli master.
Also, it seems like there's a lot of duplicate code here. Is this a good time to refactor that?

Yep, I added the repeated code as an initial version for the PR. After getting in contact with Ammar today I was able to learn about the specific file that handles all command input, so I'm going to refactor this code and see how I can abstract that try/catch logic.


Selective sync

Adds selective sync. This is a workflow requested by the Sloan Digital Sky Survey researchers at Berkeley Lawrence Lab.
New features added:

dat clone <key> --empty : will create a sparse archive and won't download any files by default.
dat sync <dir> --select=<remote-file>,<remote-file>,<remote-file>: will download remote files with the selected names
OR
dat sync <dir> --select=<local-file-list.txt> will parse the file and download all files listed (separated by newlines)

For example, check out this short video for a demo: https://www.dropbox.com/s/ih0pu1wqt2c1h9b/selective-sync-demo.mov?dl=0
Things this PR doesn't do yet:

Have nice error messages if the file doesn't exist remotely (e.g., in case of typo). Right now it just skips it.
tests

Sweet!
This looks good. The only concern I have is that this is stateless. If you run:
dat sync --select=my-file.txt

Every time you want to update my-file then you have to make sure to include it again. If you run dat sync accidentally or without specifying the file:
dat sync

Then it'll download everything.
In my mind this was a blocker before with the selective sync. Do you think we should be worried about this?
We could make it stateful by adding a .datdownload or similar file to track what files to keep in sync.

@karissa What if you want to sync a remote file named file.txt compared to only syncing file names in a local file called `file.txt? How would you distinguish between the two?

Want this feature so bad :) I think we should use Beaker style filters dat://{key}/{folder}/{file}

In general this looks solid 👍 👍 👍

@ralphtheninja yeah i think you bring up a good point, but I agree with @joehand that perhaps having some state file (like .datdownload) would make even more sense, so that later 'dat sync' commands would respect the same parameters.

OK I made some changes so now:

select-from-file allows you to provide a file. It defaults to '.datdownload' so that multiple dat sync commands will follow the same parameters.
Windows-style newlines will work.

It'd be cool to put a message after dat clone --empty on how to use it:
❯ dat clone datproject.org/rmg/librariesio-csv . --empty
Dat successfully created in empty mode. Download files using pull or sync.

@joehand It already gives that message on clone. Or what kind of message were you thinking?

@joehand It already gives that message on clone. Or what kind of message were you thinking?

Ya just some more instruction on how to use the selective stuff:
❯ dat clone datproject.org/rmg/librariesio-csv . --empty
Dat successfully created in empty mode. Select which files to download with dat sync:

dat sync --select=readme.md,my-data.csv

Or create a /.datdownload file with your file list:

readme.md
my-data.csv

And run `dat sync`.

Part of the issue was that dat pull doesn't work with selective so that message is a bit misleading right now.

Now the UI looks like this when trying to download something that doesn't exist:


Resolve unnecessary circular dependencies in code (#2716)

Very interesting! I’m currently on vacations, but I’ll take a look as soon as i can.

These are actually the simplest and tiniest code changes :-)
The problem originated mainly in old legacy code (Knex.raw()) which carried the bad design from the past.

Ok, so this didn't seem to change anything about the fact how formatter and dialect builder IIRC calls each other back and forth. But nevertheless this is a good fix too 👍

Yes, it's not about the dialects yet, but it allows for a much easier (and robust) rollup.
It can now properly resolve imports for the core of knex, and as you know that you are using a specific dialect in your code - you can specify the path to the specific dialect to include as a "dynamic module" (https://github.com/rollup/rollup-plugin-commonjs/pull/331).
So the core of knex gets rolled-up with no problem - and allowing optimizations, tree-shaking etc, and the dialect which is user-configurable anyway stays user configurable.
There is probably more refactoring that can be done to make the hierarchy in the code cleaner


Skill resetted after death even when "Reset on Death" disabled.

When got killed or death by any means then respawn, the skill were gone (include specialities) and must unlock first speciality again even with "Reset on Death" disabled. The skills should be keep even after death.

Game Version: 1.18.2
Forge Version: 40.2.0
Mod Version: betterleveling-1.18.2-0.6.1

Hey thank you for submitting your issue. I'm gonna try to reproduce it today.
Just to note, some unexpected behaviour can occur if your config file is broken.
Can you try deleting your configs to see if this fixes your problem?
Configs are located in your world save folder inside the serverconfig folder.

Fixed in 0.6.2