Polymorphism via 'discriminator' is not working as expected

Hello,
sorry to bother you again, but the discriminator-Problem seems not to be resolved yet. Sorry for not providing you an example in the last ticket.
A standard example:
swagger: '2.0'
info:
  title: Generalization Test with allOf
  description: Generalization Test with allOf
  version: "1.0"
paths:
  /getAorB:
    get:
      description: Returns an instance of ParentObject
      responses:
        default:
          description: Returns an instance of ParentObject
          schema:
            $ref: '#/definitions/ParentObject'
definitions:
  ParentObject:
    title: This is an object that holds either an instance of A or B
    type: object
    properties:
      AorB:
        $ref: '#/definitions/AbstractObject'
  AbstractObject:
    title: AbstractObject
    type: object
    description: AbstractObject is an abstract Class and a Superclass of A and B.
    discriminator: type
    properties:
      type:
        type: string
      existsInBothObjects:
        type: string
        description: This property exists in both, A and B
        example: Foo
    required:
    - type
  A:
    title: A
    description: A is a Subclass of AbstractObject.
    type: object
    allOf:
    - $ref: '#/definitions/AbstractObject'
    properties:
      onlyExistsInA:
        type: string
        description: This property is only valid within an A object
        example: A
      type:
        type: string
        enum:
        - a
  B:
    title: B
    description: B is a Subclass of AbstractObject.
    type: object
    allOf:
    - $ref: '#/definitions/AbstractObject'
    properties:
      onlyExistsInB:
        type: string
        description: This property is only valid within a B object
        example: b
      type:
        type: string
        enum:
        - b

Valid responses for /getAorB:
{
  "AorB": {
    "type": "a",
    "existsInBothObjects": "Hello World",
    "onlyExistsInA": "This is valid"
  }
}

{
  "AorB": {
    "type": "b",
    "existsInBothObjects": "Hello World",
    "onlyExistsInB": "This is valid"
  }
}

Invalid responses for /getAorB:
{
  "AorB": {
    "type": "a",
    "existsInBothObjects": "Hello World",
    "onlyExistsInB": "This property is not allowed on type A"
  }
}

{
  "AorB": {
    "type": "c",
    "existsInBothObjects": "Type c is not allowed"
  }
}

This appears to be a ref problem not a discrimator problem.  Try without using references while I try and figure out a way to handle so many refs and discriminators and allOfs at the same time.

There is a problem with your model.  There appears to be a case sensitivity where A != a so your types need to be A or B and not a or b.

{
    "swagger": "2.0",
    "info": {
        "title": "Generalization Test with allOf",
        "description": "Generalization Test with allOf",
        "version": "1.0"
    },
    "paths": {
        "/getAorB": {
           "get": {
                "description": "Returns an instance of ParentObject",
                "responses": {
                    "default": {
                       "description": "Returns an instance of ParentObject",
                       "schema": {
                            "$ref": "#/definitions/ParentObject"
                        }
                    }
                }
            }
        }
    },
    "definitions": {
        "ParentObject": {
            "title": "This is an object that holds either an instance of A or B",
            "type": "object",
            "properties": {
                "AorB": {
                    "$ref": "#/definitions/AbstractObject"
                }
            }
        },
        "AbstractObject": {
            "title": "AbstractObject",
            "type": "object",
            "description": "AbstractObject is an abstract Class and a Superclass of A and B.",
            "discriminator": "type",
            "properties": {
                "type": {
                    "type": "string"
                },
                "existsInBothObjects": {
                    "type": "string",
                    "description": "This property exists in both, A and B",
                    "example": "Foo"
                }
            },
            "required": [
                "type"
            ]
        },
        "A": {
            "title": "A",
            "description": "A is a Subclass of AbstractObject.",
            "type": "object",
            "allOf": [
                {
                    "$ref": "#/definitions/AbstractObject"
                }
            ],
            "properties": {
                "onlyExistsInA": {
                    "type": "string",
                    "description": "This property is only valid within an A object",
                    "example": "A"
                },
                "type": {
                    "type": "string",
                    "enum": [
                        "A"
                    ]
                }
            }
        },
       "B": {
            "title": "B",
            "description": "B is a Subclass of AbstractObject.",
            "type": "object",
            "allOf": [
                {
                    "$ref": "#/definitions/AbstractObject"
                }
            ],
            "properties": {
                "onlyExistsInB": {
                    "type": "string",
                    "description": "This property is only valid within a B object",
                    "example": "b"
                },
                "type": {
                    "type": "string",
                    "enum": [
                        "B"
                    ]
                }
            }
        }
    }
}

Hello,
you argued "There appears to be a case sensitivity where A != a so your types need to be A or B and not a or b.". I fear that one of us has a misunderstanding of how the discriminator works. As far as I know it does not reference any model name! I am using an enum here, and I can call it arbitrary.
So this would be valid (but arguably not the most conventional idea to do), too:
{
    "swagger": "2.0",
    "info": {
        "title": "Generalization Test with allOf",
        "description": "Generalization Test with allOf",
        "version": "1.0"
    },
    "paths": {
        "/getAorB": {
           "get": {
                "description": "Returns an instance of ParentObject",
                "responses": {
                    "default": {
                       "description": "Returns an instance of ParentObject",
                       "schema": {
                            "$ref": "#/definitions/ParentObject"
                        }
                    }
                }
            }
        }
    },
    "definitions": {
        "ParentObject": {
            "title": "This is an object that holds either an instance of A or B",
            "type": "object",
            "properties": {
                "AorB": {
                    "$ref": "#/definitions/AbstractObject"
                }
            }
        },
        "AbstractObject": {
            "title": "AbstractObject",
            "type": "object",
            "description": "AbstractObject is an abstract Class and a Superclass of A and B.",
            "discriminator": "type",
            "properties": {
                "type": {
                    "type": "string"
                },
                "existsInBothObjects": {
                    "type": "string",
                    "description": "This property exists in both, A and B",
                    "example": "Foo"
                }
            },
            "required": [
                "type"
            ]
        },
        "A": {
            "title": "A",
            "description": "A is a Subclass of AbstractObject.",
            "type": "object",
            "allOf": [
                {
                    "$ref": "#/definitions/AbstractObject"
                }
            ],
            "properties": {
                "onlyExistsInA": {
                    "type": "string",
                    "description": "This property is only valid within an A object",
                    "example": "A"
                },
                "type": {
                    "type": "string",
                    "enum": [
                        "MY_MAGIC_ENUM_THAT_WILL_SAY_THIS_IS_AN_A"
                    ]
                }
            }
        },
       "B": {
            "title": "B",
            "description": "B is a Subclass of AbstractObject.",
            "type": "object",
            "allOf": [
                {
                    "$ref": "#/definitions/AbstractObject"
                }
            ],
            "properties": {
                "onlyExistsInB": {
                    "type": "string",
                    "description": "This property is only valid within a B object",
                    "example": "b"
                },
                "type": {
                    "type": "string",
                    "enum": [
                        "completeleyDifferentMagicEnumForB"
                    ]
                }
            }
        }
    }
}

Valid responses for /getAorB:
{
  "AorB": {
    "type": "MY_MAGIC_ENUM_THAT_WILL_SAY_THIS_IS_AN_A",
    "existsInBothObjects": "Hello World",
    "onlyExistsInA": "This is valid"
  }
}

{
  "AorB": {
    "type": "completeleyDifferentMagicEnumForB",
    "existsInBothObjects": "Hello World",
    "onlyExistsInB": "This is valid"
  }
}

Invalid responses for /getAorB:
{
  "AorB": {
    "type": "MY_MAGIC_ENUM_THAT_WILL_SAY_THIS_IS_AN_A",
    "existsInBothObjects": "Hello World",
    "onlyExistsInB": "This property is not allowed on type A"
  }
}

{
  "AorB": {
    "type": "c",
    "existsInBothObjects": "Type c is not allowed"
  }
}

My understanding of the discriminator is that it points to a property that contains the subtype (ie a model name). So it is a case sensitive match to a model name.  The effort required to match against an arbitary value such as you have described would be much greater than that required for finding the name of a sub model.
Plus it would be possible to have more than one class that could match your discriminator whereas it is not allowed to have two models with same name.
I think I'll leave it as it is - It is a minor change to your definition and a major change to the validator code.
Anyone is welcome to submit a pull request to change this behaviour if they would like to.


Merge authorization-page to master

@NEsfandiari

Automatically log in user immediately after signing up
Added context functionality for logged-in user information to persist throughout different pages
Logged in user can go to subscribe page and press "Get Started" button, which will add "subscribed" tag in shopify

Preview: https://5c099de1e470857ab734524f--determined-benz-390e9b.netlify.com/


Add indentation

Add appropriate indentation in underscore.cpp file. All the implementation is left-aligned.

I can see that indentation has been there.

I dont think so. Maybe you are looking the code from GitHub, and the code they show is slightly seen indented. Can you clone it and check it out.

Ok I will do that


use swift 2 for tvOS as well

this change is required to make the xcode8 branch compile with Carthage, see #493

Thanks, i've integrated this into the xcode8 branch

@leoschweizer can you try the latest xcode8 branch to see if anything else needs changing there?

@jberkel github "stephencelis/SQLite.swift" "xcode8" as Carthage dependency definition works fine for me now.


Add support for LoRA with GQAQKVColumnParallelLinear

What does this PR do?
As per title.
This needs Neuron SDK 2.20.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Fix for readDir selection, currently any template that uses readDir* functions seems to break

I just created a naked helmfile.yaml with readDirEntries and it crashed.
environments:
  {{ range $index,$item := readDirEntries "./environments" }}
  {{$item}}:
  {{ end }}

Error: in ./helmfile.yaml: error during helmfile.yaml.part.0 parsing: template: stringTemplate:2:27: executing "stringTemplate" at <readDirEntries "./environments">: error calling readDirEntries: runtime error: invalid memory address or nil pointer dereference

I added the template tests at test/e2e/template/helmfile/tmpl_test.go to a full FileRenderer test and it crashed in a similar way.
Basically when a new FileRenderer is created nothing is set in the Contexts readDir pointer so it is a dangling pointer there.
I just set the default to os.ReadDir

@arkaitzj Good catch. Thanks very much. I think this is the most quick method.
Shall we should add a arg called readDir in to NewFileRenderer? WDYT? @mumoshu @arkaitzj

hi @yxxhero, I don't know what the usecases are there but I would merge this PR as a fix and open up the option for the new arg as an enhancement later if deemed reasonable?
Mainly because this is currently broken.

@mumoshu

We use the NewFileRender's args to inject the virtual fs interface in some unit tests like https://github.com/helmfile/helmfile/blob/85ade797abf278cbb6acebe26c1b66b39c7a98ce/pkg/tmpl/file_renderer_test.go.
That said, it's not required for the feature itself to work properly. But I'd appreciate it if you could submit another pull request to address it!

that sounds good, if there is clear consensus I will add it in this PR.

@arkaitzj just do it.


How to find neighboring cells?

Hi, thanks for the awesome package!
I'm wondering how to go about finding neighboring cells of the same dimension? I was considering doing something like this for triangular meshes:
var edges = complex.skeleton(cells, 1);
var edgeIncidence = complex.incidence(edges, cells);
var neighbors = complex.incidence(cells, edges); # <- in order to find the cells which share an edge

But neighbors always appears to be full of empty relations. Is complex.incidence only meant to be used in the case where the dimension of the first argument is smaller than the dimension of the second? Or am I thinking about the problem wrong? Thanks!

Nevermind, figured it out:
for (var i = 0; i < cell.length; i++) {
   var j = (i + 1) % cell.length;
   var edge = [cell[i], cell[j]];
   var edgeIndex = complex.findCell(edges, edge);
  var neighbor = edgeIncidence[edgeIndex];


[Feature Request] Option to distinguish app version by version name

For example, with development builds of my app Shosetsu, I don't increment the versionCode when making a release.
This option would allow a developer to have more variety in how reports are organized.

I'll mark this as enhancement, but probably won't implement it. It's high effort low value.


Bug: ReferenceError: self is not defined

After import Picker from "react-mobile-picker", this error will show.

Hi @abe1272001, you can find a running demo at https://adcentury.github.io/react-mobile-picker/ and the code in the examples folder. If this can't help you fix this issue, can you provide a minimal producible example so we can take a look? Thanks.

@adcentury Hi, thanks to your reply. Here is the example

Hi, unfortunately I have this issue too in Nextjs

Sorry, I don't test it with next.js or react 18. Since I don't have enough time to fix it right now, contributions are welcome.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_fbee48b1-fadf-4f37-bbc7-c00666b22a41/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_fbee48b1-fadf-4f37-bbc7-c00666b22a41.git

Docs Build status updates of commit a28b5b6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add DOMRect polyfill

This is a PR to add a simple DOMRect polyfill.
Spec: https://www.w3.org/TR/geometry-1/#DOMRect
MDN: https://developer.mozilla.org/en-US/docs/Web/API/DOMRect
We currently need a DOMRect polyfill for IE/Edge support in WordPress' new block-based approach to editing, and it seems better to submit it to a polyfill library we appreciate than to maintain it privately.

Hi @JakeChampion, would you be up for taking a look at this?


Added JDBC-integration

Enhanced SQL Database Integration via JDBC API
This PR marks a significant advancement in our project by introducing seamless integration with SQL databases through the JDBC API, addressing issues #212 and #124.
Key Features:
This enhancement empowers our framework to read data from SQL databases with remarkable flexibility, offering the following reading regimes:

Table-based Reading: Retrieve data from specific tables by name.
Database Exploration: Read all non-system tables within the database.
ResultSet Access: Directly access and read data from ResultSet objects.
Complex Query Results: Fetch results from intricate SQL queries, including joins between two or more tables.

Each reading regime allows for either utilizing a provided database connection or establishing a connection internally if the database configuration details are available. Furthermore, every method within these regimes offers two variants: with and without result limits.
Schema Information:
In addition to data retrieval, this enhancement provides the capability to obtain schema information for the results. You can retrieve the schema of individual tables, ResultSet objects, SQL queries, or even acquire schemas for all non-system tables within the database.
Supported Databases:
This implementation currently supports the following databases:

MySQL
MariaDB
SQLite
PostgreSQL
H2

Please note that while PostgreSQL is supported, certain data types may not be fully accommodated yet.
To gain a comprehensive understanding of this new functionality, I strongly recommend consulting the documentation.
Note: The plugin support is a work in progress and not yet complete; kindly disregard this aspect for now. Your feedback and contributions are highly valued as we continue refining this feature.

@koperagen @Jolanrensen @ermolenkodev please have a look to be familiar with the code/changes.

Awesome job! I'll leave some small comments here and there for now and play around with it a bit :)

Thanks for the initiative!
We are using Trino:
https://trino.io/docs/current/client/jdbc.html
Would it be possible to make the DbType not sealed?
Then in the DatabaseConfiguration we could pass in a custom implementation of the DbType, which would superceed the automatic selection.

@PaulWoitaschek thanks for the feedback, I will think about making nor sealed

@zaleslaw
For inspiration you can also check how exposed did it:
https://github.com/JetBrains/Exposed/blob/30a9ce0f7d6a98630147bcd8da648d974c6b63c0/documentation-website/Writerside/topics/Frequently-Asked-Questions.md?plain=1#L58


Support strings

Any pointer to where the specification (in terms of the JRuby implementation) can be found?

From a blog post giving an overview of ivars and strings:
http://jakegoulding.com/blog/2013/01/16/another-dip-into-rubys-marshal-format/
From the JRuby source:
https://github.com/jruby/jruby/blob/master/core/src/main/java/org/jruby/RubyString.java#L5220-L5224
https://github.com/jruby/jruby/blob/3485ab608b89dc31e7de71493f719a93d168900e/core/src/main/java/org/jruby/runtime/marshal/UnmarshalStream.java#L294-L309

There's also a an implementation in go which might be easier to navigate than the JRuby codebase.
https://github.com/adjust/gorails/blob/master/marshal/marshal.go

Quite nice to see we were not the only folks trying to do this.

Yeah, that's true. I think the go implementation emerged first because so many Ruby defectors have moved to go in recent times.
They conveniently also worked on supporting Rails sessions and probably where we should go next once we have a subset of necessary Ruby objects. https://github.com/adjust/gorails/tree/master/session

Go here next https://github.com/filib/ruby-marshal/issues/16.


Some characters do not escape correctly

Both $ and } should get escaped as \\$ and \\} respectively . For example, selecting and creating a snippet out of
            "program": "${workspaceRoot}/main.go"

fails to render correctly when used otherwise.

Seems none of the snippet makers successfully create the snippet every time. Most times the snippet is just not there after creation. So giving up on these 😞


feature/pdct 1441 Add family_import_id and import_id to GCF document parser

What's changed?

Add family_import_id and import_id to GCF document parser
Fixed docstring formatting inconsistency
Refactored document parser code into smaller functions
Changed document parser tests to use mock data instead of real GCF data & simplified fixtures

Proposed version
Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

[ ] Skip auto-tagging
[x] Patch
[ ] Minor version
[ ] Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.
Notes:

If none of these options are selected, auto-tagging will fail
Where multiple options are selected, the most senior option ticked will be
used -- e.g. Major > Minor > Patch
If you are selecting the version in the list above using the textbox, make
sure your selected option is marked [x] with no spaces in between the
brackets and the x

https://linear.app/climate-policy-radar/issue/PDCT-1441/add-family-import-id-to-gcf-document-mapping


Add a constant for ripple epoch offset

Issue Description
The epoch offset is currently hard-coded in multiple files as seconds(946684800) in (core/Pg.cpp, basics/chrono.h) and as days(10957) (core/impl/TimeKeeper.cpp, test/jtx/impl/ManualTimeKeeper.cpp).
Epoch offset: 2000-01-01 00:00:00 UTC is 946684800s from 1970-01-01 00:00:00 UTC
Expected Result
Define a constant

Here's one verbose but readable way to write this constant:
#include <date/date.h>
// ...
std::chrono::seconds constexpr offset = date::sys_days{year{2000}/1/1} - date::sys_days{year{1970}/1/1};

I have this in https://github.com/XRPLF/rippled/pull/4775


Directory Text

The directory text in the latest version is hard to see.

I added small fix for this issue :)


i made it better

By removing everything from this project i have made it 9001 times faster

I'll need to review all the changes before I can merge this.


Not working

Hello, when I try to run it it returns syntax error ...

No I have this error  .... Can't locate Curses.pm in @INC (you may need to install the Curses module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at ./game line 2.

You have to install libcurses-perl package for it to work. Might be named differently in your linux distro.


Fix tagging for build artifacts

Signed-off-by: Timothy St. Clair<EMAIL_ADDRESS>@chuckha this will fix the build artifacts to have proper tagging, eg - :v0.9.0

self merging to get the artifact in place, it's pretty trivial.


Cannot yield* a SagaIterator in TS 3.6+

The documentation suggests that we can yield* a Saga to compose them.
However, this isn't possible in TS 3.6+ if the yielded Saga is annotated as SagaIterator: https://codesandbox.io/s/dry-forest-gni5e
import { Action } from "redux";
import { SagaIterator } from "redux-saga";
import { takeEvery, call, put } from "redux-saga/effects";

const INCREMENT = "INCREMENT";
const DECREMENT = "DECREMENT";
const LOG = "LOG";

export function reducer(state = 0, action: Action) {
  switch (action.type) {
    case INCREMENT:
      return state - 1;
    case DECREMENT:
      return state + 1;
    default:
      return state;
  }
}

export function* watchSaga(): SagaIterator {
  yield takeEvery(INCREMENT, function*(action: Action<typeof INCREMENT>) {
    yield put({ type: LOG, message: "Increment!" });
  });

  yield takeEvery(LOG, function*(action: Action<typeof LOG>) {
    yield call(console.log.bind(console), (action as any).message);
  });
}

export function* rootSaga(): SagaIterator {
  yield* watchSaga();
}

This is the type error:
Type 'SagaIterator<any>' must have a '[Symbol.iterator]()' method that returns an iterator.

For TS <= 3.5, this type definition is used, which makes it possible:
export type SagaIterator = IterableIterator<StrictEffect>

But for TS >= 3.6, this is used instead, which is no longer Iterable:
export type SagaIterator<RT = any> = Iterator<StrictEffect, RT, any>

One can do this instead:
export function* rootSaga(): SagaIterator {
  yield fork(watchSaga);
}

But it is not strictly the same.
Is the type definition wrong, or is the documentation wrong, or is this just a limitation due to the stricter generator checking in TS 3.6?

@gilbsgilbs could you check this out?
@angelsl keep in mind that the documentation is not written with TS in mind, so differences between what is possible when using plain JS and what is possible by default when using TS are somewhat expected. For instance, it's possible to just yield anything - for example a number, but types shouldn't quite allow this because it doesn't make much sense. There is little to no gain in using yield* over yield fork() and in general the latter is recommended.

+1 on this
I get that the documentation is not written for TS in mind, but I still think this is an error in the typings. For what it's worth, I just ran into a case where I needed to use yield* in a saga.

I have same problem. As a temporary solution I have created this type which use Generator from lib.es2015.generator.d.ts.
type ExpandableSaga<Args extends any[] = any[], R = void> = (...args: Args) => Generator<StrictEffect, R, any>;
It is combination of Saga and SagaIterator types. In most cases my saga does not return any value, that is why return type is set to void by default.
Generator type contains [Symbol.iterator](): Generator<T, TReturn, TNext>; so it can be used with yield*.


Elastic search mongo-connector error

Any idea what I might be doing wrong here?
appserver232@apps:/$ mongo-connector -m mongodb://user:pass@server1:64697,server1:64696/catalogdb -t<EMAIL_ADDRESS>-d elastic_doc_manager.py -n catalogdb.summary --auto-commit-interval=60
No handlers could be found for logger "mongo_connector.util"
Traceback (most recent call last):
File "/usr/local/bin/mongo-connector", line 11, in
sys.exit(main())
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/util.py", line 85, in wrapped
func(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/connector.py", line 950, in main
conf.parse_args()
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/config.py", line 114, in parse_args
option, dict((k, values.get(k)) for k in option.cli_names))
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/connector.py", line 778, in apply_doc_managers
module = import_dm_by_name(dm['docManager'])
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/connector.py", line 768, in import_dm_by_name
"Could not import %s." % full_name)
mongo_connector.errors.InvalidConfiguration: Could not import mongo_connector.doc_managers.elastic_doc_manager.py.

Made few changes and now I'm getting the error below.
[ec2-user@ip-xxx-16-0-xxx ~]$ mongo-connector -m server1:64697 -t https://elastic-search-server -d elastic_doc_manager -n catalogdb.summary --admin-username user --password pass --auto-commit-interval=60
/usr/lib/python2.6/site-packages/elasticsearch/connection/http_urllib3.py:50: UserWarning: Connecting to elastic-search-server using SSL with verify_certs=False is insecure.
'Connecting to %s using SSL with verify_certs=False is insecure.' % host)
No handlers could be found for logger "elasticsearch"
Traceback (most recent call last):
File "/usr/bin/mongo-connector", line 11, in
sys.exit(main())
File "/usr/lib/python2.6/site-packages/mongo_connector/util.py", line 85, in wrapped
func(*args, **kwargs)
File "/usr/lib/python2.6/site-packages/mongo_connector/connector.py", line 950, in main
conf.parse_args()
File "/usr/lib/python2.6/site-packages/mongo_connector/config.py", line 114, in parse_args
option, dict((k, values.get(k)) for k in option.cli_names))
File "/usr/lib/python2.6/site-packages/mongo_connector/connector.py", line 789, in apply_doc_managers
dm_instances.append(module.DocManager(target_url, **kwargs))
File "/usr/lib/python2.6/site-packages/mongo_connector/doc_managers/elastic_doc_manager.py", line 65, in init
self.run_auto_commit()
File "/usr/lib/python2.6/site-packages/mongo_connector/doc_managers/elastic_doc_manager.py", line 279, in run_auto_commit
self.elastic.indices.refresh()
File "/usr/lib/python2.6/site-packages/elasticsearch/client/utils.py", line 68, in _wrapped
return func(args, params=params, **kwargs)
File "/usr/lib/python2.6/site-packages/elasticsearch/client/indices.py", line 53, in refresh
params=params)
File "/usr/lib/python2.6/site-packages/elasticsearch/transport.py", line 307, in perform_request
status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)
File "/usr/lib/python2.6/site-packages/elasticsearch/connection/http_urllib3.py", line 86, in perform_request
self._raise_error(response.status, raw_data)
File "/usr/lib/python2.6/site-packages/elasticsearch/connection/base.py", line 102, in _raise_error
raise HTTP_EXCEPTIONS.get(status_code, TransportError)(status_code, error_message, additional_info)
elasticsearch.exceptions.NotFoundError: TransportError(404, u'IndexMissingException[[] missing]')

@TissonMathew
Does Elasticsearch have any indexes before starting Mongo Connector? It looks like this error is happening when Mongo Connector is trying to refresh all indexes on Elasticsearch, though I'm not really sure why an index would be "missing."
Can you please provide logs from Elasticsearch itself when this happens? Thanks.

Please refer to #214

Resolved.

@TissonMathew
when i typed
mongo-connector -m localhost:27017 -t localhost:9200 --fields title,text -d mongo_connector/doc_managers/elastic_doc_manager.py
command to start  mongo-connector then i found error
No handlers could be found for logger "mongo_connector.util"
Traceback (most recent call last):
File "/usr/local/bin/mongo-connector", line 9, in
load_entry_point('mongo-connector==2.1.dev0', 'console_scripts', 'mongo-connector')()
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/util.py", line 85, in wrapped
func(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/connector.py", line 999, in main
conf.parse_args()
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/config.py", line 118, in parse_args
option, dict((k, values.get(k)) for k in option.cli_names))
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/connector.py", line 779, in apply_doc_managers
module = import_dm_by_name(dm['docManager'])
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/connector.py", line 769, in import_dm_by_name
"Could not import %s." % full_name)
mongo_connector.errors.InvalidConfiguration: Could not import mongo_connector.doc_managers.mongo_connector/doc_managers/elastic_doc_manager.py
can you resolve this
.....

I think your usage is wrong. Check out
https://github.com/10gen-labs/mongo-connector/wiki/Usage with ElasticSearch.
Also, please open a new issue for further help.
On 05/05/2015 06:02 AM, memayank00 wrote:

@TissonMathew https://github.com/TissonMathew
when i typed
mongo-connector -m localhost:27017 -t localhost:9200 --fields
title,text -d mongo_connector/doc_managers/elastic_doc_manager.py
command to start mongo-connector then i found error
No handlers could be found for logger "mongo_connector.util"
Traceback (most recent call last):
File "/usr/local/bin/mongo-connector", line 9, in
load_entry_point('mongo-connector==2.1.dev0', 'console_scripts',
'mongo-connector')()
File
"/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/util.py",
line 85, in wrapped
func(/args, */kwargs)
File
"/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/connector.py",
line 999, in main
conf.parse_args()
File
"/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/config.py",
line 118, in parse_args
option, dict((k, values.get(k)) for k in option.cli_names))
File
"/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/connector.py",
line 779, in apply_doc_managers
module = import_dm_by_name(dm['docManager'])
File
"/usr/local/lib/python2.7/dist-packages/mongo_connector-2.1.dev0-py2.7.egg/mongo_connector/connector.py",
line 769, in import_dm_by_name
"Could not import %s." % full_name)
mongo_connector.errors.InvalidConfiguration: Could not import
mongo_connector.doc_managers.mongo_connector/doc_managers/elastic_doc_manager.py
can you resolve this
.....
—
Reply to this email directly or view it on GitHub
https://github.com/10gen-labs/mongo-connector/issues/211#issuecomment-99072645.

@TissonMathew
yeah... it's working but after then this command suddenly mongo-connector became shutdown and into my log file  this is the error..
2015-05-06 14:00:37,838 [ERROR] mongo_connector.connector:277 - No replica set at "localhost:27017"! A replica set is required to run mongo-connector. Shutting down...
2015-05-06 15:06:32,370 [ERROR] mongo_connector.connector:277 - No replica set at "localhost:27017"! A replica set is required to run mongo-connector. Shutting down...
2015-05-06 15:06:44,661 [ERROR] mongo_connector.connector:277 - No replica set at "localhost:27017"! A replica set is required to run mongo-connector. Shutting down...
i know this is why because i can not create the replica set of mongodb
so can you please  suggest me how can i create replica set . actually i am brand new to mongodb so can you please suggest me ....


Alter criteria for IDing versioned content

Summary
This code was checking for .x in directory names to identify the directory as containing versioned content. Though there are currently no other sibling directories at that tier (app/), looking for a mere . would suffice, but replacing with a regular expression that looks for values like 1.0 or 1.0.1 or 1.0.x but not about or _includes.
Full changelog
Just one change.

[x] Commit message & atomicity checked
N/A Documentation
N/A Spellchecked my updates
[x] Ready to be merged

@briandominick the Travis build fails, as does my attempt to run this locally - I get:
Coopers-Kong-MacBook-Pro:docs.konghq.com cooper$ npm start

><EMAIL_ADDRESS>prestart /Users/cooper/Documents/GitHub/docs.konghq.com
> npm test

><EMAIL_ADDRESS>test /Users/cooper/Documents/GitHub/docs.konghq.com
> standard && echint --verbose

><EMAIL_ADDRESS>start /Users/cooper/Documents/GitHub/docs.konghq.com
> gulp

[18:04:40] Using gulpfile ~/Documents/GitHub/docs.konghq.com/gulpfile.js
[18:04:40] Starting 'clean'...
[18:04:41] Finished 'clean' after 337 ms
[18:04:41] Starting 'default'...
[18:04:41] Starting 'javascripts'...
[18:04:41] Starting 'images'...
[18:04:41] Starting 'fonts'...
[18:04:43] all files 94.83 kB
[18:04:43] Finished 'javascripts' after 1.94 s
[18:04:43] all files 2.77 MB
[18:04:43] Finished 'fonts' after 1.94 s
[18:05:04] gulp-imagemin: Minified 166 images (saved 1.11 MB - 37.1%)
[18:05:04] all files 1.95 MB
[18:05:04] Finished 'images' after 23 s
[18:05:04] Starting 'build'...
[18:05:04] Starting 'jekyll'...
[18:05:06] Configuration file: jekyll.yml
            Source: app
       Destination: ./dist/
 Incremental build: disabled. Enable with --incremental
      Generating...
jekyll 3.3.1 | Error:  undefined method `match?' for "404.html":String
Did you mean?  match

[18:05:06]
[18:05:06] 'jekyll' errored after 1.97 s
[18:05:06] Error: Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

    at ChildProcess.exithandler (child_process.js:276:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:915:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
[18:05:06] 'default' errored after 25 s
[18:05:06] Error in plugin 'run-sequence(jekyll)'
Message:
    Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

Details:
    killed: false
    code: 1
    signal: null
    cmd: bundle exec jekyll build --config jekyll.yml --destination ./dist/
Stack:
Error: Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

    at ChildProcess.exithandler (child_process.js:276:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:915:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
[18:05:06] 'build' errored after 1.97 s
[18:05:06] Error in plugin 'run-sequence(default)'
Message:
    Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

Details:
    killed: false
    code: 1
    signal: null
    cmd: bundle exec jekyll build --config jekyll.yml --destination ./dist/
Stack:
Error: Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

    at ChildProcess.exithandler (child_process.js:276:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:915:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
[18:05:06] 'build' errored after 1.97 s
[18:05:06] Error in plugin 'run-sequence(jekyll)'
Message:
    Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

Details:
    killed: false
    code: 1
    signal: null
    cmd: bundle exec jekyll build --config jekyll.yml --destination ./dist/
Stack:
Error: Command failed: bundle exec jekyll build --config jekyll.yml --destination ./dist/

    at ChildProcess.exithandler (child_process.js:276:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:915:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/cooper/.npm/_logs/2018-11-06T02_05_06_700Z-debug.log
Coopers-Kong-MacBook-Pro:docs.konghq.com cooper$


Disable benchmarks in PRs

In order to keep PR pages less spammy / more readable.
Having the benchmarks on commits on main is enough imo

It's a way to detect regressions in performance sensitive methods like map


DefaultPublicRoute missing DependsOn?

Hi!
Thanks for the example, it is very helpful to me!
Should not a DependsOn on the InternetGatewayAttachment be added to the DefaultPublicRoute resource?
Indeed it looks like working better when present. in order to prevent having that type of error:
route table rtb-xxxxxxx and network gateway igw-xxxxx belong to different networks.
DefaultPublicRoute:
    Type: AWS::EC2::Route
    DependsOn: InternetGatewayAttachment
    Properties:
      RouteTableId:
        Ref: RouteTablePublic
      DestinationCidrBlock: <IP_ADDRESS>/0
      GatewayId:
        Ref: InternetGateway

Cheers!

Thanks Adrien, i'm glad you found this useful.
Good spot with the DependsOn - i'll get this added.


kiosk in xbox store: sizzle reel thumbnail doesn't reflect kiosk functionality

The Xbox store listing includes a sizzle reel that is more about Arcade than Kiosk specifically. This is fine, but its thumbnail shows a simulator with border and controls, something we hide in kiosk mode. We should change the thumbnail to something familiar to kiosk. What it looks like today:

Also visible here:
https://www.xbox.com/en-US/games/store/makecode-arcade-kiosk/9p3rgvvtvb1s

Won't fix.


I think "paint" command never gets added ingame because there's already a "paint" command, so I changed that

https://github.com/Sceleratis/Adonis/blob/master/MainModule/Server/Commands/Players.lua#L130
As you see, currently it is Paint =
and the command :paint also has the same thing Paint =, perhaps that this causes a conflict and why that one :paint command never exists ingame, so I made changes to that, but perhaps that you might want to modify it in a different way, I just did it like this now.

Now we have 2 paint commands bruh

Now we have 2 paint commands bruh

Yeah but one has the prefix : and the other one has the prefix ! not sure if the "name" of the command causes any issues if they're the same, but it did regarding Paint =

still two paints

still two paints

idk someone fix it then

there


Enable saving scripts when running ngrinder-controller with context path

Resolve #389 issue.
New version of lucy xss servlet filter works fine with context path.
Script editor shows unescaped html (#385)

Can one of the admins verify this patch?

Will be reopened with the branch name hotfix/**


Allow BusyBar to shrink

Returning getWidth() dynamically for getPrefWidth() allows
BusyBar to grow but not shrink when the parent layout resizes.
segmentWidth should be a sensible prefWidth for this widget.
This is to address #316

Lemme rebase properly and try again.


Thanks to All authors

I am able  enable or disable driver verifier  commands  successfully.
I did various types of  test uisng different commands for  different  system drivers

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

ID: e566c865-f476-1ffa-242a-b7679b0b6115
Version Independent ID: 4f6e4b0e-cf22-99d6-f00d-0442b137afb2
Content: Driver Verifier - Windows drivers
Content Source: windows-driver-docs-pr/devtest/driver-verifier.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @EliotSeattle
Microsoft Alias: eliotgra

Excellent, @RAJU2529
Thanks for the shout out. Glad things are working for you.
Eliot


Make unsafe APIs more narrow in scope

Hello!  First: thanks for all the work you guys have put into building this new version of the Rust bindings to OpenEXR.  I maintained the previous set of bindings along with Benjamin Saunders, so I know how much work it can be, and how hard it can be to get right!
Anyway, browsing through the documentation, I was confused that Slice's constructors weren't marked as unsafe, since they take raw pointers which can't be bounds checked.
Of course, it's perfectly fine to create and store raw pointers--doing so isn't unsafe.  It isn't until you operate on them that it actually becomes unsafe.  So after a bit of thought, it became clear that, indeed, the Slice constructors aren't unsafe in isolation.  This crate instead makes the choice to mark e.g. write_pixels() as unsafe, since that's where the Slice is actually operated on.
While this is perfectly fine from a technical standpoint, from an API standpoint it doesn't feel great.  If something goes wrong (e.g. a segfault) when calling write_pixels(), then from the standpoint of someone who isn't familiar with the crate's implementation, almost anything done up to that point could be the source of the problem.  Any of the things passed to write_pixels() could be bogus in some way.  In other words, it makes the possible sources of unsafety very broad and non-specific.
We can make the unsafety in the API more narrow (in some sense) by marking write_pixels() as safe, and instead marking as unsafe any places where (unsafely) bogus data can be constructed.  For example, the Slice constructors that take raw pointers.
This is similar to the approach taken by e.g. str slices in Rust.  Instead of marking every method that operates on str slices unsafe, they just mark functions that have the potential to construct bogus str slices as unsafe.  This is a much narrower surface area in the API, and makes it far more specific where something may have gone wrong.
Granted, Slice will need to be changed a bit to accommodate this.  Specifically, it currently lacks a lifetime parameter.  But it should probably have a lifetime parameter anyway: it does, after all, represent a reference to data.
This would also open up the possibility of actually safe Slice constructors, that simply take a (Rust) slice to the data rather than a raw pointer, and can properly validate things.  This would provide a fully safe API through the entire OpenEXR pipeline, and would just generally make the APIs harder to accidentally misuse.

Hey Nathan,
Thanks for letting us have the OpenEXR crate, and bringing up this issue.
I could be wrong, but the APIs you brought up are something we're looking
into marking as unsafe. We're thinking of allowing certain APIs in the
bindings we write be marked as unsafe, and to have a safe layer written in
top at a later date (discussion is here:
https://github.com/vfx-rs/organization/issues/9)
I am not sure which API we are planning on pulling out and mark unsafe
instead, but it could be this one. Anders would know more.
On Thu, Oct 14, 2021, 12:35 PM Nathan Vegdahl @.***>
wrote:

Hello! First: thanks for all the work you guys have put into building this
new version of the Rust bindings to OpenEXR. I maintained the previous set
of bindings along with Benjamin Saunders, so I know how much work it can
be, and how hard it can be to get right!
Anyway, browsing through the documentation, I was confused that Slice
https://docs.rs/openexr/0.10.1/openexr/core/frame_buffer/struct.Slice.html's
constructors weren't marked as unsafe, since they take raw pointers which
can't be bounds checked.
Of course, it's perfectly fine to create and store raw pointers--doing so
isn't unsafe. It isn't until you operate on them that it actually becomes
unsafe. So after a bit of thought, it became clear that, indeed, the Slice
constructors aren't unsafe in isolation. This crate instead makes the
choice to mark e.g. write_pixels() as unsafe, since that's where the Slice
is actually operated on.
While this is perfectly fine from a technical standpoint, from an API
standpoint it doesn't feel great. If something goes wrong (e.g. a segfault)
when calling write_pixels(), then from the standpoint of someone who
isn't familiar with the crate's implementation, almost anything done up to
that point could be the source of the problem. Any of the things passed to
write_pixels() could be bogus in some way. In other words, it makes the
possible sources of unsafety very broad and non-specific.
We can make the unsafety in the API more narrow (in some sense) by marking
write_pixels() as safe, and instead marking as unsafe any places where
(unsafely) bogus data can be constructed. For example, the Slice
constructors that take raw pointers.
This is similar to the approach taken by e.g. str slices in Rust. Instead
of marking every method that operates on str slices unsafe, they just
mark functions that have the potential to construct bogus str slices as
unsafe. This is a much narrower surface area in the API, and makes it far
more specific where something may have gone wrong.
Granted, Slice will need to be changed a bit to accommodate this.
Specifically, it currently lacks a lifetime parameter. But it should
probably have a lifetime parameter anyway: it does, after all, represent a
reference to data.
This would also open up the possibility of actually safe Slice
constructors, that simply take a (Rust) slice to the data rather than a raw
pointer, and can properly validate things. This would provide a fully safe
API through the entire OpenEXR pipeline, and would just generally make the
APIs harder to accidentally misuse.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vfx-rs/openexr-rs/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVFQOCV2SC6JPD7UCQWSG3UG4WIZANCNFSM5GAM45IQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi Nathan, thanks for your feedback! As Scott said, I'm actually doing exactly this right now. If you've got any other thoughts we'd love to hear them given your previous experience.
I'm taking the approach of marking only the functions that can actually cause memory issues as unsafe, which in this case is basically read/writre_pixels and friends.
I did toy around a bit with adding lifetimes to Slice, but in the end decided against it as you quickly end up in borrow checker hell if you actually want to do anything with the memory the Slice is referencing.
I started working on a different safe API called "Frame" which you can see here https://github.com/vfx-rs/openexr-rs/blob/0a0590b99841b9e698eb1faa07df3cc91c34bb98/src/core/frame_buffer.rs#L560
This takes a slightly different approach of taking ownership of the memory that will be read to/written and wrapping up the multi-stage Slice stuff in a typestate so that the API can be completely safe. This works pretty well for flat images, but is a bit more troublesome for deeps because of the dependency between the sampleCount Slice and the others. It's also obviously a little more limited than the general Slice API because you have to transfer ownership of the memory to the FramBuffer and then back again, which depending on what you're doing may or may not be a problem, which is why I've left the original unsafe API there too.
Longer term we're hoping to help upstream rework the C++ FrameBuffer API a bit to be safer for all (it seems everyone involved realizes it's not the best design as it currently stands).

I started working on a different safe API called "Frame" which you can see here

Ah!  That's great!  I didn't notice that on my first pass through the documentation.
It would still be nice to have a safe API that doesn't require openexr to actually allocate and own the image data itself.  But for a lot of use cases that's probably fine.

which is why I've left the original unsafe API there too

Oh yeah, for sure.  I'm definitely not advocating to remove the unsafe versions of the APIs--they're really useful.  We had a similar distinction in our previous wrapper: the "happy path" completely safe APIs, and the "full flexibility" unsafe APIs.  I think that's a great approach.

I did toy around a bit with adding lifetimes to Slice, but in the end decided against it as you quickly end up in borrow checker hell if you actually want to do anything with the memory the Slice is referencing.

Ah, yeah, that's fair.  The way we dealt with that in the old bindings was that we didn't expose the slice concept at all, and just directly used FrameBuffer.  For example, in the Examples section here you can see this bit of code:
let mut fb = FrameBuffer::new(256, 256);
fb.insert_channels(&["R", "G", "B"], &pixel_data);

The insert_channels method internally builds the slices from the RGB pixel_data, so the client code never has to even care about them.  The FrameBuffer then holds a reference to pixel_data, so the borrow checker will block certain things, but in general the FrameBuffer is going to be discarded after reading/writing the file anyway, so it doesn't end up being a problem.
I'm not sure if that would be a good fit for the new bindings, which feel like a thinner layer over the C++ API than the old bindings.  But maybe there's some inspiration you can take from that.  Here's the old FrameBuffer API docs if you want to take a peek.

Thanks! Honestly I was also thinking to just completely internalize FrameBuffer to the read/write methods. Covers 99% of use cases, is simple and can be completely safe...


remove statik output from git ignore

enable easy way to remove non generated files by statik which we no longer use.

@nopcoder should this change also include adding to go.mod dependencies
	github.com/rakyll/statik v0.1.7


The method pumpAndSettle() don't wait for the widget to finish.

I have a question about the flutter integration test.
In the integration test we have pumpAndSettle(), which is used to wait for widget to finish, but there are times in tests I have wait for a external API and I need to put for example pumpAndSettle(const Duration(seconds: 5)) because the pumpAndSettle alone does not solve.
My question is, does flutter have another way for me to wait for the widget is finished or it have a method of intercept and wait a external API request.

Actually waiting on a real API request during tests is a bad practice. Use a test stub / mock class for your API calls that return a value like Future.value(myFakeApiResponse).

Hi @Gusttavogs,  This is working as intended when you don't pass a duration to pumpAndSettle it pumps for 100 milliseconds. Passing a duration seems to be the right way  for more please refer the docs https://api.flutter.dev/flutter/flutter_test/WidgetTester/pumpAndSettle.html
Closing as this is neither a bug nor a feature request.


failed to deserialize response: data did not match any variant of untagged enum Output

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
What i get in cli:
WARN Trying again after trace_filter RPC call for block range: [0..0] failed (attempt #10) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), sgd: 5, subgraph_id: QmSTQrdQAYiK925MLAvMepvWKuaSeZxFrE5JbmsrHwRrVZ, component: BlockStream
What i get in web interface:
{
"errors": [
{
"name": "SyntaxError",
"message": "Unexpected 'N'",
"at": 1,
"text": "Not found"
}
]
}
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
cargo run -p graph-node --release --
--postgres-url postgresql://root:root@localhost:5432/graph-node
--ethereum-rpc mainnet:http://<IP_ADDRESS>:7545
--ipfs <IP_ADDRESS>:5001
--debug

Hey @Shevaister this looks like the callhandler functionality isn't working as expected. Are you still having issues here? Closing for now, please re-open if still valid


Requirement of 3D junctions in Gmsh renderer

Please be as descriptive as possible, including: what is expected, why is this feature needed, what is the objective, etc.
What is the feature being requested?
Gmsh renderer does not render the junctions properly for now as there's an issue with having a 2D rectangle for representing the josephson junction within the 3D mesh. Meshing fails when the junction surfaces are fragmented from the vacuum_box. This requires us to extend the junction also to 3D.
This issue is mentioned in the code. Just search for #842 in the code in file renderers/renderer_gmsh/gmsh_renderer.py to go the location.
Enhancement to PR --> #815
What are use cases for this feature?
Think about how this can be done, and how the boundary conditions will have to assigned in Elmer to enable having the junction as a 3D box instead of a 3D sheet.
Some in-depth discussion of the problem
This issue needs to be fixed before we can go ahead with having eigenmode simulations in ElmerFEM, as it is necessary to have the junction fragmented in the vacuum_box for it to act as an inductance. The problem is that since the junction is 2D, when we fragment it with the 3D vacuum_box, it gets embedded into the volume. However, since it's a 2D sheet, the 2D mesh that is generated on the both the sides of the 2D sheet has duplicated nodes, which give a problem when extending the mesh to 3D. Therefore, we need to figure out how to get rid of this problem, or if possible make the junction 3D instead of 2D.

While working on issue #846 , I realised that by changing the fragment_interfaces method to accommodate for thickness=0, we can use 2D junctions as well. Now, once the PR #854 gets merged, the user should be able to use 2D junctions normally for example to do eigenmode simulation in a FEM solver.


Moving vlc-server to separate Dockerfile

Commands and options

You can trigger actions by commenting on this PR:

/update will merge main into this PR

/update


External assets not added to manifest.appcache

Adding external resources, e.g.,
        externals: [           "https://fonts.googleapis.com/css?family=Lato|Oswald" ] will add it to sw.js but doesn't seem to add the resource to the manifest.appcache and so doesn't work on browsers that don't have serviceworker support.

Any update guys on this one ?

See @NekR's answer in #85

AppCache doesn't support cross-origin caches over HTTPS. Do you use https on your site?


Speaker detection with zipformer

Hello guys.
In our lab we have inhouse ADOS database which contains audio of children, therapists and parents. The recordings are very noisy.
We have to build system which will detect speech of child, therapist and parent.
We saw some works for speaker recognition/diarization with a conformer. In order to get some novelty we would like to use Zipformer for this task. Do you think we can use Zipformer for this purpose? Do you think we can train Zipformer with cross-entropy loss? Of course I mean using of Encoder only (without decoder and without joiner).
Thanks,
AlexG.

Hi Alex, I've trained a Zipformer for speaker verification, the training loss is cross-entropy. It worked well.


Small change to allow it to run the docker command for example

Just a quick change. Nothing fancy.

Bah I goofed one moment


RDKB-56356: wifiWebConfig.txt file size is increasing drastically

after multiple blast triggers
Reason for change: blaster webconfig state flag was not clear for device in gw mode.
Test Procedure: trigger blaster and check for overflow in the logs Risks: Low
Change-Id: Ibde1adcda7743a71f335256f241be7ff08597c66

 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.


Missing win-32bit packages on pip (pypi) for python 3.9/3.10

Hi,
are the 32bit packages intentionally missing from the PyPI database? (https://pypi.org/project/pyodbc/#files)
As I see the appveyor config in the repository includes the 32bit version pipelines. But the latest 32bit version for windows is for python 3.8.

I didn't realize the later versions even supported 32-bit Windows.  I also didn't know that Windows 10 used to have a 32-bit version.  (Apparently they recently stopped sending it to manufacturers, so I think it is near the end.)
I'll do some research into adding these to the CI builds.  I'll also see if Github suports everything we need now and if we can drop AppVeyor completely.
We'll want to update the setup.py for 3.8:
https://cibuildwheel.readthedocs.io/en/stable/faq/#windows-importerror-dll-load-failed-the-specific-module-could-not-be-found

are the 32bit packages intentionally missing from the PyPI database?

It appears so:
https://github.com/mkleehammer/pyodbc/blob/b7e944acdeaa3233dcac045d059d93fe46a71989/.github/workflows/ubuntu_build.yml#L210-L211
As a workaround, at least for now, a limited assortment of 32-bit Windows wheels are available from
https://www.lfd.uci.edu/~gohlke/pythonlibs/#pyodbc

Covered by #1084


Issue #10 : Fixed favicon

I've added the favicon. But, using a different icon.

Great @mani200307 🔥


Make the do_async_write function a little cleaner

Codecov Report

Merging #313 into master will increase coverage by 0.01%.
The diff coverage is 88.23%.

@@            Coverage Diff            @@
##           master    #313      +/-   ##
=========================================
+ Coverage   85.49%   85.5%   +0.01%
=========================================
  Files          34      34
  Lines        4880    4878       -2
=========================================
- Hits         4172    4171       -1
+ Misses        708     707       -1

Thank you for updating!


Testing port server

run_tests.py will start a server (if it's not running, or if the running
port server mismatches the 'current' one) that serves ports to use for
tests. The server is left running after run_tests.py finishes, so that
in environments such as Mac and Windows where tests run unshielded from
each other, we don't start jumping on already used ports.

this change also makes httpcli available without the secure library linked in - @jboeuf PTAL

LGTM for http ssl related changes.

Let's get this one in today? (I'd like to be able to deal with fallout if it happens).

Seems this isn't making Windows happy.

https://grpc-testing.appspot.com/job/gRPC_pull_requests/1796/config=dbg,language=csharp,platform=windows/console

Just pushed a (potential) fix

asan really isn't happy. But it seems a side effect of the code not able to connect ? Which still means something is not happy with that PR, maybe ?

Yeah maybe. I'll take a peek.
On Thu, Aug 6, 2015, 5:00 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

asan really isn't happy. But it seems a side effect of the code not able
to connect ? Which still means something is not happy with that PR, maybe ?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2788#issuecomment-128542283.

Fixed memory leaks (I think)

We have asan that is still freaking out. Less than before, but still quite a bit.

Master was too, with #2836. Re-running Jenkins.

Looks fairly clean

Remaining failures seem infrastructural or in progress and unrelated.

Looks like this is breaking all windows builds:  On windows, run_tests.py tries to start port_server. That one fails to start because  the yaml module is not installed in python for windows. Also, it looks like installing python modules on windows is not trivial at all.  Could we switch to JSON?

Yeah we could. It'd also be OK to move the import into the /dump handler.
On Thu, Sep 17, 2015, 8:19 PM Jan Tattermusch<EMAIL_ADDRESS>wrote:

Looks like this is breaking all windows builds: On windows, run_tests.py
tries to start port_server. That one fails to start because the yaml module
is not installed in python for windows. Also, it looks like installing
python modules on windows is not trivial at all. Could we switch to JSON?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2788#issuecomment-141332641.


Revendor artichoke/mruby branched from mruby 2.1.2

<EMAIL_ADDRESS>branched from<EMAIL_ADDRESS>artichoke-vendor branched from mruby at SHA: artichoke/mruby@1a9bdfc
HEAD SHA: artichoke/mruby@e5ed86c
artichoke/mruby diff from 2.1.2: https://github.com/mruby/mruby/compare/2.1.2...artichoke:artichoke-vendor
artichoke/artichoke diff after revendoring: https://github.com/artichoke/artichoke/compare/4515d43...788f156
This PR contains several small changes to Artichoke's mruby-sys C extension, Symbol FFI implementation in Rust, artichoke-backend extn::core Ruby sources, mruby build config, and sys integrations to update to mruby 2.1.2.
Previously, artichoke/mruby was not based on a particular tag of mruby.

This PR was enabled by the "unforking mruby" work detailed and executed in these issues:

#922
#927

Looks like revendoring fixed some test panics on Windows! 🎉
https://github.com/artichoke/artichoke/pull/936/checks?check_run_id=1476320021
Updated in 502f04791df5c17b9bfc742433cf2b3f406c0cb1.


Web: thumbnails in List/Split story titles

https://getsatisfaction.com/newsblur/topics/thumbnail_view_in_web_browser

Hey, this launched! Closing.


Wunderbar tag overflow in some layout

Docked to the left + 90% zoom
Understand that it's hard to cover all permutations, but also don't recall seeing this in the old GUI.

Ah, the old UI just clips it

-- close --
Handled (it's now split to the next line)


MAZE GAME

A classic maze game move from one side to another.

@TusharAMD please assign this to me


Internal Server Error for /jobs API with userId parameter query

I'm submitting a ...

[x] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[x] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

Perform a /GET Request for jobs API with invalid userId parameter. For example: api/2.0/jobs?userId=WRONG
It will return a 500 Internal Server Error
Expected / new behavior:

Should return 400 Bad Request
Minimal reproduction of the problem with instructions:

Anything else:

Do the logs say anything about what went wrong?


ELEVTR problem solution is added from codechef

Hey! I have added ELEVTR problem solution of CodeChef here. Please accept my PR  and help me to contribute in open source.

Sure. I will check .
On Fri, 9 Oct 2020 4:42 pm Vishruth Subramanian<EMAIL_ADDRESS>wrote:

@Vishruth-S requested changes on this pull request.
Could you please add some comments in your solution briefly explaining the
logic used.
This is mentioned in Contributing
https://github.com/Vishruth-S/CompetitiveCode/blob/main/CONTRIBUTING.md#important-note-read-this-before-sending-a-pull-request
guidelines.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Vishruth-S/CompetitiveCode/pull/301#pullrequestreview-505578712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APN2WH45QDI4SIYSJ6ZWAVTSJ3V3LANCNFSM4SJX6DEA
.

Please check it now if it is OK or not.
On Fri, 9 Oct 2020 6:05 pm Swagata Srimani<EMAIL_ADDRESS>wrote:

Sure. I will check .
On Fri, 9 Oct 2020 4:42 pm Vishruth Subramanian<EMAIL_ADDRESS>wrote:

@Vishruth-S requested changes on this pull request.
Could you please add some comments in your solution briefly explaining
the logic used.
This is mentioned in Contributing
https://github.com/Vishruth-S/CompetitiveCode/blob/main/CONTRIBUTING.md#important-note-read-this-before-sending-a-pull-request
guidelines.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Vishruth-S/CompetitiveCode/pull/301#pullrequestreview-505578712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APN2WH45QDI4SIYSJ6ZWAVTSJ3V3LANCNFSM4SJX6DEA
.

@SwagataSrimani  Umm I don't see any changes 😅 . Please check if you have pushed your changes...

Thank you so much.
On Sat, 10 Oct 2020 10:36 am Vishruth Subramanian<EMAIL_ADDRESS>wrote:

Merged #301 https://github.com/Vishruth-S/CompetitiveCode/pull/301 into
main.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Vishruth-S/CompetitiveCode/pull/301#event-3862380726,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APN2WH6LBJBJ2G5VBOZTJS3SJ7TW5ANCNFSM4SJX6DEA
.


sgadmin.sh requires truststore and keystore to have file extention .jks to be parsed as JKS type

https://github.com/floragunncom/search-guard/blob/d844f41371eead76cee4c222cf6fee488049fa2f/src/main/java/com/floragunn/searchguard/tools/SearchGuardAdmin.java#L188
The code will parse truststore and keystore inputs as JKS type only if the file extension is .jks. I could not find mention of this behavior in the documentation.
It would be great if either:

This behavior were documented in the usage of the script
It was possible to provide the storetype on the cmdline, similar to how its done in the elasticsearch.yml

I came across this today as well. +1 to option 2
On Jun 29, 2016 6:44 PM, "Max"<EMAIL_ADDRESS>wrote:

https://github.com/floragunncom/search-guard/blob/d844f41371eead76cee4c222cf6fee488049fa2f/src/main/java/com/floragunn/searchguard/tools/SearchGuardAdmin.java#L188
The code will parse truststore and keystore inputs as JKS type only if the
file extension is .jks. I could not find mention of this behavior in the
documentation.
It would be great if either:

This behavior were documented in the usage of the script
It was possible to provide the storetype on the cmdline, similar to how
its done in the elasticsearch.yml

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/floragunncom/search-guard/issues/152, or mute the
thread
https://github.com/notifications/unsubscribe/ABXIEe4aVE89GiGI-5aHnJC-nsq6SMBHks5qQwNngaJpZM4JBrON
.

We will implement this, thanks for reporting.


Runtime-Configurable Engine Options (Similar to FieldTrial / RemoteConfig)

Use case
From what I understand, the Flutter engine currently lacks runtime-configurable options, leaving developers with little flexibility once the engine is initialized. While this works for many use cases, recent developments—such as the introduction of Impeller on Android—have exposed significant issues on specific devices. The diversity of Android hardware and inconsistent Vulkan driver quality further complicate the situation.
Flutter provides limited build-time customization (e.g., <meta-data> in the Android manifest to enable or disable Impeller). However, changing these settings requires a full rebuild and re-deployment. This process is not only time-consuming—especially on iOS, where app review delays are common—but also reduces stakeholders’ confidence in Flutter’s readiness for production environments.
Proposal
Introduce runtime-configurable engine options to provide developers with greater flexibility in managing critical settings. For example, developers could dynamically switch between the legacy Skia renderer and Impeller without requiring a rebuild. If implementing separate controls for each option proves challenging, consider adopting Chromium’s approach using runtime-configurable features or field trials (e.g., Flutter-Use-Impeller/Disabled/). This system enables defining and adjusting options in a centralized, declarative format at runtime.
By enabling runtime-configurable engine options, Flutter developers could:

Gradually roll out new features: Test features like Impeller with a subset of users to ensure compatibility before a full release.
Revert to stable configurations: Quickly disable problematic features if critical issues arise in production.
Enhance stability and reliability: Improve developer confidence and reduce risks associated with device-specific issues.
Streamline development workflows: Avoid lengthy rebuilds and redeployments, saving time and effort.

This change would significantly enhance Flutter’s appeal as a production-ready framework by addressing one of the most critical pain points for developers working in diverse hardware environments.

I'm a bit confused,
to switch between engines at runtime an app should be built for both (or at least ship both)
is that even possible or desirable?


Bump edge runtime 181

What kind of change does this PR introduce?
Bumps Edge Runtime image to 1.8.1 and also increases the CPU limit.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 57.281%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
5
12.31%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
4740

Relevant Lines:
8275

💛  - Coveralls


metacheck/main.c: improved reverse_bit() function

Description

The current implementation of the reverse_bit() function is inefficient.
For arm target, the rbit and rev instructions were used, which significantly increases the speed of the reverse_bit() function.
The performance of the reverse_bit() function can also be improved ( not so significantly ) without using an assembler.
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

[ ] Already covered by automatic testing.
[ ] New test added: (add PR link here).
[ ] Tested by hand on: (list targets here).

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing linter checks and tests passed.
[ ] My changes generate no new compilation warnings for any of the targets.

Special treatment

[ ] This PR needs additional PRs to work (list the PRs, preferably in merge-order).
[ ] I will merge this PR by myself when appropriate.

Yeah, I've noticed that. Sadly there's no builtin for this... What I thought about was LUT table, cheap enough for a byte. IMHO it's hardly worth this ifdef and going with asm, but I would like to let @MaciejPurski decide on this

I was thinking of such solution:
uint8_t reverse_bit(uint8_t in)
{
	uint8_t out = in;

	out = (((out & 0xaa) >> 1) | ((out & 0x55) << 1));
	out = (((out & 0xcc) >> 2) | ((out & 0x33) << 2));
	out = (((out & 0xf0) >> 4) | ((out & 0x0f) << 4));

	return out;
}

@kemonats I like this solution, I think this is the best compromise (I'd like to avoid asm when possible).
On the other hand it might be good idea to add reverse bit function to our stdlib in the future to make a use of the CPU instruction when available

Ok, so we like C version very much, but don't really want to introduce assembler to user applications when possible. So if you would agree to drop the asm version then LGTM and ready to merge

Done. I removed the asm version.


Update Companies Using Express

Hey There !
I have made few updates for the "Companies using Express"  Page.
The list of companies using expressjs can be found  here.
Following things are updated there.
A New Directory is created for this page.
4 New Logos added. (As they are StackShare Verified Users of Express).
UBER was re-branded in last Feb but still here there was old logo of UBER.
Some Logos were not in transparent PNG format so I made them in transparent background so all the logos look consistent.
More spacing between logos added.
*Please ignore GemFile.lock Changes in merge.

@crandmck @hacksparrow PTAL

Thanks!

Welcome @crandmck.
Can I go for the rebuild of whole website with improved UI ?

Can I go for the rebuild of whole website with improved UI ?

Can you be more specific about what you're proposing?
The proper way to do this would be to open a new issue with your specific proposal and why you think it's needed.

Also Can you confirm me that light black coloured "ex" in Helvetica Font is the official logo of Express Js ?

Well, the "logo" is really just the word "Express", styled as it is on the home page.  The little "ex" image is just what we've used for the favicon--I wouldn't call it "official".

I am using Express from last one and half year. Each Library and Framework I use, Have their own Branding, Iconic Logos, and Color theme, But Express is still not having any specific color theme, Iconic brand Logo. We are just having a simple b/w color themed website and a very simple logo type.
If Express Js community have the same thought , then I go ahead for this part to

Suggest a new color theme for all Express Js related stuff. (Like NodeJS has Green+Grey, and they use the same Color Combination on all their stuff, Angular has Pink+White.)
Design a new logo for express, based on our community suggestions.

For the Website Part I will made a proposal soon.


Cache extension installation

According to your documentation it is enough to just installing (nuget page) "Z.EntityFramework.Plus.QueryCache.EFCore" library. When I try to call FromCache() method I could not compile project and got warning  and had to install "Z.EntityFramework.Plus.QueryDeferred.EFCore" library as well.
Is there specific situation we need to install QueryDeferred or is it a must install with Cache extensio ?

Currently, EF Cache && EF Query Future require also Query Deferred.
We added a task to remove the dependencies in both libraries. This should be completed in one or two weeks.


SecretSyncedError when Vault Secret is created via API

Hello,
I get this error whenever I create a secret using the Vault API:
status:
  conditions:
  - lastTransitionTime: "2023-02-08T16:54:55Z"
    message: could not get secret data from provider
    reason: SecretSyncedError

Creating the same secret using the Vault UI is working and syncing the external secret.
Below the code for creating the secret using the API:
import requests
import json

# Token

headers = {'X-Vault-Token': 'xxxxx'}

# Connection to Vault

vaultapi = f'http://vault.prefect-orion-dev:8200'

# Create KV secret engine named prefect
payload_kv = {
  "type": "kv",
  "version": "2",
  "config": {
    "force_no_cache": True,
    "default_lease_ttl": 0,
    "max_lease_ttl": 0
  }
}
requests.post(f'{vaultapi}/v1/sys/mounts/prefect', headers=headers, json=payload_kv)

# Create secret for Google Cloud service account at prefect/gcp/sa path

payload_sa = {
  "type": "service_account",
  "project_id": "my-project",
  "private_key_id": "myprivatekeyid",
  "private_key": "-----BEGIN PRIVATE KEY-----xxxxxx-----END PRIVATE KEY-----\n",
  "client_email"<EMAIL_ADDRESS>  "client_id": "000000000",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509"
}

requests.post(f'{vaultapi}/v1/prefect/gcp/sa', headers=headers, json=payload_sa)

My Kubernetes resources:
apiVersion: v1
kind: Secret
metadata:
  name: vault-token
  namespace: prefect-orion-dev
type: Opaque
data:
  token: xxxxxxxxxx=

---

 apiVersion: external-secrets.io/v1beta1
 kind: SecretStore
 metadata:
   name: vault-backend-prefect
   namespace: prefect-orion-dev
 spec:
   provider:
     vault:
       server: http://vault.prefect-orion-dev:8200
       path: prefect
       version: v2
       auth:
        tokenSecretRef:
          name: vault-token
          key: token

---

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: my-cool-secret-prefect
  namespace: prefect-orion-dev
spec:

  refreshInterval: "15s"
  secretStoreRef:
    name: vault-backend-prefect
    kind: SecretStore
  target:
    name: my-cool-new-secret-prefect
    creationPolicy: Owner
  data:
    - secretKey: my-cool-new-secret-key
      remoteRef:
        key: gcp/sa

Can you get external-secrets logs as well?

Error log for when i create the secret via API:
{"level":"error","ts":1675878504.3307962,"logger":"controllers.ExternalSecret","msg":"could not get secret data from provider","ExternalSecret":"prefect-orion-dev/my-cool-secret-prefect","error":"Secret does not exist","stacktrace":"github.com/external-secrets/external-secrets/pkg/controllers/externalsecret.(*Reconciler).Reconcile\n\t/home/runner/work/external-secrets/external-secrets/pkg/controllers/externalsecret/externalsecret_controller.go:190\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:235"}
The secret is there:

As soon as i delete the kv engine (named prefect) and secret created with API and recreate everything manually the external secret goes active:
{"level":"info","ts":1675878774.6796513,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"prefect-orion-dev/my-cool-secret-prefect"}

I don't think creating a kv with requests.post(f'{vaultapi}/v1/sys/mounts/prefect', headers=headers, json=payload_kv) is actually producing a valid store from ESO point of view. Probably that is the underlying issue here.

Not sure if it's the same cause, but I had the same symptoms when creating secrets via the CLI (E.g: vault kv put ...).
It turned out that I needed to specify the version when enabling the kv store: vault secrets enable -version=2 kv. If you omit the -version option, it seems to default to 1.


NIFI-8163: When counting number of components, we traverse into all P…

…rocess Groups, but then call findAllRemoteProcessGroups, which is a recursive call, instead of calling getRemoteProcessGroups(). This results in counting the Process Groups many times. So fixed that.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Reviewing...

Reviewing...

Tested this out and could see the count issue without the fix. Rebuilt with fix and the counts are coming up correct now. Cool, looks good, +1, will merge.

Tested this out and could see the count issue without the fix. Rebuilt with fix and the counts are coming up correct now. Cool, looks good, +1, will merge.


Inline Verbatim Syntax

I suggest adding a note to the documentation for the Verbatim tag to point out that a string literal can be used for inline verbatim text. I found that Pebble works the same as the popular Jinja2 Python template engine in this regard. However, the documentation for Jinja2 addresses inline verbatim text (referred to as inline raw text in Jinja2), but Pebble docs doesn't. I actually assumed that I had to use the verbatim tag inline, which looked terrible and only realized that I could do the same as in Jinja2 when I was about to post an enhancement request here.
For example, I am need to include {{ in the output of a template with text before and after it on the same line. I found that I could do the following in Pebble...
     {{ "{{" }}

However, I made several templates where I didn't know that I could do this and so I did the following...
    {% verbatim %}{{{% endverbatim %}

With other text on the line before and after it, which looked terrible.
Nathan

@ebussieres Hi, pull request seems merged. Close issue?