primordic/IssueDupesLite huggingface dataset:
Repository: davidhalter/jedi

Issue #253: Can Jedi provide location-based context information?
Created: 2013-06-25T21:52:58Z
Hi,
I'd like to write a Vim plugin that can take a position in a source file, and returns its context.
For example, it will take (32, 47, 'foo.py'), and line column 47 in line 32 of foo.py is inside the method "bar()"of class "Qux", return something like "Qux.bar()".
What support does Jedi offer for that kind of functionality?

Duplicate issue #254: Can Jedi provide location-based context information?
Created: 2013-06-25T22:41:32Z
Hi,
I'd like to write a Vim plugin that can take a position in a source file, and returns its context.
For example, it will take (32, 47, 'foo.py'), and line column 47 in line 32 of foo.py is inside the method "bar()"of class "Qux", return something like "Qux.bar()".
What support does Jedi offer for that kind of functionality?

Closing comment (2013-06-25T22:42:37Z): Sorry, duplicate of #253.
Repository: davidjerleke/embla-carousel

Issue #202: [Feat]: SSR support
Created: 2021-06-15T14:28:38Z
NoteEdit: This feature is under development:

#1095

Edited by @davidjerleke 2024-12-26.


Bug is related to

 The Embla Carousel core (all versions)

Embla Carousel version

v4.5.3

Describe the bug

When carousel is being rendered via SSR there's noticeable flickering effect on first slide on each page refresh (regardless of cache).

CodeSandbox

https://codesandbox.io/s/suspicious-burnell-mfs1q

Steps to reproduce

Go to https://mfs1q.sse.codesandbox.io/
Refresh the page and look at carousel.

Expected behavior

It shouldn't flicker when SSR is used.

Additional context

Duplicate issue #689: [Bug]: Init event not fired in SSR (React / NextJS)
Created: 2024-01-12T10:19:21Z
Bug is related to

 embla-carousel-react

Embla Carousel version

v8.0.0-rc19

Describe the bug
The .on("init") event is not invoked when used in a useEffect in a SSR component.
CodeSandbox
https://stackblitz.com/edit/stackblitz-starters-syez5k?file=app%2FEmblaComponent.tsx
https://stackblitzstarterssyez5k-c0ir--3000--f7aa08df.local-credentialless.webcontainer.io/
const [emblaRef, emblaApi] = useEmblaCarousel();

useEffect(() => {
  if (!emblaApi) return;

  emblaApi.on('init', () => {
    console.log('init');
  });
}, [emblaApi]);

Steps to reproduce

Open the Stackblitz webcontainer
Open the console
There is no 'init' log

The log is shown after a hot reload. If you see the init log, do a hard refresh.
Expected behavior
The init event should always fire.

Closing comment (2024-01-16T12:52:10Z): @StevenVerbiest thanks. Although Embla doesn't run its script on the server, it still allows rendering the HTML and CSS on the server side.

Duplicate of #202.
Repository: davidjerleke/embla-carousel

Issue #42: Create an option to block excessive scrolling
Created: 2020-01-05T19:32:33Z
Hi @davidjerleke!
Embla currently has ways to remove the leading and trailing blanks from the Slider (containsScroll: true), but still allow for excessive scrolling. It would be interesting to add an option to block this scroll and stop it when it reaches the end or beginning of the Slider. I would like to know what you think of this idea
Below is the example of the "excessive scroll" I am referring to

Duplicate issue #163: Feature request: more scroll physics
Created: 2021-03-31T07:43:05Z
Feature request is related to

 The Embla Carousel core (all versions)

Is your feature request related to an issue?
I'm curious whether embla-carousel has an option like ClampingScrollPhysics. It seems all examples have bouncing scroll physics at both ends of the contents.
Describe the solution you'd like
Add terminalPhysics enum option that can be 'clamp', 'bounce', etc.
Describe alternatives you've considered
I have no better idea about api.

Closing comment (2021-03-31T11:33:02Z): Duplicate of #42.
Repository: davidjerleke/embla-carousel

Issue #39: [Feat]: Add a fade plugin
Created: 2019-12-23T23:29:30Z
Love the carousel and was able to get it working right away. The one thing that I need that it doesn't provide is a way to have a scroll option for single/multiple slides and a fade option to handle next/previous transition when it's just showing a single slide at a time.
Is that something that has been requested before?

Duplicate issue #112: Fade Slider?
Created: 2020-10-22T01:26:27Z
Can you add Fade Effect in embla-carousel ?

Closing comment (2020-10-24T09:01:33Z): Duplicate of #39.
Repository: davidjerleke/embla-carousel

Issue #124: [Feat]: Repeat items if necessary to achieve infinite scroll
Created: 2020-11-21T10:38:39Z
Hello everybody
Based on #114 I could implement a continuously running slider. When the slider is too wide or there are not enough items, to fill the whole width the slider becomes buggy.
I've created a Sandbox here. Here is a little clip about, which shows the problem:

If I fill the whole visible width with items it works fine. Would it be easy to implement a feature within embla, which at least fills the visible width? .. because even if it isn't buggy, I want to fill the whole width for a nice appearance.
Thank you in advance!

Duplicate issue #1000: [Bug]: {loop:true} option does not work when there're only two slides
Created: 2024-09-12T09:54:47Z
Which variants of Embla Carousel are you using?

 embla-carousel (Core)
 embla-carousel-react
 embla-carousel-vue
 embla-carousel-svelte
 embla-carousel-autoplay
 embla-carousel-auto-scroll
 embla-carousel-solid
 embla-carousel-auto-height
 embla-carousel-class-names
 embla-carousel-fade
 embla-carousel-docs (Documentation)
 embla-carousel-docs (Generator)

Steps to reproduce
{loop:true} option does not work when there only two slides
3 slides looks good
Expected Behavior
It can be switched in a loop
Additional Context
I have also tried...
What browsers are you seeing the problem on?
No response
Version
No response
CodeSandbox
https://codesandbox.io/p/sandbox/embla-carousel-loop-react-forked-j9jwym
Before submitting

 I've made research efforts and searched the documentation
 I've searched for existing issues
 I agree to follow this project's Contributing Guidelines for bug reports

Closing comment (2024-09-12T10:19:28Z): @Kimi-Gao a friendly reminder: Please make research efforts before creating bug reports about behavior that's by design, because it's tedious answering the same questions over and over again.
This is what the docs say about the loop option:

Embla automatically falls back to false if slide content isn't enough to create the loop effect without visible glitches.


Duplicate of: #124 (comment)
Repository: davidjerleke/embla-carousel

Issue #53: Optional keyboard left/right arrow key navigation
Created: 2020-03-25T20:53:23Z
It would be great to be able to use the left/right arrow keys to navigate slides by default when the carousel is in focus.

Duplicate issue #278: Unable to access and move through carousels with the keyboard.
Created: 2022-02-04T00:54:31Z
Feature request is related to

 embla-carousel (core package)
 embla-carousel-react
 embla-carousel-autoplay
 embla-carousel-auto-height
 embla-carousel-class-names
 embla-carousel-docs (documentation website)

Is your feature request related to an issue?
I'm unable to focus on or navigate the carousel with my keyboard.
Describe the solution you'd like
For accessibility reasons, I would expect interactive elements to be interactive with a keyboard as well as a mouse.
Describe alternatives you've considered
There really isn't an alternative to this, aside from not supporting it at all.
Additional context
n.a.

Closing comment (2022-02-05T21:10:50Z): Duplicate of #53.
Repository: davidjerleke/embla-carousel

Issue #114: [Feat]: Continuously running carousel (ticker, marquee, ..)
Created: 2020-10-31T16:53:55Z
Hello everybody
I'm using Embla already in a project and it's great. Thank you for the amazing work!
Now I have the use case to build a carousel which runs continuously like a "stock market" ticker. So no speed up and slow down. Do you think it's easy to build something like that with Embla? Where would be a good starting point?

Duplicate issue #105: Automatic and slow scroll with dragFree
Created: 2020-09-18T10:14:18Z
I was wondering if there is a way to slowly auto scroll the content of a carousel with the dragFree option? In order to sort of show to users that there is more content in a nice way.
Kind of something like that, but automatically:

Closing comment (2024-01-25T20:47:54Z): Duplicate of #114.

@raymondarevalo no need to look for temporary CodeSandbox solutions anymore. A plugin for this is finished and will be released very soon. Stay tuned.
Here’s the PR for it:

#634
Repository: davidjerleke/embla-carousel

Issue #647: Can't import `EmblaCaroouselType`, `EmblaOptionsType`, `EmblaPluginType` from `embla-carousel-react`, `embla-carousel-vue` and `embla-carousel-svelte`
Created: 2023-12-07T09:33:22Z
Bug is related to

 embla-carousel-react
 embla-carousel-vue
 embla-carousel-svelte
 embla-carousel-solid

Embla Carousel version

v8.0.0-rc15

Describe the bug
Since version v8.0.0-rc15,  ESLint says that the SliderPropsOptions type does not have a loop property. This happens to all properties that are in EmblaOptionsType:

Also because of this, useEmblaCarousel has the options argument type Partial<OptionsType> | undefined instead of EmblaOptionsType | undefined, which causes a linter error:

Duplicate issue #668: ESM d.ts point to non-existent .ts files
Created: 2023-12-29T20:53:22Z
Bug is related to

 embla-carousel-react


  
    
      embla-carousel/rollup.config.js
    
    
        Lines 125 to 127
      in
      b3b8554
    
  
  
    

        
          
           const esmTypesFileWithExtensions = esmTypesFile.replace( 
        

        
          
             /from\s'(.*)';/g, 
        

        
          
             (match) => match.replace(/';/g, `.ts';`) 
        
    
  


Embla Carousel version

v8.0.0-rc15 - rc18

Describe the bug
Incorrect ESM:
export { EmblaOptionsType } from 'embla-carousel/components/Options.ts';
export { EmblaEventType, EmblaEventListType } from 'embla-carousel/components/EventHandler.ts';
export { EmblaPluginType } from 'embla-carousel/components/Plugins.ts';
export { EmblaCarouselType } from 'embla-carousel/components/EmblaCarousel.ts';
export { UseEmblaCarouselType } from './components/useEmblaCarousel.ts';
export { default } from './components/useEmblaCarousel.ts';

Expected behavior
export { EmblaOptionsType } from 'embla-carousel/components/Options';
export { EmblaEventType, EmblaEventListType } from 'embla-carousel/components/EventHandler';
export { EmblaPluginType } from 'embla-carousel/components/Plugins';
export { EmblaCarouselType } from 'embla-carousel/components/EmblaCarousel';
export { UseEmblaCarouselType } from './components/useEmblaCarousel';
export { default } from './components/useEmblaCarousel';
Additional context

Add any other context about the problem here, like screenshots or similar.

Closing comment (2023-12-30T06:43:55Z): @NikitaIT did you search issues before creating this bug report?


Please read this comment from the following issue #647.


Duplicate of #647.
Repository: davidjerleke/embla-carousel

Issue #38: The Slider is skipping other items
Created: 2019-12-13T07:26:38Z
Hello, when users swipe hard enough it looks like its skipping other slides, how can we limit it to only one slide per swipe? slidesToScroll: 1 doesn't seem to do anything
const wrap = document.querySelector('.js-home-slider');
  const viewPort = wrap.querySelector('.js-home-slider-viewport');
  const dots = wrap.querySelector('.js-home-slider-dots');
  const homesliderStart = EmblaCarousel(viewPort, {
    loop: true,
    draggable: true,
    dragFree: false,
    speed: 10,
    startIndex: 0,
    slidesToScroll: 1,
  });

Duplicate issue #107: How to turn off momentum scrolling and have any swipe go to next or previous slide? 
Created: 2020-09-28T15:20:00Z
Is it possible to fix/lock any swipe to go to the next slide in the carousel as opposed to triggering momentum scrolling on quick swipes?

Closing comment (2020-09-29T05:50:54Z): Duplicate of #38.
Repository: davidjerleke/embla-carousel

Issue #42: Create an option to block excessive scrolling
Created: 2020-01-05T19:32:33Z
Hi @davidjerleke!
Embla currently has ways to remove the leading and trailing blanks from the Slider (containsScroll: true), but still allow for excessive scrolling. It would be interesting to add an option to block this scroll and stop it when it reaches the end or beginning of the Slider. I would like to know what you think of this idea
Below is the example of the "excessive scroll" I am referring to

Duplicate issue #517: Option to Disable Rubber Band Effect when Loop is set to False
Created: 2023-07-06T20:44:54Z
Feature request is related to

 embla-carousel (core package) 6.2.0

Is your feature request related to an issue?
#42
Describe the solution you'd like
i'd like an option or workaround to disable rubber-banding on the first / last item when loop is False
i use embla nested within ANOTHER swiper element, and when the user swipes right on the first image,
i'd like the outer container to pick up the pan gesture, and animate the outer container
currently: i see the inner slideshow moving AND the outer container moving simultaneously, which just isn't what my client desires.
Describe alternatives you've considered


disabling 1:1 swipe-based page naviation effect in favor of an Arrow overlay element coming into view
still has issue of nested gesture recognition (bad visual affordance to user that there's more media to view, rather than that they've reached a hard Stop edge and will begin controlling the OUTER container)


disable visual feedback and just respond to swipe (bad ux)


disable swipe gesture stick to alternative arrow button navigation (would love to keep swiper like "native app" feeling)


Additional context
you can see the nested swiper effect / issue if you visit this page on mobile:
https://www.wright20.com/auctions/2023/07/2021-art/100

Closing comment (2023-07-07T04:28:04Z): Duplicate of:

#42
Repository: davidjerleke/embla-carousel

Issue #39: [Feat]: Add a fade plugin
Created: 2019-12-23T23:29:30Z
Love the carousel and was able to get it working right away. The one thing that I need that it doesn't provide is a way to have a scroll option for single/multiple slides and a fade option to handle next/previous transition when it's just showing a single slide at a time.
Is that something that has been requested before?

Duplicate issue #250: Is there any way to change slide animation?
Created: 2021-12-05T08:14:42Z
Hi there, Embla carousel is super carousel. I am finding any way to change slide animation. Because in my last project, my buyer tell me to change slide animation. In my project I use two carousel. I have set Fade animation in one carousel. And other carousel should animated to smooth slide like keen slider. But I am using embla carousel.
is there any way or have to this features?

Closing comment (2021-12-05T13:03:53Z): Duplicate of #39.
Repository: ddev/ddev

Issue #741: TYPO3: Create typo3conf/AdditionalConfiguration.php even if typo3conf doesn't exist
Created: 2018-03-16T18:27:59Z
What happened (or feature request):
Followup from #693 (comment):
Generate AdditionalConfiguration.php and parent folder (if they don't exist) and warn if LocalConfiguration.php doesn't exist
What you expected to happen:
How to reproduce this:
Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.
Anything else do we need to know:
Related source links or issues:
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

Duplicate issue #931: Create non-existing folder typo3conf before writing AdditionalConfiguration.php in TYPO3
Created: 2018-06-18T08:22:52Z
Is your feature request related to a problem? Please describe.
When you start a TYPO3 project and run ddev start on a fresh TYPO3 composer installation the file generation of AdditionalConfiguration.php with the DB credentials fails due to the non-existing folder typo3conf.
Describe the solution you'd like
If there is no folder typo3conf, create it before writing AdditionalConfiguration.php.
Then you can start a TYPO3 project with only three commands: composer require typo3/minimal, ddev config and ddev start. Without the folder you need to start the Install process (which creates the folder) and run ddev config again to write the file.
Describe alternatives you've considered
There are no alternatives. ;)

Closing comment (2018-06-18T13:25:55Z): This is already done and will be in the next release, this is a duplicate of #741
We'd love to have you try out the current master version of ddev at https://circleci.com/gh/drud/ddev/2973#artifacts/containers/0
Closing as duplicate of #741, let me know if I haven't understood.
Repository: ddev/ddev

Issue #5239: umask 0027 prevents healthcheck in ddev-router
Created: 2023-08-05T06:03:27Z
Is there an existing issue for this?

 I have searched the existing issues

Output of ddev debug test
No response
Expected Behavior
DDev should run with umaks 0027 set in user's ~/.bashrc
Actual Behavior
In ddev-router the file /healthcheck.sh is not readable for others and the health check fails.
Steps To Reproduce

On Ubuntu 22.04 set umask 0027 in user's ~/.bashrc
Install docker
Install ddev
Create dummy ddev project
Start project => error: ddev-router failed to become ready: health check timed out
Connect to the ddev-router instance e.g. 'docker exec -it --user root ddev-router bash' to check the file permissions of /healthcheck.sh

Anything else?
Looks like Failed to start ddev router #1237 but has different cause.
May be a similar issue as web_extra_daemons start fails with error "ERROR (no such group)" #4872

Duplicate issue #5243: ddev-router healthcheck.sh  permission denied
Created: 2023-08-07T11:23:49Z
Is there an existing issue for this?

 I have searched the existing issues

Output of ddev debug test
Running ddev start I see below error:
Failed to start ahi: ddev-router failed to become ready; debug with 'docker logs ddev-router' and 'docker inspect --format "{{json .State.Health }}" ddev-router'; logOutput=, err=health check timed out after 1m0s: labels map[com.docker.compose.service:ddev-router] timed out without becoming healthy, status=
But still the web app is accessible in browser and working fine.
To debug I ran docker inspect --format "{{json .State.Health }}" ddev-router and I got the below output:
{"Status":"unhealthy","FailingStreak":757,"Log":[{"Start":"2023-08-07T11:20:47.937625831Z","End":"2023-08-07T11:20:48.076172289Z","ExitCode":126,"Output":"/bin/bash: /healthcheck.sh: Permission denied\n"},{"Start":"2023-08-07T11:20:49.087961165Z","End":"2023-08-07T11:20:49.258456123Z","ExitCode":126,"Output":"/bin/bash: /healthcheck.sh: Permission denied\n"},{"Start":"2023-08-07T11:20:50.271309582Z","End":"2023-08-07T11:20:50.407708957Z","ExitCode":126,"Output":"/bin/bash: /healthcheck.sh: Permission denied\n"},{"Start":"2023-08-07T11:20:51.418983124Z","End":"2023-08-07T11:20:51.563713416Z","ExitCode":126,"Output":"/bin/bash: /healthcheck.sh: Permission denied\n"},{"Start":"2023-08-07T11:20:52.574944875Z","End":"2023-08-07T11:20:52.654258958Z","ExitCode":126,"Output":"/bin/bash: /healthcheck.sh: Permission denied\n"}]}
Expected Behavior
ddev-router container should be healthy
Actual Behavior
ddev-router container should be unhealthy
Steps To Reproduce
No response
Anything else?
No response

Closing comment (2023-08-07T12:50:58Z): When asking for help, please provide the requested output from ddev debug test - it helps understand so much.
I imagine it's a duplicate of

#5239
Repository: ddev/ddev

Issue #376: "ddev describe" should report information about the routed and unrouted web ports
Created: 2017-07-05T21:10:44Z
What happened (or feature request):
Our users may well want to know about the exposed ports (especially http) on their localhost, as it makes many things possible, as in #375 where ngrok is suggested. This is easily accessible in docker ps, but would be better coming from ddev.
We should report in ddev describe:

The actual correct port the router is providing
The unrouted ports exposed by the web container.

What you expected to happen:
Version: Please include the output of ddev version and the project's .ddev/config.yaml.
How to reproduce this:
Anything else do we need to know:
Related source links or issues:

Duplicate issue #342: Add a URL field to config, make the router optional
Created: 2017-06-20T16:04:39Z
What happened (or feature request):
Feature request, touching on a few related concerns. #321 is the motivation for this request.
Currently, all ddev sites get a url at .ddev.local. We provide a way to run on a port alternate from 80, but it is not very intuitive. We also assume that users will want a domain like the one we provide, while there are valid use cases for throwing a site on localhost at an available port.
What you expected to happen:
I think we should introduce a URL field to the config.yaml to be used to address these concerns. The field would allow users to define the URL the site is served from in the following ways, achieving the following result for each way:

Set to "localhost". The router is not used for the site, and instead we output the published port of the web container as the site URL. e.g. after ddev start: "Your application can be reached at http://localhost:4379
Set to "localhost:8089". The router is not used for the site, and port 8089 is used to expose the site, provided it is available.
Set to "[sitename].ddev.local:8089". The router is used for the site, port 8089 is used to expose the site, provided it is available. e.g. after ddev start: "Your application can be reached at http://[sitename].ddev.local:8089"
At this point we may as well allow the URL to be defined how the user wants, unless there's a reason not to that I'm not seeing. e.g. user can have there site at http://sitename.banana.dev or whatever.

This would entail changes to the prompts in "ddev config" to add a URL prompt, and list the possible options for the user. I think we should still provide [sitename].ddev.local as the default value.
I suspect this approach would also entail changing configurations in the docker-compose.yml. We will need to come to a decision on if we are going to control / maintain this file, or allow users to configure it.
How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
Related source links or issues:
#321
#323

Closing comment (2017-07-07T00:07:04Z): Related and possibly sort-of-duplicate: #376: "ddev describe" should report information about the routed and unrouted web ports
Repository: ddev/ddev

Issue #1099: Provide Application Links via ddev config
Created: 2018-09-11T09:32:12Z
During development, my ddev setup might bring in additional applications like a SOLR Management Interface, Redis UI or Elasticsearch UIs.
As a developer, I want to be able to provide application links based on configuration in config.yaml.
In my concrete application (and maybe even in DDEV UI) I want to be able to access those links easily (on PHP level maybe as env variables or alike.
Placeholders for the project's URL might come in handy as well.
Idea of config.yaml
APIVersion: v1.1.1
name: awesome-project
type: typo3
docroot: public
php_version: "7.2"
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
provider: default
applicationLinks:
  "Bitbucket Repo": https://bitbucket.typo3.com/repo/browse/awesome-repo
  "Mailhog": {projectUrl}:1025
  "PHPMyAdmin: {projectUrl}:8036
  "Elasticsearch HEAD": {projectUrl}:9200/_plugins/HEAD

Duplicate issue #1098: Provide links to mailhog and phpMyAdmin as PHP env variable
Created: 2018-09-11T09:12:23Z
As a user I want to be able to see the links to both mailhog and phpMyAdmin in my CMS.
In order to provide those links, I need to be able to access them in any given way, the easiest would be env variables.
That way we can add a dedicated tab into TYPO3s admin panel allowing for quick access to the services without the necessity to remember ports.

Closing comment (2018-09-20T23:09:21Z): Is this the  same as #1099? Should we close one of them?
Repository: ddev/ddev

Issue #2129: Add `--skip-hooks` flag for ddev start, restart, etc.
Created: 2020-03-27T15:01:49Z
Is your feature request related to a problem? Please describe.
My goal is to always have my commands executed under DDEV. So for example I don't want to run composer install, but instead ddev composer install. To do so I need my project to be started.
However, I often have my config.local.yaml defined with post-start hook that will drush site-install. So what happens is, on first install, it will start the container, try to install (and fail because composer didn't run yet), and then it will  composer install.
I was able to workaround it, with some trickery. Specifically:
ddev composer install
cp .ddev/config.local.yaml.example .ddev/config.local.yaml
ddev restart

Describe the solution you'd like
Instead of this late copy, or having to delete the config.local.yaml, it could be convenient to do something like:
ddev start  --skip-config-hooks
ddev composer install

# Restart, to run the post-start hooks.
ddev restart

Duplicate issue #6185: flag to skip post-import-db-* hooks when using import-db
Created: 2024-05-15T14:53:29Z
A colleague asked me about this and I was surprised to not find a native way of doing it.
I wonder if this is something logical to add?

Closing comment (2024-05-15T16:09:37Z): This would be a duplicate of

#2129
true?
Repository: ddev/ddev

Issue #6149: Support config.*.yaml in `ddev config` command
Created: 2024-05-03T11:58:59Z
Is there an existing issue for this?

 I have searched the existing issues

Is your feature request related to a problem?
Would it be possible to support the other config.*.yaml files when using ddev config?
I.e. when I want to disable settings management
ddev config --disable-settings-management
it changes the default config.yaml, but actually I want to change config.local.yaml.
Is there actually a way to do this via cli?
Describe your solution
t.b.d
Describe alternatives
No response
Additional context
No response

Duplicate issue #7060: Cause ddev config commands to respect project name specified in config.local.yaml
Created: 2025-03-09T18:04:47Z
Is there an existing issue for this?

 I have searched the existing issues

Is your feature request related to a problem?
For my projects, the config.yaml file is checked into the repo.  I often have multiple copies of the site and have a config.local.yaml where I override the name.  Some ddev commands get confused and operate on the name specified in the config.yaml rather than the name specified in the config.local.yaml.  I recently learned that one option is to remove the name line from the checked in config.yaml which causes ddev to default to using the directory name as the project name.  While this is an excellent option, perhaps it would be better to make ddev respect the new name.
Describe your solution
Update ddev commands to use the name specified in the config.local.yaml file rather than to use the name specified in the config.yaml
Describe alternatives
No response
Additional context
No response

Closing comment (2025-03-09T20:07:00Z): ddev config will update config.yaml only.
I think this is a duplicate of

#6149

true?
Repository: ddev/ddev

Issue #2046: Docker Desktop 2.2.0.0 on Windows: No consistency in file mounts
Created: 2020-01-22T13:08:41Z
Describe the bug
Installing a e.g. a TYPO3 project via composer with a composer.json file with "ddev composer install".
After changing the composer.json file and doing "ddev composer update" nothing will be changed (I think the file is cached because of new Docker file caching).
To Reproduce
Steps to reproduce the behavior:

Install a composer project with "ddev composer install" on Windows with Docker Desktop 2.2
Change the composer.json file
Do a "ddev composer update"
Nothing will be changed by composer and the changed in composer.json will be ignored

Expected behavior
The changes in composer.json file should be used and e.g. new packages installed or updated.
Version and configuration information (please complete the following information):

Host computer OS and Version: Windows 10 (newest release)
Docker version information: Docker Desktop 2.2 with Docker 19.03.5
ddev version information: 1.12.1

Duplicate issue #2045: Symlinks broken on Windows and Docker Desktop 2.2.0.0
Created: 2020-01-22T11:30:24Z
After ugrading Docker from 2.1.0.5 to 2.2.0.0 symlinks created by
ddev composer install do not work anymore neigher do thoose directly created from inside the container by e.g. composer install  (haven't tried more use cases)
They look good from the host but from the container they are not accessable -> "input/output error".
I guess this might be cause by the "new filesharing implementation" that has been introduced in 2.2.0.0
Downgrading back to 2.1.0.5. Fixes this issue.

Closing comment (2020-01-22T17:10:50Z): I'm going to close this as a duplicate of #2046 - Since ddev can't find symlinks that have been created in the container, it can't update them. And that's because they don't ever get presented to the host.
The very simple and very effective alternative is to use nfs_mount_enabled in ddev so then you're not using the new Fuse filesystem.
Repository: dependabot/dependabot-core

Issue #1778: Add support for multiple update_schedules / update_type combos for a single ecosystem / directory
Created: 2020-04-05T16:35:09Z
Hey, I'd love to be able to trigger and receive PRs for security updates on a live schedule.
and my regular scheduled all updates weekly.
The following is a mock for my config.yml -- obviously fails the validator as a dupe atm :)
version: 1

update_configs:
  - package_manager: "ruby:bundler"
    directory: "/"
    update_schedule: "weekly"
    version_requirement_updates: auto
    allowed_updates:
      - match:
          update_type: "all"

  - package_manager: "javascript"
    directory: "/"
    update_schedule: "weekly"
    version_requirement_updates: auto
    allowed_updates:
      - match:
          update_type: "all"


  - package_manager: "ruby:bundler"
    directory: "/"
    update_schedule: "live"
    version_requirement_updates: auto
    allowed_updates:
      - match:
          update_type: "security"

  - package_manager: "javascript"
    directory: "/"
    update_schedule: "live"
    allowed_updates:
      - match:
          update_type: "security"

Duplicate issue #3240: Scheduling for specific dependencies?
Created: 2021-03-05T23:51:24Z
Some dependencies may directly impact the feature of the package and while others not. I want to be notified ASAP when updates happen for those important dependencies while just monthly for others.

Closing comment (2021-05-19T15:31:54Z): Ok, I'm going to close this as a dupe of #1778, which is the feature request underpinning all of these types of requests. It's something we've been thinking through as we've been working on #2219, but we haven't scheduled work on it.
Repository: dependabot/dependabot-core

Issue #4178: Check and update dependencies in GitHub Actions action.yml
Created: 2021-08-30T14:43:01Z
When using composite actions steps are defined in action.yml and we can have dependency to another actions.
Currently dependencies aren't checked in action.yml

Duplicate issue #6656: Dependabot to update composite actions in workflows files from a different repository
Created: 2023-02-13T20:19:51Z
Is there an existing issue for this?

 I have searched the existing issues

Feature description
Hello,
I'd love for Dependabot to update composite actions defined in a separate repository being used in the workflows of another repository with git commit ID's.
I've got a repository with Composite actions with say 3 commits on the repoA

(X, Y) committed specifically to folder/action-1
(Z) commit specifically to folder/action-2

repoA (public)
 - folder/action-1 (Commits: X, Y)
    - action.yml (type: composite)
 - folder/action-2 (Commits: Z)
    - action.yml (type: composite)

I've got a repository with Composite actions with say 2 commits on the repoB

<C1, C2>committed specifically to repo root

repoB (public)
    - action.yml (type: composite)

repoC (private)
  - .github
     - workflows
        - ci.yml
           -- uses: repoA/folder/action-1@X
           -- uses: repoA/folder/action-2@Z
           -- uses: repoB@C1
     - dependabot.yml
          version: 2
          updates:
              - package-ecosystem: "github-actions"
                directory: "/" (`# Update workflow files in this repo and look for composite Actions version updates defined in repoB`)
                schedule:
                  interval: "daily"
              - package-ecosystem: "github-actions"
                directory: "/folder/action-1" (`# Look for Composite action-1 version updates in repoA`)
                schedule:
                  interval: "daily"
              - package-ecosystem: "github-actions"
                directory: "/folder/action-2" (`# Look for Composite action-2 version updates in repoA`)
                schedule:
                  interval: "daily"

Expected:

PR to bump  repoA/folder/action-1@X to  repoA/folder/action-1@Y where Y is the new commit SHA on repoA for action-1
PR to bump  repoB@C1 to  repoB@C2 where C2 is the new commit SHA on repoB for action in root

Existing / Similar Issues found:

I have come across #4178 and wasn't sure if the actual composite action in the calling workflow can be updated VS of the dependencies of the composite actions themselves.
#4327 and not sure if this feature is what is expected. If, so pls relate.

Can someone help me understand if this is supported and what the Dependabot configuration should look like?

Closing comment (2023-02-14T15:19:51Z): I think this is indeed a duplicate of #4178 and will be fixed by #4327. Although it does not have the level of commit granularity you're requesting. If two composite actions live in the same repo, my understanding is that Dependabot will update to the latest commit in the repository, regardless of whether that commit only updates one of the composite actions.
Repository: dependabot/dependabot-core

Issue #6339: `schedule.interval` support  cron expressions
Created: 2022-12-20T02:37:20Z
I would like the ability to schedule dependabot, schedule.interval, on more options other than daily, weekly, and monthly.
For my use case specifically, I am looking for schedule it quarterly and semi-annually.
Rather than adding options quarterly and semi-annual, I believe it would be much better if dependabot were allowed to be scheduled using a cron expression to make it more generic. This would allow users to schedule it all kinds of different ways that better fit the user's needs.

Duplicate issue #7490: `schedule.interval` of `fortnight` (every two weeks)
Created: 2023-06-27T17:35:20Z
Is there an existing issue for this?

 I have searched the existing issues

Feature description
Dependabot version updates reporting weekly results in a noisy pull request queue; monthly reporting results in a potential backlog of version updates. It seems to me that for medium-sized projects, the right frequency would be every two weeks.

Closing comment (2024-12-23T23:20:29Z): Closing as a dupe of #6339 ; let's use #6339 to track
Repository: dependabot/dependabot-core

Issue #3290: Standard Python support
Created: 2021-03-17T12:15:22Z
There’s exactly two standard ways of specifying dependencies, none of which dependabot supports.


PEP 517’s prepare_metadata_for_build_wheel().
The legacy way to specify Python dependencies is requirements.txt. The standard way is having a PEP 517 build system configured. That build system can optionally define a function called prepare_metadata_for_build_wheel. If that function exists, the dependencies can be obtained (from the metadata) without building a wheel, otherwise build_wheel() needs to be called.
Code to just do the above would look like:
import build
deps = build.ProjectBuilder("path/to/project").get_dependencies("sdist")
# or
deps = build.ProjectBuilder("path/to/project").get_dependencies("wheel") - {"wheel"}


PEP 631 a new standardized way to specify dependencies in a Python project (now merged into PEP 621).
It’s supported by flit and a bunch of other new build backends. So if you want to continue your (incomplete) way of just parsing files and not calling into Python, this needs to be supported.

Duplicate issue #4683: Support for pyproject.toml
Created: 2022-01-30T21:30:07Z
This request is to add pyproject.toml support without the use of poetry or any external packages (just pip).
This was partially implemented back in  back in 2018 with #635, which included support for poetry. But pyproject.toml was initially proposed in PEP 518 and later expanded in PEP 517, PEP 621 and PEP 660, which made it is possible to make a package without the use of any setup script or external packages.
Would be really nice to have dependabot detect those dependencies and open pull requests to keep them up to date :)
References:

Documentation for pip on pyproject.toml: https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/
Example of pyproject.toml only package: https://github.com/FasterSpeeding/Tanjun/blob/master/pyproject.toml

Closing comment (2022-03-10T02:37:52Z): I think this is a duplicate of #3290
Repository: dependabot/dependabot-core

Issue #2140: Support for Google Cloud Build's `cloudbuild.yaml`
Created: 2019-06-11T09:03:43Z
Google Cloud Build is a widely used CI/CD pipeline that integrates with Github, is automatically picks up a cloudbuild.yaml file.
One can define build steps:
- steps:

- name: '<IMAGE>'
....

where name will be a docker image, residing on a public and/or private registry.

Duplicate issue #3675: Support for dependencies on CI/CD
Created: 2021-05-08T02:18:06Z
It' be awesome to support CI/CD systems such as, for example, github actions and Google's cloud build.
Both of these make intensive use of repos that developers also want to be able to update.
OpenSSF's scorecard is working on supporting this too.

Closing comment (2022-08-25T02:53:08Z): Closing as a duplicate of #2140 which already tracks Google Cloud Build.
Repository: dependabot/dependabot-core

Issue #3143: Inconsistent requirements.txt comments
Created: 2021-02-15T18:22:30Z
Package manager/ecosystem
python, pip-tools
What you expected to see, versus what you actually saw
Our org has a monorepo with multiple requirements.txt and requirements.in files. When there is a dependency that needs to be upgraded across multiple requirements files, Dependabot usually opens a single PR that contains all of the changes but sometimes opens multiple PRs, one for each subproject. This is a little annoying but we can deal with it; although if there is a way to consistently split up the PRs I'd love to know about it!
Our main issue is that this big single PR updates every single comment in the requirements.txt files it touches with relative pathnames from the repo root, so # via -r requirements.in becomes # via -r ussd/requirements.in. Any subsequent PR that touches only a single subproject reverts these comments (# via -r ussd/requirements,in -> # via -r requirements.in). This switching back-and-forth is fairly annoying and can cause octopus merges to fail in fun and interesting ways.

Duplicate issue #3636: python pip-compile comment requirements.in path modified by dependabot (when pip-compile run from subdir, and requirements.in is in a nested subdir)
Created: 2021-05-04T12:45:43Z
Package ecosystem
python
Package manager version
pip-compile 5.5
Language version
python 3.8
Manifest location and content prior to update

foo/deploy/base/build/requirements.in

#
# This file is autogenerated by pip-compile
# To update, run:
#
#    pip-compile --generate-hashes --output-file=deploy/base/build/requirements.txt deploy/base/build/requirements.in
#
algoliasearch==2.4.0 \
    --hash=sha256:525f9d50f5363c8ae6603a8e328d8c23957e825fdfe363ecbda55487a0140c76 \
    --hash=sha256:5f62155450949642fe6ae1c163d89630c9ffce9cca62901893ddc1ad3e653239
    # via -r deploy/base/build/requirements.in

(extract)
dependabot.yml content
none
Updated dependency
any
What you expected to see, versus what you actually saw
All # via -r deploy/base/build/requirements.in are replaced by # via -r requirements.in, which isn't stable with our manual usage of pip-compile.
We run pip-tools from subdirectory (foo/), with pip-compile --generate-hashes --output-file=deploy/base/build/requirements.txt deploy/base/build/requirements.in
Native package manager behavior
pip-compile generates (and keep stable) # via -r deploy/base/build/requirements.in (called from subdir foo/)
Images of the diff or a link to the PR, issue or logs

🕹 Bonus points: Smallest manifest that reproduces the issue

Closing comment (2022-11-23T22:21:43Z): This appears to be a dupe of #3143.
Many thanks to @jon-betts for flagging that.
Repository: derailed/k9s

Issue #1471: Start k9s in (Faults view) mode (CLI flag)
Created: 2022-02-21T22:24:29Z
Addin an option to CLI to be able to start K9S in viewing fault mode (toggle fault)/ctrl-z
A new CLI flag like --faults can be used.
The use case is we can start many k9s dashboards(e.x. using tmux) with different context all in faults mode, currently I have to swith to each dashboard and press ctrl-z

Duplicate issue #1607: Ability to start k9s in errors mode
Created: 2022-06-22T01:53:04Z
Describe the solution you'd like
Startup command like k9s --context CTX -A --errors and k9s in error state after start.

Closing comment (2023-02-13T06:31:18Z): TIL of k9s fault mode :-)
Seems like a duplicate of #1471
Repository: derailed/k9s

Issue #1462: k9s running very slowly when opening namespace with 13k pods
Created: 2022-02-11T21:20:56Z
Describe the bug
We have a cluster with 13k pods in a single namespace. When I start k9s in that namespace, it can take minutes for the pods to load and for the terminal to become responsive once again, although there is a lot of latency/stutter. I understand that 13k pods are not very common, and it would be totally fine to say that that is outside the scope of what k9s is designed to handle. But I saw this other ticket that seemed very similar but for secrets. I wonder if we could do something like that? Only load metadata to list the pods and get the details on-demand?
To Reproduce
Steps to reproduce the behavior:

Open k9s
Navigate to the namespace with 13k pods
Wait about a minute
See pods
/<pod-name-filter>
Wait a couple of minutes
See a handful of pods I care about, if it is a small number k9s works fine again, if not there would still be latency

Expected behavior
K9s does not slow down.
Screenshots
It's my employer's cluster, doubt I could post a picture here. Let me know if there is something else I can provide.
Versions (please complete the following information):

OS: macOS Big Sur
K9s: v0.25.18
K8s: v1.19.7

Additional context
The cluster is running on AWS EKS

Duplicate issue #2574: List with namespaces unresponsive
Created: 2024-03-01T12:37:03Z
Describe the bug
When using version 0.31.8 or 0.31.9 the list of namespaces is slow to unresponsive. Reverting back to 0.31.7 seems to fix the issue.
Opening our cluster with about 1200 namespaces makes k9s unresponsive and use lots of cpu.
During this pressing any key takes about 20/30 seconds to do anything.
Opening the list of pods with about 5k of them has no issue.
To Reproduce
Steps to reproduce the behavior:

Go to namespaces

Historical Documents
This is with the default configuration as i removed k9s and the configuration files and reinstalled to see if the problem persists.
Expected behavior
Be more responstive
Versions (please complete the following information):

OS: [e.g. OSX 14.3.1]
K9s: [e.g. 0.31.7/8]
K8s: [e.g. 1.28.5]

Closing comment (2024-03-01T22:43:46Z): Dup #1462
Repository: derailed/k9s

Issue #357: Display kubectl command
Created: 2019-10-15T07:48:48Z
Describe the solution you'd like
Would it be possible to display or put in the clipboard (directly or on demand via a shortcut) the corresponding kubectl command for each action executed in the k9s console?

Duplicate issue #559: Display k8s commands that k9s runs on the background
Created: 2020-02-20T00:17:29Z
Is your feature request related to a problem? No
Describe the solution you'd like
For example, when I press 
 to exec to a pod, I would like to see:
kubectl --context $_CONTEXT -n $NAME_SPACE exec -it $POD_NAME -- bash/ash/sh etc...
Thank you for this cool tool.

Closing comment (2020-02-20T15:24:47Z): @pamido I think we already have this feature available when k9s shell out to kubectl. Please see the debug logs ie k9s -l debug
Dup #357
Repository: derailed/k9s

Issue #1373: change namespace not possible 
Created: 2021-12-14T09:52:36Z
Describe the bug
After updating to the 0.25.10 version, I can't really switch the namespace anymore. Going through the :ns screen, taping enter, I always land within the same namespace, no matter which one I select. And when I'm in the deployment view, for instance, I can change it by pressing 1,2,3 etc, but as soon as I click enter to see the pods or I switch the resource type, I get the old one selected again.
To Reproduce
Steps to reproduce the behavior:

Go to namespace view
Press enter on any other than the current one
See the old namespace still being active

Expected behavior
The selected namespace should remain active.
Versions:

OS: macOS
K9s: 0.25.10
K8s: 1.20.11

Duplicate issue #1378: Regression: Namespace filters are no longer applied on startup
Created: 2021-12-14T19:16:59Z
This looks like a regression of this bug: #1319 in v0.25.10
Refiling here with updated version info.
Describe the bug
Previous versions of k9s would read the k9s.clusters..namespace.active key to determine which namespace filter to apply for the active cluster. Its ignored on startup and the default namespace filter is applied instead.
To Reproduce
Steps to reproduce the behavior:

Start k9s
From any view, change the namespace filter to all by pressing 0
Exit k9s
Start k9s and notice that the default namespace filter is applied vs all.

Expected behavior
The namespace filter stored in the configuration file should be applied on launch.
Versions (please complete the following information):

OS: OSX 11.6.1
K9s: v0.25.10
K8s: Any

Additional context
Workaround: Downgrade to v0.25.8 and this issue does not appear in that version.

Closing comment (2021-12-15T00:21:10Z): It appears this problem is slightly different from before.  Now, the filter appears to always be set to default when changing view or context.
For example, while in the pod view, I can set the filter to kube-system and it's recorded as expected in config.yml.  But, once I change the view (for example to secrets), the active namespace filter is changed to default.  The same thing happens if changing context, etc.
I believe this may be related to #1373
Repository: derailed/k9s

Issue #1747: Open controller shortcut
Created: 2022-09-07T11:28:01Z
In the pods view I usually want to open the controller of a specific pod (ReplicaSet -> Deployment, for example) and then restart the deployment, without navigating to the deployments view, filter them out and selecting the one I need.
It would be awesome if k9s supported this with a shortcut.

Duplicate issue #2696: Add shortcut to jump to the "Controlled By" resource
Created: 2024-05-09T17:58:19Z
Describe the solution you'd like
Consider adding a quick keyboard shortcut to jump to the "Controlled By" "parent" resource when describing a "child" resource.
For example, when describing a pod, jump to the Deployment/ReplicaSet/etc. that controls that pod.
This can help navigating between resources quickly and avoid looking them up manually.
Thanks!

Closing comment (2024-05-24T19:28:52Z): Duplicate of #1747 and solved with the merge of #2700.