undefined method `inheritance_column' for Class

I'm using the rails4-mongo5 branch, currently migrating from rails_admin to active_admin.
Everything works fine at first (installation), but as soon as I create a resource and try to access it in the dashboard I get:

undefined method `inheritance_column' for Home:Class

Not quite sure what else I should say now; I have followed the instructions in the README of the branch but the error persists.
Any idea how I could work around or fix this error? What I already tried was forking and changing inheritance_column to _types but it must have created more errors rather than fixing them (subsequent errors kept popping up no matter how many I tried to "fix").

@gerryhd please post a backtrace, and a pared down copy of the "Home" class, we'll take a look and see why you might be getting this error.

NoMethodError - undefined method `inheritance_column' for Home:Class:
  activeadmin (1.0.0) lib/active_admin/resource/attributes.rb:35:in `sti_col?'
  activeadmin (1.0.0) lib/active_admin/resource/attributes.rb:27:in `reject_col?'
  activeadmin (1.0.0) lib/active_admin/resource/attributes.rb:8:in `block in default_attributes'
  activeadmin (1.0.0) lib/active_admin/resource/attributes.rb:7:in `default_attributes'
  activeadmin (1.0.0) lib/active_admin/resource.rb:180:in `resource_attributes'
  activeadmin (1.0.0) lib/active_admin/resource.rb:188:in `content_columns'
  activeadmin (1.0.0) lib/active_admin/filters/resource_extension.rb:112:in `default_filters'
  activeadmin (1.0.0) lib/active_admin/filters/resource_extension.rb:96:in `filter_lookup'
  activeadmin (1.0.0) lib/active_admin/filters/resource_extension.rb:25:in `filters'
  activeadmin (1.0.0) lib/active_admin/filters/resource_extension.rb:145:in `block in filters_sidebar_section'
  activeadmin (1.0.0) lib/active_admin/helpers/optional_display.rb:25:in `display_on?'
  activeadmin (1.0.0) lib/active_admin/resource/sidebars.rb:17:in `block in sidebar_sections_for'
  activeadmin (1.0.0) lib/active_admin/resource/sidebars.rb:17:in `sidebar_sections_for'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:114:in `sidebar_sections_for_action'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:138:in `skip_sidebar?'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:76:in `build_page_content'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:54:in `block (2 levels) in build_page'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:31:in `block in build_tag'
  arbre (1.1.1) lib/arbre/context.rb:92:in `with_current_arbre_element'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:49:in `with_current_arbre_element'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:26:in `build_tag'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:39:in `insert_tag'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:14:in `div'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:50:in `block in build_page'
  arbre (1.1.1) lib/arbre/context.rb:92:in `with_current_arbre_element'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:49:in `with_current_arbre_element'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:49:in `build_page'
  activeadmin (1.0.0) lib/active_admin/views/pages/base.rb:10:in `build'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:30:in `block in build_tag'
  arbre (1.1.1) lib/arbre/context.rb:92:in `with_current_arbre_element'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:26:in `build_tag'
  arbre (1.1.1) lib/arbre/element/builder_methods.rb:39:in `insert_tag'
  activeadmin (1.0.0) app/views/active_admin/resource/index.html.arb:2:in `block in __home_gerry__rvm_gems_ruby_______homiemx_gems_activeadmin_______app_views_active_admin_resource_index_html_arb___4419455023637826552_70077157862700'
  arbre (1.1.1) lib/arbre/context.rb:45:in `initialize'
  activeadmin (1.0.0) app/views/active_admin/resource/index.html.arb:1:in `__home_gerry__rvm_gems_ruby_______homiemx_gems_activeadmin_______app_views_active_admin_resource_index_html_arb___4419455023637826552_70077157862700'
  actionview (4.2.5) lib/action_view/template.rb:145:in `block in render'
  activesupport (4.2.5) lib/active_support/notifications.rb:166:in `instrument'
  actionview (4.2.5) lib/action_view/template.rb:333:in `instrument'
  actionview (4.2.5) lib/action_view/template.rb:143:in `render'
  actionview (4.2.5) lib/action_view/renderer/template_renderer.rb:54:in `block (2 levels) in render_template'
  actionview (4.2.5) lib/action_view/renderer/abstract_renderer.rb:39:in `block in instrument'
  activesupport (4.2.5) lib/active_support/notifications.rb:164:in `block in instrument'
  activesupport (4.2.5) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  activesupport (4.2.5) lib/active_support/notifications.rb:164:in `instrument'
  actionview (4.2.5) lib/action_view/renderer/abstract_renderer.rb:39:in `instrument'
  actionview (4.2.5) lib/action_view/renderer/template_renderer.rb:53:in `block in render_template'
  actionview (4.2.5) lib/action_view/renderer/template_renderer.rb:61:in `render_with_layout'
  actionview (4.2.5) lib/action_view/renderer/template_renderer.rb:52:in `render_template'
  actionview (4.2.5) lib/action_view/renderer/template_renderer.rb:14:in `render'
  actionview (4.2.5) lib/action_view/renderer/renderer.rb:42:in `render_template'
  actionview (4.2.5) lib/action_view/renderer/renderer.rb:23:in `render'
  actionview (4.2.5) lib/action_view/rendering.rb:100:in `_render_template'
  actionpack (4.2.5) lib/action_controller/metal/streaming.rb:217:in `_render_template'
  actionview (4.2.5) lib/action_view/rendering.rb:83:in `render_to_body'
  actionpack (4.2.5) lib/action_controller/metal/rendering.rb:32:in `render_to_body'
  actionpack (4.2.5) lib/action_controller/metal/renderers.rb:37:in `render_to_body'
  actionpack (4.2.5) lib/abstract_controller/rendering.rb:25:in `render'
  actionpack (4.2.5) lib/action_controller/metal/rendering.rb:16:in `render'
  actionpack (4.2.5) lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
  activesupport (4.2.5) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
  /home/gerry/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'
  activesupport (4.2.5) lib/active_support/core_ext/benchmark.rb:12:in `ms'
  actionpack (4.2.5) lib/action_controller/metal/instrumentation.rb:44:in `block in render'
  actionpack (4.2.5) lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
  actionpack (4.2.5) lib/action_controller/metal/instrumentation.rb:43:in `render'
  wicked_pdf (1.1.0) lib/wicked_pdf/pdf_helper.rb:42:in `render_with_wicked_pdf'
  actionpack (4.2.5) lib/action_controller/metal/implicit_render.rb:10:in `default_render'
  responders (2.1.0) lib/action_controller/responder.rb:236:in `default_render'
  responders (2.1.0) lib/action_controller/responder.rb:170:in `to_html'
  responders (2.1.0) lib/responders/flash_responder.rb:107:in `to_html'
  responders (2.1.0) lib/action_controller/responder.rb:163:in `respond'
  responders (2.1.0) lib/action_controller/responder.rb:156:in `call'
  responders (2.1.0) lib/action_controller/respond_with.rb:203:in `respond_with'
  inherited_resources (1.7.2) lib/inherited_resources/actions.rb:7:in `index'
  activeadmin (1.0.0) lib/active_admin/resource_controller/streaming.rb:12:in `index'
  actionpack (4.2.5) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
  actionpack (4.2.5) lib/abstract_controller/base.rb:198:in `process_action'
  actionpack (4.2.5) lib/action_controller/metal/rendering.rb:10:in `process_action'
  actionpack (4.2.5) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
  activesupport (4.2.5) lib/active_support/callbacks.rb:117:in `call'
  activesupport (4.2.5) lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
  activesupport (4.2.5) lib/active_support/callbacks.rb:505:in `call'
  activesupport (4.2.5) lib/active_support/callbacks.rb:92:in `__run_callbacks__'
  activesupport (4.2.5) lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
  activesupport (4.2.5) lib/active_support/callbacks.rb:81:in `run_callbacks'
  actionpack (4.2.5) lib/abstract_controller/callbacks.rb:19:in `process_action'
  actionpack (4.2.5) lib/action_controller/metal/rescue.rb:29:in `process_action'
  actionpack (4.2.5) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
  activesupport (4.2.5) lib/active_support/notifications.rb:164:in `block in instrument'
  activesupport (4.2.5) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  activesupport (4.2.5) lib/active_support/notifications.rb:164:in `instrument'
  actionpack (4.2.5) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
  actionpack (4.2.5) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
  actionpack (4.2.5) lib/abstract_controller/base.rb:137:in `process'
  actionview (4.2.5) lib/action_view/rendering.rb:30:in `process'
  actionpack (4.2.5) lib/action_controller/metal.rb:196:in `dispatch'
  actionpack (4.2.5) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
  actionpack (4.2.5) lib/action_controller/metal.rb:237:in `block in action'
  actionpack (4.2.5) lib/action_dispatch/routing/route_set.rb:76:in `dispatch'
  actionpack (4.2.5) lib/action_dispatch/routing/route_set.rb:45:in `serve'
  actionpack (4.2.5) lib/action_dispatch/journey/router.rb:43:in `block in serve'
  actionpack (4.2.5) lib/action_dispatch/journey/router.rb:30:in `serve'
  actionpack (4.2.5) lib/action_dispatch/routing/route_set.rb:817:in `call'
  omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
  rack (1.6.4) lib/rack/deflater.rb:35:in `call'
  warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
  warden (1.2.3) lib/warden/manager.rb:34:in `call'
  rack (1.6.4) lib/rack/etag.rb:24:in `call'
  rack (1.6.4) lib/rack/conditionalget.rb:25:in `call'
  rack (1.6.4) lib/rack/head.rb:13:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/flash.rb:260:in `call'
  rack (1.6.4) lib/rack/session/abstract/id.rb:225:in `context'
  rack (1.6.4) lib/rack/session/abstract/id.rb:220:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/cookies.rb:560:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.2.5) lib/active_support/callbacks.rb:88:in `__run_callbacks__'
  activesupport (4.2.5) lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
  activesupport (4.2.5) lib/active_support/callbacks.rb:81:in `run_callbacks'
  actionpack (4.2.5) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/reloader.rb:73:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
  airbrake (5.3.0) lib/airbrake/rack/middleware.rb:22:in `call'
  better_errors (2.1.1) lib/better_errors/middleware.rb:84:in `protected_app_call'
  better_errors (2.1.1) lib/better_errors/middleware.rb:79:in `better_errors_call'
  better_errors (2.1.1) lib/better_errors/middleware.rb:57:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
  web-console (2.2.1) lib/web_console/middleware.rb:39:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.2.5) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.2.5) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.2.5) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.2.5) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.2.5) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.2.5) lib/rails/rack/logger.rb:20:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
  rack (1.6.4) lib/rack/runtime.rb:18:in `call'
  activesupport (4.2.5) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
  rack (1.6.4) lib/rack/lock.rb:17:in `call'
  actionpack (4.2.5) lib/action_dispatch/middleware/static.rb:116:in `call'
  rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
  railties (4.2.5) lib/rails/engine.rb:518:in `call'
  railties (4.2.5) lib/rails/application.rb:165:in `call'
  rack (1.6.4) lib/rack/content_length.rb:15:in `call'
  puma (2.13.4) lib/puma/server.rb:541:in `handle_request'
  puma (2.13.4) lib/puma/server.rb:388:in `process_client'
  puma (2.13.4) lib/puma/server.rb:270:in `block in run'
  puma (2.13.4) lib/puma/thread_pool.rb:106:in `block in spawn_thread'

The ActiveAdmin related class "Home" is empty
ActiveAdmin.register Home do
# See permitted parameters documentation:
# https://github.com/activeadmin/activeadmin/blob/master/docs/2-resource-customization.md#setting-up-strong-parameters
#
# permit_params :list, :of, :attributes, :on, :model
#
# or
#
# permit_params do
#   permitted = [:permitted, :attributes]
#   permitted << :other if params[:action] == 'create' && current_user.admin?
#   permitted
# end

end

So I added a class method "inheritance_column" to my model Home and gave it a hardcoded value and it works now, but what exactly is "inheritance_column" for and why would the gem ask me for it? Obviously hardcoding some value into it isn't the best solution so I'd like to know how to fix this properly.

@gerryhd is the Home model an STI model?  inheritance_column is supposed to tell the model which column to get the STI class from (eg :_type)

@gerryhd Did you resolve this issue?  I'm hoping it was just that it was an STI model?

inheritance_column is a deprecated method of ActiveRecord::base . I think ActiveAdmin did recognise my models as STI models, but none of them really are as far as I'm concerned. So I followed instructions here https://apidock.com/rails/ActiveRecord/Base/inheritance_column/class#364-two-ways-to-disable-single-table-inheritance , specifically the second option, and added them (via extended Class ) to all the models I'll need for ActiveAdmin. It's been working fine since.

👍 Sounds good, thanks for the info!


Ignore sec-advisories for some crate until a given date

Bytecode Alliance folks have ran into an interesting use case: a low-urgency sec-advisory that is fine to ignore for some time, but that should be re-reviewed some time later: https://github.com/bytecodealliance/wasmtime/pull/2881. To not forget about it, it'd be nice that cargo-deny can "ping back" after a given date, while ignoring the issue until the given date. Is that something that would make sense to add in cargo-deny?
(There's the question of which time zone should be applied to such a date, but any would work, really; I don't expect that being a day early or late in this kind of situation would be dramatic.)

but don't think I want to go back to that failing (essentially random) builds either.

That's a good point. Maybe that's a different feature request, but it'd be nice if there was a way to run the sec-advisories checks only with a certain cargo deny runtime flag; then users could use Github period jobs (cron-like) to just run the sec-advisories checks, separate from the rest of the Cargo deny checks. This way, the sec-advisories checks wouldn't happen in random builds, but in separate instances.

This is already supported, cargo deny check by default will run all checks, but you can specify which checks to run, eg cargo deny --all-features check advisories


Subscribe with buttons

Description
This PR updates the subscribe command to be interactive with discord buttons.
Running this command now gives the users a set of buttons to click to add or remove pre-determined announcement roles.
Adding or removing a role updates the button state to reflect the change and what would happen if the user clicks the button again.
Screenshot(s)
This is what the command looks like after I ran it with no roles, then added the PyWeek role to myself.

This has fixup commits, so please do not update this branch, as it will stop me from being able to rebase and actually fix them up.

This has fixup commits, so please do not update this branch when it's approved.
Doing so would stop me from being able to rebase and actually fix them up. Just ping me when it's ready and I'll rebase properly.


Mattermost moving to API version 4

Hey @jovandeginste !
First, hugely appreciate you sharing this project back with the world. Fantastic work!
I wanted to let you know about our plans moving to API v4:
To make the Mattermost API web service easier to use and to offer more powerful options for these integrations, Mattermost will be moving to a new API version soon.  Highlights include:

Fully documented API endpoints
More in-depth access to server functionality
Wider use of established HTTP verbs
Consistent endpoint structures
A new and improved Go driver

We plan to release API version 4 on March 16th, with Mattermost server 3.7.  While the current API version 3 will be supported until September 16th, we recommend you begin using API version 4 soon after its release.
Contributing
API version 4 is an active and on-going project. If you're interested in helping contribute, please join our Mattermost community instance and the APIv4 channel.
We've prepared a contribution process for APIv4 and a progress tracker for new APIv4 enpoints to help you get started.
We're also open for suggestions on adding new API endpoints to help with your integration.

Is this an actually relevant issue for this project? We have analyzed the code and found that it uses a webhook - where the API AFAWK did not change. Or are we missing something?

@ArloL Looks like you're correct, good catch. Closing the issue.


Default scoped in a Module when I'm using unscoped

Hi guys, firstly I would like to thank you for the great work.
I have the following code:
module Test
  extend ActiveSupport::Concern
  included do
    include Mongoid::Document
    field :title, :type => String
    default_scope desc :title
  end
end

class Person
  include Test
  field :name, :type => String
  scope :by_name, order_by([[:name, :desc]])
end

And I run:
p1 = Person.create :title => "abc", :name => "abc"
p2 = Person.create :title => "cba", :name => "cba"

Person.all.to_a # [p2, p1] in order
Person.unscoped.to_a # [p1, p2]

puts Person.unscoped.by_name.inspect
# <Mongoid::Criteria
#  selector: {},
#  options:  {:sort=>[[:title, :desc], [:name, :desc]]},
#  class:    Person,
#  embedded: false>

As you can see, when I'm using unscoped included in a Module before a scope defined in a class, Mongoid does not exclude default_scope from criteria object. I had confirmed this when I ran this example:
class Game
  include Mongoid::Document
  field :name, :type => String
  field :title, :type => String

  default_scope desc :title
  scope :by_name, order_by([[:name, :desc]])
end

g1 = Game.create :title => "abc", :name => "abc"
g2 = Game.create :title => "cba", :name => "cba"

Game.all.to_a # [g2, g1] in order
Game.unscoped.to_a # [g1, g2]

puts Game.unscoped.by_name.inspect
# <Mongoid::Criteria
#  selector: {},
#  options:  {:sort=>[[:title, :desc], [:name, :desc]]},
#  class:    Game,
#  embedded: false>

When I define the default_scope in a class, Mongoid works.
Can you help me?

I'm using Mongoid 2.2.2

Why do they guys close my issue?

I've flagged for this weekend's release - should be an easy fix.

I believe this is also affecting the Mongoid:::Paranoia extra.
Even when using unscoped the Paranoia criteria appears to be applied. I am using an older version of Mongoid though so it may be fixed in the latest. Could you do a check for it? (There is a test for it by the looks of it)

The issue is a bit broader - #unscoped is not working at all if any named scope is chained after it.

Is this still on the roadmap?

@geetarista Yup, it's scheduled for 2.4.0 .

I'm looking at it now - needs a bit more work than I originally thought which is why it got pushed to a minor release and not a patch.

No worries. I appreciate the updates.

So this turned into a complete pain that could not be completely solved without a rewrite of the criteria/scoping code. (Which has already started in the origin repo.) In order not to break the public API in a minor release, I've provided a fix that gets around this issue for now, with the true rewrite coming in 3.0.0.
Simply in this case, if you now define all the named scopes as lambdas, all will be kosher.
scope :by_name, lambda { order_by([[:name, :desc]]) }

The problem was that the default scope was getting applied at class load time to all named scopes, and even if you called unscoped applying the named scoped after would still contain the default. A smart removal of the default scope when defining a named scope has too many edge cases to be implemented, so I need to rewrite the way the defaults are applied... This will come soon.

Cool. Thanks for the workaround, Durran.


Replace device info with accession data source 1/2

Previously, we captured a bunch of diagnostic information about the mobile
device when accessions were created by the seed collector app. We have never
used that information for anything other than inferring whether or not an
accession came from the mobile app. We already expose that in the API as the
source field on the accession payload; the value of that field is inferred
from the presence or absence of mobile device details.
We do still want to keep track of which accessions were created via the seed
collector app, and we'll also want to know which ones were created using CSV
upload when we add that feature.
Update the data model to explicitly store the source field rather than
inferring it, and add a third possible value to represent importing from CSV
or other kinds of files.
This removes the deviceInfo payload field and adds the source field to
the accession creation payload. If not present, it defaults to Web, mirroring
the current behavior when no device info is present.
This first change removes all the references to the app_devices table but
doesn't drop the table so as to not break the previous code version during
deployment; a followup change will backfill the data sources of existing
accessions and drop app_devices.

Current dependencies on/for this PR:

main

PR #562

PR #563

PR #564
PR #565   👈

PR #566

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: EYRsPciwds2tANP1f3b7


luci-app-attendedsysupgrade: use remote revision for version code

With 8860ca069c04e3dbd3f107f1526f2901f1085902 the check against the version_code parameter was implemented but was incorrectly set to the current revision instead of the latest available remote revision.
This resulted in not being able to upgrade due to the version_code parameter never matched the newer remote revision on the sysupgrade server.
To clarify the problem, r26637-05aec66d53 is the current running revision, and r26679-70088a7e4c is the latest remote revision (which we want to upgrade to) at time of writing this.
See https://github.com/openwrt/luci/pull/7163#issuecomment-2176678529
Without fix:

With fix:

[X] This PR is not from my main or master branch :poop:, but a separate branch :white_check_mark:
[X] Each commit has a valid :black_nib: Signed-off-by<EMAIL_ADDRESS>row (via git commit --signoff)
[X] Each commit and PR title has a valid :memo: <package name>: title first line subject for packages
[ ] Incremented :up: any PKG_VERSION in the Makefile
[X] Tested on: (x86/64, SNAPSHOT r26637-05aec66d53, Firefox) :white_check_mark:
[X] ( Preferred ) Mention: @ the original code author for feedback @aparcar
[ ] ( Preferred ) Screenshot or mp4 of changes:
[ ] ( Optional ) Closes: e.g. openwrt/luci#issue-number
[ ] ( Optional ) Depends on: e.g. openwrt/packages#pr-number in sister repo
[X] Description: (describe the changes proposed in this PR)

We should if possible wait for @aparcar to verify this but seeing how firmware selector works as described in https://github.com/openwrt/luci/pull/7163#issuecomment-2176770355 I'm very sure this is how it's supposed to be implemented, with the latest remote revision being supplied as the version_code parameter.

Could you create a PR to revert this? And also is anyone interested in taking over maintainer ship of the app?

Could you create a PR to revert this?

https://github.com/openwrt/luci/pull/7168

So what's the consensus on this? It goes on with some modification?

So what's the consensus on this? It goes on with some modification?

That's the goal, the gist is that the LuCI app has the ability to flash the current running version again (it's part of the "Advanced options"), which breaks if you are running a SNAPSHOT and supply the version_code parameter to the API as you can't re-flash a SNAPSHOT since the image builders for that version are long gone by then. There needs to be some code to remove the version_code parameter only if not running on a stable branch (23.05, 22.03 etc.) if this case happens without breaking existing functionality.

Got it. OK, is that achievable?
Snapshot just needs to take current snapshot but there's no trivial way to do so?

It should be, I just haven't had time to look into into (work ya know :P). The one thing I can't wrap my head around right now is if the LuCI app actually supports to re-flash the existing SNAPSHOT version you have installed, which I think is no (due to the above reasons in the previous comment). However, it's still presented as a valid option at the moment to do this, which, if this is kept, will break when adding the version_code parameter as the image builders for SNAPSHOT:s doesn't accept "old" version codes.
So, my guess right now (I haven't had time to investigate it tho) is that the behavior that the LuCI app allowed you to re-flash the same installed SNAPSHOT has never been a valid configuration, and it would then instead just flash the newest available image from the image builders instead of the one you actually requested. Adding the version_code parameter exposed this existing, invalid configuration, which is why it wasn't as trivial to solve that I thought it would be, as the correct way to fix this then would be to disallow the re-flash of the already installed SNAPSHOT version by hiding it in the dropdown or any similar solution.

Is this changed any by your new PR #7203 ?

Is this changed any by your new PR #7203 ?

No, it's two completely different issues. In #7203, all the existing code already used the versioned endpoints except for /api/overview, so the /api/v1/build endpoint that accepts the version_code parameter wasn't touched at all in that PR.


Feature/parallel pub

Adds commands publishing options to the Controller (sequence, parallel, array)
Handles twist array input in DriveManager and sends commands to the robot using cmd_rate
Updates docs

Updated docs with control algorithms configuration classes and default parameters


v1.12 backports 2023-07-31

[ ] #26880 -- Documentation: fix the broken links/dead links (@vipul-21)
[ ] #25324 -- operator: Adjust CiliumEndpoint GC to only run once in kvstore mode (@learnitall)

:warning: conflict due to hive and cell refactoring

Once this PR is merged, you can update the PR labels via:
$ for pr in 26880 25324; do contrib/backporting/set-labels.py $pr done 1.12; done

/test-backport-1.12

/test-1.18-4.9

/test-backport-1.12

/test-1.17-4.9


Implement ItemStack/ItemStackSnapshot isEmpty().

I believe this has been implemented. https://github.com/SpongePowered/SpongeCommon/blob/175e583203cba692d42ad0b0265949d74bebbea3/src/mixins/java/org/spongepowered/common/mixin/api/mcp/item/ItemStackMixin_API.java#L209-L212


WebRTC: Long-term project to complete the documentation

The documentation of WebRTC is incomplete. Both reference and guide/tutorial content is either missing or incomplete. This epic involves completing that work; see the user stories within for details.

Notes from conversation with jib on IRC about priorities

None of the transport stuff is really implemented in Firefox
An example showing how to use WebRTC using transceivers would be helpful. jib wrote a blog post about this: https://blog.mozilla.org/webrtc/rtcrtptransceiver-explored/
Stats would be useful. RTCStatsReport etc. But we don’t implement all of it yet. You can see what each browser implements here: https://webrtc-stats.callstats.io/verify

Does RTCCertificate need to be included in this Epic?

Also removal of RTCIdentityEvent?


Fix documentation about zip action

I found miss on documentation about zip action.

Documented
Actual

output_name
output_path

https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/zip.rb#L36
Additionally, I prefer to change env_name also.

@giginet Thanks for the PR. Please address the comment and I'll merge the documentation. 🚀

Thanks @giginet 👍


Scoring discrepancies between beta and prod

We should fix these. List them here and @lsabor keep us posted on your progress in resolving them.

Parity has reached near completion for scoring leaderboards. The only scoring leaderboards that are out of sync are the 2024 ones.

Parity reached on scoring leaderboards
parity up to participation numbers achived for non scoring leaderboards.
Nearing ticket completion

The final issue for this is that moderators are included. Moving this to lower priority

Moderators / non admins aren't excluded.
Also general discrepencies have been solved.
Closing as complete


searchCatalog doesn't seem to consider "pageSize" in the request.

I constructed the request body as follows:
request = {     scope: {includeProjectIds: ['myprojectID']},     query: 'someWord',     pageSize: 5 }
However, in response, it returns way more results than 5. And there is not nextPage token in the response.

@alexander-fenster this is a little weird, is there a chance we defined the field wrong in the proto?

It auto-paginates automatically and fetches all the responses (this is the default behavior). To get just the first page with 5 results, pass {autoPaginate: false} as an options object (second parameter, after the request).
Quite soon, we'll have async iterators here to make it less weird :)

Great! That solved the problem. Thank you very much.


Change we are hiring to we are looking for new members

link to google interest form

Awesome: Exactly what we need


'GlossaryTerm' support searching custom propertie

For example, I think that after providing 'custom properties', supporting' custom properties' search will make the use of glossary term more friendly. For example, in many scenarios, after the term description contains more meaning, you need to search for a specific 'custom properties' to locate a series of terms.

Hi @dexter-mh-lee Excuse me，I want to know, if custom properties search is supported, in addition to @searchable, where else should we pay attention to model construction?

Hi @Huyueeer!
We are now managing feature requests through our new portal to improve visibility & prioritize work into our public roadmap. If this request is still relevant, please create a new issue so we can gauge current interest from the Community & prioritize work accordingly.
We'll close out this issue in the meantime. Feel free to reach out to me on DataHub Slack with any questions!


Weird truncation of public runtime variables

Environment

Operating System: Darwin
Node Version:     v20.7.0
Nuxt Version:     3.9.0
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, runtimeConfig
Runtime Modules:  -
Build Modules:    -

Reproduction
Repricable in a vanilla Nuxt project – simply set a public runtime config
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  devtools: { enabled: true },
  runtimeConfig: {
    public: {
      TRUNCATE_TEST: '',
    },
  },
})

And in a .env file set a variable with only numbers and a dot in it:
NUXT_PUBLIC_TRUNCATE_TEST="3764781224009.4594925821288"

Describe the bug
The variable gets truncated, so<PHONE_NUMBER>009.4594925821288 becomes<PHONE_NUMBER>009.4598. But if I append an alphabetical character (e.g. x) to the end of the variable, then I get a full value back.
Additional context
The value is a Slack client ID that I'd need to pass in order to configure an "Add to Slack" button. If the variable is only numeric, it weirdly always takes the first 3 characters and the very last character and strips the rest 🤔 So basically:
3764781224009.4594925821288
XXXXXXXXXXXXX.YYYstripppedY

3764781224009.4598 # output

Logs
No response

Duplicate of https://github.com/nuxt/nuxt/issues/24812

Oh, thanks! 🎉


tuples as data not filter-able for equality?

Using
'0.17.0rc1+31.g9be2180'
and  a column of tuples like so:
df.BINNING_SET.head()

TIME_OF_INT
2014-10-18 07:36:19.926570     (0, 1, 319, 11)
2014-10-18 07:36:19.926570     (0, 1, 441, 11)
2014-10-18 07:36:59.675040    (52, 4, 89, 115)
2014-10-18 07:36:59.675040    (2, 34, 96, 115)
2014-10-18 07:55:27.922290    (52, 4, 89, 115)
Name: BINNING_SET, dtype: object

I can't seem to filter on any tuple like so:
df.BINNING_SET==df.BINNING_SET.iloc[0]

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-41-435fa8bdd1a7> in <module>()
----> 1 df.BINNING_SET==df.BINNING_SET.iloc[0]

/Users/klay6683/miniconda3/lib/python3.4/site-packages/pandas-0.17.0rc1+31.g9be2180-py3.4-macosx-10.5-x86_64.egg/pandas/core/ops.py in wrapper(self, other, axis)
    724                 other = np.asarray(other)
    725
--> 726             res = na_op(values, other)
    727             if isscalar(res):
    728                 raise TypeError('Could not compare %s type with Series'

/Users/klay6683/miniconda3/lib/python3.4/site-packages/pandas-0.17.0rc1+31.g9be2180-py3.4-macosx-10.5-x86_64.egg/pandas/core/ops.py in na_op(x, y)
    642             if isinstance(y, (np.ndarray, pd.Series)):
    643                 if not is_object_dtype(y.dtype):
--> 644                     result = lib.vec_compare(x, y.astype(np.object_), op)
    645                 else:
    646                     result = lib.vec_compare(x, y, op)

pandas/lib.pyx in pandas.lib.vec_compare (pandas/lib.c:14361)()

ValueError: Arrays were different lengths: 41994 vs 4

Looks like it's trying to compare your whole series to the tuple, because the tuple is a sequence.
You can (practically) only support either a comparison of a series to a sequence, or a comparison of each point of a series to a sequence; not both.
Solution is fairly consistent to both https://github.com/pydata/pandas/issues/10900 and https://github.com/pydata/pandas/issues/10399 - is there a reason you can't use a DataFrame here?

I'm a bit confused, because before it was said that this problem would only appear when using df.apply. I think this basically just boils down to pandas not supporting tuples as object elements, as the operation I'm doing above is a fully supported on in general, isn't it? I'm unclear on what you mean by "using a DataFrame"?

@michaelaye Yes exactly - you may be constantly struggling if you try and use sequences as object elements. Others who are closer to the project should weigh in here though.
Re the DataFrame - I didn't see that this is a column in a DataFrame already. My suggestion isn't very helpful, then.
This does seem like a reversion, FWIW:
series=pd.Series(tuple(pd.np.random.rand(3)) for _ in range(20))
series==series.iloc[0]
# 0      True
# 1     False
# ...
INSTALLED VERSIONS
------------------
commit: None
python: 3.4.3.final.0
python-bits: 64
OS: Darwin
OS-release: 14.4.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8

pandas: 0.16.2

In [2]: series=pd.Series(tuple(pd.np.random.rand(3)) for _ in range(20))

In [3]: series==series.iloc[0]
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-3-83f74919dc93> in <module>()
----> 1 series==series.iloc[0]

/Users/maximilian/Dropbox/workspace/pandas/pandas/core/ops.py in wrapper(self, other, axis)
    724                 other = np.asarray(other)
    725
--> 726             res = na_op(values, other)
    727             if isscalar(res):
    728                 raise TypeError('Could not compare %s type with Series'

/Users/maximilian/Dropbox/workspace/pandas/pandas/core/ops.py in na_op(x, y)
    642             if isinstance(y, (np.ndarray, pd.Series)):
    643                 if not is_object_dtype(y.dtype):
--> 644                     result = lib.vec_compare(x, y.astype(np.object_), op)
    645                 else:
    646                     result = lib.vec_compare(x, y, op)

/Users/maximilian/Dropbox/workspace/pandas/pandas/lib.pyx in pandas.lib.vec_compare (pandas/lib.c:13811)()
    799
    800     if n != len(right):
--> 801         raise ValueError('Arrays were different lengths: %d vs %d'
    802                          % (n, len(right)))
    803

ValueError: Arrays were different lengths: 20 vs 3

In [5]: pd.show_versions()

INSTALLED VERSIONS
------------------
commit: d28fd702c87f4c2629c53d763551feb5395ff8b5
python: 3.4.3.final.0
python-bits: 64
OS: Darwin
OS-release: 14.4.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8

pandas: 0.17.0rc1+60.gd28fd70

That would explain why @jreback before only sounded like it's only an issue for df.appy. I'm sure if using tuples is a general problem, he would have warned me. (Or he did, and I wasn't listening. ;) )

I know this has been suggested before...but why not store the tuple as DataFrame columns?  It's more idiomatic, and will be faster / more memory efficient.  If all you ever want to do is access the columns as group, just define something like a fields accessor as I did below.
In [144]: df
Out[144]:
                                BINNING_SET
2014-10-18 07:36:19.926570   (0, 1, 319, 11)
2014-10-18 07:36:19.926570   (0, 1, 441, 11)
2014-10-18 07:36:59.675040  (52, 4, 89, 115)
2014-10-18 07:36:59.675040  (2, 34, 96, 115)
2014-10-18 07:55:27.922290  (52, 4, 89, 115)

In [145]: fields = ['f1', 'f2', 'f3', 'f4']  #names for tuple components...

In [146]: df = df.BINNING_SET.apply(lambda x: pd.Series(x, index=fields))

In [147]: df
Out[147]:
                            f1  f2   f3   f4
2014-10-18 07:36:19.926570   0   1  319   11
2014-10-18 07:36:19.926570   0   1  441   11
2014-10-18 07:36:59.675040  52   4   89  115
2014-10-18 07:36:59.675040   2  34   96  115
2014-10-18 07:55:27.922290  52   4   89  115

In [152]: df[(df[fields] == df[fields].iloc[0]).all(1)]
Out[152]:
                            f1  f2   f3  f4
2014-10-18 07:36:19.926570   0   1  319  11

Thanks, that looks like a not too bad alternative, although the syntax is on the verge of becoming hard to read with this additional .all(1).
Yes, the main reason why working in tuples was a way to filter for a set of these values at once.

@michaelaye you simply need to use a column MultiIndex (e.g. say you have several sets of these tuples).
In [8]: df = DataFrame(np.random.randn(6,4),index=pd.date_range('20130101',periods=6,freq='2s'),columns=pd.MultiIndex.from_product([list('AB'),range(2)]))

In [9]: df
Out[9]:
                            A                   B
                            0         1         0         1
2013-01-01 00:00:00 -0.296009 -0.374544  1.168945 -1.406648
2013-01-01 00:00:02 -0.532468 -0.540057 -0.022324 -0.395088
2013-01-01 00:00:04 -0.742925 -0.051457 -1.107048  0.549880
2013-01-01 00:00:06  1.070147 -0.205438  0.563086 -0.540265
2013-01-01 00:00:08 -0.128169 -0.219555  0.208610  0.438773
2013-01-01 00:00:10  1.287697 -0.496478 -0.266373  0.810742

In [11]: df[['A']]
Out[11]:
                            A
                            0         1
2013-01-01 00:00:00 -0.296009 -0.374544
2013-01-01 00:00:02 -0.532468 -0.540057
2013-01-01 00:00:04 -0.742925 -0.051457
2013-01-01 00:00:06  1.070147 -0.205438
2013-01-01 00:00:08 -0.128169 -0.219555
2013-01-01 00:00:10  1.287697 -0.496478

Hm, my binning sets are just 4 out of a 20-30 column dataframe, so, IIUC, to use the MultiIndex way for different combinations of binning set numbers, I would have to repeat all the other columns, each time, correct? IIUC, you mean something like this:
Out[147]:
                            f1  f2   f3   f4  v1  v2
2014-10-18 07:36:19.926570   0   1  319   11   1   3
2014-10-18 07:36:19.926570   0   1  441   11   2   4
2014-10-18 07:36:59.675040  52   4   89  115   3   7
2014-10-18 07:36:59.675040   2  34   96  115   5   9
2014-10-18 07:55:27.922290  52   4   89  115   4   1

would become
Out[147]:
                           (0,1,319,11)        (0,1,441,11)
                                     v1   v2             v1   v2
2014-10-18 07:36:19.926570            1   3               2    4

no that is very odd to use a tuple as an indexer in a MultiIndex. These should simply be strings.
In [13]: df = DataFrame(np.random.randn(6,5),index=pd.date_range('20130101',periods=6,freq='2s'),columns=pd.MultiIndex.from_tuples([('f',1),('f',2),('f',3),('v',1),('v',2)]))

In [14]: df
Out[14]:
                            f                             v
                            1         2         3         1         2
2013-01-01 00:00:00 -1.165661 -1.181265 -0.126375 -0.834884 -0.357954
2013-01-01 00:00:02  1.087771 -0.529879  0.822059 -0.213104 -0.363985
2013-01-01 00:00:04 -0.246989 -1.611963  0.619888 -0.007096  0.115296
2013-01-01 00:00:06 -1.271250  0.011331 -0.698223 -0.471338 -0.391065
2013-01-01 00:00:08  0.752136 -0.133435 -1.394301 -0.923060  0.301170
2013-01-01 00:00:10  0.053189  0.459304 -2.736818 -0.365441  0.616951

In [15]: df[['v']]
Out[15]:
                            v
                            1         2
2013-01-01 00:00:00 -0.834884 -0.357954
2013-01-01 00:00:02 -0.213104 -0.363985
2013-01-01 00:00:04 -0.007096  0.115296
2013-01-01 00:00:06 -0.471338 -0.391065
2013-01-01 00:00:08 -0.923060  0.301170
2013-01-01 00:00:10 -0.365441  0.616951

Well, I need to retain the values of the binning set, because they have mathematical meaning that I need to apply later on in the process. Of course I could store them somewhere in a dictionary, but that sounds like becoming more complicated than it needs to be.
The other advantage of having these 4 numbers as a tuple is that I am able to do groupby operations over it. Interestingly, pandas head does not have a problem doing that, while the equality check fails.

ok, I guess I don't understand what your issue is. In order to see if their is an actual problem, I would need a self contained reproducible example.
closing, but you can post here.

The above mentioned regression is not an issue per se?

For reference, this was the commit that caused the change: https://github.com/pydata/pandas/commit/4fe7c68728da2174f7ccd290a43e358f16a1a6f9


Fix PySpark DataFrameWriter JDBC method docstring because a dictiona…

What changes were proposed in this pull request?
The Python DocString of the method jdbc of PySpark DataFrameWriter is modified to specify that a dictionary is used instead of a list.
How was this patch tested?
No testing is needed only the docstring was modified.

Can one of the admins verify this patch?

Can you try build the api docs and paste a screenshot? Just want to make sure the special characters are rendered correctly.

Jenkins test this please

Test build #63741 has started for PR 14624 at commit b0864ec.

Test build #63741 has finished for PR 14624 at commit b0864ec.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63741/
Test FAILed.

Merged build finished. Test FAILed.

I just tried to verified this because I was curious of some weird broken characters at the end of some lines here, which are shown only sometimes for unknown reason in my internet browser.
I found these are as below <U+2028>:
+        :param properties: ...  at<U+2028><U+2028>
+                           least ... values.<U+2028><U+2028>
+                           For example { 'user' : 'SYSTEM', 'password' : 'mypassword' }

So, building documentation is being failed as below:
SyntaxError: Non-ASCII character '\xe2' in file .../spark/python/pyspark/sql/readwriter.py on line 720, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

Without those weird characters, it shows as below:

BTW, it seems there is another same instance here, https://github.com/mvervuurt/spark/blob/b0864ecb51a28452f6e33f4bdcd30795c7c2ec99/python/pyspark/sql/readwriter.py#L404-L405.

My bad about the other pull request. This one is the correct one ;)

You just have this one pull request right?

Jenkins add to whitelist

Test build #63788 has started for PR 14624 at commit b0864ec.

Test build #63788 has finished for PR 14624 at commit b0864ec.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63788/
Test FAILed.

@mvervuurt Could you please double check this one? I am pretty sure I checked out this PR and then tested this correctly.

This is the  correct PR. What else would you like me to check?

Could you check if there are some whitespaces at rhe end of lines and building Python document is okay? There is the instruction for building up here, https://github.com/apache/spark/tree/master/docs
Also, could you check the same instance I said above please?
If you have any problem with building up Python documentation, I can open a new PR based on this including the same instance above. I will ask committers to credit that PR to you.

It seems I don't need to build the master anymore. Thanks for accepting the pull request. I'll be sure to build master first next time.


Improve diagram layout of some examples

In some examples, this leeds to the smaller diagram size - which in fact is a positive effect.

Thanks! Especially SimpleAirCycle looks much better now :)

Thanks! Especially SimpleAirCycle looks much better now :)

I feel motivated to try other examples as well. :-)


nhost-cli: 1.28.1 -> 1.28.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/nhost/cli/releases.
meta.description for nhost-cli is: Tool for setting up a local development environment for Nhost
meta.homepage for nhost-cli is: https://github.com/nhost/cli
meta.changelog for nhost-cli is: https://github.com/nhost/cli/releases/tag/v1.28.2
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.28.2 with grep in /nix/store/syv2mx60yrm4yignya8x8ghppcawnfxr-nhost-cli-1.28.2
found 1.28.2 in filename of file in /nix/store/syv2mx60yrm4yignya8x8ghppcawnfxr-nhost-cli-1.28.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

nhost-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/syv2mx60yrm4yignya8x8ghppcawnfxr-nhost-cli-1.28.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nhost-cli https://github.com/r-ryantm/nixpkgs/archive/02816f87e444e971eb8d8b833601eb826df0dc43.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/02816f87e444e971eb8d8b833601eb826df0dc43#nhost-cli

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/syv2mx60yrm4yignya8x8ghppcawnfxr-nhost-cli-1.28.2
ls -la /nix/store/syv2mx60yrm4yignya8x8ghppcawnfxr-nhost-cli-1.28.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

nhost-cli

Maintainer pings
cc @Moraxyc for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Improve workaround for wgpu's gles texture type inference

https://github.com/StarArawn/bevy_ecs_tilemap/blob/3171dcb02bf3ef0183727d507005cfd354e708c6/src/render/texture_array_cache.rs#L151-L152
The current workaround is incomplete, count should not be 1 or divisible by 6.
See https://github.com/gfx-rs/wgpu/issues/3124#issuecomment-1447875760 for more context.

https://github.com/StarArawn/bevy_ecs_tilemap/blob/3171dcb02bf3ef0183727d507005cfd354e708c6/src/render/texture_array_cache.rs#L151-L152
The current workaround is incomplete, count should not be 1 or divisible by 6.
See gfx-rs/wgpu#3124 (comment) for more context.

I'm not sure why count shouldn't be 1 or divisible by 6? It also looks like wgpu hasn't implemented a fix yet.

I have been meaning to test this more with opengl on the desktop, but I think that on webgl2 our users aren't really affected by this because they need to use the atlas feature to avoid another bug anyway.
I attempted this earlier, but I think there are some other criteria that had me scratching my head at the time:
https://github.com/gfx-rs/wgpu/blob/9dc834a0ac694d576a584a89f72733a0bb2f4485/wgpu-hal/src/lib.rs#L884

I'm not sure why count shouldn't be 1 or divisible by 6?

Since we might use GL_TEXTURE_2D, GL_TEXTURE_CUBE_MAP or GL_TEXTURE_CUBE_MAP_ARRAY based on this heuristic instead of the intended GL_TEXTURE_2D_ARRAY.

I think that the other bug I alluded to https://github.com/gfx-rs/wgpu/issues/3197 has been fixed. It doesn't seem totally necessary to use the atlas feature now, so we should probably take a look at this again.


Questions about forking

Because this is MIT license, I assume that this is safe to fork and/or use code from this provided I follow the license and include a disclaimer showing your MIT license where your code is used?
I kinda wanted to make my own codec based config for a general library mod but a friend linked me this and i felt it was a better implementation than I could do, so hopefully you'd be fine with such a fork existing?
Amazing work on this btw.

Forking is fine as long as you follow the license terms.


Formatting testcase: results not as expected

Describe the bug
Formatting doesn't work as expected
To Reproduce
Please see attached testcases
test-input.txt
test-expected.txt

THanks @mariusa.
It will be fixed in the next version.
I'll move this issue to formatter repository, ok?


carrier_ip and wlz support

Please, is there any plan to add wavelength and carrier_ip support to this module?  The amount of kludgery we've had to do to handle WLZs properly is painful, often wrapping this module in another module.
Given Total provisions: 18.8M I feel you may want to take a stab at this internally, but if you're willing to consider PRs. I am willing to give it a go. Thanks.

it would be good if you had any references to the support you are looking for  (hence the request issue template we provide but that was deleted)
there is work on-going to address some of the core shortcomings of the current module version but it won't happen over night. As you said, its is a very heavily used module so significant changes will require judicious testing, validation, and we will need to provide ample supporting documentation for users to upgrade. You can track some of that experimental progress here https://github.com/clowdhaus/terraform-aws-vpc-v4 if interested though

cool, I really like the direction the v4 is going, especially swaping "count" for "for_each".   I will comment more there as I'd much rather put effort on a more future proof codebase.


Captcha Solver

I love your library and I find it very useful!
When will you add the CAPTCHA solver?
Thanks for your work :)

I thought about it... Okay, i will add this feature in next release. Can you suggest list of the best captcha solver?

I think this one is one of the best: https://anti-captcha.com

https://github.com/AdminAnticaptcha/anticaptcha-noDEJS
I like this one too

Guys! Look for this https://github.com/Kamikadze4GAME/node-anticaptcha
Today will write README.md

Hmm, why write your own library, while there already exist a perfectly fine one? (see my previous comment)

Just look at their source code. He is terrible. I wrote my for fast and high-quality support. Soon there will be documentation.

Is this going to be implemented still? This would be really handy


Can we add meta for charts and other elements we add in?

Category

[ ] Enhancement

While creating a chart is can we add a meta option to the chart.xml file while getting from the user.
    let meta = {
        chartId: 123,
        name: 'User 1'
    }
    slide.addChart( pptx.charts.BAR, data, options, meta );

We can add this meta into the chart.xml file like the one below
<c:chartSpace xmlns:c="http://schemas.openxmlformats.org/drawingml/2006/chart"
	xmlns:a="http://schemas.openxmlformats.org/drawingml/2006/main"
	xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships"
	xmlns:c16r2="http://schemas.microsoft.com/office/drawing/2015/06/chart">
	<c:meta>
		<c:chartId>123</c:chartId>
		<c:name>User 1</c:name>
	</c:meta>
</c:chartSpace>

Inside the meta, we can add whatever the meta passed by the creater.

Hi @mariselvanm
It may be in the spec, but PowerPoint doesn't like it.
I added:
<c:meta>
    <c:chartId>123</c:chartId>
    <c:name>User 1</c:name>
</c:meta>

to a chart.xml output file and PPT declared it corrupted at open and stripped it out upon save...


Can't build project on ubuntu 16.04

I have followed all installation steps, installed all necessary tools, but when I now try to make my project, I get the following stacktrace:
[  4%] Building CXX precompiled header cotire/blackbird_CXX_prefix.hxx.gch
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
CMake Error at cmake/Modules/cotire.cmake:1848 (message):
cotire: error 4 precompiling
/root/Projects/blackbird/build/cotire/blackbird_CXX_prefix.hxx.
Call Stack (most recent call first):
cmake/Modules/cotire.cmake:3512 (cotire_precompile_prefix_header)
CMakeFiles/blackbird.dir/build.make:63: recipe for target 'cotire/blackbird_CXX_prefix.hxx.gch' failed
make[2]: *** [cotire/blackbird_CXX_prefix.hxx.gch] Error 1
make[2]: *** Deleting file 'cotire/blackbird_CXX_prefix.hxx.gch'
CMakeFiles/Makefile2:131: recipe for target 'CMakeFiles/blackbird.dir/all' failed
make[1]: *** [CMakeFiles/blackbird.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
Any suggestions on what a possible solution could be?

Which version of gcc is this?

The GCC version is 5.4.0 20160609

Try disabling cotire in cmake. Just comment out the line in CMakeLists.txt
# cotire(${PROJECT_NAME})

The build now continues to fail in a later stage with a different error:
Compiling shell.o:
Compiling sqlite3.o:
Archiving libsqlite3.a:
ar: creating libsqlite3.a
a - sqlite3.o
Linking sqlite3:
Compiling src/curl_fun.o:
Compiling src/bitcoin.o:
Compiling src/check_entry_exit.o:
Compiling src/time_fun.o:
Compiling src/db_fun.o:
Compiling src/result.o:
Compiling src/parameters.o:
Compiling src/main.o:
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
Makefile:53: recipe for target 'src/main.o' failed
make: *** [src/main.o] Error 4
Is it a version conflict somewhere maybe?

You're getting an internal compiler error, it means the source you're feeding it is triggering some kind of bug in the compiler itself. I have no idea why that's happening. You could try building with a different version of gcc or see if you can reproduce the bug with a minimal source example.
I would start with main.cpp and see if that always triggers ICE. From there start stripping out unnecessary code until it compiles successfully. That'll narrow down where the problem is.

Looks like you're running out of RAM. Are you trying to build this on a VPS with 512MB and no swap? What does dmesg say?

I indeed had a VPS with only 512 MB of memory. I increased my VPS memory to 1GB and now the build succeeds.
Thanks for your help!


WAX showing but seems inaccessible

As long as I can remember, I've been able to see my WAX tokens but not access them. I just figured it was a glitch that would clear up with an update, then I forget for awhile, then I try again and the same thing. What's going on?

Might be a UI bug. We are up to version 1.2.2 now, I'm curious to know if that resolves the issue.
I'd probably also recommend looking at the account on wax.bloks.io and see if there's any information you can glean.
If 1.2.2 still doesn't work, knowing the account name itself would likely help because we'd be able to setup a Watch Wallet for it and see the exact same interface you would see (anyone can setup a watch wallet for any account, feel free to try). If 1.2.2 doesn't resolve it and you don't mind sharing that account name, feel free to email it to<EMAIL_ADDRESS>and we can take a look.

Thanks Aaron,
I am updated to 1.2.1. I took the snap a bit ago and just didn't get to sharing until today.
It still shows the same in 1.2.1. But on the blockchain it shows no wax at all, just Karma
This is a genesis acct, in case that helps. Do you know if there are WAX tokens somehow locked or something?

That's very weird, I haven't run into this before.
The "Total" column is a combination of staked, liquid, refunding, delegated and REX (where it exists), so there's a number of places it could be coming from.
Without digging into the account itself and looking I'm not sure what it could be though.

Emailed
Thanks Aaron


Might cause crash in karaoke text after sprite text support localization.

Because karaoke text(or lyric text) is based on SpriteText, which will cause error after sprite text support localization
The main solution might create it's own sprite text, not use exist one.

Fixed in #19


very long generation time

Thanks for putting time and effort in such an amazing project, Great work!
Currently i'm using Chatette in a project (Generation modifiers are awesome), one problem though, the generation takes too much time!
i'm generating about ~35K sentences

Statistics:

Parsed files: 29
Declared units: 80 (80 variations)
	Declared intents: 8 (8 variations)
	Declared slots: 17 (17 variations)
	Declared aliases: 55 (55 variations)
Parsed rules: 11031

generation takes about ~ 1 hour, while a clone to chatito takes about ~ 10 min
my question is:
what's the complexity of chatette? or what aspect of the statistics above, the generation time is directly propotional to?
(i noticed that chatette runs on a single core, so i've tried splitting the master file into 4 files and used ray to generate each master file on a separate worker.
with this i managed to get the generation time down to ~25 min but still quite an overhead)
if anyone have a thought or advice, i'd be grateful!

This is weird, I used to generate ~27k sentences in around a few minutes. That being said, I didn't test performances since v1.4.2, and I made a large refactor which might have decreased performances. I'll check again on v1.6.0.
Would you mind answering a few questions so that I can have a better understanding of what is going on here?

I assume you are using a fairly normal computer but I prefer to ask, is your computer particularly slow?
Can you confirm you are using Chatette v1.6.0?
Which part of the process is especially slow: parsing, generation or writing the outut file(s)?
Are your template files particularly convoluted? By that I mean, do you often have very long chains of aliases used inside other aliases, used in other aliases, and so on? Also, do you use a lot of modifiers?
Could you measure whether it is the memory consumption or the CPU utilization that is the limiting factor? Basically, when you run Chatette, is most of your RAM being used or is the CPU core that it is executing on running at full throttle?

To answer your questions, you can see a rule as a tree, where each piece of content would be a node, and branches would be possible choices the generator can make.
For example, the template
%[intent]
    A single rule with an ~[alias] and a [choice|small choice]

~[alias]
    another rule with a [choice|small choice]
    a third rule

could be seen as

To generate an example, Chatette traverses such a tree. Therefore, several factors can increase generation time:

the depth of such a tree
the number of unit references/choices in the rules
the length of the rules

There are a few things I would suggest you do to try and decrease the execution time, aside from the obvious suggestion (e.g. closing all resource intensive application when running Chatette):

as I said before, try to keep your rule trees as shallow as possible, limiting the amount of unit references and choices you use in them
limit the amount of generation modifiers if you don't really need them as they add a small overhead during generation
if you can, split your files in separate files, and run Chatette separately on each of them to avoid regenerating a lot of examples when you only made changes to a handful of units. What I usually do is to have several master files which contain unrelated intents, and one file containing "common" aliases that are included in each master file.
you can maybe try using Chatette v1.5.0 and see if the performance is better. Be careful that some syntax was introduced in v1.6.0 and will not be recognized in previous versions (you can take a look at the changelog).
you can try using a faster python interpreter such as pypy
you can take a look at the code and try to make it more efficient
your way of parallelizing the execution using ray certainly is one of the best solution. Chatette obviously has a potential to execute in a multi-threaded way, I might add this in the future.

Of course, those suggestions are just workarounds, having Chatette execute for an hour for "only" 35k examples is not acceptable. Improving the performance of Chatette is the real solution here. I will do it but it will certainly take time.
On a side note, if you are using Chatette for machine learning tasks, be careful that you can easily have your models overfit with such a high number of examples.
I hope this helps and thank you for your kind message :)

Apologies for late reply, things came up and couldn't access the machine on which i'm experimenting.
First of all, Thank you the detailed reply, and yes it helped!! (especially the second half)
regarding your questions:

I assume you are using a fairly normal computer but I prefer to ask, is your computer particularly slow?

Well, it's a Thinkpad with Core i7-8565U CPU and 8 GBs of RAM.

Can you confirm you are using Chatette v1.6.0?

Yes! i'm using version 1.6.0

Which part of the process is especially slow: parsing, generation or writing the outut file(s)?```

The generation i think, because the parsing is done quickly and i'm left with the prompt: [DBG] Generating training examples...

Are your template files particularly convoluted? By that I mean, do you often have very long chains
of aliases used inside other aliases, used in other aliases, and so on? Also, do you use a lot of modifiers?

Yes kind of, a typical intent definition is basically built of aliases, some of them are nested up to 4 levels.
i.e
[high_level_alias --> sub_alias_lvl1 --> sub_alias_lvl2 --> small_alias that contain slots]
i think here's some work that can be done (flatting and splitting things a bit)

Could you measure whether it is the memory consumption or the CPU utilization that is the limiting factor? Basically, when you run Chatette, is most of your RAM being used or is the CPU core that it is executing on running at full throttle?

i think it's CPU, here's a screenshot from htop when generating today:

this run took about ~50min

What i'm going to do is to try to refactor my templates as much as i can, but without hurting the modularity and readability as much (chatette winning point).
and regarding performance optimization of v1.6.0 it would be awesome if i can help!! but i lack the experience in that matter. that's why i went for dealing with it as a black box and try to multi process on a high level or use ray.

Thanks for your replies :)
I think I see what the problem is: since v1.6.0, I've been trying to use caching during generation to improve generation time, but for big templates, it will use the whole RAM which makes it very slow. I assumed this would be a problem for much larger files but apparently I was wrong.
I'll add a way to disable that (or just turn it down) in the next update. It is likely it will take time as I don't have much time at the moment, so I hope you can cope with the current version.
If you can, trying the previous version (v1.5.2) could help I think.
Thanks again for the heads up!

I just released a patch (v1.6.1) which tackles the issue temporarily: the problem came from the caching strategy which is way too aggressive. That patch disables caching when there are more than 50 units (aliases, slots and intents) declared.
I could record about a 4x increase in the execution time, for medium size templates (you can find my benchmarks here).
Of course, this is just a temporary solution, I plan to tackle the issue in a cleaner and more robust way in future releases. I will keep this issue open until I am satisfied with the caching strategy, and more generally the execution time.


Roll Engine from 6934f8aa311e to c2c74ed7080a (2 revisions)

https://github.com/flutter/engine/compare/6934f8aa311e...c2c74ed7080a
2020-10-21<EMAIL_ADDRESS>Roll Dart SDK from 8be6a08153cc to 86242db30c23 (2 revisions) (flutter/engine#22018)
2020-10-21<EMAIL_ADDRESS>Roll Skia from 1c823674d957 to 2d2f82c00aeb (13 revisions) (flutter/engine#22015)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Landing to kick tree


Change recommended RE.md to PersistentDict.

Closes #1227. See that issue for motivation and design discussion.
This is a critical fix that should go into 1.6.0.

Basically, replace sqlite3 persistence with PersistentDict.
Any gotchas?
I've no particular experience with PersistentDict and our beam lines are not tied to any specific implementation of persistence.   Where's the documentation for PersistentDict?
This should work like plumbing, hope this will not be user-visible.

Is this OS-independent (looks like it is)?

Yes.

Thought you said zict was not a good fit. Can you comment more about how msgpack overcomes this fit?

Yes, I was originally imagining a solution that let us use a single file. Upon further consideration, using a directory is a better choice because it can be faster and mitigates contention issues. Using msgpack for serialization overcomes my concerns with JSON (which has to convert numpy arrays to lists) and pickle (which raises security concerns when applied to long-term storage).

Good find. I think that would also be a defensible choice; it is a well-documented and actively maintained project. I'm personally happier with a thin wrapper (PersistentDict) of a thin wrapper (zict) of a MutableMapping. It looks like PersistentMapping introduces additional abstractions (a cache and a "data manager") that are beyond the scope of our needs.

Thanks for the good questions, @prjemian!

Thanks for adding the test with RE!

Hurray for numpy.testing.assert_array_equal! I have had trouble testing msgpack because it turns lists into tuples, or the other way, and this handles it.

Thanks, all!


Add encrypted API key to AppVeyor

Why is the AppVeyor build failing?

This branch is not meant to be built, and has no configuration for it. It just contains one (now two) encrypted files to be fetched by the master AppVeyor build.


[Discussion] How to update Spleeter properly

Hi,
I currentkly have Spleeter Version: 2.3.1 installed on my macMini M1.
How do I properly update it to the latest version?
Cheers Marc

Hi @daslicht
Do you need to update for any particular reason ?

Hi @daslicht
Do you need to update for any particular reason ?

nope I just ask out of curiosity


Make file copying async to support network copies

File IO is blocking and synchronous. When working with local file system IO this is fine, since its going to block there anyways, but we should be able to dispatch all child directories across an asyncio.gather at each step of the directory tree walk traversal.
We should implement a semaphore to limit the number of coroutines that get launched. We can launch this same asyncio dispatch when copying files, so that file copies aren't done serially, but can be passed to the host system IO and run concurrently. Especially for network traffic IO when supporting universal pathlib type Path objects for cloud storage, as in #9 .


Is the widget working only when connected to the same network?

Hello, good morning, As I wrote yesterday UI-Service not reachable! #18, the widget finally was working good, this morning as well, but when I left home and get into the the office wifi, the widget is not reporting any more, I have it connected to the cloud.
Is it supported or I have to be in the same net to get the information?
Thnak you

If you should be able to reach your system from anywhere than maybe you need to increase the timeout variable in the script. It is currently 2seconds. Maybe increase this value and try again

Hello, Yes I have to 10 since yesterday, but it is not reachable. I increase to 15 and the same result

And when you copy the url from the script into the browser you can access your homebridge-config-ui-x ?
The widget is not explicitly constructed to work outside the same network, so i don‘t know if it should work in your concrete case

Not really, to access I should be in my network. Other wise I should use a Public IP. I think it is clear. Is not possible to access from different network. Any way getting back I will check if the access thru the widget works, then I will have all clear. But to all the Hombridge plugin device services in IOs I can access being outside.

Yes you probably have an apple tv or a homepod or an ipad setup as you hub for homekit, that‘s why you can control your devices. But that is something completely different. And if you cant access the homebridge-config-ui-x with the url you use in the script then it of course won‘t work especially if it is not a public ip but a local one...

Yes, I thought so.

Confirmed! it works only being in the same network.

The „only“ part is not entirely true. It depends on your concrete system setup. It should technically work if you can publicly access your homebridge-config-ui-x instance

Sorry, I close it by accident. How can I make it public access? Public IP?

I guess public ip yes.

I need to open ports to have the access to the Config-UI-X. I think will stay where I am. Only monitoring  the info when I am in the same network. Thank you. Your widget is amazing!!!


How to target Source Text of Layer inside a Composition in the Composition

The AE file I have contains a 'main' composition, in this I have a couple of basic text fields, but also a composition called 'myComposition' which has source text in I wish to change. How do I target that source text in my assets definition?
          {             value: 'Angry Cat',             type: 'data',             composition: 'myComposition'             layerName: 'personName',             property: 'Source Text'           },

the piece of code you provided should work just fine
another way is to target all compositions by using *symbold


AO texture influences roughtness

I'm trying to bake AO for my models and export them als GLB's to view in Three.js.
My setup looks like this :

And it gives me the following result in the GLTF Viewer :

It seems like the AO Map influences the roughness map somehow, you can see the org. roughtness texture is applied as well. I also tried to use the same map for both textures but just scale one of them but that doesn't work at all, the mapping node is ignored.

In the file there is another object with ao and normal where everything works fine. On the other hand the normal map is an own texture and ao, metal and roughtness get joined which might be the reason the mapping node solution doesn't work and they all must use the same uv...
Blend File and GLB :
AO_Test.zip
ao_map_in_spec.zip
It would be much appreciated if someone could help me.

This is probably because the image is encoded as a JPEG. JPEG artifacts aren't confined to one channel so if there are hard edges causing artifacts in one channel, they will visibly bleed into the others.

Try setting the option Geometry > Images to PNG format (.png) when you export and see if it still happens.

Seems we can close this ticket.
Don't hesitate to comment if you have any info to add.


Bug: WikiRunner: "NextKatacodaStep" cant display Images in the .asciidoc file

Bugfix has been merged with another PR


load file from assets in standalone

this should not be there, drop a file on the patchfield to load an asset

this should not be there, drop a file on the patchfield to load an asset

this results always in something like this. how can i upload things to the assets folder ?

for the standalone (for now) there will be no "asset folder" as there is on cables.gl, you simply access files on your local machine. these will be listed in file manager, eventually.
does the texture above work for you if you connect it somewhere? title is weird though....

@wirmachenbunt how did you manage to get into the state of the first screenshot at all, do you remember?

when i created the first cables project, it created the assets folder with it. looked like the stuff is supposed to be in there. hence i put the textures in the folder, accessed them via the UI in cables - > error

okay, cool, thanks!


Add a shortcut to get to next breakpoint

I'm currently trying the v2-integration branch on neovim. It is great that now the vdebugstart is made in the background, but now each time I press  to get to the next breakpoint, the session is then closed because it expects another one.
My point being that we should be able to have a shortcut to get to the next breakpoint, unless I missed something...

@Taluu hmm in normal vim F5 brings you to the next breakpoint. This might be neovim specific.

Yup, that is what it did when I was using the master branch, on neovim...
Maybe adding another shortcut for breakpoints could do the trick ?

Nevermind, it seems that on "normal" sessions (with autostart), F5 does bring me to the next breakpoint as expected, but for a reason that I can't wrap my head around is that with an ide key, F5 ends the session and expects another session...

If it does not hit your breakpoint its normal behaviour in v2, it keeps on listening for a new incoming request, where v1 would only handle one request and stop

I'll test it a bit further with the ide key, I think this is why it does that...

thanks

@Taluu can thisone be closed? It looks like its having the correct behaviour

I'll have to check as I didn't have the occasion to test it with the idekey...

@Taluu maybe if some weird behaviour happens with idekey enabled it should be another issue?

Yeah, sure. Closing then.

Had this issue again. No ide_key set, but using Docker.
With the proper path sets (through the path_maps option), I can debug, but if I try to jump on the next breakpoint with <F5>, it ends the session. Here are the logs with level 2 :

Log opened at 2018-03-25 02:41:49
I: Connecting to configured address/port: <IP_ADDRESS>:9000.
I: Connected to client. :-)
-> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///srv/api/public/index.php" language="PHP" xdebug:language_version="7.2.3" protocol_version="1.0" appid="34" idekey="www-data"><engine version="2.6.0"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2018 by Derick Rethans]]></copyright></init>

<- context_names -i 1
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="1"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context><context name="User defined constants" id="2"></context></response>

<- feature_set -i 2 -n max_children -v 128
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="2" feature="max_children" success="1"></response>

<- breakpoint_set -i 3 -t line -f "file:///home/talus/dev/foodmeup/backend/public/index.php" -n 5 -s enabled
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="3" state="enabled" id="340012"></response>

<- step_into -i 4
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="step_into" transaction_id="4" status="break" reason="ok"><xdebug:message filename="file:///srv/api/public/index.php" lineno="3"></xdebug:message></response>

<- stack_get -i 5
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="5"><stack where="{main}" level="0" type="file" filename="file:///srv/api/public/index.php" lineno="3"></stack></response>

<- context_get -i 6 -c 0
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_get" transaction_id="6" context="0"><property name="$v" fullname="$v" type="uninitialized"></property></response>

<- run -i 7
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="7" status="stopping" reason="ok"></response>

Log closed at 2018-03-25 02:42:01

- [Debug] {Sun 25 2018 04:41:55} Setting buffer for DebuggerWatch: ['[ *Locals ] [ Superglobals ] [ User defined constants ]', '', '- Locals at /path/to/project/public/index.php:3', '', ' ⬦ $v = (uninitialized)', '']
- [Debug] {Sun 25 2018 04:41:55} Setting buffer for DebuggerStack: ['[0] {main} @ /path/to/project/public/index.php:3', '']
- [Debug] {Sun 25 2018 04:41:55} Setting buffer for DebuggerStatus: ['Status: listening', 'Listening on :9000', 'Not connected', '', 'Press <F5> to start debugging, <F6> to stop/close. Type :help Vdebug for more information.']
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F7> :python3 debugger.detach()
'
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F4> :python3 debugger.step_out()
'
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F2> :python3 debugger.step_over()
'
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F12> :python3 debugger.eval_under_cursor()
'
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F3> :python3 debugger.step_into()
'
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F11> :python3 debugger.get_context()
'
- [Debug] {Sun 25 2018 04:41:55} Storing existing key mapping, 'noremap <F9> :python3 debugger.run_to_cursor()
'
- [Info] {Sun 25 2018 04:41:55} Found connection from ('<IP_ADDRESS>', 39586)
- [Debug] {Sun 25 2018 04:41:55} Command: context_names -i 1
- [Debug] {Sun 25 2018 04:41:55} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="1"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context><context name="User defined constants" id="2"></context></response>
- [Debug] {Sun 25 2018 04:41:55} Available context names: {0: 'Locals', 1: 'Superglobals', 2: 'User defined constants'}
- [Debug] {Sun 25 2018 04:41:55} Command: feature_set -i 2 -n max_children -v 128
- [Debug] {Sun 25 2018 04:41:56} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="2" feature="max_children" success="1"></response>
- [Info] {Sun 25 2018 04:41:56} Updated line number of breakpoint 11001 to 5
- [Info] {Sun 25 2018 04:41:56} Registering 1 breakpoints with the debugger
- [Debug] {Sun 25 2018 04:41:56} Command: breakpoint_set -i 3 -t line -f "file:///path/to/project/public/index.php" -n 5 -s enabled
- [Debug] {Sun 25 2018 04:41:56} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="3" state="enabled" id="340012"></response>
- [Debug] {Sun 25 2018 04:41:56} Command: step_into -i 4
- [Debug] {Sun 25 2018 04:41:56} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="step_into" transaction_id="4" status="break" reason="ok"><xdebug:message filename="file:///srv/api/public/index.php" lineno="3"></xdebug:message></response>
- [Debug] {Sun 25 2018 04:41:56} ** RefreshEvent
- [Info] {Sun 25 2018 04:41:56} Getting stack information
- [Debug] {Sun 25 2018 04:41:56} Command: stack_get -i 5
- [Debug] {Sun 25 2018 04:41:56} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="5"><stack where="{main}" level="0" type="file" filename="file:///srv/api/public/index.php" lineno="3"></stack></response>
- [Debug] {Sun 25 2018 04:41:56} Replacing remote path (/srv/api) with local path (/path/to/project)
- [Debug] {Sun 25 2018 04:41:56} Replacing remote path (/srv/api) with local path (/path/to/project)
- [Info] {Sun 25 2018 04:41:56} Moving to current position in source window
- [Info] {Sun 25 2018 04:41:56} Setting source file: /path/to/project/public/index.php
- [Debug] {Sun 25 2018 04:41:56} Setting source line number: 3
- [Info] {Sun 25 2018 04:41:56} Placing pointer sign on line 3
- [Debug] {Sun 25 2018 04:41:56} ** GetContextEvent
- [Info] {Sun 25 2018 04:41:56} Getting Locals variables
- [Debug] {Sun 25 2018 04:41:56} Command: context_get -i 6 -c 0
- [Debug] {Sun 25 2018 04:41:56} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_get" transaction_id="6" context="0"><property name="$v" fullname="$v" type="uninitialized"></property></response>
- [Info] {Sun 25 2018 04:41:56} Writing 1 properties to the window
- [Debug] {Sun 25 2018 04:41:56} Writing to window:
[ *Locals ] [ Superglobals ] [ User defined constants ]

- Locals at /path/to/project/public/index.php:3

 ⬦ $v = (uninitialized)

- [Debug] {Sun 25 2018 04:41:56} ** TraceRefreshEvent
- [Debug] {Sun 25 2018 04:42:01} ** RunEvent
- [Info] {Sun 25 2018 04:42:01} Running
- [Debug] {Sun 25 2018 04:42:01} Command: run -i 7
- [Debug] {Sun 25 2018 04:42:01} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="7" status="stopping" reason="ok"></response>
- [Debug] {Sun 25 2018 04:42:01} ** RefreshEvent
- [Info] {Sun 25 2018 04:42:01} Debugging session has ended
- [Info] {Sun 25 2018 04:42:01} Closing the connection
- [Debug] {Sun 25 2018 04:42:01} Closing the socket
- [Debug] {Sun 25 2018 04:42:01} ** ListenEvent
tail: /tmp/vdebug.log: file truncated
- [Debug] {Sun 25 2018 04:42:01} Closing the socket
Sun 25 2018 04:42:01} Listening on port 9000
- [Debug] {Sun 25 2018 04:42:01} Closing the socket

Would you like me to open a new issue ? It's kinda related ("jump to the next breakpoint"), but it's also another symptom : can't get on another breakpoint, it tries to listen again to a new connection.

Hum, nevermind, it seems to work normally. It's just that if you put a breakpoint on an echo (or something that outputs something ?), it's ignored... ?
I don't think this is vdebug's fault, so I'll reclose this issue. Sorry for the noise.


Facebook API no longer allows retrieval of user friends

As noted here: https://developers.facebook.com/bugs/1502515636638396/ version 2.0+ of the Facebook Graph API can no longer be used to access a list of the user's friends. This prevents our app from identifying potential family members via the user's friend list.

Possible workaround found in the Graph API "taggable_friends" endpoint. More testing needs to be done to determine what makes a friend "taggable".
One downside using taggable_friends is that there is a great deal of junk data introduced, issue #5 has been created to address that problem.

Resolved via use of Facebook taggable_friends. Issue closed.


Support using directories that are not subdirectories of the SPRAS directory

The input, output, and config files all have to be in the subdirectories of the SPRAS directory. Any input files have to be copied into the spras input subdirectory. Would it be possible to set a different working directory or use directories that are not SPRAS subdirectories for input, output, and config?

After the updates in #49, the container run interfaces now support input, output, and config files in arbitrary locations on the file system.  However, we still need to update and test our dataset loading code if we want to use alternative working directories or absolute paths.   My initial tests with absolute paths on Windows failed.  It may be related to how Snakemake expects path components to be joined in Windows that differs from os.join.


Anime Game stuck in an awkward position and no way to set to fullscreen.

option + enter
or
command + enter
to switch to fullscreen
seriously how is this worth filing an issue? you can just enter the game and change the in-gaming setting. it's so strange that i think you are abusing github issues.

Well the in game settings would all say "windowed" so I'd thought of filing a report, sorry.


mantlui: bump nginx-mantlui version to 0.6.4

fixes #1072

@sehqlr @TanyaCouture ready to test. verify that the traefik UI works correctly. You can check Chrome dev tools to make sure there are not API request errors and/or deploy an app in marathon and verify that it shows up in the Traefik UI correctly

I tested this out on DO and GCE, and both of the test cases that @ryane asked for passed.


MPI on HPC

I've been testing out the GUI on Brown's HPC system (OSCAR). Running simulations with the MPI backend is not working because it's requesting too many processors than the instance allows. The node that my instance is running on has 48 cores, but my instance is not allotted access to all the node's cores.
https://github.com/jonescompneurolab/hnn-core/blob/18830b53c4602c8e0f9b89502222b27799c5e3ae/hnn_core/gui/gui.py#L1916-L1918
The GUI initializes the backend at the lines above using multiprocessing.cpu_count, which returns the node's total but not my instance's allotment.
The joblib backend allows you to specify the number of cores in with the GUI. Is there a reason why this option is not exposed for MPI?
joblib options

MPI options

This stack overflow answer also has a way to get the number of available cores instead of total.

This shouldn't be an issue if mpiexec is called with oversubscription allowed. Any idea why it's still failing?
If I recall correctly, the goal with the GUI was to expose as little of the parallel backend API as possible while still running the tutorials in a timely manner. Since almost all of the tutorials run single trials, JoblibBackend isn't very useful and MPIBackend can easily be run under the hood by defaulting to the maximal number of parallel jobs.
We can still convert to len(os.sched_getaffinity(0)), but I personally don't think it's necessary to expose the n_procs argument in the GUI. Big picture, I think there's something to be said for the GUI running without too much technical bloat that will confuse new users.

@rythorpe Are you suggesting we also remove the Cores: option from the GUI when using the JoblibBackend? If the goal is to remove the technical bloat, should we also remove the MPI cmd: option from the GUI? Not sure if we expect users to actually change this from the default
For what it's worth, I personally don't find it too technical to expose the number of cores. It can be nice to see what you have access to on your machine, as long as the max is set to the # of cores available on the instance to prevent user input error

@rythorpe Are you suggesting we also remove the Cores: option from the GUI when using the JoblibBackend? If the goal is to remove the technical bloat, should we also remove the MPI cmd: option from the GUI? Not sure if we expect users to actually change this from the default
For what it's worth, I personally don't find it too technical to expose the number of cores. It can be nice to see what you have access to on your machine, as long as the max is set to the # of cores available on the instance to prevent user input error

See the conversation on the PR for more details. I guess I see the GUI primarily an educational tool, so while I agree that adding the number of cores as a simulation parameter in the GUI isn't, in itself, a deal breaker, I think there's something to be said for a GUI simulation that "just runs" without having to sift through a myriad of parameters that don't directly relate to the scientific discourse of our workshops.


Feedback Wanted | Small Store Listing

Some very niche small stores which are bitcoin only have requested to be added.
I think these are most suitable for the spend bitcoin page however they are so niche that the general audience of bitcoin-only may not find them useful (lowering signal:noise)
I propose that either there is a niche stores page or we don't list this type of store.
Interested to hear thoughts from users and contributers.

Do these stores only accept Bitcoin as a payments method? Are they related to Bitcoin besides payment method?
If they are only being considered to be added to Bitcoin-only because they only accept Bitcoin for payment, I don't think it makes sense, seems like they should be a Bitcoin related business to be added.
That being said, I can see the value in having a list of stores that accept Bitcoin for payments. I assume the list will eventually be too large to manage, and at that point the list won't matter anymore.
If you have cycles, I'd suggest making a Bitcoin only payments page.

Second joe's thoughts.
It'd definitely be nice to see a list of stores that accept bitcoin (only) for payments, and I have seen a few loose compilations floating around the internets, but the maintenance of that would likely be a nightmare.

Agreed - If a store is bitcoin-only AND sells bitcoin related products/services they will be listed.
There are far too many websites that simply accept bitcoin but don't sell bitcoin related products/services - It would be impossible to keep track.


Local Files Migration to ODFB

This document mentions that "If you have files and folders on your computer or on a network drive, you can use either of the following tools to to migrate that content to your own OneDrive for FREE!"
But Migration Manager and SPMT can be used to migrates files from file shares. I couldn't find any way to migrate files from individual computer to their respective OneDrive.
Can you please provide some clarity on Local Files and Folder migration from individual desktop to OneDrive in the Article?
Thanks.

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

ID: 8673a55f-50c6-bd98-6b4f-d54db859216d
Version Independent ID: 571c56c2-0be7-0296-ab36-3a75ff3874a9
Content: Migrate content to OneDrive in Office 365 - Migrate to SharePoint and OneDrive
Content Source: migration/Migrating-content-to-OneDrive-for-Business.md
Service: sharepoint-online
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@3novsan  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@3novsan Thank you for reaching out and helping improve MS Docs. Please have a look at this article and let me know if it helps at all. https://techcommunity.microsoft.com/t5/microsoft-onedrive-blog/migrate-your-files-to-onedrive-easily-with-known-folder-move/ba-p/207076

@3novsan Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Design/Trials new locks

Design a new, better locking grid system. Might need to go back to drawing board here.

RFID tags for the key and the box
GPS for kayaks

kayaks locks are directly connected to the screen


Auto Type Table should respect typescript alias in tsconfig.json

What problem will this feature address?
as title, for now I read the source code it's just fs.readFile(path). However, in my code it's a huge monorepo and it's pretty hard to maintain to use relative path
Describe the solution you'd like
    "paths": {
      "@/*": ["./src/*"]
    },

<AutoTypeTable<EMAIL_ADDRESS>name="HandlerContext" />

Describe alternatives you've considered
I have to add my wrapper
const { AutoTypeTable: Internal } = createTypeTable();

const AutoTypeTable = (props) => <Internal {...props} path={...}/>

Additional context
No response

The path property is the file path of ts file, not an import path. It is required because we need to manipulate the file content and to improve performance by not scanning every file to Typescript Compiler.

Also have you tried type? It's probably what you're looking for.
https://fumadocs.vercel.app/docs/ui/components/auto-type-table#type


spin up CircleCI to execute cargo test for lib3h repo

As a network developer, I can rely on CircleCI to execute cargo test on lib3h so that I don’t have to manually do it each time.

[ ] Create a Circle job that executes cargo test against the lib3h codebase

resolved by https://github.com/holochain/lib3h/pull/38


Support for mobile and tablet resolutions

A collection of potential changes, or "weak points" we need to address to achieve a more responsive design.
Desktop ( > 1024px )
Study List

[ ] 1700px: Table no longer centered
[ ] 1570px: Table begins to go off screen

Viewer

[ ] xxx: Layout grid size allows for impossibly small viewports
[ ] 1486px: Overlay text begins to overlap
[ ] 1180px: Toolbar buttons wrap
[ ] 1118px: Toolbar buttons 3x wrap
[ ] 1024px: Open Measurements and Series side panels make for difficult viewing

Tablet ( > 769px )
Study List

[ ] 980px: "Investigational Use Only" header wraps
[ ] 680px: Logo text wraps
[ ] 500px: User preferences modal minimum width

Viewer

[ ] xxx: Thumbnail vertical height allows for limited view of series in scroll list
[ ] xxx: Free floating CINE player doesn't mesh w/ tablet design patterns
[ ] 950px: Measurements panel settings overflow off screen
[ ] 510px: More menu wraps
[ ] 500px: User preferences modal minimum width

Mobile ( > 320px )
Study List

[ ] 630px: Date range selector minimum width

Summary
Study List
Our biggest hurdle is the table. Tables are notoriously difficult to make responsive so you can see the right data in the right contexts. I like to refer to this ux design article for patterns that may be of some help. On our lowest resolutions, I'd recommend having a single search input that plain text OR filters on all fields, and an "advanced" filtering button that uses a sidedrawer for additional filters.
We can move to a card list, or keep the table and reduce our data to what's needed to "seek" our entry. Tapping an entry on mobile might expand the row (or open a panel) to show more information before we initiate viewing.
Viewer

Determine available layout sizes/options based on screen resolution
Side panels become drawers that overlay the main viewing area. We can probably persist thumbnails w/ the viewer on tablets, but not mobile.

This can make drag-n-drop much trickier

Dynamic toolbar buttons that can adjust to the available viewing space and collapse intelligently. As we add extensions, how smart we can make this without overcomplicating config will be very important

👞 🤖 💨

👞 🤖 💨
There is an in-progress PR that addresses these issues for the StudyList route. The Viewer would be next.

Side Panels become "drawers" on mobile
Overlay text uses a better layout for small screens
Conditionally available layouts based on screen size
Need to be extremely clever with our toolbar

This was an outdated wish list. I'm more than happy to accept PRs for this functionality, but I'm okay with it falling to the graveyard until we make a concerted effort to address our shortcomings here.


containerd library update

Description
I've scanned dockle using trivy, and it complains me an high severity issue in library containerd v1.5.1 used by dockle, issue seams easy to fix by updating library to at least v1.5.7 or latest v1.6.0

What did you expect to happen?
What happened instead?
Output of run with -debug:
(paste your output here)

Output of dockle -v:
dockle version 0.4.4
(paste your output here)

Additional details (base image name, container registry info...):

This issue has been fixed in v0.4.5.