fix(inferencer): added predefined relationInfer control

Inferencer relationInfer issue with accessor key when the field is multiple but does not have any object/value in the array
Closing issues
closes #4497

[x] Corresponding issues are created/updated or not needed
[x] Docs are updated/provided or not needed
[x] Examples are updated/provided or not needed
[x] TypeScript definitions are updated/provided or not needed
[x] Tests are updated/provided or not needed
[x] Changesets are provided or not needed

Hello @rasitcolakel, could you update snapshots for inferencer specs? Currently tests are failing, and it would be nice to squash commits into one commit with correct commit message format? You've done it right in the last commit but since previous ones aren't following the convention, CI is failing.
We'll review it ASAP, and thanks for the contribution!

@aliemir thanks for your commit Ali Emir


Map viz: add support for new backend response features

Resolves #1191
☝
Testing advice in the linked issue.
If the vocabulary is small, use it as-is, to make sure that the colours are consistent wherever you are on the map.
If >8 values in a continuous, then of course the colours will change as you move around.  Also, as you move around, it's likely that any checkbox selections will have to be reset, so a check is made for this too (no pun intended).
Also added client-specified (from study metadata) bin specification for numeric continuous vars. This means that these stay the same as you move around the map, which we think is desired behaviour.  Only categoricals >8 values should change the legend as you move around the map.

hey @bobular do you mind reminding me which studies have geolocation data please? Thanks!

Just went back and tried 2. again - and this time it worked? So must have been an odd fleeting error... very curious

Ready for a quick once-over, @asizemore  - thanks for your comments!

Looks lovely @bobular !!
Yeah, you're right this should probably get discussed soon at any of the meetings. Although i'm probably not being helpful - I liked seeing all of the "1"s in proportion mode :)

conclusions from the meeting today:

count changes only for the pie plot, not for either bar option

Some thoughts behind this decision:
When a legend item is toggled off in bar proportion mode, the y-axis stays the same and we see that the proportions are still the proportions of the total. In the pie plot case, because the colored arcs must fill the pie, it's now showing each colored arc as a proportion of the sum of all colored arcs. This is equivalent to changing the y axis in the bar plot proportion mode to be the sum of the proportions that are still there, instead of always being 1.


[BUG] [1.12] Fishing Rod crosshair instability

When in Shoulder Surfing mode and holding a Fishing Rod, by simply moving about the terrain, there is no stability in the crosshair's y-axis. It seems to only affect this item, but as someone who uses it in combat, it can be slightly distracting.
To reproduce, it should become apparent when comparing a Fishing Rod to any other item, that the crosshair bounces up and down and appears lower than it should.
Issue happened in latest 1.12 compatible version of the mod, with only Optifine installed and in a Single Player survival world.
Also, thank you so much for fixing the reach issue, I am very grateful! Love your work. :)

My bad sorry, didn't realise this was a setting. Disabled it and it's perfect for my playstyle. Thank you!


Stage -> Master

Eth, Avax, Matic, QCK, LVN and  more other logos are missing on the Assets page. Can be found scrolling through the assets page till the end.

Disclaimer text translation is missing and the translation of all the Disclaimers are missing.


Rewrite test file path?

Our project runs tests inside a docker container. When I run tests from the shell I usually use:
docker-compose exec test rails test **/filename_test.rb
When I use Ruby Spec Runner I see:
/usr/local/bundle/gems/bootsnap-1.10.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require': cannot load such file -- /home/hovis/dev/hiringthing/HiringThing/test/unit/lib/htlogic/htlogic_business_hooks_test.rb

The load error makes a lot of sense because this absolute path to the test file is incorrect inside docker, that's a host path.  The correct absolute path inside the container is /app/test/unit/lib/htlogic/htlogic_business_hooks_test.rb.
Maybe instead of a setting to rewrite the test file path there could be a setting that specifies the location of the Rails app on the host, and then Ruby Spec Runner could just trim that string from the test file path?
If I set my Rails app dir to "/home/hovis/dev/hiringthing/HiringThing/" then the test command could try to run "test/unit/lib/htlogic/htlogic_business_hooks_test.rb" which should run perfectly.
The more future-proof setting would just be a regex that could rewrite the test path for a variety of scenarios different than mine.
Note: I'm also using a remote SSH connection in VS Code, but that doesn't seem to be causing any problems here at all. The test file path being executed is correct on/for the remote host, it's just not correct for the docker container running on the remote host.
Thoughts?

Hmmm I see a couple of problems that would need to be solved for this to work with running things in docker. The extension works by writing output from minitest and rspec to a file which the extension is watching for changes. So the test runner inside the container would need to be able to write to a file that the extension can watch (so I imagine this would need to be on the host). Right now those files are created and managed by an npm package that creates a file in an appropriate tmp dir of your machine. So I think setting up a directory like this would be doable in docker, but then would need to make large changes to the way the watched output file is setup and cleaned up.
The second problem is that the extension will need to be able to understand which file is being referenced by the test output. In minitest this might be doable cause we have to manually write the test path into the output ourselves, however in rspec it uses the built in json format which uses its own paths so we would need some way to map that back to the files open in vscode.
So it doesn't look like it will be be a trivial solve. What do you think of these problems given your experience with developing inside a docker container?

Oof.
As for the temp file the simplest solve would just be mapping/binding, but this is involved enough that I'm scared away for now.
Thanks for the feedback!

Hi @foneandrew, I would like to revisit this.
Currently, I'm setting rspecCommand to docker-compose exec -T web bundle exec rspec to run the spec inside docker. Then when I hit run, it runs this command which works when I modify the file path from
docker-compose exec -T web bundle exec rspec -f p -f j --out '/path/to/output-file.json'  '/path/to/spec/graphql/types/query_type_spec.rb

to
docker-compose exec -T web bundle exec rspec -f p -f j --out '/path/to/output-file.json' 'spec/graphql/types/query_type_spec.rb

It seems like adding a Rails app dir, like @hovissimo suggested, could be a solution to fix that? Right now I'm just modifying it manually.

Thanks for posting the example of the changes you'd need to get it to work with docker. If it works with just that change to the test file path then I reckon we can do it. Glad the temp file path thing is not a blocker. I'd like to look into it this week if I can find the time.

I added a new config option in 3.9.0 that will hopefully work for both of you.


[TACHYON-1227] Added test cases covering the implementation of the ClientHandler class

https://tachyon.atlassian.net/browse/TACHYON-1227

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/6571/
Test PASSed.

@HorizonNet Thanks for the PR! We're always looking to improve our unit test coverage. It looks good overall, I've just left a few minor comments.

@aaudiber Thanks for the comments. I incorporated your feedback into an update for this PR.

+1 LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/6587/
Test PASSed.

LGTM


Fix an assertion caused by static plugins being duplicated in multiple dynamic libraries

Motivation and Context
It doesn't work the way I wanted it to work, back to the drawing board. Sorry!
A double-fix workaround for the following assertion, which was encountered very often by @ykarmesh (original Slack thread for reference: 1, 2):
Assertion inserted.second failed at .../src/Corrade/PluginManager/AbstractManager.cpp:276

As of mosra/corrade@ba9a173c9310cb82fdf0bc83622b4e6828ac67d9, this assertion is gone. However because duplicated static plugins likely point to something being wrong with the way the project is built, it's still a warning.
Then, to avoid the warnings, I changed the build system to only link the static plugins to the leaf executables / dynamic modules, not to every static library, which is how it should be. Linking them to static libraries led to them being compiled several times over, only for the extra copies getting discarded by the final link step, increasing compile times for no reason. And ultimately, linking the static plugins to both the Magnum and the Habitat Python module (starting in #1901) led to them being present in two (or even more?) copies when both modules get imported, which was the root cause for the original assertion. It doesn't work the way I wanted it to work. Needs further investigation.

@jrreyna & @ykarmesh -- if you want to have a quick fix for #1901 without merging all this waiting on this to be done, it should be enough to just git pull latest master in src/deps/corrade. You'll get warnings printed that way, but no assertion.
How Has This Been Tested
Even though I originally thought this is an impossible bug (sorry), I managed to reproduce the error in an isolated scenario, on all platforms. So it's a bit strange that @jrreyna wasn't hitting this on Mac.
Nevertheless, the removed assert makes it a non-fatal problem. Ideally the Python module should also not print any warnings related to duplicate plugins, please let me know if it still does. It'll print many warnings right now however, I need to figure out a different solution.

I'm now at a state where it's

either building and passing tests on the CI, but linking the static plugins to both Python modules, and thus probably causing PluginManager warnings on systems that are not the CI,
or not causing any warnings on systems that are not the CI, but failing on the CI because the Habitat Python module doesn't see the plugins linked to the Magnum Python module, dying on an error related to ObjImporter.

I'm going to leave this PR as-is for now, until I understand what's going on. The essential fix in Corrade is going to get included as part of #1901 instead.


Enhance List of Deployments

As a:
Deveoper/operator
I want:
To get a list of all the deployments associated to a service or any filters of my choice
So that:
So that I can observe what has been deployed and the associated information to the deployment
Implementation details:

Given an author (into src repo), display all the deployments created by them
[x] Provide the option to --watch the deployments for a live view  PR

Acceptance Criteria:
User is able to filter via author and also watch the deployments for a live view

Closing since cli enhancements are covered in other issues


Test Pydantic 2.0 to ensure nothing breaks

https://twitter.com/pydantic/status/1674820177005887508
It shouldn't since simpleaichat doesn't do too many shenanigans.
If all good, then should pin pydantic>=2.0 for next version since it offers a performance increase all around.

Per the migration guide several field names have changed (with the current ones depreciated) so changes + pinning will be necessary. Will have to do a full PR.

Done


Add new matcher toContainValue

What
New matcher toContainValue

Why
See #3
Housekeeping

[x] Unit tests
[x] Documentation is up to date
[x] No additional lint warnings

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      4    +2
  Lines           9     18    +9
  Branches        1      2    +1
=====================================
+ Hits            9     18    +9

Impacted Files
Coverage Δ

src/matchers/toContainValue/index.js
100% <100%> (ø)

src/matchers/toContainValue/predicate.js
100% <100%> (ø)

Continue to review full report at Codecov.

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


Integral symbol is rendered incorrectly in Firefox

Hi,
It seems to me that integral signs are rendered to small in Firefox. For example, this snippet: http://mathb.in/17534 results in the following:
http://venemo.net/owncloud/public.php?service=files&t=4019eefbc365c09d459f31919b154973
I'm not sure if this is an issue with mathb or mathjax, but thought it's worth reporting.

MathB.in now uses MathJax 3.2.2. The integral sign appears to be of the correct size with this version of MathJax.


Save Location

Resized images appears on Camera folder of Google Photos because images saved under a subfolder in /sdcard/DCIM. Could you move the subfolder to /sdcard/Pictures ?

I'll try if it doesn't break the save

I'll try if it doesn't break the save

I thought about it, and i will add fascility to pick output folder manually i think


Typescript syntax highlighting breaking on certain regex following !

VSCode Version: 1.43.0-insider (user setup)
OS Version: Windows 10 pro

Steps to Reproduce:

Fresh install of VSCode Insiders (Also occurring on stable)
Paste the following code into a file:

class Foo {
    public foo(): boolean {
        return !/[():\w]/.test('foo');
    }

    private bar(): void {}
}

Does this issue occur when all extensions are disabled?: Yes
Funnily enough, it appears this code breaks GitHub's syntax highlighting as well.
Escaping the parens will fix syntax highlighting on the remainder of the document, but the syntax highlighting on the regular expression itself is still broken. Removing the ! and not escaping the parens fixes everything, but obviously that completely changes the meaning of the code.
Here's the example above:

And here's the prominent example in my code that sparked this issue:

The last screenshot is from stable with all my extensions, however I can confirm it appears similarly broken on a fresh insiders install with no extensions.

Confirmed with the latest grammar from master

I gotta tell ya, this does not feel right at all:

But at least I can work again 🤷♀

Another potential solution would be to simply take the inverse of the character set in the regular expression itself, like:
if (/[^():\w]/.test(reader.peek(index)))
    return false;

I ended up using this a few times today in some new code, but this solution is of course not always viable.
Hope to see some resolution to this issue soon.

Funnily enough, it appears this code breaks GitHub's syntax highlighting as well.

Due to GitHub using this as their TypeScript syntax highlight grammar.

That makes a lot of sense.

The way I worked around this issue was to just add parenthesis around the expression:
!(/regex/.test(...))

Oh, I hadn't considered that under the assumption that it would throw warnings due to the no-extra-parens typescript-eslint rule but I tested it just now it looks like it doesn't. Good to know. Obviously a fix for this problem is still the desirable solution, though.

@sheetalkamat When you have a chance, can you or someone on the TS team please take a look at this. We're seeing a lot of reports on the VS Code side but I had trouble figuring out what's going wrong in the grammar

In VS Code v1.43.2, the issue and https://github.com/microsoft/vscode/issues/92904 does not seem to be resolved.


Allow changing color scheme

"Night mode" (all in red on black) comes to mind.

"Night mode" (all in red on black) comes to mind.

Indeed.
See Stellarium for a working example. Used by astronomers while observing.


soundness

For soundness, there are some dependencies like this :
header
account <- header
storage <- account <- header
transaction < - header
receipt <- header

For now for simplicity, we just get nearest dependent value from memorizer which we not sure if it's verified during the program. But also at the same time we just want to verify minimal time of value that used as possible. e.g adding header verification logic on sub child's verification doesn't make sense.
so what we need to do is we perhaps track parent dependency for soundness and at the last step we just verifies to ensure assumption that we took above is indeed correct.

resolved by #18


Suggestion for performance?

Question
Problem: when logging in to the app for the first time, thousands of objects are loaded from the server and each are cached with hive. Writing them all at once makes the UI freeze up (for as long as 10 seconds), even as async code in a service outside the UI.
The code to write the data is simple but ends up calling box.put over 25,000 times in some circumstances. The database has over 10,000 locations and each are cached individually (but they are fetched as a group). Each also has a timestamp for when it was last fetched.
Code sample
  void cacheResponse(T response) {
    box.put(_queryKey(response.cacheKey), response.toJson());
    _setQueryLastUpdated(response);
    _addCachedId(response.cacheKey);
  }

  void _setQueryLastUpdated(T response) {
    box.put(_queryDateKey(response.cacheKey),
        DateTime.now().toUtc().toIso8601String());
  }

  void _addCachedId(String id) {
    Set<String> allIds = _cachedIds();
    allIds.add(id);
    box.put(_idListKey, allIds.join(","));
  }

If I simply comment out the contents of cacheResponse, the app runs super fast again. So I've got some questions about how I could design this better and use Hive in a more performant way.

Would it be better to cache entire responses as 1 key? I have been caching each object within the response so far.
Would it be better to run cacheResponse in a different isolate?

Version

Platform: iOS + Android
Flutter 2.2.0
hive: ^2.0.4

It runs about 50 times faster with this, but I'd still be curious to see what you guys suggest in general
  void cacheResponse(List<T> response) {
    final cachedAt = DateTime.now().toUtc().toIso8601String();
    Set<String> allIds = _cachedIds();
    allIds.addAll(response.map((e) => e.cacheKey));

    box.putAll(
      Map.fromEntries([
        ...response.map((t) => MapEntry(_queryDateKey(t.cacheKey), cachedAt)),
        ...response.map((t) => MapEntry(_queryKey(t.cacheKey), t.toJson())),
        MapEntry(_idListKey, allIds.join(",")),
      ]),
    );
  }

hello u can use hive in isolate(it's require intitiate and use hive only in this new isolate), but it's solve ur problem


update max_file_uploads link

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
❌

Fixed issues
https://github.com/yiisoft/yii2/issues/18950

👍🏻


Add ability to read from ansible.cfg

Implements https://github.com/konstruktoid/ansible-hvault-inventory/issues/120

Could you run ruff and black on the code as well (https://github.com/konstruktoid/action-pylint)?

Done!


Add execution time in FileSystemMasterAuditContext

Address #13510 to show time spent for certain RPC calls in audit logs

Codecov Report

Merging #13511 (ecf1a50) into master (5721e85) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master   #13511      +/-   ##
============================================
- Coverage     43.78%   43.77%   -0.01%
+ Complexity     9048     9042       -6
============================================
  Files          1377     1377
  Lines         79867    79872       +5
  Branches       9708     9708
============================================
- Hits          34971    34966       -5
- Misses        41956    41962       +6
- Partials       2940     2944       +4

Impacted Files
Coverage Δ

...a/alluxio/master/file/DefaultFileSystemMaster.java
64.71% <0.00%> (-0.03%)
:arrow_down:

...uxio/master/file/FileSystemMasterAuditContext.java
28.94% <0.00%> (-3.41%)
:arrow_down:

...java/alluxio/worker/block/io/StoreBlockWriter.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...lluxio/client/metrics/MetricsHeartbeatContext.java
77.21% <0.00%> (-3.80%)
:arrow_down:

...lluxio/client/file/cache/store/LocalPageStore.java
75.28% <0.00%> (-2.25%)
:arrow_down:

...e/common/src/main/java/alluxio/metrics/Metric.java
58.33% <0.00%> (-0.84%)
:arrow_down:

...n/java/alluxio/master/metastore/caching/Cache.java
94.14% <0.00%> (-0.54%)
:arrow_down:

...ava/alluxio/multi/process/MultiProcessCluster.java
59.89% <0.00%> (-0.27%)
:arrow_down:

...main/java/alluxio/concurrent/jsr/ForkJoinTask.java
5.67% <0.00%> (-0.25%)
:arrow_down:

...main/java/alluxio/concurrent/jsr/ForkJoinPool.java
30.21% <0.00%> (+0.10%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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

jenkins, test this please

alluxio-bot, merge this please


Deployment fails because IGW is not attached before ELB creation

Attempting to run the deploy in eu-west-1 fails because at the time of load balancer creation the IGW is not attached yet. This seems to fix the issue
889f3bddac9:ZonalShiftExample [rudpot:ct-keyera:eu-west-1]
$ git diff
diff --git a/ZonalShiftExample/ARC-Zonal-Shift-Demo.json b/ZonalShiftExample/ARC-Zonal-Shift-Demo.json
index 9667060..db7035c 100644
--- a/ZonalShiftExample/ARC-Zonal-Shift-Demo.json
+++ b/ZonalShiftExample/ARC-Zonal-Shift-Demo.json
@@ -318,7 +318,7 @@
     },

     "ElasticLoadBalancer": {
-      "DependsOn": "WebServerIGW",
+      "DependsOn": ["WebServerIGW", "WebserverIGWAttachment"],
       "Type" : "AWS::ElasticLoadBalancingV2::LoadBalancer",
       "Properties" : {
         "IpAddressType" : "ipv4",

Makes sense, thanks.  Fixed in 42b514c179a6375f841245ab476f630cc74152b5


Update nc_sentinel.c

With Redis 4.01 the sentinel information changed, so a quick patch to have twemproxy + sentinel working is change the skipped lines from 3 to 4 on line 155.

Does this work in redis 3.2 and 3.0?

@diegotez Thanks for the patch!
@TysonAndre It looks like it ought to.
connected to an older Sentinel:
Connected to localhost.
Escape character is '^]'.
INFO
$2857
# Server
redis_version:3.2.6
redis_git_sha1:77de5c2b
redis_git_dirty:0
redis_build_id:1a9d3bc621cb3a9f
redis_mode:sentinel

@diegotez I didn't notice that you were making this PR against master at the time of reviewing.
Currently, we're developing against the build-nutredis branch for redis changes (Not that well documented).

Patches to the redis components (sentinel) didn't work in some edge cases alongside our patches to the memcache failover. We didn't have the resources to fix that, so we use separate binaries for redis proxies and memcached proxies.

I believe https://github.com/ifwe/twemproxy/pull/6 did the same thing, but was more robust for changes to line counts.


gpu donot work

clf = LGBMClassifier(**{    'device': 'gpu',
'gpu_platform_id': 0,
'gpu_device_id': 0,
'gpu_use_dp':True})

LightGBMError                             Traceback (most recent call last)
 in
37
38 data = lgb.Dataset(X, y)
---> 39 _ = lgb.cv(param, data, num_boost_round=10000, verbose_eval=1000)
/usr/local/lib/python3.6/dist-packages/lightgbm/engine.py in cv(params, train_set, num_boost_round, folds, nfold, stratified, shuffle, metrics, fobj, feval, init_model, feature_name, categorical_feature, early_stopping_rounds, fpreproc, verbose_eval, show_stdv, seed, callbacks, eval_train_metric)
527                             params=params, seed=seed, fpreproc=fpreproc,
528                             stratified=stratified, shuffle=shuffle,
--> 529                             eval_train_metric=eval_train_metric)
530
531     # setup callbacks
/usr/local/lib/python3.6/dist-packages/lightgbm/engine.py in _make_n_folds(full_data, folds, nfold, params, seed, fpreproc, stratified, shuffle, eval_train_metric)
346         else:
347             tparam = params
--> 348         cvbooster = Booster(tparam, train_set)
349         if eval_train_metric:
350             cvbooster.add_valid(train_set, 'train')
/usr/local/lib/python3.6/dist-packages/lightgbm/basic.py in init(self, params, train_set, model_file, model_str, silent)
1634                 train_set.construct().handle,
1635                 c_str(params_str),
-> 1636                 ctypes.byref(self.handle)))
1637             # save reference to data
1638             self.train_set = train_set
/usr/local/lib/python3.6/dist-packages/lightgbm/basic.py in _safe_call(ret)
45     """
46     if ret != 0:
---> 47         raise LightGBMError(decode_string(_LIB.LGBM_GetLastError()))
48
49
LightGBMError: Out of Host Memory

This is failing before it begins training. It is trying to convert your dataset into the internal LightGBM format and running out of memory. This might fail whether you use device': 'gpu', or `device': 'cpu'.
Have you considered using the use_two_round_loading parameter? It will help prevent a memory explosion when loading data.

I think the error message is quite clear and self-described. It comes from OpenCL and indicates the lack of GPU memory. It's possible that your model is very large and cannot be fitted into memory.


feat: change edge case for s3 key for badger tree

Need merge this changes to the api along with @axejintao


Kyle Yu: Assignment 3

You have accidentally added the .Ds_Store file, please delete that and push again.


Thank you

@JackHack96 I just want to say THANK YOU. For two years I was suffering with shitty sound because of Beats Audio and nothing helped when I tried to fix it. But today I've installed PulseEffects and imported yours presets, and I'm no longer suffering from shitty sound.

I'm glad it helped you!

I'll ride on this issue to also say a personal thank you (cause it's already closed).
All of the settings in wwmm's PulseEffects legit made absolutely zero sense to me.
Despite wanting to improve my listening experience, I don't understand sound effects at all.
So I just spent aplenty on quality headphones and earbuds, and I simply assumed those would be the best quality that I could ever achieve; unless I wanted to fork out more for one of those for-professional gears or whatever.
So I was also somewhat glad there were community presets available (and linked in the repo's wiki).
Honestly, I wouldn't have bothered trying PulseEffects if there were no presets cause I would have no idea where to start anyway.
Like, even after seeing this repo, I was like, "What the frick is Convolver? ... IRS? What?".
And after trying Bass Enhancing + Perfect EQ from this repo, honestly I was like,... holy guacamole!
I feel like I've missed A LOT in the past few years. I repeat, A LOT!
So yeah, I wanna say thank you very much for these presets! 🙏
Like, I understand that wwmm's huge efforts on PulseEffects also made this possible.
But it's like one those sayings y'know, that even the most useful of things would simply become useless in the hands of those who coulnd't realize their true values, or something along that line..


Introduce namespace to environments

Environments currently have the concept of a server URI, but it is
ambiguous which cluster namespace to use.
This commit will introduce the concept of namespaces to the env
commands.
For example,
kubecfg env add staging http://mock-staging-uri \  --namespace=staging-namespace
kubecfg env set staging --namespace=staging-namespace
The default environment will use the namespace of the default context.
This commit will also update commands that take the  arg such as
apply to make use of the env namespace, if specified.
Fixes #148

Does this just set the default (fallback) namespace? (ie: what -n does currently)
In particular: what happens when objects declare an explicit namespace?  how will this feature behave when the objects span multiple namespaces, and/or includes non-namespaced objects (CRD declarations, ClusterRoles, etc)?  I see the code just sets the equivalent of existing -n, but various symbols are renamed DefaultNamespace -> Namespace and other changes that make the namespace more prominent - so I guess I'm wondering what the future intended semantics are here.
(I'd kind of like to see the reverse version, where we remove the legacy kubectl idea of an implicit "ambient" namespace, and instead make it always explicit via a convention around regular jsonnet parameters)

I brought up a related question in #148.
I agree with @anguslees that the default/overridden namespace treatment in kubectl is contentious, at times confusing or annoying. If you try to deal with manifests that already have a "metadata.namespace" field, you can leave off kubectl's --namespace flag or match the values of the "metadata.namespace" fields, which feels like a cruel game of needing to restate a predetermined answer.
In my project, I mandated that we maintain most of our Kubernetes manifest files with no "metadata.namespace" field, and that we'd use the --namespace flag with kubectl apply (or kubectl create) to project those manifests into one or more appropriate namespaces. However, that approach limits how you can use kubectl apply --prune, because you're more likely to want to throw files from multiple namespaces into the set considered for pruning. I'm now experimenting with going back the other way, with every manifest having a populated "metadata.namespace" field, and duplicating manifests that we used to share into a separate set for each namespace, backing away from relying on the --namespace flag.
That's still a separate matter from the namespace nominated in the KUBECONFIG file as "contexts.context.namespace." From both #148 and the changes considered here, we're considering adding something more like kubectl's --namespace flag to override the namespace designated by the current context.
Could we get away with @anguslees's "reverse version," where there's no built-in way to confine the target namespace?

@anguslees @seh The core issue right now is that an environment points at a specific cluster URI, but the namespace is populated by client-go. So, if you run apply us-west/dev and you happen to have namespace set in your $KUBECONFIG, the cluster points at us-west/dev but the namespace is pulled from current-context. This is quite likely to be not what you want.
In order for these commands to make sense, I think we to either:

Always override the namespace to be "" if it's populated from $KUBECONFIG, or
Allow users to specify their own namespace as part of the environment specification.

In the case of this PR, we're proposing to auto-populate namespace with whatever's in $KUBECONFIG's current-context. I could see us defaulting to "", but to not have any ability at all to specify namespace at the ksonnet app level, I think, is going to be a point of friction.

If you're not honoring the API server URL from KUBECONFIG, then you should not honor a namespace specified there either. That leans toward knocking it out with either "", or some weird sentinel like "ksonnet-nonexistent."
For cases where you're managing several namespaces in a cluster, specifying a singular "target" namespace doesn't make any sense. For cases where you're managing a single namespace, then it does make sense, and could even be necessary if the materialized Kubernetes manifests lack a "metadata.namespace" field. However, you could instead mandate that that field be populated in order to have this tool use such manifests.

I completely agree that there are applications where we don't want to have namespace set, and this proposal does support that.
But, another goal is to work out of the box with existing k8s apps, so I'm uncomfortable not supporting namespace as part of an environment spec, since a nontrivial set of people would have to change a lot of code in order to get the desired effect. Besides, we also allow the --namespace flag, so it's not like we don't allow people to specify this anyway.

I didn't mean to suggest that you eliminate a target namespace from the environment specification. I wanted to make it clear that an environment should completed occlude using values out of a KUBECONFIG file.
If the environment can designate a target namespace, but not require that one be set, that would satisfy my concern. I'd like it to behave such that if I set no namespace in my environment, and I attempt (accidentally) to operate on an object whose manifests lacks a populated "metadata.namespace" field, the operation would fail.

I think we're all in firm agreement on the big picture: if we are going to supply an ambient namespace, then it should be from environment not ~/.kube/config.  So in that sense, lgtm.
@jessicayuen: My understanding is that the current code does use the namespace from the current active KUBECONFIG context (if there is no more-explicit -n cli arg), and I thought this test confirmed that behaviour.  Do you see otherwise? (is the test broken/insufficient?)
@seh: The kubecfg code has to explicitly handle missing metadata.namespace and substitute the default namespace (for namespaced resources).  So it would be very easy, and robust, to change this behaviour to (eg) abort with an error instead if there was an object with blank/missing metadata.namespace.  I agree with @hausdorff that this would be surprising/upsetting to people who relied on this legacy implicit namespace behaviour of kubectl, but it's certainly something we could do.  (I think we have both groups internally at Bitnami fwiw - I know of one repo that relies on late-bound namespace for testing vs prod deployments, and another that has a CI test that rejects PRs with missing metadata.namespace)

Thank you for clarifying, @anguslees. I would like it if one could express in an environment either of two preferences:
• When a namespaced kind's manfiest's "metadata.namespace" field is absent, use this namespace.
• When a namespaced kind's manifest's "metadata.namespace" field is absent, fail.
We could implement that by treating a present, nonempty namespace in the environment as choosing the first preference, and the lack of a namespace in the environment as choosing the latter preference. Calling the environment field something like "default namespace"—though confusing due to the ever-present "default" Kubernetes namespace—would make it clear that the namespace is only used to avoid a failure that would otherwise occur.

@anguslees : I meant that the current code uses the current active context if there is no explicit (or implicit in the case of this PR) -n flag set. It is when the -n flag is set that defaultNamespace() makes less sense. It is even more so the case with this change, where the -n flag is set implicitly if there is a namespace specified in the environment.

Closing -- moved to the ksonnet repository.


Test resilience handling for the last replica timeout

Which issue(s) this PR fixes:
longhorn/longhorn#8711
What this PR does / why we need it:
Adds a robot test for longhorn/longhorn#8711.
Special notes for your reviewer:
Please feel free to take a close look at this one. I'm not super familiar with writing tests for the new framework, so I may have broken a convention.

Do we need to skip this test for OS other than SLES?

No. The iptables command is executed inside an instance-manager pod, which is definitely running a suse-like OS. I intended the comment there as a way to communicate that you can't use the iptables functionality inside other arbitrary pods.

@mergify backport v1.7.x


Improve moderation behaviors: reduce account-level alerts and improve UX around threads

Don't show account-level severity=alert blurs=none labels on the posts of users unless it's from the app's baked in moderation
Tune the UI of labels on posts & profiles to show who gave the label
Bundle blurred replies into a single element at the bottom

The code for this isn't exactly incredible so I'm open to discussions.
Tune the rendering of blurs=none labels
They now show who applied the label:

On a post
On a profile

Group together blurred items in threads
Threads now move blurred items down to the bottom and put them behind a single blur.

Before
After

If all of the items are blurred by account muting, the blur says "Show muted replies" and will show all of them with one click. If there are other reasons (eg labels) then the blur says "Show hidden replies" and will then show each item under their respective blurs.
Don't show account-level severity=alert blurs=none on the posts of users
Previously, an account-level label would show on all the posts of a user. This was creating a bit of an scarlet letter effect that's overly divisive. This update has the following effects:

Labels on accounts which 1. do not blur content, 2. are severity=alert, and 3. aren't from official moderation , will now ONLY show on the profile
Labels on accounts which blur content will continue to blur content
Labels on posts will continue to work as before

Put another way, if your account has a severity=alert blurs=none label on it, that only shows on the profile now -- not on the individual posts.

Before
After

To test
Start the dev-env. Log in as bob.test.

To test the labeling behavior, subscribe to labeler.test and then view threads.
To test the muting behavior, mute various users and then view threads.

This is a great iteration on the system as-is, and I definitely think it'll cause a lot less confusion when it comes to the UX being misinterpreted. I assume this also applies to quote posts 'inheriting' labels if the quoted user carries them, like so?

Only sticking points with the patch is that sometimes mid-thread, it's useful, say, were someone to be tagged at the account level for a certain behavior, call it Intolerance or Trolling, to name a couple, for labeler subscribers to still be aware of it if they want. Any thoughts on adding an optional toggle in the Moderation > Advanced section that can be set defaulted to OFF that instead reapplies the more aggressive in-thread label behavior as before? Or maybe making this configurable on the labeler's end, just spitballing, nothing too concrete but just getting my thoughts out as a labeler operator. Overall it's a good fix, I'd just worry about folks thinking that the labeler system "broke" because it no longer shows mid-thread, if that makes any sense.

the intent was to A) enable folks to filter posts from labeled users, via the hide setting

Gotcha, this I did not know, it's useful info to have as far as the intended use case of the settings.

enable neutral or positive labels, via the warn or show badge setting

This would be very useful as I know a couple labeler services are experimenting with value-neutral, informational labels (like "verified" tags) and it'd be good to be able to have one that isn't intended solely for content attrition

Overwhelmingly the effect is to make me view the person in a negative light (scarlet letter effect) which I think may worsen rifts between people.

Very true, this has been somewhat upsetting to see as it was also an unintended use case as far as the labeler's end as well, even as it pertains to a moderation-focused service. Ideally these were purely 'caution' signs if someone was exhibiting a behavior pattern and are intended to be appealed when there's a cessation of said behavior but that doesn't seem to be how folks are using our systems currently, will advise the team on maybe putting out some documentation on this

Rather than directly showing the label, I wonder if we ought to adopt a slightly more neutral phrasing (something like "1 label by X") which you then see in a modal when you tap to open.

On this one I would offer some pushback if only because when neutral or positive affect labels are assigned (eventually), it's an additional step to finding said info and, depending on the use case, people may see "1 label by [x]" and if it's primarily a moderation focused labeler, may misattribute that to effectively replicate the unintended Scarlet Letter effect you mentioned (i.e. "there's A Label on this account and therefore it must be a bad one")

It's why I think our approach to blocks has been the right call.

Wholeheartedly agree, the complete cauterization of info flow is very useful at deterring that sort of unpleasant behavior and it's one of the best changes you've implemented over other iterations of the feature

What have we wrought

We're going to need to tweak this PR to continue supporting that. Some scattered thoughts.

We could tweak it so severity=inform labels always show on posts but severity=alert labels don't. (To answer your question above about the "1 label by [x]" on the profile, I'd do the same there.)
We really ought to be showing who the badge is from. This is unfortunate because also...
The badge is taking up a fair amount of space right now.

I'm going to play with it a bit.

Ideally these were purely 'caution' signs if someone was exhibiting a behavior pattern

Yeah I really don't know if we can make that usecase work because of the realities of how it comes off. I think labeling an account entirely is useful for the "hide" behavior but showing any kind of warning on the posts is just a lot. I was debating a small ⚠ icon which expands to show the alert labels, but in some ways that's even worse.

On this one I would offer some pushback if only because when neutral or positive affect labels are assigned (eventually), it's an additional step to finding said info and, depending on the use case, people may see "1 label by [x]" and if it's primarily a moderation focused labeler, may misattribute that to effectively replicate the unintended Scarlet Letter effect you mentioned (i.e. "there's A Label on this account and therefore it must be a bad one")

Yes I agree, and I'm inclined to make the neutral or positive ones show fully and only negative ones go behind a grouping. I might special case some of our official labels though -- impersonation for instance is a pretty important badge to be showing.
I think there are very useful and fun things that can be done with neutral & positive labels. The "verified" badge is a bit... hm. It might work if we indicate who did it, and I quite like delegating the power of verification. The question is whether it can go systemically awry, but for labeling I have a strong philosophy of allowing some risk of downside in order to give room to the potential for upside.

Tuned label rendering to be a little smaller, a little roumder, and to show who applied the label.
On posts:

Feed
Expanded

On the account:

Modified the logic of when a label shows. This is the comment in the code:

The issue we have with labels on accounts is that 'negative' labels are showing everywhere, acting as a kind of "scarlet letter" punishment, when their intent is to just enable users to hide other users that are causing issues. Labelers don't have a way to express that an account-level label shouldnt show on every post.

However, there are some cases where we really do want to show the labels:

When the label is informational or positive (like "Verified")
When the label is crucial (like "Impersonation")

The solution we're applying FOR NOW is to hide severity=alert labels on accounts when looking at posts unless they're from the app's baked in moderation.

The labeling system will need to be expanded to improve this situation. See https://github.com/bluesky-social/atproto/issues/2444

Hey Paul,
I think there's actually some really good value to the "scarlet letter" effect.
example: at://did:plc:p3dhh5eapbqv6zugzvq7itkm/app.bsky.feed.post/3kqy2oppfts2p
This kinda behavior is exactly what negative labels are meant to prevent, someone jumping in a thread and being overtly problematic and is the entire point of the account. This change would also seemingly make lists more powerful than labels since lists would still have the scarlet letter effect to them. Yes, some labels (and lists) are negative. And they probably should be. It's a warning sign to people that would be affected by the behavior in question.
Additionally, even with positive or neutral labels, labels still seem to have a scarlet letter effect: https://bsky.app/profile/erinbiba.bsky.social/post/3kqygolvjks27
maybe this is just because positive/neutral labels are "newer" than negative labels, but it's happening.

Hm! Challenging issue.
I personally believe in de-escalation and separation in the context of social networks. The way I see it, social has a natural draw towards conflict. To fight that, I think we have to err toward de-escalation.
My concern is that the utility of the scarlet letter is less than its potential to induce conflict. It's extremely embarrassing to be tagged like that, and I don't want to create an atmosphere of aggregate grievance. My ideal would be: when somebody crosses the line with a community of users, they get removed from the space and that's the end of it. My fear is: we scarlet letter a bunch of people and their grievance grows into a backlash.
To some degree I think we may need to answer this by giving more control to the labelers, so they can make these calls, but I also don't want to pass the buck by just pushing it onto others. I figure I should at least weigh in as a participant before I default to "yall decide."
If the full answer really is "give this power to the labelers to decide," then my immediate question is -- should we leave it until the labelers have that power (which will take more dev work, so it'll be a bit) or should we enact this change in the interim?

This is gonna be a doozy of a writeup but I have some thoughts on this mechanically.
I think there's a lot of good points here, but if I can be frank, I think a lot of this is through the lens of a broader top-down approach when I believe that looking at this from an end user's angle is possibly more beneficial to understanding how this dynamic evolved and how the divergence in use cases emerged.
 Yes I'm using your own title, but bear with me. Let's say Turbo Dudes are often brigaded by extremely vitriolic and hateful people, solely because they are Dudes who are Turbo. This is an undesirable interaction for you as a user, so you seek out ways to mitigate your exposure or contact with, well, let's call them Dudephobes. A labeler is developed by another Turbo Dude that says it will place a Dudephobia warning on these sorts of people ahead of time so that you might see that much less, provided they do their job well. You subscribe to said labeler, on the default settings (Warn) and so now, whenever you wander into a thread, there's now visible warning signs on users who are Dudephobes. You have a couple of options here as a user. You can:

Leave it set to Warn and just give these guys a wide berth when it comes to your interactions with or around them, if at all (anecdotal evidence shows most users will leave most everything on Warn, perhaps out of morbid curiosity or out of an interest of seeing if someone got falsely flagged, which does happen). From there they tend to apply individual blocks as-needed.
Set it to Hide (anecdotal data has found that very few people are actively doing this) and never see a Dudephobe again, even though they definitely exist, can still see your profile, and still harass you in now-hidden comments but only for your app view. We'll note that in the above example, it can sometimes create this effect where folks, well intentioned or otherwise, engage the Dudephobe in a hostile manner, effectively escalating said situation and creating a firestorm in your replies that, because of your settings, you have no idea is happening.
Use the labeler's unique hybrid moderation model and set the Dudephobes moderation list to Block, effectively cauterizing that interaction and creating the community expulsion feature you mentioned. Anecdotal data shows this is the least likely course of action, probably because, again, users are incentivized towards conflict because of both past and present experiences on social networks.

Let's sit with that last point because I think it also paints a salient picture of why, for instance, the most popular labeler services at present are designed to remove content from a user's timeline, rather than categorize it on a more neutral basis:
For a certain subset of users, typically marginalized users, they are not seeking de-escalation, per se. They're not looking for a fight, either, though they'll definitely put one up if backed into a corner. They want a walled garden. The Posting Garden of Eden. It's why browser extensions like Shinigami Eyes and Soupcan exist and are very popular with this subset - people do not want certain folks on their feeds, and will actively seek out methods to identify and excise them, and this is the exact demographic which moderation labelers like Aegis, Taurus, etc. serve and, in their hopes, protect.
It's also one of the things myself and other operators of the Aegis system have ruminated on in the past month - if the moderation provided at the site level was sufficient to meet this need for a safe space online, our service would not be the most popular labeler at this point in time, nor would any moderation labeler. In other words, users are demonstrating that they want MORE controls and measures to lock down their experience, rather than open it up. This isn't just in our cluster, either, the system is utilized by everyone from newskies to 100K+ follower accounts, as our reports and posts showing off the labels in action have shown.
This also explains why the Scarlet Letter effect kicks in, or rather why it seems to escalate tensions. If you consider the user profile of someone who, for instance, gets an account level label of Dudephobe applied, this typically happens not because they were sitting in their own cluster, minding their own business - labelers with human driven operation don't often "see" content like this outside of their scope. They tend to get these labels because they demonstrate a repeat pattern of engaging in unwanted ways with communities who do not want to deal with them - thus the labels, for some users, are this:

ideal would be: when somebody crosses the line with a community of users, they get removed from the space and that's the end of it.

This is sort of the same dynamic that emerged with moderation lists, but with the ability to apply them with more precision (i.e. labels can go on the post level, lists can't): a few trusted services will emerge, reach wide adoption, at which point inclusion in that label set is, yes, an effective Excommunicado from a community. I also personally remember similar pushback with moderation lists when they first rolled out in May. But now I'm a member of over 250 moderation lists, and it doesn't quite phase me as much as it did way back when. So I guess my question, then, is this:
What, specifically, is the envisioned distinction between labels and moderation lists when it comes to their application to accounts?
Because if we think of them mechanically, they're identical right now at the account level - they apply to and mask everything a user posts, are indicated on the profile if someone is using the labeler or list, and are invisible to the user themselves otherwise, save for third party services or subscribing to the list/labeler yourself. They both lack the precision of a post level label, and both carry the weight, when combined with trust and adoption, of an effective scarlet letter, regardless of the labeler's intent (for the record, ours is one focused on disincentivizing that behavior by leveraging the label's perceived social power against the offending user - we often do appeal these when it's evident that the tagged user hasn't reoffended or expresses an intent to make amends in their appeal).
So what's causing the increase in perceived pushback? Perhaps looking at similar user sentiments in past PR's for mod lists back at their initial rollout could give us some perspective on the conundrum we're facing now. Maybe it's the misconception that labeler service labels are "official" or direct from Bluesky - in that circumstance, the suggestion to include the attribution of which labeler applied it in the UI itself might be the way to go. Or maybe it's just growing pains. Who knows.
Anyways, I rambled on quite a bit but I figured an extended peek under the hood and end user perspective might be beneficial at having a more holistic view of the situation while you weigh what path you wanna pursue.

My quick takes on the proposal, not replying to any of the other discussion:

big plus one to grouping the muted posts at the bottom
adding attribution to badge-labels is also good. we might need to use the handle of labeler account to avoid impersonation at some point? and/or have short vs. long names; want a very short name for this badge attribution
I don't love special-casing our mod service, and it smells like something that could stick around indefinitely
the current uses under mod policy that I can think off the top of my head are impersonation, spam, inauthentic, and misleading/scam. that is more than one label, which makes it feel like more of a category/pattern that just a one-off need.
I do think that generally account-level severity=alert / blurs=none should show on every post. the use-cases for that feel legit to me, and if it is being weaponized we should try to mitigate that another way (I haven't read the threads above which I think touch on this)
this is unearthing old complexity skeletons, but isn't this just the profile-record vs account-level distinction?
my intuition/preference would be to find a way to have the account alert badge still apply on every post, but have it visually be more obvious that it is account-level not post-level. and make the "inform" vs "alert" distinction clearer. a warning on the avatar has been thrown around, I think we don't love that? or something more "above the fold" or upper-right-corner. this UI design is hard to get polished/a11y/etc; if we don't have time to design this right now, we could keep the existing behavior and recommend/guide/document that folks name the account-level labels "Account Blah" to help make it clearer it isn't a post-level label? Not great.

Big picture, i'm not a hard-block on the proposal. I know paul has wrangled with this deeply and trust direction on this. I do think that we are still in the "how will folks use labels" phase; I think we definitely get to iterate on the semantics/behaviors/capabilities at least once in response to real-world use, but don't want to churn on it too much? Maybe this is novel enough to warrant a bunch of iteration though. :thinking:

this is unearthing old complexity skeletons, but isn't this just the profile-record vs account-level distinction?

Yeah, as it currently works, profile-level labels only show on the profile and not on posts. Account-level labels show on all posts and the profile.

my intuition/preference would be to find a way to have the account alert badge still apply on every post, but have it visually be more obvious that it is account-level not post-level. and make the "inform" vs "alert" distinction clearer. a warning on the avatar has been thrown around, I think we don't love that? or something more "above the fold" or upper-right-corner. this UI design is hard to get polished/a11y/etc; if we don't have time to design this right now, we could keep the existing behavior and recommend/guide/document that folks name the account-level labels "Account Blah" to help make it clearer it isn't a post-level label? Not great.

Ideally, playing off this last point, one could easily see a solution in noting that a label is done at the account level since that would be easy to see programatically. Would be pretty messy to do something like that on the ozone-side where labeler operators would basically have to duplicate their entire label set... Could keep the same format too Account: label-display-name

@EstrogenEmpress and @aetaric I appreciate yall sharing your thoughts about this. My beliefs about de-escalation are real -- but I'm not at all certain that showing the alert badges on posts is a net negative. I'm not the one experiencing the outcomes or living the same stakes. If you tell me showing the alert badges is a net positive, that's the feedback I'm looking for and I'm going to follow it! And if you end up changing your mind, I want to hear about that too!
I think for sure it's worth seeing how the other changes in this PR affect things first.

an idea I wanted to float here: what if moderation service's labels included a tiny icon of the moderation service's profile pic at the end of the bubble? you don't have to worry about impersonation since the user only sees labels for the services they've opted into anyway

an idea I wanted to float here: what if moderation service's labels included a tiny icon of the moderation service's profile pic at the end of the bubble? you don't have to worry about impersonation since the user only sees labels for the services they've opted into anyway

I like this idea too and Paul seemed open to considering it:
https://bsky.app/profile/pfrazee.com/post/3kqxs3fubo22i


Initial implementation for VR combat.

This doesn't quite work properly because controller.position doesn't actually line up with the hand mesh. I'm not sure how to get the exact position of the hands themselves. I'm also unsure if I'm doing the right thing with the world matrix transformation - should I even be applying that when I get the position of the controller?
Once we've got the postilion sorted I'll work on adding a velocity threshold.
Preview here: https://pr-361.lba2remake.net

Updated to use the correctly use the position of the handMesh so now everything lines up nicely. I'll work on adding a velocity threshold in a follow up PR.


ros# and MRTK conflict

Overview
Hi! I tried to import MRTK-unity after importing ros-sharp library. MRTK-unity and ros-sharp include a dll with the same name though their contents are different. Any idea to fix it? Here is the error aftering import MRTK-unity.

Unity Editor Version
2017.4.10f1
Mixed Reality Toolkit Release Version
2<IP_ADDRESS>

Just reverse the order. Install MRTK-unity first.


Importing from Excel

Community;
I would like to import excel data to a sql server table and then do some cleaning and staging. After cleaning I would like to move to another table. I will use stored procedure to move the data to the next table. Now I need to know how can run a command to first import and then run the stored procedure.
Thank you

Sorry, this is not a Serenity issue, nor question.


Gem::xxx deprecation warnings

Hi,
Gem::cache , Gem::source_index and Gem::SourceIndex are deprecated and rubigen uses them.
NOTE: Gem.cache is deprecated, use Gem::source_index. It will be removed on or after 2011-08-01.
Gem.cache called from /usr/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/rubigen/lookup.rb:284.
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:1139.
NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#each called from /usr/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/

I am getting a similar error in 1.5.7
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /Library/Ruby/Gems/1.8/gems/rubigen-1.5.7/lib/rubigen/lookup.rb:284.


[orge] Fix the function override problem under osx

Fixes https://github.com/microsoft/vcpkg/issues/31006
Fix the following issue to keep the return value and parameter types of the override function and the inherited function consistent.
/Users/vcpkg/Jim/vcpkg/buildtrees/ogre/src/v13.6.2-57c75b3e04/PlugIns/EXRCodec/src/O_IStream.cpp:42:18: error: return type of out-of-line definition of 'Ogre::O_IStream::tellg' differs from that in the declaration
Int64 O_IStream::tellg() {
~~~~~            ^
/Users/vcpkg/Jim/vcpkg/buildtrees/ogre/src/v13.6.2-57c75b3e04/PlugIns/EXRCodec/src/O_IStream.h:49:16: note: previous declaration is here
    uint64_t   tellg () override;
    ~~~~~~~~   ^
/Users/vcpkg/Jim/vcpkg/buildtrees/ogre/src/v13.6.2-57c75b3e04/PlugIns/EXRCodec/src/O_IStream.cpp:46:17: error: out-of-line definition of 'seekg' does not match any declaration in 'Ogre::O_IStream'
void O_IStream::seekg(Int64 pos) {
                ^~~~~
2 errors generated.

The usage and feature has been tested successfully locally.
A PR https://github.com/OGRECave/ogre/pull/2831 has been submitted upstream to fix this issue. Subsequent waiting for the upstream integration to release a new version can delete the patch submitted this time.

[X] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Please fix the port name typo in the titlle.


update platform-go-middlewares to 0.14.0

Description
Update platform-go-middlewares to 0.14.0
It will fix the error on the requests
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] 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
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #978 (8bddeae) into main (ff45299) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #978      +/-   ##
==========================================
- Coverage   30.83%   30.80%   -0.04%
==========================================
  Files          45       45
  Lines        5464     5464
==========================================
- Hits         1685     1683       -2
- Misses       3543     3544       +1
- Partials      236      237       +1

Impacted Files
Coverage Δ

pkg/services/devices.go
60.75% <0.00%> (-0.43%)
:arrow_down:

Continue to review full report at Codecov.

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

Test results are available in Ibutsu. The test run IDs are:
331fe5e3-dd7d-42dc-95ab-0988ef86c081
7ffb49d1-9073-4a9c-922c-a51308824d3e


Delete user submission GCP000839

By user request, please delete submission id '65eb3a8bdb8d9f000195c3f1'.
The user has re-submitted under a new GCP, so this submission should be deleted to prevent it being wrongly linked to publication details in future.
Study directories should also be deleted from staging (GCST90320043 - GCST90320045). Please let me know if I need to do this part.

@earlEBI the submission, BOW & associated studies have been deleted , you can delete the staging directory folders

I have deleted the directories on staging.


Update deployment scripts to automatically setup IdP

Purpose

Update the deployment to automatically setup IdP with the deploy target.

Goals

Update the deployment to automatically setup IdP with the deploy target.

Approach

Update the deployment to automatically setup IdP with the deploy target.

User stories

N/A

Release note

N/A

Documentation

N/A

Training

N/A

Certification

N/A

Marketing

N/A

Automation tests

Unit tests

N/A

Integration tests

N/A

Security checks

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

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

N/A

Test environment

N/A

Learning

N/A

Codecov Report

Merging #44 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #44   +/-   ##
======================================
  Coverage    25.7%   25.7%
======================================
  Files          45      45
  Lines        1058    1058
  Branches      158     158
======================================
  Hits          272     272
  Misses        723     723
  Partials       63      63

Continue to review full report at Codecov.

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


Fix GitHub Actions configuration

Bug Fix
Description
The GitHub Actions tox configuration was misconfigured such that no unit tests were actually running.
This was due in part to non-standard tox configuration conventions py3.6 vs py36. This PR uses the standard Python versioning that is available by default in tox.

https://tox.wiki/en/latest/config.html#tox-environments

Regression in

2d7151f5c2615517e6686576e1d53e0c89cfd549
#408

Also remove deprecated import that caused failure under Python 3.10
Why should this be added
Currently no unit tests are running on CI

This is a legitimate 3.10 testing failure:
    File "/home/runner/work/django-dbbackup/django-dbbackup/dbbackup/tests/testapp/urls.py", line 8, in <module>
      from django.conf.urls import include, url
  ImportError: cannot import name 'url' from 'django.conf.urls' (/home/runner/work/django-dbbackup/django-dbbackup/.tox/py310-django40/lib/python3.10/site-packages/django/conf/urls/__init__.py)

If this PR is ready I can merge

@johnthagen As quick note, all Jazzband members have the ability to merge PRs.
Being a project lead only provides the ability to create releases on PyPI.
Also, jezdez has added me as a project lead according to https://jazzband.co/projects/django-dbbackup


pip install cadquery

this make use of the recently added pip install cadquery
don't merge till the ci_with_install.yml and install instructiosn on the readme have been updated

conda build appears to be not working, but this bug has been reported elsewhere


chore(deps): :arrow_up: update dependency aws-sdk to v2.1319.0

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

aws-sdk
2.1318.0 -> 2.1319.0

Release Notes

aws/aws-sdk-js
v2.1319.0
Compare Source

feature: AuditManager: This release introduces a ServiceQuotaExceededException to the UpdateAssessmentFrameworkShare API operation.
feature: Connect: Reasons for failed diff has been approved by SDK Reviewer

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
curl: (18) transfer closed with 17886092 bytes remaining to read
Download failed: https://nodejs.org/dist/v18.12.1/node-v18.12.1-linux-x64.tar.xz
bash: npm: command not found


numpy RandomState.standard_normal needs int input

Hello,
I found a bug, which affects newer numpy versions (at least since 14.2 and 15.1):
The method standard_normal from RandomState class needs an integer input, otherwise a TypeError is thrown: TypeError: 'float' object cannot be interpreted as an integer.
https://github.com/acoular/acoular/blob/d207799adc423ba65f1bfe1e829c138cc9ace3d5/acoular/signals.py#L169
A possible fix is:
 s[ind:] += repeat( rnd_gen.standard_normal(int(round(nums / dind+1))), dind)[:lind]

Thanks for your great work on beamforming!
Andreas

Hi Andreas,
thanks for pointing this out! The PNoiseGenerator class was due for some updates anyway, but this will accelerate its priority.
Best regards
Gert

Issue is resolved now


[Snyk] Security upgrade alpine from 3.17 to 3.18.5

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to alpine:3.18.5, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

436
CVE-2023-6129 SNYK-ALPINE317-OPENSSL-6148880
No Known Exploit

436
CVE-2023-6129 SNYK-ALPINE317-OPENSSL-6148880
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

 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.


Add improved scene support to the person integration

Add improved scene support for the person integration by implementing reproduce state support.
To get started with this issue, you will need to set up a Home Assistant development environment. The easiest approach is to get started using a dev container.
Once you have a development environment set up, run the following and follow the instructions:
python3 -m script.scaffold reproduce_state

(This issue is part of #25681)

Person has no services. This does not apply.


Printing imported names

is this what you want for #78?
using EzXML
    docstr = """
    <?xml version="1.0" encoding="UTF-8"?>
    <root>
        <foo>ok</foo>
    </root>
    """
doc = parsexml(docstr)
show(doc)
> EzXML.Document(EzXML.Node(<DOCUMENT_NODE@0x000000001014d320>))

import EzXML.Node
show(doc)
> EzXML.Document(Node(<DOCUMENT_NODE@0x000000001014d320>))

Cool! This is the thing what I wanted.
Can you add a similar method to the Document type?

Yeah but you've only overridden Base.show function for 'Node' and 'StreamReader' type.
So it Document is already working like this on '0.7.0' 😃
using EzXML
import EzXML.Document

show(doc)
> Document(EzXML.Node(<DOCUMENT_NODE@0x0000000027c375f0>))

Oops, you're right.

Thank you for your pull request :)

Happy to be helpful:) Thank you for great package!


Raz/MGMT-1231

If user pass namespace argument update the default inventory-url to use bm-inventory under this namespace.

Thank you for your patch. Honestly, I like approach from #258 most.
Next time you can try git push --force to your branch when a PR is open here. Just prefix the PR title with WIP to avoid any confusions while you keep working on it.

Thank you for your patch. Honestly, I like approach from #258 most.
Next time you can try git push --force to your branch when a PR is open here. Just prefix the PR title with WIP to avoid any confusions while you keep working on it.

Right, will do next time.
Why would you like #258 more then this one?
I think that it is more organized like this but I can also reopen #258

Why would you like #258 more then this one?

Code-style reasons only. Two people, two opinions. In that case the function is never called twice and there is expectation that this won't change. The logic fits one line only. It is called directly from already "more" complex command decreasing readability. If you use the simple setting of env variable, the code readability is increased - a future maintainer will not need to "jump" but just read the script from top to bottom.

Why would you like #258 more then this one?

Code-style reasons only. Two people, two opinions. In that case the function is never called twice and there is expectation that this won't change. The logic fits one line only. It is called directly from already "more" complex command decreasing readability. If you use the simple setting of env variable, the code readability is increased - a future maintainer will not need to "jump" but just read the script from top to bottom.

Legit, fixed that.

Thanks!


Some of the assets in AssetLib have bad hash, unable to install and bring up error

Godot version:
3.1 stable and beyond
OS/device including version:
Win10
Issue description:

That should be reported on https://github.com/godotengine/godot-assetlib, it's not an engine issue.

Anyway, I fixed it.

Anyway, I fixed it.

How?


[Feature Request] Extended Checkbox states

Currently - [ ] and - [x] are supported states of checkboxes.
It would be useful to many to have a greater variety of states, each with their individual toggles in the settings regarding their inclusion in the plugin's consolidated list pane.
I am proposing adding support for:
Important
Proposed plaintext: - [!]
Could be placed at the top of the consolidated list by default.
Tentative
Proposed plaintext: - [?]
Could be placed at the bottom of the consolidated list by default
For those upcoming events that shouldn't be forgotten, but might not even happen.
Scheduled
Proposed plaintext: - [>]
In an ideal world, I would be able to use the Slated schedule command to turn a checkbox into this state via a secondary-click menu. Items with this state should not be shown, because their newly scheduled (unchecked) date will naturally be included.
Canceled
Proposed plaintext: - [-]
Canceled tasks would not show up in the consolidated list, but unchecked items could be changed to this state via a secondary-click menu.

I do not think these should be enabled by default, but for users of this snippet, it currently feels like a choice between more checkbox states and this extension. I would like to help change that. I understand this is not markdown spec, but I am not concerned with that in my vault.
Since an image may help convey this to anyone in a tl;dr mood:

Yeah I like this sort of idea, or at least a way to tag certain checklist items as important or otherwise. I'm initially a bit skeptical to do it based on the char that's inside of the check because in the rendered markdown that technically means the item is checked off, and you may want to indicate something as important that is still incomplete. I have been toying with the idea of something similar to iOS reminders, where you can prefix and todo with 1-3 exclamation marks to set priority.
e.g. - [ ] !!! do this thing would be the most important, and could reflect so in both styling and sort order in the plugin.
Would something like that move this in the right direction?

Ah I've never seen that in reminders, since it doesn't seem typing in the exclamation marks works. If reminder integration is planned, I think that would be a really cool direction.
Considering a lot of the code necessary to do that would not change, would it be possible to have user defined categories assigned to different prefix strings? - [ ] ? win the lotto could be my tentative prefix
Additionally sorting order could be defined by the user as list in a textbox in settings.
Default: !!!, !!, !
Example custom order: %&, !!!, ???, !!, ?? , &&, %%, !, ?

LogSeq supports priorities using essentially inline tags: [#A] (Or B or C). I came here looking to see if inline tags could be used to group or sort the tasks. I suppose any of these syntaxes would do the trick. There have been other syntaxes I've seen as well. I think FoldingText did @p1 and things like @due(2021-06-21) as well. Certainly add me to the list of interested parties.

nvm, that commit doesn't close this ^ All it does is add support for arbitrary characters inside a checklist (e.g. - [a] === - [x], which is a step in the right direction

I would also like to see the incomplete or in-progress style supported: - [/]


Is it possible to add country codes e.g. .au to an Eddystone URL frame?

Is it possible to add country codes e.g. .au to an Eddystone URL frame?
An example would be:  https://google.com.au
This would code as: 0x01, 0x67, 0x6F, 0x6F, 0x67, 0x6C, 0x65, 0x07, 0x2E, 0x61, 0x75
If this would be correct, what would we need to use as a termination character?

The compression codes, like the one you used for '.com' are entirely optional and can be used anywhere. There is no need for a termination character. Your URL as you've specified it is valid.

Scott, thanks for that, I sometimes take things too literally.  I like the ability to use short readable URL’s with the multitude of .com/xxxxxx that it entails with the full gambit of printable characters (90+) options for each subsequent character after the ‘/’.
I've been an assembler type person since the late 1980's and am enjoying my sojourn into the amazing world of C++.

Actually for a short URL path segment, you can only use exactly 79 ASCII characters.

Adrian, thanks for that update.

There is not coming back from this
On Jan 26, 2017 11:11 PM, "RussM4120"<EMAIL_ADDRESS>wrote:

Is it possible to add country codes e.g. .au to an Eddystone URL frame?
An example would be: https://google.com.au
This would code as: 0x01, 0x67, 0x6F, 0x6F, 0x67, 0x6C, 0x65, 0x07, 0x2E,
0x61, 0x75
If this would be correct, what would we need to use as a termination
character?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/eddystone/issues/201, or mute the thread
https://github.com/notifications/unsubscribe-auth/AX_276ltLJv5_VRfGVliiPLj9xGYx7x2ks5rWZipgaJpZM4LvfUa
.

I don't even think God wold forgive me
On Jan 31, 2017 6:28 PM, "Brandie Jackson"<EMAIL_ADDRESS>wrote:

There is not coming back from this
On Jan 26, 2017 11:11 PM, "RussM4120"<EMAIL_ADDRESS>wrote:

Is it possible to add country codes e.g. .au to an Eddystone URL frame?
An example would be: https://google.com.au
This would code as: 0x01, 0x67, 0x6F, 0x6F, 0x67, 0x6C, 0x65, 0x07, 0x2E,
0x61, 0x75
If this would be correct, what would we need to use as a termination
character?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/eddystone/issues/201, or mute the thread
https://github.com/notifications/unsubscribe-auth/AX_276ltLJv5_VRfGVliiPLj9xGYx7x2ks5rWZipgaJpZM4LvfUa
.


Improve LUISRecognizer/Recognizer connection

When IRecognizer moved to Recognizer abstract class it was slightly awkward with the way that LUISRecognizer works.  We need to review how it is integrated to see if we can make it smoother.
[bug]

The loader uses the syntax {path} to get config information from the loader.  This looks like, but is not an expression.  To make it an expression you need access context which is not present in the loader.  If we defer it to later we would have the context, but the current code relies on endpoint/key/appid being resolved at creation time.  We also need to make sure changes don't break legacy code.

I'm also not sure whether Tom or Emilio are better to make these changes, so I added Emilio.


New info from systemd printed to logs

In the latest base images I now see additional info printed out when INITSYSTEM=on, this is actually pretty useful info to have, so I think it should be kept, just highlighting this.

I'm not sure why this started happening, we didn't change anything systemd related. Maybe it was an update.


Allow Guzzle 7.0

Etcd client is pinned to Guzzle 6.x. There is the 7.0 and 7.1 already released.
There should be an upgrade.

Hi, is there any plan to do this?


Fix D3D11 unbinding SRV/UAV resources with different mipmap ranges

Direct3D allows binding the same texture as both an SRV and UAV resource as long as the mipmap ranges differ between the two.

wrong repo


No checkpoints in replicator

I cherry-picked the use_checkpoints option of the BigCouch replicator into the master branch. I also added tests and mentioned it in the docs.
This is just a first quick stab. I need to check whether it needs more documentation/tests or not.

With CouchDB 2.0 this code should have merged. If not, please open a new PR.


List of available callbacks like onViewOpen

This is probably comming from my inexperience, but where can I find the list of all available callbacks like
onViewOpen
onSave
... etc?
I especially need callbacks for two events:
when buffer gets focus, cursor is inserted into buffer
and when buffer losts focus, cursor is removed from buffer

Any function with the PostActionCall() in it will have the callback from lua. Post function name has 'on' in front of it. eg function name Save() becomes onSave
Here is a list below if you do not want to look in the source code.

onSuspend
onBackspace
onMousePress
onDeleteWordRight
onPageDown
onScrollUp
onDeleteWordLeft
onCursorPageUp
onScrollDown
onDelete
onHalfPageUp
onCenter
onIndentSelection
onHalfPageDown
onCursorUp
onOutdentLine
onToggleRuler
onCursorDown
onOutdentSelection
onJumpLine
onCursorLeft
onInsertTab
onClearStatus
onCursorRight
onSaveAll
onToggleHelp
onWordRight
onSave
onClearStatus
onWordLeft
onFind
onToggleHelp
onSelectUp
onFindNext
onToggleBindings
onSelectDown
onFindPrevious
onShellMode
onSelectLeft
onUndo
onCommandMode
onSelectRight
onRedo
onQuit
onSelectWordRight
onCopy
onQuitAll
onSelectWordLeft
onCutLine
onAddTab
onStartOfLine
onCut
onPreviousTab
onEndOfLine
onDuplicateLine
onNextTab
onSelectToStartOfLine
onDeleteLine
onVSplit
onSelectToEndOfLine
onMoveLinesUp
onHSplit
onParagraphPrevious
onMoveLinesDown
onUnsplit
onParagraphNext
onPaste
onNextSplit
onCursorStart
onPasteAll
onPreviousSplit
onCursorEnd
onSelectAll
onToggleMacro
onSelectToStart
onOpenFile
onPlayMacro
onSelectToEnd
onStart
onSpawnMultiCursor
onInsertSpace
onEnd
onSpawnMultiCursorAtMouse
onInsertNewline
onPageUp
onSkipMultiCursor
onRemoveMultiCursor
onRemoveAllMultiCursors

Any Function with PreActionCall() in it will have the callback from lua. Pre function name has 'pre' in front of it. e.g function name Save() becomes preSave
same as list above but change on to pre

Look in file cmd/micro/lua.go if you need any golang functions from lua.

I didn't understand how these events are created, now, reading actions.go I know, thank you.


SITE: Add shipment entry

CMO send a message to SITE that an order changed it's status from "Approved" to "In Preparation".
SITE adds a new shipment entry in the database and mount the shipment DSU.

This may be invalid due to business process flow change


How do I serve static files

I apologize in advance for this newbie question ...

serves up static files with grace and aplomb (and also appropriate mimetypes)

How do I do this?  I don't see any option for static paths.  This is my set of options I'm using now...
http.createServer(beefy(
  entries: '/client-app': 'client/app.coffee'
  cwd: __dirname
  live: true
  quiet: false
  bundlerFlags: [
    '-o', "bundle.js"
    "-t", "coffeeify"
    "--extension", ".coffee"
  ]
)).listen 1340

Never mind.  I was using the wrong directory to serve from.


Upgrade compatibility to Arc 2.8

Arc 2.8 just dropped. Make sure new dev branches are using 2.8.

We are now on 2.9.2 I think. It looks like the toolbar is mapped to 2.6 or later.

The toolbar is on version <IP_ADDRESS>739 of the SDK. Did you want to restrict the toolbar compatibility to just ArcPro 2.9 or later? I've been testing with the latest version, but it should still be compatible with 2.6. After 3.0 drops, are we going to target 2.x or 3.x?


"odo storage list" doesn't honour "--app" or "--project" flags

[kind/bug]

What versions of software are you using?

Created a storage using odo storage craete.
List the storage with odo storage list command for app and project that don't exist.

Actual behavior
odo storage list shows storage even if we specify an app or project that's not existing on the OpenShift cluster.
$ odo project list
ACTIVE     NAME
*          myproject

$ odo app list
The project 'myproject' has the following applications:
NAME
app

$ odo config view
COMPONENT SETTINGS
------------------------------------------------
PARAMETER         CURRENT_VALUE
Type              nodejs:latest
Application       app
Project           myproject
SourceType        local
Ref
SourceLocation    .
Ports             9090/TCP
Name              nodejs-nodejs-ex-kdab
MinMemory
MaxMemory
DebugPort
Ignore
MinCPU
MaxCPU

$ odo storage list
The component 'nodejs-nodejs-ex-kdab' has the following storage attached:
NAME          SIZE     PATH
mystorage     1Gi      /opt/storage

# so far, so good

$ odo storage list --app myapp    # there's no app named 'myapp'
The component 'nodejs-nodejs-ex-kdab' has the following storage attached:
NAME          SIZE     PATH
mystorage     1Gi      /opt/storage

$ odo storage list --project newproject    # there's no project named 'newproject'
The component 'nodejs-nodejs-ex-kdab' has the following storage attached:
NAME          SIZE     PATH
mystorage     1Gi      /opt/storage

Expected behavior
odo storage list should honour the additional flags and show storage belonging to a different app/project or throw an error if the said app/project doesn't exist.

/kind bug
/priority medium

@dharmit odo storage list doesn't have the --app and --project flags.
And for me its giving me an error when I run odo storage list --project asdf
$ odo storage list --project asfd
Error: unknown flag: --project
Usage:
  odo storage list [flags]

Examples:
  # List all storage attached or mounted to the current component and
  # all unattached or unmounted storage in the current application
  odo storage list

Flags:
      --context string   Use given context directory as a source for component settings
  -h, --help             Help for list

Additional Flags:
  -o, --o string             Specify output format, supported format: json (default "json")
  -v, --v Level              Log level for V logs. Level varies from 0 to 9 (default 0).
      --vmodule moduleSpec   Comma-separated list of pattern=N settings for file-filtered logging

 ✗  unknown flag: --project

The fact that it throws error when you provide --project or --app flags and it didn't throw any such  errors when I opened the issue, indicates that some PR between our respective attempts has fixed this issue. :laughing:
Closing the issue.


No stdin support

Currently RustyHermit and uhyve lack of stdin support. It would be great to have this feature for testing purposes.

libhermit actually has some kind of preliminary support for stdin. But Uhyve does not support this yet.
https://github.com/hermitcore/libhermit-rs/blob/master/src/fd/stdio.rs#L61-L70


Search count spell status

Add optional search count and spell status.

This implementation does not include search count nor spell status in the inactive status line.
I tested having search count in the inactive status line however I wasn't convinced it was useful when jumping around windows and doing different searches. More testing and usage is probably needed before making a decision to include search count in the inactive status line. I would appreciate your thoughts on this?
For spell status, it might be nice to display the window's spell status in the inactive status line, since each window remembers if spell is on or off and continues to display spelling errors when inactive (and spell is on). However, simply copying the current spell status implementation to the inactive window did not work, where the current active window's spell status was displayed in each inactive window. I have no idea how complicated it would be to have this work correctly. It's probably better to first test drive only having spell status for the active window, to see if it's really needed in inactive windows.
For the layout in the readme, I added a single section W, even though there is a separator between search count and spell status. I checked where separators are currently used, where for the right side found that they are used between sections X and Y, and, Y and Z. However for the left side found that there is only one separator between B and C. Note, I realise it wouldn't make sense to have a separator between A and B, so a separator is really only missing between C and D when mapping back to the layout sections. Then, I'm hoping it is okay to add a single section W which includes a separator within it.
I welcome any feedback on the above points, other implementation details, and added documentation.

Nice work.
Upon review all seems fine. W is correct for the section.
I agree with spell & search count being displayed only for the active statusline. It should be noted that I use Neovim 99% of the time, and I have global statusline enabled, so I don't really have inactive statusline in my setup (choice a personal choice).
I will give this a quick run and see if anything pops up. I will need to port this over to linefly.
I also need to implement Macro recording status for both plugins.
Thanks again, really nice PR.

After a test run, all good; very nice look too.

Thank you for merging! And thank you for the tweaks on the search count implementation.

I use Neovim 99% of the time, and I have global statusline enabled

It's time I got back to my Neovim configuration, will move to linefly and try the global status line.
If you have a few minutes, could you please explain what '%*' does?
Would you happen to have a good resource or reference for Vim script? Half a year ago I found a guide at IBM (developer, articles/tutorials) that I recall was pretty good, however the link seems dead now.

It's time I got back to my Neovim configuration, will move to linefly and try the global status line.

Global statusline is very nice since it now provides a full screen width statusline for the current window (there are no inactive statuslines). However, you do need to enable winbar to disambiguate windows. mistfly and linefly both have direct options for winbar, which appear is little tags at the top of each window split with mode indicator and filename. You can define your own winbar or just use the one provided by linefly.

If you have a few minutes, could you please explain what '%*' does?

Good question; it means end-previous-highlighting. mistfly uses coloring for some segments of the statusline and %* is a dictate to go back to the default statusline colors for the next segment (usually white text). '%#MistflyNormalEmphasis#' opens up coloring (using MistflyNormalEmphasis highlight group), and %* is used to end that coloring.
Looking at the mistfly code, I think through cut-n-paste %* is used far too much. I will audit and trim the usages back.
Good catch.

Would you happen to have a good resource or reference for Vim script? Half a year ago I found a guide at IBM (developer, articles/tutorials) that I recall was pretty good, however the link seems dead now.

An implied assumption is that I know Vimscript.
I know just enough to barely get by (and I forget it quickly too).
Nonetheless I have used these resources:

Vim scripting cheats
Vim Script for the JavaScripter (written by the lead developer of ALE plugin)
ChatGPT (quite useful for answering questions, including Vimscript)

I am a Neovim person, and I completely switched my entire setup to Lua last year. So that's another language to keep on top of. But in all honesty, Lua is a far better language than Vimscript. A little bit more verbose, but less quirky.
Side note, with Bram Moolenaar's very sad passing the Vim side of the equation looks uncertain (from my vista).

Thanks. Looking forward to trying the global statusline with winbar.

Good question; it means end-previous-highlighting

Ah ha. Thank you! My subpar search skills failed to solve my curiosity.

Looking at the mistfly code, I think through cut-n-paste %* is used far too much.

I added to that, trying my best not to break its usage :)

I will audit and trim the usages back.

I saw the cleanup. Nice.

Nonetheless I have used these (Vimscript) resources...

Cool. Much appreciated. Seems that it's time I tried out ChatGPT; I've been holding off.

I completely switched my entire setup to Lua

That is on my dot files to-do list. Although every time I check someone's Neovim Lua configuration, I 'holy heck' out loud.

Cool. Much appreciated. Seems that it's time I tried out ChatGPT; I've been holding off.

It is just another tool; sometimes it is useful, other times ChatGPT will actually lie.
I found it best to give it very short simple questions rather than bigger programming problems.
I use it like a personal StackOverflow, with the notion that ChatGPT could be lying to you (maybe around 30% of the time).

That is on my dot files to-do list. Although every time I check someone's Neovim Lua configuration, I 'holy heck' out loud.

If it is of any interest I converted my Vim (in Vimscript) setup over to Neovim (in Lua) and kept both in my dotfiles:

Vim vimrc and vim folder
Neovim init and nvim folder

Note, legacy Vimscript will always be supported in Neovim, so no harm in keeping a working setup. There are better ways to spend time.

It is just another tool

We had a presentation on tools like Copilot. Got to welcome these tools, rather than hide.

If it is of any interest I converted my Vim (in Vimscript) setup over to Neovim (in Lua)

For sure it is. Thanks!

There are better ways to spend time.

Ha, yeah. Although it must be satisfying once switched over. Plus the recent plugins seem to only have the Lua configuration example; although wrapping with lua << EOF ... EOF continues to work for me.


Fixes Part 2 of Issue 75

Fixed the second part of issue 75 where the GetCurrentUserRoles() method was not checking for the existence of the roleAttribute key in the CAS assertion's attributes dictionary. Also added documentation to the method.

Fixes #75


Failed to fetch

TypeError: Failed to fetch
 While processing action:
 function (dispatch, getState, api) {
    dispatch({
      type: _actionTypes2.default.LOADING
    });
    var chain = currentChain(getState());
    var showHidden = getState().wallet.settings.get('showHiddenAccounts', false);
    return api.emerald.listAccounts(chain, showHidden).then(function (result) {
      dispatch({
        type: _actionTypes2.default.SET_LIST,
        accounts: result
      });
      dispatch(fetchHdPaths());
      dispatch(fetchBalances(result.map(function (account) {
        return account.address;
      })));
    });
  }

MyEtherWallet (MEW) and Emerald Wallet are both client side applications to access ETC. A MEW user can easily migrate to Emerald Wallet by simply importing their ETC account's keystore file or private key in the Emerald Wallet.
Video links:
myetherwallet.com
github.com/etcdevteam/emerald-wallet
docs.etcdevteam.com
ETCDEV:
Our Team: https://etcdevteam.com/
Our Projects: https://github.com/etcdevteam/
Follow us on Twitter: https://twitter.com/etcdev
Become a DApp Developer: https://docs.etcdevteam.com/
More ETC:
ETC HQ: https://ethereumclassic.org/
Join ETC: https://joinetc.tech


Description of task appears when you hover over task name in menu

In order to provide a bit more information about what is contained within a task,  when one hovers over the task name before loading it from the Squid Task Library it would be helpful for the content of the "description" of that task to appear.  This will give the user more information about what is IN the task before opening it. For example a task name might specify 9pks but I cannot tell which 9 until I open it.  If the "description" was shown I would see it is for masses from 196-254, that helps me evaluate if this task is useful to me.   By doing it through the description, you do not encumber the file name with lots of detail.
On a related note @cross-a, the names of your existing tasks are not particularly meaningful (for example the Z1, Z2 thing is really unnecessary).  There might be some benefit to re-using the exact names that come with the pre-loaded tasks with Squid2.x  but this is also an opportunity to make them more concise and/or meaningful.  I don't feel strongly about either outcome but I thought I would bring it up in case you wish to revisit these names.

ETA - the description would appear whether you are loading from the Task Library, or loading any other .xml task (not in the library)

This latter request for a hover-description for any task.xml is not practical as that interaction would have to occur in the operating system's file opener - but:  we could have a 'peek' mode where you choose a task.xml and the description appears, and then you would have to decide to proceed to load; if not, repeat;

A peek mode sounds good to me.  It means an extra click to load a task but I think it is worth it to see what you are getting in advance.  Chime in @sbodorkos @cross-a @cwmagee if you disagree.

added in version v1.5.8


Instance $children can be undefined

Looks like $children array can be undefined at least then instance._inactive is true.
It causes this to fail with error:
backend.js:321 Uncaught TypeError: Cannot read property 'map' of null

should be fixed in https://github.com/vuejs/vue-devtools/commit/653cd33a9f3208a212e947f77f3112ac4f308883 - can you build locally to test it?

Quick check in devtools says me that affected instance had isBeingDestroyed: false. Thank you :)
Anyway, I will try to build it and test it. Will reopen it if something goes wrong.

It works great. Thanks again!


GoLand Run Configurations

Adds a number of GoLand run configurations, allowing developers to run and debug all Armada components from one IDE.

Fixes #
Special notes for your reviewer:

It would be great if you could add some docs for this to in the developer guide and verify that mage localdev full testsuite still works and you can access Lookout and Binoculars