primordic/IssueDupesLite huggingface dataset:
Repository: composer/satis

Issue #656: "Your package name My Repository is invalid": bug or breaking change?
Created: 2021-07-08T21:37:53Z
Hello,
Using the satis.json from the docs at https://getcomposer.org/doc/articles/handling-private-packages.md#setup :
{
  "name": "My Repository",
  "homepage": "http://packages.example.org",
  "repositories": [
    { "type": "vcs", "url": "https://github.com/mycompany/privaterepo" },
    { "type": "vcs", "url": "http://svn.example.org/private/repo" },
    { "type": "vcs", "url": "https://github.com/mycompany/privaterepo2" }
  ],
  "require-all": true
}
And the latest container tag:
Digest: sha256:0f6cb23de613edf42bfe4da17333b5ada6bb99e21c20324ed91db5f13bb9e744
Status: Downloaded newer image for composer/satis:latest

I get this error:
docker run --rm --init -it \
  --user $(id -u):$(id -g) \
  --volume $(pwd):/build \
  composer/satis build satis.json foo

In RootPackageLoader.php line 76:
                                                                                                                                                                                                           
  Your package name My Repository is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name shoul  
  d match "^[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]?|-{0,2})[a-z0-9]+)*$".                                                                                                                               
                                                                                                                                                                                                           

build [--repository-url [REPOSITORY-URL]] [--repository-strict] [--no-html-output] [--skip-errors] [--stats] [--] [<file> [<output-dir> [<packages>...]]]


Is this a bug or a breaking change?
Cheers!

Duplicate issue #526: Deprecation warning for name attribute in satis.json
Created: 2019-02-12T00:47:34Z
The name in the satis.json is treated like a repository and so a deprecation warning is thrown during build:
Deprecation warning: Your package name Satis Repository is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9]([_.-]?[a-z0-9]+)*". Make sure you fix this as Composer 2.0 will error.

Closing comment (2021-08-02T07:17:31Z): Similar to #656 but the latter is more up to date since we updated to Composer v2.
Repository: composer/satis

Issue #600: Deprecation notice for authentication via URL query parameters
Created: 2020-05-26T08:26:43Z
Describe the bug
When I click on any of the releases on the renderer html page for a package, I get a GitHub Not found page. Shortly after I have received an email from Github saying:

Please use the Authorization HTTP header instead, as using the access_token query parameter is deprecated. If this token is being used by an app you don't have control over, be aware that it may stop working as a result of this deprecation.
Depending on your API usage, we'll be sending you this email reminder on a monthly basis for each token and User-Agent used in API calls made on your behalf.
Just one URL that was accessed with a token and User-Agent combination will be listed in the email reminder, not all.
Visit https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param for more information about suggested workarounds and removal dates.
Thanks,
The GitHub Team

To Reproduce
Click on any of the releases on the renderer html page for a package hosted on GitHub.
Outcome
{
  "message": "Not Found",
  "documentation_url": "https://developer.github.com/v3/repos/contents/#get-archive-link"
}


Expected behavior
I should be navigated to the release page for that release or something similar.

Duplicate issue #593: GitHub is deprecating auth via query param -- Composer 1.9.3 has a fix
Created: 2020-04-13T20:16:50Z
Describe the bug
GitHub is deprecating the ability to authenticate via query parameter: https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters
This causes warnings to be sent by GitHub, and eventually will break.
To Reproduce
Attempt to use Satis for any private repository, auth with a token, and the token user will receive an email warning about the deprecation.
Expected behavior
That Satis will use the correct method of auth, and not create warnings.
See this issue (composer/composer#8586) for a discussion of the Composer side of this. It seems like updating the internal Composer version to 1.9.3 may be sufficient to resolve this problem.

Closing comment (2020-11-11T21:37:39Z): Yes, unless this issue is similar to #600
But closing either way
Repository: composer/satis

Issue #403: documentation
Created: 2017-02-28T12:19:03Z
I want to move some of the docs from https://getcomposer.org/doc/articles/handling-private-packages-with-satis.md into the docs directory, and improve them. Currently they are not easy to find, not very precise/detailed and overal just not great (in my opinion).
Any help, thoughts and feedback is appreciated.

Duplicate issue #582: PHP version documentation outdated
Created: 2020-02-03T16:29:35Z
https://getcomposer.org/doc/00-intro.md
The documentation states PHP version 5.3.2+ is required
Composer requires PHP 5.3.2+ to run
However the default installation is via composer and requires PHP 7.2+
https://github.com/composer/satis/blob/master/composer.json
"require": {
        "php": "^7.2",

Actual behaviour on a stock CentOS 7 box:
$ composer create-project composer/satis:dev-master
[InvalidArgumentException]
Could not find package composer/satis with stability stable in a version installable using your PHP version 5.4.16.

If the documentation could be updated to mirror the composer.json file it should prevent others following me into building a CentOS 7 server defaulting to PHP 5.4 which can't then install composer.
If the docs were within the project I'd happily have issued a PR but don't believe that to be the case.

Closing comment (2020-02-03T16:33:00Z): Somewhat related to #403 - having the documentation in another repo right now does not make much sense.
Repository: composer/satis

Issue #311: git ssh repos in index.html
Created: 2016-03-12T18:56:07Z
so, i put some git repo to satis.json:
git@github.com:composer/satis.git
satis will scan it via ssh, etc. but html it generates would be vcs link as:
<a href="git@github.com:composer/satis.git" title="5aa6fd7833019ffe0f09d7d794a34af2ab77450f">dev-master</a>

meaning browser will treat this as relative url, and the link would be:
https://satis.example.org/git@github.com:composer/satis.git

the alternative way to specify git links that are absolute and understood by git and browser would be to prefix with ssh:// and change colon to slash:
ssh://git@github.com/composer/satis.git
this way the links in generated html won't be relative

Duplicate issue #418: wrong url to repository
Created: 2017-06-01T14:14:31Z
Hello,
I've successfully configured satis to get my gitlab projects on an other server.
The problem is that the URLs to the repositories are wrong...
http://composer.xx.com/git@gitlab.xx.com:private/storage.git
Is there a way to tell satis the correct url?
Thank you

Closing comment (2017-06-06T12:43:04Z): Duplicate of #311 I just realized :-)
Repository: composer/satis

Issue #325: Tagging release versions to allow fetching a known version of Satis
Created: 2016-04-13T13:43:16Z
To allow deploying a particular version of Satis it would be very useful if git tags could be utilised for each new release of Satis. This would for instance allow a CI process running a Satis build to be able to pull down a known version of Satis to run (using composer create-project).
This would be especially useful when breaking changes are made such as removing PHP 5.4 support as any CI servers with PHP 5.4 on them (CentOS/RHEL7) can still build from the last tag supporting 5.4 instead of always using master

Duplicate issue #336: New beta release?!
Created: 2016-06-08T16:56:12Z
It's been awhile since 1.0.0-alpha, maybe it's time to 1.0.0-beta release?

Closing comment (2016-06-08T18:41:06Z): Kind of a duplicate of #325
There are too many bugs open in my opinion to tag again already.
Repository: composer/satis

Issue #94: Generate index.html without re-scanning repositories
Created: 2013-10-13T22:04:45Z
The satis build command does a couple of things:

Scans repositories for new versions.
Generates a packages.json file.
Generates an index.html file.

When tweaking the Twig template for index.html, it would be useful to have a command for only doing step 3, or at least to avoid doing step 1, which can take a long time.

Duplicate issue #174: Regenerate index.html from packages.json
Created: 2014-09-10T00:01:32Z
This goes out of standard workflow: if I make (or some tool) modifications to packages.json it would be nice to have separate command to regenerate index.html.
My use case is that I need to put dist section to every package that points to external location where package could be downloaded. A different tool makes this job but index.html remains outdated.

Closing comment (2015-11-21T11:54:05Z): Duplicate of #94.
Repository: composer/satis

Issue #62: Ability to dump dependencies
Created: 2013-04-03T22:52:02Z
Add require-dependencies as boolean key to satis.json file.
Currently users have two options:

require-all as true and dump all packages;
require with wanted packages.

We may face a problem when trying use require. When running an install/update we may get a missed package. We must declare explicitly every dependency... for every package and its dependencies... and its dependencies... and then you have no life. require-dependencies could make PO's life easier

Duplicate issue #59: Building dist archives doesn't go through packages recursively
Created: 2013-04-01T16:36:06Z
Whenever I require package in my source json and I build dists it doesn't build dists for its dependencies.
To achieve that you need to keep track of all dependencies and require them manually in satis configuration. You also need to change versions whenever dependency version changes.
I think it should rather go recursively inside and build dists for all of the requirements as well. Maybe adding option for archive would be good - create-dependencies-dists.
Thanks

Closing comment (2013-06-20T14:18:07Z): Thanks for pointer. This seems to be now duplicate #62
Repository: concrete-utopia/utopia

Issue #1469: Resizing the code editor pane sometimes scrolls the entire editor. Only reloading fixes it.
Created: 2021-07-07T11:21:49Z
This one is very hard to reproduce. Sometimes dragging the split pane (from between the code editor and the canvas) to resize the code editor will trigger a scroll on the entire editor in a way that doesn't appear to be fixable. Whenever this has happened to me I've had to reload the editor. It might be a layout issue as opposed to scrolling?

Duplicate issue #1483: Bug: resizing the code editor scrolls the editor
Created: 2021-07-12T11:38:53Z
STR

New project
Resize the code editor left-right a few times in one drag
(possibly) click into the code editor or onto the navigator

Observed: entire editor scrolls, cutting 20px or so of the top of the editor in the process. Can't scroll back
Expected: No scrolling
(NEW) Video:

  
    
    

    editor.scrollling.undesired.mp4

Closing comment (2021-07-12T12:51:31Z): This is a duplicate of #1469, but I'll close that one as this has a video which will help with the repro
Repository: concrete-utopia/utopia

Issue #5464: Replace Element is broken for the root element of a component
Created: 2024-05-02T13:01:57Z
If you select the root element of a component and attempt to replace that element (via the navigator or context menu), we will instead add the new element as a child of the component

Duplicate issue #5464: Replace Element is broken for the root element of a component
Created: 2024-05-02T13:01:57Z
If you select the root element of a component and attempt to replace that element (via the navigator or context menu), we will instead add the new element as a child of the component

Closing comment (2024-05-15T12:37:20Z): from https://discord.com/channels/647102474519576589/1200387323884490812/1240281642602594315

btw EP.parentPath is already unsafe if we call it for the root element of a component, because it will just happily chop off the root element from the path and return a pointer to the instance of the component holding the root element. but surely that's not -really- the parent when it comes to replacements or siblings. –– this EP.parentPath problem is maybe also related to #5464
Repository: concrete-utopia/utopia

Issue #1218: [assets] uploading a new image shows unrelevant toast message
Created: 2021-05-07T09:39:33Z
Uploading an asset that didn't exist already shows the "assets replaced" toast, even when nothing was in fact replaced.
The correct behaviour is that it should only be shown when an existing asset was actually replaced.
This was added because caching(?) makes it show the previous asset until reloading the editor, if this can be fixed the toast can be removed completely.

Duplicate issue #1074: Adding images to Utopia always shows "Assets replaced" popoup
Created: 2021-04-12T16:52:09Z
Problem
When adding an image to Utopia by e.g. adding it to the file browser, we show a toast that starts with "Assets replaced". However, this happens also when an image is added to the editor for the first time - so there is no replacing involved.
We introduced this toast to indicate that image assets that have been replaced may need an editor update. However, it appears that now this toast fires always:
(in image-insert.ts: )
export function fileResultUploadAction(fileResult: FileResult, targetPath: string): EditorAction {
  switch (fileResult.type) {
    case 'IMAGE_RESULT': {
      const afterSave = EditorActions.saveImageReplace()

where saveImageReplace invokes
case 'SAVE_IMAGE_REPLACE': {
          const toastAction = showToast(
            notice(
              'Assets replaced. You may need to reload the editor to see changes.',
              'WARNING',
              true,
            ),
          )

Closing comment (2021-05-17T11:49:40Z): @enidemi I think this is a duplicate of #1218 - can you confirm?
Repository: concrete-utopia/utopia

Issue #1128: [BUG] Highlight bounds aren't correctly captured for all top level elements of this project
Created: 2021-04-20T14:21:17Z
In the Majestic Broker project, for some reason we only capture highlight bounds for the main App component, meaning that selection following is broken for anything else.
Project: https://utopia.pizza/project/0501e894/

Duplicate issue #1159: Selection from code to canvas isn't updating
Created: 2021-04-26T18:57:51Z
Problem
Moving the cursor in code does not select the element on the canvas. Video below.
Specific STR a bit unclear, but involved insertion, modifying css in code incl deleting and re-adding and undoing / redoing changes, and then navigating via arrow keys and mouse.

  
    
    

    selection.does.not.follow.mp4

Closing comment (2021-04-27T09:58:24Z): This might be related to #1128, so it's worth checking this again when that has been fixed.
Repository: concrete-utopia/utopia

Issue #1024: Code editor scrolls back when moving cursor to end of line with keyboard
Created: 2021-03-30T17:01:13Z
Describe the bug
When encountering a line of code that's longer than the available window, and using CMD+Right to jump to the end of the line, the editor jumps, but then scrolls back
To Reproduce

Type in a line of code that stretches beyond the visible right edge of the code editor, eg

<div
        style={{
          width: 270,
          height: 215,
          background: 'hsl(0,0%,97%)',
          boxShadow: 'rgba(0, 0, 0, 0.1) 0px 0px 0px 1px, rgba(0, 0, 0, 0.1) 0px 4px 11px',
          backgroundColor: 'rgb(247, 247, 247, 1)',
        }}
      >Hello</div>


(if required, make the code editor pane smaller)
Position the cursor in the line containing box-shadow
Press CMD+Right (or repeatedly, Right)
Cursor moves correctly, editor scrolls, and scrolls back

Expected behaviour
Cursor moves, window scrolls and stays scrolled
Screenshots

Duplicate issue #1025: Editing code causes "jumps" in the code editors scroll position
Created: 2021-03-30T17:09:01Z
Describe the bug
When making edits (eg deletion or pasting) code, the code editor jumps visually. It shouldn't.
To Reproduce
Steps to reproduce the behavior. For canvas tasks, take care to note down all relevant key holds, keys typed, selected state etc. E.g:

Paste the below code into a new project, into storyboard.js
Copy and paste the large div with multiple rows of style info below itself

Observed: file scrolls to the top, then back
Result: Mouse pointer is still indicating resize, even though A can't be resized where the mouse is, an B is no longer selected or resizeable when dragging the mouse where it is.
Expected behaviour
No scrolling at all should occur except the built-in VSCode one.
Likely related to #1024
Sample Code
/** @jsx jsx */
import * as React from 'react'
import { Scene, Storyboard, jsx } from 'utopia-api'
export var App = (props) => {
  return (
    <div
      style={{
        padding: 20,
        width: '100%',
        height: '100%',
        backgroundColor: '#FFFFFF',
        position: 'relative',
      }}
    >
      <div
        style={{
          width: 270,
          height: 215,
          background: 'hsl(0,0%,97%)',
          boxShadow: 'rgba(0, 0, 0, 0.1) 0px 0px 0px 1px, rgba(0, 0, 0, 0.1) 0px 4px 11px',
          backgroundColor: 'rgb(247, 247, 247, 1)',
        }}
      >
        <div
          style={{
            paddingLeft: 8,
            paddingRight: 8,
            fontFamily: 'Inter',
            fontSize: 11,
            color: 'hsl(0,0%,10%)',
            display: 'flex',
            alignItems: 'center',
            height: 34,
          }}
        >
          <span style={{ fontWeight: 600 }}>Item Selector</span>
          
        </div>
        
      </div>
    </div>
  )
}
export var storyboard = (
  <Storyboard>
    <Scene
      component={App}
      props={{}}
      style={{ position: 'absolute', left: 0, top: 0, width: 375, height: 812 }}
    />
  </Storyboard>
)

Closing comment (2021-04-06T11:09:53Z): I'm pretty sure this is related to #1024 (as mentioned in there)
Repository: concrete-utopia/utopia

Issue #833: Regression: Elements in JSX blocks can no longer be directly updated
Created: 2021-01-08T14:56:32Z
In this project you are able to select the blue rectangle on the canvas and drag it or update it via the Inspector, but doing so no longer updates the code. This is a very recent regression, possibly caused by a data-uid fix that was included in #820

Duplicate issue #834: Fix being able to manipulate elements inside arbitrary JSX blocks.
Created: 2021-01-08T15:00:50Z
Appears the recent work to support comments in arbitrary blocks has broken the ability to reproduce the code after manipulating the elements.
Sample project: this project - you are able to select the blue rectangle on the canvas and drag it or update it via the Inspector, but doing so no longer updates the code. This is a very recent regression, possibly caused by a data-uid fix that was included in #820

Closing comment (2021-01-08T15:06:53Z): Closing as duplicate of #833
Repository: concrete-utopia/utopia

Issue #508: Support ESModule import
Created: 2020-09-08T10:06:51Z
Problem
We initially assumed that only a v small number of React projects use ESModules. Unfortunately, that turned out to be somewhat too optimistic.
The R3F community  in particular likes and uses them, and they the projects there are snacks we'd like to support.
Related / affected: #86, #426, #427

Duplicate issue #426: Can't import OrbitControls due to it being an ES Module
Created: 2020-08-17T18:28:04Z
project: https://utopia.app/p/ee1a59ea-wobbly-airbus/
This very may well will be a wontfix, but this is a very very commonly used three feature, and the old package https://www.npmjs.com/package/three-orbitcontrols recommends the ES Module import.

Closing comment (2020-09-25T16:06:52Z): Closing as this is basically a duplicate of #508
Repository: concrete-utopia/utopia

Issue #1264: performance: inspector component section rerenders on every scroll
Created: 2021-05-14T13:58:57Z

Duplicate issue #1262: Typing a character into div contents causes inspector to re-render even though selection hasn't changed
Created: 2021-05-14T11:18:42Z
STR

New project
Type "Hello world" into the div in , one character at a time

Observed: on each keystroke, inspector re-renders and flickers (maybe a section is being added?).
Expected: it doesn't, since selection doesn't change
NB This seems like a pretty recent (1w or less) regression

Closing comment (2021-05-16T10:42:50Z): @enidemi could this be related to #1264 ?
Repository: concrete-utopia/utopia

Issue #1196: Logging out in one tab shows "Utopia is offline" error bar
Created: 2021-05-04T15:19:26Z
STR:

Open a project in one tab, log in, and open the Chrome inspector
Open another tab and go to /logout

The open project will now display the "Utopia is offline" status bar along the top, and will repeatedly make failing (with a 401 status) calls to the server.
MN edit: see also #1196

Duplicate issue #1215: Show one error message if I'm not logged in, and another if the user has lost connection to the server
Created: 2021-05-06T16:33:01Z
Problem
If I get logged out, I now see (correctly) the error message telling me so, in the bar atop the editor. However, if I get disconnected (eg wifi cuts out, local server dies) I see the same error message. We already had an error message for the "disconnected" application state, so we should resurrect it, and determine when to show which.

Closing comment (2021-05-06T16:56:39Z): Duplicate of #1196 - closing
Repository: consuldemocracy/consuldemocracy

Issue #730: Configurable dictionary for full text searches 
Created: 2015-11-25T13:34:36Z
We are currently using Postgres's spanish dictionary for full text search.
We would like to use different dictionaries depending on the configuration of a particular Consul instance.
Suggestion:
Use a setting's key to define the desired dictionary.

Duplicate issue #3294: hardcoded "spanish" language in module Searchable
Created: 2019-02-13T01:34:18Z
The file app/models/concern/searchable.rb uses a dictionary that is set to spanish. This should be configurable.
module Searchable
  extend ActiveSupport::Concern

  included do
    include PgSearch
    include SearchCache

    pg_search_scope :pg_search, {
      against: :ignored, # not used since using a tsvector_column
      using: {
        tsearch: { tsvector_column: 'tsv', dictionary: "spanish", prefix: true }
      },
      ignoring: :accents,
      ranked_by: '(:tsearch)',
      order_within_rank: (column_names.include?('cached_votes_up') ? "#{table_name}.cached_votes_up DESC" : nil)
    }
  end

end

Closing comment (2019-10-19T03:19:01Z): Duplicate of #730.
Repository: consuldemocracy/consuldemocracy

Issue #3553: Close supports to comments on Collaborative legislation processes
Created: 2019-05-28T09:36:45Z
What we need
When the debate or drafting phase of a collaborative legislation processes have finished, it should not be allowed to users to vote on the existing comments, as it is not allowed to create new comments.

Duplicate issue #4290: user can still vote on comment annotations when legislation process is closed
Created: 2020-12-16T14:02:13Z
After the legislation process period is closed the user can still vote on a annotation comment via the direct link to the comment, for example https://consulproject.org/comments/1234
User share these links to their annotations to collect votes via social media
When screenshots are needed let me know.

Closing comment (2021-10-17T18:46:12Z): Closing then as duplicate of #3553 👍.
Repository: consuldemocracy/consuldemocracy

Issue #445: Los filtros no resetean la paginación
Created: 2015-09-09T12:04:20Z
Al cambiar el filtro de un formulario la página debería resetearse a la primera
Al cambiar de tag en la nube de tags también

Forma sencilla de hacer esto: añadir un ?page=1 en las urls.

Duplicate issue #404: Eliminar parametro de página cuando se cambia de filtro
Created: 2015-09-07T14:41:58Z
Ahora si estas en la página 9 y cambias de filtro de debates, te mantienes en la página 9 de este nuevo filtro, lo cual descoloca un poco a los usuarios.

Closing comment (2015-09-10T19:44:44Z): Duplicate #445
Repository: consuldemocracy/consuldemocracy

Issue #2744: OAuth login options shouldn't show if they are not properly configured
Created: 2018-07-09T16:49:43Z
User Story
As an admin I want users to be able to login into platform.
Why is this Needed?
If the oauth logins like twitter or FB are not configured (see below) they are still shown on the login screen and users may try to login with it which will result in an error.
Description
You may call it the feature to show that these are the possibilites. If so then the documentation https://consul_docs.gitbooks.io/docs/content/en/features/oauth.html should inform how to disable showing them.
Current Behavior
Not configured oauth
  twitter_key: ""
  twitter_secret: ""
  facebook_key: ""
  facebook_secret: ""
  google_oauth2_key: ""
  google_oauth2_secret: ""

Social media logins appear on http://consul.kodujdlapolski.pl/users/sign_up.
Expected Behavior
Social media logins shouldn't appear on http://consul.kodujdlapolski.pl/users/sign_up
Steps to reproduce
It's a clear docker deployment.
Definition of Done

Duplicate issue #3346: Disable social media logins on register page when credentials are not set
Created: 2019-03-08T11:33:35Z
Currently, the register page will always show all social media buttons, even when the credentials are not set, causing a 500 page when somebody clicks the log in.
We want to achieve a situation where only configured social media logins are shown.

Closing comment (2019-11-13T03:50:59Z): Duplicate of #2744.
Repository: consuldemocracy/consuldemocracy

Issue #4355: Check target attribute in links
Created: 2021-02-12T15:25:43Z
Description
Type: Bug
Current Behavior
When I click a link which mentions it opens in a new window, it does not open in a new window.
Expected Behavior
When I click a link which mentions it opens in a new window, it opens in a new window.
Steps to reproduce

Go to sign_up page
Click on terms and conditions of use

Duplicate issue #4892: How to new debates policy target="_blank"
Created: 2022-08-03T05:33:03Z
How to new debates policy target="_blank"  Unable to open a new page. (checkbox).
Ex.
<%= f.check_box :terms_of_service,
title: t("form.accept_terms_title"),
label: t("form.accept_terms",
policy: link_to(t("form.policy"), "URL", target: "_blank"),
conditions: link_to(t("form.conditions"), "URL", target: "_blank")
) %>

Closing comment (2022-08-04T14:12:21Z): Hi, @Chanachai-Pansailom 😄.
Thanks for reporting. This is actually a known issue. Feel free to send a pull request to fix it!
Closing as duplicate of #4355
Repository: consuldemocracy/consuldemocracy

Issue #1255: User accounts verification
Created: 2016-11-06T17:23:43Z
Hi consul community!
Is there any way to remove the user account verification? In our case consul is intended to behave as a forum to take proposals, but we don't care about where come from users but in participation.
If it's not possible, is there any other solution?
The padron API is useful in other towns?
Could an administrative rol verify manually users?
...
Thanks!

Duplicate issue #1912: Customize the Verification method ?
Created: 2017-09-23T00:21:40Z
We are looking to use Consul for our Coop that has several thousand members.
Is there a way to customize the Verification method ?
Thanks

Closing comment (2017-09-25T15:59:58Z): Related to #1255
Repository: consuldemocracy/consuldemocracy

Issue #2328: Budget: add column show to valuators
Created: 2018-01-16T11:41:30Z
Background
Now on /admin/budgets/N/budget_investments/X/edit#classification admin users can assign valuators to a budget investment. Once assigned, the valuators can see their assigned budget investments to valuate.
What we need


When the tab Under valuation is active, the last column should show "Show to valuator" (instead of "Selected") with a checkbox (view screenshot).


The valuators on /valuation/budgets/N/budget_investments only should see their assigned budget investments with this checkbox active.


Notes
This feature is created on Madrid's fork on this commit, use for reference:


admin/budget_investments/_investments.html.erb (I)


admin/budget_investments/_investments.html.erb (II)


controllers/admin/budget_investments_controller.rb


controllers/valuation/budget_investments_controller.rb


models/budget/investment.rb


spec/factories.rb


db/schema.rb


🙏  Don't forget specs to this features (references on):
features/admin/budget_investments_spec.rb and features/valuation/budget_investments_spec.rb
Also don't forget to include this on dev_seeds.rb
Screenshot

Duplicate issue #2514: Backport `visible_to_valuators` feature from madrid's fork
Created: 2018-03-04T22:05:30Z
Madrid's fork has a feature that allows admins to set if a valuator should be able (or not) to see an investment. Just search visible_to_valuators in that codebase and you'll find all related code.

Closing comment (2019-10-11T21:51:28Z): This issue seems to be a duplicate of #2328, which was closed by #2342. This issue was created before the latter was merged.
Repository: consuldemocracy/consuldemocracy

Issue #2499: Let managers update a user's email
Created: 2018-03-01T10:16:24Z
What we need
At /management/account the manager should be able to update the email to a user account.

Shows user's email or "No-email user".
For "change user" red color link you can use delete CSS class.
In the edit form, the document type and number fields can be disabled.

Notes
Beware some users might not even have an email.
Screenshots
Info shows "email" and "edit user" button

New form to change email

Duplicate issue #3546: Add a "Modify email" menu to the Management interface
Created: 2019-05-28T09:29:31Z
Background
The Management interface /management/ allow the managers to do actions to help users.
What we need
Add a new submenu titled "Modify email" to the interface. It will allow to change the email associated to the user account, to add one in case the account has no mail associated, or to delete the existing one in case the user prefer not to have any email associated to the account.

Closing comment (2019-11-13T20:21:14Z): Duplicate of #2499.
Repository: containers/buildah

Issue #953: Shell test failed in conformance testing
Created: 2018-08-22T17:50:23Z
During conformance testing it was discovered:
That the shell test failed.
buildah bud t buildahimage .
buildah inspect buildah-image
Dockerfile contents

FROM centos:7

SHELL ["/bin/bash", "-xc"]

RUN env


Per Yiqiao Pu
[1] https://github.com/ypu/buildah/tree/conformance
Buildah v1.4

Duplicate issue #951: buildah inspect Shell and ArgsEscaped are not filled in 
Created: 2018-08-22T17:28:18Z
During conformance testing it was discovered:
That buildah inspect does not show any values in the ArgsEscaped or Shell variables when they are filled in for Docker images.
Per Yiqiao Pu
[1] https://github.com/ypu/buildah/tree/conformance

Closing comment (2018-08-23T21:32:13Z): Closing as this is a dup of #953
Repository: containers/buildah

Issue #5674: race: parallel builds: copying...committing...creating... layer not known
Created: 2024-08-08T00:25:51Z
This might be the same as containers/podman#23331 . If it is, someone please close this or move.
Setup:
$ for i in 1 2;do printf "FROM quay.io/libpod/testimage:20240123\nRUN echo hi from $i\n" >Containerfile$i;done
In window 1:
$ while :;do buildah build -t c1 --layers=true -f Containerfile1 || break;buildah rmi c1;done
In window 2:
$ while :;do buildah build --layers=false -t c2 -f Containerfile2|| break;buildah rmi c2;done
Within 30-60s, window 1 will barf:
STEP 1/2: FROM quay.io/libpod/testimage:20240123
STEP 2/2: RUN echo hi from 1
Error: checking if cached image exists from a previous build: getting top layer info: layer not known

or
STEP 1/2: FROM quay.io/libpod/testimage:20240123
STEP 2/2: RUN echo hi from 1
hi from 1
COMMIT c1
Error: committing container for step {Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] Command:run Args:[echo hi from 1] Flags:[] Attrs:map[] Message:RUN echo hi from 1 Heredocs:[] Original:RUN echo hi from 1}: copying layers and metadata for container "a8d0253ccd5f337ca69e106657dc645e4926b20d9775621827b6ec118bcb35fa": committing the finished image: creating image "41778f8cf15b69d1fdb79d5bb744ba65eac877e27a21dd12af8700594d88585b": layer not known

The rmi seems important; I can't get it to fail (at least not within my patience tolerance of ~10m) if I omit rmi from either loop.
Testing with podman fails MUCH faster than buildah, for reasons I don't understand, and also fails sometimes in window 2. Buildah only fails in window 1.
This is blocking parallelization of podman test 070-build and I bet this is one of the uncategorized weirdnesses I've seen in #5552 but didn't follow up on.

Duplicate issue #5615: Error: checking if cached image exists from a previous build: getting top layer info: layer not known
Created: 2024-07-02T11:24:57Z
I have four parallel build jobs running. Each using the same base image. It pretty much builds down to podman build -t test-$iteration . followed by a podman rmi test-$iteration.
Sporadically, I get the error mentioned in the title. I did not check the code but it seems that buildah should consider an image to not exist when the top-layer has been removed.
Cc: @nalind @mheon

Closing comment (2024-08-30T01:42:07Z): oops, I only just noticed this. I'm 99% sure this is the same as #5674. You can work around it by adding --layers=false to all the builds commands.
Repository: containrrr/watchtower

Issue #262: Manually triggering Watchtower to check for updates outside of normal interval?
Created: 2019-03-27T17:34:52Z
Hi Guys,
I am trying to figure out if there is a way to trigger watchtower outside of the normal interval I set up.  One of my containers was updated but its actually a flawed update and it isnt working right now.  The image was updated again but it waits about 10 days to recheck.  In the mean time I wanted to see if I could send a command to watchtower to check now instead of waiting another 9 days.
Thanks

Duplicate issue #7: Trigger container restart via WebHook
Created: 2015-12-31T10:23:28Z
Hi, instead of checking for the changes every N seconds, it would be nice to trigger container's restart once new image has been pushed successfully to the docker hub etc. Any ideas how to implement this?

Closing comment (2019-04-02T16:26:59Z): This issue is very closely related to #262 and will as a result be closed.
Repository: containrrr/watchtower

Issue #1837: latest tag missing other arch except amd64
Created: 2023-11-11T17:47:45Z
Describe the bug
the latest tag on docker hub is amd64 only. this breaks all the arm servers.
Steps to reproduce
try to run watchtower on arm server
Expected behavior
it should run.
Screenshots
No response
Environment

Platform ubuntu
Architecture arm
Docker Version

Your logs
docker compose up
[+] Running 2/1
 ✔ Container watchtower-watchtower-1                                                                                                                         Created      1.0s
 ! watchtower The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested              0.0s
Attaching to watchtower-watchtower-1
watchtower-watchtower-1  | exec /watchtower: exec format error
watchtower-watchtower-1 exited with code 0

Additional context
No response

Duplicate issue #1838: Raspberry pi 4 not supported?
Created: 2023-11-11T19:28:49Z
Describe the bug
Error docker execution
 ! watchtower The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s 

docker-compose
version: "3"
services:
  watchtower:
    image: containrrr/watchtower:latest
    restart: unless-stopped
    #command: 
    environment:
      - TZ=America/Argentina/Cordoba
      - PUID=1000
      - PGID=1000
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_INCLUDE_RESTARTING=true
      - WATCHTOWER_POLL_INTERVAL=86400
      - WATCHTOWER_NOTIFICATION_URL=pushover://shoutrrr:xxxxx@xxxx/?devices=[xxxx,xxx]&title=Actualizo+docker+image&priority=1
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock


Steps to reproduce
docker compose up -d
Expected behavior
Working watchtower
Screenshots
No response
Environment

Raspberry pi 4
Linux raspberrypi 6.1.0-rpi4-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (2023-10-05) aarch64 GNU/Linux
Static hostname: raspberrypi
Icon name: computer
Machine ID: xxx
Boot ID: xxxx
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-rpi4-rpi-v8
Architecture: arm64

Your logs
exec /watchtower: exec format error
exec /watchtower: exec format error

Additional context
No response

Closing comment (2023-11-11T20:23:49Z): Duplicate of #1837.
This is fixed as of release v1.7.1. You may need to do a manual docker pull containrrr/watchtower.
Repository: containrrr/watchtower

Issue #939: API changes for selecting whether to use HTTP API triggers, scheduled triggers, or both
Created: 2021-04-26T18:08:32Z
Just a thought, wouldn't manually specifying a schedule or interval warrant the enabling of the periodic updates as well?
It would be breaking behaviour, but it seems like a more obvious way to inerpret the command line/environment args.
It should probably also write a startup message when running in "manual" mode, with schedMessage being something like:
Waiting for manual dispatch, but that is probably outside the scope of this PR...

Originally posted by @piksel in #916 (comment)

Duplicate issue #952: Fail to update watchtower when http api is running
Created: 2021-05-04T06:57:42Z
Describe the bug
Watchtower does not seem to be able to create a new instance of watchtower because http api port is allready used by current watchtower instance.
time="2021-05-04T06:41:49Z" level=debug msg="Renaming container /watchtower (7466244452a6) to bVxoHrZQQfmJwmVPzqUzmrEWtaigXveU"                                                                                                                              │
│   time="2021-05-04T06:41:49Z" level=info msg="Creating /watchtower"                                                                                                                                                                                            │
│   time="2021-05-04T06:41:51Z" level=debug msg="Starting container /watchtower (f2211634e4c3)"                                                                                                                                                                  │
│   time="2021-05-04T06:41:52Z" level=error msg="Error response from daemon: driver failed programming external connectivity on endpoint watchtower (0c44b36fce32cb7f8b15a6ae631577478607525311c1dcd03adebe017933944e): Bind for 0.0.0.0:8080 failed: port is    │
│   already allocated" 


To Reproduce
Enable http api:
-p 8080:8080 -e WATCHTOWER_HTTP_API_UPDATE=true -e WATCHTOWER_HTTP_API_TOKEN=Token

Closing comment (2021-06-11T18:01:36Z): Highly related to #939
I added an endpoint that just closed down the API (given the right token of course) and that just halted the container (since the only thing blocking it is the http server).
Update: And even more confusing, if the http.ErrorServerClosed error is ignored (which it should be), it starts the scheduler upon closing the web API.
Repository: containrrr/watchtower

Issue #43: docker swarm service update
Created: 2017-01-16T16:13:32Z
Is it possible to trigger an update to a docker swarm service ?

Duplicate issue #94: Please support swarm and services
Created: 2017-07-18T06:38:53Z
Monitoring docker services in a swarm cluster would be super useful!

Closing comment (2017-12-12T18:39:06Z): Duplicates #43
Repository: containrrr/watchtower

Issue #1441: `no-restart` doesn't recreate containers after updating
Created: 2022-10-19T08:40:58Z
The way no-restart works currently doesn't make any sense and does not align with the docs.
I think this is a feature that has been broken by refactoring some time ago.
Currently the StartContainer call is the one that creates the new container:

  
    
      watchtower/pkg/container/client.go
    
    
         Line 227
      in
      398d271
    
  
  
    

        
          
           createdContainer, err := client.api.ContainerCreate(bg, config, hostConfig, simpleNetworkConfig, nil, name) 
        
    
  


, and then starts it:

  
    
      watchtower/pkg/container/client.go
    
    
         Line 255
      in
      398d271
    
  
  
    

        
          
           return createdContainerID, client.doStartContainer(bg, c, createdContainer) 
        
    
  


It is entirely skipped if NoRestart is given:

  
    
      watchtower/internal/actions/update.go
    
    
        Lines 226 to 233
      in
      398d271
    
  
  
    

        
          
           if !params.NoRestart { 
        

        
          
           	if newContainerID, err := client.StartContainer(container); err != nil { 
        

        
          
           		log.Error(err) 
        

        
          
           		return err 
        

        
          
           	} else if container.ToRestart() && params.LifecycleHooks { 
        

        
          
           		lifecycle.ExecutePostUpdateCommand(client, newContainerID) 
        

        
          
           	} 
        

        
          
           } 
        
    
  


This means that the option currently only removes containers which I cannot image is what anyone wants.

Discussed in #1440

Originally posted by milindpatel63 October 18, 2022
From the description of the argument here, https://containrrr.dev/watchtower/arguments/#without_restarting_containers
It states that the "no restart" option doesn't restart the containers after updating.
But it also doesn't recreate them.
This should be made clear in the docs.
I use systemd to just "start" and "stop" the containers. But i expected watchtower with "WATCHTOWER_NO_RESTART=true" to just recreate the containers after updating and leave them stopped.
Kindly update the docs

Duplicate issue #1552: Regression makes `--no-restart` only remove container and then bail
Created: 2023-02-06T13:02:12Z
Yeah, the way it works now doesn't make any sense. I think this is a feature that has been broken by refactoring some time ago.

Currently the StartContainer call is the one that creates the new container, and then starts it.
This means that the no-restart option currently only removes containers which I cannot image is what anyone wants.
Originally posted by @piksel in #1440 (comment)

Closing comment (2023-02-06T13:16:23Z): duplicate of #1441. closing
Repository: contentlayerdev/contentlayer

Issue #337: Request support for naming files in other languages
Created: 2022-11-25T04:01:50Z
https://github.com/contentlayerdev/contentlayer/blob/main/packages/%40contentlayer/core/src/generation/generate-dotpkg.ts#L389
你好.mdx
&&.mdx

Perhaps it would be useful to use something like the functionality in the transliteration package to support files named in other languages?
I might know why other languages are not supported here, could a config item (fileNmaeTransfrom:(name:string)=>string|Promise<string>) be provided in contentlayer.config.ts to allow the user to handle this?
https://www.npmjs.com/package/transliteration
https://discord.com/channels/872106850928164874/872106850928164878/1045543968110301195

Duplicate issue #375: Document Collection Manifest Generator generates duplicate import names for Korean file names
Created: 2023-02-09T12:44:56Z
It seems that there is a problem with the Document Collection Manifest generator. When using a file name in Korean, the generator is unable to create an appropriate import name, so it creates an import name based on the first alphabet of the extension. This causes an issue by creating a duplication of the import name.
// NOTE This file is auto-generated by Contentlayer
import test23Md from './test23.md.json' assert { type: 'json' }
import mdx from './개발자 키리 - 대한민국 최애 개발자.mdx.json' assert { type: 'json' }
import mdx from './테스트용마크다운.mdx.json' assert { type: 'json' }
import 2____mMdx from './한글2____m.mdx.json' assert { type: 'json' }

export const allPosts = [helloWorldMd, test23Md, mdx, mdx, 2____mMdx]
Screen shot
My content directory

Auto generated 'document collection manifest'

Closing comment (2023-02-13T13:26:19Z): Thanks for opening this issue. This looks like a duplicate of #337. If you think it's a separate issue or have other questions, feel free to follow up in the comments.
Repository: contentlayerdev/contentlayer

Issue #575: Support NextJS 14
Created: 2023-10-26T21:03:43Z
npm ERR! code ERESOLVE
--
14:57:32.907 | npm ERR! ERESOLVE could not resolve
14:57:32.908 | npm ERR!
14:57:32.908 | npm ERR! While resolving: next-contentlayer@0.3.4
14:57:32.908 | npm ERR! Found: next@14.0.0
14:57:32.908 | npm ERR! node_modules/next
14:57:32.908 | npm ERR!   next@"^14.0.0" from the root project
14:57:32.908 | npm ERR!
14:57:32.908 | npm ERR! Could not resolve dependency:
14:57:32.908 | npm ERR! peer next@"^12 \|\| ^13" from next-contentlayer@0.3.4
14:57:32.908 | npm ERR! node_modules/next-contentlayer
14:57:32.909 | npm ERR!   next-contentlayer@"^0.3.4" from the root project
14:57:32.909 | npm ERR!
14:57:32.909 | npm ERR! Conflicting peer dependency: next@13.5.6
14:57:32.909 | npm ERR! node_modules/next
14:57:32.909 | npm ERR!   peer next@"^12 \|\| ^13" from next-contentlayer@0.3.4
14:57:32.909 | npm ERR!   node_modules/next-contentlayer
14:57:32.909 | npm ERR!     next-contentlayer@"^0.3.4" from the root project

Duplicate issue #605:  next-contentlayer installation ERROR in next 14.0.3 on terminal
Created: 2023-11-20T15:29:41Z
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: mirsazzathossain.me@0.1.0
npm ERR! Found: next@14.0.3
npm ERR! node_modules/next
npm ERR!   next@"14.0.3" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^12 || ^13" from next-contentlayer@0.3.4
npm ERR! node_modules/next-contentlayer
npm ERR!   next-contentlayer@"^0.3.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\Sahad\AppData\Local\npm-cache_logs\2023-11-23T07_19_34_982Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: C:\Users\Sahad\AppData\Local\npm-cache_logs\2023-11-23T07_19_34_982Z-debug-0.log

This error does not appear when I changed the version to next 13

Closing comment (2023-11-24T23:33:32Z): Duplicate of #575. Resolvable by #576
Repository: contentlayerdev/contentlayer

Issue #149: Support for nested field types in computed fields
Created: 2022-03-16T16:56:35Z
Right now if I have a computed field and I'd like to return a non-primitive value I have to use json as the type. Ideally I'd be able to use a nested field definition to provide stronger typing for computed fields.
Related to #91 in that this would bring computed fields in line with regular fields.

Duplicate issue #419: Can't use nested type in computed fields
Created: 2023-04-11T19:42:16Z
I have a field that will be computed and I want to return a specific object shape with an associated type.
For example:
export const Post = defineDocumentType(() => ({
  name: "Post",
  images: {
    type: "list",
    of: { type: "string" },
  },
  computedFields: {
    processedImages: {
      type: "list",
      of: {
        type: "nested",
        of: Image, // referencing a defined nested type
      },
    },
  },
}));
I'm currently working around this by transforming the images and writing my own types in the project code. These types inherit from Contentlayer types.

Closing comment (2023-04-24T14:36:52Z): Duplicate of #149