fix: uneven list header padding (#12029)

SUMMARY
Adjust list header padding.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Closes #12029
@junlincc
TEST PLAN
1 - Go to any major list (charts, dashboards, databases, etc)
2 - Check header padding
ADDITIONAL INFORMATION

[x] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12412 (65bc2e1) into master (4cf3f99) will decrease coverage by 3.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12412      +/-   ##
==========================================
- Coverage   66.79%   63.17%   -3.62%
==========================================
  Files        1014      485     -529
  Lines       49524    29884   -19640
  Branches     5077        0    -5077
==========================================
- Hits        33079    18879   -14200
+ Misses      16314    11005    -5309
+ Partials      131        0     -131

Flag
Coverage Δ

cypress
?

javascript
?

python
63.17% <ø> (-0.90%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.24%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/db_engine_specs/presto.py
70.56% <0.00%> (-11.48%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
86.49% <0.00%> (-5.49%)
:arrow_down:

... and 549 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4cf3f99...65bc2e1. Read the comment docs.

Codecov Report

Merging #12412 (65bc2e1) into master (4cf3f99) will decrease coverage by 3.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12412      +/-   ##
==========================================
- Coverage   66.79%   63.17%   -3.62%
==========================================
  Files        1014      485     -529
  Lines       49524    29884   -19640
  Branches     5077        0    -5077
==========================================
- Hits        33079    18879   -14200
+ Misses      16314    11005    -5309
+ Partials      131        0     -131

Flag
Coverage Δ

cypress
?

javascript
?

python
63.17% <ø> (-0.90%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.24%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/db_engine_specs/presto.py
70.56% <0.00%> (-11.48%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
86.49% <0.00%> (-5.49%)
:arrow_down:

... and 549 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4cf3f99...65bc2e1. Read the comment docs.

tested - No issues found

tested - No issues found

Code looks good to me. Tempted to do the usual nag about gridUnit, but I don't like fractional gridUnits, so I'll let the 2px go :)
I'd merge this, but would love to have @nytai's nod of approval first :D

Code looks good to me. Tempted to do the usual nag about gridUnit, but I don't like fractional gridUnits, so I'll let the 2px go :)
I'd merge this, but would love to have @nytai's nod of approval first :D


Option to use git branch name automatically as alias

Feature request
The alias plugin is especially valuable for development in a multi-developer scenario with features developed in separate branches. An idea is that the plugin offers an option (either in serverless.yml or as a commandline parameter) that automatically derives the alias name from the branch that is deployed from.
If enabled the plugin would use git to determine the current branch. Then it would automatically set the alias name to the branch name on "serverless deploy".
The exception are builds done on build servers, where in general a commit is checked out and not a special branch. The plugin should determine this scenario and refuse deployment on such systems without specifying an explicit alias (via the --alias switch).

As we use one branch per feature and per bug, we have A LOT of branches over the course of a few weeks. This feature would require a cleanup of these branches once merged into master but I'm not sure how this should work on a CI/CD.

Yes, you're right. This is probably not a feature that would be used in such a heavy load environment (in regards to code creation and death). Maybe on the developer side the already existing deploy --alias and remove alias --alias workflows are pretty enough to let devs test their implementation and keep control over the lifetime of an alias by themselves.
Another issue with the branch name approach could be the length limits for stack names that are implied by AWS (max. 128 characters). Structured git branch names would easily break here.

Closing this for now as it is quite exotic and error-prone.


Add upper-bound for Tensorflow version (<2.0.0)

closes #498
Currently setup.py installs any Tensorflow version above 1.8.0, including 2.0.0 now that it has been officially released. This PR adds upper bound to <2.0.0.
Open questions:

Should installation fail if it detects tensorflow>=2.0.0 installed? Sounds reasonable that way, but also many Python packages "force-install" their versions of packages.
Should docs stress that this is for Tensorflow versions >=1.8.0,<2.0.0?

Thanks for the PR

Should docs stress that this is for Tensorflow versions

yes

Should installation fail if it detects

I don't know. It will fail anyway afterward


"undefined method `route_instance_path' for nil:NilClass" when creating a comment

Hi,
When I create an admin comment, I get the following error:
undefined method `route_instance_path' for nil:NilClass

I'm using ActiveAdmin 0.3.3 and Rails 3.1.1. The full trace is available here. This may be related to issue #528.

I have the same problem.

I have the same problem.

I have the same problem with Rails 3.0.9 and ActiveAdmin 0.3.3

Just ran into this too.

I'm hitting this same issue with rails 3.1.1 and the latest activeadmin from github.  I threw a debugger into the offending code in lib/active_admin/comments.rb and noticed something a bit strange here (line 46):
resource_config = active_admin_config.namespace.resource_for(comment.resource.class)

Trying to just inspect active_admin_config.namespace just hangs forever.  And obviously the resource_for call just returns nil.  If I get some more time I'll investigate further.

Same issue :-(

Same here.
Ruby 1.9.2, Rails 3.1.1, ActiveAdmin 0.3.3

+1 :: 1.9.2p290, 3.1.1, 0.3.4
NoMethodError in Admin::CommentsController#show
undefined method `route_instance_path' for nil:NilClass

activesupport (3.1.1) lib/active_support/whiny_nil.rb:48:in `method_missing'
activeadmin (0.3.4) lib/active_admin/comments.rb:47:in `block (3 levels) in <top (required)>'
activesupport (3.1.1) lib/active_support/callbacks.rb:457:in `_run__4295348987191613425__process_action__2206591857616638567__callbacks'
activesupport (3.1.1) lib/active_support/callbacks.rb:386:in `_run_process_action_callbacks'
activesupport (3.1.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
actionpack (3.1.1) lib/abstract_controller/callbacks.rb:17:in `process_action'
actionpack (3.1.1) lib/action_controller/metal/rescue.rb:17:in `process_action'
actionpack (3.1.1) lib/action_controller/metal/instrumentation.rb:30:in `block in process_action'
activesupport (3.1.1) lib/active_support/notifications.rb:53:in `block in instrument'
activesupport (3.1.1) lib/active_support/notifications/instrumenter.rb:21:in `instrument'
activesupport (3.1.1) lib/active_support/notifications.rb:53:in `instrument'
actionpack (3.1.1) lib/action_controller/metal/instrumentation.rb:29:in `process_action'
actionpack (3.1.1) lib/action_controller/metal/params_wrapper.rb:201:in `process_action'
activerecord (3.1.1) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
actionpack (3.1.1) lib/abstract_controller/base.rb:121:in `process'
actionpack (3.1.1) lib/abstract_controller/rendering.rb:45:in `process'
actionpack (3.1.1) lib/action_controller/metal.rb:193:in `dispatch'
actionpack (3.1.1) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'
actionpack (3.1.1) lib/action_controller/metal.rb:236:in `block in action'
actionpack (3.1.1) lib/action_dispatch/routing/route_set.rb:65:in `call'
actionpack (3.1.1) lib/action_dispatch/routing/route_set.rb:65:in `dispatch'
actionpack (3.1.1) lib/action_dispatch/routing/route_set.rb:29:in `call'
rack-mount (0.8.3) lib/rack/mount/route_set.rb:152:in `block in call'
rack-mount (0.8.3) lib/rack/mount/code_generation.rb:96:in `block in recognize'
rack-mount (0.8.3) lib/rack/mount/code_generation.rb:103:in `optimized_each'
rack-mount (0.8.3) lib/rack/mount/code_generation.rb:95:in `recognize'
rack-mount (0.8.3) lib/rack/mount/route_set.rb:141:in `call'
actionpack (3.1.1) lib/action_dispatch/routing/route_set.rb:532:in `call'
sass (3.1.10) lib/sass/plugin/rack.rb:54:in `call'
warden (1.1.0) lib/warden/manager.rb:35:in `block in call'
warden (1.1.0) lib/warden/manager.rb:34:in `catch'
warden (1.1.0) lib/warden/manager.rb:34:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'
rack (1.3.5) lib/rack/etag.rb:23:in `call'
rack (1.3.5) lib/rack/conditionalget.rb:25:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/head.rb:14:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/params_parser.rb:21:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/flash.rb:243:in `call'
rack (1.3.5) lib/rack/session/abstract/id.rb:195:in `context'
rack (1.3.5) lib/rack/session/abstract/id.rb:190:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/cookies.rb:331:in `call'
activerecord (3.1.1) lib/active_record/query_cache.rb:62:in `call'
activerecord (3.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:477:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
activesupport (3.1.1) lib/active_support/callbacks.rb:392:in `_run_call_callbacks'
activesupport (3.1.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
actionpack (3.1.1) lib/action_dispatch/middleware/callbacks.rb:28:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/reloader.rb:68:in `call'
rack (1.3.5) lib/rack/sendfile.rb:101:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/remote_ip.rb:48:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/show_exceptions.rb:47:in `call'
railties (3.1.1) lib/rails/rack/logger.rb:13:in `call'
rack (1.3.5) lib/rack/methodoverride.rb:24:in `call'
rack (1.3.5) lib/rack/runtime.rb:17:in `call'
activesupport (3.1.1) lib/active_support/cache/strategy/local_cache.rb:72:in `call'
rack (1.3.5) lib/rack/lock.rb:15:in `call'
actionpack (3.1.1) lib/action_dispatch/middleware/static.rb:53:in `call'
railties (3.1.1) lib/rails/engine.rb:456:in `call'
railties (3.1.1) lib/rails/rack/content_length.rb:16:in `call'
railties (3.1.1) lib/rails/rack/log_tailer.rb:14:in `call'
rack (1.3.5) lib/rack/handler/webrick.rb:59:in `service'

@simonc It might be hacky, but pry it and/or debug print both values and class types?

Ok, this is a quick fix: https://gist.github.com/1369085 of course this isn't the solution but it works. Please don't judge me!

This should be fixed now. I'm going to close it, but please reopen if the issue persists. (Fix is on master)

@gregbell you rock!

Related to #794

I'm still having the same problem on nested resources.

Still having the same problem, using activeadmin (0.3.4) and rails 3.1.3. It shows NoMethodError page but it was able to post the comment if you hit back button on the browser
activesupport (3.1.3) lib/active_support/whiny_nil.rb:48:in method_missing' activeadmin (0.3.4) lib/active_admin/comments.rb:47:in block (3 levels) in <top (required)>'
activesupport (3.1.3) lib/active_support/callbacks.rb:457:in _run__4191934539891253243__process_action__3760801307854670151__callbacks' activesupport (3.1.3) lib/active_support/callbacks.rb:386:in _run_process_action_callbacks'
activesupport (3.1.3) lib/active_support/callbacks.rb:81:in run_callbacks' actionpack (3.1.3) lib/abstract_controller/callbacks.rb:17:in process_action'
actionpack (3.1.3) lib/action_controller/metal/rescue.rb:17:in process_action' actionpack (3.1.3) lib/action_controller/metal/instrumentation.rb:30:in block in process_action'
activesupport (3.1.3) lib/active_support/notifications.rb:53:in block in instrument' activesupport (3.1.3) lib/active_support/notifications/instrumenter.rb:21:in instrument'
activesupport (3.1.3) lib/active_support/notifications.rb:53:in instrument' actionpack (3.1.3) lib/action_controller/metal/instrumentation.rb:29:in process_action'
actionpack (3.1.3) lib/action_controller/metal/params_wrapper.rb:201:in process_action' activerecord (3.1.3) lib/active_record/railties/controller_runtime.rb:18:in process_action'
actionpack (3.1.3) lib/abstract_controller/base.rb:121:in process' actionpack (3.1.3) lib/abstract_controller/rendering.rb:45:in process'
actionpack (3.1.3) lib/action_controller/metal.rb:193:in dispatch' actionpack (3.1.3) lib/action_controller/metal/rack_delegation.rb:14:in dispatch'
actionpack (3.1.3) lib/action_controller/metal.rb:236:in block in action' actionpack (3.1.3) lib/action_dispatch/routing/route_set.rb:65:in call'
actionpack (3.1.3) lib/action_dispatch/routing/route_set.rb:65:in dispatch' actionpack (3.1.3) lib/action_dispatch/routing/route_set.rb:29:in call'
rack-mount (0.8.3) lib/rack/mount/route_set.rb:152:in block in call' rack-mount (0.8.3) lib/rack/mount/code_generation.rb:96:in block in recognize'
rack-mount (0.8.3) lib/rack/mount/code_generation.rb:103:in optimized_each' rack-mount (0.8.3) lib/rack/mount/code_generation.rb:95:in recognize'
rack-mount (0.8.3) lib/rack/mount/route_set.rb:141:in call' actionpack (3.1.3) lib/action_dispatch/routing/route_set.rb:532:in call'
sass (3.1.11) lib/sass/plugin/rack.rb:54:in call' warden (1.1.0) lib/warden/manager.rb:35:in block in call'
warden (1.1.0) lib/warden/manager.rb:34:in catch' warden (1.1.0) lib/warden/manager.rb:34:in call'
actionpack (3.1.3) lib/action_dispatch/middleware/best_standards_support.rb:17:in call' rack (1.3.5) lib/rack/etag.rb:23:in call'
rack (1.3.5) lib/rack/conditionalget.rb:25:in call' actionpack (3.1.3) lib/action_dispatch/middleware/head.rb:14:in call'
actionpack (3.1.3) lib/action_dispatch/middleware/params_parser.rb:21:in call' actionpack (3.1.3) lib/action_dispatch/middleware/flash.rb:247:in call'
rack (1.3.5) lib/rack/session/abstract/id.rb:195:in context' rack (1.3.5) lib/rack/session/abstract/id.rb:190:in call'
actionpack (3.1.3) lib/action_dispatch/middleware/cookies.rb:331:in call' activerecord (3.1.3) lib/active_record/query_cache.rb:64:in call'
activerecord (3.1.3) lib/active_record/connection_adapters/abstract/connection_pool.rb:477:in call' actionpack (3.1.3) lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
activesupport (3.1.3) lib/active_support/callbacks.rb:392:in _run_call_callbacks' activesupport (3.1.3) lib/active_support/callbacks.rb:81:in run_callbacks'
actionpack (3.1.3) lib/action_dispatch/middleware/callbacks.rb:28:in call' actionpack (3.1.3) lib/action_dispatch/middleware/reloader.rb:68:in call'
rack (1.3.5) lib/rack/sendfile.rb:101:in call' actionpack (3.1.3) lib/action_dispatch/middleware/remote_ip.rb:48:in call'
actionpack (3.1.3) lib/action_dispatch/middleware/show_exceptions.rb:47:in call' railties (3.1.3) lib/rails/rack/logger.rb:13:in call'
rack (1.3.5) lib/rack/methodoverride.rb:24:in call' rack (1.3.5) lib/rack/runtime.rb:17:in call'
activesupport (3.1.3) lib/active_support/cache/strategy/local_cache.rb:72:in call' rack (1.3.5) lib/rack/lock.rb:15:in call'
actionpack (3.1.3) lib/action_dispatch/middleware/static.rb:53:in call' railties (3.1.3) lib/rails/engine.rb:456:in call'
rack (1.3.5) lib/rack/content_length.rb:14:in call' railties (3.1.3) lib/rails/rack/log_tailer.rb:14:in call'
rack (1.3.5) lib/rack/handler/webrick.rb:59:in service' /Users/dv/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/webrick/httpserver.rb:111:in service'
/Users/dv/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/webrick/httpserver.rb:70:in run' /Users/dv/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/webrick/server.rb:183:in block in start_thread'

I'm having the same problem as @dvliman

I'm getting this issue on 0.3.4. Perhaps this should be merged in 0.3.x stable branch and made a point release.

In my controller spec I have this error I don t know if it is related ..
Admin::EmployeesController POST create with invalid params re-renders the 'new' template
Failure/Error: post :create, :employee => {}
NoMethodError:
undefined method `employees_url' for #Admin::EmployeesController:0x007f87810c5c00

Solved this by updating activeadmin. I had activeadmin (0.3.4). Updated my gemfile to use gem 'activeadmin', "~> 0.4.1"
When did "gem install activeadmin" by itself, it installs 0.4.1, but when I add just 'activeadmin' to my gemfile it uses 0.3.4.. not sure why I have to specify.


trying to Find First Child element that start with some letters or contains some letters

In FLAUI trying to get a reference to a child element that starts with some letters or contains some for letters. example start with or "DOC" or contains "DOC" what I'm trying to do is that I'm opening some office files like doc,xls, ppt. and want to attach the file as he is open to the screen.
` foreach (var file in listOfFiles)
{
if (file.Name.Contains("DOC") || file.Name.Contains("PPT") || file.Name.Contains("XLS") || file.Name.Contains("TXT"))
{
file.AsButton().Invoke();
            var window = new UIA3Automation();
            desktopWindow = window.GetDesktop();
            desktopWindow = WaitForElement(() => desktopWindow.FindFirstChild(cr => cr.ByName("// Here want to put name that start with ... or contains ...")));
            var app = FlaUI.Core.Application.Attach(desktopWindow.Properties.ProcessId);
            var application = app.GetMainWindow(new UIA3Automation());
            CloseingProcess(application.Name);`

You can use PropertyConditionFlags.MatchSubstring for a substring matching. In the current development version (released to be soon), you can use element.FindFirstChild(cf => cf.ByName("Test", PropertyConditionFlags.MatchSubstring));. which is a shorthand for element.FindFirstChild(new PropertyCondition(automation.PropertyLibrary.Element.Name, "Test", PropertyConditionFlags.MatchSubstring)); which you can use in the currently release version.

what does it mean "automation.PropertyLibrary.Element.Name"?

Or element.FindFirstChild(cf => cf.Name?.StartsWith("bla bla")


How to set Select component loses its focus state after selecting one of its menu item

Expected behavior:
After selecting an item, Menu list will be close immediately and Select component loses its focus state with borderBottom become 1px solid and backgroundColor become white.
Current behavior:
Select behavior after selecting an item
As shown in the image above, the borderBottom is 2px solid and the backgroundColor isn't white which are indicating the Select component is in a focus state.
What should I do to achive the expected behavior?

The current behavior matches native behavior and the behavior in the WAI-ARIA authoring practices.
If you really want to deviate from best practices you could programmatically blur the element in an onClose event. Though we'll likely not document a solution.
Do you have some resources indicating that it should loose focus when an item is selected?

Actually I don't really want to loose the focus
Just want to mimic the behavior as in https://fonts.google.com
I have got the answer though in here: https://stackoverflow.com/a/56244539/9177853
I had already tried this before I got the answer:

you could programmatically blur the element in an onClose event

by using: ref={ref => {this.element = ref}}
then run this.element.blur(); in onClose event, but gave me an error something like

not a function

the same with this: this.element.current.blur();.
it seems simplest if I using blur, but I don't know how to make it work.

it seems simplest if I using blur, but I don't know how to make it work.

This is best answered on stackoverflow. You can use the "material-ui" tag for questions related to this package. Please add a link to the question in this thread so that others may find it as well.


Investigate replacing java.util.logging.Logger with SLF4J

@GCHQDeveloper314 noted that Gaffer mostly uses SLF4J to perform logging; except for the Road Traffic data example which uses java.util.logging.Logger.  Investigate changing this to SLF4J to standardise our code. Check there are no similar anomalies elsewhere in the codebase.

Hi. I have made a pull request regarding this issue here #2663. Thanks


[ALGO] Borůvka's algorithm

Borůvka's algorithm
Borůvka's algorithm, also known as Sollin's algorithm, is a classic approach to find the Minimum Spanning Tree (MST) of a graph. It works well for disconnected graphs by finding a Minimum Spanning Forest. This algorithm is unique in the way it handles edge selections, and it can be highly efficient for sparse graphs.
More details can be found on the wikipedia entry.
Syntax
The algorithm should have the following syntax:
/**
 * @brief Finds the Minimum Spanning Tree (MST) using Borůvka's algorithm.
 *
 * Borůvka's algorithm is efficient for sparse graphs and can also find the
 * Minimum Spanning Forest for disconnected graphs. This algorithm returns
 * a vector containing edge IDs that make up the MST.
 *
 * @tparam GRAPH The graph type.
 * @param graph The input graph.
 *
 * @return A std::vector of edge IDs that make up the MST.
 *         Returns an empty vector if the MST cannot be formed.
 */
template <typename GRAPH>
std::vector<edge_id_t> boruvka_minimum_spanning_tree(
    const GRAPH& graph);

This should live in the graaf::algorithm namespace under include/graaflib/algorithm/minimum_spanning_tree/boruvka.h.
Definition of Done
This issue is done when:

[ ] The algorithm is implemented
[ ] The new function has a javadoc-style comment explaining the interface
[ ] Appropriate tests are added under test/graaflib/algorithm/minimum_spanning_tree/boruvka_test.cpp
[ ] A test coverage of at least 95% is reached
[ ] A documentation entry is added under docs/docs/algorithms under the appropriate category

Just adding a short description and the algorithm syntax here is fine
See the wiki on how to build the documentation locally

[ ] The algorithm is added to the list of algorithms in README.md

Hi, I have some experience with C++ and would like to tak a part in this project! I find this a good first issue since it’s fairly known what needs to be done and since I’m Czech, I have access to many original materials about Borůvka. Therefore, I’d like to try and implement this, if possible. I’m also taking part as a Hacktoberfest attendee

Hi, I have some experience with C++ and would like to tak a part in this project! I find this a good first issue since it’s fairly known what needs to be done and since I’m Czech, I have access to many original materials about Borůvka. Therefore, I’d like to try and implement this, if possible. I’m also taking part as a Hacktoberfest attendee

Hi Harry, welcome to Graaf!
Of course, happy to assign this to you. Looking forward to your contribution :)

Awesome, thank you!

Hi @bobluppes, just wanted to make an update. I've been busy with work and studies so I haven't been able to get to this yet, but I hope to get to it at the end of the upcoming week.
Just wanted to inform that I indeed am thinking about this, just haven't had much time to fully get into it yet. Sorry for that!

Hi @bobluppes, just wanted to make an update. I've been busy with work and studies so I haven't been able to get to this yet, but I hope to get to it at the end of the upcoming week.
Just wanted to inform that I indeed am thinking about this, just haven't had much time to fully get into it yet. Sorry for that!

Hi @HarryHeres, no problem!
Thanks for the update and let me know if you have any questions/issues

@bobluppes I finally got some time to realize this. As I'm working, I had an idea. Wouldn't it be better to differentiate the return values a bit? For example, we could return a NULL value if the provided graph is invalid (e.g. null pointer or 0 vertices or 0 edges). Otherwise, if the MST just was not computable, we could then return an empty vector. I believe this would benefit the user of a bit more knowledge of what happend?
I'm not a C++ dev mainly so I might have a completely wrong view on this.

@bobluppes I finally got some time to realize this. As I'm working, I had an idea. Wouldn't it be better to differentiate the return values a bit? For example, we could return a NULL value if the provided graph is invalid (e.g. null pointer or 0 vertices or 0 edges). Otherwise, if the MST just was not computable, we could then return an empty vector. I believe this would benefit the user of a bit more knowledge of what happend?
Also, under the type GRAPH, what do we expect the user to put in? I suppose something like graph<V,E,graph_type>? Why not expect the exact graph typename, just like in Prim's or Kruskal's implementations?
I'm not a C++ dev mainly so I might have a completely wrong view on this.

Hi @HarryHeres, these are some good remarks! Regarding the GRAPH type, you are correct that changing the interface to something like graph<V, E, graph_type> is more precise. This should avoid the user from passing in any arbitrary type.
Regarding the return value, the reasoning for the proposed interface is that we can either compute a MST for the graph, or there is no MST (for example due to the graph not being spannable). Therefore we either return a non-empty vector or an empty one.
Do you see a different reason as to why we can not compute a MST? If we want to make it more explicit that we did not find a MST we could indeed differentiate this in the return value as you suggested. We could do this by returning an std::optional<std::vector<edge_id_t>>, which is the modern equivalent of a nullptr 😉

Awesome, thank you for your input!
Regarding the return values - std::optional is definitely an interesting choice. You do have a point with the MST calculation being basically either possible or not. For the time being, I will leave it as it was intended, if there's any other state I would run into, we could discuss further if we should introduce a more sophisticated pattern :) Does that sound OK?

Awesome, thank you for your input!
Regarding the return values - std::optional is definitely an interesting choice. You do have a point with the MST calculation being basically either possible or not. For the time being, I will leave it as it was intended, if there's any other state I would run into, we could discuss further if we should introduce a more sophisticated pattern :) Does that sound OK?

Thanks, that sounds fine by me! I think it would make sense to do a follow up and change the interface of the MST functions to return an empty optional if no tree was found. Then the return value semantics are more clear for the user.
But let’s continue like this and discuss further in a follow up 👍🏻

@bobluppes Can we reopen? I was quite busy lately

Unstale


Support for http proxy?

Does restic support http proxy? Searched document and can't find any. It would help the following two situations:

Any backend that uses http/https (such as S3-class backends);
self-update in case the firewall requests so.

I would suggest the following interface of environment variables:

HTTP_PROXY_URL
HTTP_PROXY_USERNAME
HTTP_PROXY_PASSWORD

For example, a squid server listening at <IP_ADDRESS> port 3128 with username "foo" and password "bar" would have environment:
HTTP_PROXY_URL=http://<IP_ADDRESS>:3128
HTTP_PROXY_USERNAME=foo
HTTP_PROXY_PASSWORD=bar

Empty USERNAME would mean no credentials needed.

With the rclone backend, the standard proxy variables (HTTP_PROXY, HTTPS_PROXY) should be respected.

Oh, I completely missed that. So that resolved the first one -- I guess we can always manually overwrite the binary file.
Thank you for the help!


Sources

Analytic sources
Magnetic Dipole.
Electric Dipole.

This issue was moved to simpeg/simpeg#125


Varargs for Seq[ReactElement] children

The way the @react macro works, if you want an apply method that takes varargs children you have two options:

ReactElement* in the first parameter list.
ReactElement* in another parameter list.

Option 1 means no other parameters can have default values. Option 2 means props values cannot be easily manipulated because no copy method is generated.
A 3rd option: convert Seq[ReactElement] into a varargs parameter would break compatibility with existing code.
This change introduces a boolean expandChildrenSeq parameter to the @react annotation. If true a children: Seq[ReactElement] parameter will be converted into a varargs ReactElement* parameter in the generated apply method, enabling both default parameter values for other props parameters and a generated copy method, and preserving compatibility with existing code.

scalafmt seems to have reformatted more than my changes. Not sure why.

Looks great overall! Just one API design possibility to ponder.

for what it's worth, it's possible to support default values with ReactElement* currently with just a little extra typing:

// 4 lines of extra code providing default values, and of course you can make as many `apply` methods as suitable
object Button {
  def apply(onClick: () => Unit, appear: Appear)(children: ReactElement*): ReactElement =
    AtlaskitButton(Some(onClick), appearance = Some(appear.value), `type` = None)(children)
}

@js.native
@JSImport("@atlaskit/button", JSImport.Default)
private object RawAtlaskitButton extends js.Object

@react object AtlaskitButton extends ExternalComponent {

  // as this PR points out, here you can't provide default values and we must construct using object above to get defaults
  case class Props(
                    onClick: Option[() => Unit],
                    appearance: Option[String],
                    `type`: Option[String],
                    children: ReactElement*
                  )

  override val component = RawAtlaskitButton
}

@jedahu I think we can merge this PR and then generalize the support later; could you add a quick note to the changelog and docs explaining this feature?


Rollback on Error doesn't work

Rollback on Error option doesn't work in Postgresql, regardless running a script  or statement (set of statements)
To reproduce the error run the simple script using either "Execute SQL Statement" or "Execute SQL Script"
BEGIN;
SELECT a a;

It raises the error:
SQL Error [42703]: ERROR: column "a" does not exist
Now run any simple query let's say
SELECT 1
It ends up with
SQL Error [25P02]: ERROR: current transaction is aborted, commands ignored until end of transaction block
In case of running script it has additional impact. Running script offers "retry" option. Which obviously is useless because of error above.

I can't reproduce it.
What dbeaver version do you have?
Are you in the smart-commit mode?

Using <IP_ADDRESS>003021717
It behaves the same regardless smart-commit mode.

still cannot reproduce an issue. could you post a video?
thanks in advance

ticket closed. if it is still actual for you - feel free to reopen the ticket


Updated dependencies

updated hashbrown to 0.15.1
cargo test succeeded locally.
see also to hashbrown changelog

Thanks!


D3D12nBodyGravity doesn't work on Xbox one

The sample app is not working on Xbox one. Below is the error message I encountered.
Unhandled exception at 0x00007FFB5B64AFAC (ucrtbased.dll) in D3D12nBodyGravity.exe: An invalid parameter was passed to a function that considers invalid parameters fatal. occurred
However, it works on Windows 10. I thought Xbox one supports DirectX 12 as well.

UWP on Xbox One does support DirectX 12, but only if you enable Game mode. See this blog post.


es fix

Description
This was difficult to reproduce because it only happened if a default version had been set, which isn't required when using the API to publish. Anyway, just needed to follow the same steps that we do for bioworkflows. Added test.
But, indexing locally doesn't fail for me like it does on dev. I'm unclear whether this will resolve that issue, but I wasn't able to reproduce it if anyone has ideas.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-3846
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] Check the Snyk dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future

But, indexing locally doesn't fail for me like it does on dev. I'm unclear whether this will resolve that issue, but I wasn't able to reproduce it if anyone has ideas.

I was able to reproduce it locally by registering a GitHub App tool, setting a default version for the tool, publishing, then indexing


python310Packages.fastapi: 0.85.1 -> 0.85.2

Description of changes
https://github.com/tiangolo/fastapi/releases/tag/0.85.2

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 199126 run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.pytest-ansible
python39Packages.pytest-ansible

54 packages built:

ansible
ansible-later (python310Packages.ansible-later)
ansible-lint (python310Packages.ansible-lint)
ansible_2_13 (python310Packages.ansible-core)
dyndnsc
etebase-server (python310Packages.etebase-server)
home-assistant-component-tests.bmw_connected_drive
kargo
parsedmarc (python310Packages.parsedmarc)
python310Packages.aiofile
python310Packages.aiomisc
python310Packages.ansible
python310Packages.ansible-compat
python310Packages.ansible-kernel
python310Packages.ansible-runner
python310Packages.bimmer-connected
python310Packages.caio
python310Packages.dependency-injector
python310Packages.fastapi
python310Packages.fastapi-mail
python310Packages.geoip2
python310Packages.json-logging
python310Packages.mocket
python310Packages.ormar
python310Packages.slowapi
python310Packages.sopel
python310Packages.strawberry-graphql
ttp (python310Packages.ttp)
python39Packages.aiofile
python39Packages.aiomisc
python39Packages.ansible
python39Packages.ansible-compat
python39Packages.ansible-core
python39Packages.ansible-kernel
python39Packages.ansible-later
python39Packages.ansible-lint
python39Packages.ansible-runner
python39Packages.bimmer-connected
python39Packages.caio
python39Packages.dependency-injector
python39Packages.etebase-server
python39Packages.fastapi
python39Packages.fastapi-mail
python39Packages.geoip2
python39Packages.json-logging
python39Packages.mocket
python39Packages.ormar
python39Packages.parsedmarc
python39Packages.slowapi
python39Packages.sopel
python39Packages.strawberry-graphql
python39Packages.ttp
soco-cli
theharvester


[BUG] Delay safety factor results in 4 sample delay for perfectly aligned captures

If you have a capture that is perfectly aligned with the training .wav, NAM will correctly detect a 0 sample offset but then adds a 4-sample safety factor.
This was clearly done intentionally, but it will result in a model with a 4-sample delay.
Interestingly, my testing shows that the delay might actually help training (maybe because it allows the model to see a few samples "into the future").
The delay should probably either be eliminated, or (if it serves a useful purpose) reported by the model to the plugin so that it can be compensated for.

The purpose of the delay is that it can be a little tricky to tell exactly what the delay is when the reamp is a little noisy. Even if the amp is "reacting", it can be a few samples before the response gets over the noise floor. So the "4 samples" is a bit of a kludge to just make sure that it's not being asked to "predict the future".
I've sort of kept an eye on it, but I'm not 100% confident it's exactly the right value or might be better-tuned. But a little bit of delay is much better than being even a single sample on the wrong side (the error skyrockets).
But if you've got the bandwidth and interest to dig deeper into it and think you can tune it to work better, I'm happy to hear what you find 🙂

Forgot to mention: the colab/GUI trainers provide the ability to explicitly provide the delay if you know it exactly (as you mentioned you "know" that your files are perfectly aligned--so you could provide a delay of zero in that case). (See: https://github.com/sdatkinson/neural-amp-modeler/blob/3cf65f56ddd1762e026d53e0adc54753ddc4dae0/nam/train/colab.py#L72, default is None which tells it to try and figure it out for itself.)
The subtlety is that it's 4 samples ahead of where the signal crossed the threshold, but the amp could have (and probably is) reacting before that point. The "4 samples" is a crude guess, but the fundamental thing is that there's uncertainty because the data are noisy. So I'm not sure it'd be correct for it to report to the plugin that it's 4 samples behind--it's probably less than that by a little bit, give or take.


iOS bug - Counter number incorrect on app launch

When the application is launched on iOS the counter number is at zero even if the actual count is higher than that, example: locally stored count is 50, on app launch however it shows as 0, user taps on the plus button - the count now updates to 51

Fixed in latest release


File/folder picker does not handle init folder and root folder access denied properly on Android 10 and lower

The file/folder picker on Android is a bit broken.
Everything is tested with osu!~lazer~ on real unrooted devices with no SD card plugged in, internal storage only.
On open, picker will drop user into /sdcard as init directory, which is denied on Android 10 and lower, even with Storage permission allowed. This works fine on Android 11 though, no problem is encountered.
The current code on directory change will try to traverse up the tree of the directory until it reaches a readable directory.
On Android 10 and lower, it will deny access to /sdcard, so the picker goes up one directory, which is root. Root is (partially) readable, we can see some content in here, but we can't go anywhere listed, access denied. So, after the picker load, user will be dropped into root folder and got stuck here, while the path shown is still kept at /sdcard (this is another bug, but this can be fixed quite easily).
On Android 11 (12 not tested because I don't have money) I can get into /sdcard and everything works fine. But if I went to root or "Computer" then same thing happens, I got stuck there, and /sdcard is not inside root somehow, so I'm forced to close the picker then open it again to get back to /sdcard. In this case a back button mechanism should kind of "fix" this. Somehow I can access this folder without even giving the Storage permission. Weird.

known issue.
https://github.com/ppy/osu/pull/15248 has a flow for requesting permissions properly, but is broken because of android losing egl context on pause. i have a path forward how to resolve that but it may take a while more until that's ready.

Does the solution address user getting into inaccessible path though, because going up the tree until a readable folder is found is not a good idea, especially on *nix and Android.
Just stay in the current path and don't change path at all is better imo.

that assumes that the original directory is still accessible which is not necessarily true either. example:
dir1
└─ dir 2
   └─ dir 3

now assume you're in dir 3, then delete dir 2, but then try to navigate to dir 2 after that deletion. neither the target directory, or the original directory, exist anymore. this would previously lead to crashes.
just needs a better sane fallback directory for android, is all.

Yeah, we need a better Computer directory for Android.
The Computer directory is generated by this code:
https://github.com/ppy/osu-framework/blob/c4a6dc5bc3e3b8c7121b334408eae6d9b48ab5bd/osu.Framework/Graphics/UserInterface/DirectorySelector.cs#L130-L138
This generates a bunch of nonsensical "drives" on android (one of which is /storage/emulated/0/data so it's actually possible to return to a sane folder).
We should move this drive-creation process to a platform specific thing in GameHost, probably make it an IEnumerable<DirectoryInfo>, similar to UserStoragePaths.
Needs a bit more consideration for display names (eg. /storage/emulated/0 → Internal storage).
Or maybe we want Computer to map to /storage/emulated/0?
(Troughout this post, when I say /storage/emulated/0 I mean the user ID-adjusted /storage/emulated/<n> folder.

Made a quick and dirty PoC for a custom Computer directory, and it works as expected.
if (newDirectory == null)
{
    string[] customDirs =
    {
        "/sdcard",
        "/storage/emulated/0",
    };

    var dirs = customDirs.Select(s => new DirectoryInfo(s));

    foreach (var dir in dirs)
        directoryFlow.Add(CreateDirectoryItem(dir, dir.FullName));

    return;
}

So, should "Computer" represent the emulated user storage (/storage/emulated/) or list all the actual storage devices connected (/storage/sdcard)?
Not sure how to actual solve this though. Making "Computer" one of the above will prevent rooted Android user from accessing these path, but will bring better experience for unrooted user. By binding "Computer" root folder won't even be shown to the user.
And about deleted dir handling for bdach's example, we can

On error opening a directory, check if current directory is still accessible. If it's still ok, stay there and flash error as usual.
If current dir is not accessible, try to go to a fallback or default directory that we're pretty sure is accessible.
If still inaccessible, try to traverse the tree like what we're currently doing.
Worst case, if all else fail, show error then close picker or similar panic behavior.

So, should "Computer" represent the emulated user storage (/storage/emulated/) or list all the actual storage devices connected (/storage/sdcard)?

Since Android has gotten really restrictive with storage in 12, we definitely want Computer (should probably be renamed, keeping localisation support in mind) to link to or be /storage/emulated/<user id>.

Making "Computer" one of the above will prevent rooted Android user from accessing these path, but will bring better experience for unrooted user. By binding "Computer" root folder won't even be shown to the user.

Computer is not the root folder, it's the null folder, which, in our code, is the "parent" for /. So if you want to access / on a rooted device, you could open /storage/emulated/0 and then tap on the / breadcrumb. If we can read that folder, we'll stay on it and show the folder/file list, if not, we'll just fall back to it's "parent", Computer.
We don't want to include / in Computer, as that will confuse normal/unrooted people.
And for your latter points, since Computer is the "true parent" of all directories, we'll always have a sane default to fall back to.

So "Computer" is only a logical place we created to hold the directory content?
So, from what I understand, when user click on "Computer", it will redirect to /storage/emulated/<user-id> and change breadcrumb to
Computer > / > storage > emulated > id
And breadcrumb with only Computer is, as a result, not possible on Android, right?
Alright that makes sense.

Or maybe we want Computer to map to /storage/emulated/0?

When I say this, I mean Computer just listing every directory in /storage/emulated/0. I can see this being confusing, so we probably won't do that.

Yeah, just use the "Computer" as a redirect is best IMO.
Actually, I'm thinking about setting "Computer" to be just root on *nix OSes, since what they're currently doing is list all mounted devices (this means all the virtual mounts like root(?), sys, proc,...) and is kinda useless. It's better to just make it root and make it /storage/emulated/0 on Android only.


.vscode typescript settings not respected in .vue files

I have the following settings added to my workspace .vscode/settings.json
    "typescript.tsdk": "node_modules/typescript/lib",
    "typescript.preferences.importModuleSpecifier": "non-relative",
    "typescript.preferences.importModuleSpecifierEnding": "minimal",
    "typescript.preferences.quoteStyle": "single",
    "typescript.preferences.autoImportFileExcludePatterns": [
        "@vue/reactivity",
        "@vue/runtime-dom",
        "./dist",
        "./src/index.ts"
    ],

And in a .ts file I see a nice short list of suggestions

But in a .vue file the list is much different

Not only is autoImportFileExcludePatterns not respected it seems the other settings are not respected either. For example, changing the value of quoteStyle has no effect in a .vue file and it does in a .ts file.

Currently you must enable hybridMode to get them work

I added "vue.server.hybridMode": true, to my settings but no change. Is there something else I need to do?

Just had a try, even tho in code action select drop down it shows double quote, the result still in single quote.

@RayGuo-ergou are the other settings working for you? Are you using hybrid mode?

Tried another setting
"typescript.preferences.importModuleSpecifierEnding": "js",

I think it always use default value

Hey there, as there have been many fixes in the last 2.x versions: Please let us know if you're still encountering this issue. Otherwise kindly close this one, thanks!


Promote to conda organization?

Now that conda.org soft-launched... do we want to initiate the process to migrate to the conda org?

I think that's a good idea. Want to call for a vote here?

@conda-incubator/steering
This vote falls under the "Incorporate a Software Project into the main conda Organization" policy of the conda governance policy, please vote and/or comment on this proposal at your earliest convenience.
It needs 60% of the Steering Council to vote yes to pass.
To vote, please leave yes, no or abstain as comments below.
If you have questions concerning the proposal, you may also leave a comment or code review.
This vote will end on 2023-05-16, End of Day, Anywhere on Earth (AoE).

Aye

yes

yes! 🚀

Yes

yes

Yes

yes

Yes

Voting Results
This was a standard, non-timed-out vote.
Among Steering Council members there are 5 "yes", 0 "no", and no abstentions.
This vote has NOT reached quorum (5 is lower than 60% of 14).
Hence, it has also NOT passed. I'll bring this topic up in the community sync meeting to solicit feedback and decide what to do next.

D'oh, I missed that GitHub auto-hides similar comments and the number of votes was actually 8. Update forthcoming..

I've updated the voting results accordingly now, we still missed quorum very close.

@travishathaway @jaimergp I'm interested in restarting this vote, to move this into the main conda org, we missed it barely at the time and it's been serving us well since then. What do you think?

Yes, let's bring it up on Wednesday.

@conda-incubator/steering-council
Since we haven't achieved quorum last year, haven't gotten specific feedback what we should do differently and continue to successfully use conda.org as an outreach platform, I'd like to call for another vote on this.
This vote falls under the Incorporate a Software Project into the main conda Organization policy of the conda governance policy, please vote and/or comment on this proposal at your earliest convenience.
It needs 60% of the Steering Council to vote yes to pass.
To vote, please leave yes, no or abstain below.
If you have questions concerning the proposal, you may also leave a comment or code review.
This vote will end on 2024-08-13, End of Day, Anywhere on Earth (AoE). This is an extended voting period due to summer holiday time in the Northern Hemisphere.
Please use the following form to vote:
@xhochy (Uwe Korn)

[ ]  yes
[ ]  no
[ ]  abstain

@cj-wright (Christopher J. 'CJ' Wright)

[ ]  yes
[ ]  no
[ ]  abstain

@mariusvniekerk (Marius van Niekerk)

[ ]  yes
[ ]  no
[ ]  abstain

@goanpeca (Gonzalo Peña-Castellanos)

[ ]  yes
[ ]  no
[ ]  abstain

@chenghlee (Cheng H. Lee)

[ ]  yes
[ ]  no
[ ]  abstain

@ocefpaf (Filipe Fernandes)

[ ]  yes
[ ]  no
[ ]  abstain

@marcelotrevisani (Marcelo Duarte Trevisani)

[ ]  yes
[ ]  no
[ ]  abstain

@msarahan (Michael Sarahan)

[ ]  yes
[ ]  no
[ ]  abstain

@mbargull (Marcel Bargull)

[ ]  yes
[ ]  no
[ ]  abstain

@jakirkham (John Kirkham)

[ ]  yes
[ ]  no
[ ]  abstain

@jezdez (Jannis Leidel)

[ ]  yes
[ ]  no
[ ]  abstain

@wolfv (Wolf Vollprecht)

[ ]  yes
[ ]  no
[ ]  abstain

@jaimergp (Jaime Rodríguez-Guerra)

[ ]  yes
[ ]  no
[ ]  abstain

@kkraus14 (Keith Kraus)

[ ]  yes
[ ]  no
[ ]  abstain

@baszalmstra (Bas Zalmstra)

[ ]  yes
[ ]  no
[ ]  abstain

It has come to my attention based on the vote comment log provided by GitHub that when using the checkbox interface above, sometimes it may not correctly register the vote (e.g. when on a smartphone). Please make sure your vote has been recorded accordingly, thank you!

yes!

It has come to my attention based on the vote comment log provided by GitHub that when using the checkbox interface above, sometimes it may not correctly register the vote (e.g. when on a smartphone). Please make sure your vote has been recorded accordingly, thank you!

Yes I have been bitten by this a couple times now 😅

@conda-incubator/steering-council This is a kind reminder to vote for this proposal, to graduate conda-dot-org to the main conda organization (also make sure your vote was actually recorded, see above comment). Thank you!

yes

@mbargull, please use the check box next to your name above!  We're using a new format for voting.

Voting Results
This was a non-timed-out vote with an extended voting period.
Among Steering Council members there are 13 "yes", 0 "no", and no abstentions.
Among Emeritus Steering Council members there are 0 "yes", 0 "no", and no abstentions.
This vote has reached quorum (13 is at least 60% of 15 active steering council members).
It has also passed since it recorded 13 "yes" votes and 0 "no" votes giving 13/13 which is greater than 60% of 13.

Congratulations @conda-incubator/conda-dot-org!
Next steps

[ ] review incubation team setup and decide how to set up new conda-dot-org team in conda organzation (see below for more info)
[ ] recrate the conda-dot-org team in the conda organization and invite the same people (please check your emails for the invite from GitHub!) (see below)
[ ] transfer the repo, to https://github.com/conda/conda-dot-org (change repo name?)
[ ] fix the team permissions to admin permissions for the repo

Incubator team
The team setup for the conda-dot-org website was quite elaborate, there are three incubating subteams:
Content

@travishathaway
@tnabtaf
@jaimergp
@goanpeca
@beeankha
@kathatherine
@ang852

Design

@jezdez
@travishathaway
@tnabtaf
@jaimergp
@kenodegard
@eakbulut
@kathatherine
@ang852

Implementation

@jezdez
@travishathaway
@tnabtaf
@jaimergp
@goanpeca
@barabo
@kenodegard
@beeankha
@JeremiahSifuentes

New, graduation team
As you can see, there is a lot of duplication, and some members have moved on in their career, since conda.org was incubated.
To have a consistent, active website team, I suggest the following team for the conda organization:

[ ] @jezdez
[ ] @travishathaway
[ ] @jaimergp
[ ] @goanpeca
[ ] @beeankha
[ ] @kathatherine
[ ] @kenodegard
[ ] @eakbulut
[ ] @JeremiahSifuentes

Could the people not mentioned, please let me know if they want to participate? I think it's totally fine to also bring this up at a later time, in case of slow responses.
@dashagurova Do you also want to participate?

Oh, I completely misunderstood that I had to click that checkbox. I would be happy to continue to be on the team, @jezdez.

Oh, I completely misunderstood that I had to click that checkbox. I would be happy to continue to be on the team, @jezdez.

Added you!

@beeankha Just added you to the team as well

Thank you, @jezdez !

Closing since this is mostly done.


Installation via Package Control on OSX does not change the editor

I installed the package via package control and restarted my editor, but there were no changes. I'm running OSX, the only other package currently installed is Materialize.
The package shows up in preferences/browse packages and can be removed and reinstalled without any changes being seen in sublime.

This issue can be closed, solution can be found @ https://github.com/equinusocio/material-theme-appbar/issues/25

Cool. And you can also close issues that you made by pressing the Close Issue button to the left of the Comment button :)


feat: add callback to i2c constructor

This closes Issues #76.

Looks good, an other option would be to align iotjs i2c.open API :
https://github.com/jerryscript-project/iotjs/blob/master/docs/api/IoT.js-API-I2C.md

May I suggest to consider to forward to abandonware fork
Relate-to: https://github.com/kelly/node-i2c/issues/97


Anerdw: Blacklist (?-i:^Prunkellator 28371$)

Anerdw requests the blacklist of the username (?-i:^Prunkellator 28371$). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?-i:^Prunkellator 28371$) has been seen in 7 true positives, 0 false positives, and 0 NAAs.

Approved by Fastnlight in Charcoal HQ


Replace using private -routing service with public router

I'm using ember-source 3.20 and started noticing an issue where the service:-routing. generateURL returns a URL with query params appended if the route where you are loading the page on has query params already in the URL, even if the usage of href-to in the template does not specify any query params. This is weird behavior and is causing bugs in our application that has a lot of filtering. The flow now for a user:

filters by something
reloads the page with the query param in the URL
the side nav link has hardcoded the query param in the href

The service:router. urlFor seems to be the better way to go and fixes the issue with the non-wanted query params in the href.

I created a working public gist that we are going to use locally for the time being to fix the issue.
https://gist.github.com/jordpo/94af6f864ffad1928513f123070d039f
Minus the TS, want me to open a PR?

How does <LinkTo> behave in your scenario? href-to attempts to behave as closely as possible to LinkTo

<LinkTo> has the same unexpected behavior.
I created a repo with the comparison between <LinkTo>, href-to, and my alternative helper href-to-fix. If you load the app at http://localhost:4200/?q=helloworld you can see the href for the first two be /?q=helloworld and for the helper with my fix, the href is /.
Since I provided no query params to either the component or the helpers, I would expect no query params to be present in the resulting href attributes. That seems like a reasonable expectation and like I said causes bugs in production code where a route is loaded with unexpected query params.
Here is the link for my repo that you can pull down and see https://github.com/jordpo/link-to-qp-sitickiness.

I believe that this is the expected behaviour of <LinkTo>, and by extension, {{href-to}}:
https://guides.emberjs.com/release/routing/query-params/#toc_sticky-query-param-values

Thanks. I understand the stickiness about query params and just assumed that had to do with the controller being a singleton. It's interesting that the link href is also updated though not sure I see the value of that since the controller preserves the query param values when exiting the route unless you explicitly reset them.
How would you clear a query param? When we exit the route we set the query params back to the defaults but the link href has the original query param that the app loaded with in it. So any subsequent visit to that page via the original link will contain that original query param even when we don't want it to.

I'm not sure, it's been a little while since I've worked with query params. Perhaps ask in Ember Discord?

How would you clear a query param?

The docs seem to cover that:

So I pushed an update to my repo highlighting an important difference in behavior between <LinkTo> and href-to. The former does recompute when the query params are changed in the resetController hook while href-to doesn't recompute. Do we need to add a recompute to the helper based on query params changing like that?

Also confirmed that the href on <LinkTo> changes any time the query param changes on the route. So it does feel like a recompute issue for the helper.

Thanks, it seems like it. Perhaps you might add a failing test as a first step?

Yeah will do. Probably not tonight but will try to open a PR in the next day or so.

I updated the issue subject to be clearer.

nice one, thanks

@GavinJoyce opened a PR with the test and the fix. I don't like using observer but not sure we have any other option here.

@GavinJoyce would the next step do a major version release since the update has breaking changes?

Yes, I'll do that soon.

Awesome - thanks!


is any possibility to traind a diffrent datafolder like snake with pretraind model

Kindly explain further the details you are asking for.

See #8


rough start

@JustinGrilli  I find the Tableau Utilities DAG a little hard to read because of it's length.  What do you think about pushing functionality to an optional subpackage now that we know how to configure that.
Then we could have airflow pip install tableau_utilities[airflow] and the DAG would be very simple.
If that sounds ok to you I can take the lead on the refactor.  Not sure if I have time immediately this week but let me know if this looks good to as an approach.

I don't want to be responsible for other's Airflow DAGs haha.
If we make the Airflow sample an actual part of the package, then we'd be responsible for ensuring the Airflow code remains functional and can be used more generally.
I don't mind occasionally updating the sample as we continue to iterate on our own DAG, but there may be things we do to our DAG that will not work for others.
That being said, if you want to make the sample code more modular, go for it!

@JustinGrilli  I hear you and your concerns make sense.  I know I've mentioned this before so thanks for humoring me in bringing it up again.
I'll figure something out over time.  We could move the samples to multiple files but that's it's own headache for adding the sample here.
We could also move some functionality to the main package like "diff config and a column" in a generalized sense. That would also slim things down in the DAG and splits the difference with your concerns.
I'll close this out and think about it over time and submit PRs later.
Thanks!


Embedding Pruning + Bottleneck Aligning killed

Hi,  I try to run training with default setup and one batch of SA-1B dataset which I split 50/50. The process is killed after Pruning Start:
$ CUDA_VISIBLE_DEVICES=0 python prune_distill_step1.py  --traindata_path /home/wnnuser/SlimSAM/data/sa_1b_000000 --valdata_path /home/wnnuser/SlimSAM/data/sa_1b_000000_test --epochs 2

CUDA AVAILABLE: True
CUDA visible devices: 1
CUDA Device Name: Tesla T4
/home/wnnuser/SlimSAM/segment_anything_kd/build_sam.py:115: FutureWarning: You are using torch.load with weights_only=False (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for weights_only will be flipped to True. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via torch.serialization.add_safe_globals. We recommend you start setting weights_only=True for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
state_dict = torch.load(f)
===========================Parameter Settings===========================
Pruning Ratio: 0.5
VIT num_heads: 12
norm_type: mean
imptype: Disturb
global: False
learning rate: 0.0001
a_weight: 0.5
round_to 12
TRAIN_SIZE 10000 VAL_SIZE 50 GRAD_SIZE 1000 Epochs 2
===========================Pruning Start===========================
/home/wnnuser/SlimSAM/torch_pruning/dependency.py:639: UserWarning: Unwrapped parameters detected: ['neck.1.weight', 'neck.3.weight', 'pos_embed', 'neck.1.bias', 'neck.3.bias'].
Torch-Pruning will prune the last non-singleton dimension of a parameter. If you wish to customize this behavior, please provide an unwrapped_parameters argument.
warnings.warn(warning_str)
Killed
Regarding the warningweights_only I've tried True and False and in both cases the same issue.

Hi @ksulima ,
I haven't encountered this problem either, but I think it might help if you try to roll back the pytorch version.

@ksulima ,
I implemented Slimsam using python=3.8, pytorch=1.7, and torchvision=0.8. The GPU is a single 24gb Titan RTX GPU. I hope this can help you.


Remove frames

Just this for now. I am thinking of implementing other features and will look at the rendering problems later.

Sorry I missed it. I've got a lot on my plate at the moment and won't have much free time until about the end of April.

No problem


Cant load top down space adventure godot project?

When i download the source files for the space adventure it throws errors and doesnt include the top down space adventure files...

Please, submit screenshots of the errors so we have something to work with


DE10 hardware params

Hello, I'm trying to replicates the results found in demonstration section the PipeCNN paper for the DE-1 soc board and was wondering if it would be possible to get the hardware parameter settings used to create the bit-streams used to produce the results found in the paper.

Hi, the code has been modified for many times since the PipeCNN paper, so it is better to conduct another round of design space exploration to find out the best paras for the current version of code. We have not tested the latest code for DE-1 yet.

Perfect. Thanks!


feat: Update PyO3 to 0.23.3

Update dependencies of PyO3 in https://github.com/keep-starknet-strange/garaga/blob/main/tools/garaga_rs/Cargo.toml to version 0.23.3 and update code so that cargo build outputs no deprecation warnings.
See https://pyo3.rs/v0.23.0/migration.html

i want to solve this issue, can i take this up?

yes


Update MaxMind DB

🐛 Summary
We came across a warning/error about an IP address not being found in the geolocation database. When faced with the output below (please see ‘any helpful log…’ section), further analysis showed, for a specific asset, the registered location was US-based, but the geolocation was coming back from a restricted country. Finally, MaxMind confirmed the address was, indeed, US-based. We believe the MaxMind database needs to be updated for cyhy-ip verification for add commands.
To reproduce
We were unable to reproduce this behavior with another example for this bug report. However, overall it appears the MaxMind database needs to be updated. (Please reach out to VS Operators for specific, historical example.)
Expected behavior
We would not have expected this error to present itself on a non-restricted IP address, such as the one we came across. (Please reach out to VS Operators for specific, historical example.)
Any helpful log output or screenshots
(No screenshots, just terminal output below.)
The error seen when adding an IP to stakeholder's scope:
cyhy-ip -s cyhy-ops-production-write add ENTITY XXX.XXX.XXX.0/24
IP XXX.XXX.XXX.0 not found in geolocation database
float() argument must be a string or a number (None, None)

@rpearson42 Due to the way this information is currently sourced you will need an updated cisagov/cyhy-core Docker image. This is handled at the team level and is not something we (the dev team) manage directly.


Added keywords

I'v noticed a keywords missing from package.json and added some.

Thank you, landed in 64a2353
We have already keywords in the shadow repos, but missed them in angular-translate actually. 🚶


Fix the exception handling issue in Email Sink publish method

Purpose

The purpose of this PR is to fix the issue in email sink publish method exception handling.
According to the current implementation if there is an exception which is not an instance of  'MailConnectException' or 'ConnectException' then it creates new RuntimeException for each case and bubble up to the caller methods. But there is a problem when the caller methods do not handle the Runtime Exception properly.
This was noticed with the incident:https://github.com/wso2-extensions/siddhi-io-email/issues/43 and there the HA member change handler activation logic loop breaks due to bubbled up Runtime Exception from the Email sink publish method. By looking at the Runtime Exception trace log, the issue occured due to the SMTP server failed to send that message into the define email addresses.
To avoid this kind of issue, rather creating new Runtime Exception bubble up, the particular event log and drop in the Email sink publisher method.

Goals

Fix the exception handling issue in Email Sink publish method

Approach

Rather creating new Runtime Exception and bubble up from publish method, the particular payload log and drop in the Email sink publisher method

User stories

N/A

Release note

N/A

Documentation

N/A

Training

N/A

Certification

N/A

Marketing

N/A

Automation tests

Unit tests

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

N/A

Test environment

N/A

Learning

N/A

Close the PR as fixes need to be added into carbon-analytics repo as fixes for: https://github.com/wso2/carbon-analytics/issues/1510


Issue with shared_preferences package

Hi
Recently I added this package to our project in order to use the geo-fencing feature, but it seems that its dependencies use shared_preferences_ios which is incompatible with the latest shared_preferences package as "shared_preferences: ^2.0.18"
it causes an error as follows:
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: MissingPluginException(No implementation found for method getAll on channel plugins.flutter.io/shared_preferences)
Could you please tell me what's going on?

Same issue! Why this is happen?

"I had the same error and I solved it by adding shared_preferences_ios: ^2.0.0 to my pubspec.yaml file."
"shared_preferences_ios" is a Flutter package that provides a simple way to store and retrieve data in the persistent memory of the device. The version "^2.0.0" of this package is compatible with iOS 14 and later versions.
To add this dependency to your pubspec.yaml file, you should follow these steps:
1-Open your Flutter project's pubspec.yaml file.
2-Look for the "dependencies" section in the file.
3-Add the dependency "shared_preferences_ios: ^2.0.0" at the end of the dependencies list.
4-Save the pubspec.yaml file.


[CI] Determine which gpu tests, if any, can be parallelized, and strategy to do so

#8576 is enabling pytest-xdist for CPU-targeted TVM tests. This is a good first step to parallelizing the TVM test suite, but the real benefits will come if we can find a way to do this for tests that target GPUs. It's not clear if this can be done.
I think:

we can probably safely run smaller GPU tests in parallel
we don't have a good list of which tests those are so we don't know how much benefit this will provide
we should probably write more smaller tests, though
we should probably build tvm.testing decorators to formally identify these in code

Known unknowns that could break this approach:

Are there ordering problems with some tests?
I think we generate cached testdata for re-use between tests, and that needs to be broken out into pytest fixtures
Other driver-level issues that could break this.

Feel free to generate actionable child issues as a result of this. If things are not actionable and require deliberation, it would be great to post up to discuss.tvm.ai instead--we like to keep issues in GH to only those with clear steps to resolve.
@mikepapadim to take a look at this
cc @Mousius @denise-k @driazati @gigiblender @jroesch @leandron

Closed as the CI performance push was largely completd, would need re-timing for current bottlenecks.


nz-modal  when nzOnOk is typeof OnClickCallback, click ok button trigger nzAfterClose twice

Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-modal-bug-report000?file=src%2Fapp%2Fapp.component.ts
Steps to reproduce

open console
click show modal button
click 确定 button.

handleOk(): boolean {
  return true;
}

handleCancel(): boolean {
  return undefined;
}
afterClose($event: any){
  console.log('closed for: '   $event);
}

What is expected?
console one line:
closed for: true
What is actually happening?
console two lines:
closed for: true
closed for: undefined

Environment
Info

ng-zorro-antd
7.3.3

Browser
Chrome 72.0.3626.121（正式版本） （64 位

BTW, when opening the page,  afterClose is triggered once immediately.

fixed via #4702


ot-node v6 installation script is failing

Issue description
After rebuilding my server from scratch , the installation script is failing on npm installation phase. "Executing npm install: FAILED"
Expected behavior
installation should succeed
Actual behavior
Updating .bashrc file with OriginTrail node aliases: SUCCESS
Updating Ubuntu package repository: SUCCESS
Updating Ubuntu to latest version (may take a few minutes): SUCCESS
Installing default-jre: SUCCESS
Please select the database you would like to use: [1]GraphDB [2]Blazegraph [E]xit: 2
Blazegraph selected. Proceeding with installation.
Downloading Blazegraph: SUCCESS
Copying blazegraph service file: SUCCESS
Enable Blazegraph service on boot: SUCCESS
Starting Blazegraph: SUCCESS
Confirming Blazegraph has started: SUCCESS
Downloading Node.js v16: SUCCESS
Setting up Node.js v16: SUCCESS
Updating the Ubuntu repo: SUCCESS
Installing node.js and npm: SUCCESS
Installing tcllib and mysql-server: SUCCESS
Creating a local operational database: SUCCESS
Commenting out max_binlog_size: SUCCESS
Disabling binary logs: SUCCESS
Restarting mysql: SUCCESS
Executing npm install: FAILED
Steps to reproduce the problem

Fresh server running  Ubuntu 20.04
apt install git -y && cd /root && git clone https://github.com/OriginTrail/ot-node && cd ot-node && git checkout v6/release/testnet
3./root/ot-node/installer/installer.sh

Specifications

Node version:  v6.0.0-beta.1.34
Platform: 4 GB Memory / 80 GB Disk / AMS3 - Ubuntu 20.04 (LTS) x64
Node wallet: 0xa3Df2CB888Ee424991D56A0f65d6ce662673b9c3
Node libp2p identity:

Contact details

Email<EMAIL_ADDRESS>
Error logs
Executing npm install: FAILED
There was an error executing npm install.
npm WARN deprecated<EMAIL_ADDRESS>please use version 2.x npm WARN deprecated<EMAIL_ADDRESS>This package is broken                                                               and no longer maintained. 'mkdirp' itself supports promises now, please switch to that. npm WARN deprecated<EMAIL_ADDRESS>request ha                                                              s been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated<EMAIL_ADDRESS>this library is no longe                                                              r supported npm WARN deprecated<EMAIL_ADDRESS>This module has been superseded by the multiformats module npm WARN deprecated multico<EMAIL_ADDRESS>This module has been superseded by the multiformats module npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to version 7 or hi                                                              gher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-ran                                                              dom for details. npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to version 7 or higher. Older versions may use Math.random() in certain                                                               circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated<EMAIL_ADDRESS>                                                            .0: This repository is now being maintained by ChainSafe, and can be found at https://github.com/ChainSafe/js-libp2p-noise under @chain                                                              safe/libp2p-noise npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to version 7 or higher. Older versions may use Math.random() in certai                                                              n circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated<EMAIL_ADDRESS>Ple                                                              ase upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. Se                                                              e https://v8.dev/blog/math-random for details. npm WARN deprecated<EMAIL_ADDRESS>This module has been superseded by the multiformats                                                               module npm WARN deprecated<EMAIL_ADDRESS>This module has been superseded by the multiformats module npm WARN deprecated<EMAIL_ADDRESS>                                                            : This module has been superseded by the multiformats module npm notice npm notice New minor version of npm available! 8.5.0 -> 8.6.0 n                                                              pm notice Changelog: https://github.com/npm/cli/releases/tag/v8.6.0 npm notice Run npm install -g<EMAIL_ADDRESS>to update! npm notice n                                                              pm ERR! code 1 npm ERR! path /root/ot-node/node_modules/ganache/node_modules/@trufflesuite/bigint-buffer npm ERR! command failed npm ER                                                              R! command sh -c node-gyp rebuild npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp in                                                              fo using<EMAIL_ADDRESS>| linux | x64 npm ERR! gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3" npm ERR! gyp                                                               http GET https://nodejs.org/download/release/v16.14.2/node-v16.14.2-headers.tar.gz npm ERR! gyp http 200 https://nodejs.org/download/re                                                              lease/v16.14.2/node-v16.14.2-headers.tar.gz npm ERR! gyp http GET https://nodejs.org/download/release/v16.14.2/SHASUMS256.txt npm ERR!                                                               gyp http 200 https://nodejs.org/download/release/v16.14.2/SHASUMS256.txt npm ERR! gyp info spawn /usr/bin/python3 npm ERR! gyp info spa                                                              wn args [ npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py', npm ERR! gyp info spawn args                                                               'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'make', npm ERR! gyp info spawn args '-I', npm ERR! gyp                                                               info spawn args<EMAIL_ADDRESS>npm ERR! gyp info spaw                                                              n args '-I', npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi', npm ERR! gyp info spawn args '-                                                              I', npm ERR! gyp info spawn args '/root/.cache/node-gyp/16.14.2/include/node/common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shar                                                              ed_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=/root/.cache/node-gyp/1                                                              6.14.2', npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp', npm ERR! gyp info spawn args '-                                                              Dnode_lib_file=/root/.cache/node-gyp/16.14.2/<(target_arch)/node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=/root/ot-node/no                                                              de_modules/ganache/node_modules/@trufflesuite/bigint-buffer', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn                                                               args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info sp                                                              awn args 'build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp ERR! build error npm ERR! g                                                              yp ERR! stack Error: not found: make npm ERR! gyp ERR! stack at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js                                                              :10:17) npm ERR! gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:18 npm ERR! gyp ERR! stack at new Promise (                                                              ) npm ERR! gyp ERR! stack at step (/usr/lib/node_modules/npm/node_modules/which/which.js:54:21) npm ERR! gyp ERR! stack at /                                                              usr/lib/node_modules/npm/node_modules/which/which.js:71:22 npm ERR! gyp ERR! stack at new Promise () npm ERR! gyp ERR! stack                                                               at subStep (/usr/lib/node_modules/npm/node_modules/which/which.js:69:33) npm ERR! gyp ERR! stack at /usr/lib/node_modules/npm/node_mod                                                              ules/which/which.js:80:22 npm ERR! gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5 npm ERR! gyp ERR! stack                                                               at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5 npm ERR! gyp ERR! System Linux 5.4.0-104-generic npm ERR! gyp ERR! command                                                               "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" npm ERR! gyp ERR! cwd /root/ot-node/node_m                                                              odules/ganache/node_modules/@trufflesuite/bigint-buffer npm ERR! gyp ERR! node -v v16.14.2 npm ERR! gyp ERR! node-gyp -v v8.4.1 npm ERR                                                              ! gyp ERR! not ok npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2022-04-09T13_30_42_729Z-debug-0.log
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to<EMAIL_ADDRESS>

A temporary fix (proposed by Max111 on telegram) is to remove the ganache dependency from the package.json file AFTER cloning the directory but BEFORE running the installer.
Run the following and delete the line containing the ganache dependency (line 46 -I believe):
cd /root/ot-node && nano package.json
OR run the following:
sed '/ganache/d' /root/ot-node/package.json

This was fixed with #1920. Thanks for raising the issue.


fix: restore command prompt when blurred then focused

Problem
When a user types a quick action command starting with / or a context command starting with @ and then loses focus, the command context is lost. When the user refocuses on the input field and continues typing, the quick pick overlay does not reappear, causing the command to never be picked up.
Solution

[x] Added a focus event listener to the PromptTextInput class to check the input value when the input field regains focus.
[x] If the input value starts with / or @, the quick pick overlay is reopened, and the commands are filtered accordingly.
[x] Ensured that the quick pick overlay behaves as expected when the user resumes typing after losing focus.
[x] If a user previous typed half a command /show which filtered out 4 commands when they re-focus on the input field, only restore those 4 commands

Preview

To Do

[!TIP]
Tomorrow Day Problems

chat-prompt-input.ts could probably use some redundancy grouping for similar functionality
handleInputKeydown has a complexity score of 54

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

There are two issues related with the @ command picker in the PR:
1st issue
When user starts with @ to pick a context (currently this is the general expected behavior btw.) and blurs the input area and comes back in. There is an additional @ char.
Gif: (loading)

2nd issue
When there is another context picker trigger (second @) it is becomes not possible to write text again.
Gif: (loading)

Note about how they are and should work:
Quick action commands can be opened only if there is no text written. Even after you type sth. you cannot go back to the beginning of the line and open it. Reason behind that is we cannot be sure that if the command accepts additional text or not. And there can be only one command selected.
However, context selection (@) is different, it is just a predefined text selection which always starts with @. User can select them anywhere inside the text and pick as much as they want.

However, context selection (@) is different, it is just a predefined text selection which always starts with @. User can select them anywhere inside the text and pick as much as they want.

Ah, GTK! TY

However, context selection (@) is different, it is just a predefined text selection which always starts with @. User can select them anywhere inside the text and pick as much as they want.

Ah, GTK! TY

Checks, works as expected 👍🏻

Any hesitation on merge?


Using json::decode::(json_str) adds 60 seconds to release build time

I was trying to figure out why my --release build (incremental not fresh) took so long and i narrowed it down to usage of json::decode::<MessageEvent>(json_str) in on_receive
Is this expected? Is there anything I can do to avoid it? My alternative is manually parsing the messages i'm interested in. I guess it's just a rustc being slow at some stuff thing.

I certainly do not expect that!
However, I'm no rust expert, so it's possible the way it's written is hard
on the compiler (?)
I'm buried in classwork right now but if you could post some more details
about your setup (rust version etc) I'll try to profile it myself when I
get time again.
cc @mthjones
On Nov 21, 2015 13:03, "David Hewson"<EMAIL_ADDRESS>wrote:

I was trying to figure out why my --release build took so long and i
narrowed it down to usage of json::decode::(json_str) in
on_receive
Is this expected? Is there anything I can do to avoid it? My alternative
is manually parsing the messages i'm interested in. I guess it's just a
rustc being slow at some stuff thing.
—
Reply to this email directly or view it on GitHub
https://github.com/BenTheElder/slack-rs/issues/26.

I made a gist based on the example code
https://gist.github.com/dten/c1d9c6503d6aa1973b91
a clean release build takes 300 seconds (line in)
comment out the line and build release again is 5 seconds
uncomment the line and release build is 66 seconds
this is on my laptop and using rustc 1.6.0-nightly (b7845f93b 2015-11-15)

Thanks.
I haven't been using nightly recently, perhaps it's a bug with the nightly?
I'll try to figure out what's going on when I get some free time,
eventually we'll switch to serde for parsing once custom derive is
available on stable.
On Sat, Nov 21, 2015 at 6:11 PM, David Hewson<EMAIL_ADDRESS>wrote:

I made a gist based on the example code
https://gist.github.com/dten/c1d9c6503d6aa1973b91
a clean release build takes 300 seconds (line in)
comment out the line and build release again is 5 seconds
uncomment the line and release build is 66 seconds
this is on my laptop and using rustc 1.6.0-nightly (b7845f93b 2015-11-15)
—
Reply to this email directly or view it on GitHub
https://github.com/BenTheElder/slack-rs/issues/26#issuecomment-158689709
.

just tried the stable. similar results; 5 seconds to 53 seconds

attached two traces from using rustc -Z time-passes
not really sure what they mean but these two parts used to be ~1 second and are now the below values
time: 23.207; rss: 263MB	llvm module passes
time: 26.173; rss: 261MB	codegen passes
slow.txt
fast.txt

That compile time...woof. I think it may be due to the number of variants that exist for the message event. I don't have my primary dev machine available right now, but I'll try and take a look at this.

Getting to this today, sorry I've been pretty busy with end-of-the-semester work.
Looking at your traces first, no significant difference until the last three steps:
fast:
time: 2.562; rss: 155MB	LLVM passes
  time: 0.914; rss: 155MB	running linker
time: 0.916; rss: 155MB	linking

slow:
time: 49.809; rss: 180MB	LLVM passes
  time: 1.087; rss: 180MB	running linker
time: 1.089; rss: 180MB	linking

Looking at the -Z time-llvm-passes info, the Machine Common Subexpression Elimination and Function Integration/Inlining passes jump out as taking over 8 seconds each on the slow version!
Yikes! looks like we're stressing out the LLVM passes pretty bad.
Like @mthjones said, it's probably the number of variants in the return type stressing out the codegen pretty badly for some reason. I'm not really sure what the best route to solve that is. We could break up the type into more event subtypes but the enum would still have as many total variants in order to handle each type.... I'm not convinced that would actually help.

In the next release, you won't need to call this yourself, while I'd like to try to fix this, I think the best thing to do will be to eventually move to serde for json parsing.
Until then incremental builds should improve a lot as the parsing will be done inside the run code in the slack crate (and not in your code, unless you really wanted to for some reason).


Bugfix/266 toggle instance in pyblish pype crashes

Issue:
setData method called in model cause TypeError: invalid result from InstanceItem.setData()
Solution:
Toggle setData method happens on item not on model.
Resolves: https://github.com/pypeclub/pype/issues/266

This should be fixed in pyblish-lite too for client without 2.10 release.

Not sure whether its related to this, but the callback instanceToggled does not seem to work.

That is not related, but good to know. Just look how it's implemented in pyblish-qml and it should be easy to implement here if necessary in next PR. But I don't see use case for that to be honest?

But I don't see use case for that to be honest?

For example in Harmony you can persist the publish state to the scene so anyone picking up the scene afterwards will have the same enabled/disabled instances.
In Harmony this is done thought enabling/disabling nodes in the view.

In Harmony this is done thought enabling/disabling nodes in the view.

Create new issue, it should be easy to do.


Dev to main

Many improvements, video frame buffering, more random configs, better settings handling, etc.

For Peren's video build.


Update adding-view.md

remove space from bullet list

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnetcore/tutorials/first-mvc-app/adding-view.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Disable-JenkinsJob and Enable-JenkinsJob

The main purpose of the PR is for new Disable-JenkinsJob and Enable-JenkinsJob functions. As part of this, I refactored the logic to resolve a command from a folder (optional), job name (optional), and command name into its own Resolve-JenkinsCommandUri function, which reduces a lot of code duplication.

This change is

Codecov Report

Merging #88 into dev will increase coverage by 1.4%.
The diff coverage is 26.82%.

@@            Coverage Diff            @@
##              dev      #88     +/-   ##
=========================================
+ Coverage   28.46%   29.87%   +1.4%
=========================================
  Files          22       25      +3
  Lines         411      405      -6
=========================================
+ Hits          117      121      +4
+ Misses        294      284     -10

Impacted Files
Coverage Δ

src/lib/Rename-JenkinsJob.ps1
0% <0%> (ø)
:arrow_up:

src/lib/Remove-JenkinsJob.ps1
0% <0%> (ø)
:arrow_up:

src/lib/Disable-JenkinsJob.ps1
0% <0%> (ø)

src/lib/Invoke-JenkinsJob.ps1
0% <0%> (ø)
:arrow_up:

src/lib/Enable-JenkinsJob.ps1
0% <0%> (ø)

src/lib/Set-JenkinsJob.ps1
0% <0%> (ø)
:arrow_up:

src/lib/New-JenkinsFolder.ps1
0% <0%> (ø)
:arrow_up:

src/lib/New-JenkinsJob.ps1
0% <0%> (ø)
:arrow_up:

src/lib/Resolve-JenkinsCommandUri.ps1
100% <100%> (ø)

src/lib/Get-JenkinsJob.ps1
100% <100%> (ø)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dbc6e95...464f746. Read the comment docs.

@PlagueHO No. Just a strange habit I have. I've removed them.

@PlagueHO Also, I don't think my new test script runs as part of your build, since it's in its own file.

@splatteredbits - your tests did run just fine :grin: : https://ci.appveyor.com/project/IAG-NZ/jenkins/builds/20180416#L166

@PlagueHO Changes made. Ready for another review.

@splatteredbits - this is now up on the PSGallery. Cheers for your help!


Fix the location of the realm in the JWT Filter reference

@nbkrause documentation changes need to be carefully coordinated with what's happening on the shared/story-doc-improvement branch at this point.

@khussey Thanks for the review. I made the change you requested. I left the original location changed as well since I believe I remember you saying those old pages will still be linked for some time. Please let me know if you need me to change that as well.


Adds code of conduct

Fixes: #10
Adds CODE_OF_CONDUCT.md to the project

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@thinkingserious I have signed the CLA. Please review

Hello @geekyd,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

@thinkingserious
I have filled the form. Thanks for the update.


Resolving private repositories

Description

I've been using buckaroo quite some time with my private repos and I'm constantly running into the same issue. I'm using buckaroo in "SSH" mode exclusively as it easier with private repos.
When using buckaroo resolve on a buckaroo project with private-repo dependencies, buckaroo results in an unresolvable error the first time, the second time it manages to resolve it and to create a lock file.
Expected Behavior

I would expect buckaroo to work the same with private repos as with public repos.
Actual Behavior

The first resolve:
info Resolve start: 2020-07-13T19:35:07
info Resolving dependencies using quick strategy...
[git] info Fetching refs from git@github.com:roey-e/six-p.git
[git] success Fetched 24 refs in 3.334
[git] info Shallow cloning git@github.com:roey-e/six-p.git
[solver] warning Unresolvable: github.com/roey-e/six-p@branch=master
info Resolve end: 2020-07-13T19:35:16
info Resolve time: 00:00:09.0553388
error The package github.com/roey-e/six-p at branch=master is unresolvable.

The second resolve:
info Resolve start: 2020-07-13T19:39:33
info Resolving dependencies using quick strategy...
[git] info Fetching refs from git@github.com:roey-e/six-p.git
[git] success Fetched 24 refs in 2.661
[solver] info Trying github.com/roey-e/six-p at branch=master
info Resolve end: 2020-07-13T19:39:36
info Resolve time: 00:00:03.4153366
success A solution to the constraints was found.
success The lock-file was updated.

Reading the log, I understand it has something to do with cloning the repo the first time. Deleting '~/.buckaroo' (which holds the cache if I am not mistaken) after the first resolve keeps the error.
Possible Fix

I tried to find what causes it. I debugged buckaroo and found out it might be calling sourceExplorer.FetchManifest from Solver.fs:186 which ultimately calls fetchFile of GitHubApi.fs:6. fetching a file from a private repo using 'https://raw.githubusercontent.com/' is not possible (unless using a token of course).
I looked up for a way to fetch a single file using SSH, but I did not succeed (git archive --remote doesn't work with GitHub). So maybe the fix is not trivial, I'm not familiar with buckaroo's code enough to come up with a solution easily.
Steps to Reproduce

Have a buckaroo project with at least one private repo as a dependency.
Clone your buckaroo project.
Remove the buckaroo.lock.toml file.
buckaroo resolve (or buckaroo resolve --upgrade if the lock file is not up to date) -> error :(
buckaroo resolve -> buckaroo.lock.toml generated :)

I used my roey-e/protobuf (branch: python-protobuf-buck) which uses my roey-e/six repo as a dependency which I privatized (roey-e/six-p).
Your Environment

Version used: The latest buckaroo (3.0.1)
Operating System and Architecture: It happens on Ubuntu 18.04 and on Windows 10

Thanks @roey-e  for investing time into investigating this issue. Your analysis was quite on point and was very helpful. I made a new release and you can find more context in the associated PR.
Please let me know if the issue still persists in the new release


Breaktime

corrected bad values in config.py

I wonder if the implementation should have a random element to it. For instance, the config could have something like an ideal_runtime_hours and ideal_break_minutes. The reason, I'm thinking, is for anti-behavioral pattern detection.
With those set, the bot may run for the specified time the first iteration, but then the second iteration could vary within reasonable parameters.
e.g.,
ideal_runtime_hours=4
ideal_break_minutes=15
Iteration 1:
* runtime: 4 hours
* break time: 15m

Iteration 2:
* runtime: 3.5 hours
* break time: 30m

Iteration n:
* runtime: 1.5 hours
* break time: 10m

Another aspect, in a similar vein, is detecting if it's "overrunning" (i.e., no sane human would run for 4 hours, sleep 30m, run 4 hours, sleep 30m, run 4 hours, sleep 30m, etc.)
This isn't to say that these two implementations are mutually exclusive.


Update cache-control for newly created blobs

Updated the existing ones using azure powershell.
Update the script here to make sure we update the cache-control for newly created blobs.
Fixed issue: https://github.com/Azure/azure-sdk-tools/issues/976

The following pipelines have been queued for testing: java - templatejs - templatenet - templatepython - template Sign off on the approval gate to test the release stage of each pipeline.


Investigate why pod log streaming works inconsistently in CI environment

vmlifecycle tests that require virt-handler pod log streaming do not behave consistently in our JENKINs environment.
We need to track down why log streaming behaves inconsistently and improve the situation so we can re-enable these tests in JENKINs.

I'm beginning to think this issue may have something to do with the Regex parsing of the log line

I think this is fixed.
Please reopen if this is still an issue.