Mac OS 10.8.2 STM32VL Discovery error

Hi guys! U've made great work!
But I have some errors when trying to launch st-util (with --stlinkv1 or not - doesn't matter) : WARN src/stlink-sg.c: libusb_claim_interface() failed
Full log with --stlinkv1:
macbookpro:stlink.git Disminder$ ./st-util --stlinkv1
libusb: 0.000000 info [process_new_device] allocating new device for location 0x14800000
libusb: 0.000075 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000082 warning [process_new_device] Got unknown device speed 3
libusb: 0.000096 info [process_new_device] found device with address 128 at 128-05ac-8007-09-00
libusb: 0.000472 info [process_new_device] allocating new device for location 0x1a000000
libusb: 0.000517 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000524 info [process_new_device] found device with address 1 at 001-05ac-8006-09-00
libusb: 0.000860 info [process_new_device] allocating new device for location 0x1d000000
libusb: 0.000898 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000905 info [process_new_device] found device with address 1 at 001-05ac-8006-09-00
libusb: 0.001229 info [process_new_device] allocating new device for location 0x14000000
libusb: 0.001272 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.001279 info [process_new_device] found device with address 129 at 129-05ac-8007-09-00
libusb: 0.001588 info [process_new_device] allocating new device for location 0x1d100000
libusb: 0.001777 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.001792 info [process_new_device] found device with address 2 at 002-8087-0024-09-00
libusb: 0.002137 info [process_new_device] allocating new device for location 0x1a100000
libusb: 0.194109 info [process_new_device] allocating new device for location 0x1d180000
libusb: 0.194462 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.194485 info [process_new_device] found device with address 3 at 003-0424-2512-09-00
libusb: 0.194936 info [process_new_device] allocating new device for location 0x1d181000
libusb: 0.383382 info [process_new_device] allocating new device for location 0x1a110000
libusb: 0.676523 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.676566 info [process_new_device] found device with address 3 at 003-05ac-8510-ef-02
libusb: 0.677064 info [process_new_device] allocating new device for location 0x14200000
libusb: 0.677318 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.677336 info [process_new_device] found device with address 1 at 001-0483-3744-00-00
libusb: 0.677746 info [process_new_device] allocating new device for location 0x1d182000
libusb: 0.678559 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.678582 info [process_new_device] found device with address 5 at 005-05ac-0263-00-00
libusb: 0.678942 info [process_new_device] allocating new device for location 0x1d181300
libusb: 0.864914 warning [darwin_cache_device_descriptor] could not retrieve device descriptor 05ac:8286: device not responding. skipping device
libusb: 0.865751 info [darwin_open] device open for access
libusb: 0.866251 error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
2013-01-29T22:12:18 WARN src/stlink-sg.c: libusb_claim_interface() failed
libusb: 0.866964 info [event_thread_main] thread exiting
Error: could not open stlink device
Error: could not open stlink device

Without --stlinkv1:
macbookpro:stlink.git Disminder$ ./st-util
2013-01-29T22:13:07 WARN src/stlink-usb.c: libusb_claim_interface() failed

Doesn't know what to do with this problem. In Windows everything is OK (that's mean that my Discovery work's correctly). Please help, if u can :)
Best wishes, Disminder.

I have the same problem on Ubuntu 15.04 64bit with a Nucle-F4011RE. Any ideas, how to fix this?

+1 for Ubuntu 15.10 with STM32 Nucleo for F4

I have the same problem with mac OS 10.11.2 ...
would be really nice if someone would know a solution for this! :)

This is possible due to kernel claimed usb device. So libusb/stlink is unable to claim it. Please test with latest v1.2.0 and latest kernel driver.

I'm closing this due to inactivity and the issue is reused by other people which is not Mac OS X related. Feel free to open a new issue when the problem still exists with v1.2.0 or master. Also read https://github.com/texane/stlink/blob/master/stlinkv1_macosx_driver/README.md
Thanks for your contributions!


dev-coner - feedbacks 201016 lecorguille

See: https://github.com/bgruening/training-material/issues/164
Some feedbacks I plan to fix in this PR:
Feedbacks from @abretaud

[x]  a heavy silence fell on the room during the conda packaging hands-on 😄 people were lost and didn't know how to start. So describing a little more the meta.yaml/build.sh would help I think

Feedbacks from @loraine-gueguen

[x] example for macros
[x] some pictures are too small

@loraine-gueguen Can you point me those?

some pictures are too small

ping @abretaud: is it good for you?

[X] a heavy silence fell on the room during the conda packaging hands-on 😄 people were lost and didn't know how to start. So describing a little more the meta.yaml/build.sh would help I think

I like it!

@lecorguille The pictures that were too small last time at screen as far as I remember: the ones on the second and third slides in the wrapper section.

[X] some pictures are too small
Done for the three first pictures of the wrapper section

Ping @abretaud I need your returns Lapinou 🐰

ping @abretaud: is it good for you?
a heavy silence fell on the room during the conda packaging hands-on 😄 people were lost and didn't know how to start. So describing a little more the meta.yaml/build.sh would help I thi

Much better thanks!

I have just run all the hand-on using a VM that was provided by @chcaron. It's works!
If everybody is ok! @abretaud or @bgruening  can you merge this PR?

:tada:
Thanks!!!!

Houhou!


Pype.py do not boot on import

Issue

if pype.py is (accidentally) imported it will always run boot function which may cause infinite tray execution if it happens on tray initialization

it may cause huge issues due to a bug on different place e.g. whensomething like this is executed __import__(".")

Changes

do not run boot on pype.py import until it's in __main__

I agree with this. @antirotor what do you think?

I agree with it too. Better safe then sorry.


Clarification needed on subgraph naming and labeling for different environments

Hi,
I am currently playing with the federated graph system and trying to understand how to organize multiple projects and environments.
From the documentation, I understand you can have multiple subgraphs with different environments (dev or prod), but it is not working as I expected.
Scenario:
I have a Federated Graph called Animal with two subgraphs (Cat and Dog). Both of these subgraphs are labeled env=development and I want to promote these in a production environment.
Issue:
I attempted to create a new Federated Graph named Animal-Prod labeled env=production. However, I encountered an issue where I couldn't create subgraphs under Animal-Prod with the same names (Cat and Dog) but with the label env=production.
Questions:

Is it a system constraint that prevents creating subgraphs with the same name across different federated graphs, even if they have distinct labels? is the intention to have Cat-dev and Cat-prod
What is the recommended approach for promoting subgraphs from a development environment to production, ensuring that both versions coexist?

Any guidance or clarification on this would be greatly appreciated.

Hello @oerhahon.

You are correct as in we check that subgraphs have a unique name despite having different labels. Since we work with labels which canbe anything given the context we do not have a concept of promoting a graph.
Since you want both versions to coexist, the recommended approach would be to have subgraphs with different names and labels.

Thanks for the clarification.


Static site generation build process breaks when it encounters 'href' string in content json file

Environment

Operating System: Darwin
Node Version:     v18.0.0
Nuxt Version:     3.13.0
CLI Version:      3.13.1
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools, modules, features, tiptap, ignore
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://github.com/majoflosa/nuxt-generate-bug-demo
Describe the bug
Given a nuxt project using content module with .json files as content, and a page in the app that fetches that content:
If a value in these content files contains the string href, the build process will break when generating the  app as a static site by running npm run generate or nuxt generate.
For example, suppose I have a nuxt page that looks like

<template>

Bug Demo: Nuxt Static Site Generation

{{ data }}

</template>

The page will fetch content from a file in content/test.json, which looks like:
{"normalString":"foobar", "errorCase1": "Example Link"}

Trying to generate this static site causes an error:
  ERROR  [nuxt] [request error] [unhandled] [500] ENAMETOOLONG: name too long, open '/Users/mauricio/dev-experiments/nuxt-generate-bug-demo/.nuxt/cache/nitro/prerender/payload_%22https_google.com_%22%3EExample%20Link%3C_a%3E%22,%20%20%22_id%22_%20%22content_test.json%22,%20%20%22_type%22_%20%22json%22,%20%20%22title%22_%20%22Test%22,%20%20%22_source%22_%20%22content%22,%20%20%22_file%22_%20%22test.json%22,%20%20%22_stem%22_%20%22test%22,%20%20%22_extension%22_%20%22json%22%7D%3C_pre'

/"https://google.com//">Example Link",  "_id": "content:test.json",  "_type": "json",  "title": "Test",  "_source": "content",  "_file": "test.json",  "_stem": "test",  "_extension": "json"}
Example Link",  "_id": "content:test.json",  "_type": "json",  "title": "Test",  "_source": "content",  "_file": "test.json",  "_stem": "test",  "_extension": "json"}</pre (12ms)
  │ └── Error: [500] Page not found: /%22https://google.com//%22%3EExample%20Link%3C/a%3E%22,%20%20%22_id%22:%20%22content:test.json%22,%20%20%22_type%22:%20%22json%22,%20%20%22title%22:%20%22Test%22,%20%20%22_source%22:%20%22content%22,%20%20%22_file%22:%20%22test.json%22,%20%20%22_stem%22:%20%22test%22,%20%20%22_extension%22:%20%22json%22%7D%3C/pre

 ERROR  Exiting due to prerender errors.
at prerender (node_modules/nitropack/dist/chunks/prerender.mjs:220:11)
  at async node_modules/nuxt/dist/index.mjs:3628:5
  at async build (node_modules/nuxt/dist/index.mjs:5778:3)
  at async Object.run (node_modules/nuxi/dist/chunks/build.mjs:102:5)
  at async Object.run (node_modules/nuxi/dist/chunks/generate.mjs:60:5)
  at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.b8b195e1.mjs:1648:16)
  at async runCommand$1 (node_modules/nuxi/dist/shared/nuxi.b8b195e1.mjs:1639:11)
  at async runMain$1 (node_modules/nuxi/dist/shared/nuxi.b8b195e1.mjs:1777:7)

Additional context
The exact cause seems to be somewhat inconsistent. In this minimal reproduction example, the error only occurs if the problematic string (in a /content json file) contains href=\"[some url here]\". In a different project, the error occurs if a string contains any instance of href. This issue is written assuming the cause is either the same or similar enough to explain any case.
This error only occurs when trying to generate the static site. The build and dev commands do not throw errors.
Logs
No response

Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏

Hi @danielroe - thanks for the response. I've made several attempts to reproduce this in a pure Nitro project, trying different prerender settings, and haven't been able to reproduce the error.
Something that leads me to think it has to do with the Nuxt environment (or maybe Content module?) is the first line of the error output:
ERROR  [nuxt] [request error] [unhandled] [500] ENAMETOOLONG: name too long, open '/Users/mauricio/dev-experiments/nuxt-generate-bug-demo/.nuxt/cache/nitro/prerender/payload_%22https_google.com_%22%3EExample%20Link%3C_a%3E%22,%20%20%22_id%22_%20%22content_test.json%22,%20%20%22_type%22_%20%22json%22,%20%20%22title%22_%20%22Test%22,%20%20%22_source%22_%20%22content%22,%20%20%22_file%22_%20%22test.json%22,%20%20%22_stem%22_%20%22test%22,%20%20%22_extension%22_%20%22json%22%7D%3C_pre'

It seems the prerender process here is trying to take everything after href= and make it part of the file name in payload_[some suffix here]. These payload files aren't part of the process in a pure Nitro setup (unless there's something I should be doing to prompt building those payload files; happy to hear suggestions, if so).
So far, it looks like in Nuxt, nitro interprets href= as a signal to start creating a new file with the value of that href as the file name, as seen in the next line of the error:
/"https://google.com//">Example Link",  "_id": "content:test.json",  "_type": "json",  "title": "Test",  "_source": "content",  "_file": "test.json",  "_stem": "test",  "_extension": "json"}</pre (12ms)
  │ └── Error: [500] Page not found: /%22https://google.com//%22%3EExample%20Link%3C/a%3E%22,%20%20%22_id%22:%20%22content:test.json%22,%20%20%22_type%22:%20%22json%22,%20%20%22title%22:%20%22Test%22,%20%20%22_source%22:%20%22content%22,%20%20%22_file%22:%20%22test.json%22,%20%20%22_stem%22:%20%22test%22,%20%20%22_extension%22:%20%22json%22%7D%3C/pre

Where we currently see /"https://google.com//"... it would usually show the name of the next file being created, when it's running normal, like /about/_payload.json for instance.
I've never tried setting up projects with just Nitro, so happy to try out suggestions to better attempt to replicate this there.


ref(controller): use the env config instead of directly getting from environment

fixes #338

Current coverage is 46.60% (diff: 0.00%)

Merging #431 into master will decrease coverage by 0.35%

@@             master       #431   diff @@
==========================================
  Files            26         26
  Lines          1118       1118
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            525        521     -4
- Misses          562        566     +4
  Partials         31         31

Powered by Codecov. Last update ac829c0...703df6d

can you try to write unit tests for this if possible? Trying to increase coverage in #437 so it'd be helpful to have this all covered before merging.

@bacongobbler i had added test.Can you review it again.

LGTM even without the change. This is partially blocking #437 as it touches on some of the code I'm directly testing in build.go (in a good way) :+1:


CINFRA: BugFix recovery of views under replication2

Scope & Purpose
Recovery tests on Views are red in Replication2. We found the issue that InvertedIndexes cannot always repeat an operation (replace document with itself) which is what Replication2 Protocol relies on. This all raced with what is still to be recovered from replicated log and what is recovered from rocksdb, and sometimes Replication2 recovers a small amount of operations multiple times.

[x] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.11: (Please link PR)
[ ] Backport for 3.10: (Please link PR)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

Red test is unrelated to change.


[Question] What is the recommended way to get Syntax Highlighting?

First of all, congratulations for this amazing blogging platform that I am glad and proud to use for my blog.
I saw multiple ways to get Syntax Highlighting with Prism.js and Highlight.js (what I am currently using). However, I would like to know if there is some plugin/recommended way to integrate the embedded GitHub markdown using ````` to highlight the code.
Regarding this markdown syntax highlight, I found the plugin ghost-prism-plugin and two closed issues: #1091 and #1431. However, everything seems to be really old, leaving me with the only option of using some custom JS library instead of something integrated with the markdown.
Thank you,
Carlos.

By the way, I open a new issue on purpose and aware of the recommendation of using IRC/Forum to ask questions. I open it to request the integration of the syntax highlighter in Ghost itself. I could participate on such integration submitting a pull request if accepted such idea.

Hi @carlosbaraza :)
As you mentioned, Ghost already supports the markdown for getting syntax highlighting as you can use ````language` to trigger highlighting.
Including a library to do the highlighting itself is a job for your theme. Many themes come with something like prism built in, and some don't. The default theme Casper does not include it.
However, if the theme you're using doesn't support it, and you want to add highlighting without editing the theme you can use the code injection feature to add it by linking to prism via a cdn.
There are also some people voting for this feature on the wishlist but I'm really not sure what we'd do if it gets a lot of votes - maybe add it to Casper, but it seems unnecessary seeing as it's already so easy to do and effectively supported by Ghost itself.
I'm going to close this issue because there's nothing to do here - the only place we could add support would be Casper, which is in a different repo.

Hi @ErisDS ,
Thank you for the quick answer and my apologies for opening a non-sense issue.

@ErisDS Sorry for replying such an old issue.
Is ```language` still available in the latest version?
 I would like to avoid any injected css or js if possible.
Thank you!

@andy1247008998 ```language is supported markdown but you will need to add a client-side syntax highlighting library to your theme or through the Code Injection screen to get syntax highlighting, there's no built-in support for that as it's very much a theme-level concern.


Documentation: Fix out-of-sync codeowners

The default make target is currently failing because 7335755e ("CODEOWNERS: Add ownerships for IPsec team") updated the CODEOWNERS file without regenerating the Documentation/codeowners.rst file. This commit it by regenerating the Documentation copy.
This is covered in CI but as part of the Travis CI build only. I'm guessing we all missed it because we didn't expect tests to cover CODEOWNERS changes, and especially not Travis.
Fixes: https://github.com/cilium/cilium/pull/21567.

Yeah, I must admit I would have thought that the Documentation/ targets would cover this.


Create Outbound OML NK1 Segment

Story
As a public health lab, to be able to make use of received electronic NBS orders, I need the OML NK1 segment included with the order.
Pre-conditions

[x] The required fields are already included in the incoming FHIR.

Acceptance Criteria

[x] The NK1 segment shows up in the outbound OML and has all the required fields.

Tasks
Research

[x] Identify required fields.

Engineering

[x] Update sample test file to include patient contact information
[x] Map NK1 segment

[x] NK1-1: Set ID - NK1 (SI)
[x] NK1-2: Name (XPN)

[x] NK1-2.1: Family Name (FN)
[x] NK1-2.2: Given Name
[x] NK1-2.3: Second and Further Given Names or Initials Thereof

[x] NK1-3: Relationship (CWE)

[x] NK1-3.1: Identifier
[x] NK1-3.2: Text
[x] NK1-3.3: Name of Coding System
[x] NK1-3.9: Original Text

[x] NK1-5:  Phone Number (XTN) - not required but already present

[x] NK1-5.3: Telecommunication Equipment Type
[x] NK1-5.5: Country Code
[x] NK1-5.6: Area/City Code
[x] NK1-5.7: Local Number
[x] NK1-5.12: Unformatted Telephone Number

[x] Copy patient address and telecom to patient's contacts' address and telecom in our application.

Definition of Done

[x] Documentation tasks completed

[x] Documentation and diagrams created or updated

[x] Implementation guide (/ig folder)

[x]  Add ig provenance (changelog) updates for this story specifically (if applicable)

[x] ADRs (/adr folder)
[x] Main README.md
[x] Other READMEs in the repo
[x] If applicable, update the ReportStream Setup section in README.md

[x] Threat model updated
[x] API documentation updated
[x] Source code documentation created when the code is not self-documenting

[x] Code quality tasks completed

[x] Logging added where useful
[x] Code refactored for clarity and no design/technical debt
[x] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies
[x] Code is reviewed or developed by pair; 1 approval is needed but consider requiring an outside-the-pair reviewer
[x] Code quality checks passed

[x] Security & Privacy tasks completed

[x] Security & privacy gates passed

[x] Testing tasks completed

[x] Load tests passed
[x] Unit test coverage of our code >= 90%

[x] Build & Deploy tasks completed

[x] Build process updated
[x] API(s) are versioned
[x] Feature toggles created and/or deleted.  Document the feature toggle
[x] Source code is merged to the main branch

Research Questions

Optional: Any initial questions for research

Decisions

Optional: Any decisions we've made while working on this story

Notes

RS fhir -> hl7vs KS video

This Story helps complete the requirement:
MVP-REQ-08 - Each intermediary will support at least one format for outbound orders


How to get MangedEntity objects for hosts inside cluster using pyVmomi ?

Hi Experts,
I would like to call "AddMonitoredEntities()" method (which is exposed by http://pubs.vmware.com/vsphere-6-5/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.HealthUpdateManager.html)
This method accepts hosts from clusters as monitoredEntites. I am able to get "ManagedObject" for hosts but could not figure out yet how to convert or get hosts "managedEntity" instead?
I was able to do using Java SDK though. I will try further using pyVmomi.
Any help/guideline/snippet on this would be useful.

When you can try to do in the case you have a list that is explicitly 1 type, e.g.
>>> objs
(ManagedObject) []

is using the .Array() function to convert it.
Using the above object
>>> vim.ManagedEntity.Array(objs)
(vim.ManagedEntity) []

Obviously you'd have a non-empty list, but it should work.


About the Clip + FT results

Thanks for your excellent work, but I'm curious about the Clip + FT experimental settings you posted. What data and which part of the parameters do you use for fine-tune ?

We finetune the image backbone of CLIP. Training data are the same with baselines. We find it is hard for finetuning to achieve better performance. This mayby because the dataset is small for finetuning CLIP.


Update CSS and bring up to date with main

This PR merges in main, and simplifies and improves the layout of the AWV component, and makes it more workable on small displays.

This looks really good on my desktop. It has some issues on my phone, but I think we can consider this a "my phone" problem. I don't think it's realistic to display this much information on such a small screen.
It also loads pretty slowly on my phone. The app itself takes ~5-10 seconds to load (with Safari on the slower end), and then opening the AWV takes another 5-10 seconds (although this branch loads a cloud data layer from the get go).
If you think there are small tweaks we can make without too much trouble, here are screenshots of how this looks on my phone.

The map is so small that if you try to zoom out to see the entire US, the cloud layer has the weird gappy grid.

The table info rolls off the side of the screen.

Possible fixes:

[ ] Quick: Widen the dimension of the AWV dialog. Maybe just make it 100%.
[ ] Quick: Slightly reduce font size on mobile throughout the AWV.
[ ] Less quick: move the % cloud cover scale bar to be horizontally above or below the map.

I've fixed a bunch of minor issues, and now it is fullscreen on mobile. i am allowing smaller font-sizes now, by using it's own definition of --default-font-size. the minimum value can be varied so that it is large enough but not too large on your phone

I have added a AWV query param that can be used to set some initial state. the idea being that we could share a 'cloud view' link that opens it in the awv-view so people can go directly to it
http://localhost:8080/?awv=true&lat=42&lon=-71


Phaser + p2 issue on example "collide custom bounds"

This Issue is about

A bug in the API:

Phaser version(s): 2.9.2
Live example: https://samme.github.io/phaser-examples-mirror/p2 physics/collide custom bounds.html
What should happen: balls should not go out of the rectangle
What happens instead: balls goes out on the left

I have no idea what's wrong but the bug is obvious :/ .
[edit] I'm starting the debug. The bug was not present in the version 2.6.2 of phaser but is present in the version 2.7.3

https://github.com/photonstorm/phaser-ce/pull/411#issuecomment-350672823

Why did it change after v2.6.2 though?

@samme it's a p2.js upgrade to last version. I still think it's broken but I can't provide a correct fix, and it works with a simple workaround.


"ClientSession is Uninitialized" when calling Run-TestsInNavContainer

This is similar to issue #527.
I'm calling Run-TestsInNavContainer from our pipelines, it has been working fine for some time now. But today I started to get "ClientSession is Uninitialized" when calling Run-TestsInNavContainer.
I'm using navcontainerhelper <IP_ADDRESS> (pipeline updates to latest version)
The target is a BC14 database.
Output when creating container:
Create CI-bld13 from mcr.microsoft.com/businesscentral/sandbox:w1
NavContainerHelper is version <IP_ADDRESS>
Host is Microsoft Windows Server 2019 Standard - ltsc2019
Docker Client Version is 19.03.1
Docker Server Version is 19.03.1
Using image mcr.microsoft.com/businesscentral/sandbox:w1-ltsc2019
Disabling Health Check (always report healthy)
Creating Container CI-bld13
Version: 14.4.35602.0-W1
Style: sandbox
Platform: 14.0.35570.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.17763.678 (ltsc2019)
Host OS Version: 10.0.17763.720 (ltsc2019)
WARNING: The container operating system matches the host operating system, but the revision is different.
If you encounter issues, you might want to specify -isolation hyperv
Using locale en-US
Using process isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file ***
Downloading C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\my\license.flf
Files in C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\my:
- AdditionalOutput.ps1
- AdditionalSetup.ps1
- license.flf
- MainLoop.ps1
- updatehosts.ps1
Creating container CI-bld13 from image mcr.microsoft.com/businesscentral/sandbox:w1-ltsc2019
92ecc421f71442c7a2186aefffd5c7663ab6a2c578c0d1c3c9a03da801e067bd
Waiting for container CI-bld13 to be ready
Initializing...
Starting Container
Hostname is CI-bld13
PublicDnsName is CI-bld13
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Creating Self Signed Certificate
Self Signed Certificate Thumbprint D8F83C3DA6F06F736305706E9733546F89369884
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Enabling Financials User Experience
Using license file 'c:\run\my\license.flf'
Import License
Creating http download site
Setting SA Password and enabling SA
Creating *** as SQL User and add to sysadmin
Creating SUPER user
Container IP Address: <IP_ADDRESS>
Container Hostname  : CI-bld13
Container Dns Name  : CI-bld13
Web Client          : http://CI-bld13:8080/NAV/
Dev. Server         : http://CI-bld13
Dev. ServerInstance : NAV

Files:
http://CI-bld13:8080/al-3.0.154634.vsix

Initialization took 53 seconds
Ready for connections!
Reading CustomSettings.config from CI-bld13
Container CI-bld13 successfully created

Error:
Importing Objects from C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\PsTestTool-3\PSTestToolPage.fob (container path)
Objects successfully imported
CommunicationError : An error occurred while sending the request.
ClientSession is Uninitialized
at AwaitState, C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\PsTestTool-3\ClientContext.ps1: line 157
at OpenSession, C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\PsTestTool-3\ClientContext.ps1: line 129
at Initialize, C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\PsTestTool-3\ClientContext.ps1: line 46
at ClientContext, C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\PsTestTool-3\ClientContext.ps1: line 23
at New-ClientContext, C:\ProgramData\NavContainerHelper\Extensions\CI-bld13\PsTestTool-3\PsTestFunctions.ps1: line 39
at <ScriptBlock>, <No file>: line 39
##[error]ClientSession is Uninitialized
##[error]At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Invoke-ScriptInNavContainer.
ps1:37 char:13
+             Invoke-Command -Session $session -ScriptBlock $scriptbloc ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

##[error]    + CategoryInfo          : OperationStopped: (ClientSession is Uninitialized:String) [], RuntimeException

##[error]    + FullyQualifiedErrorId : ClientSession is Uninitialized

##[error]

##[error]PowerShell exited with code '1'.

I got it on a dev computer a few weeks ago, but then a restart helped. A restart of our build server did not help this time.
I see that the error is thrown from AppHandling\ClientContext.ps1. Could it be a timing issue, so that the 100 ms timeout is not enough?
Just let me know if you need more info

Could you try to add -debugMode to the run-tests - to see if that prints out additional information?

Ok, I'll update my pipelines to test this. I'll try to bind that parameter to the System.Debug variabel in yaml, would be nice if that worked...
I'll be back.

If possible, maybe you could get the event log from the container (Get-NavContainerEventLog) if this error occurs?

The pipeline is cleaning up in the end, removing containers and all.
But I'll check out what I can find, maybe I always should collect event logs etc if pipeline fails, and publish as an artifact for that build, making it easier to trouble shoot strange behaviors. Failing tests is the easy ones to solve.

The debugMode does not help here. The flag is not set yet when the error occur.
$clientContext.DebugMode = $debugMode is called after [ClientContext]::new(..) in AppHandling\PsTestFunctions.ps1
Maybe the debugMode should have been added to the constructors of ClientContext instead, otherwise it's hard to get this help if initialization fails.
Below is a detailed log of this task, but it's nothing new really :(
2019-09-13T12:20:06.0902711Z ##[section]Starting: Run Tests
2019-09-13T12:20:06.1074781Z ==============================================================================
2019-09-13T12:20:06.1074940Z Task         : PowerShell
2019-09-13T12:20:06.1075064Z Description  : Run a PowerShell script on Linux, macOS, or Windows
2019-09-13T12:20:06.1075316Z Version      : 2.151.2
2019-09-13T12:20:06.1075426Z Author       : Microsoft Corporation
2019-09-13T12:20:06.1075564Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2019-09-13T12:20:06.1075719Z ==============================================================================
2019-09-13T12:20:06.9200607Z ##[debug]VstsTaskSdk 0.11.0 commit 7ff27a3e0bdd6f7b06690ae5f5b63cb84d0f23f4
2019-09-13T12:20:07.0568392Z ##[debug]Entering C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1.
2019-09-13T12:20:07.0638737Z ##[debug]Loading resource strings from: C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\task.json
2019-09-13T12:20:07.0842833Z ##[debug]Loaded 11 strings.
2019-09-13T12:20:07.0878278Z ##[debug]SYSTEM_CULTURE: 'en-US'
2019-09-13T12:20:07.0897808Z ##[debug]Loading resource strings from: C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\Strings\resources.resjson\en-US\resources.resjson
2019-09-13T12:20:07.1106746Z ##[debug]Loaded 11 strings.
2019-09-13T12:20:07.1287144Z ##[debug]INPUT_ERRORACTIONPREFERENCE: 'stop'
2019-09-13T12:20:07.1315410Z ##[debug]INPUT_FAILONSTDERR: 'false'
2019-09-13T12:20:07.1346772Z ##[debug] Converted to bool: False
2019-09-13T12:20:07.1365923Z ##[debug]INPUT_IGNORELASTEXITCODE: 'false'
2019-09-13T12:20:07.1382408Z ##[debug] Converted to bool: False
2019-09-13T12:20:07.1403355Z ##[debug]INPUT_PWSH: 'false'
2019-09-13T12:20:07.1418413Z ##[debug] Converted to bool: False
2019-09-13T12:20:07.1437919Z ##[debug]INPUT_WORKINGDIRECTORY: 'C:\Agent_AS011_01\_work\4\s'
2019-09-13T12:20:07.1539711Z ##[debug]Asserting container path exists: 'C:\Agent_AS011_01\_work\4\s'
2019-09-13T12:20:07.1562337Z ##[debug]INPUT_TARGETTYPE: 'filePath'
2019-09-13T12:20:07.1591852Z ##[debug]INPUT_FILEPATH: 'C:\Agent_AS011_01\_work\4\NAB%20DevOps%20Tools\PowerShell\Run-Tests.ps1'
2019-09-13T12:20:07.1608622Z ##[debug]Asserting leaf path exists: 'C:\Agent_AS011_01\_work\4\NAB%20DevOps%20Tools\PowerShell\Run-Tests.ps1'
2019-09-13T12:20:07.1642931Z ##[debug]INPUT_ARGUMENTS: '-credential ([PSCredential]::new("***", (ConvertTo-SecureString -String "***" -AsPlainText -Force))) -TestResultsFile (Join-Path "C:\Agent_AS011_01\_work\4\s" "TestResults.xml") -testsuite "QWEPR" -containerNameSuffix "12" -debugMode:$True'
2019-09-13T12:20:07.1676428Z Generating script.
2019-09-13T12:20:07.1720816Z Formatted command: . 'C:\Agent_AS011_01\_work\4\NAB%20DevOps%20Tools\PowerShell\Run-Tests.ps1' -credential ([PSCredential]::new("***", (ConvertTo-SecureString -String "***" -AsPlainText -Force))) -TestResultsFile (Join-Path "C:\Agent_AS011_01\_work\4\s" "TestResults.xml") -testsuite "QWEPR" -containerNameSuffix "12" -debugMode:$True
2019-09-13T12:20:07.1824777Z ##[debug]AGENT_VERSION: '2.155.1'
2019-09-13T12:20:07.1889836Z ##[debug]AGENT_TEMPDIRECTORY: 'C:\Agent_AS011_01\_work\_temp'
2019-09-13T12:20:07.1905434Z ##[debug]Asserting container path exists: 'C:\Agent_AS011_01\_work\_temp'
2019-09-13T12:20:07.2236683Z ##[debug]Asserting leaf path exists: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'
2019-09-13T12:20:07.2251271Z ========================== Starting Command Output ===========================
2019-09-13T12:20:07.2391649Z ##[debug]Entering Invoke-VstsTool.
2019-09-13T12:20:07.2526089Z ##[debug] Arguments: '-NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'C:\Agent_AS011_01\_work\_temp\9df10ab4-429d-4631-a018-036473339cb3.ps1'"'
2019-09-13T12:20:07.2539449Z ##[debug] FileName: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'
2019-09-13T12:20:07.2554685Z ##[debug] WorkingDirectory: 'C:\Agent_AS011_01\_work\4\s'
2019-09-13T12:20:07.2600007Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'C:\Agent_AS011_01\_work\_temp\9df10ab4-429d-4631-a018-036473339cb3.ps1'"
2019-09-13T12:20:13.0316437Z Importing Objects from C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\PSTestToolPage.fob (container path)
2019-09-13T12:20:24.0333717Z Objects successfully imported
2019-09-13T12:20:26.9454089Z CommunicationError : An error occurred while sending the request.
2019-09-13T12:20:27.0074631Z ClientSession is Uninitialized
2019-09-13T12:20:27.0097264Z at AwaitState, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 157
2019-09-13T12:20:27.0099667Z at OpenSession, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 129
2019-09-13T12:20:27.0102183Z at Initialize, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 46
2019-09-13T12:20:27.0104563Z at ClientContext, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 23
2019-09-13T12:20:27.0107167Z at New-ClientContext, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\PsTestFunctions.ps1: line 39
2019-09-13T12:20:27.0109545Z at <ScriptBlock>, <No file>: line 39
2019-09-13T12:20:27.2106673Z ##[debug]Error record:
2019-09-13T12:20:27.3118844Z ##[debug]powershell.exe : ClientSession is Uninitialized
2019-09-13T12:20:27.3130435Z ##[debug]At line:1 char:1
2019-09-13T12:20:27.3143559Z ##[debug]+ & 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' --% -No ...
2019-09-13T12:20:27.3152541Z ##[debug]+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-09-13T12:20:27.3163346Z ##[debug]    + CategoryInfo          : NotSpecified: (ClientSession is Uninitialized:String) [], RemoteException
2019-09-13T12:20:27.3174130Z ##[debug]    + FullyQualifiedErrorId : NativeCommandError
2019-09-13T12:20:27.3184615Z ##[debug]
2019-09-13T12:20:27.3200436Z ##[debug]Script stack trace:
2019-09-13T12:20:27.3231106Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3241703Z ##[debug]at Invoke-Tool, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\ps_modules\VstsTaskSdk\ToolFunctions.ps1: line 107
2019-09-13T12:20:27.3252406Z ##[debug]at <ScriptBlock>, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1: line 98
2019-09-13T12:20:27.3262907Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3273885Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-09-13T12:20:27.3284508Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-09-13T12:20:27.3295345Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3311058Z ##[debug]Exception:
2019-09-13T12:20:27.3344513Z ##[debug]System.Management.Automation.RemoteException: ClientSession is Uninitialized
2019-09-13T12:20:27.3591593Z ##[error]ClientSession is Uninitialized
2019-09-13T12:20:27.3598551Z ##[debug]Processed: ##vso[task.logissue type=error]ClientSession is Uninitialized
2019-09-13T12:20:27.3598880Z ##[debug]Error record:
2019-09-13T12:20:27.3620218Z ##[debug]At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Invoke-ScriptInNavContainer.
2019-09-13T12:20:27.3627306Z ##[debug]ps1:37 char:13
2019-09-13T12:20:27.3634964Z ##[debug]+             Invoke-Command -Session $session -ScriptBlock $scriptbloc ...
2019-09-13T12:20:27.3642626Z ##[debug]
2019-09-13T12:20:27.3655568Z ##[debug]Script stack trace:
2019-09-13T12:20:27.3666986Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3674775Z ##[debug]at Invoke-Tool, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\ps_modules\VstsTaskSdk\ToolFunctions.ps1: line 107
2019-09-13T12:20:27.3682453Z ##[debug]at <ScriptBlock>, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1: line 98
2019-09-13T12:20:27.3690072Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3697686Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-09-13T12:20:27.3705291Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-09-13T12:20:27.3712901Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3724837Z ##[debug]Exception:
2019-09-13T12:20:27.3737184Z ##[debug]System.Management.Automation.RemoteException: At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Invoke-ScriptInNavContainer.
2019-09-13T12:20:27.3745340Z ##[debug]ps1:37 char:13
2019-09-13T12:20:27.3753294Z ##[debug]+             Invoke-Command -Session $session -ScriptBlock $scriptbloc ...
2019-09-13T12:20:27.3761142Z ##[debug]
2019-09-13T12:20:27.3773379Z ##[error]At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Invoke-ScriptInNavContainer.
ps1:37 char:13
+             Invoke-Command -Session $session -ScriptBlock $scriptbloc ...

2019-09-13T12:20:27.3774279Z ##[debug]Processed: ##vso[task.logissue type=error]At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Invoke-ScriptInNavContainer.%0D%0Aps1:37 char:13%0D%0A+             Invoke-Command -Session $session -ScriptBlock $scriptbloc ...%0D%0A
2019-09-13T12:20:27.3785468Z ##[debug]Error record:
2019-09-13T12:20:27.3848898Z ##[debug]+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-09-13T12:20:27.3857937Z ##[debug]
2019-09-13T12:20:27.3870971Z ##[debug]Script stack trace:
2019-09-13T12:20:27.3883649Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3892077Z ##[debug]at Invoke-Tool, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\ps_modules\VstsTaskSdk\ToolFunctions.ps1: line 107
2019-09-13T12:20:27.3900309Z ##[debug]at <ScriptBlock>, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1: line 98
2019-09-13T12:20:27.3908434Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3916619Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-09-13T12:20:27.3924941Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-09-13T12:20:27.3933168Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.3946189Z ##[debug]Exception:
2019-09-13T12:20:27.3959778Z ##[debug]System.Management.Automation.RemoteException: +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-09-13T12:20:27.3968475Z ##[debug]
2019-09-13T12:20:27.3980880Z ##[error]+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2019-09-13T12:20:27.3981757Z ##[debug]Processed: ##vso[task.logissue type=error]+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0D%0A
2019-09-13T12:20:27.3994091Z ##[debug]Error record:
2019-09-13T12:20:27.4108270Z ##[debug]    + CategoryInfo          : OperationStopped: (ClientSession is Uninitialized:String) [], RuntimeException
2019-09-13T12:20:27.4118147Z ##[debug]
2019-09-13T12:20:27.4133507Z ##[debug]Script stack trace:
2019-09-13T12:20:27.4147871Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4157955Z ##[debug]at Invoke-Tool, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\ps_modules\VstsTaskSdk\ToolFunctions.ps1: line 107
2019-09-13T12:20:27.4167874Z ##[debug]at <ScriptBlock>, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1: line 98
2019-09-13T12:20:27.4177639Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4187948Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-09-13T12:20:27.4197496Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-09-13T12:20:27.4207370Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4221882Z ##[debug]Exception:
2019-09-13T12:20:27.4236773Z ##[debug]System.Management.Automation.RemoteException:     + CategoryInfo          : OperationStopped: (ClientSession is Uninitialized:String) [], RuntimeException
2019-09-13T12:20:27.4246499Z ##[debug]
2019-09-13T12:20:27.4260500Z ##[error]    + CategoryInfo          : OperationStopped: (ClientSession is Uninitialized:String) [], RuntimeException

2019-09-13T12:20:27.4261668Z ##[debug]Processed: ##vso[task.logissue type=error]    + CategoryInfo          : OperationStopped: (ClientSession is Uninitialized:String) [%5D, RuntimeException%0D%0A
2019-09-13T12:20:27.4274822Z ##[debug]Error record:
2019-09-13T12:20:27.4362284Z ##[debug]    + FullyQualifiedErrorId : ClientSession is Uninitialized
2019-09-13T12:20:27.4371868Z ##[debug]
2019-09-13T12:20:27.4385814Z ##[debug]Script stack trace:
2019-09-13T12:20:27.4400005Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4409738Z ##[debug]at Invoke-Tool, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\ps_modules\VstsTaskSdk\ToolFunctions.ps1: line 107
2019-09-13T12:20:27.4419485Z ##[debug]at <ScriptBlock>, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1: line 98
2019-09-13T12:20:27.4429009Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4438610Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-09-13T12:20:27.4448227Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-09-13T12:20:27.4457792Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4471970Z ##[debug]Exception:
2019-09-13T12:20:27.4486062Z ##[debug]System.Management.Automation.RemoteException:     + FullyQualifiedErrorId : ClientSession is Uninitialized
2019-09-13T12:20:27.4495652Z ##[debug]
2019-09-13T12:20:27.4509162Z ##[error]    + FullyQualifiedErrorId : ClientSession is Uninitialized

2019-09-13T12:20:27.4509978Z ##[debug]Processed: ##vso[task.logissue type=error]    + FullyQualifiedErrorId : ClientSession is Uninitialized%0D%0A
2019-09-13T12:20:27.4523580Z ##[debug]Error record:
2019-09-13T12:20:27.4604360Z ##[debug]
2019-09-13T12:20:27.4612644Z ##[debug]
2019-09-13T12:20:27.4625238Z ##[debug]Script stack trace:
2019-09-13T12:20:27.4637971Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4646631Z ##[debug]at Invoke-Tool, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\ps_modules\VstsTaskSdk\ToolFunctions.ps1: line 107
2019-09-13T12:20:27.4654956Z ##[debug]at <ScriptBlock>, C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1: line 98
2019-09-13T12:20:27.4662980Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4671216Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-09-13T12:20:27.4679325Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-09-13T12:20:27.4687428Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-09-13T12:20:27.4699655Z ##[debug]Exception:
2019-09-13T12:20:27.4712024Z ##[debug]System.Management.Automation.RemoteException:
2019-09-13T12:20:27.4720201Z ##[debug]
2019-09-13T12:20:27.4731812Z ##[error]

2019-09-13T12:20:27.4732469Z ##[debug]Processed: ##vso[task.logissue type=error] %0D%0A
2019-09-13T12:20:27.4744490Z ##[debug]Exit code: 1
2019-09-13T12:20:27.4771339Z ##[debug]Leaving Invoke-VstsTool.
2019-09-13T12:20:27.4818911Z ##[error]PowerShell exited with code '1'.
2019-09-13T12:20:27.4819791Z ##[debug]Processed: ##vso[task.logissue type=error]PowerShell exited with code '1'.
2019-09-13T12:20:27.4892542Z ##[debug]Processed: ##vso[task.complete result=Failed]Error detected
2019-09-13T12:20:27.4905468Z ##[debug]Leaving C:\Agent_AS011_01\_work\_tasks\PowerShell_e213ff0f-5d5c-4791-802d-52ea3e7be1f1\2.151.2\powershell.ps1.
2019-09-13T12:20:27.5285149Z ##[section]Finishing: Run Tests

I'll proceed to see if I can export some logs if the pipeline fails

Now I exported the Application and System logs if the pipeline fails.
This is what I get, but it didn't give me any more clues about what's wrong: ErrorLogs_1.0.668.zip
Anything more I can fetch from the container to help us solve this?
At least I got my pipelines improved with this :-)

Now I commented out the cleanup in my pipeline, leaving the container as-is after failing pipeline build.
I just discovered that it is the call to Get-TestsFromNavContainer that fails, not Run-TestsInNavContainer. But I don't think that changes much.
Anyway, now I got a container that throws this error on every call to Get-TestsFromNavContainer.
Any suggestions on what to do further investigate in this? I'll try to modify the constructors of ClientContext to include debug-mode, maybe that will show something more...

Now I finally made at least some progress. From the InnerException of the CommunicationError Exception I get this:
CommunicationError : An error occurred while sending the request.
CommunicationError InnerException : System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it <IP_ADDRESS>:80
   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Framework.UI.Client.JsonHttpClient.<>c__DisplayClass9_0.<EndOpenSession>b__0() in s:\repo\src\Platform\Client\ClientService\Prod.Client.ClientService.Client\Service\ServiceClients\JsonHttpClient\JsonHttpClient.cs:line 158
   at Microsoft.Dynamics.Framework.UI.Client.JsonHttpClient.ConvertExceptions[T](Func`1 action) in s:\repo\src\Platform\Client\ClientService\Prod.Client.ClientService.Client\Service\ServiceClients\JsonHttpClient\JsonHttpClient.cs:line 181
ClientSession is Uninitialized
at AwaitState, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 160
at OpenSession, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 132
at Initialize, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 46
at ClientContext, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\ClientContext.ps1: line 23
at New-ClientContext, C:\ProgramData\NavContainerHelper\Extensions\CI-bld12\PsTestTool-3\PsTestFunctions.ps1: line 39
at <ScriptBlock>, <No file>: line 39
ClientSession is Uninitialized
At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Invoke-ScriptInNavContainer.ps1:37 char:13
+             Invoke-Command -Session $session -ScriptBlock $scriptbloc ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (ClientSession is Uninitialized:String) [], RuntimeException
    + FullyQualifiedErrorId : ClientSession is Uninitialized

The interesing part is  No connection could be made because the target machine actively refused it <IP_ADDRESS>:80
So it tries to connect to localhost port 80. But Why? The only references I find to port 80 in navcontainerhelper is related to traefik, which I'm not using. (At least I'm not aware of using that)
When running docker container ls I see that it uses ports 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 8080/tcp
What is port 80 used for in my container?
Why is the ClientContext trying to connect to <IP_ADDRESS>:80?
Btw, I created PR #619 to help troubleshoot similar errors in the future.

The connection to the WebClient comes from inside the container and it tries to connect to localhost to avoid leaving the container. Can you connect to the Web Client from the outside with a browser?
Does it help to run IISRESET inside the container?

I think I just found out what was causing this...
Of course I couldn't connect to the web client from the outside...
I added the webclientport parameter to my script, but mistakenly set the default port to 8080 instead of 80. So when not specifying the port it tried to create the web client on the same port as the file share site. embarrassed
Would you accept a PR that adds the default port numbers to the port number parameters of the New-NavContainer function? At least the parameters WebClientPort and FileSharePort ports. Then I could also check that those ports does not collide, resulting in this mess.... If any of the other ports would collide I believe that the NST would fail instead.
Anyway, this issue is closed now...

PR is welcome, if it can help other people not encounter similar problem.
Thanks.

btw, have you managed to get the debugMode to work?
When I tested that switch I had two problems:

It was set too late, so it was not set when I got my issue
After I added it to the constructor instead, to solve point 1 above, I didn't get it to work anyway. It seemed as if it was not reachable in the action context where it was used... Even if $this.debugMode was set, it always returned nothing when called inside the event action

In some cases I got output from debugmode (especially when the clientsession error stems from a dialog popping up in the session). I will check if I can make it better for connection issues

another issue was that the GetAllForms() always failed for me, since $this.clientSession.OpenedForms was null.

Yeah, I didn't take into consideration that the session wasn't initialized.
I did add this as a parameter because it was risky:-)


RFC: Typed response statuses in Scala 2.13+

Lifting information in Status to type level in a backwards-compatible way is surprisingly straightforward. Trying to preserve that information in Response leads to a world of variance-related hurt. ResponseBuilder a demo of what this makes possible rather than something that's ready to be merged, but maybe something like it would be a good fit for the DSL module?
If the changes to Status are approved I can split them out into a standalone PR.

Now if only I'd thought to compile the tests

Apparently I messed something up when running mima locally, because this is super binary incompatible.

I win 😎

Just a note that I haven't forgotten this but it's been buried behind more urgent looking things and I'm very sorry about it.

No need at all to be sorry! It's not urgent at all.

I might redo this with an initial emphasis on exposing the category of status (1xx/2xx/3xx/4xx/5xx) in Response types, which might be more feasible with the variance changes.


SDK changes to add ShowLogonSession

Summary of the pull request
This pull request does the following:

introduces a new IDeveloperIdProvider interface named ShowLogonSession
nit: formats developerIDState to DeveloperIdState according to recommended guidelines
uses ShowLogonSession in the connect developer account user flow

References and relevant issues
Detailed description of the pull request / Additional comments
The purpose of the new interface is to provide plugins the flexibility of driving a custom user experience if desired. In conjunction with the AuthenticationExperienceKind enums defined, this method may be called instead of using the AdaptiveCard for user interaction.
Validation steps performed
Local Build
Manual testing with devhomegithubextension
PR checklist

[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated

Closing out this PR. The SDK changes have been committed from the feature branch and a future PR will be created to commit the remaining changes outlined in this PR i.e. changes inside AccountsPage.xaml.cs.


Make top bar visible when scrolling up

Hello , Dev
Make top bar visible when scrolling up as i can easily switch to bookmarks or Ask HN page without going through all submissions back to access it

I think a good compromise for this would be to hide it when the user scrolls down, and bring it back when the user scrolls back up.

Another solution might be to add a "back to top" floating button once the user hits a certain threshold (example >=50 submissions down).


Create self-hosting guide

The guide should make it easy to host the project yourself.
Trigger.dev involves several services.
Our current deployment system:

The main web app and web socket services using Flight Control (see [flightcontrol.json].(https://github.com/triggerdotdev/trigger.dev/blob/bf57430b6663fa62fc4a395d3aeb05104eae0d1b/flightcontrol.json)
The authentication service (which uses Nango) to fly.io.
Apache Pulsar using StreamNative.

Please note that there is a development guide if you want to run locally.

Looking forward to this. Docker containers would be fantastic.

Consider using Nix 🙏🏻

Is this not going to happen anymore?

@jeanpfs yes, this is definitely going to happen! We're just coordinating these guides (we plan on having a guide for as many platforms as possible) on our trigger.dev-docs repo


GraphQL (WIP)

Pushing this just to show the progress so far. Not ready to merge yet.
Related issues: #32, #59
Notes:

Pothos is good! Some minor issues with docs, but nothing critical; Prisma plugin and Relay plugin work fine, which is great.
urql with SSR is... ugh. Dealing with it right now (haven't pushed the related commit yet). I had to read through the next-urql source code to figure it out.

next-urql uses the deprecated getInitialProps from older Next.js as a default mechanism but has the solution for more modern getStaticProps or getServerSideProps
we'll have to list all requests for GraphQL data in getServerSideProps manually (e.g., deeply nested components which need some portion of data won't magically SSR with all their useQuery data by themselves)

this is not urql's fault, since the alternative is to render everything on the server twice, which is slow

I don't like the amount of code which will be necessary for every getServerSideProps function (urqlState: ssrCache.extractData(), initUrqlClient, etc.); I'll try to come up with some helper functions to make the DX smoother

I'm replacing searchAccordingToQueryData with a GraphQL query, to abstract away all search logic from the frontend code. This requires substantial refactorings, hope to push the working implementation in a day or two.

80% complete, 80% to go.

SSR is working
frontpage uses graphql, dashboards are too

Needs fixing:

[ ] timestamp field (I used custom scalar for the timestamp field on the backend and need to map it properly on the frontend now, probably with urql-custom-scalars-exchange, but it requires schema awareness which I haven't dealt with yet)
[ ] creating dashboards is not implemented yet
[ ] there are probably a few bugs, I should check every page by hand
[ ] docs for writing new endpoints and description fields in graphql schema

Also:

I don't like my current implementation for visualization and qualityIndicators, not sure if I'll improve it before merging or deal with it later
I feel like CommonDisplay can/should be simplified, though it's not much worse now than it was before

urql-custom-scalars-exchange

It works, but it's incompatible with SSR, since Next.js can't serialize Date objects.
There's a workaround with superjson, but I don't think that an extra dependency is worth it.
I left urql-custom-scalars-exchange config & schema introspection code for the future since I already wrote it when I realized this, and schema introspection might be needed for better urql caching anyways.
For now I'm just serializing timestamp as an int (which is better/safer than a date string) and decode it with new Date(ts * 1000) on the frontend.

creating dashboards

Done.

Pushed the new changes, https://metaforecast-git-graphql-quantified-uncertainty.vercel.app/ is mostly functional now. (SSR on the frontpage is currently broken, will investigate).

Ok, I think this is done!
Docs are in docs/graphql.md, and I added a description for the most of graphql fields (sometimes copying from specification.json, which can be deprecated soon, since GraphQL is better for this kind of documentation).

Notes on SSR.
I still don't like how SSR is implemented, especially making a choice of "do I pass the page data from getServerSideProps in urqlState cache or in page props".
Passing in props means that the page is not really dynamic (I consider initialBlah props with useState to be an anti-pattern which should be avoided if possible). Which is mostly fine, except for the frontpage, which is dynamic. It also means that we won't be able to benefit from urql's caching abilities in the future, and caching is a big selling point for graphql; though it's more useful for SPA-like rich UI features, which we don't have yet.
On the other hand, passing in urqlState means that we have to do the query in getServerSideProps and then do the same query with the useQuery on client. Which means that if the document or variables for one of these queries ever changes on the future and we forget to change the other call then SSR would break (i.e. degrade to client-side query, the page won't break entirely, but it would break silently and we might not notice it for a while).
Issues with both of these approaches are non-critical, and it's not hard to change the code from using one approach to another. But I don't like having this choice, it feels like extra cognitive load for no clear benefit.
I don't have any good ideas for how to deal with it yet, and maybe I'll just get adjusted to it over time.

Notes on types.

I got rid of FrontendQuestion since we can just use types from graphql-code-generator based on fragments in our queries
OTOH, there are now two Question types on the backend: first in src/backend/platforms/index.ts and the second one from Prisma; I'd like to keep just the second one eventually, but we'll need to refactor the DB to make it strictly typed (split qualityIndicators and extra fields into postgres columns)

for now, dealing with JsonValue for qualityIndicators and extra is annoying, since Prisma assumes that a JSON field from the DB can be any JSON-compatible value, e.g. a scalar or an array

I got bitten a few times by "strict": true not being enabled in our tsconfig.json, especially by nullable types; we're down to 349 errors when strict is enabled (from 523 on the initial typescript PR)

Any idea why the netlify build preview is failing? The vercel one is working: https://metaforecast-lfn840cvn-quantified-uncertainty.vercel.app

Ok, I think this is done!

Should I merge, or any last checks?

Your notes on SSR (server-side rendering, I'm guessing) went a bit over my head. Any actionables, besides writing this down somewhere so that we remember this when we come back to it in a few months?

Any idea why the netlify build preview is failing?

Probably because the build now requires prisma generate, which is run in npm run build (see scripts in package.json) but netlify runs next build instead.
Anyway, I disabled netlify builds yesterday since we don't use it anymore.

Your notes on SSR (server-side rendering, I'm guessing) went a bit over my head.

That's fine. It's kinda hard to explain clearly without repeating all graphql/urql docs, and I think I'm not doing anything non-standard here.

Any actionables, besides writing this down somewhere so that we remember this when we come back to it in a few months?

No, my notes above are "writing this down somewhere", I should've been more clear about that. No actions needed. (I slightly dislike putting stuff like this in docs/ in the repo, since code usually changes faster than documentation and documentation can get out of sync with reality or with our understanding of best practices.)


Cache Site.get_site_root_paths in the request scope (v2)

Fixes #2916
RFC: #14
This is a rebased and updated version of #3188 by @gasman that moves the business logic for caching site_root_paths inside of the Page model. This makes it easier to use the API from outside Wagtail itself (the most common use case for this is most likely any navigation menu-related template tags, e.g., https://github.com/wagtail/wagtaildemo/pull/110/files).

[x] Add/update usage documentation/recommendations for using and overriding URL-related methods on the Page model, if this is the route we want to go
[x] Determine whether to deprecate Page.url and Page.full_url or defer that decision till a later date. While convenient, using them circumvents the possibility of caching site_root_paths and is probably a habit worth disincentivizing. (DECISION: don't deprecate)
[x] Determine if passing request to these methods is appropriate (seems to be okay, other methods on Page already accept a request)

See also: #3350

Hi @gasman, sorry for the delay on this. I rebased on master again and removed the deprecation TODO items. Does this look all right to you (assuming Travis CI passes)? And would you prefer to merge with the history intact, or would you like me to squash this into a single commit?
Thanks!

Hi @gasman, I've rebased this on master again and moved the release notes to 1.11. Please let me know if this looks good or if you see any tweaks I could make.

Squashed / merged in 1f8edc8984beac8040569c2db3c7ad0cad06f550 - thanks @tobiasmcnulty!


set restitution=1 can not work well

I set restitution=1 and set inertia=Infinity
but it is sleeping soon
The engine below is working well with restitution=1
http://piqnt.com/planck.js/VaryingRestitution

This is a known issue, so please see #256, #21, #216, thanks.


podman-remote.conf enablement

add the ability for the podman remote client to use a configuration file
which describes its connections. users can now define a connection the
configuration and then call it by name like:
podman-remote -c connection1
and the destination and user will be derived from the configuration
file.  if no -c is provided, we look for a connection in the
configuration file designated as 'default'.  If the configuration file
has only one connection, it will be deemed the 'default'.
Signed-off-by: baude<EMAIL_ADDRESS>

I don't want this config file to move into a general podman.conf file, Just for podman-remote connections.
I don't mind if it handles any flags that can be set in podman-remote.

LGTM

/lgtm


Do not work AutoComplete

I clone you project in android studio. but when search location in AutoCompleteTextView, show me this error : Error contacting API:
how can fix this problem and show locations when write location names ?

You have to ensure that you have the correct API keys included. Did you
include the API keys from the Google Console in the app?
On May 25, 2016 5:39 AM, "Mohammad"<EMAIL_ADDRESS>wrote:

I clone you project in android studio. but when search location in
AutoCompleteTextView, show me this error : Error contacting API:
how can fix this problem and show locations when write location names ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jd-alexander/Google-Directions-Android/issues/59

I fix it, but i have this issue : http://stackoverflow.com/questions/37437885/bug-show-empty-google-map-in-android/37438245#37438245 . a few devices show map and many devices not show map! can you help me for this issue ?
I really need this help


pulid_v1.1.safetensors

pulid_v1.1.safetensors - not working - redownloaded it several times - not working - please do reUpload the file

yes same

same

Hello, any one figured out a solution to this?

Same.. Hope the developer would step in to help!


Fix issues found when booting a diskless livenet image

This PR relates to the following issues regarding livenet images in the diskless role: #523 #521 #524

For #523, using cp -a instead of cp -r will keep the setuid flag for /usr/bin/sudo.

For #521, asking disklessset to disable SELinux would put selinux=False in the kernel command line, which would not disable SELinux during boot. The proposed fix will correctly write selinux=0 in the kernel command line.

For #524, the self.MOUNT_DIRECTORY variable is created with a / at the end and used in many places in the code. The proposed fix will keep the variable as-is but remove the / when writing the host file.

By the way, you are committing with @giacomo-mcevoy but doing PR with @ginomcevoy.
Is it on purpose ?

By the way, you are committing with @giacomo-mcevoy but doing PR with @ginomcevoy.
Is it on purpose ?

No it is not, I will review this in my git config for next time.

Hello, I have updated the changelog to mention this PR. Not sure I did the right thing with git, apologies if there is an inconvenience.

The fail is not related to this PR. Merging. Thanks a lot for this PR 😉


Enddat 151

The major changes between this and the previous pull request was added tests for the new functionality. Also changed to add a call to explictly initialize the data set models in workflowStateModel. This way any info such as the parameter codes does not get loaded until its needed.

Wunderbar :+1:

I'm going to close this one. The refactoring I'm doing is significant enough that I don't want to just add it to this pull request.


Created Dashboard and DashboardWidget classes

What's new

Dashboard and DashboardWidgets are now wrapped in their own classes. This should make it easier to add a delete button/movement controls/etc to dashboard widgets.
Added ability to rename dashboards to their context menu.

Issues/todo

Issue #6
No validity checking for notebook names

Having Dashboard extends from MainAreaWidget maybe a convenient way to drag cells to, like Console does.

Having Dashboard extends from MainAreaWidget maybe a convenient way to drag cells to, like Console does.


Python interoperability for FastAPI?

Hi, with IBM ditching kitura project I have second thoughts about using vapour for REST API service. So, the first most option that comes to my mind is Python Interoperability and FastAPI.

Can I know what are pros and cons for using FastAPI for exposing swift models for inference?
Will there be any bottleneck because of interoperability?
FastAPI is pretty fast but it's host language - Python is slow. I remember developers mentioning that Python interoperability project converts python code to native swift/assembly language. Consequently, FastAPI must become faster.. will it?

Perhaps I do not understand, but why do you want to use FastAPI and Vapor together? Theoretically, you should be able to use FastAPI/Flask/Something in Swift but I would not recommend it. Python interoperatibility is meant for tools like pandas, for experimenting.
By the way, I have been using S4TF + Vapor for some time now and it is mostly OK, but sometimes you come across weird bugs. Because Vapor is built on stable swift toolchain but S4TF is based on latest, nightly, toolchains and therefore there is some incompatibility.
Also, python interoperability does not converts python code into native swift. It basically "just" calls python interpreter in the background.

Also, regarding Kitura, I'll point out that it's being transitioned to a community project, so I wouldn't totally write that out either. Most of the server-side Swift for TensorFlow projects I've seen have used Vapor or even SwiftNIO directly, however.

I see. I had misconception that that python code is converted to native code. Thanks for clearing it out @kongzii.

@BradLarson currently I am hosting my models using TFLite using FastAPI (something like this). Would I get almost same inference time when using server-side-swift? Or put it in other words, what is the BEST approach to deploy S4TF models on cloud?

Hi @rakesh4real !
This is a great question, but this is not something the core S4TF team is going to focus on in the short term. As a result, if folks in the community would like to put together some best practices to share, that would be great and we'd be happy to review!
In the meantime, we'll close this issue as it's not a focus of the team.
All the best,
-Brennan


Depth. Remove background works. But 3D Mesh removes foreground

$ sysinfo
CPU: quad core Intel Core i7-2860QM (-MT MCP-)
speed/min/max: 3292/800/3600 MHz Kernel: 6.10.12-100.fc39.x86_64 x86_64
Up: 2d 21h 27m Mem: 17.17/31.28 GiB (54.9%) Storage: 1.86 TiB (26.8% used)
Procs: 402 Shell: Bash inxi: 3.3.34
Python 3.10 venv

Steps to reproduce.
Depth tab. Generate.

Mesh is very distorted and upside-down, whether or not remove background is checked.
When Remove Background is checked, 3D Mesh generates background instead of foreground.
It doesn't matter which model is selected.

I'd suggest switching the model. Res101 is fast and low memory but often give poor results. Also while it likely isn't an issue here tiling mode is intended more for textures (wrapping depth).
DepthAnything2 is usually quite good. Zoedepth should also give better results.

No change.

I fixed most of it by commenting out this line in core.py:
115     try:
116         if not inputdepthmaps_complete:
117             print("Loading model(s) ..")
118             model_holder.ensure_models(inp[go.MODEL_TYPE],
    device, inp[go.BOOST], inp[go.TILING_MODE])
119         print("Computing output(s) ..")
120         # iterate over input images
121         for count in trange(0, len(inputimages)):
122             # Convert single channel input (PIL) images to rgb

123             if inputimages[count].mode == 'I':
124 # -----    #inputimages[count].point(lambda p: p *
    0.0039063096, mode='RGB')
125                 inputimages[count] =
    inputimages[count].convert('RGB')

It appears the stable-diffusion-webui-depthmap-script has its own github presence.

Video creation works. So it's just the display that is scaled too far in the z direction.


[QUERY] Using Azure.Data.Tables SDK 12, how do you configure a secondary location connection string?

Query/Question
I am using SDK 12 to access table storage and have configured the TableServiceClient to point to the storage endpoint.
How do I setup the sdk to use a secondary RA-GRS location should the primary location not respond?  I only need read data when it fails over to the secondary location.
Environment:

Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0] Azure.Data.Tables 12.2.0
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8] Windows 10, Dotnet Core 3.1
IDE and version : [e.g. Visual Studio 16.3] Visual Studio 16.11.1

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

The secondary endpoint is built up by convention and automatically configured when a TableServiceClient is constructed.

/unresolve
@christothes thank you for your reply.
Does this mean that by default, the TableServiceClient will automatically read from the secondary location should the primary location fail?
Is there any documentation expanding on this behavior?
Are there any fail over options or settings that can be controlled when the TableServiceClient is configured?

@christothes Is there any documentation expanding on this behavior?
Are there any fail over options or settings that can be controlled when the TableServiceClient is configured?

Hi @setiseeker - Sorry, I was mistaken in my previous response - I was thinking of getting the replication stats, which automatically uses the secondary endpoint (see this). If you need to direct read-only requests to the secondary endpoint, the secondary endpoint must be configured by creating a new TableClient with the secondary endpoint convention. ex. https://myaccount-secondary.table.core.windows.net.
I'll log a feature request to add this option to the Options for read-only operations, such as Query.

@christothes thank you for the updated info.
If I understand correctly, my code will need to handle the failover operation to the secondary endpoint should a failure occur as the SDK does not do that automatically?

Thank you for your help @christothes


intra/extracellular ribonucleoprotein complex, merge?

do we need?
GO:1990903    extracellular ribonucleoprotein complex | is_a
GO:0030529    intracellular ribonucleoprotein complex
extracellular has no annotations....

How about

obsolete 'GO:1990903    extracellular ribonucleoprotein complex'
merge GO:0030529    intracellular ribonucleoprotein complex into parent 'GO:1990904 ribonucleoprotein complex'?

That works.

+1
no annotation to GO:1990903 in CP either

Dear all,
The proposal has been made to obsolete 'GO:1990903 extracellular ribonucleoprotein complex’. The reason for obsoletion is that there are no known extracellular ribonucleoprotein complexes.
There are no annotations or mappings to this term. Any comments can be added to this issue: https://github.com/geneontology/go-ontology/issues/15303
We are opening a comment period for this proposed obsoletion. We'd like to proceed and obsolete this term on March 16, 2018. Unless objections are received by March 16, 2018  we will assume that you agree to this change.
Thanks, Pascale

[ ] obsolete 'GO:1990903 extracellular ribonucleoprotein complex'
[ ]   merge GO:0030529 intracellular ribonucleoprotein complex into parent 'GO:1990904 ribonucleoprotein complex'

@pgaudet
This was part of the extracellular vesicles work. Could you please hold on to this while I check, I am drowning in other tasks at the moment and in meetings all day. I only saw this ticket now and did not realise that you were already merging terms... I'll comment by the weekend (possibly the plan is good to go but I'd really like to have time to check).
Thanks.
Paola

ribonucleoprotein complex (or specific child)  occurs_in(extracellular vesicle)?

@ValWood @pgaudet @bmeldal
GO:1990903 ‘extracellular ribonucleoprotein complex’ was added in 2015 as part of the extracellular vesicles/exRNA project. The project resulted in a publication (https://www.ncbi.nlm.nih.gov/pubmed/27076901). I’m not sure why a reference was not provided by the experts at the time I was adding the terms, but figure 1 in our paper points to PMID:21383194 for ‘extracellular ribonucleoprotein complex’. I had a brief look and that sounds quite sensible. What’s more, GO:1990903 ‘extracellular ribonucleoprotein complex’ is explicitly shown in figure 2 (“The list of exRNA-related terms, synonyms and relationships that have been added to GO”). The paper is less than 2 years old; we should probably keep that term.
In summary, I’d suggest to

[ ] add PMID:21383194 as a dbxref to GO:1990903 ‘extracellular ribonucleoprotein complex’
[ ] do not obsolete GO:1990903 ‘extracellular ribonucleoprotein complex’
[ ] de-merge GO:0030529 ‘intracellular ribonucleoprotein complex’ from its parent 'GO:1990904 ribonucleoprotein complex’
optionally,
[ ] someone might look into the possibility of annotating PMID:21383194 (sorry, I really don't have time to do that).

Lastly, a general comment. The fact that that term was created as part of a focused ontology project is visible from its dbxref ‘GOC:vesicle’. In similar cases, when feasible, I’d suggest checking directly with the editor(s) who was/were responsible for the specific project. I don’t look at all GO GitHub tickets anymore for obvious reasons, so it was only the obsoletion email that drew my attention. If my suggestions above end up being accepted, I could have saved Pascale some time.
Thanks, and a nice weekend to all :-)

I will also chime in here. The collaboration with GOA and ExoCarta/Vesiclepedia is still ongoing. Seeing as this is an active collaboration, I think we should keep the term.

Hi @ggeorghiou @paolaroncaglia
Thanks for the feedback. ‘extracellular ribonucleoprotein complex’ is odd in that there is no equivalent term for extracellular protein complex. All I could find is 'GO:1990563 extracellular exosome complex', which is a direct child of extracellular space.
So if this miRNA-protein complex is important, I could rename the term 'GO:1990903 ‘extracellular ribonucleoprotein complex’ as such and add the reference.
Would that be an acceptable compromise? It seems to me that the grouping term (extracellular ribonucleoprotein complex) is unnecessary and inconsistent with the current structure of the ontology.
Thanks, Pascale

Hi @pgaudet ,
I’d still prefer to keep the general term ‘extracellular ribonucleoprotein complex’, on the grounds that the extracellular RNA community considered it important to have as such in the ontology. Our paper describes the process that many members of that community went through to find consensus on terms they wished to be in GO, so it’s not like one single person asked for the term without thinking too much about it. I can relate to the dislike of not having a ’symmetrical’ ‘extracellular protein complex’ term ;-), but clearly the presence of ‘extracellular ribonucleoprotein complex' reflects the wish of one particular community we serve, rather than the broader way we try to have regular patterns in GO. Also, an implication of what @ggeorghiou wrote is that ExoCarta/Vesiclepedia are still in the process of getting their annotations in shape for submission to GO. I’m no longer involved in that, but I suspect that they may well be using/have used ‘extracellular ribonucleoprotein complex’ already.
Thanks,
Paola

But we only add complexes to GO if there is functional information, and there is not functional information in PMID:21383194, so we would not annotate that paper?
The authors say quite clearly in the abstract
"In addition, identification of extracellular Ago2-miRNA complexes in plasma raises the possibility that cells release a functional miRNA-induced silencing complex into the circulation."
So, we  should wait for evidence for such a role, otherwise it will make much work for later...There is enough to do (and too much to fix), already.
v

@ValWood @pgaudet
Thanks for looking into that paper. I ticked the last box in one of my previous comments to show that someone has looked into annotating it. My concern about not depriving the exRNA community of a general term that they asked for is still valid, though. I’ll contact some of my coauthors on the exRNA paper and ask them for examples of extracellular ribonucleoprotein complexes other than the Ago2-miRNA from PMID:21383194. Please keep this ticket open until I hear back from them. Thanks.

For the records: I emailed Kei-Hoi Cheung, Louise Laurent and Shivakumar Keerthikumar today.

Question for editors: the pattern 'organelle x complex' is not widely used; most of the instances I found are when a complex type exists in two different organelles, for example 'mitochondrial DNA-directed RNA polymerase complex', under 'mitochondrial protein complex' (there is no equivalent 'nuclear protein complex grouping term, but there is a term 'nuclear DNA-directed RNA polymerase complex').
In which direction do we want to go? It seems difficult to classify complexes based on where they are located.
Thanks, Pascale

Good question, Pascale.
I assume things like mitochondrial and nuclear transcription processes differ in detail but the principles of transcription should be the same so the complexes have essentially the same function.
The locations should then be captured with an extension, right?

My opinion is point 2 here ;)
https://github.com/geneontology/go-ontology/issues/12418
I don't think we need a grouping term for  'mitochondrial protein complex'
it has it's own term
mitochondrial DNA-directed RNA polymerase complex (GO:0034245)
and is a  "mitochondrial part".
I also think we should get rid of organelle specific instances of identical complexes (i.e nuclear proteasome, cytosolic proteasome), and use extensions.

@ValWood The alternative (keeping organelle-specific grouping terms) seems unmaintainable.

...and unnecessary.
If a complex is organelle specific, it has a part_of parent  to the organelle.
If the same complex is found in multiple locations, an occurs_in extension works best ( and a co-annotation to the location, but this could be inferred longer term...)

@ValWood @pgaudet @bmeldal
Here's a reply from Louise Laurent (UCSD):
"This paper immunoprecipitated using an anti-AGO2 antibody from detergent-free biofluid, and concluded that extracellular miRNA was associated with non-EV AGO2-containing RNPs: PMID:21609964."
And here's my reply to her:
"...I will point my GO colleagues to the paper below. However, as that is only one example of an extracellular, vesicle-free miRNA-protein complex, and it was published in 2011, it would be really helpful if you could please provide additional, and possibly more recent, examples of extracellular complexes of RNAs (can be other than miRNAs) and proteins that are not bounded by vesicles. ...".
If I do receive more examples, I'll paste them here. Cheers.

Hi paola,
The point was that there was no evidence for functional significance of this particular association at present which is a pre-requisite for a  complex in GO....
This abstract says:
We hypothesize that extracellular miRNAs are in the most part by-products of dead cells that remain in extracellular space due to the high stability of the Ago2 protein and Ago2-miRNA complex.
Could you ask about functional significance?

Hi @ValWood,
I thought long and hard about how to reply in a polite and friendly manner :-) but I’m afraid that the answer is “no, I can’t ask about functional significance”. I’ve already asked for more (and more recent) examples, which implies that I’m looking for as good an experimental evidence as we can get, and to me that also implies indication of actual roles for those complexes. It should mean the same to them, too. I emailed 3 of them and the above is the only reply I got so far. Feel free to obsolete the term if you really want to, and if you don’t mind that a term slated for obsoletion is explicitly shown in a figure in a recent paper authored by GOC members.
Thanks,
Paola

Hi @paolaroncaglia,
I'm only trying to establish if there is any additional evidence to provide biological justification for keeping the term (i.e any other RNA complex, or publication that we overlooked).
So far, we have only established that  none of the papers supplied so far describe the existence of an ‘extracellular ribonucleoprotein complex’ with a biological role, so there does not seem to be, based on the current data.
It does not even appear to be part of the extracellular exosome according to the authors who clearly state in the abstract:
"We hypothesize that extracellular miRNAs are in the most part by-products of dead cells that remain in extracellular space due to the high stability of the Ago2 protein and Ago2-miRNA complex."
This term does not fit normal design pattern (see above).
GO is  not a static resource, so inclusion in a paper (GOC or not) does not seem to be a valid reason to keep a term which is not biologically meaningful, and would not be used in annotation? I'm sure we all have publications with obsoleted terms by now ;)

Hi @ValWood
As I mentioned before, we have an ongoing collaboration with Vesiclepedia/ExoCarta. I am still waiting to hear back from them regarding how their GO annotations are progressing, but given the deadline for deciding what to do with these terms, I am going to have a look at a previous GPAD they have sent us to see how the term has been used and where it has been referenced. Seeing as they do not have the opportunity to hear about changes to the GO unless we feed it back to them, I ask for a bit of time to allow them to update us and see if this term is still useful to them. There may be annotations that support this term being kept and I would hate for them to not have their say.

Hi @ValWood,
Thanks. I share @ggeorghiou’s concerns; hopefully there will be useful functional information in the GPAD file he has. If not, it might take some time to get feedback from its authors - we gather there’s been some changes in management overseeing the practical aspects of the resources; both George and I have emailed the PI at Exocarta/Vesiclepedia in the last few days but no reply yet. Other than that, I accept your point of view on that term and leave it to you and others involved to decide of its fate. I’ll be honest though, while I understand and second the discussion about not wanting to explode the GO with ‘extracellular’ and ‘intracellular’ terms where the location can be better captured otherwise, a quick search for ‘extracellular’ returns >140 terms and if the GOC wishes to gradually get rid of them all, this (and similar changes) should be communicated to our users. I know that the question is a bit more complex, but it seems that the outside world is not really being made aware of the changes in GO - not the trivial ontology changes that are healthy in a dynamic resource, but the overarching changes in strategy.
My 2 cents. Cheers,
Paola

Hello,
I see at least two issues being discussed here:

how to group 'protein complex' terms
rules for creating complex terms: does the complex need to have a known activity or not ?
I think the Complex WG is addressing the second point (right @bmeldal ?)

WRT the first point: in GO we have only two grouping terms by organelle for protein complexes, 'extracellular ribonucleoprotein' and 'mitochondrial protein complex'.
@paolaroncaglia
I was not disputing terms like 'extracellular ferritin complex'. 'Extracellular miRNA-protein complex' seems OK as well. However I do think we need to remove the grouping terms because these are very incomplete and will confuse users.
So, are you OK with renaming ''extracellular ribonucleoprotein' to extracellular miRNA-protein complex', and adding the reference you mentioned ?
Thanks, Pascale

I see at least two issues being discussed here:

how to group 'protein complex' terms
rules for creating complex terms: does the complex need to have a known activity or not ?
I think the Complex WG is addressing the second point (right @bmeldal ?)

Yes, we said we need to have at least some idea of its function to curate a complex. In many cases we know it exists and which process it affects but don't know its actual MF so we just annotate to BP. But we can say something about its role.

WRT the first point: in GO we have only two grouping terms by organelle for protein complexes, 'extracellular ribonucleoprotein' and 'mitochondrial protein complex'.

There are more, like GO:0098796 membrane protein complex. They were introduced by David OS for grouping and logical defs.
We might have to reconsider this strategy.
We have a call in a little over an hour!
Birgit

Thanks @bmeldal, this is useful.
We didn't manage to discuss this at the last call - I would still like to get clarification from the editors about what GO captures WRT complexes: from #12782 I thought we wanted to have as little overhead as possible in managing protein complexes, which is why I merged 'protein complex' into 'macromolecular complex'. To be consistent with that logic we should NOT classify complexes by organelle/localization either.
@ukemi
@cmungall
@thomaspd
Can you please comment ?
Thanks, Pascale

As I have said before. I am always concerned when we make changes or remove terms that have resulted from consulting experts in a field.

I agree David, but this case is a bit different, as these terms were not proposed by experts for functional annotation but for experiment metadata annotation.  Are the exosome terms labeled in the ontology?  Maybe we need a GO-function-slim to support our major use case, that would exclude the exosome terms unless they've been demonstrated to be functionally relevant.

From the papers supplied for this particular term, the authors say that is likely a result of
"in the most part by-products of dead cells that remain in extracellular space due to the high stability of the Ago2 " so this isn't exosome.
It seems strange to include these....

Editors discussion March 19:

Annotation should be made to both 'ribonucleoprotein complex' AND 'extracellular' (note that without a GO-CAM model these would not be linked).
For specific complexes, we can add a 'part_of' assertion in the logical definition, like we do for
chloroplast isoamylase complex :
'isoamylase complex'
and ('part of' some chloroplast)

So @paolaroncaglia : since you already published the ID I can merge the term 'extracellular ribonucleoprotein complex' into the parent 'ribonucleoprotein complex', or rename it 'extracellular miRNA-Ago2 complex' (@bmeldal would that be a valid term?)
Thanks, Pascale

Hi all, in reply to some of your questions:
@pgaudet wrote
“I was not disputing terms like 'extracellular ferritin complex'. 'Extracellular miRNA-protein complex' seems OK as well. However I do think we need to remove the grouping terms because these are very incomplete and will confuse users.
So, are you OK with renaming 'extracellular ribonucleoprotein [complex]’ to ‘extracellular miRNA-protein complex', and adding the reference you mentioned?”
and
“since you already published the ID I can merge the term 'extracellular ribonucleoprotein complex' into the parent 'ribonucleoprotein complex', or rename it 'extracellular miRNA-Ago2 complex’”
and
“Also - I am not disputing the term, but the impact on the ontology structure. I would expect the experts did not take that into account when proposing terms - right?”
Actually, looking at figures 1 and 2 in https://www.ncbi.nlm.nih.gov/pubmed/27076901, they did put some thought into the ontology structure. Sure, you may still consider them less ‘ontology conscious’ than professional GO editors. See below for other comments please.
@thomaspd wrote
“I agree David [@ukemi, re. “I am always concerned when we make changes or remove terms that have resulted from consulting experts in a field”], but this case is a bit different, as these terms were not proposed by experts for functional annotation but for experiment metadata annotation. Are the exosome terms labeled in the ontology? Maybe we need a GO-function-slim to support our major use case, that would exclude the exosome terms unless they've been demonstrated to be functionally relevant.”
GO:0070062 ‘extracellular exosome’ is not labeled not-for-annotation, but the whole point of exosome research from the past few years is exactly that (at least some) extracellular vesicles seem to play roles in cancer and other diseases… How to differentiate functionally relevant exosomes from ones that aren’t, in the ontology, is a complex discussion that I’m not going into now :-) I agree that the miRNA-Ago2 complex doesn’t come with good functional evidence in the 2 papers we know of (in response to @ValWood “From the papers supplied for this particular term, the authors say that is likely a result of "in the most part by-products of dead cells that remain in extracellular space due to the high stability of the Ago2" so this isn't exosome.”).
So ok with merging 'extracellular ribonucleoprotein complex' into its parent 'ribonucleoprotein complex’.
Paola