Default child state solution does not work with ui-sref links

(follow up from #497)
As per the FAQs, to setup a default child state you merely have to set url: "" on the child.
That works well for href links, but nor for ui-sref ones, which has the side effect of also making ui-sref-active not work.
Plunkr: http://plnkr.co/edit/MhJael2qqrGtXe4VHsQO?p=preview

Since you are defining what you want to be the "default" state, you have to transition to that state. Default does not mean redirectTo. Thats a feature thats planned for the future. Using regular 'href' doesn't do the same even though it certainly appears to. It actually transition to the child state directly, as if you have put 'parent.childState' in a ui-sref.

I think I see the difference between default and redirectTo now.
So the FAQ entry about setting up a default child state can only ever work for href links, correct? An ui-sref link would always target a specific state and thus not work (and neither would ui-sref-active).

I was re-reading the original thread and as per @nateabele response to @pduey, this difference in behavior should not happen. Am I missing something here?

@filipesilva did you ever get to the bottom of this or find a workaround?
Its not clear if there is there in fact a gap in functionality to set a default child state with parent abstract state (when using ui-sref), or if this should be working.

No, I didn't get any further on this topic. At the moment I just use the redirectTo implementation described in https://github.com/angular-ui/ui-router/issues/1235#issuecomment-73538396, it's been working well for me in production so far.

I managed to work around by removing the abstract state and have the detail targeting the grandparent state.
Before:
.state('app.resources.products', {
  abstract: true,
  url: '/products',
  template: '<ui-view/>'
})
.state('app.resources.products.list', {
  url: '',
  template: '
Products list
'
})
.state('app.resources.products.detail', {
  url: '/:productId',
  template: '
Product detail
'
})

After:
.state('app.resources.products', {
  url: '/products',
  template: '
Products list
'
})
.state('app.resources.products.detail', {
  url: '/:productId',
  views: {
    '@app.resources':{
      template: '
Product detail
'
    }
  }
})


Malformed URL generation query parameters

Just spotted that the URL generation you have is producing malformed parameters.
So for example you have the following being produced..
[![Travis branch](https://img.shields.io/travis/rust-lang/rust/master.svg?maxAge=2592000?style=plastic)]()

Which should be..
[![Travis branch](https://img.shields.io/travis/rust-lang/rust/master.svg?maxAge=2592000&style=plastic)]()

Parameters after the first ? should be &. As far as I can see, this is effecting the Markdown generator.

Hope it helps :smile:

@karlbateman  Could you make a PR for this?

@e-cloud Sure, what do you need from me?

fix the logic generating the url 😄

Ok, I'll fork it.. when I get a mo, I will fix it 🚀

Could you point me in the direction of the component which is generating the URL?

I think it's here where it starts

Ta

@e-cloud Hey, I got working on this and have a fix in place, but I am not sure how to test it as I only have the style parameter being generated.

You can post a PR first, so that i can know what have been changed. Then, we can find a way for testing.

Thank you for reporting this issue!
I think it was fixed by 9ba76602c1cfdd3c5670c0c100f48b05759a6293.


Disable multiprocessing when dumping features in hubert preprocessing

The multi-processing works well on MFCC features. However, it sometimes makes the script hang when dumping HuBERT features. Change it to for-loop resolves the issue.

The multi-processing works well on MFCC features. However, it sometimes makes the script hang when dumping HuBERT features. Change it to for-loop resolves the issue.

Sounds like oversubscription issue.
What happens if you set the number of threads to 1?
https://jdhao.github.io/2020/07/06/pytorch_set_num_threads/

That's what I was using. OMP_NUM_THREADS=1
I was using it for training kmeans model with mfcc features, because there is some warning message shows
OpenBLAS Warning : Detect OpenMP Loop and this application may hang. Please rebuild the library with USE_OPENMP=1 option.

With OMP_NUM_THREADS=1, the kmeans method is working.
However, with OMP_NUM_THREADS=1, the script still hangs in the dumping hubert feature step.

oops, I misread the option. I used OMP_NUM_THREADS instead of OM_NUM_THREADS, let me try with it with multi-processing.

OM_NUM_THREADS is typo. OMP_NUM_THREADS is correct.


VideoTansaction.Builder methods should be public

Name says it all. If we try and use the transactions outside of the VideoActivity we can't use the build method to even create it

@gryffindor14: Quoting the documentation:

The only supported API at the moment is through CameraActivity and its IntentBuilder for still pictures and VideoRecorderActivity and its IntentBuilder for videos.

While there are other public classes and methods in the library, ones that may be exposed as part of a public API in the future, they are not supported at present.

VideoTransaction, therefore, is not part of the public API. I don't mind making fairly trivial changes like this, but please understand that what you are doing is not supported.

Addressed in v0.2.2.


Actions for UX Measurability and Improvement

We should enable us to measure some (anonymous) metrics about user behaviors and collect some feedback. This means Console as well as Customer Portal.
Why we should measure user behavior
Measuring user behavior helps us to improve the experience in ZITADEL for our users and our product strategy. Right now our UX improvement is a lot of guess work and not trial and error. With some reliable user data directly from our users we have more information that we can analyse.
Passive Metrics
Passive metrics describes any information that is recorded from ZITADEL automatically. This involves time spent on certain subpages or forms, to bounce points (where the user leaves a page (or ZITADEL)), to general customer/user numbers like how many users a customers has, how many use multi tenancy, who uses feature X, etc...)

[ ] #5311
[ ] #5312
[ ] #5313

Active Metrics
Active metrics involves everything where we actively asking customers and users for feedback. This can be dedicated user tests (as we did with the login, for example), surveys on social media, our website or on Discord. Or we could ask new customers if we can have a detailed debriefing with them after their going-live.
Another good approach would be to observe first time users.

[ ] Usertests with selected user groups
[ ] Surveys
[ ] Detailed debriefing with new customers after going-live
[ ] First time user observation

Additional

[ ] #5314

closed in favour of internal issue


Resume dump on failed restore

So unless there's some kind of way for us to detect whether go-lxc supports the feature or not, we won't be able to include that second commit in the stable branch due to it depending on a newer go-lxc.

I seem to remember us hitting this before for some other migration feature (was it the new Migrate API?).
Is there anything we can do with reflection or similar to detect this stuff?

It was with PreservesInodes, and I think you just didn't cherry pick it, right?

Yeah, that's the one. Was just wondering if there was something better we could do about those.

I'm not aware of anything; I don't think golang has conditional compilation for go code proper, just C :\

Couldn't use reflect with FieldByName to check whether the field exists in the struct from go-lxc?

Same "should" work for PreservesInodes too

http://paste.ubuntu.com/18828543/

You can, but I'd rather not :)


Dependency (fibers) is "gone forever"

It appears that fibers has revved versions and the older v1.0.6 is now "gone forever".
See: https://github.com/laverdet/node-fibers/issues/244
This obviously breaks things...

Thanks for the heads up. Upgraded the ref in 2.1.26.


Default assets

On buildnet, you can QA with this token: AS1dTb8iM9ED2adV6a26BMjg3sYQywiyLn33nJTRZ2fiY7FtRGSA
(total supply is 1, with 9 decimals, I can send you some if needed)
The tokens are sorted alphabetically to have a constant order each time, we will sort is by dollar value when it will be available

@pivilartisant on top of this Pull Request you can work on the dollar value display in the frontend, maybe on another branch

Several observations:
* The non-compliance with the principles of **Separation of Concerns** and **Open/Closed**, or **Protected Variation**, suggests that this PR introduces legacy, unclean code, and potential regressions.

* It is not explained how the publication of new assets will be managed without causing breaking changes.

That said, refactoring the code will likely be too burdensome given the deadlines.

Did you have a look at the following PR https://github.com/massalabs/station-massa-wallet/pull/933?


[bug] on JRuby, Loofah subclasses are broken

Please describe the bug
On JRuby, running Loofah's test suite:

  1) Error:
IntegrationTestHtml::html4 fragment::#to_text#test_0001_add newlines before and after html4 block elements:
NoMethodError: undefined method `scrub!' for #<Loofah::HTML4::DocumentFragment:0x6ac4f31d>
    lib/loofah/concerns.rb:121:in `to_text'
    test/integration/test_html.rb:58:in `block in IntegrationTestHtml'

  2) Error:
IntegrationTestHtml::html4 fragment::#to_text#test_0003_remove extraneous whitespace:
NoMethodError: undefined method `scrub!' for #<Loofah::HTML4::DocumentFragment:0x13bf5fd>
    lib/loofah/concerns.rb:121:in `to_text'
    test/integration/test_html.rb:76:in `block in IntegrationTestHtml'

  3) Error:
IntegrationTestHtml::html4 fragment::#to_text#test_0002_add newlines before and after html5 block elements:
NoMethodError: undefined method `scrub!' for #<Loofah::HTML4::DocumentFragment:0x138d978e>
    lib/loofah/concerns.rb:121:in `to_text'
    test/integration/test_html.rb:67:in `block in IntegrationTestHtml'

  4) Error:
IntegrationTestHtml::html4 fragment::#to_text#test_0004_replaces <br> with newlines:
NoMethodError: undefined method `scrub!' for #<Loofah::HTML4::DocumentFragment:0x7a22302c>
    lib/loofah/concerns.rb:121:in `to_text'
    test/integration/test_html.rb:85:in `block in IntegrationTestHtml'

1055 runs, 2084 assertions, 0 failures, 4 errors, 0 skips

Additional context
I'm pretty sure this is due to changes made in https://github.com/sparklemotion/nokogiri/pull/3117 to fix https://github.com/sparklemotion/nokogiri/issues/316.

This was closed by #3372 and that fix shipped in v1.17.2.


Fetching values for LOVs from backend

The evolutility backend offers an LOV endpoint. But in the frontend you use hardcoded lists for LOV fields, like this:
id: 'priority', attribute: 'priority', type: 'lov', label: 'Priority', required: true,
                    width: 100,  inMany: true,
                    list: [
                        {id: 1, text: '1 - ASAP'},
                        {id: 2, text: '2 - Urgent'},
                        {id: 3, text: '3 - Important'},
                        {id: 4, text: '4 - Medium'},
                        {id: 5, text: '5 - Low'}
                    ]

Is there a way to easily fetch the list items from the backend instead?

This feature is not implemented yet. I plan to do it (it is in evolutility-ui-react already).


Localization for exception messages

Could you please help me a little with localization stuff.
Configuration:

Web browser and its version: Firefox 48.0.1
Operating system and its version: Windows 7
PDF.js version: 1.4.20

Steps to reproduce the problem:
I am trying to reproduce issue with "Missing PDF file" exception (add some wrong letters in src for the pdf document file). If I am on en-US locale I see correct error translation when expand "More Information" button. But if I am change locale to different one - I see just one translated word (is "Message(Mensaje):") and the rest of the error still appear on en-US.
Could you please tell me are there some ability to reproduce this scenario on the "pdfjs DEMO" (using this link: https://mozilla.github.io/pdf.js/web/viewer.html) or could maybe you can describe me how exactly should the errors shown on the UI with different locales? Or maybe are there some another scenario and steps to reproduce any exception (unexpected Server error  etc.)?
Screenshot with English localization:

Screenshot with Spanish localization:

Thank you.

The "Missing PDF ..." message that is provided when clicking on the "More Information" button is the exact error as it comes from the API (in this case the worker side of PDF.js, see src/core/network.js#L484-L501).
Please note that the additional information provided by the "More Information" button is provided for debugging purposes and thus aimed at developers, rather than regular users, hence those messages are not intended to be translated. (Note that the "Missing PDF file" in the top left is translated, since this part is intended for regular users.)
Closing as answered.

Thank you very much!


Updated to allow subject name specification for schema registry

Updated to allow subject name specification for schema registry

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.58%. Comparing base (0e0f899) to head (bf362ba).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
- Coverage   90.64%   90.58%   -0.07%
==========================================
  Files          18       18
  Lines        1539     1550      +11
==========================================
+ Hits         1395     1404       +9
- Misses         94       95       +1
- Partials       50       51       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Does the live API still work?

I imported the zip into dialog flow and when I test it I get the response "I'm sorry but I can't find the price right now."
I'm getting the error Webhook call failed. Error: 400 Bad Request
Perhaps the webhook (https://us-central1-bitcoin-info-io17.cloudfunctions.net/bitcoinInfo) is no longer working properly or am I doing something wrong?

Thank you - But I'm no longer with Google and my hunch is that someone 'shutdown' this demo...


Removing duplicated release logic from catching pokemon

This logic is an exact copy paste from the ReleasePokemonWorker. Since that will be called on every tick as of https://github.com/PokemonGoF/PokemonGo-Bot/pull/1159, then we don't need this logic here.

Seems legit.
👍

👍


#697: Migrate to JSR330

Migrating to JSR330. Notable find: removed the bogus duplicate of the ArtifactResolver component in AbstractVersionsUpdaterMojo (there are two which point to the same component).
Using constructor-style injection, as advised in the reference.

@slachiewicz @slawekjaranowski please review

@slachiewicz why did you close it before merging?

@slachiewicz @slawekjaranowski please merge ;)

@ajarmoniuk was merged by direct push in commit: https://github.com/mojohaus/versions-maven-plugin/commit/a54e87fac6597d58eee14ec33c17590524836f48 instead of using GH gui
Another case for manual push is that this PR will be missing from auto generated releases notes.
@slachiewicz what is purpose for direct push it?

I see. Thanks for the explanation.

this time i was forking from command line, not from GH ui. I've updated, rebased change before push to test it locally.

maybe release note action configuration should be updated?

As I know release-derafter only take list of merged PR .. so we should process all important changes by PR with merged status ... 😄

i've updated release note with my merge PR plus few small styling updates

We will see what will happen after next release note rebuilds ... try to re-run Release Drafter action

all my changes dropped :( thx for explanation

@slachiewicz I've noticed that you're now trying to replace constructor-based injection with injecting fields. -- that is, placing the @Inject annotations next to fields. While this is certainly possible, it's not advised to do so as it's using reflection.
Please see https://github.com/eclipse/sisu.plexus/wiki/Plexus-to-JSR330#Basics

Yes, i expect that without constructors it will be easier to refactor code to not use deprecated classes from Maven 2.
Someone can migrate Mojo one by one.
Later we can introduce constructors with new proper parameters.


serde and (bevy) asset loading

Acceptance Criteria:

ASM is loadable from a ron file during runtime

Resolved by #8


Add WMR camera settings provider

Overview
Add WMR-specific camera settings provider.
A custom profile will be added to enable #6531 and https://docs.microsoft.com/en-us/windows/mixed-reality/mixed-reality-capture-for-developers#handle-the-additional-holographiccamera-render-in-unity

/azp run

Dependent on #6549

/azp run


fix: parse webVTT time NaN

Link to related issue (if applicable)
Sumary of proposed changes
If VTT time format is 00:00:15.792, it will be work,
but some VTT time has 00:15.792 format, it can not work.
Task list

[ ] Tested on supported browsers
[ ] Gulp build completed

Cheers 👍


Handle canMatchSearchAfter for frozen context scenario

Description
There is a corner case where sort is failing on nested field after this PR https://github.com/opensearch-project/OpenSearch/pull/7453. When nested field is date type and have filter in nested field has now() function call.
OpenSearch prevents SortFields' initialization in such cases more then one time.
This is very corner scenario but I added integ tests for that as we didn't have any integ test.
As a mitigation, I am pssing already initialized SortAndFormats in ContextIndexSearcher in this PR. In fact I also made change to invoke that if clause only if SearchContext contains searchAfter.
This happens only when nested_sort is having date field type and filter is having range along with now(). Culprit is the now() call that Opensearch is trying to avoid since now() should get called only once.
How to repro the issue
PUT test_sort_nested_date2
{
  "settings" : {
      "number_of_shards" : 1,
      "number_of_replicas" : 0
  },
  "mappings": {
    "properties": {
      "nested_field": {
        "type": "nested",
        "properties": {
          "date_field": {
            "type": "date",
            "format": "date_optional_time"
          }
        }
      }
    }
  }
}

POST test_sort_nested_date2/_bulk
{"index": {"_id": "1"}}
{"nested_field": [{"date_field": "2023-10-26T12:00:00+09:00"}, {"date_field": "2025-10-01T12:00:00+09:00"}]}

GET test_sort_nested_date2/_search
{
  "sort": [
    {
      "nested_field.date_field": {
      "mode": "max",
        "order": "desc",
        "nested": {
          "path": "nested_field",
          "filter": {
            "bool": {
              "filter": [
                {
                  "range": {
                    "nested_field.date_field": {
                      "gte": "now/h",
                      "time_zone": "+09:00"
                    }
                  }
                }
              ]
            }
          }
        }
      }
    }
  ]
}

This search query failes with below Exception,
{
  "error": {
    "root_cause": [
      {
        "type": "parse_exception",
        "reason": "could not read the current timestamp"
      }
    ],
    "type": "search_phase_execution_exception",
    "reason": "all shards failed",
    "phase": "query",
    "grouped": true,
    "failed_shards": [
      {
        "shard": 0,
        "index": "test_sort_nested_date2",
        "node": "WT1VH4gyTVGVZyi_tNMO-Q",
        "reason": {
          "type": "parse_exception",
          "reason": "could not read the current timestamp",
          "caused_by": {
            "type": "illegal_argument_exception",
            "reason": "features that prevent cachability are disabled on this context"
          }
        }
      }
    ]
  },
  "status": 400
}

Server side traces are corelated with canMatchSearchAfter where we are trying to initialize SortAndFormats again to get MinMax values.
[2023-10-21T12:21:59,877][DEBUG][o.o.a.s.TransportSearchAction] [bc908df47a785e9192f108cf1282c4e4] All shards failed for phase: [query]
OpenSearchParseException[could not read the current timestamp]; nested: IllegalArgumentException[features that prevent cachability are disabled on this context];
    at org.opensearch.common.time.JavaDateMathParser.parse(JavaDateMathParser.java:83)
    at org.opensearch.index.mapper.DateFieldMapper$DateFieldType.parseToLong(DateFieldMapper.java:510)
    at org.opensearch.index.mapper.DateFieldMapper$DateFieldType.lambda$dateRangeQuery$1(DateFieldMapper.java:464)
    at org.opensearch.index.mapper.DateFieldMapper$DateFieldType.handleNow(DateFieldMapper.java:493)
    at org.opensearch.index.mapper.DateFieldMapper$DateFieldType.dateRangeQuery(DateFieldMapper.java:459)
    at org.opensearch.index.mapper.DateFieldMapper$DateFieldType.rangeQuery(DateFieldMapper.java:434)
    at org.opensearch.index.query.RangeQueryBuilder.doToQuery(RangeQueryBuilder.java:527)
    at org.opensearch.index.query.AbstractQueryBuilder.toQuery(AbstractQueryBuilder.java:117)
    at org.opensearch.index.query.BoolQueryBuilder.addBooleanClauses(BoolQueryBuilder.java:346)
    at org.opensearch.index.query.BoolQueryBuilder.doToQuery(BoolQueryBuilder.java:329)
    at org.opensearch.index.query.AbstractQueryBuilder.toQuery(AbstractQueryBuilder.java:117)
    at org.opensearch.search.sort.SortBuilder.resolveNestedQuery(SortBuilder.java:245)
    at org.opensearch.search.sort.SortBuilder.resolveNested(SortBuilder.java:203)
    at org.opensearch.search.sort.FieldSortBuilder.nested(FieldSortBuilder.java:588)
    at org.opensearch.search.sort.FieldSortBuilder.build(FieldSortBuilder.java:411)
    at org.opensearch.search.sort.SortBuilder.buildSort(SortBuilder.java:166)
    at org.opensearch.search.sort.FieldSortBuilder.getMinMaxOrNullInternal(FieldSortBuilder.java:631)
    at org.opensearch.search.sort.FieldSortBuilder.getMinMaxOrNullForSegment(FieldSortBuilder.java:626)
    at org.opensearch.search.internal.ContextIndexSearcher.canMatchSearchAfter(ContextIndexSearcher.java:499)
    at org.opensearch.search.internal.ContextIndexSearcher.canMatch(ContextIndexSearcher.java:491)
    at org.opensearch.search.internal.ContextIndexSearcher.searchLeaf(ContextIndexSearcher.java:309)
    at org.opensearch.search.internal.ContextIndexSearcher.search(ContextIndexSearcher.java:295)
    at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:551)
    at org.opensearch.search.query.QueryPhase.searchWithCollector(QueryPhase.java:341)
    at org.opensearch.search.query.QueryPhase$DefaultQueryPhaseSearcher.searchWithCollector(QueryPhase.java:419)
    at org.opensearch.search.query.QueryPhase$DefaultQueryPhaseSearcher.searchWith(QueryPhase.java:408)
    at org.opensearch.search.query.QueryPhase.executeInternal(QueryPhase.java:263)
    at org.opensearch.search.query.QueryPhase.execute(QueryPhase.java:150)
    at org.opensearch.search.SearchService.loadOrExecuteQueryPhase(SearchService.java:527)
    at org.opensearch.search.SearchService.executeQueryPhase(SearchService.java:591)
    at org.opensearch.search.SearchService$2.lambda$onResponse$0(SearchService.java:560)
    at org.opensearch.action.ActionRunnable.lambda$supply$0(ActionRunnable.java:73)
    at org.opensearch.action.ActionRunnable$2.doRun(ActionRunnable.java:88)
    at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
    at org.opensearch.threadpool.TaskAwareRunnable.doRun(TaskAwareRunnable.java:78)
    at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
    at org.opensearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:59)
    at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:815)
    at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
    at java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.IllegalArgumentException: features that prevent cachability are disabled on this context
    at org.opensearch.index.query.QueryShardContext.failIfFrozen(QueryShardContext.java:521)
    at org.opensearch.index.query.QueryShardContext.nowInMillis(QueryShardContext.java:555)
    at org.opensearch.index.mapper.DateFieldMapper$DateFieldType.lambda$handleNow$2(DateFieldMapper.java:491)
    at org.opensearch.common.time.JavaDateMathParser.parse(JavaDateMathParser.java:81)
    ... 41 more

Related Issues
Resolves #11248
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@reta @msfroh @backslasht @sohami ^^ We hit the wild corner case :(

❌ Gradle check result for 7b8eeec: FAILURE

[org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/240_date_nanos/date with nested sort now}](https://build.ci.opensearch.org/job/gradle-check/30222/testReport/junit/org.opensearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_search_240_date_nanos_date_with_nested_sort_now_/)
[org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/240_date_nanos/date with nested sort now}](https://build.ci.opensearch.org/job/gradle-check/30222/testReport/junit/org.opensearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_search_240_date_nanos_date_with_nested_sort_now__2/)
[org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/240_date_nanos/date with nested sort now}](https://build.ci.opensearch.org/job/gradle-check/30222/testReport/junit/org.opensearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_search_240_date_nanos_date_with_nested_sort_now__3/)
[org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/240_date_nanos/date with nested sort now}](https://build.ci.opensearch.org/job/gradle-check/30222/testReport/junit/org.opensearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_search_240_date_nanos_date_with_nested_sort_now__4/)

Those are indeed flaky till we get it to 2.12 (backport)

@gashutos sorry but we have merge conflict here ...

@gashutos sorry but we have merge conflict here ...

Oops, resolved just now.

@gashutos could you please manually backport to  2.x? thank you.

Using the latest docker version (opensearchproject/opensearch:latest) fails with this error. Curiously the latest version in AWS does not.

Using the latest docker version (opensearchproject/opensearch:latest) fails with this error.
Thank you @lasiltan , that should not be the case, @gashutos could you please double check? Thank you.

The latest image is 2.11.1 version.
[gashutos@dev-dsk-gashutos-1c-2320b8cf ~]$ curl https://localhost:9200 -ku 'admin:admin'
{
  "name" : "e566097573d4",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "rKUWMmhWRZmleVAts-28VQ",
  "version" : {
    "distribution" : "opensearch",
    "number" : "2.11.1",
    "build_type" : "tar",
    "build_hash" : "6b1986e964d440be9137eba1413015c31c5a7752",
    "build_date" : "2023-11-29T21:43:10.135035992Z",
    "build_snapshot" : false,
    "lucene_version" : "9.7.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

This fix will be available in 2.12 release -> schedule.
For AWS managed OpenSearch services, we have different release schedule and we patched this fix to 2.11 AOS version itself.


Ignore case sensitivity with observation query parameters

What
Lower case all variable values relevated to a dimension in observation
endpoint. These variables can be found in query_paramaters,
dimensions or headers. The reason for doing this is so we can
compare request query parameters with data in mongo and neo4j without
failing to find expected data.
More specifically, the headers in a version document are stored in mongo
as defined by the original v4 file loaded into import process. Mean while the
dimension.names field stored against a version document are not
necessarily the same, as these get lower cased on input. These
dimension.name values are the ones our api users see and hence are
more likely to enter as query parameters. Also the neo4j dimension nodes
use the lower cased naming convention and hence querying the database
with sentenced cased dimension names leads to failure of finding
dimensions stored in neo4j therefore resulting in no observations found
where one would expect to find one or many.
How to review
Check unit tests pass and logical changes make sense.
Who can review
Team B

This line of work has been deprecated by https://github.com/ONSdigital/dp-dataset-api/pull/124


cannot import imzML

Basic information

My operating system and version: macos M1
My MZmine version: 3.9.0

What happened
Hi,
I cannot import imzML files saved from Cardinal (v3.2.1). However, imzML files exported via timsconvert (https://github.com/gtluu/timsconvert) load just fine.
I have noticed that timsconvert saves both mz and intensity values are saved as 64-bit float. Tried that with Cardinal but did not help either.
this is the error I get:  2023-11-03 09:50:09 FINEST io.github.mzmine.gui.MZmineGUI displayMessage Error - Error parsing mzML: java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because "accession" is null (ImzMLHandler.java:242) - null

Here are the dummy datasets I am using: https://drive.google.com/drive/folders/175O2I-N-rnYc7atHhbk-j7G6RIJhq9cy?usp=drive_link
Any suggestions on how to work around this issue?
thank you in advance

The files you uploaded are really small. Are the files from tismconvert as small?
For now i'd say just go with the files from timsconvert.
If you have a windows or linux machine, you can also directly import the tdf/tsf files.

HI,
thanks for the response. those are just test files (just a few points) for demonstration only.
The point of using Cardinal is for pre-processing and wanted to test mzmine for mz annotation.


ViewState is not implicitly saved in onSaveInstanceState(), and there is no hook to Flow to trigger a state save

In onSaveInstanceState(), a Flow Dispatch is not triggered, and as a result, the views' state is not preserved into the State objects, but onResume() triggers a REPLACE direction that would destroy the previous view along with its view state.
I personally added a package-internal class that manually places the view state into the InternalLifecycleIntegration's KeyManager, but it is not a canonical solution.
public class ForceBundler {
    public static void saveToBundle(Activity activity, View... activeViews) {
        InternalLifecycleIntegration internalLifeCycleIntegration = InternalLifecycleIntegration.find(activity);
        if(internalLifeCycleIntegration != null) {
            KeyManager keyManager = internalLifeCycleIntegration.keyManager;
            for(View view : activeViews) {
                State state = keyManager.getState(Flow.getKey(view));
                state.save(view);
                if(view instanceof Bundleable) {
                    state.setBundle(((Bundleable) view).toBundle());
                }
            }
        }
    }
}

Which I call in onSaveInstanceState()
@Override
protected void onSaveInstanceState(Bundle outState) {
    ForceBundler.saveToBundle(this, root.getChildAt(0));
    super.onSaveInstanceState(outState);
}

Personally I would expect a call to the changeKey() method in onSaveInstanceState() as that triggers state persistence, and this to be managed automatically through the KeyChanger.

Here's where BasicDispatcher does it in the sample: https://github.com/square/flow/blob/master/flow-sample-basic/src/main/java/flow/sample/basic/BasicDispatcher.java#L46
This behavior should probably just be added to KeyDispatcher

@edenman that's wonderful, but it doesn't run on device rotation.

@Zhuinden I just tested out rotation, seems to call save/restore on the screen view just fine...did you remember to set ids on all of your layout files?

@edenman ...seriously, I seem to have forgotten to add an android:id="@+id/custom_view" to my custom viewgroups. With that added, view state is persisted properly.
However, that doesn't change the fact that in order to save your state to a bundle instead of a BaseSavedState using View.onSaveInstanceState(), you'll have to access the State directly from the KeyManager.
Well at least now the custom view can handle it instead of the container in onSaveInstanceState(), and I don't have to worry about hacking the view state in myself, so that's neat.

I'm a little confused. @Zhuinden can you describe in high-level terms what you expect to happen that isn't happening?

Are you trying to force a state save?  If so, why?

@loganj the KeyDispatcher provides the State objects for the given context from the KeyManager and allows persistence to the State's Bundle parameter, however, the custom view itself has no means of persisting to the State's Bundle on its own. I personally did that here.
So there isn't really a simple way of saving to the State's Bundle directly for the given Context in onSaveInstanceState() from the custom view.

I see. The Bundle wasn't really intended for use by the view, but by the dispatcher. The use case motivating it was dispatchers who wanted to save non-view state alongside the view state.
Note that State#save uses View#saveHierarchyState-- your ViewGroup's children should already be persisted so long as they have IDs, there's no need to try to save them explicitly as your example does.

@loganj even then, I'm not sure what kind of state you can truly persist that runs on traversals, but not on configuration change. Essentially, I still don't see how to store the current key state to the state without actively forcing it in onSaveInstanceState(), as traversals don't run for onPause(). The previous keys had the chance to store their state to the State, but not the current key.

It sounds like the root problem here is that Flow doesn't allow saving state on lifecycle events. That's true. We've been handling lifecycle events outside of Flow, but it probably makes sense for Flow to handle that case for you. Tracked as #181.

Continuing in #181


SSO CAS is not working while returning back from CAS Server

SSO CAS was working fine before ubuntu security patch update. Once I update the ubuntu security patch, it is not working. Getting issue while returning back from CAS Server.
Getting below error:
<cas:serviceResponse xmlns:cas='http://www.yale.edu/tp/cas'>\n <cas:authenticationFailure code="INVALID_TICKET">Ticket 'ST-231187-6FE0JcCRd4viAFOKts5-p3XWaVH15QFwSNdE7NSwOMXdlMR8PL3tUlNBlgnXlPmCepbCpGGUIbDglJa2-cas.stetson.edu' not recognized</cas:authenticationFailure>\n</cas:serviceResponse>\n in /var/www/html/vendor/jasig/phpcas/source/CAS/Client.php:3278\nStack trace:\n#0 /var/www/html/vendor/jasig/phpcas/source/CAS/Client.php(1454): CAS_Client->validateCAS20()\n#1 /var/www/html/vendor/jasig/phpcas/ in /var/www/html/vendor/jasig/phpcas/source/CAS/Client.php on line 3278,

Your ST ticket is deemed invalid by the server. This may be many things:

Mismatch of the services URLs (User authentication vs ticket authorization) - check debug log for a different URL. This may be related to URL rewrites, http/https switch or load balancers etc.
You can check the CAS server side why this request fails. The CAS server log should have some info
Try a simple example to exclude any issues with the code

Please also be advised that the ticket shared in your original question might be valid despite implementation error (eg trailing domain name in the ticket).
It would be safe to warn your CAS team about a private ticket gone public, just in case.

@gboddin ST Tickets normally have something like 10s expiration... Should not be an issue.
https://apereo.github.io/cas/6.2.x/configuration/Configuration-Properties.html#service-tickets-behavior

Closing the issue due to no response. If you need further help please post more information and reopen the issue.

Closing the issue due to no response. If you need further help please post more information and reopen the issue.


Instagram Support for Ghost

Issue Summary
Many of the sites that Ghosst supports are adding media links to sites other than faebook and twitter. It would greatly improve the versitality of Ghost to expland the availble options. Other sites would include GitHub, YouTube. I am aware that themes exist to fix this but those solutions are "janky" at best. Alot of Ghost users are not as tech savy as others and this would halp improve the platform for those users.
Steps to Reproduce

Notify theme creators.
Add the option in the ghost admin pannel
Add it to the Ghost API.
Make sure this new type of theming is backwards compatable with old themes

Technical details:
Feature to improve ease of access for many Ghost users.

Hey @tjh2822  👋 Please do not use GitHub for feature requests. We use GitHub solely for bug-tracking and on-going feature development so we try to keep it noise free.
You can vote on this idea on the forum here: https://forum.ghost.org/t/additional-social-accounts-in-general-settings/750
FYI: Many projects have their own support guidelines and GitHub will highlight them for you, or the project owners will use issue templates to point you in the right direction, please read them before opening issues

Hey folks 👋 just in case anyone comes across this issue I added another idea to vote for in the forum https://forum.ghost.org/t/additional-social-accounts-for-authors/13725
It's specifically about authors but it might be what you were looking for @tjh2822 👍


Update sbt-typelevel to 0.5.0-RC9

About this PR
📦 Updates org.typelevel:sbt-typelevel from 0.5.0-M5 to 0.5.0-RC9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "sbt-typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel", artifactId = "sbt-typelevel" }
}]

labels: sbt-plugin-update, early-semver-pre-release, semver-spec-pre-release, version-scheme:early-semver, commit-count:1

Superseded by #87.


feat: add dynamic callstack for prevent the re-entrancy attack

Description

This PR based on the PRs below related the global API. please review first that.
https://github.com/line/cosmwasm/pull/182
https://github.com/line/wasmvm/pull/61
https://github.com/line/lbm-sdk/pull/500
Closes https://github.com/line/cosmwasm/pull/178
ditto. please read more detail in the above.
Types of changes

[ ] Bug fix (changes which fixes an issue)
[x] New feature (changes which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] ETC (build, ci, docs, perf, refactor, style, test)

Checklist

[x] I followed the contributing guidelines.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[ ] The PR title and commits are followed conventional commit form.

rebased to squash merged PR(https://github.com/line/wasmvm/pull/61).


Implement the repo API for source-build

Part of https://github.com/dotnet/source-build/issues/169

Ping! @mikeharder can you take a look? This is passing in the source-build PR now.


GEODE-2644: Cleanup config classes

Add LogConfigSupplier and some additional changes to LogConfig for
logging changes.
This is only part of the work for GEODE-2644. Aside from LogConfigSupplier and LogConfig, this PR simply removes warnings, renames variables, and fixes some comments.

I removed the AtomicReference from LogConfig. Sai and I had intended to delete it but I missed it before.


Is crocoite Linux-only?

Dear developers, it seems to me that the binary google-chrome-stable is hardcoded in crocoite and I believe that binary does not exist on macOS. I installed the Homebrew package chrome-cli and symlinked google-chrome-stable to chrome-cli, however, crocoite still won't run on my Mac. ("Exception: Chrome died on us.\n").
Will crocoite run at all on a Mac or is it Linux-only?
Thanks.

Honest answer is: I don’t know if it will run on macOS, because I have
not tested it.
I don’t think chrome-cli is the correct package though. crocoite expects
the binary google-chrome-stable to be the Chrome browser itself.  Not
sure where it’s installed on macOS, but on Gentoo Linux it resides in
/opt/google/chrome/ – this SO question might give you a hint:
https://superuser.com/a/157486

On macOS the Google Chrome binary resides in /Applications/Google Chrome.app/Contents/MacOS/Google Chrome. Symlinking /usr/local/bin/google-chrome-stable to there and running crocoite results in the same "Exception: Chrome died on us.\n" error.
For now I am assuming that crocoite won't run on macOS, and closing this issue. Thanks for the help!


Default cluster values configmap and kubeconfig

Towards https://github.com/giantswarm/giantswarm/issues/11656
This PR defaults the cluster values configmap and kubeconfig. Next PR will default the labels.

Tested on ginger.


Make temperature and humidty private

Add access functions for temperature & humidity to prevent writing to internal variable.

fixed in 0.2.0


Typo in description of JS switch statement

Challenge Name

https://www.freecodecamp.com/challenges/selecting-from-many-options-with-switch-statements
Issue Description

There is a typo in the description:

A switch statement tests a value and can have many case statements which defines various possible values.

@4rkz thanks for the issue. Yes, this needs to be changed so that defines is changed to define.

A switch statement tests a value and can have many case statements which define various possible values.

@erictleung you're welcome.

I'd like to fix this to start getting familiar with the code base and start contributing. I'll take care if this tomorrow 9/17/16

why is this bug still in help wanted? IF @TannerPlauche isn't working on this, could I?


Accessibility improvements

Settings: group items and add section headers

May be done better (especially integrating switch with the label but it may be improved in future versions of Compose), but it's already good to merge.

Thanks!


Excerpt way too short

Quick summary
The Excerpt is way shorter than 400 Characters
(The Excerpt also shows a Link)
Settings

Post

Steps to reproduce
Add Excerpt to the Posts
It's sometimes just two words
What you expected to happen
The Excerpt should be 400 Characters and without link
What actually happened
It's just two words with a Link (the Link isn't always there)
Impact
One
Available workarounds?
No but the platform is still usable
Logs or notes
Theme: Neve

This is often a problem with content that will be added to the excerpt (like sharing links and stuff) that will be ignored by Mastodon. Can you maybe share an example Post?

All my recent posts have the same issue https://g0v.social/<EMAIL_ADDRESS>(in Mandarin)

Could it be related to the use of the "read more" block?

Is someone interested in working on a PR?

Is it OK to completely get rid of the excerpt_more filter? It's already there since beginning so someone's custom template may depend on it.
Another option is to exclude the excerpt_more link from the word limit calculation.

what would you prefer?

I thought about using the wp_trim_excerpt instead of the current construct and to hook into the filters to set the length and the excerpt_more.
What do you think?

I made a proof of concept https://github.com/kanru/wordpress-activitypub/pull/1/files
Then I realized two points

wp_trim_excerpt() actually does nothing other than applying the wp_trim_excerpt filter, is this a bug? https://github.com/WordPress/wordpress-develop/blob/52854e2796bff1ab2e69991b1c233c277542a0fc/src/wp-includes/formatting.php#L3967
wp_trim_words() and thus wp_trim_excerpt() count words but the current [ap_excerpt] shortcode counts characters.

How about I add a new parameter words to indicate wp_trim_words should be used? And we just don't apply the excerpt_more filter, always use '[…]'?


refactor: clean up helmut library

What was done:

Removed some of Python 2 related imports
Cleaned up some unused files
Removed REST implementation for helmut, as it is not used code path, we are only using SDK version instead

semgrep and snyk are broken for all external contributors, this is something we will need to fix in the future.
This PR should not affect semgrep and snyk anyways.

:tada: This PR is included in version 2.1.1 :tada:
The release is available on:

v2.1.1
GitHub release

Your semantic-release bot :package::rocket:


Sixel encoder is supported

Takes the new https://github.com/gui-cs/Terminal.Gui/pull/3768 changes in place of my adhoc NetDriver only code

The new windows terminal preview (front window) reports it supports sixel while current edition (behind) does not

I've closed this and instead moved the code into main sixel branch as interfaces.  The actual ansi request code is commented out in that branch.
This means that the sixel changes that are dependent on this branch are just uncommenting.  I've tested it here: https://github.com/tznind/gui.cs/pull/171/commits/1f473cbe7964700af01b5149ad1dd1a4026989fb
So can merge in


Support for WiFi 802.11 Ad Hoc mode

Is it possible to add support for WiFi 802.11 Ad Hoc mode to the ESP32 WiFi Stack Libraries?

One for me. Ad Hoc mode would be extremely useful for p2p comunication and mesh networks.

Will Ad-Hoc ever be on the ToDo list? Really want to use my ESPs with existing mesh networks that follow the 802.11 ad-hoc standard for making mesh networks.

Hi @wgaylord . Ad Hoc is not in our TODO list. Sorry for that.

Is there a specific reason why? Or just other priorities?

As far as I know, the Ad-Hoc (IBSS) mode is basic functionality in the WiFi stack.
It should not be difficult to expose this function to the framework.
So please reconsider.

Hi @honza-klu @preechaim, thank you for your suggestion. For now we are doing other tasks. If there are any news about this, we would let you know.

Is 802,11 Ad Hoc going to be looked at or is it not being looked at as it would compete with ESP-Mesh? Just looking for an answer.  I would attempt to implement Ad Hoc somehow but the WiFi stack is closed source in a binary only so I would have to use sending and reception of raw packets.


问题请教

感谢您的分享！
我在编译时出现了以下的错误：（我采用的是cuda11.1版本，请问如何在不修改版本的情况下解决这个问题呢？）
Errors     << rangenet_plusplus:make /home/llz/catkin_RNT/logs/rangenet_plusplus/build.make.000.log
: warning: ISO C++11 requires whitespace after the macro name
: warning: ISO C++11 requires whitespace after the macro name
: warning: ISO C++11 requires whitespace after the macro name
/home/llz/catkin_RNT/src/RangeNetTrt8/ops/project_kernel.cu(3): error: A device variable cannot be marked constexpr
/home/llz/catkin_RNT/src/RangeNetTrt8/ops/project_kernel.cu(4): error: A device variable cannot be marked constexpr
2 errors detected in the compilation of "/home/llz/catkin_RNT/src/RangeNetTrt8/ops/project_kernel.cu".
CMake Error at project_ops_generated_project_kernel.cu.o.RELEASE.cmake:283 (message):
Error generating file
/home/llz/catkin_RNT/build/rangenet_plusplus/CMakeFiles/project_ops.dir/ops/./project_ops_generated_project_kernel.cu.o

你可以尝试不使用全局变量而使用局部变量，将这部分挪到下面的函数中，如图所示

非常感谢您的回复！上述问题已经解决，但是又遇到了新的：
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:256:32: error: ‘kPREFER_PRECISION_CONSTRAINTS’ is not a member of ‘nvinfer1::BuilderFlag’
  256 |   config->setFlag(BuilderFlag::kPREFER_PRECISION_CONSTRAINTS);
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:291:16: error: ‘class nvinfer1::IBuilder’ has no member named ‘buildSerializedNetwork’
  291 |       builder->buildSerializedNetwork(*network, *config));
      |                ^~~~~~~~~~~~~~~~~~~~~~

非常感谢您的回复！上述问题已经解决，但是又遇到了新的：
<command-line>: warning: ISO C++11 requires whitespace after the macro name
<command-line>: warning: ISO C++11 requires whitespace after the macro name
<command-line>: warning: ISO C++11 requires whitespace after the macro name
<command-line>: warning: ISO C++11 requires whitespace after the macro name
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp: In member function ‘void rangenet::segmentation::NetTensorRT::serializeEngine(const string&, const string&)’:
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:256:32: error: ‘kPREFER_PRECISION_CONSTRAINTS’ is not a member of ‘nvinfer1::BuilderFlag’
  256 |   config->setFlag(BuilderFlag::kPREFER_PRECISION_CONSTRAINTS);
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:291:16: error: ‘class nvinfer1::IBuilder’ has no member named ‘buildSerializedNetwork’
  291 |       builder->buildSerializedNetwork(*network, *config));
      |                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvinfer1::ICudaEngine]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvinfer1::ICudaEngine; _Dp = std::default_delete<nvinfer1::ICudaEngine>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:100:42:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvinfer1::ICudaEngine::~ICudaEngine()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /usr/include/x86_64-linux-gnu/NvInfer.h:53,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:10,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvInferRuntime.h:1358:13: note: declared protected here
 1358 |     virtual ~ICudaEngine() {}
      |             ^
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvinfer1::IExecutionContext]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvinfer1::IExecutionContext; _Dp = std::default_delete<nvinfer1::IExecutionContext>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:101:49:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvinfer1::IExecutionContext::~IExecutionContext()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /usr/include/x86_64-linux-gnu/NvInfer.h:53,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:10,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvInferRuntime.h:1693:13: note: declared protected here
 1693 |     virtual ~IExecutionContext() noexcept {}
      |             ^
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvinfer1::IRuntime]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvinfer1::IRuntime; _Dp = std::default_delete<nvinfer1::IRuntime>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:226:72:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvinfer1::IRuntime::~IRuntime()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /usr/include/x86_64-linux-gnu/NvInfer.h:53,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:10,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvInferRuntime.h:801:13: note: declared protected here
  801 |     virtual ~IRuntime() {}
      |             ^
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvinfer1::IBuilder]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvinfer1::IBuilder; _Dp = std::default_delete<nvinfer1::IBuilder>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:247:72:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvinfer1::IBuilder::~IBuilder()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:10,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvInfer.h:7261:13: note: declared protected here
 7261 |     virtual ~IBuilder()
      |             ^
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvinfer1::IBuilderConfig]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvinfer1::IBuilderConfig; _Dp = std::default_delete<nvinfer1::IBuilderConfig>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:253:79:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvinfer1::IBuilderConfig::~IBuilderConfig()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:10,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvInfer.h:6756:13: note: declared protected here
 6756 |     virtual ~IBuilderConfig() {}
      |             ^
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvinfer1::INetworkDefinition]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvinfer1::INetworkDefinition; _Dp = std::default_delete<nvinfer1::INetworkDefinition>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:259:46:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvinfer1::INetworkDefinition::~INetworkDefinition()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:10,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvInfer.h:5434:13: note: declared protected here
 5434 |     virtual ~INetworkDefinition() {}
      |             ^
In file included from /usr/include/c++/9/memory:80,
                 from /usr/local/include/opencv4/opencv2/core/cvstd_wrapper.hpp:11,
                 from /usr/local/include/opencv4/opencv2/core/cvstd.hpp:81,
                 from /usr/local/include/opencv4/opencv2/core/base.hpp:58,
                 from /usr/local/include/opencv4/opencv2/core.hpp:54,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/net.hpp:13,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:9,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/c++/9/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = nvonnxparser::IParser]’:
/usr/include/c++/9/bits/unique_ptr.h:292:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = nvonnxparser::IParser; _Dp = std::default_delete<nvonnxparser::IParser>]’
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:264:53:   required from here
/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvonnxparser::IParser::~IParser()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~
In file included from /home/llz/catkin_RNT/src/RangeNetTrt8/include/netTensorRT.hpp:12,
                 from /home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:1:
/usr/include/x86_64-linux-gnu/NvOnnxParser.h:232:13: note: declared protected here
  232 |     virtual ~IParser() {}
      |             ^
make[2]: *** [CMakeFiles/rangenet_lib.dir/build.make:76：CMakeFiles/rangenet_lib.dir/src/netTensorRT.cpp.o] 错误 1
make[1]: *** [CMakeFiles/Makefile2:336：CMakeFiles/rangenet_lib.dir/all] 错误 2
make: *** [Makefile:141：all] 错误 2

我认为其中错误主要在:
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:256:32: error: ‘kPREFER_PRECISION_CONSTRAINTS’ is not a member of ‘nvinfer1::BuilderFlag’
  256 |   config->setFlag(BuilderFlag::kPREFER_PRECISION_CONSTRAINTS);
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/llz/catkin_RNT/src/RangeNetTrt8/src/netTensorRT.cpp:291:16: error: ‘class nvinfer1::IBuilder’ has no member named ‘buildSerializedNetwork’
  291 |       builder->buildSerializedNetwork(*network, *config));
      |                ^~~~~~~~~~~~~~~~~~~~~~

/usr/include/c++/9/bits/unique_ptr.h:81:2: error: ‘virtual nvonnxparser::IParser::~IParser()’ is protected within this context
   81 |  delete __ptr;
      |  ^~~~~~

这两部分在终端中被标红

trt版本需8.2.3+

非常感谢您的回复！
请问您所做的版本在有光追的显卡上效果如何呢

本工程主要是结合学到的cuda等技巧进行加速的，所以重点在于加速上。我是在titan rtx做实验，速度比原来的都要快很多。最新的数据一个是包括前后处理和预测为30ms左右。分割效果上rangenet++什么效果，这个就是什么效果。

您好，我已经更换了我的环境与您的一致。现在也都编译通过了，我想请问我要如何进行测试呢？
就是像rangeNet_lib一样调用infer？
并且在launch文件夹中没有launch文件存在。

ok，已提交launch文档（之前被ignore了...）；
您试过移除你新生成的trt文件和编译缓存，然后重新执行吗。
可以添加我学校的邮箱<EMAIL_ADDRESS>

trt版本需8.2.3+

Natsu-Akatsuki
根据用户带来的错误，您是如何理解这一点的？

Just a API migration problem. A more detailed question is welcomed. @Egorundel


Playground options gives parsing error

SyntaxError: /Users/chulchong/cs/wedding/src/Components/Gallery.js: Unexpected token (17:4)
15 |
16 |   const options = {
17 |     {
|     ^
18 |         "layoutParams": {
19 |             "structure": {
20 |                 "galleryLayout":

const options = {
   {
       "layoutParams": {
           "structure": {
               "galleryLayout": 1
           },
           "targetItemSize": {
               "value": 80
           }
       },
       "behaviourParams": {
           "item": {
               "overlay": {
                   "hoveringBehaviour": "NEVER_SHOW"
               },
               "content": {
                   "hoverAnimation": "COLOR_IN",
                   "loader": "COLOR"
               }
           },
           "gallery": {
               "scrollAnimation": "SLIDE_UP"
           }
       }
   }
       };

The older option syntax is not working as well
const options = {
    galleryLayout: 0,
    collageDensity: "0.1",
    galleryMargin: 10,
    hoveringBehaviour: "NEVER_SHOW",
    imageHoverAnimation: "ZOOM_IN",
    gallerySize: 100,
    imagePlacementAnimation: "SLIDE",
  };

Hey,
We will probably need to update this representation.
Could you please try to use a flat version of these?
You can use this:
import { flattenObject } from 'pro-gallery-lib';
It will take your object (which we know is much more readable), and flatten it to:
{...
"layoutParans_structure_galleryLayout": 0
...}
The old naming of version 4 doesnt exist anymore.


Backlink to obsidian

Thank you for this useful plugin!
Is it possible to have an option to add a backlink to the Obsidian note to the task created in Things?

This should already be the behavior of the Create Task command. A task will be added to the Things inbox with a backlink to the Obsidian note in the notes section of the task.


Icon in dropdowns

Doing this

works in UT

but doesn't work in Material APEX

@sonny316, since this is a hack in UT, I decided not to pursue a fix (natively). If this is critical for you, please contact me in private and we can find a solution together, but it will fall out of the (free) open source support.
Thanks for understanding.
Reference: http://www.relational.es/blog/apex-how-to-create-a-select-list-with-fontawesome-icons/


VOI creation feature is not available.

@gmershad can you provide more information around this issue? For example:

Current behavior
Expected/desired behavior
Potential implementation details
Sources/Reading to assist in understanding issue, or as support for why change should happen


Update to support axlsx 3.0.0

There's a 3.0.0 branch of axlsx prepping for release here: https://github.com/randym/axlsx/tree/release-3.0.0
axlsx-styler is currently locked to 2.x, so won't work with the new version.
This might be as simple as making the dependency open-ended in the gemspec, but I haven't had a close look at all the changes.

I contacted Sakovias, he doesn't code on ruby anymore but still is open to accept pull requests if needed :)

I'll prep a PR, thanks@

@nfruneau Ha! I just spotted that you've got a PR open already. :)

yes I am using my branch atm to overcome the issue and it works well, but if you want to make some  integration tests as @sakovias requested feel free to do so :)

https://github.com/sakovias/axlsx_styler/pull/21


Code doesn't use blurRadius parameter

Line 32 of UIImageView+LBBlurImageView is the offending one
(Pulled from cocoa pods)
Actual:
blurRadius = (blurRadius <= 0) ? : kLBBlurredImageDefaultBlurRadius;
Should be:
blurRadius = (blurRadius <= 0) ? kLBBlurredImageDefaultBlurRadius : blurRadius;

Agreed!

+1

This is still broken in the most recent Cocoapods version 0.2.2!


FQ: Basic environment variable support

When this is fixed (if it ever worked?) it would be very useful to align to the well established variables present in in the retail upstream NFS provisioner using pathPattern. I see there's some basic ones now, but it doesn't help to actually place data correctly.
As an example: ${.PVC.namespace}/${.PVC.name}${.PVC.annotations.nfs.io/storage-path}
docs: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner

Seems to be possible now: https://github.com/rancher/local-path-provisioner/issues/302#issuecomment-2558094271


[Task]: Check font sizes everywhere

Description
Font sizes are too small in some cases.
Investigate a way to use css clamp or something similar to pair OS font sizes.
Requirements

[ ] Works on Android
[ ] Works on iOS

https://developer.android.com/guide/webapps/targeting#DensityCSS
We could target by device screen density to clamp font sizes?


[BUG] Qualification tool: Invalid --platform doesn't error

Describe the bug
Passing an invalid or not supported platform doesn't error.  This can lead to user getting results they don't expect.
ie: --platform gcp  or --platform data-t4fdsfd

In addition to this, the platform types in user tools do not match platform types in core tools. Platform types in core tools -support gpu options (eg, dataproc-t4, emr-t4, emr-a10 etc) where as user tools takes only CSP names as platform (eg, dataproc, emr)
Because of this, we cannot leverage the custom speedup factors generated for different GPU types.

This issue exists in the profiling tool options as well where we should also try and create parity with what names we use in the user-tools and the jar versions to avoid more match case statements and chances of error.


Ubiquiti Solution Doesn't Use Custom Logs via AMA

Describe the bug
The solution says Custom Log via AMA is required, however, so I set that up. However, the solution itself still wants to use the now deprecated connector when running reports or queries.
To Reproduce
Steps to reproduce the behavior:

Install AMA, configure log ingestion from Unifi's SNMP trap on premise. Logs flowing into Sentinel's Log Analytics Ubiquiti_CL
Install solution
Do not configure the deprecated connector
No results are being found

Expected behavior
Results in Hunting, Logs, etc produce

Hi @doodlemania2, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks!

@doodlemania2, Could you please let us know which solution version you are using?
And please also know what error you're facing while configuring the rule or running the Parser. Thanks!

Hi there, here's the version info:

which creates two connectors - the deprecated one and the AMA one:

I set up the AMA log and logs are flowing:

but the workbooks and other components are (at least appear) to still be looking for data from the deprecated connector:
 -- isn't configured because deprecated

@doodlemania2, Thanks for the sharing detailed info. we will check into the issue and get back to you. Thanks!

@doodlemania2, waiting for logs to investigate. Thanks!

Sent you email offline

@doodlemania2, Received.
You can send the Ubiquiti_CL in csv format by setting the last 24 hr durations.

@doodlemania2, Thanks!

@doodlemania2, After running the below parser is it give the result? -

for us with your shared data it does not parse -

@doodlemania2,
Actually, the solution contents (Connector,Workbook,rules) are Parser dependent, so the message which you received into the table - Ubiquiti_CL is not in an expected format.
And due to that the contents are not showing any results.
We found the sample data in our repo in which the message format has been mentioned -
"Message": "<30>Mar  9 14:51:17 U7PG2,18e8296c3188,v<IP_ADDRESS>5: logread[1491]: Logread connected to <IP_ADDRESS>:22022"
https://raw.githubusercontent.com/Azure/Azure-Sentinel/refs/heads/master/Sample Data/Custom/UbiquitiAuditEvent.json
When we use the above data for testing, the solution content shows the results -

So, could you please check in source itself and the source configuration to get correct format in message. Thanks!

I'm afraid I don't know what you're asking.
I set up the custom log connector because the ubiquiti one is deprecated. Are you saying that I should be using the deprecated connector instead?

@doodlemania2, No, the configuration you did are correct one. No need to use the old, deprecated connector.
So, the data received in a Message column is in a different format and due to that the workbook not showing any results, the expected message format should be like -
"Message": "<30>Mar  9 14:51:17 U7PG2,18e8296c3188,v<IP_ADDRESS>5: logread[1491]: Logread connected to <IP_ADDRESS>:22022"
This message format came from source itself, which is Ubiquiti side, so can you check is there any log format option are available? or which needs to be enabled, to get the correct message log.
Thanks!

Oh I see, thank you. I'm not given any options in Ubiquiti to configure:

and on the Azure side, not doing any transformations:

output:

Oh, I think I see the problem. Do you have updated instructions for how to configure rsyslog such that the AMA agent picks up the correct datasouce?

Okay, I think I have it working now - I am getting logs inside the parser:

Does this look right?

@doodlemania2, Great.
Now you can check for the rest of the solution content, it should work as data has been parsed.
Please let us know if any issues are there. Many thanks!

@doodlemania2, is there anything for us? if your issue has been resolved, can we close this from GitHub?

Looks good - thank you for the great help!


Fix for issue #407

Fix for issue #407 . Disable RecyclerView animations messing up screen when user scrolls through long device list during scan.

 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.

Thanks!


Add missing custom component files

Description
This PR fixes #574 and fixes #583
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@ayushthe1 add a reviewer, please. add appropriate labels, too, please.

@leecalcote I don't have the permissions to do that.  Could you please add it.

Hi, guys. There are tons of files and are hard to review.

@ayushthe1 you do have permission to manage issue labels...
@Aisuko you're right. It's completely overwhelming.

@ayushthe1 Many JSONs are differently formatted; could you get them to be consistent?

@leecalcote This either requires a validation script or merge and see whether it's all fine or not.

@ayushthe1 Is there any new update, can we keep going? Thanks.

Updated the model name

There are still some failed CI tests, @theBeginner86 do you know how to resolve this?

I added the missing model name in https://github.com/service-mesh-patterns/service-mesh-patterns/pull/106

This PR https://github.com/service-mesh-patterns/service-mesh-patterns/pull/107 would solve the last set of tests that checks the sample apps.

updated filename reference for sample app design to bookInfo.yaml

https://github.com/service-mesh-patterns/service-mesh-patterns/pull/108

All ✅
Lets merge this

Thank you for your efforts to resolve this issue !👍  Which release will contain this patch and when will it happen?

Thank you for your efforts to resolve this issue !👍 Which release will contain this patch and when will it happen?

Its already released in latest meshery-istio adapter. https://github.com/meshery/meshery-istio/releases/tag/v0.6.11

@theBeginner86 I've updated meshery-istio to v0.6.11,

and this is my pattern yaml file:
name: Istio Installation with CryptoMB
services:
  istioservicemesh:
    name: istioservicemesh
    type: IstioMesh
    model: ISTIO
    namespace: "istio-system"
    settings:
      profile: default
      version: 1.17.2
    traits:
      components:
        ingressGateways:
        - enabled: true
          name: istio-ingressgateway
          k8s:
            overlays:
              - kind: Deployment
                name: istio-ingressgateway
                patches:
                - path: spec.template.spec.containers.[name:istio-proxy].args.[-1]
                  value: "--concurrency=4"
            # Limit CPU/MEM usage to 4 vCPUs/4 GB for QoS reasons.
            # Enable CPU manager static policy in kubelet to even more deterministic results.
            resources:
              requests:
                cpu: 4000m
                memory: 4096Mi
              limits:
                cpu: 4000m
                memory: 4096Mi
            hpaSpec:
              maxReplicas: 1
              minReplicas: 1
            podAnnotations: # this controls the SDS service which configures ingress gateway
              proxy.istio.io/config: |
                privateKeyProvider:
                  cryptomb:
                    pollDelay: 10ms
      automaticSidecarInjection:
        namespaces:
        - default
      meshmap:
        edges: []
        id: istioservicemesh
        label: istioservicemesh
        position:
          posX: 59.458251455094434
          posY: 5.53595199333449

but it still failed with error:

Is there something wrong with my configuration? Could you please give me an example for that?

@theBeginner86 I've updated meshery-istio to v0.6.11,
and this is my pattern yaml file:
name: Istio Installation with CryptoMB
services:
  istioservicemesh:
    name: istioservicemesh
    type: IstioMesh
    model: ISTIO
    namespace: "istio-system"
    settings:
      profile: default
      version: 1.17.2
    traits:
      components:
        ingressGateways:
        - enabled: true
          name: istio-ingressgateway
          k8s:
            overlays:
              - kind: Deployment
                name: istio-ingressgateway
                patches:
                - path: spec.template.spec.containers.[name:istio-proxy].args.[-1]
                  value: "--concurrency=4"
            # Limit CPU/MEM usage to 4 vCPUs/4 GB for QoS reasons.
            # Enable CPU manager static policy in kubelet to even more deterministic results.
            resources:
              requests:
                cpu: 4000m
                memory: 4096Mi
              limits:
                cpu: 4000m
                memory: 4096Mi
            hpaSpec:
              maxReplicas: 1
              minReplicas: 1
            podAnnotations: # this controls the SDS service which configures ingress gateway
              proxy.istio.io/config: |
                privateKeyProvider:
                  cryptomb:
                    pollDelay: 10ms
      automaticSidecarInjection:
        namespaces:
        - default
      meshmap:
        edges: []
        id: istioservicemesh
        label: istioservicemesh
        position:
          posX: 59.458251455094434
          posY: 5.53595199333449

but it still failed with error:
Is there something wrong with my configuration? Could you please give me an example for that?

Can you share the logs of istio adapter?

@gyohuangxin  Did you create the above configuration from Meshmap or is it handtyped

@Revolyssup I handtyped it, and I didn't see any logs in Istio adapter, the error happened in meshery main process:
meshery-meshery-1        | time="2023-06-12T05:51:21Z" level=info msg="kubernetes contexts successfully retrieved from remote provider"
meshery-meshery-1        | time="2023-06-12T05:51:21Z" level=info msg="attempting to fetch patterns resource from cloud"
meshery-meshery-1        | time="2023-06-12T05:51:21Z" level=info msg="pattern resources successfully retrieved from remote provider"
meshery-meshery-1        | map[string]interface {}{"name":"Istio Installation with CryptoMB", "services.istioservicemesh.id":"47565a89-f7c3-4d76-9304-10c8d67fd999", "services.istioservicemesh.model":"ISTIO", "services.istioservicemesh.name":"istioservicemesh", "services.istioservicemesh.namespace":"istio-system", "services.istioservicemesh.settings.profile":"default", "services.istioservicemesh.settings.version":"1.17.2", "services.istioservicemesh.traits.automaticSidecarInjection.namespaces.0":"default", "services.istioservicemesh.traits.components.ingressGateways.0.enabled":true, "services.istioservicemesh.traits.components.ingressGateways.0.k8s.hpaSpec.maxReplicas":1, "services.istioservicemesh.traits.components.ingressGateways.0.k8s.hpaSpec.minReplicas":1, "services.istioservicemesh.traits.components.ingressGateways.0.k8s.overlays.0.kind":"Deployment", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.overlays.0.name":"istio-ingressgateway", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.overlays.0.patches.0.path":"spec.template.spec.containers.[name:istio-proxy].args.[-1]", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.overlays.0.patches.0.value":"--concurrency=4", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.podAnnotations.proxy.istio.io/config":"privateKeyProvider:\n  cryptomb:\n    pollDelay: 10ms\n", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.resources.limits.cpu":"4000m", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.resources.limits.memory":"4096Mi", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.resources.requests.cpu":"4000m", "services.istioservicemesh.traits.components.ingressGateways.0.k8s.resources.requests.memory":"4096Mi", "services.istioservicemesh.traits.components.ingressGateways.0.name":"istio-ingressgateway", "services.istioservicemesh.traits.meshmap.id":"istioservicemesh", "services.istioservicemesh.traits.meshmap.label":"istioservicemesh", "services.istioservicemesh.traits.meshmap.position.posX":59.458251455094434, "services.istioservicemesh.traits.meshmap.position.posY":5.53595199333449, "services.istioservicemesh.type":"IstioMesh"}
meshery-meshery-1        | IstioMesh ISTIO
meshery-meshery-1        | time="2023-06-12T05:51:21Z" level=error msg="could not find component with name: IstioMesh, model: ISTIO, apiVersion: "
meshery-meshery-1        | time="2023-06-12T05:51:21Z" level=error msg="could not find component with name: IstioMesh, model: ISTIO, apiVersion: " app=meshery code=2012 probable-cause= severity=2 short-description="unable to Create Comp Config..could not find component with name: IstioMesh, model: ISTIO, apiVersion: " suggested-remediation=


Fix windows entry long text scroll.

Fixes #232
Long text entries display in a weirdly scrolled way on Windows upon first window creation. This is due to the cursor being placed at the end of the text but control dimension still being unknown.
Fix by placing the cursor only if the uiEntry has the focus as cursor placement is otherwise determined by the user upon clicking the control.
Verify: qa > uiEntry > 4. Entry Long Text
I would still hold off merging this until we can determine why the cursor position is being set in the first place (introduced in #102).
The only use case I can think of is when the uiEntry in question is already focused. @adamierymenko was this your original use case? Setting the text when the user is already editing the text within the control? If that is the case I will add another qa test.
Otherwise my cursor is always placed right under my mouse cursor once I click or at the end if the control is bigger (Windows 7 & wine 8.16).

Upon further testing and reflection I have come to the conclusion that this is safe to merge.
I can not come up with any test scenario that breaks anything with this patch.
Is does however fix the issue #232 as can be seen in qa > uiEntry > 4. and qa > uiEntry > 5.

(Windows 7 & wine 8.16)
It does however fix the issue https://github.com/libui-ng/libui-ng/issues/232 as can be seen in qa > uiEntry > 4. and qa > uiEntry > 5.

Confirmed here on Win 11, this patch fixes both 4. Entry Long Text and 5. Entry Overflow Text.


fix: Include only src in the build output.

This fixes missing typescript definitions in the build output (package.json points to dist/index.d.ts and the file is not there after building the project). Plus it probably doesn't make sense to include tests in the build anyway.

Fixed in 1.12.0
Please let me know if this release resolves the issue for you 😄
Thank you for raising @pjamrozowicz!

It works, thanks @ljwagerfield!


WIP: Fix overflow issue in AxisInfoAnalysis

For now only add a reproducer.

Close as it's fixed by https://github.com/openai/triton/commit/24a1bac851e650d7cfe2508e556e72e23e730ec5


add newScore attribute to Player

scor eof last quiz question
when next question, add to regular score and set to 0
make sure sent to frontend

3db18dd213f0415d7dfe65247e8f71458f6f663c


Consider adding to the C# extension project?

The official csharp extension is at https://github.com/OmniSharp/omnisharp-vscode
Have you considered contributing some of this work there?

I think Microsoft people are not interested in a solution explorer feature. And I would not like to mess up this great extension with my stuff... so the answer is: no, I haven't.
Thanks!

I'm Microsoft people, and I'm interested :)

I have taken a look at omnisharp-vscode source code, it seems everything is based on a omnisharp-roslyn, so I guess if I would like to contribute to this project I should create the server side code in c# (omnisharp-roslyn) and the client code in typescript (omnisharp-vscode), isn't it?


Were you able to convert the pre-trained model to CoreML?

Conversion is possible. I have tried so and have succeeded. You do need to dig deep into the coremltools and implement some custom ops. But since last December I checked, even though the conversion is correct and the inference is correct, the speed is pretty slow in CoreML. The CropAndResize operation in CoreML is not very well optimized and it is very slow. Our model needs this operation to crop thousands of patches for refinement. I don't whether Apple has made improvement till now.
I don't have the conversion code no more. You will need to experiment yourself.

Thanks. Good to know. You converted direct from Pytorch to CoreML using coremltools4.0 or you went via the onnx route?

coremltools.


Deployment Pane: Add support for bicepparam files

In deploy pane you cannot choose bicep param files only json param. Please add support for both types

You can use them! just try the following:


Would you mind adding some methods for contrast?

Basically, would like to be able to get some foreground color based on a background, so it matches an expected contrast.
This would be pretty useful for texts colors and whatnot
Thanks

Hi, thanks for the request!
I have added a contrast static method. Please let me know if this suits your needs.

Hi, thanks for the additional clarification.
I have added a findContrast method which does exactly as you have described. Usage is as such:
const c1 = new Color(203, 213, 255);
const c2 = new Color(122, 143, 255);
const c3 = Color.findContrast(c1, c2);
c3.toString(); // #4c599e

You can also set a minimum contrast using the 3rd argument (default is 4.5)
const c1 = new Color(203, 213, 255);
const c2 = new Color(122, 143, 255);
const c3 = Color.findContrast(c1, c2, 3);
c3.toString(); // #6272cc

@elusivecodes this findContrast method seems to take 2 colors, why is that?
Is it possible that it takes just 1?

Hi,
This is a static method, that returns a new Color instance. The first argument is the input color (and does not change), the second argument is the desired color. If the contrast between the input and desired color is already above the minimum, it will just return (a clone of) the desired color. Otherwise, it will adjust the desired color until it reaches the minimum contrast.
This wouldn't be very useful with just 1 argument, either the generated color would always be grayscale, or the same hue/saturation as the input color, or with a fixed hue offset from the original color. All of these options greatly limit the possibilities, and could each easily be achieved using this implementation anyway.

I've modified the second argument to be optional. If it's omitted (or set to null), it will default to a clone of the first color. I think this would best accommodate all use cases.

great... thanks for the help 😄


Create and store a CRI-O runtime_vm implementation

CRI-O does not want to hold every potential implementation of their RuntimeImpl interface inside their repo (https://github.com/cri-o/cri-o/issues/2255), hence we need to create a shared library (.so file) implementing this interface for the shim-v2 case.
This will avoid to put the burden of pulling containerd packages directly onto Kata Containers instead of CRI-O.
I think we need to simply pull the code of oci/runtime_vm.go from CRI-O into a new directory cri-o of our kata runtime repo.
From this code, our Makefile should build the corresponding .so file.

/cc @egernst @mrunalp


Dry common functions

Don't merge yet, tests are still running

Except some other issues this PR causes that we don't fit into 65K cloud-init data limit for infra node:
| oshift31                  | dc830001-3643-4033-ad75-0b5263c72fee | Resource CREATE failed: BadRequest: resources.infra_host.resources.host: User data too large. User data must be no larger than 65535 bytes once base64 encoded. Your data is 65928 bytes (HTTP 400) (Request-ID: req-eaa7c3fb-3541-4ec6-9fac-5da7088ab8c4) | CREATE_FAILED      | 2016-04-12T09:46:04 |

If you REALLY want to get DRY, I think master-boot.sh and node-boot.sh are identical.  Replace with ose-host-boot.sh ?

Yes, this patch address master|node-boot scripts among others. The problem was 65K limit, an option would be to have common lib for all nodes, and then common lib for ose nodes so these ose-related functions are don't increase overall size on infra node (which is the one hitting the limit)

this patch needs bigger rebase since a lot has change meantime, don't merge yet.

updated

rebased


types are not correct for esm usage

@open-wc/semantic-dom-diff/chai-dom-diff-plugin.d.ts (3,29): Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './get-diffable-html.js'?
This is an issue all across @open-wc modules.

Closed by #2777


Changing when ngModel and ngModelRange get updated

Hi.
I'm using this slider in a project at work, and I would like to modify the behavior of when ngModel and ngModelRange get updated.
I would like to modify the slider so that ngModel and ngModelRange are updated only when the dragging of the knobs or the range ends, not during the actual dragging of the knobs.
From what I can tell from playing with the source for the past two days, updating the UI is tightly coupled with updating ngModel and ngModelRange.
Any thoughts or suggestions?

Sorry - did anything ever happen regarding this issue?

Yeah, what happened with this?


Fix undefined sheet error when SSR without rendering any styles

When SSR without any styles, StyleSheet.sheet returned by glamor is
undefined, and thus the cssRules property is undefined. I have
substituted this with an empty array instead, and it is now working in
my case. This should solve one of the issues mentioned multiple times in
#124.
Side note: this is my first ever PR anywhere... please let me know if I'm doing something dumb

Hey @kristojorg, this is great, thanks for taking the time to submit a PR!
We just rebuilt the entire SSR system in #214, which was merged into the v2 branch. Would you mind making a similar change to that branch? Also it'd be great if we could circumvent this issue from our source, not the vendored dependencies. (i.e. not src/vendor/) Changing a vendored dependency makes updating it very hard in the future, as we have to remember what happened to it.
Thanks so much again!

Cool, I just submitted a new PR to the v2 branch with a fix :-) ! Hope it helps

How to install the v2 branch? I tried npm i<EMAIL_ADDRESS>but this didn't work. And is there some clear documentation on how to SSR styled components?
I've tried using https://github.com/styled-components/babel-plugin-styled-components but my app crashed after installing it. Any heads up?

npm install --save styled-components@next, then use the babel plugin. It's not documented yet as it's not released yet, we're still working out the kinks.

Thanks for your reply. Before using this I will wait until v2 is stable, because literally none of my styles work after updating (although the babel plugin error did disappear haha).

Oh oops 🙈 are you server-side rendering?

Not yet. Is that required with v2? Still need to use the flush etc, or is the getCSS() as stated in https://github.com/styled-components/styled-components/issues/124 possible?

Not required with v2 at all, getCSS works perfectly fine see #214. You're not using SSR and no styles show up?

Ok thanks, will try the example shown in 214.
Yes indeed, no serverside rendering atm. For instance my Header.jsx as shown below work perfectly fine with styled-components 1.3.1, but after updating to with styled-components@next no styles are working anymore.
import React, { Component } from 'react';
import { Link } from 'react-router';
import styled from 'styled-components';

class Header extends Component {
  render() {
    return (
      <HeaderElem>
          <NavElem>
            <NavLink to="/">
              Terug
            </NavLink>

            <NavTitle>

            </NavTitle>
          </NavElem>
      </HeaderElem>
    );
  }
}

const HeaderElem = styled.header`
  position: fixed;
  top: 0;
  left: 0;
`;

const NavElem = styled.nav`
  display: flex;
  position: relative;
  width: 100vw;
  padding: 21px 20px 16px;
  color: #fff;
  font-size: 18px;
  text-align: center;
  background: #38659e;
`;

const NavLink = styled(Link)`
  position: absolute;
  left: 20px;
  top: 50%;
  transform: translate(0, -50%);
  color: #fff;
  text-decoration: none;
`;

const NavTitle = styled.div`
  flex-grow: 2;
`;

export default Header;

Did you build the v2 branch after npm install? To use the v2 branch I had to :
cd node_modules/styled-components
then
yarn build or npm build
After that it worked fine

Ohh that's my mistake when I published that then @kristojorg! 🙈 will fix that with the next pre-release!

Thanks for pointing that out, although building doesn't seem to fix my problem.
As you can see in my example I defined all my styled outside my React component. I'd check the  of my webpage through the inspector and I saw a lot of styles, many of them empty:

So somehow I thought moving the styled elements would work. And this worked. The styles where added, but my global styles (body styling and font-face) didn't load.
I prettified my code above, but it looks like it isn't loading the in correct order. Also they're many empty classes which seems not like it use to be.
I downgraded to 1.3.1 again and moved most of my styles back outside the component. I hope styles outside the component will still be allowed in v2 since it looks a lot clearer to me!


fix: allow netstandard2.0

Allows use of latest c# features while downleveling to netstandard2.0
ref #239

@viceice  I see the support for multiple target framework.
Cool!
Thanks.


As a user, I want to start grid with system boot

https://www.npmjs.com/package/auto-launch

Implemented


Switch to Node10 Execution Handler

Azure DevOps is beginning the process to deprecate the Node execution handler in favor of Node10. As of a few days ago, custom tasks across the board spam warnings into build pipelines, the dependency-check task being one of them.
See here for more info:
https://aka.ms/migrateTaskNode10

See PR #93


reworking and adjusting the output table function

The old output tables function uses a dict inside a function to find the parameter description/name from the corresponding variable. I want to try to improve this to be more independent of the hard coded dict and descriptions.
Additionally, the tables are adjusted for the new rheologies that were added with #99.

It would be nice to improve Tables.jl indeed. Taking a quick look, some suggestions:

Get rid of all the global variables.
There is  a lot of code repetition in Phase2Dict. You can avoid all that type-based branching by defining small functions and using multiple dispatch.
In general, all  the functions are quite large and monolithic. Splitting them into smaller functions is probably  a good idea when possible. Code will probably more clear and may also lead to code re-usability.

Are you still planning to work on this? I am wondering whether it would makes sense to move this out to an external package, something like  GeoParamsTables.jl, so we can move out some dependencies that are not really needed when one uses GeoParams in a solver or similar.

Are you still planning to work on this? I am wondering whether it would makes sense to move this out to an external package, something like GeoParamsTables.jl, so we can move out some dependencies that are not really needed when one uses GeoParams in a solver or similar.

I do not have a lot of time at the moment, but I will finish this pull request once I have more time again.
Concerning the tables feature, the only output dependency that I use is Unidecode.jl as far as I know. So, I don't mind moving the Tables to another package if that helps. I guess I would need to rethink how to code some stuff then, but just do as you thinks suits best for GeoParams.

I think it make sense to move it out. It is not really needed inside GP. And I don't think it will change the current code structure, since its already a submodule, just need to update a few lines of code here and there.

I'm fine with moving this to a separate package


Add Paulo Ricardo Kenshun Nakaima to Contributors list"

Hi  @guimpo, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.