Device Keyboard

WIP - Only integrated Adam's keyboard so far. Currently using the jog scrolling version of the keyboard which is working nicely.
I might explore a very basic restoration protocol here so that I can better understand how we should approach a more complete protocol.

Bunch of temp commits here for testing & exploration. Will drop them all except for keyboard changes once we're happy.
You can find "Restore" under the device settings.

I took a test run of this. I haven't reviewed the app side. The device code of the device side looks well arranged. Here's my UX comments trying to record and enter a few backups:

The keyboard state should be in the workflow.
It seems like it would be much more efficient to have a larger 4 row keyboard. I don't need to see several rows of what I've already entered. The last four characters would be enough in a single row at the top. This would allow for four rows of characters.
The share index should be entered separately and not assumed.
The frost[X] shouldn't be displayed while entering the backup.

A general comment is that I think we should use capital letters, not start with the 1 which is confusing because you can also have lowercase l. The 1 can be added by us internally before parsing.

might be a bit late but I have been using the meshtastic keyboard on their t-watch (which I believe is the same screen setup) it looks like this, it has haptic and it seems like a good layout compromise for their purpose, though it is still to small in my opinion for frequent messaging. I hope this is helpful

We could show the FROST[x] inside the framebuffer once on the entering share stage.
We used to have the ability to return to the entering HRP page by pressing backspace with an empty framebuffer, I kind of liked this feature but maybe it is excessive functionality.
@midizzz we're going to looking into some other keyboard designs in a subsequent PR. Our keyboard is likely too small for a full qwerty keyboard but we have some other ideas like nokia style or expanding grouped keys.

We could show the FROST[x] inside the framebuffer once on the entering share stage.

I don't think so. There's no space for that?

We used to have the ability to return to the entering HRP page by pressing backspace with an empty framebuffer, I kind of liked this feature but maybe it is excessive functionality.

I think we shouldn't even enter it on the device since it's public. You never want to edit this. You do want it displayed on the final confirm page on the device. We should look at this again when we make a more step by step workflow for restoring the backup. This along with printing out backup cards. We might decide not to have FROST[..] anywhere at all.

Reviewed and tested!
Do you think it is worth taking the time to make our existing UI elements widget style? Or only as needed?
Please approve (I can't approve own pr) after checking 5a36deff4437dc0532c6dec371ac68ca3a7c48a6 makes sense. The coordinator loop thread finishing keygen UI protocol was racing against the backup protocol beginning.


BUG: refguide-check: allow multiline namedtuples

Reference issue

closes gh-16081
What does this implement/fix?

Make refguide-check understand multiline namedtuples.
Additional information

Hmm, looks like there's a new complaint about sparse/linalg/_isolve/iterative.py in refguide now, unless the previous issue was fixed and that's just showing up as the "next issue."

Well, the sparse.linalg failure is something else, I'm pretty sure. Was there some work in sparse.linalg recently?

Ok, tried to rerun $ python dev.py --refguide-check locally and it passes. I'd suspect a slight numerical issue and a default tolerance being just a wee bit too tight.

Hmmm. The sparse.linalg failure is reported to be
===================
scipy.sparse.linalg
===================

scipy.sparse.linalg.bicgstab
----------------------------

File "build/testenv/lib/python3.9/site-packages/scipy/sparse/linalg/_isolve/iterative.py", line 62, in bicgstab
Failed example:
    np.allclose(A.dot(x), b)
Expected:
    True
Got:
    False

Looking at the html docs, https://docs.scipy.org/doc/scipy/reference/generated/scipy.sparse.linalg.bicgstab.html, there is no docstring example. However, https://github.com/scipy/scipy/blob/main/scipy/sparse/linalg/_isolve/iterative.py#L215
seems to list an example --- which uses random numbers without seeding. So maybe that's just it, an unlucky draw from a pseudo-random distrtibution.
While I'm looking at this file:

why on earth are docsrings included in some form of decorator?
html docs do not seem to show examples
html docs lack the source link

maybe separate issue for the separate issue

Sounds just the right motto for 00:01 local time on the 1st of May, the Labour day :-).


style(eslint): review naming convention

Description

Steps

[ ]
[ ]

Breaking changes

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


upgraded to next SNAPSHOT

ugraded to 0.9.0-SNAPSHOT
this PR has to be merged before we can push the 0.8.x branch to uberfire/uberfire

Looking at this right now. Will build&deploy locally (to make sure the snapshots are immediately there) and then merge it.


Set the waffle project to the github user/repo

Issue created with imdone.io

DOING: Set the waffle project to the github user/repo +feature id:130
lib/views/product-detail-view.coffee:13
@imdone creator-bot. Get TODOBOTs to do your work at imdone.io

Replace this with something meaningful like... "@piascikj started working this issue."

TODO: Set the waffle project to the github user/repo +feature id:130 gh:194
lib/views/product-detail-view.coffee:13
@imdone comment-bot. Get TODOBOTs to do your work at imdone.io

Replace this with something meaningful like... "@piascikj started working this issue."

DOING: Set the waffle project to the github user/repo +feature id:130 gh:194
lib/views/product-detail-view.coffee:13
@imdone comment-bot. Get TODOBOTs to do your work at imdone.io

DONE: Set the waffle project to the github user/repo +feature id:130 gh:194
lib/views/product-detail-view.coffee:13
@imdone closer-bot. Get TODOBOTs to do your work at imdone.io

Replace this with something meaningful like... "@piascikj started working this issue."

DOING: Set the waffle project to the github user/repo +feature id:130 gh:194
lib/views/product-detail-view.coffee:13
@imdone comment-bot. Get TODOBOTs to do your work at imdone.io

Replace this with something meaningful like... "@piascikj started working this issue."

READY: Set the waffle project to the github user/repo +feature id:130 gh:194
lib/views/product-detail-view.coffee:20
@imdone comment-bot. Get TODOBOTs to do your work at imdone.io

DONE: Set the waffle project to the github user/repo +feature gh:194 id:94
lib/views/product-detail-view.coffee:19
@imdone closer-bot. Get TODOBOTs to do your work at imdone.io


Fix logging bug: Pub-Sub and RPC logger HTML pages now display logs properly

This PR addresses issue #14 . Here is the logs screenshots

LGTM


Migrate kie-tools/ci_codeql.yml GH workflow to Apache Jenkins

The job is created on ASF Jenkins and it's generating the reports for go and javascript: https://ci-builds.apache.org/job/KIE/job/kie-tools/job/kie-tools-ci-codeql/view/change-requests/job/PR-9/5/
Still need to discuss the need of uploading the sarif report files to github.

As previously discussed all PR related to GH Actions -> Jenkins (as this one) opened to https://github.com/apache/incubator-kie-tools-temporary-rnd-do-not-use are GOOD to be integrated as it is a temporary repository.
Track at #704


EmailLinkSignIn - retrieve email used

Is there any way to retrieve the email used to send an email link without implementing a custom function/implementation of the firebaseui react?
i.e. it'd be great to have something similar to the below in the umailLinkSignIn callback:
emailLinkSignIn: function(email) {
   window.localStorage.setItem('emailForSignIn', email)
}

so we can avoid reprompting for the email.

When the link is opened on the same device, we do not prompt the user to provide it again. We already cache the email locally in those flows.

perfect, once I changed the signInFlow from 'popup' to 'redirect' it started automatically logging in with the correct email address - thanks.
Still seems to be relevant if you have is set as popup signInFlow though.
have used the below in uiConfig as a workaround:
signInFlow: firebase.auth().isSignInWithEmailLink(window.location.href) ? 'redirect' : 'popup',

I don't think signInFlow should affect this. signInFlow affects sign-in with IdPs like Google, Facebook, Twitter, etc with popup or redirect.

I'm seeing the same behavior.  Changing signInFlow from popup to redirect fixed the issue.

I'm having the same (I think) issue. When using email link authentication and pressing the link in the email, the user won't get logged in when I have signInFlow set to popup. However if signInFlow is set to redirect , it works fine.

I had the same problem and it took quite a while to figure out. Setting signInFlow to redirect makes passwordless e-mail sign in work.


[SC-168] move bash scipt to template

In an effort to remove a dependency on Sage-Bionetworks/service-catalog-utils
repo and its inherant transitive dependencies.  We move the script into
the cloudformation template.

This is a bad idea.


⚠ Secret Website 3 has degraded performance

In 8c085f1, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2764 ms

Resolved: Secret Website 3 performance has improved in 29ec072.


Emoji Fonts not working

Not tagged as a bug since I'm not sure if it's suited for this, or if I'm doing something wrong.

Open the multiple-fonts example
Change the Roboto font to for example, Noto Emoji
Make it print out a basic smile emoji
Watch it crash

I'm trying to draw basic emojis in my own UI, but it's refusing to work due to this issue.

I suspect this is a bug for the upstream library
Might be same issue as https://github.com/ocornut/imgui/issues/6302 although that doesn't mention crashing

That's now been fixed, although can't utilize it in imgui-rs yet.


detach command failed with an unexpected error, TypeError: NoneType object is not iterable

Hi,
I am using Azure Kubernetes Services(AKS) with Windows Server containers (in Preview - version 1.14.0). I am following this doc to try and detach my standard SSD AzureDisks from my windows nopepools which run on virtual machine scale sets.
I run the cmd az vmss disk detach --resource-group myResourceGroup  --vmss-name myScaleSet --lun lunNumber (I got a message saying -n is deprecated, use --vmss-name instead) and got this error.

Any ideas?
Also, when a pod is deleted and restarted in AKS and gets put on another node (VM), does the AzureDisk automatically detach from the deleting pod and attach to the new created pod? I'm trying to see how convenient an AzureDisk is for storing persistent data in case of VM or pod failure in AKS
Thanks!

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

ID: 572ce9c7-8ca7-a7c3-2b76-0883025cbb5c
Version Independent ID: 96ee5f8c-0a94-3ce4-0ce9-cdec7f48cba0
Content: Tutorial - Create and use disks for scale sets with Azure CLI
Content Source: articles/virtual-machine-scale-sets/tutorial-use-disks-cli.md
Service: virtual-machine-scale-sets
GitHub Login: @cynthn
Microsoft Alias: cynthn

Hi @lingtham Thank you for your feedback! We will review and provide an update as appropriate.

@lingtham VMSS is automatically created and managed by AKS. If you want to delete the volume then do it through kubectl.
It is not recommended to change the settings of VMSS which is attached to AKS.
Yes, Azure disk will detach and attach to the new pod automatically. Azure disks are RWO(disk can be attached to only one POD at a time), so you need to have deployment strategy as Recreate considering there will be little downtime.
Here Recreate will delete the old pods (volume is free to be attached) and then creates new pods (volume is attached automatically).

Is there no command I can use to just detach the disk?
And what would be the kubectl command to delete the disk? I tried to delete the disks in Azure Portal but it would not let me because the disks are attached to a VM, which is why I am trying to detach them first.

@lingtham Please use this command to check the persistent volumes kubectl get pv.
Use this command to check the persistent volume claim to ensure no POD is using this persistent volume claim kubectl get pvc.
Then use this command to delete kubectl delete pvc  azure-managed-disk.
Once you delete the PVC if the PV has Recalim Policy as Delete then the Volume will be automatically deleted.

Both of these commands return no resources found so I'm guessing they're not persistent volumes. kubectl delete pvc azure-disk reutnrs a persistentvolumeclaims not found error. I didn't create a persistent volume claim for the disks, they're static disks, made following this doc.
Again, I tried deleting them on Azure Portal but it won't allow me because they are attached to a VM. How do I DETACH them then delete or would there be a kubectl command to delete regular disks, not PVCs.

@lingtham Thanks for providing the information and pointing to the document that was followed by you.
I have reproduced the issue and was successful in deleting the Static Disk attached to the Cluster.

Wait for sometime and you can see the Disk coming back to Unattached state on the portal(refresh the blade)
Delete the Disk from portal (refresh the blade) and the disk will be deleted.

The disk is attached to the VM and not to the POD, because of the file format issue which was already reported by you in #34509

Yes, deleting my deployment and then deleting the disks works. I was hoping for a less disruptive way to detach the disks but it makes sense. Thank you for your help!


Bug: vertical alignement in menu

Hi  👋
The elements in the menu aren't aligned correctly. I don't know how to fix that.

            Features

            Plateform

            FAQ

Thanks in advance.
Hugo.

Your code looks good here: https://play.tailwindcss.com/0uBhOqc3Ew
Are you sure there aren't any other CSS affecting your elements?

Ok, I just find the issue. There was a space-y-2 in my css that affect the menu-horizontal. Thanks for the response.


ESP32-C3 SHA-256 comparison failed (won't boot)

Welcome to HomeSpan!
Apple HomeKit for the Espressif ESP-32 WROOM and Arduino IDE

** Please ensure serial monitor is set to transmit
Message Logs:     Level 0
Status LED:       Pin 5
Device Control:   Pin 6
Sketch Version:   n/a
HomeSpan Version: 1.4.2
Arduino-ESP Ver.: 2.0.2
ESP-IDF Version:  4.4.0
ESP32 Chip:       ESP32-C3 Rev 3 single-core 4MB Flash
ESP32 Board:      esp32c3
PWM Resources:    6 channels, 4 timers, max 14-bit duty resolution
Sodium Version:   1.0.12-idf  Lib 9.4
MbedTLS Version:  mbed TLS 2.16.11
Sketch Compiled:  Dec 30 2021 19:45:55
Device Name:      HomeSpan LEDs
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x8 (TG1WDT_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x403867b6
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x420
load:0x403ce000,len:0x90c
load:0x403d0000,len:0x236c
SHA-256 comparison failed:
Calculated: ccb0d00bac7e84e1d90a12e4f75f4ab6c5f7e71bb209afd5819c4c9557a6db71
Expected: c9cf160580940ec7801c73b16423824e72ad12055c732e83ce66332240af42a7
Attempting to boot anyway...
entry 0x403ce000

Welcome to HomeSpan!
Apple HomeKit for the Espressif ESP-32 WROOM and Arduino IDE

This error message seems to occur with any ESP32-C3 sketch, unrelated to HomeSpan.  However, it seems the error may be in the error message itself since programs seems to work fine anyway.  May want to make note of this on the Arduino-ESP32 GitHub site (if they are not already aware).

I ran a different example and it seems to work? I'm not sure why the first sketch continuously restarts..
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x420
load:0x403ce000,len:0x90c
load:0x403d0000,len:0x236c
SHA-256 comparison failed:
Calculated: ccb0d00bac7e84e1d90a12e4f75f4ab6c5f7e71bb209afd5819c4c9557a6db71
Expected: c9cf160580940ec7801c73b16423824e72ad12055c732e83ce66332240af42a7
Attempting to boot anyway...
entry 0x403ce000

Welcome to HomeSpan!
Apple HomeKit for the Espressif ESP-32 WROOM and Arduino IDE

** Please ensure serial monitor is set to transmit
Message Logs:     Level 0
Status LED:       Pin -  *** WARNING: Status LED Pin is UNDEFINED
Device Control:   Pin -  *** WARNING: Device Control Pin is UNDEFINED
Sketch Version:   n/a
HomeSpan Version: 1.4.2
Arduino-ESP Ver.: 2.0.2
ESP-IDF Version:  4.4.0
ESP32 Chip:       ESP32-C3 Rev 3 single-core 4MB Flash
ESP32 Board:      esp32c3
PWM Resources:    6 channels, 4 timers, max 14-bit duty resolution
Sodium Version:   1.0.12-idf  Lib 9.4
MbedTLS Version:  mbed TLS 2.16.11
Sketch Compiled:  Dec 30 2021 19:55:22
Device Name:      HomeSpan LightBulb
*** HomeSpan Info ***
➤ Accessory:  AID=1
➟ Service AccessoryInformation:  IID=1, UUID="3E"
⇨ Characteristic Name("My Table Lamp"):  IID=2, UUID="23"
⇨ Characteristic Manufacturer("HomeSpan"):  IID=3, UUID="20"
⇨ Characteristic SerialNumber("123-ABC"):  IID=4, UUID="30"
⇨ Characteristic Model("120-Volt Lamp"):  IID=5, UUID="21"
⇨ Characteristic FirmwareRevision("0.9"):  IID=6, UUID="52"
⇨ Characteristic Identify(0):  IID=7, UUID="14"
➟ Service HAPProtocolInformation:  IID=8, UUID="A2"
⇨ Characteristic Version("1.1.0"):  IID=9, UUID="37"
➟ Service LightBulb:  IID=10, UUID="43"
⇨ Characteristic On(0):  IID=11, UUID="25"
Range Check: No Warnings
Configured as Bridge: NO
Service                         UUID         AID  IID  Update  Loop  Button  Linked Services

AccessoryInformation              3E           1    1      NO    NO      NO  -
HAPProtocolInformation            A2           1    8      NO    NO      NO  -
LightBulb                         43           1   10      NO    NO      NO  -
*** End Info ***
Accessory ID:      2A:A8:2D:2A:94:27                               LTPK: 99AF5F879B2B4AAFA35AC6C0C00140860B964ABED189BDAF92829206C6411C08
No Paired Controllers
Accessory configuration number: 1
*** WIFI CREDENTIALS DATA NOT FOUND.  YOU MAY CONFIGURE BY TYPING 'W '.
HomeSpan LightBulb is READY!

Check the pins you defined for the LED and Control in the first sketch. GPIO6 is a special pin and input enabled depending on fuse settings on the chip.  May want to try a different pin in case that is the issue.  GPIO5 for the LED should be fine.
In your second sketch the Control and LED pins are not defined, so no issue with picking a "bad" pin.

I'm such a noob, thanks!


Initial commit for http paths match rules

Description
Add support for HTTP path matching. The path match may be either exact or prefix. If multiple matches are specified then they are OR'd together.
Sample
apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
  name: database
spec:
  selector: app == 'database'
  ingress:
    - action: Allow
      source:
        serviceAccounts:
          names: ["summary"]
      http:
        paths:
         - exact: /v2/keys
         - prefix: /v2/keys/accounts
  egress:
    - action: Allow

---

NOTE: @caseydavenport feel free to add other reviewers.

@saumoh I noticed a new commit but it doesn't seem to have addressed all my comments.  Please let me know when it's ready for another look.


[new series] DevOps

[x] ci cd
[x] github action

[x] unit test post link
[ ] integration test post link
[x] implementation

[x] unit test

[x] github action post link
[ ] integration test post link

[ ] integration test

Add detailed explanation to unit test
Add mock implementation experiment code to unit test


Add missing dependency image_geometry

@PerrineAguiar PTAL

The pinhole_camera model (link) depends on it.

@PerrineAguiar Thanks for your review. I addressed your comments.

LGTM, thanks for the quick answer.


'Restore Grid Defaults' Action ungroups grids

Context Menu item "Restore Grid Defaults" will ungroup your grid, even though the code driven default is actually to have the grid grouped.
Easily reproduced in toolbox activity widget, or "Grids -> Grouped Columns" example.

In both Toolbox examples above, the code-driven default is actually null - the groupBy is set after the GridModel is initialised through a separate bindable on the model. The 'Restore Grid Defaults' action is working correctly.
I've opened a PR to adjust the Toolbox example and activity widget to set groupBy when initialising the GridModel, and to bind the controls to the GridModel's observable groupBy rather than a separate bindable.
https://github.com/xh/toolbox/pull/554


Menu Entry Swapper Customizable Shift-Click Teleport Items Bugged

I have always used Custom Shift Click to wear my Amulet of Glory with Teleport item enabled so I can click to Rub, but now that is broken with all the teleport jewelry. I have found a workaround by doing shiftclick Rub and normal click to wear but I miss my old setup. Please fix this bug or let me know if it was changed on purpose.

Ah, didn't see you submitted this as I was working on my bug report.
I am also quite annoyed with the change.

I'm happy to add this as a separate issue if you'd prefer, but I also noticed the "claim-slime" entry swap got mixed up in the restructure. It turns on when you check "trade", rather than "claim-slime".
Cheers for all of the menu entry swap updates thought, it looks so much cleaner!

I'm happy to add this as a separate issue if you'd prefer, but I also noticed the "claim-slime" entry swap got mixed up in the restructure. It turns on when you check "trade", rather than "claim-slime".
Cheers for all of the menu entry swap updates thought, it looks so much cleaner!

Can you test https://github.com/Adam-/runelite/commit/597bbc6b1c51dd8f357eed1befc596a14a2e651d? it should fix this issue.

I'm happy to add this as a separate issue if you'd prefer, but I also noticed the "claim-slime" entry swap got mixed up in the restructure. It turns on when you check "trade", rather than "claim-slime".
Cheers for all of the menu entry swap updates thought, it looks so much cleaner!

Can you test Adam-@597bbc6? it should fix this issue.

How do I use this script? Do I download it and drag and drop? Sorry, I am quite new to this stuff. I am just a casual user after all.

Don't worry, I've tested it and can confirm it fixes the teleport item issues.

fixed in 31c66294f09bb8fefd1691601bf4cd7906864779


ci: add various scan & enforce them

Add a GHA composite action that runs Snyk and Snyk Code

Add aforementioned action to the CI job. In the case of the CI, the goal is only to report (so this is why there's a continue-on-error). The enforcing is done using the checks that this generates. You can see an example in the coveo/cli: https://github.com/coveo/cli/pull/794/checks?check_run_id=6525846881. The boon of this method is that it allows PR to come in if they do not worsen the project (so if the project were to have a vuln detected, it will not grind the CI to a halt).

Add the action to the CD, but this time, it'll crash if there's unaddressed vulnerability.

For Snyk dependency analysis: vuln has to be fixed or addressed using Snyk UI.
For Snyk Code and CodeQL, use the GitHub Code Scanning Alert UI.

fixes #20

Needs #36 to resync package-lock.json, which will allow snyk dependency scan to work properly

I'm really not that knowledgeable in Github actions, but it seems like we repeat a lot of code?

Oh yeah. :feelsgood: . There's the concept of composite actions, that I wanted to use for that... But they do not support the continue-on-error option. So I was forced to repeat.
Tho I'll check again it seems it's been added very very recently. OneMoreTry ™

e.g. of the end results. SnykCode, Snyk Open Source are enforced (i.e. cannot merge if red)


unable to install customized quickstart image

Describe the Bug
Tried to change the DOCKER_ORG, DOCKER_IMAGE and DOCKER_TAG in the Makefile file, build the container and then install it using make install but it tries installing the cloudposse/atmos image instead of the customized one.
Expected Behavior
Running make install should install by customized image
Steps to Reproduce
Clone the repo, patch the Makefile and build the container image
$ git clone
$ cd examples/quickstart
$ sed -i -e 's/DOCKER_ORG ?= cloudposse/DOCKER_ORG ?= myorg/' Makefile
$ sed -i -e 's/DOCKER_IMAGE ?= $(DOCKER_ORG)\/atmos/DOCKER_IMAGE ?= $(DOCKER_ORG)\/myatmos/' Makefile
$ make init build

Try to install the image
$ make install
# Installing newatmos from cloudposse/atmos:latest...
Unable to find image 'cloudposse/atmos:latest' locally
docker: Error response from daemon: pull access denied for cloudposse/atmos, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

# Failed to install newatmos
# If this is not due to file system permissions, please
# check for known issues and consider reporting the failure at
#    https://github.com/cloudposse/geodesic/issues

Try: sudo make install
make: *** [Makefile:35: install] Error 1

==> The default cloudposse/atmos image is used instead of the customized one.
Changing the following section of the Makefile from
install:
	@docker run --rm $(DOCKER_IMAGE_NAME) | bash -s $(DOCKER_TAG) || (echo

to
install:
	@docker run --rm -e DOCKER_IMAGE -e DOCKER_TAG $(DOCKER_IMAGE_NAME) | bash -s $(DOCKER_TAG) || (echo

will fix the issue, I'll provide a pull request soon.
Screenshots
No response
Environment
No response
Additional Context
No response

#612 introduces a devcontainer and simpler demos to get started. I think this is the direction we'll go, instead of investing in the tutorial repo.


Iluminate/Mail sending batch email using Mailgun SMTP

I am trying to get Batch Sending to work over SMTP, but even though I'm sending to multiple recipients and I've specified user variables (and the variables are getting replaced successfully in the email that is sent), every single recipient shows up in the To: field of the resulting messages at the receiver.
Email code (below):

Mail::send('emails', ['body'=> $bodyMsg], function($message) use ($fromAddr, $fromName, $toAddr, $subject, $recipientVariables){
                $message
                    ->from($fromAddr, "Coach %recipient.lead_coach%")
<EMAIL_ADDRESS><EMAIL_ADDRESS>                    ->subject($subject);
                $message->getSwiftMessage()->getHeaders()->addTextHeader('X-Mailgun-Recipient-Variables', $recipientVariables); // json encoded string
            });

I'm sure that 'X-Mailgun-Recipient-Variables' value is added to the header. For your reference see below
Message-ID<EMAIL_ADDRESS>Date: Mon, 24 Oct 2016 10:47:58 -0400
Subject: Testing Mailgun
From: "Coach %recipient.lead_coach%"
To<EMAIL_ADDRESS><EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailgun-Recipient-Variables<EMAIL_ADDRESS>{"first_name":
 "alana","email": "velmurugan@proisc.com","lead_coach": "Merle","unique_id":
<EMAIL_ADDRESS>{"first_name": "al","email":
 "bright@proisc.com","lead_coach": "Chris","unique_id": 213702}}

I put in a mailgun trouble ticket yesterday (after 24 hours) still there is no reply from them. I got another resource from here (http://stackoverflow.com/questions/37948729/mailgun-smtp-batch-sending-with-recipient-variables-shows-all-recipients-in-to-f?rq=1) and it also not worked for me.
So please anyone can help out on this.

Please try on the forums, this repo is for bug reporting only.

Since I'm a new user of laravel, can you please share forum url?


PR: Set python_min environment variable for subrepo conda package builds

Building a subrepo conda package will fail if python_min is not defined either as an environment variable or in meta.yaml, e.g. qtconsole (see conda-forge/qtconsole-feedstock#61).

@meeseeksdev please backport to 6.x


Data in the init callback is returned as String

We should return a nice JSON, not an ugly string

we can't do this for backwards-compatibility. we return data_parsed as well, which is nice json

I believe data_parsed is actually a string. Is that not the case? I'd recommend adding a new, basic data return which is the JSON.

no. data is a string, data_parsed is an object
what do you mean by "adding a new, basic data return which is the JSON"

if that's the case, no need.


Missing run button for tests with the same title

In our sources, create two tests e.g.:
	test('a', () => {
	});
	test('a', () => {
	});

The tests run fine and this doesn't appear to be forbidden by mocha:

However, in the editor, only the second test has a run button:

cc @jrieken @hediet

This is because they look identical to the test extension, so the last one wins. When Mocha reports test results, even to the raw 'reporter' interface, it does so only by using the completed title of the test, so in the results I could not distinguish between two identically named tests.

@connor4312 I created the issue because I ran into this 2-3 times in the past. I think I might be using a pattern where I duplicate a test in order to write a new one. The missing run icon made me think that testing is not flaky and made me go back to the command line. Only yesterday I realized the root cause of the problem is the title duplication. I agree that having two tests with the same title is unreasonable and doesn't need to be supported. But would it be possible to show a squiggle, or render the buttons and then run both tests, or some other solution? It's just the current solution made me think testing is flaky, because there's no indication that the title is duplicated, especially with tests which have many lines and don't fit in a viewport.


[ERROR] :: 429 Client Error: Too Many Requests for url。 I get an error when I get too many tweets

Is there any good solution?

Apparently you ran out of api rate limits. I recommend you to keep an eye on the rate limits. Usually the rate limits gets renewed in every 15 minutes, but again it may vary in some cases, so please keep on checking these rate limits. You can check #29
You can also disable the pagination and handle the requests manually, check the example code.


Change state for a entity

Could there be an option to change the state of an entity?

@lukasgarcya please try executeService method to execute an action, resulting in the state updation of the given entity.


feat: add exporter and podmonitor for kibana

Signed-off-by: disaster37<EMAIL_ADDRESS>

Fix issue #27


Issue with TC-2018-1  (build 58245)

Since I updated my TC server plugin is not working anymore.
Seems that matrix tab is not working anymore and build is mark as success while child build are failing (event with "wait child build finished" activated)

map.get(SettingsConst.PROP_CONST_BUILD_PARAMETERS) is giving null ptr in MatrixBuildRunTypePropertiesProcessor class

Hello @fduvoux. Thanks for your contribution to this plugin. I'm really excited to see people use it.
But, unfortunately, I don't have time to work on it, at least for now. If you can create a PR with fix, I will look on it and merge.

Hi,
I created a PR with a fix I made last night.
CI is not working but seems not to be related to my PR.
If you can have a look, it works pretty well on my 2 TC servers.
Regards,

Fabien DUVOUX
On Mon, Jul 16, 2018 at 3:45 PM Vitaliy Gergel<EMAIL_ADDRESS>wrote:

Hello @fduvoux https://github.com/fduvoux. Thanks for your contribution
to this plugin. I'm really excited to see people use it.
But, unfortunately, I don't have time to work on it, at least for now. If
you can create a PR with fix, I will look on it and merge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/presidentio/teamcity-matrix-build-plugin/issues/12#issuecomment-405252262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfhCr-HkTeoRtulmRWOu2ZzkoCXrhinks5uHJjxgaJpZM4VQ4ng
.

Looks well. Thanks for you contribution.


ActiveSupport and ActionPack are upgraded

AC

[x] Bump ActiveSupport to at least <IP_ADDRESS> (gem "activesupport", ">= <IP_ADDRESS>")
[x] Bump ActionPack to at least <IP_ADDRESS> (gem "actionpack", ">= <IP_ADDRESS>")

Related to #174

This was done in #186


Add soft-delete and delete functionality on asset

"Ready For Review" checklist

[x] PR title accurately summarizes changes
[x] PR description

Does this fix any open issues?
Yes
What changes are you making?

add commands to handle soft_delete_relations and destroy_with_relations
add Delete button to views/admin/assets/index page
refactor how asset's relationship are soft and hard deleted
added stimulus js controller for admin/assets to handle Spam and Delete buttons. No restore or unspam functionality for now (on purpose)

Why did you implement it this way?

Would like to achieve more explicit logic of when and what gets deleted or updated when asset is marked as soft_deleted.
-app/commands folder helps store logic that is performed ON an asset, but asset doesn't really need to know how to do it. Folders should be created by object (asset, user, track, etc) with class names express the verb of what this command is doing. Example: DeleteAssociations, CreateWaveform.

Is there anything reviewers need to know or pay attention to?
No
Does anything special need to happen for deployment?
No

[x] Optional: Inline github PR comments explaining context of tricky / complicated / unexpected lines so reviewers can follow along.
[x] If appropriate, new tests were added for isolated methods or new endpoints
[ ] All tests green
[ ] Percy changes are purposeful or explained
[x] I booted up the branch locally, exercised any new code I wrote.
[ ] If css was touched, I verified changes are happy on mobile (via Percy is ok)
[ ] ~I opened an issue for any logical followups~

Nice, this stuff is looking solid! 💣
Deja vu from the user soft deletion — if we deploy this then "delete" will mean something different on the track edit page vs. admin page which is maybe dangerously confusing for mods. So we should update AssetsController#destroy to use soft delete as well.

I didn't want to pile all in one PR :) But absolutely can.

We might need to discuss this complicating things with asset soft deletion — https://github.com/sudara/alonetone/issues/653

Note, can't seem to use module Asset
 TypeError:
        Asset is not a module
      # ./app/commands/asset/soft_delete_with_relations.rb:1:in `<top (required)>'

Ahh right, Asset is defined as a class (model).
Some of my clients name commands explicitly like so:
class AssetCommand
  def initialize(asset)
    @asset = asset
  end

  def delete_with_relations
    @asset.comments&.with_deleted&.delete_all
    # ...
  end

  def restore_with_relations
    # ...
  end

  def really_destroy_with_relations

  end
end

That makes for a friendly and direct API: AssetCommand.new(@asset).delete_with_relations
I'm not really sure we will have any more asset related commands coming up in addition to these (waveform can be WaveformCommand otherwise in an AudioFeature namespace) — but if you wanna namespace my vote is "anything but Assets" as that feels unintuitive (operates on 1 asset vs. many assets.)
Another kinda interesting theme — we are finding out that both soft and regular deletion both reliably have "after" callbacks....

Followup: https://github.com/sudara/alonetone/issues/672


Very slow startup. Disable Jupyter checks?

Bug: Notebook Editor, Interactive Window, Editor cells

The Python extensions seems to start very slowly of late, sometimes taking over 20 seconds to become available. One of the things I've noted is that it seems to import jupyer and notebook on every restart
> ~/.pyenv/versions/sdssdb/bin/python -c "import jupyter"
> ~/.pyenv/versions/sdssdb/bin/python -c "import notebook"

Is it possible to disable that check? I'm not using notebooks in any of my projects and ultimately I'd prefer to be able to disable all the notebook features that seems to be dragging the performance of the extension.

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running:                       N/A
Extension version:                               2020.3.71113
VS Code version:                                1.44.0-insiders
Setting python.jediEnabled:               false (although it's slow regardless)
Python and/or Anaconda version:     pyenv 3.8.1
OS:                                                     Linux and Mac
Virtual environment:                         pyenv virtualenv

There is a 'python.dataScience.disableJupyterAutoStart' setting, but that should have no effect on the loading of the extension. It happens after the extension has already loaded. Something else must be making it slower.

I have the same issue with 2020.3.71113 and is very slow/unable to start the Jupyter kernel.

Running  an empty cell should do nothing.

Yeah looks like there's a bug if you run an empty cell before running anything else, it hangs the interactive window. I'll log an issue.

Maybe I made it a bit confusing by creating a bug report against data science. To be clear, I'm not using the Python extension with a Jupyter kernel or to load a notebook. I'm trying to use the extension as an IDE to edit code but I still see how it tries to load jupyter and it has been noticeably slower lately. I have
"python.dataScience.disableJupyterAutoStart": true

in my settings but that doesn't prevent the extension from checking jupyter on start.

Let's validate that it's not our issue.

@albireox
I'd like to get to the bottom of this issue.
Based on your experience the extension takes 20 seconds to load.
Please could you try the following:

Close VS Code
Open VS Code
Open a python file
Wait for the extension to get activated completely ( in your case 20 seconds).
Once done, select the command Developer: Toggle Developer Tools from the command palette.
Please go into the console window and save everything into a file and paste it here.

console.log

I am having this identical issue (20+ second hang at "python extension loading") on both my home and work computer. Here is my console.log and specs from my home computer if it helps:

Jupyter: not installed
Anaconda: not installed
Python: 3.8.2 64-bit
Extension version: 2020.4.74986
VS Code version: 1.44.2
Jedi: same result if it's enabled or not
OS: Windows 10

Version: 1.44.2 (user setup)
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T16:36:23.138Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Closing this issue as, we addressed checking Jupyter when extension loads.


Creating a backend via the console and importing Auth from Cognito causes "auth headless is missing the following inputParams" when running "amplify pull"

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d3cbhlqhrq2d8
Region
us-east-1
Amplify Console feature
Backend builds
Describe the bug

I logged into the AWS console and went to the AWS Amplify console.
I created a new backend and then opened up the Amplify Admin UI for that created backend.
I added Authentication by importing from Cognito. No errors came up during the import. I see the details (user pool id, web client id, native client id, etc.) correctly in the Admin UI.
When I try to pull down the app locally via the CLI, I get the following error --

✖ There was an error initializing your environment.
Failed to pull the backend.
auth headless is missing the following inputParams userPoolId, webClientId, nativeClientId
Error: auth headless is missing the following inputParams userPoolId, webClientId, nativeClientId

Full log from when I run the command --
➜  auth-with-totp-mfa git:(main) ✗ amplify pull --appId d3cbhlqhrq2d8 --envName staging --yes
Opening link: https://us-east-1.admin.amplifyapp.com/admin/d3cbhlqhrq2d8/staging/verify/
✔ Successfully received Amplify Admin tokens.
Amplify AppID found: d3cbhlqhrq2d8. Amplify App name is: auth-with-totp-mfa
Backend environment staging found in Amplify Console app: auth-with-totp-mfa
✔ Successfully pulled backend environment staging from the cloud.
✖ There was an error initializing your environment.
Failed to pull the backend.
auth headless is missing the following inputParams userPoolId, webClientId, nativeClientId
Error: auth headless is missing the following inputParams userPoolId, webClientId, nativeClientId
    at ensureHeadlessParameters (/Users/keledwin/.nvm/versions/node/v14.16.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/src/provider-utils/awscloudformation/import/index.ts:1269:11)
    at Object.headlessImport (/Users/keledwin/.nvm/versions/node/v14.16.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/src/provider-utils/awscloudformation/import/index.ts:1126:40)
    at importedAuthEnvInit (/Users/keledwin/.nvm/versions/node/v14.16.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/src/provider-utils/awscloudformation/import/index.ts:903:18)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at updateConfigOnEnvInit (/Users/keledwin/.nvm/versions/node/v14.16.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/src/provider-utils/awscloudformation/index.js:50:72)
    at /Users/keledwin/.nvm/versions/node/v14.16.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/src/index.js:306:22

Expected behavior
It should not produce an error. If everything looks correct and can be "built" inside the Admin UI without issue, then pulling it down should not produce an error at all.
Reproduction steps
Reproduction steps mentioned in the bug description ^^
Build Settings
No response
Additional information
No response

Also - while the Authentication configuration shows correctly the in Amplify Admin UI, it does not show correctly in the AWS Amplify Console. When I click on the dropdown for my staging backend environment and choose "View details", the Overview shows that the Authentication category has been added. However, if I click on the Authentication tab to see the details of the category, it does not show anything and instead gives me instructions to run amplify add auth via the cli.
But! When I look at the network requests, I see a call to s3 that is fetching the Authentication details for the Amplify app, and it does correctly get the Cognito configuration, including the UserPoolId, AppClientID, and AppClientIDWeb.
So it looks like somewhere...someone's wires are getting crossed and not detecting these clearly present and existing values.

Workaround - was able to weirdly get past this issue by setting some environment variables on the command line for each of the missing values and then omitting the --yes flag from the amplify pull command. But this behavior is clearly still buggy.

Hope to see this fixed. I am facing this issue.


Linux server use....

I have uploaded my cpp's and .exe as well as several test cases. Code compiles on linux, however ./coogsive "input=filename" isnt showing any output. I have the substring var set to 6 in code so it should be checking after "input= for its filename.  Am I not compiling correctly?

So here's what you do and then let me know if you still have any issues. I'm writing this from step 1 assuming you have nothing setup. Feel free to skip forward to where the steps apply to you.

Download a FTP client as it gives you a nice GUI/File Explorer ... I use WinSCP if your on MacOS something similar is bound to exist after a quick google search. https://winscp.net/eng/download.php

Download a Zip file of HW1s repository (the green clone/download button right corner) and extract the test cases folder.
https://github.com/uhcs2320/hw01

Login to WinSCP and create a temporary folder named "testing."

Put the test cases inside this folder and copy only the CPP file for your program into the test cases folder itself.

Open up your choice of a terminal/command prompt/type thing. If you have Putty installed pressing CTRL + P inside of WinSCP launches Putty.

Navigate into directory using cd "testing/test-cases"

Compile using: g++ -std=c++11 -o coogsive -I ./ *.cpp
//If it successfully compiles now is a good time to type "clear" (no quotation marks) and press enter before the next step

Run it against all 20 test cases using:
for A in a b c d e f g h i j k l m n o p q r s t ; do echo "Test case: $A"; ./coogsive "input=test-${A}.1.txt" | diff - test-${A}.out.txt ; echo "" ; done

Have Fun!

@ShortCircuit865 Please don't list out the letters like that, it is just sloppy and could lead to careless mistakes. Use {a..t} instead in the condition of the for loop in step 8.
@MoJoShMaN I suspect you are not reading the file correctly; try this to read the file name
std::string name(argv[1]);
name.substring(name.find('=') + 1);    // Grab everything after the equal sign
name.substring(0, name.find('\"'));    // remove ending quotes if any

You have to check your readFile method.
Cleaning it up a little may help, for example, you define an int variable i that is not utilized.
Also, it seems that you are reading the position for ; but you're not expecting a semicolon as part of the filename. The idea was to adapt the example Param.cpp to fit your code.
The example code given to you is not going to solve things for students directly.
I mentioned that I'll looked at your code, but there were things coming up at the office and home, so only now I'm able to give you some suggestions, sorry about that.
I noticed that using global variables is facilitating things in (at least one of) your recursive functions, which is useful. However, if you find getting stuck, then review how global variables are utilized in places such as the readFile method. Global variables are handy but can easily cause trouble due to difficulty of keeping track of where their values can change.
Last comment: I think that the name of the file should be hw2 instead of hw02.

@NeoISE I copied the method Meza provided in the first hw0 assignment and simply replace "uhday" with "coogsive"
So I'm not very experienced with stuff of the sort.
Out of curiosity I tried what I think you were suggesting a few different way without any success.
Are you saying I should wrap the letters in brackets like so? {a, b, c, d, ....}
or literately {a..t}

@ShortCircuit865 The literal one, in Bash or any other shell (i.e. zsh) will expand that out as is to a sequence of letters.


Translation

Hi!
How can I view the card in my language?
It is not specified in the documentation...
Thank you

Probably you can find solution here


Better error reporting when loading malformed styles

When maperture can't load a style json because it's got a syntax error, we get an "Error: Style was not found" message in the layer picker, but on the console I can see it was actually a syntax error. In my case: main.js:8 SyntaxError: Expected ',' or '}' after property value in JSON at position 88582
Possible improvements:

could we detect the difference between a missing or inaccessible file (which would get the "Style was not found" error) versus a file that is an unparseable style (which would get something like "Style syntax error" or "Style file could not be parsed" message)?
I also notice that a parsing error in one of the local styles caused all of my local styles to disappear from the picker. Is it possible to have the picker maintain the parsable styles, and maybe indicate if one of the local styles has an error (maybe strikethrough the name of the style in the picker?)

I also notice that a parsing error in one of the local styles caused all of my local styles to disappear from the picker. Is it possible to have the picker maintain the parsable styles, and maybe indicate if one of the local styles has an error (maybe strikethrough the name of the style in the picker?)

@almccon https://github.com/stamen/maperture/pull/117 should provide better error messages, but for this issue, my guess would be this is happening due to a setup step in the local.js file of your client repo rather than in maperture code. Without seeing the specific implementation, can you tell me if there is there logic in there that looks like:
let localServerIsRunning = false;
const localUrlPath = 'http://localhost:8000/styles';

try {
  const response = await fetch(`${localUrlPath}/cool-style/style.json`);
  const style = await response.json();
  if (style) {
    localServerIsRunning = true;
  }
} catch (err) {}

I know this logic has been a problem elsewhere (I've unfortunately written this logic in places), so if this is what it looks like, then erroring on that one style may cause logic further down in local.js to determine that no local styles should be available.
Instead we would want to implement something like:
const localServerIsRunning = window.location.origin.includes('localhost');

If this doesn't appear to be the problem, then maybe we can open a ticket in the client repo for me to see the implementation this is a problem with and we can open a new upstream ticket here if necessary.


copper delivery

the term for this is
GO:0015680    intracellular copper ion transport
intracellular copper delivery | exact
but I don't think this is transport, it's  just insertion?
see
Cerqua C, Morbidoni V, Desbats MA, Doimo M, Frasson C, Sacconi S, Baldoin MC, Sartori G, Basso G, Salviati L, Trevisson E. | Related Articles
COX16 is required for assembly of cytochrome c oxidase in human cells and is involved in copper delivery to COX2.
Biochim Biophys Acta. 2018 Jan 18;. [Epub ahead of print]
PMID: 29355485

@ValWood - this term is used for experimental annotations for several genes, some of which look like they  match the definition, e.g. FET4, CTR2. Therefore, I think that this term needs to continue to be what it is.

Gene/product
Gene/product name
Annotation extension
Contributor Organism
Evidence

COX17
Copper metallochaperone that transfers copper to Sco1p and Cox11p
SGD
Saccharomyces cerevisiae S288C
IDA

COX17
Copper metallochaperone that transfers copper to Sco1p and Cox11p
SGD
Saccharomyces cerevisiae S288C
IMP

FET4
Low-affinity Fe(II) transporter of the plasma membrane
SGD
Saccharomyces cerevisiae S288C
IMP

CTR2
Low-affinity copper transporter of the vacuolar membrane
SGD
Saccharomyces cerevisiae S288C
IMP

Atox1
antioxidant 1 copper chaperone
RGD
Rattus norvegicus
IMP

CCS1
Copper chaperone for superoxide dismutase Sod1p
SGD
Saccharomyces cerevisiae S288C
IMP

CCS
Copper chaperone for superoxide dismutase
PINC
Homo sapiens TAS

COPT5
AT5G20650
TAIR
Arabidopsis thaliana
IMP

I took a quick look at the paper you mention, but it is not clear to me what COX16 is doing.
If you'd like to propose a new term specifically for 'copper delivery', please propose a new term with all the appropriate details:
name: [term name]
namespace: BP
def: "definition text "[definition dbxrefs, e.g. GOC:abc, PMID:12345678]
is_a: [GO term]
relationship: [any other appropriate relationships]

I'm fine with letting @pgaudet take care of this if she wants, but considering that longstanding GO practice is that the meaning of the term is defined by the definition, currently:
Def: The directed movement of copper (Cu) ions within a cell.
I think that keeping this term with this existing meaning and removing the synonym, IF needed, would be more consistent with our stated practice.

Yes but it's in the wrong place in the ontology in this case.....

...in addition most of the usage is for the "chaperone", not the transmembrane transporter.
Probably obsoletion is the only way to deal with it in this case.

see also https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3875331/

Hello,
Looking at these more closely, it seems like the odd balls in the annotations are FET4 and CTR2. Here's what I did:

Changed parent to 'protein maturation' (as an aside: but is this really OK under 'gene expression'?)

also changed definitions of the corresponding MF to "Directly binding to and delivering copper ions to a target protein." (also for the parent 'metallochaperone' and sibling 'iron chaperone')

There is no corresponding iron delivery term, however there is 'protein maturation by iron-sulfur cluster transfer', so we could rename 'intracellular copper ion delivery' to 'protein maturation by copper ion transfer'?

If that works I will implement the changes and ask an annotation review for FET4 and CTR2.
Thanks, Pascale

I agree with these proposed changes. @Antonialock  could you glance over and see if this looks OK? (Antonia has been working on our iron-sulfur pathway and so should spot any problems with these).
Re the protein maturation under gene expression, the rationale is that:
gene expression def:
The process in which a gene's sequence is converted into a mature gene product or products (proteins or RNA). This includes the production of an RNA transcript as well as any processing to produce a mature RNA product or an mRNA or circRNA (for protein-coding genes) and the translation of that mRNA or circRNA into protein. Protein maturation is included when required to form an active form of a product from an inactive precursor form.
I think it is correct.

Hi @Antonialock,
This ticket is only about the copper chaperone ("intracellular copper ion delivery" - what I proposed to call "protein maturation by copper ion transfer"). I think that 2 and 4 are the same thing (or I dont know if they can really be distinguished): I think proteins carry copper in the intracellular environment and the copper can be transferred to specific target proteins
(I dont see how 'import into cell' and 'homeostatic control ' are related).
Thanks, Pascale

Looking at the ontology structure, I went ahead and renamed 'intracellular copper ion delivery' to ' protein maturation by copper ion transfer'

Pascale


Arrival and Departure: Animate the vehicle annotation's position

Expected behavior
The vehicle's position should be animated as new data comes in
Actual behavior
There's no animation
Steps to reproduce the behavior
Open the arrival and departure controller; wait a minute or two.
Screenshot of the issue (if applicable)

FWIW, due to limitations in some vehicle GPS update rates, on Android we only animate the change in the buses position on the map if it's less than a distance threshold - from VehicleOverlay:

/**
* If a vehicle moves less than this distance (in meters), it will be animated, otherwise it
* will just disappear and then re-appear
*/
private static final double MAX_VEHICLE_ANIMATION_DISTANCE = 400;

After staring at the map for a while and seeing some buses cross lakes, drive straight through buildings, and take other routes that they obviously couldn't in real life due to a large distance between position updates, this is the distance that I chose to limit that behavior while still providing a smooth transition for more frequent updates.

Awesome, thanks Sean :)


IPv6 support?

ipV6 / node17-Issue
When trying to connect to my FireTV 4k stick I get this error message:
firetv.0 (55777) can not connect to <IP_ADDRESS> Error=connect ECONNREFUSED ::1:5037
Describe the bug
Adapter has issues with IPv6, it seems.
To Reproduce
Adapter start gives:
2021-11-25 14:18:58.972  - info: firetv.0 (124245) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.firetv, node: v17.1.0, js-controller: 3.3.20
2021-11-25 14:18:59.138  - error: firetv.0 (124245) can not connect to <IP_ADDRESS> Error=connect ECONNREFUSED ::1:5037

<IP_ADDRESS> is the correct adress for my FireTV Stick 4k.
Versions:

Adapter version: firetv - v1.0.0
JS-Controller version: 3.3.20
Node version: v17.1.0
Operating system: Raspberry OS 'Bullseye'

Can the adapter be forced to connect via ipv4 and not ipv6? I have no clue about javascript, but can it happen that 'localhost:5037' is adressed and that will be resolved to ::1:5037 on my ipv6/ipv4 machine. Can <IP_ADDRESS> used instead?

This seems to be the case for me as well:
https://github.com/DeviceFarmer/adbkit/issues/209
Can the solution:
As a short term solution, users of this package can explicitly pass '<IP_ADDRESS>' as the host configuration option.
also be applied to this adapter?

I installed backported versions:
adb=1:29.0.6-20~bpo11+1
android-libcutils=1:29.0.6-20~bpo11+1
android-libbase=1:29.0.6-20~bpo11+1
android-liblog=1:29.0.6-20~bpo11+1

I will need sometime to figure out if the adapter is compatible with these ipv6-enabled adb version.

https://github.com/iobroker-community-adapters/ioBroker.firetv/pull/46

PR merged


OpenBLAS : Program will terminate because you tried to start too many threads.

After some time, I often get this error.
There is nothing special or heavy, that was executed.

Thanks for sharing this very strange bug.... I had never seen this error in any of the tested OS distributions. Can you please share the following info:

OS (and version)
numpy version
scipy version
PyQt5 version
OpenBLAS version.

I will try to reproduce this behavior.

openSUSE Leap v15.0
numpy 1.14.5
scipy 1.1.0
exostriker 4acfa3cebbdb162217f3a3d33e001f8f2ec8aa2c

PyQt5 and openblas (/usr/lib64/libopenblas_pthreads.so.0): How do it get it?

for PyQt4
from PyQt5.Qt import PYQT_VERSION_STR
print("PyQt version:", PYQT_VERSION_STR)
on my openSUSE Leap v15.0 i have the same scipy and numpy...
can you try:
import numpy as np
np.show_config()

What I often do is pressing fit and switching between Simplex and L-M.

The only thing that is sufficiently different between yours and my setup is that I am using 'PyQt version:', '5.5.1'. The problem must be in numpy, or scipy, which both depend on OpenBLAS.
Switching between L-M and Sipliex is harmless, but when you press "fit" it does some operations mostly done with numpy. Scipy is only used to find the peaks on the GLS periodogram.
So I am almost sure the problem is in some numpy operation, but I can't reproduce the error at the moment.... When the error occurs, did the GUI crashes or you only get a crash message on the stdout/stderr window? This is an important lead.
Looking at the OpenBLAS issue box on the GitHub I ended up here:
https://github.com/xianyi/OpenBLAS/issues/1735
people try different things with mixed success like:
export OMP_NUM_THREADS=1
export VECLIB_MAXIMUM_THREADS=1
export OPENBLAS_NUM_THREADS=1
if these do not work, you may consider reinstalling OpenBlas

I added
os.environ["OPENBLAS_MAIN_FREE"] = "1"
at the beginning of es_gui.py. This has no effect on my system(s), but might improve others like yours. Please report if you keep seeing this weird OpenBLAS related crash.

Mathias, I believe this is a problem with your system. I am closing, but, if someone else experiences
the same problem, please re-open.


GEODE-3544

JSON parsing failed for short data type & base class setter method is not used
when key having base class  property in it
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ X] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ X] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ X] Is your initial contribution a single, squashed commit?

[ X] Does gradlew build run cleanly?

[ X] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@jaredjstewart do you see any problems with these changes?


Empty output

I have used mkdocs2pandoc > Reader.pd but this was excluding "empty" sections such as

Practical WetLab:

Week 1:

Tuesday:

ExperimentX: 'Practical/WetLab/Week1/Tuesday/ExperimentX.md'

In which I would like to also have Practical WetLab, Week1, Tuesday, ExperimentX in the PDF.
Now I was trying this program and all I get is
Practical WetLab {: .page-title}
Week 1 {: .page-title}
Tuesday {: .page-title}
Wednesday {: .page-title}
The actual content is missing?

Fixed in https://github.com/twardoch/mkdocs-combine/releases/tag/<IP_ADDRESS>

(At some point mkdocs started using 'unicode' filenames while this tool only expected 'str', it works now)

I'm getting the same issue as @jjkoehorst. I'm on release <IP_ADDRESS> and get the same empty output.
Anything else I could be doing wrong?


HP EliteBook 9470m - Updated Model Folder with BIOS F.70

HP released BIOS Update F.70 for the EliteBook 9470m. I have updated the Model folder to reflect this. The folder also contains all of the other files as they are. Make it easy for a commit.
References:
https://ftp.hp.com/pub/softpaq/sp87001-87500/sp87466.html
****
HP EliteBook Folio 9470m.zip

@thecatdidit Thanks for the update!
For the future, please only include files that have changed in the ZIP, this make integrating it for me a little easier.
Your BIOS-Update.txt was somewhat off I think. The BIOS version noted was still F.69, although this was about F.70.
Also, your files got the the -p"@@PASSWORD_FILE@@" parameter removed, so anyone with a BIOS password can't use the file. I guess you removed it because you don't use a BIOS password, but that's not necessary. If BIOS Sledgehammer detects a @@PASSWORD_FILE@@ parameter and the current machine does not have a BIOS password set, the parameter is silently removed so it will work in any case.

Files added, closing issue

@thecatdidit No problem, I'm glad you informed me about the new BIOS and that I only want the changes is because I'm a lazy sloth :)
But if you want to warm up with GitHub, look up pull requests. They make changes really easy, both for the creator and the integrator.

@texhex Will do. In fact, I have another model to include, so I'll check it out.


python310Packages.cement: 3.0.6 -> 3.0.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cement is: "CLI Application Framework for Python"
meta.homepage for python310Packages.cement is: "https://builtoncement.com/"
meta.changelog for python310Packages.cement is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.8 with grep in /nix/store/6zi11ac3dg0blai7rsbh3l2bgh2qdkrv-python3.10-cement-3.0.8
found 3.0.8 in filename of file in /nix/store/6zi11ac3dg0blai7rsbh3l2bgh2qdkrv-python3.10-cement-3.0.8

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.cement
python39Packages.cement

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6zi11ac3dg0blai7rsbh3l2bgh2qdkrv-python3.10-cement-3.0.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cement https://github.com/r-ryantm/nixpkgs/archive/b9b9d3c98c9096b394b93923a5b429b945864673.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6zi11ac3dg0blai7rsbh3l2bgh2qdkrv-python3.10-cement-3.0.8
ls -la /nix/store/6zi11ac3dg0blai7rsbh3l2bgh2qdkrv-python3.10-cement-3.0.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.cement
python39Packages.cement

Maintainer pings
cc @eqyiel for testing.

Result of nixpkgs-review pr 187367 run on x86_64-linux 1

2 packages built:

python310Packages.cement
python39Packages.cement


Implement Pass-through Handlers For Peer Vote and Timeout Msgs

Current dependencies on/for this PR:

feature/proof-of-stake

PR #830

PR #848

PR #849

PR #850

PR #851

PR #852

PR #853   👈

This stack of pull requests is managed by Graphite.


[BUG]:  picam(hq) stops working when installing photobooth

Describe the bug
installed raspberry pi os (latest version as of today) and checked if the picamHQ worked as expected via libcamera-still, which it did.
updated via apt and finally installed photobooth via the shell script.
Steps to reproduce the behavior
to my surprise after the installation finished and i rebooted i cant get an image via libcamera-still
ERROR: *** no cameras available ***
or gphoto2 --capture-image
Could not detect any camera *** Error (-105: Unknown model)
Expected behavior
working picam via libcamera and/or gphoto2
Photobooth Version
latest via installscript (v4 i guess)
Browser and browser version
No response
Operating System
No response
Did it work before?
Yes
Latest working version
No response
Additional context
i dont know if it worked before as intended, i just found this project.

i forgot to add: i flashed a new sdcard to confirm the camera was working as it was sitting there with the cabling the way it was when it didnt work with the sdcard that had photobooth on it. it worked :-/ i am confused.
i tried the usual things like killing the gvfs process and so on.

Blacklisted while by accident installing gphoto2 preview?
sudo rm /etc/modprobe.d/v4l2loopback.conf
sudo rmmod v4l2loopback
sudo reboot

Pi cameras aren't supported by gphoto2, no need to care about gphoto2.

Blacklisted while by accident installing gphoto2 preview?
sudo rm /etc/modprobe.d/v4l2loopback.conf
sudo rmmod v4l2loopback
sudo reboot

that worked like a charm! you made my day and/or party.
any way this can get integrated in the installer? it was completely vanilla and happened two times so it isnt some kind of fluke.
thanks again for the great project, will donate to the seals!

info "Do you want to install a service to be able to stream your camera to?"
    info "Your camera must be supported by gphoto2 for liveview."
    info ""
    echo "Your options are:"
    echo "1 Install gphoto2 webcam service"
    echo "2 Install go2rtc and needed service to stream your camera via http"
    echo "3 Don't install a service to set up preview for gphoto2"
    info ""
    ask_yes_no "Please enter your choice:" "3"
    info ""
    if [[ $REPLY =~ ^[1]$ ]]; then
        GPHOTO_PREVIEW=true
        MJPEG_PREVIEW=false
        info "### We will install a service to set up a virtual webcam for gphoto2."
        warn "### Note: This will disable other webcam interfaces on a Raspberry Pi (e.g. Pi Camera)."
    elif [[ $REPLY =~ ^[2]$ ]]; then
        GPHOTO_PREVIEW=false
        MJPEG_PREVIEW=true
        info "### We will install a service to set up a mjpeg stream for gphoto2."
    else
        GPHOTO_PREVIEW=false
        MJPEG_PREVIEW=false
        info "### We won't install a service to set up preview for gphoto2."
    fi

You choosed 1 Install gphoto2 webcam service, while  3 Don't install a service to set up preview for gphoto2`  would have been your option. The webcam service blacklists Pi Camera Kernel module.

got it, my bad!


Wait for prometheus to be running before restarting operator

@enmasse-ci run tests testcase=MonitoringTest

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: MonitoringTest
TOTAL: 1
PASS: 1
FAIL: 0
SKIP: 0
BUILD_NUMBER: 153


Add section about imports

references #3

Thanks again!

No worries! You might get some more of these as I also need the webhook endpoints exposed in order to manage the webhooks with the GitHub provider ;)

That sounds like a great idea! I look forward to it. :grinning:


docker update to 1.9 in CentOS causes conflict with Origin <= 1.2

Docker 1.9 is now the default install from CentOS Extras.  Due to instabilities with OpenShift < 1.2 it has been marked with a conflict.  Origin 1.1.4 is still current in COPR repo from Origin/EPEL.
To install correctly on CentOS 7 the Docker version must be restricted to 1.8.x in master-boot.sh and node-boot.sh unless the Origin version >= 1.2

Origin in COPR:
https://copr-be.cloud.fedoraproject.org/results/maxamillion/origin-next/
epel-7-$basearch/

Docker bug 1304038
https://bugzilla.redhat.com/show_bug.cgi?id=1304038

This has been resolved with the release of Origin 1.1.6 which uses Docker 1.9


Skype attachment

Hi all!
I have a problem. The object contains list of attachments if incoming message has one. But ContentUrl don't work. For example object have
ContentUrl=https://df-apis.skype.com/v2/attachments/0-neu-d5-faac5db55162e82d9261c8777066c6d3/views/original
or
ThumbnailUrl=https://df-apis.skype.com/v2/attachments/0-neu-d5-faac5db55162e82d9261c8777066c6d3/views/thumbnail
But if open a url in browser, then it's empty.

Similar to #662. Skype attachments are secured by bot JwtToken, you need bot JwtToken as a bearer token to be able to access those urls.


proposing an better ui for the web development section

The web development section of our platform is a crucial resource for developers of all skill levels. To optimize its impact and accessibility, we propose a refined user interface (UI) that prioritizes simplicity, intuitiveness, and responsiveness. The new design will streamline navigation, improve content discovery through organized categories, and introduce interactive elements for better learning engagement. Our goal is to deliver an aesthetically pleasing and functional experience, ensuring that users can focus on learning and applying new skills with ease.
This description conveys both the purpose and approach for the UI improvement. How does it sound?

Ok


Update main.js

New Features and Usage

If state of FHEM Device is function of switch (on/off), then fhem.x.xxx.state_switch will be automatically created. (use for VIS and Material)
dummy as switch: attr xxxx setList on:noArg off:noArg
If state alias exist, the name of the channel will be alias.
fhem.x.info.Settings: select content of log.info
fhem.x.info.Info:  NumberObjects= Number of Objects in FHEM, roomioBroker=true/false
fhem.x.info.Commands: sendFHEM=send command to FHEM, resultFHEM=result of the command, lastCommand=last command from ioBroker to FHEM
After synchronization FHEM: new Device in FHEM will be automatically created.
After synchronization FHEM: delete Device in FHEM  will be automatically deleted.
Set function light (TYPE=HUEDevice), heating (model=HM-CC-RT-DN), temperature (unit=°C), switch(state_switch) during synchronization (tested Material Adapter)

I have no possibility to test it.
:)


Finish user stories

As a [role]
I need [function]
So that [benefit]
Details and Assumptions
* [document what you know]

Acceptance Criteria
gherkin
Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

labeled as for current sprint


Update mutations.md

Description

The docs refers to non existent gql. This PR aims to rewrite gql -> strawberry
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[x] Documentation

Issues Fixed or Closed by This PR

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Codecov Report
Patch and project coverage have no change.

Comparison is base (8c38f96) 87.76% compared to head (9c89698) 87.76%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #319   +/-   ##
=======================================
  Coverage   87.76%   87.76%
=======================================
  Files          33       33
  Lines        2942     2942
=======================================
  Hits         2582     2582
  Misses        360      360

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


(to) github.com/teamhephy

and quay.io/kingdonb (the temporary home of the build-time dependencies
This one is to merge if you please @Cryptophobia
We can switch everything from quay.io/kingdonb to quay.io/ [the team account] before the first release, but ... this way for now
We are going to have to make these github.com/deis -> github.com/teamhephy go-dep changes all over the place to make the build processes work though, I'm afraid.
I'm not sure how many more repos have this issue, but I'm not in a hurry to update them all at once.  Let's make these kind of updates on each repo individually, only as we're ready to do smoke testing of each component.

This is addressed and closed for now via https://github.com/teamhephy/controller-sdk-go/pull/4


www/nginx, security/tor: hotfix for P4 related issues

See https://forum.opnsense.org/index.php?topic=23771.0 for details.
Router in controller has issues with snake case action names which worked in the previous Phalcon version.
This only affects nginx and tor.
I made this in three commits on purpose -> to be used with the OPNsense patch utility.

merged, thanks


second Iceland source

From same dataset using other street name column - "skip": "true"

New Zealand screenshot


Update Composer dependencies (2020-09-23-00-04)

Visual regression test passed!
View the visual regression test report


Cherry pick a merge commit fails

I tried to use the "Cherry Pick" action on a merge commit and got the following error:
7:35:51 AM Cherry-Pick Error
           error: Commit 6076f2987fcb7e108a293ebdd22d8926e2330451 is a merge but no -m option was given.
           fatal: cherry-pick failed

The version control console shows the following commands:
07:40:56.995: git fetch --progress origin refs/changes/33/6433/1
From ssh://git.XXX.ch:29418/YYY
 * branch            refs/changes/33/6433/1 -> FETCH_HEAD
07:40:58.585: git cherry-pick -x -n 6076f2987fcb7e108a293ebdd22d8926e2330451
error: Commit 6076f2987fcb7e108a293ebdd22d8926e2330451 is a merge but no -m option was given.
fatal: cherry-pick failed

Merge-commits can only be checked out. There is now an action available for doing this.


Revisit icon hash calculations for Echoes

The formula in calculateIconHashForAllCards needs support for echo effects and bonus icons.

We can actually eliminate the hash altogether now that we have a array-based auxiliary value table.

This isn't technically complete yet. Complex Numbers wasn't the only spot where we were relying on the hash.

Never mind, I guess Complex Numbers was the only thing that depended on it!


rm segfault workaround in example

The comment in the first actors example mentions that a dummy return was needed to avoid a segfault with "await async". This doesn't seem to be true anymore -- at least, the example doesn't segfault and produces the same output for me either way (running on Pop!_OS 22.04 Linux).

@DestyNova thanks!
CI is failing due to unrelated things so I can't just merge this. We get spurious segfaults, which is from a change I merged yesterday, see #1290. The other is because we currently presume CI is running for this repo, opened #1291 for that. Regardless, nothing you need to think of - I'll fix and thanks again :)

@DestyNova I just merged #1292 which addresses the brew-macos problem in #1291. You should now be able to submit PRs to this repo and have CI run successfully for them. It naturally won't magically update this particular PR since your branch is based before the fix in #1292.

Oh I need to update the branch, of course.

This is merged through #1303 which is (re)based on main after #1302 to avoid the compilation problems described by #1290. Thanks again @DestyNova


startsAt and endsAt of webhook‘s json format

#Alertmanager config problem:
Can i change startAt's format ,it's rfc3339 default ? i want change it to CST
"alerts": [     {       "labels": <object>,       "annotations": <object>,       "startsAt": "<rfc3339>",       "endsAt": "<rfc3339>"     },

@shitWang I am not aware of any way you can change this through configuration. What is your use case to do so?

The codes  is not configuration .it‘s a json string of alertmanager sending alert  to webhook url (i use webhook receiving alert）and i want get time of alert that is "startAs" var with CST but it's rfc3339...
so... i want to ask how do change that？？？

@shitWang I am sorry, but I don't understand your question. Can you elaborate further?

Since the time is in  rfc3339, you should be able to use a datetime library in your webhook receiver to decode the date and print it in CST (or any other timezone you want)

So,it's only changed in my webhook receiver ？can not in server by configuration？

Correct. Internally, Prometheus uses UTC for everything, so it's up to the receiver to display it in the preferred format.

Ok. thinks for help


Scenario testing - Restarts and upgrades

In the acapy tools repo there is some really useful testing using docker containers that allows testing of upgrade scripts and restarts. https://github.com/hyperledger/aries-acapy-tools/tree/main/askar_tools/tests/e2e.
It should be possible to support this in the scenarios directory from acapy itself. It would be awesome to be able to test a supported upgrade path from the last LTS version and test a few different restarts with changed configurations such as making public dids and using seeds etc.

@jamshale  are there instructions for running the e2e tests?

In [acapy-tools](https://github.com/openwallet-foundation/acapy-tools) I don't think there is any instructions :/ . It's pretty simple though. I just poetry install and then navigate to askar_tools and run poetry run pytest ..
You can use other pytest commands to run an individual test.

ok thanks, I'll add this to the README

Probably more useful to be able to test this with a back-end postgres database rather than having to worry about import/export for sqlite wallets (and then the tests could run in a separate docker container, and just point to the external database).

I agree. For this scenario testing against a postgres db would be easier and better. The sqlite testing was much more difficult with restarts in acapy-tools. Also would be good to have postgres getting tested more here in general.

@jamshale I'm getting errors running the tests.
I ran poetry install --with=dev (to include the dev dependencies, basically acapy-controller, which failed with the following error:
HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with url: /indicio-tech/acapy-minimal-example.git/info/refs?service=git-upload-pack (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)')))

I updated the project to use acapy-controller = "~=0.2.0" (the published version of the library) and then the install worked.
After running poetry run pytest . however everything failed:
FAILED tests/e2e/test_export.py::TestPgExport::test_export_pg - aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host selfserve.indiciotech.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:...
FAILED tests/e2e/test_export.py::TestPgExport::test_export_sqlite - docker.errors.APIError: 409 Client Error for http+docker://localhost/v1.43/containers/create?name=alice: Conflict ("Conflict. The container name "/alice" is already in use by container "81137e408a975071c15cfb032...
FAILED tests/e2e/test_mt_convert_to_mw.py::TestMultitenantConvertToMultiwallet::test_conversion_pg - aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host selfserve.indiciotech.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:...
FAILED tests/e2e/test_mt_convert_to_mw.py::TestMultitenantConvertToMultiwallet::test_conversion_sqlite - docker.errors.APIError: 409 Client Error for http+docker://localhost/v1.43/containers/create?name=admin: Conflict ("Conflict. The container name "/admin" is already in use by container "14b1b2cf31f1c7e6c9f075f70...
FAILED tests/e2e/test_tenant_import.py::TestTenantImport::test_tenant_import_pg - aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host selfserve.indiciotech.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:...

Any thoughts?  Looks like a certificate error and then the container ... already is use is because a previous test failed.

(the above is in the askar_tools directory, for the tests under acapy_wallet_upgrade some work and some fail)

What's running at selfserve.indiciotech.io:443?

Ya. These test in acapy-tools aren't the best, but the container process that allows restarts is what I wanted to replicate for acapy.
I got around the hardcoded stuff in the library for the ledger here https://github.com/openwallet-foundation/acapy/blob/main/scenarios/examples/presenting_revoked_credential/example.py#L50.

I notice that the test container logic starts up a bunch of services within the python code.  Typically in other projects we do this within a docker-compose file, and then pass parameters in (overrides) via environment variables.
I'd like to convert this project to use a similar structure - docker compose and then build a docker image to run the unit tests.
Before I dive into the code, does this make sense?  It should make it easier to use these components within other repo's (like aca-py).

Yes. That would be good. In the scenario tests in acapy we use docker compose files. It's really just about how to persist the storage containers for the length of the test and restart the agents with a different image and configs. The acapy-tools e2e tests do this so I thought we could use a similar design.

It's really just about how to persist the storage containers for the length of the test and restart the agents with a different image and configs.

I'll work on updating the acapy-tools tests to use docker and think about how to do this for the aca-py scenario tests ...

The reason the tests start the container in python is because that seemed like the best way to control starting and stopping containers. I also generally prefer to keep it simple and just use docker compose wherever possible but, at the time, I was not finding good solutions that permitted both simple docker compose and controlling startup parameters and starting and stopping the containers. So docker compose got nixed.

@jamshale I'm getting errors running the tests.

FYI managed to fix the certificate issue with this:  https://stackoverflow.com/questions/52805115/certificate-verify-failed-unable-to-get-local-issuer-certificate

@jamshale  I think the scenario testing approach will have to change to support acapy restarts (especially if we are shutting down one acapy version and then starting up another).
Right now the scenario test all start their agents via docker compose, so there is no mechanism for the test (which runs in one container) to restart the agent (which runs in a different container).  (The test creates an instance of an acapy_controller.Controller to control the running agent.)
One possibility is to change the acapy-test container to include the acapy_controller.Controller wrapper, and then expose an additional endpoint to start, stop or restart the agent.  (The agent would then be controlled from within the python code, similar to how the askar_tools tests work.)  Of course all the other protocols would have to be exposed in a similar way.
Another possibility is to ditch the use of docker compose to start the agents and just manage all the agents within python code, similar to how the askar_tools tests work.
One wrinkle is the requirement to support different versions of acapy - i.e. startup an older version of acapy, run some scenarios, shut down the agent and then start up a new agent (with a newer acapy version) pointing to the same wallet.  (Or running a wallet upgrade in between.)
@jamshale  @dbluhm  any thoughts?

What if it was separate from the scenario tests?

I'll setup a separate test ...  One option for the "acapy version" issue is to have two Controller containers based on two different acapy versions (for example the latest acapy release and the local acapy source code) and then starting an agent in one container, executing some protocols, shutting down the agent, and then starting a new agent from the other Controller container (pointing to the same wallet).
The upgrade (if we're running a wallet upgrade) could be run directly from the example code.

FYI I'm putting together a HackMd to iron out the details before I start coding:
https://hackmd.io/@H1HgS-RdQMukDzKQtR7iNg/rywTQukEkg

@jamshale @swcurran @dbluhm  ...
After a bit of beating my head against a wall I've come to the conclusion that the way we're testing the aca-py tools vs the aca-py scenario tests are basically incompatible:

for aca-py tools, the tests are run locally and the docker containers are started/stopped from within the python code (using https://docker-py.readthedocs.io/en/stable/)
for the scenario tests, there is a python script that is run locally, but it's just a "driver" that uses docker compose to start some containers, run tests, and then shut down the containers

The python docker library use by aca-py tools tests can't be run within a docker container (can't connect to docker on the host) so it can't be used within the scenario tests, the way they are currently structured.
A couple of options:

we could write a process that starts/stops the aca-py agent, and run this in a container (this was my original thought, but it can't use the docker library so would need to run the agent as a sub-process, the way the alice/faber demo does it)
we could modify the whole test approach, so that the driver script (https://github.com/openwallet-foundation/acapy/blob/main/scenarios/conftest.py) runs multiple steps for each scenario - ie. start containers, run tests, stop agent(s), run upgrades, start agent(s), etc.

Either of these would be fairly complicated so not sure it would be worth the effort, vs just using the aca-py tools repo to do the upgrade testing.
Thoughts?

Ok. That's a bit of a bummer. I didn't expect it to be this complicated. Maybe it would be easier to just have a test in acapy-tools that tests the upgrade to latest acapy with the scenarios we think are important. I still think it would be very useful for migration stuff like anoncreds upgrade and the upcoming DIDInfo work.
We could have a github action the clones acapy-tools and runs the test on a release like we are doing with OATH right now.

I'm not sure the python docker library will work under github actions (it needs a docker instance to talk to)

Ok. Maybe we can leave this for now. I didn't intend for it to be a lot of work. Maybe we can think of another way to test these scenarios.

It's possible to share the docker socket with a container to enable it to use docker on the host machine. This usually involves adding a volume to the container. A quick ChatGPT generated example:
version: "3.8"

services:
  docker-client:
    image: docker:latest
    container_name: docker_client
    privileged: true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./workspace:/workspace
    environment:
      - DOCKER_HOST=unix:///var/run/docker.sock
    entrypoint: ["sh", "-c", "while true; do sleep 3600; done"]

# Example Usage:
# To run a Docker command inside the container:
# docker exec -it docker_client docker ps

It's possible to share the docker socket with a container to enable it to use docker on the host machine. This usually involves adding a volume to the container.

I ran a quick test and this worked!  I'll put together a simple example and open a PR.

I'm working on a simple test scenario with an agent restart (including updating the agent from the previous release to the latest code).  The stop/start is working but the networking config on the new agent isn't working yet :-S  I've created a draft PR in case anyone wants to take a look.
Note that the new agent is started by docker directly rather than docker-compose, so docker-compose doesn't know anything about it.  This will complicate the test cleanup a bit ...

Explicitly creating a docker network might help with that. There's a lot of gotchas in docker networking though -- hopefully we can work through this one

Explicitly creating a docker network might help with that. There's a lot of gotchas in docker networking though -- hopefully we can work through this one

You can use indy-test-automation as a reference, it sets up a docker network in several places (GHA workflows and scripts) for the purpose of setup and testing of a network.  Search for docker network.

Turns out I didn't need to create a network just explicitly connect to the network docker compose already created ...
The restart is now working (shut down alice aca-py 1.0.1 and then start a new alice with acapy-test (built from local code) connecting to the same database.  Docker logs are all screwy because some containers are started by docker compose and some aren't, and also the post-test cleanup will be a bit trickier.
I'll work on including an upgrade step in between the alice shutdown and restart.

Good news (or bad news) - I've implemented a fairly robust anoncreds upgrade test and I'm now getting an error in the upgrade step.  I'll dig into this but it looks like an aca-py issue.  Alice has issued 6 credentials to 3 holders (2 each) and revoked 3 credentials (1 each).  I set the revocation registry size to 5 so a new registry should have been created during this scenario.
See PR #3410
alice-1           | 2024-12-19 18:57:15,708 aiohttp.access INFO <IP_ADDRESS> [19/Dec/2024:18:57:15 +0000] "POST /anoncreds/wallet/upgrade?wallet_name=alice HTTP/1.1" 200 248 "-" "Python/3.10 aiohttp/3.11.10"
alice-1           | 2024-12-19 18:57:15,710 acapy_agent.wallet.anoncreds_upgrade INFO Upgrade in process for wallet: alice
alice-1           | 2024-12-19 18:57:15,720 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:15,728 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading records for wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:15,728 acapy_agent.wallet.anoncreds_upgrade INFO Retry attempt 1 to upgrade wallet alice
alice-1           | 2024-12-19 18:57:16,745 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading records for wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:16,745 acapy_agent.wallet.anoncreds_upgrade INFO Retry attempt 2 to upgrade wallet alice
alice-1           | 2024-12-19 18:57:17,759 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading records for wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:17,760 acapy_agent.wallet.anoncreds_upgrade INFO Retry attempt 3 to upgrade wallet alice
alice-1           | 2024-12-19 18:57:18,776 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading records for wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:18,776 acapy_agent.wallet.anoncreds_upgrade INFO Retry attempt 4 to upgrade wallet alice
alice-1           | 2024-12-19 18:57:19,799 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading records for wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:19,799 acapy_agent.wallet.anoncreds_upgrade INFO Retry attempt 5 to upgrade wallet alice
alice-1           | 2024-12-19 18:57:20,814 acapy_agent.wallet.anoncreds_upgrade ERROR Error when upgrading records for wallet alice : cannot access local variable 'is_active' where it is not associated with a value
alice-1           | 2024-12-19 18:57:20,814 acapy_agent.wallet.anoncreds_upgrade ERROR Failed to upgrade wallet: alice after 5 retries.
alice-1           |                 Try fixing any connection issues and re-running the update

OK. Thanks for testing this. I wasn't super confident about some of this more complicated revocation stuff. There's some subtle differences between revocation with anoncreds.
Maybe we can keep the failing test as a separate branch, and I can try and look at it soon.

Doing a very quick review of the aca-py upgrade code, I suspect the issue is with the record for the "used up" revocation registry (used for the first 5 credentials).

Found the issue!

Looks like a mistake here https://github.com/openwallet-foundation/acapy/blob/main/acapy_agent/wallet/anoncreds_upgrade.py#L485. Needs to have the is_active variable declared before calling the function.
Should have done more revocation testing with the multitenant upgrade and would have caught it.

This is awesome — nice work!  Testing is really helpful!  Having a good ways to test — amazing.


Password test is broken

I just setup a new instance and used pwgen -y 23 to generate a password.
Odly enough
it gives an error for the string
ahj!ahtieThoh3ieh5bohwa
but if you cut the first 3 charaters
!ahtieThoh3ieh5bohwa
it is considered right again.
using 0.4.5 of harbor.

Password has a length restriction between 7 and 20 characters.

Well the UI does not tell ("At least 8 characters with 1 lowercase letter, 1 capital letter and 1 numeric character.") nor does it limit
<input type="password" class="form-control" id="password" ng-model="user.password" ng-change="vm.reset()" name="uPassword" required password>

We've updated message about this status, it will release at 0.5.0.
Dup #1010


fix(client)!: safe and unsafe raw queries

Fixes https://github.com/prisma/prisma/issues/7142
Fixes https://github.com/prisma/prisma/issues/8189
TODO:

add runtime checks (exceptions)

BREAKING CHANGE

@Jolg42 the current changes are TS-only changes, we'd like to add an error for JS users too (runtime).

Tracked in https://github.com/prisma/prisma/issues/8808 now