text:
[WG Platforms] Platforms Def - What is a platform

Review and finalize "What is a platform" section of Platforms whitepaper: https://github.com/cncf/tag-app-delivery/blob/platforms-v1alpha1/platforms-whitepaper/v1alpha1/paper.md#what-is-a-platform

@joshgav it'd be great to potentially own this section if possible would love to add some details here as well as helping solicit feedback let me know if that works!

Thank you @abhinavm-rafay, that would be great, I went ahead and assigned you here; we can add others if appropriate.
As we chatted, let's try making significant edits via PRs to the platforms-v1alpha1 branch, and having discussions here or in distinct issues as you feel appropriate. Thank you!

It seems like we have some doubts about the naming. We opted for talking about "platforms" in general, but as also understandable from Matthew Skelton's comment, that term is too generic and we probably need to be more specific.

Therefore, an "application platform" (or "internal developer platform/IDP") would be a type of cloud native platform that supports the path to deliver value to the application end-users, from idea to production. But there are more.
Other types of cloud native platforms would be:

core platform (containing only the services necessary to offer a Kubernetes-based environment with security, compliance and access control that could provide the foundation to build special-purpose platforms on top of it).
deployment platform (focused on the final part of the path to production)
data platform (oriented to big data or ML use cases)
observability platform (offering services to monitor, visualize, and work with telemetry and other signals coming from different sources, including other platforms).

I wonder if an "application platform" (which supports the path to deliver value to the application end-users, from idea to production) consists of a deployment platform and observability platform? The path from idea to production always needs deployment and observability, isn't it?

These categories are not standard terminology, so I wouldn't try to use them here. At least, not in this first paper. I would talk more in general about "cloud native platforms" with focus on how we build them, both from a technical and an organisational point of view, and how to provide the best user experience. I'm not a fan of the "developer platform" terminology because application developers are not the only users of the platform. I think that the UX is critical for all users of the platform.

Totally agree, we also had platform users who hosted third-party applications on our platform, but they weren't developers. Although they used the same APIs (gitops-repos, gitlab-pipelines) to deploy there applications on the platform. However, they didn't develop the applications by themselves.
What do you think about the term "container platform"?

Just raising my hand to help here 👍

I'd like to add the Pulumi name & logo for the diagram in this section, likely best fitting in "provide environments and resources". In addition to being a CLI, Pulumi has the Automation API, an SDK to allow platform teams to integrate provisioning in their services, and a Kubernetes operator for provisioning via programs defined as k8s resources in YAML.
I can make a PR to add to the table under #279, however the image is a blob and I don't want to race anyone on trying to edit the diagram in Google Docs.

It seems like we have some doubts about the naming. We opted for talking about "platforms" in general, but as also understandable from Matthew Skelton's comment, that term is too generic and we probably need to be more specific.

Therefore, an "application platform" (or "internal developer platform/IDP") would be a type of cloud native platform that supports the path to deliver value to the application end-users, from idea to production. But there are more.
Other types of cloud native platforms would be:

core platform (containing only the services necessary to offer a Kubernetes-based environment with security, compliance and access control that could provide the foundation to build special-purpose platforms on top of it).
deployment platform (focused on the final part of the path to production)
data platform (oriented to big data or ML use cases)
observability platform (offering services to monitor, visualize, and work with telemetry and other signals coming from different sources, including other platforms).

I wonder if an "application platform" (which supports the path to deliver value to the application end-users, from idea to production) consists of a deployment platform and observability platform? The path from idea to production always needs deployment and observability, isn't it?

I also see an "application platform" as one that comprises all the necessary capabilities to go from idea to production. But I wouldn't define it in terms of a combination of other platform types. In general, I see a "pool" of capabilities that are composed together to achieve a well defined goal. What capabilities to include depends on what we are trying to achieve. Which is why I wouldn't focus too much on platform types, besides providing examples.

These categories are not standard terminology, so I wouldn't try to use them here. At least, not in this first paper. I would talk more in general about "cloud native platforms" with focus on how we build them, both from a technical and an organisational point of view, and how to provide the best user experience. I'm not a fan of the "developer platform" terminology because application developers are not the only users of the platform. I think that the UX is critical for all users of the platform.

Totally agree, we also had platform users who hosted third-party applications on our platform, but they weren't developers. Although they used the same APIs (gitops-repos, gitlab-pipelines) to deploy there applications on the platform. However, they didn't develop the applications by themselves.
What do you think about the term "container platform"?

I see "container platform" as a type of cloud native platforms. Perhaps one I could use as a developer to provide a pre-built container image, and then the platform takes care of the rest. But I wouldn't expect the platform to take care of provisioning databases on Azure (just to make an example), or to take care of supporting the entire software supply chain, or to provide a temporary development environment. But that is a very subjective description, which is one of the reasons why I prefer focusing more on the general architectural style ("cloud native") and the several capabilities that might be part of the final product (in a flexible and composable fashion).

Looking for thoughts and opinions of others on this, To build a platform that can offer services to thousands of customers, cloud providers have an underlying control plane that ensures the desired state of infrastructure that a customer has requested is aligned with the actual state.
If they are not already, the control plane will work to drive the two states to alignment. In simplest terms, the control plane is what translates from the interface exposed to users to actions required to satisfy their requests. A platform is an API that the control plane exposes. A lot of companies like Upbound and many others, here's how to drive the conversation, and here's how they think about the platform, looking for opinions do you think these sentences and terms fall under the definition, if yes, I'm thinking we can drive a similar story forward.

@AaronFriel, we're working on a different place to include examples and other resources. (cc'ing @joshgav)
Can you please move your request into the Capabilities section? https://github.com/cncf/tag-app-delivery/issues/279

Similarly, I like talking about "cloud native platforms" as an architectural style to design and implement platforms that thrive in cloud environments (but they don't have to necessarily run there). That architectural style could be applied to support multiple use cases resulting in different categories of platforms, all sharing the same architectural principles and properties (the ones listed in the paper as "key attributes").

Hi @ThomasVitale
I agree with this as well. The problem is if we get too broad it might not be as impactful for those who are adopting cloud native technologies and need some guidance on what direction to go in. The goal is to provide a clear pathway for those enterprises and companies who have adopted data center/cloud technologies today and are transitioning to building platforms via cloud-native but need some guidance.
@joshgav Any thoughts here?

Looking for thoughts and opinions of others on this, To build a platform that can offer services to thousands of customers, cloud providers have an underlying control plane that ensures the desired state of infrastructure that a customer has requested is aligned with the actual state.
If they are not already, the control plane will work to drive the two states to alignment. In simplest terms, the control plane is what translates from the interface exposed to users to actions required to satisfy their requests. A platform is an API that the control plane exposes. A lot of companies like Upbound and many others, here's how to drive the conversation, and here's how they think about the platform, looking for opinions do you think these sentences and terms fall under the definition, if yes, I'm thinking we can drive a similar story forward.

@Saim-Safdar Agreed on this and this kind of ties in with thomas's comment as well. there is an intended desired state that developers request for and some underlying component/control plane that takes care of this in terms of reconciliation and operations. Not all of this can be delegated simply to the cloud provider because there are other things that need taking care of for example authentication or invoking APIs across multiple cloud platforms to deploy the entire app stack.

Similarly, I like talking about "cloud native platforms" as an architectural style to design and implement platforms that thrive in cloud environments (but they don't have to necessarily run there). That architectural style could be applied to support multiple use cases resulting in different categories of platforms, all sharing the same architectural principles and properties (the ones listed in the paper as "key attributes").

Hi @ThomasVitale
I agree with this as well. The problem is if we get too broad it might not be as impactful for those who are adopting cloud native technologies and need some guidance on what direction to go in. The goal is to provide a clear pathway for those enterprises and companies who have adopted data center/cloud technologies today and are transitioning to building platforms via cloud-native but need some guidance.
@joshgav Any thoughts here?

Yeah, I agree that it's important to give some concrete examples to make it clear to the reader.

Looking for thoughts and opinions of others on this, To build a platform that can offer services to thousands of customers, cloud providers have an underlying control plane that ensures the desired state of infrastructure that a customer has requested is aligned with the actual state.
If they are not already, the control plane will work to drive the two states to alignment. In simplest terms, the control plane is what translates from the interface exposed to users to actions required to satisfy their requests. A platform is an API that the control plane exposes. A lot of companies like Upbound and many others, here's how to drive the conversation, and here's how they think about the platform, looking for opinions do you think these sentences and terms fall under the definition, if yes, I'm thinking we can drive a similar story forward.

@Saim-Safdar Agreed on this and this kind of ties in with thomas's comment as well. there is an intended desired state that developers request for and some underlying component/control plane that takes care of this in terms of reconciliation and operations. Not all of this can be delegated simply to the cloud provider because there are other things that need taking care of for example authentication or invoking APIs across multiple cloud platforms to deploy the entire app stack.

That's a very good point and an important aspect we could elaborate later in the document (perhaps "attributes of platforms"?). Having the platform as a "universal control plane" makes it possible to manage any tool in a consistent and unified way (either running on k8s or externally), while still allowing flexibility to organisations that don't have to go through a big-bang migration but can proceed in small steps and continue using existing tools they spent a lot of money to establish over the years. With the different being that they are integrated with the platform for unified management and control. I really like how Victor Farcic (Upbound) explains this concept in this episode of his show: https://www.youtube.com/watch?v=j5i00z3QXyU

Lots of great thoughts and progress here!
A couple of quick opinions from me:
There is lots of chatter in general in the other issues and slack around examples that are "platforms as a product" and I believe this paper should be focused on helping to point out problems, approaches, and solutions experienced by people, etc, not necessarily what a platform should look/function like. It's up to the products themselves to define the user experience and how they solve problems in their own unique ways, and to what depth.  Those are the same decisions these teams will make when they start developing their own platforms.
To me, the platform is the (almost literal) sandbox that teams play in together to get work done. It's the tangible place folks can go get the information they need, create the resources they need, operate within guardrails, etc, in ways that also fit the business requirements. Not a "one PaaS that rules them all", but an understood collection of tools that work together.
While this isn't a maturity model, and maybe it will grow into one in the future, there should be flexibility in the definition of a platform to make it so it doesn't require 'doing all the things' as some sort of conformance for being a platform.

@ThomasVitale

I would talk more in general about "cloud native platforms" with focus on how we build them, both from a technical and an organisational point of view, and how to provide the best user experience. I'm not a fan of the "developer platform" terminology because application developers are not the only users of the platform.

I like talking about "cloud native platforms" as an architectural style to design and implement platforms that thrive in cloud environments (but they don't have to necessarily run there). That architectural style could be applied to support multiple use cases resulting in different categories of platforms, all sharing the same architectural principles and properties (the ones listed in the paper as "key attributes").

:heart:
I also prefer to call these platforms "cloud" or "cloud-native" platforms, and I also think "cloud" or "cloud-native" is a new architectural style enabled by such platforms. I wrote about it a while ago FWIW: https://blog.joshgav.com/posts/cloud-redefined-infrastructure
IMO "developer" is a bit of a distraction as the value of a cloud platform is mostly in accelerating delivery of value and that doesn't have to involve application developers - think of commercial-off-the-shelf (COTS) software operators, data scientists, information workers, etc. An overemphasis on developers may also be questioned by enterprise leaders.
It has led to heated discussion when an adjective is proposed, and so in fact that's why the WG is just called "Platforms" :laughing:. But I think we might be able to get consensus on "cloud-native platforms" - after all we're developing this as the "cloud-native computing foundation".
@ThomasVitale

In general, I see a "pool" of capabilities that are composed together to achieve a well defined goal. What capabilities to include depends on what we are trying to achieve. Which is why I wouldn't focus too much on platform types, besides providing examples.

Other types of cloud native platforms would be:

core platform (containing only the services necessary to offer a Kubernetes-based environment with security, compliance and access control that could provide the foundation to build special-purpose platforms on top of it).
deployment platform (focused on the final part of the path to production)
data platform (oriented to big data or ML use cases)
observability platform (offering services to monitor, visualize, and work with telemetry and other signals coming from different sources, including other platforms).

@abhinavm-rafay

The problem is if we get too broad it might not be as impactful for those who are adopting cloud native technologies and need some guidance on what direction to go in.

How about we list these "types of platforms" as use cases in the "Why are platforms valuable" section?
We would describe the core notion of cloud-native platforms as collections of integrateable capabilities first, then describe specific sets of such capabilities for particular use cases next.

@jkleinlercher

What do you think about the term "container platform"?

Overcoming the notion of a container "platform" may in fact be part of the reason to publish this paper :laughing:. That is, containers are interesting but they're just one form of compute in a broad platform of capabilities; there are other forms of compute and other capabilities required to build cloud-native apps. Just to illustrate, an enterprise could adopt a build-from-source-oriented compute paradigm using e.g. Knative and hide containers from developers.
@Saim-Safdar

cloud providers have an underlying control plane that ensures the desired state of infrastructure that a customer has requested is aligned with the actual state

Yes! I agree that this is the implementation of a platform many of us believe in, and not coincidentally Kubernetes' controller-manager (or "operator") framework embodies it. FWIW I wrote about that here: https://blog.joshgav.com/posts/kubernetes-isnt-about-containers.
I'm not sure I'd go so far as to say a reconciliation-oriented approach is required for a platform though. For example, some folks may prefer to imperatively run Terraform commands. I think the top-level requirement is to choose and implement consistent interfaces to a complete set of capabilities in some way that fits the needs of the organization and platform users.
Thoughts?

@joshgav I like the idea of the types of platforms
I think we should also think about this from a persona point of view. We have builders and consumers. The builders are typically platform admins. Users can be a developer but can be anybody including platform users or other types of admins themselves. They could be doing security, fin ops, anything.
I think for the paper it should be giving them direction in terms of

what are the pain points today - stitching disparate solutions, not able to create self-service models across your org for different personas, not able to launch new capabilities fast because of governance issues and security
what are different types of platforms
what should a platform encompass - talk about it at a core level, needs to address builder and consumer in terms of solving for some key KPIs (need to lahnch capabilities fast, need a way to authenticate different users) , can have some key capabilities, we can point out examples

I think the key is that while we don't want to be too prescriptive in saying it has to be this way, we should point out some key considerations that organizations need to think about. For example, in order to scale a governance model is needed so that users of the platform don't do anything out of compliance or anything insecurely.
@ThomasVitale @krumware @Saim-Safdar would love to know your thoughts here

@joshgav +1 for the idea of the types of platforms
But the challenge is, as with Kubernetes, comes in many flavors, the platform comes in many flavors, and we need to tell what, when, why, and how to operate, for each of the types of platforms we are about to choose, which ends up in a debate for a certain type of scenario you need this plus a unification of observability platform plus data platform, we might need to have an answer ready for cross-sectional and unification, this might lead us to forget about the core problem we are addressing here, what platform actually does best, I believe we can use the cloud-native maturity model as in conjunction with defining the platform, as we can say the platform has a bear minimum of what tools people use most and ready for interoperability for day 02.
Developer platforms influence the developer experience by letting the 99% developer focus on coding without worrying about infrastructure or how to run their software. But many platforms are also designed with the flexibility to let the 1% developer explore and experiment. The developer platform, supported by architecture, DevOps and SRE teams, contains the ingredients of transformation for all of these teams and roles, fueling improvement in the developer experience, which fuels faster, safer software releases.  Words are taken from this article
What I try to understand here is who is the most consumers or end-user of the platform, is it a developer, SRE, DevOps, FinOps or we can name it, if we have an answer ready, we need to focus more on that consumer and drive the opinion of the community about other roles and we can pinpoint about the bear minimum for others consumers of the platform users. For example, here's the consumer needs platform most of the time, for this certain activity:

Creating a service that automatically deploys to the platform
Editing secrets and automatically redeploying the service
Deploying a branch to a new environment
Accessing logs
Seeing resources that a service consumes For each use case,

Hey all, just following along with interest given the why section will need to make sense with the changes y'all implement.
One thing I am seeing in this thread is a thread of conversation that seems to be moving towards defining concrete platforms that I think is taking us away from the original intention.
I want to bring back the comment from @krumware about a focus on platform as a product that will evolve with the org:

There is lots of chatter in general in the other issues and slack around examples that are "platforms as a product" and I believe this paper should be focused on helping to point out problems, approaches, and solutions experienced by people, etc, not necessarily what a platform should look/function like.

Two trends I am seeing in this conversation are:

Defining platform types The attempt to concretely list types of platforms may lead us down a path that makes readers think we are providing a blue print to success. E.g. "if I just create 4 teams for the core, deployment, data and observability platforms my organisation will be successful". I believe this was an anti pattern when we were previously discussing goals for the paper.

THE platform I think this may be a knock on from the point above, but we seem to be falling into a pattern of talking about THE platform when in our calls I hear people advocating that the platform is the same as any product: Start with something valuable, extend it to cover more uses, and of course split it into more manageable domains as necessary when you need to.

To wrap up, this is a really interesting thread, and as a (mostly) observer I just wanted to share what I am witnessing in hopes it helps converge the interesting ideas into the right set of messages for this white paper. It would be great to refer back to the intention of the paper more (and put that in writing if it isn't already) so that we can all better check that we are staying on course for this paper and allowing other interesting topics to evolve into their own offerings.

Hi @abangser
I agree with this sentiment. Ultimately every organization will have a different version of a platform that fits best to their organization. What we need to do is describe the pain points and give some guidance in terms of key things to look out for key capabilities that are worth investigating etc without getting too prescriptive
this is why imo as I had mentioned in the call a week or two ago that we should have the why section first, or relevant personas. It's hard to describe what is a platform without describing the state of platform teams, what the pain points of platform engineers and developers are and why platforms are needed. I believe putting the why first also allows us to focus more on breadth from the very beginning
@joshgav @abangser let me know your thoughts here but I do think some kind of problem statement and why we're talking about this is crucial before a what is a platform section.

Thank you all for your thoughts. I think we're all agreeing on the notion of platform types, and also agreeing that we don't want to talk about them much in this top-level doc. That is, we specifically don't want to a) canonically define any specific "types" (aka "use cases", "scenarios", "archetypes") or b) get particularly deep into how to implement any given type.
OTOH this conversation leads us to think of getting a bit more prescriptive in later work - for example we might describe a specific type in conjunction with an actual prototype of that type as worked in #293, and reference it from a doc exploring platform types.
My suggestion is we iterate on the existing 6 (2 x 3) use cases listed in the "Why Platforms" section - perhaps one app dev use case, one data science use case and one third-party COTS use case? Our goal with the examples should be to illustrate and help folks understand platforms, again not to formalize any "types" or get too prescriptive. I'll add this suggestion to #274 too.

For those interested, I have taken a stab at swapping the order of why and what sections. Please join in commenting on if this is a useful change in general, and more specifically what about the change would need to change if we were to merge it 🙇♀
https://github.com/cncf/tag-app-delivery/pull/294

Thank you all for #309, #305, #301, #294, #289 and more. The paper is much better after your contributions!

authors: AaronFriel Saim-Safdar ThomasVitale abangser abhinavm-rafay jkleinlercher joshgav krumware

repo: cncf/tag-app-delivery


text:
Table/grid widget

Hi.
First of all, thanks for this great library.
I was looking the documentation and could not find a Table/Grid/Spreadsheet widget.
Is there any?
I just want to show an editable table.
Thanks in advance.

Never mind. Just found it. It's the listbox.

source: gharchive/issue

repo: cnjinhao/nana

license_type: permissive

license_source: github-api


text:
Suggestion: Add badges top of README to track activity, job status, etc

Suggestion
I would like to suggest to add top of the README.md file badges in order to track activity such: contributors, activity = commits, jobs
Example of code:

I would like to tackle this issue

sounds good @xoanmm ... looking forward to your PR!

PR created @nimakaviani : https://github.com/cnoe-io/idpbuilder/pull/263

authors: cmoulliard nimakaviani xoanmm

repo: cnoe-io/idpbuilder


text:
allpix CMakeLists.txt cannot check ROOT compiled C++ version

CMake cannot check ROOT C++ compiled version using build flags:
mauricio.donatti@s-det05-l:~/allpix/allpix-build$ cmake -DCMAKE_INSTALL_PREFIX=../allpix-install/ -DCMAKE_BUILD_TYPE=DEBUG . ../allpix-squared/
-- Git project directory is dirty:
 fatal: not a git repository (or any of the parent directories): .git.
-- Building Allpix^2 version v3.1.0-2-ga552a3f89-dirty.
-- Building "DEBUG"
-- Installing to "/home/ABTLUS/mauricio.donatti/allpix/allpix-install"
-- Unit tests: 20 examples
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- Could NOT find Doxybook2 (missing: DOXYBOOK2_EXECUTABLE)
-- Could NOT find Pandoc (missing: PANDOC_EXECUTABLE)
-- Could NOT find Latexmk (missing: LATEXMK_EXECUTABLE)
-- Could NOT find Lualatex (missing: LUALATEX_EXECUTABLE)
-- Could NOT find Biber (missing: BIBER_EXECUTABLE)
CMake Error at CMakeLists.txt:200 (MESSAGE):
  Could not deduce ROOT's C++ version from build flags: -pipe -fsigned-char
  -pthread

-- Configuring incomplete, errors occurred!
See also "/home/ABTLUS/mauricio.donatti/allpix/allpix-build/CMakeFiles/CMakeOutput.log".
See also "/home/ABTLUS/mauricio.donatti/allpix/allpix-build/CMakeFiles/CMakeError.log".

Current implementation checks ROOT_CXX_FLAGS env variable. It would be better to check ROOT_CXX_STANDARD as shown in ROOT documentation.
This issue has been found on Ubuntu 22.04:
mauricio.donatti@s-det05-l:~/allpix/allpix-build$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

closed by a58d8509b8da04264dd4c2c54d2c12024ce7f038.
View https://github.com/allpix-squared/allpix-squared/pull/49

repo: cnpem/allpix-squared

license: MIT


text:
Change default version for new projects to 0.1.0

I just started using huak (heard about it on the Python Bytes Podcast), and I really like the idea!
I noticed that new projects created with huak new have a default version of 0.0.1. The semver 2.0.0 specification suggests starting at 0.1.0 (which is what cargo defaults to BTW). I suggest to adopt the same convention.
I do realize that this is a matter of preference but I think it's not a bad idea to try to be consistent with the semver spec :)

I totally understand, I guess it's just a matter of what you are used to. I think the people who wrote down semver have in mind that the 3rd digit is really just for bug fixes, and in the pre-1.0 period you can do whatever you want. It's the 1.0.0 that sets the stage for stability. Sounds like your approach is a bit different so I'll let you decide what you prefer :)

I'll add my two cents. Formal standards (such as the mentioned "semver") is a good thing unless they are in conflict with what people actually do :)
In my personal experience, 0.0.X is a popular way to mark the state of the project as something like "ready for sharing as PoC for enthusiasts, not so ready for wide adoption". I come from the field of Deep/Machine Learning, and the recent examples that come to mind are torcheval and tensordict (note how the 0.1.0 released is described as "First official release"). In my personal project, I follow the same strategy: DeLU. However, all this may be just a personal bias :)
Anyway, I think the pre-0.1.0 stage of the project is a thing overlooked by the semver rather that a "bad practice that diverges from standards".

repo: cnpryer/huak


text:
:sparkles: convert genotypes from top to forward

Description

SNPconvert.py was modified to convert data into forward coordinates
Related Issue

closes #111
Motivation and Context

These changes are required if we need to convert data to forward coordinates, for example to create a VCF file
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change which improve code itself)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

coverage: 94.311% (+0.003%) from 94.308%
when pulling 7ac8fa63c7de447ff4f9e63a543d6b58b0e2d12c on issue-111
into bd0c5e6375a79287db2109cbec7fe8886ae24107 on devel.

source: gharchive/pull-request

authors: bunop coveralls

repo: cnr-ibba/SMARTER-database


text:
builtins: introduce builtins for some binary predicates

PR: https://github.com/cockroachdb/cockroach/pull/47584
From release notes:

Added support for ST_Covers, ST_CoveredBy, ST_Contains, ST_Crosses, ST_Equals, ST_Intersects, ST_Overlaps, ST_Touches and ST_Within for GEOMETRY geospatial types. [#47584][#47584] {% comment %}doc{% endcomment %}

The following predicates are now documented:

ST_Covers (#8576)
ST_CoveredBy (#8575)
ST_Contains (#8572)
ST_Intersects (#8574)
ST_Overlaps (#8579)
ST_Touches (#8580)
ST_Within (#8573)

Leaving the following to be done:

ST_Equals
ST_Crosses

authors: jseldess rmloveland

repo: cockroachdb/docs


text:
go txn sample

This change is

Also, which other dev(s) should look at this before it gets merged?

I've assigned David randomly :)

Review status: 0 of 1 files reviewed at latest revision, 2 unresolved discussions.

_includes/app/txn-sample.go, line 42 [r1] (raw file):
I've added some more comments. I'll write a page for the proper explanation now, as we discussed.

_includes/app/txn-sample.go, line 70 [r1] (raw file):
sprinkled some more comments

Comments from the review on Reviewable.io

Review status: 0 of 1 files reviewed at latest revision, 6 unresolved discussions.

_includes/app/txn-sample.go, line 13 [r2] (raw file):
Maybe we can just make them integer "cents", or even "credits" (and rename from bank to something else)

Comments from the review on Reviewable.io

Review status: 0 of 1 files reviewed at latest revision, 6 unresolved discussions.

_includes/app/txn-sample.go, line 13 [r2] (raw file):
@tamird had the same suggestion - integer cents. But... isn't that a shame? Our database has DECIMAL (and apps do use that for money. At least big ones I've worked on in the past). Should we suggest anything less by using ints? It's go's problem that it doesn't have a fixed precision data type (and in fact it does, through 3rd party libs that seems like will make it to the language at some point).
Would a comment about our use of float change your mind?

Comments from the review on Reviewable.io

Review status: 0 of 1 files reviewed at latest revision, 7 unresolved discussions.

_includes/app/txn-sample.go, line 13 [r2] (raw file):
I know this is missing the forest for the trees, but using floats for money, even just in a demo, is going to distract some readers.

_includes/app/txn-sample.go, line 13 [r2] (raw file):
IMO we can just use an integer -- the goal of the hello world txn example isn't to point out that we have a fancy DECIMAL type. Using floats is likely to distract some readers, and i think adding comment about go's stdlib would just be even more of a digression from what we want the example to showcase.

Comments from the review on Reviewable.io

Review status: 0 of 1 files reviewed at latest revision, 7 unresolved discussions.

_includes/app/txn-sample.go, line 13 [r2] (raw file):
OK, let's move to "credits"

Comments from the review on Reviewable.io

So as discussed with Spencer, we're just going to keep it as is but change DECIMAL TO INT and remove all reference to $.

Review status: 0 of 1 files reviewed at latest revision, 7 unresolved discussions.

_includes/app/txn-sample.go, line 13 [r2] (raw file):
recapping offline discussion: we're changing all the examples (including the basic ones) to just use an integer "balance" and not talking about what it is.

Comments from the review on Reviewable.io

Review status: 0 of 1 files reviewed at latest revision, 7 unresolved discussions.

_includes/app/txn-sample.go, line 47 [r2] (raw file):
I think it's weird to connect to a database that doesn't exist yet. The fact that it happens to work seems to me like accidental (and in fact I think it's a bug).
No?

_includes/app/txn-sample.go, line 51 [r2] (raw file):
well what else? We should have a story for timeouts, but I think we're not there yet.

_includes/app/txn-sample.go, line 63 [r2] (raw file):
i preferred to have var explicitly called retryable for clarity

Comments from the review on Reviewable.io

merging. If there's more disagreement (to set or not the database in the conn string) will fix in another PR.

authors: RaduBerinde andreimatei dt jseldess


text:
[WIP] Add v19.1.0-beta.20190318 release notes

For https://github.com/cockroachdb/cockroach/issues/35660.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/390125c3b9c12cfc9c3068ae5893ed63faeb9f0e/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b0953824b564c76aabbbcd5e821764d851de98fb/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f928a3c5b07e83dd8bb4daa55a2262d72c5ed515/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/cc02ac12fa37327c8a3b169c9bb2ceb21cacf7f9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/548634e067ec6e3a3bc0ab39c6d6ad3e35404257/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/913512d9fcbe9eb59fdccdce7c493336ae2e27c2/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b5881da023b545399d1ba18d4ad46f212fe9d0a9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e36af36903c2a8e3e8479f5f2ed5513e0c1f2928/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e36af36903c2a8e3e8479f5f2ed5513e0c1f2928/

authors: cockroach-teamcity jseldess


text:
Correct reference to jekyll-sitemap plugin in base config

Fixes #5859.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4390ba2d414e5871843f9afd9db7d21a516e3978/

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4390ba2d414e5871843f9afd9db7d21a516e3978/

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c8d118364de0b42f1dd9b12acedf921a70d47c06/


text:
Add a separate crate insn_decode in kernel for instruction decoding

This pull request introduces the kernel/insn_decode crate, which provides instruction decoding capabilities. It is implemented by referring the  instruction decoder from the ACRN project. As an acknowledgment, its copyright notice has been included in the header of decode.rs.
Upon a successful decoding for a given set of instruction bytes, a DecodedInsnCtx is created, containing detailed decoding outcomes. This structure exposes two public interfaces that allow access to the corresponding DecodedInsn and the decoded instruction length.
Currently, the crate supports decoding for the in/out, rdmsr, wrmsr, rdtsc, rdtscp, and cpuid instructions, which are essential for the current SEV #VC handler. So the #VC handler has been revised to utilize this crate for instruction decoding. The test suite is also expanded to cover all the aforementioned instructions. But due to the lack of an AMD machine on my end, this pull request has not been tested on an actual hardware. Appreciate it if someone can help to try this PR on an actual AMD machine.

In-SVSM tests and regular boot work with these patches.

Thanks @00xc for the help to try this PR on the hardware! Really appreciate that!

repo: coconut-svsm/svsm


text:
CC0022 DisposableVariableNotDisposedAnalyzer: False positive for containers

#Bug
This should not trigger CC0022:
public class Test : IDisposable
{
    private readonly List<IDisposable> _streams = new List<IDisposable>();

    public Test()
    {
        _streams.Add(new MemoryStream());
    }

    public void Dispose()
    {
        foreach (IDisposable disposable in _streams)
        {
            disposable.Dispose();
        }
    }
}

@oysteinkrog Bug confirmed!

authors: carloscds oysteinkrog

repo: code-cracker/code-cracker

license_source: bigquery


text:
add an option to answer builder to fetch and update existing answers

right now AnswerGroupBuilder always creates a new set of answers. Give an option to update existings answers.

Any news?
I'm trying to do it this way, I know it's not the best one:
def build_answer_group
      @answer_group = AnswerGroup.where(user: user, question_group: question_group).first_or_create
      if @answer_group.answers.blank?
        @answers = @question_group.questions.collect do |question|
          @answer_group.answers.build(question_id: question.id)
        end
      else
        @answers = @answer_group.answers
      end
    end

Moreover, I've added a field to AnswerGroup to know if the survey is completed, because I give to users only one attempt.

the code is in a separate branch, i have to bring it to latest master, and make a release.
code reference: https://github.com/code-mancers/rapidfire/commit/43f285f7de341da1102df2133ef4663cf2065ed8

Great job!

What about this issue, will be merged? is insecure use this in my production app?

@brunoocasali this should get merged. i added this issue to never ending v3.0.0 release. hopefully should be able to release it soon.

This PR fixes it https://github.com/code-mancers/rapidfire/pull/85. Thanks @leonhooijer

authors: brunoocasali iffyuva marcolong

repo: code-mancers/rapidfire

license: mit


text:
Handle additional audit result details

User story
As an user, I want to be able to add additional details to my plugin results to be able to provide meaningful information to the report consumers in addition to issues. At the moment the existing option issues is insufficient for information that is related to more than one line of code.
Acceptance criteria

[ ] The details field of an AuditDetails should provide a new optional property for additional information
[ ] The information is displayed in the md format of reports

Implementation details

To start with a details type that matches most of the available data we could introduce a table type.
This information should get displayed after the issues if present.
The details should have issues and table optional.

Types:
type Headings = {
    key: string;
    label?: string;
}

type Table = {
  headings: Headings[]
  items: (unknown | Record<string, unknown>)[]
}

Examples:
const list: Table = {
  items: [ 'Tina', 'John' ]
}

Output:

Tina
John

const tableOfItemsOnly: Table = {
  items: [
    { name: 'Tina', age: 42, height: 165},
    { name: 'John', age: 21, height: 172},
  ]
}

Output:

name
age
height

Tina
42
165

John
21
172

const tableWithHeading: Table = {
  heading: [
    { key: 'name' },
    { key: 'age'},
  ],
  items: [
    { name: 'Tina', age: 42, height: 165},
    { name: 'John', age: 21, height: 172},
  ]
}

Output:

name
age

Tina
42

John
21

const tableHeadingLabels: Table = {
  heading: [
    { key: 'name', label: 'Name'},
    { key: 'age', label: 'Age'},
  ],
  items: [
    { name: 'Tina', age: 42, height: 165},
    { name: 'John', age: 21, height: 172},
  ]
}

Output:

Name
Age

Tina
42

John
21

Example Before:

Largest Contentful Paint (Lighthouse)
🟨 3.2 s (score: 73)
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Example After:

Largest Contentful Paint (Lighthouse)
🟨 3.2 s (score: 73)
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
LCP Breakdown:

Phase
% of LCP
Timing

TTFB
27%
620 ms

Load Delay
25%
580 ms

Load Time
41%
940 ms

Render Delay
6%
140 ms

Element:
<img _ngcontent-ng-c1817005767="" alt="poster movie" class="aspectRatio-2-3 gradient" width="154" height="205" loading="eager" fetchpriority="high" ng-img="true" src="https://image.tmdb.org/t/p/w185/hu40Uxp9WtpL34jv3zyWLb5zEVY.jpg" srcset="https://image.tmdb.org/t/p/w185/hu40Uxp9WtpL34jv3zyWLb5zEVY.jpg 185w, http…" sizes="(min-width: 600px) 21vw, 15vw">

Research
Community plugin on measuring style usage
Example of the current output in the md report:

lighthouse reports
Lighthouse is a perfect example for considering this new detail property as a LHR provides a multitude of additional information that is at the moment not possible to be included in details.
Here a list of possible lighthouse audit results and how they are displayed on their end.
Example of Details.Debugdata
{
    "details": {
      "type": "debugdata",
      "items": [
        {
          "cumulativeLayoutShiftMainFrame": 0.000_350_978_852_728_593_95
        }
      ]
    }
}

Example of Details.Opportunity
{
        "details": {
          "type": "opportunity",
          "headings": [
            {
              "key": "url",
              "valueType": "url",
              "label": "URL",
            },
            {
              "key": "responseTime",
              "valueType": "timespanMs",
              "label": "Time Spent",
            },
          ],
          "items": [
            {
              "url": 'https://staging.code-pushup.dev/login',
              "responseTime": 449.292_000_000_000_03,
            },
          ],
          "overallSavingsMs": 349.292_000_000_000_03,
        }
      },

Example of Details.Table in Details.List
   {
      "scoreDisplayMode": "informative",
      "displayValue": "2,240 ms",
      "details": {
        "type": "list",
        "items": [
          {
            "type": "table",
            "headings": [
              {
                "key": "node",
                "valueType": "node",
                "label": "Element"
              }
            ],
            "items": [
              {
                "node": {
                  "type": "node",
                  "lhId": "page-0-IMG",
                  "path": "1,HTML,1,BODY,1,APP-ROOT,0,APP-SHELL,2,DIV,2,DIV,1,CT-MOVIES-LIST,0,ARTICLE,2,UI-MOVIE-LIST,0,UI-GRID-LIST,0,A,0,IMG",
                  "selector": "ui-movie-list > ui-grid-list > a.ui-grid-list-item > img.aspectRatio-2-3",
                  "boundingRect": {
                    "top": 175,
                    "bottom": 413,
                    "left": 30,
                    "right": 189,
                    "width": 158,
                    "height": 238
                  },
                  "snippet": "<img _ngcontent-ng-c1817005767=\"\" alt=\"poster movie\" class=\"aspectRatio-2-3 gradient\" width=\"154\" height=\"205\" loading=\"eager\" fetchpriority=\"high\" ng-img=\"true\" src=\"https://image.tmdb.org/t/p/w185/hu40Uxp9WtpL34jv3zyWLb5zEVY.jpg\" srcset=\"https://image.tmdb.org/t/p/w185/hu40Uxp9WtpL34jv3zyWLb5zEVY.jpg 185w, http…\" sizes=\"(min-width: 600px) 21vw, 15vw\">",
                  "nodeLabel": "poster movie"
                }
              }
            ]
          },
          {
            "type": "table",
            "headings": [
              {
                "key": "phase",
                "valueType": "text",
                "label": "Phase"
              },
              {
                "key": "percent",
                "valueType": "text",
                "label": "% of LCP"
              },
              {
                "key": "timing",
                "valueType": "ms",
                "label": "Timing"
              }
            ],
            "items": [
              {
                "phase": "TTFB",
                "timing": 618.4395,
                "percent": "28%"
              },
              {
                "phase": "Load Delay",
                "timing": 108.52322934454139,
                "percent": "5%"
              },
              {
                "phase": "Load Time",
                "timing": 1359.7222634888808,
                "percent": "61%"
              },
              {
                "phase": "Render Delay",
                "timing": 156.7545071665777,
                "percent": "7%"
              }
            ]
          }
        ]
      }
    },

Other audits to exclude:
A Lighthouse result contains a couple of audits that have no score.
There are multiple scenarios that I was able to track down:

The provided URL is not accessible. In this case all audits have a score of null but are still present in the result.
If the URL is valid, the following scoreDisplayMode have a score of null:

informative
notApplicable
manual

Here a screenshot:

LHR example:
report.json

Hello @BioPhoton
A table type would be really helpful.
Also, it would be great, because we can also add as much info as we need to and not be blocked by the 1048 max chars (hope so).
Also, what would be great, is to have some global css classes for basic styling (pills (success, warning, error))
I see that you already added DS component styles usage. And the table option would be a perfect fit for that one.

closed by #667

authors: BioPhoton eneajaho

repo: code-pushup/cli


text:
Cannot run oc login when running in vsock mode and using Docker Desktop with Kubernetes activated

General information

OS: macOS / Windows

Steps to reproduce

Start Docker Desktop
Activate Kubernetes
Start CRC with vsock mode
Try oc login

Description
Both apiserver of Kubernetes in Docker Desktop and authentication server of OpenShift in CRC are using the same port 127.0.0.1:6443.
OpenShift web console works because it uses port 443 (https://oauth-openshift.apps-crc.testing/login/htpasswd_provider), but the CLI uses the other port.
First, we can detect this issue by checking the port is free before starting the daemon and/or doing crc start.
We can also change the port of the authentication server. kube-apiserver is not configurable in Docker Desktop.

If you deploy an application in Docker Desktop k8s which uses port 443, will it also try to open it on localhost? This issue is about port 6443 / Docker desktop, but since vsock is using a shared host resource (port number allocation), we're bound to be having conflicts here and there. Hopefully it won't happen too much, but I think we won't know before it's more widely used.

If you deploy an application in Docker Desktop k8s which uses port 443, will it also try to open it on localhost? This issue is about port 6443 / Docker desktop, but since vsock is using a shared host resource (port number allocation), we're bound to be having conflicts here and there. Hopefully it won't happen too much, but I think we won't know before it's more widely used.

authors: cfergeau guillaumerose

repo: code-ready/crc


text:
hyperv: Add support for updating memory used by the VM

WIP implementation at https://github.com/cfergeau/machine/commit/ab9ca038898e8638bec71cd9cb18f29e31226029

This is needed by https://github.com/code-ready/crc/issues/1522

all done :tada:

repo: code-ready/machine


text:
bug: Mobile UI is not responsive and Spelling error "watch hostory"

Describe the bug
In the mobile view the website is not responsive very hard to navio through other chapters. And there is a spelling mistake in the side menu "watch hostory"
To Reproduce
Steps to reproduce the behavior:

Do something
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots or GIFs

Info (please complete the following information):

Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

the typo has been fixed not yet merged

Hello @sachinshrmaa I would like to work on this, main issue is that sidebar don't close automatically on small screens, I will do that and will show the refresh database on while the sidebar is open


text:
Trouble opening the PDF

"Data is protected. If you are using 12 Step Meeting List, consider setting data sharing to open."
I saw that others had this issue and the resolution was to go to the settings under Data, but I do not see that option.
Maybe I am just in over my head as usual:)

That's correct, go to Wordpress Dashboard > Meetings > Import & Settings > Feed Management > Feed Sharing and set Restricted to Open.

For what it's worth, I think it's time to get rid of this setting.

authors: JenniferWallis joshreisner


text:
Add rubocop-rspec_rails to beta

Same thing as #367 for the beta channel
Rubocop-rspec has extracted the rails cops to rubocop-rspec_rails

the cops related to rspec-rails are aliased (RSpec/Rails/Foo == RSpecRails/Foo) until v3.0 is released

https://github.com/rubocop/rubocop-rspec/blob/master/CHANGELOG.md#2280-2024-03-30
So it would be nice to support it before v3 is released

@fede-moya any chance this could be merged?

+1 in getting this into beta. At the moment this particular issue is breaking our CodeClimate integration. We would like to not have to remove departments from the configuration. Open to the option to have CodeClimate ignore these departments, if there is one.

authors: fonji hallelujah vietqhoang

repo: codeclimate/codeclimate-rubocop


text:
x = _i += 10 doesn't work (like emitted by CoffeeScript compiler)

x = _i += 10

Aether apparently doesn't handle this sort of operation properly, instead just doing the _i += 10 part. Interestingly, it does handle x = _i++ and x = ++_i.

Fixed with @basicer's new Esper interpreter.

repo: codecombat/aether


text:
Java language version

what Java language version are you targeting?
Can you successfully parse lambdas and method references?
Thank you

Hello @LeanderK!
The target is the AP subset, it's now described here I'm not sure if they changed the subset from February but I don't think so, I checked quickly and it looks like the same 😄 !
So no lambdas…
Also as far as I remember there's an issue with private methods because JavaScript (ECMAScript 5 original target) used to handle privates in a very differently from how JAVA handles privates…

ok, thank you for your Help!

authors: LeanderK lucasfarias

repo: codecombat/cashew


text:
New female and male names added!

Female = Anabel, Paulark
Male = Eugen, Toremon

Great–can you sign the CLA so we can merge this in?

authors: dheerajdake nwinter

repo: codecombat/codecombat


text:
add Standardized Curricula in teacher resources hub

in order to show the localized standardized curricula we add a new title in teacher resources hub. look at the red square. yellow square is China specific content. and if other country has similiar curricula they can add here, too.

@nwinter any problem now? can i merge this pr?


text:
[WIP] Trying out some different components from Tailwind UI

Trying out some different Tailwind UI components

closing in favor of #109


text:
[CCAP-482] update provider response info review

🔗 Jira ticket

✍ Description

📷 Design reference

✅ Completion tasks

[ ] Added relevant tests
[ ] Meets acceptance criteria

Also, duh, there's a broken test but I'm sure you'd notice that regardless 😄

I like where you're going with this. In your Loom, you said there's some inconsistency with the names of inputs which is what is causing you to have to pass around a different prefix string or something-- why not just use this PR to 100% clean that up and create the consistency you're looking for? I vote for going through all that effort now, and have the end result be the cleanest version of the code possible -- especially since you've already identified the issue -- vs having it almost there and still being slightly annoying with some workaround built in?
Maybe I'm misunderstanding though, and doing all that cleanup is essentially impossible?

That's a really good point. The cost of doing it now is relatively less than doing it later since I've identified the issue. Thank you! Appreciate the feedback.

authors: analoo cram-cfa

repo: codeforamerica/il-gcc-form-flow


text:
capture non-case-sensitive DIBELS levels

DIBELS level are no longer case-sensitive so e.g., both "Core" and "CORE" will be captured in the profile
included "Benchmark" as "Core"

Refer to #73 for details

repo: codeforamerica/somerville-teacher-tool


text:
Remove 00-0000 All Occupations from soc-list endpoint

This is present in the occupation list but does not produce results. We should remove it from the soc-list.

Fixed as part of https://github.com/codeforboston/jobhopper/pull/257

Fixed as part of https://github.com/codeforboston/jobhopper/pull/257

closed per lillian

closed per lillian

authors: alexjball jedpittman l-cheung

repo: codeforboston/jobhopper


text:
Database design/database creation

We have several user needs that will require the storage of data.

log-in /password recovery
storage of certain client information
certain data inputs that are temporarily stored)/visualizations for each client.

Being worked on; let me know if you want to join.

repo: codefordc/clean-slate


text:
[Bug Report] - Mismatching passwords not shown on pod creation

Describe the bug:
The user is required to confirm their password when creating a new account, however the password in "Confirm Password" is not checked against the "Password" field. You can create a new account with mismatching passwords (Password, Confirm Password).
Expected behavior:
I would expect client side validation to block submission until the passwords match.
Actual Behavior:
You can successfully create an account with mismatching password (the primary?)
Screenshots:
This would work:

To Reproduce:
Steps to reproduce the behavior:

Go to /signup
Attempt to create an account with different passwords
...
Success?

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Possible Fix:
We should block submission and show an error, additionally password strength validation (length etc.) seems to be missing as well.

Bitwarden 🙌

Hey @AJSterner was curious if you're still doing this bug fix? I could start up a branch and get this patched up. 👍

authors: AJSterner andycwilliams leekahung

repo: codeforpdx/PASS


text:
Codeigniter\Entity - Fix ToArray datamap

Description
There are couple of issues with the way datamap works

It keeps doubles the values original and mapped where only mapped should be kept
If datamap is used on existing attribute it will not work properly as value is already processed through data map in the getter
When unsetting the key we need to double check if there is not another map that uses the key in $to map as if unset it won't be accessible in the next loop

I've added the getSwappedEntity() method which returns the entity which is affected by all those issues.
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

This PR is not final yet. This is just to understand the issue. I'm thinking about more elegant solution to avoid having all those checks and do everything in single foreach loop.
As datamap already works on magic getter the idea is to properly prepare keys and then run foreach loop to get values using those keys.
The way to prepare those keys will be done like this

get all keys of $this->attributes let those be named $keys
filter out keys starting with _underscore from $keys
get unique values fro the $this->datamap let those be named as $mapped_keys
filter out the $mapped_keys from the $key
Append all keys from $this->datamap to $keys
Run single foreach $keys as $key and pouplate $results with $this->__get($key)

Let me know what you think about doing it this way

I've submitted another commit which will handle this by processing keys first

I like this. Nice and clean solution.

@najdanovicivan

I've added the getSwappedEntity() method which returns the entity which is affected by all those issues.

You added the swapped case, but do you really need the use case?
It seems it gives users a lot of complexity.
If we prohibit it, the Entity would be simpler.

authors: kenjis michalsn najdanovicivan


text:
indexing pdf content

Hi
I have problem with indexing pdf files.
It's seams that mime type is not recognized, because content of pdf file is not extracted.
It just store file context like '%PDF-1.4 %�쏢 5 0 obj <> stream x��}K���nxf|��/� ....
Same results with xls, doc files
Could you help me please ?
Thank you

Is there the file on internet?
I'd like to reproduce the problem.

Hi
Yes, file is on internet for public access.
http://www.csas.cz/static_internet/cs/Komunikace/Interni_komunikace/Informacni_kniha/Prilohy/TOP_Business_sdeleni_klientum.pdf
But i think the problem is not in file.
Did i undestand correctly, that river-web is indexing content of pdf directly or should i uses attachment plug-in ?

authors: jirkaMat marevol

repo: codelibs/elasticsearch-river-web


text:
Getting rate limiting issue?

Hi all,
First, thank you guys for very amazing tool.
I tried Newspaper to get list articles from a publisher by following the REAME file, however, the obtained significantly decline after each time I build the source.
`>>> import newspaper

cnn_paper = newspaper.build('http://cnn.com')
No handlers could be found for logger "tldextract"
print(cnn_paper.size())
222
cnn_paper = newspaper.build('http://cnn.com')
print(cnn_paper.size())
6
cnn_paper = newspaper.build('http://cnn.com')
print(cnn_paper.size())
1
`

Am I getting rate limitting or have I done somthing wrong? Thank you
Btw, here is the environment: Ubuntu 14.04, Python 2.7.6, newspaper for python2

Sorry, I just found caching on the docs. Please close this.

Newbie.  Also receiving this error.
No handlers could be found for logger "tldextract"
Thanks.

Great module!  Also receiving this error.
No handlers could be found for logger "tldextract"
for row in range(ws.nrows):
# read second column URL only
url = ws.cell_value(row,1)
# extract only primary domain name - not subdomain
eresult = tldextract.extract(url)

repo: codelucas/newspaper


text:
Parsing issue - UnicodeEncodeError in get_parsing_candidate()

import newspaper
article = newspaper.Article(url='http://waynemessick.com/marketing/small-business-internet-marketing-advertising-strategies')
article.download()
article.parse()

Causes:
Traceback (most recent call last):
  File "/home/yuri/repos/newspaper/newspaper/article.py", line 166, in parse
    parse_candidate = self.get_parse_candidate()
  File "/home/yuri/repos/newspaper/newspaper/article.py", line 333, in get_parse_candidate
    return RawHelper.get_parsing_candidate(self.url, self.html)
  File "/home/yuri/repos/newspaper/newspaper/utils.py", line 59, in get_parsing_candidate
    raw_html = raw_html.encode('utf-8')
UnicodeEncodeError: 'utf-8' codec can't encode character '\ude7e' in position 13277: surrogates not allowed

Also encountered on:
http://tayloringit.com/2016/03/ltmooc16-level-2-a-facilitators-reflection-on-artificial-intelligence-ai/
http://newmoonmanifesting.com/thirst-for-innovation-aquarius-new-moon/


text:
v5 Vim custom commands

First of all, thanks for the marvelous job you do!
I researched that editor commands are loaded for the execution in the : command input
Is there any possibility to define a custom command by myself like ":wq" to close the window?

I'm not aware of the vim mode supporting custom commands, but I'm not deeply familiar with it and the docs are known to be incomplete. Still, since this is the bug tracker, I'm going to close this since it's a question, not a bug.

@marijnh Can you please tell me, where can I ask this question?
As I found out, vim gets commands from the global command registry of the editor. So can I somehow set custom command to the editor?

You can assign to CodeMirror.commands.[name] to define new commands in the editor. Asking questions is best done on the forum.

As I found out, vim gets commands from the global command registry of the editor.

Nope, use CodeMirror.Vim.defineEx. As Marijn said, RTM: Extending VIM.

authors: ElijahKaftanov benhormann marijnh

repo: codemirror/CodeMirror


text:
Added a new theme: yonce

Adapted from the popular Bash-It/Visual Studio Code/iTerm/Slack & Alfred theme, Yoncé, by @minamarkham. I say "adapted" as VSCode themes are very complex and allow for a bit more nuance, so I did the best I could. Along those same lines, only ASCII characters seem to work with the demo page, for whatever reason, so I changed the é to an e.
Licence from the original VSCode theme:
https://github.com/minamarkham/yonce-vscode/blob/master/LICENSE
More info:
https://yoncetheme.com/

Nice, thanks. Merged as 2c123a4a

authors: marijnh thomasmaclean


text:
feat: support toggle extent

#99

This pr still have a issue that i don't know how to fix :

When toggle the extent button , it can't immediate render

This is this PR's behavior
https://user-images.githubusercontent.com/76603360/207765493-a8b937d3-4067-46f2-b007-1092d7ed69b8.mov

@sudongyuer What will happen if you move the scope after the code cell has been moved out of it? Is the parent of the cell updated to the scope at the outer layer?

@sudongyuer What will happen if you move the scope after the code cell has been moved out of it? Is the parent of the cell updated to the scope at the outer layer?

https://user-images.githubusercontent.com/76603360/207772790-c79dd567-371c-485f-9e23-4770c4284563.mov

You can see more contexts in #99

The node's parent will not change , it will remain the relationship before

@sudongyuer yes, i saw the discussion in #99. Should we update the parent then? Otherwise, the code scoping is not correct.

@sudongyuer yes, i saw the discussion in #99. Should we update the parent then? Otherwise, the code scoping is not correct.

I just think this pr is to control the extent option in node , if you want to remove node's parent relationship , should be better add another feature  to support that . Also need some suggestions from @lihebi

Controlling only the "extent" option itself doesn't make a useful feature. We should implement the logic for updating node parent relations in this PR.

Screen.Recording.2022-12-16.at.13.20.56.mov

Thanks!
When you click the release button, the pod "jumps" out. It is because you updated its parent but didn't update its position (which is relative to the parent). We don't want that jump.

[xinyi] you should update nodesMap[id].level recursively as well
[forrest] Is recursive updating necessary?
[xinyi] It's always necessary to update the levels

Xinyi had explained it. Just an echo: Xinyi was talking about recursively updating the levels property of descendant nodes, which is missing in this PR.

[forrest] After a user clicks the "remove extent" button of a cell/scope, the cell/scope will move with the mouse.

To make things simple, we could just drop the node to ROOT scope when the release button is clicked. We probably want to show some indicators (e.g., a highlighted shadow) to mark it global. Then we can drag-n-drop to the location.

[xinyi] what will a collaborator see during the process of changing scope?

This will no longer be a problem if we adopt the "drop-to-ROOT-scope" approach above.

[xinyi] you should update nodesMap[id].level recursively as well
[forrest] Is recursive updating necessary?
[xinyi] It's always necessary to update the levels

Xinyi had explained it. Just an echo: Xinyi was talking about recursively updating the "levels" property of descendant nodes, which is missing in this PR.

[forrest] After a user clicks the "remove extent" button of a cell/scope, the cell/scope will move with the mouse.

To make things simple, we could just drop the node to ROOT scope when the release button is clicked. We probably want to show some indicators (e.g., a highlighted shadow) to mark it global. Then we can drag-n-drop to the location.

[xinyi] what will a collaborator see during the process of changing scope?

This will no longer be a problem if we adopt the "drop-to-ROOT-scope" approach above.

Thx xinyi ~

authors: forrestbao lihebi sudongyuer

repo: codepod-io/codepod


text:
Use CMD to allow running a shell inside the container

Describe in detail the problem you had and how this PR fixes it
I can't start the container with /bin/sh to debug it.
Is there an open issue you can link to?
No but I hope this https://stackoverflow.com/a/21564990/4446318 helps explain the issue better than I can.

No you can't just if no container is running.
docker run image bash will fail cause bash is no argument. Additionally if ever the code-server binary will fail to start on startup you have no easy way to debug this. You would need to build a docker image based on this on to get into that container. Entrypoint is meant to be used to change the shell or to add helper scripts at startup.

I don't think its limited JUST for helper scripts. ENTRYPOINT was designed for applications to take arguments during run. Which is basically a glorified exec passing.
If you really want to run bash in it, don't do it via docker run. Run the image first then docker exec.
It's easier to debug it while running rather than slapping CMD which does not allow us to pass more args if needed.

Yes, it is.
I mean I could just build my own image, too. Doesn't solve the problem.
If it is not running you can't debug it and my container wasn't running.
CMD only needs the executable in it otherwise it does the same here.
So the only change would be that all docker-compose users with a command entry need to append code-server at the beginning.

@SuperSandro2000 I appreciate your concern but the issue for us is we want to keep the docker one-liner as short as possible.
You have two options for debugging.

Start the container and then use docker exec.
Start a new Dockerfiles and use the COPY instruction to copy the binary from our image into your own and set it up however you want.

Ah, you actually want docker run  --entrypoint=/bin/bash. That should work.

I literally listed your debug ideas already and said why they are not ideal.
docker run --entrypoint=/bin/bash
That is more useful. Thanks

repo: codercom/code-server


text:
[WIP] 統計情報ページで道場数がグラフとテーブルでズレている

https://coderdojo.jp/stats にて、推移グラフと推移テーブルがあるが、道場数のみ、この値が異なっている。
cf, #340 (comment)

集計結果に 2013 年が含まれていない理由を調査中...
[1] pry(main)> period = Time.zone.local(2012).beginning_of_year..Time.zone.local(2017).end_of_year
=> Sun, 01 Jan 2012 00:00:00 JST +09:00..Sun, 31 Dec 2017 23:59:59 JST +09:00

[2] pry(main)> Dojo.aggregatable_annual_count period
=> {"2012"=>5, "2014"=>9, "2015"=>4, "2016"=>30, "2017"=>30}


text:
Add ability to check and fix Django settings

Add CodeRed Cloud Django settings templates.
Check for wsgi.py. If it cannot be found, check if the django_project might be set incorrectly and offer to set it.
Check for Django settings file. If it doesn't exist, offer to create it from a settings.py.
Check and rewrite Django settings file(s) if they seem to be missing references to important environment variables such as VIRTUAL_HOST or DB_HOST.

Housekeeping:

Move env to webapp __init__ instead of args on utility methods.
Upgrade pyinstaller
Fix formatting of spec file (also include new templates dir)

Note: PATCH-ing the custom_django_project in coderedapi currently redeploys the webapp. In this case, that is undesired behavior as we are trying to fix this pre-deployment. We should probably change coderedapi before releasing this feature.
The code here seems quite inelegant and/or side-effect heavy. I guess that is the nature of what we are trying to do, with a lot of dependent nested logic. But open to suggestions on practical ways to organize it better (api.py file is getting a bit massive)

API.py is getting a bit dense and hard to follow. It seems the overwhelming majority of this size comes from django specific logic checks/fixes, so it would make sense logically to move these checks into a django_checks.py file.

I split out the individual checks into separate functions in utils. Then split high-level checking on the Webapp into separate functions. I'm a bit happier with it, and it should be mostly test-able now.

repo: coderedcorp/cr


text:
Start with catchy example and collaborate on the beginning

Maybe use a more fleshy example to start with, working on documentation collaboratively (instead of everyone creating empty doc from scratch). Show what can be done.

Would be fun but cannot introduce this for the upcoming workshop since we have this lesson on the first day. Once we move to a later day we can start from a real example and go collaboratively.

Done in b1581099463cfa36e75cba957f62041f5826fe6f.

authors: bast rlonka

repo: coderefinery/documentation


text:
Issue 26 create text related reusable components

Change Summary
Added the following components:

Field_Input, for HTML's <input>
Field_TextArea, for HTML's <textarea>
Field_Radio, for HTML's <radio> (the radio button asks for a binary "yes" or "no")

These components are results of the combination of issue 26 and 9
They have hard-coded CSS though, may need to update at some point
There is a page to test these out called form_testing
Change Form
Fill this up (NA if not available). If a certain criteria is not met, can you please give a reason.

[x] The pull request title has an issue number
[x] The change works by "Smoke testing" or quick testing
[ ] The change has tests
[x] The change has documentation

Other Information
[Is there anything in particular in the review that I should be aware of?]

Hey,
I noticed that after merging this branch with main, some of the CSS stopped working. I'm pretty sure it's because of the updated tailwind.config.css file.
I wasn't sure on how to go about it so I just made a very quick fix by putting in one-off RGB values instead of tailwind's classes.
Is this good enough for now or should I update anything?

Hey, I noticed that after merging this branch with main, some of the CSS stopped working. I'm pretty sure it's because of the updated tailwind.config.css file.
I wasn't sure on how to go about it so I just made a very quick fix by putting in one-off RGB values instead of tailwind's classes.
Is this good enough for now or should I update anything?

This is probably because we've overriden the tailwind colours instead of extending them. Could you make a fix in this?

@yelnats8 All good. Just merge with main and you're set to merge

repo: codersforcauses/repair-labs


text:
Aggiungere test

Essendo un progetto open source sarebbe meglio aggiungere anche i test.

Io avevo in mente di fare i test quando si interpellava mongo, per non avere problemi dopo.

Io avevo in mente di fare i test quando si interpellava mongo, per non avere problemi dopo.

repo: codershub-it/CodersHub-Bot


text:
Service cards theme updated

resolves #170

Kindly show your output so that I can review

perfect


text:
title is not in the center

@codervivek5 plz assign me this issue

please assign it to me @codervivek5 .

Please give me a chance to resolve the title alignment issue (#2400) on the location-based shopping website.


text:
Update README.md

This is a test. Do not merge.

Going to close 😅

authors: bnb jaclynj

repo: codespaces-examples/node


text:
Display black poster in empty inline video

Prevent newly inserted video content element from collapsing.
REDMINE-17742

Coverage remained the same at ?% when pulling 465e256324aff89c69ad9d0e16fce92d25da9ddb on tf:video-default into c3d225f006789617ed5ae387875ec4498ae1c183 on codevise:master.

Travid build passed but failed to report back to PR.

authors: coveralls tf

repo: codevise/pageflow


text:
Update @nx/workspace to 20.0.0

Update Nx from 19.8.4 to 20.0.0

Auto-generated by create-pull-request

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.63%. Comparing base (80f98da) to head (b271eaa).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #170   +/-   ##
=======================================
  Coverage   97.63%   97.63%
=======================================
  Files          17       17
  Lines         211      211
  Branches       30       30
=======================================
  Hits          206      206
  Misses          5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter hakalb

repo: codeware-sthlm/nx-plugins


text:
Release v0.12.4

This PR acts as a release commit for changes made in #43.
Changes required by steps 1-3 of https://design.codidact.org/setup/releasing/ are completed upon merging this PR.
An errant v0.12.4 tag needs to be destroyed in this repo and this PR's contents tagged as that after this is merged. Then step 6 needs to be followed, or we could change the deployment scripts/GitHub pages source to use develop instead.
Someone will still have to release using NPM publish - I would recommend setting up a user we can use as a bot and in the event that no npm releasers are otherwise available.
//cc @cellio

I think we should probably release this as 0.12.5. ISTR that there was a 0.12.4 release that we pulled because it broke things, not that I can remember what. Trying to release another 0.12.4 on top of that might cause issues.

This means bumping the change in the three files that edited the version number and...what else?  (Several files show as "large diff".)  I'd really like to be able to get this co-design change pushed out to qpixel and the communities.

This means bumping the change in the three files that edited the version number and...what else? (Several files show as "large diff".) I'd really like to be able to get this co-design change pushed out to qpixel and the communities.

Full steps to release are at https://design.codidact.org/setup/releasing/. Change version number, commit any changes, create an npm and git version, and npm publish.

authors: ArtOfCode- cellio sau226

repo: codidact/co-design


text:
No visualizers generated in VS2017 15.8 Preview 3

I have rebuilt my solution several times, but the visualizer assemblies are not being generated. Are there any other VS2017 extensions that may be blocking the operation?

Hi, I doubt other extensions could conflict with this one but I can't exclude it for sure. The visualizer assembly generation is bound to the compilation process, so the problem lies either in the installation process or on the folder permissions --> Documents\Visual Studio 2017\Visualizers .
One thing that could help me identify the issue is to have the log files (you have to enable logging in the option menu), Also if you could enable error reporting I would see the exceptions coming through in Sentry.
Please check out the guide on how to enable logs and/or error reporting here

Will do
Get Outlook for iOShttps://aka.ms/o0ukef

From: codingadventures notifications@github.com
Sent: Friday, July 6, 2018 12:00:22 PM
To: codingadventures/LINQBridgeVs
Cc: Mike Stacey-Gee; Author
Subject: Re: [codingadventures/LINQBridgeVs] No visualizers generated (#47)
Hi, I doubt other extensions could conflict with this one but I can't exclude it for sure. The visualizer assembly generation is bound to the compilation process, so the problem lies either in the installation process or on the folder permissions --> Documents\Visual Studio 2017\Visualizers .
One thing that could help me identify the issue is to have the log files (you have to enable logging in the option menu), Also if you could enable error reporting I would see the exceptions coming through in Sentry.
Please check out the guide on how to enable logs and/or error reporting herehttps://github.com/codingadventures/LINQBridgeVs#bridgevs-option-menu
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/codingadventures/LINQBridgeVs/issues/47#issuecomment-403002075, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQGEzUJNJYzYqUzSrnTD3zr3T2ZeiRMCks5uD0NGgaJpZM4VFKPO.

Hi,
I have enabled error reporting and logging. After several rebuilds there is no log file.
Regards
Mike
From: codingadventures notifications@github.com
Sent: 6 July 2018 12:00
To: codingadventures/LINQBridgeVs LINQBridgeVs@noreply.github.com
Cc: Mike Stacey-Gee MikeStacey-Gee@esdm.co.uk; Author author@noreply.github.com
Subject: Re: [codingadventures/LINQBridgeVs] No visualizers generated (#47)
Hi, I doubt other extensions could conflict with this one but I can't exclude it for sure. The visualizer assembly generation is bound to the compilation process, so the problem lies either in the installation process or on the folder permissions --> Documents\Visual Studio 2017\Visualizers .
One thing that could help me identify the issue is to have the log files (you have to enable logging in the option menu), Also if you could enable error reporting I would see the exceptions coming through in Sentry.
Please check out the guide on how to enable logs and/or error reporting herehttps://github.com/codingadventures/LINQBridgeVs#bridgevs-option-menu
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/codingadventures/LINQBridgeVs/issues/47#issuecomment-403002075, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQGEzUJNJYzYqUzSrnTD3zr3T2ZeiRMCks5uD0NGgaJpZM4VFKPO.

That is very odd. I haven't got anything new either in Sentry. Please check the registry here \HKEY_CURRENT_USER\Software\LINQBridgeVs (refers to the section How it works in the readme). If the installation went well and also you bridged your solution correctly you should find in the registry your solution listed:
\HKEY_CURRENT_USER\Software\LINQBridgeVs\15.0\Solutions\yoursolution
As a side note: which OS are you using? What type of solution are you trying to map (c#, vb, f#)

Hi,
I found out the problem. The preview version of Visual Studio install itself in C:\Program Files (x86)\Microsoft Visual Studio\Preview instead of C:\Program Files (x86)\Microsoft Visual Studio\2017 which is the default installation folder for Visual Studio 2017. Thus during the first configuration the relevant .target files needed to override the MSBuild process don't end up in the correct folder.
To fix this issue please copy the folder v15.0 and its content from C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\v15.0 to C:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise\MSBuild\v15.0
The next time the solution is rebuilt the visualizers are correctly generated

Thank you for investigating, very much appreciated. This explains why it works on a remote VM in my office where the standard VS2017 is installed.
Get Outlook for iOShttps://aka.ms/o0ukef

From: codingadventures notifications@github.com
Sent: Saturday, July 7, 2018 11:41:39 AM
To: codingadventures/LINQBridgeVs
Cc: Mike Stacey-Gee; Author
Subject: Re: [codingadventures/LINQBridgeVs] No visualizers generated in VS2017 15.8 Preview 3 (#47)
Hi,
I found out the problem. The preview version of Visual Studio install itself in C:\Program Files (x86)\Microsoft Visual Studio\Preview instead of C:\Program Files (x86)\Microsoft Visual Studio\2017 which is the default installation folder for Visual Studio 2017. Thus during the first configuration the relevant .target files needed to override the MSBuild process don't end up in the correct folder.
To fix this issue please copy the folder v15.0 and its content from C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\v15.0 to C:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise\MSBuild\v15.0
The next time the solution is rebuilt the visualizers are correctly generated
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/codingadventures/LINQBridgeVs/issues/47#issuecomment-403206501, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQGEzfsCPvvVqVZT5fY3xjyu269UXiRzks5uEJBjgaJpZM4VFKPO.

Thanks for reporting the issue, I added a section in the README in case someone else has the same problem.

authors: MikeStacey-Gee codingadventures

repo: codingadventures/LINQBridgeVs


text:
Open a PR for new functionality

Add a new branch for the new functionality
Write specs, open a PR

https://github.com/codingalone/grumlin/commit/f7115f18159a8a924c356d8aa2c5cdec7963a858

Opened a pull request
https://github.com/babbel/grumlin/pull/83

repo: codingalone/grumlin


text:
Appveyor version

We need to research how Appveyor set the project versions and what do we need from it.

Closed by 19572b4ae05c96fef332fbef9bfef4e82d76486e.

repo: codingteam/naggum


text:
[Image-M1] Wrap image management / dedup mechanism into library

Move file upload & hash generation code from https://github.com/cofacts/rumors-api/pull/273 to a separate Node.JS repository with the following functionality:

setup GCP credential
upload image
search for near duplicate result given a query image
documentation

Currently opened https://github.com/cofacts/media-manager

main branch: bootstrapped with tsdx
[WIP] MediaManager class implementation  https://github.com/cofacts/media-manager/pull/1/files

repo: cofacts/rumors-api


text:
Thumbnail & preview for video and audio files

Current media variant settings: https://github.com/cofacts/rumors-api/blob/4b00d586e44cb6aa15c858e9c945b8ea4c67d3bc/src/graphql/mutations/CreateMediaArticle.js#L61-L82

Current logic only generates variants for images
We need to modify the logic to handle video and hopefully audio
Need to determine a size for thumbnail (website & LINE bot list page) & preview (website detail before login)
ffmpeg is already included, so just use it :)

ffmpeg is quite CPU intensive.
New proposal is to use Transcoding API + Google cloud function that listens on GCS change.

Detail: https://g0v.hackmd.io/aJqHn8f5QGuBDLSMH_EinA#Video-summarization-for-thumbnails
Initial Proposal: https://g0v.hackmd.io/@cofacts/meetings/%2FucUXvnqbRBmsD6YGkmdYvg

Hi, can you assign this issue to me, please?

Hi @ndcroos thanks for commenting! Would you share with us your idea on how to implement this?

authors: MrOrz ndcroos


text:
[Trivial] expose user.appId for all users & all apps

In the user profile page for LINE bot users, I want to tell site visitors that this user is from LINE and its username / avatar is randomly generated. Therefore, I would like to expose user's appId.
Currently I cannot think of reasons why we kept it for current user. No concern is documented in the design document either. This PR removes the restriction.

Coverage decreased (-0.05%) to 86.143% when pulling 760468d51b90546657fdee727232b582434937d6 on expose-user-appid into 9cf53b702f56c252cc19f9e0f7ccb818071d417b on master.

authors: MrOrz coveralls


text:
Move checkpointing code from Composable onto _checkpointable class

All attributes, methods related to checkpointing should be moved onto the writer classes (which inherit from _checkpointable.
Specifically, the methods Composable.job_done() and the attribute Composable.checkpointable should be shifted onto _checkpointable. The redundant attribute self._checkpointable should be removed.

We have eliminated support for checkpointable apps.


text:
Training MSNet3D error

I am trying to train MSNet3D on stereodriving and KITTI2015 but faced this error:
File "train.py", line 205, in
train()
File "train.py", line 98, in train
loss, scalar_outputs, image_outputs = train_sample(sample, compute_metrics=do_summary)
File "train.py", line 155, in train_sample
disp_ests = model(imgL, imgR)
File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 161, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/opt/conda/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 171, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/opt/conda/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 86, in parallel_apply
output.reraise()
File "/opt/conda/lib/python3.8/site-packages/torch/_utils.py", line 428, in reraise
raise self.exc_type(msg)
RuntimeError: Caught RuntimeError in replica 0 on device 0.
Original Traceback (most recent call last):
File "/opt/conda/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 61, in _worker
output = module(*input, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/trainer/mobile_stereo/models/MSNet3D.py", line 124, in forward
out1 = self.encoder_decoder1(cost0)
File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/trainer/mobile_stereo/models/MSNet3D.py", line 46, in forward
conv5 = F.relu(self.conv5(conv4) + self.redir2(conv2), inplace=True)
RuntimeError: The size of tensor a (4) must match the size of tensor b (3) at non-singleton dimension 2
Does anybody know how to solve this problem?
Looking forward to your reply！

What arguments are you giving the train.py function?

Thanks for your reply
I am giving these arguments:
python train.py --dataset drivingstereo --datapath /home/trainer/Datasets/drivingstereo/ --trainlist ./filenames/ds_train.txt --testlist ./filenames/ds_test.txt --epochs 400 --lrepochs "200:10" --batch_size 1 --test_batch_size 1 --model MSNet3D  --logdir ./log_drivingstereo/

I freshly pulled the code and used the same arguments as you did (only changing the data path), but I can't replicate your error.

When does it throw the error?

When does it throw the error?

3D-mobilestereonet can not reach the test results of kitti2015，why？thanks。I used the MSNet3D_SF_KITTI2015.ckpt you provided.We submitted the parallax map to the kitti website, but the results were very different from those in the paper. In the paper, it is 1.75 3.87 2.10 1.61 3.50 1.92, but what I measured is 2.01 4.40 2.40 1.85 3.88 2.18, is it the wrong way for me to fine-tune, or is it for some other reason? Please help me.

authors: YznMur flyxuexi samuel-woerz

repo: cogsys-tuebingen/mobilestereonet


text:
Choose H2O datasets in A/B tests

Closes #654
Disable 0.5 GB datasets by default in A/B
Simplify running 50 GB tests (cc @hayesgb )

@crusaderky
We have some conflicts now because I've merged the PR to run the individual A/B tests.
If you can fix them and include the data paths for the cases that you consider useful for tests, this is good to go.

The 50GB datasets consistently fail on a cluster of 200 m6i.large workers. I'd rather treat the proper investigation on what's needed to make them go through as out of scope for the purpose of this PR.

The 50GB datasets consistently fail on a cluster of 200 m6i.large workers. I'd rather treat the proper investigation on what's needed to make them go through as out of scope for the purpose of this PR.

Which clusters?
I'm looking at all clusters with >100 m6i.large workers in the last two weeks and I only see one: test_h2o-f9339777
But I do see two clusters with 1200 m6i.large workers, test_h2o-66b8ca9c and test_h2o-4f710b97.
Is it possible you were trying 1200 workers instead of 200?

The 50GB datasets consistently fail on a cluster of 200 m6i.large workers. I'd rather treat the proper investigation on what's needed to make them go through as out of scope for the purpose of this PR.

@crusaderky when you say they fail is this for all the datasets?
I would expect this not to be great for the case when the data was saved as categories, and for the case of pyarrow strings, if the code stays the same, this implies that we are not casting the types upon reading, causing these columns to be read as python strings (this will imply way bigger memory usage)
But I have been able to successfully run the queries in https://github.com/coiled/h2o-benchmarks/blob/main/h2o_benchmarks_2022-10-0_pyarrow_str_50GB.ipynb with 10 t3.large workers.

@crusaderky when you say they fail is this for all the datasets?

Complicated answer. After every test, you get a restart, but if a test kills off a worker the next, unrelated test will be messed up too. I've also seen failures in the cluster dump. So short of adding a flag that says "don't call client.restart, but instead nuke the whole cluster and rebuild it from scratch after every test" I'd need to kick off the tests one by one to answer you.
Also, with 200 workers it took more than 2 hours to run and it got killed off by github CI - thus no final report.

I'm looking at all clusters with >100 m6i.large workers in the last two weeks and I only see one with 200 workers: test_h2o-f9339777
But I do see two clusters with 1200 m6i.large workers, test_h2o-66b8ca9c and test_h2o-4f710b97.
Is it possible you were trying 1200 workers instead of 200?

The overview for all the clusters you linked shows 200. There were 6x calls to client.restart, which restarted the worker, not the host - so 1200 worker processes, 200 at a time, on 200 hosts.

@ncclementi am I clear to merge?

The overview for all the clusters you linked shows 200. There were 6x calls to client.restart, which restarted the worker, not the host - so 1200 worker processes, 200 at a time, on 200 hosts.

Ick. Okay, yeah, I didn't see that you keep getting 200 new workers, thanks for pointing that out. That's not good that running this killed all your workers and also that those clusters ran for multiple hours.
If the result of merging this is that we'll regularly run clusters like the test_h2o clusters that I linked to, I don't think that's good and would ask you hold off on merging.
If this wouldn't be part of regular coiled-runtime runs, then I don't have any immediate concerns.

No, this is to be explicitly enabled on a ad-hoc basis. We will normally run the 5gb datasets only.

Sounds good, thanks!
On Mon, Jan 16, 2023 at 4:59 PM crusaderky @.***> wrote:

No, this is to be explicitly enabled on a ad-hoc basis. We will normally
run the 5gb datasets only.
—
Reply to this email directly, view it on GitHub
https://github.com/coiled/coiled-runtime/pull/655#issuecomment-1384681547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALBFDHTBGGRRJ3XN6COW56TWSXOEZANCNFSM6AAAAAATVP3X2I
.
You are receiving this because you commented.Message ID:
@.***>

@crusaderky it looks like the failure is unrelated, merging this one!
Thank you for your work.

authors: crusaderky ncclementi ntabris

repo: coiled/coiled-runtime


text:
feat: experimental work on WM draft2

WM2 Experimentations
Mostly following these WICG/webmonetization PRs/issues:

BREAKING CHANGE: consolidate events
BREAKING CHANGE: use Navigator interface instead of Document
BREAKING CHANGE: use  element instead of
More complete state machine

Also experimented with PPK navigator.monetization.pointer getter/setter proposal. This behaves similar to document.title modifying/adding <title> in the document <head>. set localStorage.WM_POINTER_PROPERTY to truthy value then reload to enable for evaluation/experiments.
Once the new branch of WICG/webmonetization is ready, extension will match that.
Preview Extension
Published @ CoilPreview https://chrome.google.com/webstore/detail/coilpreview/iehmfkldnblennopinmmagfidpflefkp

0.0.64 - Wed Nov 24 18:52:09 +07 2021 - pending
0.0.63 - Sat Nov 20 11:07:45 +07 2021 - published
0.0.62 - Fri Nov 19 12:56:04 +07 2021 - published

TODO

[x] Add navigator.monetization object (0.0.?)
[x] Add navigator.monetization.state with 'idle' or 'interactive' values (0.0.?)

[x] TODO: don't map pending to interactive (0.0.61)

[x] Emit "statechange" events from navigator.monetization (0.0.?)
[x] Emit "monetization" events from navigator.monetization (essentially "monetizationprogress" events) (0.0.?)
[x] Add document.monetization.pointer experiment (matching document.title <->  behavior) when localStorage.WM_POINTER_PROPERTY defined (0.0.61)
[x] Log statechange events when WM_DEBUG set (0.0.61)
[x] Add MonetizationEvent and MonetizationStateChangeEvent Event subclasses (0.0.62)

[ ] TODO: marcos says will only be one event class MonetizationEvent
[ ] TODO: does it matter if have rich set of event classes, if they aren't exposed on window ?

[x] Add update available notification for CoilPreview extension (0.0.63)
[x] TODO: change paymentPointer in monetization event to url (PR)

[ ] [QUESTION] Make sure only link tag requests (i.e. urls) are routed to navigator.monetization ?

[ ] just normalize to an url ? enforce link tags if navigator.monetization api accessed ? "don't worry be happy" ?
This is more a question for WM1/WM2 side-by-side implementation

[ ] [QUESTION] Implement  Navigator#activeMonetizationElement ?

Marcos says this will be a "private" slot. So essentially an impl detail??

[x] [QUESTION] MonetizationEvent actually has type progress ( marcos said no in previous meeting iirc )

it's definitely just "monetization"

[ ] [QUESTION] Will SPSP be endowed with some kind of receipt validation

See https://github.com/interledger/rfcs/issues/582

[ ] [QUESTION] Should we drop requestId ?? (Web-Monetization-Id already deprecated in favor of receipts)

Ben is in favor of dropping it, but has back-compat concerns "do it additively"
Back compat by keeping v1 around in extension, but leave v2 spec clean?

[ ] Enforce urls only in link tags (see: https://github.com/coilhq/web-monetization-projects/pull/1009/files)
[ ] Link tag @attrs implementation, what attrs? CORS ? what will need an observer ?

Closing as no longer tracking the older spec branch

repo: coilhq/web-monetization-projects