Php config imports

Referenced issue : #1539
Based on #1537
Several proposals for this importing feature.
Use variadic
use Behat\Config\Config;

$config = new Config();
$config->import('first_file.php', 'second_file.php', ...);

If we have too much files to imports, using multiple lines is still possible.
use Behat\Config\Config;

$config = new Config();
$config->import(
    'first_file.php',
    'second_file.php',
    ...,
    ...,
    'another_file.php',
);

Use array
use Behat\Config\Config;

$config = new Config();
$config->import(['first_file.php', 'second_file.php', ...]);

Use simple way
use Behat\Config\Config;

$config = new Config();
$config
    ->import('first_file.php')
    ->import('second_file.php')
    // ...
;

One of the benefits of this way is that we can add optional arguments later.
Moreover, we need to think about an implementation for importing using a pattern.
Using pattern
use Behat\Config\Config;

$config = new Config();
$config->import('config/../..php');

Symfony way
Dependency Injection
https://github.com/symfony/symfony/blob/7.3/src/Symfony/Component/DependencyInjection/Loader/Configurator/ContainerConfigurator.php#L64
Routing
The routing way is also interesting
https://github.com/symfony/routing/blob/7.1/Loader/Configurator/RoutingConfigurator.php#L37

I think my preference would be:

For explicit files, a variadic e.g. import(string ...$imports)
For pattern matching, a separate importMatching(string $pattern) - if you want multiple patterns, you call it multiple times. Possibly with something like importMatching(string $pattern, bool $throwIfNoMatches = true) to give people control / safety over what happens if nothing matches the pattern.

I think my preference would be:
* For explicit files, a variadic e.g. `import(string ...$imports)`

* For pattern matching, a separate `importMatching(string $pattern)` - if you want multiple patterns, you call it multiple times. Possibly with something like `importMatching(string $pattern, bool $throwIfNoMatches = true)` to give people control / safety over what happens if nothing matches the pattern.

I've removed the two methods way from the proposal and added a simple one based on Symfony routing configurator.

@acoulton Is the current state ok for you.
I've simplified with a single method with string or array of string.


feat: Google sheet file picker on blank page

Description
This PR adds:

Google sheet file picker needs to be shown on blank page
Refactored file picker code into a separate component called GoogleSheetFilePicker

How to test:
For selected sheets scope, once authorisation is complete, user would be taken to file picker page, with blank background as per designs

Add a TL;DR when description is extra long (helps content team)

Fixes #21065
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


schema_generated.h checked into source instead of generated

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
master
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
The schema_generated.h file is checked into the source tree, as opposed to being generated by flatc. This in turn induces a dependency on a very specific version of flatc:
static_assert(FLATBUFFERS_VERSION_MAJOR == 23 &&
              FLATBUFFERS_VERSION_MINOR == 5 &&
              FLATBUFFERS_VERSION_REVISION == 26,
             "Non-compatible flatbuffers version included");

There are other files that are generated by flatc in the BUILD. What is special about this file that requires it to be checked into the source tree? There are some references to schema_generated.h.oss that suggest that there's some Google specific stuff that's being omitted, but that's just a guess.
Standalone code to reproduce the issue
N/A

Relevant log output
No response

Hi, @aws-taylor! Could you please follow the steps below ;

Remove the checked-in schema_generated.h file from the source tree
Regenerate the schema_generated.h file using flatc
Add the generated schema_generated.h file to the project's build configuration.
Update the file to check the changes
Please let us know which TF version you are using?

Thank you!

Hi @sushreebarsa,
I think I was unclear - the issue isn't that the file is out of date - the issue is that the file shouldn't be checked into the source tree it all - it should be generated as part of the build. I can take the steps you mention, but that just pushes the problem down the road.

Please let us know which TF version you are using?
This issue exists on the top of tree

-Taylor

Hi @aws-taylor, thanks for raising this issue.
I was able to regenerate the file after deleting it but I feel like it was likely checked-in for a reason.
@qukhan, Can you please take a look? Perhaps you have better insight here.

also running into this at alpine linux via chromium. schema_generated.h is actually just one of them
$ rg -l '"Non-compatible flatbuffers version included"'
tensorflow/lite/acceleration/configuration/configuration_generated.h
tensorflow/lite/experimental/acceleration/configuration/configuration_generated.h
tensorflow/lite/delegates/gpu/common/gpu_model_generated.h
tensorflow/lite/delegates/gpu/common/task/serialization_base_generated.h
tensorflow/lite/delegates/xnnpack/weight_cache_schema_generated.h
tensorflow/lite/delegates/gpu/cl/serialization_generated.h
tensorflow/lite/delegates/gpu/cl/compiled_program_cache_generated.h
tensorflow/compiler/mlir/lite/schema/schema_generated.h
tensorflow/lite/schema/conversion_metadata_generated.h
tensorflow/lite/schema/schema_generated.h


Stop relying on pgrep -q

Many distributions don't support pgrep -q, which causes build_local.sh
to behave incorrectly. This patch redirects to /dev/null instead.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

/retest

/test e2e-aws


Fix backtick issue for new terminal keybinding

The markdown code inline code block was broken due to the use of a double backtick. Adding a backwards slash in front of the backtick solves that.

Sorry for the many commits. My first change didn't change it as expected. It took a while before I found the correct combination of backticks to display the keybinding within the code block correctly.

Hey @PaulvdDool, appreciate you taking the time to figure out how to get this binding to render properly - unfortunately, we build these keybinding files with a script - looks like it needs to be updated.

Hey @PaulvdDool, appreciate you pointing this out how to get it to render correctly - I went ahead and updated the script here:
https://github.com/zed-industries/docs/pull/39


Question: Send parameter with intercept

Node version: v12.16.2
Sails version (sails): 1.2.3

throw { badCombo: 'Invalid email or username.' }

.intercept('incorrect', 'badCombo')

Hi,
How can I send the parameter with intercept, as with throw?

https://stackoverflow.com/questions/61671595/send-parameter-with-intercept-in-sailsjs


Fix ContentObserver notification tests

The ContentObserver callback mechanism is managed in another thread so in some cases the test failed due to lack of synchronization.
I propose to use CountDownLatch and wait until 1 second to be compatible with more devices (like mine).

@glureau Thanks for the contribution. For the DBFlow 3.0 release we hope to improve many aspects of the library. It will be a huge release and hopefully will be out by mid October. If this PR is not addressed in 3.0, it will be a priority after release. More on that here. Please let me know if you have any questions :)


fix(119): swap flutter_icons with fluttericon

Icon designs remain same except fill/outline effects.
Fixes #119
Screenshots of the changes -
From -> To
 to

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.053%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3910

Relevant Lines:
5280

💛  - Coveralls


Upgrade cwltool

Feature Request
Desired behaviour
During the 1.2 Dockstore lifecycle, cwltool has significantly changed. Pick a relatively recent and stable version of cwltool to upgrade and test with for 1.3

This is a bit of an oddball ticket, assigning this to Gary to keep track of running all the verified workflows and the ga4gh-dream workflows using the new cwltool

This was done for 1.3.0 release


installation and setup instruction

Hi, i am interested in testing this project out. are there instructions somewhere?
does this just work or it has dependencies?
it will be nice and helpful if you can write-up a short installation and setup instructions.

@CNajm can you send me a pull request with a fix of new xpaths?

@CNajm Issues addressed.


[The One Ring 2nd Edition] Version 2.00 Release

Changes / Comments
The current The One Ring 2nd Edition sheet is loosely based on the 1st Edition of the game, and needs to be updated for a better experience now that the game is officially released.
This sheet supports the new game mechanics in the released game, and provides a graphical face-lift for the ported sheet.
This sheet adds parsed rolls to the sheet, with logic for favoured and ill-favoured rolls through queries; it support for all types of bonuses and penalties through modification queries; it takes weary, miserable and ill-favoured conditions into account; then calculates all the outcomes and presents the output in a brand new roll template.
The existing fields have not been touched, so anyone running the previous tor2e sheet can be upgraded without data loss. The same encumbrance calculation is used, while sheet workers for Weary and Miserable conditions have been added.
The sheet was pre-announced on the forums here: https://app.roll20.net/forum/post/10558357/.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[x] Does this add functional enhancements (new features or extending existing features) ?
[x] Does this add or change functional aesthetics (such as layout or color scheme) ?
[x] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

Hi everybody,
unfortunately this is an another 2e charactersheet for The One Ring 2e (see the existing/rejected PR https://github.com/Roll20/roll20-character-sheets/pull/9970). It seems that we have not properly coordinated our development (if I understand this correctly I've coordinated with the existing maintainers of the Roll20 1e and 2e charactersheets via Discord and @dwarfwing has announced this development on the Roll20 forums). I've tried to contact https://app.roll20.net/users/8097845/richard-w#, who announced this release without my knowledge (see https://app.roll20.net/forum/post/10558357/the-one-ring-2nd-edition-sheet-version-2-dot-00-pre-announcement)  before @dwarfwing raised this PR).
Additionally I've just noticed that this PR will overwrite the existing sheet of @Aragent without coordination (as I understand).
My existing branch of the TOR 2e charactersheet is here (which is also ready for release and contains an additional  charactersheet for adversaries and some other features):
https://github.com/bhuesemann/roll20-character-sheets/tree/tor2e_01-01-00
I would like to clarify how we can join forces and prevent splitting the development and player community with two alternative TOR 2e charactersheets. Thus I've already contacted https://app.roll20.net/users/8097845/richard-w# today before this PR was created.
@Roll20 @nmbradley Please give us some time to clarify things before merging this PR. I see a good chance to merge all  branches into one.
@dwarfwing and https://app.roll20.net/users/8097845/richard-w# : Please get in contact or answer my message via Roll20 or the existing community on Discord: https://discord.com/channels/348254014598545408/348255648615628801
Cheers,
Bodo

Hi,
I was busy getting this PR done so I missed the reach out from @bhuesemann yesterday. I have responded to the message and we will continue discussion outside of this PR.
I agree we need to discuss how to proceed before going ahead with this PR, I am fine with either leaving it as is for now or just republish at a later stage. I myself don't like keeping PRs open for too long, so happy to go with the latter option.
Thanks @nmbradley for your continued support!


Unable to reference external typings

I'm trying to use the "externals" flag to get the d.ts bundle to include typings for external libraries that exist in my node_modules folder, however for the life of my I cannot get this to work properly. I continually get : TypeError: Cannot read property 'file' of undefined. I've looked through other issues here and it seems some involve the author manually hacking the project, and others just seem to not have been resolved. Anyone else having trouble with this? I'd appreciate any help.

i have this problem aswell !

I think it is only for external files (outside directory) but will not resolve module X to node_modules\X.
So this will not work:

import * as wrap from "word-wrap"
But this did work for me:
import * as wrap from "../node_modules/word-wrap"

This project just need a little push :)


Always flush in WebSocketsTransport

Is this fixing an existing broken test? If not can you add a test for the scenario it is fixing.

Is this fixing an existing broken test? If not can you add a test for the scenario it is fixing.

No tests, it's a performance thing.


Support for custom Input markup

Hi!
I was thinking of developing some sort of option that allows the component to render a custom markup for the input. For example, I need to render a Material Design input that also needs a label element, something like:

     <input placeholder="Placeholder" id="first_name" type="text" class="validate">
     First Name

How do you think we could approach this?
Thanks!

You can style the element as you like. The label doesn’t have to be included in the component, you can render the label next to the component and use the id prop on the Component.
Example JSX setup:

     <Geosuggest placeholder="Placeholder" id="first_name" className="validate" />
     First Name

Right. Didn't think about that. Thx!

:)


make heatmap compatible with plt.subplots

Currently, there is no way to use graspy.plot.heatmap within plt.subplots

closed via #189


Add recommended shareable config

Only 4 of the rules are recomended: https://github.com/YozhikM/stylelint-a11y#rules

Oops, I just blindly copied the "recommended config". I'll update the PR accordingly.

Done. I updated that part of the documentation to reflect the shareable config, I hope that's ok.

LGTM.


add RelatedResourceFilter to security-group

Would like to have the ability to compare the tags and NetworkLocation of a security group, sg-1, with the tags and NetworkLocation of a security group, sg-2, where sg-2 is listed as an inbound rule to sg-1.

you'll have to elaborate on this a bit more clearly, what's a nested security group.

By nested, I meant security-groups that are listed as inbound rules of another security-group.

thanks for the clarification, sounds good. note that security group references can cross accounts along vpc peering at which point there is no easily viable mechanism for verifying the referenced attributes.


IO-279: Added ignoreNew parameter on instantiating Tailer.

Encountered this bug today when we try to tail a file that is being modified even though there is no new content being added.

@garydgregory could You take a look at this PR?
We need this for openHAB - https://github.com/openhab/openhab2-addons/issues/5442

Hi @Misiu,
Thanks for the ping.
I am -1 to this PR because:

It breaks binary compatibility. You can tell since this build is broken. See the red "All checks have failed" note on this page and the associated Travis builds.
It does not contain a unit test to test the new feature.

Gary

No activity since 2017, closing.

No activity since 2017, closing.


Faster/tighter BlockedBloom64

This version is more stable when the number of keys is high.
Before:
adds    cycles: 76.0/key, instructions: (35.0/key,  0.5/cycle) cache misses: 4.45/key branch misses: 0.00/key
0.00%  cycles: 86.5/key, instructions: (49.0/key,  0.6/cycle) cache misses: 5.35/key branch misses:  0.0/key
0.25%  cycles: 86.5/key, instructions: (49.0/key,  0.6/cycle) cache misses: 5.36/key branch misses:  0.0/key
0.50%  cycles: 86.5/key, instructions: (49.0/key,  0.6/cycle) cache misses: 5.35/key branch misses:  0.0/key
0.75%  cycles: 86.5/key, instructions: (49.0/key,  0.6/cycle) cache misses: 5.35/key branch misses:  0.0/key
1.00%  cycles: 86.5/key, instructions: (49.0/key,  0.6/cycle) cache misses: 5.35/key branch misses:  0.0/key
                  BlockedBloom64       22.45   25.54   25.54   25.54   25.54   25.54  1.0453%      10.24       6.58   55.6%   100.0

After...
                                                find    find    find    find    find                        optimal  wasted million
                                      ns/add      0%     25%     50%     75%    100%        ε  bits/item  bits/item   space    keys

adds    cycles: 76.2/key, instructions: (35.0/key,  0.5/cycle) cache misses: 4.46/key branch misses: 0.00/key
0.00%  cycles: 87.7/key, instructions: (50.0/key,  0.6/cycle) cache misses: 5.36/key branch misses:  0.0/key
0.25%  cycles: 87.7/key, instructions: (50.0/key,  0.6/cycle) cache misses: 5.36/key branch misses:  0.0/key
0.50%  cycles: 87.7/key, instructions: (50.0/key,  0.6/cycle) cache misses: 5.36/key branch misses:  0.0/key
0.75%  cycles: 87.7/key, instructions: (50.0/key,  0.6/cycle) cache misses: 5.36/key branch misses:  0.0/key
1.00%  cycles: 87.6/key, instructions: (50.0/key,  0.6/cycle) cache misses: 5.36/key branch misses:  0.0/key
                  BlockedBloom64       22.49   25.87   25.88   25.87   25.88   25.87  0.9338%      10.24       6.74   51.9%   100.0

I have added a port of block bloom to aarch64. It is not very fast, but it works.

Added naive block Bloom (unprincipled).


Nimble 9.0 has breaking changes

There is a release candidate for version 9 of Nimble available that has support for XCode 12 (more info here). However, updating to Nimble 9 breaks this Pod.
I have attached a screenshot that indicates specifically which file/part of the code is causing the compilation issues, it is just a type mismatch between TimeInterval and DispatchTimeInterval in Expectation+Leaks.swift.

Hello guys, is this fix will be merged soon?

Just merged it!
On Tue, Nov 10, 2020 at 10:07 AM Fotis Kalaitzidis<EMAIL_ADDRESS>wrote:

Hello guys, is this fix will be merged soon?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/leandromperez/specleaks/issues/19#issuecomment-724690057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZTBDFOYRQYZIWBJAAHH3SPE3ITANCNFSM4RXGAEPQ
.


PI-8463 - always use default history in nav drawer + no arbitrary del…

…ay for click handler (use Ripple.onComplete instead).

Coverage decreased (-0.1%) to 32.826% when pulling 5893cade376deb8857fe9e7b624122a3b362d5a4 on PI-8463-view-titles into c778b4551f3ca46f3d984f5a95c47889bb04e61c on master.


Auto-generate Java equals() methods for records

At the moment, Djinni does not auto-generate Java's equals method for records. So records fall back on the identity equals implementation of Object when not overridden manually.
I think it would be a good default to say that two records are equals if and only if all their members are equal. Could this be auto generated from Djinni? Records with +j can still override the implementation from RecordnameBase.

Djinni can already generate equality and ordering comparisons, but you need to request that on a per-record basis.  Check out "Deriving Methods" in the README.md file.

Thanks for the hint. Now I get the error from Djinni

Cannot safely implement Eq on a record that may be extended

I guess this is because I use records with custom constructors. Can't we implement Eq in the auto-generated base class? This leaves room for customizations when a record is extended.

That feature decision was from before my time as a Djinni maintainer, but I believe the logic was that if a record is extended, then the base class equality comparison can't be guaranteed to be accurate for any new members which are implemented in the subclass.  In C++ the comparisons are not virtual methods, so there could be potential incorrect results if a subclass object is compared via a reference/pointer to a base class.  Djinni is taking the guaranteed safe option here.  If you're extending the record, there's no reason you can't implement your own safe equality comparisons in the base class (albeit at the cost of some annoyingly manual effort).


Update+ improvements  Usagesummary.ps1

Added 3 missing metrics.
Changed the logic for retrieving usage:
. Created an array with the list of all subscriptions
. Changed the get-azsSubscriberUsage to include the subscriberID.
This way we will have better performance, avoiding gateway timeout errors while executing the sql query.

any feedback on this?

any update on this PR?

@CarlosGon could you pls address the comments? Can you pls make the PR to the az branch as well?

@bganapa
Comments resolved. Code formatted with VScode


Diff takes more than 4 minutes to complete

#2968 is very nice :-)
But it still performs many GetCommit calls, these are unnecessarily slow and in fact ay be cached so are probably unnecessary.
GetCommit is slow
This is intentional: this call is batched.  This batching makes sense when performing other operations (see @tzahij's blog post) because they involve concurrency at load.  For instance, when a large-scale Spark job starts reading from lakeFS, it performs multiple concurrent reads, and each fetches the same HEAD commit.  Batching means responses arrive later than they might.
But batching does not make sense in FindMergeBase: this function sequentially fetches commits, so if we batch the commits we slow each iteration down.  One speedup might be to pass this function an unbatched CommitGetter.
But we can do even better...
GetCommit should be cached
There can be many thousands of commits.  However, a quick inspection of graveler.go suggests that the relation graveler_commits is never updated other than by FillGenerations / LoadCommits.  Commits are immutable.
So we can cache commits.  Every call to GetCommit should go through a cache.  The cache can (easily) have size 10_000, and will hold all relevant commits in memory.  FillGenerations can simply invalidate the cache :-) , it is anyway only used by restore-refs.  And, if we use our cache.Cache then we don't even need to batch: concurrent GetCommit operations only call out once to the database, and the result is cached for later operations.
WDYT?  Can we open a new issue "Cache commits"?

@arielshaqed @talSofer I don't want to lose the above comment. Should we create a separate issue for commit caching?

sure, it's on my list. thanks for confirming


vim_performance_operating_range: can't dup NilClass

For some VMs, when you do
vm.cpu_usagemhz_rate_average_high_over_time_period, you get..
TypeError: can't dup NilClass
	from /home/himdel/manageiq/app/models/vim_performance_operating_range.rb:31:in `dup'
	from /home/himdel/manageiq/app/models/vim_performance_operating_range.rb:31:in `values_with_std_dev'
	from /home/himdel/manageiq/app/models/vim_performance_operating_range.rb:19:in `values_to_metrics'
	from /home/himdel/manageiq/app/models/metric/ci_mixin/long_term_averages.rb:29:in `averages_over_time_period'
	from /home/himdel/manageiq/app/models/metric/ci_mixin/long_term_averages.rb:3:in `block (2 levels) in <module:LongTermAverages>'

(because values is nil).

(for me, an affected vm is "windows 2012" with id=10000000000715)
I can provide more info if you tell me what :)

@agrare feel free to punt over to @jameswnl if this is purely metrics related ... I saw vim in the logs, but realized right after I assigned it that the vim_performance stuff is shared by everyone.

I think this is mine...I think this is due to the changes in vpors in #12972 .

@himdel Somehow you have a nil values column in vim_performance_operating_ranges.  Maybe this can happen on an upgrade, but I don't think this can happen in regular workflow.  What is the rest of the stack trace (I'm assuming it's during C&U capture)

@Fryguy not during capture, but when trying to display textual summary screen for the VM...
[----] F, [2017-03-06T17:54:10.513610 #392:2abddc59f848] FATAL -- : Error caught: [ActionView::Template::Error] can't dup NilClass
/home/himdel/manageiq/app/models/vim_performance_operating_range.rb:31:in `dup'
/home/himdel/manageiq/app/models/vim_performance_operating_range.rb:31:in `values_with_std_dev'
/home/himdel/manageiq/app/models/vim_performance_operating_range.rb:19:in `values_to_metrics'
/home/himdel/manageiq/app/models/metric/ci_mixin/long_term_averages.rb:29:in `averages_over_time_period'
/home/himdel/manageiq/app/models/metric/ci_mixin/long_term_averages.rb:3:in `block (2 levels) in <module:LongTermAverages>'
/home/himdel/manageiq-ui-classic/app/helpers/vm_helper/textual_summary.rb:777:in `block in textual_normal_operating_ranges_cpu'
/home/himdel/manageiq-ui-classic/app/helpers/vm_helper/textual_summary.rb:776:in `each'
/home/himdel/manageiq-ui-classic/app/helpers/vm_helper/textual_summary.rb:776:in `each_slice'
/home/himdel/manageiq-ui-classic/app/helpers/vm_helper/textual_summary.rb:776:in `textual_normal_operating_ranges_cpu'
/home/himdel/manageiq-ui-classic/app/helpers/textual_summary_helper.rb:16:in `expand_textual_summary'
/home/himdel/manageiq-ui-classic/app/helpers/textual_summary_helper.rb:39:in `block in expand_textual_group'
/home/himdel/manageiq-ui-classic/app/helpers/textual_summary_helper.rb:39:in `map'
/home/himdel/manageiq-ui-classic/app/helpers/textual_summary_helper.rb:39:in `expand_textual_group'
/home/himdel/manageiq-ui-classic/app/views/shared/summary/_textual_normal_operating_ranges.html.haml:1:in `__home_himdel_manageiq_ui_classic_app_views_shared_summary__textual_normal_operating_ranges_html_haml__4215603692743199013_70264380536980'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:159:in `block in render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:166:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:354:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:157:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:343:in `render_partial'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:311:in `block in render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:310:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/renderer.rb:47:in `render_partial'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/renderer.rb:21:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/helpers/rendering_helper.rb:32:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb:12:in `render_with_haml'
/home/himdel/manageiq-ui-classic/app/views/layouts/_textual_groups_raw.html.haml:6:in `block (2 levels) in __home_himdel_manageiq_ui_classic_app_views_layouts__textual_groups_raw_html_haml__2813905039599057273_70264927763040'
/home/himdel/manageiq-ui-classic/app/views/layouts/_textual_groups_raw.html.haml:4:in `each'
/home/himdel/manageiq-ui-classic/app/views/layouts/_textual_groups_raw.html.haml:4:in `block in __home_himdel_manageiq_ui_classic_app_views_layouts__textual_groups_raw_html_haml__2813905039599057273_70264927763040'
/home/himdel/manageiq-ui-classic/app/views/layouts/_textual_groups_raw.html.haml:2:in `each'
/home/himdel/manageiq-ui-classic/app/views/layouts/_textual_groups_raw.html.haml:2:in `__home_himdel_manageiq_ui_classic_app_views_layouts__textual_groups_raw_html_haml__2813905039599057273_70264927763040'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:159:in `block in render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:166:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:354:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:157:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:343:in `render_partial'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:311:in `block in render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:310:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/renderer.rb:47:in `render_partial'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/renderer.rb:21:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/helpers/rendering_helper.rb:32:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/haml-4.0.7/lib/haml/helpers/action_view_mods.rb:12:in `render_with_haml'
/home/himdel/manageiq-ui-classic/app/views/layouts/_textual_groups_generic.html.haml:2:in `__home_himdel_manageiq_ui_classic_app_views_layouts__textual_groups_generic_html_haml__4502002952510700228_70264608758340'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:159:in `block in render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:166:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:354:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/template.rb:157:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:343:in `render_partial'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:311:in `block in render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/partial_renderer.rb:310:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/renderer.rb:47:in `render_partial'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/renderer/renderer.rb:21:in `render'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/rendering.rb:104:in `_render_template'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/streaming.rb:217:in `_render_template'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/rendering.rb:83:in `render_to_body'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/rendering.rb:52:in `render_to_body'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/renderers.rb:142:in `render_to_body'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/abstract_controller/rendering.rb:48:in `render_to_string'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/rendering.rb:41:in `render_to_string'
/home/himdel/manageiq-ui-classic/app/controllers/vm_common.rb:1230:in `block in replace_right_cell'
/home/himdel/manageiq-ui-classic/app/controllers/vm_common.rb:1236:in `replace_right_cell'
/home/himdel/manageiq-ui-classic/app/controllers/vm_common.rb:979:in `tree_select'
/home/himdel/manageiq-ui-classic/app/controllers/application_controller/explorer.rb:193:in `block (2 levels) in generic_x_show'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/mime_responds.rb:201:in `respond_to'
/home/himdel/manageiq-ui-classic/app/controllers/application_controller/explorer.rb:186:in `generic_x_show'
/home/himdel/manageiq-ui-classic/app/controllers/vm_common.rb:120:in `x_show'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/abstract_controller/base.rb:188:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/rendering.rb:30:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:126:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:455:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:101:in `__run_callbacks__'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:90:in `run_callbacks'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/abstract_controller/callbacks.rb:19:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/rescue.rb:20:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `block in instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/notifications.rb:164:in `instrument'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activerecord-5.0.2/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/abstract_controller/base.rb:126:in `process'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/rendering.rb:30:in `process'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal.rb:190:in `dispatch'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_controller/metal.rb:262:in `dispatch'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/routing/route_set.rb:32:in `serve'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/journey/router.rb:39:in `block in serve'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/journey/router.rb:26:in `each'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/journey/router.rb:26:in `serve'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/routing/route_set.rb:725:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/secure_headers-3.0.3/lib/secure_headers/middleware.rb:10:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/etag.rb:25:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/conditional_get.rb:38:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/head.rb:12:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/session/abstract/id.rb:222:in `context'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/session/abstract/id.rb:216:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/cookies.rb:613:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:97:in `__run_callbacks__'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/callbacks.rb:90:in `run_callbacks'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/callbacks.rb:36:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/executor.rb:12:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-5.0.2/lib/rails/rack/logger.rb:36:in `call_app'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-5.0.2/lib/rails/rack/logger.rb:26:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/sprockets-rails-3.2.0/lib/sprockets/rails/quiet_assets.rb:13:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/request_id.rb:24:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/method_override.rb:22:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/runtime.rb:22:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/executor.rb:12:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionpack-5.0.2/lib/action_dispatch/middleware/static.rb:136:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/sendfile.rb:111:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/railties-5.0.2/lib/rails/engine.rb:522:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.3.0/lib/puma/configuration.rb:224:in `call'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.3.0/lib/puma/server.rb:561:in `handle_request'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.3.0/lib/puma/server.rb:406:in `process_client'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.3.0/lib/puma/server.rb:271:in `block in run'
/home/himdel/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/puma-3.3.0/lib/puma/thread_pool.rb:111:in `block in spawn_thread'

Also, SELECT * FROM "vim_performance_operating_ranges" WHERE values IS NULL  gives me 114 rows, all VmOrTemplate, 2 different time profiles...

@himdel Can I get access to your database?

@himdel Can you verify if<PHONE_NUMBER>5322 is in your schema_migrations table?  If not, can you migrate the database and see if you still have the issue?

It is there :) And if I drop it and run the migration, I still get the same 114 rows...
And the migration says...
==<PHONE_NUMBER>5322 FixVporTimeProfileIds: migrating ============================
-- Removing old VimPerformanceOperatingRanges
   -> 0.0008s
   -> 0 rows
==<PHONE_NUMBER>5322 FixVporTimeProfileIds: migrated (0.0171s) ===================

BTW since you mention that particular migration... running that one on the db from https://github.com/ManageIQ/manageiq-ui-classic/pull/254#issuecomment-279721158 crashes because TimeProfile.default returns nil.

Please reopen if you are still seeing this.


Adding .cadl & package.json cadlMain back compat support

[x] Need to double check vscode .cadl file support.

Oh, it auto-merged :)

Opened https://github.com/microsoft/typespec/pull/1675 to fix the one issue.


Bump python-dotenv from 0.21.0 to 0.21.1

Bumps python-dotenv from 0.21.0 to 0.21.1.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: python-dotenv dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

 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.


integration not working

Hi i got the link account in notifications buth when i try this happens
invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application.
the uri is the uri of my hassio server, portforwarding is set, any ideas?

Fixed with ssl implementatie


Add genecards.org annotation for genes?

If feasible, we should add genecards.org as a link out for genes in the HIPC Dashboard.

Zhou indicates this is ok to pursue, reusing the CTD2 xref file.   We might gain other sources also from the xref file.

tested on local test server.  works as desired.

tested on production.


Support "Copy the main branch only" in Create a new fork

Feature Description
Something like GitHub:

Screenshots
No response

side-note: GitHub is still using "master" instead of "main"?

side-note: GitHub is still using "master" instead of "main"?

I believe the dialog above just uses the name of the default branch.


Add recording rules for aggregate availability and jupyterhub usage

Signed-off-by: Anish Asthana<EMAIL_ADDRESS>

/approve


Fix google_cfe cluster name prefix check in google default creds

Looks like this check was broken in https://github.com/grpc/grpc/pull/26147
The issue wasn't noticed until now just because C++ client tests were already broken for a couple of other reasons during these past two weeks.

Ruby tests failed because of a build issue related to gpg:
gpg: directory '/Users/kbuilder/.gnupg' created
gpg: keybox '/Users/kbuilder/.gnupg/pubring.kbx' created
gpg: connecting dirmngr at '/Users/kbuilder/.gnupg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr


[Groups] Failure response for group commands.

Reproduction steps
Summary: According to test-plan test ACE-1.6 step 7: AddGroup command with groupID set to 0x0104 expected outcome is no response but got failure: src/transport/SessionManager.cpp:194: CHIP Error 0x000000AC: Internal error when executed.
Diff link: https://github.com/project-chip/connectedhomeip/compare/master...manjunath-grl:connectedhomeip:ACE_Groups_ChipError_Response
Reproduction step:

Terminal 1:

Build All-cluster-app
scripts/examples/gn_build_example.sh      examples/all-clusters-app/linux/      examples/all-clusters-app/linux/out/all-clusters-app   chip_inet_config_enable_ipv4=false
Run ./chip-all-clusters-app

Terminal 2:

Build Chip-tool :
gn gen out/debug --args='chip_mdns="platform" chip_inet_config_enable_ipv4=false'     ninja -C out/debug
Commission DUT and TH :
./out/debug/chip-tool pairing code 0x12344321 MT:-24J0AFN00KA0648G00
Run ACE-1.6 test:
./scripts/tests/yaml/chiptool.py tests Test_TC_ACE_1_6

Bug prevalence
Everytime when executed
GitHub hash of the SDK that was being used
b6caecf7860072bd4e55be43dc830b5ce990ddef
Platform
other
Platform Version(s)
No response
Anything else?
Test-plan:

Execution logs:

ACE_Fail_logs.zip

Closing the ticket. Duplicate of https://github.com/project-chip/connectedhomeip/issues/27967

Still facing issue attached logs for reference:
Diff link: https://github.com/project-chip/connectedhomeip/compare/master...manjunath-grl:connectedhomeip:ACE_Groups_ChipError_Response
Execution logs:
ACE_Fail_logs.txt
Screenshots:

Step 7 is trying to add new group of ID 261( 0X105) using an existing group ID (0x104) that does not have privilege
Test plan does not check for any outcome and moves on with the next step.
The objective is to check no groupid of 0x105 should be added and this is done via ViewGroup using unicast method at later point of time.
The script needs to ignore as there is no expected outcome and needs to continue with the next steps.
Please let me know if there is any issue in continuing with the next steps?

Does this error occur with the current manual steps? Or does this happen when you try to implement the yaml?

From @sumaky comment we can understand the there wouldn't be response for the group command and script needs to ignore and proceed with next steps. But while implementing in YAML, even though we don't mention any expected response by default it expects to be  'SUCCESS' if nothing is specified.

Yeah, the problem here is that the group command is failing in the controller because the TH doesn't have an entry for that key. It's a tooling problem. Have a patch out to suma for testing.


Add new journey

Description
Create Pericles001.md and add to Data.json
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

Thanks for your contribution!


Expose plug endpoints so we can mount in an existing plug app

uploaded binary is represented as such
%{"bio" => "Guitarist", "email" =><EMAIL_ADDRESS>"name" => "Dweezil Zappa", "number_of_pets" => "3",
"photo" => %Plug.Upload{content_type: "image/jpg", filename: "cute-kitty.jpg", path: "/var/folders/_6/xbsnn7tx6g9dblyx149nrvbw0000gn/T//plug-1434/multipart-558399-917557-1"}}

we then need to access the path perhaps we can do something like
body = File.stream!(params["photo"].path)
Upload.part(url, header, body)

as soon as we receive the stream and hand it over to the b2 uploader.


chore(RingTheory/Localization): golfs and generalizations

In RingTheory/LocalProperties/Basic: add some lemmas connecting localization of submodules and localization of ideals, and use results about the former to golf results about the latter.

In RingTheory/Localization/Module: golf a proof using the recently introduced IsLocalization.linearMap_compatibleSMul.

In Algebra/Module/Projective, Algebra/Module/LocalizedModule/IsLocalization, RingTheory/Localization/Submodule: generalize from AddCommGroup/CommRing to AddCommMonoid/CommSemiring. Also golf a lemma statement in the second file.

RingTheory/Localization/Algebra, RingTheory/Localization/Ideal: add two TODOs that are not done here for import reasons.

Originally in #19118

Thanks!
bors merge


VSTest task is invoked with working dir prepended to the TestAssembly field

Given the following input:
TestAssembly: **\*.tests.dll;**\*.specs.dll;-:**\obj\**;-:.\tests\FunctionalTests**
I would expect it to run tests that end in tests.dll, or specs.dll, except for assemblies in obj folders, or assemblies in the relative .\tests\functionaltests folder
Instead, VSTest.ps1 is invoked with the following parameter
testAssembly=D:\agents\agent1\_work\871969cb\super-project\**\*.tests.dll;**\*.specs.dll;-:**\obj\**;-:.\tests\FunctionalTests**
When the testAssembly parameter is split for file finding, we get this:
include D:\agents\agent1\_work\871969cb\super-project\**\*.tests.dll
include **\*.specs.dll
exclude **\obj\**
exclude .\tests\FunctionalTests**
The PWD for the task is the parent directory for the VSTest.ps1 script, not the working directory.
The first include will work because the file finder starts at the non-wildcard portion of the string: D:\agents\agent1\_work\871969cb\super-project  and finds all descendant files that match the pattern **\*.tests.dll
The second include fails to find any tests because it's looking in the agent's tasks folder, no the working directory.
The first exclude works because it's a wildcard prefixed match.
I'm not sure if the second exclude would work, again because the root for path comparison isn't the working directory.

Update: with S87 deployment, we have made a few improvements in VSTest task, including how we handle multiple assemblies. Like you noted, when specifying multiple assemblies, only the 1st assembly used to be relative to the Sources Directory. All others were defaulting to Agent directory. This is fixed
Please give it a try and let us know if you have more feedback
Thanks!


cmd/server: add methods for easier checking of Customer status levels

Paygate (and other apps which use Customers) needs to ensure their status is sufficient to initiate Transfers (meaning OFAC or CIP). This is a helper for doing so.

Codecov Report

Merging #46 into master will increase coverage by 0.38%.
The diff coverage is 79.24%.

@@           Coverage Diff            @@
##           master    #46      +/-   ##
========================================
+ Coverage   60.61%    61%   +0.38%
========================================
  Files          15     16       +1
  Lines        1615   1636      +21
========================================
+ Hits          979    998      +19
- Misses        500    501       +1
- Partials      136    137       +1


Empty prover message

Add a clear option for the prover's (non-oracle) message to be empty. Since all prover messages are now empty in the newest optimized version of Marlin, it's less confusing if that's very explicit

Awesome, thanks :)


Changing array to es5array on array method does not give correct output.

(function() {
    var arr = [11, 22, 33, 44];
    var first = true;
    arr.reduce(function (a1, a2, a3, a4) {
        if (first) {
            first = false;
            Object.defineProperty(arr, '2', { get : function() {
                return 201;
            }});
        }
        console.log(a2);
    });
})();

This should print (Chrome and Firefox do that)
22
201
44
Actual
22
44
This is because we use the DirectGetItem to fetch values.

@bterlson to comment on that.

@akroshg what comment do you want? I agree that our behavior is incorrect here.


update to maths utilities

quaternion

euler method REMOVED
now has a rotationTo method to get the quaternion to rotation between two vectors (helpful method that was hidden behind gl-matrix)

vector

lerp would return vec3, casting it to float32array to keep return types consistent

quaternion to euler was extremely unreliable in test cases, seems unfitting to provide it as a utility function when it doesn't give exactly what the user would expect

Thanks! Would it be possible for you to create some tests for quaternion toEuler function?

Thanks! Would it be possible for you to create some tests for quaternion toEuler function?

sure, I'll take a look into it when I get the chance

Thanks! Would it be possible for you to create some tests for quaternion toEuler function?

Just looking into sorting a test out, struggling to understand how to extract an image from the canvas, not entirely sure the best way to do this? I've looked at using the extract plugin on the renderer but that doesn't appear to work for me

After some tinkering, I think its best not to implement as the test cases weren't reliable across more than 2 axis of rotation and beyond 90 degrees +/- in any axis

I see, thanks for giving it a go :)


CLI command to generate a valid graphQl schema from the faker one

It could be useful to have a CLI command that would create a new schema file from the schema.faker.graphql without the faker directives (@fake, @examples and @listLength).
Example you have this schema.faker.graphql...
type Book {
  id: String!
  title: String! @fake(type: words)
  subtitle: String @fake(type: companyCatchPhrase)
  publication: Int @examples(values: [161213760, 163213760, 163513760])
  authors: [Author] @listLength(min: 1, max: 5)
}

...you run graphql-faker generate-schema and you get a new file  schema.graphql:
type Book {
  id: String!
  title: String!
  subtitle: String
  publication: Int
  authors: [Author]
}

What do you think of this idea?

@IvanGoncharov I already implement the script for my use case so there won't be a lot of work there for you. What do you think of this idea? Could I have a green light to open a PR?

Sadly the maintainers (@IvanGoncharov, @RomanHotsiy) aren't really active on this repo so I won't waste time by opening PR. Here is the simple getSchemaFromContent helper that takes a faker shema string as a parameter and return it without the faker directives:
const FAKER_DIRECTIVE_MATCHER = / @fake\((.*?)\)\n/g
const EXAMPLES_DIRECTIVE_MATCHER = / @examples\(values: \[(.*?)\]\)\n/g
const LISTLENGTH_DIRECTIVE_MATCHER = / @listLength\((.*?)\)\n/g
const MATCHERS = [FAKER_DIRECTIVE_MATCHER, EXAMPLES_DIRECTIVE_MATCHER, LISTLENGTH_DIRECTIVE_MATCHER]

const replaceAll = (str: string, find: string, replace: string): string => {
  return str.split(find).join(replace)
}

const getAllFakerDirectivesFromContent = (content: string): string[] => {
  let directives: string[] = []
  MATCHERS.forEach((matcher) => {
    directives = [...directives, ...Array.from(content.matchAll(matcher), (m) => { return m[0] })]
  })

  return directives
}

export const getSchemaFromContent = (content: string): string => {
  const directives = getAllFakerDirectivesFromContent(content)

  directives.forEach((directive) => {
    content = replaceAll(content, directive, '\n')
  })

  return content
}

Hope it will help you @ojczeo 👍

@johannchopin thanks man!


CBP-7008 Learn how to update the Kaniko Action

WIP

Obsolete because of https://github.com/cloudbees-io/kaniko/pull/36


Request to provide a GPU-Accelerated Base Docker Image for CT

Hi,
When I use the base_image=nvidia/cuda:11.4.2-cudnn8-devel-ubuntu20.04 to build the docker environment following the steps given here, I encounter the subsequent error:
2023-04-03 17:42:04.452598: E tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:417] Loaded runtime CuDNN library: 8.5.0 but source was compiled with: 8.6.0.  CuDNN library needs to have matching major version and equal or higher minor version. If using a binary install, upgrade your CuDNN library.  If building from sources, make sure the library loaded at runtime is compatible with the version specified during compile configuration.
2023-04-03 17:42:04.455368: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at conv_grad_input_ops.cc:385 : UNIMPLEMENTED: DNN library is not found.

Could you kindly recommend a suitable base_image that is compatible with tf-agent[reverb] v0.16?
Thanks,
Sayak

Sorry I have not run with GPU in a while.  I might soon.  Based on the error the cuDNN in the docker is too older 8.5 and you need 8.6.  My guess is you should be able to fix that by changing the base image to something newer that has cuDNN 8.6.

I did not test it; but this would seem to be a decent guess.
11.8.0-cudnn8-devel-ubuntu22.04

I have fixed the smoke tests and gotten GPU acceleration working in docker. There were some issues with torch needed by dreamplace; but that is fixed.  https://github.com/google-research/circuit_training/tree/main/tools#end-to-end-smoke-test


Extra tests

These are the tests from #25 that need further review.

Coverage increased (+4.0%) to 95.778% when pulling ac5f61acfad75aaa4e30e19b49c272d207cd63fe on tyll:extra_tests into f0dd323dbef8cbba991c11dd414ade5d0fd4c31d on nmstate:master.


Fixed typo in C# sample

Preview Changes at:
http://bw-apdocs-fix-conference-id.s3-website-us-east-1.amazonaws.com/


[telemetry] platform dashboard

depends on #5376

@zhenyasav would you like me to do this one, too?


Swift tests: RSC14d

Current Swift tests state:
Executed 139 tests, with 51 failures (4 unexpected)

Most because of RestClientStats.swift and RestChannel.swift.
@mattheworiordan We need to merge it all to get the current state on this.


rds.ParameterGroup diff not clear

What happened?
Hi,
when doing a up on a stack with a rds.ParameterGroup, Pulumi will always show a diff. This is due to the order the array gets saved in the Pulumi service.
This makes the detection of an actuall very difficult, as everything is marked in red in the Pulumi output.
Demo code:
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
import {rds} from "@pulumi/aws";

const vpc = new awsx.ec2.Vpc("vpc", {
    cidrBlock: "<IP_ADDRESS>/16",
    enableDnsHostnames: true,
    enableDnsSupport: true,
})

const group = new rds.SubnetGroup("group", {
    subnetIds: vpc.publicSubnetIds,
    name: "group",
})

const securityGroup = new aws.ec2.SecurityGroup("securityGroup", {
    name: "securityGroup",
    vpcId: vpc.vpcId,
    ingress: [
        {
            protocol: "tcp",
            fromPort: 5432,
            toPort: 5432,
            cidrBlocks: [
                "<IP_ADDRESS>/0",
            ],
        }
    ],
    egress: [
        {
            protocol: "tcp",
            fromPort: 5432,
            toPort: 5432,
            cidrBlocks: [
                "<IP_ADDRESS>/0",
            ],
        }
    ],
})

const backyardParameterGroup = new aws.rds.ParameterGroup(
    "parameterGroup",
    {
        family: "postgres14",
        parameters: [
            {name: "max_connections", value: "500", applyMethod: "pending-reboot"},
            {name: "wal_buffers", value: "2048", applyMethod: "pending-reboot"}, // in 8kB
            {
                name: "default_statistics_target",
                value: "100",
                applyMethod: "immediate",
            },
            {name: "random_page_cost", value: "1.1", applyMethod: "immediate"},
            {
                name: "effective_io_concurrency",
                value: "200",
                applyMethod: "immediate",
            },
            {name: "work_mem", value: "65536", applyMethod: "immediate"}, // in kB
            {
                name: "max_parallel_workers_per_gather",
                value: "4",
                applyMethod: "immediate",
            },
            {
                name: "max_parallel_maintenance_workers",
                value: "4",
                applyMethod: "immediate",
            },
            {
                name: "pg_stat_statements.track",
                value: "ALL",
                applyMethod: "immediate",
            },
            {
                name: "shared_preload_libraries",
                value: "pg_stat_statements,auto_explain",
                applyMethod: "pending-reboot",
            },
            {
                name: "track_io_timing",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "log_min_duration_statement",
                value: "1000",
                applyMethod: "immediate",
            },
            {
                name: "log_lock_waits",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "log_temp_files",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "log_checkpoints",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "log_connections",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "log_disconnections",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "log_autovacuum_min_duration",
                value: "0",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_format",
                value: "json",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_min_duration",
                value: "1000",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_analyze",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_buffers",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_timing",
                value: "0",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_triggers",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_verbose",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.log_nested_statements",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "auto_explain.sample_rate",
                value: "1",
                applyMethod: "immediate",
            },
            {
                name: "rds.logical_replication",
                value: "1",
                applyMethod: "pending-reboot",
            },
        ],
    },
);

const db = new aws.rds.Instance("db", {
    identifier: "db",
    engine: "postgres",
    engineVersion: "14.1",
    instanceClass: "db.t3.micro",
    allocatedStorage: 5,
    username: "edu",
    password: "e12345678",
    dbSubnetGroupName: group.name,
    vpcSecurityGroupIds: [securityGroup.id],
    parameterGroupName: backyardParameterGroup.name,
    publiclyAccessible: true,
    skipFinalSnapshot: true,
})

Expected Behavior
Shows only diffs of fields, which actually changed.
Steps to reproduce
See above the code!
Output of pulumi about
pulumi about -s xxx/prod
CLI
Version      3.60.0
Go Version   go1.20.2
Go Compiler  gc

Plugins
NAME    VERSION
aws     5.33.0
awsx    1.0.2
docker  3.6.1
nodejs  unknown

Host
OS       darwin
Version  13.2.1
Arch     arm64

Current Stack: xxx/xxx/prod

TYPE                                   URN
pulumi:pulumi:Stack                    urn:pulumi:prod::xxx::pulumi:pulumi:Stack::xxx-prod
pulumi:providers:aws                   urn:pulumi:prod::xxx::pulumi:providers:aws::default_5_33_0
pulumi:providers:awsx                  urn:pulumi:prod::xxx::pulumi:providers:awsx::default_1_0_2
awsx:ec2:DefaultVpc                    urn:pulumi:prod::xxx::awsx:ec2:DefaultVpc::default
pulumi:providers:aws                   urn:pulumi:prod::xxx::pulumi:providers:aws::default_5_16_2
aws:rds/subnetGroup:SubnetGroup        urn:pulumi:prod::xxx::aws:rds/subnetGroup:SubnetGroup::xxx-backyard
aws:ec2/securityGroup:SecurityGroup    urn:pulumi:prod::xxx::aws:ec2/securityGroup:SecurityGroup::xxx-backyard-rds
aws:rds/parameterGroup:ParameterGroup  urn:pulumi:prod::xxx::aws:rds/parameterGroup:ParameterGroup::xxx-backyard
aws:rds/instance:Instance              urn:pulumi:prod::xxx::aws:rds/instance:Instance::xxx-backyard

Found no pending operations associated with prod

Backend
Name           [pulumi.com](http://pulumi.com/)

Dependencies:
NAME            VERSION
@types/node     16.18.23
prettier        2.8.7
@pulumi/aws     5.33.0
@pulumi/awsx    1.0.2
@pulumi/pulumi  3.60.0

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@dirien Thanks for logging this. To confirm the severity of this, this is isolated to only the diff preview right? It doesn't cause the cloud resource to be recreated?

@rquitales: no it does not trigger a recreated.

@dirien Thanks for logging this. To confirm the severity of this, this is isolated to only the diff preview right? It doesn't cause the cloud resource to be recreated?

Same for me. When I run multiple time pulumi up every time I get
     pulumi:pulumi:Stack     harbour-dev
 ~   └─ aws:rds:SubnetGroup  rds          update     [diff: ~subnetIds]

I've found this extends beyond just sort order.
When asked, AWS will always say the applyMethod is "pending-reboot". (Which makes sense, as applyMethod is basically a flag on how to handle a parameter change, not a long-term part of the resource state)
So if you set a parameter applyMethod to "immediate". Pulumi will try to set that, read back "pending-reboot", store that in the resource state, and then generate a diff and repeat the whole cycle on the next update, ad infitum.
applyMethod should basically be ignored for purposes of diffs.

Summary
Contrary to the original hypothesis, set element reordering is not affecting diffs as both TF and bridged providers
apply canonical ordering based on the custom set hash function. The issue here is indeed with implicit refreshing that
changes applyMethod, that is pulumi up results in a different applyMethod in the cloud state from the inputs. This
change affects the parameter hash and ordering when more than 1 parameter is involved, adding to the confusion.

currently Pulumi matches default TF behavior on the same program which also has a perpetual diff

aws_db_parameter_group
offers a note about potential perpetual diffs

Pulumi docs have a similar NOTE

TF does not have the perpetual diff when run with -refresh=false

There is currently no supported way for the Pulumi bridged provider to match the -refresh=false behavior of
Terraform

Resolution
Currently leaning toward closing this as working as advertised, although the NOTE in the docs is a little vague about
the possibility of perpetual diffs right after creating the resource and not making any changes. If you are affected by
this, you might be able to tweak applyMethod values in your program until the perpetual diff disappears.
A more involved possibility would be to build support in pulumi-terraform-bridge for matching -refresh=false behavior
of Terraform.
Minimal repro
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
import {rds} from "@pulumi/aws";

const backyardParameterGroup = new aws.rds.ParameterGroup(
    "parametergroupmy",
    {
        family: "postgres14",
        parameters: [
            {
                name: "track_io_timing",
                value: "1",
                applyMethod: "immediate", // Changing this to pending-reboot fixes the diff
            },
        ],
    },
);

This yields:
$ pulumi preview --diff

 ~ parameters: [
     ~ [0]: {
             ~ applyMethod: "pending-reboot" => "immediate"
             ~ name       : "track_io_timing" => "track_io_timing"
             ~ value      : "1" => "1"
           }
   ]

Recommended workaround: edit your program source to mach applyMethod to the target values suggested by the pulumi preview --diff.
Minimal repro in TF
Write infra.tf:
resource "aws_db_parameter_group" "default" {
  name   = "rds-pg"
  family = "postgres14"

  parameter {
    name  = "track_io_timing"
    value = "1"
    apply_method = "immediate"
  }
}

And then:
$ terraform apply
$ terraform plan
aws_db_parameter_group.default: Refreshing state... [id=rds-pg]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_db_parameter_group.default will be updated in-place
  ~ resource "aws_db_parameter_group" "default" {
        id          = "rds-pg"
        name        = "rds-pg"
        tags        = {}
        # (4 unchanged attributes hidden)

      - parameter {
          - apply_method = "pending-reboot" -> null
          - name         = "track_io_timing" -> null
          - value        = "1" -> null
        }
      + parameter {
          + apply_method = "immediate"
          + name         = "track_io_timing"
          + value        = "1"
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

$ terraform plan -refresh=false

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.

@stepan-romankov could you please open a separate issue with a repro for [diff: ~subnetIds] as I'm not currently able to reproduce this from this program? Much appreciated.

FWIW on the larger program I get:
pulumi preview --diff                                                                                ~/tmp/2024/03/aws-2442
Previewing update (dev)

View Live: https://app.pulumi.com/anton-pulumi-corp/aws-2442/dev/previews/146208b6-2bba-45b4-b6d8-910a0900f83e

  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:dev::aws-2442::pulumi:pulumi:Stack::aws-2442-dev]
    ~ aws:rds/parameterGroup:ParameterGroup: (update)
        [id=parametergroupmy-f2e2fcd]
        [urn=urn:pulumi:dev::aws-2442::aws:rds/parameterGroup:ParameterGroup::parametergroupmy]
        [provider=urn:pulumi:dev::aws-2442::pulumi:providers:aws::default_6_25_0::e55fd59a-44b2-4e82-94e2-7a8f07c2bad1]
      ~ parameters: [
          ~ [2]: {
                  - applyMethod: "pending-reboot"
                  - name       : "track_io_timing"
                  - value      : "1"
                }
          ~ [3]: {
                  - applyMethod: "pending-reboot"
                  - name       : "log_checkpoints"
                  - value      : "1"
                }
          ~ [10]: {
                  + applyMethod: "immediate"
                  + name       : "track_io_timing"
                  + value      : "1"
                }
          ~ [14]: {
                  + applyMethod: "immediate"
                  + name       : "log_checkpoints"
                  + value      : "1"
                }
        ]
Resources:
    ~ 1 to update
    1 unchanged

And editing these listed entries gets rid of the perpetual diff.

For completeness, here are some upstream issues essentially closed as won't fix:
https://github.com/hashicorp/terraform-provider-aws/issues/22028
https://github.com/hashicorp/terraform-provider-aws/issues/20660

I've tried applying an ignoreChanges workaround but it does not apply to this problem, unfortunately. This is now tracked in https://github.com/pulumi/pulumi-terraform-bridge/issues/1756

It remains an option to consider @kmosher  suggestion regarding applyMethod should basically be ignored for purposes of diffs, ideally this is something that would happen upstream but we can just do this in the bridged provider as well. One approach would be patching the upstream provider and coding a special CustomizeDiff CustomizeDiffFunc that removes diffs that pertain changes that shift apply_method only without changing the value. The CustomizeDiff interface is a little tricky but at a glance it seems like it could be done correctly to solve this problem and make the resource work as you would expect.


Vector AMO Clarification

Section 8 says about the width field for vector AMO operations:
width[2:0] specifies size of memory elements, and distinguishes from scalar AMO
Is this correct? I thought that this is the index width, and the memory elements are SEW-sized.

Thanks for pointing this out; will fix.


style:  making the code less complex in the http_util

It's quite messy because prioritizing finishing the functionality instead of being something readable, I'm too lazy to make a "string factory" but it would be what I would like in the final solution, in addition to being very reusable.
features

[ ] rename http_util.headers() to http_util.create_request()
[ ] http_util.craete_request() must be return a object (like pipeline, eg, std.http.get)
[ ] add_body shold not be used when method is GET or HEAD
[ ] mutable header behavior is a default value can be changed by add_custom_headers()
[ ] imutable headers shold not be modified by add_custom_headers()
[ ] all headers add must be ordered with constructor
[ ] headers should not be duplicated
[ ] create a string result toHttpProtocol() for ginga
[ ] create a string result toCurlCommand() for Curl protocol
[ ] return values by to...() must be a string and function (empty closujure)

in the future a function must be a cleaner for temp files etc...

Notes

You can suggest other names that you think are more friendly
It doesn't matter if you do http_util.create_request():add_custom_header orhttp_util.create_request().add_custom_header

example
Protocol Ginga

before
local headers = http_util.headers(self.header_list, self.header_dict, {
    'Host', self.p_host..params, false,
    'Accept', '*/*', true,
    'Cache-Control', 'max-age=0', false,
    'User-Agent', 'Mozilla/4.0 (compatible; MSIE 4.0; Windows 95; Win 9x 4.90)', true,
    'Content-Length', tostring(#self.body_content), false,
    'Connection', 'close', false
})
local request = 'GET '..self.p_uri..' HTTP/1.1\r\n'..headers..'\r\n'..self.body_content..'\r\n\r\n'

affter
local request = http.create_request(self.method)
    .add_imutable_header('Host', self.p_host..params)
    .add_imutable_header('Cache-control', 'max-age=0')
    .add_mutable_header('Accept', '*/*')
    .add_custom_headers(self.header_list, self.header_dict)
    .add_imutable_header('Connection', tostring(#self.body_content))
    .add_imutable_header('Content-Length', 'close')
    .add_body(self.body_content)
    .toHttpProtocol()

Protocol Curl
before
local index = 1
local cmd = 'curl -L \x2D\x2Dsilent \x2D\x2Dinsecure -w "\n%{http_code}" '
local protocol = self.method == 'HEAD' and '\x2D\x2DHEAD' or '-X ' .. self.method
local params = http_util.url_search_param(self.param_list, self.param_dict)

local headers, index = ' ', 1

while self.header_list and index <= #self.header_list do
    local header = self.header_list[index]
    headers = headers..'-H "'..header..': '
    headers = headers..self.header_dict[self.header_list[index]]..'" '
    index = index + 1
end

local body = ''
if self.method == 'POST' and self.body_content then
    body = '-d \''..self.body_content..'\' '
end

local request = cmd..protocol..headers..body..self.url..params

after
local request = http.create_request(self.method)
    .add_url_with_params(self.url, params)
    .add_custom_headers(self.header_list, self.header_dict)
    .add_body(self.body_content)
    .toCurlCommand()

I ended up closing PR #61 and #62, as they are very small, and it would be complex to deal with the tasks separately for both me and you @lnpotter .
I put this list of tasks more like a checklist, you can choose for each commit to be one, or just to confirm what remains to be done.
If you want it, and have the capacity to implement it completely, tell me about, and I hope you implement it! I was almost starting to do it because milestone 0.0.5 will be a lot of network updates.

I was going to try to implement it in isolation, to make it easier for me and you to understand. Do you want me to do it all at once? I can try, but my knowledge of Lua is shallow, @RodrigoDornelles.

@lnpotter
This can be a single PR, and each topic can be a commit if you want to do it separately.
Here's a tip, when you use : in lua instead of . it passes the object into the function as the first parameter.
local function add_body(self, body)
   self.body = body
   return self -- pipeline tricky
end

local function myprint(self)
   print(self.body, self.method)
end

local function create_request(method)
   return {
      method=method,
      add_body=add_body,
      print=myprint
   }
end

create_request('get'):add_body('foo'):print()

You would need to implement some lists in terms of headers, if you find it very comfortable there are other issues with less difficult levels, and I will try to implement this one.

Understood. I'll do it this way, then I'll create a PR with the respective changes in commits.


Setting file permissions fails for filenames with spaces

I noticed in some logs after a recent install of a site with existing content (user populated) that there were some errors from chmod and it looks like it couldn't set permissions for files that had spaces in their names.
This looks like a problem where xargs is treating every space piped to it from find as a new file to be chmoded. Indeed, that's what I'm seeing from a quick search and the solution seems to be to add a flag to change xargs's delimiter. Hopefully it's that simple, need to test.

| xargs -d '\n' chmod ... brought up xargs: unrecognized option: d in the logs. Looks like the version bundled with our base image does not support it:
Usage: xargs [OPTIONS] [PROG ARGS]

Run PROG on every item given by stdin

        -0      NUL terminated input
        -a FILE Read from FILE instead of stdin
        -o      Reopen stdin as /dev/tty
        -r      Don't run command if input is empty
        -t      Print the command on stderr before execution
        -p      Ask user whether to run each command
        -E STR,-e[STR]  STR stops input processing
        -I STR  Replace STR within PROG ARGS with input line
        -n N    Pass no more than N args to PROG
        -s N    Pass command line of no more than N bytes
        -P N    Run up to N PROGs in parallel
        -x      Exit if size is exceeded

I tried the -0 option because I wasn't entirely privy to what exactly NUL terminated input was despite the help screen assuming I was: xargs: argument line too long.
An alternative is provided on Stack Overflow and needs to be tested more rigorously before committing:
| tr '\n' '\0' | xargs -0 -n1 chmod.... So far so good from command line when I shell into the container. Unfortunately I don't have the data this week to try this out with a build yet.


Track V3 Tasks Remaining

These are all the things we need to finish with V3 Track API

[x] Re-enable TestPeerConnection_Media_Closed
[x] Rework API so that Bind is called in SetRemoteDescription
[x] Write the following tests for new Track API

[x] Writing to a un-added Track
[x] Write to a track on Closed PeerConnection
[x] Write to a track on a disconnected PeerConnection
[x] Write to a track with one bad PeerConnection
[x] Offer fail when Answerer doesn't support a codec
[x] Answer fail when Offerer doesn't support a codec
[x] Does sending use the proper Payload type

[ ] Make TrackRemote an interface
[x] Review Public API for sharp edges.

[x] MimeType is currently case sensitive. Users will need to do video/VP8 and video/vp8, anything we can do to help?
[x] Are we all clear to do all the use cases for Interceptor (NACK, FEC, Congestion Control, Stats)

@at-wat @masterada @jeremija ^ following up on the other PR. Add anything else you think is important!
If you agree I would like to merge the other PR and then begin the process of getting this done for v3.0.0. We are so close, and really want more people involved :)

MimeType is currently case sensitive. Users will need to do video/VP8 and video/vp8, anything we can do to help?

https://tools.ietf.org/html/rfc2045#section-2

All numeric and octet values are given in decimal notation in this set of documents. All media type values, subtype values, and parameter names as defined are case-insensitive.  However, parameter values are case-sensitive unless otherwise specified for the specific parameter.

I think as TrackLocalStaticRTP is in the main package, parameters like MTU is better to be configurable by users.
https://github.com/pion/webrtc/pull/1517#discussion_r523729641

@at-wat That sounds good to me! If you want to start the ...opt or doing a configuration struct I am happy with either.

@jeremija @OrlandoCo Any interest in splitting/taking on any of these tasks? I am happy to do all of them, just don't want to duplicate work :)

@at-wat I tried a few different ways (and failed) to make TrackRemote an interface. I might be missing something, but I don't see the value.

I don't think we should encourage casting in OnTrack. Users are going to copy examples and be confused why they don't work.
I can't think of any use cases that are blocked. Users can just chain Read into their own code etc...

@Sean-Der so sorry for a late reply. Last week has been super crazy for me work-wise :frowning_face:. I see you've already implemented all of this (kudos to you!), and I just read your comment about how you ran into issues with the last task (making TrackRemote an interface))

@jeremija no worries at all :) this all Open Source/for fun!
If you have some time approving https://github.com/pion/webrtc/pull/1546 would be a huge help.

These are all merged, we are now just stabilizing /v3 :partying_face:


WIP: Rhstor 1748 add support for subscription pause/unpause

Add the ability to unpause a subscription if it is paused for RamenDR.
If the user has specified a failover cluster for a subscription in the
AVR CR, we will restore the backed up PVs to it before the subscription
is unpaused

I am declining this PR.  Too many changes as a result of messy merge conflict.


#xxxx tablet re-render optimisation

#655 merge first

@Chris-Petty, I've merged a couple of PRs to development branch, can you update this branch from dev pls and let me know, will review then.

@andreievg ready for review


Tune tree differ

In edits where there are numerous possibilities for how to account for the changes, the tree differ doesn't always land on the solution that makes the most sense to me.
Example: https://wiki-topic.toolforge.org/diff-tagging?lang=en&revid=1051321835
The counts actually seem right but in fact the tree differ has decided the {{For...}}} template moved as can be seen in the intermediate diff: https://edit-types.wmcloud.org/api/v1/diff?lang=en&revid=1051321835
The Mediawiki differ got this one correct (I would say -- actually no right answer here). One possibility is that we could an additional cost to changes for nodes that have an exact match between revisions to discourage "changes" or "moves" in nodes that were not actually edited. I'll have to explore what impact that would have. I think it would be relatively cheap to implement at least.

This also causes issues when e.g., a template is moved within text and the tree differ ascribes the changes to the text and not the template. Then when the text post-processing is done, no changes are detected.
Example test that fails because no changes are detected by the differ:
def test_move_template():
     curr_wikitext = prev_wikitext.replace('\n{{Use dmy dates|date=April 2017}}',
                                           '{{Use dmy dates|date=April 2017}}\n',
                                           1)
     expected_changes = {'Template':{'move':1}}
     diff = get_diff(prev_wikitext, curr_wikitext, lang='en')
     assert expected_changes == nd.get_diff_count(diff)

Or this diff which falsely assumes the References section was removed: https://wiki-topic.toolforge.org/diff-tagging?lang=simple&revid=7992487
Probably I need an attribute on nodes that is like 'removable' that I set to false for sections that exist unchanged in both revisions.


AttributeError: 'NoneType' object has no attribute 'tobytes'

after training a model and loading it up to test it using the model inferance tab. after choosing the model , song and the mangio crepe method then selecting convert. I get an error. the log says.
Traceback (most recent call last):
File "D:\RVC_voice\Mangio-RVC-v23.7.0\my_utils.py", line 96, in load_audio
ffmpeg.input(file, threads=0)
File "D:\RVC_voice\Mangio-RVC-v23.7.0\runtime\lib\site-packages\ffmpeg_run.py", line 325, in run
raise Error('ffmpeg', out, err)
ffmpeg._run.Error: ffmpeg error (see stderr output for detail)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\RVC_voice\Mangio-RVC-v23.7.0\infer-web.py", line 292, in vc_single
audio = load_audio(input_audio_path0, 16000, DoFormant, Quefrency, Timbre)
File "D:\RVC_voice\Mangio-RVC-v23.7.0\my_utils.py", line 103, in load_audio
raise RuntimeError(f"Failed to load audio: {e}")
RuntimeError: Failed to load audio: ffmpeg error (see stderr output for detail)
Traceback (most recent call last):
File "D:\RVC_voice\Mangio-RVC-v23.7.0\runtime\lib\site-packages\gradio\routes.py", line 437, in run_predict
output = await app.get_blocks().process_api(
File "D:\RVC_voice\Mangio-RVC-v23.7.0\runtime\lib\site-packages\gradio\blocks.py", line 1349, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "D:\RVC_voice\Mangio-RVC-v23.7.0\runtime\lib\site-packages\gradio\blocks.py", line 1283, in postprocess_data
prediction_value = block.postprocess(prediction_value)
File "D:\RVC_voice\Mangio-RVC-v23.7.0\runtime\lib\site-packages\gradio\components.py", line 2586, in postprocess
file_path = self.audio_to_temp_file(
File "D:\RVC_voice\Mangio-RVC-v23.7.0\runtime\lib\site-packages\gradio\components.py", line 360, in audio_to_temp_file
temp_dir = Path(dir) / self.hash_bytes(data.tobytes())
AttributeError: 'NoneType' object has no attribute 'tobytes'

I believe this is caused by a missing index file which didn't get generated in the log file.

turns out I had the wrong path to my audio folder.

Wdym, i had this problem for a very long time and couldnt fix it, i dont think i had the wrong path, also the path didnt contain spaces or special characters etc


One-use timeout

We might sometimes want to modify the timeout for a single operation. This may require a withTimeout field for MonadLifx.

Note that getTimeout is ultimately only used in receiveMessage.


Status search parameter parsing

First, thanks for building and maintaining twitter4j for so long. It's a pleasure to use! :)
My team recently tried to do some simple status searching, and we noticed that while paging status searches is easy, the "next page" fields are not exposed by the current API. (They're handled opaquely by the Query object using a anextPagea query parameters variable.)
This change parses those nextPage variables and extracts the values from that parameter string into the greater Query object whenever possible, namely:

query
lang
locale
max_id
count
geocode
result_type

Other variables -- since, until, and since_id -- get rolled into the query (e.g., since:2014-1-1) and so are not parsed into the Query.
This change is fully backwards compatible. This change would make more information available to those who wish to use it. I've also added a test for the change.
Hopefully all this makes sense! Let me know if you have any questions for me. :)

Hi team,
I'm sorry if I raise issue wrong location, and I will be happy if you let me know the right one.
I'm searching the data for my company (via hashtag), and the query such as below:
https://api.twitter.com/1.1/search/tweets.json?q=%23アッコの宇宙大戦争&locale=ja
It's run OK via twitter console:  https://dev.twitter.com/rest/tools/console (return a lot of result)
But via twitter4j, the result is empty. I've tried to search and get the same issue in SO:
http://stackoverflow.com/questions/18031393/how-to-restrict-the-language-of-results-in-twitter4j-to-english
Have you known or fixed it?
Regards,

@nhthai2207 Don't know whether it is a bug or not, but twitter4j issues are tracked here, not in github: http://issue.twitter4j.org/youtrack/issues/TFJ Have you tried using a tool like Charles to inspect the request being made to api.twitter.com?


Introduce VatLayer integration

https://vatlayer.com/ integration will be a nice Addon to current saleor setup.
Couple of assumptions:

Move to separated package like https://github.com/mirumee/django-prices-openexchangerates
Package should deliver a Model that will keep vat rates
Integration on saleor side has to be discussed - products should be tagged in some way, to use correct tax rate
Package should deliver a manegement command that will handle rates update

Integration plan:

[ ] provide a model to store per-country tax rates and reduced tax rates (JSON field? hstore?)
[ ] write a function that makes a request to the http://apilayer.net/api/rate_list endpoint and updates the database accordingly
[ ] write a management command that calls the above function so we can call it once per day
[ ] write a function that takes a country code and a rate name (to handle reduced rates -- list available at http://apilayer.net/api/types) and returns a tax price modifier

For Saleor integration we need to introduce a country picker in the UI in case GeoIP gets it wrong.

[ ] Implement PriceModifier (ref: https://github.com/mirumee/django-prices-openexchangerates/blob/master/django_prices_openexchangerates/init.py#L16)
This modifier will apply a VAT to a Price
[ ] Implement an utility function that will return correct PriceModifier for selected country

Hi, what is the status of this issue? This is currently a blocker for my project and before I start developing a palliative solution I'd like to double check the status as the last update is three months ago.

The prices library is in place, we're waiting for a legal review of tax intricacies involved in serving b2b and b2c clients.

Good to hear, so if time gets too tight for my project I will use the PR as an interim solution and see how to merge things later, not bothering redoing the wheel.

it's been six months since last update. Any new information about this implementation? Is there any shop online with Saleor? I can't imagine how it could go live without a proper VAT implementation and the VAT branch is quite outdated, so I was wondering if I still should use it.

Tax support was introduced in #1929 💸


fixleft outer join estimation

Proposed changes
A left join B on A.x=B.x and A.y=B.y
B.x and B.y make result tuple number scale out.
suppose A is scaled out by B.x N1 time, and scaled out by B.y N2 time, and N1 < N2.
we should choose N1 as the final scale out factor, not N2.
this pr impact on tpcds_sf100 59/17/29/25/47/40/54
before
query59 77295   75279   75230   75230
query17 22642   21566   21599   21566
query29 16508   16092   16006   16006
query25 20262   20571   21171   20571
query47 23571   23264   23107   23107
query40 3305    2849    3064    2849
query54 9052    8882    8715    8715
Total cold run time: 172635 ms
Total hot run time: 168044 ms
after
query59 56435   54717   53919   53919
query17 24167   22377   23237   22377
query29 16950   18325   16333   16333
query25 21478   22975   21358   21358
query47 24412   24611   23920   23920
query40 5491    4779    5176    4779
query54 8671    8664    8658    8658
Total cold run time: 157604 ms
Total hot run time: 151344 ms
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


[HOLD for payment 2023-06-23] [$250] [Accessible Pressables] Migrate AttachmentView

Migrate AttachmentView to use the new Pressable components
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ece6545b87692f1e
Upwork Job ID:<PHONE_NUMBER>597038592
Last Price Increase: 2023-06-12

I can work on this one

PR: https://github.com/Expensify/App/pull/20627

Can someone bring me up to speed on these issues. Are they flat rate at $250? When do they need to be paid, and to who?

Here's the TL;DR on these:

We've been working with Software Mansion to complete this migration, and they're almost done.
The only reason they're labeled external w/ an Upwork job at all is to auto-assign a C+ and pay them out for the review
Because they're all the same and quite simple, yes I've been pricing them at $250

Sorry for the Inconvenience. Didn't knew that i shouldn’t apply on this Issues. 👍

@roryabraham Hi, as an expert contributor from Software Mansion I'd like to get this issue, can you assign me to this one, please?

@trjExpensify The only payment due here is $250 to @parasharrajat for the review

Offer sent to @parasharrajat

Bump @parasharrajat so you can get your 🤑

Totally.

Same as Friday, melvin. Did you get this handled through NewDot, @parasharrajat? :)

Hm okay, but you should have been able to request by now?

Just waiting for @parasharrajat NewDot payment

Approved $250 based on https://github.com/Expensify/App/issues/20600#issuecomment-1636584593

Neeeat! Thanks, closing! :)