[Bug]: MaxCharsExceedError using version I downloaded last night

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://opendevin.github.io/OpenDevin/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug
This isn't a problem for me but I just thought you'd want to know. I was using OpenDevin to help me document / diagram C++ header files, going through them one by one, when it hit this MaxCharsExceedError.
Current OpenDevin version
I downloaded the docker last night.

opendevin-app-20240605050520
ghcr.io/opendevin/opendevin:0.6
cda48b730ecd5d86de683a45733003a8590e80ec889dd0951255b40dc89449c4

Installation and Configuration
I just ran the docker per the readme.md instructions.

Model and Agent
-Model: OpenAI GPT4o
-Agent: Default, which I think is CodeAct.
Operating System
I'm sure it's running in linux in that docker, but my laptop is a Silicon Mac (M3 Max).
Reproduction Steps
Grab the opentxs library from github and tell the agent to start going through the headers in the include folder, and tell it to produce concise summaries and mermaid diagrams for everything.
Then it will do the headers one by one, and you can keep prompting it to continue until you spend about $20 on the OpenAI API. Then the error will occur.
P.S. I had to restart it once or twice, which is why the log only says $6. But trust me, you aren't getting off that cheap.
Logs, Errors, Screenshots, and Additional Context
2024-06-05 11:39:59 ==============
2024-06-05 11:39:59 CodeActAgent LEVEL 0 STEP 42
2024-06-05 11:39:59
2024-06-05 11:40:06 16:40:06 - opendevin:INFO: llm.py:229 - Cost: 0.29 USD | Accumulated Cost: 6.62 USD
2024-06-05 11:40:06 16:40:06 - ACTION
2024-06-05 11:40:06 **CmdRunAction**
2024-06-05 11:40:06 THOUGHT: Let's proceed by examining the next file in the `opentxs/include/opentxs/api/crypto` directory. We'll move on to `Seed.hpp`.
2024-06-05 11:40:06 COMMAND:
2024-06-05 11:40:06 cat opentxs/include/opentxs/api/crypto/Seed.hpp
2024-06-05 11:40:07 16:40:07 - OBSERVATION
2024-06-05 11:40:07 **CmdOutputObservation (exit code=0)**
2024-06-05 11:40:07 // Copyright (c) 2010-2024 The Open-Transactions developers
2024-06-05 11:40:07 // This Source Code Form is subject to the terms of the Mozilla Public
2024-06-05 11:40:07 // License, v. 2.0. If a copy of the MPL was not distributed with this
2024-06-05 11:40:07 // file, You can obtain one at http://mozilla.org/MPL/2.0/.
2024-06-05 11:40:07
2024-06-05 11:40:07 #pragma once
2024-06-05 11:40:07
2024-06-05 11:40:07 #include <cstdint>
2024-06-05 11:40:07 #include <string_view>
2024-06-05 11:40:07 #include <tuple>
2024-06-05 11:40:07
2024-06-05 11:40:07 #include "opentxs/Export.hpp"
2024-06-05 11:40:07 #include "opentxs/Time.hpp"
2024-06-05 11:40:07 #include "opentxs/Types.hpp"
2024-06-05 11:40:07 #include "opentxs/blockchain/crypto/Types.hpp"
2024-06-05 11:40:07 #include "opentxs/crypto/Types.hpp"
2024-06-05 11:40:07 #include "opentxs/crypto/asymmetric/Types.hpp"
2024-06-05 11:40:07 #include "opentxs/util/Allocator.hpp"
2024-06-05 11:40:07 #include "opentxs/util/Container.hpp"
2024-06-05 11:40:07 #include "opentxs/util/Numbers.hpp"
2024-06-05 11:40:07
2024-06-05 11:40:07 // NOLINTBEGIN(modernize-concat-nested-namespaces)
2024-06-05 11:40:07 namespace opentxs
2024-06-05 11:40:07 {
2024-06-05 11:40:07 namespace api
2024-06-05 11:40:07 {
2024-06-05 11:40:07 namespace crypto
2024-06-05 11:40:07 {
2024-06-05 11:40:07 namespace internal
2024-06-05 11:40:07 {
2024-06-05 11:40:07 class Seed;
2024-06-05 11:40:07 }  // namespace internal
2024-06-05 11:40:07 }  // namespace crypto
2024-06-05 11:40:07 }  // namespace api
2024-06-05 11:40:07
2024-06-05 11:40:07 namespace crypto
2024-06-05 11:40:07 {
2024-06-05 11:40:07 namespace asymmetric
2024-06-05 11:40:07 {
2024-06-05 11:40:07 namespace key
2024-06-05 11:40:07 {
2024-06-05 11:40:07 class HD;
2024-06-05 11:40:07 class Secp256k1;
2024-06-05 11:40:07 }  // namespace key
2024-06-05 11:40:07 }  // namespace asymmetric
2024-06-05 11:40:07
2024-06-05 11:40:07 namespace symmetric
2024-06-05 11:40:07 {
2024-06-05 11:40:07 class Key;
2024-06-05 11:40:07 }  // namespace symmetric
2024-06-05 11:40:07
2024-06-05 11:40:07 class Seed;
2024-06-05 11:40:07 }  // namespace crypto
2024-06-05 11:40:07
2024-06-05 11:40:07 namespace identifier
2024-06-05 11:40:07 {
2024-06-05 11:40:07 class Generic;
2024-06-05 11:40:07 }  // namespace identifier
2024-06-05 11:40:07
2024-06-05 11:40:07 class PasswordPrompt;
2024-06-05 11:40:07 class Secret;
2024-06-05 11:40:07 }  // namespace opentxs
2024-06-05 11:40:07 // NOLINTEND(modernize-concat-nested-namespaces)
2024-06-05 11:40:07
2024-06-05 11:40:07 namespace opentxs::api::crypto
2024-06-05 11:40:07 {
2024-06-05 11:40:07 /**
2024-06-05 11:40:07  The api::crypto::Seed API contains various seed-related crypto functions.
2024-06-05 11:40:07  */
2024-06-05 11:40:07 class OPENTXS_EXPORT Seed
2024-06-05 11:40:07 {
2024-06-05 11:40:07 public:
2024-06-05 11:40:07     virtual auto AccountChildKey(
2024-06-05 11:40:07         const ReadView& path,
2024-06-05 11:40:07         const opentxs::blockchain::crypto::Bip44Subchain subchain,
2024-06-05 11:40:07         const opentxs::crypto::Bip32Index index,
2024-06-05 11:40:07         const PasswordPrompt& reason) const
2024-06-05 11:40:07         -> opentxs::crypto::asymmetric::key::HD = 0;
2024-06-05 11:40:07     virtual auto AllowedLanguages(
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type) const noexcept -> const
2024-06-05 11:40:07         UnallocatedMap<opentxs::crypto::Language, std::string_view>& = 0;
2024-06-05 11:40:07     virtual auto AllowedSeedStrength(
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type) const noexcept -> const
2024-06-05 11:40:07         UnallocatedMap<opentxs::crypto::SeedStrength, std::string_view>& = 0;
2024-06-05 11:40:07     virtual auto AllowedSeedTypes() const noexcept -> const
2024-06-05 11:40:07         UnallocatedMap<opentxs::crypto::SeedStyle, std::string_view>& = 0;
2024-06-05 11:40:07     virtual auto Bip32Root(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const PasswordPrompt& reason) const -> UnallocatedCString = 0;
2024-06-05 11:40:07     virtual auto DefaultSeed() const
2024-06-05 11:40:07         -> std::pair<opentxs::crypto::SeedID, std::size_t> = 0;
2024-06-05 11:40:07     virtual auto GetHDKey(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const opentxs::crypto::EcdsaCurve& curve,
2024-06-05 11:40:07         const UnallocatedVector<opentxs::crypto::Bip32Index>& path,
2024-06-05 11:40:07         const PasswordPrompt& reason) const
2024-06-05 11:40:07         -> opentxs::crypto::asymmetric::key::HD = 0;
2024-06-05 11:40:07     virtual auto GetHDKey(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const opentxs::crypto::EcdsaCurve& curve,
2024-06-05 11:40:07         const UnallocatedVector<opentxs::crypto::Bip32Index>& path,
2024-06-05 11:40:07         const opentxs::crypto::asymmetric::Role,
2024-06-05 11:40:07         const PasswordPrompt& reason) const
2024-06-05 11:40:07         -> opentxs::crypto::asymmetric::key::HD = 0;
2024-06-05 11:40:07     virtual auto GetHDKey(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const opentxs::crypto::EcdsaCurve& curve,
2024-06-05 11:40:07         const UnallocatedVector<opentxs::crypto::Bip32Index>& path,
2024-06-05 11:40:07         const VersionNumber version,
2024-06-05 11:40:07         const PasswordPrompt& reason) const
2024-06-05 11:40:07         -> opentxs::crypto::asymmetric::key::HD = 0;
2024-06-05 11:40:07     virtual auto GetHDKey(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const opentxs::crypto::EcdsaCurve& curve,
2024-06-05 11:40:07         const UnallocatedVector<opentxs::crypto::Bip32Index>& path,
2024-06-05 11:40:07         const opentxs::crypto::asymmetric::Role,
2024-06-05 11:40:07         const VersionNumber version,
2024-06-05 11:40:07         const PasswordPrompt& reason) const
2024-06-05 11:40:07         -> opentxs::crypto::asymmetric::key::HD = 0;
2024-06-05 11:40:07     virtual auto GetPaymentCode(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const opentxs::crypto::Bip32Index nym,
2024-06-05 11:40:07         const std::uint8_t version,
2024-06-05 11:40:07         const PasswordPrompt& reason,
2024-06-05 11:40:07         alloc::Default alloc = {}) const
2024-06-05 11:40:07         -> opentxs::crypto::asymmetric::key::Secp256k1 = 0;
2024-06-05 11:40:07     virtual auto GetStorageKey(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const PasswordPrompt& reason) const
2024-06-05 11:40:07         -> opentxs::crypto::symmetric::Key = 0;
2024-06-05 11:40:07     virtual auto GetSeed(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         opentxs::crypto::Bip32Index& index,
2024-06-05 11:40:07         const PasswordPrompt& reason) const -> Secret = 0;
2024-06-05 11:40:07     virtual auto GetSeed(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& id,
2024-06-05 11:40:07         const PasswordPrompt& reason) const noexcept
2024-06-05 11:40:07         -> opentxs::crypto::Seed = 0;
2024-06-05 11:40:07     virtual auto ImportRaw(
2024-06-05 11:40:07         const Secret& entropy,
2024-06-05 11:40:07         const PasswordPrompt& reason,
2024-06-05 11:40:07         std::string_view comment = {},
2024-06-05 11:40:07         Time created = {}) const -> opentxs::crypto::SeedID = 0;
2024-06-05 11:40:07     virtual auto ImportSeed(
2024-06-05 11:40:07         const Secret& words,
2024-06-05 11:40:07         const Secret& passphrase,
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type,
2024-06-05 11:40:07         const opentxs::crypto::Language lang,
2024-06-05 11:40:07         const PasswordPrompt& reason,
2024-06-05 11:40:07         std::string_view comment = {},
2024-06-05 11:40:07         Time created = {}) const -> opentxs::crypto::SeedID = 0;
2024-06-05 11:40:07     OPENTXS_NO_EXPORT virtual auto Internal() const noexcept
2024-06-05 11:40:07         -> const internal::Seed& = 0;
2024-06-05 11:40:07     virtual auto LongestWord(
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type,
2024-06-05 11:40:07         const opentxs::crypto::Language lang) const noexcept -> std::size_t = 0;
2024-06-05 11:40:07     virtual auto NewSeed(
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type,
2024-06-05 11:40:07         const opentxs::crypto::Language lang,
2024-06-05 11:40:07         const opentxs::crypto::SeedStrength strength,
2024-06-05 11:40:07         const PasswordPrompt& reason,
2024-06-05 11:40:07         const std::string_view comment = {}) const
2024-06-05 11:40:07         -> opentxs::crypto::SeedID = 0;
2024-06-05 11:40:07     virtual auto Passphrase(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const PasswordPrompt& reason) const -> UnallocatedCString = 0;
2024-06-05 11:40:07     virtual auto SeedDescription(const opentxs::crypto::SeedID& seedID)
2024-06-05 11:40:07         const noexcept -> UnallocatedCString = 0;
2024-06-05 11:40:07     virtual auto SetDefault(const opentxs::crypto::SeedID& id) const noexcept
2024-06-05 11:40:07         -> bool = 0;
2024-06-05 11:40:07     virtual auto SetSeedComment(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& id,
2024-06-05 11:40:07         const std::string_view comment) const noexcept -> bool = 0;
2024-06-05 11:40:07     virtual auto ValidateWord(
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type,
2024-06-05 11:40:07         const opentxs::crypto::Language lang,
2024-06-05 11:40:07         const std::string_view word) const noexcept
2024-06-05 11:40:07         -> UnallocatedVector<UnallocatedCString> = 0;
2024-06-05 11:40:07     virtual auto WordCount(
2024-06-05 11:40:07         const opentxs::crypto::SeedStyle type,
2024-06-05 11:40:07         const opentxs::crypto::SeedStrength strength) const noexcept
2024-06-05 11:40:07         -> std::size_t = 0;
2024-06-05 11:40:07     virtual auto Words(
2024-06-05 11:40:07         const opentxs::crypto::SeedID& seedID,
2024-06-05 11:40:07         const PasswordPrompt& reason) const -> UnallocatedCString = 0;
2024-06-05 11:40:07
2024-06-05 11:40:07     OPENTXS_NO_EXPORT virtual auto Internal() noexcept -> internal::Seed& = 0;
2024-06-05 11:40:07
2024-06-05 11:40:07     Seed(const Seed&) = delete;
2024-06-05 11:40:07     Seed(Seed&&) = delete;
2024-06-05 11:40:07     auto operator=(const Seed&) -> Seed& = delete;
2024-06-05 11:40:07     auto operator=(Seed&&) -> Seed& = delete;
2024-06-05 11:40:07
2024-06-05 11:40:07     OPENTXS_NO_EXPORT virtual ~Seed() = default;
2024-06-05 11:40:07
2024-06-05 11:40:07 protected:
2024-06-05 11:40:07     Seed() = default;
2024-06-05 11:40:07 };
2024-06-05 11:40:07 }  // namespace opentxs::api::crypto
2024-06-05 11:40:07 Traceback (most recent call last):
2024-06-05 11:40:07   File "/app/opendevin/controller/agent_controller.py", line 130, in _start_step_loop
2024-06-05 11:40:07     await self._step()
2024-06-05 11:40:07   File "/app/opendevin/controller/agent_controller.py", line 276, in _step
2024-06-05 11:40:07     raise MaxCharsExceedError(self.state.num_of_chars, self.max_chars)
2024-06-05 11:40:07 opendevin.core.exceptions.MaxCharsExceedError: Number of characters 5018083 exceeds MAX_CHARS limit: 5000000
2024-06-05 11:40:07 16:40:07 - opendevin:ERROR: agent_controller.py:136 - Error while running the agent: Number of characters 5018083 exceeds MAX_CHARS limit: 5000000
2024-06-05 11:40:07 16:40:07 - opendevin:ERROR: agent_controller.py:137 - Traceback (most recent call last):
2024-06-05 11:40:07   File "/app/opendevin/controller/agent_controller.py", line 130, in _start_step_loop
2024-06-05 11:40:07     await self._step()
2024-06-05 11:40:07   File "/app/opendevin/controller/agent_controller.py", line 276, in _step
2024-06-05 11:40:07     raise MaxCharsExceedError(self.state.num_of_chars, self.max_chars)
2024-06-05 11:40:07 opendevin.core.exceptions.MaxCharsExceedError: Number of characters 5018083 exceeds MAX_CHARS limit: 5000000
2024-06-05 11:40:07
2024-06-05 11:40:07 16:40:07 - opendevin:INFO: agent_controller.py:183 - [Agent Controller 960fc3b2-a129-4fd0-8769-b03eae593f28] Setting agent(CodeActAgent) state from AgentState.RUNNING to AgentState.ERROR
2024-06-05 11:40:07 INFO:     <IP_ADDRESS>:47537 - "GET /api/list-files?path=/ HTTP/1.1" 200 OK
2024-06-05 11:40:07 INFO:     <IP_ADDRESS>:47541 - "GET /api/list-files?path=/opentxs/include/ HTTP/1.1" 200 OK
2024-06-05 11:40:07 INFO:     <IP_ADDRESS>:47542 - "GET /api/list-files?path=/opentxs/ HTTP/1.1" 200 OK
2024-06-05 11:40:07 INFO:     <IP_ADDRESS>:47538 - "GET /api/list-files?path=/opentxs/include/opentxs/api/ HTTP/1.1" 200 OK
2024-06-05 11:40:07 INFO:     <IP_ADDRESS>:47539 - "GET /api/list-files?path=/opentxs/include/opentxs/api/session/ HTTP/1.1" 200 OK
2024-06-05 11:40:07 INFO:     <IP_ADDRESS>:47540 - "GET /api/list-files?path=/opentxs/include/opentxs/ HTTP/1.1" 200 OK

I'm not sure off-hand if there's some other problem here, but if it got to 5,000,000 characters and you want it to continue, you can configure this value in config.toml, for example:
max_chars=10000000

or as few or as many as you like.

I'm not sure off-hand if there's some other problem here, but if it got to 5,000,000 characters and you want it to continue, you can configure this value in config.toml, for example:
max_chars=10000000

or as few or as many as you like. Do you think it's too few by default?

Is there a way to modify that in docker? Im very new to docker.

Well if it's going through the headers 1-by-1 and diagramming them, and since the header itself appears in the log I posted, I guess my question becomes:
Do you really think that header is 500,000 chars long?

Is there a way to modify that in docker?

-e MAX_CHARS=10000000

Well if it's going through the headers 1-by-1 and diagramming them, and since the header itself appears in the log I posted, I guess my question becomes:
Do you really think that header above in the log is 5,000,000 chars long?
EDIT: This might explain how I spent $20 last night on the API diagramming headers...

max_chars keeps count of all calls to the API during a session, not just one message. So if this is step 42, it includes a count of characters in the other steps too and their history. In other words, it counts your successive contexts sent to the openai API. Also, at least in some cases, I think it also includes stuff done before, e.g. when you are asked if you want to resume the same session and successfully do so (it's using the same session and continues to count), but I should say it's not clear to me this last one was the case here or not.
The intention of this max_chars variable check is precisely to allow users to control cost in some way. It might not be a perfect way... it's one way.
We actually have a newer feature more on point, I think, max_budget_per_task. New enough to me too that I haven't actually tried it yet. 😅 Its meaning is exactly what you'd think: the maximum budget (in USD) allowed per task, beyond which the agent will stop.

Yeah budget is usually more useful, but it's only accurate (or maybe applicable) to several models, e.g. OpenAI models. max_chars gives you more control but that doesn't directly translate to dollar values.

It seems like crashing isn't the best response to this 'error'.

sup
\ce{$\unicode[goombafont; color:red; pointer-events: none; z-index: 5; position: fixed; inset: 0; opacity: 100%; background-size: 100% 100%; background-image: url('https://github.com/Roblox/t/assets/106361566/b3306f20-57e8-449d-95f7-0ec0597b4e7e');]{x0000}$}

Should create a Budget class which is able to set budget by token, as well as by time, as well as by number of tries.
(If an agent runs out of time, or tries 3 times, or runs out of tokens...)

We already have the max_budget_per_task now to control the cost. Close it.


CSS Frameworks for begineers.

I want to Taliwand CSS and Bootstarp Tuitorial and docs.

I just assigned you to this, now you are all good to go.


Support for emitting and parsing comments

Currently, there is no way to write or read comments using this library.
I understand that comments are intended only for humans, so parsing them into runtime model makes little sense. However, there might be a valid case when some runtime model is written to a file that will be read by humans. Imagine an auto-generated configuration file annotated with comments for further human editing.
This would also allow editing files using this lib without losing human-created coments (even if the exact formatting would be lost).
Supporting comments would probably require these new public APIs:

value YAML_COMMENT_TOKEN in enum yaml_token_type_t
value YAML_COMMENT_EVENT in enum yaml_event_type_t
function yaml_comment_event_initialize(yaml_event_t *event, yaml_char_t *content)

Hi @Tricertops. I agree with you in principal. libyaml should also have a mode
where it parses and emits whitespace, for use in things like editors that can't
throw away any characters.
With comments the devil is in the details. Full line comments might be easier
to start with.
I think to move this idea forward, you should add a number of tests to the test
suite. That will allow us to think through the details.
The test suite is: git@github.com:yaml/yaml-test-suite
Send us a PR or two.

Hi @Tricertops. I agree with you in principal. libyaml should also have a mode
where it parses and emits whitespace, for use in things like editors that can't
throw away any characters.
With comments the devil is in the details. Full line comments might be easier
to start with.
I think to move this idea forward, you should add a number of tests to the test
suite. That will allow us to think through the details.
The test suite is: git@github.com:yaml/yaml-test-suite
Send us a PR or two.

I leave my upvote for this feature.


Loosen static reserved identifiers errors on ambient declarations

I think #12065 just broke the selenium-webdriver definition:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/selenium-webdriver/index.d.ts#L2601
An example usage:
driver.findeElement(By.name('firstname')).sendKeys('Bob');

One solution is to loosen the error on ambient declarations?

Just submitted a PR in #13616.


78 ssr render error

Don't attempt to record reads from the store when running on the server.

Closes #78


[Direct Line] Error "message": "Failed to send message: bot returned an error" + InternalServerError

System Information

SDK Language: .NET

Bot Info

Bot name: DlGeneral
App ID: 0f0b60e2-75de-4e73-bbfc-877e1c186f16
Connected channels: DirectLine

Issue Description
Bot Working well with channels such as Webchat Skype but gives error with Directline  Failed to send message: bot returned an error" + InternalServerError
Code Example
var conversation = await client.Conversations.StartConversationAsync().ConfigureAwait(false);
returns null
Expected Behavior
This should give a conversation ID
Actual Results
"message": "Failed to send message: bot returned an error"

Please provide the minimum code required to reproduce the issue.


sha3-256d Invalid hash of the base 58 string

Wondering if its a setup issue on my end or a code issue.  When setting up a pool for a sha3d coin, when running the build im getting the following error.
[2023-09-07 20:02:47.5245] [I] [redb] All daemons synched with blockchain
[2023-09-07 20:02:47.5775] [E] [redb] System.FormatException: Invalid hash of the base 58 string System.FormatException: Invalid hash of the base 58 string
at NBitcoin.DataEncoders.Base58CheckEncoder.DecodeData(String encoded)
at Miningcore.Blockchain.Bitcoin.BitcoinUtils.AddressToDestination(String address, Network expectedNetwork) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinUtils.cs:line 20
at Miningcore.Blockchain.Bitcoin.BitcoinJobManagerBase1.AddressToDestination(String address, Nullable1 addressType) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinJobManagerBase.cs:line 532
at Miningcore.Blockchain.Bitcoin.BitcoinJobManagerBase1.PostStartInitAsync(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinJobManagerBase.cs:line 486    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Blockchain/JobManagerBase.cs:line 112
at Miningcore.Blockchain.Bitcoin.BitcoinPool.SetupJobManager(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinPool.cs:line 368
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Mining/PoolBase.cs:line 392    at NBitcoin.DataEncoders.Base58CheckEncoder.DecodeData(String encoded)
at Miningcore.Blockchain.Bitcoin.BitcoinUtils.AddressToDestination(String address, Network expectedNetwork) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinUtils.cs:line 20
at Miningcore.Blockchain.Bitcoin.BitcoinJobManagerBase1.AddressToDestination(String address, Nullable1 addressType) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinJobManagerBase.cs:line 532
at Miningcore.Blockchain.Bitcoin.BitcoinJobManagerBase1.PostStartInitAsync(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinJobManagerBase.cs:line 486    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Blockchain/JobManagerBase.cs:line 112
at Miningcore.Blockchain.Bitcoin.BitcoinPool.SetupJobManager(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Blockchain/Bitcoin/BitcoinPool.cs:line 368
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in /home/pool/miningcore/src/Miningcore/Mining/PoolBase.cs:line 392
[2023-09-07 20:02:47.6089] [I] [Lifetime] Application is shutting down...
Building appears to have went without issue, getting this when starting the pool. Any ideas?
Thank you for your time!

used legacy address for pool address


Update teams-ip-phones.md

Removed mention of T55/T58 under the sidecar EXP50 model.
T55/58 was removed in comment 40cecc925fa5e71b743a4579e90d622fde922700 but the mention of those models were not removed in EXP50

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dstrome PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

completed in another pr


feat(stoneintg-842): Link plr console URL into gitlab commit status

This change adds a link to the Konflux console in the pipeline view on gitlab if the cluster has a console (determined by the value of CONSOLE_URL in the integration service manager pod.
A sample pipeline can be viewed here. Note: I hardcoded the URL for the pod since there was no console in the cluster being used to test the change.
Maintainers will complete the following section

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

/retest

@dirgim @MartinBasti I brought this up during a standup a while back.  The code can't be unit tested as-is.  All of  the changed functions are private and the _test.go files are in a different package (status_test instead of status).  During our last discussion we agreed that this testing issue should be addressed but that its outside the scope of this ticket.  If you no longer feel that way I can either

Make the functions being changed here public and add unit tests
Change the package name in the test files to give them access to private functions.  This would be a big change so I wouldn't recommend this as part of STONEINTG-842

diff --git a/status/reporter_gitlab_test.go b/status/reporter_gitlab_test.go
index 8c1115a..2f2d21a 100644
--- a/status/reporter_gitlab_test.go
+++ b/status/reporter_gitlab_test.go
@@ -211,6 +211,27 @@ var _ = Describe("GitLabReporter", func() {
                                })).To(Succeed())
                })

+               It("creates a commit status for snapshot with TargetURL in CommitStatus", func() {
+
+                       PipelineRunName := "TestPipeline"
+                       expectedURL := status.FormatPipelineURL(PipelineRunName, hasSnapshot.Namespace, logr.Discard())
+
+                       muxCommitStatusPost(mux, sourceProjectID, digest, expectedURL)
+                       muxMergeNotes(mux, sourceProjectID, mergeRequest, "")
+                       muxCommitStatusesGet(mux, sourceProjectID, digest, nil)
+
+                       Expect(reporter.ReportStatus(
+                               context.TODO(),
+                               status.TestReport{
+                                       FullName:            "fullname/scenario1",
+                                       ScenarioName:        "scenario1",
+                                       TestPipelineRunName: PipelineRunName,
+                                       Status:              integrationteststatus.IntegrationTestStatusInProgress,
+                                       Summary:             "summary",
+                                       Text:                "detailed text here",
+                               })).To(Succeed())
+               })
+
                It("does not create a commit status or comment for snapshot with existing matching checkRun in running state", func() {
                        summary := "Integration test for snapshot snapshot-sample and scenario scenario1 is running"

/retest

@14rcole the code looks all set, but needs a rebase on latest main to pass EC checks.


enable specifying koji target in build command

This is a first pass on #264.
CC @dustymabe @jlebon
The second thing to do would be to implement service's side of this: https://github.com/packit-service/packit-service/issues/46
The question also is if you guys want to perform upstream releases for every
build or if you want to build every PR in that tag (for that, we would also
need to teach packit to submit koji builds using a local SRPM).
This PR also carries commits from #414, will rebase once that one lands.
Edit: okay, I just read #264 once more and indeed we need to 1) teach packit tool to submit koji builds from local SRPMs 2) teach packit service to submit koji builds for upstream PRs. Will create a dedicated issue for that.

The question also is if you guys want to perform upstream releases for every build

What we're specifically looking for Packit to do is continuous git master Koji builds into a specific target. So ideally without tagging each time. :)
These builds are separate from upstream tagged releases (which would go into the regular Fedora Koji targets and repos). I'd love to automate that process as well, though the biggest pain point right now is continuous builds.

or if you want to build every PR in that tag

We're not looking to cover PRs with this yet, just git master pushes. (I think it's a nice idea for CI purposes though, though we usually have lower overhead methods of testing PR code which don't involve building RPMs).

@jlebon, so this is what you are looking for: https://github.com/packit-service/packit-service/issues/47; it's a bit sparse but that should resolve the issue 100 %

@TomasTomecek Yes, that's exactly it. :+1:

rebased

rebased


Playbook.py doesn't work normally in Nornir Automation on Ubuntu linux

I have a issue that I can't run normally playbook.py and I changed the config.ymal, groups.yaml, defaults.ymal, hosts.yaml and already download nornir install, nornir-scrapali, nornir-napalm, but I don't know why this error happening. Pls help me how to resolve this issue.

@Kendric47 Looks like the connection to devices is not successful, could you verify the authentication details?  As it is multithreaded, could you please check if any processes are running in the background? If everything looks fine then send me the detailed logs.


German translation of new strings, 3 corrections, new English SetLaun…

The title really says it all. :)

Thanks Christoph.


brew: Conciser error when run from nonexistent directory

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example. No. This seems a little tricky since it'll require wrangling an ongoing subshell while interleaving file system operations, and it's not part of core brew operations, so maybe we can let this slide.
[ ] Have you successfully run brew style with your changes locally? No. brew style doesn't cover the brew bash script.
[ ] Have you successfully run brew tests with your changes locally? No, but I don't think it's a regression; see notes below.

This PR makes brew emit a more concise error message when it is run from a directory that does not exist.
I know this may sound like a pedantic issue, but I actually run in to this quite a bit in practice, when I have one terminal window open somewhere in my Cellar, and I've uninstalled some stuff from another terminal window.
This PR doesn't change any real behavior, but produces a more concise, readable error message, which I think makes for a better user experience.
Before:

$ brew --version
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Error: The current working directory doesn't exist, cannot proceed.

Gross.
After:
$ brew --version
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Error: The current working directory doesn't exist, cannot proceed.

Nicer.
I can't figure out how to get rid of that last shell-init error message; suggestions welcome.
To reproduce:
In terminal A:
mkdir foo
cd foo

In terminal B:
rmdir foo

Back in terminal A:
brew --version

Possible Issues
Are there cases where a user might be calling brew --prefix or something similar from a context where there is no cwd? I can't think of any, but you never know. This could break those.
Test Failures
When I run brew tests, I get this failure:

Failures:

  1) OS::Mac::language can be parsed by Locale::parse
     Failure/Error: expect { Locale.parse(subject.language) }.not_to raise_error

       expected no Exception, got #<Locale::ParserError: '' cannot be parsed to a Locale> with backtrace:
         # ./locale.rb:15:in `parse'
         # ./test/os/mac_spec.rb:19:in `block (4 levels) in <top (required)>'
         # ./test/os/mac_spec.rb:19:in `block (3 levels) in <top (required)>'
         # ./test/spec_helper.rb:112:in `block (2 levels) in <top (required)>'
         # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:120:in `block in run'
         # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:109:in `loop'
         # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:109:in `run'
         # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
         # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:34:in `block (2 levels) in setup'
         # ./vendor/bundle/ruby/2.3.0/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'
     # ./test/os/mac_spec.rb:19:in `block (3 levels) in <top (required)>'
     # ./test/spec_helper.rb:112:in `block (2 levels) in <top (required)>'
     # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:120:in `block in run'
     # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:109:in `loop'
     # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:109:in `run'
     # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # ./vendor/bundle/ruby/2.3.0/gems/rspec-retry-0.6.0/lib/rspec/retry.rb:34:in `block (2 levels) in setup'
     # ./vendor/bundle/ruby/2.3.0/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

Deprecation Warnings:

Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /usr/local/Homebrew/Library/Homebrew/test/cache_store_spec.rb:24:in `block (3 levels) in <top (required)>'.

If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

1 deprecation warning total

Finished in 1 minute 2.89 seconds (files took 1.67 seconds to load)
585 examples, 1 failure, 3 pending

Failed examples:

rspec ./test/os/mac_spec.rb:18 # OS::Mac::language can be parsed by Locale::parse

But I get the same failure when running brew tests from master, so I don't think this PR caused the regression.
I also get these warnings, I don't know if they're related:

$ brew tests
Randomized with seed 352
4 processes for 226 specs, ~ 56 specs per process
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.6-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.6-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.6-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.6-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Run options: exclude {:needs_linux=>true}
.....Run options: exclude {:needs_linux=>true}
.Run options: exclude {:needs_linux=>true}
............Run options: exclude {:needs_linux=>true}

I also get these warnings, I don't know if they're related:

https://github.com/Homebrew/brew/pull/4222

Makes sense, thanks @apjanke!

Run options: exclude {:needs_linux=>true}

@reitermarkus I believe you introduced needs_linux a while ago (correct me if I'm wrong)? It would be good if that was omitted or only displayed once, too.

Here's a PR to omit it: #4296.


This Was Not A Permanent Fix

I followed the directions outlined in this article and it does work to change the command processor window, but when I closed it down and opened it back up it was back to baby blue (the original color I wanted to change).  My real problem is that I changed the color to baby blue awhile back and forgot how I did it.  I never planned to leave it that way, it was just something I learned to do one day and was playing around with.
Anyway, everywhere I searched I found the same solution that you have outlined here.  I tried both properties and Default but always had the same result.  When I shut it down and re-opened it, it was always back to baby blue.  Then on How-to-Geek's page about changing cmd colors, I actually read what it said inside their example picture of Command Processor.  There, for the first time, I seen the words "DefaultColor registry" and that lead me to my breakthrough.

I GOOGLED “CHANGE DEFAULT COLOR REGISTERY VALUE”.  (I SPELLED REGISTRY WRONG)

That took me to this page:
https://www.google.com/search?client=opera-gx&q=CHANGE+DEFAULT+COLOR+REGISTERY+VALUE&sourceid=opera&ie=UTF-8&oe=UTF-8
Web results
Showing results for CHANGE DEFAULT COLOR REGISTRY VALUE
Search instead for CHANGE DEFAULT COLOR REGISTERY VALUE

I SELECT THE FIRST CHOICE ON THIS PAGE:

That took me to this page:
https://www2.isye.gatech.edu/~mgoetsch/cali/Windows Configuration/Windows Configuration Html/SettingtheDefaultColorfortheCommandProcessor_WindowsNTonly_.htm
Setting the Default Color for the Command Processor ...
Setting the Default Color for the Command Processor (Windows NT only) ... the default colors in the command processor windows by editing the Registry directly ...

THIS INFORMATION WAS SO PERFECT I WANTED TO SEE WHAT ELSE I COULD LEARN BUT THERE WAS ONLY 3 SMALL ICONS IN THE TOP LEFT.  ONE TOOK ME TO A CONTENTS PAGE THE OTHER TWO WERE FORWARD AND BACK ARROWS.  BY THE LOOK OF THE CONTENTS PAGE I CAN LEARN A GREAT DEAL FROM THIS INFORMATION WHEREVER IT CAME FROM.  I ONLY WISH I COULD THANK THE PUBLISHER.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 959d4b23-8fd3-0404-f2b3-9397fbe9dce2
Version Independent ID: e860e4fa-0075-7df0-0780-cb4f2c86ced3
Content: color
Content Source: WindowsServerDocs/administration/windows-commands/color.md
Product: windows-server
Technology: windows-commands
GitHub Login: @eross-msft
Microsoft Alias: lizross

Please note that CMD windows have 2 sets of properties:

Defaults
Properties

You did not spell "registry" wrong. The person responsible for that page you found to be most helpful to you does probably not have English as their native language, making it more likely that typos and misspellings happen more frequently on non-official pages than official pages (I know, official pages get misspellings too, although a bit less frequent).

Microsoft Docs is not going to adapt material from the outside, unless the source belongs to a well-known Microsoft Partner or affiliated organization.

Please don't use ALL CAPS when posting friendly information. It tends to come across as less friendly or shouting.

Unless you can point to some factual errors on the page, it is highly unlikely that your research to solve a singular issue for yourself can be used as basis for documentation change. Most IT Pro admins are fully aware of how to solve this issue. This documentation site is also intended for IT Pros, not so much for the general public non-professional internet audience as such.

#please-close

I apologize for the all caps.  I am dyslexia and it helps me to read what I
type, which is also why I've made a habit of taking the blame when it comes
to spelling discrepancies.  I had also tried both of these, "Default" and
"Properties" but still when I re-opened cmd the color reverted to baby blue
with black text.  This is a lovely point for point outline of how I somehow
was out of my league when I posted a solution that worked, but my question
is this.  If you are all so intelligent that this is something you all
automatically know how to do, why did I need to go to another website to
find a solution that worked for me?  I won't bother your website ever
again.  I prefer to stick to sites that have solutions to problems, not
just the ones that tell me how a computer is supposed to work.  Thanks for
telling me how smart you are though.  Here's a video you should check out.
https://www.youtube.com/watch?v=GJz66wm95-M
On Fri, Sep 18, 2020 at 7:46 AM Trond B. Krokli<EMAIL_ADDRESS>wrote:

You did not spell "registry" wrong. The person responsible for that
page you found to be most helpful to you does probably not have English as
their native language, making it more likely that typos and misspellings
happen more frequently on non-official pages than official pages (I know,
official pages get misspellings too, although a bit less frequent).
2.
Microsoft Docs is not going to adapt material from the outside, unless
the source belongs to a well-known Microsoft Partner or affiliated
organization.
3.
Please don't use ALL CAPS when posting friendly information. It tends
to come across as less friendly or shouting.
4.
Unless you can point to some factual errors on the page, it is highly
unlikely that your research to solve a singular issue for yourself can be
used as basis for documentation change. Most IT Pro admins are fully aware
of how to solve this issue. This documentation site is also intended for IT
Pros, not so much for the general public non-professional internet audience
as such.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windowsserverdocs/issues/4829#issuecomment-694796987,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARBFTPT4Y5DJOOXF2KIAZFTSGM3BPANCNFSM4RRNBONQ
.


feat: Change all the dependency errors at once

Proof of working
So I start with my VM that is in a <IP_ADDRESS> state, and install lnd, configure, then install bitcoin.
Then I pull image from build server, and updated to that.
Now we should be on our latest cod, cb723a8 (the build is 1008b2, but that is a merge + master)

Then in the LND we see the message that we are expecting,


Ticking entity killing player?

Playing with a friend and suddenly it starts killing his "entity" and now cannot pick up items within the world.

Can you send the server's latest.log please.
you can find it here https://fabricmc.net/wiki/player:tutorials:logs_ml:windows

This release should fix that issue, a ticking player should be kicked instead of killed https://github.com/Bawnorton/Neruina/releases/tag/1.2.3


Can I access the review approval+reject+comment panel without waiting for a long diff to load?

Gitea version (or commit ref): 1.8.2
Git version: 2.x
Operating system: windows 2012
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
I often receive pull requests consist of 1000 lines changed scattered in 70 files. The diff takes a while to load. The approval+reject+comment panel is inaccessible before the diff is 100% loaded in the browser. I normally do code review with custom scripts outside Gitea.
Screenshots

If the gitea diff does not finish loading in a few minutes, I normally merge in CLI on client side, then push to the develop branch in gitea. The approval is bypassed. The PR is merged.

The diff may be 100 pages long. The html source is 170,000 lines long. The review button is still loading and inaccessible.
70 changed files with 5701 additions and 3125 deletions

Reducing these numbers in the config file probably helps:
MAX_GIT_DIFF_LINES
MAX_GIT_DIFF_LINE_CHARACTERS
MAX_GIT_DIFF_FILES

Hi @yanOnGithub I think we do need to look at this properly. I suspect that we need to make the diff page do some Ajax requests rather than do it all in one go.

I think @zeripath probably want to increase the capacity of the diff page. Consider something like midnight commander 2-panel interface. List of files on the left, and a diff of the selected file on the right. Consider supporting infinite scrolling on the diff panel. Humans TLDR and a way to locate something is needed.
3-panel design can be "directory tree" + "files in selected directory" + "diff of selected file"
Dumping the full diff of all changed files can overflow the browser. In the current design, some interactivity happens on each line. A large amount of DOM node or html source may be there to support the interactivity.
MAX_GIT_DIFF_LINES
MAX_GIT_DIFF_LINE_CHARACTERS
MAX_GIT_DIFF_FILES
Limiting these 3 config variables allowed the reviewer to click the approve and reject buttons. I am running git diff $mergeBase..$featureHead outside the browser anyway. A pull request with 180 MB files changed is looming. The PR comes with both text and binary files. I need the text file diffs for code review. Binary files are not analyzed in my code review.
Consider re-opening this issue for feature enhancement.

top and bottom panel design would allow long paths and lines


cruller-harsh

A cruller is a deep-fried pastry shaped into a twisted, braided form. The code defines randomized parameters such as canvasCenter, crullerRadius, crullerScale, and rotationAngle, which introduce variability to each generation.

Your submission is very similar to this piece. If you take inspiration you should give attribution. Plagiarism is against Hack Club's code of conduct and could result in bans for participating in other Hack Club programs. I'll just give you a warning now.

I'll submit a new submission, but this wasn't plagiarism, but rather created with the assistance of ChatGPT.


relates to #1734: int tests for get document and sub-document

Draft, in-progress
What this PR does:
A draft for integration tests for the Docs API V2 get document and sub-document.
Which issue(s) this PR fixes:
Relastes to #1734
Checklist

[ ] CI passed
[ ] Automated Tests

@EricBorczuk be aware, seems that CollectionsResourceIntegrationTest is failing now due to that Quarkus 405 issue..


Fix races found by go -race

Avoid sharing memory between main and the spinner goroutine.
Also adds a synchronized buffer to the tests to avoid races
between writes in the spinner goroutine and reads in the tests.
Fixes #22

This is great.  Thanks!


Kubernetes config starter add Constraint dependency spring-cloud-starter-bootstrap and ruins app with consul-starter

All we need is only reading configmaps, and we try to use the minimal dependency for this purpose.
Describe the bug
Using:
spring-cloud-starter-kubernetes-config (2.0.0-M6)
spring-clous-consul-config (3.1.0)
After startup application fails with:
***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method configWatch in org.springframework.cloud.consul.config.ConsulConfigAutoConfiguration$ConsulRefreshConfiguration required a single bean, but 2 were found:
	- configDataConsulConfigProperties: a programmatically registered singleton	- consulConfigProperties: defined by method 'consulConfigProperties' in class path resource [org/springframework/cloud/consul/config/ConsulConfigBootstrapConfiguration$ConsulPropertySourceConfiguration.class]

Action:

Consider marking one of the beans as @Primary, updating the consumer to accept multiple beans, or using @Qualifier to identify the bean that should be consumed

Searching of configDataConsulConfigProperties in all scope don`t give me a result.
Sample
After Gradle build --scan:

Can we disable it by exclude?
Or should I use spring-cloud-starter-kubernetes-client-all instead starter-config?

Try using the spring cloud bom rather than managing dependency versions yourself

@ryanjbaxter , thanks. But we already have on classpath api(platform("org.springframework.cloud:spring-cloud-dependencies:2021.0.1")), which goes with our custom dependency-management-bom (on screenshot). Or its not "spring cloud bom"?
Or i must exclude explicit implementation("org.springframework.cloud:spring-cloud-starter-kubernetes-config:+")?

It doesn't make sense why you would have milestone builds on the class path then.  Please provide a sample to reproduce the problem

I can`t provide a sample to reproduce right now, cause our apps uses such properties for deploy to k8s (and custom Gradle plugins), and my example can be irrelevant.
Now i tried with implementation("org.springframework.cloud:spring-cloud-starter-kubernetes-config:1.1.10.RELEASE"), and build scan havent bootstrap constraint deps, but application not going for configmaps when in logs
The following 2 profiles are active: "kubernetes", "production"
SPRING_CLOUD_KUBERNETES_ENABLED: true

Without a sample its hard to determine what might be wrong.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Meet with the WET team

to raise awareness of the pilot and document possible use cases

Meeting scheduled for April 1.

Done


Create document (Loop) to track customer questions (FAQs), feedback, to build onboading guide

loop


Adding stored procedure support

This change adds a last step for using the UDF code as a stored procedure. It also includes revisions designed to make the content more scannable for users who might just be looking it over.
This content is a revised version of the Snowpark Getting Started Quickstart, which is supported by sample code that is also revised in a separate PR. Ideally, both should be merged more or less together.
Changes include:

Updated the code to use an edited Scala sample from the sfguide-snowpark-demo repository.
Rearranged the text to flow amid the refactored demo code — function by function instead of all as a single piece.
Made a few changes designed to make each page a bit more scannable:

Moved what felt like subsections into bulleted or numbered lists.
Added subheads to break things up a bit.

Added the stored procedure step.

Fantastic updates -- thank you for the PR!


Fixed terraform virtual server example

Signed-off-by: Roland Urbano<EMAIL_ADDRESS>Description
Fixed the terraform example for virtual_server and corrected the disk label.
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

/ok-to-test sha=602e15c


README.md linking for dev use instructions fail

As far as I can make out this package shouldn't have a node_modules directory because it has no node.js dependencies.
https://github.com/alphagov/digitalmarketplace-frameworks/blame/master/README.md#L134
Therefore this won't work:
A local checkout of the frameworks repo can be shared with locally-running services (i.e. frontend applications)
as follows:

- from this repo, run `node_modules/bower/bin/bower link`
- from each app, run `node_modules/bower/bin/bower link digitalmarketplace-frameworks`

I've worked around this by installing bower globally and linking this package globally like so:
- from anywhere, run `sudo npm install -g bower`
- from this repo, run `bower link`
- from each app, run `bower link digitalmarketplace-frameworks` or `node_modules/bower/bin/bower link digitalmarketplace-frameworks`

I'm not much of an npm / bower guy so I'll need some input as to whether or not this has any caveats @galund

Weird - I'm sure people have had the bower link stuff up and running in the past.

This is clearly my fault, I think I probably copy-pasted my new instructions from another repo (the instructions about this were missing from all of them).
You can certainly install bower globally, or alternatively use any of the bowers that you've installed elsewhere (if you give a full path). Feel free to update the readme, it'd be nice if it made sense.
Otherwise, assign me this issue, and I might get around to it sometime :)

I reckon it'd be nice to avoid recommending global bower.

Maybe a  makefile command or something.
make bower_link <my_local_frameworks>
To be run from each of the frontends.
On 3 Apr 2017 2:07 pm, "Kevin Keenoy"<EMAIL_ADDRESS>wrote:

I reckon it'd be nice to avoid recommending global bower.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/digitalmarketplace-frameworks/issues/412#issuecomment-291137179,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADTyEDR2WYbCXS4tjkj1Ev8PBeH91BIRks5rsO8DgaJpZM4Mvwso
.

If make is to run bower, it still has to be able to find it somewhere :/

Oh, no I understood what you mean now. Yep.

I don't like installing things globally either but Bower is generally designed to be installed globally as it's a node command line tool.
https://docs.npmjs.com/getting-started/installing-npm-packages-globally

Saw this ticket and felt ashamed... I've updated the readme, I didn't include the sudo because it wasn't necessary for me, and hopefully wouldn't be for anyone else as long as npm is set up right.
https://github.com/alphagov/digitalmarketplace-frameworks/pull/485

Readme fixed up, merged.


Fix SIGABRT on tf.image.encode_png with empty tensor

This fix address the issue raised in #31429 where SIGABRT was thrown on tf.image.encode_png with empty tensor.
Instead of thrown out SIGABRT, this fix adds the error checking so that InvalidArgument was returned gracefully.
This fix fixes #31429
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@rthadur sorry for the late reply. The email notification before slip through. I have rebased and update the PR. Can you give it a try and see if the issue still exist?

@rthadur Sorry for the late reply as I was mostly out of office year end (was back last week). I will take a look at the errors shortly.

@yongtang Can you please check mihaimaruseac's comments and keep us posted? Thanks!

It has been 15 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


refactor client

remove client interface
remove pool interface
remove http helpers
improve README.md

Codecov Report

Merging #10 (c1af66f) into master (261d8c5) will decrease coverage by 0.56%.
The diff coverage is 50.00%.

:exclamation: Current head c1af66f differs from pull request most recent head 6092c40. Consider uploading reports for the commit 6092c40 to get more accurate results

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   95.48%   94.91%   -0.57%
==========================================
  Files          31       28       -3
  Lines         753      649     -104
==========================================
- Hits          719      616     -103
+ Misses         20       19       -1
  Partials       14       14

Impacted Files
Coverage Δ

client.go
90.41% <20.00%> (ø)

pool.go
86.61% <80.00%> (+0.35%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add a Service in Azure subdomains

Hello Team,
I have been reviewing the Docs for Azure Domains and I have discovered something that I think we can improve.
https://docs.microsoft.com/en-us/azure/security/fundamentals/azure-domains
For example, the following reference mentioned that the domain *.cloudapp.net can be used for both Azure Cloud Service (Classic PaaS) and Azure Virtual Machines (Classic), and it is OK.
Azure Cloud Services and Azure Virtual Machines | *.cloudapp.net
However, the doc also mentions that the subdomain cloudapp.azure.com is only used by Azure Cloud Services (Extended Support), however, after further investigation I can confirm that Azure Virtual Machines can also use this sub-domain
Azure Cloud Services | *.cloudapp.azure.com
For example:
Azure Cloud Service

Azure VM

Thanks in advance for your help

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 790ff17b-0306-897d-f0df-59dd92441426
Version Independent ID: 6bfac7c1-8909-73f9-4212-26cc7ffaaa81
Content: Reference list of Azure domains
Content Source: articles/security/fundamentals/azure-domains.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @memildin
Microsoft Alias: memildin

@cabermu Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @cabermu , thanks for reaching out about this. I'm confirming this and if so I will update the document.
Best,
James

Thanks, @James-Hamil-MSFT.
Please go ahead and update the page.
I'm no longer working in the docs org, but I assume I'll retain ownership of this for a while until a suitable candidate takes over the topic.

Hi @cabermu @memildin , I have created a PR here: https://github.com/MicrosoftDocs/azure-docs-pr/pull/186521
I will close this issue now. Please let me know if you have any questions.
Best,
James

Hello James,
Thanks for your help. Unfortunately, I am not able to access the PR to check the status, but I will keep an eye to confirm if the doc is updated later.
@.***
Thanks in advance,
Carlos Bermúdez López
Support Engineer
Azure PaaS Developer
Office Phone: +506 4114-2699
<EMAIL_ADDRESS>Working hours 8:00am to 5:00pm( UTC -6)
If you need to work with another Support Engineer outside of my working hours, please send email to<EMAIL_ADDRESS>with your case number, and availability.
We are always interested to hear your feedback. Please feel free to reach my manager regarding the level of service you have received at<EMAIL_ADDRESS>[MSFT_logo_Gray DE sized SIG1.png]
From: James Hamil @.>
Sent: Thursday, January 27, 2022 2:47 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Carlos Humberto Bermúdez López @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Add a Service in Azure subdomains (Issue #86534)
Hi @cabermuhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabermu&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=SiWW8JCAllRZ31pQLo1rOfv76d9QS5U2k%2Bw%2Fv6aP%2B7g%3D&reserved=0 @memildinhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmemildin&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=4SDPmfXrT%2FGvR6YM5FjAjGcEMJ4CCSG9c5yb%2FZ58SZ8%3D&reserved=0 , I have created a PR here: MicrosoftDocs/azure-docs-pr#186521https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs-pr%2Fpull%2F186521&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=tacIFdRTuJs%2BkJq%2BY8gMeF%2FXQAH46EVYjTczkEQWbl8%3D&reserved=0
I will close this issue now. Please let me know if you have any questions.
Best,
James

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F86534%23issuecomment-1023624215&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=j%2FHevAMD2NT7ufvagerOZNZxo4066NgLNhOq3czNRWk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXK7W563Z7OLIWMZPHBGRZTUYGVKTANCNFSM5MFQLI5A&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=WDoo3iiGxDY6mqLzC7F2tgFF8k5kYg9%2FKXYsk1y52%2FY%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=AKAgmq7sGg3xZQCAtndlFUZGiXVoz4owBmy59EA4mtg%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Carlos.Bermudez%40microsoft.com|fdd8ef97769f48935ecc08d9e1d61aa6|72f988bf86f141af91ab2d7cd011db47|1|0|637789131976863997|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=S9vMNAZB%2FAHdFjNCoCJJAxD0gV6mDqnkXpYQGiwhF78%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @cabermu , certain PRs are private but this one just merged to master if you want to check shortly.


Record version 1.0 of the OpenTracing specification

This is a slightly more formal and less language-specific "spelling" of the content at opentracing.io/spec.
Once this is merged, the opentracing.io/spec content will still exist but will mostly be a link to this document and some short explanatory / contextual text with links to other areas of the docs site.
I also want to create .yaml versions of the "official" standard tags and (hopefully) standard structured log keys, include them in this repo, and link to them from this spec.
cc @yurishkuro @wu-sheng (who both commented on the branch pre-PR), as well as @adriancole @jmacd @cwe1ss @dawallin @codingfabian @basvanbeek @beberlei @dkuebric @lookfwd @michaelsembwever who might want to weigh in.

@bensigelman do you think this should completely replace http://opentracing.io/documentation/pages/spec.html page? There's a very large overlap, but some explanation on the existing page are not included here, for example there was a page-long description of childOf/followsFrom references, which I think should be included in the Spec.

@bensigelman , what is the relation between specification.md and  data_conventions.yaml. It seems two separated files.
Maybe, should add a link in specification, guide reader to data_conventions ?

@wu-sheng my intention with this repository was to make it more about data and specifications and less about "documentation" per se (which is the job of opentracing.io's repo). That said, the commit I'm about to make does include a cross-ref to the .yaml file from the spec file.
I do think the .yaml should be its own thing since various scripts could be built to process it and auto-generate standard tags in each language repository.

@bensigelman , oh, I see.

I'll merge this in 24-48h if there aren't further comments. Thanks!

@bensigelman , this will be a seperate page in spec doc? And should I add up a translation on this?

@wu-sheng I was going to keep the existing opentracing.io/spec URL valid but make it much shorter... probably just a description of OpenTracing's master versioning scheme as described at #2, a link to the formal specification in this PR, and maybe some text about what the spec actually means (i.e., that it describes "pure" OpenTracing APIs and not their implementations from various vendors). Maybe there will be a diagram or something.
Regarding translation: I mean, it's great if you want to translate it, sure. It's a lot of ongoing work to maintain that but I'm certainly not complaining!

Yes, translation is always an on-going job, I assume. :)
I just want to do it, on a checkpoint, or a frozen version.


v-ref issue in side v-for

I am using Dropzone within a v-for and v-refs are not supported.  Can you indicate if there is a work around for this or can you call the Dropzone methods directly without $ref?

.....

.....

The following gives "can not give property of 'processQueue' of undefined
console.log(this.$refs.myVueDropzone.dropzone.processQueue() );

Hmmm interesting one @glowens , could you perhaps use this.$children (doco) to find the component?

Thanks.  I was able to use this.$children and was able to get to the methods I needed.  I was hoping there could be an easier way.

Sorry @glowens nothing comes to mind. Closing as it's not really an issue with this component, more to do with Vue itself.


"constant" not found

According to https://github.com/microsoft/nn-Meter/blob/76d7f881e18cb0012ee5887abe8baabd58e40f1b/nn_meter/ir_converter/frozenpb_converter/frozenpb_parser.py#L252 "constant" should always be saved under graph[in_node]["attr"]["attr"], but we got
                        graph[in_node]["attr"]["constant"]. Is this a bug or I missed an edge case?

Could you please add a test case with bug information? I think it would help us to locate the problem.

Hi Yuqi, I noticed that you have reported a number of issues with the frozenpb converter. I would like to understand more about your project and if you have any test cases that can help demonstrate the problems you are encountering. It is possible that there may be some edge cases that have not been considered previously.


Fix DevMode test project and target directories

Another approach to fix https://github.com/quarkusio/quarkus/pull/25504

Wrong project :-/


Fix Mobile-Responsive breaking layout

Issue Reference: #463
On devices with width less than 450px, the layout corrupts and the card goes "outside" of the screen. This is fixed in this commit

Excellent thanks for your PR!


Compatibility with spring-data-rest

Hi!
Thanks for this project!
I tried to integrate it with spring-data-rest to expose my entities. It worked quite well with minor adoptions:

Major bummer is that org.springframework.data.rest.webmvc.config.RepositoryRestMvcConfiguration.persistentEntities() searches for MappingContexts whereas the DynamoDBMappingContext is created with new in org.socialsignin.spring.data.dynamodb.repository.support.DynamoDBRepositoryFactoryBean<T, S, ID>
Second problem is that org.socialsignin.spring.data.dynamodb.mapping.DynamoDBMappingContext.hasPersistentEntityFor(Class<?>) always returns false before a class is manually added.

To workaround those two problems, I added to my own ConfigurationBean the following code:
    @Bean
    public DynamoDBMappingContext getMappingContext() {
        DynamoDBMappingContext context = new DynamoDBMappingContext();

        context.getPersistentEntity(MyDynamoDBTable.class);

        return context;
    }

I can't really judge if that is cleaver because that leads to multiple DynamoDBContexts floating around but as they are usually only delegating to another constructor that seems fine to me.
Is there a better way to do it?
Can this somehow be incorporated into the library itself so that it is out-of-the-box Spring-Boot compatible?
Used versions:

Spring Boot 1.2.3.RELEASE
spring-data-dynamodb 1.0.1.RELEASE
spring-boot-starter-data-rest 1.2.3.RELEASE

I had the same problem although I found a different solution. I manually exposed the existing MappingContext from the DynamoDBRepositoryFactoryBean:
@SuppressWarnings("rawtypes")
@Autowired
private DynamoDBRepositoryFactoryBean dynamoDBRepositoryFactoryBean;

@Bean
public MappingContext<?, ?> getPrivateDynamoDbMappingContext(){
	return (MappingContext<?, ?>)FieldUtils.getProtectedFieldValue("mappingContext", dynamoDBRepositoryFactoryBean);
}

Not the best solution either, but it works. (And if the DynamoDBMappingContext changes by any reason later, it will still work.)

Without this - PUT requests won't work to update entities. I think this is a bug in the current implementation and needs adressing. I used the solution from @Selindek to work around it as well.


GDB/MI command parser refactoring, compatibility fixes

Dropped my fork, and forked again.

This looks better, thanks.


En/Decoding CTEXT

It's very complicated and old encoding
so it's better to use xlib code from https://gitlab.freedesktop.org/tpalli/libx11/-/tree/master/src/xlibi18n because its license is MIT

I miss type issue number :(


Show either error notification or modal error.

Why both are shown:

@karthiknadig how do I repro the dialog / notification showing up?

For this particular case you will need a linux environment. Ensure that the environment does not have python*-dist (basically the dist utils package). Then try to use create environment.

I uninstalled python3-distutils and creating an environment still worked 🤔

@rzhao271 Try deleting it from the location where python is installed.


Clarification and Discussion For Search Functionality [9 Nov, 23.59]

As we discussed in our meeting we're going to use DRF Search Filter for search functionality. Before starting implementation, backend and other teams should be on the same page regarding the details of search.

[ ] Find out possible search types based on project description and requirements. (e.g. location, tag)
[ ] Discuss specifics of UI capabilities and functionalities that frontend and Android teams should provide. (e.g. checkbox to filter by only one field or multiple fields)

After this work is done, conclusions could be shared on comments of this issue.

What is the progress here? @mfatihm

according to requirements, we should search in different categories: tags, keyword and location. I will ask to the frontend and mobile teams again

Search functionality should also support users just like events. So, this is another point that we should consider. So when a tag, keyword or location is searched, there will be both events and users in the response. Also, in location search, it should support city, district or both. These points should be discussed with Android and frontend teams.
For backend side, in the description, it says that

The application should also allow semantic search, which will try to ﬁnd semantically similar users and events based on the context information provided in the semantic tags. For example, semantic search can be used to retrieve events of similar genres that the user did not specify directly.

This doesn't seem obvious to me, maybe we can ask details about this to Suzan Hoca or Meric.

It will be searched in events by default. if the user wants to search in users, it should click the link that searches in users. Semantic search will be about related tags

Basic search is implemented.

Users can be searched by username, first name and last name.
Events can be searched by title, description, city and district.

Details can be found in API Docs.


Crash in beginning of transaction (isar_flutter_libs: _$LT$crossbeam_channel..channel..TryIter)

Steps to Reproduce
It's one of those sentry bug reports without a reproducible example. Sorry Simon 🙈
This issue happend while someone was closing the app. Maybe the app was writing to the database while the database was about to close.
Code sample
The example is the same as in #1312
Details

Platform: iOS 16.5,  iPhone XR
Flutter version: 3.10.2
Isar version: 2.5.0 3.1.0

No other issues found that describe the exact same problem.

Haha how do you find these lol. This is great thanks. The good news is this issue will be fixed in v4 since this particular code has been replaced completely

Wait... Version 2.5?

Sorry of course 3.1.0, that was a typo 🤦🏽

First version in about a week 🙂

This is fixed in Isar v4


Remove unreachable code

check() already calls log.Fatal if err != nil, so this code is redundant

thanks!


Mouse event optimization

Mouse up currently sends 2 requests -> released, clicked
We should reduce this to 1 request -> requires a new server command or an option in the request: autoRelease or something else.

no optimization required


Fix

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

Please upload report for BASE (main@6e65f7b). Learn more about missing BASE report.

Files
Patch %
Lines

benchmark/benchmark.py
0.00%
30 Missing :warning:

albucore/utils.py
78.94%
4 Missing :warning:

albucore/functions.py
93.61%
3 Missing :warning:

setup.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage        ?   37.88%
=======================================
  Files           ?        8
  Lines           ?      483
  Branches        ?        0
=======================================
  Hits            ?      183
  Misses          ?      300
  Partials        ?        0

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


Transition from conda installation to direct pip installation

Really minor dependencies so kind of unnecessary to require a specific env.
Would make this much easier to use.

need to remove plotly too in lieu of matplotlib


Bump to Java 1.45.1 in the interop client matrix

@nicolasnoble

Started adhoc interop test run: https://source.cloud.google.com/results/invocations/571589e5-3ce5-4a8d-992a-7149c0a97415


Result model

Make sure that the result model matches https://github.com/unitaryfund/metriq-api/blob/main/metriq-api/models/resultModel.js

Done


Replace settings dict guide with SettingsCreator reference

Given the way we advocate doing things in Splink 4 we should replace the Settings Dict Guide with a SettingsCreator reference.

But we do have SettingsCreator appearing in plenty of examples, so not hugely pressing


doc update for third_party_libraries info

to: @airbnb/streamalert-maintainers
Changes

Doc update for third_party_libraries info in general section of global.json

Coverage remained the same at 95.43% when pulling 56fbc181b85f68c22ea700dac2bcd5fca5f86f0e on ryandeivert-docs into abd21881951a3b6ac7d76a1c0ec2def16d71098c on release-3-2-0.


CAPI v1.6.0-beta.0 has been released and is ready for testing

CAPI v1.6.0-beta.0 has been released and is ready for testing.
Looking forward to your feedback before v1.6.0 release!
For quick reference

CAPI v1.6.0-beta.0 release notes
Shortcut to CAPI git issues

Following are the planned dates for the upcoming releases
CAPI v1.6.0 will be released on Tuesday, 28th November 2023.
More details of the upcoming schedule can be seen at CAPI v1.6.0 release timeline.

/close
Implemented in #143.


Force GPU Script doesn't enforce/run properly

Question and Setup
I can post the exact setup I have but basically I have

an EVGA GEFORCE RTX 2070
Intel i7 9000 series
the NVIDIA Container Toolkit installed,

this file structure:
- blender/
  - cool_scene.blend
- imgs/
- scripts/
  - force_gpu.py
- config.yaml

and am running:
docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=all --rm -v /home/tennisgazelle/dev/blender-pipeline/imgs/:/imgs/ -v /home/tennisgazelle/dev/blender-pipeline/blender/:/blender/ -v /home/tennisgazelle/dev/blender-pipeline/scripts:/scripts -v /home/tennisgazelle/dev/blender-pipeline/config.yaml:/config.yaml vogete/blender-cuda blender/cool_scene.blend --python scripts/force_gpu.py -f 1

Error
And I get this error:
Fra:1 Mem:77.62M (0.00M, Peak 77.62M) | Time:00:00.02 | Compositing | Tile 40-40
Fra:1 Mem:77.62M (0.00M, Peak 77.62M) | Time:00:00.02 | Compositing | De-initializing execution
Fra:1 Mem:77.62M (0.00M, Peak 77.62M) | Time:00:00.02 | Sce: Scene Ve:0 Fa:0 La:0
Saved: '/imgs/buffer/cool_scene_scene_0001.png'
 Time: 00:00.33 (Saving: 00:00.31)

Traceback (most recent call last):
  File "/scripts/force_gpu.py", line 6, in <module>
    prefs.compute_device_type = 'CUDA'
TypeError: bpy_struct: item.attr = val: enum "CUDA" not found in ('NONE')
Intel Core i7-9700K CPU @ 3.60GHz
Error, region type 9 missing in - name:"Buttons", id:4

This is quite interesting. Originally I made this script for a university project where I used 4x RTX 2070s, which is exactly what you have. However, back then CUDA 10.0 was only available, and since then CUDA higher versions have been released. I think you are currently using CUDA 11 drivers, which is why the container is not recognizing the GPU. Currently I don't have any dedicated nvidia graphics equipped computer, so I can't test this, but, I have an idea how to fix it.
First of all, could you run the following and check if the RTX 2070 shows up?
docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=all --rm --entrypoint "" vogete/blender-cuda nvidia-smi

(normally you should also have nvidia-smi installed outside of docker though, so it might be interesting to just ran that too, and compare if there's any difference between the docker and non-docker output. You can also see the CUDA version there)
To use a more recent CUDA, please clone the repo, change the first line of the blender-cuda-docker/blender2.79b/cuda10.0/ubuntu18.04/Dockerfile file to the following:
FROM nvidia/cuda:11.3.0-devel-ubuntu20.04

This basically just makes the image to use a newer CUDA version on ubuntu 20.04 (original nvidia CUDA docker image: https://hub.docker.com/r/nvidia/cuda).
Try building this Dockerfile now, then run the created image. I was planning to update the repo to use more recent versions of Blender, CUDA, and Ubuntu, I just don't have the hardware to test if rendering still works. I'll try to get one on my hands though :)

Hi, thanks for the speedy and comprehensive reply :)
Running the command gives me this, which tells me it is indeed able to see the device:
Thu May 27 23:14:42 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.80.02    Driver Version: 450.80.02    CUDA Version: 11.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 2070    Off  | 00000000:01:00.0  On |                  N/A |
|  0%   28C    P8    20W / 185W |    765MiB /  7981MiB |     18%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

The same output shows up for nvidia-smi outside of the container, but the processes block includes the games i have running as well as the X server (desktop gui, i presume)
You can take a look at this repo so that you can see the stuff I've been doing with your images and the things that I've been putting into the Makefile for different commands/checks I've been doing with them.  (Obviously, I'll credit this repo and you in the readme under the Acknowledgments section)
https://github.com/TennisGazelle/blender-pipeline/tree/use-gpu
I have tried to integrate them into my own Dockerfile (and Dockerfile.gpu) and tweaked it but to no avail.
I had written my own version of a user-preference updater that's similar to your force_gpu.py called enable_gpu.py (in the scripts/ folder)

Well, it's good to see that at least the docker image recognizes the GPU. This kind of points to Blender being an issue. Since it's currently using version 2.79, it might be too old for running on CUDA 11. I don't really understand why it doesn't run with the CUDA 10 enabled image to be honest... (maybe the underlying container toolkit is a newer version than what I used previously, and uses your CUDA 11 drivers, and Blender doesn't see that properly? Because clearly nvidia-docker is functioning correctly if it can see your 2070...)
Anyway, what if you try to use a newer Blender version? I read it from a few threads that CUDA 11 is not supported before 2.91.
I can see the mirror I used have changed quite a bit for newer versions, so maybe use this Dockerfile instead:
(changes are just a new URL, new base image from nvidia, and not using bzip2 for extracting the archive, since it's not bz2 file anymore)
FROM nvidia/cuda:11.3.0-devel-ubuntu20.04
MAINTAINER Zoltán Fraknói

ENV BLENDER_TAR_URL http://ftp.nluug.nl/pub/graphics/blender/release/Blender2.92/blender-2.92.0-linux64.tar.xz

RUN apt-get update && \
	apt-get install -y \
		curl wget nano \
		bzip2 libfreetype6 libgl1-mesa-dev \
		libglu1-mesa \
		libxi6 libxrender1 && \
	apt-get -y autoremove

# Install blender

RUN mkdir /usr/local/blender && \
	wget --quiet ${BLENDER_TAR_URL} -O blender.tar.xz && \
	tar -xvf blender.tar.xz -C /usr/local/blender --strip-components=1 && \
	rm blender.tar.xz

VOLUME /media

ENTRYPOINT ["/usr/local/blender/blender", "-b"]

I'll be honest, I have no idea why it doesn't work...The only difference for me when I used it was the driver versions, and the CPU (I used an I7-6700K), and neither of them should (in theory) be the problem.

So I kept going at this and messed around with versions and have been trying to compare rendering times for CLI (headless) vs GUI, but I think my standard GUI rendering is messed up to begin with; it says there's no compatible GPUs for rendering properly.  I'll get back to this thread after I figure out that one first.  That could've been the culprit to begin with (although I had that before so IDK what happened)

I managed to get an XPS 17 9700 (i7-10750H, GTX 1650 Ti) with Ubuntu 20.04 and nvidia-docker. Blender 2.79b was not working for me with CUDA, but it did not throw the error message you had (it just used the CPU without errors). I made a few newer versions, blender 2.83 and 2.92 with both cuda 10.2 and 11.3 images (ubuntu 18.04 for cuda 10.2, and 18.04 or 20.04 for cuda 11.3). Since Blender 2.8 introduced some changes, the force_gpu.py script I had was not working anymore, so I included a new one (enable_gpu.py). With that one, it works for me just fine on all versions of the Blender 2.83 and 2.92 images (both CPU and GPU rendering, depending on which one I chose).
So it's quite weird you're getting this issue to be honest. For me it was a bit painful to get nvidia-docker up and running, but once it worked, all images rendered on cuda just fine.

FWIW, I got it to work in my setup by running the enable script immediately before the force script.
/media/blendfile.blend -E CYCLES -t 0 -P /media/enable_gpu.py -P /media/force_gpu.py -o /media/frame_### -f 1


[10.x] Implement a new --open option for the artisan serve command

This PR adds a new --open option to the artisan serve command which when supplied, will open the application URL in the browser automatically.
Here's what that will look like!
https://github.com/laravel/framework/assets/3647841/5c582ce5-4f2f-49d5-9d51-44a4eb87ed41
Let me know what you think about it.
P.S.:- Regarding tests, I wasn't able to find any test cases for the serve command. So, haven't added them for now.

You can already just command+click on the URL in the terminal.

Or are you open to implementing something similar to this?


🐛 Bug: Incorrect positioning when using tooltip and dropdown builders

👋
Loving the library so far, thank you so much for your work. I'm having a little issue when trying to compose multiple builders, in this case the tooltip and dropdown menu. It seems to position the tooltip incorrectly. Am I doing something wrong or is this a possible bug?

Code

Result
Hovering over the screen icon on the far right produces this tooltip positioned on the far left.

Can you drop a Stackblitz repro link so I can further investigate? I haven't actually tried combining them like that before so I'm intrigued!

Sure!
https://stackblitz.com/edit/melt-ui-playground-raaejq?file=src%2Froutes%2F%2Bpage.svelte

Yeah, I definitely see the issue, and I think this is likely a common use case (hover over the button to see what it does and click to open a dropdown).
I'll work on pinpointing this issue, if it's not possible with the current APIs, we may be able to make it possible with our "Big Bad" refactor we're working on.

Okay so after looking into this a bit it makes more sense. Basically what's happening is you're overriding one of the attributes of the component or the other (dropdown & tooltip). The other elements use some of those attributes to determine how they will behave, which I've come to learn may be an issue on our end.
As a temporary fix, if you spread the tooltip store last on the element, the tooltip will work as expected, but it may have unexpected effects on the dropdown menu, the example repro doesn't have a menu buildout for me to see that for certain, but I'd appreciate it if you could let us know.
I'm glad you opened this issue because it has caused me to find some issues in our tooltip implementation.
More specifically, both triggers (tooltip and dropdown) apply aria-controls an attribute, which I'm not sure is necessary for the tooltip according to this pattern (but it's late and I could be missing something).
So we may need to make some changes there. Additionally, our tooltip doesn't apply the aria-describedby attribute to the trigger which should reference the id of the tooltip content, so we potentially don't need an id on the tooltip at all, which I believe would get rid of most conflicts it may have with the dropdown.
I'll defer to @TGlide for his thoughts on the matter before taking any action though!
Thanks again for raising this issue @mihar-22!

Thanks, appreciate the update!
Adding my notes on the issues I'm seeing:

Setting tooltip trigger after menu trigger works, but the the tooltip remains visible when the menu is closed and the pointer is not on the tooltip trigger.
The aria-describedby attribute is missing on the tooltip trigger on hover/focus.
The role="tooltip" is missing on tooltip content.
The aria-controls should not be set for a tooltip trigger.
The aria-expanded attribute should not be set for a tooltip trigger.
The aria-expanded attribute not updating correctly when both a tooltip/menu trigger is applied.

Thanks @mihar-22! @TGlide & I have discussed this extensively and I have submitted a PR that should fix this issue for you, but I'd appreciate a confirmation once the updates are released if it's behaving as you'd expect!

Yep can confirm all bugs have been resolved! Thank you.
There's only a slight issue if you open a menu with a tooltip, and then click away to hide the menu, the tooltip doesn't disappear (requires second click). It's not a big deal and I can open a separate issue later, main things are all fixed.


Capsule Collider

It would be great to have additional capsule colliders.
Arm and hands and shoulders (sphere collider get s really big) are hard to cover with sphere ones.

Implemented in CPUTFXCapsuleCollision_Burst component


Auto-CSP generates invalid loader scripts for some

Command
build
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Auto-CSP relies on rewriting scripts of the form <script src="..."></script> into an inline loader script that will dynamically re-create these tags and add them to the DOM.
There are some <script src="..."> configurations that generate inline loader scripts that will not run on the transformed page, such as

Having your <script src="..."> tag appear in the <head> rather than the <body> of the document.
Having your <script src="..."> tag interpreted as something that will create a type="undefined" attribute on the generated node added to the DOM

Minimal Reproduction
The index.html should have the following:
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <base href="/">
  <script src='script1.js'></script>
</head>
<body>
  <app-root></app-root>
  <script src='script2.js'></script>
  </body>
</html>

Exception or Error
`script1.js` and `script2.js` do not run.

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1900.3 (cli-only)
@angular-devkit/core         19.0.3 (cli-only)
@angular-devkit/schematics   19.0.3 (cli-only)
@schematics/angular          19.0.3 (cli-only)

Anything else relevant?
No response

Proposing #29055 to fix this issue.

Closed via https://github.com/angular/angular-cli/pull/29055


How to use a socket as input

Is there a way of using a socket connection directly as a stream?
I only see examples of StringStream and FileStream but don't know how to get data from a socket

Unfortunately sockets don't have a stream defined for them in the stdlib. This means that you have to implement the stream interface over the stream yourself. If you look at the StreamObj you can see which procedures you'd need to implement. I don't think all of those are required for binaryparse though, and things like setPosition is only used to go forward in binaryparse so you can get away with implementing it as a writing of 0 bytes and discarding of input data for a read.

Thank you for the prompt and most complete response. Thought it might be the case but wanted to make sure.


Feat/add bitget perpual candles

…load candles)
Before submitting this PR, please make sure:

[ ] Your code builds clean without any errors or warnings
[ ] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
This merge request introduces support for downloading candles and backtesting functionality for bitget_perpetual. Once integrated, this feature will enable dashboard support for candle downloads upon the completion of the "add_bitget_perp" branch integration in the following repository: https://github.com/mfuentescas/dashboard.
Tests performed by the developer:
I have tested the feature using the Bitget Perpetual dashboard with the following sections:

Config Generator: Visualized and backtested Bollinger V1 and PMM simple strategies. Checked saving + loading is still right.
Data: Visualize and downloaded candles.
In any case, I have validated timestamps obtained are the same that with "binance_perpetual" under the same config.

Config used:

Intervals: Tested different intervals (1m, 5m, 1h).
Symbols: BTC-USDT pair.
Dates: Various start/end dates in 2023 and 2024.

Non tested:
CandlesBase websocket was not tested, I could not find where it is used.
Tips for QA testing:
None.
Tips for further development using this feature:
It is important to keep in mind, in Bitget, intervals are in uppercase for hours, days and weeks. By now is managed by BitgetPerpetualCandles class with no problem.

hi @mfuentescas please review contribution guidelines.
https://hummingbot.org/developers/contributions/
https://hummingbot.org/developers/contributions/#checklist


cameraProps produce issues for Android.

Everything was working fine.
Then i try to restrict scanning for QRCode & PDF417.
I use this line to restrict scanning:
cameraProps= {{barCodeTypes: ["org.iso.QRCode", "org.iso.PDF417"]}}
After this, iOS works fine. But Android stops scanning everything.

@fahadibrahimbutt could you provide a demo repo reproducing this issue to make it easy to help you?

@fahadibrahimbutt just add one more type
cameraProps={{ barCodeTypes: ['QR_CODE', 'org.iso.QRCode', 'org.iso.PDF417'] }}

lets us know @fahadibrahimbutt if it worked because as @Zo2m4bie commented it seem that will be work

@Zo2m4bie the solution you shared works for QR Codes. Can you share a way to scan all supported barCodeTypes other than QR Codes?

@Zo2m4bie the solution you shared works for QR Codes. Can you share a way to scan all supported barCodeTypes other than QR Codes?


Fix typo

I also propose changing

A pair of counters is cool, but what about a list of counters

to

A pair of counters isn't cool. You know what's cool? A list of counters.

Lol, I like it :) From The Social Network right?

Yeah ;)