Thread automatically created by Justin Marsh in #1138182212655788054

G'day folks. Tried upgrading our app to Rails 8.1, mostly went okay but there was one hiccup that was causing the Rails console to bomb out when calling

reload!

that I traced back to this commit in Rails: https://github.com/rails/rails/commit/d43dc9af18766f91eb450e1c6b8c8c5e64f925e6 The basic gist of it is that

config.active_support.executor_around_test_case

defaults to

true

since Rails 7 and this causes the nesting behaviour of

ActiveSupport::ExecutionContext

to act as nested regardless of the environment you're in, although that nesting behaviour is only supposed to have any impact on the test environment. In our case, something in Avo's use of

ExecutionContext

in combination with our own app causes this new nesting behaviour to call

pop

too many times on the

ExecutionContext

, causing

@current_attribute_instances

to eventually become

nil

rather than the expected hash. This results in an exception after trying to reload in the console that reads:

NoMethodError: undefined method '[]' for nil (NoMethodError)

        current_instances[current_instances_key] ||= new
                         ^^^^^^^^^^^^^^^^^^^^^^^

The workaround that we've put in is to just set

config.active_support.executor_around_test_case

to false in environments other than the test environment. So far so good, although we haven't tried the upgrade in production and won't be for a few weeks at least. I haven't been able to reproduce this behaviour in a minimal test case yet, so there may be something deeper in our app that intersects with this issue, but the error itself was consistent in terms of happening by way of

Avo::ExecutionContext#initialize

.

hey guys, one of my clients has an old version of Avo:

gem "avo", "3.15.7"
gem "avo-advanced", "3.15.7"

for some reason, this:

ruby
class Avo::Resources::CommunityUser < Avo::BaseResource
  self.includes = [ :community, :user, :team ]
  self.model_class = ::Community::User

  def fields
    field :id, as: :id
    field :community, as: :belongs_to, searchable: true, can_create: false
    field :user, as: :belongs_to, can_create: false, searchable: true, attach_scope: -> {
      query.not_deleted
    }
    field :status, as: :select, enum: ::Community::User.statuses.keys
    field :role, as: :select, enum: ::Community::User.roles.keys
    field :team, as: :belongs_to, can_create: false
    field :team_role, as: :select, enum: ::Community::User.team_roles.keys
    field :created_at, as: :date_time, hide_on: %i[edit new]
  end
end

neither the community nor the user are being able to be searched; the

search controller

is being called, but no responses is coming back. if you use the global search to search for a user, he shows any idea ?

Hello everyone, quick question. Is there a version of "help text" that appears in the show view as well, not just the edit view? Thank you!

Hi, I've just been updating my app to use Pagy 43 to fix a bug I was hitting with Pagy. But I can't even run my app now. Looks like Avo is having trouble with it. I've just tried to update Avo too using rails avo:update but even that won't do anything as it seems to choke on missing old Pagy functionality. Why is Avo breaking due to a change in my own app? I hope I don;t need to go and undo all the changes i've just spent doing. It fixes a bug and really need Pagy 43.

Hello, In the app i've inherited there is a resource, of which I need to make a new instance of and as part of that I also need to create an instance of a second model at the same time. I've used

create_success_action

in it's Avo controller to do this like so:

page = @record.build_node
    @record.node = page
    @record.save

Unfortunatley it's failing to save as the node instance requires a

template_id

being passed to it for it to save. Is there any way of having a select field of

Template

records showing at the end of my main resource definition that I can use to pass to

build_node

in the

create_success_action

? This should allow my main record

Structure::Page

and node record to both be created successfully at the same time.

I noticed a documentation error: https://docs.avohq.io/3.0/discreet-information.html#information-properties

Hey, after updating Avo to 3.26.4 my dynamic filters wont work and result in http500, Did anything change? https://cdn.discordapp.com/attachments/1138182212655788054/1443218030971850932/Screenshot_2025-11-26_at_13.32.04.png?ex=69873108&is=6985df88&hm=37e06b579c001f61878d072b740ee516b957cc1ec3e343e8e7c29f294f23f079&

Hi! I couldn't find any mention of this here/on GitHub, and in the [code](https://github.com/avo-hq/avo/blob/cb38252b21b64818cf7ac0bc070c518553333984/lib/avo/fields/date_time_field.rb#L14), it looks like it's just hardcoded. But I want to confirm - is it possible to set a default date/time format for all such fields?

Hi -I think I encountered a bug in Avo Pro, not sure if this is the right place to report it. I believe this error happens when you try to go to the /new any resource that is available for global search. This is the backtrace:

hashids (1.0.6) lib/hashids.rb:29:in `Integer'
hashids (1.0.6) lib/hashids.rb:29:in `block in encode'
hashids (1.0.6) lib/hashids.rb:29:in `map!'
hashids (1.0.6) lib/hashids.rb:29:in `encode'
prefixed_ids (1.6.1) lib/prefixed_ids/prefix_id.rb:14:in `encode'
prefixed_ids (1.6.1) lib/prefixed_ids.rb:123:in `to_param'
avo-pro (3.27.0) app/components/avo/pro/global_search_component.rb:17:in `extra_params'
avo-pro (3.27.0) app/components/avo/pro/global_search_component.html.erb:5:in `call'

I believe the error is in

Avo::Pro::GlobalSearchComponent#extra_params

- it should be checking for

@resource.record.blank?

instead of

@resource.blank?

So, I have a JSON field that is a nested data structure

{
  "a": {
    "foo": 1,
    "bar": 2
  },
  "b": {
    "baz": 3,
    "blorb": 4
  }
}

Hey guys! After version 3.25, all my booleans look like this I think something was introduced by https://github.com/avo-hq/avo/pull/4024 Did anyone run into something similar? https://cdn.discordapp.com/attachments/1138182212655788054/1449109571670114354/image.png?ex=6986df35&is=69858db5&hm=f93712c096e84a05b6ea89ce0ca26a4712b9b1341b0ae02e74c42b94412b9f13&

Hello, by reading about cards, I wasn't able to read that information. The question is: whether it is possible by running in the loop, to have same card multiple times in the same dashboard? Something like:

def cards
  locations.each do |location|
    card Avo::Cards::Sales::Timeline, some_param_here: location.id
  end
end

We're already using a card with multiple locations inside that one timeline chart, but was curious if possible to do separate timelines per location. Location Timeline 1 Location Timeline 2 Location Timeline 3

Hi guys @loud-jewelry-99127 @lemon-wall-20836 Found a bug in last release https://github.com/avo-hq/avo/issues/4248

anyone having issues with https://packager.dev/avo-hq this evening?

Help with DateTimeFilter reacting with a SelectFilter

[Advanced Filter] issue with input using

type: :date

Hey folks, our penetration tester flagged a (very) minor finding to do with the avo portion of our application. How would you prefer I share the details? Didn't want to post them publicly.

Hey guys, another one from me when you have a moment—I'm just trying to strengthen our Content Security Policy by removing unsafe-inline from script_src (https://content-security-policy.com/unsafe-inline/), and I'm getting some violations on the Avo pages. Looks like it's coming from turbo within Avo. I noticed this has come up once or twice in GH issues (e.g. https://github.com/avo-hq/avo/issues/4284#issuecomment-3990637667) and wondered if there's a go-to solution yet, or is the only option to override/disable that CSP protection on the Avo ApplicationController?

I feel like I must be doing something wrong here, but I'm not sure what it is... Select fields are always super tall on the first render. If I reload the page, they size properly. It seems to be related to the

inline-flex

Tailwind class but I can't quite figure out what's going on or how to resolve it. I'm using tailwindcss-ruby 4.3.0, and avo 3.31.2. My

package.json

is presently empty, so I don't think it's interference from some other dependency / plugin... Any chance this is a known thing? https://cdn.discordapp.com/attachments/1138182212655788054/1509786164574556250/image.png?ex=6a1a7170&is=6a191ff0&hm=c4e99b2d5206330f635d2cd1d68da2b6213d71ccaf59e8f3a7d6932bf3ba4e50&

Hey. I have a question regarding Cards (in Dashboard). According to [docs](https://docs.avohq.io/3.0/cards.html#cards) I can set 1-6 colspan on cards: > Each card has its own cols and rows settings to control the width and height of the card inside the parent's grid. They can have values from 1 to 6. However basically ony 1–3 makes sense. Everything above (4, 5, 6) equals 3 cols ans the parent grid is set to

sm:grid-cols-3

anyway. Is this by design? Why have values from 1–6 and not 1–3? I'm asking because I wanted to have 4 cards in a row but this doesn't seem to be possible out of the box. https://cdn.discordapp.com/attachments/1138182212655788054/1510945934500954132/image.png?ex=6a1ea98e&is=6a1d580e&hm=bafac93c02668058cd6b6abd1c753e316de637bf5f0e9c68a90907b8a6074a30&

Hey Team, We are on the annual Pro plan ($600/yr) and I'd like to upgrade to Advanced ($150/mo) for ~1 month to test some advanced-license features. Can I do Advanced as a single month (monthly billing), or is it annual-only? And do I need to request a refund/prorated credit on the current Pro plan, or is there a cleaner way to handle the switch? Thanks!

Our packager.dev key appears to have suddenly stopped working in CI but license is paid up on avohq - is there any way to further debug what might be going on since it looks like packager.dev is up?

Hey guys, i'm trying to create an action that renders fields in a cluster... in the docs i found this: > Fields on an action work the same way as on resources. But in fact, when i try to add a panel/cluster i got > NoMethodError (undefined method 'items_holder' for nil): i already tried to monkey patch the

Avo::BaseAction

with

self.items_holder = Avo::Resources::Items::Holder.new(parent: self)

to see if this works... the error stop, but the layout isn't rendering as i want yet 🙁 How can I render fields (in actions) in columns instead of rows? Example, Foo, Bar, Zaz are fields...

Some ID#1
  [ Foo ] [ Bar ] [ Zaz]
  Some ID#2
  [ Foo ] [ Bar ] [ Zaz]
  Some ID#3
  [ Foo ] [ Bar ] [ Zaz]

or

Some ID#1 [ Foo ] [ Bar ] [ Zaz]
  Some ID#2 [ Foo ] [ Bar ] [ Zaz]
  Some ID#3 [ Foo ] [ Bar ] [ Zaz]

Hi guys I trying to access the avo docs at https://docs.avohq.io/3.0 but the page doesn't load.

Hello, do you know if it's possible to remove the

trash

button from has_many tabs? as people click it thinking it removes the reference (detach) but it actually deletes the records 🫤 https://cdn.discordapp.com/attachments/1138182212655788054/1521847391278334052/image.png?ex=6a465254&is=6a4500d4&hm=b308cb939ced6edeb8c6dc50d9387906ea3cb277b4a2a5a645b3e7c42859c30f&

Hello, giving some visibility to this issue, we are not able to build. https://github.com/avo-hq/avo/issues/4608 Thanks!

Hi folks! Hope you're well. I have a question about gem server auth. We use AI tools, including cloud environments like Claude Code for Web, Cursor Web, etc. But we often run into the issue that our test suite can't run because

bundle install

fails without the gem server auth token. Your [docs page](https://docs.avohq.io/3.0/gem-server-authentication.html#Forbidden%20403%20in%20a%20sandboxed%20or%20cloud%20environment%20(Cursor%20Cloud)) mentions cursor cloud which suggests it's acceptable to put our packager.dev token in the environment secrets. Claude Code for Web has something similar, though advises against putting secrets there. Just thought I'd check, given how popular these tools are these days, whether you've run into this one before and have a particular recommendation for enabling cloud/web agents to run

bundle install

? https://cdn.discordapp.com/attachments/1138182212655788054/1531328644470013962/Screenshot_2026-07-27_at_16.50.30.png?ex=6a68d06f&is=6a677eef&hm=cd08700c94b5342c46c5789f5996add0cf4a90e9ae3b22a1a1c1fba58a58b158&

Hello, with the release of Avo 4 we have an application that's currently using Avo 3. I have been asked to review our options for continuing to use Avo. It looks like the Avo 4 "essentials bundle" is the minimum required for this application, which puts the price at $75 / month. That is a substantial increase ($900 / year) from the $250 / year for the current Avo 3 license, so I expect to be asked if we can continue with Avo 3's current annual license. I see that it's set to renew next month at $350. I also noted Adrian's comment in another thread: > Avo 4 is essentially a different product from Avo 3. > Avo 3 will still be updated and kept secure. Avo 4 is the new flagship product going forward. It is useful to know that Avo 3 will still be supported, but will the license structure remain the same or is it expected to transition to the same monthly-only tiers as Avo 4 with no annual payment option? Is the price expected to stay roughly the same, or will it increase to be closer to Avo 4's cost?

is it possible to still purchase avo 3? we have an app that for various reasons cannot upgrade to 4, due to some low-level incompatibilities. We're on avo 2 and would like to upgrade, but 4 is not possible for the foreseeable future, and we're using features on 2 that require a pro license on 3.