text:
Regression of probe-rs run on nrf5340 (compared to v0.24.0)

Describe the bug
When trying to flash & run the application core of the nrf5340 using the latest main (probe-rs 0.24.0 (git commit: 849498d6)), Erase&Flash works as expected but probe-rs fails to run/attach to the application as follow:
$ cargo run
    Finished `dev` profile [optimized + debuginfo] target(s) in 11.53s
     Running `probe-rs run --chip nRF5340_xxAA --probe '1209:4853' --log-format oneline 'target\thumbv8m.main-none-eabihf\debug\rs-watch'`
 WARN probe_rs::session: Could not clear all hardware breakpoints: An ARM specific error occurred.

Caused by:
    A timeout occurred during an operation.                                                                                Error: The flashing procedure failed for 'target\thumbv8m.main-none-eabihf\debug\rs-watch'.

Caused by:
    0: Something during the interaction with the core went wrong
    1: An ARM specific error occurred.
    2: A timeout occurred during an operation.
error: process didn't exit successfully: `probe-rs run --chip nRF5340_xxAA --probe '1209:4853' --log-format oneline 'target\thumbv8m.main-none-eabihf\debug\rs-watch'` (exit code: 1)

To Reproduce
Steps to reproduce the behavior:
You need either a ZSWatch-HW or a nrf5340-DK

Clone https://github.com/igiona/rs-watch
Adapt/Remove the probe S/N in .cargo/config.toml
cargo run
watch it fail

Expected behavior
The application starts, probe-rs attaches and defmt-logs are displayed.
Desktop (please complete the following information):

Windows 11

Additional context
The same code runs as expected when using probe-rs v0.24.0 (installed via cargo binstall):
probe-rs 0.24.0 (git commit: 6fc653a)

@Dirbaio is this something you experience also on the nrf54 ?

Bisect result is point to:

$ git bisect bad
a4dd765487bcfa7f25027bd7daffbb57cf531248 is the first bad commit
commit a4dd765487bcfa7f25027bd7daffbb57cf531248 (HEAD)
Author: Robin Mueller 31589589+robamu@users.noreply.github.com
Date:   Thu Jul 11 12:48:28 2024 +0200

Halt core when flashing RAM (#2672)

changelog/added-core-halt-for-ram-flash.md | 1 +
probe-rs/src/flashing/loader.rs            | 9 +++++++++
2 files changed, 10 insertions(+)
create mode 100644 changelog/added-core-halt-for-ram-flash.md

Reverting the commit on main fixes this issue, so indeed this is causing troubles on the nrf5340.

Seems to me like we cannot halt the core. Why though?

Seems to me like we cannot halt the core. Why though?

From #2909 I'm somehow keen to think that halting one core, does halt the other as well and probe-rs kind of don't like/expect it?

For reference, this also happens with nrf9160 and nfr9161 (which makes sense because they both have nrf5340 inside).
Downgrading to v0.23.0 fixes the issue.

For reference, this also happens with nrf9160 and nfr9161 (which makes sense because they both have nrf5340 inside).

These chips don't have a nRF5340 inside. On the nRF5340, there is an application and a radio core, which both can be accessed.
The nRF9160 and 61 only have an application core.

Downgrading to v0.23.0 fixes the issue.

Does this mean that v0.24.0 is broken for you? Then this sounds like a different issue?

Thanks for the clarification.
I had the same issues of locked core when flashing with v0.24 (latest). I
had to 'manually' unlock it with --allow-erase-all  I downgraded to v0.23
and no more issue. So I suppose v0.24 is broken (Windows 10 native and
Windows 10 when flashing using WSL).
On Mon, Dec 9, 2024, 22:19 Dominik Boehi @.***> wrote:

For reference, this also happens with nrf9160 and nfr9161 (which makes
sense because they both have nrf5340 inside).
These chips don't have a nRF5340 inside. On the nRF5340, there is an
application and a radio core, which both can be accessed.
The nRF9160 and 61 only have an application core.
Downgrading to v0.23.0 fixes the issue.
Does this mean that v0.24.0 is broken for you? Then this sounds like a
different issue?
—
Reply to this email directly, view it on GitHub
https://github.com/probe-rs/probe-rs/issues/2930#issuecomment-2529501344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJLYXTP2QKTGIW7DZ4KETL2EYCM5AVCNFSM6AAAAABS2AEFOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRZGUYDCMZUGQ
.
You are receiving this because you commented.Message ID:
@.***>

Thanks for the clarification.
I had the same issues of locked core when flashing with v0.24 (latest). I
had to 'manually' unlock it with --allow-erase-all  I downgraded to v0.23
and no more issue. So I suppose v0.24 is broken (Windows 10 native and
Windows 10 when flashing using WSL).
On Mon, Dec 9, 2024, 22:19 Dominik Boehi @.***> wrote:

For reference, this also happens with nrf9160 and nfr9161 (which makes
sense because they both have nrf5340 inside).
These chips don't have a nRF5340 inside. On the nRF5340, there is an
application and a radio core, which both can be accessed.
The nRF9160 and 61 only have an application core.
Downgrading to v0.23.0 fixes the issue.
Does this mean that v0.24.0 is broken for you? Then this sounds like a
different issue?
—
Reply to this email directly, view it on GitHub
https://github.com/probe-rs/probe-rs/issues/2930#issuecomment-2529501344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJLYXTP2QKTGIW7DZ4KETL2EYCM5AVCNFSM6AAAAABS2AEFOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRZGUYDCMZUGQ
.
You are receiving this because you commented.Message ID:
@.***>

Could you give this a try?
cargo install probe-rs-tools -f --git https://github.com/igiona/probe-rs.git --locked --branch revert-halting-on-wr

?

authors: Tiwalun Yatekii igiona marcteys

repo: probe-rs/probe-rs


text:
Feature: Use two rows for showing column description

Is your feature request related to a problem? Please describe.
With lots of columns, space is usually scarce for several reasons (practically, technicall not) which makes colum descriptions to be truncated most of the time
Describe the solution you'd like
One day it clicked to me, why not simply have an option to expand the height of the top column (description) row to double height, so it would use the height of 2 standard rows as one.
Describe alternatives you've considered
None yet.
Additional context
Nope

Rows have fixed sizes for performance reasons.

source: gharchive/issue

authors: dmex ghost

repo: processhacker/processhacker

license: MIT

license_type: permissive

license_source: github-api


text:
Simple transitions to the Showcase Projects.

Here are some transitions which make the page look more decent. Does this look fine?
Changes:
Added some simple transitions to the Showcase Projects. I have already talked about this in the Forum
but was unable to get a response. Does this look good?

Thank you @pcgamer1 ! As a reminder, an issue needs to be opened before a pull request is opened, then you can tag the issue in the pull request. You can read more about it in the GitHub Issue Flow. This is necessary for tracking development and keeping discussion clear.
Also, the p5js.org/showcase page is currently only left for legacy reasons (so that existing links does not 404) from some previous decisions, so I will close this PR for now. We can re-open it in the future if we make new plans for the legacy showcase page.
Thanks again for implementing the transition!

source: gharchive/pull-request

license: mit

license_source: bigquery


text:
Add Active Support as dependency and require HashWithIndifferentAccess

References #18 .

@PatKoperwas can you merge when you want to accept this? I don't have write access to the repository.

repo: procore/ruby-sdk


text:
test-utils: Use different permutation module

JS-combinatorics has a number of issues when trying to use the work
inside a service, due to its variable interface (commonjs vs umd).
Switching to a simpler module should help with this issue.
Change-type: patch
Signed-off-by: Lucian Buzzo lucian.buzzo@gmail.com

@balena-ci rebase

authors: Ereski LucianBuzzo

repo: product-os/jellyfish-worker


text:
Remover dependências ao deletar um user para com school_unit.

Descrição
Esse PR remove dependências de deletar um user para com school_unit.
Conserta bug #169.
Checklist

[x] Código compila corretamente (Se aplicável);
[x] Mudanças realizadas foram testadas e passaram no testes (Se aplicável);
[x] Documentos gerados/atualizados (Se aplicável);
[x] Feito por conta própria (Se aplicável).

O motivo para isso estar acontecendo é bem simples.
No model user.rb temos as a seguintes linhas de codigo:
  has_one :school_unit,
    dependent: :destroy

O que essa linha diz é: user tem um school_unit, quando deletar um usuário, delete a school unit dele também.
Essa linha de código está errada em dois aspectos:

Não se deleta uma unidade só porque um usuário deve ser deletado.
Não existe a associação inversa de school_unit pertence a um user.

repo: proepidesenvolvimento/guardioes-api


text:
add a test for channel +n / -n

This is broken in Ergo's master apparently :-)

Ergo patch: https://github.com/ergochat/ergo/pull/2064

repo: progval/irctest


text:
AssertThatTypeDoesNotMatchTest.java:31-31: Improve test coverage and mutation...

The puzzle 47-de66b5c3 (from #47) in atom-codegen/src/test/java/oo/atom/codegen/bytebuddy/matchers/AssertThatTypeDoesNotMatchTest.java (lines 31-31) has to be resolved: "Improve test coverage and mutation coverage for {@link AssertThatTypeDoesNotMatch}"
The puzzle was created by Kapralov Sergey on 29-Sep-17.
Estimate: 15 minutes, role: IMP.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@skapral please pay attention to this new issue.

repo: project-avral/oo-atom


text:
#2 Move TH tests from backend

Merge first: https://github.com/project-chip/certification-tool/pull/219

Copy test collections from backend/test_collections
Change the backend volume mapping to use test_collections folder from TH

We don't want to move the matter program folder location anymore

repo: project-chip/certification-tool


text:
TLV tag use in SetupPayload does not seem to match spec

Problem
In SetupPayload.cpp we have:
bool IsCHIPTag(uint8_t tag)
{
    return tag >= (1 << kRawVendorTagLengthInBits);
}

bool IsVendorTag(uint8_t tag)
{
   return tag < (1 << kRawVendorTagLengthInBits);
}

but in the spec "5.1.4.1. Manufacturer-specific Elements" says:

Manufacturer-specific elements SHALL be tagged with context-specific tags that have semantics which are defined by the vendor for use in the products using their Vendor ID, and SHALL use tag values 0x80 to 0xFF.  Tag values 0x00 to 0x7F are reserved to indicate CHIP-common elements.

which seems exactly backwards from the code.
What exactly is going on here?  @shana-apple
Proposed Solution
Sort out what's going on, and fix or document to make it clear how this code and the spec interact.  Add tests as needed.

Suggest:
bool IsCommonTag(uint8_t tag)
{
return tag < 0x80;
}
bool IsVendorTag(uint8_t tag)
{
return tag >= 0x80;
}

@bzbarsky-apple  in initial spec the range of CHIP/Matter vs vendor was opposite and was changed . Maybe the code you found predates that change

Marked as spec.

authors: bzbarsky-apple leorozendaal tcarmelveilleux woody-apple

repo: project-chip/connectedhomeip


text:
[TC-TSTAT-2.2] - Results CONSTRAINT_ERROR instead Success

Issue : Results CONSTRAINT_ERROR instead Success when we tried to write occupied-cooling-setpoint
CommitID - fa8db560907713c555b06120658034e8c6ccea1a  (SVE-2 branch)
Expected behaviour : DUT expects Success
Actual behaviour : DUT results CONSTRAINT_ERROR
App used - thermostat-app
Steps to reproduce :

DUT side :

sudo rm -rf /tmp/chip_*
sudo ./chip-all-clusters-app

TH side

sudo rm -rf /tmp/chip_*
./chip-tool pairing ethernet 1 20202021 3840 fe80::e65f:1ff:fe0f:2753  5540
./chip-tool thermostat write occupied-cooling-setpoint -30  1 1
PFA Logs:
TSTAT-2.2_cntrl.txt

@chrisbeach59 please take a look?

This is expected behavior.

@chrisbeach59
Is the verification command correct here https://docs.google.com/spreadsheets/d/1h4d4J90KAxFqUL_cXZHyM3pHjHCEXzFITkQhN2KMqDY/edit#gid=1154794263&range=E130:G130 ??

@sowmyassp Interesting that it shows when setting the cooling setpoint to -30 that they show constraint error.  Which would expect.  So the short answer is that the VS step is quite wrong.   I would have expected to the first part of the step to have been
thermostat write occupied-cooling-setpoint 2600 1 1
I would recommend that thermostat cluster be tested with UI Automated testing.  It is critical to make sure the xml file matched the configuration of the thermostat cluster by ZAP

closing the issue per Chris's comment

authors: bzbarsky-apple chrisbeach59 cjandhyala sowmyassp


text:
[Platform] RPC console missing whl in artifacts

Reproduction steps / Feature
Rpc console packages is missing the tokenizer whl in the artifacts:

Traceback (most recent call last):
  File "/home/gtvchrome/venv/rpc_console/bin/chip-console", line 5, in <module>
    from chip_rpc.console import main
  File "/home/gtvchrome/venv/rpc_console/lib/python3.9/site-packages/chip_rpc/console.py", line 61, in <module>
    from pw_tokenizer.database import LoadTokenDatabases
ModuleNotFoundError: No module named 'pw_tokenizer'

### Platform

python

### Platform Version(s)

_No response_

### Type

Manually tested with SDK

### (Optional) If manually tested please explain why this is only manually tested

Error occurs while installing tool artifacts: `pip install out/chip-console-whl/*.whl`

### Anything else?

_No response_

@rgoliver Was this fixed by #22875?

authors: bzbarsky-apple rgoliver


text:
When I compile example/chi-tool on the Raspberry Pi, there is an error in the compilation

g++ -MMD -MF obj/commands/pairing/chip-tool.PairingCommand.cpp.o.d -Wconversion -O0 -g2 -fno-common -ffunction-sections -fdata-sections -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -Wall -Wextra -Wshadow -Wunreachable-code -Werror -Wno-unused-parameter -Wno-psabi -Wno-cast-function-type -fdiagnostics-color -fno-strict-aliasing -D_REENTRANT -isystem../../third_party/connectedhomeip/third_party/ot-br-posix/repo/src -isystem../../third_party/connectedhomeip/third_party/ot-br-posix/repo/include -I/usr/include/dbus-1.0 -I/usr/lib/aarch64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -std=gnu++14 -fno-rtti -Wnon-virtual-dtor -DCHIP_CONFIG_IM_ENABLE_SCHEMA_CHECK=1 -DCHIP_HAVE_CONFIG_H=1 -DLWIP_IPV4=1 -DLWIP_IPV6=1 -DLWIP_API=1 -DLWIP_ETHERNET=1 -DLWIP_SLIP=0 -DLWIP_6LOWPAN=1 -DLWIP_PPP=1 -I../.. -I../../third_party/connectedhomeip/src/app/util -I../../third_party/connectedhomeip/src/app -Igen/third_party/connectedhomeip/src/app/include -I../../third_party/connectedhomeip/src/include -I../../third_party/connectedhomeip/src -Igen/include -I../../third_party/connectedhomeip/src/lib -I../../third_party/connectedhomeip/config/standalone -I../../third_party/connectedhomeip/third_party/nlassert/repo/include -I../../third_party/connectedhomeip/third_party/nlio/repo/include -I../../third_party/connectedhomeip/src/lwip/standalone -I../../third_party/connectedhomeip/third_party/lwip/repo/lwip/src/include -I../../third_party/connectedhomeip/src/lwip/include -I../../third_party/connectedhomeip/src/setup_payload -Igen -Igen -I../../third_party/connectedhomeip/third_party/inipp/repo/inipp -I../../third_party/connectedhomeip/src/app/server -c ../../commands/pairing/PairingCommand.cpp -o obj/commands/pairing/chip-tool.PairingCommand.cpp.o
../../commands/pairing/PairingCommand.cpp: In member function ‘CHIP_ERROR PairingCommand::PairWithoutSecurity(Command::NodeId, Command::PeerAddress)’:
../../commands/pairing/PairingCommand.cpp:80:95: error: ‘CHIP_ERROR chip::Controller::DeviceCommissioner::PairTestDeviceWithoutSecurity(chip::NodeId, const chip::Transport::PeerAddress&, chip::Controller::SerializedDevice&)’ is deprecated: Available until Rendezvous is implemented [-Werror=deprecated-declarations]
80 |     return mCommissioner.PairTestDeviceWithoutSecurity(remoteId, address, serializedTestDevice);
|                                                                                ^
In file included from ../../commands/pairing/../../config/PersistentStorage.h:21,
from ../../commands/pairing/PairingCommand.h:21,
from ../../commands/pairing/PairingCommand.cpp:19:
../../third_party/connectedhomeip/src/controller/CHIPDeviceController.h:341:5: note: declared here
341 |     PairTestDeviceWithoutSecurity(NodeId remoteDeviceId, const Transport::PeerAddress & peerAddress, SerializedDevice & serialized);
|     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
[173/395] c++ obj/config/chip-tool.PersistentStorage.cpp.o
ninja: build stopped: subcommand failed.
Proposed Solution
<suggested fix, suggested enhancement>

My gcc version is：
g++ (Ubuntu 10.2.0-13ubuntu1) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
In file included from ../../third_party/connectedhomeip/src/platform/Linux/bluez/AdapterIterator.cpp:18:
../../third_party/connectedhomeip/src/platform/Linux/bluez/AdapterIterator.h:87:22: error: missing initializer for member ‘chip::DeviceLayer::Internal::AdapterIterator::::address’ [-Werror=missing-field-initializers]
87 |     } mCurrent = { 0 };
|                      ^
../../third_party/connectedhomeip/src/platform/Linux/bluez/AdapterIterator.h:87:22: error: missing initializer for member ‘chip::DeviceLayer::Internal::AdapterIterator::::alias’ [-Werror=missing-field-initializers]
../../third_party/connectedhomeip/src/platform/Linux/bluez/AdapterIterator.h:87:22: error: missing initializer for member ‘chip::DeviceLayer::Internal::AdapterIterator::::name’ [-Werror=missing-field-initializers]
../../third_party/connectedhomeip/src/platform/Linux/bluez/AdapterIterator.h:87:22: error: missing initializer for member ‘chip::DeviceLayer::Internal::AdapterIterator::::powered’ [-Werror=missing-field-initializers]
../../third_party/connectedhomeip/src/platform/Linux/bluez/AdapterIterator.h:87:22: error: missing initializer for member ‘chip::DeviceLayer::Internal::AdapterIterator::::adapter’ [-Werror=missing-field-initializers]
cc1plus: all warnings being treated as errors
[6/126] c++ obj/third_party/connectedhomeip/src/platform/Linux/libDeviceLayer.MdnsImpl.cpp.o
ninja: build stopped: subcommand failed.


text:
[nrfconnect] Fixed window covering bug in updating cluster attributes

Problem
Nrfconnect window covering example doesn't update window covering cluster attributes properly.
Change overview

Moved PostAttributeChange method from window-covering-server.cpp to header.
Called PostAttributeChange method in nrfconnect implementation of MatterWindowCoveringClusterServerAttributeChangedCallback
Changed mode default value from 0x14 to 0.

Testing
Reproduced manually tests described in: https://github.com/project-chip/connectedhomeip/issues/18371
Fixes: https://github.com/project-chip/connectedhomeip/issues/18371

Please hold on with the merge, we need to retest.

@kkasperczyk-no I was not asking you to modify the cluster code.  But I was asking for decent API docs on the API being added to the cluster, and that did not happen.....

@kkasperczyk-no I was not asking you to modify the cluster code. But I was asking for decent API docs on the API being added to the cluster, and that did not happen.....

@bzbarsky-apple sorry about that, I forgot to do the change after answering on your comment. Pushed followup PR: https://github.com/project-chip/connectedhomeip/pull/18840


text:
[EFR32] Fix/matter support pointer update

Update the submodule reference to the main branch with latest commit
Tested locally and verified

@Thirsrin it seems this needs conflict resolution.


text:
Fix RR-1.1 python test case, enable group testing

align the step number logs
enable groups acl beofre groups testing
align ACL targets parameters to values provided in test plan

Follow up to those changes: https://github.com/project-chip/connectedhomeip/pull/25789

Created PR to Test Plan to align the ACL's device types targets: https://github.com/CHIP-Specifications/chip-test-plans/pull/2511


text:
Address 9154 and CM/AC DNS-SD convergence

Problem
What is being fixed?  Examples:

Fix https://github.com/project-chip/connectedhomeip/issues/9154: DNS-SD commissionable node discovery does not time out
Fix SDK to address https://github.com/CHIP-Specifications/connectedhomeip-spec/issues/3805: DNS-SD fields - CM and AC fields are unnecessarily confusing, error prone

Change overview

add timers for commissionable node discovery timeout and extended discovery timeout
make extended discovery configurable per the spec, add shell commands for configuring
code to match latest DNS-SD commissionable node discovery changes (CM/AC convergence)

Testing
How was this tested? (at least one bullet point required)

tv-app and lighting app shell commands to toggle commissioning mode (disabled, basic, enhanced)
chip-tool to discovery and print out DNS-SD values

Does anyone recognize the cirque error?
otbr-agent[55]: [CRIT]-PLAT----: Init() at ../../third_party/openthread/repo/src/posix/platform/hdlc_interface.cpp:150: InvalidArgument
I've seen this on another PR recently, but I'm not familiar with that area of the code.
As far as I can tell, the cirque failure is unrelated to this PR. CRA/CRI change looks good. I'm less familar with the spec about the timing, but it looks correct from my reading.

I couldn't figure out why this would have anything to do with this PR. I'll check with the larger group on whether this is known

This PR broke commissioning ESP32 using chip-tool. ESP32 gets on the network and can be discovered but chip-tool never actually discovers it, and instead hangs until the whole process times out.
Repro:
chip-tool pairing ble-wifi   112233 20202021 3840

authors: chrisdecenzo mspang


text:
Fixed issue with Cost Details page showing incorrect charts

This change ensures the current group_by is reset whenever the parent's group_by is changed.
Fixes https://github.com/project-koku/koku-ui/issues/133

Deploy preview for project-koku ready!
Built with commit 4cbed8060a58a8975e544170b9fc4c49ce373b42
https://deploy-preview-134--project-koku.netlify.com

@dlabrecq I just merged https://github.com/project-koku/koku-ui/pull/132 - can you pull rebase to fix the ci problem?
I can tell that the travis failed because unit tests took ~12 minutes.

Codecov Report

Merging #134 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #134   +/-   ##
=======================================
  Coverage   89.26%   89.26%
=======================================
  Files         113      113
  Lines        1164     1164
  Branches      147      147
=======================================
  Hits         1039     1039
  Misses        114      114
  Partials       11       11

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6524eac...3e3c9df. Read the comment docs.

authors: boaz1337 codecov-io dlabrecq

repo: project-koku/koku-ui


text:
[NCL-7142] Allow user to specify sasl login option

The 2 new configs that the user can specify are:

saslMechanism
clientJaasConf

They are then sent to the KafkaLog4jAppender for more configuration.
These 2 configs specify the authentication option when talking with
Kafka.
See: https://docs.confluent.io/platform/current/kafka/authentication_sasl/authentication_sasl_plain.html for examples.

@thescouser89 woah that's so perfect! amazing! :100: :rocket: you're the best!

repo: project-ncl/quarkus-logging-kafka


text:
remove wrong market OXY/USDT

Please remove wrong market OXY/USDT because it is market for OXY/WUSDT pair. And there is the OXY/WUSDT market in list (please, check previous element in array).

Thanks for the PR. Fixed in 41d814d4d3fea082c6f9c9db401f2f09bb1370e4

authors: dmitrytarassov nathanielparke

repo: project-serum/serum-ts


text:
Data exhaust

For Raw telemetry exhaust. It should read from channel-exhaust backup instead of reading from raw backup.

Please raise a pull request against release-1.9 branch.

repo: project-sunbird/sunbird-analytics


text:
ログチャネルのクローズ処理の中で計算量が多すぎるという疑惑

ログチャネルのクローズ時に、次のコードが呼ばれる。1回のエポックで、数百のログチャネル
がクローズされるような状況ではO(n^2)のオーダーで、メモリオーダ、memory_order_seq_cst
でAtomic変数へのアクセスが行われる。これが、性能上問題ないか確認する必要がある。
for (const auto& e : log_channels_) {
    auto working_epoch = static_cast<epoch_id_type>(e->current_epoch_id_.load());
    if ((working_epoch - 1) < upper_limit && working_epoch != UINT64_MAX) {
        upper_limit = working_epoch - 1;
    }
    auto finished_epoch = e->finished_epoch_id_.load();
    if (max_finished_epoch < finished_epoch) {
        max_finished_epoch = finished_epoch;
    }

下記がvoid datastore::update_min_epoch_id(bool from_switch_epoch)のdisassemble結果（sourceとの対応有）で、問題とされているforは"===="で囲まれた部分ですが、「メモリオーダ、memory_order_seq_cstでAtomic変数へのアクセス」はどの機械語命令のことでしょうか？（）内は私が補ったコメントです。
なお、std::atomic_thread_fence(std::memory_order_acq_rel); でmfence命令が入ることを期待したのですが、入っていませんでした。memory orderを保証する別のメカニズムがあるのでしょうか？（最近のCPU事情には疎い．．．）
000000000002b810 <_ZN9limestone3api9datastore19update_min_epoch_idEb>:
void datastore::update_min_epoch_id(bool from_switch_epoch) {  // NOLINT(readability-function-cognitive-complexity)
   2b810:       f3 0f 1e fa             endbr64
   2b814:       55                      push   %rbp
    epoch_id_type max_finished_epoch = 0;
   2b815:       31 c9                   xor    %ecx,%ecx
void datastore::update_min_epoch_id(bool from_switch_epoch) {  // NOLINT(readability-function-cognitive-complexity)
   2b817:       48 89 e5                mov    %rsp,%rbp
   2b81a:       41 57                   push   %r15
   2b81c:       41 56                   push   %r14
   2b81e:       49 89 fe                mov    %rdi,%r14
   2b821:       41 55                   push   %r13
   2b823:       41 54                   push   %r12
   2b825:       53                      push   %rbx
   2b826:       48 81 ec e8 01 00 00    sub    $0x1e8,%rsp
   2b82d:       64 48 8b 04 25 28 00    mov    %fs:0x28,%rax
   2b834:       00 00
   2b836:       48 89 45 c8             mov    %rax,-0x38(%rbp)
   2b83a:       31 c0                   xor    %eax,%eax
   2b83c:       48 8b 5f 38             mov    0x38(%rdi),%rbx
    auto upper_limit = epoch_id_switched_.load() - 1;
   2b840:       48 83 eb 01             sub    $0x1,%rbx
   2b844:       48 8b 07                mov    (%rdi),%rax
   2b847:       48 8b 7f 08             mov    0x8(%rdi),%rdi
====
    for (const auto& e : log_channels_) {
   2b84b:       48 39 f8                cmp    %rdi,%rax
   2b84e:       74 29                   je     2b879 <_ZN9limestone3api9datastore19update_min_epoch_idEb+0x69>
   2b850:       48 8b 10                mov    (%rax),%rdx
   2b853:       48 8b 52 70             mov    0x70(%rdx),%rdx
        if ((working_epoch - 1) < upper_limit) {
   2b857:       48 83 ea 01             sub    $0x1,%rdx
   2b85b:       48 39 d3                cmp    %rdx,%rbx
   2b85e:       48 0f 47 da             cmova  %rdx,%rbx　（rdx: working_epoch - 1, rbx: upper_limit）
   2b862:       48 8b 10                mov    (%rax),%rdx
   2b865:       48 8b 52 78             mov    0x78(%rdx),%rdx　（0x78(%rdx): e->finished_epoch_id_をrdx: finished_epochに入れる）
   2b869:       48 39 d1                cmp    %rdx,%rcx　（rcx: finished_epoch、このcmpがif (max_finished_epoch < finished_epoch) に相当）
   2b86c:       48 0f 42 ca             cmovb  %rdx,%rcx
    for (const auto& e : log_channels_) {
   2b870:       48 83 c0 08             add    $0x8,%rax　（次のlog_channels_エントリへ）
   2b874:       48 39 f8                cmp    %rdi,%rax
   2b877:       75 d7                   jne    2b850 <_ZN9limestone3api9datastore19update_min_epoch_idEb+0x40>
====

authors: t-horikawa umegane

repo: project-tsurugi/limestone


text:
refactor(sync): use task scheduler

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

When syncing to an existing local repo, we may clobber "latest", do sane things and log

For a given/existing repo, sync and clients may both be writers to the same repo, so locking?

Recursive download of references (I expect two levels)

authors: peusebiu rchincha

repo: project-zot/zot


text:
CU-2fr23gk

add correct colors
cleanup

Task linked: CU-2fr23gk Add newm colors

authors: j-mateo martyu

repo: projectNEWM/newm-mobile


text:
Support for /32 floating IPv4s

Would like to be able to use Calico with Vultr's floating IPs. They are provided to the node as /32s. It works just fine to add the /32 to a dummy interface and have bird going. I think Vultr is not the only host to do this
Expected Behavior
When I add a /32 IPPool, I'd like to see it go through. Implementation details may be more troublesome but this "just works" fairly easily. The host just needs to reply to ARPs for the IP with its interface's MAC and should work as hoped.
Current Behavior
When adding a /32 IPPool, I get an error saying IPAM only supports /26 and larger.

This is fixed in master now - you can create IPPools between /20 and /32 (inclusive).
Will be available in Calico v3.3.

authors: caseydavenport teran-mckinney

repo: projectcalico/calico


text:
TCP connections are unstable & flaky. Getting java.net.SocketException: Connection reset intermittenly

##< BUG DESCRIPTION >
All services: java.net.SocketException: Connection reset .
-- > Getting too many RST's on established TCP connections .  This is highly intermittent .
conntrack is making a new connection as established but it was not created as part of TCP connection establishment, no SYN packet was seen. This causes packets on a valid connection to be send to a non existent TCP connection on port 1024.
Expected Behavior
TCP connection should not be abruptly dropped.
Current Behavior
TCP connections are getting dropped intermittently
Possible Solution
Packets which are marked invalid should get dropped
Steps to Reproduce (for bugs)
Execute the below script & observe the CONNTRACK entry on node & also collect the TCP dump
1.#!/bin/bash
i=0
while [ true ]
do
echo Count: $i
time curl  --header 'Accept: application/json' 'h{HTTPURL}/v3/resource/test/35'  -H "Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXXXXX" > /dev/null
i=$((i+1))
done
2.
3.
4.
Context
Your Environment

Calico version  -->>    Image:      docker.io/calico/node:v3.15.1
Orchestrator version - Kubernetes v1.16.3
Operating System and version: Ubuntu 18.04.5 LTS (GNU/Linux 4.15.0-130-generic x86_64)
Link to your project (optional):

FWIW, we don't see this in our overnight test runs.
Can you check MTU (or upgrade to a recent Calico version with automatic MTU configuration)?

Hi Matt ,
Sure ! will give a try & revert back .
Is this happening because of packets being marked as Invalid & this creating IP address spoofing scenario & hence connections being dropped ?

We generally recommend the current release of Calico - at the moment that's v3.19.1.  That should choose the MTU correctly itself.

@vishumindtree any update on this one?

you can run conntrack -L to track TCP connection.

This issue is not reproducible on calico_version: v3.17.4.

authors: caseydavenport lwr20 vishumindtree xiaods


text:
Example: kubeadm calico manifest points to a broken link

Example: kubeadm calico manifest points to a broken link
kubectl apply -f http://docs.projectcalico.org/v2.2/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico.yaml
taken from here:
http://docs.projectcalico.org/v2.2/getting-started/kubernetes/installation/hosted/kubernetes-datastore/#example-kubeadm
see also: https://github.com/projectcalico/calico/issues/716

Wow this is bad.
Part of this issue should be ensuring all of our manifest links are correct.

I will fix this as part of 716

authors: caseydavenport djosborne frnkdny


text:
Unexpected vif_type=tap breaking all tests

My most recent PR FV run  (Icehouse) failed with these errors in the nova-scheduler log:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1388, in _build_instance
    set_access_ip=set_access_ip)
  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 414, in decorated_function
    return function(self, context, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1806, in _spawn
    LOG.exception(_('Instance failed to spawn'), instance=instance)
  File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__
    six.reraise(self.type_, self.value, self.tb)
  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1803, in _spawn
    block_device_info)
  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2370, in spawn
    write_to_disk=True)
  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3572, in to_xml
    disk_info, rescue, block_device_info)
  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3378, in get_guest_config
    flavor)
  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 384, in get_config
    _("Unexpected vif_type=%s") % vif_type)
NovaException: Unexpected vif_type=tap

Sounds similar to #297; maybe they've revved the package.
This was run-fv-tests-pr-req build 129.

Looks like nova has been revved to 1:2014.1.5-0ubuntu1.4 upstream, replacing our 1:2014.1.5-0ubuntu1.3calico1.0.0+1.

Pins should prevent this.

@matthewdupre is there anything left to do on this now you've fixed the pins?

Not on this particular issue (or this particular upstream release).
If anybody hits this symptom, please check your apt preferences (or RPM priorities).  The install instructions should lead you through setting them up.  If you can't use a pin / priority for some reason, please let us know on slack / IRC / ..., and we'll try and prioritize the rebase.

authors: fasaxc matthewdupre


text:
Update the etcdv3 prefix doc

Description
Update the etcd path doc with details of the new etcdv3 paths
None required

Thanks @robbrockbank ! Looks like chicken-egg  errors. @bcreane if we generate 3.1 from master, OpenStack will be there already. However, @robbrockbank the master copy should contain OpenStacj info if possible.

@emanic:  Given we don't currently support OpenStack in master, is it correct to include the OpenStack paths in master?

@robbrockbank Yes, we are keeping them in the master but removing from v3.0

I am going to go ahead and merge this one as it is only failing on chicken-egg errors. I also made a story in JIRA to track the /calico/felix/v1/*  path question. Thanks @robbrockbank

authors: emanic robbrockbank


text:
Add Slack and IRC badges

Add more badges, like the calico-docker repo

Hard to review, I'm just going to merge and fix up if it doesn't look right!

authors: eepyaich fasaxc


text:
Fix GuC loading failing on ubuntu host side

Guc loading error seen in host dmesg logs
GuC firmware i915/adlp_guc_70.1.1.bin: fetch failed with error -2
[drm] GuC firmware i915/adlp_guc_70.1.1.bin version 0.0
GuC initialization failed -2
Fix the issue by copying all the firmware files present in the i915 folder to /lib/firmware/i915 instead of copying selective files.
Tracked-On: OAM-105224
Signed-off-by: Jeevaka Prabu Badrappan jeevaka.badrappan@intel.com

@yhe39, @YuanjunHuang  Could you review this PR?

LGTM.
I tried on ADL/TGL. 5.15 and 5.10 kernel, the host all could run on SRIOV PF mode and load guc fw successfully.

authors: JeevakaPrabu YadongQi yhe39


text:
Implement IPv6 support for DNS, fix some DNS server behaviours

This commit allows the DNS server to serve IPv6 address records (AAAA) for both interaction and NS glue. In combination with the changes in #181 and #182 this allows for IPv6 interaction and provides more opportunities for interaction to ocurr when e.g. IPv6 and IPv4 egress firewalling differ on a network being tested.
Specifying the '-ip' option multiple times now allows setting multiple response addresses for the DNS server. Both IPv4 and IPv6 addresses are supported. If no IP address is specified the auto-detected address will be logged at startup time to aid with troubleshooting.
Fixes a couple of behaviour bugs with the DNS server implementation and changes the default TTL to 5 from 3600.

I should say as well: this is a fairly big diff and I'm certainly open to revising it if it isn't in line with your plans for things.

Hi folks,
I'm going to look at re-writing this patch and will re-submit it against current dev.
Cheers,
Michael

@pulse-michaelfincham thank you 🙌🏻  It would be great if you could split the PR into multiple, each with a particular change.

@pulse-michaelfincham I created #307 for one of the features introduced in this, and I intended to do the same for two other changes made in this PR, but I don't have enough context, so I'll leave it up to you to put it in the PR or issue.
Thanks again, closing this PR now as this will be handled separately.

authors: ehsandeep fincham pulse-michaelfincham

repo: projectdiscovery/interactsh


text:
Move bevy_replicon_renet to a dedicated repository

Moved to https://github.com/projectharmonia/bevy_replicon_renet.

I think we can merge 0.14.0-rc into master after this merge. What do you think?

Okay, keeping it separate then!


text:
can't transition from demo

I posted this describing the situation but haven't heard back.
http://talk.projectjellyfish.org/t/how-to-tie-in-manageiq-after-building-jellyfish/49

Hello,
Sorry for the delay in responding.  Please take a look here and let me know if you have any questions:
http://projectjellyfish.readthedocs.org/en/latest/how-tos/setup-manageiq/

repo: projectjellyfish/api


text:
New slot created disappears from the list if collapse button is clicked while the creating is in progress

Browser: Edge
Repro:

Create new slot
navigate to Slots list and click on the collapse button.

New slot does not show until refresh button on the function app is clicked.

Probably a duplicate of a bug that Elliott opened.

Yes this is the same as the one that Elliott filed.

Dupe of https://github.com/Azure/azure-functions-ux/issues/1304

authors: lindydonna panchagnula paulbatum pragnagopa

repo: projectkudu/AzureFunctionsPortal


text:
aspirate generate -ct v1 or aspirate build -ct v2 doesn't override the fallback tag from aspirate init -ct latest

🔥 Bug Description
Related to #127
When I initialise the Aspire project with the command, aspirate init -ct latest, it generates aspirate.json and latest is set as the fallback tag.
However, if I run the command, aspirate generate -ct v1 or aspirate build -ct v2 doesn't take precedence over latest. The Kustomization files are still pointing to the fallback tag, latest in this example.
🔍 Steps to Reproduce the Bug

Run the init command, aspirate init -ct latest ...
Run the generate command, aspirate generate -ct v1 ... or build command, aspirate build -ct v2 ...
Check the deployment.yml files under the aspirate-output/* directory that point to the latest tag

Thanks - just fixed, will be going out in the release which also fixes #127 in the next hour :)


text:
Update Google API library

When working on https://github.com/prometheus-community/stackdriver_exporter/pull/74, I noticed google.golang.org/api/monitoring/v3 is marked as deprecated.
It needs to be updated to cloud.google.com/go/monitoring/apiv3

Any news related to this topic?

Looks like the above deprecation is now deprecated. :joy:

https://pkg.go.dev/cloud.google.com/go/monitoring/apiv3/v2
https://pkg.go.dev/cloud.google.com/go

authors: SuperQ colleym


text:
Modify storage time

After sts prometheus-k8s is started, --storage.tsdb.retention.time parameter is 24 hours by default. How to modify this parameter? I want to save the data for 15 days

.spec.retention in the Prometheus object.

.spec.retention in the Prometheus object.

Thank you very much

.spec.retention在普罗米修斯对象中。

apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
labels:
prometheus: k8s
name: k8s
namespace: ops-prod
spec:
alerting:
alertmanagers:
- name: alertmanager-main
namespace: ops-prod
port: web
baseImage: 747875099153.dkr.ecr.us-east-1.amazonaws.com/ops-basic/prometheus
imagePullSecrets:

name: registry-secret
enableFeatures:
storage.tsdb.min-block-duration: 2h
storage.tsdb.max-block-duration: 2h

Please take a look at the configuration. I tried to configure it but it doesn't seem to work

repo: prometheus-operator/kube-prometheus


text:
add groupKey to alerts/groups API endpoint

Discussion started at #574
Add the groupKey information to the alerts/groups endpoint.
When having configured a webhook receiver it contains the groupKey. Adding the groupKey to the overview of alertgroups makes it possible to match the incoming webhook with groups reported back from the API.

Updated the PR as proposed in the comment

LGTM 👍

authors: fabxc soupdiver

repo: prometheus/alertmanager


text:
Internal Sever Error when trying to see metrics via locust_exporter

Hi ,
I am using locust_exporter from https://github.com/mbolek/locust_exporter . When  running the exporter I am getting Internal server error on the browser and following error is displayed on the terminal :
Traceback (most recent call last):
File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/wsgiref/handlers.py", line 137, in run
self.result = application(self.environ, self.start_response)
File "/Users/locust_exporter/.venv/lib/python3.9/site-packages/prometheus_client/exposition.py", line 118, in prometheus_app
status, header, output = _bake_output(registry, accept_header, params)
File "/Users/locust_exporter/.venv/lib/python3.9/site-packages/prometheus_client/exposition.py", line 100, in bake_output
output = encoder(registry)
File "/Users/locust_exporter/.venv/lib/python3.9/site-packages/prometheus_client/exposition.py", line 202, in generate_latest
output.append(sample_line(s))
File "/Users/locust_exporter/.venv/lib/python3.9/site-packages/prometheus_client/exposition.py", line 159, in sample_line
['{}="{}"'.format(
File "/Users/locust_exporter/.venv/lib/python3.9/site-packages/prometheus_client/exposition.py", line 160, in
k, v.replace('', r'').replace('\n', r'\n').replace('"', r'"'))
AttributeError: ("'NoneType' object has no attribute 'replace'", Metric(locust_requests_avg_content_length, Locust requests avg_content_length, gauge, , [Sample(name='locust_requests_avg_content_length', labels={'path': '/api/test, 'method': 'POST'}, value=165.0, timestamp=None, exemplar=None), Sample(name='locust_requests_avg_content_length', labels={'path': 'Aggregated', 'method': None}, value=165.0, timestamp=None, exemplar=None)]))

Anyone looking into this?


text:
Add support for thread data parsing.

Provide access to /proc/PID/task/TID files, for thread specific values. Since such files have the same structure as /proc/PID/ ones, the data structures and the parsers for the latter may be reused.
@discordianfish, @pgier if you could take a look at this very basic PR, that would be appreciated. TIA

Hello @discordianfish, could you take a look at this simple PR? Thank you!

Great, LGTM!

Thank you, could you also merge it on my behalf or point me to ppl. that might be able to do so? I don't have write access.

We need another maintaoner to approve /cc @pgier @SuperQ

Minor nit, otherwise LGTM.

Thank you, all done!

Thank you all for making this happen.

authors: discordianfish emypar

repo: prometheus/procfs


text:
gke have updated the k8s version for the region we are using

it errors for 1.10.4-gke.2 as it is not available anymore for the region
we are using.

:+1:

authors: krasi-georgiev sipian

repo: prometheus/prombench


text:
tsdb: prometheus ignores  --storage.tsdb.retention.time=1h option

Prometheus ignores retention time option and keeps metrics for longer time.
I restarted prometheus with retention time option set:
$ date
Wed Aug 14 11:12:05 +03 2019

$ ps aux | grep prom
autotst   8580  0.0  0.3 162720 53356 ?        Sl   10:08   0:03 ./prometheus --config.file=prometheus.yml --web.listen-address=192.168.248.69:6102 --storage.tsdb.retention.time=1h

$ cat prometheus/prometheus.log
level=info ts=2019-08-14T07:08:32.461Z caller=main.go:329 msg="Starting Prometheus" version="(version=2.11.1, branch=HEAD, revision=e5b22494857deca4b806f74f6e3a6ee30c251763)"
level=info ts=2019-08-14T07:08:32.462Z caller=main.go:330 build_context="(go=go1.12.7, user=root@d94406f2bb6f, date=20190710-13:51:17)"
level=info ts=2019-08-14T07:08:32.462Z caller=main.go:331 host_details="(Linux 3.10.0-862.14.4.el7.x86_64 #1 SMP Fri Sep 21 09:07:21 UTC 2018 x86_64 alice jnetx.ru)"
level=info ts=2019-08-14T07:08:32.462Z caller=main.go:332 fd_limits="(soft=16384, hard=16384)"
level=info ts=2019-08-14T07:08:32.462Z caller=main.go:333 vm_limits="(soft=unlimited, hard=unlimited)"
level=info ts=2019-08-14T07:08:32.464Z caller=main.go:652 msg="Starting TSDB ..."
level=info ts=2019-08-14T07:08:32.464Z caller=repair.go:59 component=tsdb msg="found healthy block" mint=1565703901407 maxt=1565719200000 ulid=01DJ6KBBV9BZDSXV8GPFFFCTGH
level=info ts=2019-08-14T07:08:32.464Z caller=repair.go:59 component=tsdb msg="found healthy block" mint=1565740800000 maxt=1565748000000 ulid=01DJ712T8BNZSP9665NHGJJRZK
level=info ts=2019-08-14T07:08:32.464Z caller=repair.go:59 component=tsdb msg="found healthy block" mint=1565719200000 maxt=1565740800000 ulid=01DJ712TB7JEVGKSZFFN09C5BA
level=info ts=2019-08-14T07:08:32.464Z caller=repair.go:59 component=tsdb msg="found healthy block" mint=1565748000000 maxt=1565755200000 ulid=01DJ77YHGBNEJP5FNR2FYMKEWF
level=info ts=2019-08-14T07:08:32.464Z caller=repair.go:59 component=tsdb msg="found healthy block" mint=1565755200000 maxt=1565762400000 ulid=01DJ7ET8RB0RGYAX030J5SS0T8
level=info ts=2019-08-14T07:08:32.480Z caller=web.go:448 component=web msg="Start listening for connections" address=192.168.248.69:6102
level=info ts=2019-08-14T07:08:32.656Z caller=main.go:667 fs_type=XFS_SUPER_MAGIC
level=info ts=2019-08-14T07:08:32.656Z caller=main.go:668 msg="TSDB started"
level=info ts=2019-08-14T07:08:32.656Z caller=main.go:738 msg="Loading configuration file" filename=prometheus.yml
level=info ts=2019-08-14T07:08:32.658Z caller=main.go:766 msg="Completed loading of configuration file" filename=prometheus.yml
level=info ts=2019-08-14T07:08:32.658Z caller=main.go:621 msg="Server is ready to receive web requests."
level=info ts=2019-08-14T09:00:01.499Z caller=compact.go:495 component=tsdb msg="write block" mint=1565762400000 maxt=1565769600000 ulid=01DJ7NP00B1J9S7PMPVEGXDE13 duration=79.489743ms
level=info ts=2019-08-14T09:00:01.510Z caller=head.go:586 component=tsdb msg="head GC completed" duration=1.230089ms
level=info ts=2019-08-14T09:00:01.566Z caller=head.go:656 component=tsdb msg="WAL checkpoint complete" first=6 last=7 duration=55.713136ms
$ cat prometheus/prometheus.yml
global:
  scrape_interval: 10s
  scrape_timeout: 10s
scrape_configs:
  - job_name: 'System'
    metrics_path: '/metrics'
    scheme: 'https'
    static_configs:
    - targets: ['192.168.248.69:6131', '192.168.248.69:6103']
    tls_config:
      insecure_skip_verify: true

But data keeps growing:
$ du -h prometheus/data/
96K     prometheus/data/wal/checkpoint.000005
16M     prometheus/data/wal
544K    prometheus/data/01DJ6KBBV9BZDSXV8GPFFFCTGH/chunks
660K    prometheus/data/01DJ6KBBV9BZDSXV8GPFFFCTGH
260K    prometheus/data/01DJ712T8BNZSP9665NHGJJRZK/chunks
348K    prometheus/data/01DJ712T8BNZSP9665NHGJJRZK
764K    prometheus/data/01DJ712TB7JEVGKSZFFN09C5BA/chunks
896K    prometheus/data/01DJ712TB7JEVGKSZFFN09C5BA
256K    prometheus/data/01DJ77YHGBNEJP5FNR2FYMKEWF/chunks
344K    prometheus/data/01DJ77YHGBNEJP5FNR2FYMKEWF
256K    prometheus/data/01DJ7ET8RB0RGYAX030J5SS0T8/chunks
344K    prometheus/data/01DJ7ET8RB0RGYAX030J5SS0T8
18M     prometheus/data/

$ ls -la prometheus/data/
total 0
drwxr-xr-x 8 autotst rnd1 199 Aug 14 10:00 .
drwxr-xr-x 5 autotst rnd1 188 Aug 13 16:44 ..
drwxr-xr-x 3 autotst rnd1  68 Aug 14 02:00 01DJ6KBBV9BZDSXV8GPFFFCTGH
drwxr-xr-x 3 autotst rnd1  68 Aug 14 06:00 01DJ712T8BNZSP9665NHGJJRZK
drwxr-xr-x 3 autotst rnd1  68 Aug 14 06:00 01DJ712TB7JEVGKSZFFN09C5BA
drwxr-xr-x 3 autotst rnd1  68 Aug 14 08:00 01DJ77YHGBNEJP5FNR2FYMKEWF
drwxr-xr-x 3 autotst rnd1  68 Aug 14 10:00 01DJ7ET8RB0RGYAX030J5SS0T8
-rw-r--r-- 1 autotst rnd1   0 Aug 13 16:44 lock
drwxr-xr-x 3 autotst rnd1 127 Aug 14 10:08 wal

And grafana still shows previous data on dashboards

Looks like at the noon (see updated log file in first comment) prometheus removed data not in 3 hours range

Hi!
It might be indeed confusing but this actually expected behavior with the current implementation. It is due to Prometheus storage format, where we collect metrics up to 2h and then produce "TSDB block". Retention only affects storage, so it won't remove anything until the full block is outside of given time range. In the same manner if your set retention to 8h you probably will have data still for 10-11 hours because compacted blocks might be as large as 8h. This is not very accurate by design. Same if you would set size retention.
Maybe we should be more explicit about this in documentation?

authors: bwplotka xnike

repo: prometheus/prometheus


text:
[release 2.53] Revert 13583 to stop dropping samples in remote-write catch-up

fixes https://github.com/prometheus/prometheus/issues/14087
I reverted the changes in watcher.go, but left the new test in place, and enhanced it as discussed at #14439.

(Test is now flaking consistently in the merge-to-main PR 😬 )


text:
tsdb: don't allow ingesting empty labelsets

See #5617
When we ingest an empty labelset in the head, further blocks can not be
compacted, with the error:
level=error ts=2020-02-27T21:26:58.379Z caller=db.go:659 component=tsdb
msg="compaction failed" err="persist head block: write compaction:
add series: out-of-order series added with label set \"{}\" / prev:
\"{}\""

We should therefore reject those invalid empty labelsets upfront.
This can be reproduced with the following:
cat << END > prometheus.yml
scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 1s
    basic_auth:
      username: test
      password: test
    metric_relabel_configs:
    - regex: ".*"
      action: labeldrop

    static_configs:
    - targets:
      - 127.0.1.1:9090
END
./prometheus --storage.tsdb.min-block-duration=1m

And wait a few minutes.
Signed-off-by: Julien Pivotto roidelapluie@inuits.eu

Shouldn't we also check that there's at least a metric name when scraping?

This is an issue with metrics_relabeling. I don't know if we support empty
names or not.
Le ven. 28 févr. 2020 à 10:00, Brian Brazil notifications@github.com a
écrit :

Shouldn't we also check that there's at least a metric name when scraping?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/6891?email_source=notifications&email_token=AACHHJSGGNHROFHUO7GRTPLRFDHB3A5CNFSM4K5D344KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENHZBQY#issuecomment-592416963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHHJXDRCMWIHXVDAKICPTRFDHB3ANCNFSM4K5D344A
.

All metrics have to have a metric name.

I will rewrite the PR. If we check for name we don't have to check for
emptiness. Note: labels are sorted, so __name will come in the first
labels, right? I can loop from the beginning.
Le ven. 28 févr. 2020 à 10:14, Brian Brazil notifications@github.com a
écrit :

All metrics have to have a metric name.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/6891?email_source=notifications&email_token=AACHHJXBYL66L6ZAUJZL5ELRFDIY3A5CNFSM4K5D344KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENH2L3A#issuecomment-592422380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHHJSAJBQZNHGEF6SQEILRFDIY3ANCNFSM4K5D344A
.

The TSDB doesn't care about metric names though, it's agnostic to that. So we need checks in two places.

something like this --  test to be added in scrape package

But we need relabel to happen first
Le ven. 28 févr. 2020 à 11:31, Brian Brazil notifications@github.com a
écrit :

@brian-brazil commented on this pull request.
In scrape/scrape.go
https://github.com/prometheus/prometheus/pull/6891#discussion_r385620257
:

@@ -1154,6 +1154,11 @@ loop:
continue
}

	if !lset.Has(labels.MetricName) {

		app.Rollback()

This doesn't seem right, we should be treating this the same as a parse
error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/6891?email_source=notifications&email_token=AACHHJR77G35EB57IBVEULTRFDRZHA5CNFSM4K5D344KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCXKUTWQ#pullrequestreview-366299610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHHJXAV76IQJF32DW6DBLRFDRZHANCNFSM4K5D344A
.

Yes, but the rest of the logic should be the same as a parse error.

authors: brian-brazil roidelapluie


text:
Discrepancy between Assertion python file documentation and the actual implementation

Describe the bug
From this documentation page, it seems quite straightforward to read config parameters passed to an external python script for evaluations. Unfortunately the context object does not seem to follow the structure described in the example code.
To Reproduce
a config with the following assert:
    assert:
      - type: python
        value: file://eval_script.py
        config:
          minOutputLength: 10
          maxOutputLength: 10000000

the eval_script.py:
from typing import Any, Dict, TypedDict, Union
import json

def get_assert(output: str, context) -> Union[bool, float, Dict[str, Any]]:
    print('Prompt:', context['prompt'])

    min_len = context['config']['minOutputLength']
    max_len = context['config']['maxOutputLength']

    if len(output) > max_len or len(output) < min_len:
        return {
            'pass': False,
            'score': 0.0,
            'reason': 'Length is not good!',
        }

    # This return is an example GradingResult dict
    return {
      'pass': True,
      'score': 0.6,
      'reason': 'Looks good to me',
    }

according to the documentation page this should work, instead a key error is raised.
The actual config parameters seems to be accessible like follows:
min_len = context['test'][index_of_the_text]['config']['minOutputLength']

Expected behavior
I should be able to get it just as explained in the documentation, as follows:
min_len = context['config']['minOutputLength']

Thank you

Thanks for reporting this @DarioBernardo! We'll work on a fix today.
Relates to https://github.com/promptfoo/promptfoo/issues/1701

@vedantr would you mind taking a look at this if you have time? Don't worry if not.

Will do! I'll submit a PR to fix.

I’m really excited about this functionality. It’s going to unlock the ability to use the same Python script across multiple assertions.
Once it’s working as shown in the examples, I think it would be beneficial to adjust the Assertion Properties to include the config field.

+1 for this. I'm trying to make universal Python assert that I can parametrize via the assert config, but without this working it's probably not possible.

authors: DarioBernardo camorales197 hodanajan mldangelo vedantr

repo: promptfoo/promptfoo


text:
New tests suite

Adding tests for all new features.

Coverage increased (+0.3%) to 85.127% when pulling 6893d04b139d455585f3c4760f8fc43708887e5d on sergio-ocon:even_more_testing into abb810f7e75dfcf395609e88570c66193edbf9f0 on propedeutica:master.

Coverage increased (+1.6%) to 86.392% when pulling df6f5d95253653813b2dd23335dcad9d4f77e6f5 on sergio-ocon:even_more_testing into abb810f7e75dfcf395609e88570c66193edbf9f0 on propedeutica:master.

Coverage increased (+8.9%) to 93.73% when pulling a58e93e3754f43f84048ef9951d4d4e6acfcaf2e on sergio-ocon:even_more_testing into abb810f7e75dfcf395609e88570c66193edbf9f0 on propedeutica:master.

authors: coveralls sergio-ocon

repo: propedeutica/shift-reservation


text:
feat: add custom metric support

https://linear.app/propel/issue/PRO-2387

lets add an acceptance test  for Metric, that way you can be sure it is working properly

authors: GabrielMusatMestre senekis

repo: propeldata/terraform-provider-propel


text:
No ->save() function generated by propel build?

Hi, I'm relatively new to Propel. I setup my DB with propel init, and did propel build, which generated the models. However, when I tried to use the ->save() function, my IDE reports that the method does not exist. Does anyone know why this is so?
I'm using PHPStorm 2017.1.4
Also, my IDE also reports that another definition with the same name exists in the file, and commenting out the use myNameSpace\SubNameSpace\ModelName seemed to help.

bump

In Propel3 active-record methods are optional. Set activeRecord="true" at <entity> or <database> to activate it.

What if I don't activate it?

In the data mapper pattern, the persistance logic is not contained into the entity, so you should use the session objectd to do it:
// create the $configuration manually
$configuration = new Configuration(‘./path/to/propel.yml’);

$session = $configuration->createSession();

$car1 = new Car(‘Ford Mustang’);
$session->persist($car);
$car2 = new Car(‘Ferrari Testarossa’);
$session->persist($car);

$session->commit(); //Save the objects to the database, following the unit-of-work pattern

authors: cristianoc72 marcj xiurobert


text:
wrong internal state with title setting and unable to make new figures

Description
When I was adjusting the axes titles of a figure, something seemed to break the internal state of proplot. The package does not work anymore, see the error message below. I have no choice but restart the whole python session.
Steps to reproduce
I tried the following code
import proplot as pplt

fig, axs = pplt.subplots(None, 1, 4)
axs[0].format(
    title='title',
    titleloc='c', titlesize=10, titleweight='normal', titlecolor='gray10'
)

It complains "gray10" is not a good color as follows
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
/tmp/ipykernel_125973/2407293224.py in <module>
      2
      3 fig, axs = pplt.subplots(None, 1, 4)
----> 4 axs[0].format(
      5     title='title',
      6     titleloc='c', titlesize=10, titleweight='normal', titlecolor='gray10'

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/cartesian.py in format(self, aspect, xloc, yloc, xspineloc, yspineloc, xoffsetloc, yoffsetloc, xwraprange, ywraprange, xreverse, yreverse, xlim, ylim, xmin, ymin, xmax, ymax, xscale, yscale, xbounds, ybounds, xmargin, ymargin, xrotation, yrotation, xformatter, yformatter, xticklabels, yticklabels, xticks, yticks, xlocator, ylocator, xminorticks, yminorticks, xminorlocator, yminorlocator, xcolor, ycolor, xlinewidth, ylinewidth, xtickloc, ytickloc, fixticks, xtickdir, ytickdir, xtickminor, ytickminor, xtickrange, ytickrange, xtickcolor, ytickcolor, xticklen, yticklen, xticklenratio, yticklenratio, xtickwidth, ytickwidth, xtickwidthratio, ytickwidthratio, xticklabelloc, yticklabelloc, xticklabeldir, yticklabeldir, xticklabelpad, yticklabelpad, xticklabelcolor, yticklabelcolor, xticklabelsize, yticklabelsize, xticklabelweight, yticklabelweight, xlabel, ylabel, xlabelloc, ylabelloc, xlabelpad, ylabelpad, xlabelcolor, ylabelcolor, xlabelsize, ylabelsize, xlabelweight, ylabelweight, xgrid, ygrid, xgridminor, ygridminor, xgridcolor, ygridcolor, xlabel_kw, ylabel_kw, xscale_kw, yscale_kw, xlocator_kw, ylocator_kw, xformatter_kw, yformatter_kw, xminorlocator_kw, yminorlocator_kw, **kwargs)
    987         """
    988         rc_kw, rc_mode = _pop_rc(kwargs)
--> 989         with rc.context(rc_kw, mode=rc_mode):
    990             # No mutable default args
    991             xlabel_kw = xlabel_kw or {}

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/config.py in __enter__(self)
    791         rc_old = context.rc_old  # used to re-apply settings without copying whole dict
    792         for key, value in kwargs.items():
--> 793             kw_proplot, kw_matplotlib = self._get_item_dicts(key, value)
    794             for rc_dict, kw_new in zip(
    795                 (rc_proplot, rc_matplotlib),

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/config.py in _get_item_dicts(self, key, value, skip_cycle)
    922         # Get validated key, value, and child keys
    923         key, value = self._validate_key(key, value)
--> 924         value = self._validate_value(key, value)
    925         keys = (key,) + rcsetup._rc_children.get(key, ())  # settings to change
    926         contains = lambda *args: any(arg in keys for arg in args)  # noqa: E731

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/config.py in _validate_value(key, value)
    884             value = validate_matplotlib[key](value)
    885         elif key in validate_proplot:
--> 886             value = validate_proplot[key](value)
    887         return value
    888

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/internals/rcsetup.py in _validate_color(value, alternative)
    264             or not REGEX_NAMED_COLOR.match(value)
    265         ):
--> 266             raise ValueError(f'{value!r} is not a valid color arg.') from None
    267         return value
    268     except Exception as error:

ValueError: 'gray10' is not a valid color arg.

The problem is that I can not make any new figures since then.
When I start a new figure in a jupyter cell
fig, axs = pplt.subplots(None, 1, 4)

I get the following error
Error in callback <function install_repl_displayhook.<locals>.post_execute at 0x7f705b74adc0> (for post_execute):
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/pyplot.py in post_execute()
    137             def post_execute():
    138                 if matplotlib.is_interactive():
--> 139                     draw_all()
    140
    141             # IPython >= 2

~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/_pylab_helpers.py in draw_all(cls, force)
    135         for manager in cls.get_all_fig_managers():
    136             if force or manager.canvas.figure.stale:
--> 137                 manager.canvas.draw_idle()
    138
    139

~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/backend_bases.py in draw_idle(self, *args, **kwargs)
   2053         if not self._is_idle_drawing:
   2054             with self._idle_draw_cntx():
-> 2055                 self.draw(*args, **kwargs)
   2056
   2057     def get_width_height(self):

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/figure.py in _canvas_preprocess(self, *args, **kwargs)
    461         ctx3 = rc.context(fig._render_context)  # draw with figure-specific setting
    462         with ctx1, ctx2, ctx3:
--> 463             fig.auto_layout()
    464             return func(self, *args, **kwargs)
    465

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/figure.py in auto_layout(self, renderer, aspect, tight, resize)
   1474         _align_content()
   1475         if tight:
-> 1476             gs._auto_layout_tight(renderer)
   1477         _align_content()
   1478

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/gridspec.py in _auto_layout_tight(self, renderer)
    818         pad = self._outerpad
    819         obox = fig.bbox_inches  # original bbox
--> 820         bbox = fig.get_tightbbox(renderer)
    821
    822         # Calculate new figure margins

~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/figure.py in get_tightbbox(self, renderer, bbox_extra_artists)
   1637
   1638         for a in artists:
-> 1639             bbox = a.get_tightbbox(renderer)
   1640             if bbox is not None and (bbox.width != 0 or bbox.height != 0):
   1641                 bb.append(bbox)

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/cartesian.py in get_tightbbox(self, renderer, *args, **kwargs)
   1310         self._apply_axis_sharing()
   1311         self._update_rotation('x')
-> 1312         return super().get_tightbbox(renderer, *args, **kwargs)
   1313
   1314

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/base.py in get_tightbbox(self, renderer, *args, **kwargs)
   2610         if self._inset_parent is not None and self._inset_zoom:
   2611             self.indicate_inset_zoom()
-> 2612         self._tight_bbox = super().get_tightbbox(renderer, *args, **kwargs)
   2613         return self._tight_bbox
   2614

~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/axes/_base.py in get_tightbbox(self, renderer, call_axes_locator, bbox_extra_artists, for_layout_only)
   4444                 if bb_yaxis:
   4445                     bb.append(bb_yaxis)
-> 4446         self._update_title_position(renderer)
   4447         axbbox = self.get_window_extent(renderer)
   4448         bb.append(axbbox)

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/base.py in _update_title_position(self, renderer)
   2388         # Sync the title position with the a-b-c label position
   2389         aobj = self._title_dict['abc']
-> 2390         tobj = self._title_dict[self._abc_loc]
   2391         aobj.set_transform(tobj.get_transform())
   2392         aobj.set_position(tobj.get_position())

KeyError: None

---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
~/local/conda/envs/nemo/lib/python3.8/site-packages/IPython/core/formatters.py in __call__(self, obj)
    339                 pass
    340             else:
--> 341                 return printer(obj)
    342             # Finally look for special method names
    343             method = get_real_method(obj, self.print_method)

~/local/conda/envs/nemo/lib/python3.8/site-packages/IPython/core/pylabtools.py in retina_figure(fig, base64, **kwargs)
    166         base64 argument
    167     """
--> 168     pngdata = print_figure(fig, fmt="retina", base64=False, **kwargs)
    169     # Make sure that retina_figure acts just like print_figure and returns
    170     # None when the figure is empty.

~/local/conda/envs/nemo/lib/python3.8/site-packages/IPython/core/pylabtools.py in print_figure(fig, fmt, bbox_inches, base64, **kwargs)
    149         FigureCanvasBase(fig)
    150
--> 151     fig.canvas.print_figure(bytes_io, **kw)
    152     data = bytes_io.getvalue()
    153     if fmt == 'svg':

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/figure.py in _canvas_preprocess(self, *args, **kwargs)
    461         ctx3 = rc.context(fig._render_context)  # draw with figure-specific setting
    462         with ctx1, ctx2, ctx3:
--> 463             fig.auto_layout()
    464             return func(self, *args, **kwargs)
    465

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/figure.py in auto_layout(self, renderer, aspect, tight, resize)
   1474         _align_content()
   1475         if tight:
-> 1476             gs._auto_layout_tight(renderer)
   1477         _align_content()
   1478

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/gridspec.py in _auto_layout_tight(self, renderer)
    818         pad = self._outerpad
    819         obox = fig.bbox_inches  # original bbox
--> 820         bbox = fig.get_tightbbox(renderer)
    821
    822         # Calculate new figure margins

~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/figure.py in get_tightbbox(self, renderer, bbox_extra_artists)
   1637
   1638         for a in artists:
-> 1639             bbox = a.get_tightbbox(renderer)
   1640             if bbox is not None and (bbox.width != 0 or bbox.height != 0):
   1641                 bb.append(bbox)

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/cartesian.py in get_tightbbox(self, renderer, *args, **kwargs)
   1310         self._apply_axis_sharing()
   1311         self._update_rotation('x')
-> 1312         return super().get_tightbbox(renderer, *args, **kwargs)
   1313
   1314

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/base.py in get_tightbbox(self, renderer, *args, **kwargs)
   2610         if self._inset_parent is not None and self._inset_zoom:
   2611             self.indicate_inset_zoom()
-> 2612         self._tight_bbox = super().get_tightbbox(renderer, *args, **kwargs)
   2613         return self._tight_bbox
   2614

~/local/conda/envs/nemo/lib/python3.8/site-packages/matplotlib/axes/_base.py in get_tightbbox(self, renderer, call_axes_locator, bbox_extra_artists, for_layout_only)
   4444                 if bb_yaxis:
   4445                     bb.append(bb_yaxis)
-> 4446         self._update_title_position(renderer)
   4447         axbbox = self.get_window_extent(renderer)
   4448         bb.append(axbbox)

~/local/conda/envs/nemo/lib/python3.8/site-packages/proplot/axes/base.py in _update_title_position(self, renderer)
   2388         # Sync the title position with the a-b-c label position
   2389         aobj = self._title_dict['abc']
-> 2390         tobj = self._title_dict[self._abc_loc]
   2391         aobj.set_transform(tobj.get_transform())
   2392         aobj.set_position(tobj.get_position())

KeyError: None

Figure(nrows=1, ncols=4, refwidth=2.5)

Proplot version
Paste the results of import matplotlib; print(matplotlib.__version__); import proplot; print(proplot.version)here.
3.4.3
0.9.5.post284

I think I see the problem -- the rc state is not reset by Configurator.__exit__ during the error because the error is triggered inside Configurator.__enter__ rather than inside the with...as block. This leaves rc in a "user-modification" context mode rather than an "initialization" mode, so the initial values for ax._title_loc and ax._abc_loc are unset.
I think the solution is to validate rc values inside of pplt.rc.context rather than inside of pplt.Configurator.__enter__ and simplify the content in __enter__, and/or use a try...except block in __enter__ that calls __exit__ if necessary.

This was a very simple fix -- should have done it much sooner. Fixed by c567329 with a simple try-except clause.

authors: lukelbd syrte

repo: proplot-dev/proplot


text:
A question about learning rate.

In your paper "A Reinforcement Learning Environment For Job-Shop Scheduling", I saw that you used a linear scheduler for the learning rate and the entropy coefficient who decay linearly each parameter from 0.0006861 to 0.00007783 and from 0.0002458 to 0.002042 respectively.
I am confused about the learning rate and the entropy coefficient. Is this learning rate Actor-Net's learning rate? Is this entropy coefficient Critric-Net's learning rate?

The actor and the critic share the same learning rate.
The entropy coefficient is a term that is used to encourage exploration. I recommend you to read this paper that explore the impact of entropy on policy optimization: https://arxiv.org/abs/1811.11214

Thanks for your suggestion.

authors: DS-cmd ingambe

repo: prosysscience/JSSEnv


text:
[Automatic validation] Missing License

How to fix
Add a license for this repository. See help for guidance. Private repositories don't need a license.
About validation
These issues are created, closed and reopened by repository validator when commits are pushed to repository.
If there are problems, please add an issue to repository validator
DO NOT change the name of this issue. Names are used to identify the issues created by automation.

[Automatic validation]: Issue fixed. Closing issue.

repo: protacon/docker-git-lfs


text:
add context to metadata schemas page

This adds an intro paragraph and some more context to the metadata schemas page, plus a link to the "best practices" doc on docs.ipfs.io. I also added a blurb about how nft.storage can handle metadata for you.
Closes #44

Image optimization came back clean!
Vuepress build was successful!

docs/reference/metadata-schemas.md:

The following link returned HTTP status code 301 (Moved Permanently):
https://ethereum.org
The following link returned HTTP status code 302 (Found):
https://binance.org
Consider a shorter alternative to avoid wordiness....example an image, video, or game asset. In order to make an NFT represent so...
                                           ^^^^^^^^^^^

Consider a shorter alternative to avoid wordiness....display NFTs to buyers and sellers, but in order to do so, the metadata need...
                                           ^^^^^^^^^^^

Use ‘own’ only if you want to emphasize that something belongs to a person or thing or was done by a person or thing. Consider writing “your”....ta standard, possibly extending it with your own specific needs. This refere...
                                           ^^^^^^^^

The verb “check out” can sound colloquial in this context. Consider using a more formal alternative....ards. If you have trouble reading them, check out the official JSON Schema g...
                                           ^^^^^^^^^

If a new sentence starts here, add a space and start with an uppercase letter....ns new window). TIP If you're using nft.storage  (opens new window) to store...
                                           ^^^^^^^

Image optimization came back clean!
Vuepress build was successful!

docs/reference/metadata-schemas.md:

The following link returned HTTP status code 301 (Moved Permanently):
https://wikipedia.org/wiki/Metadata
The following link returned HTTP status code 301 (Moved Permanently):
https://ethereum.org
The following link returned HTTP status code 302 (Found):
https://binance.org
There may an error in the verb form ‘be extend’....existing metadata standard, and if need be extend it with your specific need...
                                           ^^^^^^^^^

If a new sentence starts here, add a space and start with an uppercase letter....ns new window). TIP If you're using nft.storage  (opens new window) to store...
                                           ^^^^^^^

Image optimization came back clean!
Vuepress build was successful!

docs/reference/metadata-schemas.md:

The following link returned HTTP status code 301 (Moved Permanently):
https://wikipedia.org/wiki/Metadata
The following link returned HTTP status code 301 (Moved Permanently):
https://ethereum.org
The following link returned HTTP status code 302 (Found):
https://binance.org
If a new sentence starts here, add a space and start with an uppercase letter....ns new window). TIP If you're using nft.storage  (opens new window) to store...
                                           ^^^^^^^

authors: filecorgi yusefnapora

repo: protocol/nft-website


text:
🛑 refs.ipfs.io is down

In f653c3f, refs.ipfs.io (https://refs.ipfs.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: refs.ipfs.io is back up in dadbb89 after 2 hours, 3 minutes.

repo: protocol/upptime-pln


text:
Adding Energy Systems and Informatics collection of resources to Curated Lists

Hi! Found this collection and suggest adding it. I am not affiliated.
URLs to the project:
https://energy.acm.org/resources/
According to their site, a curated collection of publicly available datasets, models, and software that The ACM Special Interest Group on Energy Systems and Informatics (SIGEnergy) finds to be useful for researchers and professionals who study energy systems and informatics.
More information can be found via the link I have provided.

The last commit was "Fixing casing in Energy Systems and Informatics collection of resources", wrong commit message.

Hi @Ly0n! I see there is a lot going on and the team seem to have a lot on their plate, so just to tidy up, your suggestions for this PR would be highly valuable to me.

Dear @Zhenev,
I went through all the projects that are in this list. Many of the projects listed are really high quality. Thanks for your pull request and sorry for the delay. Many such lists are often older / unmaintained and thus often unusable for users. That's why such a review takes longer.

repo: protontypes/open-sustainable-technology


text:
Implement addCancelAction method in base crud controller

This pull request

[x]

Follows #.
Related to #.
Fixes #.

Not generic enought for now

authors: dragosprotung mateusz-wu

repo: protung/easyadmin-plus-bundle


text:
Node version update

Update of node version

New branch created

New branch created

repo: provectus/kafka-ui


text:
Why domains is required for kubernetes module?

Describe the bug
Unable use sak-kubernetes module without providing domains for docker proxy
╷
│ Error: Invalid index
│
│   on .terraform/modules/kubernetes/local.tf line 2, in locals:
│    2:   registry = "https://registry.${var.domains[0]}"
│     ├────────────────
│     │ var.domains is empty list of string
│
│ The given key does not identify an element in this collection value: the collection has no elements.

Use version
I use sak-kuberentes from master branch (https://github.com/provectus/sak-kubernetes/commit/e6cf16d2d0d86b5fc0d61ed431c5e8041471de1f)
To Reproduce
module "kubernetes" {
  source = "github.com/provectus/sak-kubernetes?ref=e6cf16d2d0d86b5fc0d61ed431c5e8041471de1f"

  environment        = local.environment
  project            = local.project
  availability_zones = data.aws_availability_zones.current.zone_ids
  cluster_name       = "${local.environment}-${local.project}"
  vpc_id             = module.network.vpc_id
  subnets            = module.network.private_subnets
}

We need to use ingress because the registry required HTTPS connections. You can try to add insecure options for dockerconfig in kubernetes modules and use internal domain (http://registry..svc.cluster.local)

maybe it is better to leave such values as default?

authors: RustamGimadiev akastav

repo: provectus/swiss-army-kube


text:
无法下载 http416错误

无法下载
3.0
macos

升级到最新版本

repo: proxyee-down-org/proxyee-down


text:
Filter does not take lists

Closes #469

Nice, thank you!

authors: aljazerzen max-sixty

repo: prql/prql


text:
rancher authentication between karma and alertmanager

I set up an authentication between karma and alertmanager via rancher.
It works very well for viewing alerts, but not for sending silences.
My configuration of karma :
alertmanager:
      interval: 30s
      servers:
        - name: ocb-test01
          uri: https://rancher.xxxx/k8s/clusters/local/api/v1/namespaces/monitoring/services/alertmanager-operated:9093/proxy/
          headers:
            Authorization: "Bearer xxxxx"
          timeout: 20s
          proxy: true
          tls:
            insecureSkipVerify: true

I tested with a curl and it works fine :
curl -X POST -H "Authorization: Bearer xxxx" https://rancher.xxxx/k8s/clusters/local/api/v1/namespaces/monitoring/services/alertmanager-operated:9093/proxy/api/v2/silences

Looking at the rancher logs I had the impression that the token is not sent.

I've started nc in listen mode on port 9093:
$ nc -v -l 9093

Then I started karma with this config file:
alertmanager:
  interval: 10s
  servers:
    - cluster: HA
      name: ha1
      uri: "http://localhost:9093"
      timeout: 10s
      headers:
        Authorization: "Bearer xxxxx"

And I see that the header is being passed:
% nc -v -l 9093
GET /metrics HTTP/1.1
Host: localhost:9093
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip
Authorization: Bearer xxxxx

I've also used https://github.com/jmartin82/mmock to ensure that all requests have it set:

You test with get methods and it works fine. The problem I encounter is only with post methods and directly with karma.

Ah, sorry, missed that.
I don't see any headers being set in proxy code, so that does look like a bug.

Should be fixed via #2115

It works well with the fix, thank you.

authors: ncauchois prymitive

repo: prymitive/karma


text:
Alertmanager "external uri" for frontend code to use in non-proxied mode

I'm in a situation where karma is running in non-proxied mode and has read-only access to AM's API via an internal uri (e.g. localhost). The user's browser has read/write access to AM's API via an external uri e.g alerts.domain.foo. Thus to be able to add silences via the external uri, karma would need to know what AM's external uri is and generate the correct API requests. I couldn't find such flag/config (e.g. --alertmanager.uri.external) hence this feature request, thanks!

added external_uri option via #900, please check if that works as you expect

Can confirm it works as expected, thanks a lot! :+1:

authors: filippog prymitive


text:
Error checking

What is available to check if the command was successful or not?
I've tried $rc =  and testing for
$rc.Code
$rc.ExitCode
and neither has any value.
I'm trying to build a resilient script :D

Hi @juler69 - does #39 help?
try/catch blocks and an appropriate ErrorActionPreference need to be used.
any pacli errors are now written to the error stream (check $error[0])

Thanks

repo: pspete/PoShPACLI


text:
Differentiate between the return values

As jobs are executed, the will eventually have return values of the executed function ≠ 0, which could be valuable for the user.
These jobs could also be collected under a "state", regarding #112

HTCondor exit codes can be found here:
https://htcondor.readthedocs.io/en/latest/codes-other-values/condor_shadow-exit-codes.html

repo: psyinfra/HTCAnalyze


text:
[FIX] Fixing AST to make it compile on 1.16.0-nightly.

Hi @ptal!
While I was compiling https://github.com/goyox86/bailey I found this:
goyox86@Bailey:~/Code/rust/oak|goyox86/1.16.0-nightly⚡
⇒  cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling partial v0.1.1
   Compiling oak v0.4.6 (file:///home/goyox86/Code/rust/oak)
error[E0308]: mismatched types
   --> src/liboak/ast.rs:142:54
    |
142 |       path.segments.last_mut().unwrap().parameters = generics_params;
    |                                                      ^^^^^^^^^^^^^^^ expected enum `std::option::Option`, found enum `syntax::ast::PathParameters`
    |
    = note: expected type `std::option::Option<syntax::ptr::P<syntax::ast::PathParameters>>`
    = note:    found type `syntax::ast::PathParameters`

error: aborting due to previous error

error: Could not compile `oak`.

To learn more, run the command again with --verbose.

This change fixes that!
Regards

Thanks!

repo: ptal/oak


text:
chore(main): release butler-sheet-icons 3.5.0

:robot: I have created a release beep boop
3.5.0 (2024-04-24)
Features

Add --log-level option as alias for --loglevel (f2194e6)
Add aliases for BSI commands (f70d493), closes #533
Add new option --exclude-sheet-status for excluding private/published/public sheets from thumbnail update (dc932a3), closes #526

Bug Fixes

More robust implementation for --except-sheet-* options (7c73b73), closes #528
qscloud: Fix broken login to QS Cloud (146f715)
qseow: Show regular sheet ids instead of engine sheet ids in log output (a962adc), closes #529

Miscellaneous

deps: Update dependencies (8c3266b)
deps: Update dependencies (1ec3d1c)
deps: Update dependencies (af3b6e8)
main: release butler-sheet-icons 3.5.0 (e86fdf0)
qseow: Change default Sense version to 2024-Feb (d71f14a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ptarmiganlabs/butler-sheet-icons/releases/tag/untagged-a71792f40f7c7686aa25 :sunflower:

repo: ptarmiganlabs/butler-sheet-icons


text:
🛑 checkip.pterodactyl-installer.se is down

In b5f95ce, checkip.pterodactyl-installer.se (https://checkip.pterodactyl-installer.se) was down:

HTTP code: 0
Response time: 0 ms

Resolved: checkip.pterodactyl-installer.se is back up in 15369e1 after 14 minutes.

repo: pterodactyl-installer/service-status


text:
[BUG] pattern on stroke has variable distance and dotted stroke shows up

It seems the distance between instances varies with cursor speed during the stroke, I'd imagine due to performance, most likely. This example was using a 64x64 clipart and the distance between instances changes according to the cursor speed during a stroke.
On a related note, when the dashed style is selected, the stroke seems to show through instead of staying invisible

@pubpub-zz this version has consistently spaced clipart instances! A bug I noticed though was that the clipart box indicator for when you're first choosing the clip's dimensions doesn't seem to be working

I can not reproduce the box indicator issue, can you provide a video ?

https://user-images.githubusercontent.com/19545604/209451167-7a814211-f026-4eb1-9d92-c0f9047479c0.mp4
all the pens turned red after I hit ctrl+r, but it was happening like this even before I did that

Ça. You please provide your config and pens file

Absolutely!
pens-and-config.zip
PS/ Happy Holidays!

Thanks merry Christmas to you too 😀
First remember this release integrates  #240 : when activated (default), pressing shift or control will provide you access to up to 10 more pens. Your pens defines those pens to all as red. This can be disabled when checking off extrapens in  hotkeys option tab
Second, this version also introduced the switch from hand to pen when pressing shift or control to toggle between hand and line to ease drawing straight lines. There was a side effect, when you are using as you did a hotkey that contains ctrl or shift - as you have set scale / rotate to ctrl+R - reseting the tool to hand when releasing. I've fixed it ; can you check it is now ok for you?
Also I've associated this feature to the option setting "alt as as temporary" : you can disable it unchecking the function
give me your feedbacks
ppInk ctrl in hotkeys.zip

With that build, I still get the same effect when hitting ctrl+r and trying to insert a clipart afterwards. If I disable the extra pens the clipart still doesn't display the box around it when trying to determine its size. I have also tried disabling "alt as temporary" and the bug is still there. It's no deal breaker but might want to fix it for the next release :D

🤔🤔🤔🤔
can you provide a video and also your hotkeys.ini please

https://user-images.githubusercontent.com/19545604/209880459-bc74c82e-6caa-4a55-80b9-c89b00347253.mp4
the hotkeys.ini that I'm using is the one that came in bundled with the zip above. I extracted the archive and tested from that one straight

I've not been able to find the hotkeys.ini not in your previous zip. only config and pens

Sorry, I meant your file, not mine. I downloaded and used the bundled build from this post https://github.com/pubpub-zz/ppInk/issues/238#issuecomment-1366515679 to record the video 2 posts above

authors: NOVAinc pubpub-zz

repo: pubpub-zz/ppInk


text:
UAT | Filing | Info icons repeat information

Describe the bug
Info boxes do not share any additional info. E.g. infobox for "Date of Issuance" says "Date of Issuance".
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Additional explanatory information in non-legal language should be added.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

All text for infoboxes to be updated.
List and info here:
https://docs.google.com/document/d/1QOctdG2AaZjtjTAgIbzSYt8aYkFdr4ZnEYDCvYLtn40/edit

authors: AyushiSinghalLaw Taherabharmal

repo: pucardotorg/dristi