[Bug]: Umami docker fails, login first fail

Describe the Bug

I tried v2.14.0 still got the same error
My OS:
cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
uname -m
x86_64
Database
PostgreSQL
Relevant log output
2024-12-22T22:23:49.547322092Z yarn run v1.22.22
2024-12-22T22:23:49.595681812Z $ npm-run-all check-db update-tracker start-server
2024-12-22T22:23:50.158680325Z $ node scripts/check-db.js
2024-12-22T22:23:50.293932651Z ✓ DATABASE_URL is defined.
2024-12-22T22:23:50.375299791Z ✓ Database connection successful.
2024-12-22T22:23:50.431822014Z ✓ Database version check successful.
2024-12-22T22:23:51.590460405Z Prisma schema loaded from prisma/schema.prisma
2024-12-22T22:23:51.590494615Z Datasource "db": PostgreSQL database "umami", schema "public" at "postgresql:5432"
2024-12-22T22:23:51.590497695Z
2024-12-22T22:23:51.590499786Z 7 migrations found in prisma/migrations
2024-12-22T22:23:51.590501846Z
2024-12-22T22:23:51.590503686Z Applying migration `01_init`
2024-12-22T22:23:51.590505596Z Applying migration `02_report_schema_session_data`
2024-12-22T22:23:51.590507896Z Applying migration `03_metric_performance_index`
2024-12-22T22:23:51.590509915Z Applying migration `04_team_redesign`
2024-12-22T22:23:51.590511815Z Applying migration `05_add_visit_id`
2024-12-22T22:23:51.590513686Z Applying migration `06_session_data`
2024-12-22T22:23:51.590515556Z Applying migration `07_add_tag`
2024-12-22T22:23:51.590517466Z
2024-12-22T22:23:51.590519316Z The following migration(s) have been applied:
2024-12-22T22:23:51.590521206Z
2024-12-22T22:23:51.590523066Z migrations/
2024-12-22T22:23:51.590524966Z   └─ 01_init/
2024-12-22T22:23:51.590527766Z     └─ migration.sql
2024-12-22T22:23:51.590529726Z   └─ 02_report_schema_session_data/
2024-12-22T22:23:51.590531656Z     └─ migration.sql
2024-12-22T22:23:51.590533546Z   └─ 03_metric_performance_index/
2024-12-22T22:23:51.590535416Z     └─ migration.sql
2024-12-22T22:23:51.590537276Z   └─ 04_team_redesign/
2024-12-22T22:23:51.590539186Z     └─ migration.sql
2024-12-22T22:23:51.590541036Z   └─ 05_add_visit_id/
2024-12-22T22:23:51.590542896Z     └─ migration.sql
2024-12-22T22:23:51.590544716Z   └─ 06_session_data/
2024-12-22T22:23:51.590546556Z     └─ migration.sql
2024-12-22T22:23:51.590548376Z   └─ 07_add_tag/
2024-12-22T22:23:51.590550236Z     └─ migration.sql
2024-12-22T22:23:51.590552076Z
2024-12-22T22:23:51.590554016Z All migrations have been successfully applied.
2024-12-22T22:23:51.590555916Z
2024-12-22T22:23:51.590564257Z ✓ Database is up to date.
2024-12-22T22:23:51.859872513Z $ node scripts/update-tracker.js
2024-12-22T22:23:52.255480840Z $ node server.js
2024-12-22T22:23:52.595255720Z    ▲ Next.js 15.0.4
2024-12-22T22:23:52.595569723Z    - Local:        http://localhost:3000
2024-12-22T22:23:52.595614933Z    - Network:      http://<IP_ADDRESS>:3000
2024-12-22T22:23:52.595618703Z
2024-12-22T22:23:52.595621224Z  ✓ Starting...
2024-12-22T22:23:52.691316439Z  ✓ Ready in 100ms
2024-12-22T22:24:58.260125220Z error Command failed with signal "SIGILL".
2024-12-22T22:24:58.260238421Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-12-22T22:24:58.281960412Z ERROR: "start-server" exited with 1.
2024-12-22T22:24:58.297329682Z error Command failed with exit code 1.
2024-12-22T22:24:58.297435604Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-12-22T22:24:58.856589836Z yarn run v1.22.22
2024-12-22T22:24:58.895677758Z $ npm-run-all check-db update-tracker start-server
2024-12-22T22:24:59.311756973Z $ node scripts/check-db.js
2024-12-22T22:24:59.451708567Z ✓ DATABASE_URL is defined.
2024-12-22T22:24:59.529485924Z ✓ Database connection successful.
2024-12-22T22:24:59.586105816Z ✓ Database version check successful.
2024-12-22T22:25:00.648431503Z ┌─────────────────────────────────────────────────────────┐
2024-12-22T22:25:00.648482823Z │  Update available 5.17.0 -> 6.1.0                       │
2024-12-22T22:25:00.648489113Z │                                                         │
2024-12-22T22:25:00.648494213Z │  This is a major update - please follow the guide at    │
2024-12-22T22:25:00.648498843Z │  https://pris.ly/d/major-version-upgrade                │
2024-12-22T22:25:00.648503634Z │                                                         │
2024-12-22T22:25:00.648506963Z Prisma schema loaded from prisma/schema.prisma
2024-12-22T22:25:00.648508333Z │  Run the following to update                            │
2024-12-22T22:25:00.648513023Z │    yarn add --dev prisma@latest                         │
2024-12-22T22:25:00.648517603Z │    yarn add @prisma/client@latest                       │
2024-12-22T22:25:00.648522354Z └─────────────────────────────────────────────────────────┘
2024-12-22T22:25:00.648596314Z Datasource "db": PostgreSQL database "umami", schema "public" at "postgresql:5432"
2024-12-22T22:25:00.648604725Z
2024-12-22T22:25:00.648609144Z 7 migrations found in prisma/migrations
2024-12-22T22:25:00.648613344Z
2024-12-22T22:25:00.648617584Z
2024-12-22T22:25:00.648621574Z No pending migrations to apply.
2024-12-22T22:25:00.648625765Z
2024-12-22T22:25:00.648630164Z ✓ Database is up to date.
2024-12-22T22:25:00.963465050Z $ node scripts/update-tracker.js
2024-12-22T22:25:01.347011392Z $ node server.js
2024-12-22T22:25:01.959484010Z    ▲ Next.js 15.0.4
2024-12-22T22:25:01.960337498Z    - Local:        http://localhost:3000
2024-12-22T22:25:01.960356708Z    - Network:      http://<IP_ADDRESS>:3000
2024-12-22T22:25:01.960360239Z
2024-12-22T22:25:01.960398179Z  ✓ Starting...
2024-12-22T22:25:02.122739468Z  ✓ Ready in 172ms

Which Umami version are you using? (if relevant)
v2.15.1
Which browser are you using? (if relevant)
Chrome 131.0.6778.205
How are you deploying your application? (if relevant)
Coolify

You need to post the error that is in the box.

yes the deploy process was fine, but it had problems during the first login

this log:
2024-12-24T07:15:13.677413054Z error Command failed with signal "SIGILL".
2024-12-24T07:15:13.677735705Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-12-24T07:15:13.702318229Z ERROR: "start-server" exited with 1.
2024-12-24T07:15:13.722795854Z error Command failed with exit code 1.
2024-12-24T07:15:13.723134876Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
and the server was restarted


Cannot Do Anything With Ore Chunks

I get ore pieces which makes ore chunks but then I cannot craft/smelt or do anything with ore chunks. Is this a bug? Conflicting mods?  I cannot find any recipe in JEI using Ore Chunks. I've scoured the internet, including every issue, open and closed here. No one seems to have this issue. I see this mod removed several unnecessary steps from the original Ex Nihilo so I feel like I'm just being stupid and not doing something right.
All my mods:
Actually Additions
BuildCraft
CodeChicken Lib
CoFH Core
CoFH World
Ex Compressum
Ex Nihilo Creatio
Extra Utilities 2
Forge Mod Loader
Galacticraft Core
Galacticraft Planets
Inventory Tweaks
JourneyMap
Just Enough Items
Mantle
Mekanism
Micdoodle8 Core
Not Enough Items
Redstone Flux
Refined Storage
Thermal Dynamics
Thermal Expansion
Thermal Foundation
Tinkers' Construct
Tiny Progressions

Is everything running with default configs? I don't see anything off hand that I am aware of which would mess with the smelting recipes. Are you able to smelt other ores?

Is everything running with default configs? I don't see anything off hand that I am aware of which would mess with the smelting recipes. Are you able to smelt other ores?

Yes, I haven't changed anything in the config files. I can smelt the vanilla ores and the ores from other mods without any iss-- Okay, I'm fairly certain I wasn't able to smelt any chunks when I posted this, but now I'm able to smelt all of the chunks except for Osmium. I thought I had to craft the chunks into gravel ore first, but I know I tried smelting chunks/pieces when I realized there was no gravel ore to craft.
Okay, I can smelt Osmium.. Just not in the Tinkers' Smeltery. You know what, I apologize for wasting your time. I'll just close out this issue and mark it up as me being ignorant.


Release actual code on hex

Hi,
The last version available on hex is the 0.5.1 that use elixir 1.1.x, would you mind to publish a new version on hex that would use elixir 1.2.x avoiding to have to add the dependency as a git repository.
Thanks

I've released version 0.6.1 some minutes ago. Happy building! 💖

Thanks
Il sab 7 mag 2016, 12:07 Christoph Grabo<EMAIL_ADDRESS>ha
scritto:

Closed #5 https://github.com/edib-tool/mix-edib/issues/5.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/edib-tool/mix-edib/issues/5#event-653414143


chore: update .mergify.yml for polaris v1.x.x

Created release/v1.x.x-polaris branch off of release/v1.x.x
Created backport/v1.x.x-polaris label

Bump @davidterpay


getting aider + ctags installed on OSX

Hi i'm trying to figure out how to use ctags with aider but it's not clear from the instructions.
I cloned aider, installed it, and then cloned ctags and put it in the aider directory. i also installed that. it seems to be available because the command "aider" works but it doesn't see the universal ctags. am I doing something wrong?
i navigate to my project directory and type "aider" and it loads up, and I get this:
(aider) ➜  pricer git:(main) ✗ aider .
Model: gpt-4
Git repo: .git
Repo-map: basic using 1024 tokens (universal-ctags not found)
Use /help to see in-chat commands.

Thanks for trying aider. Sorry to hear you're having trouble getting ctags to work with it.
You need to install ctags, not just clone the universal-ctags repo. On OSX, you can usually install it with brew uninstall universal-ctags.
Here is some more info from the universal-ctags repo:
https://github.com/universal-ctags/homebrew-universal-ctags
Basically, you're in business if you can run ctags --version from your shell and get output like this:
$ ctags --version
Universal Ctags 6.0.0, Copyright (C) 2015-2022 Universal Ctags Team
...

I'm going to close this issue for now. Feel free to re-open it if you're still having problems.


XRay Remote Service Name is always "Remote"

I am in the process of customizing brave and putting into the production system but I came across a problem.
Despite of creating my interceptor with hardcoded labels, it always displays remote in the console. I could not find time to check it but seems there is a bug at there. I might give a try tomorrow to find culprit.

This issue was moved to openzipkin/zipkin-aws#58

moved because the mapping logic is in zipkin-aws (the xray reporter converts the objects, including mapping names)


Fix translating lea with RIP relative register

This allows the lifting of instructions like
0x703E42C    4C:8D15 3D2D2DFB    lea r10,qword ptr ds:[0x2311199]

 | | 0000: [ PSEUDO ]     +0x0     movq     rip          0x703e433
 | | 0001: [ PSEUDO ]     +0x0     movq     t1           0x0
 | | 0002: [ PSEUDO ]     +0x0     addq     t1           rip
 | | 0003: [ PSEUDO ]     +0x0     addq     t1           -0x4d2d2c3
 | | 0004: [ PSEUDO ]     +0x0     movq     t0           t1
 | | 0005: [ PSEUDO ]     +0x0     movq     r10          t0
 | | 0006: [ PSEUDO ]     +0x0     vexitq   -0x1

This shouldn't be necessary as RIP is considered a generic register, but I'm doing some tests myself to make sure this is the case.

Seems to work fine without this patch after switching the submodule to the experimental branch.

I didn't realize there is a experimental branch. The main issue was that RIP is not considered a physical register in this branch, but thanks for letting me know.

Yeah - that was my fault. This repo should've been on the experimental branch by default.


Take CanEqual in Scala 3 build for assertResult and should/mustEqual matcher

Hi Chee Seng,
In the Scala 3 build let's take CanEqual in assertResult and "should equal" matchers.
assertResult is here
https://github.com/scalatest/scalatest/blob/3.2.x-new/jvm/core/src/main/scala/org/scalatest/Assertions.scala#L863
and here
https://github.com/scalatest/scalatest/blob/3.2.x-new/jvm/core/src/main/scala/org/scalatest/Assertions.scala#L842
We'll need to change the signature in Scala 3 so that it takes L and R type params. So the signature would be:
scala> def myAssertResult[L, R](expected: L)(actual: R)(implicit prettifier: Prettifier, caneq: CanEqual[L, R]) = if expected == actual then succeed else throw new Exception(s"Expected $expected, but got $actual")
def myAssertResult
  [L, R]
    (expected: L)
      (actual: R)
        (implicit prettifier: org.scalactic.Prettifier, caneq: CanEqual[L, R]):
          org.scalatest.compatible.Assertion

scala> myAssertResult("hello")(Option("hello"))
1 |myAssertResult("hello")(Option("hello"))
  |                                        ^
  |Values of types String and Option[String] cannot be compared with == or !=

scala> myAssertResult("hello")("hello")
val res2: org.scalatest.compatible.Assertion = Succeeded

scala> case class Apple(size: Int)
// defined case class Apple

scala> case class Orange(size: Int)
// defined case class Orange

scala> myAssertResult(Apple(42))(Orange(42))
java.lang.Exception: Expected Apple(42), but got Orange(42)
  at rs$line$8$.myAssertResult(rs$line$8:1)
  ... 38 elided

scala> import scala.language.strictEquality

scala> myAssertResult(Apple(42))(Orange(42))
1 |myAssertResult(Apple(42))(Orange(42))
  |                                     ^
  |         Values of types Apple and Orange cannot be compared with == or !=

Similar thing for shouldEqual and mustEqual.
It may be more tricky for a should equal (b), a should not equal b, a shouldNot equal(b). See how far you can take it to those. There are also anded and ored uses of those that we should test.
Thanks.
Bill

@cheeseng by the way this one we should do in 3.2.x-new.

@bvenners Fyi I have submitted the following PR for assertResult, shouldBe and mustBe:
https://github.com/scalatest/scalatest/pull/2002
For shouldEqual/mustEqual, they currently already takes an implicit Equality[T], I am not sure if adding another CanEqual will be a good idea.
I can still continue with 'should be' and 'must be', not sure about 'should not be' and 'must not be', probably not a good suit I think.


Incorrect montage view plotting only a subset of channels

Describe the bug
Plotting only a subset of the channels included in a Montage results in a corrupted plot.
@cbrnr probably related to this https://github.com/mne-tools/mne-python/pull/4276?
Steps and/or code to reproduce
import mne

montage = mne.channels.read_montage(
        kind='standard_1020', ch_names=['Fz', 'Cz', 'Pz'])
mne.viz.plot_montage(montage=montage)

Expected results
I would have expected a plot showing the positions of "Fz", "Cz" and "Pz"
Actual results

Additional information
Platform:      Windows-10-10.0.16299-SP0
Python:        3.7.3 (default, Mar 27 2019, 17:13:21) [MSC v.1915 64 bit (AMD64)]
Executable:    C:\Continuum\anaconda3\pythonw.exe
CPU:           Intel64 Family 6 Model 142 Stepping 10, GenuineIntel: 8 cores
Memory:        15.9 GB
mne:           0.18.dev0
numpy:         1.16.2 {blas=mkl_rt, lapack=mkl_rt}
scipy:         1.2.1
matplotlib:    3.0.3 {backend=Qt5Agg}
sklearn:       0.20.3
nibabel:       Not found
mayavi:        Not found
cupy:          Not found
pandas:        0.24.2
dipy:          Not found

Thanks for the report -- closing as duplicate of #5190 and #3987. Proposal for fixing here and WIP PR in #5472, feel free to take over if possible!


mavros: 0.18.5-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository mavros to 0.18.5-0:

upstream repository: https://github.com/mavlink/mavros.git
release repository: https://github.com/mavlink/mavros-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.23
previous version for package: 0.18.4-0

libmavconn

No changes

mavros
* lib: update ArduPilot modes
* Contributors: Randy Mackay

mavros_extras

No changes

mavros_msgs

No changes

test_mavros

No changes

That release introduce new APM modes: QuadPlane and Copter.
https://github.com/mavlink/mavros/pull/633


Validate bolt11 string before trying to pay it

...using decodepay and making sure decoding is possible.
Today, the bolt11 string is validated when calling ln_pay, but if it is not valid, lnurl only knows ln_pay failed but doesn't know it's because the bolt11 is invalid.  We must not save the invalid bolt11 in the database because if fallback is executed, it checks first to see if a payment has been done on the bolt11 (with ln_listpays) but this returns an error if it is invalid.  And lnurl won't take any chance and will refuse to fall back the payment on chain to avoid paying twice.

Current workaround when this happens: update LnurlWithdrawEntity set bolt11=null where lnurlWithdrawId=nnnn


Initial documentation for applicationInstance cmdlets

Added documentation for the following applicationInstance cmdlets:

Set-CsOnlineApplicationInstance
New-CsOnlineApplicationInstance
Get-CsOnlineApplicationInstance

OPS Build status updates of commit 571503b:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 571503b:
:clock10: Incremental building: average incremental building time is 12 min(s) 23 sec(s)

OPS Build status updates of commit 571503b:
:clock10: Incremental building: average incremental building time is 12 min(s) 23 sec(s)

OPS Build status updates of commit 571503b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 0ade58a:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

@islubin and @tomkau for visibility on this PR.

OPS Build status updates of commit 0ade58a:
:clock10: Incremental building: average incremental building time is 12 min(s) 23 sec(s)

OPS Build status updates of commit 0ade58a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit c4c1e7b:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit c4c1e7b:
:clock10: Incremental building: average incremental building time is 12 min(s) 23 sec(s)

OPS Build status updates of commit c4c1e7b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 5a951b5:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 5a951b5:
:clock10: Incremental building: average incremental building time is 12 min(s) 24 sec(s)

OPS Build status updates of commit 5a951b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 6b2d323:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 6b2d323:
:clock10: Incremental building: average incremental building time is 12 min(s) 24 sec(s)

OPS Build status updates of commit 6b2d323:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit e1c2ae5:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit e1c2ae5:
:clock10: Incremental building: average incremental building time is 12 min(s) 24 sec(s)

OPS Build status updates of commit e1c2ae5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit b4818b1:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit b4818b1:
:clock10: Incremental building: average incremental building time is 12 min(s) 26 sec(s)

OPS Build status updates of commit b4818b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit ec6d421:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit ec6d421:
:clock10: Incremental building: average incremental building time is 12 min(s) 26 sec(s)

OPS Build status updates of commit ec6d421:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit ce7ea4f:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit ce7ea4f:
:clock10: Incremental building: average incremental building time is 12 min(s) 26 sec(s)

OPS Build status updates of commit ce7ea4f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Any chance of nedb becoming available for IndexedDB

Thanks a mil

As of v1.4, NeDB automatically selects the best method to persist data on the browser (IndexDB then WebSQL then localStorage), so the limit is removed. WARNING: it's not back compatible with v1.3, but that should not be a major issue as user apps can resync entirely.


AWS ALB Ingress is not recoginized and route53 record is not being created

I am using AWS ALB Ingress Controller -
https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.1.2/docs/examples/alb-ingress-controller.yaml
it is able to create alb and I was manually modify the Route53 record to get access to the service.
According to the doco, https://github.com/kubernetes-incubator/external-dns/blob/master/docs/faq.md
I have put the following annotation in my ingress config -
external-dns.alpha.kubernetes.io/target: test.example.com
Also the following in my service config - my service is NodePort
external-dns.alpha.kubernetes.io/hostname: test.example.com
kubectl get ing shows like the following -
NAME                    HOSTS                  ADDRESS                                                                       PORTS     AGE
promethus-alb-ingress   test.example.com dda10ba4-xxx.ap-southeast-2.elb.amazonaws.com   80        1h
External dns logs of the pod shows the following -
time="2019-05-23T06:22:23Z" level=info msg="config: {Master: KubeConfig: RequestTimeout:30s IstioIngressGatewayServices:[istio-system/istio-ingressgateway] Sources:[service ingress] Namespace: AnnotationFilter: FQDNTemplate: CombineFQDNAndAnnotation:false IgnoreHostnameAnnotation:false Compatibility: PublishInternal:false PublishHostIP:false ConnectorSourceServer:localhost:8080 Provider:aws GoogleProject: DomainFilter:[example.com] ZoneIDFilter:[] AlibabaCloudConfigFile:/etc/kubernetes/alibaba-cloud.json AlibabaCloudZoneType: AWSZoneType:public AWSZoneTagFilter:[] AWSAssumeRole: AWSBatchChangeSize:1000 AWSBatchChangeInterval:1s AWSEvaluateTargetHealth:true AWSAPIRetries:3 AzureConfigFile:/etc/kubernetes/azure.json AzureResourceGroup: CloudflareProxied:false CloudflareZonesPerPage:50 RcodezeroTXTEncrypt:false InfobloxGridHost: InfobloxWapiPort:443 InfobloxWapiUsername:admin InfobloxWapiPassword: InfobloxWapiVersion:2.3.1 InfobloxSSLVerify:true InfobloxView: InfobloxMaxResults:0 DynCustomerName: DynUsername: DynPassword: DynMinTTLSeconds:0 OCIConfigFile:/etc/kubernetes/oci.yaml InMemoryZones:[] PDNSServer:http://localhost:8081 PDNSAPIKey: PDNSTLSEnabled:false TLSCA: TLSClientCert: TLSClientCertKey: Policy:sync Registry:txt TXTOwnerID:default TXTPrefix: Interval:1m0s Once:false DryRun:false LogFormat:text MetricsAddress::7979 LogLevel:info TXTCacheInterval:0s ExoscaleEndpoint:https://api.exoscale.ch/dns ExoscaleAPIKey: ExoscaleAPISecret: CRDSourceAPIVersion:externaldns.k8s.io/v1alpha1 CRDSourceKind:DNSEndpoint ServiceTypeFilter:[] CFAPIEndpoint: CFUsername: CFPassword: RFC2136Host: RFC2136Port:0 RFC2136Zone: RFC2136Insecure:false RFC2136TSIGKeyName: RFC2136TSIGSecret: RFC2136TSIGSecretAlg: RFC2136TAXFR:false NS1Endpoint: NS1IgnoreSSL:false TransIPAccountName: TransIPPrivateKeyFile:}"
time="2019-05-23T06:22:23Z" level=info msg="Created Kubernetes client https://<IP_ADDRESS>:443"
time="2019-05-23T06:22:26Z" level=info msg="All records are already up to date"
time="2019-05-23T06:23:26Z" level=info msg="All records are already up to date"

I noticed the same issue.
I had to use external-dns.alpha.kubernetes.io/hostname: instead of external-dns.alpha.kubernetes.io/target: in the ingress config to get it working.

Same issue here.

@free8gent Sorry did not help. Which image for external-dns are you using. I am using -
image: registry.opensource.zalan.do/teapot/external-dns:latest

I am using this:
alb-ingress-version:
image: docker.io/amazon/aws-alb-ingress-controller:v1.1.2
external dns version
image: registry.opensource.zalan.do/teapot/external-dns:v0.5.9
make sure the args configured to do ingress and the domain:
        - args:
          - --log-level=info
          - --domain-filter=test.domain.com
          - --policy=upsert-only
          - --provider=aws
          - --registry=txt
          - --interval=1m
          - --source=service
          - --source=ingress

ingress resource annotation
external-dns.alpha.kubernetes.io/hostname: my.test.domain.com
logs from external-dns
time="2019-06-17T19:41:00Z" level=info msg="Desired change: CREATE my.test.domain.com A"
time="2019-06-17T19:41:00Z" level=info msg="Desired change: CREATE my.test.domain.com TXT"
time="2019-06-17T19:41:01Z" level=info msg="2 record(s) in zone test.domain.com. were successfully updated"

@free8gent  Thanks but does not work in my case, it works with nginx controller.

It is also not working for me


AttributeError: 'Mapper' object has no attribute 'x' on longer column filter chains longer

This seems to be a new behavior in 1.5.0, and a regression from 1.4.2.
I have an admin view that has a column filter that looks like this "order.product.sku":
class ItemView(AuthenticatedModelView):
    column_filters = ('order.userid', 'order.email', 'order.product.sku')

Tracestack:
[..]
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/contrib/sqla/view.py", line 329, in __init__
    menu_icon_value=menu_icon_value)
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/model/base.py", line 782, in __init__
    self._refresh_cache()
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/model/base.py", line 903, in _refresh_cache
    self._refresh_filters_cache()
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/model/base.py", line 811, in _refresh_filters_cache
    self._filters = self.get_filters()
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/model/base.py", line 1113, in get_filters
    flt = self.scaffold_filters(n)
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/contrib/sqla/view.py", line 617, in scaffold_filters
    is_hybrid_property = tools.is_hybrid_property(self.model, name)
  File "/home/pi/.virtualenvs/myenv/lib/python3.4/site-packages/flask_admin/contrib/sqla/tools.py", line 200, in is_hybrid_property
    attr = getattr(last_model, names[i])
AttributeError: 'Mapper' object has no attribute 'product'

Can you show me how the Item and Order models is defined?

Sorry for the delay, here's a stripped down model:

class Item(db.Model):
id = db.Column(db.Integer, primary_key=True)
created_at = db.Column(db.DateTime, default=datetime.datetime.utcnow)
order_id = db.Column(db.Integer, db.ForeignKey('order.id',
                                               onupdate="CASCADE",
                                               ondelete="CASCADE"),
                     nullable=False)

class Product(db.Model):
id = db.Column(db.Integer, primary_key=True)
name = db.Column(db.String(128), nullable=False)
sku = db.Column(db.String(128), nullable=False)
class Order(db.Model):
id = db.Column(db.Integer, primary_key=True)
timestamp = db.Column(db.DateTime, nullable=False,
default=datetime.datetime.utcnow)
product_id = db.Column(db.Integer, db.ForeignKey('product.id',
onupdate="RESTRICT",
ondelete="RESTRICT"),
nullable=False)
product = db.relationship('Product', backref='orders', )

Can't seem to reproduce the problem...
Can you provide a complete minimal example that isn't working for you?

Ok, I dug down a little bit and narrowed it to the way the relationship is defined between models:
#works
class Product(db.Model):
    id = db.Column(db.Integer, primary_key=True)

class Order(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    #items = db.relationship('Item', backref='order', passive_deletes="all")

class Item(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    order_id = db.Column(db.Integer, db.ForeignKey('order.id', onupdate="CASCADE", ondelete="CASCADE"),
                         nullable=False)
    order = db.relationship('Order', backref='items')

#no longer works:
class Product(db.Model):
    id = db.Column(db.Integer, primary_key=True)

class Order(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    items = db.relationship('Item', backref='order', passive_deletes="all")

class Item(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    order_id = db.Column(db.Integer, db.ForeignKey('order.id', onupdate="CASCADE", ondelete="CASCADE"),
                         nullable=False)
    #order = db.relationship('Order', backref='items')

# the view with the filter that's causing the exception
class ItemModelView(AuthenticatedModelView):
    column_filters = ('order.product.sku', )

I might also be doing something wrong, and it just happened to work before 1.5.0. Please advise.

The example is not complete - order has no product member, product has no sku member...
When I tried to configure it myself last time, it just worked.
So I'm gonna have to ask to you to provide a complete example. Something I can copy and run.

Nevermind, I'll just work around the issue.
Thanks!

Here's a working example of this error which I saw: https://github.com/bepetersn/flask-admin-example1. Not sure what the error means, maybe you want to look into it. However, on further playing with this, I discovered how to do what I needed to do. I had this:
    model = Job
    column_display_pk = True
    # Including this filter breaks
    column_filters = ('order_id', 'order.location.name', )

I changed to this:
    model = Job
    column_display_pk = True
    # Including this filter breaks
    column_filters = ('order_id', 'order.location', )

and order.location.name became an available filter.


Cleanup KNIs

I believe either nff_go_stop or flow.StopPort be calling rte_kni_release on each of the rte_kni* in low.h’s kni[MAX_KNI] array.

Fix by https://github.com/intel-go/nff-go/pull/510, can you please check, that fix is enough?

LGTM. Thanks!


[Community] Super-secret task ZconV

[redacted]

Panel arranged with Wallet Teams reps.
Pre-recording scheduled.


What would be the possiablity of C#?

How viable would a trimmed down version of C# be?
Could it even be made to work with rust's safety features?

I think it would be more difficult as we'd need to build the ffi bindings ourselves, as far as I can see there's no mlua equivalent for C# yet

@makspll how does mlua have to do with C#?
I mean using a trimmed down version of C# for a scripting language in bevy.
There is also ZeroSharp but that means writing your own core lib.


test error

Traceback (most recent call last):
File "tools/extract_results.py", line 59, in
main()
File "tools/extract_results.py", line 34, in main
results.append([fid] + [float(x) for x in res_info.split(':')[-1].split(',')])
File "tools/extract_results.py", line 34, in
results.append([fid] + [float(x) for x in res_info.split(':')[-1].split(',')])
ValueError: could not convert string to float: ' Evaluating voc_2007_test_all1 using 2007 metric. Note that results do not use the official Matlab API.'

The script automatically gets the test results from the log file's last line. Please double-check whether there is an error in the testing process causing no test results in the log file to resolve this issue.


Using succeeded() in Template Expressions

Description
I have a job in a template that depends on a preceding job as well as a template parameter:
parameters:
  runTests: true

# omitted for brevity

- job: "Test"
  dependsOn: "Build"
  condition: ${{and(parameters.runTests, succeeded())}}

I'm trying to use the succeeded() job status function within a template expression to ensure that the job only runs if "Build" succeeded and "runTests" is true. Unfortunately, it seems like this isn't allowed - the job "Test" fails with an error message stating that "succeeded" is invalid.
I've tried
and(${{parameters.runTests}}, succeeded())

as well.
Is there a way to evaluate parameters and job status functions in a single boolean expression?

No, the ${{ }} expressions are evaluated when compiling the plan.
It sounds like this is what you want:
parameters:
  runTests: true

- ${{ if eq('true', parameters.runTests) }}:
  - job: "Test"
    dependsOn: "Build"

No, the ${{ }} expressions are evaluated when compiling the plan.

Ah okay I get it now. Yeah the conditional insertion is what I needed, somehow didn't occur to me that they can be used for jobs. Thanks for the tip!
Link to documentation on conditional insertion for anyone else with similar issues.


Update code samples

Forgot to update code samples along with #40. This is them.

Also, if you don't mind, could you add this to the to-do list somewhere?
* Killing / restarting a shard [needs clarification](http://discordjs.guide/#/sharding/additional-information)
* Update `Reflect.defineProperty()` and prototyped methods to use `.findOrCreate()`/`.findOrBuild()` instead of manual checks
* Fix code style inconsistency in the Sequelize pages
* Fix wording style inconsistency in the Sequelize pages (e.g. using "we" instead of "you")

Probably under a section titled "Fixes" or something.


Fix minor translation error on french localization file

Minor fix for french localization.

@olivier-monaco I noticed you've updated the locales for non-English languages. These will be overwritten during the sync from our translation tool Crowdin. If you'd like to contribute your translations, please visit https://crowdin.com/project/gitea. Please revert the changes done on these files. :tea:


Removes unused GuestContainer.container_id attribute

It was assigned to, but never read. Removing it simplifies load() method, which should be helpful in the longrun.

/packit retest-failed

Perhaps squash the one-liner?

Perhaps squash the one-liner?

Sure, will use squash and merge.


add watermark metrics

This solves #310
Adding 4 new metrics: Disk allocation watermark high, low, flood_stage and disk threshold_enabled.
Metrics support both types of disk allocation watermarks - size in bytes and in percent (shown in label of the metrics).

I add support on this feature. This is an highly needed metric for the monitoring of a production cluster. This allow a clean monitoring state of the ES cluster disk usage status without the need to create host dependent disk usage alarms which is painfull with multiple cluster using different watermark levels.

Would love this feature too (at least percentage) so we can have dynamic alerting threshold based on configured wattermarks and not arbitrary static ones.

I rebased and removed the 3rd party dependency. Also solved the issue with value in bytes/ratio/percents watermark by two types of metrics - that will be collected according to type of watermark value.


transition

Can the order of the images be arranged according to the order of the picture names? Because of the animation to make slides, the current animation is not perfect.
eg:http://t.cn/Rr8DrXi
eg2:http://t.cn/Rr8kUPT ,
The animation of the sina icon is correct and qq is incorrect because there is one more icon between the qq icons.
合成图片时的顺序能否根据图片名顺序排列？因为要做滑过的动画，目前的动画不完美。
sina图标的动画是正确的，qq的不正确，因为qq图标间多一个图标。

Unfortunately, the binary-tree layout doesn't offer much in terms of sorting. There are a couple options here:

Switch to the left/right or top/down layout algorithms

https://github.com/twolfson/gulp.spritesmith/tree/6.9.0#algorithms

Provide a custom layout algorithm and use that


Two questions related to testing

Hi, trying to figure out how to do this:
https://formidable.com/open-source/urql/docs/advanced/testing/
And (probably less related to this lib, but still) this:
https://storybook.js.org/addons/@urql/storybook-addon
Couldn't find any info(i'm using v2.1.0).
Any clues?
The only option i see now is mocking fetch using jest-mock-fetch.. but just wanted to make sure i'm approaching this correctly.

Ok, answered the second one myself. for anyone reaching this later:
https://github.com/draftbit/bs-storybook now supports CSF, which supports passing params. so this works:
component->CSF.addMeta(
  ~name="Name of comp",
  ~parameters={
    "urql": () =>
      {
        "data": {
          "query_name": data,
        },
      },
  },
  (),
)

Still can't figure out the best approach to mock reason-urql though

Hey @BlueHotDog! Interesting questions, and ones I haven't actually considered before. Let's start with the testing piece.
So, the type of the urql Client instance, t, is abstract. For this reason, I think it'll be difficult to follow exactly what the urql docs present, because we can't just mock executeQuery, executeMutation, etc. in a record and hand it to Provider — it needs to be of type Client.t.
To start out, I would try creating a client and mocking its methods with %%raw, calling jest.spyOn(client, 'executeQuery').mockImplementation(() => never) (or however you want to mock this). For example:
it("mocks the Client", () => {
  let client = Client.make(~url="https://localhost:3000", ())
  let never = Wonka.never

  %%raw(`
    jest.spyOn(client, 'executeQuery').mockImplementation(() => never);
    jest.spyOn(client, 'executeMutation').mockImplementation(() => never);
  `)

  // Mounting your component and asserting here.
})

In terms of asserting on the mock calls methods themselves, bs-jest unfortunately doesn't seem to have matchers for toBeCalled, and even the MockJs module is experimental. So, I'd recommend forcing states as recommended in the urql docs and asserting on component output rather than mock calls.
I know it's not a super satisfying solution, but hopefully a useful starting point!

Thanks @parkerziegler
I'm very happy of writing my own bindings(god knows that's a prerequisite using rescript :) ). Just wanted to see if i missed something before rolling my own.
Also, maybe we can add a MockContext component that'll accept such arguments?

@BlueHotDog Yep, that's definitely a solid idea. Something to the effect of:
type mockClient = {
  executeQuery: MockJs.fn,
}

@module("urql") @react.component
external make: (~value: mockClient, ~children: React.element) => React.element = "Provider"

Going to close this for now, but feel free to reopen if there's more that isn't working here or if this seems unachievable in user-land and we can chat further. Thanks!


Error on 3.5.0-rc.3 arangod.exe auto-upgrade-start with 3.4.x database folder

My Environment

ArangoDB Version:        3.5.0-rc.3
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:  Manual Start
Configuration:               No changes
Infrastructure:
Operating System:        Windows 10
Total RAM in your machine:        32Gb
Disks in use:        SSD
Used Package:              Windows win64 zip Package

Component, Query & Data
Affected feature:
Upgrade

Size of your Dataset on disk: 42Gb
Steps to reproduce

Start .\arangod.exe --database.auto-upgrade true

Problem:
A error message is shown, although the upgrade was successful and the process ends:
2019-06-21T13:45:30Z [7536] ERROR [fae2c] {rocksdb} RocksDB encountered a background error during a compaction operation; The database will be put in read-only mode, and subsequent write errors are likely

I don't know whether the exit of the process is intentional, but since the upgrade did run well, maybe there should be no ERROR message. A normal start (.\arangod.exe) after the upgrade ran well and let me insert documents (no errors and no read-only mode in the new process).
Expected result:
No error message.

Hi @x3cion,
the exit of the arangod process with option --database.auto-upgrade true is intentional once the database upgrade has finished. Afterwards the same arangod command without option --database.auto-upgrade true has to be executed to startup the server again.
However it is not expected that the stated error message occurs during the upgrade. I was not able to reproduce this error when performing a 3.4.6-1 -> 3.5.0-rc.3 upgrade on a database directory with some sample data.

Do you have a backup of your 3.4.x database directory, that can be used to reproduce this error?
Which 3.4.x version did you use when performing the upgrade?
Since performing the upgrade, did you see any errors in the log?

Hi @x3cion,
Since we have not heard back from you in a while, I am closing this issue for now.
If this issue persists, please reply to my latest comment and we will reopen it.


[WIP] add conan dependencies

Description
Manage internal dependencies with conan. #977

gtest/1.8.1
nlohmann_json/3.7.0
protobuf/3.9.1
boost/1.74.0

Testing instructions
tools/generate-files
conan install -if build --profile=conan/profile .
cmake -H. -Bbuild -DCMAKE_BUILD_TYPE=Debug -DCODE_COVERAGE=ON
make -Cbuild -j12 tests TrezorCryptoTests

Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[x] Prefix PR title with [WIP] if necessary.
[x] Add tests to cover changes as needed.
[ ] Update documentation as needed.
[x] I have read the guidelines for adding a new blockchain
[x] If there is a related Issue, mention it in the description (e.g. Fixes #<issue_number> ).

tools/install-dependencies failed, we need to build two protobuf plugins

I'm trying to make this work #1109 .  Protobuf building is put back, but currently I have some issues with installing conan itself.
 Successfully installed Jinja2-2.11.2 MarkupSafe-1.1.1 PyJWT-1.7.1 PyYAML-5.3.1 bottle-0.12.18 certifi-2020.6.20 chardet-3.0.4 colorama-0.4.3 conan-1.29.2 deprecation-2.0.7 distro-1.5.0 fasteners-0.15 future-0.18.2 idna-2.10 monotonic-1.5 node-semver-0.6.1 packaging-20.4 patch-ng-1.17.4 pluginbase-1.0.0 pygments-2.7.1 pyparsing-2.4.7 python-dateutil-2.8.1 requests-2.24.0 six-1.15.0 tqdm-4.49.0 urllib3-1.25.10
/home/runner/work/_temp/93f1c9f0-4c3c-4f40-a9f3-1739a0a8ad34.sh: line 8: conan: command not found

@catenocrypt Sorry for the long answer, the problem is in the canon installation path. I'm trying to resolve this issue.

@catenocrypt @hewigovens Why don't you use cmake to xcode build ? Are there any restrictions?
cmake -G Xcode ..  should work.

@stracedude we do compile iOS lib with cmake (see tools/ios-build), iOS tests and some other helper classes are in swift folder

@hewigovens @catenocrypt
The problem is that it is not possible to use canon with swift in the current form.
In ios-ci run tools/ios-test, it use project.yml, build protobuf, link json and boost from cpp.xcconfig. I can't embed conan here.
I see 2 ways:

add xcode generator in conan, create conanbuildinfo.xcconfig  and use it in project.yml. Simple solution. But I have no experience in this. https://docs.conan.io/en/latest/integrations/ide/xcode.html
build the swift framework and its test with cmake. A complex solution, but beautiful - with a single build system.
https://cmake.org/cmake/help/v3.6/release/3.4.html

@stracedude let's keep protobuf as it is now? for swift framework, we will adopt swift package manager later, no plan to step back to conan or cmake (so we can try out new apple toolchain easily)

Is it possible to keep protobuf as it is for swift, but use conan for C++?  I guess not as both are handled in install-dependencies.

@hewigovens @catenocrypt  Yes, I think it will work, need to make the build stages independent. I will try to do this in the next few days.

<3AhLfoVCK1UcA8VjCDu6r1ZQTLEdVq3LPc>

Summarizing the status:

Which pkgs can be managed with conan?
boost, nlohman_json, gtest, and protobuf <-- last one is questionable

How often did we update them?  Maybe once per year each; update is likely imposing other changes even if managed with conan

What extra dependencies are needed in the development environment?
Python (not used so far), conan.

Other issues
Integrating in iOS pipeline

--> Looking at the costs (ios issues, extra deps) and benefits (smoother dependency version update) I would skip this for now.  Open for discussion, @hewigovens , @stracedude .

let's skip this then, we might need a simple script to check latest versions of our dependencies


Move the poems to a database

Instead of storing the poems in text files and running the analysis each time, load the entire data object into a database.

poems
poets
meters

rhyme_schemes?

We can add rhyming schemes later, to flag the rhymes that don’t work according to a pattern.

Works in local and in Travis CI
Doesn't work in Heroku, probably because it doesn't like sqlite


Complete KITTI output services

Complete services... add frame count param to enable function to limit output.

This functionality is to be replaced/refactored with ODE services


Zend Framework 3 Update

All Zend Framework packages have been updated, but no new major framework version has been tagged.

Thanks for the PR

My apologies, I mis-read Zend blog post. I went in and checked the individual component repositories and, while they support php 7.1 and 7.2, they are also still supporting php 5.6. I'll keep watching the zend projects for when they drop php 5.6 and 7.0.

No problem at all :+1:
I myself caught into similar complicated posts about PHP version bumps.


Low FPS even with few particles

There are scenarios (e.g., leave Ex Machina preset running for several minutes) where the FPS will drop low (15ish FPS on my 2020 M1 MBP) yet it won't recover even if I change Burst Size to 1 and Burst Delay to 60. The number of pixels will drop to less than 100 but the FPS does not improve.

This does not always replicate, however.


Idea: Make factory paths configurable

Just found this project, and it looks pretty cool. It would be cool if it was possible to specify the path where you want factories to be located.
For example, i put all my factories under a Factory namespace.
module/Application/src/Application/Factory/Controller/IndexControllerFactory
module/Application/src/Application/Factory/Service/UserServiceFactory

@Danielss89
Thanks for your request.
But to be honest, I personally think, that keeping all factories in a special path is a bad practice. You need to build the same directory tree under your module/Application/src/Application/Factory/ path that you already have under module/Application/src/Application/. To handle this and the current way of keeping classes and factories in the same directory will need additional configuration or command flags.
So I am sorry, I won't implement this in the near future due to limited free time. If this request is supported by significant number of users, it might come some day. But for now I will close this.


std calculation

I don't think this matters much, but you're calculating the per channel std without the global mean you precalculated. (donkey.lua line 193). This is incorrect, but assuming you wanted to do it like this, you could collapsed the mean and std loop into a single one instead of doing two. The proper way would be to calculate the std using the previously calculated mean. However, I don't think this will change much in practice.

you are right, does not matter much in practice but it's wrong. if you do a PR, will welcome it, but wont fix it myself. I've moved on to a more compact 400 line version that I wrote, which I like a bit more.


Contribution of Corda Interopability

There is additional contribution of Corda Interoperability from Accenture to be merged into Github (pending Open Source scanning closure).

Fixed by https://github.com/hyperledger-labs/blockchain-integration-framework/pull/35


BLD: Adds versioneer

closes #216

Awesome!  What's the change with the travis emails?

every time travis runs your branch it emails you the response. I personally dislike this behavior. if we don't to disable it that is fine

Looks great. Kinda unfortunate we have to save versioneer.py in the repo itself. +1 on not emailing.

Looks good to me then.  Agreed @twiecki - I suppose it needs to be bootstrapped somehow...

Merged with https://github.com/quantopian/pyfolio/commit/3f11250c932ff023ba96d3530e0eff88a2afa96b. Thanks @llllllllll and @richafrank.

Kinda unfortunate we have to save versioneer.py in the repo itself.
This is how versioneer is intended to be used. The versioneer install script vendors itself into the project.


Add more if cases for the first character of the username

Closes: #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Eject on Windows

Windows started automatically remounting drives after fwup exited. This is really annoying so now there's eject code.

Coverage remained the same at 85.926% when pulling 25ff8379cb9b572fdf183f59845303d5222f775d on windows-eject into 62ebaa2b1a984a3f94acc9d9b49de855b000d7c6 on master.


Fix linting issues on CSS files

The intention here was greater consistency, all errors were triggered by 'stylelint'.

Remove duplicate properties
Add missing semicolons
Whitespacing where required, like spacing between properties and values (ie. 'color: red')
New lines whenever necessary
Remove empty lines whenever necessary
Correct indentation
New line at the end of file

The background for this change is that I was looking into moving relevant styles from E-porto to Hedwig, but saw that Stylelint was flashing red on many files. So I thought I might as well fix these.

Great, thanks! 👍


Why is enable() not a function?

I'm using TypeScript and I have the following:
let debug = require('debug')('mytest');
debug.enable();

Which causes a JS error stating that debug.enable is not a function.
However this works:
debug.enabled = true;

What am I doing wrong?

What makes you think loggers have an .enable() method?

@Qix- I apologize, I pasted the wrong version of my code. I just updated it.

Loggers don't have an enable method. Only the top-level debug module does.
const debugMod = require('debug');
debugMod.enable('mytest');
const debug = debugMod('mytest');

Though this is an anti-pattern. You should really, really be using the DEBUG environment variable.

Thanks for the clarification, got it now.
FWIW, I'm using enable because docker requires that you build a brand new container from an image to change the environment variables. To me this isn't an acceptable way to turn debugging on or off.

You can declare environment variables at run time.
docker run -ti --rm -e 'DEBUG=myapp:*' some/image

Yes I know, that’s declaring it during container creation from an image.

Yep, is there a problem with that? Docker containers are meant to be destroyed and re-created.


As a auditree user I want basic check to ensure that objects in the repo are compliant.

Issue description / feature objectives
For auditree current workflows have oscal objects inserted into the repo with plant. Each of these objects should have an auditree check to ensure that the objects are compliant with the current version of the OSCAL schema.
Completion Criteria

[ ]

Expected Behavior
Actual Behavior

@alfinkel - as discussed.

At this point in time not a priority.

My understanding of the current roadmap for auditree is that it will remain 'control agnostic'. Without a current clear roadmap closing until internal discussion is resolved.


Error getting - The JSON-RPC connection with the remote party was lost before the request could complete.

Getting the error The JSON-RPC connection with the remote party was lost before the request could complete.
from model builder error window
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.JsonRpc.d__162.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.JsonRpc.d__151`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.<b__92_0>d.MoveNext()

I also encountered this issues.

I also encountered this issues when I clicked the start training button.

Good news, after updating the ML model, I successfully completed the training
https://marketplace.visualstudio.com/items?itemName=MLNET.ModelBuilder2022

i am facing this issue, i am running Microsoft Visual Studio Professional 2022 (64-bit) - Version 17.11.5 and my ML.NET Model Builder version is <IP_ADDRESS>5601
Also, i noticed that, error comes only when i try to train image classification model using GPU, when i train using CPU this error is not coming and training completed successfully.


[v2.9.20] Bad Gateway

Script
nginx-proxy-manager
Describe the bug
No matter if I upgrade fron v2.9.19 or do a fresh install I get the well known "Bad Gateway" error when trying to log in via the webinterface.
System info:

Proxmox Version: 7.3-6
Debian Version: 11

Screenshots
If applicable, add screenshots to help explain your problem.

I have the same problem.
The system log says that the signals module was not found.
Mar 16 13:02:39 lxc-tmp systemd[1]: Starting Nginx Proxy Manager...
Mar 16 13:02:39 lxc-tmp systemd[1]: Started Nginx Proxy Manager.
Mar 16 13:02:39 lxc-tmp node[7028]: node:internal/modules/cjs/loader:1024
Mar 16 13:02:39 lxc-tmp node[7028]:   throw err;
Mar 16 13:02:39 lxc-tmp node[7028]:   ^
Mar 16 13:02:39 lxc-tmp node[7028]: Error: Cannot find module 'signale'
Mar 16 13:02:39 lxc-tmp node[7028]: Require stack:
Mar 16 13:02:39 lxc-tmp node[7028]: - /app/logger.js
Mar 16 13:02:39 lxc-tmp node[7028]: - /app/index.js
Mar 16 13:02:39 lxc-tmp node[7028]:     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Function.Module._load (node:internal/modules/cjs/loader:866:27)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Module.require (node:internal/modules/cjs/loader:1093:19)
Mar 16 13:02:39 lxc-tmp node[7028]:     at require (node:internal/modules/cjs/helpers:108:18)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Object.<anonymous> (/app/logger.js:1:19)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Module._compile (node:internal/modules/cjs/loader:1191:14)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Module.load (node:internal/modules/cjs/loader:1069:32)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Function.Module._load (node:internal/modules/cjs/loader:904:12)
Mar 16 13:02:39 lxc-tmp node[7028]:     at Module.require (node:internal/modules/cjs/loader:1093:19) {
Mar 16 13:02:39 lxc-tmp node[7028]:   code: 'MODULE_NOT_FOUND',
Mar 16 13:02:39 lxc-tmp node[7028]:   requireStack: [ '/app/logger.js', '/app/index.js' ]
Mar 16 13:02:39 lxc-tmp node[7028]: }
Mar 16 13:02:39 lxc-tmp systemd[1]: npm.service: Main process exited, code=exited, status=1/FAILURE
Mar 16 13:02:39 lxc-tmp systemd[1]: npm.service: Failed with result 'exit-code'.
Mar 16 13:02:39 lxc-tmp systemd[1]: npm.service: Scheduled restart job, restart counter is at 1.
Mar 16 13:02:39 lxc-tmp systemd[1]: Stopped Nginx Proxy Manager.

an npm install signals says:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/knex
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/objection
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

unfortunately, I don't know npm well enough to fathom the problem here.

Looking further at the logs, it seems that signale being missing is a red herring. I fixed the signale issue (well, fudged it, but enough for that to no longer error) and now the major complain is that sqlite3 is missing.
This is also backed u by running any yarn command, which attempts to fix/rebuild missing dependencies each time, always failing on sqlite3
I've never used Alpine or yarn before trying to get this container setup going, so have insufficient knowledge to diagnose further.

Good news with the new version (2.9.21) everything works again.

Confirmed

Fixed in nginx-proxy-manager (upstream);
https://github.com/NginxProxyManager/nginx-proxy-manager/commit/fec36834f7dbc2f1bfcbbfddf942939d564429a8

Updated objection, knex, liquidjs, signale and sqlite3 packages

Changes for objection migration
Moved common access template code to an include
Fixed access rules configuration generation
develop (#2703)
v2.9.21
@jc21
jc21 committed yesterday


Fix VK_EXT_debug_utils inconsistency

Fixes #660

For the deprecation message, vk.xml uses the following: Backwards-compatible alias containing a typo. I don't think we should use exactly that, but something like it has my preference.

Also, can you double-check if intradoc links in deprecation messages now work?

Even after fixing the reference (must be prefixed by Self:: or DebugUtils::) they still don't work:

Can you remove the [] link brackets around it, and add () at the end of the name?

@BeastLe9enD Also, after targeting 0.37-stable feel free to submit a new PR removing the functions entirely for master (with appropriate changelog item). I'll sort out the changelog on master when we eventually perform a 0.37 release.

Since this hasn't been rebased on 0.37-stable (only the target branch was updated) I'll cherry-pick it to that branch (like I do with any other PR for now, however inconvenient that workflow may be) and push a commit to master that removes the deprecated functions entirely.


Fix UserWarning: Overriding existing custom namespace 'dp' (on 'Expr')

On #1614:

src/opendp/polars.py:7
  .../opendp/python/src/opendp/polars.py:7: UserWarning: Overriding existing custom namespace 'dp' (on 'Expr')
    @pl.api.register_expr_namespace("dp")

Fix the warning.
Configure pytest to fail on warnings.

This was a temporary issue due to git doubling registration code.


Fix compatibility with omniauth-oauth 1.4+

Re-implements callback_url removed by omniauth/omniauth-oauth2#70

oops, dupe of #4 :)


Latex serializer/output mode

Adds output mode --output latex, which serializes the AST to LaTeX.

@dwightguth for serializing k terms, I don't plan to use the latex attribute, but to just emit the klabel names. The idea is that as another pass you will tell K to emit the latex prelude for you, which will add in all the newcommand definitions needed to make the definitions valid. If you don't supply a latex attribute, it will generate some sensible newcommand for you, but if you do supply it it will directly use that.
So, given the following definition:
syntax Exp ::= Int | Bool
            | Exp "+" Exp
            | Exp "<=" Exp [latex(#1 \le #2)]

So if you run something like krun --gen-latex-prelude, it will produce the following latex prelude:
\newcommand{\klabelPlus}[2]{#1 + #2}            // auto-generated based on the production
\newcommand{\klabelLTEQ}[2]{#1 \le #2}        // use the user-supplied one

And you serialize the term 3 + 4 <= 8 with --output latex, it will produce (without the prelude):
\klabelLTEQ{\klabelPlus{3}{4}}{8}

This means that --output latex can be a strict serializer to abstract LaTeX ASTs, and leaves all the decisions about how to display things to the newcommand declarations. This will make it much easier to uniformly fiddle with the resulting display of the document when doing final touches by just changing the generated \newcommand declarations.

Oh I see. That makes sense, actually. This is good enough for now, then. We can improve it if it becomes necessary.


Entry exit analytics availability date change

@alfergus Can we please also add a statement to this change: "These details are available for journeys published (or updated) after the preview is enabled. "  I am not sure how to recall and update the PR.

Hi @vinayd-msft and @bishalgoswami, I can do the change but I need to know what the specific 'details' are you are referring to. Where in the change do you want to include the additional statement? At the end? Just want to get this accurate.

Should be at the end, I expanded "These details" based on your feedback. The updated note will read like this:
Entry and exit details are in preview. If you don't see these details, go to Settings > Feature switches > Journey and enable the "Tile entry and exit analytics (preview)" feature switch. This feature is currently available for one-time journeys with static audience. Support for repeating journeys is planned by December 16, 2024. Support for Ongoing journeys will be available in Feb 2025 release. Entry and exit details are available for journeys published (or updated) after the preview is enabled.

Should be at the end, I expanded "These details" based on your feedback. The updated note will read like this:
Entry and exit details are in preview. If you don't see these details, go to Settings > Feature switches > Journey and enable the "Tile entry and exit analytics (preview)" feature switch. This feature is currently available for one-time journeys with static audience. Support for repeating journeys is planned by December 16, 2024. Support for Ongoing journeys will be available in Feb 2025 release. Entry and exit details are available for journeys published (or updated) after the preview is enabled.

I went ahead and updated this. Thanks, Vinay!


Add an additional jar for Spark local run

To run spark in local, there are some libraries which need to be added. common-text jar is missing in the list. Without this jar, you will not able to see Application Detail UI. Tested from my side, after adding this library able to see the Application Detail UI page.
Following this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [HOP-XXX] - Fixes bug in SessionManager,
where you replace HOP-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the commit message.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install apache-rat:check to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using git rebase -i.

Trivial changes like typos do not require a JIRA issue (javadoc, comments...).
In this case, just format the pull request title like (DOC) - Add javadoc in SessionManager.
If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[ ] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
[ ] In any other case, please file an Apache Individual Contributor License Agreement.

Will take a look to see if we can add it as a default jar or if it indeed needs to be added to the guide.

Will take a look to see if we can add it as a default jar or if it indeed needs to be added to the guide.

Thanks.

Added the library to the release, so this doc change is no longer needed.
change here: https://github.com/apache/hop/pull/1682/commits/8e54ad51e7a4b284374a00f4caab3900eab031dc


Callback URL mismatch in e-mail notifications (port missing)

Affected module
Does it impact the UI, backend or Ingestion Framework?
It impact the UI and backend
Describe the bug
E-mail notification has callback URL, derived from backend environment settings (OM_URI).
Eventually, port number in callback URL lost in templating.
To Reproduce
For example:
docker compose exec -ti openmetadata-server bash -c set | grep -E 'OM_URI|OPENMETADATA_SERVER_URL'
OM_URI=' "http://localhost:8585/"'
OPENMETADATA_SERVER_URL='""'
but, in e-mail message I got the 'reset link', pointing on http://localhost/
Expected behavior
'reset link' pointing on http://localhost:8585/
Version:

OS:  Linux <IP_ADDRESS>-microsoft-standard-WSL2
Python version: 3.8.10
OpenMetadata version: 1.2.0
OpenMetadata Ingestion package version:  openmetadata-ingestion==1.2.0

To reproduce issue step by step:

git clone https://github.com/vitaly-zverev/OpenMetadata.git issue_13930
cd issue_13930 && git switch issue_13930_Callback_URL_mismatch
docker compose -f docker/docker-compose-quickstart/docker-compose-postgres-carbonio.yml up -d
docker compose -f docker/docker-compose-quickstart/docker-compose-postgres-carbonio.yml exec -ti carbonio /opt/zextras/bin/zmprov createDomain openmetadata.org
docker compose -f docker/docker-compose-quickstart/docker-compose-postgres-carbonio.yml exec -ti carbonio /opt/zextras/bin/zmprov createAccount<EMAIL_ADDRESS>P@ssw0rd
Open http://localhost:8585/forgot-password and submit form for<EMAIL_ADDRESS>Open https://localhost/carbonio, login as admin/P@ssw0rd and check mail
We can see 'Reset link', pointed on 'http://localhost/users/password/reset?user=admin...'

hi @vitaly-zverev this should be fixed in upcoming version, setting openmetadata_url -> this is used to generate the url OM_URI is removed


[Bug]: /artifacts/build.sh times out attempting to load .dockerignore & Dockerfile

Description
Using Coolify Cloud & v4.0.0-beta.323
All deployments are suddenly stuck loading at & time out after a long while:
[2024-Aug-20 10:05:11.823831] ----------------------------------------
[2024-Aug-20 10:05:11.833426] Building docker image started.
[2024-Aug-20 10:05:11.839621] To check the current progress, click on Show Debug Logs.
[2024-Aug-20 10:05:17.033470]

[COMMAND] docker exec jw4k848wo8s0og0k8kgo08s8 bash -c 'bash /artifacts/build.sh'
[OUTPUT] #0 building with "default" instance using docker driver  #1 [internal] load .dockerignore
[2024-Aug-20 10:05:26.929672]

[COMMAND] docker exec jw4k848wo8s0og0k8kgo08s8 bash -c 'bash /artifacts/build.sh'
[OUTPUT] #1 ...  #2 [internal] load build definition from Dockerfile

Revalidating server works fine but doesn't fix the issue. I've raised this issue in the Discord and one more user has the same sudden issue so far.
Minimal Reproduction (if possible, example repository)
Deploying any Dockerfile on Coolify Cloud (tried Nixpacks aswell)
Exception or Error
No response
Version
v4.0.0-beta.323
Cloud?

[X] Yes
[ ] No

Your disk is probably full. Can you please check?
The next version of Coolify will have a fix for the automated docker cleanup job.

Looks like disk still has some space available:
filesystem      Size  Used Avail Use% Mounted on
udev            7.8G     0  7.8G   0% /dev
tmpfs           1.6G  2.8M  1.6G   1% /run
/dev/vda1       310G  118G  193G  39% /
tmpfs           7.9G     0  7.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/loop0       64M   64M     0 100% /snap/core20/2182
/dev/loop1       64M   64M     0 100% /snap/core20/2318
/dev/loop2       92M   92M     0 100% /snap/lxd/24061
/dev/vda15      105M  6.1M   99M   6% /boot/efi
/dev/loop3       40M   40M     0 100% /snap/snapd/21184
/dev/loop4       39M   39M     0 100% /snap/snapd/21759
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/7ba1faa39a6ac5dabf2f2c2fac5677a0ebe580ecb654a252d929be72203c6643/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/01a7d46c016c38c01670bb722f48cd33574267b2390d24a12de9b133cf97e951/merged
/dev/loop5       92M   92M     0 100% /snap/lxd/29619
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/3d772f546dd4eb603c40a7e4fbbecc21b289d33eb30ba3b354f18243fa8e37d3/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/0f3721b4f55feb89340f39c8ebf615803dd408f5154bd56ce0e070400191c76e/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/eb872e21f48069e8b92c28b8993f366603e47221b06f4a09a3ea399c1e8117db/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/f7a3ddbe0791bede45fd61ebd53434bd27309b530c46264030e103e2abd9edb7/merged
tmpfs           1.6G     0  1.6G   0% /run/user/0
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/8ad36a85765469dff0fd03aa03d2ed0cf734d29988b4bd70f3dda74c306484cc/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/d99ef68cebf6c624e124cdbf9a46cd57c7f3d31594549b311a22c10e54719067/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/3ac46da71a71e6853321ea6855ef95968d4e4d3f0f74a7cd2421c871fb8cce65/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/b3ffcfcb7e9e3a3cecfc5033d2a1ca8074417c3fe715b7d0e00791175f26d986/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/89ee4cada862b4dafd1d0660ba9b9961ccac150f83158de03012e6a3bab40bee/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/70f89420c1febca13586b70389f71e9763b49ea46e81774c63638ffda4ad4cbd/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/d179198c9ebb4ebd0518a2f34aa748ccb5482e03a0f67362de55bbda10a89b3b/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/7a3fae7d7e71a81514b8d0b41143f5ebcc07720a793a3ed127596aaa8d158aa7/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/dde7752463e0e6c5e7ccf54e45986731bcca45e154331d834bd7ce4589d9897e/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/bd069e4a582f5ca84e1f80a78c1d618f94d89c4f0c9d71e26c7157da393c1fd3/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/bec2253093f5a06312c8178af76f91dfbc06ddc818f7724c8a1470877d78048c/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/a8d339756f30d67dea2c803f23184ec49a7e443d0cad0e5a8308aa590ea69a36/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/7ad524f43d8f5a70ac531f58cfcba3193a54a5a6ef10a56be3164b0d32f562c0/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/483bd5941fbd5cd5ee1bbd9ef8d1b43911681ca2067ed3b771534db678c45a23/merged
overlay         310G  118G  193G  39% /var/lib/docker/overlay2/8138a2f20297451449cd5526650092f62a57a3a86fa66a1c1d16f43d2f6ce5d7/merged

I had a similar issue, and resolved it by adding swap space to my server. Turns out I was running out of memory.

Thank you @CodeCooler
I've just tried adding swap space following this guide https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-20-04
But no luck fixing this issue. I will restart the docker engine now as Andreas suggested to me.

I ended up having to completely remove docker & having coolify reinstall it.
Maybe this setting should be enabled by default @andrasbacsai? To prevent this issue from happening - I had about 100G of old docker files.

Hey, I am facing the same issue. Stuck at "load .dockerignore"
Using docker compose and beta 323
My disk is not full, and I have enabled force cleanup.
root@svr-muc1-doc-kubminion-001:~/.ssh# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             32G     0   32G   0% /dev
tmpfs           6.3G  4.6M  6.3G   1% /run
/dev/md0p1      900G  585G  270G  69% /
tmpfs            32G     0   32G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/008ce4afaa5e6539f7c318a160dae45f5531b41f43701b1bf50b89c1adde25f2/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/b71997adc631846ae5bb7dc4fb2f65aecf67c32bdc5e2bb988030dfc49476866/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/51cb076558dd6607ecd97843f1911484fa02d4f07a8cc6e904f8ce0df2ccfb01/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/4c775e2278b10048c17384989d91630ed3ca71848a0c906c46b87f8b3b8a8445/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/dc30412d311cdbe3c3f3328006d59759c96cc44bd7526731a0395814ed4be25f/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/a385b62e03a5ce784861e155eef6d0cb7aca1c73543d81601e0623d3ee07db82/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/f892e172a39197c16eb3b427ac134f4e7fd13545ecd080d497a2031d70195881/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/2dbfce0bafa80ad8b353f871fe675916c1b3afae3d2adcd3f6c1e943a697cbc6/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/89aa12c9c28f6c973cc5e25f8e9ccb5b9202e20533316eb45b4beac68a6d2855/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/10ebd3502d50beb5fc1276fa8e188f56e900fe9997433bfd35bd9e8dca3d1ddc/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/8e9c28f5cec932c8d905bfae829e77bc21e0f06051eb036f7bc9de9c2ceaf8c9/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/d46402ad3e37f94a82b03f5d8ffd30689a147729ff3afcc92c9a5f38dd574257/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/de3f82bd2eca7c465dafdd1be39d8d5e39c5d68e4ef0271d9c1ec25bfb1a2a46/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/9bd11899c6b3233cfd5ca1402d19eab81a4387dd99f355d80b1b202fcb563d76/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/af9afbc98b184757fd56523344a70870c6956873d91d36b02c1e017790b55bd2/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/e0c7dab4a1582977f4bd09e16f0bd25aeecc4e7018d31eaae269f09ae7c87f5d/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/d5fbf1ff4d4aafbaecdedc66d7412b942328d37741d754005d930f9f0ecaa059/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/a84b4ad8904d6fa547a454af7ada2798a04675213fe0317b2552037726c9a5e0/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/fb8ff8151d9ed0b341676c359f524e85a2ff8858a8cc3297550920921636c3b7/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/380e1c3376e671247489b1e41e4ddca2365ec411953e6e0b743f781457dcd211/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/7e06cca3f4ccf5a60e0f1f0c9a7d973fbdb85751d9a59eaf0cd7924c01160bdf/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/81964f5437672273409fe4a6b0d5c171ef6d4a43710237996683a32241d6637f/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/2d39d823e4ef0cd4dd909a9e5980ecc46e3df971da606acec303ef91d7e4e59d/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/f39df1611e8f5dc7c03805f4df43193415fdad78265d5bc98758af1fbb5d0b50/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/3464180aff1eeb24d4347dc498b9b8b4df12e08d09973232237430c16bc685d0/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/985bbc7386b19ca7dc710744a8a427ae6690be5b15da1f33d80d974a75ee43c3/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/cc419de097ed663687879370308fb02bde4801fc4f001b9038f80ce69606013d/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/80219c028a070688684fd08f3bed444ca3c8f44b42101f7394460bc270ff3f57/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/76088cec4fbee0678de0db2022383ae106339b6e98d6f8fc5aa26db2c5bc7f4b/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/fba9b26204dfc4789e5fe42253025da84d60629d2c48f9b4d8fd4898865460bb/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/3ba9e2a9ef3111253afe28a7bec9ee8552bdce002680376d80c3ef55e3182bb5/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/835f595b5592119ab5d9df1af2d7e5bf02ab304d0b231fde03a109fb851a0ffd/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/2e107347fac73dce535e16fd766f8895b12ee12c6fe03d0571e9a2151b5976b4/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/74b101e4b26b1e5ab4f5e85c58ef5f9f9a2124e6ab116f941263e530d5e3435b/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/6695d5b8a6d4f7d51834d5af56c192b9944cd1fce8f4dd75f5280b3dba574f17/merged
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/606acf0c18a4598a4bcb01a49a3d02aaca6a4aa06be280661c7f69e1c25c5f7a/merged
tmpfs           6.3G  4.0K  6.3G   1% /run/user/1002
tmpfs           6.3G  4.0K  6.3G   1% /run/user/1000
overlay         900G  585G  270G  69% /var/lib/docker/overlay2/95139e10f88bae42f3f3a79cf67d1c059de80b10753a9a765eeac6f0086b928a/merged

@adaichendt-tv1 I was talking to Andreas about this issue on Stream some days ago and he mentioned that the only way to fix this right now is to restart docker.

oof, thanks for the tip!
this is a production ready environment, so restarting is not something I can do. It is our current docker machine which I added to coolify to orchestrate our containers from there in the future.
Is restarting a one-time fix or is there a possibility that I need to restart more frequently?
Do we have an understanding of the root cause? Could you perhaps link the timecode of the stream here for future documentation?

Same here @AndreasFaust
If your commands take forever, it's likely that your docker will also not restart - this happened to me and lead to having to reinstall everything, with downtime :(
Very worried it will happen again. @andrasbacsai did you possibly have a chance to look into this yet?

This is indeed worrying. I have multiple servers with multiple projects.
To reinstall everything would be painful.

I was able to restart the docker service recently, which resolved the problem. A simple systemctl restart docker.service. It causes downtime tho as all the containers will be restarted.

Thank you, that sounds promising!
So we assume Coolify has kind of a memory leak?

I'm not convinced this is a bug of coolify. It might just be something docker related. I don't have any insight into coolify tho, hence I was wondering about a timestamp of that stream where it was discussed to form a more complete picture of the root cause of this issue.

As I checked, the builder cache of Docker builds up to a certain point, even Docker cannot handle it. So you meed to restart Docker Engine, and then cleanup (docker builder prune) manually.
Probably Nixpacks fills up the cache this much. ☹

Thank you, @andrasbacsai !
Fortunately this is my only project using Nixpacks, if that’s the source of the problem.
But is there a way, to prevent this? Like Coolify providing a build-cache-monitor and warn before things get out of control?

… or a routine, that deletes the build cache, when it reaches a certain threshold?

I don't think the automated docker cleanup job is working properly. I just manually ran docker image prune -a and removed 40 gigs of images that were piling up again.

In the latest version, we changed the force cleanup to be automatic on every server by default.
Cloud will get the latest version soon.

@GautierT There will be a button in the next version so you can run the Cleanup with one click https://github.com/coollabsio/coolify/pull/3545

@biboc Yes, the Coolify docker cleanup process also cleans up the builder cache.

The problem is that this command also hangs though. Running this manually did not work in the cases that I and others were reporting.

Yes I heard there is a docker bug where only restarting helps not much we can do on our end.

But shouldn't the docker cache be cleared automatically by the job that coolify is running already? Or what could cause the cache to suddenly accumulate?
Andras mentioned a fix to the clean up job in one of his first replies. So this is possibly already fixed. Just haven't gotten an update on the cloud version yet since.

Yes it is fixed an cache will be cleaned by the coolify job if force cleanup is enabled or soon via a button click to run it manually. The problem is if build cache execeds a certain amount docker can not handel it anymore so the only fix is to restart docker. See the comment here https://github.com/coollabsio/coolify/issues/3150#issuecomment-2326573453

Having this same issue unfortunately with v4.0.0-beta.370...

I'm hitting this basically on every deployment now...restart works but it's not ideal i'm on v4.0.0-beta.370

I also hit this issue last night.  The server deployed in the morning and failed to deploy later in the day.
Tried to run the prune command, docker builder prune -af but it would not complete.
Forced the Docker service to restart, sudo systemctl restart docker, and it was able to.  Took about 2-3 minutes.  I then ran the prune command and it completed in 5 seconds or so.
The server is not critical but it will be a nuisance if this is a going concern.  It would be really nice if there was some number to watch to know when this is going to happen.  Ideally that number is tied to an automated fix or clean up that prevents me from seeing the problem.


[Wallet] Type safe navigate

Description
Following the upgrade to react-navigation which enables type safe navigation params, we still had our global navigate wrapper which wasn't checking navigation params.
This PR fixes it and caught a couple of small issues related to them.
Note: the default navigate method typing is slightly incorrect and won't catch when the parameters for a route are needed but they aren't provided.
See https://github.com/react-navigation/react-navigation/issues/7936
Our global navigate helper fixes that.
Other changes

Fix crash when opening the import wallet screen from the enter invite code screen during onboarding
Add getMockStackScreenProps helper to create both navigation and route props in a type safe way for tests.

Tested
Global navigate(...) calls are now type safe for the route name and its params!
Related issues
None.
Backwards compatibility
Yes.

nice work!


RPM: Videostream package seem not maintained anymore.

https://chocolatey.org/packages/videostream is bad checksums since many weeks/months.
I wrote to the maintainer privately, on his disqus wall and I opened an pull rtequest of his github.

Can I be added as a maintainer on the package now ?
Thanks in advance.

What is missing ?

Closing issue due to not following the template.
Please read the repository Readme.md file before opening any further issues.
Btw, the PROOF you show is a pull request to an unrelated repository, and not to the repository the maintainer of the package uses.
You also do not open an issue here to get added as a maintainer, it is an alternative when you do NOT want to be the maintainer.

Hi Kim,
Then can you point me in the right direction please ?

In which regard?
Opening an RFM request for this repository?
Or opening a pull request to the correct repository?
I assume the latter.
The pull request needs to go into https://github.com/CruzMarcio/au-packages, which is linked to on the package details page. Instead, you opened a PR to https://github.com/majkinetor/au-packages-template probably due to how the repository is set up. The repository you should have made the PR to is a fork of the latter repository, and as such, when you open the pull request, you need to select the correct repository, instead of relying on the defaults.
Even if it were the correct repository, no maintainer would have accepted it due to the number of commits in the pull request (probably due to opening on the wrong repository).
If you meant regarding opening an RFM request, then please read through the Readme.md and fill out the template when you create an issue based on Maintainer Request template (remember to also read the comments in that template).


Installation Information

Is your feature request related to a problem? Please describe the problem you're trying to solve.
I'm having trouble understanding this, but I suspect it's my very limited understanding of Ruby.  It would be useful thought to know general install instructions though.
What version of Ruby is this developed for? I'm using ruby 2.6.3p62 which isn't the latest (just what Mac's run with).
This seems to work:
$ bundle install
From there I think I should be able to run:
$ ./bin/site-inspector inspect whitehouse.gov -a
But that just gives me this error:
Traceback (most recent call last):
	5: from ./bin/site-inspector:8:in `<main>'
	4: from ./bin/site-inspector:8:in `require_relative'
	3: from /Users/mgifford/Documents/GitHub/site-inspector/lib/site-inspector.rb:75:in `<top (required)>'
	2: from /Users/mgifford/Documents/GitHub/site-inspector/lib/site-inspector.rb:35:in `cache'
	1: from /Library/Ruby/Site/2.6.0/rubygems/core_ext/kernel_require.rb:85:in `require'
/Library/Ruby/Site/2.6.0/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- site-inspector/cache (LoadError)

I've searched around to try to find ways around this but no luck....
Describe the solution you'd like
I'd like to have basic install instructions.

Try bundle exec ./bin/site-inspector inspect whitehouse.gov -a? Ruby can be a bit finicky with dependencies and it looks like site inspector's libraries aren't in ruby's load path when it's initialized.

That seemed to work in my Linux environment. Still working on getting it to work on a Mac, but this now is clearly not an issue with your scripts. Thanks @benbalter - appreciate the pointer.

Just wanting to add that it is also useful for me with 2021-analysis-of-federal-dotgov-domains is that it is useful to prepend bundle exec.  Without it I get:
$ ./script/crawl
Traceback (most recent call last):
        2: from ./script/crawl:6:in `<main>'
        1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- site-inspector (LoadError)

But it is working like a charm with the bundle exec.  Thanks.


Inline hyperlinking needs to be consistent

The inline hyperlinking needs to be edited for consistency. The following example illustrates:
Requirements and Installation Guides
Mattermost supports workplace messaging for teams using one to three servers with instructions available in the Install Guides section of this documentation. See Software and Hardware Requirements documentation for server sizing estimates.
The "Install Guides"  section is referenced in proper noun capitalization in the above example. It should be hyperlinked. One click drill downs are the hallmark of online documentation.

Hi @seenthattinker. I've taken a look through our Requirements and Installation Guides and wanted to confirm whether you're referring to a specific guide or the guides in general?
Here's one example of a guide with hyperlinks. If you'd be open to letting me know whether this is the correct guide or, if not, providing the link/s that'd be great.
You're also welcome to edit the docs in question and submit a pull request so that we can take a look at your changes and review them.
Thank you!

Hi @seenthattinker. I've reviewed the content and I'm not able to locate the exact location of the missing hyperlinks. The content or structure may have changed since this issue was opened. Please let me know if that is the case and, if so, if the issue has been resolved. :) Thank you!

This has been addressed by docs 2.0. Closing. :)


Avoid polluting C# generated type with _schemaName and _schemaFullName fields

In commit 46c96f4b381c851e15f5602e6abe8aa0a4919285, the fix for #140, two new class-level static fields _schemaName and _schemaFullName. These names now preclude a Bond type from using the name _schemaName elsewhere, like in a .bond file or in some other part of the partial class.
@sapek pointed this out:

It is better to avoid polluting user namespace. This disallow schemas that use _schemaName as a field name. What's worse, the user won't find out that is it disallowed until they try to codegen/build C#. It is also completely unnecessary, the calls to GetSchemaFullName could be easily generated insitu.
The fact that the names use underscore, which is conventionally used for internal names doesn't change anything. Bond schema language should allow users to design their schema with their meaning of internal fields that start with underscore.

We originally went with a static field to avoid computing the name on every ctor call.
I see a few different approaches to resolve this:

just call GetSchemaFullName to get the ctor argument
add a cache to GetSchemaFullName so that we don't recompute (and walk the type hierarchies) every time it's called

needs synchronization--either implicit (like Serialize's cache) or explicit

use an even uglier name like _bond_internal_afc485567

for robustness, the internal name prefix would need to be reserved in gbc

there might need to be multiple internal name prefixes, depending on the set of allowed identifiers in all the target languages

Picking between 1 and 2 will require some benchmarks to get a sense for how expensive GetSchemaFullName is compared to how expensive synchronization is. 3 is more code in gbc and some documentation. It's a well attested pattern in many languages, though not idiomatic C#.

We've re-opened #140, so this is now a duplicate of that.


Support \r carriage

Attempting to support \r without even make a compilation (triggering the tests a.k.a TDD)

Unfortunately we cannot replace any user data since it will mess up source maps. We need to solve that problem first.


Error adding sample data

What steps will reproduce the problem?
After installing and configuring demo (with sqlite) without changing anything, running vendor\bin yii fixture/add 20 produces error.
What is the expected result?
Fixture to add random data.
What do you get instead?
[ERROR] Maximum function nesting level of '256' reached, aborting!
Additional info

Q
A

Version
1.0.?

PHP version
7.4.3

Operating system
Win 10 x64

yii fixture/add 10 is working ok. The error comes from Cycle ORM mapper and it's dependency zendframework/zend-hydrator. Exception is thrown on this line from yii code.
I will debug it further and open issue on Cycle repository also.

I could not reproduce

Q
A

PHP version
7.4.3

Operating system
Win 10 x64

yii fixture/add 20 mySQL - ok, SQLite - ok
yii fixture/add 50 mySQL - ok, SQLite - ok

I've found the reason for the issue. xdebug extension has maximum level of function nesting, which can be increased (which is 256 by default). See this issue. Disabling xdebug fixed the problem.
You can reproduce the problem enabling xdebug for php-cli. It is always enabled in my case as I extensively debug also command line php.
Feel free to close the issue, or keep it open if you think there is a need to add a note somewhere.


Make rubber rounds research exclusive, but provide disablers.

About the PR

This PR removed the rubber rounds from security spawn loadouts, but provides them disablers instead. I decided to try this first after chewing on what position rubber bullets vs disablers play in the games combat, and after some discussions about whether rubber bullets are different enough from disablers or too difficult to balance using the same weapons as lethal rounds.
I think trying this first before anything more drastic is a good idea since it accomplishes two things. It makes the rubbers much less common and more of a research goal to match their effect in game of an upgrade to security's disabler tech. It also allows us to keep the entities in game while we wait on new med, which I am hopeful will give us some options to differentiate the two non-lethal techs with more less-than-lethal levers to pull like pain etc.
Why / Balance

Rubber bullets are in a weird spot currently. They're given out at round start while disablers are not, yet they are often more effective than disablers. This fixes that. They are also difficult to balance because they need to be considered along-side the use of lethal rounds in the same weapons. This kicks that can down the road slightly.
Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Security is no longer issued rubber bullets at round start.
tweak: Security is now issued Disablers at round start.

This kicks that can down the road slightly

go the mile and yeet it entirely.

I'm happy to do that, I just kind of expect us to want them once we have mew med stuff to play with which will actually differentiate them.
I could yeet the research for now, and then they wouldn't be acquirable. Would that be sensible? I guess we can always revert this PR later... hmmm.

Shit, I just finished a PR with all that. Should I just PR that or leave it to you?

Shit, I just finished a PR with all that. Should I just PR that or leave it to you?

Oh if you've got it, by all means, I can close.

#26470