9.11 RC5 upgrade: SQL error occur when using DB table prefix

Description of bug
Upgraded from 9.10 to 9.11 RC5.
DB error occured when installer executed DB upgrade scripts: "CREATE VIEW [dbo].[vw_PortalPermissions]"
I'm quite sure this has to do with a missing table prefix in the upgrade script. The site is using a table prefix "dnn_". The script tries to SELECT from table "PortalPermission", however that table is called "dnn_PortalPermission" in this case.
Error information
Installer wrote:
"Executing Script: 09.11.00.SqlDataProvider Error! (see 09.11.00.log.resources for more information)"
Content of the log file:
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'dbo.PortalPermission'.    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at DotNetNuke.Data.SqlDatabaseConnectionProvider.ExecuteNonQuery(String connectionString, CommandType commandType, Int32 commandTimeout, String query)
at DotNetNuke.Data.SqlDataProvider.ExecuteScriptInternal(String connectionString, String script, Int32 timeoutSec)
ClientConnectionId:65b7f729-ca8a-4501-96b8-46d9e9726445
Error Number:208,State:1,Class:16
CREATE VIEW [dbo].[vw_PortalPermissions]
AS
SELECT  PP.PortalPermissionID,
PP.PortalId,
P.PermissionID,
PP.RoleID,
R.RoleName,
PP.AllowAccess,
PP.UserID,
U.Username,
U.DisplayName,
P.PermissionCode,
P.ModuleDefID,
P.PermissionKey,
P.PermissionName,
PP.CreatedByUserID,
PP.CreatedOnDate,
PP.LastModifiedByUserID,
PP.LastModifiedOnDate
FROM        dbo.[PortalPermission]    AS PP
INNER JOIN dbo.[Permission]       AS P  ON PP.PermissionID = P.PermissionID
LEFT  JOIN dbo.[Roles]            AS R  ON PP.RoleID       = R.RoleID
LEFT  JOIN dbo.[Users]            AS U  ON PP.UserID       = U.UserID
`
Affected version

[ ] 10.00.00 alpha build
[x] 09.11.00 release candidate
[ ] 09.10.02 release candidate
[ ] 09.10.01 latest supported release

Update: Problem can be solved by manually executing the script with table prefix added. When the view is succesfully created, the site becomes available and seem to work fine.

Great catch. Thanks for that test.

Fixed

Great! Thanks


[REVIEW] Update queries, benchmarking automation, instrumentation, and tools library

This PR:

[x] Updates the automation and instrumentation associated with the TPCxBB benchmark
[x] Updates the tools library as per recent RAPIDS library updates
[x] Updates the queries as per the recent RAPIDS library updates and newest SF10K runs
[x] Updates the pure dask conda environment
[x] Updates the BSQL conda environment

This PR does not:

Include configuration for setting up a cluster. An example cluster configuration will be included in a follow-up.
Update the BSQL queries. This will be done in a follow-up PR

@Christian8491 can you review the BSQL conda yml file and request any necessary changes?

@beckernick the changes for this yml file should be like this.
channels:
  - blazingsql/label/cuda10.2
  - rapidsai
  - nvidia
  - conda-forge
  - blazingsql
  - defaults
dependencies:
  - python=3.7
  - cudatoolkit=10.2
  - cudf=0.14
  - libcudf=0.14
  - librmm=0.14
  - rmm=0.14
  - dask-cuda=0.14
  - dask-cudf=0.14
  - cuml=0.14
  - ucx-py=0.14
  - blazingsql
  - scipy
  - scikit-learn
  - cupy=7
  - spacy
  - oauth2client
  - asyncssh
  - psutil
  - ipykernel
  - pip
  - pip:
    - jupyter-server-proxy
    - git+https://github.com/dask/dask.git
    - git+https://github.com/dask/distributed.git

Thanks. Do we need to make any updates for 0.15 beyond unpinning (for now)?

I think the utils.py might be too big now, it might make sense to factor out some code from there.

I agree. I had this thought while porting the changes but decided to keep it as is for now. May still be worth updating in this PR, but could also be a follow-up.

I think the utils.py might be too big now, it might make sense to factor out some code from there.

I agree. I had this thought while porting the changes but decided to keep it as is for now. May still be worth updating in this PR, but could also be a follow-up.

I think it makes sense to update it this pr.
We can probably break out the logic bits (like left semi join/date logic) from the other util stuff like uploading/verification etc. Its kind of confusing to have it all in one big file .
Sorry for asking you to do more work on this. :-(

oauth2client

I dont think this is right. I think we want what is already set in this PR, with blazingsql-nightly and rapidsai-nightly, which should then pull the latest and greatest which will be better than what we have in our stable 0.14 version

Ready for a second round of reviews

Thanks for the quick iteration. Merging.
README update to follow imminently.


New feature: Restrict status

Feature request
As a user I want to restrict the values that may occur for the 'status' field so that I can introduce standards for my Sphinx projects.
Implementation proposal
New configuration dictionary in conf.py:
needs_status_whitelist = {
  '<status_1>': "<status_1_description>",
  '<status_2>': "<status_2_description>"
}

New implementation proposal

conf.py
New boolean flag needs_defined_status_only
any .rst file
New directive 'needs_status' which defines a status and outputs nothing
Fields.. needs_status::
    :name: open
    :description: The need type req is in state open

any .rst file
New directive 'needs_legend_status' which dumps a legend for all status

Optional features (if you have the time)

More fields for needs_status directive:

      :predecessor: <status_name>
      :color: <rgb_color_code>

More fields for needs_legend_status directive:.. needs_legend_status::
    :type: table / diagram
    :add_description: True/False (Usecase for diagram

The diagram type will be painted with plantuml (type: node) and uses the predecessor information for status connections

Implemented initial proposal only.


Server Reports Top 10 DB Space Usage does not work on case sensitive instance

SQL Operations Studio Version: 0.31.4  (mac)
Server Reports version: 0.1.2

Steps to Reproduce:

Install Server Report extension on an instance using case sensitive collation, then open the tab.
The 'Top 10 DBA Space Usage' graph will be blank, instead of showing data.
Click ...'Run Query'
The query will fail with multiple errors:

Msg 2812, Level 16, State 62, Line 10 Could not find stored procedure 'sp_msforeachdb'. Msg 2812, Level 16, State 62, Line 25 Could not find stored procedure 'sp_msforeachdb'. Msg 2812, Level 16, State 62, Line 39 Could not find stored procedure 'sp_msforeachdb'.
Thoughts on fixing this:

The proper case of this built in procedure is: sp_MSforeachdb. A quick fix would be to fix the case of the statement.
This built in procedure is officially unsupported and has been found to be unreliable by many users, so a longer term fix would be to use a different mechanism to loop between the databases. (Example post talking about the problems by Aaron Bertrand is here.)

Hi @LitKnd, thanks for bringing this up and the nice gif.
It looks like @vickyharp opened this same issue: https://github.com/Microsoft/sqlopsstudio/issues/1799 She also suggested the same change.
I can check with engineering team to see if we can make an update. In the short-term, we can make this fix, but long term we can discuss a better approach.

Thanks! Just realized I was only searching for open issues, so I missed it.

I think this should already be fixed.  I'll push an extension update later today.

I published Server Reports 0.1.3 which should fix this.  Please reactive if this problem persists with the latest extension.  Thanks for reporting!

Yes, it's beautiful now! Thanks.


Add policy support to peer-pods

This series add policy support to peer-pods.
Only packer built podvm images will work for now. A follow on commit will enable addition of opa and related deps via mkosi build

Tested a scenario where the default policy only allows SetPolicy API
root@ip-192-168-87-191:/etc/kata-opa# ls -ltr
total 12
-rw-rw-r-- 1 ubuntu ubuntu 1361 Dec 14 17:21 allow-all.rego
-rw-rw-r-- 1 ubuntu ubuntu 1361 Dec 14 17:21 allow-all-except-exec-process.rego
-rw-rw-r-- 1 ubuntu ubuntu 1395 Dec 15 16:06 disallow-all-except-setpolicy.rego
lrwxrwxrwx 1 ubuntu ubuntu   34 Dec 15 16:07 default-policy.rego -> disallow-all-except-setpolicy.rego

And policy is made available via annotation
 io.katacontainers.config.agent.policy: cGFja2FnZSBhZ2VudF9wb2xpY3kKCmRlZmF1bHQgQWRkQVJQTmVpZ2hib3JzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgQWRkU3dhcFJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IENsb3NlU3RkaW5SZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBDb3B5RmlsZVJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IENyZWF0ZUNvbnRhaW5lclJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IENyZWF0ZVNhbmRib3hSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBEZXN0cm95U2FuZGJveFJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IEdldE1ldHJpY3NSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBHZXRPT01FdmVudFJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IEd1ZXN0RGV0YWlsc1JlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IExpc3RJbnRlcmZhY2VzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgTGlzdFJvdXRlc1JlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IE1lbUhvdHBsdWdCeVByb2JlUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgT25saW5lQ1BVTWVtUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUGF1c2VDb250YWluZXJSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBQdWxsSW1hZ2VSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBSZWFkU3RyZWFtUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUmVtb3ZlQ29udGFpbmVyUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUmVtb3ZlU3RhbGVWaXJ0aW9mc1NoYXJlTW91bnRzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUmVzZWVkUmFuZG9tRGV2UmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUmVzdW1lQ29udGFpbmVyUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgU2V0R3Vlc3REYXRlVGltZVJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFNldFBvbGljeVJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFNpZ25hbFByb2Nlc3NSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBTdGFydENvbnRhaW5lclJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFN0YXJ0VHJhY2luZ1JlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFN0YXRzQ29udGFpbmVyUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgU3RvcFRyYWNpbmdSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBUdHlXaW5SZXNpemVSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBVcGRhdGVDb250YWluZXJSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBVcGRhdGVFcGhlbWVyYWxNb3VudHNSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBVcGRhdGVJbnRlcmZhY2VSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBVcGRhdGVSb3V0ZXNSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBXYWl0UHJvY2Vzc1JlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFdyaXRlU3RyZWFtUmVxdWVzdCA6PSB0cnVlCgpkZWZhdWx0IEV4ZWNQcm9jZXNzUmVxdWVzdCA6PSBmYWxzZQo=

CAA logs
...
2023/12/15 16:15:44 [adaptor/proxy] SetPolicy: policy:package agent_policy

default AddARPNeighborsRequest := true
default AddSwapRequest := true
default CloseStdinRequest := true
default CopyFileRequest := true
default CreateContainerRequest := true
default CreateSandboxRequest := true
default DestroySandboxRequest := true
default GetMetricsRequest := true
default GetOOMEventRequest := true
default GuestDetailsRequest := true
default ListInterfacesRequest := true
default ListRoutesRequest := true
default MemHotplugByProbeRequest := true
default OnlineCPUMemRequest := true
default PauseContainerRequest := true
default PullImageRequest := true
default ReadStreamRequest := true
default RemoveContainerRequest := true
default RemoveStaleVirtiofsShareMountsRequest := true
default ReseedRandomDevRequest := true
default ResumeContainerRequest := true
default SetGuestDateTimeRequest := true
default SetPolicyRequest := true
default SignalProcessRequest := true
default StartContainerRequest := true
default StartTracingRequest := true
default StatsContainerRequest := true
default StopTracingRequest := true
default TtyWinResizeRequest := true
default UpdateContainerRequest := true
default UpdateEphemeralMountsRequest := true
default UpdateInterfaceRequest := true
default UpdateRoutesRequest := true
default WaitProcessRequest := true
default WriteStreamRequest := true

default ExecProcessRequest := false
2023/12/15 16:15:58 [adaptor/proxy] CreateSandbox: hostname:bp-test sandboxId:bbddbf5c1fe49f27b82461aef98f7af681ea8bf13bffcf03c5ce96768c1313b9
2023/12/15 16:15:58 [adaptor/proxy]     storages:
2023/12/15 16:15:58 [adaptor/proxy]         mountpoint:/run/kata-containers/sandbox/shm source:shm fstype:tmpfs driver:ephemeral
2023/12/15 16:15:58 [adaptor/proxy] CreateContainer: containerID:bbddbf5c1fe49f27b82461aef98f7af681ea8bf13bffcf03c5ce96768c1313b9
...

In order to test with mkosi image, apply the following patch
diff --git a/podvm-mkosi/Makefile b/podvm-mkosi/Makefile
index 20ab680..7ac8a71 100644
--- a/podvm-mkosi/Makefile
+++ b/podvm-mkosi/Makefile
@@ -13,6 +13,8 @@ fedora-binaries-builder:
        docker buildx build \
                -t fedora-binaries-builder \
                --load \
+               --build-arg CAA_SRC="https://github.com/bpradipt/cloud-api-adaptor" \
+               --build-arg CAA_SRC_REF="policy" \
                - < ../podvm/Dockerfile.podvm_builder.fedora

 PHONY: binaries

I had to add a commit to fix the missing agent-config.toml in /run/peerpod for packer built image. Discussions happening in slack - https://cloud-native.slack.com/archives/C04A2EJ70BX/p1702557858190549

@mkulke @katexochen @stevenhorsman ptal
For testing you'll need the latest CCv0 kata shim with policy support.
You can use a daemonset to replace the existing shim from the coco operator installed system as mentioned in the following commit - https://github.com/confidential-containers/cloud-api-adaptor/pull/1607#issuecomment-1856274841

@stevenhorsman I couldn't find s390x binary for opa from the release page, however the opa support code is written in a way that it should be easy to extend and include opa binary for s390x podvm images.

@stevenhorsman I couldn't find s390x binary for opa from the release page, however the opa support code is written in a way that it should be easy to extend and include opa binary for s390x podvm images.

Good point - in kata-containers (https://github.com/kata-containers/kata-containers/pull/7769/files) we built it from source, but I'm not sure if there is any plan to get upstream to create s390x & ppc64le releases, or if we'll need to self-build in peer pods too. @BbolroC - might know move about that?

@BbolroC - might know move about that?

I haven't raised any discussion internally yet. I will bring this topic soon and update you guys on the plan. Thanks!

@stevenhorsman I couldn't find s390x binary for opa from the release page, however the opa support code is written in a way that it should be easy to extend and include opa binary for s390x podvm images.

Good point - in kata-containers (https://github.com/kata-containers/kata-containers/pull/7769/files) we built it from source, but I'm not sure if there is any plan to get upstream to create s390x & ppc64le releases, or if we'll need to self-build in peer pods too. @BbolroC - might know ~move~ more about that?

I can also add support to build the opa binary from source.
@stevenhorsman @BbolroC would that be fine ?

@stevenhorsman @BbolroC I have switched to building OPA from source. Ptal.

Good point - in kata-containers (https://github.com/kata-containers/kata-containers/pull/7769/files) we built it from source, but I'm not sure if there is any plan to get upstream to create s390x & ppc64le releases, or if we'll need to self-build in peer pods too. @BbolroC - might know ~move~ more about that?

see https://github.com/open-policy-agent/opa/issues/5838

I've had a quick flick through the source code and it looks okay. Once #1627 is merged and this is rebased on it I'll give it a proper review and build the image and test it out. Just one question I have for now - with the different options for specifying whether the policy is enabled and which one is default, where you planning to add anything to the README about it?

Hi @bpradipt - I think you'll need to rebase this to pick up the rebase fix I made a couple of days ago and get the e2e tests working.
BTW - I'm still working on testing it - I have the podvm building now, but hitting some issues creating pods that I'm debugging (It's been a while since I manually tested ibm cloud peer pods as I've mostly been playing with libvirt recently). As expected specifying DEFAULT_AGENT_POLICY_FILE in DEFAULT_AGENT_POLICY_FILE=allow-all-except-exec-process.rego make podvm-builder podvm-binaries podvm-image doesn't seem to work which we might want to look into, but not a big deal

Hey Pradipta, I'm getting nydus errors when trying to deploy this, which might be an error on my side, but another thing that I've realised is that we (in https://github.com/confidential-containers/cloud-api-adaptor/blob/02662febe863e342c02a12a43b8c793a0e687b82/Makefile#L168 and https://github.com/confidential-containers/cloud-api-adaptor/blob/02662febe863e342c02a12a43b8c793a0e687b82/test/provisioner/provision.go#L187) and just installing the 0.8 version of the operator, with will use the 0.8 version of kata-containers payload I believe. Do you have a fork of the operator that points to the current CCv0 payload that we can use for testing. I'm not sure we are ready to commit that anyway, so I think we need something in the documentation to allow people to even use policy?

Do you have a fork of the operator that points to the current CCv0 payload that we can use for testing?

I could see a branch in your fork, so created https://github.com/stevenhorsman/cc-operator/tree/peer-pods-use-latest-CCv0-for-testing in case that is helpful

Hey Pradipta, I'm getting nydus errors when trying to deploy this, which might be an error on my side, but another thing that I've realised is that we (in
https://github.com/confidential-containers/cloud-api-adaptor/blob/02662febe863e342c02a12a43b8c793a0e687b82/Makefile#L168
and
https://github.com/confidential-containers/cloud-api-adaptor/blob/02662febe863e342c02a12a43b8c793a0e687b82/test/provisioner/provision.go#L187
) and just installing the 0.8 version of the operator, with will use the 0.8 version of kata-containers payload I believe. Do you have a fork of the operator that points to the current CCv0 payload that we can use for testing? I'm not sure if we want to commit that anyway, so I think we need something in the documentation to allow people to even use policy?

Hey Steve, I manually updated the payload to a latest one for testing.

Hi @bpradipt - I think you'll need to rebase this to pick up the rebase fix I made a couple of days ago and get the e2e tests working.
BTW - I'm still working on testing it - I have the podvm building now, but hitting some issues creating pods that I'm debugging (It's been a while since I manually tested ibm cloud peer pods as I've mostly been playing with libvirt recently). As expected specifying DEFAULT_AGENT_POLICY_FILE in DEFAULT_AGENT_POLICY_FILE=allow-all-except-exec-process.rego make podvm-builder podvm-binaries podvm-image doesn't seem to work which we might want to look into, but not a big deal

I added a Docker build arg to specify the agent policy file during building the binaries.

@stevenhorsman I have rebased the code. PTAL. Hope we can merge this soon

Is there any intention to add an e2e test for this? I think without it and considering that a user can't run it with standard operator deploy as they need a custom payload we should add at the start of the docs that this is an untested, experimental feature and mention the manual adjustment required?

I added a Docker build arg to specify the agent policy file during building the binaries.

I'm not sure if my comment didn't make sense, but I don't think I understand this reply. I ran DEFAULT_AGENT_POLICY_FILE=allow-all-except-exec-process.rego make podvm-builder podvm-binaries podvm-image I think you would need a change in https://github.com/bpradipt/cloud-api-adaptor/blob/a2c636f4663fd0102c662392188a5f99848da135/Makefile#L218 to optionally pass through the DEFAULT_AGENT_POLICY_FILE to get that to work?

I'll add it. My intention was to avoid additional Makefile options if possible. So only added it in Dockerfile allowing anyone to use explicit docker build to use a different policy file than what is shipped and tested as part of upstream.

Is there any intention to add an e2e test for this? I think without it and considering that a user can't run it with standard operator deploy as they need a custom payload we should add at the start of the docs that this is an untested, experimental feature and mention the manual adjustment required?

e2e is definitely needed. But I would prefer to do it as a separate PR. Also for users, we expect them to deploy released version and main is anyway unstable. Or am I missing something ?

I'll add it. My intention was to avoid additional Makefile options if possible. So only added it in Dockerfile allowing anyone to use explicit docker build to use a different policy file than what is shipped and tested as part of upstream.

Sorry if I confused things further. I didn't necessarily mean for it to get added now (though we need to make our docs consistent long term), which is why I said we might want to look into, but not a big deal, I was just trying to explain the process I did as the docker build arg reply suggested that I hadn't explained properly

e2e is definitely needed. But I would prefer to do it as a separate PR. Also for users, we expect them to deploy released version and main is anyway unstable. Or am I missing something ?

I think that's fair, I didn't really mean users, more developers who want to play around with policy to let them know it doesn't work from the main branch at the moment?

e2e is definitely needed. But I would prefer to do it as a separate PR. Also for users, we expect them to deploy released version and main is anyway unstable. Or am I missing something ?

I think that's fair, I didn't really mean users, more developers who want to play around with policy to let them know it doesn't work from the main branch at the moment?

Personally my thinking is that operator deployment from main and kata payload are transient aspects.
I replaced the shim with latest CCv0 using a daemonset. But this is a hack and I don't think it makes sense to add it to the doc.
I can add a statement on requiring a shim with agent-policy support to the doc. Or if there is something else that would help, please suggest and I'll update this PR.
Or if you want to hold this PR till we have the right working payload, I'm fine with that as well :-)

@stevenhorsman the e2e failure looks unrelated

@stevenhorsman the e2e failure looks unrelated

I guess it is might be due to the problem fixed in https://github.com/confidential-containers/cloud-api-adaptor/pull/1651 ?

@bpradipt - What tag of the CAA did you use in your testing? I'm just using the default quay.io/confidential-containers/cloud-api-adaptor:dev-d4496d008b65c979a4d24767979a77ed1ba21e76 with libvirt, and the CAA can't communicate with the peer pod VM (which I also saw last week on the latest CAA then, hence why I used the release one)?

We're getting a failure in the kcli setup:
time="2024-01-08T20:03:06Z" level=info msg="Cluster provisioning"
Traceback (most recent call last):
  File "/usr/bin/kcli", line 33, in <module>
    sys.exit(load_entry_point('kcli==99.0', 'console_scripts', 'kcli')())
  File "/usr/lib/python3/dist-packages/kvirt/cli.py", line 5371, in cli
    args.func(args)
  File "/usr/lib/python3/dist-packages/kvirt/cli.py", line 131, in get_version
    git_version, git_date = get_git_version()
  File "/usr/lib/python3/dist-packages/kvirt/common/__init__.py", line 2112, in get_git_version
    git_version, git_date = open(git_file).read().rstrip().split(' ')
ValueError: not enough values to unpack (expected 2, got 1)
F0108 20:03:08.329146   27874 env.go:369] Setup failure: exit status 1
FAIL	github.com/confidential-containers/cloud-api-adaptor/test/e2e	1.793s
FAIL

I tried re-queuing it a few times last night and still got it and we saw it in the nightly run this morning: https://github.com/confidential-containers/cloud-api-adaptor/actions/runs/7456619508/job/20288166316. I had a quick look at https://github.com/karmab/kcli/blame/main/kvirt/common/init.py#L2107 and the code doesn't seem to have changed recently, but we'll need to dig in a bit more. I'll raise a separate issue for this though.


Tweet link in markdown shows a preview/embed

See previous effort in web3 https://github.com/life-itself/web3/issues/150
Like we do with youtube ... #88
Acceptance

[ ] Pasting a twitter link in its own paragraph at line start results in embed e.g. pasting the following results in an embed/preview of the tweet
[ ] Docs page for this

Blah, blah ...

https://twitter.com/rufuspollock/status/1524012242777395201

Tasks

[ ] research and proposed solution with time estimate
[ ] create a tweet embed component

with placeholder for loading and deleted/not found tweets

[ ] add custom styles for proper tweet embed previews (dark mode)
[ ] use component in links for parsing in markdown.

Notes

Twitter embed api is fairly slow and so takes time to load. A placeholder has been added for better ux.
On further research during development, the embeds (youtube, twitter, etc) load iframes with large htmls which affect the page load and SEO.
Possible solutions to the above problems:

fetch tweets and render component during build time. This requires getting a twitter api key and recreating custom twitter component that matches the look of the embed. (overwork but blazing fast. see here).
create remark plugin for twitter embeds based on this gatsby remark plugin. Although still not sure if this would resolve tweet loading time.

@PhilippeduPreez let's extend our remark-embed plugin to handle twitter embeds as well

@olayway Twitter API usage is not free anymore, so twitter embeds (iframe) looks like the best solution and can be added in the existing remark-embed plugin


OpenShift v3 quickstart

These commits still contain the deployment scripts for the previous version. With the quickstart for v3, the user experience should be much better. BTW, when I tried to use the docker image on Openshift, I got a permission error, presumably because it doesn't run container under root user.
See #246, #1388

Could someone please help me understand why the last three tests might have failed? I don't know enough about what the tests are designed to exercise, but the files I added or modified were all in their separate directories; I can delete them entirely and run Huginn without a problem.

Hi @baip,
thanks for all that work, the spec failures are not related to you changes. Sadly we do have some flaky specs recently.
Is there any way to have a simpler deployment to OpenShift? The amount of code we would need to maintain scares me a bit. Especially compared to Heroku it looks like a lot of boiler plate that every project needs to duplicate. If our docker container would not run as root could the docker image be used to simplify the deployment process?

@dsander It's actually not that bad. There are only files in openshift/templates, .s2i/bin, and .openshift/action_hooks/setup_env; other files in .openshift are left-over from the OpenShift v2. I just wish to keep the scripts recorded somewhere because they would still provide a good example of automated Linux deployment.
If we ask user to run something like a new bin/setup_openshift script, the deployment can be much simpler. The complexity mostly arises from the template files AND allowing the possibility of changing DATABASE_ADAPTER after deployment (so have to provide modified build scripts to use the same hack Dockerfile uses). But providing template files makes it possible for users to do a one-liner deploy or even do it very conveniently on the web console.

Thanks it indeed looks a lot simpler now.

The complexity mostly arises from the template files AND allowing the possibility of changing DATABASE_ADAPTER after deployment (so have to provide modified build scripts to use the same hack Dockerfile uses).

I don't know much about how OpenShift works. Is it kind of a mixture of deploying docker containers and how Heroku works? In the Dockerfile we only have those hacks to precompile the assets when we build the image. Since Rails requires a database connection to do that we need to add the sqlite gem. Heroku does not require the hack because the asset precompilation is done on every deploy (which is kind of the standard for Rails applications). Switching the database adapter should not require any hacks as long as bundle install runs on every deploy.

I think OpenShift now runs Docker containers, while Heroku custom built their own container solution based on LXC. Besides running Docker images directly, OpenShift has something called source-to-image, which uses a language runtime image with scripts that can build user code into a new image and start the application when deployed. So this operation mode is very similar to Heroku. We can also describe the entire setup in a template file, but when using these quickstart templates, the database is being deployed at the same time as the application itself and may not be ready for Huginn to use, which is why I had to modify the builder scripts to use sqlite3 temporarily.

the database is being deployed at the same time as the application itself and may not be ready for Huginn to use, which is why I had to modify the builder scripts to use sqlite3 temporarily.

I see so we could do the asset precompilation in the run script which would allow us to get rid of the assemble script?
When #2112 is merged, can we use one of the docker images for OpenShift? To me it looks like most of the logic that is done in both scripts is already handled by the docker containers.

Yes, but the pod restart will then take significantly longer; the run script does "database:migratebut notbundle install`, so it's quite fast right now. Docker images should work, but then one loses the ability to play with the code and still easily deploy.

I played around with OpenShift a bit and noticed their stock build image for ruby worked as long as I set ON_HEROKU=true in the build environment variables. Not sure how and why (maybe something in Rails changed) but the asset precompilation step does not seem to require a database connection anymore. Maybe that simplifies things a bit?
My build environment config:
                    {
                        "name": "ON_HEROKU",
                        "value": "true"
                    },
                    {
                        "name": "LC_ALL",
                        "value": "en_US.UTF-8"
                    },
                    {
                        "name": "LANG",
                        "value": "en_US.UTF-8"
                    },
                    {
                        "name": "APP_SECRET_TOKEN",
                        "value": "xxx"
                    }

Wow, you're right. I had actually tried adding ON_HEROKU=TRUE, but only after I started tinkering with customizing the assemble script to set up .env. I realized that ON_HEROKU sets up several defaults if the relevant environment variables are not set themselves, but didn't know that it also skips the dotenv file altogether. This means the Dockerfile... I wish I had consulted you first....

Thanks a lot @baip!

Glad to see it merged. Thanks!

Nice @baip!


Bind longpress leftctrl to hyper, one hit leftctrl to capslock not work.

I want:

bind long press capslock to control
bind one hit capslock to esc
bind long press leftctrl to hyper (C-M-S-A)
bind one hit leftctrl to trigger capslock

1 and 2 work well, but 3 and 4 not work.
When I long press leftctrl, it's still leftctrl, when I short hit leftctrl is's leftctrl also.
My configuration is:
[main]
capslock=overload(control, esc)
leftctrl=overload(hyper, capslock)

[hyper:C-M-S-A]

Do you think my configuration is wrong?

Iirc, leftctrl should be leftcontrol (cf. keyd monitor). Looks good otherwise.

Iirc, leftctrl should be leftcontrol (cf. keyd monitor). Looks good otherwise.

Thank you, it works well after I changed to leftcontrol :smile:


Math Expression xor issue

Even with just 1^1 I get this error:
`Error occurred when executing MathExpression|pysssss:
unsupported operand type(s) for ^: 'float' and 'float'`

PS; I'd love to be able to use more logic functions in this node if possible, I've been able to simulate an and, but it's far from pretty

Fixed xor a^b (everything was previously cast to a float, it now leaves ints as they are)
Additionally ive added:
Bitwise ops:
a|b
a&b
~a
Cast:
int(a) - if you have a float but need to use a bitwise operator
Boolean ops (all return 1 or 0):
a and b
a or b
not a
Comparison ops (all return 1 or 0):
== != > >= < <=
Conditional:
iif(value, a, b) - No lazy evaluation, if value is truthy a will be returned, else b
Hopefully that'll be of some use to you (assuming I didn't mess anything up 😅)


RangeError: "size" argument must not be negative

I got a strange error while taking screenshot of a particular page. It happens in ".screenshot()" command. Other steps using "matchScreenshot" works perfectly except this step. Could you please help ? Thank you.
Note: It takes a screenshot but render a empty .png file (0 kB) and cannot move it to the match screenshot folder.
RangeError: "size" argument must not be negative     at Function.Buffer.allocUnsafe (buffer.js:253:3)     at Jimp.cropQuiet (C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\node_modules\@jimp\plugin-crop\dist\index.js:43:27)     at Jimp.(anonymous function) [as crop] (C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\node_modules\@jimp\core\dist\index.js:1222:23)     at crop (C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\lib\screenshots.js:145:26)     at C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\lib\screenshots.js:209:22     at arrayEach (C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\node_modules\lodash\lodash.js:516:11)     at Function.forEach (C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\node_modules\lodash\lodash.js:9344:14)     at stitchScreenshots (C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\lib\screenshots.js:206:7)     at C:\Users\hai.le\AppData\Local\Cypress\Cache\3.4.0\Cypress\resources\app\packages\server\lib\screenshots.js:350:21     at runCallback (timers.js:789:20)     at tryOnImmediate (timers.js:751:5)     at processImmediate [as _immediateCallback] (timers.js:722:5)

I ran into this same issue due to having the following CSS on the element I was trying to take a snapshot of: height: calc(100% - 66px);. When I changed it to max-height, the test is now passing!
Additionally, I was able to get better error messages after upgrading to Cypress 3.5.0 or higher, so you may want to give that a try! https://github.com/cypress-io/cypress/issues/5149

I ran into this same issue due to having the following CSS on the element I was trying to take a snapshot of: height: calc(100% - 66px);. When I changed it to max-height, the test is now passing!
Additionally, I was able to get better error messages after upgrading to Cypress 3.5.0 or higher, so you may want to give that a try! cypress-io/cypress#5149

Could you please specify how to change height: calc(100% - 66px); to max-height ? Is it in HTML of website or cypress-match-screenshot library ?

It'll be in your HTML or CSS file. Try searching for any instances of height: calc( and see if you can refactor away from using it.
Definitely a short-term solution but looks like the bug is either coming from cypress or jimp as many of these plugins have the same issue

I went ahead and filed this issue for the cypress team to weight in on as it's not an issue with this particular plugin: https://github.com/cypress-io/cypress/issues/6099.
I realized that using the CSS properties scale and transition can also cause this issue to occur so you may want to check for those in your codebase as well until a real solution is in place.


[Subtask] Add open API doc for fileset catalog

Describe the subtask
This issue tracks the work of adding an open API doc for fileset catalog, so that we can test it through the generated open API tool.
Parent issue
#1241

@jerryshao Are you working on this? I happen to be interested in the Open API recently and I would like to give it a try. Of course, I'd like to complete some other missing open APIs.

Sure, please go ahead.


Where is BSP code?

Does LiteOS provide BSP? I can't find it.

@VincentLee-EN
Sure, now  you can  find some bsp for differents targets board in the folder:
targets/bsp

@VincentLee-EN
Sure, now  you can  find some bsp for differents targets board in the folder:
targets/bsp


WIP: Add TypeScript to Vue.js

Close #4

@hdurix could you fix conflicts and merge it

Bug bounty claimed: https://opencollective.com/generator-jhipster/expenses/6403


Feature: ability to see how many users are currently connected

Ability to see how many users are connected

@allancoding Do you think you could do this? I'd like this feature but specifically for the public server

Where do you what the stats to be?

Could you put it right under the RUNNING status element. Have something like Users connected: 10

Are we going to keep the other one as a backup? I know my school has that one blocked but not the other one

Ok set https://emuserver.emulatorjs.ga/ as the main one.
Then if that request fails then use the url https://emuserver.herokuapp.com/

Ok, I will do so when I get the time

I think this issue is closed.


Need more CSS resets for sauce performance

Brief inspection looks like min-heights were added to more things.

Looks like we should try to nuke this entire stylesheet actually.  Removing it restores normality and the note sort of explains why it was added the way it was.  Fine for normal strava but not for us.


SSH Port

I tried looking for a settings to change the default sshd port from 22 to something else with no luck, where can this be changed?

there is no such setting. can be changed in a file funct.py
Отправлено из Mail.Ru для Android пятница, 31 августа 2018г., 05:07 +06:00 от Hendrey Chikane<EMAIL_ADDRESS>:

I tried looking for a settings to change the default sshd port from 22 to something else with no luck, where can this be changed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,  view it on GitHub , or  mute the thread .

Thanks, solved it, check this out.
def ssh_connect(serv, **kwargs):
	import sql
	fullpath = get_config_var('main', 'fullpath')
	for sshs in sql.select_ssh(serv=serv):
		ssh_enable = sshs[3]
		ssh_user_name = sshs[4]
		ssh_user_password = sshs[5]
		ssh_key_name = fullpath+'/keys/%s.pem' % sshs[2]
	ssh_port = XXXX
	ssh = SSHClient()
	ssh.load_system_host_keys()
	ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy())
	try:
		if ssh_enable == 1:
			k = paramiko.RSAKey.from_private_key_file(ssh_key_name)
			ssh.connect(hostname = serv, port = ssh_port, username = ssh_user_name, pkey = k )
		else:
			ssh.connect(hostname = serv,  port = ssh_port,  username = ssh_user_name, password = ssh_user_password)
		if kwargs.get('check'):
			return True
		else:
			return ssh

I' m added this too))


Use Rf_mkCharLenCE() instead of Rf_mkCharLen()

Just happened to find this. This can be a problem only on Windows with R < 4.2 (Rf_mkCharLen() uses the native encoding), where UTF-8 is not R's default encoding, so this is almost just a nitpicking.

Do we need to test this explicitly? Perhaps use a non-ASCII string to see how it is handled?

I don't think so. We can test this only on R 4.1, which will retire soon.


Can only print one page in docs

Reported by Mike Dianovsky -
Your print feature in your MakeCode Docs only lets you print the first page of the document and not the entire document :  https://arcade.makecode.com/courses/csintro2/functions/intro
Is there a way to print the complete document?  I provide the link above as an example to show that only page 1 will print.
Also, I noticed that Print is broken completely in Edge.

multi page printing be fixed when we next release arcade as I fixed that in the new docs:

Not sure on edge printing; it looks better on edge, but had a few quirks still (https://arcade.makecode.com/concepts w/ new docs is only printing the first 6 boxes on edge, where it's printing everything properly on chrome). Will take a look

This is fixed in Arcade and will be released as part of the next release. ETA end of month.


Update 404 template

See https://github.com/ietf/www.ietf.org/issues/17

No action is required. 404 will be served from wagtail after tomorrow's migration.


Adding OUTDIR env var, update to docker 1.9.0

Adding optional OUTDIR env var which defaults to ./bin/${name}
Update docker to 1.9.0
fixes #14

I can confirm that this fixes my problem (issue 14).

If this defaults to writing to bin instead of the root of the source path, I think it's going to break existing users who are used to the way it works out of the box. Like my CI. :smile:
Maybe instead of OUTDIR, you can just override the whole path altogether? Then you can do whatever you want, make it bin/vault or nonconflicting-vault, etc.

testing-the-ground-with-one-toe-vault...

@dpetersen where should we put the compiled binary? typically it would go in $GOPATH/bin right?

@chiefy it's $GOPATH/bin when you go get something, but generally a go build will just drop the binary in the same directory you're in as far as I know. The golang-builder seems analogous to a go build.
Either way, the current implementation drops the binary in the source directory. If we change that default it's going to break any setup that depended on the current default location of the build binary. I do like the idea of being able to customize the location and name of the binary for cases where the default doesn't work, like vault.

@dpetersen I refactored it a bit, added some docs and rebased. Your CI looks like it isn't setup right?

I don't know what circle's deal is. As far as I know it was never set up to run on this project at all.
So I don't have merge rights on this repository. The Labs team does not actually exist anymore, though some of us do have the ability to merge here. @bdehamer, does this look good to you? It looks good to me.

@dpetersen @bdehamer Can you please merge @chiefy 's changes? I am hitting the same issue while trying to create vault container.

ping @dpetersen @bdehamer LGTM :thought_balloon: ?


FY2020Q2 Refresh

Updated instructions for all exercises
Updated project files for all exercises
Refreshed screen captures in slide deck for Ex 2

manually merged


Security: Update stylus to 0.54.5, fixes minimatch 0.3.0 RegExp DoS issue

Hi there,
Kue currently uses<EMAIL_ADDRESS>with the following dependency tree:
+<EMAIL_ADDRESS>  +<EMAIL_ADDRESS>    +<EMAIL_ADDRESS>
On install, NPM warns<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue".
Simply updating the package.json to<EMAIL_ADDRESS>would update glob to 7.0.x and minimatch to 3.0.2, fixing the RegExp DoS issue.
Thank you!
P.S. Very funny that this security alert is issue #911 🚨

Come across this issue via synk.io
More details can be seen here
https://snyk.io/test/npm/kue/0.11.1

this should be fixed now


Should unresolved newsbeuter issues be reposted here?

Should unresolved newsbeuter issues be reposted as newsboat issues or will you somehow migrate them?

I decided against migration because I have no way of disabling the Newsbeuter issue tracker. Issues will be posted both here and there, and the trackers will diverge. I can fight it by reposting every issue, or I can embrace it by treating Newsbeuter tracker as an extension of Newsboat's. That's one point.
Another point: Newsboat development should happen on Newsboat turf, so discussions should happen here even if the bug originated in Newsbeuter.
Thus, the guideline is:

if you have something new to say, open an issue here and reference Newsbeuter one (use akrennmair/newsbeuter#123 syntax, GitHub will turn it into a link);
if you're fixing a bug that has an issue in Newsbeuter but not in Newsboat, don't bother filing it—just reference the Newsbeuter issue. I'd also drop a comment in that Newsbeuter issue saying the issue has been fixed in Newsboat; this will send notifications to everyone who subscribed.

I didn't actually discuss this with anyone, so if you see any flaws, please point them out!

Considering that newsbeuter has 200 open issues, how would you keep track of the one’s not affecting newsboat and those fixed in newsboat?
How about creating a newsboat meta-issue containing a list of newsbeuter issues (just their titles as links) and then tag these issues as fixed, invalid, to do, etc.?

Users and developers could see the state of any old issue (doing this in the newsbeuter tracker without the ability to close issues might become difficult)
Developers could easily find old bug reports and feature requests to work on
Discussions could proceed to take place in their original newsbeuter issues where relevant comments might already have been posted (if a discussion becomes irrelevant to newsbeuter, it can still be migrated to a new newsboat issue)
Should anyone continue developing newsbeuter, they could easily see what has been done and issue discussions would not be split across two projects (unless necessary)

Rather than reply to each of your points separately, I'll attack your assumptions, of which I see two:

there are developers who look through old issues in search of something to fix; and
all bugs will be fixed.

The first assumption runs counter to what I've seen while maintaining Newsbeuter: there were zero PRs fixing issues reported to our Google Code tracker. Issues were fixed because:

a developer ran into them him-/herself; or
there was some discussion where an old issue was mentioned and this somehow sparkled developer's enthusiasm; or
BountySource offered a reward for fixing it; or
the issue was new and easy and I fixed it during triage or shortly afterwards.

The second assumption I agree with in principle, but disagree with in context of Newsboat and Newsbeuter as they are today. There are more new issues than commits fixing them. There are only a handful of "serial contributors", none of them very active. (That includes me.) Even though Newsbeuter is 10 years old, it's still in a bootstrapping stage where code-writing activities haven't yet reached sustainable levels. While that is the case, we don't need a perfect system where every bug is up-to-date—developers are so few that imperfections are easily resolved by talking to each other.
(My view on first assumption is based on my memory—I didn't do an actual numeric analysis of PRs. My view on second assumption is biased—I like programming and am not very interested in management.)
Does that stance make sense to you?

Yes, your stance makes sense to me.
(As a side note, I did not make any assumptions as I am not familiar enough with the development of newsbeuter. I only listed a few points that would be made possible by the meta-issue approach. You can certainly judge much better than I whether it would make sense.)
The reason I created this issue in the first place is simple. As a user I was wondering how I could make it as easy as possible for developers to discover, prioritize and fix the issues I (and others) previously created.

Ah; sorry for going full analytical and preachy on you, then.
For a user, the situation is quite grim: one writes a detailed report, answers whatever questions I might ask during triage, and then waits for someone to decide to work on the issue. Developers are few ⇒ no organization ⇒ no leverage to influence them to work on a particular thing.
Regarding your points: the first and fourth are already possible because we'll reference Newsbeuter issues from here, and GitHub will display "backlinks" in the other tracker. The second point I addressed as a first assumption; third point is complicated because relevancy is subjective, off-topic creeps in slowly not suddenly, and even technical discussions rarely are about a single thing. So the situations isn't as bad as you might've thought (we have some of your points), but far from perfect (if only we could make the other tracker read-only...)
I guess we're done with this issue, so I'm going to close it. Thank you for your concern, and sorry about my answers being as dissatisfying as they are. I'm not deliberately making Newsboat development harder to get into than it should be, I promise!

I end up breaking my own rules now: instead of dragging all discussions to this tracker, I had a little chat in Newsbeuter's. I think it's okay because the problem was small and the fix quite obvious; though if the person wanted to select what URL to enqueue, I'd ask them to discuss it here because it's a lengthier and more Newsboat-specific discussion.

Newsbeuter repo is now archived. We can be sure no new issues or comments will appear there.
If you're still affected by an old, unresolved Newsbeuter issue, please re-report it on this issue tracker.


Structured readme

I added a few bits of our NAR abstract because we forgot to say what's the purpose of workbench :)
I also made a clearer that the only requirement is Docker, and separated Kitematic from non-Kitematic users when describing how to launch the whole thing.
I modified the "&" and remove the "(" and ")" in the section headers because "special characters" broke the links in the TOC (escaping, or using html entities didn't work)

Modifications I'd like to introduce:
I would break up the tools' table into as many tables as the number of tool categories, so that the whole TOC becomes more structured, and the table becomes more readable:

one column less
table header always visible
more "go to back" button instead of just one at the end of the table
What do you think?

one column less
table header always visible
more "go to back" button instead of just one at the end of the table
What do you think?

Yes please! Good idea!


feat: add new snapshot cheatcodes

ref https://github.com/foundry-rs/foundry/pull/6548

merged into foundry, available next nightly


Paste image wrong ?

When paste image, every image looks like an attached image
optional settings
    "pasteImage.namePrefix": "${currentFileNameWithoutExt}_",
    "pasteImage.prefix": "/",
    "pasteImage.path": "${projectRoot}/img",
    "pasteImage.basePath": "${projectRoot}",

On the Finder of MacOS, copy a image file would only copy the icon of file, you have to open file and then copy image.

thanks


Align ManagementServerPortUtils strategy from boot 2

@spencergibb could you add some details to the description of the issue?  If you think this can be done in Hoxton.SR1 can you move it there?


[release-2.4] trigger a new build to fix cve problems

Signed-off-by: Wei Liu<EMAIL_ADDRESS>

/lgtm

refer to https://github.com/stolostron/backlog/issues/22156


add some tools for generating all dumps and scraping for metadata

Running
python gemmbench/gemm_bench.py
python common_utils/get_dumps.py gemm/mlir
python common_utils/instruction_counts.py gemm/dumps

Will generate a .csv that looks like:

Filename
Instruction Count
agpr_count
vgpr_count
vgpr_spill_count

./gemm/dumps/gemm_4096_4096_8192_bf16_tA/module_main_dispatch_0_rocm_hsaco_fb.rocmasm
1022
0
66
0

./gemm/dumps/gemm_2048_10240_1280_bf16/module_main_dispatch_0_rocm_hsaco_fb.rocmasm
1020
0
66
0

./gemm/dumps/gemm_1024_10240_1280_bf16/module_main_dispatch_0_rocm_hsaco_fb.rocmasm
1020
0
66
0

./gemm/dumps/gemm_8192_5120_640_bf16/module_main_dispatch_0_rocm_hsaco_fb.rocmasm
1020
0
66
0

./gemm/dumps/gemm_8192_8192_8192_f16/module_main_dispatch_0_rocm_hsaco_fb.rocmasm
520
32
132
0

Actually, why do we need get_dumps at all? This can be generated with the --dump_dir flag in the main script

@kuhar good point, I removed the file.

I took your code and cleaned it up in the way I would write it: https://github.com/nod-ai/iree-kernel-benchmark/pull/15
Didn't want to highjack your PR, but I want to structure it differently so that we can add more static attributes like the compilation pipeline from mlir, and I didn't see how else to make it more extensible

Closing as this was superseded by https://github.com/nod-ai/iree-kernel-benchmark/pull/15


Swift Package Manager support

This PR does not support swift test because it requires test dependencies are SPM compatible.
Currently, OHHTTPStubs is not SPM compatible.

:ship:


Remove Dependency on commons-configuration

Is it possible to refactor and eliminate dependency on commons-configuration?
In Hystrix I'm exploring whether I should eliminate use of Archaius in core due to different environments having conflicts. The primary source of conflicts is the Apache Commons libraries (https://github.com/Netflix/Hystrix/issues/252 as example).
If Archaius truly needs commons-configuration, does the usage of it need to be part of the public API, or can the usage be shaded internally so it's not a dependency seen by consumers?

@gorzell @howardyuan Any progress on removing Guava/Jackson from the exported set of Archaius dependencies?  I'm combing through Hystrix backlog and ran across Netflix/Hystrix#252 and was curious where this was at.  Thanks!

I have been thinking about this a bit.  I think it really depends on which dependency you care the most about.  I don't actually know how guava is being used, I can guess about Jackson.  These can probably be pulled out into sub modules, or surgically removed pretty easily.
The dependency on commons-configuration is a much bigger deal and would probably warrant a major version effort.  Some of the key things to think about would be:

Separating the API from the implementation
How to best plug in/load the correct implementation at runtime
The bootstrap process for archaius in general.  Right now it depends on a static block and the class loader.  This would probably need to be changed to something totally different in order to support a more plugable implementation.

These are just my initial thoughts, I am sure there are more concerns that I am forgetting.

:+1: on changing the way archaius bootstraps.  @gorzell's list is great.  spring-cloud-netflix has to work around the static initializers and general use of static singletons.

Perhaps we can instead just focus on Archaius 2 which we are wanting to do anyways as we move towards async/reactive support alongside Ribbon/RxNetty/Eureka2/etc?

@benjchristensen I took a quick look around the project and didn't see anything relating to Archaius 2.  Is there a design doc or something similar somewhere?  Is it in another repo that I missed?
I think we can address these issues either way, or both.  Although as mentioned some of them will involve breaking existing APIs/packaging.

No there aren't yet. Just emerging discussions that Archauis v1 doesn't fit the new apps we're building very well.

It would be great to have a chat about the goals of that effort so that we can decide how and where we want to tackle some of these bigger issues with the library.

@elandau has put in a lot of thoughts in Archaius V2.0. I'm looping him in so he can share his thoughts. I know that he's planning to write down some doc soon.

I'm going to open a bunch of issues regarding Archaius 2.0.  But in the meantime here are some thoughts,
Archaius will be broken up into the following projects

archaius-core   The only dependency will be commons-lang3 for the interpolation code
archaius-typesafe  The only dependency will be typesafe config
archaius-governator  Will pull in governator and guice and re-implement fabricator to merge configuration with configuration mapping and DI.  This will likely be what's described here, https://github.com/Netflix/governator/issues/182
archaius-legacy   Adapters for the legacy API

The new API will be designed with a more robust ConfigurationManager.  There will be no static classes so archaius can be easily used in unit tests.  The ConfigurationManager will manage configuration loading via a pluggable ConfigurationLoader SPI.  Multiple ConfigurationLoaders may be added to support various configuration solutions such as Typesafe Config and Commons Configuration, all of which will reside in separate sub-projects so dependencies will be under tight control.  Cascade loading will be specified via a CascadingPolicy interface that converts a single configuration name (basename, filename, URI, etc.) to a priority ordered list of possible permutations to load.  ConfigurationManager will manage configuration in two tiers.  The first is the top level property solution order, such as FastProperties, Application, Library, System, Env.  The second will track cascaded configurations and library configurations in the order in which they are loaded.  This will only be done in the Application and Library order.  The top level configuration will be responsible for resolving the property name as well as interpolating the value.
I'm also planning to redo DynamicProperty to treat property value updates as streams of updates with binding to variables and methods as an extension.  This will allow us to maintain a simple property update API.
For example,
public class MyService {
     private AtomicInteger timeout = new AtomicInteger();

    @Inject
    MyService(ObservablePropertyManager manager) {
        manager.subscribe("myservice.timeout", Integer.class, 1000, FieldUpdater.create(timeout));
    }

    private void doSomething() {
        while (true) {
               ... timeout.get();
        }
    }
}

Or react directly to updates,
public class MyService {
    @Inject
    MyService(ObservablePropertyManager manager) {
        manager.subscribe(new PropertyObserver<Integer>() {
                        public void onChange(Integer newValue) {
                        }
                   }, "myservice.timeout", Integer.class, 1000, );
    }
}

I plan to have a prototype ready by end of next week so we can reference the code in this discussion.

That all sounds like good progress.  I am wondering if you could even pull out the string stuff into another module.  I am also curious if the cost of autoboxing really warrants having specially named classes for all the primitive types (but maybe I have just been in scala land too long).
Would the stream aspect introduce a dependency of core on Rx?  I understand why Rx integration is important, but I am not sure how much of the community at large would want to have it as a direct dependency.

Sorry, I didn't mean to imply this will have a dependency on Rx.  I was just describing an Rx like API.  With that said, I do envision an archaius-rxjava subproject that can convert a property value stream to an Observable so that the property can be composed into your Rx code.

Sounds good.
On Feb 27, 2015 1:04 PM, "elandau"<EMAIL_ADDRESS>wrote:

Sorry, I didn't mean to imply this will have a dependency on Rx. I was
just describing an Rx like API. With that said, I do envision an
archaius-rxjava subproject that can convert a property value stream to an
Observable so that the property can be composed into your Rx code.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/archaius/issues/182#issuecomment-76471461.

I issued PR #215 for v2 initial implementation.  If you want to review it's best to fork and look at the code locally because the PR changes are painful to look at as they include all the deleted files.


Drop support for theia as a browser editor

Describe the bug

Gitpod no longer supports Theia as a browser editor so gitpod-laravel-starter should not either
simply removing the .theia directory from this repository should fix the bug and not be considered a breaking change since Gitpod users no longer have the option of using Theia at all.
Screenshots

Steps to reproduce

Expected behavior

Additional information

This change affects the tools for this project, so:

[ ] Add support for this in the updater: https://github.com/apolopena/gls-tools/blob/main/tools/update.sh
[ ] Add support for this in the manifest generator: https://github.com/apolopena/gls-tools/blob/main/tools/manifest.sh


Improve bar chart borderRadius

As you can see, the endingShape & startingShape are very ugly for bar chart.
plotOptions: {
  bar: {
    horizontal: false,
    columnWidth: '50%',
    distributed: true,
    endingShape: 'rounded',
    startingShape: 'rounded',
  },
},

Please change 'flat' or 'rounded' to number (or add the possibility to use number) to create custom border radius for bar column.
For example (similar in HighCharts):
https://github.com/highcharts/rounded-corners & https://jsfiddle.net/BlackLabel/tdp1y0wb
or
https://github.com/bellstrand/highcharts-border-radius

@junedchhipa any progress on this? Can you please give an option to set border radius for vertical bars same as backgroundBarRadius option in bar plotOptions?

there is a little css trick you can use here with css clip-path , You will have to tweek it so meet your specific styling needs and you have to disable animations on the chart ( you might be able to keep animations if you apple the style after the animations have been set with something like renderer2
.apexcharts-bar-series.apexcharts-plot-series
  .apexcharts-series:nth-child(1)
  path {
  clip-path: inset(0% 0% -31% 0% round 8px);
}

This specific style was using with a stacked bar, it might be a bit different with a normal bar chart

there is a little css trick you can use here with css clip-path , You will have to tweek it so meet your specific styling needs and you have to disable animations on the chart ( you might be able to keep animations if you apple the style after the animations have been set with something like renderer2
.apexcharts-bar-series.apexcharts-plot-series
  .apexcharts-series:nth-child(1)
  path {
  clip-path: inset(0% 0% -31% 0% round 8px);
}

This specific style was using with a stacked bar, it might be a bit different with a normal bar chart

Since v3.26.0, there is a new property called borderRadius which allows setting the rounded borders manually.
plotOptions: {
  bar: {
    borderRadius: 5
  }
}

Can borderRadius accept percentage @junedchhipa? The current implementation looks weird especially when the column width changes.
Here is what I want. Basically perfect round corners.

But here it is when the column width becomes too large.

It gets even weirder when the column width gets too small.

Thx for the great lib btw.


Gradle does not treat SNAPSHOT dependencies in Ivy repositories as changing

For our company we have a large, multi-repository, multi-module gradle setup. The code is separated in multiple smaller but interdependent artifacts which are downloaded from, and published to, our artifactory-server. For active development, all artifacts are versioned with "-SNAPSHOT".
This setup works pretty well, but only if we run --refresh-dependencies often to force refreshing of our SNAPSHOTs. This makes building unreliable from IDE's and also forces needles refreshes of non-changing artifacts.
Expected Behavior
If artifacts are suffixed with "-SNAPSHOT" they should be marked changing. Artifacts that are marked changing should be refreshed every single time if resolutionsStrategy.cacheChangingModulesFor 0, 'seconds' is set. Both for direct, and for transitive dependencies.
Current Behavior
Even though dependencies are downloaded some of the time, they are not refreshed reliably. It is hard to test what causes the dependencies to download or to be marked as up-to-date, but I think they are not marked as 'changing' correctly. The only thing I found in the logs after much experimentation was the following when using --refresh-dependencies:
[DEBUG] [org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.IvyXmlModuleDescriptorParser] post 1.3 ivy file: using exact as default matcher
[DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ExternalResourceResolver] Metadata file found for module 'com.company:some-artifact:master-SNAPSHOT' in repository 'ARTIFACTORY_REPO'.
[DEBUG] [org.gradle.api.internal.artifacts.ivyservice.modulecache.DefaultModuleMetaDataCache] Recording module descriptor in cache: com.company:some-artifact:master-SNAPSHOT [changing = false]
[DEBUG] [org.gradle.api.internal.file.delete.Deleter] Deleting /home/USER_NAME/.gradle/caches/modules-2/metadata-2.23/descriptors/com.company/some-artifact/master-SNAPSHOT/5a53c5d0c22379b62e7ea108d68c191d/descriptor.bin
[DEBUG] [org.gradle.api.internal.file.delete.Deleter] Deleting /home/USER_NAME/.gradle/caches/modules-2/metadata-2.23/descriptors/com.company/some-artifact/master-SNAPSHOT/5a53c5d0c22379b62e7ea108d68c191d/descriptor.bin.fslck

Company details are obviously changed but the interesting part was the [changing = false] part, which is logged out by gradle at this line. This suggests that somewhere the changing property is not correctly forwarded.
Setup to Reproduce
▾ repo1/
    ▾ module-one/
        build.gradle
    build.gradle
▾ repo2/
    ▾ module-two/
        build.gradle
    build.gradle

And in module-two the following setup.
def version = "master-SNAPSHOT" //Actually provided by a custom plugin
dependencies {
	compile("com.company:module-one:${version}")
}

The problem occurs when module-one is already in cache, but has been changed and republished to the same location with the same version name. The changed version is not re-downloaded.
Environment
Reproducible on Ubuntu (14 and 16) and on Windows 7. Version output:
------------------------------------------------------------
Gradle 3.5
------------------------------------------------------------

Build time:   2017-04-10 13:37:25 UTC
Revision:     b762622a185d59ce0cfc9cbc6ab5dd22469e18a6

Groovy:       2.4.10
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_65 (Oracle Corporation 25.65-b01)
OS:           Linux 3.11.0-26-generic amd64

What I've tried
I've tried setting the changing property manually, both for transitive and direct dependencies, but this did not change anything.
    configurations.all { config ->
        resolutionStrategy {
            cacheChangingModulesFor 0, 'seconds'
            cacheDynamicVersionsFor 0, 'seconds'
        }
        incoming.beforeResolve {
            allDependencies*.each { dep ->
                if ( dep.getVersion()?.endsWith( '-SNAPSHOT' ) ) {
                    if ( dep.metaClass.respondsTo( 'setChanging', Boolean ) ) {
                        dep.setChanging( true )
                    }
                }
            }
        }
        afterEvaluate {
            if (config.state != org.gradle.api.artifacts.Configuration.State.UNRESOLVED) {
                throw new GradleException("ERROR: [...]")
            }
            allDependencies*.each { dep ->
                if (dep instanceof ExternalModuleDependency) {
                    if (dep.version.endsWith("-SNAPSHOT")) {
                        dep.setChanging(true)
                    } else if (dep.group.equals('de.esolutions')) {
                        logger.warn("WARNING: Custom version used for eso project '${dep.group}:${dep.name}:${dep.version}' in $config. Don't forget to fix this before comitting.")
                    }
                }
            }
        }

Do you configure cacheChangingModulesFor and cacheDynamicVersionsFor for all projects or the subproject that need it by using allprojects or subprojects? Just putting the logic into the root build script of your multi-project build won't do.

@meonlol Did you get your issue resolved in the meantime?

Sorry, I'm very busy at the moment.
I do apply it for all projects, which makes it so weird.
I realize that it will be hard to reproduce, so I will try to setup a demo project to isolate the problem away from our setup as soon as possible.

Okay, so I reproduced the Bug:
https://github.com/meonlol/bug-refresh-dependencies
The dependency-graph is like this:
project:proj-module
\---  sdk:sdk-module
      \--- sdk:sdk-module-api

sdk-module depends on sdk-module-api
So when I make a change in the Interface in sdk-module-api, publish it to artifactory, and run ./gradlew build -I ../init.gradle from project, I expect it to download the changed jar for sdk-module-api automatically, as all artifacts are marked -SNAPSHOT, but it does not refresh without --refresh-dependencies.
I've tried to explicitly set the incoming dependencies to changing using the init.gradle script, but is seems to have no effect.

We've just come across this problem also - although I don't think it's because of SNAPSHOT dependencies being marked as changing = false. What we do see is that, even though we've overridden the default cache expiry using cacheChangingModulesFor, the cache is only "expired" after 24 hours. I've done some debugging of this, and it appears to be because even though all the Configurations defined by the gradle script have an extra moduleCacheRule and artifactCacheRule with the expiry age that we've specified in the build script, when it comes time to do the actual resolving, the Configuration used is a detachedConfiguration (not sure what that is), created in the MavenPomResolver (from the dependency-management-plugin). Detached configurations are created with the DefaultConfigurationContainer.detachedConfiguration() method, and they don't have the extra moduleCacheRule or artifactCacheRule on the DefaultCachePolicy in the ResolutionStrategy.
I hope that makes some kind of sense to someone with a better knowledge of Gradle than myself.

I've just tested it and the bug is still present in Gradle 4.3.1.
This bug forces us to --refresh-dependencies on all our builds, and as our project grows our build times also increase, which is getting to a point where it starts becoming a real problem for our developers.
Could someone please look in to this?

Thanks for providing a sample project. I am going to have a look in the coming days. General observation: You use the Maven SNAPSHOT syntax though you are publishing and consuming to an Ivy repository. What's the backstory here? Why don't you set up a Maven repository if that's the concept you'd like to use.

Well, when we started on this project we decided to make our build system compatible with our old projects, which use Ant, and since Ivy was built for Ant we decided go with that.
Later we wanted to have our internal artifacts represent the tips of our branches, for which we decided to use the -SNAPSHOT notation as we figured the standardized notation would mark the artifacts as changing automatically.

A module with a *-SNAPSHOT version coming from a Maven repository will be considered changing by default. If you're using an Ivy repository, this rule doesn't apply, which means you'll need to tell Gradle to consider these modules as changing.
Note that the code in your example init.gradle will not apply to transitive dependencies. You're using configuration.allDependencies {} which applies to direct dependencies declared in the configuration or any parent configurations, but not transitive dependencies.
So you have a few options:

Stop using SNAPSHOT modules, and instead publish each SNAPSHOT with a unique version and use a version range selector to get the latest one.
Switch to using a Maven repository, for which Gradle will automatically consider SNAPSHOT to mean 'changing'.
Tell Gradle to consider all -SNAPSHOT dependencies as changing, something like this:

dependencies {
    components {
         all { ComponentMetadataDetails details ->
             if (details.id.version.endsWith('-SNAPSHOT')) {
                  details.changing = true
             }
         }
    }
}

We've tried option 3, as you can see in the code under "What I've tried" in my initial comment, and it doesn't work. That's the problem.

I could not get your suggestion to work. This is still a problem, that is consistently reproducible in the repo I've built for it:
https://github.com/meonlol/bug-refresh-dependencies
I will try and see if we can migrate to a maven repo as a workaround.

Sorry if I wasn't clear: Gradle does not treat SNAPSHOT dependencies in Ivy repositories as changing. This isn't a bug: because SNAPSHOT modules are a Maven concept we decided long ago to only treat these as changing when they are found in a Maven repository.

To get the components rule working, try adding it to https://github.com/meonlol/bug-refresh-dependencies/blob/master/project/proj-module/build.gradle. It might be worth adding a println details.id before the if block in the rule to see if any components are being loaded by the rule.
Something like this:
dependencies {
    compile("com.bug.refresh.dependencies:sdk-module:${version}")

    components {
         all { ComponentMetadataDetails details ->
             println details.id
             if (details.id.version.endsWith('-SNAPSHOT')) {
                  details.changing = true
             }
         }
    }
}


parquet-cli without hadoop throws java.lang.NoSuchMethodError on any parquet file access command

I can't do even basic things with parquet-cli from 1.13.0-SNAPSHOT.
Steps to reproduce:

git clone <parquet-mr repo>
cd parquet-mr
mvn clean install -DskipTests
cd parquet-cli
mvn clean install -DskipTests
mvn dependency:copy-dependencies
java -cp 'target/*:target/dependency/*' org.apache.parquet.cli.Main cat <parquet file>

Results:

Exception in thread "main" java.lang.NoSuchMethodError: org.apache.parquet.avro.AvroSchemaConverter.convert(Lorg/apache/parquet/schema/MessageType;)Lorg/apache/avro/Schema;
    at org.apache.parquet.cli.util.Schemas.fromParquet(Schemas.java:89)
    at org.apache.parquet.cli.BaseCommand.getAvroSchema(BaseCommand.java:405)
    at org.apache.parquet.cli.commands.CatCommand.run(CatCommand.java:66)
    at org.apache.parquet.cli.Main.run(Main.java:157)
    at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
    at org.apache.parquet.cli.Main.main(Main.java:187)

Environment: Amazon Linux 2, Java 8
Reporter: Timothy Miller / @theosib-amazon
Assignee: Kengo Seki / @sekikn
Note: This issue was originally created as PARQUET-2142. Please see the migration documentation for further details.

Balaji K:
I see your environment is Linux. Feels like a dupe of https://issues.apache.org/jira/browse/PARQUET-2104 . Parquet-cli is broken on linux afaik.

Kengo Seki / @sekikn:
I also came across this issue. As @theosib-amazon pointed out, parquet-cli-$PROJECT_VERSION-runtime.jar contains the same class as parquet-cli-$PROJECT_VERSION.jar with a different method signature, due to the relocation of the org.apache.avro package.

$ unzip target/parquet-cli-1.13.0-SNAPSHOT-runtime.jar org/apache/parquet/avro/AvroSchemaConverter.class
Archive:  target/parquet-cli-1.13.0-SNAPSHOT-runtime.jar
  inflating: org/apache/parquet/avro/AvroSchemaConverter.class
$ javap -c org.apache.parquet.avro.AvroSchemaConverter

...

  public org.apache.parquet.schema.MessageType convert(shaded.parquet.org.apache.avro.Schema);

...

  public shaded.parquet.org.apache.avro.Schema convert(org.apache.parquet.schema.MessageType);

...

I'll submit a documentation fix to notifying users not to include unnecessary jars when running parquet-cli without Hadoop.

Timothy Miller / @theosib-amazon:
I added -verbose:class to the java command line, and I found this in the output:

[Loaded org.apache.parquet.avro.AvroSchemaConverter from file:/local/home/theosib/packages/PARQUET-2140/parquet-mr/parquet-cli/target/parquet-cli-1.13.0-SNAPSHOT-runtime.jar]

This isn't correct. It should be loading AvroSchemaConverter from target/dependency/parquet-avro-1.13.0-SNAPSHOT.jar. Evidently the instructions are wrong. I changed the run command to this:

java -cp 'target/parquet-cli-1.13.0-SNAPSHOT.jar:target/dependency/*' org.apache.parquet.cli.Main cat ~/guid.parquet

And the NoSuchMethodError went away. Now I get the Unknown error and java.lang.RuntimeException that we see in PARQUET-2143.


kms.list_resource_tags does not support KeyArn parameter

Hi,
Expected behaviour: call kms.list_resource_tags(keyARN) and get the tags back (if the key was created before).
Actual behaviour:
botocore.errorfactory.NotFoundException: An error occurred (NotFoundException) when calling
  the ListResourceTags operation: The request was rejected because the specified entity or resource
  could not be found.

Boto3 docs https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/kms.html#KMS.Client.list_resource_tags says you can pass KeyID or KeyARN as parameter.
I traced the moto.kms.models.list_resource_tags method and I see it does a dict.get on a dict keyed by KeyID. So, it makes sense a lookup by KeyARN fails.
Thanks again for developing moto!

Hi @rtoma,thanks for raising this! Marking it as a bug, as we should support both options.

This should be fixed as of moto >= 2.2.8.dev23 - let us know whether we've missed anything.


Spawning actors out of begin_play

Hi,
I'm having an issue when spawning new actors. The code works fine when inside the function begin_play, but when called from an other function it just crashes UE without explanation.
I'm new to UE so maybe I haven't completely understood how it should work...
Here is the code I use :
new_actor = self.ue_object.actor_spawn(ue.find_class('PyActor'), FVector(0, 0, 0), FRotator(0, 0, 90))
Thank you

Are you using a threaded build ?
Does the following class (mapped to PyActor) works:
class Spawner:
    def begin_play(self):
        self.uobject.enable_input()
        self.uobject.bind_pressed_key('X', self.spawn)

    def spawn(self):
	    new_actor = self.uobject.actor_spawn(ue.find_class('PyActor'), FVector(0, 0, 0), FRotator(0, 0, 90))

Yes I'm using a threaded build.
Your class works fine, it also works fine when I do :
class SuperHero:

    def begin_play(self):
        ue.log('Begin Play on Hero class')
        self.uobject.enable_input()
        self.uobject.bind_key('K', ue.IE_PRESSED, self.spawn)

    def spawn(self):
        ue.log("Spawned")
        new_actor = self.uobject.actor_spawn(ue.find_class('PyActor'), FVector(0, 0, 0), FRotator(0, 0, 90))

```

But UE still crashes when called from an other function inside SuperHero.
The log only shows :
[2016.10.04-19.24.26:412][452]LogPython: Spawned

Remove threading support, unfortunately an optimization we have in the PyActor constructor causes a deadlock. I am still unsure if investing in threading support is a good idea. It introduces lot of performance implications and complexities. I leave the issue opened as the fix is pretty easy (albeit it wil lrequire to disable the optimization when threading is enabled)

Latest version removed the python initializiation out of the constructor. This should support object spawning in any part of the code

Can we close it ?

Yes thank you for the quick fix. Works fine for me now

I am using multithreading to Spawn an Blueprint Actor and Unreal Engine is crashing suddenly when the spawn function called.


java.lang.NoClassDefFoundError

java.lang.ClassNotFoundException: Didn't find class "com.googlecode.mp4parser.authoring.Movie" on path: DexPathList[[zip file "/data/app/io.uxtesting.uxtester-YVh29ln6RLhg8oU75MkwCQ==/base.apk"],nativeLibraryDirectories=[/data/app/io.uxtesting.uxtester-YVh29ln6RLhg8oU75MkwCQ==/lib/arm64, /system/lib64]]

This is probably caused by your progaurd


Add Server 2016 NAT support

With Server 2016 TP3+, there is a new NAT virtual switch type. This would be an excellent addition to the module (I wish it was included in Windows 10 too :angry:). However, in the first instance, it will need some additional metadata in the configuration document..

@iainbrighton I can work on adding this NAT support.

@DexterPOSH - Thanks for volunteering! :smiley:
Just a word of warning - as we're using the xVMSwitch from the xHyper-V DSC resources to configure the virtual switches, this functionality will first need to be put into the official https://github.com/PowerShell/xHyper-V resource. I have opened an issue https://github.com/PowerShell/xHyper-V/issues/40 to implement this functionality.
Are you still happy to implement this functionality over there first? Once complete, we can then enable NAT functionality here?

@iainbrighton Thanks for the heads up.
Let me try and see if I can finish this early, if am able to do that I will do a PR to the parent repo.

@DexterPOSH @csandfeld - FYI - It looks like NAT support is included on Win 10 build 10586. I might be seeing the NAT -SwitchType be because I have the RSAT tools installed?! Regardless, I have a NAT virtual switch up and running on build 10586 :smiley:
From other Twitter conversations, it looks like the New-VMSwitch implementation might be changing, at least that it what it looks like in the later Win 10 build 11082. If this is the case, we're all going to be in for a bumpy ride :grimacing:

NAT support on Win 10 :+1:
Changing New-VMSwitch implementation :-1:

Win 10 11082 allows me to specify NAT as the Switch type although it seems that the Help Needs updating to reflect that this has been included - not updated either after running Update-Help -Force
I reckon its part of either the implemented version of HyperV or possibly via RSAT tools
But you can create a NAT Switch with the below
New-VMSwitch -Name NAT -SwitchType NAT -NATSubnetAddress <IP_ADDRESS>

Poor example but yeah its in there

Cool. I haven't deployed 11082, but does the Win 10 RSAT hotfix install OK (you would have had to manually download it, install it and then enable the features)? I typically get an 'unsupported' error with the RSAT tools on preview builds!

Didnt have it installed when I ran it - though I do now and it installed fine using my Install-Win10RSATTools function https://github.com/kilasuit/PoshFunctions/blob/Dev/Scripts/Install-Win10RSATTools.ps1

@iainbrighton I spoke to Ravikanth at work and he already has a NAT VM switch implementation in his repo. He will be doing a PR soon to the xHyperV repo.
I will be going through that and see how we can fit those changes here.

@DexterPOSH Excellent! This is what I have run on my Win10 machine:
## Create NAT virtual switch
## This automatically adds the <IP_ADDRESS>/24 IP address to the virtual ethernet adapter
## Removing the virtual switch doesn't appear to clean this up particularly well :(
New-VMSwitch -Name NAT -SwitchType NAT -NATSubnetAddress <IP_ADDRESS>/24
## Add the NAT translation for machines on the <IP_ADDRESS>/24 subnet
New-NetNat -Name NAT -InternalIPInterfaceAddressPrefix <IP_ADDRESS>/24

I think we're going to need a NAT translation DSC resource. What repo this goes into, I haven't a clue at the moment! It may need a new 'xNAT' repo or put into the xNetworking repo?

@iainbrighton I see the code pushed upstream by Ravi.
https://github.com/rchaganti/DSCResources/tree/master/cHyper-V/DSCResources/cNatSwitch

@DexterPOSH I don't see any reference to a New-NetNat equivalent resource? I'm sure this will need working as well?

@iainbrighton, I do see New-NetNat being used in the Set-TargetResource definition in the psm1 file.

@DexterPOSH I'm not 100% convinced that that's the right place for it. What happens when I need an alternative NAT configuration?
IMHO the resource shouldn't be making any assumptions, but that's probably a conversation that needs to happen over at https://github.com/PowerShell/xHyper-V/issues/40


[Beta] backport version string fix

Beta backport of #9727 for 1.55.

:warning: Warning :warning:

Pull requests are usually filed against the master branch for this repo, but this one is against rust-1.55.0. Please double check that you specified the right target!

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 45a309e15dba8f999a7379bd0fa54c270923b26a has been approved by alexcrichton

:hourglass: Testing commit 45a309e15dba8f999a7379bd0fa54c270923b26a with merge 95cf038f06eb22ebbbb1ea922218724376470b0b...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing 95cf038f06eb22ebbbb1ea922218724376470b0b to rust-1.55.0...


added mine(ashis) and subham-rai github profile

Signed-off-by<EMAIL_ADDRESS>

fixed this issue sir @leecalcote


Run azd up occurs error in the progress

Describe the issue:
When running azd up, the following error occurs:

and the final result of running azd up shows no errors.

Repro Steps:

Run azd init -t Azure-Functions-OpenAI-Demo.
Run azd auth login.
Run set-executionpolicy remotesigned.
Run azd up.

Environment:

azd version 1.10.2 (commit 84ea22048b9a1c167bc4ae2095cc7f91798ef11e)
OS: Windows

Expected behavior:
Running azd up shows no errors during the process.
@hemarina and @BigMorty  for notification.

@eamonoreilly Please review this issue.

@jerryshia What version of .NET do you have installed? It seems you might not have .NET 8 and it is using .NET 6 and trying to update the app to support this but Flex consumption only supports .NET 8. You can run dotnet --version to check and get .NET 8 from https://dotnet.microsoft.com/en-us/download/dotnet/8.0 if needed. If that is not the issue, I may need ask for additional information. Thanks

@eamonoreilly We are using .NET 8. After investigation, we found that it was because of the version of Azure Functions Core Tools. Our previous version was 4.0.5455. After updating to the latest version 4.0.6543, this issue can no longer be reproduced, but we encountered another error as follows:


Add Hamiltonian Simulation

This models the time evolution of a quantum system using the Trotterization method on the local simulator.

This should be pretty much ready as a first draft.

This is just to show that the result converges with the actual result. If you want, I can tell the user that they can use less precision.

View entire conversation on ReviewNB


R: Autocompletion will double first word in R chunk in RMD

When Using vscode-R, autocompletion will double first word in R chunk in RMD file. For example, 'as.character' will be 'as.as.character' in R chunk in .Rmd file but work well in .R file. Authors from vscode-R extension think it is a vscode issue and symbol with . will cause this problem. In R, as.character is an independent function unlike python.

This really sounds like an issue of vscode-R. Why do its authors think otherwise?
Can you reproduce this independently of R?

The author think that . in R is obviously different from other language e.g. python. It causes that R-languageserver did not well deal with . . For example, as.tibble is a whole as a function other than 2 independent functions as and "tibble". R-LSP did not make error in as_tibble. Thanks.


CheckGPS is not defined

I have use plugin and install it but when app run find this error
CheckGPS is not defined

Sorry. I think something went wrong in your installation process. that's not an issue with this plugin. Have a look at https://github.com/lfreneda/cordova-plugin-fastrde-checkgps-sample for a working example.


Create a public image for (rust) keylime agent on quay.io/keylime

Currently, we already have up-to-date (daily built) images for the following components in https://quay.io/organization/keylime

REPOSITORY NAME
LAST MODIFIED
ACTIVITY

K keylimekeylime-ci
05/26/2023

K keylimekeylime_registrar
Yesterday at 4:56 AM

K keylimekeylime_verifier
Yesterday at 4:56 AM

K keylimekeylime_tenant
Yesterday at 4:57 AM

K keylimekeylime_base
Yesterday at 4:56 AM

We need to add a keylime_agent image there

Fixed (thanks @ansasaki and others)

REPOSITORY NAME
LAST MODIFIED
ACTIVITY

K keylimekeylime_verifier
Last Friday at 11:29 AM

K keylimekeylime_registrar
Last Friday at 11:29 AM

K keylimekeylime_agent
08/11/2023

K keylimekeylime-ci
05/26/2023

K keylimekeylime_tenant
Last Friday at 11:29 AM

K keylimekeylime_base
Last Friday at 11:29 AM


adadelta optimizer

an implementation of Adadelta http://arxiv.org/abs/1212.5701 that works with GPU

You have to rename file 'adadelta' to 'adadelta.lua'  and also add an include statement in init.lua. Also, can you merge the test pull request into this one rather than two different ones.

By the way, there is another pull request from @urikz (https://github.com/torch/optim/pull/54). Maybe it is best to decide which one to go with, but at this moment, both needs some minor changes.


Move topology to different handler / querier

@jpinsonneau I've tried to decouple the topology code versus standard flow query code. There's some duplication, but not so much. It should help me a lot when I'll have to rebase my refactoring PR with yours.
I haven't manually tested yet. Automated tests pass, but I'm not sure if you added new tests for topology.

Thanks for your suggestion ! LGTM


Jog slider should reflect max machine speed?

A bit tricky since we scale XY vs Z differently, but maybe scale it vs XY

Its now a percentage of max speed (0.1 to 100) presented in log scale


Allow running echogen test outside of makefile

Previously this depended on an env var set in the makefile to generate
the intended result of the golden file

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
1a2becaf86666c04f56650126fd47dfc33309150
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


nshlib/cmd_wait: Wait failed if FS_PROCFS not enabled

Summary
Wait failed if FS_PROCFS not enabled
Env
# sim:nsh
- CONFIG_FS_PROCFS=y

Error
nsh> sleep 5 &
sh [4:100]
nsh> wait 4
nsh: wait: wait failed: 2

cmd_wait()
snprintf(path, sizeof(path), "/proc/%d/status", tid);

Reported by @XuNeo and @Gary-Hobson, thank you;-)
Impact
nshlib/cmd_wait
Testing

Selftest: Using sim:nsh with CONFIG_FS_PROCFS disabled - PASSED
NuttX CI

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the NuttX requirements, although the provided information is minimal.
Here's a breakdown of why and what could be improved:
Strengths:

Clear Summary: The summary concisely explains the bug, the affected code, and the general mechanism of the fix (accessing a procfs entry that doesn't exist when procfs is disabled).
Impact is identified: The impact on nshlib/cmd_wait is noted.
Testing is described:  The testing methodology is explained, referencing both local testing and CI.

Weaknesses & Areas for Improvement:

Missing "Why" in Summary: While the bug is described, the PR doesn't explicitly state why this change is necessary.  Is wait expected to work without procfs?  Should it return a different error code?  This needs clarification.
How it works is vague: "accessing a procfs entry" isn't sufficient.  Did you add a check for CONFIG_FS_PROCFS?  Did you change the error handling?  The PR description should clearly explain the code changes.
Impact is incomplete:  While nshlib/cmd_wait is mentioned, the explicit YES/NO answers for each impact category are missing. This makes it harder to quickly assess the scope of the change.  For example:

Impact on user: YES (users relying on wait without procfs will see different behavior).  Describe the new behavior.
Impact on build:  Probably NO (unless you added build dependencies).
Impact on hardware: NO
Impact on documentation:  Potentially YES if the behavior of wait is now different and needs documenting.
Impact on security:  Likely NO.
Impact on compatibility: Potentially YES.  Explain if the change breaks any existing scripts or usage patterns.

Testing logs are missing: The template clearly requests "Testing logs before change" and "Testing logs after change". These are crucial for reviewers to understand the impact and verify the fix.  Include the actual output of the wait command both before and after your changes.
Build Host(s)/Target(s) incomplete:  Provide more details about your local testing environment.  "sim:nsh" is a start, but specify the architecture (e.g., sim:qemu-x86_64).

In short, while the core information is present, this PR description needs more detail and completeness to meet the NuttX standards fully.  Filling in the missing information will significantly improve the review process and the overall quality of the contribution.

Please remove CONFIG_NSH_DISABLE_WAIT from boards/arm/mps/mps3-an547/configs/ap/defconfig:
====================================================================================
Configuration/Tool: mps3-an547/ap,CONFIG_ARM_TOOLCHAIN_GNU_EABI
2024-11-13 13:37:27
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
  Normalize mps3-an547/ap
68d67
< # CONFIG_NSH_DISABLE_WAIT is not set
Saving the new configuration file
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   boards/arm/mps/mps3-an547/configs/ap/defconfig

Please remove CONFIG_NSH_DISABLE_WAIT from boards/arm/mps/mps3-an547/configs/ap/defconfig:
====================================================================================
Configuration/Tool: mps3-an547/ap,CONFIG_ARM_TOOLCHAIN_GNU_EABI
2024-11-13 13:37:27
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
  Normalize mps3-an547/ap
68d67
< # CONFIG_NSH_DISABLE_WAIT is not set
Saving the new configuration file
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   boards/arm/mps/mps3-an547/configs/ap/defconfig

Get, done, thank you, please review: https://github.com/apache/nuttx/pull/14776
And a simply check by execuating find boards/ -name defconfig | while read i; do if grep CONFIG_NSH_DISABLE_WAIT $i >&/dev/null; then if ! grep CONFIG_FS_PROCFS $i >&/dev/null; then echo $i; fi; fi; done

It seems that the CI not running with the latest apache/master even if it was triggered after https://github.com/apache/nuttx/pull/14776 was merged.
Local test OK
$ git checkout apache/master
Previous HEAD position was 6554ed4d668 get g_tcbinfo just use elf memory
HEAD is now at 85eed31443e mps3-an547:ap: Disable cmd_wait() as it depends on procfs currently
$ yes | ./tools/refresh.sh --defaults mps3-an547:ap
  Normalize mps3-an547:ap
$

try git push -f ... again.


filling is slower with numpy 1.15

It looks like histogram filling is about 10 times slower with numpy 1.15 than with 1.13

The histogram is simple 1-axis like this: Hist(bin("NJets", 20, 0, 20))

! I recently upgraded to numpy 1.5 too, and I get all sorts of mornings about binary incompatibilities. There's something going on with this release. There will be a performance at great when I replace some of the numpy calls with numexpr, but like everything that will have to wait until conferences are over.


Receive feedback on DPG Ask Form

Once the DPG Ask Form has been moved to a platform like form.io and a mechanism to extract details from the DPG-specific .json file has been determined, receive feedback from key stakeholders incl.:

[ ] Nathan B
[ ] GH contacts
[ ] 1-2 DPGs with whom we have a good relationship

Once feedback has been received, update the form to reflect the appropriate feedback

Amreen will transfer this ownership to Praj


[Adaptive] [LG] [DCR] ImportResolver delegate should not only return text, but also id

In current implementation of file reference feature between lg files. We can pass a delegate to help the engine to resolve imports.
But if the delegate only return text, there is no way the engine can detect duplication, like

[import](b.lg)
[import](./b.lg)
[import](b) // maybe

Because in the import discovery phase, the engine must use some kind of id\key to identify the resource been discovered. So the request here is: make sure delegate return id+text.
The idea can be summarized as "if you want to take over resource discovery process, you should also provide a global id to identity resource".

fixed by #2065