Integrate the search functionality with the datahub api end point

User Story
As a developer, facilitate the implementation of search functionality to link with the datahub, retrieving a list of tables.
Value / Purpose
The central aim is to empower users with the capability to search and locate items effectively.
Hypothesis
Enabling this functionality will aid in testing the connection to the datahub and obtaining the desired search results.
Proposal

Implement search functionality by directly calling the datahub API for initial results.
Optionally, consider using a Python library for ease, so to integrate it into the FastAPI layer later.
** Note: Following is not necessary but for later**
a. Develop a dedicated endpoint in FastAPI to handle the search functionality.
b. Invoke the Python function from the created endpoint to ensure seamless integration.
Keep the approach flexible, allowing for iterative improvements and adjustments as needed.

Definition of done

[ ] Functional search capability intended for utilised in the frontend.

DatahubGraph docs:
https://datahubproject.io/docs/python-sdk/clients#datahub.ingestion.graph.client.DataHubGraph
get_search_results(start=0, count=1, entity='dataset')
Parameters:
start (int)
count (int)
entity (str)

We can also drop down to the GraphQL layer with
execute_graphql(query, variables=None)
Parameters:
query (str)

variables (Optional[Dict])

The endpoint we want to be using is https://datahubproject.io/docs/graphql/queries/#searchacrossentities
We will need to pass in filter information, sort order, pagination information.
We should expect to get back

search results
total number
search suggestions
some aggregations (TBC)

There are some search options here - will start with the defaults though
https://datahubproject.io/docs/graphql/inputObjects#searchflags

Can test GraphQL queries here https://demo.datahubproject.io/api/graphiql

I'm planning to make the search method reasonably flexible (i.e. return a lot of details about each search result) so we can experiment with the frontend side, and then we can remove stuff we don't need later to optimise the query.
Some reckons

Search results could return datasets or data products
Search results should include every property that we set when registering data products & tables
Search results should return edited descriptions if available (see editableProperties field)
Search results should contain any breadcrumb information (list of names and urns)
The query should return everything needed to render pagination

Here's a starter query that combines dataset results with data product results
Request
            {
                searchAcrossEntities(
                    input: {types: [DATASET,DATA_PRODUCT], query: "*", start: 0, count: 10}
                ) {
                    start
                    count
                    total
                    searchResults {
                    entity {
                        type
                        ... on Dataset {
                            urn
                            type
                            platform {
                                name
                            }
                            name
                            properties {
                                name
                                qualifiedName
                                description
                                customProperties {
                                    key
                                    value
                                }
                                created
                                lastModified
                            }
                            editableProperties {
                                description
                            }
                            browsePathV2 {
                                path {
                                    name
                                    entity {
                                        urn
                                    }
                                }
                            }
                            tags {
                                tags {
                                    tag {
                                        urn
                                        properties {
                                            name
                                            description
                                        }
                                    }
                                }
                            }
                            lastIngested
                            domain {
                                domain {
                                    urn
                                    id
                                    properties {
                                        name
                                        description
                                    }
                                }
                            }
                        }
                        ... on DataProduct {
                            urn
                            type
                            properties {
                                name
                                description
                                customProperties {
                                    key
                                    value
                                }
                                numAssets
                            }
                            domain {
                                domain {
                                    urn
                                    id
                                    properties {
                                        name
                                        description
                                    }
                                }
                            }
                            tags {
                                tags {
                                    tag {
                                        urn
                                        properties {
                                            name
                                            description
                                        }
                                    }
                                }
                            }
                        }
                    }
                    }
                }
            }

Response
{
  "searchAcrossEntities": {
    "start": 0,
    "count": 10,
    "total": 10000,
    "searchResults": [
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:6cc5cbc4-c002-42c3-b80b-ed55df17d39f",
          "properties": {
            "name": "Use of force",
            "description": "Prisons in England and Wales are required to record all instances of Use of Force within their establishment. Use of Force can be planned or unplanned and may involve various categories of control and restraint (C&R) techniques such as physical restraint or handcuffs.\n\nPlease refer to [PSO 1600](https://www.gov.uk/government/publications/use-of-force-in-prisons-pso-1600) for the current guidance.",
            "customProperties": [],
            "numAssets": 7
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:3dc18e48-c062-4407-84a9-73e23f768023",
              "id": "3dc18e48-c062-4407-84a9-73e23f768023",
              "properties": {
                "name": "HMPPS",
                "description": "HMPPS is an executive agency that carries out sentences given by the courts, in custody and the community, and rehabilitates people through education and employment."
              }
            }
          },
          "tags": {
            "tags": [
              {
                "tag": {
                  "urn": "urn:li:tag:custody",
                  "properties": {
                    "name": "custody",
                    "description": "Data about prisons and prisoners. Not just NOMIS!"
                  }
                }
              }
            ]
          }
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:common-platform",
          "properties": {
            "name": "common-platform",
            "description": null,
            "customProperties": [],
            "numAssets": 231
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": null
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:contracts",
          "properties": {
            "name": "contracts",
            "description": null,
            "customProperties": [],
            "numAssets": 18
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:edc1ed2e-b5b2-4a0f-a8d1-ce123d2ebd3c",
              "id": "edc1ed2e-b5b2-4a0f-a8d1-ce123d2ebd3c",
              "properties": {
                "name": "HR",
                "description": null
              }
            }
          },
          "tags": null
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:delius",
          "properties": {
            "name": "delius",
            "description": null,
            "customProperties": [],
            "numAssets": 496
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": null
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:f3416fac-2ad1-4b61-9a92-fbcb48649bc3",
          "properties": {
            "name": "External movements",
            "description": "Data from Book a Secure Move - movements to and from prisons. This includes transfers between prisons, court appearances, release on temporary license (RoTL), movements to and from police custody and any other type of movement supported by the BaSM service.\n\nA **movement** will involve one or more **journey**, each with a \"from\" and \"to\" location (prison, police station, court etc.). Journeys have **people** associated with them, and people have a **profile**. [Movements](https://datahub.apps-tools.development.data-platform.service.justice.gov.uk/dataset/urn:li:dataset:(urn:li:dataPlatform:glue,hmpps_book_secure_move_api_prod.moves,PROD)) and [journeys](https://datahub.apps-tools.development.data-platform.service.justice.gov.uk/dataset/urn:li:dataset:(urn:li:dataPlatform:glue,hmpps_book_secure_move_api_prod.journeys,PROD)) will trigger several **events**.\n\nNote that movements will include remand or unsentenced prisoners.",
            "customProperties": [],
            "numAssets": 10
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:3dc18e48-c062-4407-84a9-73e23f768023",
              "id": "3dc18e48-c062-4407-84a9-73e23f768023",
              "properties": {
                "name": "HMPPS",
                "description": "HMPPS is an executive agency that carries out sentences given by the courts, in custody and the community, and rehabilitates people through education and employment."
              }
            }
          },
          "tags": {
            "tags": [
              {
                "tag": {
                  "urn": "urn:li:tag:custody",
                  "properties": {
                    "name": "custody",
                    "description": "Data about prisons and prisoners. Not just NOMIS!"
                  }
                }
              }
            ]
          }
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:family_derived",
          "properties": {
            "name": "family_derived",
            "description": null,
            "customProperties": [],
            "numAssets": 6
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": null
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:familyman",
          "properties": {
            "name": "familyman",
            "description": null,
            "customProperties": [],
            "numAssets": 36
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": null
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:familyman_cases",
          "properties": {
            "name": "Family court cases",
            "description": "Data from FamilyMan - the Family Courts case management system.\n\nContains data on **cases**, **people** and the **events** associated with cases.",
            "customProperties": [
              {
                "key": "product-source",
                "value": "datahub-cli-test"
              }
            ],
            "numAssets": 3
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": {
            "tags": [
              {
                "tag": {
                  "urn": "urn:li:tag:court",
                  "properties": null
                }
              },
              {
                "tag": {
                  "urn": "urn:li:tag:adoption",
                  "properties": null
                }
              },
              {
                "tag": {
                  "urn": "urn:li:tag:test",
                  "properties": {
                    "name": "test",
                    "description": "dsffsd"
                  }
                }
              }
            ]
          }
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:fines_enforcement",
          "properties": {
            "name": "fines_enforcement",
            "description": null,
            "customProperties": [],
            "numAssets": 8
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": null
        }
      },
      {
        "entity": {
          "type": "DATA_PRODUCT",
          "urn": "urn:li:dataProduct:mags_curated",
          "properties": {
            "name": "mags_curated",
            "description": null,
            "customProperties": [],
            "numAssets": 12
          },
          "domain": {
            "domain": {
              "urn": "urn:li:domain:8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "id": "8bc42de3-eba1-4fdc-8842-17a0d4d0fda3",
              "properties": {
                "name": "HMCTS",
                "description": "HM Courts and Tribunals Service is responsible for the administration of criminal, civil and family courts and tribunals in England and Wales."
              }
            }
          },
          "tags": null
        }
      }
    ]
  }
}

Missing functionality from ingestion:

Owners and maintainers (see https://datahubproject.io/docs/graphql/enums/#ownershiptype)
Custom properties (dpiaRequired, retentionPeriod, email, version)


Cap on pop

Great program. This could be useful.
You may need to add a cap on pop.
I get results like this:
C200DBD-9
C967DFH-3
What TL modifier is used for starport X?
I get:
X7B6778-9
Cheers
/P-O

Looks like the DMs for Starport got cut out.
Will take a look at planet populations.
Thanks.

Now that I think about it. I'm just gonna remove as much of the Traveller 5.10 code as I can, since most of it doesn't make any sense for Common Traveller.


Restrict search hits base on one field

I want to know how I can restrict hits to doesn't show if isConfirmed equal to zero
How I can do that?

Hey @mahdi-gh1373,
search.addWidget(
  instantsearch.widgets.configure({
    filters: 'isConfirmed > 0',
  });
);

Configure is a widget you can use to add arbitrary filters to the search without displaying it in any way.
Please reopen if that wasn't what you expected


Replace minquery library by a simple cursor marshall/unmarshal

minquery is only used for serializing / de-serializing bson.
It is fairly easy to do within mgo-cursor-pagination and would remove a dependency.

done


SocialAuth afterLogin Event

I have the need for an afterLogin event to be dispatched from the SocialAuth plugin and I've partially implemented it. Before I open a pull request with my updates I was wondering if this was something you may be interested in...

Sounds good.


Pattern fingerprint doesn't work on some smarts patterns

Description:

RDKit Version: '2017.09.1.dev1'
Platform: osx

The specified SMARTS pattern below generates probe bits that filter out true matches.

import os
from rdkit import Chem, RDConfig
from rdkit.Chem import AllChem
from rdkit import DataStructs

# this works
# core = Chem.MolFromSmarts('CCCCOC')

core = Chem.MolFromSmarts('[#6;$([#6]([#6])[!#6])]')
v = AllChem.PatternFingerprint(core, 2048)

for mol in Chem.SDMolSupplier(os.path.join(RDConfig.RDDataDir,
                                           'NCI', 'first_200.props.sdf')):
    match = mol.HasSubstructMatch(core)
    if match:
        assert DataStructs.AllProbeBitsMatch(v, AllChem.PatternFingerprint(mol, 2048))

Duplicates #1496

After encountering exactly the same problem with exactly the same input (funny "coincidence" that) I created the simplified bug report

I had forgotten about that bug report :)


movercontroller namespace

About the PR
No code changes apart from whitespace
Giving these files the Project Zero Warning treatment but I don't want to do the namespace changes on the same PR as the code update

but I don't want to do the namespace changes on the same PR as the code update

Why not just do the namespace change in a separate commit?

but I don't want to do the namespace changes on the same PR as the code update

Why not just do the namespace change in a separate commit?

I did that the last time, and apparently that still isn't always easy to review or something

but I don't want to do the namespace changes on the same PR as the code update

Why not just do the namespace change in a separate commit?

I did that the last time, and apparently that still isn't always easy to review or something

It's only difficult if you're looking at the entire PR diff instead of the commit diffs.

It's only difficult if you're looking at the entire PR diff instead of the commit diffs.

Why not just do the namespace change in a separate commit?

We usually squash merge, so the separate commit would get lost when merging a PR into master.
This way we keeps the file history readable.

It's only difficult if you're looking at the entire PR diff instead of the commit diffs.

..

That's just skill issue on Sloth's part if he doesn't know how to look at commit diffs.

Why not just do the namespace change in a separate commit?

We usually squash merge, so the separate commit would get lost when merging a PR into master. This way we keep the file history readable.

There's no reason why you'd have to squash the entire PR. You can squash all commits except the one with the namespace change, so you end up with 2 commits.


chore: Update release version

Pull Request
Description
PR contains the version update of LPVS for the new release 1.3.0.
Fixes #352
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code cleanup/refactoring
[X] Documentation update
[ ] This change requires a documentation update
[ ] CI system update
[ ] Test Coverage update

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (6600bd2) 91.36% compared to head (0c98250) 91.34%.
Report is 4 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #361      +/-   ##
============================================
- Coverage     91.36%   91.34%   -0.02%
+ Complexity      478      475       -3
============================================
  Files            49       48       -1
  Lines          1609     1606       -3
  Branches        194      194
============================================
- Hits           1470     1467       -3
  Misses           82       82
  Partials         57       57

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Framework] Native function support deriving multi-sign address

rooch_framework::bitcoin_address{
  public native fun derive_taproot_multisign_public_key(public_keys: &vector<vector<u8>>, threshold: u64): vector<u8>;
    public native fun derive_taproot_address(taproot_public_key: &vector<u8>): BitcoinAddress;
}

#2294

public native fun verify_bitcoin_address_with_public_key(addr: &BitcoinAddress, pk: &vector): bool;

Secp256k1 public key can be converted to bitcoin p2tr and p2pkh. Should it be handled for all cases or just p2tr and p2pkh addresses from the public key bytes?

  public native fun verify_bitcoin_address_with_public_key(addr: &BitcoinAddress, pk: &vector<u8>): bool;

Secp256k1 public key can be converted to bitcoin p2tr and p2pkh. Should it be handled for all cases or just p2tr and p2pkh addresses from the public key bytes?

To verify it, convert the pk bytes to the bitcoin address (address type unknown at the time) and check if it's the same address with the first address param.

The native function definition is changed. #2294

The native function definition is changed. #2294

I will change it to derive_taproot_multisig_public_key instead of multisign as I will use multisig2 rust lib to achieve this feature.


bump neato pybotvac version

#Description:
As per https://github.com/stianaske/pybotvac/issues/30, pybotvac had issues with non-US locales.
This was fixed, and delivered into version 0.0.15.
https://github.com/stianaske/pybotvac/releases/tag/v0.0.15
Checklist:

[x] The code change is tested and works locally.
[pending CI] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[N/A-trivial] I have followed the development checklist

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[?] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[N/A] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[N/A] Tests have been added to verify that the new code works.

Hi @fermulator,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

https://github.com/home-assistant/home-assistant/pull/25250 bumps the version and adds additional support as well.

Duplicate of #25200

Closing this as we merged #25200


No callback of finshed offline map package

I cannot verify that an offline map package is downloaded, since there is no callback when the package has the state completed.

Hi,
You could handle this event event EventHandler OfflinePackProgressChanged;
public void OfflinePackProgressDidChange(OfflinePack pack)
        {
            var expected = (float)pack.Progress.CountOfResourcesExpected;
            float percentage = 0;
            if (expected > 0)
            {
                percentage = (float)pack.Progress.CountOfResourcesCompleted / expected;
            }
            System.Diagnostics.Debug.WriteLine($"Progress: {percentage}");
            if (pack.State == OfflinePackState.Completed)
            {
                System.Diagnostics.Debug.WriteLine("Download completed");
            }
        }

Cheers.


[zh] Deep learning

finished translation up to line 20, suggestions are welcomed, especially for line 9 as I usually just remember the original English words . Also, I'm not sure if I had the word "Dropout" translated well-enough(again this is something I just know intuitively when I first saw the English word, but not sure if I chose the word appropriate for the formal writing for the translation)

Hi @E-Coli-BW, thank you for your help, however this cheatsheet has already been translated in #12. If you want, you could instead review the latter translation or start one that has not been touched yet (convolutional-neural-networks.md, recurrent-neural-networks.md or deep-learning-tips-and-tricks.md).


sinowealth: fix all devices being detected as generic device

Hot-fix.
I did not notice that the logic was inverted when I replaced strncmp with strneq, and I didn't test it, oops.
I guess that's exactly the reason why strneq is more safe. :D

merged, thanks!


Void method result used

I have a class Foo with several methods. Some return built-in types (bool, string), others return objects (class Bar).
It seems like when prophesizing Foo, this plugin works for the methods that return built-in types but not objects with a custom class, or methods that return void.
$foo = $this->prophet->prophesize(Foo::class);
$foo->exampleReturnsBool()->willReturn(FALSE); // works great
$foo->exampleReturnsBar()->willReturn(new Bar); // PhpStorm complains "method willReturn not found in Bar"
$foo->exampleReturnsVoid()->shouldBeCalled(); // PhpStorm complains "void method exampleReturnsVoid result used"

The second case may have been fixed since this was posted. (It works fine in my testing.) But I still see "PhpStorm complains "void method exampleReturnsVoid result used" in the third case.
I'm using v7.1 of the plugin in PhpStorm 2022.3.3 with the following library versions:
$ composer info \*phpunit/phpunit; composer info \*phpspec/prophecy; composer info \*phpspec/prophecy-phpunit
phpunit/phpunit 9.6.6 The PHP Unit Testing framework.
phpspec/prophecy v1.17.0 Highly opinionated mocking framework for PHP 5.3+
phpspec/prophecy-phpunit v2.0.1 Integrating the Prophecy mocking library in PHPUnit test cases

I tested with these classes:
<?php

namespace Example;

class Foo
{
    public function exampleReturnsBool(): bool {
        return true;
    }

    public function exampleReturnsBar(): Bar {
        return new Bar();
    }

    public function exampleReturnsVoid(): void {
    }
}

<?php

namespaceExample;

class Bar
{
}

<?php

namespace Example;

use PHPUnit\Framework\TestCase;
use Prophecy\PhpUnit\ProphecyTrait;

class ExampleTest extends TestCase {

  use ProphecyTrait;

  public function testSomething(): void {
    $foo = $this->prophesize(Foo::class);
    $foo->exampleReturnsBool()->willReturn(FALSE); // works great
    $foo->exampleReturnsBar()->willReturn(new Bar); // works great
    $foo->exampleReturnsVoid()->shouldBeCalled(); // PhpStorm complains "void method exampleReturnsVoid result used"
  }

}

Confirmed, I think the void return type is the only troublemaker now. Updated the issue title to match.
Also, it seems like much of this plugin has been baked into PhpStorm itself, maybe we need to follow this bug: https://youtrack.jetbrains.com/issue/WI-68395/Do-not-report-Void-method-result-used-for-PhpSpec-Prophecy-test-calls


Os change

❗  EMBArk is changing to Ubuntu:jammy (Ubuntu 22 LTS).
To make containerization and development easier, Kali-Linux will no longer be the base OS for testing and development.
What kind of change does this PR introduce?

Python version changed from 3.9 to 3.10
dependencies are customized for ubuntu:jammy
server directory changed to /var/www
other minor additions

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

⚠ Python version changed to 3.10 : pipenv must be updated/rebuild
⚠ reinstallation required
❗ ⚠ newer kali-linux versions no longer actively supported ❗

Other information:
https://github.com/e-m-b-a/emba/pull/258

looks good. Please check the notes. I will do another functionality check and then we are set good to go

Hello Benedikt,
I tried the EMBArk installation on Ubuntu 22.04 LTS, it was a new installaton and I manually installed python3.9 before I started the EMBArk installer with -d.
During the installation I got some errors, please see the attachments:

I am not sure, maybe I tried too early the installation on Ubuntu, but I wanted to share with you my experiences.
Best regards,
torabi

Hi @torabi12 ,
I'm guessing you tried the embark:main branch?
Once this PR is merged the installation EMBArk should work as expected.
Sorry 😅
Switching to ubuntu was more complicated than expected

Hello Benedikt,
I installed Ubuntu 22.04 LTS with default parameters in VMWare Workstation and I added python3.9 with these comands:
$ sudo apt update
$ sudo apt install software-properties-common
$ sudo add-apt-repository ppa:deadsnakes/ppa
$ sudo apt install python3.9
and the basic EMBArk installation came:
$ git clone https://github.com/e-m-b-a/embark.git
$ cd embark
$ sudo ./installer.sh -d
Without python3.9 I got other errors but now I don't know how to fix the actual issues:)
If python3.9 is needed for EMBArk can you put a verification into the installer and download it automatically within EMBArk installation? I thin Ubuntu does not contain this by default.
If I can try another branch please let me know how to do it and I will try another installation as well.
Regards,
torabi

@torabi12
git clone https://github.com/BenediktMKuehne/embark -b os-change
Feel free to note any issue you encounter.

Hello Benedikt,
I installed this morning EMBArk using your source:
https://github.com/BenediktMKuehne/embark
there were some minor warnings during the instalation, please verify them which one is valid or needs modification. I insert the images like in the command line from up to down starting from IF20_cve_search part:

This is displayed 3 times in this section.
And the last one:

I did a short scan with EMBArk to see the basic functions:

but the scan stopped at 85% and didn't move:

This has never happened before with me. I was waiting and I stopped the process:

Please review the above events which one is valid.
May I do the same test on
https://github.com/e-m-b-a/embark.git
?
Regards
torabi

Hi,
at this point I'm not bothering with pip-warnings to much, as long as the modules work. (There is to much changing right now)
There apparently is also a general issue with python-pip and the setup.py, which is unrelated to EMBArk.
The dbus-error could be related to EMBAs new status-bar.
Looks like a bug
Are you on a desktop or a server-version of ubuntu 22.04 LTS ?
If you could open a issue in EMBA that'd be helpful.
Regarding the report:
Yes, currently user-input gets filtered.
In the future I'll remove the EMBA-flags with direct user-input completely.
Reason being unfiltered user-input (direct command-injection) was possible.
I know it's a bit annoying right now. Sorry 🤷
Thanks for the feedback

I also checked the main branch:
git clone https://github.com/e-m-b-a/embark.git
The error you have mentioned I think came:

and the installation stopped at the point:

Looks like the installation is terminated.

I tried the main branch also and the installation went through but the EMBArk start looks bad:

during the installation I think you have mentioned this error already:


kjwang/Fix TUP-21205 Remove CryptoHelper (Update daikon version)

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TUP-21205
What is the new behavior?
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:


Update Poseidon

There are unfinished things, but I opened a PR to initiate discussion.
Topics to discuss:

As stated in this comment, we should generate some constants for commonly used curves. I created a few for the bn254 curve for width 3 and 5, and I think we should generate more until we make a rust version of (https://extgit.iaik.tugraz.at/krypto/hadeshash/-/blob/master/code/generate_parameters_grain.sage)
Update: We could add constants for the width of 8 and support for 1-7 inputs with padding. That way we could have one set of constants for multiple input widths? Not sure if I understood the purpose of padding correctly...

@weikengchen mentioned that this impl will be reconciled with a sponge version. Does that mean they would have the same copy of the code or merged completely?

Converting bytes to field types (https://github.com/webb-tools/crypto-primitives/blob/test-poseidon/src/crh/poseidon/mod.rs#L155-L161). I expected to_field_elements to have the same results as the code below. Same for https://github.com/webb-tools/crypto-primitives/blob/test-poseidon/src/crh/poseidon/constraints.rs#L104-L120

Followed up with the discussion

Yes. I am thinking about making one. One of the reasons is that I am not sure whether the use of grain_sr_generator in the Poseidon script is the most standardized way to generate random parameters---I would instead use SHA256. There may be some considerations on the choice of parameters, e.g., having an MDS matrix that is circular.

Ideally, CRH and likely PRF would map to the sponge and the permutation part in ark-sponge for Poseidon, Rescue.

Regarding that one, I look over the code and feel we may need a more flexible implementation that does not assume the field size---32 * 8 = 256 and would be larger than 254---thus enabling many collisions when the curve is bn254.

But, basically, in sum, many changes may still occur in the Poseidon hash function.

The ark-sponge may still need a little bit of time.

One of the reasons is that I am not sure whether the use of grain_sr_generator in the Poseidon script is the most standardized way to generate random parameters---I would instead use SHA256.

FWIW, we are using Grain for the instantiation in Zcash Orchard. (If I were the Poseidon designers I would also have used SHA-256 or BLAKE2, if only to avoid "What's this Grain thing?" questions. But I think there's absolutely no problem in using Grain.)

One question: what is the identity hash?

@weikengchen I think the identity hash is just the identity function for the case when you have used a separate hash function already to generate a leaf for the tree.

Since CanonicalDeserialize is not implemented for &[Uint8], and I need it here: https://github.com/webb-tools/crypto-primitives/blob/test-poseidon/src/crh/poseidon/constraints.rs#L98 I stayed with to_bytes macro for now. Not sure what's the best route from here @Pratyush

Some new merge conflicts to be resolved here @filiplazovic

There is a high likelihood that we will bring in sponge's Poseidon implementation in some ways, and there is a possibility of refactoring the CRH to allow providing previously generated parameters.

Can we use explicit names for this though so as to not overlap with this implementation? We are using this in our fork currently and would love to get it merged so that we don't have to depend on a fork. Something like crh/poseidon_sponge? What do you think @weikengchen ?

In fact, you don't need to have a fork. You can, in your own library, have a structure that implements the CRH trait, and then inside your codebase, you can use that one instead.

@weikengchen What about Identity hash (#50)?

I think identity hash is useful, especially now we separate the leaf CRH and two-to-one CRH, and it works well with Poseidon. I will surely review it soon. Thanks for the code!
I want to mention that the code review process can be tedious, and there may be different opinions --- e.g., whether it should be called identity or something more traditional from libsnark packing, whether an assertion of the input size is needed (rather than directly pulling the first element by .get(0). The repo that the identity hash PR is over did not allow maintainers to edit directly. This would increase the interactions before the PR is finally settled down.
I think the best for webb is to find a way that the review process does not slow down or affect your development. Using a fork is very likely to be tedious as well, as you would need to merge the same number of changes as the master, although many changes are not related to your application.
I recommend webb keeping an organization misc library that implements the new primitives. As long as they implement the traits (e.g., CRH), they should be interchangeable with whatever inside the arkworks-rs, like building a Merkle tree with mixed CRH constructions.

Any update on this? I know it's a big PR. #57 is a bug that I'm blocked on right now, though.

Any update on this? I know it's a big PR. #57 is a bug that I'm blocked on right now, though.

Since we plan to replace the Poseidon hash function as a whole this week, I recommend you to either switch to an ark-sponge implementation or use a webb-tools fork. The main issue with Poseidon has always been how to generate the parameters securely. Eventually, it seems that we should just hardcode the parameters.

Likely this weekend, but it will be on the next release. In the meantime, you can use the cargo patch.

Awesome, thanks!

On Jul 1, 2021, at 18:38, Weikeng Chen @.***> wrote:

Likely this weekend, but it will be on the next release. In the meantime, you can use the cargo patch.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

@rozbb in case it’s helpful, we have this integrated here: https://github.com/webb-tools/arkworks-gadgets.
I’m also adding and formatting parameters for various curves for the gadgets and direct implementation themselves. Lmk if you’d like me to add various curves to be supported. I’ll be issuing new releases for it in that repo as well soon. They will be guarded with feature flags.


panic: if referrer is nil

https://github.com/gostaticanalysis/sqlrows/blob/master/passes/sqlrows/sqlrows.go#L94
If refs is nil, *refs become a panic.

Running into this as well. It would be helpful if it would not panic and say why or where this happens.

With this you can reproduce the issue
func issue9() {
	var ctx context.Context
	var db *sql.DB
	rows, err := db.QueryContext(ctx, "SELECT * FROM users")
	if err != nil {
		log.Fatal(err)
	}
	defer rows.Close()

	func() {
		for rows.Next() {
			rows.Scan()
		}
	}()
}


Cancel registration at PIN entry doesn't work

Tap register on home screen
Upon PIN entry, tap cancel
Button keeps spinning

Can't reproduce I get a password check error, when I do this: image

tested again with 1.8.0-rc
reproduce

start app fresh
profile -> add (+)
upon PIN entry, tap cancel
account add page will still show and user can add an account
created account will have empty PIN

This hints at some serious flaw

I think this doesn't apply anymore.


Preserve search options / Allow default search options to be configured

When I search in VS Code, via for example ctrl+d, ctrl+f, I get this tiny menu with options like case-sensitive, regex, etc. I'd really like those options to stay the way I like them. But there are to problems with that:

VS Code forgets
Not sure if it's after a certain amount of time, app reloads, project switching, or what causes VS Code to forget my choices, but annoyingly often when I press for example ctrl+d, the options are back their application defaults: all off.

There's no way to configure the default
Only search option I find is something called Smart Case, which I'm not interested in. I find no way to configure the default search options to be what I want.

Any chance of getting some settings where I can configure my preferred search options in my settings.json? And then initiate with those instead of everything off as it does now when I start a new search?
If I can configure the defaults I don't mind VS Code forgetting (would actually be preferred). But if that's not a possible, an alternative would be that VS Code just always used my last options, instead of forgetting as it does now. In other words, I'd like one of those solutions, but not both. 😛

VSCode Version: 1.36.1
OS Version: Windows_NT x64 10.0.17134
Steps to Reproduce:

Press ctrl+f
Change the search options
...
Repeat 1 and check if they're the same

Btw are you aware up/down error goes to prev/next search?

@octref I was aware of the arrow buttons, but not the shortcut key. Useful to know about, but not really what I'm looking for here. I don't want my previous search. I want to do a new search, but with my preferred search options.


Parcel loses track of source maps

I suspect all that's happening is that parcel keeps moving things around during the build and the browser can't keep up.
There's some suggestion here that we might be able to tell parcel where to look - but my initial stab at this wasn't very fruitful.
https://parceljs.org/features/targets/#sourcemap

I'm not going to work on this right now.
I had no luck finding an obvious solution using Parcel, but I did have some success with webpack 5, using the scalajs-friendly-source-map-loader webpack plugin.
However you can't use it with the dev server because it complains about paths, you have to build it, and run a static server from the dist folder. Speculate that it might work in webpack 4 maybe? The path warnings seem to be a new thing, but what do I know?
Here is the commit on a branch: https://github.com/PurpleKingdomGames/tyrian/commit/3577283df81391672c468d8718cd9165bf0e3906
In the screenshot below, you can see a tyrian app, running an embedded indigo game, and the profiler is merrily telling us that this bit of the code came from GameLoop.scala:53:4.


Adapt OSM Tile Server URL

Adapt OSM Tile Server URL

https://github.com/openstreetmap/operations/issues/737


[Hi Haddock] In what format to export Haddocks in .hi files?

An important design question of the Hi Haddock project is the choice of format that GHC shall use to include documentation in its .hi interface files. I am currently aware of two competing proposals for that format:

Export the fully parsed and renamed AST in haddock-library's MetaDoc/DocH format. This is what I proposed in my GSoC proposal. I'll call this the DocH-variant.

Export the raw docstrings, and all information that is necessary to rename identifiers in the documentation or to link to dependencies. Let's call this the raw-docstring-variant.

Here are some aspects of the two variants as I currently see them. Please mention any other aspects in the comments as I'm sure I've missed a few!
Aspects of the DocH-variant

GHC will depend on haddock-library to parse the documentation.
haddock, ghci and other consumers of the format don't need to do any further parsing or renaming.
Unlinkable identifiers are identified and warned about at compile-time.

Aspects of the raw-docstring-variant

GHC gets a simple lexer that detects identifiers and links and determines what renaming information needs to be included in the interface files.
The lexer may falsely detect some non-identifiers but that should at worst result in some bloat in the interface files.
Tools that want to use a different syntax for documentation such as MarkDown or reStructuredText will only have to extend the lexer to detect identifiers in the new syntax.
This in consequence makes it more likely that we will see other documentation formats and tools in the near future.
This variant requires less work at compile-time, and is more likely to be cheap enough that the documentation can be output by default.
haddock, ghci etc. will have to rely on haddock-library or other documentation tools to parse and rename the docs.

(I don't think I'm misrepresenting this idea, but just in case, here is @gbaz's own description.)
Can both variants be combined?
I haven't thought about it much or discussed it, but it currently seems to me, that if I implement the DocH-variant as originally planned, it might not be too hard to add a code path for the the raw-docstring-variant which could be enabled via a ghc haddock-option.
Anyone who has a clearer idea of the things involved here: Please warn me, if you think I'm underestimating the complexity! :)

Thanks for opening an issue to discuss this! I strongly support the second variant as I would prefer to not have the Haddock markup format baked into GHC. It seems wrong to force GHC to become aware of one particular markup format, especially a controversial format like Haddock. One other advantage to only packaging raw docstrings is that markup syntax (Haddock, Markdown, etc.) would be able to vary orthogonally to the GHC version.

haddock, ghci etc. will have to rely on haddock-library or other documentation tools to parse and rename the docs.

Why should GHCi need to parse the doc strings at all? It seems to me that displaying just the raw doc strings would be the best thing for the command line... Other than that, it seems morally right that only programs that want to parse the Haddock markup format incur the cost of a library which parses the Haddock format.

I haven't thought about it much or discussed it, but it currently seems to me, that if I implement the DocH-variant as originally planned, it might not be too hard to add a code path for the the raw-docstring-variant which could be enabled via a ghc haddock-option

That solves the problem of giving access to raw docstrings, but not the dependency problem. 😄

@harpocrates:

Why should GHCi need to parse the doc strings at all? It seems to me that displaying just the raw doc strings would be the best thing for the command line...

Admittedly this is not entirely clear to me too. (Also, the rendering of the docstrings in ghci is outside of the main focus of the proposal.) But I'm sure that even on the CLI, one can do a lot of nice highlighting with different font styles and colours.
Is that what you had in mind for :doc, @hvr?

Admittedly this is not entirely clear to me too. (Also, the rendering of the docstrings in ghci is outside of the main focus of the proposal.) But I'm sure that even on the CLI, one can do a lot of nice highlighting with different font styles and colours.

Copying my reply from the other thread:

That seems also like something that could be a GHCi option for those who want it (something like the -interactive-print option). One such implementation could then depend on haddock-library, but I wouldn't package that implementation with GHCi.

To explain why moving haddock-library into the GHC boot libraries is such a point of contention:
There are currently two proposals underfoot that would increase the dependency footprint of haddock-library:

#799 adds dependencies on parsec and text (both of which have been introduced as boot libraries in GHC-8.4).
#794 would add a dependency on a new package commonmark-core. That means that if haddock-library becomes a boot library, so does commonmark-core.

@bgamari, could you possibly comment on how these two issues affect haddock-library's chances of becoming a boot library, or know whom to ask?

fwiw, haddock-library was always intended to become a boot library sooner or later anyway; it's always been one in disguise anyway.

I think it would be rather unfortunate if GHC came to depend too closely on Haddock.

So.. I think my lexer proposal is sufficiently lightweight and safe that I'm not worried about technical drawbacks (I know herbert may disagree here). I don't see any purpose for combining the two variants, since it doesn't seem to resolve anything.
The fundamental question really is, shall haddock-library become a boot lib.
We should enumerate the tradeoffs properly.
Pro

The main  benefit I see is for ghci to be able to display formatted as opposed to raw docstrings, with a new :doc command (but with such a command being out of direct scope for this GSoC anyway, as far as I know?).
As noted we can warn earlier about unlinked identifiers.
The other benefit -- tighter lexing -- doesn't seem significant to me given that a good overapproximate lexer should be easy to produce.

Con

making alterations to haddock parsing require changing a bootlib will impede haddock development.
ditto for impeding alternate syntaxes or extensions.
as a rule of thumb we want to minimize GHC's dependency footprint

Can people help expand either list?
(Btw, with regard to ghci, I also like the suggestion in the other thread that ghci could just be given an option for some external formatter for docstrings -- this also lets such things evolve more quickly and e.g. add features for coloring output, etc. It is also similar to the existing -interactive-print flag (https://downloads.haskell.org/~ghc/8.2.1/docs/html/users_guide/ghci.html#ghc-flag--interactive-print), so there's prior art :-)).

I also think that GHC shouldn't be too tightly bound to Haddock. GHC is a Haskell compiler and nowhere in the Haskell Report is a documentation syntax described. Consequently, I'm not sure I see a strong reason to include a Haddock parser in GHC. Haddock is already too coupled to GHC and, in my mind, one of the goals of this project is to reduce this coupling, not further entrench it.
Incidentally, I do worry that the community as a whole would only suffer if a competing project to Haddock were to gain traction. We have a hard enough time maintaining a single documentation engine; I really don't think we can afford to maintain two, especially given the various other bits of infrastructure that integrate with Haddock. Regardless, we shouldn't let these social considerations dictate technical decisions.

The main benefit I see is for ghci to be able to display formatted as opposed to raw docstrings, with a new :doc command (but with such a command being out of direct scope for this GSoC anyway, as far as I know?).

Rendering the docstrings in ghci is a stretch goal in my proposal.

(Btw, with regard to ghci, I also like the suggestion in the other thread and above that ghci could just be given an option for some external formatter for docstrings -- this also lets such things evolve more quickly and e.g. add features for coloring output, etc. The similarity to the existing interactive-print flag means we're not breaking ground, but just extending design principles already in place).

In case anyone else is unfamiliar with ghci's -interactive-print flag, it's documented here.
And indeed it seems straightforward to add an analogous flag -interactive-render-doc that accepts functions of type  LinkEnv -> HsDocString -> IO () or similar. A library that wants to provide a function of this type could then depend on haddock-library.

Speaking from the tooling perspective, at the very least I would like GHC to resolve symbols/identifiers mentioned in comments. It would be great if GHC could just understand the subset of haddock markup that deals with references to symbols(the DocIdentifier constructor).
IIRC, one of the goals of the original plan was to make it so that that haddock and other tooling don't have to recompile stuff just to generate documentation. If Names are not resolved by GHC on the first go, haddock will be forced to recompile the entire file anyway.
As to if GHC should understand any of the other haddock markup, I'm agnostic. That can be handled by the ultimate renderer(ghci, haddock html output, haskell-ide-engine tooltips) without an unnecessary and expensive call to GHC to recompile the file.

Speaking from the tooling perspective, I would like GHC to resolve symbols/identifiers mentioned in comments. It would be great if GHC could at the very least understand the subset of haddock markup that deals with references to symbols(the DocIdentifier constructor).

Right. Both ideas under consideration will provide for this one way or another, and avoid haddock having to do an additional recompilation step.

By the way, herbert has expressed that he thinks we're sort of fooling ourselves, and that effectively haddock-library is already a bootlib, just wearing glasses and a fake mustache. If this is the case, then it potentially changes the equation here. I understand this has to do with the in-tree flag and how it operates, but I confess I don't understand the details and it would be good to see it spelled out.

Speaking from the tooling perspective, I would like GHC to resolve symbols/identifiers mentioned in comments. It would be great if GHC could at the very least understand the subset of haddock markup that deals with references to symbols(the DocIdentifier constructor).

Right. Both ideas under consideration will provide for this one way or another, and avoid haddock having to do an additional recompilation step.

Actually it seemed to me that in the raw-docstring-variant, consumers of .hi-files would still have to re-lex the docstrings in order to know what to rename, link etc.
I think it would be good if this duplicate lexing could be avoided. Maybe the docstring-lexer in GHC could output something like ~[((Int, Int), Name)] to mark the lexed identifiers in the docstring?

Right -- I was addressing recompilation, not re-lexing of the haddock docstrings. Your suggestion for attaching sourcespans to the name information makes sense to me.

I imagine that if this is done right, the whole renaming process in haddock can simply disappear.

Actually it seemed to me that in the raw-docstring-variant, consumers of .hi-files would still have to re-lex the docstrings in order to know what to rename, link etc.
I think it would be good if this duplicate lexing could be avoided. Maybe the docstring-lexer in GHC could output something like ~[((Int, Int), Name)] to mark the lexed identifiers in the docstring?

I fear duplicate lexing will not be avoided - whatever partial lexing you do in GHC will probably be very simple and,over-eager in some cases, so Haddock and other consumers of .hi files will likely be re-parsing from scratch. That's a tiny runtime cost though (parsing is not Haddock's bottleneck, and I doubt with will become so after this GSOC).
In your place, I'd simply use something like [(String,Name)] (where the Strings would be the in-docstring format of the Name) for ease of debugging .hi file dumps.

I imagine that if this is done right, the whole renaming process in haddock can simply disappear.

This is probably the key point. However you think this will be best achieved should inform your choice for the format of the name information.

So I just talked to @alexbiehl and @hvr about this issue:
We decided that I will implement the raw-docstring / lexer variant as a prototype first, and that we'll go further from there. The main advantage of this variant that we're seeing is that it should be less costly at compile-time.
Regarding the problem that in order to support new documentation markup formats, the lexer may need to be adjusted, @hvr mentioned the idea of implementing new markup formats as preprocessor steps: A GHC source preprocessor could translate the new markup format into haddock markup so it can be processed further by pre-existing tools. The main point of this solution would be that users could use new markup formats with old versions of GHC.

Here's a basic type design for the lexer variant:
Internally we'd work with
-- | The location of an identifier in a docstring
data DocIdentifierSpan = DocIdentifierSpan Int Int

data HsDocIdentifier id =
  HsDocIdentifier
    DocIdentifierSpan
    HsDocString -- ^ The identifier as it appeared in the docstring
    [id] -- ^ There can be multiple (or zero) choices for what an HsDocIdentifier stands for.
         -- See Haddock.Interface.LexParseRn.rename.
         -- id will be either 'RdrName' or 'Name'.

-- | A raw docstring and the identifiers it contains.
data HsDoc id = HsDoc HsDocString [HsDocIdentifier id]

For the serialization to .hi-files we'd extract two things:

The HsDocIdentifiers are combined into a Map String (Set Name) which can be used for renaming.

Each HsDoc docstring is serialized basically as (String, [DocIdentifierSpan]) where the spans would serve two purposes:

Initially, we'd use them to test and debug the lexer.
Simple external tools could use them to avoid re-lexing/parsing the docstrings and to target their renamer. This requires the lexer not to produce too many false positives.

And I presume the DocIdentifierSpan values would be the start and end UTF8 character offsets into the string?  So multiline haddock comments would not matter.

And I presume the DocIdentifierSpan values would be the start and end UTF8 character offsets into the string? So multiline haddock comments would not matter.

That's right.

In case you'd like to get updates about my progress: I've started blogging about this project at https://sjakobi.github.io/.

The lexer prototype is up for review at https://phabricator.haskell.org/D4749.


interface: Adding darwin support

get_link_state: Emulating Linux taking administratively down and physical layer into account
others: verbatim copy from freebsd

Thanks.

Released as v2.42.2.


Multiclass methods: Gradient always exploding

I've had some success using other methods to predict survival for my business problem. However, I can never get either of the multi class methods to work. I'm met each time with The gradient exploded... You should reduce the learningrate (lr) of your optimizer. I've tried extremely small learning rates, but still the same result.

I am facing the same issue. any solution to this problem?

Try setting auto_scalar=False

I set auto_scalar = False, but am still getting the same error. Is there any solution?


Fix dtype for wrapper observation spaces

Actually, I realized that doing self.observation_space.dtype = np.float32 isn't good, because you're just mutating the observation space of the input environment. You should probably construct a new box space, e.g. gym.spaces.Box(low=0, high=1, shape=env.observation_space.shape, dtype=np.float32)

It's a terrible bug which will cause DQN fails in Atari games. Actually In baselines/common/input.py line 18:
input_x = tf.placeholder(shape=input_shape, dtype=ob_space.dtype, name=name)
Leads to the data type of the observation's tf placeholder mismatch with the real data's. And model fails to train.
So why nobody merges this pull request into main branch

effectively megred (I merged it in together with the refactor), closing this


flutter run doesn't handle the device going away during installation gracefully

Pull the cable from your phone a few seconds after the "Installing build/app.apk" message appears:
$ flutter run
Installing build/app.apk...
protocol failure
- waiting for device -
Exception from flutter run: Exit code 1 from: /usr/local/google/home/ianh/dev/engine/src/third_party/android_tools/sdk/platform-tools/adb -s ZX1G22KJ3C install -r build/app.apk
package:flutter_tools/src/base/process.dart 234            _runWithLoggingSync
package:flutter_tools/src/base/process.dart 157            runCheckedSync
package:flutter_tools/src/android/android_device.dart 243  AndroidDevice.installApp
package:flutter_tools/src/commands/install.dart 54         installApp
package:flutter_tools/src/hot.dart 235                     HotRunner._run.<async>
===== asynchronous gap ===========================
dart:async                                                 _Completer.completeError
package:flutter_tools/src/hot.dart 338                     HotRunner._run.<async>
===== asynchronous gap ===========================
dart:async                                                 _asyncThenWrapperHelper
package:flutter_tools/src/hot.dart                         HotRunner._run
package:flutter_tools/src/hot.dart 148                     HotRunner.run.<fn>
package:stack_trace                                        Chain.capture
package:flutter_tools/src/hot.dart 147                     HotRunner.run
package:flutter_tools/src/commands/run.dart 236            RunCommand.runCommand.<async>

Duplicate of https://github.com/flutter/flutter/issues/1980


bump golang version to 1.22.8

The version of Golang being used during build is actually 1.23.2: https://github.com/NVIDIA/mig-parted/actions/runs/11350079065/job/31567676999#step:7:20 which is defined here: https://github.com/NVIDIA/mig-parted/blob/main/deployments/devel/Dockerfile#L17

Yes, I am waiting till 1.23.3 is released as it has the fixes for when running in a docker arm64 container

I think it's good to atleast bump this default even though the actual golang version is 1.23.2

The commit title is misleading since you are not actually changing the version of Go used to build this project.

Please check now


Redesign Feedback form

Is your feature request related to a problem? Please describe.
I can see there is no placeholder in form also star starts from right side it is not good.
Describe the solution you'd like
I will Redesign this feedback form try to make it stylish.

@sk66641 Please assign me !

This issue  is currently being addressed in #302. You can follow the progress and participate in the discussion there.


what is init_data？I can't train rq_vae

Should be fixed with https://github.com/EdoardoBotta/RQ-VAE-Recommender/pull/4/commits


incorrect outbound http validation blocks request if url contains '@'

I am trying to debug an issue with one of my spin app, and it seems like spin incorrectly blocks the outbound request if the url contains '@'
here is how my outbound http config looks like in spin.toml:
allowed_outbound_hosts = ["https://api.github.com", "https://github.com"]
and
the url I am trying to make request to is : https://api.github.com/repos/rajatjindal/spin-plugins/contents/manifests/kube/kube@0.2.0.json?ref=heads%2Fkube-v0.2.0
On trying to make this request, following error is thrown:
2024-11-05T02:13:16.254329Z ERROR spin_runtime_factors: Outbound network destination not allowed: https://0.2.0.json
Warning: A component tried to make an outbound network connection to disallowed destination 'https://0.2.0.json'.
To allow this request, add 'allowed_outbound_hosts = ["https://0.2.0.json"]' to the manifest component section.
Handler returned an error: Error::UnexpectedError("ErrorCode::HttpRequestDenied")

The source code for this sample can be found at: https://github.com/rajatjindal/spin-outbound-http-issue/

yeah, it seems we may need to handle this here: https://github.com/fermyon/spin/blob/4441c8cf277ab13b94a4362fde4b78fe7601493d/crates/factor-outbound-networking/src/config.rs#L444C37-L444C38

I think the issue is at https://github.com/itowlson/spin/blob/55ce36e2895a04822fcf47ad329a3ea9ae767adf/crates/factor-outbound-networking/src/config.rs#L446.  It's trying to handle the presence of a username:password@host prefix, but encodes too much of the URL when the @ is in the path or query.

Hi @itowlson, thank you for your super quick turnaround. Assuming this can be fixed/merged soon, do you have a rough idea on when we can expect this fix in Fermyon Cloud?
Thanks again

I'm not sure of timings for Fermyon Cloud, sorry.  I can try to take a look if the fix is approved but can't promise anything as there's a bunch of other stuff happening around Spin 3.

I'm not sure of timings for Fermyon Cloud, sorry. I can try to take a look if the fix is approved but can't promise anything as there's a bunch of other stuff happening around Spin 3.

sure, no problem. thank you.


[CAMEL-18191] - S3Constants class fix for AWSS3Constants in doc

issue: https://issues.apache.org/jira/browse/CAMEL-18191
at https://camel.apache.org/components/3.17.x/aws2-s3-component.html#_message_headers
at some points it is found references to the S3Constants class instead of AWSS3Constants in doc

Your welcome:)


Ports doesnt get forwarded

This issue has been moved here from https://github.com/tredly/tredly-host/issues/47. Original issue submitted by dinapappor. Please see the original thread for more details but continue discussion here.

While the reverse proxy feature with nginx works great I am having troubles getting regular destination nat to work.
I can see that in the container the ports get's added without a problem, it's added 3 times (port 13222) for three different tables, but I can't find the tables defined anywhere.
0100 allow log tcp from table(2) to <IP_ADDRESS> dst-port 13222 in via vnet0 setup keep-state
00200 allow log tcp from table(3) to <IP_ADDRESS> dst-port 13222 in via vnet0 setup keep-state
00300 allow log tcp from table(1) to <IP_ADDRESS> dst-port 13222 in via vnet0 setup keep-state
00400 allow log tcp from <IP_ADDRESS> to any dst-port 80 out via vnet0 setup keep-state
00500 allow log tcp from <IP_ADDRESS> to any dst-port 443 out via vnet0 setup keep-state
00600 allow log udp from <IP_ADDRESS> to any dst-port 53 out via vnet0 keep-state
00700 allow log tcp from <IP_ADDRESS> to any dst-port 80,5672 out via vnet0 setup keep-state
00800 allow log udp from <IP_ADDRESS> to any dst-port 53 out via vnet0 keep-state
00900 allow log udp from <IP_ADDRESS> to <IP_ADDRESS> dst-port 53 out via vnet0 keep-state
01000 allow log udp from <IP_ADDRESS> to <IP_ADDRESS> via vnet0 keep-state
01100 allow log tcp from <IP_ADDRESS> to <IP_ADDRESS> via vnet0 setup keep-state
01200 allow log ip from any to any via lo0
65535 deny ip from any to any

These rules are not in /usr/local/etc/ipfw.rules in the container. There's just a bash shebang in there.
On the tredly-host I am seeing no mention of port 13222. I've examined the ipfw list command as well as all the ipfw.* files.
From inside the container I can reach the service (in this case ssh) with that port without a problem.
Trying to reach the container from the tredly-host with ssh -luser -p13222 containerip fails with a timeout. And the same happens from the outside.
SSH listening on port 13222 inside the container:
root@project-microservice:/ # netstat -an
netstat: kvm not available: /dev/mem: No such file or directory
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address          Foreign Address        (state)
tcp4       0      0 *.13222                *.*                    LISTEN
tcp6       0      0 *.13222                *.*                    LISTEN

I have the following ports defined in the Tredlyfile:
# The following is for SSH into this instance to allow for ansible to ssh into this container and do hot code reloads.
tcpInPort=13222

# Needed to install packages
tcpOutPort=80

# Needed for connections to RabbitMQ
tcpOutPort=5672

# Needed for DNS queries.
udpOutPort=53

I am running my own package repo and I wont need https and ftp outbound. The packages get's installed fine.
I am also seeing that TSO doesn't get shut off by default. I think the issue is that since net.inet.tcp.tso is a read/write tunable it needs to go into /etc/sysctl.conf or else it wont get honored.
Loader tunables (The ones that can only be set at boot) goes into /boot/loader.conf and read/write tunables (the ones that can be changed anytime) goes into /etc/sysctl.conf.
If I can provide more information in order to debug these problems let me know. I would be happy to help.

Closing this issue as it is resolved in v1.0


Demo needed

Create a demo of the working of Reactonite which we can add in README so that a user can just refer the video/GIF before actually starting using the project.

Please refer to this link for the draft of the demo video

GIF for NonGUI Component


Make the title (optional) part of the spec-file

Feature request:
Make the title (optional) part of the spec-file. Of course, it is possible to write a script, which takes the title from the filename, but not every useful attribute of a title is fine as filename. We like filenames to be short, but titles might sometimes be more verbose. If I work in an editor like Geany, I can configure it, so that it will produce a PNG when I hit the compile button, but the title has to be set manually, which makes it a less productive workflow.
The implementation might use an additional, optional key-value notation in the file, to keep all old spec files compatibel, or use an annotation in the comment section, to create a title.

Feature request:

Sorry - my feature request was mainly meant to adress the follow up program "jsyntrax". Postet it there, too.


Code Climate problem

Code Climate is no longer able to connect to this repo, so this data is out-of-date. Please see this help article or contact us for help.

Please connect CC to this repo.

@blackms Please open https://codeclimate.com/github/blackms/pyArubaCloud and see the red message!

See #34


Allow not dropping bads when creating or plotting Spectrum objs

Closes  #11722
Closes #11382
As mentioned in the issue by @drammock :

I modified raw.compute_psd() to take in an exclude argument. The default behaviour is exclude=().
Spectrum.pick() has an exclude=(). It cannot inherit this from the aw/Epochs/Evoked data source.
However, channels in exclude are removed when raw.compute_psd() is called so does it need to inherit from the data source? In which case maybe set exclude to be a property of Spectrum so it can be accessed by pick(). Maybe there is an easier way.
'Spectrum.plot()' has an exclude argument as of version 1.5 so no need to add it

I tested this changes locally with some test data and raw.compute_psd() behaves as expected. Only removing bad channels
unless specified by exclude="bads". This being my first contribution, please do give me some feedback where needed, thanks for your time!

I pushed a minor tweak to the test and merged in current upstream main. Marking for merge-when-CIs-pass, thanks @Gon-reina !

Thanks a lot, I haven't got much experience testing so apologies in advance. I've updated main again so hopefully that does it!


Overload resolution problem

Using trill there seems to be an issue selecting the right overload for the Select extension method

open Microsoft.StreamProcessing
open System
open System.Linq.Expressions

type Record(a : int) =
    member x.A = a

let f (x : IStreamable<int64, Record>) : IStreamable<int64,int> = x.Select(fun x -> x.A) //Error
let g (x : IStreamable<int64, Record>) = Microsoft.StreamProcessing.Streamable.Select(x, (fun x -> x.A)) //Error
let h (x : IStreamable<int64, Record>) = Microsoft.StreamProcessing.Streamable.Select<int64, Record, int>(x, (fun x -> x.A)) //Error
let k (x : IStreamable<int64, Record>) = x.Select(selector = (fun x -> x.A)) //Okay

The errors in  the first three attempts are on x.A with Error	FS0072	Lookup on object of indeterminate type based on information prior to this program point. A type annotation may be needed prior to this program point to constrain the type of the object. This may allow the lookup to be resolved.
Usually a simple type annotation on x would solve the problem but this is an ideal use case of anonymous records and having to add the full type annotation would be horrendous. Luckily in this particular case using a named parameter works.
Repro steps
Add Trill nuget package and use the code above, or clone https://github.com/kevmal/overloaderr
Known workarounds

Named argument (specifically for this case)
Type annotation which kills the whole anonymous record experience
add helpers:

type Bleh() =
    static member Select(v : Expression<Func<'a,'b>>) = fun (x : IStreamable<_,_>) -> x.Select(v)
let l (x : IStreamable<int64, Record>) = x |> Bleh.Select (fun x -> x.A) //Okay

I think this will need to be recorded as a language design suggestion at https://github.com/fsharp/fslang-suggestions/, rather than a bug.  There are complicated overload sets that definitely cause problems, looking at the above overloads I can see why they might be a problem in each of the three cases
I'd really like to see some F# Trill code - besides the above do you have any available to share?

I don't have anything too exciting at the moment. But I have the fsx file I created reading through the query writing guide:
https://gist.github.com/kevmal/d5382e8d2b0059a179341805be2fc2d3

OK cool. Put a blog post up when you have a decent starter intro done?

Sure, I'll look into it.


Transcoding issue

Hello,
I have a freeswitch with mod_unimrcp, the config is as follows:
<profile name="myserver" version="2">
  <param name="client-ip" value="<IP_ADDRESS>"/>
  <param name="client-port" value="25097"/>
  <param name="server-ip" value="asr.local.com"/>
  <param name="server-port" value="5060"/>
  <param name="sip-transport" value="udp"/>
  <param name="rtp-ip" value="$${local_ip_v4}"/>
  <param name="rtp-port-min" value="28000"/>
  <param name="rtp-port-max" value="29000"/>
  <param name="codecs" value="PCMA PCMU"/>
  <param name="rtcp" value="0"/>
  <param name="rtcp-bye" value="2"/>
  <param name="rtcp-tx-interval" value="5000"/>
  <param name="rtcp-rx-resolution" value="1000"/>
  <synthparams>
  </synthparams>
  <recogparams>
    <param name="start-input-timers" value="false"/>
  </recogparams>
</profile>

Only supports PCMA, but it seems the transcoding is not done right.
2021-02-09 19:47:10.347196 [INFO] mod_unimrcp.c:3140 asr_handle: name = unimrcp, codec = (null), rate = 16000, grammar = (null), param = (null)
2021-02-09 19:47:10.347196 [INFO] mod_unimrcp.c:3142 codec = L16, rate = 16000, dest = (null)
2021-02-09 19:47:10.407195 [INFO] mpf_bridge.c:93 () Media Path ASR-1 Source->[LPCM/8000/1]->Bridge->[LPCM/8000/1]->Encoder->[PCMA/8000/1]->Sink
2021-02-09 19:47:10.427967 [DEBUG] mod_unimrcp.c:1901 (ASR-1) RECOGNIZER channel is ready, codec = LPCM, sample rate = 8000

Can you give me a hand?
Thanks

So the problem seems to be that on mod_sofia, when the codec is G.722, this is done:
codec_rate = !strcasecmp(codec->implementation->iananame, "g722") 				? codec->implementation->samples_per_second : codec->implementation->actual_samples_per_second;
But it's not done on mod_unimrcp.
This results in a sampling issue and garbles the audio going to the unimrcp server.

This issue seems to belong to mod_unimrcp in FreeSWITCH. There is no support for G.722 in the MPF library used by the client and server.


Abstract local cosigner sign methods into interface

Abstract the local cosigner sign methods into a common interface so that various HSMs can be implemented using the interface

https://github.com/strangelove-ventures/horcrux/pull/67

WIP
Phase 1: https://github.com/strangelove-ventures/horcrux/pull/98

Phase 1: https://github.com/strangelove-ventures/horcrux/pull/98 now merged.


Notebook/rework yaxis

This branch has built out a notebook with a working solution for the y-axis implementation problem (changing y-axis from displaying floats to integers).  This solution has also been added to the codebase app/visualizations.py

This branch has created a notebook with a working solution for the y-axis implementation problem (floats being displayed for counts, rather than as integers).  The solution has also been added to the code base, app/visualizations.py


feat(gtk): support create Ed25519 in gtk

Description
This PR support generation Ed25519 account type on GTK.

Related issue(s)

Fixes #1486

Why don't you get password before generating the Ed25519?
This way we keep the dialog as i t is and get password once needed.,

Why don't you get password before generating the Ed25519? This way we keep the dialog as i t is and get password once needed.,

fixed

@Ja7ad please update the description


Settings Editor UI doesn't handle touch events

VSCode Version:
OS Version:

Steps to Reproduce:

Open web selfhost in iPad/iOS
Open Settings Editor UI
We can only scroll the settings but not change the value, touch down doesn't work.

Root cause analysis
TLDR, Setting Editor is using List Widget, which registers the container to Gesture. Once the DOM node is registered in Gesture, we have to implement all touch events handler, as events are being preventDefault() on the DOM node.
List Widget and List View registers itself to Gesture to support the correct scrolling when touch events are triggered
https://github.com/microsoft/vscode/blob/0616326888e22a6e928a172f9d73a2cb7ffea56d/src/vs/base/browser/ui/list/listWidget.ts#L545
https://github.com/microsoft/vscode/blob/0616326888e22a6e928a172f9d73a2cb7ffea56d/src/vs/base/browser/ui/list/listView.ts#L238
As list view handles the touch events, they will be preventDefault
https://github.com/microsoft/vscode/blob/0616326888e22a6e928a172f9d73a2cb7ffea56d/src/vs/base/browser/touch.ts#L148-L152
Considering that Gesture has a robust logic of translating touchStart, touchMove and touchEnd to Tap/Change/Start/End, one solution is we handle the right Gesture event in every Settings View Component.
A less favorite solution is letting List View by pass some of the touch events but I wonder that would lead to bugs for List View virtualization.
Settings Editor is probably the only major component affected by this bug as others are simple List View with special Tap/ContextMenu handlers, while Settings Editor contains a lot of other basic UI elements.

FYI @joaomoreno . I appreciate that List View handles touch events internally as ScrollableElement doesn't handle touch at all (only mouse). Without that, we will run into tons of scrolling issues in any place we use ScrollableElement, like https://github.com/microsoft/vscode/issues/83715#issuecomment-553716765 . Luckily List View saved us.
It's also why I'd like to keep List View and Gesture untouched. @roblourens I can send a PR to add touch handlers in Settings Editor renderer (I already had some working locally and they look fine) if the approach sounds good to you.


Fix typo in Tutorial

Hey,
there is a typo in your tutorial over at http://wiki.ros.org/pylon_camera it says
/etc/ros/rosdep/sources.list.d/15-plyon_camera.list
instead of
/etc/ros/rosdep/sources.list.d/15-pylon_camera.list
it does not break anything so this does not have a high priority. Also, the distribution names do not necessarily need to be changed for e.g. kinetic as the branch kinetic-devel does not exist.

Hey!
Thanks for the hint, but It's a wiki page, so could can change typos yourself :)


Sql Server is not working with JdbcUtil

This is because of a typo in JdbcUtil.
I created a pull request fixing this problem: https://github.com/landawn/AbacusUtil/pull/15

Thank you!
It will be checked in and included in this weekend's release 1.5.7

@SaSa1983 I will close this issue if there is no further question.

I'm okay with closing the issue
landawn<EMAIL_ADDRESS>schrieb am Do., 21. März 2019, 05:39:

@SaSa1983 https://github.com/SaSa1983 I will close this issue if there
is no further question.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/landawn/AbacusUtil/issues/16#issuecomment-475111410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbPPMzFwc4YOiEZDYyGbW39jDQAT56_ks5vYw0UgaJpZM4btDvW
.


Company Communicator - Rename App?

Hi,
Is it possible to easily rename the app so that instead of the messages appearing from 'Company Communicator' they would appear from for example 'Communications Department' ?   Please see the screen shot of what I am talking about.
Much appreciated,
AR.

Thanks for raising the query here. Please follow the below steps.
To update name of CC

Login to Azure Portal with Global Admin Credentials (portal.azure.com)

Go to Resource Groups and Under your subscription select the resource group where the app is deployed.

Click on Azure Bot(user) --> under settings click bot profile-->Change display name as per the organizational need.

And update the names in the manifest files for user. Re-upload the manifest file again. Here is the place for reference. Please do it for user manifest file

Note:-

There might be chance that desktop app will get cached. However, it can be validated by checking in the browser version of the app.

Hi @erctechdev ,
Please let us know the status of the issue


[BUG] AUR package is out-of-date

Hi everyone, the rancher-k3d-bin in the Arch User Repository has been flagged out-of-date.
The PKGBUILD has pkgver=5.2.2 instead of pkgver=5.3.0.
Reading the PKGBUILD, I see that @JohnnyCrazy is the maintainer of the package but there's also a script to deploy new releases automatically.

I manually released 5.3.0 to the AUR. The AUR release script was broken but should work with the next release :)

Thank you!🙂


feature request: configure OpenType font features

From #6918: Please support configuration of font features, and possibly also support "user friendly" alternate configuration via font variants.
Font features allow the user to control the use of alternate glyphs and ligatures. For example:

normal vs slashed zero
lining vs old-style numbers
small-caps
fractions (and horizontal vs diagonal)
ordinals

Issue #6918 demonstrates that fonts may include useful nonstandard feature tags, so it is important that the user is not restricted to just the "font variant" options.
Example:
"editor.fontFeatures": {"zero": 1, "salt": 3, "COOL": 1},

Thanks, @voronoipotato !
One can add following to /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.css:
.monaco-editor {
    font-feature-settings: "ss02" !important;
}

More about CSS for OpenType features: https://helpx.adobe.com/fonts/using/open-type-syntax.html

@Njke hmmm that would only work if I wanted this stylistic set for all languages, however I only want ss02 on Markdown.

Thanks, @voronoipotato !
One can add following to /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.css:
.monaco-editor {
    font-feature-settings: "ss02" !important;
}

More about CSS for OpenType features: https://helpx.adobe.com/fonts/using/open-type-syntax.html

Sorry, but how do I get to /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.css
Visual Studio Code.app is an... app right? I feel dumb, how do I navigate into it?? 😆

Right-click -> "show package contents"
Carry on!

(It seems worth noting that diving into the app Package Contents CSS is pretty hacky ... this would be much nicer and less fragile if made into an actual setting).
I like the initial proposal a lot – this would be great to basically follow the CSS syntax for OpenType features. https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Fonts/OpenType_fonts_guide

With fonts like “Fira Code V2”, where several glyph alternatives can be enabled with font-feature-settings attributes, this is a super useful feature to have!

Implemented via https://github.com/microsoft/vscode/commit/ab0eb6de2d5fb4563385d98f302f78caa1767efd (https://github.com/microsoft/vscode/issues/82153) and it already shipped in Insiders.
e.g.
"editor.fontLigatures": "'ss01', 'ss02', 'ss03', 'ss04', 'ss05', 'ss06', 'zero', 'onum'"

or
    "editor.fontFamily": "Fira Code"
    "editor.fontLigatures": true,
    "[cpp]": {
        "editor.fontLigatures": "'ss06', 'ss19'",
    },
    "[javascript]": {
        "editor.fontLigatures": "'ss06'",
    },


task/174/replace-with-canvas

Codecov Report

Merging #175 (a8d8a65) into main (19af66b) will increase coverage by 1.51%.
The diff coverage is 64.28%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   78.32%   79.83%   +1.51%
==========================================
  Files          82       82
  Lines        2016     1984      -32
  Branches      316      308       -8
==========================================
+ Hits         1579     1584       +5
+ Misses        436      399      -37
  Partials        1        1

Impacted Files
Coverage Δ

client/src/components/ArtScroller.tsx
88.88% <ø> (ø)

client/src/components/MIDIListenerWrapper.tsx
96.42% <ø> (ø)

client/src/components/Slider.tsx
100.00% <ø> (ø)

client/src/components/SpringButtons/index.ts
100.00% <ø> (ø)

client/src/constants.ts
100.00% <ø> (ø)

client/src/pages/Home.tsx
100.00% <ø> (ø)

client/src/pages/LedWindow.tsx
50.00% <ø> (ø)

client/src/store/ledSlice.ts
83.33% <0.00%> (-16.67%)
:arrow_down:

client/src/utils/LedStyleEngineClass.ts
83.58% <ø> (-15.09%)
:arrow_down:

client/src/utils/MIDIControlClass.ts
72.17% <0.00%> (+0.50%)
:arrow_up:

... and 8 more

... and 6 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


multi var invalid order for setting the vars

func main() {
	dc := 632
	extra := 7
	extraMask := 127
	dc, fracc := dc>>extra, dc&extraMask
	fmt.Println(dc, fracc)
}

function main():Void {
	var _dc:GoInt = (632 : GoInt);
	var _extra:GoInt = (7 : GoInt);
	var _extraMask:GoInt = (127 : GoInt);
	var _dc:GoInt = _dc >> _extra, _fracc:GoInt = _dc & _extraMask;
	stdgo.fmt.Fmt.println(_dc, _fracc);
}

Haxe: 4, 4
Go: 4, 120

I believe the issue is the second declaration of _dc in Haxe.
If I change the name of the second declaration to be _dc2, then insert a new statement to set _dc=_dc2,  it works correctly, see this TryHaxe code.

I believe the issue is the second declaration of _dc in Haxe.
If I change the name of the second declaration to be _dc2, then insert a new statement to set _dc=_dc2, it works correctly, see this TryHaxe code.

So temp variables should be made for all multi variable statements? @elliott5

That would certainly be the simplest approach @pxshadow.
The compilation optimisation process should eliminate the temporary variables that are not actually needed, so their existance should not affect the final speed of the code.

The central problem remains that in Go you can write:
a := 42
a , b := 1 , 2

But because a has already been declared, the second declaration (alongside b) is ignored.
This behaviour needs to be modelled by go2hx.
That modelling requires keeping track of which variables have already been declared.
From the Go spec:

Unlike regular variable declarations, a short variable declaration may redeclare variables provided they were originally declared earlier in the same block (or the parameter lists if the block is the function body) with the same type, and at least one of the non-blank variables is new. As a consequence, redeclaration can only appear in a multi-variable short declaration. Redeclaration does not introduce a new variable; it just assigns a new value to the original.

This now works:
Haxe: 4 120
Go: 4 120
function main():Void {
	var _dc:GoInt = (632 : GoInt);
	var _extra:GoInt = (7 : GoInt);
	var _extraMask:GoInt = (127 : GoInt);
	var _0:GoInt = _dc >> _extra,
		_1:GoInt = _dc & _extraMask,
		_fracc:GoInt = _1,
		_dc:GoInt = _0;
	stdgo.fmt.Fmt.println(Go.toInterface(_dc), Go.toInterface(_fracc));
}


Refactor Claims

The current Claims struct is hard to work with, especially during ser/deser. This has led to the need to create helper structs that work around these difficulties.
We should:

refactor Claims to be an enum with variants that have easily accessible fields
remove StoredClaims from the host and use Claims directly
update GetClaimsResponse to use Claims directly, instead of a HashMap<String, String>
update wash and other clients to use the typed data

refs #1119 , if that RFC is accepted we can just remove the claims altogether


Vm 'cloudinit-ubuntu' not found

Hi,
I try to use the package, but I get the following error: Vm 'cloudinit-ubuntu' not found
I don't know why this is happening because the vm with the name (converted as template) exists.

Thanks a lot,
Regards.
Nicolas

I have this problem as well with Proxmox 6.4, and it looks like the issue is that Proxmox 6 expects a numeric vmid rather than a name, and the provider sends a string.
qm clone ubuntu-cloudinit-template 1xx --name test-vm
on the server returns
400 Parameter verification failed.
vmid: type check ('integer') failed - got 'ubuntu-cloudinit-template'
qm clone <vmid> <newid> [OPTIONS]

So unless there's a way to enable names on Proxmox 6, the provider needs to be able to provide numeric IDs.

@mabeltron is that the same thing on PVE 7 ?

@mabeltron @nitrique  right, api need vm id's but under the hood, the hood the provider asks first whats the vmid of the vm you want to clone(based on the name you give) and then clone it
What I see is that you are using a clustered setup, I think that's could be an issue introduced by this PR https://github.com/Telmate/terraform-provider-proxmox/pull/373/files
do you have the same vm clone name on different host? are you connetting to the api endpoint of the node you're cloning to or just the first node on the cluster?

@mleone87 My problem was that I was trying to authenticate with the API and it wasn't working for some reason. Switching to username and password works. It's the first time I've used terraform so I'm feeling around a bit.

I am also hitting this issue.

I am not sure why, but for me I it works if I use a username/password. But with a the API token it does not work. I get the Error: Vm '<vm-template-name>' not found error

@bwks you're right, it works with password but not with api keys, so it's a bug

it's not a bug, your api token has not the correct permission

@mleone87 followed the doc here , can you explain which is the missing one ?

honestly I never needed to create a separate user to do proxmox operations. I simply create api tokens for the root user with no  privileges separation.

I honestly don't know what tests those who pushed that documentation did, but they certainly weren't correct.
If you want follow the path of the docs, just add permission to the role one by one starting from the ones most probable and then report it there so I can send a PR with the correct permissions

I am not sure that its a token permission issue. I assigned all permissions to the role and the token still does not work.
I am using the same user, with the password and that uses the same role (I am pretty sure, but im not a proxmox expert) as if I am using a token.

@mleone87 Your comment about the privilege separation was a clue. Mine was set to Yes, I changed it to No and its working now.
I think we could update the docs to make this clear
pveum user token add terraform-prov@pve terraform-token --privsep=0

@nitrique do you want to give changing the priv sep to no and see if it works for you?

From the Proxmox docs for reference.
https://pve.proxmox.com/wiki/User_Management
API tokens allow stateless access to most parts of the REST API by another system, software or API client. Tokens can be generated for individual users and can be given separate permissions and expiration dates to limit the scope and duration of the access. Should the API token get compromised it can be revoked without disabling the user itself.

API tokens come in two basic types:

    - separated privileges: the token needs to be given explicit access with ACLs, its effective permissions are calculated by intersecting user and token permissions.
    - full privileges: the token permissions are identical to that of the associated user.

Confirmed turning off privilege separation works.
Is there any reason why an authentication error can't be shown in terraform plan?

There's no real reason it can't bubble up that information. We just haven't
plumbed the proxmox-api-go or this provider code to do so yet. As for the
privilege separation = no, that's exactly how I use it and implemented the
api auth for this provider. How to get priv separation working is not
something I've wanted to tackle yet.
On Sun, Nov 14, 2021, 4:33 AM Simon Greenwood @.***>
wrote:

Confirmed turning off privilege separation works.
Is there any reason why an authentication error can't be shown in terraform
plan?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Telmate/terraform-provider-proxmox/issues/432#issuecomment-968256037,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASFVZMQ6MZINODKW7OKEALUL565RANCNFSM5HI3KBKA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

our comment about the privilege separation was a clue. Mine was set to Yes (Default when creating a token), I changed it to No and its working now.

Thanks a lot, you'r a life saver ;) Working now!

It's work for me, the problem of this issue it's there are privilege separation at the token, and you need to declare explicit the permissions to access.
Thanks!

By deleting VM's from the ui, you create an inconsistency between the state files and the real world. The intended solution by HashiCorp is to remove the ressource from the state file by using terraform state rm {ressource} .
devbox@devbox:~/Documents/DevOps$ terraform state list

proxmox_lxc.basic

devbox@devbox:~/Documents/DevOps$ terraform state rm proxmox_lxc.basic

Removed proxmox_lxc.basic

Successfully removed 1 resource instance(s).

Fixed it


UPX BUG

Traceback (most recent call last):
File "C:\Users\PC\AppData\Local\Programs\Python\Python310\lib\site-packages\nuitka\plugins\Plugins.py", line 82, in withPluginProblemReporting
yield
File "C:\Users\PC\AppData\Local\Programs\Python\Python310\lib\site-packages\nuitka\plugins\Plugins.py", line 585, in onCopiedDLLs
plugin.onCopiedDLL(dll_path)
File "C:\Users\PC\AppData\Local\Programs\Python\Python310\lib\site-packages\nuitka\plugins\standard\UpxPlugin.py", line 142, in onCopiedDLL
self._compressFile(filename=dll_filename, use_cache=not self.upx_nocache)
File "C:\Users\PC\AppData\Local\Programs\Python\Python310\lib\site-packages\nuitka\plugins\standard\UpxPlugin.py", line 121, in _compressFile
executeToolChecked(
File "C:\Users\PC\AppData\Local\Programs\Python\Python310\lib\site-packages\nuitka\utils\Execution.py", line 348, in executeToolChecked
logger.sysexit(absence_message)
File "C:\Users\PC\AppData\Local\Programs\Python\Python310\lib\site-packages\nuitka\plugins\PluginBase.py", line 1285, in sysexit
cls.plugin_name + ": " + message, mnemonic=mnemonic, reporting=reporting
TypeError: can only concatenate str (not "NoneType") to str
FATAL: upx: Plugin issue while working on 'DLL 'bin\ArriveUpload.dist\PySide6\QtCore.pyd''. Please report the bug with the above traceback included.
Nuitka-Reports:INFO: Compilation report written to file 'nuitka-crash-report.xml'.
Nuitka-Reports:INFO: Compilation crash report written to file 'nuitka-crash-report.xml'.

In the template, I have made it clear, that not filling out the issue template is not acceptable. I am closing this kind of report as invalid. The main reason is that I do not want to be left guessing. For you it's easy to erase the issue template and expect me to ask you questions only as necessary, but I cannot do that. I would much rather wait for you to create a new report, fill out the template, or wait for somebody with the necessary skill to do it.
In short: No issue template, no fun. Therefore I am likely just deleting the issue, as it serves as a bad example and detraction for searches.  And even worse, it might keep good reporters from reporting as is this "already known."


Content update 7 Feb

Left some comments on the bio of new authors @gkindavishal. LMK if you are able to view those comments. Thanks!

Hi @5wathi
Unable to work on this branch due to the CLA issue with your account. Closing this PR.
New PR: https://github.com/google/devlibrary/pull/607


[Feature Request] Automatically Sync

It would be nice if Cultivation could automatically sync with data from official Genshin servers, or at least showcased servers so maybe we could try out builds with new characters that we want to pull for

Cultivation is just a launcher, it sounds like you're asking for something related to the server-side like Enka plugin (public showcase copying).
There also is absolutely no way to auto sync official data as neither Grasscutter nor Cultivation have such access to official databases or data. Using InventoryKamera or other 3rd party scanning tools on your own PC, or Enka GC plugin for public showcase only is the closest you will get.
Either way, that's something to do be done on your server-side (Grasscutter), not on Cultivation which is just a launcher.