data_asset_name is not recognized in airflow-provider-great-expectations==0.2.0

Hi team, we are working on integrating GX with snowflake datasource into our data validation system via GreatExpectationsOperator .
We are planning to run some expectations validation against a snowflake table named test_sf_table . However, we are getting KeyError: 'data_asset_name test_sf_table is not recognized.' when running our DAG. We have try both upper and lower cases with and without schema, such as data_asset_name: <schema_name>.<table_name> .
Does anyone know what the issue could be? Or is there any configuration issue in my data_context_config, checkpoint_config? Any help would be greatly appreciated ~~
Detailed Info:
we are using
airflow-provider-great-expectations==0.2.0
datasource_config:
sf_url = f'snowflake://{username}:{password}@{account}.{region}/{database}/{schema}?warehouse={warehouse}&role={role}&application=great_expectations_oss'

sf_datasource_config = {
        "class_name": "Datasource",
        "module_name": "great_expectations.datasource",
        "execution_engine": {
            "class_name": "SqlAlchemyExecutionEngine",
            "connection_string": sf_url,
        },
        "data_connectors": {
            "default_runtime_data_connector_name": {
                "class_name": "RuntimeDataConnector",
                "batch_identifiers": ["default_identifier_name"],
            },
            "default_inferred_data_connector_name": {
                "class_name": "InferredAssetSqlDataConnector",
                "include_schema_name": True,
                "included_tables": f"{schema}.test_sf_table".lower()
            },
        },
    }

data_context_config:
base_path = Path(__file__).parents[3]
ge_root_dir = os.path.join(base_path, "include", "great_expectations")
snowflake_data_context_config = DataContextConfig(
    **{
        "config_version": 3.0,
        "datasources": {
            "my_snowflake_datasource": sf_datasource_config
        },
        "stores": {
            "expectations_store": {
                "class_name": "ExpectationsStore",
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "base_directory": os.path.join(ge_root_dir, "expectations"),
                },
            },
            "validations_store": {
                "class_name": "ValidationsStore",
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "base_directory": os.path.join(
                        ge_root_dir, "uncommitted", "validations"
                    ),
                },
            },
            "evaluation_parameter_store": {"class_name": "EvaluationParameterStore"},
            "checkpoint_store": {
                "class_name": "CheckpointStore",
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "suppress_store_backend_id": True,
                    "base_directory": os.path.join(ge_root_dir, "checkpoints"),
                },
            },
        },
        "expectations_store_name": "expectations_store",
        "validations_store_name": "validations_store",
        "evaluation_parameter_store_name": "evaluation_parameter_store",
        "checkpoint_store_name": "checkpoint_store",
        "data_docs_sites": {
            "local_site": {
                "class_name": "SiteBuilder",
                "show_how_to_buttons": True,
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "base_directory": os.path.join(
                        ge_root_dir, "uncommitted", "data_docs", "local_site"
                    ),
                },
                "site_index_builder": {"class_name": "DefaultSiteIndexBuilder"},
            }
        },
        "anonymous_usage_statistics": {
            "data_context_id": "abcdabcd-1111-2222-3333-abcdabcdabcd",
            "enabled": True,
        },
        "notebooks": None,
        "concurrency": {"enabled": False},
    }
)

checkpoint_config:
snowflake_checkpoint_config = CheckpointConfig(
    **{
        "name": "test_sf_checkpoint",
        "config_version": 1.0,
        "template_name": None,
        "module_name": "great_expectations.checkpoint",
        "class_name": "Checkpoint",
        "run_name_template": "%Y%m%d-%H%M%S-test-sf-checkpoint",
        "expectation_suite_name": "sf_test.demo",
        "action_list": [
            {
                "name": "store_validation_result",
                "action": {"class_name": "StoreValidationResultAction"},
            },
            {
                "name": "store_evaluation_params",
                "action": {"class_name": "StoreEvaluationParametersAction"},
            },
            {
                "name": "update_data_docs",
                "action": {"class_name": "UpdateDataDocsAction", "site_names": []},
            },
        ],
        "evaluation_parameters": {},
        "runtime_configuration": {},
        "validations": [
            {
                "batch_request": {
                    "datasource_name": "my_snowflake_datasource",
                    "data_connector_name": "default_inferred_data_connector_name",
                    "data_asset_name": "test_sf_table".lower(),
                    "data_connector_query": {"index": -1},
                },
            }
        ],
        "profilers": [],
        "ge_cloud_id": None,
        "expectation_suite_ge_cloud_id": None,
    }
)

operator:
ge_snowflake_validation = GreatExpectationsOperator(
    task_id="test_snowflake_validation",
    data_context_config=snowflake_data_context_config,
    checkpoint_config=snowflake_checkpoint_config
)

In your datasource config, I've never used this line before:
"included_tables": f"{schema}.test_sf_table".lower()
so it may not be needed/ may be creating an issue with the data_asset_name.
Also, I'd double-check that your table exists, and that your role has access to that table!

Hi @denimalpaca , thank you so much for your quick response.

I specified included_tables because I only want to run some validation on my test_sf_table, and I read this doc: specifying included_tables will have the effect of including only the tables on this list, while excluding the rest https://docs.greatexpectations.io/docs/guides/connecting_to_your_data/how_to_configure_a_dataconnector_to_introspect_and_partition_tables_in_sql/#2-customize-the-introspection-configuration-to-fit-your-needs
I doubled check my snowflake account, and there is a table named "test_sf_table" under my database and schema.

In addition, I want to point out that The operator was able to scan the snowflake tables before throwing the KeyError. I’m also not sure why it scanned all tables, as I already set included_tables in my sf_datasource_config?
[2022-11-21, 22:03:19 EST] {connection.py:274} INFO - Snowflake Connector for Python Version: 2.8.0, Python Version: 3.9.15, Platform: Linux-5.10.76-linuxkit-x86_64-with-glibc2.31
[2022-11-21, 22:03:19 EST] {connection.py:933} INFO - This connection is in OCSP Fail Open Mode. TLS Certificates would be checked for validity and revocation status. Any other Certificate Revocation related exceptions or OCSP Responder failures would be disregarded in favor of connectivity.
[2022-11-21, 22:03:19 EST] {connection.py:951} INFO - Setting use_openssl_only mode to False
[2022-11-21, 22:03:21 EST] {cursor.py:714} INFO - query: [select current_database(), current_schema();]
[2022-11-21, 22:03:21 EST] {cursor.py:738} INFO - query execution done
[2022-11-21, 22:03:21 EST] {cursor.py:854} INFO - Number of results in first chunk: 1

In your datasource config, I've never used this line before: "included_tables": f"{schema}.test_sf_table".lower() so it may not be needed/ may be creating an issue with the data_asset_name.
Also, I'd double-check that your table exists, and that your role has access to that table!

I just removed `included_tables', but still got the same error.
KeyError: 'data_asset_name ... is not recognized.'

I'm wondering what is the data_asset_name, is it just a table name or it has to be {database}.{schema}.{table}? Thank you ~

@talagluck might be able to help here as well.
The data_asset_name should be just the table name in this case. Which version of Great Expectations are you using? I see you're using a newer version of the provider. You can also try using the default checkpoint the provider builds for you and see if that works. An issue may be that you have a different connection in your Airflow Connections than in your GE datasource, this will be resolved if you let the operator build a connection for you.
I noticed in the doc you linked it says "SimpleSqlalchemyDatasource supports a number of configuration options to assist you with the introspection of your SQL database:" and it does not look like you're using a SimpleSqlalchemyDatasource. Not sure if that's the issue, but it may be part of it, and may be why it's doing the full scan still.
Also in your CheckpointConfig, in the batch_request, I'd try removing the .lower() in the data_asset_name and removing the "data_connector_query", neither seem to be needed. (Just trying to see any potential issues here, I know I've had problems with the config files before).

thanks @denimalpaca , I'm trying it right now.

Also in your CheckpointConfig, in the batch_request, I'd try removing the .lower() in the data_asset_name and removing the "data_connector_query", neither seem to be needed. (Just trying to see any potential issues here, I know I've had problems with the config files before).

In the meantime, like I mentioned in the previous thread. I realized that it was able to connect to my snowflake, and did a lot of table scans (including tables outside our my database and schema specified in the sf_url). Do you know why this is happening or there is a way to only scan my specified database and schema?
I feel like maybe this could also be an issue, since there are tons of tables in the snowflake and it could exceed the limit?

Hi @zhangchi1 - there is a known bug around table names in Snowflake that were made explicitly lowercase, since Snowflake defaults to uppercase, while SqlAlchemy defaults to lowercase, and Snowflake makes it somewhat difficult to create and access lowercase tables (you need to wrap them in double quotes).
When you perform simple SELECT statements in your Snowflake environment from the table, do you need to wrap the table name in double quotes, e.g. MY_DB.MY_SCHEMA."test_sf_table"?

hi @talagluck , I tried in my snowflake console UI either way works. But I usually perform select query: SELECT * FROM "MY_DB"."MY_SCHEMA"."MY_TABLE".
Are you saying I should do
sf_datasource_config = {
        "class_name": "Datasource",
        "module_name": "great_expectations.datasource",
        "execution_engine": {
            "class_name": "SqlAlchemyExecutionEngine",
            "connection_string": sf_url,
        },
        "data_connectors": {
            "default_configured_asset_data_connector_name": {
                "class_name": "ConfiguredAssetSqlDataConnector",
                "include_schema_name": True,
                "schema_name": ""MY_SCHEMA"",
                "table_name": ""MY_TABLE"",
            }
        },
    }

Btw, @talagluck I'm wondering do we have any roadmap for using the snowflake-py-connector when datasource=snowflake? I'm also happy to contribute if we have something in common ~ Thank you ~

Hi @zhangchi1 - my mistake. It sounds like the issue is most likely not a lowercase table name issue.
I'm not sure what you mean by this:

I tried the above configs, but still got the keyerror. @talagluck I'm wondering if the issue could be https://github.com/great-expectations/great_expectations/issues/6260 ? Since the great_expectations airflow operator hasn't upgraded with the latest great_expectations version?

What version of great_expectations are you running? More importantly, do you get the same error when running this outside of Airflow with the same configs?

hi @talagluck we are using airflow-provider-great-expectations 0.2.1 and I believe it uses great-expectations>=0.13.14. We are also using it using pure GX outside of Airflow. will keep you posted. Thanks a lot for your continuous support

Hi @talagluck, we are getting the same error with great-expectations Version: 0.15.34.
Here are the configs for you as reference, please feel free to let me know if you find any issues. Thank you so much ~
sf_datasource = DatasourceConfig(class_name="Datasource",
                                 execution_engine={
            "class_name": "SqlAlchemyExecutionEngine",
            "connection_string": sf_url,
        },
                                 data_connectors={
            "default_configured_asset_data_connector_name": {
                "class_name": "ConfiguredAssetSqlDataConnector",
                "include_schema_name": True,
                "schema_name": "MY_SCHEMA",
                "table_name": '"MY_TABLE"',
            },
        })

sf_data_context = DataContextConfig(config_version=3.0,
                                    datasources={"my_snowflake_datasource": sf_datasource},
                                    stores=
                                    {
            "expectations_store": {
                "class_name": "ExpectationsStore",
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "base_directory": os.path.join(ge_root_dir, "expectations"),
                },
            },
            "validations_store": {
                "class_name": "ValidationsStore",
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "base_directory": os.path.join(
                        ge_root_dir, "uncommitted", "validations"
                    ),
                },
            },
            "evaluation_parameter_store": {"class_name": "EvaluationParameterStore"},
            "checkpoint_store": {
                "class_name": "CheckpointStore",
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "suppress_store_backend_id": True,
                    "base_directory": os.path.join(ge_root_dir, "checkpoints"),
                },
            },
        },
                                    expectations_store_name="expectations_store",
                                    validations_store_name="validations_store",
                                    evaluation_parameter_store_name="evaluation_parameter_store",
                                    checkpoint_store_name="checkpoint_store",
                                    data_docs_sites=
                                    {
            "local_site": {
                "class_name": "SiteBuilder",
                "show_how_to_buttons": True,
                "store_backend": {
                    "class_name": "TupleFilesystemStoreBackend",
                    "base_directory": os.path.join(
                        ge_root_dir, "uncommitted", "data_docs", "local_site"
                    ),
                },
                "site_index_builder": {"class_name": "DefaultSiteIndexBuilder"},
            }
        },
                                    anonymous_usage_statistics=
                                    {
            "data_context_id": "abcdabcd-1111-2222-3333-abcdabcdabcd",
            "enabled": True,
        },
                                    notebooks=None,
                                    concurrency={"enabled": False}
                                    )

context = BaseDataContext(project_config=sf_data_context)

sf_checkpoint = Checkpoint(data_context=context, **{
        "name": "test_sf_checkpoint",
        "config_version": 1.0,
        "template_name": None,
        "run_name_template": "%Y%m%d-%H%M%S-test-sf-checkpoint",
        "expectation_suite_name": f"sf_test.demo",
        "action_list": [
            {
                "name": "store_validation_result",
                "action": {"class_name": "StoreValidationResultAction"},
            },
            {
                "name": "store_evaluation_params",
                "action": {"class_name": "StoreEvaluationParametersAction"},
            },
            {
                "name": "update_data_docs",
                "action": {"class_name": "UpdateDataDocsAction", "site_names": []},
            },
        ],
        "evaluation_parameters": {},
        "runtime_configuration": {},
        "validations": [
            {

                "batch_request": {
                    "datasource_name": "my_snowflake_datasource",
                    "data_connector_name": "default_configured_asset_data_connector_name",
                    "data_asset_name": 'MY_TABLE',
                    # "data_connector_query": {"index": -1},
                },
            }
        ]
    })

results = sf_checkpoint.run()

Hi @zhangchi1 , was this issue ever resolved?

hi @denimalpaca, thanks a lot for reminding me. Yes,  I believe adding "assets" field in the "data_connectors" field under "datasource_config" would resolve the issue. I think we can close this issue.


CHAD-8712 Change order of capabilities to reflect DTH

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Bhavik Thati seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[MacOs] Error on task download (sometimes)

Azure DevOps Extensions
WIKI PDF Generator
Platform
Azure DevOps Services
Azure DevOps Server (TFS) Version
All versions
Extension Version
No response
Describe the bug
On MacOs there is an intermittent error after downloading the exe
Starting download azuredevops-export-wiki-osx to /Users/runner/work/_temp
##[error]Forbidden
##[error]Forbidden
(node:1745) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, chmod '/Users/runner/work/_temp/azuredevops-export-wiki-osx'
Downloaded executable /Users/runner/work/_temp/azuredevops-export-wiki-osx
    at Object.chmodSync (fs.js:1027:3)
Set execute permission on executable /Users/runner/work/_temp/azuredevops-export-wiki-osx
    at /Users/runner/work/_tasks/WikiPdfExportTask_48d40d27-32e1-460e-8ea6-0dfb48abdd6f/2.6.2/ExportFunctions.js:135:20
    at Generator.next (<anonymous>)
    at fulfilled (/Users/runner/work/_tasks/WikiPdfExportTask_48d40d27-32e1-460e-8ea6-0dfb48abdd6f/2.6.2/ExportFunctions.js:5:58)
(node:1745) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1745) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This this the same as MaxMelcher/AzureDevOps.WikiPDFExport # 108
Repo Steps

Run a pipeline that includes the task on a Mac
On around 50% fail with the error

Note: never seen on other OS
Expected Behavior
Task should always run
Logging Information
No response

WORKAROUND
I have seen this problem in my testing. It appears to be an issue with the MAC Agents being unable to download the PDF tool from GitHub, a retry usually fixes it.
The most reliable workaround is to place the azuredevops-export-wiki-osx MAC exe in your own repo and avoid the need to download it from GitHub each time.
FYI: I can't ship the EXE within the Azure DevOps task as it makes the package too big

We  think it's getting a HTTP 403, and not actually downloading it
On the ones that worked, 'Download done' is printed out, but the one that didn't got a 'Forbidden'
AzurePipelines/ExportFunctions.ts at 63bf38c4df02d85966db708864158f63635b1a12 · rfennell/AzurePipelines · GitHub
has a .catch() without a re-throw, so it'll continue on without actually stopping
Doesn't help at all explain why it's getting a forbidden at all, or why it'd be intermittent... which makes no real sense


Checkpoint on Canopy

Motivation
We want to checkpoint in Canopy to avoid the development of some validation code. More details in https://github.com/ZcashFoundation/zebra/issues/1846
Solution
Change the mandatory checkpoint from Sapling to Canopy in the testnet and in the mainnet.
I synchronized zebra using this PR up to tip in 2 hours and 40 minutes. This is an improve (expected) from the last tries in the same machine of 3 hours.
In this PR mainnet checkpoints were upgraded while testnet ones were already passing Canopy so this was not needed.
Review
@teor2345
Related Issues
If merged this PR will close https://github.com/ZcashFoundation/zebra/issues/1846

In this PR mainnet checkpoints were upgraded while testnet ones were already passing Canopy so this was not needed.

Please update both mainnet and testnet checkpoints for consistency. Otherwise, our testnet checkpoints will be very old.

In this PR mainnet checkpoints were upgraded while testnet ones were already passing Canopy so this was not needed.

Please update both mainnet and testnet checkpoints for consistency. Otherwise, our testnet checkpoints will be very old.

I pushed this change.
In general, we want to keep both checkpoint lists up to date, whenever we change one of them.

I also want to checkout this PR, and make sure we've replaced every relevant instance of Sapling with Canopy.

There were lots of missing changes.
Please use an interactive search and replace tool to create future PRs like this.
I used the following commands:
fastmod Sapling Canopy
fastmod sapling canopy
fastmod sapling canopy .github

Then I checked each change to make sure that it was correct. (Sapling is the name of a network upgrade, and a shielded pool, so we can't just do an automatic search and replace.)
The .github command was required because fastmod ignores dotfiles by default.
(I also needed to remove smart quotes, due to a bug in fastmod's unicode handling. See #1902.)

@dconnolly this PR changes the cached tests to use Canopy, so it will require a cached state rebuild.
Can you show @oxarbitrage how to do that?

* I didn't changed the RFCs in the initial PR because i wasn't sure if that was something we should do, for example i am unsure if a ZIP can be changed after is implemented. In this case i think is ok.

In general, I don't think we need to spend a lot of effort updating RFCs - if there is a significant change, we should do a rewrite or a new RFC.
But in this case, it took only a few minutes to update. And I didn't want us to get confused between Sapling and Canopy checkpoints.


Don't use null for comparefn, rely on undefined per spec http://www.ecma-international.org/ecma-262/5.1/#sec-<IP_ADDRESS>

For our in browser fork, I'm getting top-level errors thrown when trying to do HTML code hints in Firefox:
"Exception in 'change' listener on" Object { document: Object, _handleDocumentChange: function (), _handleDocumentDeleted: function (), _handleDocumentLanguageChanged: function (), _inlineWidgets: Array[0], _inlineWidgetQueues: Object, _hideMarks: Array[0], _lastEditorWidth: 474, _$messagePopover: null, _currentOptions: Object, 6 more… } "TypeError: Not enough arguments to Console.assert." "d@http://humphd.github.io/brackets/dist/main.js:12:3893
s.prototype._handleEditorChange@http://humphd.github.io/brackets/dist/main.js:23:24680
s/<@http://humphd.github.io/brackets/dist/main.js:23:18133
d@http://humphd.github.io/brackets/dist/main.js:12:3784
s.prototype._installEditorListeners/<@http://humphd.github.io/brackets/dist/main.js:23:25373
e.signal@http://humphd.github.io/brackets/dist/main.js:8:25576
hn@http://humphd.github.io/brackets/dist/main.js:5:25993
ln@http://humphd.github.io/brackets/dist/main.js:5:23561
sn@http://humphd.github.io/brackets/dist/main.js:5:23360
Mn@http://humphd.github.io/brackets/dist/main.js:5:31075
An/<@http://humphd.github.io/brackets/dist/main.js:6:1189
"

The cause is the explicit use of null vs. undefined for the comparefn passed to Array.prototype.sort.  Leaving sortFunc with an implicit value of undefined here makes it work in all browsers.  Chrome is just a bit more permissive in what it allows in this case.

In line 235, there's the exact same issue again. Also, it looks like up there, sortFunc is always null.

Good catch, fixed.  I found another one in UrlCodeHints too.  I had a look at other uses of sort in the tree, but didn't see any that had this issue.

@MarcelGerber how does that look?  Can we move this forward?

Looks great, but I, for myself, can't move this forward - I'm not part of the team.

LGTM

@humphd This looks fine to me. Could you run our unit tests and update us if they are all passing. I could then go ahead with the merge. Thanks!

I rebased this onto master and ran all the tests within Brackets.  Everything passed for me.  NOTE: running the entire suite caused some timeouts and random fails that I can't reproduce in isolated runs on the failing specs, and all in areas unrelated to this change.  The tests seem to bog down my machine as they run, and I don't have experience running the entire suite and knowing how it should perform.

It sounds like they're passing. Take a look at this wiki page.

Thanks @humphd !


main-branch-name: $CIRCLE_BRANCH always returns the same value for both the Base SHA and Head SHA

Orb version:

<EMAIL_ADDRESS>What happened:

I pass $CIRCLE_BRANCH to the nx/set-shas command, but I always receive the same value for both the Base SHA and the Head SHA.
Output of Derives SHAs for base and head for use in nx affected commands:
Commit: 3f835dfe18a35cfc74bf4a2773d366f09c298f8b
Base SHA
3f835dfe18a35cfc74bf4a2773d366f09c298f8b

Head SHA
3f835dfe18a35cfc74bf4a2773d366f09c298f8b

NX_BASE and NX_HEAD environment variables have been set for the current Job

Expected behavior:

The Base SHA should represent the last successful workflow run on 'origin/feature-branch'.
Additional Information:

.circleci/config.yml:
version: 2.1

orbs:
  node<EMAIL_ADDRESS>  nx<EMAIL_ADDRESS>
jobs:
  affected_test:
    executor:
      name: node/default
      tag: '18.16.0'
    steps:
      - checkout
      - node/install-packages
      - nx/set-shas:
          main-branch-name: $CIRCLE_BRANCH # <- Use $CIRCLE_BRANCH built-in environment variables
      - run: npx nx affected -t test --base=$NX_BASE --head=$NX_HEAD

workflows:
  lint_and_test_build:
    jobs:
      - affected_test:
          context:
            - circleci # <- Access CircleCI Context to get $CIRCLE_API_TOKEN

I discovered the compiled CircleCI config:
environment:
  PARAM_ALLOW_ON_HOLD: false
  PARAM_ERROR_ON_NO_SUCCESSFUL_WORKFLOW: false
  PARAM_MAIN_BRANCH: $CIRCLE_BRANCH # <- The string $CIRCLE_BRANCH itself, not its value

So the if...else condition in find-successful-workflow.js is actually:
if ('feature-branch' !== '$CIRCLE_BRANCH') {
  // ...
} else {
  // ...
}

Finally, the execSync in find-successful-workflow.js actually executes the following command in bash:
git merge-base origin/$CIRCLE_BRANCH HEAD

That is the cause of this problem.

As you can see here https://github.com/nrwl/nx-orb/blob/main/src/scripts/set-shas.sh#L3-L8 the $CIRCLE_BRANCH is automatically read from the global environment, so there's no need to pass it.
If the intent were to compare the top of the feature-branch with its last successful build (which is not something we would recommend on branches), then you can, unfortunately, you would have to come up with a trick since CircleCI does not support interpolation when setting environment variables.
Check this article for idea how to use the $CIRCLE_BRANCH as pass it to MAIN_BRANCH_NAME environment variable:
https://circleci.com/docs/set-environment-variable/#set-an-environment-variable-in-a-shell-command


Close doc

How do i free the memory being used by doc when i am done with it. Something like Close or Free ?

Hello Ridwan,
You don't need to, there are no resources to free (well, except heap memory but Go is a garbage collected language as you may know).
Have fun with your project!
Martin


Floating point seems to return incorrectly

What happens?
We started noticing a weird behavior in our application with a query like this:
 SELECT 1234.5678 as floating_number;
It was returning the value for floating_number as the integer 12345678 instead of floating 1234.5678.
A query like SELECT 20/3 as floating_number does return 6.666666666666667 correctly.
I isolated the code and it seems like its duck wasm (we use npm typescript package) returning the value incorrectly.
To Reproduce
I created these tests to illustrate whats going on (sorry they are a bit ugly):
// eslint-disable-next-line node/no-extraneous-import
import * as duckdb from '@duckdb/duckdb-wasm';
// eslint-disable-next-line node/no-extraneous-import
import Worker from 'web-worker';

describe('Floating point', () => {
  let c: duckdb.AsyncDuckDBConnection;
  let worker: Worker;
  let db: duckdb.AsyncDuckDB;

  beforeAll(async () => {
    // eslint-disable-next-line node/no-extraneous-require
    const resolvePath = require.resolve('@duckdb/duckdb-wasm');
    const distMatch = resolvePath.match(/^.*\/dist\//);
    const dist = distMatch![0];

    const bundle = await duckdb.selectBundle({
      mvp: {
        mainModule: `${dist}/duckdb-mvp.wasm`,
        mainWorker: `${dist}/duckdb-node-mvp.worker.cjs`,
      },
      eh: {
        mainModule: `${dist}/duckdb-eh.wasm`,
        mainWorker: `${dist}/duckdb-node-eh.worker.cjs`,
      },
    });

    worker = new Worker((await bundle).mainWorker);

    const logger = new duckdb.ConsoleLogger();
    db = new duckdb.AsyncDuckDB(logger, worker);

    await db.instantiate(bundle.mainModule, bundle.pthreadWorker);

    c = await db.connect();
  });

  test('Division returns correctly', async () => {
    const result = await c.query('SELECT 20/3 as my_num;');
    expect(
      JSON.stringify(result.batches[0]['data']['children'][0]['values']['0'])
    ).toBe('6.666666666666667');
  });

  test('Floating returns correctly', async () => {
    const result = await c.query('SELECT 1234.5678 as my_num;');
    expect(
      JSON.stringify(result.batches[0]['data']['children'][0]['values']['0'])
    ).toBe('1234.5678');
  });

  afterAll(async () => {
    await c.close();
    await db.terminate();
    await worker.terminate();
  });
});

Browser/Environment:
Node (can try to check which version of Chromium is using)
Device:
Linux
DuckDB-Wasm Version:
0.0.56
DuckDB-Wasm Deployment:
Node typescript
Full Name:
Fernando Arreola
Affiliation:
Malloy (Google)

Its wasm version NPM package 1.27.0.

It prints Float64Array(1) [ 6.666666666666667 ] in the first test.
And Uint32Array(4) [ 12345678, 0, 0, 0 ] in the second.

Can I reply to this issue like this:
Hi @narreola! Carlo and I had a look at this. We used the following .mjs file for a reproducible test. In the test, we pass a flag that sets the castDecimalToDouble-config in duckdb if true. This lets you grab a DOUBLE (Float64Array(1)) from your arrow-result with your current approach (result.batches[0]['data']['children'][0]).
// eslint-disable-next-line node/no-extraneous-import
import * as duckdb from '@duckdb/duckdb-wasm';
// eslint-disable-next-line node/no-extraneous
import Worker from 'web-worker';

async function test(castDecimalToDouble) {

    // Instantiate the asynchronus version of DuckDB-wasm
    const worker = new Worker(new URL('duckdb-node-eh.worker.cjs', import.meta.url).toString());
    const logger = new duckdb.ConsoleLogger();
    const db = new duckdb.AsyncDuckDB(logger, worker);
    await db.instantiate("duckdb-eh.wasm", "");

    if (castDecimalToDouble) {
        await db.open({
            query: {
                castDecimalToDouble: true,
            },
        });
    }
    var c = await db.connect();

    {
        const result = await c.query('SELECT 20/3 as my_num;');
        console.log(result.batches[0]['data']['children'][0]);
    } {
        const result = await c.query('SELECT 1234.5678 as my_num;');
        console.log(result.batches[0]['data']['children'][0]);
    }

    await c.close();
    await db.terminate();
    await worker.terminate();
};

await test(false); // default behaviour
await test(true); // opt-in

Alternatively, you can use the result type to access the result. It sets type: Decimal { scale: 4, precision: 8, bitWidth: 128 }, which contains the scale and precision to construct a decimal value. So when encountering a decimal type, only accessing the value via result.batches[0]['data']['children'][0] is not enough, as the information about the value is encoded in its type.
{
  timestamp: 2023-09-15T09:21:45.418Z,
  level: 2,
  origin: 4,
  topic: 4,
  event: 4,
  value: 'SELECT 20/3 as my_num;'
}
Data {
  type: Float { precision: 2 },
  children: [],
  dictionary: undefined,
  offset: 0,
  length: 1,
  _nullCount: 0,
  stride: 1,
  values: Float64Array(1) [ 6.666666666666667 ],
  nullBitmap: Uint8Array(0) [],
  nullable: false
}
{
  timestamp: 2023-09-15T09:21:45.443Z,
  level: 2,
  origin: 4,
  topic: 4,
  event: 4,
  value: 'SELECT 1234.5678 as my_num;'
}
Data {
  type: Decimal { scale: 4, precision: 8, bitWidth: 128 },
  children: [],
  dictionary: undefined,
  offset: 0,
  length: 1,
  _nullCount: 0,
  stride: 4,
  values: Uint32Array(4) [ 12345678, 0, 0, 0 ],
  nullBitmap: Uint8Array(0) [],
  nullable: false
}

A third option would be to force using DOUBLE via SELECT value::DOUBLE... :thinking:
(cc @carlopi)


Feature/sat db bin

Description
This PR adds the satellite database utility into swell that will take the active_channels table from GEOSana_GridComp and convert it into satellite yaml files. It also extends the jedi_config task to modify channel ranges and delete obs filters in the config.
Acceptance Criteria (Definition of Done)
Satellite database utility has been added and tested. Jedi_config task has been updated and tested.

Thanks for adding all this @asewnath. For me it now works from beginning to end of the workflow so I'm not sure why you were seeing the errors you were seeing. I made a few 'big picture' edits that can be seen here: https://github.com/GEOS-ESM/swell/pull/19/commits/dd5d91c318c596a55faf29e3b218508859d4074c. Mainly this was to do away with the $NOBACKUP path for the yaml files that you generated and instead move the pre-generated yaml files into swell. In the future you should be able to use your utility to regenerate these files and add them to swell where we can version control them.


Multiple accounts dont show up in pick list

Mac OS 13.4.1 (22F82)
Latest 1Password Plugin version
1Password for Mac 8.10.8 (81008045)
Runelite 2.6.3
When one 1Password file with https://runescape.com exists, the plugin works like expected.
When multiple entries in 1Password exist with https://runescape.com exist, the picker drop down field is blank:

Would love to be able to use this plugin, but right now am big sad :(

Bump :(


isar_flutter_libs_plugin.dll is flagged as infected

Steps to Reproduce

Create a new Flutter project
Install isar, isar_flutter_libs and isar_generator (no need to even import in dart files)
Build and run the application either in Release or Debug mode
Notice Bitdefender flagging isar_flutter_libs_plugin.dll as infected with Gen:Variant.Tedy.191473

Code sample
name: my_app
description: An example app

publish_to: 'none'
version: 1.0.0+1

environment:
  sdk: ">=2.15.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  cupertino_icons: ^1.0.2
  xml: ^5.3.1
  file_picker: ^4.6.1
  path_provider: ^2.0.11
  yaml: ^3.1.1
  crypto: ^3.0.2
  yaml_writer: ^1.0.2
  isar: ^2.5.0
  isar_flutter_libs: ^2.5.0

dev_dependencies:
  isar_generator: ^2.5.0
  build_runner: any

  flutter_test:
    sdk: flutter

  flutter_lints: ^1.0.0

flutter:
  uses-material-design: true

Version

Platform: Windows
Flutter version: 3.0.5
Isar version: 2.5.0
Isar Generator version: 2.5.0
VirusTotal analysis

I've compiled this dll myself and it does not contain any malicious code.
Unfortunately this is a common problem with software virus scanners haven't seen before 😞

I just ran the latest and the 2.5.0 Isar dll and it does not show any results. I can't reproduce your results.
Isar 2.5.0 result
Isar 3.0.0-dev.10 result

Thank you for taking the time to reproduce the issue !
How strange, I'll try to create a minimal repository and link it here so we have the same source

Here is the repository hopefully it can help you reproduce.

I double checked your result and noticed the file you uploaded is named isar_windows_x64-2.dll, not isar_flutter_libs_plugin.dll, is it the same file ? It doesn't have the same imports as my file either

But the isar_flutter_libs_plugin depends on your app code. I uploaded Isar Core.

But the isar_flutter_libs_plugin depends on your app code. I uploaded Isar Core.

Oh I see ! Thank you for the clarification.
Could you have a look at this repository and see if you can reproduce the issue ?
It is a newly created repository.
Please note:

I didn't touch anything beside the pubspec.yaml so I am almost sure there are no viruses 😅.
in the pubspec.yaml I changed the name, description and  added the three Isar libraries isar, isar_flutter_libs, isar_generator
if you remove isar_flutter_libs there should not be any issue, so I guess isar_flutter_libs adds some wrapper or injects code that is flagged as a virus

Unfortunately I don't think I can fix this since Isar is not doing anything malicious. Going to close this for now.

I got the same issue as well


Separate difficulties

Lno submitted a feature request: Separate difficulties
Allow for each user to select independent difficulties on maps in multi player.

Despite being a smart bot, I can not automagically respond to the user if you have any feedback to give them. Thus, if you wish to tell 'em something, respond here: https://ripple.moe/index.php?p=114&id=61

wut?

Chiede di poter scegliere di giocare a diverse difficoltà ma stessa mappa,
cosa non possibile da client credo
Il lun 4 apr 2016 10:06 Nyo<EMAIL_ADDRESS>ha scritto:

Closed #124 https://github.com/osuripple/ripple/issues/124.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/osuripple/ripple/issues/124#event-613220061

--
Ora uso un nuovo indirizzo email (marco.bassetto@protonmail.com), se vuoi
rispondermi per favore usa quello.


org.apache.hc.core5.http.NoHttpResponseException: localhost:2375 failed to respond

Issue
When we execute ./pack.java within the samples/hello-quarkus, we got this error
[main] INFO dev.snowdrop.buildpack.lifecycle.LifecyclePhaseFactory - - mounted /var/run/docker.sock at /var/run/docker.sock
[main] INFO dev.snowdrop.buildpack.lifecycle.LifecyclePhaseFactory - - mounted buildpack-output-qehdanxvwx at /layers
[main] INFO dev.snowdrop.buildpack.lifecycle.LifecyclePhaseFactory - - container id 3619cb8b340e26f66223169034641611c912d0f549a74d354d130cd6b09cee64
[main] INFO dev.snowdrop.buildpack.lifecycle.LifecyclePhaseFactory - - image reference 831c5292e451cf401acecb2e1e661e4d2f94c661da503c7a0b4d3a728169f993
[main] INFO dev.snowdrop.buildpack.lifecycle.phases.Restorer - - restorer container id 3619cb8b340e26f66223169034641611c912d0f549a74d354d130cd6b09cee64 will be run with uid 1002 and args [/cnb/lifecycle/restorer, -uid, 1002, -gid, 1000, -layers, /layers, -cache-dir, /cache-dir, -log-level, debug, -build-image, paketocommunity/builder-ubi-base:latest]
- restorer container id 3619cb8b340e26f66223169034641611c912d0f549a74d354d130cd6b09cee64 will be run with uid 1002 and args [/cnb/lifecycle/restorer, -uid, 1002, -gid, 1000, -layers, /layers, -cache-dir, /cache-dir, -log-level, debug, -build-image, paketocommunity/builder-ubi-base:latest]
[main] INFO dev.snowdrop.buildpack.lifecycle.phases.Restorer - - launching restorer container
[main] INFO dev.snowdrop.buildpack.lifecycle.phases.Restorer - - attaching log relay
[docker-java-stream--1039344372] ERROR com.github.dockerjava.api.async.ResultCallbackTemplate - Error during callback
java.lang.RuntimeException: org.apache.hc.core5.http.NoHttpResponseException: localhost:2375 failed to respond
        at com.github.dockerjava.httpclient5.ApacheDockerHttpClientImpl.execute(ApacheDockerHttpClientImpl.java:195)
        at com.github.dockerjava.httpclient5.ApacheDockerHttpClient.execute(ApacheDockerHttpClient.java:9)
        at com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:228)
        at com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269)
        at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: org.apache.hc.core5.http.NoHttpResponseException: localhost:2375 failed to respond
        at org.apache.hc.core5.http.impl.io.DefaultHttpResponseParser.createConnectionClosedException(DefaultHttpResponseParser.java:87)
        at org.apache.hc.core5.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:243)
        at org.apache.hc.core5.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:53)
        at org.apache.hc.core5.http.impl.io.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:187)
        at org.apache.hc.core5.http.impl.io.HttpRequestExecutor.execute(HttpRequestExecutor.java:175)
        at com.github.dockerjava.httpclient5.HijackingHttpRequestExecutor.execute(HijackingHttpRequestExecutor.java:50)
        at org.apache.hc.core5.http.impl.io.HttpRequestExecutor.execute(HttpRequestExecutor.java:218)
        at org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager$InternalConnectionEndpoint.execute(PoolingHttpClientConnectionManager.java:596)
        at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.execute(InternalExecRuntime.java:215)
        at org.apache.hc.client5.http.impl.classic.MainClientExec.execute(MainClientExec.java:107)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement$1.proceed(ExecChainElement.java:57)
        at org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:181)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement$1.proceed(ExecChainElement.java:57)
        at org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:172)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement$1.proceed(ExecChainElement.java:57)
        at org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:93)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement$1.proceed(ExecChainElement.java:57)
        at org.apache.hc.client5.http.impl.classic.ContentCompressionExec.execute(ContentCompressionExec.java:128)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement$1.proceed(ExecChainElement.java:57)
        at org.apache.hc.client5.http.impl.classic.RedirectExec.execute(RedirectExec.java:116)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.InternalHttpClient.doExecute(InternalHttpClient.java:178)
        at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:67)
        at com.github.dockerjava.httpclient5.ApacheDockerHttpClientImpl.execute(ApacheDockerHttpClientImpl.java:191)
        ... 4 more

If I re-execute the command ./pack.java, then error is gone. Really strange !!
Useful information
Branch/PR: `platform-12`
Java JDK: 17.0.11
Podman: 5.0.2 rootful

@BarDweller

@cmoulliard  I'm unable to recreate this, and I haven't seen the integration tests report this either
The stack trace indicates that localhost:2375 doesn't answer..
That isn't a host/port configured in the quarkus-sample, but it is a port normally used by docker when communicating via tcp, have you altered pack.java locally? what configuration are you attempting to build with? (eg, DOCKER_HOST value, podman/docker version)
The log above indicates it's mounting in /var/run/docker.sock (expected as the destination image doesn't contain a registry reference).. so it's unclear why the container would be choosing to use tcp via localhost:2375 .. It's getting all the way through the restorer phase too, which is a fair way thru the build, yet I'm guessing this error didn't occur before that, which is odd, as there's nothing special about restorer that would cause it to access the daemon differently..
If this is repeatable for you, it might be interesting to capture more trace to figure out what the root cause is.

That isn't a host/port configured in the quarkus-sample, but it is a port normally used by docker when communicating via tcp, have you altered pack.java locally? what configuration are you attempting to build with? (eg, DOCKER_HOST value, podman/docker version)

This issue occurs from time to time. I got it the first time I executed ./pack.java with the Quarkus hello sample, podman 5.0.3 and DOCKER_HOST="unix:///var/run/docker.sock" but not the second time :-(
Nevertheless, end of the build using podman, I got this error
2024-06-11T11:00:14+02:00       [INFO] Compiling 2 source files with javac [debug target 1.8] to target/classes
2024-06-11T11:00:15+02:00       [INFO] -------------------------------------------------------------
2024-06-11T11:00:15+02:00       [WARNING] COMPILATION WARNING :
2024-06-11T11:00:15+02:00       [INFO] -------------------------------------------------------------
2024-06-11T11:00:15+02:00       [WARNING] bootstrap class path not set in conjunction with -source 8
2024-06-11T11:00:15+02:00       [INFO] 1 warning
2024-06-11T11:00:15+02:00       [INFO] -------------------------------------------------------------
2024-06-11T11:00:15+02:00       [INFO] -------------------------------------------------------------
2024-06-11T11:00:15+02:00       [ERROR] COMPILATION ERROR :
2024-06-11T11:00:15+02:00       [INFO] -------------------------------------------------------------
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[4,1] package dev.snowdrop.buildpack does not exist
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[5,1] package dev.snowdrop.buildpack.config does not exist
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[6,1] package dev.snowdrop.buildpack.docker does not exist
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[21,33] cannot find symbol
2024-06-11T11:00:15+02:00         symbol:   class SystemLogger
2024-06-11T11:00:15+02:00         location: class dev.snowdrop.pack
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[19,38] cannot find symbol
2024-06-11T11:00:15+02:00         symbol:   class ImageReference
2024-06-11T11:00:15+02:00         location: class dev.snowdrop.pack
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[18,39] cannot find symbol
2024-06-11T11:00:15+02:00         symbol:   class ImageReference
2024-06-11T11:00:15+02:00         location: class dev.snowdrop.pack
2024-06-11T11:00:15+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[17,24] cannot find symbol
2024-06-11T11:00:15+02:00         symbol:   variable BuildConfig
2024-06-11T11:00:15+02:00         location: class dev.snowdrop.pack
2024-06-11T11:00:15+02:00       [INFO] 7 errors
2024-06-11T11:00:15+02:00       [INFO] -------------------------------------------------------------
2024-06-11T11:00:15+02:00       [INFO] ------------------------------------------------------------------------
2024-06-11T11:00:15+02:00       [INFO] BUILD FAILURE
2024-06-11T11:00:15+02:00       [INFO] ------------------------------------------------------------------------
2024-06-11T11:00:16+02:00       [INFO] Total time:  02:16 min
2024-06-11T11:00:16+02:00       [INFO] Finished at: 2024-06-11T09:00:15Z
2024-06-11T11:00:16+02:00       [INFO] ------------------------------------------------------------------------
2024-06-11T11:00:16+02:00       [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.1:compile (default-compile) on project quarkus-hello: Compilation failure: Compilation failure:
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[4,1] package dev.snowdrop.buildpack does not exist
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[5,1] package dev.snowdrop.buildpack.config does not exist
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[6,1] package dev.snowdrop.buildpack.docker does not exist
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[21,33] cannot find symbol
2024-06-11T11:00:16+02:00       [ERROR]   symbol:   class SystemLogger
2024-06-11T11:00:16+02:00       [ERROR]   location: class dev.snowdrop.pack
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[19,38] cannot find symbol
2024-06-11T11:00:16+02:00       [ERROR]   symbol:   class ImageReference
2024-06-11T11:00:16+02:00       [ERROR]   location: class dev.snowdrop.pack
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[18,39] cannot find symbol
2024-06-11T11:00:16+02:00       [ERROR]   symbol:   class ImageReference
2024-06-11T11:00:16+02:00       [ERROR]   location: class dev.snowdrop.pack
2024-06-11T11:00:16+02:00       [ERROR] /workspace/src/main/java/dev/snowdrop/pack.java:[17,24] cannot find symbol
2024-06-11T11:00:16+02:00       [ERROR]   symbol:   variable BuildConfig
2024-06-11T11:00:16+02:00       [ERROR]   location: class dev.snowdrop.pack
2024-06-11T11:00:16+02:00       [ERROR] -> [Help 1]
2024-06-11T11:00:16+02:00       [ERROR]
2024-06-11T11:00:16+02:00       [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2024-06-11T11:00:16+02:00       [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2024-06-11T11:00:16+02:00       [ERROR]
2024-06-11T11:00:16+02:00       [ERROR] For more information about the errors and possible solutions, please read the following articles:
2024-06-11T11:00:16+02:00       [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
2024-06-11T11:00:16+02:00 unable to invoke layer creator
2024-06-11T11:00:16+02:00 unable to contribute application layer
2024-06-11T11:00:16+02:00 error running build
2024-06-11T11:00:16+02:00 exit status 1
2024-06-11T11:00:16+02:00       Timer: Builder ran for 2m32.471688152s and ended at 2024-06-11T09:00:16Z
2024-06-11T11:00:16+02:00 ERROR: failed to build: exit status 1
[main] INFO dev.snowdrop.buildpack.lifecycle.phases.Extender - Buildpack extender container complete, with exit code 51
[main] INFO dev.snowdrop.buildpack.lifecycle.LifecyclePhaseFactory - - tidying up the build volumes
[main] INFO dev.snowdrop.buildpack.lifecycle.LifecyclePhaseFactory - - build volumes tidied up

Closing as still unable to recreate.


Fix heredoc intention

Hi @ikeikeikeike,
Thanks for this ❤ we use this in production.
I fixed the heredoc intention warning

Hello, @Schultzer! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

thx


Items: reducer action to select multiple items

So we can replace this code for the "Some" action:
method: (indices: number[]) => {
    for (const index of indices) {
        dispatch(new SelectItem(listIndex, index, true));
    }
},

Commit: https://github.com/johneastman/todo/commit/781791ecec476a604e5e1add728effbe44492b15


Check feasibility of sampled discrete parameters in CMAwM

Check the feasibility of all parameters instead of only continuous ones.
ref: https://github.com/CyberAgentAILab/cmaes/pull/136

Good catch! I applied your comment.


refactor!: update module to v4

BREAKING CHANGE: update go module to v4

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-gpio/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

Run make test, make docker, test with core services.
New Dependency Instructions (If applicable)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (681c980) to head (9f02b45).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main    #240   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          5       5
  Lines        236     236
=====================================
  Misses       236     236

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


MapperIgnore attributes not being generated on IQueryable

Describe the bug
When creating a new mapper class, if you only have an IQueryable mapping method, the MapperIgnore attributes are not honoured and will continue to generate the properties. If you add the same mapping method without the non-IQueryable, it will properly generate both the IQueryable and non-IQueryable ignored properties.
To Reproduce
Steps to reproduce the behaviour:

Create a new mapper class
Add a mapping method IQueryable<CarDto> ProjectToDto(this IQueryable<Car> car);
Add an MapperIgnoreTarget attribute on the Tires property [MapperIgnoreTarget(nameof(CarDto.Tires))]
3a. The generated code will still have the Tires property
Add another mapping method CarDto ToDto(this Car car);
Add the same MapperIgnoreTarget attribute on the new mapping method [MapperIgnoreTarget(nameof(CarDto.Tires))]
5a. The generated code will correctly ignore the Tires property on both mapping methods

Expected behavior
At 3a, the generated code should ignore the Tires property regardless of whether a non-IQueryable mapping method is present or not.
Code snippets
The models and dtos are the same as the ones provided in the docs. The mapping class is as followed as of step 3a:
[Mapper]
public static partial class CarMapper
{
   [MapperIgnoreTarget(nameof(CarDto.Tires))]
   public static partial IQueryable<CarDto> ProjectToDto(this IQueryable<Car> car);
}

Here is the mapping class as of step 5a:
[Mapper]
public static partial class CarMapper
{
   [MapperIgnoreTarget(nameof(CarDto.Tires))]
   public static partial IQueryable<CarDto> ProjectToDto(this IQueryable<Car> car);

   [MapperIgnoreTarget(nameof(CarDto.Tires))]
   public static partial CarDto ToDto(this Car car);
}

Environment:

Mapperly Version: 3.2.0
.NET Version: 7.0.302
Target Framework: net6.0
IDE: Visual Studio Professional 2022 v17.6.2
OS: Windows 10 Pro build 19045.3570

Mapperly attributes are alyways applied to the parameter / return type of mapping methods. This should work:
[Mapper]
public static partial class CarMapper
{
   public static partial IQueryable<CarDto> ProjectToDto(this IQueryable<Car> car);

   [MapperIgnoreTarget(nameof(CarDto.Tires))]
   public static partial CarDto ToDto(this Car car);
}

Mapperly uses the configuration of ToDto to build the mapping of the IQueryable.


serialize/unserialize methods are deprecated since Symfony 4.3

Changes
Fixed deprecation notices for Auth0\JWTAuthBundle\Security\Core\JWTInfoNotFoundException exception by extending __serialize and __unserialize instead of serialize and unserialize.
References
Following an implementation on PHP 7.2 / Symfony 4.3, after writing tests for our implementation that are referencing the JWTInfoNotFoundException exception, and by using the PHPUnit Bridge from Symfony which checks for Symfony deprecations, it accurately outputted:
  1x: The "Symfony\Component\Security\Core\Exception\AuthenticationException::serialize()" method is considered final since Symfony 4.3, use __serialize() instead. It may change without further notice as of its next major version. You should not extend it from "Auth0\JWTAuthBundle\Security\Core\JWTInfoNotFoundException".
    1x in Auth0UserProviderTest::testLoadUserByJWT_noSubProperty from App\Tests\Security

  1x: The "Symfony\Component\Security\Core\Exception\AuthenticationException::serialize()" method is considered internal since Symfony 4.3, use __serialize() instead. It may change without further notice. You should not extend it from "Auth0\JWTAuthBundle\Security\Core\JWTInfoNotFoundException".
    1x in Auth0UserProviderTest::testLoadUserByJWT_noSubProperty from App\Tests\Security

  1x: The "Symfony\Component\Security\Core\Exception\AuthenticationException::unserialize()" method is considered final since Symfony 4.3, use __unserialize() instead. It may change without further notice as of its next major version. You should not extend it from "Auth0\JWTAuthBundle\Security\Core\JWTInfoNotFoundException".
    1x in Auth0UserProviderTest::testLoadUserByJWT_noSubProperty from App\Tests\Security

  1x: The "Symfony\Component\Security\Core\Exception\AuthenticationException::unserialize()" method is considered internal since Symfony 4.3, use __unserialize() instead. It may change without further notice. You should not extend it from "Auth0\JWTAuthBundle\Security\Core\JWTInfoNotFoundException".
    1x in Auth0UserProviderTest::testLoadUserByJWT_noSubProperty from App\Tests\Security

Testing
PHPUnit output:
PHPUnit 5.7.27 by Sebastian Bergmann and contributors.

....                                                                4 / 4 (100%)

Time: 354 ms, Memory: 12.00MB

OK (4 tests, 12 assertions)

[x] This change has been tested on the latest version of Symfony
Checklist
[x] I have read the Auth0 general contribution guidelines
[x] I have read the Auth0 Code of Conduct
[x] All existing and new tests complete without errors

@chdeliens - Same response as #69 ... I'll see if we can get Circle adjusted (remove PHP 5) and running on this branch. Thanks for your patience!

@chdeliens - Can you rebase symfony-4-dev against this and push? That should re-run CI and pass.

@chdeliens - Ping!

Ran snyk test locally and it passed (CI failing because env vars cannot be passed to a public PR).


[Feature request] Option to automatically scroll to first selected element

Hi,
would it be possible to create an option that when set to true, would scroll to first selected element in the dropdown when the dropdown is displayed? Thanks!

Yes that feature would be great. In the meantime, you can use this logic to scroll to element when dropdown opens.
	<multiselect @open="onOpenMultiselect" />

	...

    onOpenMultiselect() {
      // Wait for comp to render
     this.$nextTick(() => {
        const scrollableEl = this.$refs.vms.$el.querySelector(
          ".multiselect-dropdown"
        );

        const childEl = this.$refs.vms.$el.querySelector(
          ".multiselect-option.is-selected"
        );
        if (scrollableEl && childEl) {
          const options = {
            top: childEl.offsetTop,
            left: 0,
            behavior: "smooth",
          };
          scrollableEl.scrollTo(options);
        }
      });
    },

Thanks!

This is added in 2.4.0 - thanks for the workaround @tskaiste .


release: add npmrc to ensure publish permissions

This is required to ensure that NPM_AUTH_TOKEN attaches during the publish command.

CI seems to be failing, is this related? https://github.com/bytecodealliance/wizer/actions/runs/10407265313/job/28822153280?pr=107


logOut does not redirect even when supplying logOutUrl

Hello,
I am supplying both the logoutUrl and postLogoutRedirectUrl.  However, the oauthService.logout() method does not redirect.
    redirectUri: 'http://localhost:4200',
    logoutUri: 'https://login.live.com/oidc_logout.srf',

    this.oauthService.logoutUrl = 'http://localhost:4200';
    this.oauthService.postLogoutRedirectUri = 'https://login.live.com/oidc_logout.srf';

    this.oauthService.logOut(true);  //tried true and false

trying to redirect to:
https://login.live.com/oidc_logout.srf?post_logout_redirect_uri=http://localhost:4200
Any ideas here?

@dosama   No, we have not heard anything.   Let us know if you figure it out.   @ezracatz

@dosama did you get it working?

I was having issues with this too using implicit flow. At the very minimum I found I needed the following in ngOnInit in app.component.ts:
this.oauthService.configure(environment.authConfig);
this.oauthService.tokenValidationHandler = new JwksValidationHandler();
this.oauthService.loadDiscoveryDocumentAndTryLogin();

It more-or-less doesn't work if you initialise the OAuthService anywhere but in AppComponent since after the login redirect, all of the configuration on the service is lost. The important part is that if loadDiscoveryDocument is not called again after being redirected for login, the logoutURL is not set and the logOut() function returns without redirecting anywhere. The TryLogin part is important too since it actually puts the token in the URL hash fragment into browser storage.

If you load the discovery document the lib uses the logoutUrl mentioned there (field end_session_endpoint).
Can you provide a minimal stackblitz.com sample that demonstrates your issue?

Ah, ok, I see. The library expects that the discovery document contains an end_session_endpoint field if there is such an endpoint.
The next version will solve this.


Profiling

This PR aims at implementing profiling in the JIT engine.
This only works on linux.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

27 of 44 (61.36%)  changed or added relevant lines in 1 file are covered.
33 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 82.203%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mlir_graphblas/engine.py
27
44
61.36%

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/engine.py
33
83.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
1963

Relevant Lines:
2388

💛  - Coveralls

Here's an example use.
test.py:
import sys
import pytest
import numpy as np

from mlir_graphblas import MlirJitEngine

STANDARD_PASSES = [
    "--sparsification",
    "--sparse-tensor-conversion",
    "--linalg-bufferize",
    "--func-bufferize",
    "--tensor-bufferize",
    "--tensor-constant-bufferize",
    "--finalizing-bufferize",
    "--convert-linalg-to-loops",
    "--convert-scf-to-std",
    "--convert-std-to-llvm",
]

engine = MlirJitEngine()

mlir_text = """
func @single_value_slow_mul(%input_val: i64) -> i64 {
  %ci0 = constant 0 : i64
  %c0 = constant 0 : index
  %c1 = constant 1 : index
  %num_iterations = constant<PHONE_NUMBER>1 : index
  %answer = scf.for %i = %c0 to %num_iterations step %c1 iter_args(%current_sum=%ci0) -> (i64) {
    %new_sum = addi %current_sum, %input_val : i64
    scf.yield %new_sum : i64
  }
  return %answer : i64
}
"""

engine.add(mlir_text, STANDARD_PASSES, profile=True)

compiled_func = getattr(engine, "single_value_slow_mul")
input_val = 10
result = compiled_func(input_val)
print(f"result {repr(result)}")

Run:
(mlirgraphblas) pnguyen@demouser-DGX-Station:/home/pnguyen/code/mlir-graphblas$ python3 test.py
Profile Results:
    [kernel.kallsyms] with build id cf1794eeb3b0240b85534152fe5d736c4af8e741 not found, continuing without symbols
    Warning:
    Kernel address maps (/proc/{kallsyms,modules}) were restricted.

    Check /proc/sys/kernel/kptr_restrict before running 'perf record'.

    As no suitable kallsyms nor vmlinux was found, kernel samples
    can't be resolved.

    Samples in kernel modules can't be resolved as well.

    # To display the perf.data header info, please use --header/--header-only options.
    #
    #
    # Total Lost Samples: 0
    #
    # Samples: 18K of event 'cycles:ppp'
    # Event count (approx.):<PHONE_NUMBER>6
    #
    # Overhead  Command  Shared Object                                   Symbol
    # ........  .......  ..............................................  .........................
    #
        99.79%  python3  shared-d76a7cd2-d4c5-4388-bc9a-a33cc84491b9.so  [.] single_value_slow_mul
         0.02%  python3  [kernel]                                        [k] 0xffffffff85a03a52
         0.01%  python3  [kernel]                                        [k] 0xffffffff864009e7
         0.01%  python3  [kernel]                                        [k] 0xffffffff85a6e428
         0.01%  python3  [kernel]                                        [k] 0xffffffff85ab3d35
         0.01%  python3  [kernel]                                        [k] 0xffffffff85a6e1fa
         0.01%  python3  [kernel]                                        [k] 0xffffffff85b0ec71
         0.01%  python3  [kernel]                                        [k] 0xffffffff85ac595e
         0.01%  python3  [kernel]                                        [k] 0xffffffff85bc7563
         0.01%  python3  [kernel]                                        [k] 0xffffffff863c44a2
         0.01%  python3  [kernel]                                        [k] 0xffffffff85a5c7a5
         0.01%  python3  [kernel]                                        [k] 0xffffffff85a6e208
         0.01%  python3  [kernel]                                        [k] 0xffffffff86400df1
         0.01%  python3  [kernel]                                        [k] 0xffffffff85b12e53
         0.01%  python3  [kernel]                                        [k] 0xffffffff85a04770
         0.01%  python3  [kernel]                                        [k] 0xffffffff863c46d6
         0.01%  python3  [kernel]                                        [k] 0xffffffff863ac504
         0.01%  python3  [kernel]                                        [k] 0xffffffff864009ae
         0.01%  python3  [kernel]                                        [k] 0xffffffff863c448a
         0.01%  python3  [kernel]                                        [k] 0xffffffff86400957
         0.01%  python3  [kernel]                                        [k] 0xffffffff85b14a9e
         0.01%  python3  [kernel]                                        [k] 0xffffffff85ac2f63
         0.01%  python3  [kernel]                                        [k] 0xffffffff86400de2
         0.01%  python3  [kernel]                                        [k] 0xffffffff85ac9371
         0.01%  python3  [kernel]                                        [k] 0xffffffff86400963
         0.01%  python3  [kernel]                                        [k] 0xffffffff85b0f06e
         0.01%  python3  [kernel]                                        [k] 0xffffffff85c1a9b0
         0.01%  python3  [kernel]                                        [k] 0xffffffff864009ab
         0.01%  python3  [kernel]                                        [k] 0xffffffff85c171a6
         0.01%  python3  [kernel]                                        [k] 0xffffffff85c1728b
         0.01%  python3  [kernel]                                        [k] 0xffffffff85c295d7
         0.01%  python3  [kernel]                                        [k] 0xffffffff85bdf16b
         0.01%  python3  [kernel]                                        [k] 0xffffffff85b03f99
         0.01%  python3  [kernel]                                        [k] 0xffffffff85c321ff
         0.00%  python3  [kernel]                                        [k] 0xffffffff85bbea44
         0.00%  python3  [kernel]                                        [k] 0xffffffff85a37965
         0.00%  python3  [kernel]                                        [k] 0xffffffff85a63c16
         0.00%  python3  [kernel]                                        [k] 0xffffffff85a0d1a1
         0.00%  python3  [kernel]                                        [k] 0xffffffff85a0e254
         0.00%  python3  [kernel]                                        [k] 0xffffffff85bc61da

    #
    # (Cannot load tips.txt file, please install perf!)
    #
result<PHONE_NUMBER>10x
(mlirgraphblas) pnguyen@demouser-DGX-Station:/home/pnguyen/code/mlir-graphblas$

Here's what's causing the perf issues on the GitHub Actions machine.
Below is (more or less) the Python code in the JIT engine that uses perf to record the events happening in some process with the id {execution_process_id}:
record_process = subprocess.Popen(
    "/bin/bash",
    stdin=subprocess.PIPE,
    stdout=subprocess.PIPE,
    stderr=subprocess.PIPE,
)
record_process.stdin.write(
    f"""
    perf record -p {execution_process_id}
    exit
""".encode()
)
record_process.stdin.flush()

If I check the stderr from this subprocess on the GitHub Actions machine, I get the following message:
Error:
Access to performance monitoring and observability operations is limited.
Consider adjusting /proc/sys/kernel/perf_event_paranoid setting to open
access to performance monitoring and observability operations for users
without CAP_PERFMON or CAP_SYS_ADMIN Linux capability.
perf_event_paranoid setting is 4:
  -1: Allow use of (almost) all events by all users
      Ignore mlock limit after perf_event_mlock_kb without CAP_IPC_LOCK
>= 0: Disallow raw and ftrace function tracepoint access
>= 1: Disallow CPU event access
>= 2: Disallow kernel profiling
To make the adjusted perf_event_paranoid setting permanent preserve it
in /etc/sysctl.conf (e.g. kernel.perf_event_paranoid = <setting>)

On the DGX machine, I have perf_event_paranoid set to -1:
(mlirgraphblas) pnguyen@demouser-DGX-Station:/home/pnguyen/code/mlir-graphblas$ cat /proc/sys/kernel/perf_event_paranoid
-1
(mlirgraphblas) pnguyen@demouser-DGX-Station:/home/pnguyen/code/mlir-graphblas$

On the GitHub actions machine (which I can access by manually running the "debug" workflow added in this commit), perf_event_paranoid is set to 4:
runner@fv-az121-12:~/work/mlir-graphblas/mlir-graphblas$ cat /proc/sys/kernel/perf_event_paranoid
4

I can't change it to anything else because I don't have permission to do so.
runner@fv-az121-12:~/work/mlir-graphblas/mlir-graphblas$ echo -1 > /proc/sys/kernel/perf_event_paranoid
bash: /proc/sys/kernel/perf_event_paranoid: Permission denied

I don't know of any way to workaround this situation.
Thus, I make it so that the profiling tests are skipped when /proc/sys/kernel/perf_event_paranoid is not -1 in https://github.com/metagraph-dev/mlir-graphblas/pull/98/commits/c7c77f657307d2d65e2a89af2ab783724fcaa7da.

In https://github.com/metagraph-dev/mlir-graphblas/pull/98/commits/f5f84bac7dfc3d687e0e89db70fc6246749937d1, I made it so that we have this result for test.py:
(mlirgraphblas) pnguyen@demouser-DGX-Station:/home/pnguyen/code/mlir-graphblas$ python3 test.py
Profile Results:
    [kernel.kallsyms] with build id cf1794eeb3b0240b85534152fe5d736c4af8e741 not found, continuing without symbols

    Sorted summary for file /tmp/tmpjmxms3rs/shared-4dd621ae-132e-4182-8a17-e4285af3c38d.so
    ----------------------------------------------

       99.97 <stdin>:10
     Percent |	Source code & Disassembly of shared-4dd621ae-132e-4182-8a17-e4285af3c38d.so for cycles:ppp (18667 samples)
    --------------------------------------------------------------------------------------------------------------------------
             :
             :
             :
             :	Disassembly of section .text:
             :
             :<PHONE_NUMBER>000590 <single_value_slow_mul>:
             :	single_value_slow_mul():
        0.00 :	  590:   xor    %ecx,%ecx
        0.00 :	  592:   movabs $0x2dfdc1c34,%rdx
        0.00 :	  59c:   xor    %eax,%eax
        0.00 :	  59e:   cmp    %rdx,%rcx
        0.00 :	  5a1:   jg     5bb <single_value_slow_mul+0x2b>
        0.00 :	  5a3:   nop
        0.00 :	  5a4:   nop
        0.00 :	  5a5:   nop
        0.00 :	  5a6:   nop
        0.00 :	  5a7:   nop
        0.00 :	  5a8:   nop
        0.00 :	  5a9:   nop
        0.00 :	  5aa:   nop
        0.00 :	  5ab:   nop
        0.00 :	  5ac:   nop
        0.00 :	  5ad:   nop
        0.00 :	  5ae:   nop
        0.00 :	  5af:   nop
        0.02 :	  5b0:   add    %rdi,%rax
        0.01 :	  5b3:   inc    %rcx
        0.00 :	  5b6:   cmp    %rdx,%rcx
     <stdin>:10   99.97 :	  5b9:   jle    5b0 <single_value_slow_mul+0x20>
        0.00 :	  5bb:   retq
(mlirgraphblas) pnguyen@demouser-DGX-Station:/home/pnguyen/code/mlir-graphblas$

This looks almost ready to merge for now.  I've made one suggestion to allow the output file for profiling to be set by the user, so that the file can be used later.  Additionally, I am curious if the debug Github Action is something generically useful we want to check in, or was that just for temporary debugging of this PR?

Oops, accidentally closed PR

@seibert, I implemented the changes you suggested.
For the "Debug CI Jobs" GitHub Actions workflow, I would be okay with removing or keeping it. I do not have strong feelings about it. The reasons I left it in are:

Leaving it in will not cause any extra work to be done on the GitHub Actions machines since the workflow has to be initiated manually.
I can imagine cases in the future where it might be easier to directly work on the GitHub Actions machine to address or reproduce an issue. However, since this PR is the only example where this has shown to be useful, it's debatable whether this is sufficiently motivating.


Clarify difference between App Platform and App Catalogs in web UI docs

Towards https://github.com/giantswarm/giantswarm/issues/16903
Follow up to https://github.com/giantswarm/docs/pull/917
@Oshratn asked if we can make clearer the difference between App Platform and App Catalogs. I also added a note on how Helm relates to App Platform.
We should also update this page after the navigation changes. The list of catalogs is no longer shown. @oponder Could you take a look at that?
Please remember to

[x] Give the PR a meaningful title -- it will be shown in the release notes
[x] Add (or remove) user questions associated with any updated docs

But it seems that @rossf7 is looking into a more in-depth rewrite.

The main problem is this screenshot is outdated. We should update it to use the new search-based navigation.

Going with this for now.


Dark Mode

Instead of just adding a darkmode, I would add a theme system that allows you to choose from a variety of themes. This would give the user a wider choice and at the same time allow the program to match e.g. the colors of a university/school.


Not Found Error

When I try to run the PlanRAG, it shows that the model has been loaded. So what is it going to found exactly, and why it need to find it?
I'm too confused about this, could you please help me with it? Thanks a lot for your help.

Hello,
Could you please provide exact source code of run.sh ?
It seems that the problem is about vllm, but I am not sure without the code.


WAC104 fails to connect

I think this may have to do with the UPnP of the WAC104 not being compatible.
I have no problem with the R7800 Router.  Not a big thing but would be nice to add
the WAC104
Logger: pynetgear.router
Source: components/netgear/router.py:53
First occurred: 1:14:30 PM (6 occurrences)
Last logged: 1:45:01 PM
login using all known port-ssl combinations failed.

Thanks. Little hard for me to add support because I don't have the hardware to reverse how the APIs work.

same issue with wac104 not being picked up on this integration, would be great if this worked for the wac 104's

Do you have the firmware version of your WAC104?

V<IP_ADDRESS>
Robert Boccia

From: Ronnie @.>
Sent: Saturday, September 16, 2023 7:12:27 PM
To: rroller/netgear @.>
Cc: Robert Boccia @.>; Comment @.>
Subject: Re: [rroller/netgear] WAC104 fails to connect (Issue #16)
Do you have the firmware version of your WAC104?
—
Reply to this email directly, view it on GitHubhttps://github.com/rroller/netgear/issues/16#issuecomment-1722273509, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR4IWBE5XR2KWYVAOP43PP3X2XMXXANCNFSM6AAAAAAVJ6JSCM.
You are receiving this because you commented.Message ID: @.***>

Can you try pulling in the latest 0.1.5 release to see if it works? I just released a fix for newer device firmware

Related to https://github.com/rroller/netgear/issues/14
Please follow that as I'll close this issue as a duplicate


Unexpected tokenization

I'm surprised by the following input / result:

amount($) becomes {"amount($", ")}
Size (Men's):9.5 becomes {"Size", "(", "Men"}

Instead I would expect:

amount($) becomes {"amount", "(", "$", ")"}
Size (Men's):9.5 becomes {"Size", "(", "Men", ")", ":", "9.5"} or {"Size", "(", "Men", "'s", ")", ":", "9.5"}

Here's the sample I'm running:
doc, err := prose.NewDocument(data, prose.WithExtraction(false), prose.WithTagging(false), prose.WithSegmentation(false))
if err != nil {
		return nil
}

tokens := make([]string, 0)
for _, t := range doc.Tokens() {
	tokens = append(tokens, t.Text)
}

return tokens

#71


Exampler replayer as animation tool doesn't work on Nightly

Tested http://swimminglessonsformodernlife.com/aframe-motion-capture-components/examples/animationTool.html on Nightly and even though the path is being drawn after pressing the trigger button upon release the ghosts do not move.
PS: "A Saturday Night" works on the same configuration.

@dmarcos this is what I'm seeing, btw, that I messaged you about.


Use message stream factory for message input stream creation

It appears that the MessageStreamFactory was not being used when creating the MessageInputStream. This is necessary to provide a custom MessageInputStream (or more importantly to me, the ability to catch exceptions made during MessageInputStream's creation.)

What msl-core version is this in?


MAINTAINERS: Remove DT bindings area

Now that the dts/bindings filter has been removed from Devicetree Binding area in #75016, this area serves no real purpose.
Move the include/dt-bindings files to their respective areas.
Fix some of the orphaned dts/bindings paths caused by #75016
Fix the imx_spc.h file being in it's own pm/ folder instead of power/ like the other power related headers.
Add any binding with "zephyr" in the name to the devicetree area.

hey, this needs a rebase


Triart: Optimize iterations 2 takes exponentially as long as optimize iterations 1

I'm using a dark, 1920x1080 concert photo with some pretty lights. On the default sample level, Optimize iterations 1 took 10 seconds, but optimize iterations 2 takes multiple hours, using around 40-50% CPU.

This is something I definitely need to make clearer in the UI.
The bottom setting on the slider is zero iterations, meaning there is no work done by the optimiser. Above that, then yes, the computation time will increase massively.
The optimisation is optional and not something every image will need to have applied to it, but it can improve image quality massively.
The time is takes does sound excessively high, especially if that is just one iteration. How many samples/_re_samples are you doing?
Sorry for the confusion.
PS: I probably should make a triart repo.


xrbuddy: fix swapchain format selection

Increment was performed twice, so we could miss the desired format!

Good find, thanks for the fix 👍


add a setting to sort favorites to the top

ReadMe.html will need to be updated with a new screenshot and description of this setting.

Thanks for the PR. I haven't missed that kind of setting yet, but I suppose it may come in handy when you have many favourites.
One thing: the other settings are "live", i.e. if you change a checkmark, the main window's list will reflect the new setting immediately. I think that new settings should sort the list accordingly as well. Can you add that?
Oh, and another thing: You could add an updated en.catkeys.
Thanks!

Sure, I'll take a look at these.

Cool. Don't forget to add yourself to the copyright headers of the files you touched.

Thanks!
I'll upload the updated catkeys to Polyglot and put out a new release when the translations had a  bit of time to dribble in.


Revert changes to package.json and package-lock.json

For semantic release revert changes to package.json and package-lock.json, then commit all

:tada: This PR is included in version 3.26.73 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Bofrost.be has degraded performance

In 1c5c763, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 990 ms

Resolved: Bofrost.be performance has improved in e914346.


Upgrade _HIP_ code path

Because #145, the _HIP_ code path has fallen behind the CUDA and CPU variants.  Once we have a fix or workaround for #145, bring _HIP_ up to date.

Done in #192.


How to use with Windows OneNote

I'm trying to use this script with the OneNote which is installed through the MicrosoftStore, which doesn't have the onenote.exe command. In order to run OneNote from the command line I have to run:
explorer.exe shell:appsFolder\Microsoft.Office.OneNote_8wekyb3d8bbwe!microsoft.onenoteim

How would I go about configuring this script to activate in that app? I realize this isn't really related to the script but any help will be greatly appreciated.

I added OneNote by adding ahk_exe ApplicationFrameHost.exe to the VimMenu > Settings > Application list found by right clicking the executable's taskbar icon. I used Window Spy to find the name of the executable as recommended by a comment in settings.ahk.

Yup, that's pretty much the right thing to do.
I'd like to note that this version is very much a beta/development version, and is riddled with errors. For day-to-day use I'd suggest using the upstream version, rcmdnk/vim_ahk
For onenote-specific functionality, consider disabling onenote and using idvorkin/Vim-Keybindings-For-Onenote. You may need to do a similar trick to get the window recognised.


Week 27 Alexa and Ananya- Mini Lessons Plans and Progress

To-Dos:

[ ] Research (topics listed below)
[x] Make project plan/wire-frame
[ ] design home page

Research (put findings here):

[ ] Binary Search (collegeboard topic)
[ ] Images (grey scale using binary)
[ ] extra resources (TED talks, websites, etc)

Everything I completed for last week.

[x] Time and Space lesson
[x] Binary Search Lesson
[x] Student Resource page for students


Assertions for two-dimensional arrays of byte

Check List:

Fixes #1182
Unit tests : YES
Javadoc with a code example (on API only) : YES

Merged thanks @mwajcht!


Clean problematic files on alibaba workspaces

This is a temporary fix to clean workspaces on alibaba machines before builds. Currently both alibaba machines are facing this issue
18:10:26  ERROR: Failed to clean the workspace
18:10:26  jenkins.util.io.CompositeIOException: Unable to delete 'C:\Jenkins\temp'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
18:10:26  	at jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:90)
18:10:26  	at hudson.Util.deleteContentsRecursive(Util.java:262)
18:10:26  	at hudson.Util.deleteContentsRecursive(Util.java:251)
18:10:26  	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:743)

This issue has affected other windows boxes, hence the pr https://github.com/AdoptOpenJDK/openjdk-build/pull/1956, so I am putting a similar fix in for alibaba machines.
Most recent failure on build-alibaba-win2012r2-x64-1 https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-dragonwell/58/console

Probably related
https://github.com/eclipse/openj9/issues/10834
I think some new investigation by @jdekonin pointed at long path lengths being the root cause.

Probably related
https://github.com/eclipse/openj9/issues/10834
I think some new investigation by @jdekonin pointed at long path lengths being the root cause.

@Haroon-Khel Can you not just set the workspace variables to C:/workspace/ for the machines? I think that would be covered by: https://github.com/AdoptOpenJDK/openjdk-build/blob/102237341c7f0737f0dd4dc57fcc7e9e3ffe3bd5/pipelines/build/common/openjdk_build_pipeline.groovy#L915
And removes the need for another line

@Haroon-Khel Can you not just set the workspace variables to C:/workspace/ for the machines? I think that would be covered by: https://github.com/AdoptOpenJDK/openjdk-build/blob/102237341c7f0737f0dd4dc57fcc7e9e3ffe3bd5/pipelines/build/common/openjdk_build_pipeline.groovy#L915
And removes the need for another line

Good spot @Willsparker. Ill change the workspace to that and run some jobs. Should it be sufficient, ill close this pr

Good spot @Willsparker. Ill change the workspace to that and run some jobs. Should it be sufficient, ill close this pr

Latest run https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-dragonwell/81/console
14:20:19  The recommended git tool is: git
14:20:19  No credentials specified
14:20:19  Cloning the remote Git repository
14:20:19  Cloning repository https://github.com/AdoptOpenJDK/openjdk-build.git
14:20:20  ERROR: Failed to clean the workspace
14:20:20  jenkins.util.io.CompositeIOException: Unable to delete 'C:\workspace'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
14:20:20  	at jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:90)

This is while the workspace was C:/workspace/ to test. I also get this error when the workspace is C:\workspace\. I tried both because the rm command in the build scripts uses forward slashes despite it trying to remove a windows directory

Latest run https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-dragonwell/81/console
14:20:19  The recommended git tool is: git
14:20:19  No credentials specified
14:20:19  Cloning the remote Git repository
14:20:19  Cloning repository https://github.com/AdoptOpenJDK/openjdk-build.git
14:20:20  ERROR: Failed to clean the workspace
14:20:20  jenkins.util.io.CompositeIOException: Unable to delete 'C:\workspace'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
14:20:20  	at jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:90)

This is while the workspace was C:/workspace/ to test. I also get this error when the workspace is C:\workspace\. I tried both because the rm command in the build scripts uses forward slashes despite it trying to remove a windows directory

Ok, I realise that the workspace needs to be C:\workspace\openjdk-build. Having made that change, I get the familiar gradle error
14:26:52  Exception in thread "main" java.io.FileNotFoundException: \cygdrive\c\workspace\openjdk-build\workspace\.gradle\wrapper\dists\gradle-6.5-bin\6nifqtx7604sqp1q6g8wikw7p\gradle-6.5-bin.zip.lck (Access is denied)
14:26:52  	at java.base/java.io.RandomAccessFile.open0(Native Method)
14:26:52  	at java.base/java.io.RandomAccessFile.open(RandomAccessFile.java:345)

Latest run https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-dragonwell/83/console

Ok, I realise that the workspace needs to be C:\workspace\openjdk-build. Having made that change, I get the familiar gradle error
14:26:52  Exception in thread "main" java.io.FileNotFoundException: \cygdrive\c\workspace\openjdk-build\workspace\.gradle\wrapper\dists\gradle-6.5-bin\6nifqtx7604sqp1q6g8wikw7p\gradle-6.5-bin.zip.lck (Access is denied)
14:26:52  	at java.base/java.io.RandomAccessFile.open0(Native Method)
14:26:52  	at java.base/java.io.RandomAccessFile.open(RandomAccessFile.java:345)

Latest run https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-dragonwell/83/console

@M-Davies How can I test this pr? The build jobs do not give a parameter, for example, from which repo to use build scripts

@M-Davies How can I test this pr? The build jobs do not give a parameter, for example, from which repo to use build scripts

run tests
See https://github.com/AdoptOpenJDK/openjdk-build/blob/master/pipelines/build/prTester/README.md for all of our potential tests that run :)

run tests
See https://github.com/AdoptOpenJDK/openjdk-build/blob/master/pipelines/build/prTester/README.md for all of our potential tests that run :)

 PR TESTER RESULT 
❎ Some pipelines failed or the job was aborted! ❎
See the pipeline-build-check below for more information...

Failing job was an unrelated aarch64 problem. Windows ran ok

 PR TESTER RESULT 
❎ Some pipelines failed or the job was aborted! ❎
See the pipeline-build-check below for more information...

Failing job was an unrelated aarch64 problem. Windows ran ok

There is a worrying amount of hardcoded deletions here. I wonder if there's a much more efficient cleanup mechanism at the end of builds?

@M-Davies Completely agree - feel free to pick up https://github.com/AdoptOpenJDK/openjdk-build/issues/2205 ;-) I'd imagine there's a suitable variable we could use instead ...

There is a worrying amount of hardcoded deletions here. I wonder if there's a much more efficient cleanup mechanism at the end of builds?

@M-Davies Completely agree - feel free to pick up https://github.com/AdoptOpenJDK/openjdk-build/issues/2205 ;-) I'd imagine there's a suitable variable we could use instead ...

@Haroon-Khel Does this still need to be in draft in light of all the testing above?

@Haroon-Khel Does this still need to be in draft in light of all the testing above?


Start developer documentation

Most of us working on Chef Server are not the original designers. It
helps to write things down. I've started with some facts about how
search works since it has come up in many discussions over the last few
weeks.
Signed-off-by: Steven Danna<EMAIL_ADDRESS>

Thanks for the review! Updated.


Review Observer Capabilities

How much should an observer be able to view / do?
Definitely need to remove observers from the quiz and lab grading lists!

Observers should be able to view quizzes and labs, but not take them
Observers should not be in the list for grading quizzes and labs
When taking attendance the absent list should show the role (like observer, student, assistant, instructor)

This is done in the latest commit.
For attendance observers have been completely removed from the list


Build components into style guide based on template builder

Expanding on Andre work on the style guide, start building and applying the initial styling from the wireframe to the main components that have been agreed

Text Input
Text Area
Radio buttons
Select box
Checkbox
Primary Button
Secondary Button
Back button
"Add Section" skelton
Cards
Sectional Cards
Tabs

@jupiter007 I will update this card on Monday. I was off sick at the beginning of the week, so catching up a bit.
Just aiming to get the following ticked off, most have already been as its been styling the react-aria styling but just want to clean my code up a little

Text Input
Text Area
Radio buttons
Select box
Checkbox
Primary Button
Secondary Button
Back button
"Add Section" skeleton

I also have Question/Sectional "card" style in progress but I will split this into a new card as you suggested.
Other

Cards
Tabs

I suspect we might need to split these off a little, as I think tabs might come with some chat required and yeah I know youve already put cards elsewhere and we know cards might become "list" based on wireframe feedback so we dont want to take this too far.

Thanks for the update @fraserclark. Good point about cards becoming Lists.

@andrewebdev @jupiter007 @briri
Video on update
https://www.loom.com/share/ee503e9419af41f097ed41db97c71cf8
Syntax Highlighting in style guide
What is your opinion of us getting some syntax highlighting library installed to make the style guide a bit easier to work with so we can copy and paste or do you guys see moving this style guide into Storybook or something like that?
Select
React-aria has a custom select box component. When I tried it on mobile it 'breaks' the standard built in "select" functionality on iOS and Android - which isn't great
https://react-spectrum.adobe.com/react-aria/Select.html
They also mention issues with accessibility testing, although they claim it is accessible
https://react-spectrum.adobe.com/react-aria/Select.html#accessibility
How should we proceed - should we do style the react-aria one and also create an alternative more traditional html select? I don't like the modification of native elements generally.
I would say in the wireframes at the moment, we have, where possible, tried to avoid using  whenever possible to be aligned with UK Government, USWDS and many similar user testing's recommendations that a  should only be used as a last resort

@fraserclark , based on React Aria's documentaiton, their custom select does support the ARIA listbox pattern and keyboard navigation, so I'm thinking it will be ok to use it even as long as it is functioning as expected on different devices.
I can do a quick test using my Mac's VoiceOver. Also, we could seek the assistance of the accessibility team here to confirm that this component is compliant.
In regards to Syntax highlighting, I like the idea of using Storybook for documenting our components.

Pull request here
https://github.com/CDLUC3/dmsp_frontend_prototype/pull/120

@jupiter007 I will update this card on Monday. I was off sick at the beginning of the week, so catching up a bit.
Just aiming to get the following ticked off, most have already been as its been styling the react-aria styling but just want to clean my code up a little

Text Input
Text Area
Radio buttons
Select box
Checkbox
Primary Button
Secondary Button
Back button
"Add Section" skeleton

I also have Question/Sectional "card" style in progress but I will split this into a new card as you suggested.
Other

Cards
Tabs

I suspect we might need to split these off a little, as I think tabs might come with some chat required and yeah I know youve already put cards elsewhere and we know cards might become "list" based on wireframe feedback so we dont want to take this too far.

@fraserclark sorry to hear you were sick. Hope you are feeling better now.
Don't worry about the Cards and Tabs. There's a separate ticket for Cards here, and you can add the Tabs work there. This PR is already huge anyways, so lets keep them separate.