@alainlamar can you check my PR https://github.com/vyos/vyos-1x/pull/3430 ?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 8 2024
Ok, Sure.
Added access to organization's .github repository
we probably want to keep PR templates and what else there too(will create separate task)
Sure, let's do it that way
Thanks @Vijayakumar
@syncer Just want to know whether we considered using the CODEOWNERS file to achieve this
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
Behavior change for this issue was fix some month ago in migration scripts, in order to remain action "return" when upgrading from older versions to new syntax.
Note that the work in the link above, but for the get_commit_schedule function itself, has already been added in subtasks T6319/T6146. As mentioned above, the get_commit_schedule function is not useful (and potentially misleading) until we replace the legacy commit algorithm in 1.5. Remove 1.4.0 tag.
speed test info:
looks like the problem doesn't reproduce on the newest VyOS version (1.5 and 1.4)
Should be fixed in https://github.com/vyos/vyos-build/pull/600
Please review and approve/merge https://github.com/vyos/vyos-github-actions/pull/2
Mostly impossible for policy local-route
I'm not expecting that it will be implemented at all.
May 7 2024
with the fix n.fort put in this feature is greatly sort after, definitely a thump up from me.
Yes this is indeed resolved after switching to 1.5-rolling-202405070019, thank you so much @n.fort and @Viacheslav
Further tests in lab shows that non-ehternet interfaces are needed in order to offload traffic as expected. An example is when using wireguard interface: in order to offload traffic, it's necessary to add interface wgX to the flowtable.
Otherwise, it won't work as expected
Shouldnt this be adjusted in more files and places?