@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/datapackage-feedstock#26.


Not working through proxy

Hello,
running this ui throug jwilder/nginx-proxy, it doesn't work, only static elements.
Where's the issue? Any workaround to make this ui work using a subdomain instead of a port?
Thanks

Have a look at this issue https://github.com/kevana/ui-for-docker/issues/97 for some configuration example.

Thanks,
so what is the modification of the nginx configuration to be done in
https://github.com/jwilder/nginx-proxy/blob/master/nginx.tmpl
Any suggestions?

You can follow this issue up here:
https://github.com/jwilder/nginx-proxy/issues/639

@orboan you can use portainer as an alternative to UIFD, it has support for jwilder/nginx-proxy, see this issue: https://github.com/portainer/portainer/issues/348


Mac_ios wide_gamut_ios is severely flaky due to timing out

It has been flaky 7 out of latest 20 runs. It flaked across multiple bots, and doesn't seem infra related.
The test was stuck running draw image with wide gamut works ontop of platform view with blur:
[2023-11-28 13:03:37.956090] [STDOUT] stdout: 29:17 +5: end-to-end test draw image with wide gamut works ontop of platform view with blur
[2023-11-28 13:03:38.956841] [STDOUT] stdout: 29:18 +5: end-to-end test draw image with wide gamut works ontop of platform view with blur
[2023-11-28 13:03:39.956462] [STDOUT] stdout: 29:19 +5: end-to-end test draw image with wide gamut works ontop of platform view with blur
[2023-11-28 13:03:40.955829] [STDOUT] stdout: 29:20 +5: end-to-end test draw image with wide gamut works ontop of platform view with blur
[2023-11-28 13:03:41.956712] [STDOUT] stdout: 29:21 +5: end-to-end test draw image with wide gamut works ontop of platform view with blur

Suspicious culprit: https://github.com/flutter/flutter/commit/2150424cee973e4b62b4b375d86db6f57bc01ed9? /cc @jonahwilliams
Per flake workflow, assigning to test owner @gaaclarke for initial triage.

Lets revert: https://github.com/flutter/flutter/pull/139101

I added the revert label


explorer link correction

explorer link correction : https://satori.vanascan.io/

Thank you!

no problem :))


problem when backtesting minutes datasource with local timezone index

When I am trying to run my algorithm locally, every time,
zipline tried to fetch the data which was not yet available.
The problem is the len() is total numbers, but searchsorted()
returns index which is 0 based.
Also minor refactor to remove duplicate code block.

Coverage increased (+0.08%) to 86.62% when pulling 0413f7b3a4bbf482614bc36d6efe109a4f933309 on dyno:master into d192b1846f5d5cef794920b48dfcff556b2be638 on quantopian:master.

Coverage increased (+0.08%) to 86.62% when pulling 0413f7b3a4bbf482614bc36d6efe109a4f933309 on dyno:master into d192b1846f5d5cef794920b48dfcff556b2be638 on quantopian:master.

Not sure if we deal with this behavior now, but going to close this b/c it's 3 years old; if someone wants to open a new PR feel free to do so.


Simple S3 Bucket

[x] Define an S3 Bucket in Terraform
[x] We are going to use the random resource string for the name
[x] Install the AWS Terraform Provider
[x] Configure AWS Provider
[x] Perform Terraform Apply and Terraform Destroy

Needed to adjust/add boolean values to resource to meet S3 bucket naming standards to lowercase and numbers only
resource "random_string" "bucket_name" {   _lower = true_   _upper = false_   length   = 32   special  = false


Compilation Error due to esaxx-rs v0.1.10 (used in tokenizers crate)

Problem
Trying to run the basic example from README.
use kalosm::language::*;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let model = Llama::phi_3().await?;
    let mut chat = Chat::builder(model)
        .with_system_prompt("You are a pirate called Blackbeard")
        .build();

    loop {
        chat.add_message(prompt_input("\n> ")?).to_std_out().await?;
    }
}

During compilation, I get
The following warnings were emitted during compilation:

warning<EMAIL_ADDRESS>src/esaxx.cpp:620:10: fatal error: 'cstdint' file not found
warning<EMAIL_ADDRESS>  620 | #include <cstdint>
warning<EMAIL_ADDRESS>      |          ^~~~~~~~~
warning<EMAIL_ADDRESS>1 error generated.

error: failed to run custom build command for `esaxx-rs v0.1.10`

Caused by:
  process didn't exit successfully: `/Users/redacted/dev/redacted/redacted/kalosm-hello-world/target/release/build/esaxx-rs-ef80ffd7b4943882/build-script-build` (exit status: 1)
  --- stdout
  OUT_DIR = Some(/Users/redacted/dev/redacted/redacted/kalosm-hello-world/target/release/build/esaxx-rs-d244e8d43c35e3be/out)
  TARGET = Some(aarch64-apple-darwin)
  OPT_LEVEL = Some(3)
  HOST = Some(aarch64-apple-darwin)
  cargo:rerun-if-env-changed=CXX_aarch64-apple-darwin
  CXX_aarch64-apple-darwin = None
  cargo:rerun-if-env-changed=CXX_aarch64_apple_darwin
  CXX_aarch64_apple_darwin = None
  cargo:rerun-if-env-changed=HOST_CXX
  HOST_CXX = None
  cargo:rerun-if-env-changed=CXX
  CXX = None
  cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
  RUSTC_WRAPPER = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some(false)
  cargo:rerun-if-env-changed=MACOSX_DEPLOYMENT_TARGET
  MACOSX_DEPLOYMENT_TARGET = None
  cargo:rerun-if-env-changed=CXXFLAGS_aarch64-apple-darwin
  CXXFLAGS_aarch64-apple-darwin = None
  cargo:rerun-if-env-changed=CXXFLAGS_aarch64_apple_darwin
  CXXFLAGS_aarch64_apple_darwin = None
  cargo:rerun-if-env-changed=HOST_CXXFLAGS
  HOST_CXXFLAGS = None
  cargo:rerun-if-env-changed=CXXFLAGS
  CXXFLAGS = None
  cargo:warning=src/esaxx.cpp:620:10: fatal error: 'cstdint' file not found
  cargo:warning=  620 | #include <cstdint>
  cargo:warning=      |          ^~~~~~~~~
  cargo:warning=1 error generated.

  --- stderr

  error occurred: Command env -u IPHONEOS_DEPLOYMENT_TARGET "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "--target=arm64-apple-darwin" "-mmacosx-version-min=15.0" "-I" "src" "-Wall" "-Wextra" "-std=c++11" "-stdlib=libc++" "-o" "/Users/redacted/dev/redacted/redacted/kalosm-hello-world/target/release/build/esaxx-rs-d244e8d43c35e3be/out/2e40c9e35e9506f4-esaxx.o" "-c" "src/esaxx.cpp" with args c++ did not execute successfully (status code exit status: 1).

Environment:

Crate version: kalosm = { version = "0.3.2", features = ["language"] }
Rust version:  [rustc 1.81.0, nightly-aarch64-apple-darwin]
OS info: [macOS Sequoia 15.0 ; M2]

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[X] I don't have time to fix this right now, but maybe later

Hi @timurguvenkaya, try to install latest Xcode. It helped in my case.

I'm planning on making tokenizers optional once https://github.com/floneum/floneum/pull/274 is merged. It should be 5-15x faster and pure rust which should remove the cpp tooling requirements

Thank you @lukaszKielar. All works now


ci: fix issue label automation

Closes https://github.com/celestiaorg/celestia-app/issues/2262
Tested this on my fork and it works as expected. The problem with the last PR was that the environment variables are strings so they need to be compared against the string literals 'true' and 'false'.

Codecov Report

Merging #2282 (5b37c2e) into main (06e4a8b) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2282      +/-   ##
==========================================
- Coverage   21.74%   21.72%   -0.03%
==========================================
  Files         129      129
  Lines       14453    14453
==========================================
- Hits         3143     3140       -3
- Misses      11006    11008       +2
- Partials      304      305       +1

see 1 file with indirect coverage changes


Develop

Codecov Report

Merging #32 (ad8420f) into main (2e8060a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #32   +/-   ##
=======================================
  Coverage   92.02%   92.02%
=======================================
  Files          18       18
  Lines         188      188
=======================================
  Hits          173      173
  Misses         15       15

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2e8060a...ad8420f. Read the comment docs.


 I have no capacity to permantly fix compatiblitity issues.

Also, jsii is the single blocker for implementing new features in this library.
Python support will be dropped so we no longer have a need for this jsii.

Oh lol, I was just looking to add JSII support, I'm trying to write a jsii CDKTF construct which expose PolicyStatement building from iam-floyd and jsii complains when I bundle.. I'm quite confused and I was about to give up by publishing iam-floyd with the .jsii manifest so I can just keep at as a peer dependency.
Is there any way to do this without re-adding JSII? Perhaps it's necessary to do something similar to how the AWS CDK package is built?


testing, do not merge

Preview is available here:http://developers-pr70.previews.kube001.services.stellar-ops.com/docs


Make ~all mentions of "contention" link to docs

Preliminary work addressing DOC-6663
Summary of changes:

Wide-ranging "housekeeping" PR that makes ~all places where 'contention' is found as a bare word into links to the contention info on the 'SQL Performance Best Practices' page

Adds more specific links to cluster settings useful for contention debugging / monitoring

Makes many mentions of 'retry errors' into sentences that use the searchable strings '40001 error code' and restart transaction, which in turn link to the 'Common Errors' page (which in turn links to the 'Transaction Retry Error Reference')

Adds links to various contention-related tables in crdb_internal

Adds links to crdb_internal.cluster_locks in some appropriate places

Adds more links to the 'Hot Spots' section of the 'SQL Performance Best Practices' page, e.g. from the ALTER TABLE ... SPLIT AT docs

Makes the 'Indicators your application is experiencing transaction contention' section from 'Performance Recipes' also available on the 'SQL Performance Best Practices' page (via an include)

Applies to the following versions:

v23.1 (including things in _includes/ folder; cockroachcloud/ was checked and did not have any instances of the term 'contention')

As mentioned when we discussed, I think these changes are a strict improvement on what we currently have. I do think it would be useful to review these docs going forward and attempt to clarify at each point what we mean by "contention", as it's a broad term. Lock contention, which is specifically two transactions vying for (i.e. conflicting on) the same lock, is a bit different to serializability conflicts, which have to do with two transactions conflicting in their orders of operations performed on overlapping read-write sets. Both are types of transaction conflicts, and may fit under the broad umbrella of the term "contention", however it will be important to distinguish these types of transaction conflict and their behavior going forward.

Thanks for summarizing and explaining this Alex.  I will be sure to draw this distinction more clearly in DOC-7148: Update "SQL Performance Best Practices - Transaction Contention" to distinguish lock contention vs. Serialization conflicts/retries

@ianjevans FYI this is mostly adding a bunch of links.  If you are happy with the v23.1 changes I will backport to earlier versions


Enabling the authenticationendpoint webapp to capture and apply filters to dispatcher forwards made internally.

Description:
Dispatcher forwards made internally during inbound requests from the Authentication Endpoint are not captured and processed by the appropriate filters (AuthenticationEndpointFilter).

Done


Text is not correct and there is no information about how to hide fields

Refering to the following page:
https://docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/list-form-configuration
All section (header, footer and body) descriptions end with the same text: "Close the form and open the form again to view the applied header." This is not correct. The last word should correspond to the section (header, footer, body).
I also miss information about how to hide fields that I do not want to show at the moment. I also want the option to hide the selection of content type since I only use one in most solutions I build.
Addition: The layout configuration cannot be accessed from a form in "edit all mode" as stated in the text. It can only be accessed from "view all mode".
Kind regards,
Mattias Sandberg

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

ID: 0f6aeedd-a76d-88b0-7ed5-93e20ac218bc
Version Independent ID: 64315895-1103-d5f6-0195-9b5b61211132
Content: Configure the list form
Content Source: docs/declarative-customization/list-form-configuration.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Appears to be a dupe with #6591

Appears to be a dupe with #6591


prevent panic when the lister is not set for the namespace

@smarterclayton @adammhaile  from what I understand both controllers are running with some hack version of the image from this PR right now.


Automation for pywheel creation

For SlicerMorph we need to install the package as a pywheel to make ensure consistency, and version checking (e.g., an upgrade needing to install a new version).
Is it possible to automate pywheel generation, so that when a change is made to the source code, it creates a new wheel and bump ups the minor version. for example the version for the new media commit would be be 1.0.1, so that for the people who installed the SlicerMorph version from last week, the new upgrade can automatically do version check and upgrade the morphosource package if necessary.
@johnbradley @oothomas

There is now a 1.1.0 release on PyPI.


Wrong path for cloud-config in kubeadm.md

The cloud-config file should be located under /etc/kubernetes/cloud-config instead of /etc/kubernetes/cloud-config.json.
(See: https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/master/manifests.go#L41 )
If the file is not in this location the controller-manager will fail to start, as he is given the --cloud-provider option without --cloud-config. (--cloud-config will only be used when  /etc/kubernetes/cloud-config exists https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/master/manifests.go#L367 )

This change is

I signed it!

Thanks!


Error when installing -  requires a peer of<EMAIL_ADDRESS>- 1.x

Eerytime I try to install I get this error. Here is my log. Not sure why this is happening. Also npm -v react says 3.10.10 and wont update? not sure how to proceed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 1.x but none was installed.
npm WARN<EMAIL_ADDRESS>No description
Justins-MacBook-Pro:ddl-living-style-guide justin$ npm -v react
3.10.10
Justins-MacBook-Pro:ddl-living-style-guide justin$ npm install react
<EMAIL_ADDRESS>/Users/justin/GitHub/ddl-living-style-guide
└──<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 1.x but none was installed.
npm WARN<EMAIL_ADDRESS>No description
Justins-MacBook-Pro:ddl-living-style-guide justin$ npm -v react

Getting the same error when I try to npm install. Any help with this?


Add support for mobile

Is it possible to use this package as an editor for mobile apps? It seems like keyboard input, text selection and the copy/paste toolbar haven't been implemented on mobile. Is there a plan to support these features and if not, will contributions to these features be possible?

According to this, I think it'll be sometime before an official mobile support is available:

For right now we are exclusively focused on desktop OS and desktop web. I decided early on that it wasn't worth the early effort to figure out how to adapt TextClient to the needs of a text editor. The mobile integration will eventually be implemented. https://github.com/superlistapp/super_editor/pull/43#discussion_r583984567

Though, if you're interested, I was able to get scrolling, selection and keyboard input to work on iOS by modifying document_interaction.dart and here's the result:
https://user-images.githubusercontent.com/46427323/114619399-32c85180-9cb3-11eb-9bda-39b0ffbb197c.mov

As stated, our main focus right now is on Desktop and Web for the initial release. Mobile versions will be addressed later. We can use this issue as a tracking issue though.

I changed the name of this ticket so that it can be used to track mobile support.

If anyone seeing this is interested, I've made some progress in getting super_editor to work on mobile. It's still WIP and hopefully it'll be of value when the time comes for supporting mobile.
The good part is that I only had to create document_interaction_mobile.dart which takes the default Interactor 's place if the device is mobile (note: this is on mobile branch of my fork).
Here's an example demo:
https://user-images.githubusercontent.com/46427323/116639257-c5821500-a970-11eb-8b4d-718efae5cd47.mp4

Hi @osaxma, it's good to hear that you're finding it relatively easy to integrate mobile support. I'll be happy to take a look at your solution whenever we prioritize mobile.
As for adoption of a solution, expansion to mobile is likely to raise many edge-cases and nuanced interactions. As such, I'm sure that I'll be doing a fully analysis of the problem and then figuring out a solution. Therefore, it's very unlikely that we would merge a given PR from outside the project.
This is why we have a section in the contributing guide that suggests writing a proposal rather than writing code:
https://github.com/superlistapp/super_editor/blob/main/super_editor/CONTRIBUTING.md#consider-writing-a-proposal-before-writing-an-implementation
Obviously, in your case, it looks like you want a solution right now and so you're building one. That's great. But I wanted to set expectations for what's likely to happen within this project.

Hey @osaxma - I see you continue to work on your fork, awesome. We're also planning to use the editor in mobile in the near future. Maybe we can coordinate our work? How about we chat for a bit to see how we can get this done in an efficient way? Cheers

Hi @bk-one,
Glad to hear that. Please feel free to DM on Twitter (https://twitter.com/osaxma) on how you'd like to communicate.
Cheers

@osaxma I started a proposal for mobile support over in the discussions:
https://github.com/superlistapp/super_editor/discussions/242
Feel free to post any of your insights from your initial investigation.

@osaxma - Looking back at your example work, how did you configure those styling buttons on top of the keyboard, e.g., bold, italics, etc? I've skimmed through your example code but I'm not seeing where that's happening...

Hi @matthew-carroll
It's all in demo_toolbar.dart.
Some pointers:

class _ToolbarDemoState is where the toolbar is placed based on the platform.
class SelectionController is a controller for the document where the logic mess resides.
class Toolbar is the toolbar Widget which uses the controller to apply actions.

Exactly.

That's also how we handle it at Superlist.
On Wed, Sep 8, 2021 at 12:08 PM osaxma @.***> wrote:

Exactly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/superlistapp/super_editor/issues/121#issuecomment-915103103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAJEGN42AMKYVFXODCDSD3UA4YYRANCNFSM423ZFG4Q
.

Support has been added with version 0.2.0 - please file specific issues if something is not working as expected.


Support shared domain for erofs + fscache daemon

Previously,  the commit erofs: basic support for erofs + fscache daemon  supported erofs with fscache daemon.
Since the shared domain feature is not be implemented in Linux Kernel, the config field DomainID is unused.
The cfg field "DomainID" is not used since the shared domain feature is not implemented in Linux Kernel.
After Kernel implements this feature, nydus-snapshotter should adapt the DomainID field.

Good to hear about it 👍

Okay, let's keep open this issue until the patchset is landed upstream.

https://github.com/containerd/nydus-snapshotter/pull/211
already merged.


Allow users to expire, keep, or disable storage of job information

Currently, the information attached to a job that has been processed are necessarily stored back in redis. In some cases, this is not needed, and unwanted.
I added a way for users to disable this feature by making the ttl have three states:

positive (e.g. 600): the job is saved back to redis with an expiry after processing
neutral (e.g. 0): the job is saved back to redis without expiry
negative (e.g. -1): the job is not saved back to redis

I thought about using positive, None, and 0, but decided to stay with one type, not sure what's best honestly.

I dig -1.
Can you add a test for this?

Just added several tests for the 3 different ttl "states"


Documentation examples for Parquet to Delta for multiple partitions

The current Delta Lake documentation provides example for 1 partition column in Scala.
https://docs.delta.io/latest/delta-utility.html#-convert-to-delta
// Convert partitioned parquet table at path '/path/to/table' and partitioned by integer column named 'part'
val partitionedDeltaTable = DeltaTable.convertToDelta(spark, "parquet.`/path/to/table`", "part int")

My Parquet table has 3 partition columns.  It is unclear to me if current (source code) version (0.5) of Delta supports more than 1 partition column as part of this conversion.  My Spark version is 2.4.4.  (Not sure if Spark version is an requirement or not.)
If the answer is an absolute yes, some examples to show the actual syntax would be extremely helpful.  It is unclear if the string input expects a comma delimited string, and if that string has case sensitivity checks or not.
It is good to have clarity before converting a large parquet table with at least 3 partitions for example (year, month, day) and not have any irreversible corrupted table on the other side of that function.

I found the documentation I am looking for embedded inside the code comment in Spark StructType.scala file that provided the example I am looking for:
/**
   * Creates StructType for a given DDL-formatted string, which is a comma separated list of field
   * definitions, e.g., a INT, b STRING.
   *
   * @since 2.2.0
   */
  def fromDDL(ddl: String): StructType = CatalystSqlParser.parseTableSchema(ddl)

I have answered my own question.  I don't know how to enhance the Delta lake documentation, so I am leaving this issue open for the project maintainers to triage it or close it.
Hopefully this will help others in the future.

thank you for pointing it out. I will update the docs to make this clear.


Fix pinning of client-go version to kubernetes-1.8.7

Pinned version of client-go to kubernetes-1.8.7

@sayanh i used v5.0 as its official release, Is there any issues you faced if you just keep client-go to release version i.e v5.0?

@murali-reddy I'm afraid, yes, there are issues with version v5.0.0 which are:

glide up -v fails inconsistently(after changing the versions for other k8s.io/api etc. to kubernetes-1.8.7 )
if glide up -v goes fine somehow, unit tests fail.
And above all v5.0.0 is really old, and v6.0.0 seems to be the latest official release.(But again unit tests fail with v6.0.0 as well)
In order to be consistent with other k8s.io packages(e.g. api, code-generator, etc.) realease tag kubernetes-1.8.7 was used.

thanks @sayanh. client-go 6.0 is little early as it may break functionality for kuberntes 1.8.*. So approach is fine to me.

@sayanh @murali-reddy I think client-go v5.0 isn't really old because it's mainly compatible with k8s 1.8 which is widely used at this moment I think. I am just thinking should we revert the whole k8s.io package to major v1.8 and client-go major v5.0 which I believe will pass the whole tests ? Specifying k8s-1.8.7 seems like to be too specific. Sorry if I forget something but is there any specific reason you want to stick to v1.8.7 ?

@ngtuna So v5.0.0 of client-go was released in 20 Oct 2017. IMO, this is quite old.
The last stable release of 1.8.* series of k8s is 1.8.7 so far, hence migrating to k8s-1.8.7 makes sense as we want to stay with 1.8.*. Above all, 1.8.* is the most used version. So I feel it does not make sense to migrate to 1.8.0 or 1.8.1.... This was also the rationale behind changing Deployment to apps/v1beta2(as per 1.8.*)
The other option was to migrate to 1.9.1 which is too bleeding edge, IMO.
Now the question is why do you think 1.8.7 is too specific? Are there any particular issues which you are refering to? Again, if we pin down other packages(e.g. apimachinery, code-generator, etc.), which better version we have in 1.8.*?


fix: handle hr insert at end of document

Fixes #26 by detecting if selection is at end of document and inserting a paragraph in addition to the horizontal rule.
This approach feels a little hacky but is the most sensible thing I could come up with. I've created three conditions to properly insert a horizontal rule:
Empty document
When the document is empty, insert a paragraph and appended with a horizontal rule and a paragraph. This initial paragraph will retain the cursor and the appended paragraph allows for text to be entered after the horizontal rule.

Example gif

End of a populated document
When the selection is at the end of a populated document, insert a paragraph and prepend it with a horizontal rule. This ensures the cursor is placed after the horizontal rule.

Example gif

Default
This applies to all other cases. This just replaces the current selection with a horizontal rule.

Example gif

I don't think the bug is fixed. If you type abc in an empty editor, then insert a horizontal rule, it's still selected. It's not selected if there's already a newline at the end of the document (which is what probably happened in your second gif).

@double-beep nice catch. My initial implementation worked as expected, but I later used insertParagraphIfAtDocEnd which introduced a regression. I've removed the usage of insertParagraphIfAtDocEnd for inserting a horizontal rule and it now works as expected AFAICT.


periodic-containerdisks-push-nightly failing with error introspecting artifact "centos-stream:8": no candidates for version "8" and variant "GenericCloud" found"

/kind bug
What happened:
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/periodic-containerdisks-push-nightly/1645607628551753728
time="2023-04-11T02:06:49Z" level=warning msg="error introspecting artifact \"centos-stream:8\": no candidates for version \"8\" and variant \"GenericCloud\" found"
time="2023-04-11T02:06:49Z" level=error msg="artifact centos-stream:8 failed in stage push: error introspecting artifact \"centos-stream:8\": no candidates for version \"8\" and variant \"GenericCloud\" found" name=centos-stream version=8
time="2023-04-11T02:06:49Z" level=info msg="Writing results file"
time="2023-04-11T02:06:49Z" level=warning msg="artifact centos-stream:8 failed in stage push: error introspecting artifact \"centos-stream:8\": no candidates for version \"8\" and variant \"GenericCloud\" found"
time="2023-04-11T02:06:50Z" level=error msg="artifact centos-stream:8 failed in stage push: error introspecting artifact \"centos-stream:8\": no candidates for version \"8\" and variant \"GenericCloud\" found" name=centos-stream version=8
time="2023-04-11T02:06:50Z" level=info msg="Writing results file"
time="2023-04-11T02:06:50Z" level=fatal msg="artifact centos-stream:8 failed in stage push: error introspecting artifact \"centos-stream:8\": no candidates for version \"8\" and variant \"GenericCloud\" found"

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
common-templates version:
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

$ curl https://cloud.centos.org/centos/8-stream/x86_64/images/CHECKSUM
$

https://pagure.io/centos-infra/issue/1128

https://bugzilla.redhat.com/show_bug.cgi?id=2186258

https://cloud.centos.org/centos/8-stream/x86_64/images/CHECKSUM.asc is present (missing for 9) but that would mean carrying additional code to validate the signature etc. Might be worth it in the long run.

Thanks for taking care of it @lyarwood.
It looks like the CHECKSUM file is back?
https://prow.ci.kubevirt.io/job-history/gs/kubevirt-prow/logs/periodic-containerdisks-push-nightly


Add Chain Version into NEP description

Hello,
@lllwvlvwlll  suggested that we add the Chain Version in our NEPs.
I think this is a good practice, since if when we update NEO, we may affect NEPs.

We could update past NEPs to inform which networks they refer to.
A field: 'protocol' : 2+, 2, 3, 3+

We should abolish the NEO2 NEPs when NEO3 MainNet is launched.

I think all existing ones can be migrated Erik... not too much incompatible stuff I guess (haven't seen yet).

Hi @erikzhang, but we are keeping both neo2 and neo3 running simultaneously for some time, aren't we? At least during this period of time, we need to describe if the NEPs are compatible.
Today we are updating NEP-3 for neo 3 and these changes are not compatible with neo 2, however, neo 2 is the current version in production mode. This may cause issues for new developers.
I believe this is an good opportunity to filter what neps are included in neo3 and which are 'discarded'. @erikzhang  do you think there will be negative impacts? Because if there are only positive impacts (even if they are very small), maybe we can put this forward? 😅
It is a demand from our communities, they need to know in order to replicate it into their tools


Release ApiResponse public constructors

We needed to make those constructor public, otherwise there is no way to mock responses from the client in our unit tests.

Tests passing


Blocking loadscreen

The loadscreen does not currently block loading of the starting passage, it simply hides it.  Blocking would be better, in general, and resolve a few issues.
Issues
There is the, minor, potential to break existing code.

Done in v3.


[BUG] ResourceManager.Automation unable to delete node resource

Library name and version
Azure.ResourceManager.Automation 1.0.1
Describe the bug
When trying to delete a dsc node get a not found error. The url from the error is passing the name of the Dsc node instead of passing the ID.
The generated code for DscNodeResource is passing the name instead of the id of the node to the Delete method of the DscNodeRestClient.
Expected behavior
DSC Node gets deleted.
Actual behavior
DSC Node is not deleted and an error is returned.
Reproduction Steps
`
var armClient = new ArmClient(new ManagedIdentityCredential());
var automationAccount = armClient.GetAutomationAccountResource(automationAccountResourceId);
var dscNodes = automationAccount.GetDscNodes();
var dscNodeToDelete = dscNodes.FirstOrDefault();
await dscNodeToDelete.DeleteAsync(Azure.WaitUntil.Completed);
`
Environment
No response

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

The request path of the Delete operation is /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/nodes/{nodeId}, and the required parameter is named nodeId. So, the generator thought it should be Id.Name, we need to find a way to handle this case.

Also experiencing this. Workaround provided by @AlexDickerson  did work once for me but for some reason on other DSCNodes doesn't.

Had same experience as @barto90. The reflection method worked, but not consistently. I ended up using this, which seems to work much more reliably.
var dscNodeToDelete = armClient.GetDscNodeResource(DscNodeResource.CreateResourceIdentifier(dscNode.Id.SubscriptionId, dscNode.Id.ResourceGroupName, automationAccount.Data.Name, dscNode.Data.NodeId));

dscNodeToDelete.DeleteAsync(Azure.WaitUntil.Completed);


Add sse build to conda nightly build

As titled. Since now we have it available with velox, this PR just completes the Conda counterpart.
We only need to simply pass a CPU_TARGET=sse env var before running the setup.py, but I spent a little bit of time understanding how the env vars are passed from conda meta.yaml recipe to the building script. It seems like from conda build to build.sh the variables in meta.yaml will be lost. Based on the conda document the best practice is probably to put the env vars in build.sh as well.
This PR also refactored a couple of other related env vars into meta.yaml, and enabled the import test for macos builds.

PR LGTM.
Got a question regarding

It seems like from conda build to build.sh the variables in meta.yaml will be lost. Based on the conda document the best practice is probably to put the env vars in build.sh as well.

Curious about this statement here. For TorchData, the env BUILD_S3 is specified by workflow env. And, it seems this variable is passed into the packaging script and conda build https://github.com/pytorch/data/blob/3d967c63450b561355bdce719a0db1950ac1f9eb/.github/workflows/_build_test_upload.yml#L254-L258

From my experience it can be passed to build_conda.sh, but will be lost in build.sh which is called by conda build. Let me run a couple of more tests to confirm.

PR LGTM.
Got a question regarding

It seems like from conda build to build.sh the variables in meta.yaml will be lost. Based on the conda document the best practice is probably to put the env vars in build.sh as well.

Curious about this statement here. For TorchData, the env BUILD_S3 is specified by workflow env. And, it seems this variable is passed into the packaging script and conda build https://github.com/pytorch/data/blob/3d967c63450b561355bdce719a0db1950ac1f9eb/.github/workflows/_build_test_upload.yml#L254-L258

From my experience it can be passed to build_conda.sh, but will be lost in build.sh which is called by conda build. Let me run a couple of more tests to confirm.

Ok after some tests I think I figured it out: Env vars need to be specified in meta.yaml -> build -> script_env to be preserved during build. But it seems like it has some predefined ones already, like MACOSX_DEPLOYMENT_TARGET. One thing that confused me was I printed out the variables, but some have values while some don't.

Based on the conda document the best practice is probably to put the env vars in build.sh as well.

Would also be great to put the conda document link?


Support for Cloudflare Pages

Current Terraform version
± terraform -v
Terraform v0.12.26

Description
https://blog.cloudflare.com/cloudflare-pages-ga/
Use cases
Create and manage Pages
Potential Terraform configuration
...

I really don't know!
References
No response

Now that https://github.com/cloudflare/cloudflare-go/pull/724 was merged in cloudflare-go, can we expect this functionality soon?

Any updates?

Any updates?

Bumping this so it doesn’t slip into obscurity…
At the very least, it seems like it’s probably no longer pending-upstream-library since Pages features have made it into cloudflare-go.

@jacobbednarz I call dibs


Java-dependent processes use more CPU than allocated on SLURM

This is more of a general question related to the implementation of java-dependent processes in Nextflow pipelines on SLURM clusters: we've found that these processes use more CPUs than allocated in the base.config. This does not cause the pipeline to fail as such but does slow down other users jobs and our system admin will cancel such jobs. Does anyone have a solution for this (except reserving an entire node for those processes, which is what we're having to do at the moment).
Regards,
Katie.

Hi @kviljoen ! We have a SLURM cluster too and I haven't had any issues with such processes - let's not rule out the fact that I haven't looked! 😅 Not entirely sure what can be done to be honest but it appears to be a general Nextflow related issue so probably best to create an issue there? Will close this for now but feel free to ask on the #help channel on nf-core Slack too to get a bit more visibility.


Dart snapshot generator failed with exit code -6

When I am trying to build apk with command 'flutter build apk' , I am getting below error. Please let me know if anyone knows solution for this.
💪 Building with sound null safety 💪

../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 3298: error: unreachable code
Dart snapshot generator failed with exit code -6
../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 3298: error: unreachable code
Dart snapshot generator failed with exit code -6
../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 3298: error: unreachable code
Dart snapshot generator failed with exit code -6

FAILURE: Build failed with an exception.

* Where:
Script '/Users/admin/Desktop/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 1102

* What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.
> Process 'command '/Users/admin/Desktop/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 37s

Detail log for below issue with 'flutter build apk --verbose'
[        ] [ +108 ms] Running command: /Users/admin/Desktop/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/Users/admin/Desktop/flutter/bin/cache/artifacts/engine/darwin-x64/const_finder.dart.snapshot --kernel-file
/Users/admin/Desktop/flutter_projects/cirkl/.dart_tool/flutter_build/27585fa1181798a95e1557523819be5b/app.dill --class-library-uri
package:flutter/src/widgets/icon_data.dart --class-name IconData
[+3490 ms] [+3465 ms] ../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 3298: error: unreachable code
[   +1 ms] [   +2 ms] Dart snapshot generator failed with exit code -6
[        ] [  +23 ms] ../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 3298: error: unreachable code
[        ] [        ] Dart snapshot generator failed with exit code -6
[  +97 ms] [  +63 ms] ../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 3298: error: unreachable code
[        ] [        ] Dart snapshot generator failed with exit code -6
[        ] [  +11 ms] Target aot_android_asset_bundle failed: IconTreeShakerException: Invalid ConstFinder result.
[        ]            To disable icon tree shaking, pass --no-tree-shake-icons to the requested flutter build command
[        ]            #0      IconTreeShaker._parseConstFinderResult (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:311:9)
[        ]            #1      IconTreeShaker._findConstants (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:299:12)
[        ]            <asynchronous suspension>
[        ]            #2      IconTreeShaker._getIconData (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:112:45)
[        ]            <asynchronous suspension>
[        ]            #3      IconTreeShaker.subsetFont (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:177:5)
[        ]            <asynchronous suspension>
[        ]            #4      copyAssets.<anonymous closure> (package:flutter_tools/src/build_system/targets/assets.dart:99:16)
[        ]            <asynchronous suspension>
[        ]            #5      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[   +7 ms]            #6      copyAssets (package:flutter_tools/src/build_system/targets/assets.dart:83:3)
[        ]            <asynchronous suspension>
[        ]            #7      AndroidAssetBundle.build (package:flutter_tools/src/build_system/targets/android.dart:64:34)
[        ]            <asynchronous suspension>
[        ]            #8      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:839:9)
[        ]            <asynchronous suspension>
[        ]            #9      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #10     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[   +4 ms]            #11     Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #12     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[        ]            #13     FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:606:16)
[        ]            <asynchronous suspension>
[        ]            #14     AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:317:32)
[        ]            <asynchronous suspension>
[        ]            #15     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
[        ]            <asynchronous suspension>
[   +4 ms]            #16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #17     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
[        ]            <asynchronous suspension>
[        ]            #18     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
[        ]            <asynchronous suspension>
[        ]            #19     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #20     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
[   +3 ms]            <asynchronous suspension>
[        ]            #21     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
[        ]            <asynchronous suspension>
[        ]            #22     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #23     main (package:flutter_tools/executable.dart:94:3)
[        ]            <asynchronous suspension>
[        ] [        ] Target android_aot_release_android-arm64 failed: Exception: AOT snapshotter exited with code -6
[        ]            #0      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:257:7)
[        ]            <asynchronous suspension>
[        ]            #1      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:839:9)
[   +6 ms]            <asynchronous suspension>
[        ]            #2      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #3      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[        ]            #4      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #5      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[        ]            #6      FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:606:16)
[   +4 ms]            <asynchronous suspension>
[        ]            #7      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:317:32)
[        ]            <asynchronous suspension>
[        ]            #8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
[        ]            <asynchronous suspension>
[        ]            #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
[        ]            <asynchronous suspension>
[        ]            #11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
[   +2 ms]            <asynchronous suspension>
[        ]            #12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
[        ]            <asynchronous suspension>
[        ]            #14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
[        ]            <asynchronous suspension>
[        ]            #15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #16     main (package:flutter_tools/executable.dart:94:3)
[   +5 ms]            <asynchronous suspension>
[        ] [        ] Target android_aot_release_android-x64 failed: Exception: AOT snapshotter exited with code -6
[        ]            #0      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:257:7)
[        ]            <asynchronous suspension>
[        ]            #1      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:839:9)
[        ]            <asynchronous suspension>
[        ]            #2      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #3      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[   +7 ms]            <asynchronous suspension>
[        ]            #4      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #5      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[        ]            #6      FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:606:16)
[        ]            <asynchronous suspension>
[        ]            #7      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:317:32)
[        ]            <asynchronous suspension>
[        ]            #8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
[   +4 ms]            <asynchronous suspension>
[        ]            #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
[        ]            <asynchronous suspension>
[        ]            #11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
[        ]            <asynchronous suspension>
[        ]            #12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
[   +5 ms]            <asynchronous suspension>
[        ]            #14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
[        ]            <asynchronous suspension>
[        ]            #15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #16     main (package:flutter_tools/executable.dart:94:3)
[        ]            <asynchronous suspension>
[        ] [        ] Target android_aot_release_android-arm failed: Exception: AOT snapshotter exited with code -6
[        ]            #0      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:257:7)
[        ]            <asynchronous suspension>
[   +4 ms]            #1      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:839:9)
[        ]            <asynchronous suspension>
[        ]            #2      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #3      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[        ]            #4      Future.wait.<anonymous closure> (dart:async/future.dart:473:21)
[        ]            <asynchronous suspension>
[        ]            #5      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:777:32)
[        ]            <asynchronous suspension>
[        ]            #6      FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:606:16)
[   +5 ms]            <asynchronous suspension>
[        ]            #7      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:317:32)
[        ]            <asynchronous suspension>
[        ]            #8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
[        ]            <asynchronous suspension>
[        ]            #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
[        ]            <asynchronous suspension>
[        ]            #11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
[   +3 ms]            <asynchronous suspension>
[        ]            #12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
[        ]            <asynchronous suspension>
[        ]            #14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
[        ]            <asynchronous suspension>
[        ]            #15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[   +4 ms]            #16     main (package:flutter_tools/executable.dart:94:3)
[        ]            <asynchronous suspension>
[        ] [   +5 ms]
[        ]            #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
[        ]            #1      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:334:7)
[        ]            <asynchronous suspension>
[        ]            #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
[        ]            <asynchronous suspension>
[        ]            #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #4      CommandRunner.runCommand (package:args/command_runner.dart:209:13)
[   +3 ms]            <asynchronous suspension>
[        ]            #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
[        ]            <asynchronous suspension>
[        ]            #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[        ]            <asynchronous suspension>
[        ]            #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
[        ]            <asynchronous suspension>
[        ]            #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
[        ]            <asynchronous suspension>
[        ]            #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
[   +5 ms]            <asynchronous suspension>
[        ]            #10     main (package:flutter_tools/executable.dart:94:3)
[        ]            <asynchronous suspension>
[        ] [        ] Persisting file store
[        ] [  +14 ms] Done persisting file store
[        ] [  +19 ms] "flutter assemble" took 5,024ms.
[  +98 ms] [ +194 ms] ensureAnalyticsSent: 192ms
[        ] [   +1 ms] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 1
[        ] > Task :app:compileFlutterBuildRelease FAILED
[        ] Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[        ] Use '--warning-mode all' to show the individual deprecation warnings.
[        ] See https://docs.gradle.org/6.8.3/userguide/command_line_interface.html#sec:command_line_warnings
[        ] 1 actionable task: 1 executed
[        ] FAILURE: Build failed with an exception.
[        ] * Where:
[        ] Script '/Users/admin/Desktop/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 1102
[        ] * What went wrong:
[        ] Execution failed for task ':app:compileFlutterBuildRelease'.
[        ] > Process 'command '/Users/admin/Desktop/flutter/bin/flutter'' finished with non-zero exit value 1
[        ] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 7s
[ +405 ms] Running Gradle task 'assembleRelease'... (completed in 8.0s)
[   +4 ms] "flutter apk" took 8,733ms.
[   +3 ms] Gradle task assembleRelease failed with exit code 1
[        ]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:400:9)
           <asynchronous suspension>
           #2      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:179:5)
           <asynchronous suspension>
           #3      BuildApkCommand.runCommand (package:flutter_tools/src/commands/build_apk.dart:112:5)
           <asynchronous suspension>
           #4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
           <asynchronous suspension>
           #5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:209:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #9      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
           <asynchronous suspension>
           #10     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
           <asynchronous suspension>
           #11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #12     main (package:flutter_tools/executable.dart:94:3)
           <asynchronous suspension>

[  +94 ms] ensureAnalyticsSent: 83ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

@apurvbacancy
Can you provide flutter doctor -v and a complete minimal reproducible code sample without any third party plugin code that triggers the error you reported ?

@darshankawar , Please find output of 'flutter doctor -v'.
[✓] Flutter (Channel stable, 2.10.2, on macOS 11.6 20G165 darwin-x64, locale en-GB)
    • Flutter version 2.10.2 at /Users/admin/Desktop/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 097d3313d8 (9 weeks ago), 2022-02-18 19:33:08 -0600
    • Engine revision a83ed0e5e3
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/admin/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio 2.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio 2.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 100.0.4896.127

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@apurvbacancy Can you provide flutter doctor -v and a complete minimal reproducible code sample without any third party plugin code that triggers the error you reported ?

Will need this too.

Might be duplicate of https://github.com/flutter/flutter/issues/97301

Seems it was vm issue. There was some functions written in main.dart file and some of them was taking lot of memory. So I found solution by applying '@pragma('vm:never-inline')' above the functions which was taking memory.
I found those functions with running command flutter build apk --verbose


Add netcat for internal liveness probe

If running in a kubernetes cluster standalone, netcat needs to be available to execute an internal liveness probe as mentioned in #119.

My misunderstanding, netcat is available as nc.


Potential Exec implementation

I'm opening a new issue since the topic is a bit different from the purpose of #505 .
So I think I made some nice progress on the exec implementation. The changes can be seen here: https://github.com/deislabs/krustlet/compare/master...jiayihu:exec
If the WASM module doesn't have a _start, then the Pod is waiting for exec commands. Otherwise it works as before, since there is no multithreading support and Instance is not Send. This is also why we can't have a noop _start loop.
Basically what I tried to do it to have something like wasmtime add.wasm --invoke add 1 2, but with kubectl exec add -- add 1 2. I've implemented it only in the wasi-provider, so wascc behaves like before.
If feels a bit weird yeah, but I think it's a reasonable first implementation idea until threads are supported in WASI/wasmtime.
But I'm currently stuck with the expected API response. I can't find any official REST API documentation for the endpoint, so I have some questions if you don't mind.

The path in krustlet is /exec/{namespace}/{pod}/{container} but it's different from what I see in other k8s client libraries: https://github.com/clux/kube-rs/blob/33207f9589507556a2eaa1d8e36318005e12bcec/kube/src/api/subresource.rs#L480. Nervertheless it works 🤷, it's reached when using kubectl exec
The endpoint seems to expect to be a Websocket rather than a normal REST API.
https://github.com/clux/kube-rs/blob/33207f9589507556a2eaa1d8e36318005e12bcec/kube/src/api/subresource.rs#L493-L509 This is the point that I'm struggling with the most.

I'm not sure if a Websocket really makes sense for a WASM invocation. I see more as a oneshot call, just like a FaaS invocation as @thomastaylor312 said. As a matter of fact, I'm ignoring options like stdin, stdout, stderr, tty. On the other hand, it would be weird having kubectl exec not working because it expects a Websocket.
For the time being, I'm just returning the result as string. This work fine if the caller is using a normal HTTP REST call, but kubectl prints Error from server: invalid upgrade response: status code 200.
What do you think? Do you have also any tips on where I can use some existing K8s WebSocket server endpoint in Rust?

Some answers to your questions first:

So the path being called in the client is the API server endpoint for exec. Underneath the hood, the API server will call the proper kubelet exec endpoint if I remember correctly.
As for the websocket stuff, I do think it is weird in our use case, but we try to conform to what kubernetes expects. There technically isn't a well documented API contract between the API server and kubelet, but the "API" (insofar as it can be called that) we conform to is basically what kubernetes expects. We are already using warp for the kubelet endpoints and that has support for websockets: https://github.com/seanmonstar/warp/blob/master/examples/websockets.rs

I didn't do a full review, but it looks like your code is heading in the right direction. I am curious if there is a way we can use annotations within the pod (or possibly something else) to indicate to the provider that the "container" shouldn't actually attempt to run the WASM module, but just load it rather than hoping that module doesn't have a _start function.
@bacongobbler I feel like you might have thoughts here

Sorry for the late reply, I've been busy with a deadline recently. Today I gave WebSocket a try but I noticed that kubectl isn't actually using WebSocket yet, it's still using SPDY/3.1 . The apiserver supports WebSocket instead, because client libs like kube-rs use that https://github.com/kubernetes/kubernetes/issues/89163
Moreover, there's some issue with warp and WebSockets. Kubectl POSTs on /exec whereas warp::ws() filter has GET backed-in and I've opened an issue: https://github.com/seanmonstar/warp/issues/803
But even if the issue were solved, it wouldn't be a happy path for krustlet yet. I've locally patched warp to support POST websocket endpoints, but the latest warp 0.3 uses tokio 1.x and krustlet throws currently. So updating to tokio 1.x would be required. I'm sure it's on the roadmap, but I can imagine it's not an easy task. Therefore, even supporting apiserver exec is not easily done.
With that being said, I'm wondering what would be the best compromise here. I would have loved to open a PR, but I guess you wouldn't be happy with a half-done implementation where /exec can only be reached as REST endpoint and not usable by kubectl or apiserver. So this issue is basically stuck for the time being, waiting for the following steps:

Warp allowing POST WebSocket endpoints
Updating krustlet to tokio 1.x
apiserver exec can be supported
kubectl supports WebSocket (unknown ETA)
kubectl exec can be supported
WASI multi-thread support in wasmtime
krustlet can implement proper multi-thread exec invokation in the WASM module

For the time being, I'll use my fork with RESTful exec for my purposes, sigh.

@bacongobbler I actually went ahead and implemented WebSocket support as requested by the apiserver. So it doesn't support kubectl exec, but apiserver client libs work fine because it's standard GET WebSocket protocol. Tested with kube-rs. Would you be interested in the PR?

Without kubectl exec support, how does this work?


ERRO[0100] http server erroraccept unix /var/run/convoy/convoy.sock: use of closed network connection  pkg=daemon

Information:
VM OS: Centos 7
docker  --version: Docker version 17.09.0-ce, build afdb6d4

Problem
Hello, I have recently tried to install Convoy and followed the quick start guide and when I execute the sudo command to start the daemon for the COnvoy plugin
sudo convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6
it returns this output

and when I cancel it outputs:

Points:

I tried even shutting of my firewall with the VM, nope.

Checked the .sock file

Checked the directory

--
Question:
What could I be missing? Am I doing something wrong? I have tried it on 2 other VMs and its still not working and I dont know what it means please help :<. Thank you!
Blessings

Convoy daemon is running as a daemon, so it will continue running until you stop it.
You can run Convoy daemon in one console or start it as a service, then use Convoy (cli) to connect to it. Or create Docker volume with it.

Wait isnt running this command : "sudo convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6" supposed to start it? My problem is that I cant start it. I get stuck in this step and I dont know whats wrong

cause if i run it in a window and try a convoy command in another window it appears like this

@yasker

I'm late to the party but I think that yasker means you should run the daemon in the background somehow:
e.g
convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6 &
When it hangs it is actually still running correctly, so killing it is not what you want to do :)
Once I realised this I was able to continue to:
docker run -v vol1:/vol1 --volume-driver=convoy alpine touch /vol1/foo


Known limitations review in solutions-overview

The following line in Known limitations need to be reviewed, this action can be done.
Instant flows (flows that use a manual trigger) can't be added to a solution after the flow has been created. To include an instant flow in a solution, it must be created from the solution. To do this, from the solution select New > Automation > Cloud flow > Instant.

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

ID: ba673f56-d0c1-6795-c028-5e121fe3cfeb
Version Independent ID: bb0c60db-d75b-c470-81f9-3414e9b863d5
Content: Solutions in Power Apps - Power Apps
Content Source: powerapps-docs/maker/data-platform/solutions-overview.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @MahdiSheikhi. This issue has been assigned to the doc author for review.

Thanks @bishalgoswami I should add following comment:
If Instant flows (flows that use a manual trigger) added to other solutions before, can be add to the new solution.


Build Docker image and push to Dockerhub

As mentioned in #1051, the CircleCI docker build step isn't working, and we want to move it to a Github Action instead. This PR has two commits:

first, revert the CircleCI additions so that the CircleCI tests file is clean (via reverting the two commits from #1065)
second, add a build+push to dockerhub github action.

This will require two secrets that I believe can be set in the repository settings somewhere: one for a DOCKERHUB_USERNAME and another for a DOCKERHUB_TOKEN. I also went ahead and added both an amd64 and an arm64 build here, and am hoping that it just works (tm).
I also once again set the build and push to only happen when main is pushed to / gets new commits, but I think we can change that to work only on this branch from my fork if we want to test before merging.

@mockdeep hopefully it works this time!

Updated the PR with your suggestions and rebased them into the second commit. Should I keep the run-tests name on CircleCI instead of reverting to build?

Let's give it a try! I'm wondering why we don't see the image building on this PR, but maybe we need to merge it before it will run.

Should I keep the run-tests name on CircleCI instead of reverting to build

I think build is fine for now. We can always revisit later.

It worked?!!

Oh, I didn't even think to look. It did!

https://hub.docker.com/repository/docker/stringerrss/stringer/general


Check if the library is usable in the browser

Currently, I always use the library with Node.js.
I want the library to be usable in the browser too: need to ensure that.

Hi! It's becoming complex indeed... although I didn't want to.
About the JsonDB.js file, it's must be because it uses Node.js modules to read/write from/into files.
You should take a look at brackets-viewer.js which now imports the manager as a dependency and compiles it with webpack.
It was not implemented by me (the addition of the dependency) so I may not be able to help you with this. I think there is a better way to write the webpack config too, but it works.

I'm really enjoying this library so far. Simple, yet complex :)
I am running into trouble importing the brackets-manager into a Vue.js application. The viewer is fine. It was giving me an error compiling the JsonDB.js file (error below).
I'm curious if anyone has been able to run the brackets-manager project inside a browser app, and if so what their bable/etc. configuration was to make that possible.
Thanks!
Module parse failed: Unexpected token (13:11)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| const JsonDBConfig_1 = require("./lib/JsonDBConfig");
| class JsonDB {
>     loaded = false;
|     data = {};
|     config;

 @ ./node_modules/brackets-manager/dist/storage/json.js 4:23-46
 @ ./node_modules/brackets-manager/dist/index.js
 @ ./node_modules/cache-loader/dist/cjs.js??ref--12-0!./node_modules/babel-loader/lib!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./src/views/Brackets.vue?vue&type=script&lang=js&
 @ ./src/views/Brackets.vue?vue&type=script&lang=js&
 @ ./src/views/Brackets.vue
 @ ./src/router.js
 @ ./src/main.js
 @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080/sockjs-node (webpack)/hot/dev-server.js ./src/main.js

I removed node-json-db as a dependency. So it should work perfectly in the browser as of now.


Apple II language card switch references being used with slot IO index addressing

Apple II language card switch references being used with slot IO index addressing, this makes the code harder to understand due to the incorrect reference.
The following four were used incorrectly
ROMIN    .eq     $c081      ;RWx2 read ROM, write RAM bank 2
ROMIN_RO .eq     $c082      ;RW read ROM, no write
LCBANK2  .eq     $c083      ;RWx2 read/write RAM bank 2
LCBANK1  .eq     $c08b      ;RWx2 read/write RAM bank 1
Maybe checking addressing modes before making some substitutions.
Example for slot based accesses
L2A7D    ldx     $4391
lda     #$00
sta     $c084,x
sta     $c085,x
lda     #$a0
sta     $c086,x
lda     #$01
sta     LCBANK2,x - should be $c083,x
sta     ROMIN_RO,x - should be $c082,x
rts

Yeah, this is a problem.  I've seen many occasions were "LDA some_addr" and "LDA some_addr,x" both mean some_addr, but Apple II I/O is often different.
In 1.6 I've added the Disk ][ I/O locations (this change), but because they overlap with the LC locations I added them as slot 6 $C0En values.  So they don't get resolved automatically, but the symbols are present, which allows you to manually edit operands to get the (kind of ugly):
         lda     IWM_MOTOR_ON-96,x ;start the disk spinning
         lda     IWM_DRIVE_1-96,x  ;select drive 1

(I'm debating changing them from addresses with $C0En values to constants with $C08n values.  They're not getting matched automatically anyway.)
The trouble is that access to $C08n,x could be referring to any slot, including slot 0 (though that's unlikely), so it can't get matched to the "right thing" automatically.
The simple way around it is to add explicit definitions for the relevant $C08n to the project symbol list or to a project-specific symbol file.  These can define the symbol of your choice, or (in a symbol file) use the magic value "erase" to cause SourceGen to forget an earlier definition.  The former is useful if you're working on something specific, the latter if you're working on code that e.g. accesses multiple I/O devices.  For example, you can erase all of the F8ROM zero-page definitions with this.
Another way is to copy the Cxxx-IO.sym65 file into your project, edit it, and include that instead of the platform definition.  You can rename or delete the $C08n defs.
All of these measures feel like hacks, and I'm not happy that they're necessary for a situation this common on the Apple II.  I can come up with something that helps code that touches the LC and one set of slot I/O, but assigning symbols for a single piece of code that accesses I/O locations in more than one slot gets complicated quickly.
One simple change would be to make all $C08n values constants, so none of them are matched automatically, but that's annoying for code that uses the LC.
The approach you suggested -- use LC symbols for $C08n, but leave $C08n,x/y unmatched -- may be the right way to go.  I'd need to define some sort of "exact address only" flag in symbol files.

I decided to just add a separate "C08x-DiskII.sym65" that you can include to overwrite the LC definitions with Disk ][ definitions.  I'm hesitant to add a direct-vs-indexed instruction feature since it adds complexity for a very specific situation.  I'm also concerned that it doesn't fully solve even this problem, e.g. if another peripheral device accessed registers through $C08n,x then you still have ambiguity in the code.
So I took the easy way out for now.

Migrating feature requests to wiki.


Bump max deepspeed version to 0.8.0

What does this PR do?
Requires #16458
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @carmocca @akihironitta @borda @awaelchli @justusschock

CI still installs 0.7.0 😡

@awaelchli using eager helped :)

In the PyTorch GPU CI, the package is still 0.7.0

@awaelchli, as collateral it also updated colossal and all other strategies to the latest in the given range...

I pushed and pulled the docker image per your instructions and now Fabric and PL are installing 0.8.0.

Cool! Let's merge this then


Couldn't find moment datetime adapter

As stated on the home page of the repository, I couldn't find moment datetime adatper. Can it be made available?

Sorry, I noticed the adapter is available in @mat-datetimepicker/moment. I still have issue though. I am using follwing statement for provider
{ provide: DatetimeAdapter, useClass: MomentDatetimeAdapter, deps: [MAT_DATE_LOCALE] },
And getting following error
JobInviteComponent.html:46 ERROR TypeError: Cannot read property 'createDate' of undefined
at<EMAIL_ADDRESS>(mat-datetimepicker-core.js:333)
at mat-datetimepicker-moment.js:52
at range (mat-datetimepicker-moment.js:24)
at<EMAIL_ADDRESS>(mat-datetimepicker-moment.js:52)
at new MomentDatetimeAdapter (mat-datetimepicker-moment.js:32)
at createClass (core.js:8996)
at _createProviderInstance (core.js:8981)
at resolveDep (core.js:9100)
at createClass (core.js:9004)
at createDirectiveInstance (core.js:8881)

Your material version is probably to old/new.


The path retrieved in the logs registered object; is missing the first character.

export_application_logs/tasks/main.yml
...
- file_size: 125873
id: 160
name: messages_19.05.23_<IP_ADDRESS>.log
path: ederation/runtime
type: File
version: '1558616415'
- file_size: 305874
id: 161
name: messages_19.05.23_<IP_ADDRESS>.log
path: ederation/runtime
type: File
version: '1558617566'
...
Calling the rest service directly , works fine.   However; in Ansible, the path is missing the first character.  Verified on 9.0.6

This could be related  to https://github.com/IBM-Security/ibmsecurity/issues/173.  There is a workaround on this comment https://github.com/IBM-Security/ibmsecurity/issues/173#issuecomment-520769222.


Images don't upload to Shopify

Problem
When you put an image in the src/assets/images folder they do not upload to Shopify.
Replication steps
Create new theme, run "yarn start", place image in src/assets/images folder.
More Information
They don't show up in the dist/assets folder either, not sure if they're supposed to?

Hi Cory
Take a look at #658

Looks like this was addressed in #658


nrt:  a bit like cut

I need to describe a cell which is
septated with  one mononucleate and one anucleate compartment
(it basically the same as cut except the nucleus is not bisected)
I'm sure we have this term but I can't find it under spetated
fig 2 A (dn) PMID:10526233

You probably want this one:
FYPO:0001992
name: inviable elongated mononucleate vegetative cell with mislocalized septum
def: "A cell phenotype in which a cell contains a single septum, has one nucleus, is elongated, and is inviable. The septum is in an abnormal location, and the nucleus is located in one compartment of the septated cell."
... it's not connected to cut because if it's only got one nucleus, there's no evidence that the cell attempted chromosome segregation. But if you think the FYPO:0000229 def also covers FYPO:0001992, I can add a link.
FYPO:0000229 septation following abnormal mitotic chromosome segregation (def: "An inviable phenotype observed in the vegetative growth phase of the life cycle in which a cell undergoes septation despite abnormal mitotic chromosome segregation, and gives rise to inviable daughter cells.")

[i] FYPO:0003165 cut
[i] FYPO:0003166 septation following abnormal chromosome segregation, with anucleate cell formation
the FYPO:0003166 def specifies two nuclei, which may or may not be the same size

if the septum is in the middle then maybe this term is more appropriate?
ID 	FYPO:0002000
Ontology 	fission_yeast_phenotype
Term name 	inviable septated mononucleate vegetative cell

... it's not connected to cut because
yeah thats right. Its caused by the same defect, but when  the septum doesn't crash across the chromosomes so it isn't connected to cut.

I think this is closest
FYPO:0001992
name: inviable elongated mononucleate vegetative cell with mislocalized septum
def: "A cell phenotype in which a cell contains a single septum, has one nucleus, is elongated, and is inviable. The septum is in an abnormal location, and the nucleus is located in one compartment of the septated cell."
BUT
it is also true that this is an 'abolished chromosome segregation' phenotype

Hi Val
I have sort of followed this thread and if the septum is in the middle of the cell than I think that FYPO:0001992 is probably not right. Often mis segregation of the chromatin has this phenotype i.e.  In fact the cut phenotype although used a lot seems to be defined differently by different labs. Sorry if I've got the wrong end of the stick .
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo <reply<EMAIL_ADDRESS>Date: Monday, 26 October 2015 21:31
To: pombase/fypo <fypo<EMAIL_ADDRESS>Subject: Re: [fypo] nrt: a bit like cut (#2385)
I think this is closest
FYPO:0001992
name: inviable elongated mononucleate vegetative cell with mislocalized septum
def: "A cell phenotype in which a cell contains a single septum, has one nucleus, is elongated, and is inviable. The septum is in an abnormal location, and the nucleus is located in one compartment of the septated cell."
BUT
it is also true that this is an 'abolished chromosome segregation' phenotype

Reply to this email directly or view it on GitHubhttps://github.com/pombase/fypo/issues/2385#issuecomment-151290598.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

I agree with Jacky
both of these terms have some form of relationship to "abnormal chromosome segregation", via
"septation following abnormal mitotic chromosome segregation":
a. septation following abnormal chromosome segregation, with anucleate cell formation
b. inviable mononucleate monoseptate vegetative cell
both of them seem to apply in this case.

This is complicated.
Summary
When cells cut the nucleus is bisected by the septum. This is a chromsome misegregation phenotype.
Septation occurs in the absence of nuclear division.
When you see this phenotype, you also see co-occuring phenotypes in the population, which are also caused when  septation occurs in the absence of mitosis, but they look a little different because sometimes the chromsomes start to segregate, sometimes the nculeus is not ibsected, but these phenotypes are all a result of a chromsome segregation defect.
In the paper I was curating  they show these:

The top one is WT.
The other phenotypes occur in the 'cut' mutants
i) there is 'arrest', the metaphase anaphase transition does not occur and you just see condensed chromsosomes. No septum forms (relevant checkpoints still active?)
ii) Chromosome separation did not occur correctly  but septation proceeds , septum bisects nucleus (classic cut)
iii) Chromsome separation did not occur correctly  but septation proceeds , septum does not bisect nucleus ..........but is this because the nucleus is displaced, or the septum is displaced or both? Is it possible to say? Another feature of these cells is that they appear to be slightly elongated? Is the septum in the middle but the nucleus containing end continues to grow (possibly). In this example, the septum does appear to be mislocalized, but it might not be ,islocalized in the original cell. The elongation may have occured after spetation????
If this is all true, I suggest:
FYPO:0002000 name: inviable septated  mononucleate vegetative cell
redefine (to make it clear this is a chromosome segregation defect)
def: "An inviable  cell phenotype in which chromosome separation is abolished, but septation has proceeded  resulting in a cell a cell contains a single septum, and the single nucleus  is located in one compartment of the septated cell."
NTR: inviable septated  mononucleate elongated vegetative cell
def: "An inviable  elongated cell phenotype in which chromosome separation is abolished, but septation has proceeded  resulting in a cell a cell contains a septum, and the single nucleus  is located in one compartment of the septated cell.
NTR: inviable septated  mononucleate elongated vegetative cell with mislocalized septum
def: "An inviable  elongated cell phenotype in which chromosome separation is abolished, but septation has proceeded  resulting in a cell a cell contains a septum, and the single nucleus  is located in one compartment of the septated cell.   Elongation is confined to the anucleate compartment, which means that the septum is no longer localized at the  middle of the cell
These should also have a comment "consider also  'cut' and descendants as these phenotypes usually co-occur"
and "cut" should have a similar comment pointing to FYPO:0002000
Would that work? It might require a little rejiggling and possibly a review of existing cut phenotype annotations....

ouch.
I have definitely seen the variation on the last image where the cell has
DNA in only one compartment and the septum is in the "normal" (midpoint)
position. Not sure if those were elongated.
On Tue, Oct 27, 2015 at 10:24 AM, Val Wood<EMAIL_ADDRESS>wrote:

This is complicated.
Summary
When cells cut the nucleus is bisected by the septum. This is a chromsome
misegregation phenotype.
Septation occurs in the absence of nuclear division.
When you see this phenotype, you also see co-occuring phenotypes in the
population, which are also caused when septation occurs in the absence of
mitosis, but they look a little different because sometimes the chromsomes
start to segregate, sometimes the nculeus is not ibsected, but these
phenotypes are all a result of a chromsome segregation defect.
In the paper I was curating they show these:
[image: 10526233]
https://cloud.githubusercontent.com/assets/7359272/10760116/d786487a-7cb2-11e5-8176-8e39a1344459.jpg
The top one is WT.
The other phenotypes occur in the 'cut' mutants
i) there is 'arrest', the metaphase anaphase transition does not occur and
you just see condensed chromsosomes. No septum forms (relevant checkpoints
still active?)
ii) Chromosome separation did not occur correctly but septation proceeds ,
septum bisects nucleus (classic cut)
iii) Chromsome separation did not occur correctly but septation proceeds ,
septum does not bisect nucleus ..........but is this because the nucleus is
displaced, or the septum is displaced or both? Is it possible to say?
Another feature of these cells is that they appear to be slightly
elongated? Is the septum in the middle but the nucleus containing end
continues to grow (possibly). In this example, the septum does appear to be
mislocalized, but it might not be ,islocalized in the original cell. The
elongation may have occured after spetation????
If this is all true, I suggest:
FYPO:0002000 name: inviable septated mononucleate vegetative cell
redefine (to make it clear this is a chromosome segregation defect)
def: "An inviable cell phenotype in which chromosome separation is
abolished, but septation has proceeded resulting in a cell a cell contains
a single septum, and the single nucleus is located in one compartment of
the septated cell."
NTR: inviable septated mononucleate elongated vegetative cell
def: "An inviable elongated cell phenotype in which chromosome separation
is abolished, but septation has proceeded resulting in a cell a cell
contains a septum, and the single nucleus is located in one compartment of
the septated cell.
NTR: inviable septated mononucleate elongated vegetative cell with
mislocalized septum
def: "An inviable elongated cell phenotype in which chromosome separation
is abolished, but septation has proceeded resulting in a cell a cell
contains a septum, and the single nucleus is located in one compartment of
the septated cell. Elongation is confined to the anucleate compartment,
which means that the septum is no longer localized at the middle of the cell
These should also have a comment "consider also 'cut' and descendants as
these phenotypes usually co-occur"
and "cut" should have a similar comment pointing to FYPO:0002000
Would that work? It might require a little rejiggling and possibly a
review of existing cut phenotype annotations....
—
Reply to this email directly or view it on GitHub
https://github.com/pombase/fypo/issues/2385#issuecomment-151513380.

--
Antonia Lock, PhD
PomBase Biocurator, http://www.pombase.org
Department of Genetics, Evolution and Environment,
The Darwin Building,
University College London
London WC1E 6BT, UK

Just to note, we defined 'cut' the phenotype to mean the described phenotype in the original papers:
"Sometimes the septa physically cut through the nucleus producing the classic Cells Untimely Torn (cut) phenotype"
I think "cut" the mutant sometimes is used to refer to the 'collection' of phenotypes observed in 'cut' mutant cells.
The idea is that we capture the individual phenotypes occurring in 'cut' cells and their penetrance. The above would be one of the phenotypes also seen in 'cut' mutant, but is not 'cut' phenotype....but they are all related by:
i) chromosome separation abolished
ii) separation in the absence of chromosome segregation
Agree?

If it is useful to distinguish the "bisected" phenotype from the other
types than I have no problem in continuing to do so.
On Tue, Oct 27, 2015 at 10:38 AM, Val Wood<EMAIL_ADDRESS>wrote:

Just to note, we defined 'cut' the phenotype to mean the described
phenotype in the original papers:
"Sometimes the septa physically cut through the nucleus producing the
classic Cells Untimely Torn (cut) phenotype"
I think "cut" the mutant sometimes is used to refer to the 'collection' of
phenotypes observed in 'cut' mutant cells.
The idea is that we capture the individual phenotypes occurring in 'cut'
cells and their penetrance. The above would be one of the phenotypes also
seen in 'cut' mutant, but is not 'cut' phenotype....but they are all
related by:
i) chromosome separation abolished
ii) separation in the absence of chromosome segregation
Agree?
—
Reply to this email directly or view it on GitHub
https://github.com/pombase/fypo/issues/2385#issuecomment-151521499.

--
Antonia Lock, PhD
PomBase Biocurator, http://www.pombase.org
Department of Genetics, Evolution and Environment,
The Darwin Building,
University College London
London WC1E 6BT, UK

have definitely seen the variation on the last image where the cell has
DNA in only one compartment and the septum is in the "normal" (midpoint)
position. Not sure if those were elongated.

I am sure that I have annotated these. Oddly when I search on
FYPO:0001992 - inviable elongated mononucleate vegetative cell with mislocalized septum)
I only find one result and that is tbf1 (not a cut mutant?)
this is actually annotated to a descendant:
inviable swollen elongated mononucleate vegetative cell with mislocalized septum near new end
so it seems that FYPO:0001992  has no annotations??????

I wouldnt have annotated these to MISLOCALIZED septum.
I would have annotated them to
inviable mononucleate monoseptate vegetative cell and/or
septation following abnormal chromosome segregation, with anucleate cell formation
Though
Query: ( FYPO_ID(FYPO:0003166 - septation following abnormal chromosome segregation, with anucleate cell formation) ) AND ( FYPO_ID(FYPO:0002303 - inviable mononucleate monoseptate vegetative cell) )
This query matches 2 genes.

septation following abnormal chromosome segregation, with anucleate cell formation

that is the term I was looking for.....
But I think these terms FYPO:0003166 and FYPO:0002303  are describing  the same thing?

hmm, hypothetically speaking I suppose you could also get
inviable mononucleate monoseptate vegetative cell
if you have abolished DNA replication?
(would this also come under abnormal chromosome segregation?)

Yes, these exist.
Lots of DNA replication mutants give cut phenotypes too....orc1,4,5 ssp1,2,ssb1,3, rfc2
(especially after HU treatment)
I think it is a type of abolished chromosome segregation (even though chromsomes have not replicated or not fully replicated)?  What you observe is a type of abnormal chomosome segregation...(its an indirect effect)
However, my definitons suggestions above need to change from
"chromosome separation is abolished"
to
"chromosome segregation is abolished"  (abolished chromosome separation would imply that the defect was in the destruction of cohesion which is clearly not true).

I'll take care of the straightforward tickets and then come back to this ...

I would greatly prefer not to add the "chromosome separation is abolished, but septation has proceeded resulting in ..." passage to these definitions. At present, the existing definitions describe what the cells are/what features they have; they do not include any inferences about how the cells got into the observed state, and I would like to keep things that way. I'm happy to put the interpretation in comments.
I also think the ontology has some is_a links that are slightly suspicious. I'll have a thorough look over the terms for this ticket, and most likely change some is_a links to has_part or output_of.
For example, I think FYPO:0002303 should be output_of FYPO:0003166.
In general, the whole-cell descriptions are of phenotypes that are outputs of processes-gone-awry, and if multiple processes are affected, a multi-process phenotype can have single-process phenotypes as parts.
Another example: I ought to change the links for FYPO:0000229 (is-a parent of cut and its sibling) so that it's a process phenotype encompassing premature septation and abnormal chromosome segregation. It'll become:
id: FYPO:0000229
name: septation following abnormal mitotic chromosome segregation
alt_id: FYPO:0000322
alt_id: FYPO:0000323
def: "A cellular process phenotype observed in the vegetative growth phase of the life cycle in which a cell undergoes septation despite abnormal mitotic chromosome segregation, and gives rise to inviable daughter cells." [PomBase:jh, PomBase:mah, PomBase:vw]
synonym: "septation following abnormal chromosome segregation during mitotic cell cycle" RELATED [PomBase:mah]
synonym: "septation following abnormal mitotic chromosome segregation during vegetative growth" EXACT [PomBase:mah]
is_a: FYPO:0001320 ! vegetative cell phenotype
relationship: has_part FYPO:0000141 ! abnormal mitotic sister chromatid segregation
relationship: has_part FYPO:0003250 ! premature septation
There may already be a suitable cell phenotype term to be output_of FYPO:0000229, or I can add one.

Looking at this more closely now, I think FYPO:0000229 et al. should not refer only to abolished chromosome segregation, because the terms should cover cases where segregation starts but goes awry or doesn't finish, as well as where it's really abolished (even when there's a single nucleus, parts of segregation such as condensation may have begun).

For reasons noted in my earlier comments, I can't do everything precisely as requested, but I've made a bunch of changes to has_part and output_of links, and added comments to several terms.
First new term is:
inviable elongated septated mononucleate vegetative cell FYPO:0005023
The name of the second "new" term has no differences from FYPO:0001992, so I added another synonym. Let me know if you need a new term to distinguish the part of the text description where "only the anucleate compartment is elongated".
Apart from the NTR follow-up, let's see how we get on, and open new tickets for additional changes.
edit file: ba9e68937d6ce6e6ade52d2d234d93678e1e5989

release: 181b3899dabcbb4162464ba5e7afb857bd6e6776


Replacement for Twitter Blue logo

Twitter Blue is no longer a thing - what should we replace paid-for checks with instead of the Blue logo?

I guess the flying money emoji lol 💸💸💸


Update RELEASING.md to 1.0.0+ semantic versioning rules.

MSP-12646
Verification Steps

[x] Read changes RELEASING.md
[x] Verify rules match http://semver.org/spec/v2.0.0.html

Post-merge Steps
Perform these steps prior to pushing to master or the build will be broke on master.
Version

[ ] Edit lib/yard/metasploit/erd/version.rb
[ ] Change PRERELEASE back to 'staging/rails-4.0'

failing on travis
There was a NameError while loading yard-metasploit-erd.gemspec:
uninitialized constant YARD from


Fixed akv test failures with win encryption

Skipping over the tests when win encryption is set.

This change is

Codecov Report

Merging #785 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #785   +/-   ##
=======================================
  Coverage   80.06%   80.06%
=======================================
  Files          25       25
  Lines        7323     7323
=======================================
  Hits         5863     5863
  Misses       1460     1460

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9e75dfe...b128820. Read the comment docs.


refactor api-server to include /dates and /coordinates GET methods

Revised swagger definition to include

[ ] /exposures/{exposure_type}/coordinates
[ ] /exposures/{exposure_type}/dates

Reference: environmental_exposures_api/1.0.0

Michael - was this requested?

was this requested

@lstillwe - Requested by me :smile:
I should have it stubbed out in running by today's call.
Will make searching for valid coordinates and date ranges easier in the long run. And hopefully reduces the number of times we need to answer the questions about date ranges and valid points.

👍

merged