text:
Actions used from composite actions are not bumped by dependabot

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
github actions
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "daily"
    open-pull-requests-limit: 1024

  - package-ecosystem: cargo
    directory: "/src/rust/"
    schedule:
      interval: daily
    allow:
      # Also update indirect dependencies
      - dependency-type: all
    open-pull-requests-limit: 1024

  - package-ecosystem: pip
    directory: "/"
    schedule:
      interval: daily
    open-pull-requests-limit: 1024

Updated dependency
actions/cache
What you expected to see, versus what you actually saw
I expect https://github.com/pyca/cryptography/blob/main/.github/actions/cache/action.yml#L33 to be upgraded by https://github.com/pyca/cryptography/pull/8365, but it's not.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Yeah, I can reproduce this. Currently the only way to update composite actions is to configure the directory containing the action.yml file explicitly.
But even if not explicitly configured, we should also parse any local actions referenced by any parsed workflow files, so that you can get all updates for a specific dependency  together like you expected.

@deivid-rodriguez thanks! when you say to configure the directory with the action.yml, you mean one entry per composite action, is that right?

Yes, that's what I mean.

As I understand (I also bumped into this problem), there's no "standard directory" for defining internal actions (I don't think .github/actions/ is standard), and therefore dependabot simply does not assume your actions path.
I also have a similar issue with a private GitHub repo hosting multiple actions at e.g.:
/.github/dependabot.yml
/.github/workflows/my-shared-workflow.yml
/action-foo/action.yml
/action-bar/action.yml
... # and a dozen of other actions

With that repository and dependabot configured with github-actions and directory: "/", what I would like to see is Dependabot looking for all valid action.yml files and updating those, on top of updating the actions within my-shared-workflow.yml
But currently instead what happens is that dependabot will only search for updates within my-shared-workflow.yml.
Realistically I don't think dependabot will ever sweep the whole repo for valid GH Actions files, but instead I expect one of these issues being fixed (so we can have simplify our dependabot config when it has multiple directories with the same ecosystem): #2178 #1582

I believe it's correct that there's no standard directory for internal actions, however, nonetheless they could be discovered by recursively following local uses: from a workflow.

I can label as a feature request, probably a better fit! My intention to support this was to do what @Alex suggests, since that's what we already do in similar situations.

Hi! Can you try using multi-directory support and grouping rules? That should work to update composite actions. cc @abdulapopoola

Thanks! https://github.com/pyca/cryptography/pull/10921 this definitely makes it less verbose. Once there are wildcards we'll be able to do .github/actions/* I assume, at which point I think this will be sufficient for us.

Yes, that's what I mean.

@deivid-rodriguez Can you provide an example configuration for an action located at .github/actions/abc/action.yml?

I no longer maintain this repo, but you can see a few linked commit and PRs with the current workaround.

@carlincherry, are you able to give an example of how the multi-directory would look here? Would it be the below?
version: 2
updates:
  - package-ecosystem: "github-actions"
    directories:
      - "/"
      - "/.github/actions/*/action.yaml"
    schedule:
      interval: "daily"

There isn't a standard, but like many users we use .github/actions/[name] - which means the action.yaml file is at .github/actions/[name]/action.yaml.
I'm concerned that Dependabot may still be looking for a .github/workflows folder with this approach, and it's a little hard to test.

authors: Drowze alex carlincherry deivid-rodriguez king-of-poppk mrmckeb

repo: dependabot/dependabot-core


text:
NPM: fix security update for indirect and direct dependencies

What are you trying to accomplish?
When a security update is run and the project has the vulnerability as both a direct dependency, and indirect dependency of other top-level dependencies, Dependabot only fixes the top-level dependency.
By using the audit's abilities during the lowest_security_fix_version check we can return nil to force a full unlock.
Also made a slight modification to return audit results more often when doing a security update.
Anything you want to highlight for special attention from reviewers?

How will you know you've accomplished your goal?
I have a real-world test here: https://github.com/dsp-testing/npm-multiple-top-level-ancestors
The PR created should remove all instances of the vulnerable lodash.

Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

Verified it bumps the top-level and the parent of a transient dependency: https://github.com/dsp-testing/npm-multiple-top-level-ancestors/pull/1

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Maven: Change logic to check if a version is released

Previously, we parsed an HTML page looking for the name of a dependency to be present.  This was causing failures with Nexus repositories that were returning a non-browsable page.  This PR changes the logic to instead check the headers to see if the dependency exists.
Fixes https://github.com/dependabot/feedback/issues/746

@feelepxyz I fixed almost all of the tests.  There are still two tests in version_finder_spec.rb that are failing (lines 95 and 347).  I suspect that it has to do with the fixtures being HTML files, which we are no longer using due to this change.

@rebelagentm ah yeah the tests are a bit hard to follow, looks like we are changing the stub for the latest version to have an html response without a jar file. It would be good to get rid of all the html fixtures and lets, e.g. https://github.com/dependabot/dependabot-core/blob/master/maven/spec/dependabot/maven/update_checker/version_finder_spec.rb#L63-L65
For the failing tests, we should change the stub_request to respond with a 404 for the latest version and 200 for the earlier version: https://github.com/dependabot/dependabot-core/blob/master/maven/spec/dependabot/maven/update_checker/version_finder_spec.rb#L82-L93
Also rather than gsubing the maven_central_version_files_url it would be better to redefine the whole url in that test to make it easier to spot what's going on.
Let me know if you need any help on this!

authors: feelepxyz rebelagentm


text:
Point at the correct Dockerfile for python

We broke the monolithic docker image into per-language images. So point the link at the Python one.
Also update to a PR that bumped python using this new dockerfile so that we have a better example. It's not perfect as it doesn't bump the pyenv global var, but it's the best we've got right now. We can replace it with the 3.12 PR in October.

Let's first land:

https://github.com/dependabot/dependabot-core/pull/7611

As that will simplify the readme slightly by removing one of the steps completely.


text:
Problem with creating new argument / or option while calling dep deploy

Hi, I've looked into documentation code
argument('stage', InputArgument::OPTIONAL, 'Run tasks only on this server or group of servers.');
option('tag', null, InputOption::VALUE_OPTIONAL, 'Tag to deploy.');

tried insert
option('migrate', null, InputOption::VALUE_OPTIONAL, 'descr');

into my deploy.php code and call
dep deploy --migrate=true
I've an exception about missing --migrate options

How to perform adding new option in console input?
How to access that option from deploy.php file?

I've an exception about missing --migrate options

What's your error message?

Simple deployer's error about missing option, try to append --anyKey=test to your command and you'll see it

I got the error:
$ php deployer.phar deploy --anyKey=test

  [RuntimeException]
  The "--anyKey" option does not exist.

But if I define option, I can't see it.
deploy.php
<?php
require 'recipe/common.php';
option('migrate', null, Symfony\Component\Console\Input\InputOption::VALUE_OPTIONAL, 'descr');
task('test', function () {
    var_dump(input()->getOption('migrate'));
})->desc('Test.');

$ php deployer.phar test --migrate=xxx
  Executing task test
✔tring(3) "xxx"

Thanks, that's why i asked a question how to properly perform it.

source: gharchive/issue

authors: kLkA kenjis

repo: deployphp/deployer


text:
Fix for option without value

[x] Bug fix #2364?
[ ] New feature?
[ ] BC breaks?
[ ] Deprecations?
[x] Tests added?
[ ] Changelog updated?

I first created a failing test and tried to solve it the problem in Stringify.php. Something like this:
foreach ($option as $value) {
     $value = is_string($value) ? self::escape($value) : '';
     $options[] = "--$name " . self::escape($value);
}

But I think Stringify::options can be replaced by Symfony ArrayInput class (docs), because that's exactly doing what you want. But maybe I'm completely wrong.

@martijngastkemper Thanks for the fix! Would you mind fixing the test?

This was fixed in another pr.

authors: Schrank antonmedv martijngastkemper


text:
Install composer if outdated

I added a check in vendors.php: If composer already installed but versiion < 2.0.0., than install composer newly.
I need this for Contao CMS as composer >= 2.0.0 is required.

Sounds reasonable to me. But can you please NOT delete composer.lock? Thanks :-)

Sorry, this was not intended. Would you, please, be so kind to fix that for me?

Most often, I assume, it's the Hoster who not updated Composer. But anyway, may be some users want to keep an outdated version. So I agree to close this PR.
I can as good implement my own task to update composer.

authors: Ernestopheles Schrank


text:
Version 1.0.1 in eXtend veröffentlichen

nur kompatibel mit 2017.4
Bereits in den Meister gemerkelt.

erledigt
https://extend.ulicms.de/google_pagespeed_insights.html

license: Unlicense


text:
🛑 Derailed API is down

In d7fc9e4, Derailed API (https://derailed.one/api) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed API is back up in bff0c23.

repo: derailed-org/derailed-oss-status


text:
🛑 Derailed API is down

In 6690db6, Derailed API (https://derailed.one/api) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed API is back up in 9cc9e03.


text:
🛑 Derailed Home is down

In a3b1b27, Derailed Home (https://derailed.one) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed Home is back up in a4c0c38 after 324 days, 14 hours, 12 minutes.


text:
Command aliases

It'd be helpful if I could specify aliases for commands, preferably in a global and/or local config file.
Like
alias bt=stack
alias quit=exit

:+1: both of these have bit me recently.  I'll write up a patch for them now.

Re-opening because alias command / external config not implemented.

I think I'll take a stab at this.
@derekparker do you have a preferred config file format for this? Also, as there are many packages that deal with reading/writing config files, I feel it would be a good idea to use one of them. Are you averse to using a package for this?

authors: derekparker joeshaw quarnster tylerb

repo: derekparker/delve

license: mit

license_source: bigquery


text:
Add TypeMap debug info.

Do people find this backed info useful?
I so far did.

Codecov Report
Attention: Patch coverage is 64.38356% with 26 lines in your changes are missing coverage. Please review.

Project coverage is 30.53%. Comparing base (c59c1f4) to head (bcc4e3e).

Files
Patch %
Lines

src/Utility/OrmTypes.php
60.52%
15 Missing :warning:

src/Utility/ClassFinder.php
64.28%
10 Missing :warning:

src/Controller/Admin/BackendController.php
85.71%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master      #36      +/-   ##
============================================
- Coverage     31.09%   30.53%   -0.57%
- Complexity      542      568      +26
============================================
  Files            36       38       +2
  Lines          1775     1847      +72
============================================
+ Hits            552      564      +12
- Misses         1223     1283      +60

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

authors: codecov-commenter dereuromark

repo: dereuromark/cakephp-setup


text:
sbt build often fails without shared cache

Build in Docker currently can't share sbt cache.
[info] downloading https://jcenter.bintray.com/jline/jline/2.12.1/jline-2.12.1.jar ...
[info]  [SUCCESSFUL ] jline#jline;2.12.1!jline.jar (106ms)
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::              FAILED DOWNLOADS            ::
[warn]  :: ^ see resolution messages for details  ^ ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: commons-codec#commons-codec;1.10!commons-codec.jar
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

I've switched building to less elegant local version that is able to recover from temporal failures. Sometimes you might need to repeat make build several times, but already resolved dependencies will be cached.

repo: deric/kafka-manager-docker


text:
dialog closes after state update

step:

peform a transaction
quickly open a remove/close dialog (before the state got updated)
see that dialog is closed when the state is updated

Expected: the dialog not closed

resolved with e0ff09073497f1102d72ec7c1cd82555f4dc3315

repo: derivable-labs/exposure-comp


text:
initial hooks to fit stacked spectra

Working with @dirkscholte, this PR adds the option of fitting

Pull Request Test Coverage Report for Build 4569298872

57 of 564 (10.11%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-2.6%) to 50.568%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

py/fastspecfit/continuum.py
4
5
80.0%

py/fastspecfit/io.py
38
223
17.04%

py/fastspecfit/fastspecfit.py
13
334
3.89%

Files with Coverage Reduction
New Missed Lines
%

py/fastspecfit/io.py
1
54.25%

py/fastspecfit/fastspecfit.py
2
13.17%

Totals

Change from base Build 4492796939:
-2.6%

Covered Lines:
2227

Relevant Lines:
4404

💛  - Coveralls

authors: coveralls moustakas

repo: desihub/fastspecfit


text:
update [OIII] and [NII] doublet ratios; update color scheme

As posted in the #fastspecfit channel:
"I’ve been using an [NII] 6584 / [NII] 6548 doublet ratio of 2.9421 based on the atomic data and
emissivities in PyNeb, but @arjundey brought this paper to my attention, which recommends a ratio of 3.049 based on both high signal-to-noise ratio SDSS spectroscopy and a theoretical calculation which includes relativistic corrections to the magnetic dipole operator.
Similarly, I’m going to update the [OIII] 5007 / [OIII] 4959 doublet ratio from 2.9839 (current ratio, again from PyNeb) to 2.993 (0.3% higher) and cite this paper."
This PR includes this change as well as a fix for a bug introduced in #194 and some other small cosmetic changes, particularly the colors used in QA.

Pull Request Test Coverage Report for Build 11951077113
Details

9 of 24 (37.5%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on doublet-ratios at 41.091%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

py/fastspecfit/emlines.py
9
11
81.82%

py/fastspecfit/qa.py
0
13
0.0%

Totals

Change from base Build CI-979:
41.1%

Covered Lines:
3148

Relevant Lines:
7661

💛  - Coveralls


text:
Кнопка "Обновить контакты".

Собственно. Это синхронизация контактов и групп между вкладками. Добавил кого-то на одной борде - нажал Refresh на другой - уже видишь в контакт-листе.
Не знаю, мне было без этого неудобно...
Насчёт #L935, т.е. #6. Я так понял, что contactsSelector с группами строится только один раз, при вызове showReplyform(), второй раз уже не будет из-за if-а. Так что я заменил скрытие формы на удаление её DOM-ноды, по принципу - лучше поправить две строчки, чем выносить куда-то отдельно этот ребилдинг.

Так что я заменил скрытие формы на удаление её DOM-ноды

Будет теряться то, что уже было набрано в поле ответа, разве нет? Это не вариант.
Ну и ребилд этот надо таки сделать (как замену опшенов внутри селекта, чтоб листенеров не потерять). Потому как из-за такого поведения новая группа в списке появляется только после рефреша страницы. Случается редко, но всё равно бесит.
p.s. Надо бы переделать Download contacts as file через FileSaver.js

Будет теряться то, что уже было набрано в поле ответа, разве нет?

А если сохранять в переменной и потом восстанавливать? По сути, браузер то же самое делает, у себя внутрях.

Потому как из-за такого поведения новая группа в списке появляется только после рефреша страницы.

Сейчас будет появлятся после нажатия этой волшебной кнопки.
Так, в общем - что думаешь о подходе с кнопкой? У пулл реквеста есть будущее? Или ты хочешь пилить прозрачно это всё?

По сути, браузер то же самое делает, у себя внутрях.

Не тоже самое, он просто не рендерит весь вот этот кусок ХТМЛ-я, сами объекты и их свойства остаются на месте.

У пулл реквеста есть будущее?

Судя по всему - нет.  Я тут хочу впилить одну фигню к селекторам адресата, так что возможно там же и поправлю это всё - сделаю чтоб список групп (и директов) обновлялся как надо.

authors: aslian desudesutalk

repo: desudesutalk/desudesutalk


text:
Report or fail build when kotlin-compiler-embeddable version is overridden

Expected Behavior
detekt runs successfully using the expected version of the kotlin-compiler-embeddable dependency. If the version of the dependency is overridden in the user's build, either warn the user or fail the build, with a link to documentation explaining the issue and some ways to deal with it.
Current Behavior
This keeps coming up as an issue that detekt doesn't properly handle.
Context
#5644 #5582 #5551 #5021 #4786 #4287

I think this would be really valuable.

either warn the user or fail the build

Are you suggesting querying the kotlin-compiler-embeddable version at Detekt Gradle Plugin apply() type and raising a warning there?

Actually I think a more robust method is to check it in detekt-cli. We can check org.jetbrains.kotlin.config.KotlinCompilerVersion.VERSION, against the expected Kotlin compiler version before starting any analysis. We just need to embed the expected Kotlin version in the JAR somewhere to query.
What do you think about that approach?

I'm going with a failure instead of a warning - even if the mismatched Kotlin version might work (which can happen if it's just a difference in minor version, e.g. 1.7.0 instead of 1.7.10) it will eventually end in failure if not corrected. A warning might be lost in the noise.
But 100% agree on linking to a doc page with pointers on how to correct it.

I'm going with a failure instead of a warning

I thought a bit about it, and maybe this ends up being too aggressive? We would be the only Gradle plugin in the ecosystem doing this. We can expect every user to align on the Kotlin version we impose (i.e. we're not compose).

even if the mismatched Kotlin version might work

I actually think this gives us more freedom as otherwise we might be forced to release a point release whenever Kotlin releases

We can expect

Assume you meant "can't"?
In any case, that's not the expectation - remember that detekt has its own dependency configuration, which requires a specific Kotlin version. The project itself can use any Kotlin version it likes and detekt doesn't impose a specific version for the project.
However the project should not override detekt's dependency configuration otherwise there will be unhandled errors, or with the PR, at least there's a more useful error with a link to the docs to allow users to fix it themselves.

When you say the project itself you mean the runtime right?

Any other dependency configuration except the detekt dependency configuration. detekt dependency configuration needs a specific version of kotlin-compiler-embeddable so it's available on the detekt classpath when it runs. It doesn't matter what version of Kotlin is used for any other dependency configuration.

What happens if a user is applying another gradle plugin which includes a higher version of kotlin-compiler-embeddable?

If the plugin is overriding the dependency version used in the detekt dependency configuration then yes, the build will fail. My view is that the plugin either has a bug, or is misconfigured, if that happens. Do you know of any plugins that are overriding dependencies on all dependency configurations?
The other alternative is just to give up on this approach and have the Gradle plugin use the uber jar as the dependency. That should solve things for good but has other drawbacks.

Unfortunately, the approach suggested in documentation does not work with precompiled script pli=ugins and spring dependency management, fails despite of the
for me with spring boot project and build script plugins this
configurations.matching { it.name.contains("detekt") }.all {
    resolutionStrategy.eachDependency {
        if (requested.group == "org.jetbrains.kotlin") {
            useVersion(io.gitlab.arturbosch.detekt.getSupportedKotlinVersion())
        }
    }
}

Still detekt was compiled with Kotlin 1.9.23 but is currently running with 2.0.0.
kotlin args
kotlin {
    jvmToolchain {
        languageVersion.set(
            JavaLanguageVersion.of(JDK_VERSION),
        )
    }
}

tasks.withType<org.jetbrains.kotlin.gradle.tasks.KotlinCompile> {
    logger.lifecycle("Configuring $name with version ${project.getKotlinPluginVersion()} in project ${project.name}")

    kotlinOptions {
        freeCompilerArgs = listOf("-Xjsr305=strict")
        jvmTarget = JDK_VERSION
        languageVersion = KOTLIN_VERSION
        apiVersion = KOTLIN_VERSION
    }

    compilerOptions {
        verbose = true
        javaParameters = true
        languageVersion = KotlinVersion.fromVersion(KOTLIN_VERSION)
        apiVersion = KotlinVersion.fromVersion(KOTLIN_VERSION)
    }

    dependsOn("spotlessApply")
}

val commonLibs: VersionCatalog = extensions.getByType<VersionCatalogsExtension>().named("commonLibs")
val libs: VersionCatalog = extensions.getByType<VersionCatalogsExtension>().named("libs")

dependencyManagement {
    val springBootVersion = commonLibs.findVersion("springBootVersion").orElseThrow().requiredVersion
    val kotlinVersion = libs.findVersion("kotlinVersion").orElseThrow().requiredVersion

    imports {
        mavenBom("org.springframework.boot:spring-boot-dependencies:$springBootVersion") {
            bomProperty("kotlin.version", kotlinVersion)
        }
    }
}

authors: 3flex OksiBlack cortinico

repo: detekt/detekt


text:
Version catalog clean up

A somewhat opinionated clean up of our version catalog, based on the best practices published on the Gradle blog: https://blog.gradle.org/best-practices-naming-version-catalog-entries

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against 881fbd3ff061921d4fd83599a6202d5b7a17b551


text:
Attention Alignment Not Working

I am currently training the provided model with Korean and English datasets, with a total of 27 speakers.
As stated in the README.md, I added Korean to "symbols" as follows:

The problem is that even after training the model for over 45,000 steps, the attention alignment is not forming.

The target and predicted mel-spectrograms seem similar enough.

To anyone who has used this repo and to @Jeevesh8 , how long does it normally take for the attention to start aligning properly? Should I continue training?
Any help and advice would be greatly appreciated.

@jinny1208 This is common observed phenomenon[See here, for example]. The reason is mainly, I think because mel-spectrogram is predicted frame by frame(auto-regressively), so even if the model learns to just copy the last frame of the sequence(without learning anything about alignment), it can easily lower the loss quite a bit. You need to train longer.
I would suggest you to initialise from Tacotron-2 English pre-trained weights, for faster alignment.

Hi, thanks for your answer! I will train longer and update the results here

The alignment works to some degree. I probably need to train longer and do somthing else to get clearer and more robust alignments.


text:
Create methods.md

Added learnings from class Day 2 to Ruby Guide.
Relates to issue TheIronYard--Orlando/2015--SUMMER--ROR#22

Created separate files for each topic. Applied a basic template. Code blocks still need to be put into the correct format. Links and other descriptive text needs to be added in fields where not present.
References Issue TheIronYard--Orlando/2015--SUMMER--ROR#27


text:
how to use pybass3 to implement a callback function

Thank you very much for providing such a concise and easy-to-use library, which allowed me to easily implement a simple music player. However, I have a question now. I want to implement a callback function during music playback to update the interface playback progress.
I found that there seems to be a method called channel_set_sync on un4seen website to achieve the callback function. However, I could not find this method in the library you provided.
Could you please tell me how to use pybass3 to implement a callback function during playback?
Thank you!

I didn't hook into the sync logic in favor of just polling the stream's position and status.   That said I can look into implementing that but from prior experience, ctypes callbacks might be a little flaky.
What sync types are you interested in?

Just making a note - doing a quick test, it might be better to wrap a sync callback with a middleman callback as I broke the C Unseen library when I made a small logical error.

I'm sorry it took me a few days to see your reply to me.
Currently I'm just implementing my player based on the Song class, and on that basis I think I need the following sync types:
'mediaplay_mediachanged_callback',
'mediaplay_playing_callback',
'mediaplay_paused_callback',
'mediaplay_stopped_callback',
'mediaplay_forward_callback',
'mediaplay_backward_callback',
'mediaplay_timechanged_callback',
'mediaplay_positionchanged_callback',

Maybe I'm not necessarily thinking right. But thank you very much for considering implementing it.
Thank you!

I will see what I can do, most of those are pretty straightforward.

@SHI1992
Just prototyping in my head.
Would something like ChannelCallbacks.onPlay(channel_handle, your_callback) and respective onPause and onStop work?
From prior experience, you might want to skip over the forward and backward callbacks and see if time or position changed works better.  I made a prototype music player in PyQT5 that had problems with infinite recursion when I watched too many state variables.


text:
继承不走WKNavigationDelegate代理方法

我写一个子类，hook 了updateNavigationItems方法，不确定什么原因父类的WKNavigationDelegate代理方法不走了

WebViewJavascriptBridge都是WKNavigationDelegate代理

repo: devedbox/AXWebViewController


text:
Golang面试题解析（四）第35题代码不严谨

int类型是32或64位，与操作系统位数有关
package main

import (
	"fmt"
	"math"
)

func reverse2(x int32) int32 {
	fmt.Println("num2:", x)
	var num int64
	x64 := int64(x)
	for x64 != 0 {
		num = num*10 + x64%10
		x64 = x64 / 10
	}
	// 使用 math 包中定义好的最大最小值
	if num > math.MaxInt32 || num < math.MinInt32 {
		return 0
	}
	return int32(num)
}

func reverse(x int) (num int) {
	fmt.Println("num:", x)
	for x != 0 {
		num = num*10 + x%10
		x = x / 10
	}
	// 使用 math 包中定义好的最大最小值
	if num > math.MaxInt32 || num < math.MinInt32 {
		return 0
	}
	return
}

func main() {
	var a int = 2147483647
	fmt.Println("reverse():", reverse(a))
	fmt.Println("reverse2():", reverse2(int32(a)))
	// ----------------- x86_64
	// num: 2147483647
	// reverse(): 0
	// num2: 2147483647
	// reverse2(): 0

	// ----------------- i686
	// num: 2147483647
	// reverse(): -1126087180
	// num2: 2147483647
	// reverse2(): 0
}

commit rebase 一下 master。

repo: developer-learning/night-reading-go


text:
cloneElement - if children are provided in the second argument of cloneElement they are ignored.

Does not work:
return cloneElement(component, { children })

Does work:
return cloneElement(component, {}, children)

This should fix some quirky bugs that pop up in 3rd party lib like bootstrap, etc.

:)

repo: developit/preact-compat


text:
Upgrade to webpack 2

Karma is using webpack to bundle the source for testing.

Coverage remained the same at 100.0% when pulling 34048ade1ab1bd94171d6999e3b8bb15a484414b on gdub22:webpack2 into c4f3fb0e4c18bd502b9084a11149749fa6a08c9b on developit:master.

Coverage remained the same at 100.0% when pulling 8d29b0f2dac910403b97d8b229474729950f300a on gdub22:webpack2 into c4f3fb0e4c18bd502b9084a11149749fa6a08c9b on developit:master.

Coverage remained the same at 100.0% when pulling 145822ebdbd3380f104bf8f1e4be47f42c766dff on gdub22:webpack2 into abcdcdaa55200a98301e571cef6223b4ed50f565 on developit:master.

I'm surprised this works with Babel 5! haha

Ha yea, preact is still depending on babel-loader 5.x which uses babel 5.x.  Webpack is essentially just passing the options through.

authors: coveralls developit gdub22

repo: developit/preact


text:
add colormap endpoints

ref https://github.com/developmentseed/titiler/discussions/509

TODO

[x] ask for feedback
[ ] add tests

This new endpoint looks very useful. I would suggest to have a query param for number of classes at the endpoint of /colormap/{id}.
I can see current endpoint returns so many classes (44 No. what I can see in screenshot), but it would be nice if client side can request how many classes to be returned from titiler. I think number of classes parameter can be useful if want to use custom colormap to classify data with limited classes instead of linear legend.

@JinIgarashi thank for your feedback 🙏

(44 No. what I can see in screenshot)

in fact it returns 256 values, because all rio-tiler colormaps are composed of values between 0 and 255 (because that's how GDAL colormap are)
We could add a step parameter to only select few values but user would need to understand that for colormaps (e.g qualitative colormaps) this would give really weird results

Also, it might be useful if it can return color as hsl format in addition to rgba and hex formats. If color format is following maplibre style spec, it can be easier to adapt for maplibre/mapbox.

Well the more I think about this, the more I think we should only return value as RGBA tuple, not event as HEX string. It seems quite trivial do transform the RGBA values to hex or hsl in client application instead of adding more complexity in the titiler endpoint

This new endpoint looks very useful. I would suggest to have a query param for number of classes at the endpoint of /colormap/{id}.

same as https://github.com/developmentseed/titiler/pull/796#issuecomment-1999296498, this would be pretty trivial to do in the client application directly instead of adding complexity in titiler endpoint IMO

Q: we have the tilematrixet endpoints with a /tileMatrixSet prefix (defined by OGC), so should the colormap endpoints be prefixed with colorMaps (instead of colormaps as defined now)?
## This PR

/colormaps
/colormaps/{colormapId}

## Proposed

/colorMaps
/colorMaps/{colormapId}

authors: JinIgarashi vincentsarago

repo: developmentseed/titiler


text:
Release changes for OLM validation

Please specify the area for this PR
registry operator
What does does this PR do / why we need it:
Changes to fix failing OLM validation test cases, required for OperatorHub publication (devfile/api#1211).
Additionally, contains the removal of CHANGELOG in favor of using the built-in GitHub release pages that can generate this content.
Which issue(s) this PR fixes:
Fixes #?
fixes devfile/api#1251
PR acceptance criteria:

[ ] ~Change Log~

~Are all your changes documented under the upcoming release entry?~

[x] Test Coverage

Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

[x] Gosec scans

Fix all MEDIUM and higher findings and/or annotate a finding per gosec instructions: https://github.com/securego/gosec#annotating-code to address why a finding is not a security issue

Documentation

[x] Does the registry operator documentation need to be updated with your changes?

How to test changes / Special notes to the reviewer:

/retest

The registry operator also requires its own cert-manager which is not supported by OLM due to it having its own cert management: https://olm.operatorframework.io/docs/advanced-tasks/adding-admission-and-conversion-webhooks/#certificate-authority-requirements
Currently investigating a workaround to https://github.com/operator-framework/operator-lifecycle-manager/issues/1805.

The registry operator also requires its own cert-manager which is not supported by OLM due to it having its own cert management: https://olm.operatorframework.io/docs/advanced-tasks/adding-admission-and-conversion-webhooks/#certificate-authority-requirements
Currently investigating a workaround to operator-framework/operator-lifecycle-manager#1805.

Update: It seems after reviewing this more that issue here is that if we were doing any of the following it would not work with OLM's cert management:

Need to provide our own certifications
Mounting the location to store the certifications to a different location from the defaults

We are not currently doing these, only using cert-manager outside OLM. The setup for using OLM's cert manager should be the same as we currently have for cert-manager.

repo: devfile/registry-operator


text:
x update -v 1.1.1

allow -v --version flag to checkout for the version needed to be installed.
also include validations to check if the requested version is even available or not.

This might be a good idea.

repo: devhindo/x


text:
Update to Kafka 0.9.0

Update to kafka 0.9.0, upgrade consumer code as well.

@AleksandrPavlenko, hi! if you need any assistance let me know, it would be pleasure to help you with server deployment and running tests.

repo: devicehive/devicehive-java-server


text:
Vite打包 ReferenceError: require is not defined

veaury: 2.3.12,  降到 2.3.1 和2.3.8 都试了 都不行

@probe-pg 这个报错和veaury无关，是你项目的三方依赖中使用了require

确实是 其他第三库问题，添加
commonjsOptions: {
transformMixedEsModules: true
},
就好使了，谢谢

authors: devilwjp probe-pg

repo: devilwjp/veaury


text:
[Feature Request][NOWEB] - send group.join on participants join as well

Describe the bug

Webhook event group.join is not coming to the webhook URL for NOWEB engine. (as seen at this table https://waha.devlike.pro/docs/how-to/webhooks/#webhooks)
The only case it works is when the waha connected user joins the group, but the main goal is to 'watch' other users joining the group. For WEBJS it is working normally.

Version
{
  "version": "2024.10.3",
  "engine": "NOWEB",
  "tier": "PLUS",
  "browser": "/usr/bin/chromium"
}

To Reproduce Steps to reproduce the behavior:

Set webhook url to your preferred url
Use own waha connected user to join a group, you can see the incoming webhook data
Join the group with an other whatsapp
No incoming webhook data

Expected behavior

We should expect incoming data to webhook url when any other user joins the group.

Engine I'm using NOWEB engine.
Docker Logs

It is possible only to see logs of own waha connected user, other users don't log error.

yeah, that webhook is supposed to fire when YOU join a new group, now when someone joins it.
To get participants you can use GET /api/{session}/groups/{groupId}/participants
https://waha.devlike.pro/docs/how-to/groups/#participants
Just do not request it too frequently, it does communicate with WA servers and you can get rate limited, like in https://github.com/devlikeapro/waha/issues/462

Probably we can add groups.participants.{actions} tho :thinking: Let me know if you're interested and we can see how many people are interested in that too!

We can see that in WEBJS it works... Here I have two images of the payload I received on my n8n containing group.join from two -different- numbers than the one monitoring... This feature would be great in NOWEB since it is way more cost effective and less demanding than requesting group participants every now and then (and hoping not to get blocked).

I see, ok, let me see what we can do here!

+1

repo: devlikeapro/waha


text:
🛑 Consulta Socio Backoffice is down

In 68c858f, Consulta Socio Backoffice ($BACKOFFICE_SOCIO_URL) was down:

HTTP code: 502
Response time: 5221 ms

Resolved: Consulta Socio Backoffice is back up in fde7a8a.

repo: devmuvi/uptime-monitor


text:
#837: Changed type of exception

Closes: #837
Changed the exception, that is thrown when there is no git installation from IllegalStateException to CliException

Pull Request Test Coverage Report for Build 12178371349
Details

0 of 0   changed or added relevant lines in 0 files are covered.
24 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 67.265%

Files with Coverage Reduction
New Missed Lines
%

com/devonfw/tools/ide/git/GitContextImpl.java
24
63.64%

Totals

Change from base Build 12146647701:
0.0%

Covered Lines:
6565

Relevant Lines:
9410

💛  - Coveralls

authors: WorkingAmeise coveralls

repo: devonfw/IDEasy


text:
docs: update pipelines/add-pipeline article to add warning about CUSTOM operation

Description of changes

[X] Fixed the mention of the ADD PIPELINE button, which was replaced by the MANAGE button
[X] The excerpt "Follow the prompts to complete the configuration..." was replaced by an explanation in three parts, about adding a name, selecting a parallel execution limit, and most importantly, about choosing the Operation, and in this step, was added a warning not to choose the CUSTOM operation, as it operation not fully supported

GitHub issues resolved by this PR

[X] N/A

Quality Assurance

Once the changes in this PR are merged and deployed, success criteria is: Update the article https://www.devopness.com/docs/pipelines/add-pipeline/

More info

@cla-bot check

@jfoliveira, I copied your suggestions into my own commit, because when you made them, I had already made another commit correcting some spelling errors, and then the interface did not release the 'commit' of your suggestions.

@Diegiwg thanks for the contribution, it is already available in production

I was very happy to do the first (of many?) PR.

authors: Diegiwg jfoliveira thlmenezes

repo: devopness/devopness


text:
fix Dockerfile

fix TG $VERSION when TG_VERSION=latest in Dockerfile, was missing "v" in front of version number
:memo:  Brief description

:computer:  Commits

:file_folder:  Modified files

:warning: Additional information

[ ] Pushed to a branch with a proper name and provided proper commit message.
[ ] Provided a clear and concise description of what the issue is.

Check CONTRIBUTING.md and CODE_OF_CONDUCT.md for more information

Hi, thanks for taking interest in my project!
The current behaviour is intended.
See download link in https://github.com/devops-infra/docker-terragrunt/blob/master/Dockerfile#L71
So VERSION is expected to be in v0.35.13 format, if TG_VERSION is latest it needs to generate version string in such format. If you want specific version TG_VERSION should be in 0.35.13 format, just like it's in https://github.com/devops-infra/docker-terragrunt/blob/master/Makefile#L6
Hope that helps to understand the mechanism behind it.

Hi, thanks for taking interest in my project! The current behaviour is intended. See download link in https://github.com/devops-infra/docker-terragrunt/blob/master/Dockerfile#L71 So VERSION is expected to be in v0.35.13 format, if TG_VERSION is latest it needs to generate version string in such format. If you want specific version TG_VERSION should be in 0.35.13 format, just like it's in https://github.com/devops-infra/docker-terragrunt/blob/master/Makefile#L6 Hope that helps to understand the mechanism behind it.

I understand, that's exactly what I'm proposing to fix.
In current Dockerfile VERSION variable used on LINE 71 will be generated WITHOUT "v" in front  in case of TG_VERSION=latest (because of sed call on LINE 66), but WITH "v" when specific version is specified via TG_VERSION (LINE 68).

Ah, yes, sorry, you're right!
I had jet lag after re:Invent and it seemed all ok, after some sleep I see my mistake. Haven't used latest in a long while since I hardcode versions now, so I missed that.

@all-contributors bot

@all-contributors please add @dsoudakov for bug, code

authors: ChristophShyper dsoudakov

repo: devops-infra/docker-terragrunt


text:
Why is firebase a dependency?

Hello,
I just saw this warning in the console:
It looks like you're using the development build of the Firebase JS SDK.
When deploying Firebase apps to production, it is advisable to only import
the individual SDK components you intend to use.

For the CDN builds, these are available in the following manner
(replace <PACKAGE> with the name of a component - i.e. auth, database, etc):

https://www.gstatic.com/firebasejs/5.0.0/firebase-<PACKAGE>.js

Which made me wonder: why would firebase (and related fcm package) be imported here, if pushjs itself doesn't need it and this is supposed to be a thin ember wrapper around it? Is there anything you need firebase for, and in that case, why is it not mentioned in the documentation?
Among other reasons I see not to include it:

one more dependency to manage
firebase belongs to Google which may not be everyone's cup of tea
https://cost-of-modules.herokuapp.com/result?p=firebase@5.3.1

I just tried removing firebase completely and there doesn't seem to be any bug. Would you accept a PR that removes firebase completely?

Hi @devotox,
did you get a chance to review #27 ?
It has been running in production on our stack for about a month now without any issue. Hope you can merge and release soon! How can I help?

Yes would love help maintaining. And I believe firebase is a dependency
since you can use the gcp push messaging with this addon
On Mon, 17 Dec 2018, 16:27 Francois Falala-Sechet <notifications@github.com
wrote:

Hi @devotox https://github.com/devotox, do you need help with
maintaining this repo? Would love to help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/devotox/ember-cli-pushjs/issues/26#issuecomment-447906823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB-BzszimrwiHTrVVE-Evi6CPqTalXEsks5u58X-gaJpZM4V86Jz
.

Cool.
I would suggest making 2 different plugins then, because it does not fit the description (and most common need) of a Simple Wrapper around Push JS.

one plugin is the wrapper around pushjs
another plugin is built on top of this one for people who want to use firebase (and proposes a solution

Reasoning is that firebase is not the only provider of push notification that exists, while pushjs is "how" the notifications are technically displayed. If people want to integrate their own notification service, they can use the basic pushjs and add the service on top.
The cost of forcing firebase onto everyone is simply not worth it as it is not at all universal! 🙂

I think you are definitely correct.
I was using firebase heavily when I created this plugin but now I believe
it should be a lot more generic like you propose.
Are you able to make a pull request doing just this?
On Thu, 20 Dec 2018, 11:46 Francois Falala-Sechet <notifications@github.com
wrote:

Cool.
I would suggest making 2 different plugins then, because it does not fit
the description (and most common need) of a Simple Wrapper around Push JS.

one plugin is the wrapper around pushjs
another plugin is built on top of this one for people who want to
use firebase (and proposes a solution

Reasoning is that firebase is not the only provider of push notification
that exists, while pushjs is "how" the notifications are technically
displayed. If people want to integrate their own notification service, they
can use the basic pushjs and add the service on top.
The cost of forcing firebase onto everyone is simply not worth it as it is
not at all universal! 🙂
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/devotox/ember-cli-pushjs/issues/26#issuecomment-449061993,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB-BzhAafcQVXyB1usxCblFXnoVCyUArks5u677zgaJpZM4V86Jz
.

How about that: https://github.com/devotox/ember-cli-pushjs/pull/27 🙂

Thanks for the merge!
Don't forget to release to npm ;-) And let me know if you need further help!

@devotox can you release to npm please?

Haaaa yes will do on the next few days
On Fri, 28 Dec 2018, 16:37 Francois Falala-Sechet <notifications@github.com
wrote:

@devotox https://github.com/devotox can you release to npm please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/devotox/ember-cli-pushjs/issues/26#issuecomment-450431430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB-Bzpohebq3IaV_G0w11pzGa1L0crGCks5u9o8kgaJpZM4V86Jz
.

Released!

authors: devotox frsechet

repo: devotox/ember-cli-pushjs


text:
❤월급두배받는법 블로그(확인부탁드립니다!!)❤

각 챌린지 미션을 완료 할때 마다 각자 자신의 항목을 수정하는 PR을 생성해 주세요.

챌린저 정보
챌린저의 정보를 아래에 남겨주세요.

팀 이름: 월급두배받는법

Microsoft Learn 프로필 URL은 https://docs.microsoft.com/ko-kr/users/******와 같이 생겼습니다.

Microsoft Learn 프로필 URL: https://docs.microsoft.com/ko-kr/users/73885525/
GitHub ID: @ksiyeon27

아래는 SNS 챌린지의 경우에만 입력해 주세요.

다양한 SNS가 있지만, 여기서는 트위터, 페이스북, 인스타그램만 인정합니다.

SNS 이름:
SNS ID:

완료된 챌린지

이번에 완료된 챌린지의 내용을 마킹해주세요.

[ ] 애저 정적 웹 앱 챌린지 완료
[ ] 깃헙 액션 챌린지 완료
[ ] 소셜미디어 인증샷 챌린지 완료
[ ] 애저 정적 웹 앱 URL 제출 챌린지 완료
[ ] 애저 정적 웹 앱 리포지토리 제출 챌린지 완료
[x] 블로그 후기 URL 제출 챌린지 완료

@ksiyeon27 블로그 후기 너무 재밌게 잘 읽었어요!!🥔 배우신 점들과 소개를 너무 깔꼼하게 잘 정리해주셔서 좋았습니다☺🙏🏼 챌린지 완료해주셔서 감사합니다!!🥳

/retrosignoff

repo: devrel-kr/HackaLearn


text:
Unable to map inner properties of Photos/Videos/Collections/CollectionMedia objects

Describe the bug
\Devscast\Pexels\Client::getMappedData() always throws exception with incorrect type message.
To Reproduce
Steps to reproduce the behavior:

Initiate \Devscast\Pexels\Client with auth token.
Call $client->searchPhotos('westie dog')
Exception is trowed with following error message: Unexpected $type value

Additional Info
Denormalizer returns the instance of one of this classes Photos|Videos|Collections|CollectionMedia. But then, to map inner properties (e.g. photos/videos/collections/media), the check via is_subclass_of is used, which always returns false.
Would be great if you take a look. Thanks a lot!

@nastasyaaaa I'm on it

authors: bernard-ng nastasyaaaa

repo: devscast/pexels


text:
Debug Flag does not print debug logs

What happened?
devspace deploy --debug does not change the log level and I still only see info or higher messages.
What did you expect to happen instead?
devspace deploy --debug shows actual debug level log entries.
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
Just use the project in examples/quickstart.
Local Environment:

DevSpace Version:  6.3.3
Operating System: mac
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: aws
Kubernetes Version: Client Version: v1.24.2, Kustomize Version: v4.5.4, Server Version: v1.25.12-eks-2d98532

Anything else we need to know?
It also doesn't seem that an actual stacktrace is printed out on an error, is it limited to specific errors?

Hello! Thanks for reporting this issue. I can't seem to reproduce it with 6.3.3 or on the main branch. Here's a copy of the output I got, perhaps you could provide your log output as well?
> cd examples/quickstart
> devspace deploy --debug
16:49:10 info Using namespace 'loft'
16:49:10 info Using kube context 'kind-kind'
16:49:10 debug Use config:
version: v2beta1
name: quickstart
deployments:
    quickstart:
        name: quickstart
        helm:
            values:
                containers:
                    - image: loftsh/javascript:latest
dev:
    my-dev:
        name: my-dev
        imageSelector: loftsh/javascript:latest
        sync:
            - path: ./
              excludeFile: .gitignore
        terminal:
            command: ./devspace_start.sh
        ssh: {}
        ports:
            - port: "3000"
        open:
            - url: http://localhost:3000

16:49:10 debug Run pipeline:
name: deploy
run: |-
    run_dependencies --all
    ensure_pull_secrets --all
    build_images --all
    create_deployments --all

16:49:10 run_dependencies --all
16:49:10 Marked project excluded: quickstart
16:49:10 ensure_pull_secrets --all
16:49:10 build_images --all
16:49:10 create_deployments --all
16:49:10 Deploying 1 deployments concurrently...
16:49:10 deploy:quickstart Skipping deployment quickstart
16:49:10 Deploying 0 deployments concurrently
16:49:10 debug Wait for dev to finish

authors: lizardruss mschoenlaub

repo: devspace-sh/devspace


text:
:four_leaf_clover: Proposal: Switich plugininstaller.Runner.GetStatusOperation into a func slice.

What Would You Like to Add? Why Is This Needed?
Thanks to #859, we have a new and more efficient way to install plugins.
But I have a small suggestion for improvement that could make it even better.
Right now, plugininstaller.Runner.GetStatusOperation only supports passing in a single function that gets the resource. But sometimes, we'll want to reuse existing functions (like helm's several already well-established functions for getting resource), plus some additional resource keys for customization. This can lead to having multiple functions to get resource. But plugininstaller.Runner.GetStatusOperation can only pass one function here, so our code will look like this.

We have to wrapper them.
Design
// before
//type Runner struct {
//	PreExecuteOperations []MutableOperation
//	ExecuteOperations    []BaseOperation
//	TermateOperations    []BaseOperation
//	GetStatusOperations   StatusOperation
//}

type Runner struct {
	PreExecuteOperations []MutableOperation
	ExecuteOperations    []BaseOperation
	TermateOperations    []BaseOperation
	GetStatusOperation   []StatusOperation // here is changed
}

func (runner *Runner) Execute(options RawOptions) (map[string]interface{}, error) {
	...
        ...
	// 4. Get Status for this execute
	var status map[string]interface{}
	for _, getStatusOperation := range runner.GetStatusOperations {
		stat, err := getStatusOperation(options)
		if err != nil {
			return nil, err
		}
		for k, v := range stat {
			status[k] = v
		}
	}
	return status, err
}

Anything else

/cc @steinliber

repo: devstream-io/devstream


text:
⚠ Mobitopup has degraded performance

In 88e2cde, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 8692 ms

Resolved: Mobitopup performance has improved in 8ad8a49 after 7 minutes.


text:
shows webpack version Error while installing npm

i'm not adding extra files
reference :

i'm not adding extra files
reference :

Hi @SantoshKumarRavi ,
Can you please provide us your package.json file or your dependancy versions like react, webpack, etc.

This is a webpack related issue arise with the react 18 release

authors: SantoshKumarRavi hashaaan