Reconsider the highly fragile Builder

It's way too simple to create or compose JsonFormat instances that end up throwing runtime errors.
Here's a sample when running sbt/sbt's "actions/all" scripted test:
[info] sjsonnew.SerializationException: Unexpected builder state: End
[info]     at sjsonnew.package$.serializationError(package.scala:19)
[info]     at sjsonnew.Builder.stateError(Builder.scala:184)
[info]     at sjsonnew.Builder.beginArray(Builder.scala:66)
[info]     at sbt.internal.util.HListFormat$$anon$2.write(HListFormat.scala:25)
[info]     at sbt.internal.util.HListFormat$$anon$2.write(HListFormat.scala:23)
[info]     at sbt.internal.util.HListFormat$$anon$2.write(HListFormat.scala:27)
[info]     at sbt.internal.util.HListFormat$$anon$2.write(HListFormat.scala:23)
[info]     at sjsonnew.SupportConverter$class.toJsonUnsafe(SupportConverter.scala:23)
[info]     at sjsonnew.support.scalajson.unsafe.Converter$.toJsonUnsafe(Converter.scala:7)
[info]     at sjsonnew.SupportConverter$$anonfun$toJson$1.apply(SupportConverter.scala:14)
[info]     at scala.util.Try$.apply(Try.scala:192)
[info]     at sjsonnew.SupportConverter$class.toJson(SupportConverter.scala:14)
[info]     at sjsonnew.support.scalajson.unsafe.Converter$.toJson(Converter.scala:7)
[info]     at sbt.internal.util.PlainOutput.write(Output.scala:15)
[info]     at sbt.internal.util.FileBasedStore$$anonfun$write$1.apply(CacheStore.scala:39)
[info]     at sbt.internal.util.FileBasedStore$$anonfun$write$1.apply(CacheStore.scala:39)
[info]     at sbt.io.Using.apply(Using.scala:23)
[info]     at sbt.internal.util.FileBasedStore.write(CacheStore.scala:39)
[info]     at sbt.internal.util.Tracked$CacheHelp.save(Tracked.scala:58)
[info]     at sbt.internal.util.Tracked$$anonfun$inputChanged$1.apply(Tracked.scala:52)
[info]     at sbt.Classpaths$.cachedUpdate(Defaults.scala:1669)
[info]     at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1519)
[info]     at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1471)

I've hit this general problem in different manifestation over the last few weeks switching sbt's modules to sjson-new.
I've never run into these kinds of runtime errors when defining custom JSON typeclass instances using play-json.

I agree with builder API being too low level in most cases.
I already created #12 for porting Play's DSL. In the interim, LList isomorphism could also be used.

Defining how a type is serialising to JSON should be as simple as https://www.playframework.com/documentation/2.5.x/ScalaJson#Using-Writes-converters

Builder abstraction does have the benefit of performance and backend isolation. It's just not for most users to directly use it, and that's partially why Contraband exists.

It's should be generally easier to not make trivial mistakes (even when using Contraband, for types that are not defined using Contraband).
That should be a bigger priority than performance or backend isolation.

I'm not sure if this the same issue or a separate issue, but I've been hit by the fragility of the Unbuilder too:
[info] sjsonnew.DeserializationException: Expected Map as JsObject, but got JArray([Lscala.json.ast.unsafe.JValue;@45dd46fa)
[info] 	at sjsonnew.package$.deserializationError(package.scala:18)
[info] 	at sjsonnew.support.scalajson.unsafe.Converter$FacadeImpl$.extractObject(Converter.scala:111)
[info] 	at sjsonnew.support.scalajson.unsafe.Converter$FacadeImpl$.extractObject(Converter.scala:9)
[info] 	at sjsonnew.Unbuilder.beginPreObject(Unbuilder.scala:89)
[info] 	at sjsonnew.FlatUnionFormats$$anon$2.read(FlatUnionFormats.scala:120)
[info] 	at sbt.internal.util.HListFormat$$anon$2.read(HListFormat.scala:35)

The flat union formats assume that they are being called inside a JObject. But in the case of HListFormat, this isn't true, as HList's serialise to arrays. :-( :-1:

Btw this is what's causing dependency-management/cache-update to be broken.

I think this points more to the difficulty in rolling out custom HList encoding.
I'd recommend projecting it to the date types that I've provided codecs for like tuples and LList.

No. I think it's a mistake to blame the choice of how HList wishes to serialise itself to JSON.
If you use another type, that also encodes to a JSON array, which contains types that are have flat union formats, you're going to run into the same runtime issues.
We should be leveraging the typesystem to encode these contraints, rather then have these incompatibilities clash and crash all over the place - I noticed also the:

BEWARE:  A1,  A2 must be a concrete leaf type, and not an interface.

on the flat union formats - another way in which things can blow up at runtime.


New package: Dojo v0.1.0

Registering package: Dojo
Repository: https://github.com/dojo-sim/Dojo.jl
Created by: @simon-lc
Version: v0.1.0
Commit: 0f7101e81f4c6180f8a063381c79a44606662691
Reviewed by: @simon-lc
Reference: https://github.com/dojo-sim/Dojo.jl/commit/0f7101e81f4c6180f8a063381c79a44606662691#commitcomment-67752966
Description: A differentiable simulator for robotics

[noblock] We would love to name our package Dojo so that it matches the ecosystem of tools that we develop and the research paper we published. Our package is also completely unrelated to the packages having similar names so the risk of confusion is lower.
Thanks for your help!


joker: init at 0.8.5

Motivation for this change
Adding Joker, a Clojure interpreter/linter written in go.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I've opened an issue at upstream as v0.8.5 had a problem that was preventing it from building correctly. Now v0.8.6 has been released, builds correctly here and I've updated the PR. Should I update the PR name or commit message to correctly reflect that it's v0.8.6?

Sure, could you squash the commits into one with 0.8.6 in it?

Additionally I've prevented the installation of generators that were not meant to be installed into bin.


Update near-api-js when https://github.com/near/near-api-js/pull/620 is released

This PR https://github.com/aurora-is-near/rainbow-bridge-client/pull/45 installed near-api-js from commit to handle borsh in viewMethods

@paouvrard Can we update to the latest release of near-api-js? This module assumes singleton ethProvider/nearConnection and it's hard to use different versions of near-api-js in the dependency tree.

@raymondfeng This PR https://github.com/near/near-api-js/pull/620 doesn't appear to have been release in near-api-js.
cc @mfornet

Resolved.


Call::as_xml_rpc is pub(crate)

So following up from our previous conversation, I decided to take a quick and dirty shot at literally copy-pasting client.rs into my crate, get it building, then adapt it to my needs (SCGI over TCP/UDS).
I got everything working except for Call::as_xml_rpc() being pub(crate) and so inaccessible to my crate. Curious if this was intentional and what you think about it.
https://github.com/ironthree/dxr/blob/7147b9b703ff9cb884dd72eb5625d5bab65c21ef/dxr_client/src/lib.rs#L153
https://github.com/ironthree/dxr/blob/7147b9b703ff9cb884dd72eb5625d5bab65c21ef/dxr_client/src/call.rs#L48-L50

There's no reason for it being pub(crate) and not pub other than ... it was not necessary to make it pub before. :)
But given that it's unlikely to change, I can certainly make it pub with the next release.

Published as version 0.5.1:
https://github.com/ironthree/dxr/releases/tag/0.5.1
I think with this (and custom implementations of request_to_body and request_to_result) you should be set. Let me know if there's something else you need.

Thank you so much!


fix(s2s-cli): short error message

What: ENOENTのとき、エラーメッセージを短く

Why: #105

How:

Checklist:

[ ] Documentation
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

Closes #105

Coverage remained the same at 100.0% when pulling fe1090ed09e97447c02a036ec058d961761b1192 on pr-enoent-error into cc09268776d7b49498b872a9660f0ad7be206e80 on master.

Coverage remained the same at 100.0% when pulling c7eb0eac640841001f9c636bb2741985d3d62c6d on pr-enoent-error into cc09268776d7b49498b872a9660f0ad7be206e80 on master.

Coverage remained the same at 100.0% when pulling 32d41550ddb5ca684f4aff8bee8cc3a434260eda on pr-enoent-error into cc09268776d7b49498b872a9660f0ad7be206e80 on master.


Update

For some reasons the App is not available in some regions. Europe/Munich, in my case
Users have to change their appstore regional settings to...US i think?
Thanks in advance @FaizanDurrani


For browsers and Deno

Hello, thank you for the great plugin.
synckit uses worker_threads. This is problematic to run on browsers.
To handle this issue, I have created the alternative unasync.
Please consider to merge my request. Cheers.

Does it support edge functions? synckit depends on @pkgr/utils, but @pkgr/utils directly calls process.cwd(), which is not supported on edge functions, causing me to encounter an error on Vercel's edge functions.

Yes. Because unasync is also available for browsers, which do not have 'process.cwd()'.


(LOW) Extend default RecordSource by child which can handle RecordEntity save/update operations

So it can be used as more clean DataMapper.

Move serialization of update to RecordEntity and make it public;


Component Model

How to categorize this PR?

/area oci
/kind task
/priority 3
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

Integration test has not yet  run.


Update Composer dependencies (2022-02-15-00-03)

Visual regression test passed!
View the visual regression test report


Update installation guide URL for download Istio candidate

To verify run the following command and see the download complete message on cli.
$ curl -L https://istio.io/downloadIstio | ISTIO_VERSION=1.7.0-alpha.2 sh -

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
9600e0b73363e92ad139f7498021ceeb95b9a3af
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

In response to a cherrypick label: new pull request created: #26113

I don't think this should be backported to 1.7. IMO the short URL should redirect to master, see https://github.com/istio/istio/issues/26115. I'll ping folks on Slack about it.

I don't think this should be backported to 1.7. IMO the short URL should redirect to master, see #26115. I'll ping folks on Slack about it.

@jwendell The URL that I have added just points to https://istio.io/latest/docs/setup/install/ which is Installation Guides. Which will be displayed in the CLI output after running curl. So it's just the more info instruction we show it to users. I think it has nothing to do with actual downloading istio release.


Content of NumberInput Not Scrollable on Safari

Describe the bug
The NumberInput component is not scrollable when the content exceeds the visible area on Safari. This issue prevents users from being able to view or edit the full content.
Expected Behavior
The NumberInput should be scrollable, allowing users to view and edit all content.
Actual Behavior
The NumberInput is not scrollable, and the overflow content is not accessible.
Steps to Reproduce

Open Safari.
Navigate to the page containing the NumberInput component.
Enter content that exceeds the visible area of the NumberInput.

Screenshots/Videos
No response
Operating System
MacOS
What browsers are you seeing the problem on?
Safari
Browser version
No response
What device are you using?
Desktop, Mobile
Related Issues:
#81 #82

Duplicate of #82, since number inputs are just text inputs


Investigate: disable setContextClassLoader calls within JRuby

I got the following error during executing output-elasticsearch plugin. The root cause is that a context classloader cannot find the resoruce file. The problem might occur during other Java plugins are executed.
org/elasticsearch/env/Environment.java:213:in `resolveConfig': org.elasticsearch.env.FailedToResolveConfigException: Failed to resolve config path [names.txt], tried file path [names.txt], path file [.../config/names.txt], and classpath
	from org/elasticsearch/node/internal/InternalSettingsPreparer.java:119:in `prepareSettings'
	from org/elasticsearch/client/transport/TransportClient.java:157:in `<init>'
	from org/elasticsearch/client/transport/TransportClient.java:115:in `<init>'

assigned to @nahi


deisctl dock requires full name of the container

Most other commands rely on deis- as a prefix. For example, deisctl journal controller will retrieve the logs for the deis-controller component. However, deisctl dock requires the full name:
$ deisctl dock controller
Excuting 'docker exec -it controller sh' on container 'controller'
FATA[0000] Error response from daemon: no such id: controller
$ deisctl dock deis-controller
Excuting 'docker exec -it deis-controller sh' on container 'deis-controller'
/app #

Related to #4210

^ This is solved pretty easily after that's merged.  Will hold on it until then.


Menu bar doesn't work at <1024px width

Steps:

launch the web page
resize the viewport so the width is less than 1024px

Expected:
The menu bar is still usable.
Actual:
The menu bar is completely gone.
System:
Linux Mint
Chrome 58
Firefox 53

This isn't completely fixed but it's a lot better. Now the menu stays visible and I've made it drop the logo and the "case studies" item as the viewport shrinks further. The style-new.css has the notion of desktop-menu and mobile-menu but we aren't using it. Ideally we would leverage the mobile-menu for smaller screens but I'm not convinced that it's even configured right. style-new.css:224 has:
  @media screen and (min-width: 64em) {
    .mobile-menu {
      display: none;
      height: 0;
      overflow: hidden; } }

Why min-width, shouldn't it be max? Seems like a copy-paste error.
Alternatively, we already have Bootstrap so we could swap to using their navbar: https://getbootstrap.com/components/#navbar. Then we have less CSS to maintain.

Fixed enough, we can open a new issue for re-doing the navbar to properly support mobile width viewports.
Committed on dev branch.


Restructured project

Renamed to pycrust10
Created setup.py to make it available to install from pip install <path>
Added data_path parameter to CrustModel constructor. Allows to use external files.

Hi!
I'm currently using this as a dataset for an earthquake prediction model I'm working with Machine Learning, for my data science course
crust1 would be more descriptive I think.
If you want, I can rename the package and make a commit

Sure. I think we'll be good to merge then.


[T7][F09-C2]

Some comments added. Please close the PR after reading comments. Overall you guys did a good job, though I think you forgot to add a command to say if a task is completed. :) Remember to keep a reasonable level of code quality at all time. Code quality is not something you can do later.


V0.12.0.x SecondsSincePayment

Changes to SecondsSincePayment:

fix buffer overflow (memcpy from uint256 to int64_t was causing it, using GetCompact now instead)
change logic (force unknown/unpaid it to be more than 30 days old)
move implementation to cpp

Good idea about enforcing more than a month old too

Seems like this commit broke the windows build

@schinzelh How so? :( Got any logs?

@UdjinM6 n/m, CI server had a out of disk space error ^^

@schinzelh phew :)


Add godoc badge

People expect to be able to find the godoc from github via this link.
Signed-off-by: Justin Cormack<EMAIL_ADDRESS>

circleci unrelated - maybe needs prodding...

LGTM


Fixed unit test with stochasticity by fixing its random seed.

This fixes a situation where a stochastic unit test would (knowingly) fail for certain realizations of a point process by setting the random seed to a value.

Coverage increased (+0.002%) to 93.323% when pulling 277d38fa6045990feb6e95ea019cb96d80fb2fbd on INM-6:bug/poisson_tests into a54eb906bcdfff2eaeb9c49e54fa97dd8df648b4 on NeuralEnsemble:master.


OU-248: Add Alerts Detail Page

ODC-7640
OU-248
This PR is the counterpart of one in the console (PR) which looks to transfer the dev perspective alerts detail page out of the console codebase and into the monitoring-plugin. This PR must merge before the one in the console has.

The only change to the dev perspective alerts detail page is that it will no longer have a namespace selector. Since the selected alert is already namespaced, it didn't make sense to swap namespaces while focused on a specific alert.

Upon further review, due to the fetch-alerts.tsx file combining a number of different API calls, I don't think it would be best to refactor the useRulesAlertsPoller to use the useURLPoll. I believe that we should keep them as separate polling implementations for now

/jira refresh

/jira refresh

/hold

Unlike the alerts list stories when this PR is merged but the one in the console isn't merged, the alerts detail page will be unavailable. I'm putting a hold on this story so that QE could take a look at both parts together before this merges

tested with PRs
launch 4.17.0-0.nightly-2024-07-17-183402,openshift/monitoring-plugin#131,openshift/console#14072 aws
there is one bug: https://issues.redhat.com/browse/OCPBUGS-37232

/unhold

/lgtm


Notify users that LoggingRoute is not available for the embedded fluentbit config

Added notification into logging the logging status' problems field

added in https://github.com/kube-logging/logging-operator/pull/1542


[Feature request] Line continuations

I'm almost certain this has been mentioned before, but I cannot find an issue for it. If there is one, please point it out and close this one.
What I'm asking for is a feature that exists in some form or another in almost any programming language where line breaks matter: indicate that a specific newline character should be ignored.
For instance, consider a long macro that accepts an arbitrary number of data values:
  sillymacro $01, $01, $02, $03, $05, $08, $0d, $15, $22, $37, $59, $90, $d9

While that example isn't long enough to become unreadable, it should be easy to see how that would certainly happen if the list of values was two or three times as long. It forces a choice of line-wrapping or horizontal scrolling, both of which are confusing and unnecessary.
An effective solution would be to indicate to split the values into multiple lines. In order to do that, the assembler has to know that a certain line break only exists for formatting purposes and should be ignored. A way in which this can be achieved is C-style newline escaping:
  sillymacro $01, $01, $02, $03, $05, \
             $08, $0d, $15, $22, $37, \
             $59, $90, $d9

...or Visual Basic-style line continuation markers:
  sillymacro $01, $01, $02, $03, $05, _
             $08, $0d, $15, $22, $37, _
             $59, $90, $d9

Disregarding the exact character used for this purpose, the main differences between both styles are that newline escaping requires the escape character to be the very last character on the line (line continuation markers tolerate trailing whitespace), but line continuation markers are tokens by themselves and cannot occur within other tokens (on the other hand, newline escaping can occur inside a string literal, for example).
Whichever solution is picked, line continuations would certainly make macros with long (read: variable) lists of arguments more usable.

I'm in favor of \ at the end of the line.  It'd be great for strings as well.

For strings you can just split them like:
DB "String"
DB " and more string"

I don't really like the idea of applying that to strings (or comments), to be honest.
However, in general this would be useful, I agree.

The above doesn't apply when the string is an argument to a macro, sadly.

Fair enough, but for that to work with strings the string has to continue at the start of the line. That's essentially the same as just wrapping the lines in your editor.

For macro arguments, why not STRCAT?


Make Adam mode flags not hyperparameters

Fixes #7513

Pros

The flags are usually not considered as hyperparameters.
A user should not change hyperparam.amsgrad without considering whether to reset state['vhat'].  The PR will slightly work as a foolproof.

Cons

It seems safe to turn on or off hyperparam.amsgrad just once.  A user might have done so because it's easier than copying all the Adam hyperparameters.
While the PR is non-compatible, the main purpose looks refactoring.  FYI, I gave up #4069.

Other comments

Given adabound is not a hyperparameter, how about setting hyperparameters final_lr and gamma only if adabound == True?
IMO, it's not so bad to regard Hyperparameter as a set of attributes with centralized control.  (I remember https://github.com/chainer/chainer/pull/3940#discussion_r155844059.)  In the official code, however, it sounds good to restrict the usage to real hyperparameters, where "real" means "genuine" and "float".


QC Updates for Diagnostic yaml File and Detector Status Model

The yaml file has been updated with missing documentation and tests have been added. I have also removed the Station Down status since it does not currently exist in the current PeMS and feedback from district is needed to see if it provides any value. Once this PR is ready for merging the int_diagnostics__detector_status will need a full refresh. Linking #398 since this is related.

Looks great to me! Minor comment (optional to change): when nds.detector_feed_working = 'No' then 'No Data' does this make sense to say ' when nds.detector_feed_working = 'No' then 'Detector Down' like others.

I used "No Data" to be consistent with what the current system uses. If the team agrees that "Detector Down" is a better description than I would concur with you and change it:


DevOps Automation SIG Meeting - Dec 21, 2023

Date
Thursday, Dec 21 2023 - 12pm ET; 5pm UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[x] Convene, roll call, welcome new people
[ ] Approve previous meeting minutes
[x]  Working Group updates

[ ] Architecture as Code - @rocketstack-matt / @yt-ms
[ ] Backstage - @cnygardtw
[ ] OSS Supply Chain Risk Management - @johnmark
[ ] Automated Change Deployment - @rvema

[ ] Topics to cover in the SIG in 2024
[ ] Add Items Here
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info
Join Zoom Meeting

https://zoom.us/j/94904595244
Meeting ID: 949 0459 5244
Passcode: 545224
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Peter Smulovics / Morgan Stanley 🏦

Matthew Bain / Morgan Stanley

Mimi Flynn / Morgan Stanley

Amol Shukla/Morgan  Stanley

Karl Moll / FINOS

Ragha Vema | Fannie Mae

Vishwanath Gorti | Deutsche Bank

JM Walker/Fannie Mae
On Thu, 21 Dec 2023, 12:11 vgorti, @.***> wrote:

Vishwanath Gorti | Deutsche Bank
—
Reply to this email directly, view it on GitHub
https://github.com/finos/devops-automation/issues/169#issuecomment-1866664445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAQEYGQGOCGLOL6JEUP5S3YKRUVXAVCNFSM6AAAAABA3ZRKK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRWGY3DINBUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

FINOS internal podcast introducing Karl to the community, but more importantly talking about how banks should be working together to understand how to use generative AI internally (best practices & interacting with regulators), particularly when it comes to emerging software licenses which might govern whether or not code scanning tools can train on particular repos. I also discuss how these conversations are similar to industry collaborative conversations around cloud usage generally and open source particularly, and the importance of compliant open source collaboration in figuring out best practices
https://www.finos.org/blog/open-source-in-finance-podcast-karl-moll-finos


When to plan to support ES5.0.0 rc

When to plan to support ES5.0.0 rc?

I released https://github.com/xbib/elasticsearch-extras-client/ with a branch for Elasticsesrch 5 https://github.com/xbib/elasticsearch-extras-client/tree/es5
The "helper" project will fade out and will be stalled end of the year.


Added importer option to SASS.

I want to use fetch/node-sass-css-importer in my build.
This PR just passes a new option importer to sass.

I'm having an issue with broccoli serve with this...
.../broccoli-sass-source-maps/node_modules/node-sass/lib/index.js:305
            bridge.success(data);
                   ^
TypeError: undefined is not a function
    at done (.../broccoli-sass-source-maps/node_modules/node-sass/lib/index.js:305:20)
    at Object.<anonymous> (.../node_modules/node-sass-css-importer/index.js:12:14)
    at Object.options.importer.(anonymous function) (.../broccoli-sass-source-maps/node_modules/node-sass/lib/index.js:308:32)
    at options.importer.(anonymous function) (.../broccoli-sass-source-maps/node_modules/node-sass/lib/index.js:308:32)

I'll investigate...don't merge just yet :)


[WIP] Tune interface about transaction executing service.

Fix #2447

:white_check_mark: Build AElf <IP_ADDRESS>64 completed (commit https://github.com/AElfProject/AElf/commit/49b1193f18 by @EanCuznaivy)


Uncaught TypeError: Cannot read property '0' of null

I tried to load your example file simple building.ifc but the error above is raised?!

Are you finding the same issue in the deployed version? Which browser are you using? Does this only happen with the simple building.ifc sample? Did you make any modifications to the IFC file?


UI Enhancement: Learning Paths Navigation Menu

The alignment of the Learning Paths navigation menu needs improvement, especially for categories with longer names. Please review and adjust the layout for better spacing and readability.
Screenshot:

wait until latest deployment is done

ok


k8s endpoint resolver adds endpoint as soon as pod goes into running state

Describe the bug
K8S endpoints resolver add endpoints to envoy configuration using watch from k8s. It does not take readiness into account.
To Reproduce
Steps to reproduce the behavior:

Deploy a sample service which takes some time (~2 minutes) to be ready.
Scale up deployment
Check endpoints configured in envoy via Ambassador
Ambassador has added endpoints even though pod is not ready.

Expected behavior
Ambassador should wait till pod goes into ready state before adding endpoints to envoy configuration.
Versions (please complete the following information):

Ambassador: 0.60.3
Kubernetes environment kops
1.12.8

I verified code at resourcefetcher.py and looks like it is doing the right thing.
For now I am closing this issue.
I will be running more test cases and will open this issue again if I am able to reproduce issue and pin point faulty code.


Error: reimport from sonarqube

Bug description
Intermittent error when reimport from sonarqube, we are using sonarqube api import
Steps to reproduce
Steps to reproduce the behavior:
use reimport api to reimport test from sonarqube
Expected behavior
reimport success without error
Deployment method (select with an X)

[ ] Docker Compose
[X] Kubernetes
[ ] GoDojo

Environment information

DefectDojo version 2.27.0

Logs

Hi @alfajr, Can you provide a longer snapshot of the logs? To see a full context, how this exception was triggered. Thank you.

fyi, I did not check if these PRs would fix your problems, but there were at least two SonarQube related updates since 2.27.0:
https://github.com/DefectDojo/django-DefectDojo/pull/9366
https://github.com/DefectDojo/django-DefectDojo/pull/9006

Hi @alfajr, Can you provide a longer snapshot of the logs? To see a full context, how this exception was triggered. Thank you.

Hi @kiblik , here longer snapshot of the logs


jx gitops webhook delete

Is there a way on how can I delete a webhook for a repo that is no longer available?
Something like jx gitops webhook update but with the delete cmd.
Please find below the state where I can't remove the webhook
~$ jx health status -A
NAME                          NAMESPACE                     STATUS                        ERROR MESSAGE
daemonset                     kuberhealthy                  OK
deployment                    kuberhealthy                  OK
dns-status-internal           kuberhealthy                  OK
jx-bot-token                  jx                            OK
jx-install                    jx-git-operator               OK
jx-pod-status                 kuberhealthy                  OK
jx-secrets                    kuberhealthy                  OK
jx-webhook                    jx                            ERROR                         no webhook registered for XXXXX-jx3-python-test: failed to create webhook "https://hook.XXXXXX.com/hook" on repository XXXXX/jx3-python-test': Not Found
jx-webhook-events             jx                            OK
network-connection-check      kuberhealthy                  OK
pod-restarts                  kuberhealthy                  OK

We were able to solve this using the link below: https://jenkins-x.io/v3/develop/faq/using/#how-do-i-delete-an-application


Parsing error with release 2024.10.2

This is related to https://github.com/saaste/fmi-weather-client/issues/58, update will be required to the newer library

Now there is fmi-weather-client library release 0.4.0 is available, I checked and it works with 2024.10.2. Please, take this in use.

I think fix is to just use latest library right https://github.com/anand-p-r/fmi-hass-custom/pull/77
locally it worked for me.

Looks like it is working from 2024.10.3 onwards.

Just triggered a new release so close this now.


Androidx

Migrate to AndroidX?

Thanks for putting in the work, but I'll probably be doing this myself in a slightly different manner. In particular, I'm aiming not to have to enable the jetifier, which I think I should be able to pull off by updating Navi for AndroidX first.


Question about the relationship to vim-test

Describe the bug
For a go test file, the commands don't seem to work properly.
Let's say I open a ..._test.go file, when I run :TestFile, it runs all the tests, and when I do :TestNearest, it correctly run the test I'm in using the following command (I'm using richgo for my go tests):
richgo test -run '\''MyTest$'\'' ./parent/child/current'; richgo test -run 'MyTest$' ./parent/child/current

However, when I do :UltestNearest, I see no Go files in /parent
I open vim in ./parent directory and I go to the file ./parent/child/current/file_test.go, and that's where I'm trying to run the tests
Also, I'm not sure if I see this error because of what's happening above, but I thought I mention this too.
When I run :UltestSummary, I see the following error:
Error detected while processing function ultest#summary#toggle[4]..ultest#summary#open[2]..<SNR>484_OpenNewWindow[29]..<SNR>484_FullRender[2]..<SNR>484_Clear:
line    2:
E118: Too many arguments for function: clearmatches

To Reproduce
I think the explanation covers this part
Expected behavior
I was expecting for vim-ultest to mimic what vim-test does, with added features
Screenshots
Here's a screenshot of the output. Maybe it's worth noting that the right border of the box seems to be missing inside tmux. when I run it outside of tmux, the box seems to be fine ....... actually, I lied! I exited and tried again and it was find inside of tmux, but I'm keeping the screenshot just in case 🙂

Sorry if I'm bothering you with all the issues I'm creating, but the plugin seems to be very promising and useful I'm doing my best to use it, but I'm not able to succeed

Thanks for the report, not too many at all! Delighted to be finding these issues!
So the issue with clearmatches has been resolved (see #19).
The issue with the border box has happened to me rarely but I can't seem to reproduce reliably, I will attempt again later.
The main issue with the runner is odd, it should be doing the exact same as vim-test. Can you post the logs after doing ULTEST_LOG_LEVEL=DEBUG ULTEST_LOG_FILE=ultest.log nvim <test-file> so I can see what is going on?

Thank you @rcarriga for your reply. I tried to debug a bit, and I think it has something to do with file paths.
I think vim-test will add a ./ at the beginning of the file, while ultest is passing the full path to it, so I think we end up with a file that's not existent. Let's say the file I'm on is in /data/temp/whatever/my_test.go, when the path is ultimately passed to vim-test, it's something like ./data/temp/..., which, of course, doesn't point to any existing file.
I tried to change expand("%:p") to expand("%") in the function ultest#run_nearest() (I was testing :UltestNearest), but it didn't help.
I didn't include the logs since I'm testing this with my company's code, so I don't want to get into any trouble, but if you think it helps, I can try to see if I can work out something (changing the names etc.)

OK no problem of course I understand with company code.  Looking at it now you're right, vim-test does some odd handling of the file paths in go that doesn't happen anywhere else.... I will try and work around it

Switched to using relative paths, turns out there was also an issue with the go runners that don't build their arguments correctly but was able to compensate.

That's great, thank you @rcarriga
The issue with clearmatches seems to be still there for me :slightly_frowning_face: , when I run :UltestSummary, I see this:
Error detected while processing function ultest#summary#toggle[4]..ultest#summary#open[2]..<SNR>495_OpenNewWindow[29]..<SNR>495_FullRender[2]..<SNR>495_Clear:
line    3:
E118: Too many arguments for function: clearmatches

Oh sorry about that didn't realise there is an issue with 8.1 patch detection (found it here https://github.com/neovim/neovim/issues/9635), I've added a check for nvim 0.5.0 which should work

I appreciate it @rcarriga for you being super fast at replying and resolving these issues. Keep it up :+1:


Getting wrong token balance

Sometimes I get wrong balance. I'm fetching "unsettled" balance with the code below. Sometimes however I'm getting a result back that does not match with the gui. (The gui is correct.) If I settle the coins into my wallet and then resubmit them to the dex this usually fixes itself but then the problem reappears.
// Get balances
let openOrders = await market.findOpenOrdersAccountsForOwner(
connection,
owner.publicKey
);
baseTokenBalance = Math.floor(
openOrders[0].baseTokenFree.toNumber() / 1000000
);
quoteTokenBalance = Math.floor(
openOrders[0].quoteTokenFree.toNumber() / 1000000
);
console.log("--------------------------------------");
console.log("baseTokenBalanceFreeRAW:  " + openOrders[0].baseTokenFree.toNumber());
console.log("quoteTokenBalanceFreeRAW: " + openOrders[0].quoteTokenFree.toNumber());
console.log("baseTokenBalanceFree: " + baseTokenBalance);
console.log("quoteTokenBalanceFree: " + quoteTokenBalance);
console.log("--------------------------------------");

Closing this since it's based on a misunderstanding on how market.findOpenOrdersAccountsForOwner works.


Update for Block Kit

Updates this sample code to use Block Kit instead of attachments

👍 LGTM overall! (but there are some var mixed with the ES6+ styles 😉)

new screenshots for the README?


build(deps): migrate from gumdrop to clap and bump abscissa_core from 0.5.2 to 0.7.0

Motivation
This PR is needed to avoid a compilation error that is likely to be added to the Rust 2024 edition, to make our dependency tree smaller.
Related: This makes the output of zebrad --help consistent with that of zebrad help.
Solution

Bumps abscissa_core from 0.5 to 0.7.0 in zebrad/Cargo.toml
Replaces gumdrop with the latest version of clap
Updates ZebradApp's impl of Application to match new method signatures
Updates commands to use clap::Parser instead of gumdrop::Options
Uses ColorChoice::Never when initializing the updated Terminal component to avoid panicking when color_spantrace::set_theme() is called after it's been set
Adds a EntryPoint::process_cli_args() method for inserting the default subcommand if one is not provided
Moves EntryPoint from the application module to commands now that it's been excluded from abscissa_core
Reverts https://github.com/ZcashFoundation/zebra/pull/6024

Review
Anyone can review.
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

➜  zebrad help
zebrad 1.0.0-rc.8

Zcash Foundation<EMAIL_ADDRESS>
Usage: zebrad [OPTIONS] [FILTERS]... [COMMAND]

Commands:
  copy-state  The `copy-state` subcommand, used to debug cached chain state
  download    The `download` subcommand
  generate    The `generate` subcommand
  start       The `start` subcommand
  tip-height  The `tip-height` subcommand
  help        Print this message or the help of the given subcommand(s)

Arguments:
  [FILTERS]...
          tracing filters which override the zebrad.toml config

Options:
  -c, --config <CONFIG>
          path to configuration file

  -v, --verbose
          be verbose

  -h, --help
          Print help (see a summary with '-h')

  -V, --version
          Print version

Can you add the tickets that are closed by this PR to the PR description?

Replaces gumdrop with the latest version of clap
Updates commands to use clap::Parser instead of gumdrop::Options

Can you open a ticket to upgrade uses of structopt in other Zebra tools to the latest clap?

Related: This makes the output of zebrad --help consistent with that of zebrad help.

This is another minor breaking change that needs to be listed somewhere. Maybe the PR can have the full list, and we can just list the major breaking changes in the CHANGELOG with a link to the PR?

Will the PR name make sense to users?

Can you change the PR name to describe the user-visible changes, and put the implementation details in the PR?

I opened this PR in case other reviewers wanted a smaller diff:
https://github.com/ZcashFoundation/zebra/pull/6826

In the merge queue:

process didn't exit successfully: /home/runner/work/zebra/zebra/target/release/deps/zebrad-4d9e827350fddfd8 (signal: 11, SIGSEGV: invalid memory reference)
Error: Process completed with exit code 101.
https://github.com/ZcashFoundation/zebra/actions/runs/5194379481/jobs/9365975834#step:15:3531


How to write custom shaders for Transformer or Exoplayers

How to write custom shaders for Transformer or Exoplayer
We are trying to write a custom shaders  for greyscale for Exoplayer
Like this
vec2 uv = fragCoord.xy / iResolution.xy;

   vec4 tex = texture(iChannel0, uv);
   vec3 greyScale = vec3(.5, .5, .5);
   fragColor = vec4( vec3(dot( tex.rgb, greyScale)), tex.a);

While the demo application provides example of greyscale  and few others for color manipulation, which are based on Grayscale transformation matrix using the BT.709 luminance coefficients
here
how do we work with GLSL openGL shaders

To use a custom shader in Transformer or ExoPlayer, you'll want to implement a GlEffect and corresponding GlShaderProgram, extending BaseGlShaderProgram, where the GlShaderProgram must reference your custom shader.
A similar GlEffect, which uses a relatively-simple fragment shader and mostly-default behavior otherwise, is HslShaderProgram, where HslAdjustment is the GlEffect and HslShaderProgram is the GlShaderProgram. You can see that HslShaderProgram extends BaseGlShaderProgram, which implements most of the common logic used in most GlShaderPrograms. From there, the GlShaderProgram references the custom shader, fragment_shader_hsl_es2.glsl.
That said, just a heads up that the sample glsl you provided seems to me like it might multiply RGB channels by .5 each, which would make them darker but not really "grayscale". Please let us know if there's any issues with our existing RgbFilter grayscale implementation, and we can consider improving it as needed

That said, just a heads up that the sample glsl you provided seems to me like it might multiply RGB channels by .5 each, which would make them darker but not really "grayscale".
i am not saying the Grayscale you provided is wrong I am just  trying to implement  different shaders thanks for the Help


[BUG] Socials tag only appears in  tag when added via FastHTML.hdrs

Describe the bug
If the Socials() tag is added as an element of a view, it appears in the <body> of the HTML. Social media sites insist on the <meta> tags to appear in the <head>.
This should inject the Socials into the <head>, instead placing it in the body, where it is ignored. _xt_resp is not handling the tag correctly. Reference result can be seen here on facebook.
@rt("/posts")
@layout
def get():
    duration = round((datetime.now() - datetime(2005, 9, 3)).days / 365.25, 2)
    description = f'Everything written by Daniel Roy Greenfeld for the past {duration} years.'
    posts = [blog_post(title=x["title"],slug=x["slug"],timestamp=x["date"],description=x.get("description", "")) for x in list_posts()]
    return (
            Socials(site_name="Daniel Roy Greenfeld",
                        title="All posts by Daniel Roy Greenfeld",
                        description=description,
                        url="https://daniel.feldroy.com",
                        image="/public/images/profile.jpg",
                        ),
            Title("All posts by Daniel Roy Greenfeld"),
            Section(
            H1(f'All Articles ({len(posts)})'),
            P(description),
            *posts,
            A("← Back to home", href="/"),
        ),)

Result:
<body>
<meta property="og:image" content="https://daniel.feldroy.com/public/images/profile.jpg">
<meta property="og:site_name" content="Daniel Roy Greenfeld">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:type" content="website">
<meta property="og:url" content="https://daniel.feldroy.com">
<meta property="og:title" content="All posts by Daniel Roy Greenfeld">
<meta property="og:description" content="Everything written by Daniel Roy Greenfeld for the past 18.95 years.">
<meta name="twitter:image" content="https://daniel.feldroy.com/public/images/profile.jpg">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="All posts by Daniel Roy Greenfeld">
<meta name="twitter:description" content="Everything written by Daniel Roy Greenfeld for the past 18.95 years.">
...

Expected behavior
...
<meta property="og:image" content="https://daniel.feldroy.com/public/images/profile.jpg">
<meta property="og:site_name" content="Daniel Roy Greenfeld">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:type" content="website">
<meta property="og:url" content="https://daniel.feldroy.com">
<meta property="og:title" content="All posts by Daniel Roy Greenfeld">
<meta property="og:description" content="Everything written by Daniel Roy Greenfeld for the past 18.95 years.">
<meta name="twitter:image" content="https://daniel.feldroy.com/public/images/profile.jpg">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="All posts by Daniel Roy Greenfeld">
<meta name="twitter:description" content="Everything written by Daniel Roy Greenfeld for the past 18.95 years.">
</head>
<body>

Minimal working example that replicates the bug:
from fasthtml.common import *

app, rt = fast_app()
@rt("/")
def get():
    return (
            Socials(
                title="Hello, World!",
                site_name="Example site",
                description="Hello, World!",
                image="/images/profile.jpg",
            ),
            Title("Hello, World!"),
            P("Hello, World!"),
    )
serve()

Environment Information
Please provide the following version information:

fastlite version: 0.0.9
fastcore version: 1.7.1
fasthtml version: 0.4.3

Confirmation
Please confirm the following:

[x] I have read the FAQ (https://docs.fastht.ml/explains/faq.html)
[x] I have provided a minimal reproducible example
[x] I have included the versions of fastlite, fastcore, and fasthtml
[x] I understand that this is a volunteer open source project with no commercial support.

@pydanny did you want to self-assign this one, or shall I look into it?

Depends on how far you want it looked at. I won't have a chance to dig in until tonight. 😁


Reduce reliance on h-as-* types when converting mf2 to AS

h-as-* types are unofficial vocab and should not be required for most cases. we should be able to determine the type from the parent property (e.g. comment:) rather than expecting h-as-comment type on the embedded object.

:+1: :+1: :+1:
extrapolating from this, we ideally need the post type discovery algorithm, right? and if we go down that road, we should just migrate to using mf2util, right?
I'm fully in support of both of those. plus we'd be able to drop a handful of other chunks of half baked mf2 handling code in favor of mf2util's real implementations, right?
let's do it!

I'm going to call this one done :) We still allow h-as-* classes to override the detected type, and we still export them in generated html, but we don't need them on input anymore.


Proposal: Add node name in  "docker images" response

Currently, the cmd "docker images" show all node images, but it doesn't have node information. Sometimes, we want to known which node the image is belong to .
So, I want to add node name in "docker images" response.
Also,  "docker images" response has five headers(<REPOSITORY><TAG><IMAGE ID><CREATED><VIRTUAL SIZE>).  Which header is better to contain the node name?

There is no good header that's why we didn't put the node name anywhere :p
Docker recently merged labels for both images and container, so this feature will come very soon.

@vieux thks.  It's very nice to have labels to put node information.

@jimmyxian maybe you know this already..just fyi: you can use the filter to get the images in a specific node "docker images --filter node=host1".

@snrism Yes, but I think it's much better to do this through label. Just like this issue(https://github.com/docker/swarm/issues/288).

Will be provided by https://github.com/docker/docker/issues/12931

PR has been merged on the docker side, we can maybe move forward on this one? Does it makes sense still?
/cc @jimmyxian @aluzzardi

Closing due to lack of activity. Please reopen if you wish to continue discussing it.


Build a crate with specific variables

Describe the problem you are trying to solve
During the build of nginx crate, I want to let users specify the version of Nginx when they use this crate as a dependency.
Describe the solution you'd like
// build.rs of crate_a
fn main() {
    let val1 = vars!("key1");
    let val2 = vars!("key2");
}

# Cargo.toml of crate_b
[dependencies]
crate_a = { version = "0.2.0",  vars = ["key1:val1", "key2:val2"] }

openssl-rust may demonstrate a way to do this

How do vars differ from features?

vars is comma separated strong of key: value pairs. It should be used in build.rs file.

The lack of such a feature (or something similar) is a major pain in the rear for me currently.
I'd like to let users of my hazptr crate define some compile time parameters for performance fine tuning. Since this crate would likely only be used by other libraries, setting a global environmental variable upon invocation of cargo (e.g. env HAZPTR_SCAN_THRESHOLD=1 cargo build) is not a realistic option.
I've tried to do this through build scripts but failed, since apparently you can not affect environment variables through build scripts across crate boundaries.

I need this feature too!
In my case, My project is determining the features of the target by a combination of variables. Currently, I worked around this by using environment variables and build script. It works, but environment variables don't affect the build hash, So, even if environment variables are changed, cargo does not rebuild it. To prevent using the wrong build, I'm using different target dirs for each combination, but it wastes too many spaces and time to build the same dependencies.
Also, I'm interested in implementing this. Can I take this?
Here are more details to implement this. If there is any suggestion, comment, please.

Define available vars & set the default value of it (Optional) in the Cargo.toml.
Expose each vars as an environment variable to access vars in the build script.
Update build metadata hash with specified vars.
Add option setting vars to build command.

@Perlmint
you can use the following in your build.rs main function:
println!("cargo:rerun-if-env-changed=YOUR_ENV");

@yaa110
Hmm... Before I tried to use rerun-if-env-changed, It looks not working on windows. But today, I tried this with the simple reproduction case on OSX. It works. 😂 I'll retry this on the windows later.

https://internals.rust-lang.org/t/pre-rfc-mutually-excusive-global-features/19618 might be an option for this.

So I was thinking about this earlier. Then I saw this issue.
Now I was thinking of it more of an expanded form of features
[features]
default = ["tls:rustls"]
[features.tls]
options = ["native", "rustls"]
rustls = ["actix-web/rustls-0_21", "dep:rustls", "rustls-pemfile", "lettre/tokio1-rustls-tls"]
native-tls = ["lettre/tokio1-native-tls", "openssl", "actix-web/openssl"]
required = true # An Option must be selected

It would be seen as more of "features with options"
cargo build --features tls:rustls

And to use them in creates
[dependencies]
my_crate = {version: "0.1.0", features = ["tls:rustls"]}

#2980 is the issue for mutually exclusive features.  The big problem with is is feature unification (if two packages set different values, what do you do?).
This is why the above proposal shifts the problem of mutually exclusive features into being "global features", bypassing unification.

Agree that #2980 could be a way to resolve this. Some of the use cases of this can also be fixed by https://github.com/rust-lang/cargo/issues/6373#issuecomment-539883793, e.g. cargo:rerun-if-env-changed=YOUR_ENV.
Starting from Rust 1.56, [env] is also available, but there is an unexpected behavior that rerun-if-env-changed doesn't work well with [env] table. We track it in https://github.com/rust-lang/cargo/issues/10358.
Close this in favor of #2980. Please let us know if we overlooked something.


Missing file throws error that shuts down gulp

I'm using gulp-file-include in a "watch". Which is problematic, since errors about missing files terminates the process.

It's not plugin problem. Streams do not support error bubbling. You can use this
gulp.task(function (done) {
  gulp.src()
    .pipe(include())
    .on('error', done)
    .pipe(gulp.dest('dist'))
});

This will good work with every plugin that throws an error.

Learning by making mistakes, the way i like it.
Thank you!

@kirillbunin It's not very popular way, but it works better another one.


Upgrading a global service results in the service scale being set to 1.

Server version - V0.43.1
Steps to reproduce the problem:
Had a setup with 3 hosts.
Create a service with global flag enabled by choosing "Always run one instance of this container on every host" option.
Upgrade this service from UI.
Once the service is Upgraded , the scale is set to 1 and only 1 instance is up and running.
UI does not send down the label for global flag for upgrade.

Tested with build from master -oct 30 - UI - v0.63.0.
When upgrading a service that was deployed with global scheduler set , all the instances get upgraded as expected and the upgraded service has global scheduler set.


Bluetooth: BAP: Filter PA data duplicates by default

When syncing via the broadcast sink or the scan delegator it makes more sense to filter on duplicates, as the expected data rarely changes.

@cvinayak do you know if this duplicate filtering also applies (or should apply) the BIGInfo reports?

@cvinayak do you know if this duplicate filtering also applies (or should apply) the BIGInfo reports?

BIGInfo reports are not filtered in the current implementation, does the spec mandate duplicate BIGInfo to be dropped?

@cvinayak do you know if this duplicate filtering also applies (or should apply) the BIGInfo reports?

BIGInfo reports are not filtered in the current implementation, does the spec mandate duplicate BIGInfo to be dropped?

I don't know - That was what I was asking you :D
But at least using the shell, we are not interested in seeing each and very BIGInfo, but only changes, so if the controller does not (or should not) filter on duplicates, I'll need to that add that in the shell myself

@cvinayak do you know if this duplicate filtering also applies (or should apply) the BIGInfo reports?

BIGInfo reports are not filtered in the current implementation, does the spec mandate duplicate BIGInfo to be dropped?

I don't know - That was what I was asking you :D
But at least using the shell, we are not interested in seeing each and very BIGInfo, but only changes, so if the controller does not (or should not) filter on duplicates, I'll need to that add that in the shell myself

No Spec does not mention filtering of BIGInfo reports, rather:

An HCI_LE_BIGInfo_Advertising_Report event shall be generated even if the
Controller is already synchronized to the BIG.

@cvinayak do you know if this duplicate filtering also applies (or should apply) the BIGInfo reports?

BIGInfo reports are not filtered in the current implementation, does the spec mandate duplicate BIGInfo to be dropped?

I don't know - That was what I was asking you :D
But at least using the shell, we are not interested in seeing each and very BIGInfo, but only changes, so if the controller does not (or should not) filter on duplicates, I'll need to that add that in the shell myself

No Spec does not mention filtering of BIGInfo reports, rather:

An HCI_LE_BIGInfo_Advertising_Report event shall be generated even if the
Controller is already synchronized to the BIG.

Interesting. Maybe I'll file an erratum for this; it does not really make sense for the host to receive the BIGInfo at every periodic interval if it does not change.
Does that also mean that the Skip parameters from the sync create is not applied to the BIGInfo either? Or the initial disabling of the reporting?

Does that also mean that the Skip parameters from the sync create is not applied to the BIGInfo either? Or the initial disabling of the reporting?

Skip parameter will skip BIGInfo too, as controller does not listen for AUX_SYNC_IND (which contains the ACAD with BIG Info struct).
Initial disabling of reporting only applies to periodic advertising reports, does not disable BIGInfo reports.

Does that also mean that the Skip parameters from the sync create is not applied to the BIGInfo either? Or the initial disabling of the reporting?

Skip parameter will skip BIGInfo too, as controller does not listen for AUX_SYNC_IND (which contains the ACAD with BIG Info struct).
Initial disabling of reporting only applies to periodic advertising reports, does not disable BIGInfo reports.

You are correct. Interesting that there is no way to filter or disable BIGInfo reports. I wonder if that is intentional or something they just forgot to add to the PA Sync command when they added the BIGInfo


session.signals and session.frames might not correctly be implementing Mapping semantics

These containers allow someone to

Iterate on the contained signals
Lookup signals by index and name (but not slice)

They were defined as implementing the Mapping abc.  The concern is that when you iterate on other mappings, you get the keys back.  To iterate on the values, you need to call mapping.values().

For context, nidaqmx has a similar contain, channel collections.

Iterate on channels
Lookup channel by index, name, or slice

Instead of implementing Mapping, they implement Sequence.

Its unfortunate that Python does not explicitly define the semantics of the collection ABCs.  It just says "dict did this" and says what functions need to be implemented.

RE: breaking-change label
If signals and frames are changed to a sequence

keys, items, values, and get function might not exist (get might be left on anyways)
Instead an index function will exist that looks up the index for a given value.

if signals and frames are kept as a mapping

iterating on it will return names.  Instead call values() or items()


Missing settings event in forms module

added forms.settings.aside event to enable the in_menu feature

Thanks!


Try fix transparent window

What does the pull request do?
Fix https://github.com/AvaloniaUI/Avalonia/issues/11802
What is the updated/expected behavior with this PR?
Window became non-transparent
How was the solution implemented (if it's not obvious)?
https://learn.microsoft.com/en-us/windows/win32/direct3d11/overviews-direct3d-11-devices-downlevel-get
Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Fixed issues
Fixes #11802

You can test this PR using the following package version. 11.0.999-cibuild0036668-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0036686-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0036733-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]


Call to pretty printer fails

Hi Xah, thanks for this very nice WolframScript integration.
It seems as if the .el has a mistake on line 76 leading to an error when pressing TAB-TAB.
Should the call to xah-get-bounds-of-block be  a call to xah-wolfram-get-bounds-of-block?
Thanks,
Mario

thank you. fixed in https://github.com/xahlee/xah-wolfram-mode/commit/5cbe8d65d9afd0c40f11da57808463e14aca0bd6

Great, thanks!


Minikube not listed in /docs/tools/

https://kubernetes.io/docs/tools/ page does not mention minikube. Is this by design?

Probably should link to it under Native Tools?


KeyError: 'segmentation'

For cascade_rcnn_r50_fpn_1x.py and custom dataset for detection only I've got
File "/learning/other/mmdetection/mmdet/datasets/coco.py", line 87, in _parse_ann_info
gt_masks_ann.append(ann['segmentation'])
KeyError: 'segmentation'

And after changing train_pipeline options:
dict(type='LoadAnnotations', with_bbox=True, with_mask=False),
This error still exist. I assume for COCO it works, because COCO has masks. But for detection dataset it doesn't work.

Maybe I should change my annotation file which looks like for some bbox:
{'area':<PHONE_NUMBER>999998,
 'iscrowd': 0,
 'image_id': 289343,
 'bbox': [473.07, 395.93, 38.65, 28.67],
 'category_id': 18,
 'id': 1768}

and add new key-value like 'segmentation': []

I know the issue is closed but providing a better solution to this instead of messing with annotation file which can be difficult at times. Just change _C.MODE_MASK = None   in config.py.

@Aavesh
Hello，can you tell me where is the config.py?

@Aavesh or @David-19940718, what config.py file are you referring to?

@Aavesh is there a way to train models like retinaNet without providing masks? Also can you please tell where to find "config.py" that you have mentioned above.

Try to Go to /mmdetection/mmdet/datasets/coco.py" and disable all pieces of code which refer to segmentation. such as
#gt_masks_ann = []
#gt_masks_ann.append(ann['segmentation'])
#masks=gt_masks_ann,
Then see how it will turn out


NSwag Swagger Generator writes TypeNames in swagger.json when set via JsonConvert.DefaultSettings

Minimal working example:

clone https://github.com/juwens/NSwag-bugreport
open sln
build and run
open http://localhost:xxxxx/swagger/v1/swagger.json

you will see "$type" in the swagger.json

Actual behavior:
Swagger Generator writes "$type" in swagger.json when it is globally set in JsonConvert.DefaultSettings.
    public class WebApiApplication : System.Web.HttpApplication
    {
        protected void Application_Start()
        {
            Newtonsoft.Json.JsonConvert.DefaultSettings = () => new Newtonsoft.Json.JsonSerializerSettings
            {
                Formatting = Newtonsoft.Json.Formatting.Indented,
                TypeNameHandling = Newtonsoft.Json.TypeNameHandling.Objects,
                ContractResolver = new Newtonsoft.Json.Serialization.DefaultContractResolver()
                //ContractResolver = new CamelCasePropertyNamesContractResolver()
            };

Expected behavior:
Swagger Generator does not write "$type" in swagger.json
Swagger Generator uses its own specific Rule, or the one provided by configuration
RouteTable.Routes.MapOwinPath("swagger", app =>
{
    app.UseSwaggerUi3(typeof(WebApiApplication).Assembly, settings =>
    {
        settings.GeneratorSettings.SerializerSettings = new Newtonsoft.Json.JsonSerializerSettings()
        {
            Formatting = Newtonsoft.Json.Formatting.Indented,
            TypeNameHandling = Newtonsoft.Json.TypeNameHandling.None, // <- this is ignored; the JsonConvert.DefaultSettings is used
            ContractResolver = new Newtonsoft.Json.Serialization.DefaultContractResolver()
        };

        settings.MiddlewareBasePath = "/swagger";
        settings.GeneratorSettings.DefaultUrlTemplate = "api/{controller}/{id}";
    });
});

The Problem might be here: https://github.com/RSuter/NSwag/blob/34f7b94be4202400985a62032aea9bd6f7cd52f3/src/NSwag.Core/SwaggerDocument.cs#L124

How do you register the NSwag swagger.json endpoint?


Resiliency retries not work

Resiliency retries not work
darp version : 1.9.4
I deployed dapr in kubernetes with feature resiliency enabled and resiliency configured
There is an apisix dapr app as an api gateway whose upstream is a dapr app name bff with 3 instances
I expect the retry feature would help me send failed requests to other healthy bff instance, it still retry the same failed instance, then response code 502
steps:

client send request to api gateway
stop 1 bff pod
check whether response failed

seem like resiliency retires not work.
app architecture show below

Resiliency config show below
apiVersion: dapr.io/v1alpha1
kind: Resiliency
metadata:
  name: enckeappresiliency
  namespace: ingress-apisix
# similar to subscription and configuration specs, scopes lists the Dapr App IDs that this
# resiliency spec can be used by.
scopes:
  - apisix-gateway
spec:
  # policies is where timeouts, retries and circuit breaker policies are defined.
  # each is given a name so they can be referred to from the targets section in the resiliency spec.
  policies:
    # timeouts are simple named durations.
    timeouts:
      general: 1s
      important: 60s
      largeResponse: 10s

    # retries are named templates for retry configurations and are instantiated for life of the operation.
    retries:
      pubsubRetry:
        policy: constant
        duration: 5s
        maxRetries: 10

      retryForever:
        policy: exponential
        maxInterval: 15s
        maxRetries: -1 # retry indefinitely

      important:
        policy: constant
        duration: 200ms
        maxRetries: -1

      someOperation:
        policy: exponential
        maxInterval: 15s

      largeResponse:
        policy: constant
        duration: 5s
        maxRetries: 3

    # circuit breakers are automatically instantiated per component and app instance.
    # circuit breakers maintain counters that live as long as the Dapr sidecar is running. They are not persisted.
    circuitBreakers:
      simpleCB:
        maxRequests: 1
        timeout: 30s
        trip: consecutiveFailures >= 5

      pubsubCB:
        maxRequests: 1
        interval: 8s
        timeout: 45s
        trip: consecutiveFailures > 8

  # targets are what named policies are applied to. Dapr supports 3 target types - apps, components and actors
  targets:
    apps:
      apisix-gateway:
        timeout: general
        retry: retryForever
        # circuit breakers for services are scoped app instance.
        # when a breaker is tripped, that route is removed from load balancing for the configured `timeout` duration.
        circuitBreaker: simpleCB

    actors:
      myActorType: # custom Actor Type Name
        timeout: general
        retry: important
        # circuit breakers for actors are scoped by type, id, or both.
        # when a breaker is tripped, that type or id is removed from the placement table for the configured `timeout` duration.
        circuitBreaker: simpleCB
        circuitBreakerScope: both ##
        circuitBreakerCacheSize: 5000

    components:
      # for state stores, policies apply to saving and retrieving state.
      statestore1: # any component name -- happens to be a state store here
        outbound:
          timeout: general
          retry: retryForever
          # circuit breakers for components are scoped per component configuration/instance. For example myRediscomponent.
          # when this breaker is tripped, all interaction to that component is prevented for the configured `timeout` duration.
          circuitBreaker: simpleCB

      pubsub1: # any component name -- happens to be a pubsub broker here
        outbound:
          retry: pubsubRetry
          circuitBreaker: pubsubCB

      pubsub2: # any component name -- happens to be another pubsub broker here
        outbound:
          retry: pubsubRetry
          circuitBreaker: pubsubCB
        inbound: # inbound only applies to delivery from sidecar to app
          timeout: general
          retry: important
          circuitBreaker: pubsubCB

test results

dapr log

cc @halspang

how to check whether the dapr resiliency configuration is correct in k8s?

The target needs to be the other app. In this case bff. The scope is what enables the app to load the configuration, it then applies policies to what you are calling, not what you are calling from.

@halspang thank your for your reply. I tried to change the target app to bff, but still not work. How can I check the resiliency config is ok? I couldn't find it in the dapr bashboard. Should I add any dapr annotation to make resiliency config work when I apply apisix app to k8s?
The apigateway and bff are actually in two different namespace, should I append namespace to the app name in the resiliency configuration (scopes and targets sections), such as
scopes:
  - apisix-gateway.namespace1

...
targets:
    apps:
      bff.namespace2:

@halspang I also tried a simple example to check retires feature.
There are two dapr apps named aaa (1 pod) and bbb (3 pod)
aaa send request to bbb

app aaa code:
package main

import (
	"flag"
	"fmt"
	"html"
	"io"
	"log"
	"net/http"
)

func main() {

	port := flag.String("port", "foo", "a string")
	flag.Parse()

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		fmt.Println("call hello")
		fmt.Fprintf(w, "Hello, %q", html.EscapeString(r.URL.Path))
	})

	http.HandleFunc("/hi", func(w http.ResponseWriter, r *http.Request) {
		fmt.Println("call hi")
		fmt.Fprintf(w, "Hi")
	})

	http.HandleFunc("/send", func(w http.ResponseWriter, r *http.Request) {
		fmt.Println("call send")
		resp, err := http.Get("http://localhost:3500/v1.0/invoke/bbb.default/method/hi")
		if err != nil {
			log.Fatalln(err)
		}
		if resp.StatusCode >= 500 {
			b, err := io.ReadAll(resp.Body)
			if err != nil {
				log.Fatalln(err)
			}
			fmt.Println("err response=", string(b))
			w.WriteHeader(http.StatusInternalServerError)
			fmt.Fprintf(w, "fail")
		} else {
			w.WriteHeader(http.StatusOK)
			fmt.Fprintf(w, "ok")
		}
	})

	fmt.Println("start server with port", *port)
	log.Fatal(http.ListenAndServe(*port, nil))

}

dapr config
apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: featureconfig
spec:
  features:
    - name: Resiliency
      enabled: true

resiliency config
apiVersion: dapr.io/v1alpha1
kind: Resiliency
metadata:
  name: myresiliency
  namespace: default
scopes:
  - aaa
spec:
  policies:
    retries:
      retryForever:
        policy: exponential
        maxInterval: 15s
        maxRetries: -1
  targets:
    apps:
      bbb:
        retry: retryForever

aaa deploy
kind: Service
apiVersion: v1
metadata:
  name: aaasvc
  labels:
    app: aaa
spec:
  selector:
    app: aaa
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080
  type: LoadBalancer

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: aaadep
  labels:
    app: aaa
spec:
  replicas: 1
  selector:
    matchLabels:
      app: aaa
  template:
    metadata:
      labels:
        app: aaa
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "aaa"
        dapr.io/app-port: "8080"
        dapr.io/enable-api-logging: "true"
        dapr.io/config: featureconfig
    spec:
      containers:
      - name: aaa
        image: aaa
        ports:
        - containerPort: 8080
        imagePullPolicy: Never

bbb deploy
kind: Service
apiVersion: v1
metadata:
  name: bbbsvc
  labels:
    app: bbb
spec:
  selector:
    app: bbb
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080
  type: LoadBalancer

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: bbbdep
  labels:
    app: bbb
spec:
  replicas: 3
  selector:
    matchLabels:
      app: bbb
  template:
    metadata:
      labels:
        app: bbb
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "bbb"
        dapr.io/app-port: "8080"
        dapr.io/enable-api-logging: "true"
        dapr.io/config: featureconfig
    spec:
      containers:
      - name: bbb
        image: bbb
        ports:
        - containerPort: 8080
        imagePullPolicy: Never

send request to aaa

I deleted 1 pod of bbb while sending the test requests
there are 34 error logs in aaa, show below

@bookinstock @halspang - I suspect this does not seem like a resiliency retries issue. The retry is being triggered due to the resiliency policy. The name resolution is however always returning the same host - which was shutdown.
@bookinstock - Regarding this statement -
I expect the retry feature would help me send failed requests to other healthy bff instance, it still retry the same failed instance, then response code 502
Are you expecting retry policy to perform load balancing and use a healthy instance to send the  request during retry?
Also, can you confirm which Nameresolution are you using?
Can you please try to use consul with health check enabled? Link

@akhilac1 thank your for your reply.  In the example mentioned above, the resiliency retry policy is retryForever, if bbb not response, aaa will keep retry until the request got response from bbb. It work fine in the self-hosted mode, but not in the k8s environment.
Is there anything missing in configuring resiliency in k8s?
Should I add additional annotation to let the sidecar to load the resiliency config
And how to make sure the app aaa is use the applied resiliency crd myresiliency
annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "aaa"
        dapr.io/app-port: "8080"
        dapr.io/enable-api-logging: "true"
        dapr.io/config: featureconfig

@akhilac1
Are you expecting retry policy to perform load balancing and use a healthy instance to send the request during retry?-  yes
Also, can you confirm which Nameresolution are you using? - coredns

It is so helpful, thank you! 👍


nav fails to go around corner from hallway to kitchen

Returning log
troller.
[component_container_isolated-6] [INFO] [1725399875.920463599] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399876.953798300] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399877.987130781] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399879.020466875] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399880.053797144] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399881.087132457] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399882.120466764] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399883.153797780] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399884.187131717] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399885.220463355] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399886.220465641] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725399887.253798623] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [WARN] [1725399888.260204430] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399888.260241559] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399888.260248903] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399888.278676183] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [INFO] [1725399888.287132720] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [ERROR] [1725399888.287340557] [controller_server]: Invalid path, Path is empty.
[component_container_isolated-6] [WARN] [1725399888.287364231] [controller_server]: [follow_path] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399888.308742256] [local_costmap.local_costmap]: Received request to clear entirely the local_costmap
[component_container_isolated-6] [INFO] [1725399888.309089221] [controller_server]: Received a goal, begin computing control effort.
[component_container_isolated-6] [ERROR] [1725399888.309130748] [controller_server]: Invalid path, Path is empty.
[component_container_isolated-6] [WARN] [1725399888.309157537] [controller_server]: [follow_path] [ActionServer] Aborting handle.
[component_container_isolated-6] [ERROR] [1725399888.349106339] [bt_navigator_navigate_to_pose_rclcpp_node]: Failed to get result for compute_path_to_pose in node halt!
[component_container_isolated-6] [INFO] [1725399888.349244055] [behavior_server]: Running wait
[component_container_isolated-6] [WARN] [1725399888.349272689] [BehaviorTreeEngine]: Behavior Tree tick rate 100.00 was exceeded!
[component_container_isolated-6] [WARN] [1725399888.472319371] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399888.472357963] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399888.472366619] [planner_server]: [compute_path_to_pose] [ActionServer] Client requested to cancel the goal. Cancelling.
[component_container_isolated-6] [INFO] [1725399893.349346943] [behavior_server]: wait completed successfully
[component_container_isolated-6] [WARN] [1725399893.371029574] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399893.371061694] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399893.371069198] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399893.389379180] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [WARN] [1725399893.471827045] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399893.471853164] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399893.471861339] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399893.489483313] [behavior_server]: Running backup
[component_container_isolated-6] [WARN] [1725399894.639656222] [behavior_server]: Collision Ahead - Exiting DriveOnHeading
[component_container_isolated-6] [WARN] [1725399894.639701446] [behavior_server]: backup failed
[component_container_isolated-6] [WARN] [1725399894.639710252] [behavior_server]: [backup] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399894.669378947] [local_costmap.local_costmap]: Received request to clear entirely the local_costmap
[component_container_isolated-6] [INFO] [1725399894.669523496] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [WARN] [1725399895.471773456] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399895.471816196] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399895.471825293] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399895.489377537] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [WARN] [1725399896.471627899] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399896.471663324] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399896.471671830] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399896.489477095] [behavior_server]: Running spin
[component_container_isolated-6] [INFO] [1725399896.489528781] [behavior_server]: Turning 1.57 for spin behavior.
[component_container_isolated-6] [WARN] [1725399896.789630792] [behavior_server]: Collision Ahead - Exiting Spin
[component_container_isolated-6] [WARN] [1725399896.789647103] [behavior_server]: spin failed
[component_container_isolated-6] [WARN] [1725399896.789654065] [behavior_server]: [spin] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399896.819453925] [behavior_server]: Running wait
[component_container_isolated-6] [INFO] [1725399901.819551461] [behavior_server]: wait completed successfully
[component_container_isolated-6] [WARN] [1725399901.851072701] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399901.851107315] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399901.851115400] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399901.869374078] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [WARN] [1725399902.471339452] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725399902.471379947] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.66, 1.96)
[component_container_isolated-6] [WARN] [1725399902.471389064] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725399902.489520154] [behavior_server]: Running backup
[component_container_isolated-6] [INFO] [1725399906.889663460] [behavior_server]: Canceling backup
[component_container_isolated-6] [WARN] [1725399906.889726677] [behavior_server]: [backup] [ActionServer] Client requested to cancel the goal. Cancelling.
[component_container_isolated-6] [INFO] [1725399906.889797138] [bt_navigator]: Goal canceled
[component_container_isolated-6] [WARN] [1725399906.889814521] [bt_navigator]: [navigate_to_pose] [ActionServer] Client requested to cancel the goal. Cancelling.
^C[WARNING] [launch]: user interrupted with ctrl-c (SIGINT)

From east end of hallway, colliding as entering computer room
[component_container_isolated-6] [INFO] [1725399999.021688570] [amcl]: initialPoseReceived
[component_container_isolated-6] [WARN] [1725399999.021746318] [amcl]: Failed to transform initial pose in time (Lookup would require extrapolation into the future.  Requested time<PHONE_NUMBER>.021721 but the latest data is at time<PHONE_NUMBER>.997490, when looking up transform from frame [base_footprint] to frame [odom])
[component_container_isolated-6] [INFO] [1725399999.021755665] [amcl]: Setting pose<PHONE_NUMBER>.021756): 10.662 9.583 -1.125
[component_container_isolated-6] [INFO] [1725400013.910953803] [bt_navigator]: Begin navigating from current location (10.55, 9.95) to (8.72, 2.00)
[component_container_isolated-6] [INFO] [1725400013.942702170] [controller_server]: Received a goal, begin computing control effort.
[component_container_isolated-6] [WARN] [1725400013.942742776] [controller_server]: No goal checker was specified in parameter 'current_goal_checker'. Server will use only plugin loaded general_goal_checker . This warning will appear once.
[component_container_isolated-6] [WARN] [1725400014.956105935] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725400014.956158533] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.72, 2.00)
[component_container_isolated-6] [WARN] [1725400014.956189901] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725400014.971130840] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [INFO] [1725400014.976275575] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [ERROR] [1725400014.976385770] [controller_server]: Invalid path, Path is empty.
[component_container_isolated-6] [WARN] [1725400014.976432637] [controller_server]: [follow_path] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725400015.001237425] [local_costmap.local_costmap]: Received request to clear entirely the local_costmap
[component_container_isolated-6] [INFO] [1725400015.001399486] [controller_server]: Received a goal, begin computing control effort.
[component_container_isolated-6] [ERROR] [1725400015.001431896] [controller_server]: Invalid path, Path is empty.
[component_container_isolated-6] [WARN] [1725400015.001463044] [controller_server]: [follow_path] [ActionServer] Aborting handle.
[component_container_isolated-6] [ERROR] [1725400015.041323063] [bt_navigator_navigate_to_pose_rclcpp_node]: Failed to get result for compute_path_to_pose in node halt!
[component_container_isolated-6] [INFO] [1725400015.041374920] [local_costmap.local_costmap]: Received request to clear entirely the local_costmap
[component_container_isolated-6] [INFO] [1725400015.041449809] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [WARN] [1725400015.041743715] [BehaviorTreeEngine]: Behavior Tree tick rate 100.00 was exceeded!
[component_container_isolated-6] [WARN] [1725400015.768338882] [planner_server]: Planner loop missed its desired rate of 20.0000 Hz. Current loop rate is 1.2554 Hz
[component_container_isolated-6] [INFO] [1725400015.793011013] [controller_server]: Received a goal, begin computing control effort.
[component_container_isolated-6] [INFO] [1725400016.826551225] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400017.859885517] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400018.893217820] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400019.926550247] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400020.959885323] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400021.993216296] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400023.026551772] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400024.059885558] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400025.093211384] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400026.093216511] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400027.126552604] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400028.159883802] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400029.193216006] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400030.226548835] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400031.259885976] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400032.293217751] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400033.293212506] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400034.326555460] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400035.359883260] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400036.393215071] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400037.426552406] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400038.460381671] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400039.493230195] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400040.526552314] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400041.559880448] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400042.593226660] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400043.593217868] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400044.626552255] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400045.659885394] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400046.693225090] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400047.726549821] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400048.759884555] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400049.793229292] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400050.826550498] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400051.859880996] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400052.893217208] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400053.893217390] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400054.926550504] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400055.959884323] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400056.993215452] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400058.026550862] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400059.059881687] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400060.093215361] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400061.126548729] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400062.159882211] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400063.193215847] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400064.193215034] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400065.226550842] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400066.259882044] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400067.293211106] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400068.326548729] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400069.359886936] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400070.393218494] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400071.426551288] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400072.459881771] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400073.493228299] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400074.493213526] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400075.526550694] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400076.559880390] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400077.593228426] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400078.626550285] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400079.659884592] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400080.693215977] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400081.726548949] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400082.759884680] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400083.793211767] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400084.793219282] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400085.826550455] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400086.859882233] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400087.893215637] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [INFO] [1725400088.926549536] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [WARN] [1725400089.923198983] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725400089.923240060] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.72, 2.00)
[component_container_isolated-6] [WARN] [1725400089.923248145] [planner_server]: [compute_path_to_pose] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725400089.941846428] [global_costmap.global_costmap]: Received request to clear entirely the global_costmap
[component_container_isolated-6] [INFO] [1725400089.959881895] [controller_server]: Passing new path to controller.
[component_container_isolated-6] [ERROR] [1725400089.960011145] [controller_server]: Invalid path, Path is empty.
[component_container_isolated-6] [WARN] [1725400089.960036132] [controller_server]: [follow_path] [ActionServer] Aborting handle.
[component_container_isolated-6] [INFO] [1725400089.981881924] [local_costmap.local_costmap]: Received request to clear entirely the local_costmap
[component_container_isolated-6] [INFO] [1725400089.982091965] [controller_server]: Received a goal, begin computing control effort.
[component_container_isolated-6] [ERROR] [1725400089.982143691] [controller_server]: Invalid path, Path is empty.
[component_container_isolated-6] [WARN] [1725400089.982165401] [controller_server]: [follow_path] [ActionServer] Aborting handle.
[component_container_isolated-6] [ERROR] [1725400090.022082317] [bt_navigator_navigate_to_pose_rclcpp_node]: Failed to get result for compute_path_to_pose in node halt!
[component_container_isolated-6] [WARN] [1725400090.022221646] [BehaviorTreeEngine]: Behavior Tree tick rate 100.00 was exceeded!
[component_container_isolated-6] [INFO] [1725400090.022234239] [behavior_server]: Running spin
[component_container_isolated-6] [INFO] [1725400090.022282539] [behavior_server]: Turning 1.57 for spin behavior.
[component_container_isolated-6] [WARN] [1725400090.763671303] [planner_server]: GridBased: failed to create plan with tolerance 0.50.
[component_container_isolated-6] [WARN] [1725400090.763713591] [planner_server]: Planning algorithm GridBased failed to generate a valid path to (8.72, 2.00)
[component_container_isolated-6] [WARN] [1725400090.763725363] [planner_server]: [compute_path_to_pose] [ActionServer] Client requested to cancel the goal. Cancelling.
[component_container_isolated-6] [WARN] [1725400090.922422741] [behavior_server]: Collision Ahead - Exiting Spin
[component_container_isolated-6] [WARN] [1725400090.922449892] [behavior_server]: spin failed


[CT-1377] [Feature] Add functionality to use separate files for project variables

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
The dbt_project.yml file gets very long and tough to maintain when there are a lot of different variables declared for different purposes. On top of that, it's tough to look through the history of dbt_project.yml when it has so many changes for many different cases. It would be nice to be able to have separate variable files that can be split out for certain use cases and maintained separately.
Describe alternatives you've considered
Adding everything into dbt_project.yml.
Who will this benefit?
Anybody that uses variables extensively, or would like more organization to dbt_project.yml.
My use case that prompted this was that I want to set up a mapping to maintain BigQuery policy tags all in one place/variable to make it more maintainable and readable when the policy tags are referenced. It would be a fairly large mapping and dbt_project.yml is already getting quite large for our team.
Are you interested in contributing this feature?
No response
Anything else?
No response

Closing because I found this issue after opening, and I think it covers what I was suggesting:
https://github.com/dbt-labs/dbt-core/issues/4938

@nolan-jardine I really agree with the thrust of your issue! We should have a separate place to define variables for use in dbt projects. The question is whether those variables should:

support any kind of env-based Jinja compilation
be consolidated with "global" variables (env vars / CLI flags / "user config" in profiles.yml)

Glad you found #4938, I agree that's the right place to keep the ideas centralized. I just converted it to a discussion (#6170) so that it's easier to find, share, and weigh in on.


Search by url

Issue
https://github.com/premieroctet/digestclub/issues/36

Not sure if we should use contains or equals for url?