Plugin and/or Workflow deployment tasks fail if some system libraries are present in output directory

Plugin and/or Workflow deployment tasks fail in case there are NuGet packages libraries in the project output directory that are not in the _ignoredAssemblies list from SparkleXrm.Tasks.pluginRegistration.cs.

This could be due to a change in the way that we load assemblies now to look for the class attributes. Which version are you using and could you give an example of the assemblies and the error you are seeing, please?

We started experiencing this issue after the addition of several Microsoft NuGet packages to our Plugins project. The actual error happened during loading of Microsoft.Rest.ClientRuntime library which has already been added to exclusion list in spkl_dev brach. The error reads like this: 'Could not load file or assembly 'Microsoft.Rest.ClientRuntime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.' But this library is present in the output directory. Also we have other Microsoft libraries in output directory that are not present in the exclusion list so I think this calls for a more general solution.

Also please note that in order to connect to a Dynamics instance v <IP_ADDRESS>42 to test the fix I had to update all Microsoft.CrmSdk.* packages to the latest version otherwise I was unable to instantiate CrmServiceClient with the following message: Unable to connect to CRM: Method not found: 'System.String Microsoft.Xrm.Sdk.Organization.OrganizationDetail.get_EnvironmentId()'
I didn't include package updates in my PR because they are not directly related to the fix and it may be a version-specific issue.


Standardize extract and track data source

Summary
This PR does two things:

it adds rudimentary provenance tracking to data processed from the LAC TSV extracts. For each patient record supplied in one of these files (that we hit with our convertParquetMPI notebook), we create the meta field within the patient resource and store a completely hacky jank URI in its source property to track that this record originated in IRIS (Brady, if you've got any thoughts on what this URI should actually be to be correct, I'm all ears lol).
it performs standardization and preprocessing on records extracted from LAC TSVs. This is handled the same way record linkage is in the notebook: secrets get created in Azure KeyVaults via the supplied terraform, which allows the notebook to use the secret value to get the container app's URL to hit as an endpoint.

Fixes
#179  https://app.zenhub.com/workspaces/skylight-dibbs-viper-6480ba23b5a07644e0e46d23/issues/gh/cdcgov/phdi/681

DOB is now also standardized. Wasn't really sure what you meant about putting a test case in a comment, but what's there shows where meta gets put if you run that code on that bundle.

@BradySkylight I blatantly misunderstood what Dan meant with the test in the comment so he and I cleared that up lol. Here's the output of running the code on a sample input bundle, with the new meta property situated squarely on the patient resource:
{'resourceType': 'Bundle', 'type': 'batch', 'entry': [{'fullUrl': 'urn:uuid:123456789', 'resource': {'resourceType': 'Patient', 'id': 'a637-9d83-d59w-qlu9', 'name': {'given': ['John'], 'family': 'Shepard'}, 'birthdate': '11-07-1994'}, 'meta': {'source': 'uri:iris'}}]}

Close... here is the proper location (see below).  However, I'm still seeing some errors and trying to figure out what the cause is when I'm testing against our server.  I'll let you know if there are additional changes necessary.
{     "resourceType": "Bundle",     "type": "batch",     "entry": [         {             "fullUrl": "urn:uuid: 123456789",             "resource": {                 "resourceType": "Patient",                 "id": "a637-9d83-d59w-qlu9",                 "meta": {                     "source": "uri:iris"                 },                 "name": {                     "given": [                         "John"                     ],                     "family": "Shepard"                 },                 "birthdate": "11-07-1994"             }         }     ] }


Unable to Debug Connect-PartnerCenter cmdlet

Am trying to debug the error which i receive for the below command using -debug flag. However there is no debug response and i get the same error response. This make is extremely difficult - impossible to get to the issue.
Connect-PartnerCenter -ApplicationId 0b292c96-5d35-45cc-966c- -Credential $credential -debug
Thanks,
Pradebban Raja

Am surprised how can this issue be closed, is the debug flag giving out intended results? Which release, where is the commit details? Please help me understand why this bug is closed?
Get Outlook for Androidhttps://aka.ms/ghei36

From: Isaiah Williams<EMAIL_ADDRESS>Sent: Saturday, February 2, 2019 10:23:33 AM
To: Microsoft/Partner-Center-PowerShell
Cc: Pradebban Raja; Mention
Subject: Re: [Microsoft/Partner-Center-PowerShell] Unable to Debug Connect-PartnerCenter cmdlet (#59)
Closed #59https://github.com/Microsoft/Partner-Center-PowerShell/issues/59.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/Partner-Center-PowerShell/issues/59#event-2113879603, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMcxBh8JPtqpIlVz2jFMwQ3w3mFPLuHkks5vJa11gaJpZM4aW040.

Hi @rajaprad,
My apologizes about this, but I would like to share that with the update that was released today debug statements are now included specifically for the Connect-PartnerCenter command. Overtime you will see us additional debug statements to help troubleshoot any issue that you might encounter. I would like to encourage you to update to the latest version and try your operation again.

Thats awesome, i would give it  try! Thanks

From: Isaiah Williams<EMAIL_ADDRESS>Sent: Tuesday, February 5, 2019 12:56 AM
To: Microsoft/Partner-Center-PowerShell
Cc: Pradebban Raja; Mention
Subject: Re: [Microsoft/Partner-Center-PowerShell] Unable to Debug Connect-PartnerCenter cmdlet (#59)
Hi @rajapradhttps://github.com/rajaprad,
My apologizes about this, but I would like to share that with the update that was released today debug statements are now included specifically for the Connect-PartnerCenter command. Overtime you will see us additional debug statements to help troubleshoot any issue that you might encounter. I would like to encourage you to update to the latest version and try your operation again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/Partner-Center-PowerShell/issues/59#issuecomment-460522491, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMcxBpKTlle6c5sLdWIub2jHvOkh2QYOks5vKRzxgaJpZM4aW040.


Use EF Core compiled models

https://devblogs.microsoft.com/dotnet/announcing-entity-framework-core-6-0-preview-5-compiled-models/#background

Done


Using [asar-plus] can still extract app.asar

I have updated your<EMAIL_ADDRESS>Test using commands: asar-plus e -iff -iu app.asar ./app/
You can still extract the app.asar to ./app, is there any way to prevent asar-plus
https://github.com/evlon/asar-plus

Have you enabled encryption? Starting from v3 we will focus more on that, other protection methods are no longer as effective as they used to be.

Yes, i use the following code
const asarmor = require('asarmor');
const { join } = require("path");
exports.default = async ({ appOutDir, packager }) => {
try {
const asarPath = join(packager.getResourcesDir(appOutDir), 'app.asar');
console.log(asarmor applying patches to ${asarPath});
const archive = await asarmor.open(asarPath);
archive.patch(); // apply default patches
await archive.write(asarPath);
} catch (err) {
console.error(err);
}
};
And I have enabled encryption, using normal unpacking methods will result in multiple 1GB sized files, but using asar-plus will directly result in normal files

You're still missing something in your code. Please see https://github.com/sleeyax/asarmor/blob/f9a2c148312df481de47ef0a6b62e527aa1ddd8e/example/node/build.js#L11 and https://github.com/sleeyax/asarmor/blob/f9a2c148312df481de47ef0a6b62e527aa1ddd8e/example/electron/afterPack.js#L13 as examples.
It seems like asar-plus was specifically designed to combat asarmor's base protections so encryption is the only thing that can protect your asar file contents from it.

Sorry, I didn't read the document carefully, but I am using vue-cli-plugin-electron-builder, which is different from the structure in the document. How should I configure beforePack.js and where should I copy main.node to?

I have enabled encryption now, and all the JavaScript files packaged into the app.asar have been encrypted by AES, but I don't know how to automatically decrypt them at runtime

Sorry, I didn't read the document carefully, but I am using vue-cli-plugin-electron-builder, which is different from the structure in the document. How should I configure beforePack.js and where should I copy main.node to?

I can only provide support for electron builder for now, it's impossible to support all plugins / build tools. If this plugin is based on electron builder, you should be able to follow the guide along in a similar manner while also checking the documentation.


[SharpDX.Direct3D11] Added DirectX11.3 support

Hello, since I noticed it was missing, I added mappings for directx11.3.
I tried to reuse the existing regular expressions instead of adding new ones, and naming should be consistent with other features.
Thanks

Thanks! This is merged.


fix: do not pick up duplicates

Currently, it is possible to get errors (for example for unique scenario names) by passing something like: gherkin-lint src src/x.feature - x.feature would be picked up twice and then error.
This PR fixes this.
cc @brendanAnnable

Not to self:
/home/travis/build/vsiakka/gherkin-lint/test/feature-finder/test.js
   1:5   error  'path' is defined but never used    no-unused-vars
   3:5   error  'expect' is defined but never used  no-unused-vars
  10:28  error  Unexpected trailing comma           comma-dangle

Node 0.12 failed with:
/home/travis/build/vsiakka/gherkin-lint/src/feature-finder.js:33
      throw new Error(`Invalid format of the feature file path/pattern: "${pat
                      ^
SyntaxError: Unexpected token ILLEGAL

@vsiakka ?

I think it's fine to remove 0.12, I'll do that now.

I removed node 0.12. This looks good after you fix the lint errors.

Lint errors should have been fixed? Node 0.12 was the last blocker.

See https://travis-ci.org/vsiakka/gherkin-lint/builds/274065792?utm_source=github_status&utm_medium=notification

Ok I didn't realise, I will merge then.

published with v2.5.1

Thanks you!
On 14 Sep. 2017 19:52, "vsiakka"<EMAIL_ADDRESS>wrote:

published with v2.5.1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vsiakka/gherkin-lint/pull/83#issuecomment-329433072,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALehlPR8w8eu-UexiO-j_C55sodpzAIks5siPdpgaJpZM4PSn76
.


enhance 'ssl_version' to be able to set max version as well

just using 'ssl_version' is not enough in some cases, e.g. setting it to tlsv1.2 only means the min version, if we want to limit the max version, we have to provide such interface. I check the curl code that it's simply using the higher 16 bits to store the max version and lower 16 bits to store the min version, hence the "<<" shift operator.
Also fix a small typo in the comment.

Perhaps there is a backwards-compatible way to add this functionality instead? Maybe a separate ssl_version_range method?

Good suggestion, but ideally the interface exposed should be minimal.

do you think ssl_min_max_version is better than ssl_version_range()? @sagebind

do you mind bumping up a version for this small feature?

oh. i have another PR to add the copy and clone for sslversion. after that, I'm okay for bumping the version.


Update key-vault-setup.md

Corrected Azure Cli command for enabling for deployment.
Issue raised under #31263

@lgulliver : Thanks for your contribution! The author, @singhkays, has been notified to review your proposed change.

#sign-off

@shashishailaj: I'm sorry - only the author of this article, @singhkays, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Looks good from me (content owner). #sign-off

@rloutlaw: I'm sorry - only the author of this article, @singhkays, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@shashishailaj: I'm sorry - only the author of this article, @singhkays, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


[NuGetInstallerV0 NuGetToolInstallerV0 NuGetToolInstallerV1] Added telemetry tracking

Task name: NuGetInstallerV0, NuGetToolInstallerV0, NuGetToolInstallerV1
Description: added telemetry tracking
Documentation changes required: (Y/N) no
Added unit tests: (Y/N) no
internal workitem: #1406
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

Tested changes - LGTM, thanks!


Remove one TODO

it's fixed https://github.com/flutter/flutter/issues/8986 is resolved.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I signed the CLA.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

I'm the wrong person to review this, but since the TODO was added by @goderbauer, maybe they are the right person?
BTW you have a test failing because some of the gradle files have trailing spaces.

Tests are passing now


RTCP reception mechanism

I've added a channel to the RTCTrack object that will receive incoming RTCP messages related to an outgoing RTP track. I've also worked on the RTCP parsing infrastructure.
There's also a small commit that makes the Readme.md links work (for the license)

Pull Request Test Coverage Report for Build 1147

11 of 179 (6.15%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 24.892%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/rtcp/picture_loss_indication.go
0
1
0.0%

pkg/rtcp/receiver_report.go
0
1
0.0%

pkg/rtcp/header.go
0
2
0.0%

internal/network/manager.go
7
19
36.84%

rtcpeerconnection.go
4
16
25.0%

pkg/rtcp/rapid_resynchronization_request.go
0
36
0.0%

internal/network/port-receive.go
0
42
0.0%

pkg/rtcp/packet.go
0
62
0.0%

Totals

Change from base Build 1140:
-0.4%

Covered Lines:
1735

Relevant Lines:
6970

💛  - Coveralls

Thanks for cleaning up those linter warnings. Looks great! I'll start reviewing your changes now.
Also, it looks like coveralls is complaining about the test coverage. Could you write a few tests to keep the coverage up? You can follow the pattern in receiver_report_test.go.

Will do, I'll have another patch ready in a day or too
On Tue, Nov 27, 2018, 14:30 Max Hawkins<EMAIL_ADDRESS>wrote:

Thanks for cleaning up those linter warnings. Looks great! I'll start
reviewing your changes now.
Also, it looks like coveralls is complaining about the test coverage.
Could you write a few tests to keep the coverage up? You can follow the
pattern in receiver_report_test.go.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pions/webrtc/pull/242#issuecomment-442186510, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACEaez2Hx5wWtdFU3qUUtjkHi4e1w21oks5uzZLPgaJpZM4YzbiO
.

This all looks great. I'm going to go ahead and approve.
Please address those two comments and then feel free to merge.
Thanks again for your contribution!

the "update branch" button is greyed out for me (i don't have write access...) would you mind pulling these changes in?


feat: ios preprocessing page (url metadata)

Summary
on iOS we can use a JavaScript file to preprocess the webpage before the share extension is called (cf Accessing a Webpage). This is useful if we want to extract data directlty from the webpage and avoid to scrap the url in a second time.

Custom configuration example
    "plugins": [
      [
        "expo-share-intent",
        {
          "iosActivationRules": {
            "NSExtensionActivationSupportsWebURLWithMaxCount": 1,
            "NSExtensionActivationSupportsWebPageWithMaxCount": 1,
          },
          "preprocessorInjectJS": "metas['og\\:image'] = metas['og\\:image'] || document.querySelector('img#main-image')?.getAttribute('src')"
        }
      ],

Todo

[x] Add generic preprocessing script
[x] Auto extra all page header metadata (open graph) in share extension
[x] send all metadata to application
[x] add plugin configuration to add a custom rule to extract content
[x] Update README.md

Issue
Fixes https://github.com/achorein/expo-share-intent/issues/142

This would be an awesome feature to test!

@ansh now available ;)

You're an absolute legend.
Thank you!


fix: sonar minors #5

Description

Minor fixes for Sonar
nanoid is deprecated in the "ai" package
When destructuring a useState, the getter and setter should use a consistent naming convention

:tada: This PR is included in version 1.17.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Local chunk error when listing/reading files after restarting Docker Desktop

What happened?:
When attempting to read data from Pachyderm after quitting and opening Docker Desktop, I get a chunk error. This occurs with listing files in a repo and getting files from a repo:
❯ pachctl list repo
NAME  CREATED    SIZE (MASTER) DESCRIPTION
repo2 2 days ago ≤ 0B
repo1 3 days ago ≤ 10.09KiB
❯ pachctl list file repo2@dev
local://.pach/ does not contain item: (chunk/2731330a0cc4b75b8ff71d8e4b484e3665e6a80663b5faa61883b5499f24b549.000000000000000f)
❯ pachctl get file repo2@dev:/file4
couldn't download /file4 from repo2@dev=: local://.pach/ does not contain item: (chunk/2731330a0cc4b75b8ff71d8e4b484e3665e6a80663b5faa61883b5499f24b549.000000000000000f)

What you expected to happen?:
To successfully read data from Pachyderm.
How to reproduce it (as minimally and precisely as possible)?:
Create a repo and add files to it. Quit Docker Desktop. Open Docker Desktop. Attempt to list or read a file from the repo.
Anything else we need to know?:
Environment?:

Kubernetes version (use kubectl version): 1.24.2
Pachyderm CLI and pachd server version (use pachctl version): 2.2.7
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s): Local (Docker Desktop)
If you deployed with helm, the values you used (helm get values pachyderm): default values + local install
OS (e.g. from /etc/os-release): macOS 12.5
Others: Docker Desktop 4.11.1, Docker Engine 20.10.17

Brody and I discussed this a little bit. With deployTarget=LOCAL, we use a hostPath for chunks rather than anything that pretends to be persistent, and yeah, your chunk storage is going away.  I'd deploy Minio and use that if you want something that works right now.  I think we'll change the chart to provision a PV for local cases.  (There might be some history behind this where some tests could run on your workstation when the k8s pachd's files were shared with it, but CI isn't using that; it deploys minio and eschews pachd.storage=LOCAL.)
A template of values that I personally recommend are here: https://github.com/pachyderm/jonathan-install-scripts/blob/main/values.yaml  and the minio manifest that CI uses is here: https://github.com/pachyderm/pachyderm/blob/master/etc/testing/minio.yaml


Failing to build for android

Hey there, Every time I go to build for an android device I recieve a clang error linker command failed
[i] Target: android
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/fyne-cross/bin/android
[✓] "dist" dir cleaned: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/fyne-cross/dist/android
[✓] "temp" dir cleaned: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/fyne-cross/tmp/android
[i] Checking for go.mod: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/go.mod
[✓] go.mod found
[i] Packaging app...
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/create: dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
[✗] could not package the Fyne app: could not package the Fyne app: exit status 126
┌─[gianni@pop-os] - [~/Desktop/GoCode/LearnJapanese/GUIs] - [Fri Dec 18, 16:17]
└─[$] <> usermod -aG docker gianni
usermod: Permission denied.
usermod: cannot lock /etc/passwd; try again later.
┌─[gianni@pop-os] - [~/Desktop/GoCode/LearnJapanese/GUIs] - [Fri Dec 18, 16:17]
└─[$] <> sudo usermod -aG docker gianni
┌─[gianni@pop-os] - [~/Desktop/GoCode/LearnJapanese/GUIs] - [Fri Dec 18, 16:17]
└─[$] <> newgrp docker
┌─[gianni@pop-os] - [~/Desktop/GoCode/LearnJapanese/GUIs] - [Fri Dec 18, 16:17]
└─[$] <> fyne-cross android
[i] Target: android
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/fyne-cross/bin/android
[✓] "dist" dir cleaned: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/fyne-cross/dist/android
[✓] "temp" dir cleaned: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/fyne-cross/tmp/android
[i] Checking for go.mod: /home/gianni/Desktop/GoCode/LearnJapanese/GUIs/go.mod
[✓] go.mod found
[i] Packaging app...
go build -buildmode=c-shared -o /tmp/gomobile-work-932417829/lib/armeabi-v7a/libGUIs.so GUIs failed: exit status 2
# fyne.io/fyne/internal/driver/gomobile
android.c:50:9: warning: returning 'const char *' from a function with result type 'char *' discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
android.c:67:48: warning: incompatible integer to pointer conversion passing 'uintptr_t' (aka 'unsigned int') to parameter of type 'jobject' (aka 'void *') [-Wint-conversion]
android.c:71:55: warning: incompatible integer to pointer conversion passing 'uintptr_t' (aka 'unsigned int') to parameter of type 'jobject' (aka 'void *') [-Wint-conversion]
android.c:122:48: warning: incompatible integer to pointer conversion passing 'uintptr_t' (aka 'unsigned int') to parameter of type 'jobject' (aka 'void *') [-Wint-conversion]
android.c:125:48: warning: incompatible integer to pointer conversion passing 'uintptr_t' (aka 'unsigned int') to parameter of type 'jobject' (aka 'void *') [-Wint-conversion]
android.c:161:50: warning: passing 'char *' to parameter of type 'jbyte *' (aka 'signed char *') converts between pointers to integer types with different sign [-Wpointer-sign]
# fyne.io/fyne/app
app_mobile_and.c:46:48: warning: incompatible integer to pointer conversion passing 'uintptr_t' (aka 'unsigned int') to parameter of type 'jobject' (aka 'void *') [-Wint-conversion]
app_mobile_and.c:49:48: warning: incompatible integer to pointer conversion passing 'uintptr_t' (aka 'unsigned int') to parameter of type 'jobject' (aka 'void *') [-Wint-conversion]
app_mobile_and.c:72:33: warning: incompatible pointer to integer conversion passing 'JNIEnv *' (aka 'const struct JNINativeInterface **') to parameter of type 'uintptr_t' (aka 'unsigned int') [-Wint-conversion]
app_mobile_and.c:42:36: note: passing argument to parameter 'jni_env' here
# GUIs
/usr/local/go/pkg/tool/linux_amd64/link: running /usr/local/android_sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/armv7a-linux-androideabi16-clang failed: exit status 1
/usr/local/android_sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: /tmp/go-link-633107991/000000.o:1:2: invalid character
/usr/local/android_sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: /tmp/go-link-633107991/000000.o:1:2: syntax error, unexpected $end
/usr/local/android_sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: /tmp/go-link-633107991/000000.o: not an object or archive
clang: error: linker command failed with exit code 1 (use -v to see invocation)

[✗] could not package the Fyne app: could not package the Fyne app: exit status 1

@GhettoGhandi looks like there are some permission issues with docker.

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/create: dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.

Could you please check your docker setup or try run the command using sudo?

I had a similar problem on Xubuntu 20.04. Adding the user to the group "docker" solved this for me:
$  sudo groupadd docker
$ sudo usermod -aG docker

I had a similar problem on Xubuntu 20.04. Adding the user to the group "docker" solved this for me:
$  sudo groupadd docker
$ sudo usermod -aG docker

@GhettoGhandi did you had any chance to test as per comment above or docker docs? It should fix your issue too.
Going to close the issue, but please feel free to re-open if any issue arise.


proposal: spec: automatically instantiate generic field types that are already concrete types

Currently, when you have a generic field in a struct that has a generic, but already concrete, type, to instantiate that struct you need to explicitly tell the compiler the type.
Example:
type Foo struct {
	Field Field[int]
}

type Field[T any] struct {
	Val T
}

func Bar() Foo {
	return Foo{
		Field: Field[int]{
			Val: 10,
		},
	}
}

I find Field: Field[int]{... to be redudant, because that Field can not be of any type but an int.
I propose that this would become possible:
type Foo struct {
	Field Field[int]
}

type Field[T any] struct {
	Val T
}

func Bar() Foo {
	return Foo{
		Field: Field{
			Val: 10,
		},
	}
}

Currently, this error out as cannot use generic type Field[T any] without instantiation.

Duplicate of #50285


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: c952c930b68f0d064ceb26ca3b82b3c9aa3692e0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Simple link error in Navigation tutorial

The navigation tutorial at https://openui5beta.hana.ondemand.com/#docs/guide/1b6dcd39a6a74f528b27ddb22f15af0d.html contains an invalid link in the highlighted "Tip" section.
Currently it has: https://openui5beta.hana.ondemand.com/explored.html#/entity/sap.m.tutorial.navigation/samples
But it should be: https://openui5beta.hana.ondemand.com/explored.html#/entity/sap.ui.core.tutorial.navigation/samples
I can't see a way to send a pull request for this - you don't seem to have the doco on github.

Hello js1972,
thanks, that one slipped through our fingers. I Contacted our documentation colleagues, it will be fixed with the next release of OpenUI5.
Kind Regards,
Michael

Hi js1972,
thanks for pointing this out!
We already corrected this issue in the docu source files. Unfortunately it always takes some time until we can update the published versions....
Cheers,
Johanne


UnionRevisionLabelPodDeployer

This PR implements UnionRevisionLabelPodDeployer that returns a unified state from multiple distinct deployers. That is: none has reported an error, all have converged, all have observed exactly the same encryption configuration.
Visit https://github.com/openshift/enhancements/blob/master/enhancements/etcd/etcd-encryption-for-separate-oauth-apis.md for more details.

/assign @sttts

/lgtm
one nit.

/approve


Replace deprecated metrics

What was changed

Following the Server change to deprecate the per-command-metrics (see https://github.com/temporalio/temporal/pull/4995), this replaces those and uses the new command metric instead.
Why?

Don't use deprecated metrics anymore.
Checklist

Closes

How was this tested:

Any docs updates needed?


how to install torch>=1.10.0.dev

when I run this command
pip install --user "git+https://github.com/facebookresearch/functorch.git"
ERROR: Could not find a version that satisfies the requirement torch>=1.10.0.dev

Instructions available at our README: https://github.com/facebookresearch/functorch#binaries

Instructions available at our README: https://github.com/facebookresearch/functorch#binaries
When I run the command， only install torch 1.9.0

For CUDA 10.2
pip install --pre torch -f https://download.pytorch.org/whl/nightly/cu102/torch_nightly.html
For CUDA 11.1
pip install --pre torch -f https://download.pytorch.org/whl/nightly/cu111/torch_nightly.html
For CPU-only build
pip install --pre torch -f https://download.pytorch.org/whl/nightly/cpu/torch_nightly.html
Then pip install --user "git+https://github.com/facebookresearch/functorch.git"
ERROR: Could not find a version that satisfies the requirement torch>=1.10.0.dev (from functorch) (from versions: 0.1.2, 0.1.2.post1, 0.1.2.post2, 0.4.1, 0.4.1.post2, 1.0.0, 1.0.1, 1.0.1.post2, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.7.1, 1.8.0, 1.8.1, 1.9.0)
ERROR: No matching distribution found for torch>=1.10.0.dev

Can you try running pip uninstall torch until there is no PyTorch installed and then run one of the following commands, depending on which CUDA version you have installed?
# For CUDA 10.2
pip install --pre torch -f https://download.pytorch.org/whl/nightly/cu102/torch_nightly.html
# For CUDA 11.1
pip install --pre torch -f https://download.pytorch.org/whl/nightly/cu111/torch_nightly.html
# For CPU-only build
pip install --pre torch -f https://download.pytorch.org/whl/nightly/cpu/torch_nightly.html

Hello!
I would like to know what is the oldest version of pytorch you can support. I'm facing a dilemma that the torch_nightly now is >= 1.10 while another package I'm using (pytorch geometric) only supports up to 1.9.0.
Thanks!

@kfxw As of now, we only officially support PyTorch nightly. With the 1.10 release, we'll cut a release version.
If you urgently need functorch though, I can find a commit that works with 1.9 :)

@Chillee
Thanks for your reply! I'll try to compile my dependencies with the pytorch-nightly first and see if it works. If not, I'll come back to look for your help.

@kfxw As of now, we only officially support PyTorch nightly. With the 1.10 release, we'll cut a release version.
If you urgently need functorch though, I can find a commit that works with 1.9 :)

Hi all,
Thanks for the amazing work! Is stable Pytorch support on the roadmap? Or will the package remain on nightly for now? Thanks a lot!
Matteo

Hi all, Thanks for the amazing work! Is stable Pytorch support on the roadmap? Or will the package remain on nightly for now? Thanks a lot!

It's on the roadmap. We're planning a beta release of functorch for sometime in H1 2022, but we'll soon have a "preview" branch of functorch that works with PyTorch 1.10.

Hi all, Thanks for the amazing work! Is stable Pytorch support on the roadmap? Or will the package remain on nightly for now? Thanks a lot!

It's on the roadmap. We're planning a beta release of functorch for sometime in H1 2022, but we'll soon have a "preview" branch of functorch that works with PyTorch 1.10.

Thanks a lot for your reply!


Add 0xPlasma Finance DeFi dapp

The app doesn't connect to the safe for me

Hey! The app now appears in the list, great to have you.
A small tip from my side: remove caching from index.html. The fix didn't work for me initially but worked for my colleagues; it appears to be because I had the previous version of the app cached, and I see there are some caching headers when you request index.html on https://apy.plasma.finance


Check Policies for ListUsers and ViewUsers methods

Currently any authorized token can fetch Users information. Add policies to ListUsers and ViewUsers methods to avoid unauthorized actions.
This issue is a reminder that should be fixed here: https://github.com/mainflux/mainflux/issues/1248

Why a separate issue, and not just the comment over there? Closing this one.


Fix/ghg feedback tasks

Default to ALL GHG when gases dropdown is cleared
Fix metadata info button (Show UNFCCC metadata for both UNFCCC options)

Note: The subscript not showing in gases is a conflict with React Truncate component but I didn't have time to solve it. Maybe we could find an alternative but it has to have 'truncation' of several lines

It's looking good! =)
If anyone else is going to test it, make sure you re-import your data for historical emissions:
rails historical_emissions:import (it takes a bit of time).
One thing I've noticed and not sure is registered in the Open Stories: we need to reset the sectors selection when changing sources, as the sectors are different per source.

Hmm, it seems I found something weird, there's an extra item in the tooltip that doesn't appear in the legend:

☝ taking care of that one


[QUESTION] Moving mesh during physics simulation

Thanks for great work !
I want to simulate a cloth for a moving object, exactly like this question.
https://github.com/NVIDIA/warp/issues/160
But I couldn't find updated + refit() in the link below:
https://github.com/NVIDIA/warp/blob/main/warp/sim/model.py#L256
But, I found simillar functions during search "refit":
https://github.com/NVIDIA/warp/blob/bfbd0258479ea1378788c2ff5bdbbdc1da385612/warp/types.py#L2997-L3004
https://github.com/NVIDIA/warp/blob/bfbd0258479ea1378788c2ff5bdbbdc1da385612/warp/examples/core/example_mesh.py#L116-L129
Has the function to update mesh been moved?
Also, if I combine this properly with the example below, can I get it to work as I intended?
https://github.com/NVIDIA/warp/blob/main/warp/examples/sim/example_cloth.py

Now I can deform the mesh using wp.launch. It's working well !!
@wp.kernel
def deform(positions: wp.array(dtype=wp.vec3), new_positions: wp.array(dtype=wp.vec3)):
    tid = wp.tid()
    positions[tid] = new_positions[tid]

wp.launch(kernel=deform, dim=len(self.mesh.points), inputs=[self.mesh.points, self.animations[self.time_step]])

But it doesn't seem to work with wp.sim.ModelBuilder(). I similarly used code to deform the mesh, but the mesh did not move.
    def simulate(self):
        wp.sim.collide(self.model, self.state_0)

        # self.model.shape_geo_src[0].vertices -> np.array
        # self.model.shape_geo_src[0].mesh.points -> <warp.types.array object at 0x7febf3d0ddb0>
        # self.animations[self.time_step] -> <warp.types.array object at 0x7febf3d0ddb0>
        wp.launch(
            kernel=deform,
            dim=len(self.mesh.mesh.points),
            inputs=[self.model.shape_geo_src[0].mesh.points, self.animations[self.time_step]]
        )

        for _ in range(self.sim_substeps):
            self.state_0.clear_forces()

            self.integrator.simulate(self.model, self.state_0, self.state_1, self.sim_dt)

            # swap states
            (self.state_0, self.state_1) = (self.state_1, self.state_0)

https://github.com/NVIDIA/warp/blob/7de917925ad67168497bcc7024e5f3b40ec84e56/warp/examples/sim/example_cloth.py#L130-L139
How can I deform mesh in wp.sim.ModelBuilder() ?
Should I add the mesh any other way than builder.add_shape_mesh ?

Same problem. I do not know how to add the deform function into the simulate function.

Hi @SangHunHan92 and @biansy000,
wp.sim.ModelBuilder() is there to help setting up a simulation model. Once it's done, all the data is stored as Warp arrays in wp.sim.Model and wp.sim.State, so that's what you'd need to look at if you wanted to update anything while stepping through the simulation.
For example, to deform the mesh from the cloth example, you could run a kernel that'd modify self.state_0.particle_q before or after calling self.simulate().
The example warp/examples/sim/example_soft_body.py is actually doing something along these lines when launching the kernel twist_points.


Update README.md

I want to update documents one by one.
Signed-off-by: Masayuki Ishii<EMAIL_ADDRESS>

There is no uniformity in whether the word "meows" is enclosed in backquotes or not, but this is a minor detail.
Other than that, nothing much to say.

@kmdkuk
I'm enclosing the first meows to emphasize because it is the first definition of the software name.
I don't think I need to emphasize the other parts.


[Task]: Switch gitSyncId generation logic from ObjectId to Java UUID

Opt for a dependency on core Java utility rather than a Mongo specific hex generator.

Completed already by Shri in the PG tasks


Skip statements with Sid beginning NOREPO

repokid will now ignore statements with an Sid beginning with NOREPO.
repokid will also no longer expand wildcards on statements that don't have any repoable permissions.
roledata.py::_get_repoed_policy() will no longer try to repo statements with Sid's beginning with NOREPO.
roledata.py::_get_permissions_in_policy() now has two return values:

total_permissions
eligible_permissions <-- This is a subset of total, but excludes permissions in statements with the NOREPO Sid.

New tests should cover the logic pretty well.
Bumping version of policyuniverse

Coverage increased (+1.1%) to 59.239% when pulling 40c2abc3256d6315f08720bf1bd00971d68b87a1 on skip_norepo_sids into c1311a8dcf7a72b460ad520718b2d82f6e3fb0bd on master.

I've put this branch through it's paces in our test environment and everything worked great.

Approved


Dependency missing?

On a clean env, when doing
(cd beakerx; pip install -e . --verbose)
im seeing
mkl-random 1.0.1 requires cython, which is not installed.
mkl-fft 1.0.0 requires cython, which is not installed.

Did you install py4j see the readme.
On Thu, May 24, 2018, 3:26 AM Łukasz Pior<EMAIL_ADDRESS>wrote:

On a clean env, when doing
(cd beakerx; pip install -e . --verbose)
im seeing
mkl-random 1.0.1 requires cython, which is not installed.
mkl-fft 1.0.0 requires cython, which is not installed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twosigma/beakerx/issues/7421, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6yFaPGdjhr9ASkUmtvKRI9f12wWTtXks5t1mC9gaJpZM4ULs3B
.

yes I did
I did everything step by step as described in README, after removing all envs
It may be something new due to new version of ubuntu (Ubuntu 18.04 LTS)

i think we can ignore it
https://github.com/AnacondaRecipes/aggregate/issues/53


Newer versions of protoc don't regenerate proto descriptor

As part of the proto codegen process, we use protoc via tools/proto-compiler. Our dev docs currently say:

After installing, run protoc --version and confirm you’re running at least 3.21.8 (or newer). Don’t install protoc from package managers such as apt, as those versions are often outdated, and will not work with Penumbra.

Current version of protoc is v23.3. If that sounds astonishingly newer than v3.21, you are correct. Looks like the project jumped from v3 to v20 last year:
❯ curl -s https://api.github.com/repos/protocolbuffers/protobuf/releases | jq '.[] | .tag_name + " " + .published_at' -r
v23.3 2023-06-14T19:22:45Z
v23.2 2023-05-26T16:43:43Z
v23.1 2023-05-17T17:28:25Z
v22.5 2023-05-10T03:56:57Z
v23.0 2023-05-08T18:31:51Z
v23.0-rc3 2023-05-05T17:20:25Z
v22.4 2023-05-04T20:35:56Z
v23.0-rc2 2023-04-28T18:59:14Z
v23.0-rc1 2023-04-26T23:16:56Z
v22.3 2023-04-12T23:47:13Z
v22.2 2023-03-10T18:35:01Z
v22.1 2023-03-07T22:31:27Z
v22.0 2023-02-16T18:17:29Z
v22.0-rc3 2023-02-10T20:17:58Z
v22.0-rc2 2023-02-02T21:18:01Z
v22.0-rc1 2023-01-31T18:24:35Z
v21.12 2022-12-14T14:45:50Z
v21.11 2022-12-08T06:34:59Z
v21.10 2022-11-30T19:15:02Z
v21.9 2022-10-26T20:28:55Z
v21.8 2022-10-18T18:18:56Z
v21.7 2022-09-29T22:22:53Z
v3.20.3 2022-09-29T21:22:59Z
v3.19.6 2022-09-29T20:46:59Z
v3.16.3 2022-09-29T22:17:28Z
v21.6 2022-09-14T21:37:03Z
v3.20.2 2022-09-14T18:05:45Z
v3.19.5 2022-09-14T21:36:20Z
v3.18.3 2022-09-14T21:02:42Z
v21.5 2022-08-09T19:53:44Z

Some more info here https://protobuf.dev/support/version-support/ . For our purposes, we need to document an explicit version for protoc, and check for that in the proto compiler tool, otherwise we get very strange and hard to debug errors.
For our docs, we're linking to https://grpc.io/docs/protoc-installation/#install-pre-compiled-binaries-any-os , which appears badly out of date, given that it still recommends v3.15.8 in its example. Better would be to link out to https://protobuf.dev/downloads/ .

Ah, this isn't so bad: the problem isn't that the descriptor file isn't been regenerated, it's just that different major versions of protoc emit slightly different binary blobs. I'll update the tooling and docs to use the current latest version (23.3) and add a reminder message to the proto-compiler tool.

I think the problem isn't just about different major versions, but that the descriptor output isn't stable even within the same version. In a previous iteration of the CI tooling we ignored changes that only affected the descriptor, with the assumption that if there were "real" changes, they'd be caught by changes to the generated files (and that any generation would update the descriptor).

that the descriptor output isn't stable even within the same version

The descriptor output is stable within the same version! That's the point of the changes in #2739: if the same version is used, then we can expect the output to be fully deterministic.

In a previous iteration of the CI tooling we ignored changes that only affected the descriptor

My current understanding is that we did this because we couldn't explain why we were seeing flapping: now I'm certain it's because different version of protoc were used locally and in CI. We can still ignore the flapping on that particular file, of course, but if we're using different tooling versions then we're likely going to experience flapping elsewhere in the generated artifacts, e.g. https://github.com/penumbra-zone/penumbra/pull/2739/files#diff-4c7f8084527df765ac0133b6828891e9b82fb03557bacf323960235942b56c3aR3 So my preference would be to ride out this latest set of changes, but very open to different opinions!

After some discussion in Discord, we decided that it's fine to let the protos flap a bit, if it prevents us from requiring specific versions of tooling locally. To reduce developer friction, we'll disable the persnickety CI check that ensures the codegen is byte-for-byte identical, and lean on visual review to ensure the protos have been updated accordingly.


How to look up entity by other key

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[x] Support request
[ ] Other... Please describe:

Question
I have an entity which has a database id which is the idKey i use for the store.
This makes it easy to get an entity by calling getEntity(id)
But I also have a orderId which I would like to be able to quickly look up entities by.
I can look up the entity by looping through all the whole store but that seems very bad performance wise.
I thought about adding a orderIds: Map<OrderId, EntityId> to the root of the store and use that to look up the id.
But I'm not sure how to best keep that map updated.
How would you solve this?

Can you show what you're trying to do, please?

Store can only have one idKey, but you can use store middleware functions to keep your map updated.


sys to util

Upon running $ node cli.js I was notified that util has replaced sys. This commit changes all references of sys = require('sys') to util = require('util') and any usage of sys. to util.

Thanks!


DllReferencePlugin should modifyHash when manifest.json file contents changed

opts.manifest as a filepath, and manifest.json contents changed, but [hash] has no change

My solution:
      const manifest = this.options.manifest;
      if (typeof manifest === 'string') {
        const results = compiler.inputFileSystem.readFileSync(manifest);
        compilation.plugin('after-hash', () => compilation.modifyHash(results.toString('utf-8')));
      }

I just ran into the same (or at least very similar) problem, with rather fatal consequences: The [chunkhash] didn't change even though the contents of the chunk did change (due to the DLL variable name changing).
I created a repro repo here: https://github.com/poeschko/webpack-dll-experiment

same issue

The 3.7 release notes mention that "References to dll now contribute correctly to hash". Does that solve this issue by any chance?

@poeschko hi bro, i test lateset<EMAIL_ADDRESS>has solved this problem. so i guess it was sovled at 3.7release. anyway,use latest version can fix this bug.


test: fix timecop version to keep clock specs in tests

Which issue(s) this PR fixes:
None.
What this PR does / why we need it:
Fix the current situation where CI is failing entirely.

Example: https://github.com/fluent/fluentd/actions/runs/9312942781

timecop 0.9.9 supports Process.clock_gettime.
This breaks specifications of process_extenstion of Fluentd and Fluent::Clock.

https://github.com/travisjeffery/timecop/pull/419

Fluent::Clock uses CLOCK_MONOTONIC_RAW if possible and it does not be affected.
However, CLOCK_MONOTONIC_RAW is not available on Windows, so the impact on tests on Windows is very significant.
For now, we should avoid this effect by fixing the version.
Docs Changes:
Not needed.
Release Note:
Not needed.

@kenhys Can I merge this?


docs: explain where are settings for release files

Just a tiny change to save someone some time while reading the docs. I got lost in the angular code and npm packages trying to reverse engineer it  and figure out what setting controlled this file limit:

Eventually I tracked it down from
https://github.com/go-gitea/gitea/blob/b74a0f9060d5fda341f5554ef529a2006308c6ab/options/locale/locale_en-US.ini#L2776
to
https://github.com/go-gitea/gitea/blob/b74a0f9060d5fda341f5554ef529a2006308c6ab/templates/repo/upload.tmpl#L11
to
https://github.com/go-gitea/gitea/blob/b74a0f9060d5fda341f5554ef529a2006308c6ab/web_src/js/index.js#L1043
to
https://github.com/go-gitea/gitea/blob/b74a0f9060d5fda341f5554ef529a2006308c6ab/web_src/js/features/dropzone.js#L3
to
https://www.npmjs.com/package/dropzone
and then I realized I can't read :sweat_smile:,  back  to
https://github.com/go-gitea/gitea/blob/b74a0f9060d5fda341f5554ef529a2006308c6ab/templates/repo/upload.tmpl#L8
and quickly solved it from there!!
https://github.com/go-gitea/gitea/blob/b74a0f9060d5fda341f5554ef529a2006308c6ab/modules/upload/upload.go#L81
Yes  I know this long path was 90% me failing to read code properly and going on a red herring journey...  but point is we should not have to do this in the first place to know how to  configure this file upload form :pleading_face: :point_right: :point_left:

Should the section ## Issue and pull request attachments (attachment) be renamed to ## Issue, pull request and release attachments (attachment)?

Should the section ## Issue and pull request attachments (attachment) be renamed to ## Issue, pull request and release attachments (attachment)?

While I generally agree with that, I would maybe not use this attachment duplication, so that the following would be the new title:
## Issue, pull request and release attachments.

make lgtm work


Call ripple from code

Can i call ripple-effect programmatically?
Something like:
MaterialRippleLayout.on(view)
           .rippleColor(Color.BLACK)
           .create().call(xStart, yStart);

ripple.performRipple()
for reference


Missing link?

"For more information, see this topic." There is no hyperlink in the text, there is no link anywhere on the page that refers to this subject (Workflow User Group hierarchies). I am having trouble even finding a page anywhere in the doc that explains this topic.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d14d31ae-71e7-40b0-e620-59293e7d8e1d
Version Independent ID: eb12b834-ab93-e847-3eba-9ff7e43bc693
Content: How to Set Up Workflow Users - Dynamics NAV App
Content Source: dynamics-nav-app/across-how-to-set-up-workflow-users.md
Product: dynamics-nav-2018
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Hello David,
Thank you for your feedback! This will be fixed in the next doc update.


MR.AspNetCore.Pagination.Swashbuckle Performance problems

Hello there,
I'm facing some performance issue with MR.AspNetCore.Pagination.Swashbuckle package, and in particular when I enable pagination:
 builder.Services.AddPagination(options =>
 {
     options.DefaultSize = 100;
     options.MaxSize = 1000;
 });

 options.ConfigurePagination();

When I expand one the API section the page freeze and it takes about 10 minutes before getting loaded with pagination parameters:

this is my endpoint code:
        public async Task<ActionResult<OffsetPaginationResult<ProjectAlerts>>> GetAlerts([FromRoute] string vertical, [FromRoute] int tenantId, [FromRoute] int prjId, [FromQuery] OffsetQueryModel offsetQueryModel)

is there anything wrong in the way a bind OffsetQueryModel  or in the way I setup pagination?

Hello. This package uses swagger-ui as is without any changes. It could be a problem with swagger itself, but you should start by looking into where the time is spent when that spinner is loading. Are there console logs or warnings? Does this happen only with this particular api? You can also run your browser's profiler, and it will tell you where that time is being spent. In addition, also try removing that OffsetQueryModel from the binding and see if that makes a difference, since although I can't see any problem with it, I don't use it this way.
10 mins there sounds to me like a reactivity issue inside swagger-ui. Maybe there's something it's not expecting there.

The problem seems to be the Controller return type. If I change
public async Task<ActionResult<OffsetPaginationResult<ProjectAlerts>>> GetAlerts([FromRoute] string vertical, [FromRoute] int tenantId, [FromRoute] int prjId, [FromQuery] OffsetQueryModel offsetQueryModel)

to
public async Task<IActionResult> GetAlerts([FromRoute] string vertical, [FromRoute] int tenantId, [FromRoute] int prjId, [FromQuery] OffsetQueryModel offsetQueryModel)

everything is back to normal speed.
I tried removing OffsetQueryModel as well but it doesn't have any impact on that.
I think this is not a problem of this library, but something I would need to check with Swagger team.
Cheers

Thanks for confirming. But this still does not answer where that time is spent. Is it a request in the network tab, an error in the console log, and reactivity issue with the ui not updating until much later? etc, etc
Depending on the answer, we can be sure whether this is a swagger problem or not.
Curiously, I use this exact return type in many places in one of my apps and swagger ui can display it just fine. What does your ProjectAlerts class look like?

I'm closing this as there is nothing to do in this package. Please reopen if you still have issues.


light up the NuGet packages on GitHub

You might have noticed this announcement about adding support for NuGet packages to GitHub's security vulnerability alerts.
I tested out Octokit.net today and noticed this, and got a bit sad:

Nevermind, it's easy to fix - if the PackageProjectUrl or RepositoryUrl attributes point to a GitHub repository URL (we're not following redirects, ain't nobody got time for that), these will light up differently:

This sadly won't be backported to the old nuspecs unless they get updated, but anyone using System.Reactive currently will get the benefit after a package update.
I'm not sure how attached to fwlinks you are these days, so RepositoryUrl might be the necessary workaroudn here if you want to keep them Just In Case™.

@onovotny I'll check in with the team after Universe is done and see if they can help


NTR: normal tension glaucoma

see related ticket: https://github.com/obophenotype/human-phenotype-ontology/issues/4116#issuecomment-439625685
new term: normal tension glaucoma
parent: MONDO_0005338 'open-angle glaucoma'
def: A form of open-angle glaucoma characterized by a peak intraocular pressure that is consistently within the statistically normal range.
dbxef: UManchester:psergouniotis

note, normal tension glaucoma is currently a related synonym for MONDO_0006837 'low tension glaucoma'

https://www.ncbi.nlm.nih.gov/mesh/?term=D057066

@pnrobinson I don't think we need to add this term, as it is a synonym for low tension glaucoma.
I think this is a legitimate synonym, see: https://www.glaucoma.org/glaucoma/normal-tension-glaucoma.php
I am going to close this ticket, but please reopen if you disagree


main.py working and meeting the mailer's needs

@Spockuto Please rebase your code to make it into a couple commits and make the commit names more informative.

Done. Sending a new pull request


Feat: Remove all the warnings from tests. Make warnings as errors on CI and locally

Description
Warnings are there for a reason - and should be controlled. For now we had over 40k warnings in the code. It is very easy to miss any new ones. Ive surpressed/fixed all warnings by the best possible way i could so we can have better control over warnings and better code quality moving forward.
Please verify that you have completed the following steps

[x] I have self-reviewed my code.
[ ] I have included test cases validating introduced feature/fix.
[ ] I have updated documentation.

Looks pretty good! The only big overarching comment I have is can you make the filterwarning functions look for a particular warning rather than just catching all warnings of a generic type like DepreciationWarning?

Ive changed all src warning catches to ignore warnings based on message rather than type.


Ruby 1.9.3 Broken Development Dependency term-aniscolor

Travis CI tests are failing for all Ruby 1.9.3 builds. Gem term-ansicolor >= 1.4.0 no longer supports Ruby 1.9.3. See below error for details.
https://travis-ci.org/tmuxinator/tmuxinator/jobs/164456620
$ bundle install --jobs=3 --retry=3
Fetching gem metadata from https://rubygems.org/........
Fetching version metadata from https://rubygems.org/.
Resolving dependencies...
term-ansicolor-1.4.0 requires ruby version >= 2.0, which is incompatible with
the current version, ruby 1.9.3p551
The command "eval bundle install --jobs=3 --retry=3" failed. Retrying, 2 of 3.

@seanmalloy Thanks for digging into this! To remedy this, I think perhaps the best solution would be for us to withdraw our support for Ruby 1.9.3 (which I did in #467), since 1.9.3 is no longer supported.
A quick check seems to show that Debian is shipping Ruby 2.1.5 these days, and macOS appears to be shipping Ruby 2.0.0. Without us having the data to know for sure, I imagine most users would not be impacted by the removal.
@ethagnawl @adamstrickland Thoughts?

@J3RN That sounds reasonable to me. ruby-lang.org EOL'd Ruby 1.9.3 in February 2015.

Yeah, I agree.  1.9.3 isn't supported any longer, I don't see why we'd continue supporting it.


Build failing on Netlify

Describe the bug
I don't know if this is the right place to report this (I'm not sure if this is an issue with Netlify CMS, Netlify, Gatsby, or the Gatsby + Netlify CMS Starter), but I can't build my new Netlify CMS site using the Gatsby template. The initial build work, as did a couple more, but now every time I try to build I get a slew of error messages. I Googled some of them and some of them have been discussed in various places, but I don't know which one is actually causing the build to fail.
To Reproduce

Make a change in Netlify CMS or press "Trigger Deploy" in Netlify
Login to Netlify and view errors

Expected behavior
The site will build without throwing a slew of errors.
Screenshots
In lieu of screenshots, please find error log below.
Applicable Versions:

Netlify CMS version: 2.1.2
GitHub
OS: My OS: MacOS High Sierra. No idea what Netlify is running, which I assume is where the errors are happening.
Browser version My browser: Chrome Version 69.0.3497.100 (Official Build) (64-bit).

Node.JS version: This is done on Netlify's side, right?

CMS configuration
backend:
name: git-gateway
branch: master
media_folder: static/img
public_folder: /img
collections:

name: "blog"
label: "Blog"
folder: "src/pages/blog"
create: true
slug: "{{slug}}"
fields:

{label: "Template Key", name: "templateKey", widget: "hidden", default: "blog-post"}
{label: "Title", name: "title", widget: "string"}
{label: "Publish Date", name: "date", widget: "datetime"}
{label: "Description", name: "description", widget: "text"}
{label: "Body", name: "body", widget: "markdown"}
{label: "Tags", name: "tags", widget: "list"}

name: "Games"
label: "Games"
folder: "src/pages/games"
create: true
slug: "{{slug}}"
fields:

{label: "Template Key", name: "templateKey", widget: "hidden", default: "blog-post"}
{label: "Title", name: "title", widget: "string"}
{label: "Publish Date", name: "date", widget: "datetime"}
{label: "Description", name: "description", widget: "text"}
{label: "Body", name: "body", widget: "markdown"}
{label: "Tags", name: "tags", widget: "list"}

Additional context
Here's the error log:
4:53:21 PM: Build ready to start
4:53:22 PM: build-image version: 42bca793ccd33055023c56c4ca8510463a56d317
4:53:22 PM: buildbot version: 6bab8b64bbd90091082af19fedf16bf73d502e5e
4:53:22 PM: Fetching cached dependencies
4:53:22 PM: Starting to download cache of 106.6MB
4:53:23 PM: Finished downloading cache in 871.895608ms
4:53:23 PM: Starting to extract cache
4:53:27 PM: Finished extracting cache in 3.466807641s
4:53:27 PM: Finished fetching cache in 4.410022703s
4:53:27 PM: Starting to prepare the repo for build
4:53:27 PM: Preparing Git Reference refs/heads/master
4:53:28 PM: Found netlify.toml. Overriding site configuration
4:53:28 PM: Different publish path detected, going to use the one specified in the toml file: 'public' versus '/' in the site
4:53:28 PM: Different build command detected, going to use the one specified in the toml file: 'npm run build' versus '' in the site
4:53:28 PM: Starting build script
4:53:28 PM: Installing dependencies
4:53:28 PM: Started restoring cached node version
4:53:30 PM: Finished restoring cached node version
4:53:31 PM: v8.12.0 is already installed.
4:53:31 PM: Now using node v8.12.0 (npm v6.4.1)
4:53:31 PM: Attempting ruby version 2.3.6, read from environment
4:53:32 PM: Using ruby version 2.3.6
4:53:33 PM: Using PHP version 5.6
4:53:33 PM: Started restoring cached node modules
4:53:33 PM: Finished restoring cached node modules
4:53:33 PM: Started restoring cached yarn cache
4:53:33 PM: Finished restoring cached yarn cache
4:53:33 PM: Installing NPM modules using Yarn version 1.3.2
4:53:34 PM: yarn install v1.3.2
4:53:34 PM: [1/4] Resolving packages...
4:53:35 PM: success Already up-to-date.
4:53:35 PM: Done in 1.22s.
4:53:35 PM: NPM modules installed using Yarn
4:53:36 PM: Started restoring cached go cache
4:53:36 PM: Finished restoring cached go cache
4:53:36 PM: unset GOOS;
4:53:36 PM: unset GOARCH;
4:53:36 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.10.linux.amd64';
4:53:36 PM: export PATH="/opt/buildhome/.gimme/versions/go1.10.linux.amd64/bin:${PATH}";
4:53:36 PM: go version >&2;
4:53:36 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.10.linux.amd64.env';
4:53:36 PM: go version go1.10 linux/amd64
4:53:36 PM: Installing missing commands
4:53:36 PM: Verify run directory
4:53:36 PM: Executing user command: npm run build
4:53:36 PM: ><EMAIL_ADDRESS>build /opt/build/repo
4:53:36 PM: > npm run clean && gatsby build
4:53:36 PM: ><EMAIL_ADDRESS>clean /opt/build/repo
4:53:36 PM: > rimraf .cache public
4:53:39 PM: success open and validate gatsby-config — 0.007 s
4:53:39 PM: success load plugins — 0.219 s
4:53:40 PM: success onPreInit — 0.836 s
4:53:40 PM: success delete html and css files from previous builds — 0.084 s
4:53:40 PM: success initialize cache — 0.009 s
4:53:40 PM: success copy gatsby files — 0.014 s
4:53:40 PM: success onPreBootstrap — 0.003 s
4:53:40 PM: success source and transform nodes — 0.096 s
4:53:40 PM: success building schema — 0.255 s
4:53:40 PM: success createPages — 0.053 s
4:53:40 PM: success createPagesStatefully — 0.025 s
4:53:40 PM: success onPreExtractQueries — 0.001 s
4:53:40 PM: success update schema — 0.142 s
4:53:40 PM: error GraphQL Error Unknown field image on type frontmatter_2
4:53:40 PM:   file: /opt/build/repo/src/templates/product-page.js
4:53:40 PM:    1 |
4:53:40 PM:    2 |   query ProductPage($id: String!) {
4:53:41 PM:    3 |     markdownRemark(id: { eq: $id }) {
4:53:41 PM:    4 |       frontmatter {
4:53:41 PM:    5 |         title
4:53:41 PM: >  6 |         image
4:53:41 PM:      |         ^
4:53:41 PM:    7 |         heading
4:53:41 PM:    8 |         description
4:53:41 PM:    9 |         intro {
4:53:41 PM:   10 |           blurbs {
4:53:41 PM:   11 |             image
4:53:41 PM:   12 |             text
4:53:41 PM:   13 |           }
4:53:41 PM:   14 |           heading
4:53:41 PM:   15 |           description
4:53:41 PM:   16 |         }
4:53:41 PM: npm ERR! code ELIFECYCLE
4:53:41 PM: npm ERR! errno 1
4:53:41 PM: npm ERR<EMAIL_ADDRESS>build: npm run clean && gatsby build
4:53:41 PM: npm ERR! Exit status 1
4:53:41 PM: npm ERR!
4:53:41 PM: npm ERR! Failed at the<EMAIL_ADDRESS>build script.
4:53:41 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
4:53:41 PM: npm ERR! A complete log of this run can be found in:
4:53:41 PM: npm ERR!     /opt/buildhome/.npm/_logs/2018-10-09T23_53_40_996Z-debug.log
4:53:41 PM: Caching artifacts
4:53:41 PM: Started saving node modules
4:53:41 PM: Finished saving node modules
4:53:41 PM: Started saving yarn cache
4:53:41 PM: Finished saving yarn cache
4:53:41 PM: Started saving pip cache
4:53:41 PM: Finished saving pip cache
4:53:41 PM: Started saving emacs cask dependencies
4:53:41 PM: Finished saving emacs cask dependencies
4:53:41 PM: Started saving maven dependencies
4:53:41 PM: Finished saving maven dependencies
4:53:41 PM: Started saving boot dependencies
4:53:41 PM: Finished saving boot dependencies
4:53:41 PM: Started saving go dependencies
4:53:41 PM: Finished saving go dependencies
4:53:41 PM: Error running command: Build script returned non-zero exit code: 1
4:53:41 PM: Failing build: Failed to build site
4:53:41 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
4:53:41 PM: Finished processing build request in 19.209158665s
And here are the errors from Chrome's JavaScript console:
netlify-cms 2.1.2
/.netlify/git/github/contents/src/pages/products/index.md?ts=1539132874341&ref=master:1 Failed to load resource: the server responded with a status of 404 ()
netlify-cms.js:38 failed to load file from GitHub: src/pages/products/index.md
api.readFile.then.catch @ netlify-cms.js:38
netlify-cms.js:178 [Deprecation] Using unescaped '#' characters in a data URI body is deprecated and will be removed in M71, around December 2018. Please use '%23' instead. See https://www.chromestatus.com/features/5656049583390720 for more details.
Hi @ netlify-cms.js:178
4index.js:121 Uncaught ReferenceError: ___loader is not defined
at index.js:121
at index.js:51
at Array.forEach ()
at IntersectionObserver. (index.js:44)

I believe that means none of your product content files have an image field in the frontmatter, but you've defined that field in your graphql query. You just need one of your product content files to have that field.
Sent with GitHawk

Hm, the thing is I deleted the Products page and removed it from the config file. But some of the image files might still be around. Maybe I just need to delete them?

OK, got it figured out. Had to delete the product page template. I would expect deleting a page from within the CMS to not cause the build process to break, or if breakage is unavoidable to at least throw a more understandable error message. Should I open a separate bug report for that?

Unfortunately, we would not be able to help with an issue with a Netlify build. That would need to be reported to Netlify support at https://netlify.com/support
If you think it is a NetlifyCMS app issue, definitely feel free to create a new issue.


Abstract current OpenAI and AzureOpenAI implementations from the Core Kernel

Motivation and Context
This is an effort to abstract current OpenAI and AzureOpenAI implementations from the Core Kernel code base.

Why is this change required?
This change increases the abstractions on the Core and allow it to be handling any Backend implementations in the future

What problem does it solve?
Currently the Kernel is very coupled with those two implementations and any effort to do something differently demands more code and complexity

What scenario does it contribute to?
This contributes to reducing the places in the code that need to be changed to support new or any change in the current configurations

Description
The changes made includes abstracting how backend configurations are added to the KernelConfig class making use of two new flag interfaces ICompletionBackendConfig and IEmbeddingsBackendConfig.
Another change that was necessary was inverting the control on the ITextCompletionClient instantiation in Kernel CreateSemanticFunction to the KernelConfig as a delegate when a  func.SetAIBackend is defined.
With those changes it was possible to move out of both Kernel and KernelConfig any specific implementations from AzureOpenAI and OpenAI and adding them as Extension methods in KernelConfigExtensions.cs.
This makes the code simpler and prepares a clear path if we need to move those implementations to a dedicated backend package and add many more implementations.
Added unit tests to validate the current behavior as expected without impacts.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

@RogerBarreto some conflicts to address. There's also another PR touching the HTTP layer, so could happen again, in one or the other, depending on the order these will be merged

100% agree with the premise and I've started drafting a doc to think through this holistically.
Even if we merged this PR the problem would persist, e.g. the kernel is still rooted on text and completions (semantic memory is the only exception so far; and connectors are tangentially part of this conversation, e.g. OAI clients == connectors).
We need to push further and reason about more generic and divers AI skills, and how the kernel allows to integrate them in the same programming model.
My suggestion would be to park this PR, and join asap the conversation about the goals, and at the same time extend the list of models, making these changes part of the same story:

decouple from completion
integrate OAI ChatGPT, Edit, Insert, DallE, Stable Diffusion, Azure Speech
allow to use any backend, and for each backend one must provide specs and clients

Adding more models is the only way to test if the new code can scale. Otherwise, I would say that we're just moving the code around, without verifying the benefits. (This would also be something like the 8th/9th time we refactor OpenAI clients integration, I think this is a good opportunity to extend the AI surface as planned).

100% agree with the premise and in fact I recently started drafting a doc to think through this holistically. I was trying to integrate a separate model and noticed the excessive effort required.
Even if we merged this PR the problem would persist, e.g. the kernel is still rooted on text and completions (semantic memory is the only exception so far; and connectors are tangentially part of this conversation, e.g. OAI clients == connectors).
We need to push further and reason about more generic and divers AI skills, and how the kernel allows to integrate them in the same programming model.
My suggestion would be to park this PR, and join asap the conversation about the goals, and at the same time extend the list of models, making these changes part of the same story:

decouple from completion
integrate OAI ChatGPT, Edit, Insert, DallE, Stable Diffusion, Azure Speech
allow to use any backend, and for each backend one must provide specs and clients

Adding more models is the only way to test if the new code can scale. Otherwise, I would say that we're just moving the code around, without verifying the benefits. (This would also be something like the 8th/9th time we refactor OpenAI clients integration, I think this is a good opportunity to extend the AI surface as planned).

@dluc That make sense, we can leave this PR parked.
Latests conflicts merged.

Closing for now as this approach will be revisited into a future PR


Add more extension-point to support more rich editor (types).

Text editor is not enough for all. It will be much better if plugins could add more 'rich' editors, just like the extension editor.

@jrieken @Tyriar fyi

dupe of #12176


feat: Step divider UI

Summary
Resolves #64.
Adds drag/drop functionality for steps, and other related controls/interaction. Complete list:

steps are drag/droppable (i.e. reorganize existing steps around the recorded actions
steps are insertable
step dividers are deletable
steps have an assignable name, that can be edited via the UI
steps remain collapsible

Implementation details
There are a few deviations from the design as it is shown in the issue:

I did not add a drag/drop icon as the design shows; my thinking is that the functionality is discoverable due to the icon changing when the user passes the cursor over a divider.
There was no design specification in the issue deliverable for how the droppable areas should look. I've emulated a bit of the EUI drag/drop UI from one of the examples, using the primary and secondary colors from the EUI palette, but this is completely open for debate/improvement.

How to validate this change
Test the functionality of each of the items related in the description.

You should be able to drag dividers between the actions for the preceding and next step.
Deleting a divider should merge its nested steps to the preceding one
The first step should not be draggable or deletable
Test the renaming in combination with dragging, deleting, creating steps

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-03-28T15:51:39.195+0000

Duration: 14 min 15 sec

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

Thanks for putting this together @justinkambic. I agree with a lot of the feedback but I need some time to synthesize before I propose any solutions. Since I'm coming in a little new to this project, I'd definitely love to chat first so I can understand some of the history and decisions already made.
I'll mention some brief notes below. These are mostly thoughts and ideas rather than actionable feedback.
"+" icon
Unclear what this does. Tooltip might help, but personally I'd love to explore a different pattern for this. There already seems to be multiple uses for this icon in the app, and there are a lot of icons in general without clear descriptors. The small size of the click target and density of icons could be problematic.
Trash icon is unclear
As already stated, it's not clear whether this will delete the step and all of it's associated actions, or just the step divider. Because we visually represent actions as children of steps (via the accordian pattern), I'd expect that deleting a step would also delete actions. I found it confusing when the actions were moved into a different step. Perhaps we could be more explicit somehow in the UI. For example, there could be a confirmation modal which asks the user to confirm their desired outcome: delete step divider vs delete step and actions.
I also find it odd that deleting a step vs deleting an action use a different pattern. I think there's an opportunity to unify here.
Dragging behavior
It seems a little odd that you can drag steps but not actions, especially when moving a collapsed step. I understand the concerns about breaking a script by allowing users to reorder actions, but this "strictness" makes the the drag interactions feel less intuitive.
For example, imagine 2 steps (A and B), each with 2 actions (1 2 3 4):
---Step A---
action 1
action 2
---Step B---
action 3
action 4

If I want to move action 3 into step A, my instinct is to just drag it into the step / group. Instead, I have to move Step B below action 3, which works but would not be my first guess. I think partially because we allow users to collapse steps and hide the associated actions, users would expect to be able to move actions around. I'm not saying we should necessarily do this, but if we removed the collapsing behavior, the limitations / strictness of the dragging behavior might feel a little more intuitive?
Lastly, the "drop zones" for the drag behavior are hard to hit. I'd expect the dropzone to be the entire container, and moving the step without releasing the click would visually reorder the steps and actions. It's hard to communicate with a static image, but I'm imagining something more like this:

I understand this behavior might be difficult with the components we're currently using, so we'd have to revisit.
Next steps
Let's sync up and talk about this. I'd love to spend some time and address these problems, but I need to balance it with some of the other priorities I have going on as I get up to speed on the Synthetics project.

Delete button is visible when editing a step name and prompts unexpected behavior. My suggestion is to hide the delete button. WDYT?

Well-spotted! Yes, I'll add this to the PR description and update when resolved.

a few comments about some aria-labels

Thanks for this - I was planning to come back and address code stuff after the dependent PR is merged, but I appreciate your consideration of this now. aria is functionality.

Hey @lucasfcosta 👋

Everything seems to be working fine now except for the tooltip and behaviour of the lateral testing panel once tests are running. Essentially, once you click "Test", its tooltip is always displayed on top of everything, including the side panel with results (it always happens when I break down steps).

This bug is fixed by this PR and it's been merged to main

@lucasfcosta I've updated the branch to incorporate almost all your feedback; I did skip one comment, LMK if there's some specific change you'd like to see implemented there.
Thanks for such a detailed review, I think we are getting closer on this one!

@lucasfcosta thanks again for all your UI testing of this PR.
Can you have a look at this commit when you have a chance? It’s my proposed solution to the issue of unwanted expansion of those elements. Basically it floats the isOpen state from the component level up to the data structure level to help ensure that it is persisted when UI elements are destroyed/mutated as part of the drag/drop functionality.

Thanks for finding this bug @lucasfcosta - I am thinking it actually exists on main but I am fine with fixing it here. I have resolved the problem and am in the process of writing an e2e test to cover it for the future. Sadly it was a bit tricky and I probably won't have a commit ready for review until I start my day tomorrow sometime.

@lucasfcosta I believe this is worth yet another look 😃
I have resolved the issue you discovered with https://github.com/elastic/synthetics-recorder/pull/175/commits/b3e7dd6dd9648e6df354bc87e17469f0cc3a2fe4, and I've taken the time to add a comprehensive e2e test that should cover almost all of the functionality that was broken. Even for some of the fields not covered, the underlying issue I fixed was a single point of failure for all of them, so as long as some are working, that issue should be resolved for all of them.


Extism gem fails to load on Ruby 3.3.0 on macOS

The extism gem throws an error immediately after trying to require the library:
brandon@Air ~ % gem install extism
Successfully installed extism-1.0.0
Parsing documentation for extism-1.0.0
Done installing documentation for extism after 0 seconds
1 gem installed

brandon@Air ~ % irb

irb(main):001> require 'extism'
/Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/ffi-1.16.3/lib/ffi/dynamic_library.rb:65:in `load_library': Could not open library 'extism': dlopen(extism, 0x0005): tried: 'extism' (no such file), '/usr/local/lib/extism' (no such file), '/usr/lib/extism' (no such file), '/Users/brandon/extism' (no such file). (LoadError)
Could not open library 'libextism.dylib': dlopen(libextism.dylib, 0x0005): tried: 'libextism.dylib' (no such file), '/usr/local/lib/libextism.dylib' (no such file), '/usr/lib/libextism.dylib' (no such file), '/Users/brandon/libextism.dylib' (no such file).
Searched in <system library path>, /usr/lib, /usr/local/lib, /opt/local/lib, /opt/homebrew/lib
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/ffi-1.16.3/lib/ffi/library.rb:95:in `block in ffi_lib'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/ffi-1.16.3/lib/ffi/library.rb:94:in `map'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/ffi-1.16.3/lib/ffi/library.rb:94:in `ffi_lib'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/extism-1.0.0/lib/extism/libextism.rb:8:in `<module:LibExtism>'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/extism-1.0.0/lib/extism/libextism.rb:6:in `<module:Extism>'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/extism-1.0.0/lib/extism/libextism.rb:1:in `<top (required)>'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/extism-1.0.0/lib/extism.rb:7:in `require_relative'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/extism-1.0.0/lib/extism.rb:7:in `<top (required)>'
	from <internal:/Users/brandon/.rbenv/versions/3.3.0/lib/ruby/site_ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:141:in `require'
	from <internal:/Users/brandon/.rbenv/versions/3.3.0/lib/ruby/site_ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:141:in `rescue in require'
	from <internal:/Users/brandon/.rbenv/versions/3.3.0/lib/ruby/site_ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:135:in `require'
	from (irb):1:in `<main>'
	from <internal:kernel>:187:in `loop'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/irb-1.11.2/exe/irb:9:in `<top (required)>'
	from /Users/brandon/.rbenv/versions/3.3.0/bin/irb:25:in `load'
	from /Users/brandon/.rbenv/versions/3.3.0/bin/irb:25:in `<main>'
<internal:/Users/brandon/.rbenv/versions/3.3.0/lib/ruby/site_ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- extism (LoadError)
	from <internal:/Users/brandon/.rbenv/versions/3.3.0/lib/ruby/site_ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
	from (irb):1:in `<main>'
	from <internal:kernel>:187:in `loop'
	from /Users/brandon/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/irb-1.11.2/exe/irb:9:in `<top (required)>'
	from /Users/brandon/.rbenv/versions/3.3.0/bin/irb:25:in `load'
	from /Users/brandon/.rbenv/versions/3.3.0/bin/irb:25:in `<main>'
irb(main):002>

Oops! Missed the sudo extism lib install step, and the fact that there were off-page steps needed:
curl https://get.extism.org/cli | sh

hey @brandondrew! glad you got it working

there were off-page steps needed

do you recall which of these steps weren't on the doc you used to get started? would like to fix that

It might make sense to include the missing curl step on that page (even though there are other options), to make it easier to follow the directions as a simple step-by-step process (and allow those who want to dig into the alternative methods to follow the link).
It so common for READMEs to include several different pages (do this on Red Hat, this on Ubuntu, this on Windows, this on Mac, etc.) that I tend to scan the commands and mentally filter out the ones that don't seem to apply.  In this case that strategy failed me.

@nilslice yeah, the curl step was not on the page I was reading: https://extism.org/docs/quickstart/host-quickstart

You could just include a note next to the curl step that building from source and using Nix are also alternative options.

I see, thanks! Yea, linking to a single page is really an effort for us to reduce the amount of changes needed in case the curl install instructions change. will bring it up to the team and see - appreciate your feedback!


Notorious doesn't work with non <IP_ADDRESS> hosts

It does work, but it can't connect to it's own IP for whatever reason, but I guess that makes sense.


power consumption comparison between Teensy3.1 and TeensyLC

Hi, first of all, thank you for your great work!
I use your library on a Tennsy32 (no modification) and measure hibernate power consumption of about 43uA. Did you manage to have less than that?
I'm also wondering whether using an TeensyLC would provide further lower consumption or not. I do not have the TeensyLC and if you measure lower power consumption, then it will definitely be interesting for me to buy some.  Thank you for any answer you can provide.
regards,

I saw around 15uA with nothing attached to Teensy 3.2 and around 5uA on a TeenyLC with nothing attached. I actually did redundant measurements with three different types of current detecting equipment.

Thank for the answer. I also have nothing attached to the Teensy32 and the lowest in hibernate is the 43uA. I have version 5.5, would version 6 reduce power consumption? So seems that the LC does reduce the power consumption. I'm going to get some of them to test. Thanks again for your excellent work!

Version 6 would not matter since they both share pretty much the same driver code for the actual low power operation. That being said I'm no longer going to develop version 5 anymore and will merge version 6 in the near future. Works almost the same as version 5, version 6 makes it easier for me to add new features.
Back to the actual measurements, can tell me how you are measuring for current (equipment). Make sure nothing is attached to the teensy and can you share the code you are using?

I'm using the a variant of the example for hibernate:
#include <Snooze.h>
SnoozeBlock config;
void setup() {
Serial.begin(38400);
pinMode(LED_BUILTIN, OUTPUT);
config.setTimer(30000);// milliseconds
}
void loop() {
Serial.println("No low power for 10s");
Serial.flush();
delay(10000);

Serial.println("Entering low power for 30s");
Serial.flush();
delay(100);
/********************************************************
 * feed the sleep function its wakeup parameters. Then go
 * to deepSleep.
 ********************************************************/
//int who = Snooze.deepSleep( config );// return module that woke processor
int who = Snooze.hibernate( config );

Serial.print("Wake up from low power with code: ");
Serial.println(who);
Serial.flush();

}
Nothing is attached. To measure consumption I use traditional 1ohm schematic to measure voltage between the 2 side of the resistor. I also used the meter in amp mode tuned to uA and the measures are consistent. I'm injecting 5v to Vin. When in hibernate mode, drawn current is about 43uA. When active, the drawn current is about 32mA.

Hmmm, try taking all the print statements out. USB doesn't work well at all when using sleep, not sure if that will do anything for the current but in Hibernate the USB regulator is put in low power state so maybe if anything is in the usb queue it could effect the regulator. I measured and other have confirmed the ~15uA for the Teensy3.2.  I also used a shunt resistor a multimeter and specialized low current measuring tool that all agreed on multiple Teensy's. Not saying your measurements are wrong I just not sure why it is giving you these readings.

OK, I will try to remove the print statement, but I assumed that the
flush() would actually flush the queue. It the print statements do
reduce the efficacy of the low power, then in production mode, I have to
remove all print statements. I don't have the specialized tool, but the
difference is quite high currently, so will try first what you say and
will get back to you. Thanks for the answer.
regards,
Le 16/11/16 à 18:13, duff2013 a écrit :

Hmmm, try taking all the print statements out. USB doesn't work well
at all when using sleep, not sure if that will do anything for the
current but in Hibernate the USB regulator is put in low power state
so maybe if anything is in the usb queue it could effect the
regulator. I measured and other have confirmed the ~15uA for the
Teensy3.2.  I
also used a shunt resistor a multimeter and specialized low current
measuring tool that all agreed on multiple Teensy's. Not saying your
measurements are wrong I just not sure why it is giving you these
readings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/duff2013/Snooze/issues/14#issuecomment-261008587,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNEN0VcDxxKUxv03Apo_gRNKEbRyfJ0ks5q-zmygaJpZM4KyN57.

C. Pham.
--
|------------ Congduc PHAM - Professor --------------------------|
|  LIUPPA - Equipe T2I              |         U.P.P.A. Pau       |
|  http://liuppa.univ-pau.fr/       |   http://www.univ-pau.fr   |
|----------------------------------------------------------------|
|UPPA, LIUPPA laboratory, UFR Sciences et Techniques             |
|Avenue de l'Université - BP 1155                                |
|64013 PAU CEDEX, FRANCE                                         |
|                                                                |
|phone:  [33] (0) 5 59 40 75 94                                  |
|fax:    [33] (0) 5 59 40 76 54                                  |

<EMAIL_ADDRESS>http://www.univ-pau.fr/~cpham

flush for USB (Serial) does not do anything. https://github.com/PaulStoffregen/cores/issues/43

OK, I removed all print statements and it does not change anything,
still about 43uA in hibernate.
I took another Teensy32, this one shows 50uA.
It is far from the 15uA that you manage to get. Could you share the code
with which you measure the 15uA?
Regards,
Le 16/11/2016 à 21:29, duff2013 a écrit :

flush for USB (Serial) does not do anything. PaulStoffregen/cores#43
https://github.com/PaulStoffregen/cores/issues/43
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/duff2013/Snooze/issues/14#issuecomment-261062434,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNENzdzjcoWi4_z2cIP3TwX8pcxigOqks5q-2fCgaJpZM4KyN57.

C. Pham.
--
|------------ Congduc PHAM - Professor --------------------------|
|  LIUPPA - Equipe T2I              |         U.P.P.A. Pau       |
|  http://liuppa.univ-pau.fr/       |   http://www.univ-pau.fr   |
|----------------------------------------------------------------|
|UPPA, LIUPPA laboratory, UFR Sciences et Techniques             |
|Avenue de l'Université - BP 1155                                |
|64013 PAU CEDEX, FRANCE                                         |
|                                                                |
|phone:  [33] (0) 5 59 40 75 94                                  |
|fax:    [33] (0) 5 59 40 76 54                                  |

<EMAIL_ADDRESS>http://www.univ-pau.fr/~cpham

just what you posted is good, maybe the new regulator on the Teensy3.2 Vin power could be accounting for this? I really don't know what else to tell you. I'll get out my equipment next week and see what I come up with since it's been awhile and I need to do some work with the Teensy 3.5/6 and Snooze anyway.

Hi, I confirm that with the TeensyLC 5uA with nothing attached can be achieved. But for the Teensy32, still it is around 40uA.
regards,

The values I reported are with a Teensy 3.1 which used a smaller volatge regulator compared to the 3.2. Your values for the Teensy 3.2 are what I got. You can read about the differences between the 3.1 and 3.2 here and here. Thanks for following up!

OK, thank you. Then I will also buy some 3.1 has I probably don't need 500mA on the power pin.

I'm going to close this issue.


Signature Mismatch in Latest Version Magento 2.3.0

Hello, I have installed your Extension downloaded from Marketplace. Up to Magento 2.2.6 It's working fine. But Issue in latest Magento 2.3.0. There is error message 'ERROR: Signature mismatch', and redirected to 'https://test.cashfree.com/billpay/checkout/post/submit' url after selecting Cashfree as a Payment Method.

@vrajeshkpatel They have not updated their plugin yet ?
@akashcashfree When is the next release?

Not yet release.

@4j4yk  and @vrajeshpatel4u You can use our latest plugin.


Content publishing process audit & analysis

Acceptance criteria: Assess our processes of publishing content for both efficiency and speed, and also align the content itself to what our adopters' needs and wants are.
Definition of done: An audit and analysis of our content publishing process, start to finish, that includes suggestions to improve and for it to be as relevant as possible.
cc: @JennySanchez @wonilsuhibm

Hi, @jimpistilli I saw the story point setting is at 21. It seems really high, can you confirm? Thank you.

@JennySanchez Corrected that to a 5, if you think that's accurate.

@jimpistilli The draft of the website content publishing process and timeline can be found here.
The document is created based on Lara's pattern content publishing roadmap document.
The focus here is to make sure the steps look correct and the timelines look reasonable.

@JennySanchez Reviewed and made a few edits but overall looks good to me.

@jimpistilli Got it. Thank you for reviewing the doc.


Nav bar button not aligned in about us tab

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

Shop navigation button is not aligned in the same line in about us tab.
please assign this issue to me under GSSoC'24
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

hey i can fix this issue under gssoc 24


Fine tune tone for the answer

Wondering if it is possible to fine-tune the tone the AI replying to me? such as if I provided the dialogue of Sherlock Holmes, could it reply me with the tone that Sherlock talks? Ty!
this issue is opened on behalf of twitter user ring_hyacinth, tweet

Maybe an option to customize the prompt would be a general solution

Person bot is a thing now. Closing this issue. #182


Fix tests fails with new Scikit-Learn 0.23.1

For now I made changes only in branch of code for latest version of Scikit-Learn.
But I think that our work with Logistic Regression is too complicated. We have the branching on init stage in
https://github.com/IntelPython/daal4py/blob/master/daal4py/sklearn/linear_model/logistic_path.py
like
if LooseVersion(sklearn_version) >= LooseVersion("0.22"):
    from ._logistic_path_0_22 import *
else:
    from ._logistic_path_0_21 import *

and in files _logistic_path_*.py themselves.
Please help me clarify that it is really necessary and advice how to simplify it.

But I think that our work with Logistic Regression is too complicated.

The 0.22 file can probably be tidied up, ridding it of dead code intended to support legacy behavior.


[SDL 0099] New remote control modules (LIGHT, AUDIO, HMI_SETTINGS) and parameters (SIS Data)

Proposal: New remote control modules (LIGHT, AUDIO, HMI_SETTINGS) and parameters (SIS Data)

SDL remote control provides the ability for mobile applications to control certain components of the vehicle, such as, tune the radio, set the desired temperature or change the fan speed. However, currently only CLIMATE and RADIO modules are available for remote-control. Mobile application developers need more than basic climate or radio control. To meet developers' requirements, we propose to add three new modules (AUDIO, LIGHT, HMI_SETTINGS) and some new parameters (heatedXXXEnable and radio sisData) to the existing CLIMATE and RADIO modules respectively. This proposal only defines new data types and new parameters added to the existing data types. It does not add or change any remote control RPCs.

Review: https://github.com/smartdevicelink/sdl_evolution/issues/296
Steering Committee Decision:

The Steering Committee voted to accept this proposal with revisions. The author will revise the proposal to fix a few typos, as well as include descriptions for the groups of lights - listing which single light elements they typically include. It was also noted that limiting the scope of proposals, especially those related to Remote Control, in the future will help to make for easier understanding and discussion among SDLC Members.
Proposal has now been revised to include the descriptions and fix the typos mentioned.

Note that this feature is revised in SDL 0182

Proposal markdown file has been updated per the revisions included in accepted Evolution Proposal Revise SDL-0099 - New remote control modules.  Implementation will need to be revised to remove the duplicate structs and reuse GPSData and RGBColor.

Proposal markdown file has been updated to fixREAR_LEFT_BREAK_LIGHT and REAR_RIGHT_BREAK_LIGHT typos.  Proposal now includes REAR_LEFT_BRAKE_LIGHT and REAR_RIGHT_BRAKE_LIGHT.  RPC Spec implementation should reflect correct spelling.

Proposal file has been updated per the revisions in  this accepted PR.

Proposal file has been updated per the revisions in  this accepted PR.

PR has been revised per accepted PR.


Query: Remove unnecessary ExplodeStarProjection

Handle StarProjection expression better in PushDownSubquery
SelectExpression.BindSubqueryProjectionIndexToSelectExpression method which binds AnonymousObject index with correct projected expression
resolves #8131

@anpete - updated to simplify ExplodeStarProjection (since we already have list of lifted projections) & renamed methods


UI shows policy reports from both 1.10 & 1.11

Policy reports generated in 1.10 are not cleaned after upgrade to 1.11.
This results in policy-reporter UI showing both old and new reports.

~ k get policyreports -n default
NAME                                   PASS   FAIL   WARN   ERROR   SKIP   AGE
polr-ns-default                        3      5      0      0       0      52m
c787b9cf-8d84-40cf-8771-c076575d1c71   0      1      0      0       0      33m
02e6696a-2ada-410c-88ce-6d9af7130164   3      4      0      0       0      33m
9af1624e-a929-403e-8e72-96e7a5daee3e   3      4      0      0       0      32m
738906dc-1668-47b3-a768-de762b8321e5   3      4      0      0       0      31m

Possible solution proposed on daily would be to delete old policy report from helm hook during upgrade to 1.11.0.

Closing in favor of https://github.com/kubewarden/helm-charts/issues/408