[DSA]: <IP_ADDRESS> Explain Knuth–Morris–Pratt algorithm(Strings)-Audio

Description
Discuss the Knuth Moris Pratt Algorithm. Mention about its implementation, complexity, examples.
Task

[ ] Audio

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

Domain
DSA
Type of Contribution
Audio
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Do you want to work on this issue @Palak-Srivastava ?

Yes @Muskan-creator Maam, Can I?


UI epileptic when opening dependent optionset without chromium browser (Mozilla)

Hello,
I have this issue where the dependent optionset is blinking when I use none chromium browsers.
Am I the only one getting this UI issue ? Do you have any idea on how to fix it ?
I use the <IP_ADDRESS> verison.
Thank you very much and great job !
https://user-images.githubusercontent.com/65252004/207320559-8387b8ae-9f0e-4142-9ee8-f6be9e8a2eba.mp4

Hello,
I plan to do some rework of the control (I have a cool idea for the configuration) so I can check the issue you reported. What browser should I use to reproduce this behavior?
Thanks,
Andrew

Is it safe to say that it's FireFox?

Hello,
I am sorry for the late answer, I am personnaly using mostly chrome or
edge.
Cool, I will be waiting for the new configuration !
Nathan
Le mar. 10 janv. 2023 à 02:30, Andrew Butenko @.***> a
écrit :

Is it safe to say that it's FireFox?
—
Reply to this email directly, view it on GitHub
https://github.com/AndrewButenko/ABControlsToolkit/issues/13#issuecomment-1376597453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APR2VJDI2AP3YUKAPNN6YG3WRS3VHANCNFSM6AAAAAAS5FFPXA
.
You are receiving this because you authored the thread.Message ID:
@.***>


add code generation support for array of arrays, for example: [[string]]

Fixed by https://github.com/gilt/apidoc-generator/pull/19

This has been implemented and is in production. Thanks @haywood !


Outline how CAW is best utilized by other projects

The usefulness of this effort will be heavily affected by how easily we can share updates across projects that use it. We have been operating under the assumption that this is mainly a boilerplate that though some effort a forked project could be updated against down the road.
What would it look like to distribute this code as a package in the vein of create-react-app's react-scripts. There would likely be a devision between what is currently housed in this repo and what would belong in a package like this—utils, generators, ESLint/prettier config. If we go this route we need to do some research into how to best achieve it. Being able to consume this for web, mobile, and API projects should also be a goal (because who has time to maintain three of these 😖).

Something to keep in mind is the more that we put behind a package à-la react-scripts the less that consumers will be able to customize to their needs. In a lot of cases this is a good thing, but for something like how storybook or webdriver are configured there may need to be a way for consumers to customize it.

@blaketarter yup—that's what we need to figure out 👍

For now—we are maintaining this as a template repo. Let's reassess in the future 👍


Error message in modal after project deletion

Describe the bug
If a directory containing a project is deleted and the project is edited afterward, an unclear error message can appear:
project 68384.6497895014 not found in cache

Version
1.0.2
OS

[x] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create a project
Remove the folder from the filesystem
Perform some change to the project
See modal with unclear error message

@VanyLaw be aware of the error message during "start bot". we need to provide more detail info.

@hibrenda moving to R11

@hibrenda Seems like this issue happened during opening bot not starting bot. It's the error message popup in home page.

We will have this fixed in R11 (due to be released in November).

Let's refine the message to "path" doesn't seems to be exists anymore.


Enable configuration of doc navigation menu

One request we get commonly is how to disable parts of the navigation menu. I've consider some how we might overhaul our navigation menu, and this probably overlaps with a version 2 of the menu.
Whatever the technical solution is, the outcome would be:

User decides they don't want a section on the navigation menu
User sets an option
Navigation menu no longer includes the section (downloads, versions, edit on github, etc) -- either on future builds (build files are altered), or on all builds (api return is altered).

We don't necessarily need to wait for a version 2 to implement this, we can alter the HTML return as well. I think JSON data return from an API and client side JS to display the navigation menu is a stronger approach however, and gives a great amount of flexibility.
What is the UX for hiding?
There are several options, control of the navigation menu could be:

A theme option, or html context data
Performed in a RTD dashboard page

Which route we go also alters how we technically approach the problem.
Theme options to control this make sense perhaps, but how does this interact with RTD? Going this route means future builds are altered through the use of a theme option, existing builds wouldn't be affected. This is probably fine.
Javascript to display the theme would be templated and altered through the Sphinx build process.
If we go the route of changing the JSON return, or even changing the HTML return for now, we can do this dynamically for all built versions, but would need a dashboard page for configuring this. This wouldn't be awful, but is against our current focus to reduce the dashboard UI.

Nevermind. I think API driven flyout menu is what we actually want. We've discussed theme support and our flyout as well, and offering a flyout api that themes can consume probably would make the most sense.

Related https://github.com/rtfd/readthedocs.org/issues/5570

This is an ongoing conversation that we are having now with the new addons project: https://github.com/readthedocs/addons/issues/51. I'm closing this issue from here so we can continue talking in the other repository.


Enhancement: analysis Dict now provides total delay as well.

analysis Dict now has a total_delay key which contains the total delay over all hops in the email trail.

Thanks! @babhishek21 🎉


How to serialize / deserialize?

Looking at the code presently it seems to be very stateful and I don't think it's possible to serialize and deserialize the objects, so I'll find a way to work around it.
However, the application I'm trying to build allows multiple web and mobile users. Obviously I don't want to store all of that state in memory, so I need to be able to serialize and deserialize the object frequently - including the cookies.
Currently I'm bouncing back and forth between this and the python version trying to figure out how the api works and how to best accomplish my goals, but both are hard-coded for a single user. :-/
If it doesn't fit into your long-term goals to make this support an unlimited number of users simultaneously, I can't complain, but if it is I'll give some more specific feedback (most notably the cookie jar needs to be accepted and exportable) and pull requests if I can.

I've partially implemented serialize / deserialize methods here https://github.com/coolaj86/node-pokemap
They're not quite ready for a pull request as there seems to be something missing (or the servers are simply misbehaving as-per usual), but I think I'm almost there.


Enable consumers to skip failure to resolve dependencies

Describe the Enhancement
I would like to find a better solution for callers of postal.Service.Resolve() to identify that no dependencies were resolved without failing the build.
Currently this is possible, but it relies on inspecting the returned error text. That is brittle, and I'd like to find a better solution.
Motivation
The specific use-case I have in mind is splitting out precompiled dependencies from source dependencies (e.g. in the cpython buildpack) via different IDs/names and resolving them independently. In this scenario, we would like to be able to bypass the failure associated with resolving zero precompiled dependencies, while still failing if there are zero source dependencies resolved.
Possible Solutions
Below are multiple ways to achieve this, ordered by my most-preferred to my least-preferred solution.

Return newly-created specific error types to postal (e.g. ErrNoDependenciesResolved, ErrMultipleDependenciesResolved) which would allow consumers to introspect the error as follows:
precompiledDependency, err := service.Resolve()
if err != nil && !errors.Is(err, postal.ErrNoDependenciesResolved) {
  // fail
}

Pros:

Does not change the interface of the function (i.e. it is backwards-compatible)
There is precedent for this in golang (e.g. if err != nil && !errors.Is(err, fs.ErrExist){ ... })

Cons:

This is the most complex option for consumers
Adds the most code to the postal package
Introspecting on error types is an ugly way to manage control flow for non-failure cases

Add number of dependencies resolved as part of the result (e.g. func Resolve() (Dependency, int, error)))
precompiledDependency, count, err := service.Resolve()
if err != nil && count != 0 {
 // fail
}

Pros:

Fairly easy to read and understand

Cons:

Not backwards-compatible
Somewhat inelegant

Allow users to pass in some config to skip the failure entirely (e.g. func Resolve([existing args] , skipNoDepsFail bool) (Dependency, error) or func Resolve([existing args], config SomeNewConfigType) (Dependency, error)))
precompiledDependency, err := service.Resolve([existing args], true)
if err != nil { // err is nil when zero dependencies are resolved
 // fail
}

Pros:

Simple for consumers; keeps consumer flow clean
Fairly easy to read and understand

Cons:

Not backwards-compatible
Quite inelegant.

cc @paketo-buildpacks/tooling-maintainers - I am happy to create a PR for this but I'd like feedback on which direction we prefer.

I'd lean towards option 1 for a couple of reasons:

It has precedent as a pattern in the Go ecosystem
It is the only backwards-compatible option

I like option 1 because it allows consuming code to be very explicit about which errors to handle - reading the buildpack code will make it obvious that the buildpack won't fail if no dependencies are resolved. Also, +1 for backward compatibility.

Great, looks like we have a clear consensus that the way we'd like to see this feature implemented is via specific error types - the first option I outlined.
Thanks for the thoughts everyone. I'll submit a PR for this.


year needs to update dynamic in footer section #33

PR Description 📜
In Footer year now updating dynamically
Fixes # 33

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ] I have added screenshot for website preview in assets/images
[ ] I have added README.md in my folder

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Hello @trishanu-init please add my name in assignee so it will count in gssoc 24 please

Done
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: KAPIL GUPTA @.>
Sent: Friday, May 24, 2024 7:50:23 PM
To: Indie-Kart/ecommerce-store @.>
Cc: Trishanu Nayak @.>; Mention @.>
Subject: Re: [Indie-Kart/ecommerce-store] year needs to update dynamic in footer section #33 (PR #35)
Hello @trishanu-inithttps://github.com/trishanu-init please add my name in assignee so it will count in gssoc 24 please
—
Reply to this email directly, view it on GitHubhttps://github.com/Indie-Kart/ecommerce-store/pull/35#issuecomment-2129648471, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUM5X4IKDHWB2YOCJ5K4S53ZD5ECPAVCNFSM6AAAAABH5DO756VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGY2DQNBXGE.
You are receiving this because you were mentioned.Message ID: @.***>

Done Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
…
________________________________ From: KAPIL GUPTA @.> Sent: Friday, May 24, 2024 7:50:23 PM To: Indie-Kart/ecommerce-store @.> Cc: Trishanu Nayak @.>; Mention @.> Subject: Re: [Indie-Kart/ecommerce-store] year needs to update dynamic in footer section #33 (PR #35) Hello @trishanu-inithttps://github.com/trishanu-init please add my name in assignee so it will count in gssoc 24 please — Reply to this email directly, view it on GitHub<#35 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUM5X4IKDHWB2YOCJ5K4S53ZD5ECPAVCNFSM6AAAAABH5DO756VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGY2DQNBXGE. You are receiving this because you were mentioned.Message ID: @.***>

Thank you 😊


Reusable containers are not affected by classpath property

So according from what I've seen in the code here it's by intention that the reusable test containers config is not picked up from the classpath, which IMO is very confusing. While running my tests, I don't expect that I need some kind of "setup" (even though it's optional) before I can simply run my ./gradlew test, neither locally or inside of my CI.
Is there a workaround for it?

It is an optimization, not prerequisite.
See https://github.com/testcontainers/testcontainers-java/pull/1781#discussion_r369160221


Move releases to GitHub

Due to the tarnished reputation of Sourceforge as a "hotbed of malware" 1, 2, 3 many users would be remiss in downloading software from the site.  Cutting a release and moving the binaries into GitHub (and updating the website) would be a wonderful step forward.

I'm not aware of Sourceforge causing FOG to have malware.  First, the FOG Client would be the only thing I could think of as a potential hotbed for obtaining malware, of which we are strictly (now) on Github for anyway.
The installer of FOG is purely linux based, and I've never seen a download of FOG that has this embedded bit of software.  This might be because of us tarring the file for distribution, or it's not as simple for almost purely linux systems.  Maybe it's because it's been active for quite some time?
Our next release will be released to Github and sourceforge.  I will make some work to upload released FOG bits up to github as well as we do like to use Github now.  Our release after this current one (1.3.0 we're developing right now) will be completely on Github, and moved away from sourceforge altogether.


[WIP] Update presenters to return nested topic parents.

This is required as part of migrating DetailedGuides. Once we have dependency resolution, we will be able to implement this more elegantly.
/cc @binaryberry.

As discussed with offline at a few occasions, I thought it would've been preferrable to temporarily solve this with an extra call in client. We've done this in Whitehall in upcoming PR https://github.com/alphagov/whitehall/pull/2557. Our code: specialist_tag_finder.rb#L23-L29
However I may not have been part of all your discussions, so I'll roll with this.
But I'm not a 100% sure that the implementation is correct. This seems to take the first topic, and then recursively look up the parent for that topic. If you're going to use this is a breadcrumb, the idea is that we  recursively expand links.parent (which is of the topic type incidentally, but that's not important here).
Or am I not understanding the use case? Perhaps the PR description could provide some why's & example output.

That's fine for Whitehall Frontend, but for new style Frontend apps we want them to only need to make a single call to content store to get everything they need to render the page.
This emulates the eventual behaviour of dependency resolution, it's essentially a content store-side shim in preparation for the dependency resolution work. In theory, when that's ready we'll be able to remove this shim and the frontend will continue to work in exactly the same way.
I'll let @tvararu explain the implementation more, but my rough understanding is that parent is used for breadcrumbs and the topics are used for the "Part of:" metadata. There is an open question around the breadcrumbs though - the parent of this document is set in Whitehall admin as "PAYE", however the parent of PAYE, "Business tax", is actually displayed as the breadcrumb. Do you happen to know why this is, @tijmenb? If not, we can try and investigate.

This implementation is dodgy, yes. I'm going to go back to Whitehall to re-trace how exactly it's rendering the topic parent when the model itself only has associations for the current topics. I've done this before but the process was non-trivial and I decided to back off.

On 15 Apr 2016, at 08:04, Paul Bowsher<EMAIL_ADDRESS>wrote:
That's fine for Whitehall Frontend, but for new style Frontend apps we want them to only need to make a single call to content store to get everything they need to render the page.
This emulates the eventual behaviour of dependency resolution, it's essentially a content store-side shim in preparation for the dependency resolution work. In theory, when that's ready we'll be able to remove this shim and the frontend will continue to work in exactly the same way.
I'll let @tvararu explain the implementation more, but my rough understanding is that parent is used for breadcrumbs and the topics are used for the "Part of:" metadata. There is an open question around the breadcrumbs though - the parent of this document is set in Whitehall admin as "PAYE", however the parent of PAYE, "Business tax", is actually displayed as the breadcrumb. Do you happen to know why this is, @tijmenb? If not, we can try and investigate.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

I'm not opposed to shims. The thinking here was that we may not be completely sure about how to represent these things in the content-store. Changing an API is not trivial, so we run the risk of committing to a less-than-ideal structure here. We chose to add the hack in Whitehall so that whenever dependency resolution comes around we'd have to change at most one thing.
But let's leave that approach for now and focus on making the shim nice. Also because I didn't account for the "Part of:" content.
I'm off to a meeting now, but I'll try to figure out today 1) which data we currently show on these pages, 2) if it can be simplified 3) how we should store this in the links and 4) how we would want it back from the content store.

Thanks :). For record: that structure was suggested by @tuzz, based on the current plan for Dependency Resolution.

Do we have a record of that somewhere? https://github.com/alphagov/govuk-content-schemas/pull/279#discussion_r58688765 seems to suggest a different data structure.

The base key is different (expanded_links.parent), which is likely incorrect, but the rest is similar, no? If not, we should bring it in-line.
The tests on this branch expect:
topics: [
  content_id: topic_paye_details.content_id,
  title: topic_paye_details.title,
  base_path: topic_paye_details.base_path,
  parent: [
    {
      content_id: topic_paye.content_id,
      title: topic_paye.title,
      base_path: topic_paye.base_path,
      parent: [
        {
          content_id: topic_business_tax.content_id,
          title: topic_business_tax.title,
          base_path: topic_business_tax.base_path
        }
      ]
    }
  ]
]

There is an open question around the breadcrumbs though - the parent of this document is set in Whitehall admin as "PAYE", however the parent of PAYE, "Business tax", is actually displayed as the breadcrumb. Do you happen to know why this is, @tijmenb? If not, we can try and investigate.

In this comment I will attempt to answer that question from a technical standpoint to the best of my understanding. The particular detailed guide I am tracing through the stack is https://www.gov.uk/guidance/salary-sacrifice-and-the-effects-on-paye.
This displays the entire block in the frontend, where the "Business tax" link is present:
<!-- views/detailed_guides/show -->
<header class="block headings-block">
  <div class="inner-block floated-children">
    <%= render  partial: 'header',
                locals: {
                  header_title: t_display_type(@document),
                  document: @document,
                  footer_meta: true,
                  policies: @related_policies,
                } %>
  </div>
</header>

Going deeper:
<!-- views/documents/_header -->
<%
  header_title ||= ""
  policies ||= nil
  specialist_tag_finder = SpecialistTagFinder.new(@document)
%>
<%= render partial: 'shared/heading',
          locals: { type: add_sector_name(header_title, specialist_tag_finder.primary_sector_tag),
                    heading: document.title,
                    extra: true } %>

I'll skip some detours here: the type local being passed into shared/heading is the final HTML that gets presented. add_sector_name simply calls specialist_tag_finder.primary_sector_tag.title to get i.e. the Business tax string and appends  - guidance (header_title) to it.
So, what we need to know is what is specialist_tag_finder.primary_sector_tag:
# lib/specialist_tag_finder.rb
class SpecialistTagFinder
  def initialize(document)
    @document = document
  end

  def primary_sector_tag
    primary_subsector_tag.parent if primary_subsector_tag
  end

  def primary_subsector_tag
    if primary_tag_slug = @document.primary_specialist_sector_tag
      specialist_sector_tags.find {|t| t.slug == primary_tag_slug }
    end
  end

private

  def artefact
    @artefact ||= Whitehall.content_api.artefact(RegisterableEdition.new(@document).slug)
  end

  def specialist_sector_tags
    return [] if artefact.nil?
    artefact.tags.select {|t| t.details['type'] == 'specialist_sector' }
  end
end

So, you call primary_sector_tag which calls primary_subsector_tag which will filter specialist_sector_tags based on the @document.primary_specialist_sector_tag. Which is:
# models/edition/specialist_sectors.rb
def primary_specialist_sector_tag
  primary_specialist_sectors.first.try(:tag)
end

Note the #first. Which in the case of our Salary Sacrifice example is:
> dg.primary_specialist_sectors.first
=> #<SpecialistSector id: 47465, edition_id: 595175, tag: "business-tax/paye", created_at: "2016-02-18 09:02:19", updated_at: "2016-02-18 09:02:19", primary: true>
> dg.primary_specialist_sectors.first.tag
=> "business-tax/paye"

Going back to SpecialistTagFinder, we're filtering specialist_sector_tags based on if their slug matches the above slug. What are specialist_sector_tags again?
# Repeat from lib/specialist_tag_finder.rb
def artefact
  @artefact ||= Whitehall.content_api.artefact(RegisterableEdition.new(@document).slug)
end

def specialist_sector_tags
  return [] if artefact.nil?
  artefact.tags.select {|t| t.details['type'] == 'specialist_sector' }
end

So, we're querying the content store for a ContentItem that matches the current document's slug, which is assigned as our @artefact.
Well, that's what I hope it does anyway, because I can't get it to work in the Rails console possibly due to localisation magic:
> re = RegisterableEdition.new(d)
=> #<RegisterableEdition:0x007fd277d7b260 @edition=#<Document id: 235854, created_at: "2014-05-15 14:18:48", updated_at: "2016-02-18 10:37:00", slug: "salary-sacrifice-and-the-effects-on-paye", document_type: "DetailedGuide", content_id: "5f58d036-7631-11e4-a3cb-005056011aef">>
> re.slug
NoMethodError: undefined method `non_english_edition?' for #<Document:0x007fd2780ffe90>

Within the artefact.tags, we filter out to only leave the ones that have a type that matches specialist_sector.
These tags will be again filtered, as aforementioned, based on if their slug matches business-tax/paye.
To be continued, will edit comment once I get past the non_english_edition? block.

Useful sleuthing so far, thanks!

I can't get past the localisation block, but I think the picture is clear now. The first primary_specialist_sector (also known as a parent in the new world) is what informs the choice of breadcrumb link and text.
Ergo, I'm going to update this to no longer decorate the first topic, but the parent.

This PR has been updated to now return the nested parent hierarchy.

@boffbowsh I've updated it to now use the suggested self.class.new invocation, which is a lot cleaner. 👍
However, the structure has now slightly changed.
Before (extra keys omitted for brevity)
parent: [
  content_id: topic_paye_details.content_id,
  parent: [
    {
      content_id: topic_paye.content_id,
      parent: [
        {
          content_id: topic_business_tax.content_id,
        }
      ]
    }
  ]
]

After
links: {
  parent: [
    content_id: topic_paye_details.content_id,
    links: {
      parent: [
        {
          content_id: topic_paye.content_id,
          links: {
            parent: [
              {
                content_id: topic_business_tax.content_id,
                links: {}
              }
            ]
          }
        }
      ]
    }
  ]
}

Which is probably better. We'll have to update the schema.

Still WIP?

Actually, nope.

I think it's worth deploying this on integration first and checking we don't have a performance regression.

Agreed. 👍

Deployed to integration. Seems to work, but too well / not well at all, at the same time.
Given an object of this shape:
"content_id": "1"
"links": {
  "parent": [{
    "content_id": "2",
    "links": {
      "parent": [
        "3"
      ]
    }
  }]
},
"topics: [{
  "content_id": "4"
  "links": {
    "parent": [
      "5"
    ]
  }
}]

It will expand all parents, not just the one we care about, which is at the root level link. Ergo:
"content_id": "1"
"links": {
  "parent": [{
    "content_id": "2",
    "links": {
      "parent": [{
        "content_id": "3", // This is good.
        "links": {}
      }]
    }
  }]
},
"topics: [{
  "content_id": "4",
  "links": {
    "parent": [{
      "content_id": "5", // This is not good.
      "links": {}
    }]
  }
}]

Which in retrospect makes perfect sense given how the code is written and what it does, but not exactly what we want.
Additionally, it appears that the content store lookups are botching up in some way that needs investigating.
Before this change: http://sprunge.us/QBgY?json
After this change: http://sprunge.us/BLDH?json
It's quite peculiar. Before, we have this (shortened, IDs replaced with shorter labels):
"parent": [
  {
    "content_id": "A",
    "title": "PAYE",
    "links": {
      "parent": [
        "B"
      ]
    }
  }
],
"topics": [
  {
    "content_id": "A",
    "title": "PAYE",
    "links": {
      "parent": [
        "B"
      ]
    }
  }
],
"available_translations": [
  {
    "content_id": "C",
    "title": "Salary sacrifice",
    "links": {
      "parent": [
        "A"
      ]
    }
  }
]
},

So, we have a parent and a topic of A, which both point to B as their parent. Meanwhile, available translation C points to A as its parent.
Here's what actually happens:
"parent": [
  {
    "content_id": "A",
    "title": "PAYE",
    "links": {
      "parent": [
        {
          "content_id": null, // What?!
          ...
          "schema_name": "gone",
          "document_type": "gone",
          "links": {}
        }
      ]
    }
  }
],
"topics": [
  {
    "content_id": "A",
    "title": "PAYE",
    "links": {
      "parent": [
        {
          "content_id": null, // Same one, here it is again.
          ...
          "schema_name": "gone",
          "document_type": "gone",
          "links": {}
        }
      ]
    }
  }
],
"available_translations": [
  {
    "content_id": "C",
    "title": "Salary sacrifice",
    "links": {
      "parent": [
        {
          "content_id": "A", // This one is good.
          "title": "PAYE",
          "links": {
            "parent": [
              {
                "content_id": "B", // Why is this one correct while the above link to garbage?!
                "title": "Business tax",
                "links": {
                  "children": ["etc"]
                }
              }
            ]
          }
        }
      ]
    }
  }
]

So yes. Need to:

Stop it from nesting parents of everything, and only nest parent parents.
Figure out why it's linking to garbage data.

Perhaps that the actual feature in publishing-api will be finished soon, and this temporary solution won't be necessary anymore. Have you checked with @dougdroper / @danielroseman?

I haven't, this has been sitting around for a while, but is nonetheless necessary for the detailed guidance migration (which has had a myriad of other loose ends to tie).
Doug / Daniel?

Had a chat with @dougdroper that explained the new expanded_links feature that should cover this functionality. All that is necessary is a republish of the existing detailed guides, like https://github.com/alphagov/whitehall/pull/2576.


build: Update Kotlin to 1.9.21

Overview
Update Kotlin to 1.9.21
Fixes #
Checklist
My PR contains...

[x] No code changes (changes to documentation, CI, metadata, etc.)
[ ] Bug fixes (non-breaking change which fixes an issue)
[ ] Improvements (misc. changes to existing features)
[ ] Features (non-breaking change which adds functionality)

My changes...

[ ] are breaking changes
[x] are not breaking changes
[ ] If yes to above: I have updated the documentation accordingly

Documentation

[ ] My changes do not require a change to the project documentation
[x] My changes require a change to the project documentation
[x] If yes to above: I have updated the documentation accordingly

Tests

[x] My changes can not or do not need to be tested
[ ] My changes can and should be tested by unit and/or integration tests
[ ] If yes to above: I have added tests to cover my changes
[ ] If yes to above: I have taken care to cover edge cases in my tests

Code Coverage

Total Project Coverage
NaN%
:x:

:tada: This PR is included in version 1.2.6-snapshot.1 :tada:
The release is available on:

v1.2.6-snapshot.1
GitHub release

Your semantic-release bot :package::rocket:

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

v1.2.6
GitHub release

Your semantic-release bot :package::rocket:


Doesn't work with Multi-tenant Azure accounts

Hey, assumed I'd hit some issue like this due to trying to connect this to my business account but this addon doesn't like multi-tenant accounts, which I don't think is too hard of a fix.
Error details: error invalid_request error_description: AADSTS50194: Application 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'(StreamDeck Integration) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.

The code does have "common" as the hardcoded tenant ID. Any change of a new version where that is configurable?
Good work regardless, bet this works well for those who can use it! :)

Hm, that should work. I tested it with a personal and organizational account.
Did you follow this guide? https://github.com/marcells/streamdeck-microsoft365/blob/main/docs/CreateAzureApp.md


Cluster function is not working

Hi,
I download prebuilt image and run with default setting first.
It's ok, broker can accept publish/subscribe command.
But I change the node name from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>Then the sever can not start correctly.
The log with command "./emqttd console"
=INFO REPORT==== 27-Jul-2015::11:49:50 ===
alarm_handler: {set,{{disk_almost_full,"/"},[]}}
=INFO REPORT==== 27-Jul-2015::11:49:50 ===
alarm_handler: {set,{system_memory_high_watermark,[]}}
starting emqttd on node<EMAIL_ADDRESS>emqttd trace is starting...[done]
emqttd pooler is starting...[done]
emqttd client manager is starting...[done]
emqttd session manager is starting...[done]
emqttd session supervisor is starting...[done]
emqttd pubsub is starting...[done]
emqttd stats is starting...Eshell V6.4  (abort with ^G)
(emqttd@<IP_ADDRESS>)1>
=INFO REPORT==== 27-Jul-2015::11:49:50 ===
application: emqttd
exited: {bad_return,
{{emqttd_app,start,[normal,[]]},
{'EXIT',
{{badmatch,
{error,
{{{badmatch,{error,{no_exists,topic}}},
[{emqttd_stats,'-init/1-lc$^1/1-1-',1,
[{file,"src/emqttd_stats.erl"},
{line,144}]},
{emqttd_stats,init,1,
[{file,"src/emqttd_stats.erl"},
{line,144}]},
{gen_server,init_it,6,
[{file,"gen_server.erl"},{line,306}]},
{proc_lib,init_p_do_apply,3,
[{file,"proc_lib.erl"},{line,237}]}]},
{child,undefined,emqttd_stats,
{emqttd_stats,start_link,[]},
permanent,10000,worker,
[emqttd_stats]}}}},
[{emqttd_app,start_child,2,
[{file,"src/emqttd_app.erl"},{line,105}]},
{emqttd_app,start_server,2,
[{file,"src/emqttd_app.erl"},{line,94}]},
{emqttd_app,'-start_servers/1-lc$^0/1-0-',2,
[{file,"src/emqttd_app.erl"},{line,85}]},
{emqttd_app,'-start_servers/1-lc$^0/1-0-',2,
[{file,"src/emqttd_app.erl"},{line,85}]},
{emqttd_app,start,2,
[{file,"src/emqttd_app.erl"},{line,53}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,272}]}]}}}}
type: permanent
=INFO REPORT==== 27-Jul-2015::11:49:50 ===
alarm_handler: {clear,system_memory_high_watermark}
=INFO REPORT==== 27-Jul-2015::11:49:50 ===
alarm_handler: {clear,{disk_almost_full,"/"}}
{"Kernel pid terminated",application_controller,"{application_start_failure,emqttd,{bad_return,{{emqttd_app,start,[normal,[]]},{'EXIT',{{badmatch,{error,{{{badmatch,{error,{no_exists,topic}}},[{emqttd_stats,'-init/1-lc$^1/1-1-',1,[{file,"src/emqttd_stats.erl"},{line,144}]},{emqttd_stats,init,1,[{file,"src/emqttd_stats.erl"},{line,144}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,306}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]},{child,undefined,emqttd_stats,{emqttd_stats,start_link,[]},permanent,10000,worker,[emqttd_stats]}}}},[{emqttd_app,start_child,2,[{file,"src/emqttd_app.erl"},{line,105}]},{emqttd_app,start_server,2,[{file,"src/emqttd_app.erl"},{line,94}]},{emqttd_app,'-start_servers/1-lc$^0/1-0-',2,[{file,"src/emqttd_app.erl"},{line,85}]},{emqttd_app,'-start_servers/1-lc$^0/1-0-',2,[{file,"src/emqttd_app.erl"},{line,85}]},{emqttd_app,start,2,[{file,"src/emqttd_app.erl"},{line,53}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,272}]}]}}}}}"}
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,emqttd,{bad_return,{{emqttd_app,start,[normal,[]]},{'EXIT',{{badmatch,{error,{{{badmatch,{error,{no_exists,topic}}},[{emqtt
chlee:bin maclee$

Please remove 'data/mnesia' if you change node node.

Thanks a lot, it's working.


Docker image shouldn't contain the credentials, those should be passed while creating the container

@imaskm Thank you for the issue.
I will definitely check it out very soon.

I second this.

already created MR to resolve this and some other issues:
https://github.com/itsksaurabh/kubeact/pull/14


Potential update to rendering multiple elements

what?

... you should wrap these elements inside a fragment as you would in JavaScript or JSX.

why?
It's worth asking, why's this important?
For example, not doing this in JSX throws an error. However, it works just fine in the latest versions of Astro.
See https://stackblitz.com/edit/github-o8fjnb?file=src/pages/index.astro
If we're telling people they should do this, it's worth mentioning "why" as this seems to work just fine i.e., without error as in the JSX comparison.
See docs.

Hi @ohansemmanuel - I can tell you that when these docs were written, wrapping the elements was required. It would not work otherwise.
I'm checking in with the dev team to see whether something has changed and we can update this advice!  :raised_hands:

@sarah11918 I just verified that there's no need to have a fragment to perform this action. I can handle the update if you want me to.

Thanks @sarah11918


Cleaned up tls1_prf and added comments.

Added a description of the PRF algorithm from RFC 2246 and RFC 5246.
Added comments and made minor code changes to make it easy to associate steps in the algorithm description with lines of code in the implementation.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

maybe add a "conforms to" section into the EVP_KDF_TLS1_PRF.pod file

Maybe a reference to SP800-135 r1 should also be in there..

I'm surprised to see this added in the "3.0 New Core + FIPS" project...  that's not really what this is.

Richard - this goes inside the FIPS boundary, see SP800-135 r1

...  I thought this was a KDF backend that was being documented...  so while there is a relationship, this doesn't look like New Core or FIPS module work per se.
Ah well, I'll leave it to someone else to make a final call.

Documenting the steps just makes it easier to see that is following the standards.

I was indecisive about adding the FIPS project tag -- happy for it to be removed.


Add new rebus

Associated Issue: #14
Summary of Changes

Added new rebus on /src/js/rebuses.js

Pull Request Test Coverage Report for Build 54

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.231%

Totals

Change from base Build 53:
0.0%

Covered Lines:
87

Relevant Lines:
99

💛  - Coveralls

Awesome, thank you!


Sublime as Insert Mode -- Lost!

When I first installed neovim/ActualVim, Sublime would take over when in Insert Mode (by default). This scenario is in fact ideal to me, so I can benefit from my other Sublime extensions quickly. But some time while I was toying around with Vim by upgrading my .vimrc file and adding packages, and then applying them to nvim by symlinking, the scenario above that I thought was default (and amazing) disappeared! I've tried reading other posts concerning related issues, but can't yet figure out how to get back to that ideal state :(.

Sublime would take over when in Insert Mode

This is indeed ideal, but was never quite the case. You'll need to describe more what you could do before, and what happens incorrectly when you do it now for me to diagnose.

Thanks for the quick reply -- I'm sure you're right, but I'm completely flummoxed about how I had the functionality available to me for days last week. I even took note of what I did and sent it to two friends in case they were interested, but I just followed those same steps on a spare mac, and indeed I do not gain this functionality. This leads me to believe my "losing" it had nothing to do with any configuring I was doing yesterday. I guess I must've been toggling it somehow, but I'm surprised I wouldn't notice something like that.

On Oct 10, 2017, at 1:14 AM, Ryan Hileman<EMAIL_ADDRESS>wrote:
Sublime would take over when in Insert Mode
This is indeed ideal, but was never quite the case. You'll need to describe more what you could do before, and what happens incorrectly when you do it now for me to diagnose.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lunixbochs/ActualVim/issues/125#issuecomment-335362943, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgTy-Zn-Yhozt2KS4wr80OICDQOoriks5sqv0dgaJpZM4PzP1_.

You can bind a key to toggle by adding a user keymap like this:
    { "keys": ["ctrl+s"], "context": [{"key": "setting.actual_mode", "operand": true}],  "command": "actual_disable"},
    { "keys": ["ctrl+s"], "context": [{"key": "setting.actual_mode", "operand": false}], "command": "actual_enable"},

That does indeed work (and good to know, thanks) but definitely was not required for me before. The only other thing I can think of is that I was instead using the so-called Vintage mode, but I don't recall ever installing that. I guess we can close this and I'll let you know if I ever reproduce the scenario I had before.

On Oct 10, 2017, at 2:15 AM, Ryan Hileman<EMAIL_ADDRESS>wrote:
You can bind a key to toggle by adding a user keymap like this:
{ "keys": ["ctrl+s"], "context": [{"key": "setting.actual_mode", "operand": true}],  "command": "actual_disable"},
{ "keys": ["ctrl+s"], "context": [{"key": "setting.actual_mode", "operand": false}], "command": "actual_enable"},

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lunixbochs/ActualVim/issues/125#issuecomment-335371584, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgT9Tv1qG0rcBfO8g0aBCu-o9LvwjSks5sqwtwgaJpZM4PzP1_.


GPII-2616:  Replace marked with markdown-it...

See GPII-2616 for details.

@sgithens, I have cut a dev release for you to test with your work: 1.1.0-dev.20170927T151006Z.df42535
The main difference as I mentioned in chat is that HTML is disabled by default, there are instructions  on enabling that in the docs.  Happy to pair on it or look at things async if you like.

@amb26, I've addressed your comments and updated all dependencies as well.

Thanks, @amb26.  I cut the release, added release notes, and updated the forward-facing version.


add MCP server badge

This PR adds a badge for the @kazuph/mcp-fetch server listing in Glama MCP server directory.

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected
Confirm that there are no obvious security issues with dependencies of the server
Extract server characteristics such as tools, resources, prompts, and required parameters.

This badge helps your users to quickly asses that the MCP server is safe, server capabilities, and instructions for installing the server.

realized the project is missing a license
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
Would you mind adding one?
We will automatically pick up the change (we scan every repo every 6 hours)


Unknown problem with INNER JOIN in Meteor-Postgres project

From here: https://github.com/meteor-stream/meteor-postgres/wiki/Database-Methods

Please note that client side joins currently has an issue with inner join so we recommend using outer join whenever possible. This is a limitation of alasql, a package we are relying on.

After analysis of minisql.js (mini ORM used for the project) I found unsupported command
    DROP TABLE IF EXISTS one CASCADE

The implementation of this CASCADE story is linked to FOREIGN KEY feature.

We are removing drop table method from miniSQL (client side implementation) because it shouldn't be done on the client, only the server. However, if a table is empty, inner join crashes our app and it doesn't come back up.

It is terrible, but I can not reproduce the bug. What is the size of joined data tables?

@barbbella Version 0.2.0 just came out - so please update and let us know if the problem is still there.

@barbbella any news on this?

@mathiasrw Meteor Postgres is no longer maintained. Meteor had promised native support. I don't know what the status of that is.

We will open new issue for CASCADE operations, but this issue will be closed.


feat(zh_CN/zh_TW): Add and modify Chinese(s/t) translation

Hello! I noticed you made several commits that add new strings to welcome tool. So I translate them to S/T Chinese.
I only add Simplified version for DACHLI-Obersee-Rheintal, and this may need help of Taiwan's contributor.
However, I can guarantee that at least Simplified Chinese (zh_CN) is no problem.

Awesome! Thanks a lot @LaoshuBaby !

To facilitate translation, I've integrated Crowdin ; you can join here https://crwd.in/osm-welcome-tool


Add signal support

This implements the first signals that I thought made sense.
The opened signal fires when the console is opened (passes no arguments).
The closed signal fires when the console is closed (passes no arguments).
The toggled signal fires when the console is either opened or closed (passes no arguments).
The command_added signal fires when a command is added to the console, and passes the name, target, and target_name.
The command_removed signal fires when a command is removed from the console, and passes the removed command name.
The command_executed signal fires when a command is successfully executed and passes a reference to the command.
The command_not_found signal fires when a command fails to execute and passes the attempted command name.
I tested this commit locally with my own project but will need to come in and add more formal testing once I figure out how to use the testing suite in this project.

I implemented the requested changes to remove opened/closed and simply add a parameter on toggled to tell which occurred.

Sorry for my bad english, I didn't meant that you should remove opened/closed signals, tho I guess this matters little since it's works fine with only one signal covering both cases)
If you still would want to preserve opened/closed signals now it is the time to add them back, otherwise please just let me know and I'll merge your pr.
Great work, thank you :)

I'm fine with the way it currently works! Feel free to merge.

I just noticed you forgot to remove signal emitters for opened and closed, could you please remove them?

Odd, that must not have pushed. Of course!
On Fri, Dec 4, 2020 at 06:07 Sergei ZH<EMAIL_ADDRESS>wrote:

I just noticed you forgot to remove signal emitters for opened and closed,
could you please remove them?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/quentincaffeino/godot-console/pull/38#issuecomment-738774245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG33QM7OUU4KSVC54RT5D2DSTDNIHANCNFSM4UL2I5FQ
.

--
Josh DeGraw
(801) 860-6298
<EMAIL_ADDRESS>

@all-contributors please add @joshdegraw for code


Fix column writer nullability check

I found problem (?) with column generation regarding to nullability + converters.
The generated data class is not nullable, but other function treat type as nullable. I made a possible fix. Am I right?

Huh, looks like this causes us to sometimes generate a duplicate nullability suffix (PureDefault copyWith({MyCustomObject?? txt}) in the failing build step).

I found the problem. Fixed!

The issue came back. The field is nullable, but the converter isn't.


Adapt reference guide to new TOC experience

Bump the local-server version to 1.2.3.BS (version pulled in the docs for includes)
Add new TOC experience related infrastructure
Reorder sections to adapt to general core reference guide for consistency
Fix appendices section

Resolves spring-cloud/spring-cloud-dataflow-server-cloudfoundry#342

LGTM except the server configuration section has no CF specific content - see #344

merged via commit 05ce2724d6b67b17e1a97bdf1a3d97b06a133510


"Urgent"-Issue in null cell- null cell value getting overlapped by next cell value

I used this table transform code but there is an issue like cell value are overlapped with next cell value can please give me a solution for that and which is urgent

After detection the values are getting overlapped
(Date field value getting overlapped by Description )

could you please give me a solution

I fixed this issue, like identified the null cell and replace  the value with "Null"

I fixed this issue, like identified the null cell and replace the value with "Null"

what ocr used for this ? In easy ocr extraction of words get worst https://github.com/NielsRogge/Transformers-Tutorials/issues/372


Creating data bags with knife complains I don't have a client.pem key?

I thought we didn't need a client.pem key since we don't have a server? Any suggestions on how I could get around this since I need data bags for Opscode's users cookbook, thanks in advance.

I use data bags all the time, only, there is no need for knife. You can just create data bags by creating a json file and saving it in LittleChef's data bags dir
For users for example:
data_bags/users/user1.json
data_bags/users/user2.json
The id of the databags would be user1 and user2.
Doesn't that work for you?

@tobami Actually, the message is on the node itself during a fix. Have you experienced this?

I'm using the Opscode users cookbook, and I get this error from using the users_manage provider
FATAL: Chef::Exceptions::PrivateKeyMissing: users_manage[admin] (users::default line 23) had an error: Chef::Exceptions::PrivateKeyMissing: I cannot read /etc/chef/client.pem, which you told me to use to sign requests!

Here is my recipe
# Searches data bag "users" for groups attribute "admin".
# Places returned users in Unix group "admin" with GID 2300.
users_manage "admin" do
  group_id 6969
  action [ :remove, :create ]
end

Ok. The problem is that the new version of the cookbook, dating from February 13th, breaks something.
The previous version (from 2011) should work. Can you confirm it?:
https://github.com/opscode/cookbooks/commits/master/users/recipes/sysadmins.rb
I'll investigate further how the change causes this problem. They basically refactored all the code in recipes/sysadmins.rb into a provider

If you put the new recipes in site-cookbooks/users/metadata.json they should of course be found. I haven't encountered any bugs in the metadata handling.
That said, if you use the latest 2011 version, there won't be any metadata.json, just a metadata.rb.
With LittleChef 1.1 it is better to also use metadata.rb, and if you have knife locally configured, the metadata.json needed by LittleChef will be automatically generated.
What is your case? Was there a .rb and .json in cookbooks, but just a .json in site-cookbooks?
In any case I don't see how the recipes can't be found. Maybe it would help if you posted the metadata.json...

Srory I think I figured it out...
cookbooks
    rbenv
        recipes
            default.rb
        metadata.rb
        metadata.json
site-cookbooks
    rbenv
        recipes
            bashrc.rb
    metadata.rb

So cookbooks/rbenv/metadata.rb contains
recipe "rbenv", "Default recipe"

while `site-books/rbenv/recipes/bashrc.rb" contains
recipe "rbenv", "Default recipe"
recipe "rbenv[bashrc]", "Replace bashrc"

I am using the latest 2011 version, and only after creating site-cookbooks/rbenv/metadata.json manually did it work (I assumed it would automatically convert it from .rb)

It does create metadata.json automatically. The problem is that you have an error.
It should be rbenv::bashrc, not rbenv[bashrc]

Hmm ahh oops, actually I manually wrote that and believe I typo'd it because I am looking at my actual metadata.rb and I have it right. I will have another chance to test it again today so I'll let you know, sorry about that gahhh


LBP

Anything special to make it work with an LBP cascade? i see the boundry box doesnt update position quickly like HAAR

No, it should be simple.
At the time the code was written LBP was still fairly new and there was no C++ implementation available (or at least I didn't find one)
I tried implementing my own LBP classifier but gave up on it as I focused my attention on other projects.

No, it should be simple.
At the time the code was written LBP was still fairly new and there was no C++ implementation available (or at least I didn't find one)
I tried implementing my own LBP classifier but gave up on it as I focused my attention on other projects.

Yea, i have a classifier LBP i created myself, it works great but i cannot seem to get the tuning correct.
instead of 20X20 is uses
BOOST
LBP
50
40

seems to downscale ok but when face moves closer it seems to rely on tempalte match to make box bigger,  any tunning thoughts to this software ?  thanks!

Yea, i have a classifier LBP i created myself, it works great but i cannot seem to get the tuning correct.
instead of 20X20 is uses
BOOST
LBP
50
40

seems to downscale ok but when face moves closer it seems to rely on tempalte match to make box bigger,  any tunning thoughts to this software ?  thanks!

Height 50  width 40

Height 50  width 40

Sorry man, cant really help you.
I haven't used this in a long time. I don't really remember that well. You can try poking around the code a bit and tweak some stuff, see if it works.

Sorry man, cant really help you.
I haven't used this in a long time. I don't really remember that well. You can try poking around the code a bit and tweak some stuff, see if it works.


Openseadragon module: replace version with configurable variable

The OpenSeadragon (OSD) module code has the version of the OSD to use hard-coded in a few places. It's tricky to make it a configurable variable, but we should do that at some point.
Example: https://github.com/Islandora/openseadragon/blob/8.x-1.x/openseadragon.module#L150

Forgive my ignorance, I've been out of Islandora 8 for a bit. It appears that there is the OSD config already loaded in the method you linked to. Could you add a field there and pull it when you make that array? Or is the tricky bit the validation of the version?


Pure quadrature wrapper

Fix wrapper to CVOdeQuadInit & CVQuadRhsFn to use proper cfunction signature.

Coverage decreased (-0.02%) to 24.118% when pulling 3bb4cc961258ab1f0a171bbb3c5e381b5f60feac on AleMorales:master into 8d8f4bdc12b3873a4c7b1020da3051a0c368f145 on JuliaDiffEq:master.

Didn't see this one, sorry. Thanks!


Makefile: select good sed on mac

gsed is not a osx built in, but typically a brew add on instead..  I'm not sure it's safe to assume everyone has it...  maybe better to find the equivalent sed flags with bsd sed to get the same output -- and parameterize $SED_FLAGS ?

does go - net - ParseIP do this more cleanly?
https://golang.org/pkg/net/#ParseIP

sed: this would work for those who have GNU sed. So applying this would make it better for them at least. Agreed that we could make it even more portable.

Prints IPv4: I should have put it on another branch as I didn't want it to be part of this pull request sorry about that. Will rebase/push.


extend metadata

I should add the AttributeConsumingService element to my metadata with the list of RequestedAttribute elements inside. I saw that there are no options available to set it while in spring-security-saml it is possible. Can you tell me if it is possible to set it up in any way?

can you point me where in spring-security-saml that is configurable?


More Codes

Need to add other programming languages versions of our stuff.

All subjects now have at least two source codes.

All subjects now have at least two source codes.


Incorrect tensor type in scitail.nn.util.masked_mean

System information

Ubuntu 16.04
Anaconda 4.5.11
PyTorch 0.4.1
CUDA 9.0
NVIDIA Driver 396.54

Producing the error
pytest -v produces the following stacktrace:
    def masked_mean(tensor, dim, mask):
        """
        ``Performs a mean on just the non-masked portions of the ``tensor`` in the
        ``dim`` dimension of the tensor.
        """
        if mask is None:
            return torch.mean(tensor, dim)
        if tensor.dim() != mask.dim():
            raise ConfigurationError("tensor.dim() (%d) != mask.dim() (%d)" % (tensor.dim(), mask.dim()))
        masked_tensor = replace_masked_values(tensor, mask, 0.0)
        # total value
        total_tensor = torch.sum(masked_tensor, dim)
        # count
        count_tensor = torch.sum((mask != 0), dim)
        # set zero count to 1 to avoid nans
        #zero_count_mask = (count_tensor == 0).long()
        zero_count_mask = (count_tensor == 0)
>       count_plus_zeros = (count_tensor + zero_count_mask).float()
E       RuntimeError: Expected object of type torch.LongTensor but found type torch.ByteTensor for argument #3 'other'

Possible fix
Changing https://github.com/allenai/scitail/blob/2e57f46a4620d50e85323c4a642114426db67393/scitail/nn/util.py#L24 to
zero_count_mask = (count_tensor == 0).long()

seems to fix the error.

Accidentally duplicated because of GitHub problems.


crashing after creating a theme file then opening the custom theme dropdown

Description
after creating a theme.xaml file in the themes folder and opening the custom theme drop down it just crashes and doesnt show anything in logs
Steps To Reproduce
1.create a theme file in the theme folder
2.restart files
3.open custom thmems drop down
Steps to fix
didnt find a fix
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22621.674
Windows Version
windows 11 22h2
Relevant Assets/Logs
debug.log

Could you upload the theme file

il send it as a text file since git hub doesnt support xaml. i just modified the nord theme.
nordmodified.txt

SolidBackgroundFillColorQuarternary has an invalid color, removing the extra 0 should solve the issue.

For themes v2 it should show the theme but as invalid rather than crashing.


fix(module:avatar): implicit type conversion error

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

直接把全部的 strictTemplate 打开，然后统一提个pr？


Compressed API Response! (deflate, gzip)

Hey there,
this API Integration should use Content Compression for the API Response (https://blog.twitter.com/2012/announcing-gzip-compression-streaming-apis)
Reduced Page-Generation-Time (with deactivated Memcache Result Cache) from 7 Seconds to 1,5 Seconds ... ;-)
It's simple to hack into ... just add this Line to the CURL Options (Line 199):
CURLOPT_ENCODING => '',
Whole Options:
$options = array(
CURLOPT_HTTPHEADER => $header,
CURLOPT_HEADER => false,
CURLOPT_URL => $this->url,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 10,
CURLOPT_ENCODING => '',
);
Have fun
Andreas Schnederle-Wagner

This would work if #94 was updated, then additional cURL options could be added as the user requires.

I'm going to close this for the moment - if anyone would like to pick this up in the future please feel free to comment.


add starcoder2

add starcoder2
Description
add starcoder2
Motivation and Context
add starcoder2
How has this been tested?
i ran a build with it, and it worked
Screenshots (if appropriate)
Types of changes
add starcoder2
Social Handles (Optional)

Great work!
Kindly add:
model_type: AutoModelForCausalLM
tokenizer_type: AutoTokenizer
trust_remote_code: true


Cannot compose circuits with different numbers of measurements

Information

Qiskit Terra version: 0.17.4
Python version:
Operating system:

What is the current behavior?
Compose fails when combining circuits with no measurements together with those that do, e.g.
ansatz = TwoLocal(2, rotation_blocks='ry',
                  entanglement_blocks='cx')

qc = QuantumCircuit(2)
qc.measure_all()

ansatz.compose(qc)

gives:
CircuitError: "Trying to compose with another QuantumCircuit which has more 'in' edges."
while + works, but is deprecated in favor of compose.
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

Ok, it makes sense although a bit confusing.  Namely, I cannot add a measurement circuit onto an ansatz, but rather I must append the needed measurement rotation gates to the ansatz itself before adding the measurements to it.  It would be nice if this could work if self has no cregs given that there is no ambiguity in that case and it is a common situation to be in.

I agree with Paul. Adding a measurement circuit onto the end of a non-measurement circuit is something I do quite often.
For my own purposes, I just construct the non-measurement circuit with a classical register so that it works. But when writing educational materials, it wouldn't be great to say "here we put in a classical register just so Qiskit doesn't complain".


Add test engine filter to documentation

As suggested by @eriwen in #4523 , this PR adds a section to tell users how to use includeEngine and excludeEngine for JUnit 5.

Might not in the scope of this PR, but do you want to add a mention of filtering tags? Either in this PR or in a follow-on?

@JLLeitschuh Well, I believe includeTags/excludeTags are already in the documentation - https://docs.gradle.org/4.6-rc-2/userguide/java_plugin.html#test_grouping Thanks for your reminding.

Looks good @blindpirate. Thank you


Fall back to non fips endpoint per availability

Description of changes:
apply same fix like https://github.com/awslabs/amazon-eks-ami/pull/1524 as FIPS endpoint only exists in a handful of regions: https://aws.amazon.com/compliance/fips/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/ci
+workflow:os_distros al2023
+workflow:k8s_versions 1.29


Supply OrderN and CofactorH to constructor of FpCurve if provided

FpCurve has a constructor where the order N and cofactor H can be supplied. This pull request uses this constructor when the parameters are supplied in the Asn1Sequence (count == 4).
For the F2mCurve it is still a TODO (that was there already), but my knowledge of crypto (and my time) is currently not sufficient to implement that as well.
I made this because I needed it (redefined the class in my own project) and I thought to share it and improve BC. I hope this is added in a next release.

We updated this along the way somewhere already; processing would usually begin from the Org.BouncyCastle.Asn1.X9.X9ECParameters class, which now extracts the order/cofactor if available.


Remove key-to-action coupling.

Extracted all references to "keys" for features, instead calling the keybindings.ts to find the appropriate action. This will hopefully allow us not tie specific keys to actions. With this extracted, I think a nice way to clean this up is to create a VimState. Right now we are using the VimStyle, but just using an enum and switch.
Further, I cleaned up a couple incorrect keybindings.  All of the previous functionality still works. Granted my f and t keys don't currently work, and I'm unsure if they worked previously. I'm attempting to use atoms vim mode as a good guide. https://github.com/atom/vim-mode/blob/master/lib/vim-state.coffee
I'm looking at creating the state machine next, now that I got the flow of your application. The hope is that by making a central state machine, we can pass some of these actions to their own classes, which can interact with the machine. We'll see if the idea works. :P
I can also take a look at the f and t commands. Don't hesitate to break down some features in the issues, and allow me to take them on :).

Thanks a lot. I will work for using Enum and switch.


Added @RequiresApi(Build.VERSION_CODES.N) for NotificationChannel related code

Added @RequiresApi(Build.VERSION_CODES.N) for NotificationChannel related code for fixing #8

I don't have Android M or N at hand so I tried @RequiresApi(Build.VERSION_CODES.R) and use Android O and Q phones to get the channel info. I also tried calling a test function marked with @RequiresApi(Build.VERSION_CODES.R). Nothing happened, no blocking to access the channel info or calling the test function.

Yes. This PR is not fixing any crash / incompatibility.
It is to make the code more readable, and compiler friendly.

We need someone's help testing on Android M devices.
In my memory, @RequiresApi makes apps crash when calling from lower Android versions. However, I tried @RequiresApi(Build.VERSION_CODES.R) testing on Android O and Q, just nothing happened.
I agree that adding @RequiresApi(Build.VERSION_CODES.N) makes the code more readable. But I want to make sure it won't introduce new crashes on Android M devices mostly hold by senior citizens.

We need someone's help checking on Android M devices. I agree that this will make the code more readable and compiler-friendly. But we want to make sure adding this annotation won't introduce new crashes on Android M devices mostly hold by senior citizens. Currently, there's no related crash report on Play Console.


Namespace problem: azure.keyvault.Certifiate

Typo in the namespace - should be azure.keyvault.Certificate

Related https://github.com/pulumi/pulumi-azure/issues/97 and https://github.com/pulumi/pulumi-azure/issues/210.

Going to close this out as it's linked to #97
We can track all of the work in that issue rather than have multiple issues tracking a similar issue


Add BTCL

BTC Lite is a decentralized cryptocurrency that provides faster transactions speeds than most PoW coins.

你好，提交的信息有误，请查看。

Hello
We just saw your message. Unfortunately none of our team members speak
Chinese. Can you tell us what's incorrect?
On Fri, Sep 7, 2018, 12:40 Weli<EMAIL_ADDRESS>wrote:

你好，提交的信息有误，请查看。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/consenlabs/token-profile/pull/2280#issuecomment-419345141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Agmv7xiNieze3gf5pD8u0jWRCgW3r__Zks5uYhvwgaJpZM4WcgLT
.


engine: Add main-memory KV storage

Look good to me. Next, we need to split every attribute of file. This will change the interface of meta data db.

Can you leave an option to use rocksdb?

What do you mean? Now we can both use rocksdb and mem-kv.

Can you leave an option to use rocksdb?

What do you mean? Now we can both use rocksdb and mem-kv.

Sorry it was my mistake.

I think we need to avoid serialization, can this be done?

I think we need to avoid serialization, can this be done?

I am working on it.


CheckNumberStatus, send_message_to_id seems like no working any more

Can anyone tell how to fixed seems like function not working anymore..

Check if #856 resolves your issue in the wapi.js file


On Windows .gitattribute make clone with CRLF instead LF.

Hello!
Thanks for sharing this nice project.
I just cloned the project (Windows 10), and i got error with Grafana:
> docker logs grafana
standard_init_linux.go:190: exec user process caused "no such file or directory"

I found that the files have been all cloned with CRLF end of lines. This is du to the .gitattribute files I think ("text=auto"). You should remove this file at all i think.
By modifying the grafana/setup.sh file with good linux (LF) EOL, all is ok.

@Yivan I don't actually have a windows machine to test this, though I understand you can also change this client side based on your core.autocrlf setting.
I'll fix up the .gitattribute on another branch tonight, if you don't mind testing and then I can push changes for the .gitattribute back to master.

@Yivan could you try the fix-line-endings branch and report back your results please?
git clone https://github.com/stefanprodan/dockprom.git --branch fix-line-endings

Hello !
Thanks for your return.
I juste tested it (last Docker for Windows version) and there is no more problem with this new branch, great.
So the problem is resolved with this new branch.
I would like to add that on Windows for Docker the rootfs is "/c" and not "/", so i had to change manually in docker-compose.yml file /:/rootfs:ro by /c:/rootfs:ro, after that the up went well and i can login in GUI interfaces.
Maby it could be added in the installation step for Windows users.
Thanks.


2.8.1 fails with "Cannot find module 'react-test-renderer/shallow'"

Downgrading to 2.8.0 fixes it.

Read the README.  :P

This is a breaking change, it shouldn't be shipped in a patch release!

@pscanf If you're on React 15.4, it doesn't change anything. If you're on React 15.5, it's a bugfix, because React 15.5 had a breaking change.

The problem is, if your package.json lists react: "^15.4.0" and enzyme:
"^2.8.0", then yesterday your module was passing tests on travis, and today
it is not, because you have upgraded to the new react and the new enzyme
without actually doing anything.
On Apr 12, 2017 18:45, "Jordan Harband"<EMAIL_ADDRESS>wrote:

@pscanf https://github.com/pscanf If you're on React 15.4, it doesn't
change anything. If you're on React 15.5, it's a bugfix, because React 15.5
had a breaking change.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/enzyme/issues/892#issuecomment-293728312, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABsF--oQO-N2JLvwATBEpPtnbs8qYpM3ks5rvVO-gaJpZM4M78C7
.

Yesterday your module wasn't passing tests because it was upgraded to React 15.5 (due to the semver range), and the new console warnings were failing your tests (assuming you were being a responsible developer and failing your tests on propType warnings).

I do, in fact, fail on proptype warnings, but not on other warnings.  My tests were passing fine.  :P
Maybe we could change this bit to something like:
    if (REACT155) {
      try {
          // eslint-disable-next-line import/no-extraneous-dependencies
          shallowRendererFactory = require('react-test-renderer/shallow').createRenderer;
      } catch(err) {
          shallowRendererFactory = TestUtils.createRenderer;
      }
    } else {
      // eslint-disable-next-line import/no-extraneous-dependencies
      shallowRendererFactory = TestUtils.createRenderer;
    }

?

Then there'd be no way to warn users that they're missing a required dependency for React 15.5+.

Well, there is, because they'll still get the warning that react displays
when the module is required.  Or you could even print your own warning
there to console.error.  And it's technically not a "required" dependency
until react 16.
On Apr 12, 2017 18:54, "Jordan Harband"<EMAIL_ADDRESS>wrote:

Then there'd be no way to warn users that they're missing a required
dependency for React 15.5+.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/enzyme/issues/892#issuecomment-293729958, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABsF-_SzMFjpd_871IwvnICCriAtZhcpks5rvVYjgaJpZM4M78C7
.

Being on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>is ok (this was my situation this morning), while<EMAIL_ADDRESS>+<EMAIL_ADDRESS>fails (my current situation).

and the new console warnings were failing your tests (assuming you were being a responsible developer and failing your tests on propType warnings)

I don't agree, react prints warning specifically not to break things, so enzyme shouldn't break things because anyway react would print warnings.
It might not a big deal I guess (at least for me, since I was updating dependencies anyway), but I would see it as a breaking change nonetheless (which can cause a bit of frustration, sorry for the slightly stormy comment above).

Just adding react-test-renderer dependency fixes ecerything for me.

@tomjal's fix worked for me.

@pscanf warnings do break things; that's the flawed logic that leads to adding new warnings in a semver-minor.

Just adding react-test-renderer dependency fixes everything for me.

As much as I love this fix, it's not scalable across the millions of monthly installs enzyme gets. Fixes should follow semver conventions.

@lxe they did. React 15.5 shipped a change that was subjectively either breaking or minor, which broke some subset of users and libs. enzyme had two choices here: ship a patch that fixes things for those that React 15.5 broke (causing breakage for those users who weren't broken with React 15.5); or ship a semver-major and leave users on the current major line screwed, and forced to adapt to the React breakage (and thus accommodating those users who weren't broken with React 15.5).
semver does not strictly dictate whether "console warnings" are semver-major or not, as such, considering them breaking or non-breaking are both a valid choice.

Without taking sides, I'll say that the semver folks would probably be happy to discuss any ambiguities in a GitHub issue and update their guidelines if necessary.

@openjck the issue is on what constitutes "API" - the document says "For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself." however I claim that the API consists of "anything that's programmatically observable". Additionally, that document does talk about deprecations being in documentation; React adds deprecations in a semver-minor observably in the code, which I believe constitutes an API change.

React 15.5 shipped a change that was subjectively either breaking or minor, which broke some subset of users and libs.. enzyme had two choices here: ship a patch that fixes things for those that React 15.5 broke (causing breakage for those users who weren't broken with React 15.5); or ship a semver-major and leave users on the current major line screwed, and forced to adapt to the React breakage (and thus accommodating those users who weren't broken with React 15.5).

React 15.5 shipped a change that was objectively minor.  It adds a console.log, which isn't even present in production builds.  It affects absolutely nothing for my users.
Enzyme had a third choice; do exactly the fix I proposed above.  With that fix, if you had 15.5 and things were working, Enzyme would have had a minor patch and things would have kept working.  If you had 15.5 and you were a "responsible developer" whose tests break for any console logs, then when Enzyme referenced TestUtils.createRenderer, React would have logged the warning, and tests would have broken, but it would have been React breaking them, not Enzyme.  If you had React 15.5 and you did all the 15.5 upgrades, then Enzyme would have happily chugged along with no warnings, and all would be well.  You would work correctly in all cases, which is the definition of correct software.
I'm not sure why a major version would leave anyone "screwed" - it would have let people know they needed to do something when david told them there was a package that needed upgrading.  I'd much rather get a notification from david that I need to do something some time next week than a wall of red from travis-ci for all my various projects on the day before my code freeze.
Enzyme chose to throw an error for people who casually did an npm install today, and break a whole lot of builds.  You can argue the semantics of APIs all you want, but at the end of the day Enzyme is the package that's causing me grief, and it's objectively a breaking change.

I'm using react ^0.14.8 (I know - old) and it also affected me. I downgraded enzyme to ~2.7.1 and things got back to normal.
I'm not so much up to date with news in react, but imo if external libs, depending on enzyme, work with enzyme 2.8.0 (@jwalton proposed downgrading to this version as a solution in first comment) and not 2.8.1 then it sounds like breaking changes for me. Not a patch.
I just hope I'll be able to use enzyme in future versions, b/c I won't be able to update my react any time soon unfortunately.

@tomjal adding react-test-renderer didn't work for me - I got another error: Cannot find module 'react-dom/test-utils'

Just to re-iterate from @tiriana's point, we are also using React 0.14.8 and enzyme ^2.2.0. Everything was working fine until enzyme 2.8.1 shipped yesterday. Our react version didn't change. Downgrading and fixing version to 2.8.0 solved our problem too.

0.14.8 works for me.  If you open a new folder and try:
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node -e "try{require('enzyme'); console.log('pass');} catch(err) {console.log('***FAIL***', err.stack);}"

Does that print "pass" or "fail"?  Is it possible you have some dependency that's pulling in react 0.15.5 and causing this?

So that prints pass, but when running the unit tests through karma, I get this:
13 04 2017 16:56:10.341:ERROR [framework.browserify]: bundle error
13 04 2017 16:56:10.346:ERROR [framework.browserify]: Error: Cannot find module 'react-dom/test-utils' from '<redacted>/node_modules/enzyme/build'
13 04 2017 16:56:10.365:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/
13 04 2017 16:56:10.373:INFO [launcher]: Starting browser PhantomJS
13 04 2017 16:56:10.430:ERROR [framework.browserify]: bundle error
13 04 2017 16:56:10.430:ERROR [framework.browserify]: Error: Cannot find module 'react-test-renderer/shallow' from '<redacted>/node_modules/enzyme/build'

npm ls | grep react shows me this:
├──<EMAIL_ADDRESS>extraneous
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>npm ├─┬<EMAIL_ADDRESS>ERR!├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>

If it's affecting users without React 15.5 in their trees, then it is definitely a bug that needs fixing, but I'm not sure how it could be.

That is definitely a mystery.  This is a long shot but, @shahzainb do you have any projects npm linked into your tree?
The only place enzyme tries to require 'react-test-renderer' is here, and it's guarded by the REACT155 check which is set here in a pretty non-ambiguous fashion.  It's got to be picking up the new react from somewhere...  I'm pretty sure my PR would fix this, but only because it's going to try to fall back on the old code.

The enzyme 2.8.1 upgrade also mysteriously broke builds for me as well (we are running react 15.3.2).  I am pinning to 2.8.0

@jwalton nope I deleted the whole node_modules directory and did a full install before commenting with the above log of versions, just to make sure :)
I'll debug this further when I get some time.

This one hit me as well. Luckily I'm used to npm releases breaking things. The CI logs complained. There is a try...catch to attempt to tell me what's wrong, but webpack catches the failed module first. Fortunately webpack tells me which file attempted to make the failed import (enzyme) and sure enough there was a release the same day the error happened.
Found the culprit between 2.8.0 and 2.8.1: https://github.com/airbnb/enzyme/compare/a4c63a19f8648942b3fca72bf34d863cfa0c6dd9...8ab9528668e2b49c769e6fc4879ea710575b7f2f?expand=1
Ideally React would have done a major bump for removing code out to a different dependency and it would be more obvious something would break.
Also it might be possible enzyme to put detection around the use of TestUtils.createRenderer and fallen back to the require('react-test-renderer/shallow').createRenderer statement. That would probably prevent failures for people:
const shallowRendererFactory = TestUtils.createRenderer || require('react-test-renderer/shallow').createRenderer;

v2.8.2 published. Please comment if you're still having trouble.

@jwalton About the snippet you pasted - it logged pass in my case.

@ljharb Thx for quick reaction. But unfortunately I still get this issue: Cannot find module 'react-test-renderer/shallow'.

@tiriana can you file a new issue, and include your installed versions of react (and react-related things)?

@jwalton I actually have react 0.14.9, but nothing seems to pull readt 15.5
npm ls | grep react
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

@ljharb sure thing, will do.

@ljharb done: https://github.com/airbnb/enzyme/issues/899

Sorry, but 2.8.2 still fails
Cannot find module 'react-addons-test-utils' from 'react-compat.js'

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:169:17)
      at node_modules/enzyme/build/react-compat.js:143:21
      at Object.<anonymous> (node_modules/enzyme/build/react-compat.js:214:5)

npm ls | grep react
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped

Still failing my build too, with react 15.3.2

if I add npm i react-test-renderer  it passes. Does enzyme not list this dependency?

I'm trying to find where react-addons-test-utils used to come from... to find where react-test-renderer should go :/

See the readme; you need to explicitly add it.

oh :) sorry

Upgrading enzyme from 2.8.0 to 2.8.1 or 2.8.2 without upgrading React breaks my build, too.
The error is
 Cannot find module 'react-dom/test-utils'
I'm using react 15.4.x. and react-dom 15.4.x

@paibamboo it shouldn't attempt to require react-dom/test-utils unless you're using React >=15.5.

Why is react-test-renderer not declared as as peerDependency? I understand it's only required for<EMAIL_ADDRESS>but I don't see the problem with declaring it.

Declaring it forces everyone to install it, even if they're not using v15.5.

2.8.2 still fails for me where 2.8.0 worked. I'm using react, react-dom, and react-addons-test-utils all versioned at 15.4.2; karma 1.7.0, and webpack 2.1.  The way I finally made this work was to extend my webpack externals object to be the following:
externals: {
    'react/addons': true,
    'react/lib/ExecutionEnvironment': true,
    'react/lib/ReactContext': true,
    'react-dom/test-utils': true,
    'react-test-renderer/shallow': true
}

I tried a few different permutations with react-test-renderer before settling on this solution:

install react-test-renderer, no external -> failed
install react-test-renderer, with external -> passed
uninstall react-test-renderer, with external -> passed
uninstall react-test-renderer, no external -> failed

So clearly listing the package as an external for webpack was sufficient.  All of my shallow rendering tests still pass, and even adding a failing expectation such as expect(wrapper).to.have.className('thisDoesNotExist'); fails as expected, so it seems to be working in this configuration?

@ZebraFlesh  solution worked for me

Sounds like we may need to update the webpack documentation, and then we can close this issue?


Using Rickshaw.Fixtures.formatBase1024KMGTP seems to cause Y axis to go weird

With following configuration
var y_fixture = Rickshaw.Fixtures.Number.formatBase1024KMGPT;

var graph = new Rickshaw.Graph( {
    element: config.div.find(".chart")[0],
    width: 550,
    height: 250,
    renderer: config.renderer || 'multi',
    padding: { top: 0.05 },
    series: plotseries

});

var axes = new Rickshaw.Graph.Axis.Time( {
    graph: graph,
    orientation: 'bottom',
    timeFixture: new Rickshaw.Fixtures.Time.Local()
} );

var y_ticks = new Rickshaw.Graph.Axis.Y( {
    graph: graph,
    orientation: 'left',
    tickFormat: y_fixture,
    element: config.div.find(".y_axis")[0]
} );

var legend = new Rickshaw.Graph.Legend( {
    graph: graph,
    element: config.div.find(".legend")[0]
} );

I get following graph

If I use Rickshaw.Fixtures.Number.formatKMGT I get the following one. (Which is same as KMBT but B changed to G).

>Rickshaw.Fixtures.Number.formatBase1024KMGTP(11111111)
"10.596381187438965M"
>Rickshaw.Fixtures.Number.formatKMGT(11111111)
"11.111111M"

The problem seems to be fixable by surrounding the divisions with (y / factor).toFixed(2)

Interesting. Do you think the best option would be adding this information to documentation, or patching it?

My feeling is that it should be patched, as it cannot be fixed without altering formatBase1024KMGTP function.


GDLisp

Where do we put this?
https://github.com/eutro/gdlisp

Needs more info. Appears to be a pet project of sorts.

Yeah, absolutely. I haven't tried anything with it.

This has not been updated in 2 years.


changing memory allowed on ubuntu command line

Wondering if I can allocate memory when using Ubuntu command line.
I have done this on my mac via the gui but can't find info regarding command line.

No, you can't; on Docker for Mac, the daemon runs on a minimal Linux distro, that runs in a hyperKit VM. If you specify the amount of memory, that controls how much memory the VM gets.
On Linux, docker runs directly on the host, so has all memory available that the host has. You can limit the amount of memory that a container is allowed to use (see https://docs.docker.com/engine/admin/resource_constraints/)
Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

https://forums.docker.com
the Docker community Slack channel
StackOverflow

I'm going to close this issue because this is not a bug, but feel free to continue the conversation 👍

Awesome, I wanted it to have all of the memory available.. THANK YOU!


InstallationError While Using Pipenv install opencv-python

Expected behaviour
I use pipenv to install opencv-python, and I expected the package is successfully installed
Actual behaviour
I got Error:
(smartia-web-app) lnguyen@pop-luke:~/PycharmProjects/smartia-web-app$ pipenv update Running $ pipenv lock then $ pipenv sync. Locking [dev-packages] dependencies… Locking [packages] dependencies… ✔ Success!  Updated Pipfile.lock (482088)! Installing dependencies from Pipfile.lock (482088)…   🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 82/82 — 00:00:07 To activate this project's virtualenv, run pipenv shell. Alternatively, run a command inside the virtualenv with pipenv run. All dependencies are now up-to-date! (smartia-web-app) lnguyen@pop-luke:~/PycharmProjects/smartia-web-app$ pipenv install opencv-python Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning. Installing opencv-python… ✔ Installation Succeeded  Pipfile.lock (aa6ff6) out of date, updating to (482088)… Locking [dev-packages] dependencies… Locking [packages] dependencies… ✘ Locking Failed!  Traceback (most recent call last):   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 126, in <module>     main()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 118, in main     _main(parsed.pre, parsed.clear, parsed.verbose, parsed.system,   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 78, in _main     results = resolve(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 61, in resolve     return resolve_deps(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/utils.py", line 718, in resolve_deps     resolved_tree, hashes, markers_lookup, resolver = actually_resolve_deps(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/utils.py", line 480, in actually_resolve_deps     resolved_tree = resolver.resolve()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/utils.py", line 385, in resolve     results = self.resolver.resolve(max_rounds=environments.PIPENV_MAX_ROUNDS)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/resolver.py", line 102, in resolve     has_changed, best_matches = self._resolve_one_round()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/resolver.py", line 206, in _resolve_one_round     for dep in self._iter_dependencies(best_match):   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/resolver.py", line 301, in _iter_dependencies     dependencies = self.repository.get_dependencies(ireq)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 234, in get_dependencies     legacy_results = self.get_legacy_dependencies(ireq)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 426, in get_legacy_dependencies     results, ireq = self.resolve_reqs(download_dir, ireq, wheel_cache)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 297, in resolve_reqs     results = resolver._resolve_one(reqset, ireq)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 260, in _resolve_one     abstract_dist = self._get_abstract_dist_for(req_to_install)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 211, in _get_abstract_dist_for     abstract_dist = self.preparer.prepare_linked_requirement(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 294, in prepare_linked_requirement     abstract_dist.prep_for_dist(finder, self.build_isolation)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 127, in prep_for_dist     self.req.run_egg_info()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/req/req_install.py", line 470, in run_egg_info     call_subprocess(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/utils/misc.py", line 703, in call_subprocess     raise InstallationError( pipenv.patched.notpip._internal.exceptions.InstallationError: Command "python setup.py egg_info" failed with error code 1 in /tmp/tmp7ezd0ur2build/opencv-python/ File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 126, in <module>     main()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 118, in main     _main(parsed.pre, parsed.clear, parsed.verbose, parsed.system,   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 78, in _main     results = resolve(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 61, in resolve     return resolve_deps(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/utils.py", line 718, in resolve_deps     resolved_tree, hashes, markers_lookup, resolver = actually_resolve_deps(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/utils.py", line 480, in actually_resolve_deps     resolved_tree = resolver.resolve()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/utils.py", line 385, in resolve     results = self.resolver.resolve(max_rounds=environments.PIPENV_MAX_ROUNDS)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/resolver.py", line 102, in resolve     has_changed, best_matches = self._resolve_one_round()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/resolver.py", line 206, in _resolve_one_round     for dep in self._iter_dependencies(best_match):   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/resolver.py", line 301, in _iter_dependencies     dependencies = self.repository.get_dependencies(ireq)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 234, in get_dependencies     legacy_results = self.get_legacy_dependencies(ireq)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 426, in get_legacy_dependencies     results, ireq = self.resolve_reqs(download_dir, ireq, wheel_cache)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 297, in resolve_reqs     results = resolver._resolve_one(reqset, ireq)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 260, in _resolve_one     abstract_dist = self._get_abstract_dist_for(req_to_install)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 211, in _get_abstract_dist_for     abstract_dist = self.preparer.prepare_linked_requirement(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 294, in prepare_linked_requirement     abstract_dist.prep_for_dist(finder, self.build_isolation)   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 127, in prep_for_dist     self.req.run_egg_info()   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/req/req_install.py", line 470, in run_egg_info     call_subprocess(   File "/home/lnguyen/.local/lib/python3.8/site-packages/pipenv/patched/notpip/_internal/utils/misc.py", line 703, in call_subprocess     raise InstallationError( pipenv.patched.notpip._internal.exceptions.InstallationError: Command "python setup.py egg_info" failed with error code 1 in /tmp/tmp7ezd0ur2build/opencv-python/
Steps to reproduce

example code: N/A
operating system: I am using Linux - Pop OS 20.4
architecture (e.g. x86)
opencv-python version <IP_ADDRESS>
Python version 3.8

Issue submission checklist

[ ] This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)

[x] I have read the README of this repository and understand that this repository provides only an automated build toolchain for OpenCV Python packages (there is no actual OpenCV code here)

[ ] The issue is related to the build scripts in this repository, to the pre-built binaries or is a feature request (such as "please enable this additional dependency")

[x] I'm using the latest version of opencv-python

You have latest pip in use? That's pretty much the first thing you would have to check because the error indicates that pip is trying to compile the package from source. 19.3 is required as explained in the README and in the release notes.

@skvark
I did this this morning through the Terminal, and still having the error after it

Here is the pip version in my Pycharm under my ENV

Your pipenv is 2 years old. Maybe that has something to do with the error?

And if you can install the package with pip (you probably can), then the error is caused by pipenv.

Good catch!
I updated the pipenv by
pip3 install pipenv --upgrade
and everything is working normally
Thank you for the Assistant


Actuator endpoints returning 404

Hi
Using version 2.6.1, I can't seem to access the actuator pages.
I have tried adding the following configuration:
management:
  endpoint:
    health:
      probes:
        enabled: true
      enabled: true
  endpoints:
    web:
      exposure:
        include: info,health

But that still results in a 404:

Hi
Are you sure you are reaching the actuator service on port 9090? The service is running on a different port for security reasons.

Hi, I think this question has been answered, therefore I'll close this issue, please open a new issue or re-open this issue if you are still experiencing an issue.


new question

Using master v2.32,
autogen.sh
build.sh
the following problem occurs
CC       merecat-base64.o
CC       merecat-md5.o
CC       merecat-merecat.o
CC       merecat-mmc.o
CC       merecat-pidfile.o
In file included from merecat.c:52:0:
conf.h: In function ‘conf_srv’:
conf.h:88:16: error: ‘do_ssl’ undeclared (first use in this function)
arr[0].ssl  = do_ssl;
^
conf.h:88:16: note: each undeclared identifier is reported only once for each function it appears in
Makefile:563: recipe for target 'merecat-merecat.o' failed
make[2]: *** [merecat-merecat.o] Error 1

To debug that I need your config.log file. It looks like a missing #ifndef ENABLE_SSL.  In the meantime, try installing libssl-dev,

Ah, now I see!  Seems I've forgot to update the code path when you build without support for mercat.conf.  I.e., configure --without-config, or when the configure script cannot find libConfuse installed.  Good, find thanks!

There, latest master now has a fix for this issue. I've also updated the README with the build requirements to unlock HTTPS support (by installing libConfuse-dev).


Example code is parsing pages, but intends to parse paragraphs

The following code in
           # Read the text recognition output from the processor
            for page in document.pages:
                for form_field in page.form_fields:
                    field_name = get_text(form_field.field_name, document)
                    field_value = get_text(form_field.field_value, document)
                    print("Extracted key value pair:")
                    print(f"\t{field_name}, {field_value}")
                for paragraph in document.pages:
                    paragraph_text = get_text(paragraph.layout, document)
                    print(f"Paragraph text:\n{paragraph_text}")

code intention, that matches the "Upload Test Document" functionality should be
            for page in document.pages:
                for form_field in page.form_fields:
                    field_name = get_text(form_field.field_name, document)
                    field_value = get_text(form_field.field_value, document)
                    print("Extracted key value pair:")
                    print(f"\t{field_name}, {field_value}")
                for paragraph in page.paragraphs:
                    paragraph_text = get_text(paragraph.layout, document)
                    print(f"Paragraph text:\n{paragraph_text}")

Reference: https://github.com/googleapis/python-documentai/pull/147

@dgallegos Thanks for filing and fixing this bug.