Creating Testcontainer from custom image doesn't work

I'm writing tests for my room-service and i need the image-service because the room-service has dependencies on the image-service. this is my file tree:
+---image-service
¦   ¦   Dockerfile
¦   ¦   pom.xml
¦   ¦
¦   +---src
¦   ¦   +---main
¦   ¦   ¦   +---java
¦   ¦   ¦   +---resources
¦   ¦   +---test
¦   ¦       +---java
¦   ¦           +---de
¦   ¦               +---fh
¦   ¦                       ApplicationTest.java
+---room-service
¦   ¦   Dockerfile
¦   ¦   pom.xml
¦   ¦
¦   +---src
¦   ¦   +---main
¦   ¦   ¦   +---java
¦   ¦   ¦   +---resources
¦   ¦   +---test
¦   ¦       +---java
¦   ¦       ¦   +---de.fh
¦   ¦       ¦           ApplicationTest.java
¦   ¦       ¦
¦   ¦       +---resources
¦   ¦               application.yml

In my ApplicationTest in room-service I try to create a generic container from the dockerfile in /image-service/Dockerfile:
@BeforeClass
public static void init() {
    eurekaContainer = new GenericContainer(new ImageFromDockerfile("image-service")
            .withFileFromFile("./image-service", new File("../image-service/Dockerfile")));

    eurekaContainer.start();
}

I couldn't find any use cases like this in the documentation.
Am I using the wrong method? Are any of the paths I used wrong?

Hi @jo2,
can you try out the other methods, such as from string and from classpath?

With imageFromString I didn´t know what I should write in the string. Is it the content of the Dockerfile? The documentation only said '.withFileFromString("folder/someFile.txt", "hello")'. Also the declaration of the method doesn´t say anything 'withFileFromString(String path, String content)'.
imageFromClasspath isn´t explained in any better way.

I am currently using withDockerfile method.


Feature request: add an optional expression method for build conditional queries.

Consider the following usage:
let keyword = Some("%keyword%");

schema::post::table
 .filter(title.optinoal().like(title))
 .or_filter(summary.optinoal().like(keyword))

When the keyword is None, the where clause will be where true or true, when keyword is Some("%keyword%"),  the where clause will be where title like '%keyword%' or summary like '%keyword%'.
That will be make it easier to build conditional queries.

It's not clear for me what's the advantage of this approach over the following already supported approach:
let mut query = schema::post::table.into_boxed();

if let Some(title) = title {
    query = query.filter(schema::posts::title.like(title));
}

if let Some(keyword) = keyword {summary
    query = query.or_filter(schema::post::summary.like(keyword));
}

In contrast to the proposed approach this generates exactly the query you specify and does not introduce some place holder statements on sql side.
I'm closing this issue as it is not clear for me what are the advantages of this approach + it is definitively possible to implement as that as third party crate.


CSV Row Generator Tool

I've already used this in enough random one-off experiments that it felt worthwhile to contribute as an official example.
It's a tool that:

Ignores input, and
Generates a new TSV row of a table described by the tool's parameters

Why TSV instead of CSV?

To avoid having to do weird escaping things in the common case.

How can this be used?

When you want to generate a simple object; e.g. (name,age,gender)

Why not use JSON instead?

I think that'd be a great ADDITIONAL tool to commit? What do y'all think? (I feel like there's not much downside to having a pretty big set of example tools)

Example use:
DESCRIPTION = "podcasts"
HEADER = ["Podcast Name", "Podcast Description"]
EXAMPLE_ROWS = [
    ["Animal Planet", "The world is an amazing place. We'll tell you its stories every day."],
    ["Banking News", "All the updates you need to track the banking world."],
    ["Hollywood Gab", "The latest stories from inside Hollywood."],
    ["The MIT Tech Review", "The latest in science and technology, explained."],
    ["Politico", "Hear the opinions and analysis that shapes capitol hill."],
    ["Car Talk", "Call-in show with automotive mysteries, fix-it help, and laughter."],
]

class PodcastPremiseTool(TsvRowGeneratorTool):
    table_description: str = DESCRIPTION
    header_fields: List[str] = HEADER
    example_rows: List[List[str]] = EXAMPLE_ROWS

if __name__ == "__main__":
    with Steamship.temporary_workspace() as client:
        ToolREPL(TsvRowGeneratorTool()).run_with_client(
            client=client, context=with_llm(llm=OpenAI(client=client))
        )

@dkolas here's a "notes from the rough and tumble world of prompt engineering": this approach gets TERRIBLE results when I try it on a bunch of different use cases 😂
It's clean and elegant in theory, but the attention head doesn't seem to be able to track the implications of the header row of CSV or TSV well enough for it to behave the way that's desired.
I've rewritten it (in another project) to be JSON-based, in which the schema is repeated for every example to remind the LLM what fields are desired, and that seems to be working really well.
Will port that over and update here.
The example use case is:
"I want an example of how to generate a structured object"


Domain registrar

Which Cloudflare product(s) does this pertain to?
Email Routing
Subject Matter
Type MX Host @ Value mx02.mail.icloud.com. Priority 10 TXT: Type TXT Host @ Value apple-domain=FtKxyymI4MF4E5DG SPF: Type TXT Host @ Value "v=spf1 include:icloud.com ~all" DKIM: Type CNAME Host sig1._domainkey Value sig1.dkim.xxxg00.com.at.icloudmailadmin.com.
Content Location
New documents

Additional information
Type
MX
Host
@
Value
mx02.mail.icloud.com.
Priority
10
TXT:
Type
TXT
Host
@
Value
apple-domain=FtKxyymI4MF4E5DG
SPF:
Type
TXT
Host
@
Value
"v=spf1 include:icloud.com ~all"
DKIM:
Type
CNAME
Host
sig1._domainkey
Value
sig1.dkim.xxxg00.com.at.icloudmailadmin.com.

Domain registrar

Howdy @Gerrime, it's unclear what changes you want in our documentation based on your issue.
As best I can guess, you might want to check out iCloud custom email domains.
If you're still experiencing issues, I'd encourage you to post in the Cloudflare community or open an issue with Support.


Change retrieving viewable from warning to debug log

Fixes #74

Assuming use_shelves_only is selected, PdsFile tries to get image dimensions (.width and .height properties) from the pickle (previously "shelve") files. Only if a pickle file doesn't exist does it look at the filesystem, read the image file, and derive the image dimensions that way. This used to be an indication of a problem, such as an old pickle file, but now it is a common occurrence. This is because the NH images NH-Boresight-FOVs.png and LORRI-responsivity-plot.png are in the holdings/documents directory, which doesn't have associated pickle files. Thus every time you access one of those files, you get a warning message in the log file, even though this really shouldn't be a warning. During OPUS import, this happens for every single NH observation, making the warnings output nearly unusable.
This pull simply changes that warning message to a debug message, which is more appropriate.

I don't know whether a better long-term solution might be to add a pickle file for documents.  However, in any case, I agree that this should be done at least for now, so that the warning messages can become useful again.

I don't know why Mark didn't make pickle files for the documents directory, but I agree that seems like the better long-term solution. I will open a separate issue for that.


fix(model): fix identify compress field

The field is named compress and not compression.
See https://discord.com/developers/docs/topics/gateway#identify-identify-structure.

Since this is an API mapping fix it's acceptable for 0.2

Also worth noting that because we set this to false (and the API default is false), this will have no actual effect on the gateway

Also worth noting that because we set this to false (and the API default is false), this will have no actual effect on the gateway

I guess this change is more for other people implementing the gateway with the same model as they may nto want to do transport compression. And would rather want payload compression.


Change Project Structure: Move Figures, Remove PDF Duplicates, and Lint Code

Summary

Moved the figure directory:

The figure directory was relocated to the root folder, and all related paths in the code were updated accordingly.

Removed duplicate pdfs:

Duplicated PDF files were removed, and the paths for the remaining ones were adjusted across the project.

Changed code for linting:

Code was updated to comply with linting standards, ensuring better readability and maintainability.

Edit web code

Hey @chosh0615, just a gentle reminder—can you review this PR again?

I think this is not a priority at the moment, so will close the PR.


feat: TypeScript Rewrite

I think you forgot about this

I think you forgot about this

It can't be helped.


Allow NamedRelationship to accept a LabelExpr

This is really just a TS fix. Regular relationships could accept it, but NamedRelationship could not.

Hi @jhanggi
In order to merge this PR, we need you to sign the Neo4j CLA. You have more information, document, and steps to sign here: https://neo4j.com/developer/cla/
If you agree to it, please let me know when you have signed :slightly_smiling_face:

Hi @jhanggi
Were you able to sign the CLA? I'm not able to merge this PR until that process is completed

@angrykoala sorry for the delay. CLA signed and sent


Add Byron Network

Hello,
I would like to add Byron Network to the list of DEXes and Wallets. If there is anything that needs fixing or if you require additional information, please let me know.
Thanks!

Hi @alternateved can you please provide us with your logo, some profiles of the main individuals involved and a URL to your site please. Also if you have a blurb explaining your project please.

Description of Byron Network
Byron Network aims to bring the cutting edge solution for traders, hodlers and blockchain lovers. HD Mobile Wallet and a decentralized exchange on Cardano Blockchain is only the first step in the development of the Byron ecosystem. Our goal is to deliver investment tools and a cryptocurrency gateway for multichain investing for any blockchain enthusiast. Great experience with profound UX, thoughtful components and ability to integrate advantageous API is our top priority.
Team
Our team comprises of experienced developers and knowledgeable crypto experts, passionate about creating the backbone of the crypto trading industry. We have had a 5-year long experience building blockchain projects for our clients as a BinarApps.com software company. We supported projects such as Everest.org, Brave.com, Dash.org, Asdra.com and Minerva. Cardano with its uniqueness is a perfect opportunity for our team to make use of our expertise and contribute to the constantly expanding community. Thanks to the delivery of expectation-exceeding user products we hope to capture the potential behind Cardano Blockchain. Having the years-long yet state-of-the-art experience in the field helped us to understand the market as well as to recognise its need for a release of a cross-chain solution.
Additional information about members of our team can be found at the end of this presentation: https://byron.network/static/byron-network-presentation.pdf
Links and resources
Website: https://byron.network/
Logo: https://raw.githubusercontent.com/byron-network/byron-website/main/src/assets/logo_byron.png

thank you kindly


Import COSMIC VCF.

@tmooney Did we upload the COSMIC VCF for Mutect2?

It's imported, though it's not in the current version of the workflow.


WP_ENV not defined

to include in baobab :
if (!defined('WP_ENV '))
    define('WP_ENV', 'development');

else, in some cases
Use of undefined constant WP_ENV - assumed 'WP_ENV' in /srv/wpca-themes/marvinlabs/app/config/assets.config.php on line 41

By thinking about it, it's a bad idea. This is an user constant that should be added in wp-config, and not in any plugin or third party lib. Closing.


convert data to string before giving it to preg_match

Add a template to fix an invalid PHP call (preg_match receives a DateTime object) see details in https://github.com/OpenAPITools/openapi-generator/pull/16513
This fix is only temporary and should be removed when the next version of the generator is released

This fix is only temporary and should be removed when the next version of the generator is released

Can we create a ticket to remove it later please?
LGTM

@micbar done already in #116


Virtual lists broken

We use virtuoso for performance reasons, so we don't render too much content at once, causing performance issues with the main thread being blocked.
Some recent changes have broken this. See https://github.com/leather-wallet/extension/pull/5148 which demonstrates the issue. We render all items in the list, causing the thread to be blocked while we render the stacks accounts in the list.
https://github.com/leather-wallet/extension/assets/1618764/bc17fb57-609b-4468-8c58-70ff91d45867
Notice the delays, and lack of hover animations, that don't work while the thread is blocked.

I can take a look at this as I may have introduced it with some recent changes fixing bugs

I did some investigation on this today and from what I can see, we have never been using Virtuoso to load only what's visible in the viewport. I went back a fair few versions, to v6.20 and even to Hiro Wallet in v6.0.0.
We always render the full amount of available accounts in this list.
I dug deeper into the code and cross referenced their example code and I think the issue lies in how we are setting the height of Virtuoso. I didn't go back further than v6.0.0 but in there we are setting the list height with this code:
<Virtuoso
        initialTopMostItemIndex={currentAccountIndex}
        height="72px"
        style={{ paddingTop: '24px', height: '70vh' }}

I took a look at their sample code and added it to the APP. That worked and it relates to them specifying the height in this format:
 <Virtuoso
      style={{ height: 400 }}

If I change our lists to use that format then I can see them only loading whats in the viewport. Here's a video to demonstrate:
https://github.com/leather-wallet/extension/assets/2938440/9a904d8e-bc81-45f2-996f-74ac6233172f
We are using Virtuoso in 3 places right now. In the past we had a lot of bugs related to height and accounts being cut off from view. I added fixes for those issues but I think the underlying issue was us not using the height correctly.
I'll work on a fix to those issues now.

We always render the full amount of available accounts in this list.

Nope. See this PR from years ago that fixes render perf issues https://github.com/leather-wallet/extension/pull/2078
In your example, all the account fit in the view, so it renders them all. In video below, with hundreds of accounts, we log the index when the item mounts. Each item renders only when it appears in view.
https://github.com/leather-wallet/extension/assets/1618764/67d0a142-4662-442e-8f74-3ce1e2cac6f9
It looks like it broke in 6262267ff1, where running the same code, we see it render them all
https://github.com/leather-wallet/extension/assets/1618764/27eceef5-16cd-40a4-9ec6-afc1bd3956eb

I had indeed broken this and implemented a fix https://github.com/leather-wallet/extension/pull/5170 that reduces the impact of the bug.
Visually it's not perfect though so I will keep working on it to finish it off in https://github.com/leather-wallet/extension/pull/5171

My workaround means that sometimes the last entry in the list is cut off:

I'll fix this ASAP

The problem with loading all the data was fixed but there is a UI bug I will fix https://github.com/leather-wallet/extension/issues/5242

Closing this as I have fixed the issue in https://github.com/leather-wallet/extension/issues/5242. Pending code review


The property 'nestedModulesSpace' of Stats does not exist

Bug report
It seems that Stats doesn't have a nestedModulesSpace property like it introduced in the doc.

What is the current behavior?

Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.

configuration.stats has an unknown property 'nestedModulesSpace'. These properties are valid:
object { all?, assets?, assetsSort?, assetsSpace?, builtAt?, cached?, cachedAssets?, cachedModules?, children?, chunkGroupAuxiliary?, chunkGroupChildren?, chunkGroupMaxAssets?, chunkGroups?, chunkModules?, chunkOrigins?, chunkRelations?, chunks?, chunksSort?, colors?, context?, dependentModules?, depth?, entrypoints?, env?, errorDetails?, errorStack?, errors?, errorsCount?, exclude?, excludeAssets?, excludeModules?, groupAssetsByChunk?, groupAssetsByEmitStatus?, groupAssetsByExtension?, groupAssetsByInfo?, groupAssetsByPath?, groupModulesByAttributes?, groupModulesByCacheStatus?, groupModulesByExtension?, groupModulesByPath?, hash?, ids?, logging?, loggingDebug?, loggingTrace?, moduleAssets?, moduleTrace?, modules?, modulesSort?, modulesSpace?, nestedModules?, optimizationBailout?, orphanModules?, outputPath?, performance?, preset?, providedExports?, publicPath?, reasons?, relatedAssets?, runtimeModules?, source?, timings?, usedExports?, version?, warnings?, warningsCount?, warningsFilter? }
-> Stats options object.

If the current behavior is a bug, please provide the steps to reproduce.

Assign any integer to stats property nestedModulesSpace in webpack config

  stats: {
    nestedModulesSpace: 15,
  }

Run webpack.

What is the expected behavior?
At least it should have this property.

Other relevant information:
webpack version:  v5.10.0
Node.js version: v12.18.2
Operating System: macOS Big Sur v11.0.1
Additional tools:

Yep, good find, it's missing in the schema. Do you want to send a PR? (Make sure to also run yarn special-lint-fix to update the typings)

Sure, I'll try it when I get some time.

Hi @akasuv, are you working on this? If not, I'll send a PR.

Go ahead

I also tried to fix this and added schema but because of lack of guidance and knowledge I can't fix the issue.
I am closing my Pull request.
@jaiwanth-v  can you explain me how did you tackle this issue and how do you come to know about how this problem can be solved.
I feel much happy to learn from you.

Have a look at my PR, I think you'll understand it.

Have a look at my PR, I think you'll understand it.


Add github style syntax highlighting.

For examle:
```java
class Borsch {
  private static function borshch() {
    return new Borshch();
  }
}
```

In github results in:
class Borsch {
  private static function borshch() {
    return new Borshch();
  }
}

But in remark it just renders
class Borsch {
  private static function borshch() {
    return new Borshch();
  }
}

yeah, we know and even tried to address. The problem is this - the regular md library we use seems to set ids only for colors but doesn't provide styles. External rendering engine I have tried brings way too many dependencies and conflicted with sanitizer.

I tried to implement my change but found out that original markdown is not stored at all, and storage just contains rendered html.
I'm not sure how editing supposed to work with such model either... Do you get to edit html after you entered markdown? If it has colors would it be HTML with all the styles and stuff. Anyway. My suggestion wouldn't work with current model, and I don't know if changing model breaks something.

original markdown is not stored at all

Why is it a problem for syntax highlighting? Maybe you tried to colorize it on the client side?

I'm not sure how editing supposed to work with such model either...

Good point, me neither. Most likely this will require storing md as well.

Yes, my whole comment was about post processing MD on client side with JS. This will allow to use custom post-processing. Basic MD rendering is done how it is now. When comments is loaded client can extend with callback and re-render the comment.
Example would be mathjax/katex. Like include math formulas. This is not needed for casual comments, but some sites may want to allot to use math notations in comments. Another - plug in advanced code highlighting.
Suggestion: everything works as it is now: except add orig(md) field to Comment. It can be used either in "Edit" functionality or in andvaced re-rendering on client side if required. Re-rendering this way can be made user customization, not even requiring to edit anything in Remark. All can be done with parent HTML/CSS/JS.

@Shchvova see https://github.com/umputun/remark/issues/13 trying to decide which way to go

@Reeywhaar - I have checked the current state of fenced code blocks and on my side, it seems to render it correctly

However, I don't do any colorization and probably your side is the right place to make it happen. This way it will be theme-friendy for example.

Yep, should be not that hard.

I made a small research and realize that using JS library will make our bundle really heavy.
Because we need not just lib but an extension for each language what we need to highlight, also it will take time to parse code in runtime every time when a browser renders comment with code.
I found how it solved in Hugo https://gohugo.io/content-management/syntax-highlighting/
It parsed at a server and works like here in github comments.
@umputun @paskal what do you think about this solution?

I have done a quick test integrating bfchroma on the code-colors branch.  It produced colorized code, like this:

func
main(aa
string)
int {return 0}

I have not checked how this render affects anything else. Also, we have to make sure it can support external css and not injecting colors directly
@paskal - if you want to deal with this your are very welcome

I have tried WithClasses() and it produced the expected output:

func main(
aa string)
int {return
0}

Probably we can get ready to use css from github.com/Depado/bfchroma or github.com/alecthomas/chroma/formatters/html. One of them should have them in already.

I think this feature should be disabled by default (because the feature it will download CSS file for code highlight) and we should load CSS only when the feature is enabled.

From UX point of view, I don't really see a reason to make this optional. The CSS extra is not that big I think, and it will be cached anyway.


[DOC] Add example of "CREATE TABLE WITH" including read filter arguments

After #338 merged, we should be able to eliminate unnecessary reads from storage.
A glance at both the API docs page, and the SQL syntax page have no mention of this valuable capability for the keyword arguments supported in CREATE TABLE WITH statements

@DaceT can you tackle this?

Yes, I can!

@DaceT can you tackle this?


Exception runnging ansible 2.8 and mitogen 0.2.8

Hi,
I am facing an exception to run any playbook / ad-hoc command in the following environment:
$ ansible --version
ansible 2.8.4
  config file = /home/ansible/infra/ansible.cfg
  configured module search path = [u'/home/ansible/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

$ python
Python 2.7.5 (default, Sep 12 2018, 05:31:16)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import mitogen
>>> print mitogen.__version__
(0, 2, 8)

Both ansible and mitogen are installed from EPEL repositories on a RHEL 7.7 box.
Works well without mitogen.
Here is the full trace:
$ ansible -m ping localhost -vvv
ansible 2.8.4
  config file = /home/ansible/infra/ansible.cfg
  configured module search path = [u'/home/ansible/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Using /home/ansible/infra/ansible.cfg as config file
host_list declined parsing /home/ansible/infra/inventories/01-wea as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/01-wea as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/01-wea as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/01-wea inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/_vmware.py as it did not pass it's verify_file() method
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
 [WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

Parsed /home/ansible/infra/inventories/_vmware.py inventory source with script plugin
host_list declined parsing /home/ansible/infra/inventories/aix as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/aix as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/aix as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/aix inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/destroy as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/destroy as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/destroy as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/destroy inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/empty as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/empty as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/empty as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/empty inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/exzos as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/exzos as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/exzos as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/exzos inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/inventory as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/inventory as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/inventory as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/inventory inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/old_mysql as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/old_mysql as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/old_mysql as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/old_mysql inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/old_php as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/old_php as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/old_php as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/old_php inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/oldschool as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/oldschool as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/oldschool as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/oldschool inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/pointeuses as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/pointeuses as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/pointeuses as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/pointeuses inventory source with ini plugin
host_list declined parsing /home/ansible/infra/inventories/zabbix_tst as it did not pass it's verify_file() method
script declined parsing /home/ansible/infra/inventories/zabbix_tst as it did not pass it's verify_file() method
auto declined parsing /home/ansible/infra/inventories/zabbix_tst as it did not pass it's verify_file() method
Parsed /home/ansible/infra/inventories/zabbix_tst inventory source with ini plugin
[top  39485] 13:58:00.964105 D ansible_mitogen.affinity: CPU mask for Ansible top-level process: 0x000002
[top  39485] 13:58:00.965085 D ansible_mitogen.process: inherited open file limits: soft=16384 hard=16384
[top  39485] 13:58:00.965264 D ansible_mitogen.process: max open files already set to hard limit: 16384
[mux  39502] 13:58:00.969475 D ansible_mitogen.affinity: CPU mask for MuxProcess 0: 0x000001
[mux  39502] 13:58:00.984485 D mitogen.service: Pool(b190, size=32, th='MainThread'): initialized
[mux  39502] 13:58:00.984978 D ansible_mitogen.process: Service pool configured: size=32
META: ran handlers
[task 39536] 13:58:01.059281 D ansible_mitogen.affinity: CPU mask for WorkerProcess: 0x000002
[task 39536] 13:58:01.076850 D ansible_mitogen.process: will use multiplexer 0 (/tmp/mitogen_unix_LpKoEy.sock) to connect to "localhost"
[task 39536] 13:58:01.077113 D mitogen.unix: client: connecting to /tmp/mitogen_unix_LpKoEy.sock
[task 39536] 13:58:01.077642 D mitogen.unix: client: local ID is 1, remote is 0
[mux  39502] 13:58:01.077822 D mitogen.unix: listener: accepted connection from PID 39536: unix_client.39536
[mux  39502] 13:58:01.079719 D mitogen.parent: creating connection to context 2 using mitogen.parent
[mux  39502] 13:58:01.132095 D mitogen.parent: failing connection None due to AssertionError()
ERROR! [mux  39502] 13:58:01.132694 E mitogen.service: Pool(b190, size=32, th='mitogen.Pool.b190.0'): while invoking u'get' of u'ansible_mitogen.services.ContextService'                                                          [64/17683]
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 621, in _on_service_call
    return invoker.invoke(method_name, kwargs, msg)
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 307, in invoke
    response = self._invoke(method_name, kwargs, msg)
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 293, in _invoke
    ret = method(**kwargs)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 467, in get
    reraise(*result)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 425, in _wait_or_start
    response = self._connect(key, spec, via=via)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 377, in _connect
    context = method(via=via, unidirectional=True, **spec['kwargs'])
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2483, in local
    return self.connect(u'local', **kwargs)
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2443, in connect
    return self._connect(klass, **mitogen.core.Kwargs(kwargs))
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2423, in _connect
    conn.connect(context=context)
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 1705, in connect
    raise self.exception
AssertionError

[WARNING]:
[task 39536] 13:58:01.135219 W ansible_mitogen.connection: Connection failed; stack configuration was:
({u'kwargs': {u'python_path': [u'/usr/bin/python2']}, u'method': u'local'},
 {u'enable_lru': True,
  u'kwargs': {u'connect_timeout': 10,
              u'password': None,
              u'python_path': [u'/usr/bin/python2'],
              u'remote_name': None,
              u'sudo_args': [u'-H', u'-S', u'-n'],
              u'sudo_path': u'sudo',
              u'username': u'root'},
  u'method': u'sudo'})
[task 39536] 13:58:01.138016 D mitogen: MitogenProtocol(unix_listener.39502): disconnecting
[task 39536] 13:58:01.138274 D mitogen: Waker(fd=11/12): disconnecting
[mux  39502] 13:58:01.138283 D mitogen: <Side of unix_client.39536 fd 76>: empty read, disconnecting
[mux  39502] 13:58:01.138490 D mitogen: MitogenProtocol(unix_client.39536): disconnecting
[task 39536] 13:58:01.138570 D mitogen: Router(Broker(3710)): stats: 0 module requests in 0 ms, 0 sent (0 ms minify time), 0 negative responses. Sent 0.0 kb total, 0.0 kb avg.
The full traceback is:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/ansible/executor/task_executor.py", line 145, in run
    res = self._execute()
  File "/usr/lib/python2.7/site-packages/ansible/executor/task_executor.py", line 664, in _execute
    result = self._handler.run(task_vars=variables)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/mixins.py", line 116, in run
    return super(ActionModuleMixin, self).run(tmp, task_vars)
  File "/usr/lib/python2.7/site-packages/ansible/plugins/action/normal.py", line 46, in run
    result = merge_hash(result, self._execute_module(task_vars=task_vars, wrap_async=wrap_async))
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/mixins.py", line 346, in _execute_module
    self._temp_file_gibberish(module_args, wrap_async)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/mixins.py", line 325, in _temp_file_gibberish
    self._connection.get_good_temp_dir()
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/connection.py", line 762, in get_good_temp_dir
    self._connect()
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/connection.py", line 782, in _connect
    self._connect_stack(stack)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/connection.py", line 735, in _connect_stack
    stack=mitogen.utils.cast(list(stack)),
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 120, in call
    return call_context.call_service(service_name, method_name, **kwargs)
  File "/usr/lib/python2.7/site-packages/mitogen/core.py", line 2270, in call_service
    return recv.get().unpickle()
  File "/usr/lib/python2.7/site-packages/mitogen/core.py", line 963, in unpickle
    raise obj
CallError: exceptions.AssertionError:
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 621, in _on_service_call
    return invoker.invoke(method_name, kwargs, msg)
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 307, in invoke
    response = self._invoke(method_name, kwargs, msg)
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 293, in _invoke
    ret = method(**kwargs)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 467, in get
    reraise(*result)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 425, in _wait_or_start
    response = self._connect(key, spec, via=via)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 377, in _connect
    context = method(via=via, unidirectional=True, **spec['kwargs'])
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2483, in local
    return self.connect(u'local', **kwargs)
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2443, in connect
    return self._connect(klass, **mitogen.core.Kwargs(kwargs))
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2423, in _connect
    conn.connect(context=context)
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 1705, in connect
    raise self.exception

localhost | FAILED! => {
    "msg": "Unexpected failure during module execution.",
    "stdout": ""
}
[mux  39502] 13:58:01.148895 D mitogen: Waker(fd=6/8): disconnecting
[mux  39502] 13:58:01.149370 D mitogen: Router(Broker(5b90)): stats: 0 module requests in 0 ms, 0 sent (0 ms minify time), 0 negative responses.
If you allow me a few hours, I will check in some extra logging into master so the full stack trace of the exception can be captured. Apologies for this! I didn't realize the code path capturing that exception could capture such a generic error, it needs more logging
Thanks a ton for reporting this!

would you mind grabbing dmw branch from Git and trying your -vvv run again? There should be a new chunk of log in there, starting with 'failed to start child', that will include the original stack trace

You can also simply grab a ZIP file: https://github.com/dw/mitogen/archive/dmw.zip

I spent some time trying to reproduce on both my Ansible host and new host freshly where Ansible has been freshly installed, with no success.
The issue seemed to be 100% repeatable two days ago, for my colleague and myself (at least 6-7 runs in a row).
The only change on the Ansible host between the time I opened this issue and now is a temporary downgrade of Ansible (to 2.7) to run an incompatible playbook in 2.8, and immediately re-update again. Not sure if it could explain this strange behavior...

During the gather-facts stage of running ansible-playbook, I get a similar error stack trace as #645 on ansible 2.7.5 rhel 7.7 using python2-mitogen 0.2.8. Are there any work arounds or suggestions for finding what the cause is?

I am having the exact same issue on a RHEL7.6 box with the stock mitogen :
$ yum list installed | grep mitogen
python2-mitogen.noarch            0.2.8-1.el7         @base-epel

Stock Ansible and Python from RHEL7.6 :
$ ansible --version
ansible 2.8.4
  config file = /opt/ansible-playbooks-poc/ansible.cfg
  configured module search path = [u'/home/kwyxz/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Jun 11 2019, 14:33:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
$ python
Python 2.7.5 (default, Jun 11 2019, 14:33:56)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import mitogen
>>> print mitogen.__version__
(0, 2, 8)

Any attempt to run Ansible using the mitogen_linear strategy ends with:
TASK [Gathering Facts] **************************************************************************************************************************************************************************************************************[376/1859]
ERROR! [mux  39135] 11:46:37.976392 E mitogen.service: Pool(a090, size=32, th='mitogen.Pool.a090.0'): while invoking u'get' of u'ansible_mitogen.services.ContextService'
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 621, in _on_service_call
    return invoker.invoke(method_name, kwargs, msg)
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 307, in invoke
    response = self._invoke(method_name, kwargs, msg)
  File "/usr/lib/python2.7/site-packages/mitogen/service.py", line 293, in _invoke
    ret = method(**kwargs)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 467, in get
    reraise(*result)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 425, in _wait_or_start
    response = self._connect(key, spec, via=via)
  File "/usr/lib/python2.7/site-packages/ansible_mitogen/services.py", line 377, in _connect
    context = method(via=via, unidirectional=True, **spec['kwargs'])
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2501, in ssh
    return self.connect(u'ssh', **kwargs)
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2443, in connect
    return self._connect(klass, **mitogen.core.Kwargs(kwargs))
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 2423, in _connect
    conn.connect(context=context)
  File "/usr/lib/python2.7/site-packages/mitogen/parent.py", line 1705, in connect
    raise self.exception
AssertionError
An exception occurred during task execution. To see the full traceback, use -vvv. The error was:     raise self.exception
fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}

However using the mitogen-dmw version from the zip file https://github.com/dw/mitogen/archive/dmw.zip and pointing to it in ansible.cfg seems to work fine, fyi.


Create readme.md

Looks good! Would you mind updating the spelling error in github-slack/github-salck.zip ?


ComboBox - MaxDropDownHeight limited to 15 items

Describe the bug
The ComboBox's MaxDropDownHeight is limited to 15 items.
If you generate the ComboBoxItems by template and ViewModel it has 13 items.
If you set the ComboBoxItems directly by ComboBoxItem tags in the .xaml, the dropdown is 14 items long.
By setting the MaxDropDownHeight for i.e. to 10000 to use all the available space on the screen and allow less scrolling for the user,
both creations of ComboBoxItems let the dropdown grow to only 15 items.
If you take the style of the ComboBox from the generic.xaml and change the MaxDropDownHeight (default 504), add it to the app.xaml, it makes no difference.
Please also see this old report:
https://github.com/microsoft/microsoft-ui-xaml/issues/3877 (Question: Can UWP ComboBox max item display limit be overridden?)
My post on the MSDN Q&A:
https://learn.microsoft.com/en-us/answers/questions/1161341/combobox-maxdropdownheight-seems-to-be-limited-to?orderBy=Helpful
Documentation:
https://github.com/MicrosoftDocs/winrt-api/blob/docs//windows.ui.xaml.controls/combobox_maxdropdownheight.md
Steps to reproduce the bug

Create the ComboBox.
Add the ComboBoxItems directly in the .xaml file, at least 16 items.
Set the MaxDropDownHeight to 10000.

You can also test it by generating the ComboBoxItems by binding but it has the same behaviour as described above.
Expected behavior
The MaxDropDownHeight shouldn't be limited, it should be possible to use all the available space on the screen for the dropdown to allow faster access for the user and less scrolling.
I think it was always the normal behaviour to use all the available space.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.2.2: 1.2.221209.1
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Solution here:
https://learn.microsoft.com/en-us/answers/questions/1161341/combobox-maxdropdownheight-seems-to-be-limited-to?orderBy=Helpful


FrontEnd Form Validation

Thanks for your work, I've been looking for a way to have one source of truth for both frontend and backend validation from Prisma and this looks very promising!
Would it be possible to have a "frontend mode" where all the validation rules are put into one file / one file per Model,  to be used for form validation? 👍

Hey @MentalGear, thanks for the feedback.
So a single file with all schemas included. Okay, I'll work on it now!
On a side note though, I hope that you use the predefined issue template next time.
Should be released today hopefully :)

Thanks for the super quick response time, Omar!
A single file would be great, or maybe the option for a file per Database Table/Model.

For example: Posts Table would become Posts.schema.ts, User Table -> Users.schema.ts.

Really excited by this, since having a "single source of truth" for both backend and frontend form validation has been a full-stack ambition of mine for a long time, and now with Prisma and your awesome community generator this seems to be almost too good to be true.

Regarding the use of the generated schema from Prisma as a frontend form validator, do you see any issues or limitations?

PS: I'd normally stick to the issue template, but since this was more of a feature request than an issue report, I took the liberty of adapting.
PPS: Feel free to add a tipping jar! :)

@MentalGear I think your file per model option is the best one here. If you have run this generator locally, you must have noticed that there is a folder called objects. It contains all schema objects used in model schemas. These objects currently are in separate files. A lot of them are shared among the models. So, while trying to get them all inside a single file, it would cause an issue of order; meaning that some schemas have to come before others, and sometimes it get's long to assure this in case of bigger prisma schemas.
So, I was thinking of keeping the objects directory as it is, but apply your idea on the model schemas.
The directories should look like this after it's done:
-> generated
   -> objects
   -> models
       -> User.schema.ts
       -> Post.schema.ts
   -> index.ts

index.ts will re-export everything inside the models, which will make it easier to import them later. Unless you have something else in mind, please let me know.

Regarding the use of the generated schema from Prisma as a frontend form validator, do you see any issues or limitations?

I honestly don't know of any limitations this could have. It should work fine.

PS: I'd normally stick to the issue template, but since this was more of a feature request than an issue report, I took the liberty of adapting.

No problem at all.

PPS: Feel free to add a tipping jar! :)

Not sure how to do that, do you happen to know a service like that?

Sorry for the delayed reply @omar-dulaimi.
I had some thinking to do regarding how my vision of a unified data model usable on both client and server could be archived. I came to the conclusion that probably the inverse of Prisma's generator function would be required.
E.g.: Given a single source of truth file (that contains model structure, datatype, and validation rules), a Prisma File as well as a validation file (not sure yet for which validation lib) will be generated automatically.
I'm sorry to have invoked you, since this is not something your library is meant to do.
However, you have already done a lot of work on Prisma as well as the various validation lib generators.
Maybe you would be interested to work together on such a single source of truth model?
To put it into more concrete terms, I would imagine a model syntax either with:

Decorators for validations (like validator-class)

export class User {
  @required
  name: string;

  @IsInt()
  @isPositive()
  age: number;

  @IsEmail()
  email: string;
}

js and chaining ( yup like )

let User = object({
  name: string().required(),
  age: number().positive().integer(),
  email: string().email(),
});

or JSON (ajv like)

{
  "name":{
    "type":"string"
  },
  "age":{
    "type":"integer",
    "rules":{
      "positive":true
    }
  },
  "email":{
    "type":"string",
    "rules":{
      "email":true
    }
  }
}

Personally, I would tend towards the js chaining syntax (yup), as it feels the most readable.
Maybe it would also be possible to just write an (extended) yup file, and have the Prisma file generated from it.
Thinking about it, most of the attributes should be able to get inferred into Prisma attributes, like all the primitives of course, but also .oneOf = ENUM, @decorators like @default() = .default(), even linking to another model = .ref('$x').
However @decorators like id, unique, etc would have to be otherwise filled, maybe with custom functions if yup allows for it in their format.
Please let me know your thoughts !

Not sure how to do that, do you happen to know a service like that?
Ex: https://www.buymeacoffee.com

I'm sorry to have invoked you, since this is not something your library is meant to do.

No problem at all, I like to hear other people's thoughts. This helps in building better software, that people would use.

I came to the conclusion that probably the inverse of Prisma's generator function would be required.
E.g.: Given a single source of truth file (that contains model structure, datatype, and validation rules), a Prisma File as well as a validation file (not sure yet for which validation lib) will be generated automatically.

So basically you want to have a single file in which you define all your models using either Yup, Classes or JSON schema.
The problem with this approach is that it will go out of sync with Prisma and the databases Prisma supports very quickly and very repetitively. Since the tools you mentioned can not represent a Prisma schema 100% with all of it's attributes and special usages specific to each database type. You won't be able to represent native database types(as they are a lot and databse-specific), and they're important in order to build a performant database, that does not rely on default data types.
We have the Prisma schema, it's an up to date single source of truth. The only thing it misses according to your requirements is the validations.
So, I was thinking of instead specifiying the valdiation rules inside the schema itself, like this:
model User {
  id      Int      @id @default(autoincrement())
/// @MinLength(10)
/// @MaxLength(50)
  name    String?  @db.VarChar(255)
/// @Email()
  email   String   @unique @db.VarChar(255)
}

This way the Prisma generator(whatever it was) can use such meta data in all schemas it generates. So, you get the same behavior in all of your logic; not just one schema you manually define.
Building and maintaining a new source of truth that also generates a Prisma schema, is a big project. In case you haven't heard of it before, there's a project that got popular recently, it's called KeystoneJS. They have their own source of truth, from which they build your Prisma schema and also your dashboard. Check it out, it's really cool.
Also, I have created my Buy Me a Coffee account. Seems promising. I'll add it to my projects' READMEs.
Thank you for your thoughts, and for the website recommendation.

I like to hear other people's thoughts. This helps in building better software, that people would use.

Great attitude! Much in line with my own.
Thanks for the hint on KeystoneJS, which seems to be a good solution if you want to run your own server (I try to stay serverless), and only need backend validation within the same file. However, it doesn't satisfy my expectation of having 1 file for db, front and backend validation.

So, I was thinking of instead specifiying the valdiation rules inside the schema itself, like this:

Integrating validation rules into a Prisma schema using compiler (generator) hints with the /// notion seems the better idea, however I think parsing might get difficult, there's no type safety and no syntax highlighting.
At the moment, I'm thinking about writing my own structure from which Prisma and validation schemes can be generated. It's a bigger project, but I hope not too big. Prisma has 4 main components in their schema (name, type, operator, attributes), which should stay constant.
Thank you for keeping this issue active and your interest in general, and feel free to go ahead with the "one file" output if you like, but personally I won't need it.
If you like, I can let you know once I have something presentable for my approach - would be interested in your thoughts and maybe we can even work together on it if you like it.

Integrating validation rules into a Prisma schema using compiler (generator) hints with the /// notion seems the better idea, however I think parsing might get difficult, there's no type safety and no syntax highlighting.

Yes, it's just been requested as a feature on the Yup generator repo, so I'm going to give it a go there soon. I will learn more info about the process, since I haven't done this before in any of my generators.

At the moment, I'm thinking about writing my own structure from which Prisma and validation schemes can be generated. It's a bigger project, but I hope not too big. Prisma has 4 main components in their schema (name, type, operator, attributes), which should stay constant.

Actually it's going to be too big, because you're in a way building a new schema syntax. Prisma currently supports a lot of different database types, and each have their own special attributes and mappings. Not to mention the need for a reliable way to model relationships in your syntax (Yup or Joi), on which side, what fields, self relations, etc.

Thank you for keeping this issue active and your interest in general, and feel free to go ahead with the "one file" output if you like, but personally I won't need it.

I'm implementing something similar in order to shorten imports paths and number, so all schema imports will be done with a single line. Hopefully this change will be applied to all generators.

If you like, I can let you know once I have something presentable for my approach - would be interested in your thoughts and maybe we can even work together on it if you like it.

Yes, please do. I'm interested to see where this goes.

Yes, it's just been requested as a feature on the Yup generator repo, so I'm going to give it a go there soon. I will learn more info about the process, since I haven't done this before in any of my generators.

👍

Actually it's going to be too big, because you're in a way building a new schema syntax. Prisma currently supports a lot of different database types, and each have their own special attributes and mappings. Not to mention the need for a reliable way to model relationships in your syntax (Yup or Joi), on which side, what fields, self relations, etc.

Well, I was thinking about using prisma format for the validation, and only transpile my own custom "super-structure" to the prisma format.

Thank you for keeping this issue active and your interest in general, and feel free to go ahead with the "one file" output if you like, but personally I won't need it.

Yes, please do. I'm interested to see where this goes.

I have now a typescript/js object super-structure that is transformed into prisma schema and a validation schema. It has type checking and autocomplete, however, I'm not very happy with the readability.
 const models: modelsSchema = {
    User: {
        config: {
            idComposite: ['id', 'email'],
        },
        fields: {
            id: {
                type: Type.Int,
                isId: true,
                default: 'autoincrement()',
            },
            username: {
                aliasInDB: 'userName',

                type: Type.String,
                typeInDB: 'varchar(255)',
                list: true,
                typeIsList: false,

                default: 'Jimmy',
                isId: true,

                nullable: false,
                unique: true,

                validation: string().required().min(3).max(255),

            },

            followers: {
                relToModel: 'User',
                relToField: 'count',
                relOwnFieldName: 'followersID',
                relName: 'followers',
            },

            lastUpdated: {
                type: Type.DateTimeAuto,
                isId: true,
                nullable: false,
                unique: false,
                default: 'now()',
            },
        },
    },
}

Prisma's format is just shorter and more compact. Maybe I go with a class decorator syntax, or the /// validation hints are the nicer way to go after all. Have you tried implementing these yet?

Integrating validation rules into a Prisma schema using compiler (generator) hints with the /// notion seems the better idea, however I think parsing might get difficult, there's no type safety and no syntax highlighting.

@MentalGear I have been busy lately, I'm trying to get back on track with open source.
I don't like that structure to be honest. Stuff like string().required().min(3).max(255) won't work unless it's stringified. And if they are stringified, they become like 'now()', varchar(255) and 'autoincrement()'; which are not type-safe and could cause a lot of errors. You also lose auto-completion, which is something critical for developer experience.

Prisma's format is just shorter and more compact

Indeed.

Maybe I go with a class decorator syntax, or the /// validation hints are the nicer way to go after all. Have you tried integrating these yet?

Not yet honestly. I'll try to dedicate some time for that enhancement in the future.

Prisma is looking for comment on their validation implementation. I'm sure you have some thoughts!
https://github.com/prisma/prisma/issues/3528#issuecomment-1233557205

Prisma is looking for comment on their validation implementation. I'm sure you have some thoughts!
https://github.com/prisma/prisma/issues/3528#issuecomment-1233557205

Thank you for bringing it to my attention.


Add Cargo.lock

As explained in the cargo FAQ, a project should contain a Cargo.lock file to provide deterministic builds.
But I saw that you explicitly excluded this file in your gitignore. When you have a solid reason for this, you may close this pr.
https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control

I had issues with the Cargo.lock file when cross-compiling for windows. We can add it though, maybe the issues no longer persist


Paths containing whitespaces are only partially supported

As the applications asks me to select a path to use as a temporary and export directory, I created "DockerConverter test" as a folder. After pulling the image, the application showed me an error popup, but still displays content of the image + everything else. This is annoying as I don't know if something's wrong or not and whether I received all information that I would have received without the error popup. After adding an underscore to the path, it worked as expected.
Command line logs printed:
docker save -o /home/<USER>/Downloads/DockerConverter test/wonderfall-nextcloud-12.0.tar wonderfall/nextcloud:12.0
Error response from daemon: No such image: test/wonderfall-nextcloud-12.0.tar

Image extraction process got updated, whitespaces are now supported.


GetDownstreamEdges is not cycle safe, causing a recursion/stack overflow

Issue raised from open source community by @inishchith :
Hi team,
Hope you all are doing well. I think have identified a case of recursion of pipelines with cycles. Wanted to validate it here.
details
One of the pipelines I was trying to work through would lead to a stack overflow (logs attached)
What I think could be happening (from the surface)
For vertex scaling, there's a check for backPressure - which works with downstreamEdges info.
The problem with GetDownstreamEdges is that it's not cycle safe and could cause a recursion. I modified a mock a test case (example) to create a cycle and it checks-off.
Please correct me in case anything. Thanks!
{"level":"info","ts":"2024-01-10T16:42:20.819742396Z","logger":"numaflow.controller-manager","caller":"cmd/start.go:202","msg":"Starting controller manager","version":"Version: v1.1.2, BuildDate: 2024-01-02T06:47:33Z, GitCommit: ac716ec4ab4b49f4f013f067c33d1d89936e132a, GitTag: v1.1.2, GitTreeState: clean, GoVersion: go1.20.12, Compiler: gc, Platform: linux/amd64"}
I0110 16:42:20.820298       1 leaderelection.go:248] attempting to acquire leader lease numaflow/numaflow-controller-lock...
 Give it a 👍. We often sort issues this way to know what to prioritize.

@inishchith volunteered to work on a fix. Thank you Nishchith!


Getting started : explicit project creation isn't needed

The step related to project creation:
oc new-project enmasse
seems to be useless if the line related to run the deployment script has -p "enmasse".
Of course the script works but provides this line :
Using project "enmasse".
Error from server: project "enmasse" already exists
What do you think to remove the extra step of explicit creation of the "enmasse" project with new-project command outside of the script ?
Even because the script creates a project in any case with DEFAULT_OPENSHIFT_PROJECT name if -p option isn't used.

Forgot to close this. This should be fixed a while ago.


[Task]: Remove oldest grays in the design system

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
Remove the following css variables from the design system:
old-gray-10
old-blue-gray
old-outer-space
old-dove-gray
old-mid-gray
old-alto
old-mercury
old-dove-gray-2
old-silver
old-dove-gray-3
old-black-pearl
old-alto-opacity-50
old-white-opacity-50

hey can you assign this to me

Hey @abhijain2003, this is an issue for something I'm working on right now. If you'd like to work on some issues for Hacktoberfest, please look at the issues we've marked as good first issues to start with. Have a good day!


Report issue feature do not include extension information

Issue Type: Bug
Issue https://github.com/microsoft/vscode/issues/83074 was automatically created by the "Report issue" feature of visual studio code.
In the "File on" field I've selected "An extension" and in the "Extension" field which appears I've selected "Prettify JSON", it was the first time I used this "report" feature and I was puzzled by the fact that the extension I've selected was nowhere to be seen in the issue being created.
Issue #83074 was closed because not relevant to vscode (since it is caused by an extension) but probably the "Report issue" feature should have prevented me from creating that issue or should have warned me that the issue must be created elsewhere.
Probably the best would be to open the extension github issues (since you should already have the extension github link).


Improve readability as module file.

I added some numpy style docstrings to functions in order to make it easier to understand the structure and usage of functions in modules.
like this
def build_vocab(sentences: list) -> list:
    """
    Builds a vocabulary mapping from word to index based on the sentences.
    Returns vocabulary mapping and inverse vocabulary mapping.

    Parameters
    ----------
    sentences : list of list
        [[sentence1], [sentence2], ..., [sentenceN]]
        Each sentence is list of words.

    Returns
    -------
    vocabulary : dict
        mapping from word to index (order of appearance in sentences).
        ex. {'<PAD/>': 0, 'Hello': 1, 'World': 2}

    vocabulary_inv : list
        list of words, sorted by word frequency in sentences.
    """

I tested training 3 models (rand, static, non-static) on both dataset (keras, local) tensorflow backend, there was no problem. Please review some changes.

Thank you so mush for your reaction.
I will try working on forked repo to deepen understanding of algorithms.


Motion layer

Code with dynamic reconfiguration changes, pid algorithm changes, camera node changes etc.

Remove commented lines of code if not required. Comments at the right places instead.
Resolve conflict in README.md

The commented lines for most nodes are an auxiliary code just required during our testing phase of PIDs and motion .... they will be removed prior to the competition but till then they are quite necessary to avoid wastage of time

@Suryansh470 , the codes can be made a lot better and cleaner if you begin to use OOP concepts (like classes) to write the various nodes. A particular emphasis on the arduino node in which we can simplify it by creating a class named thruster which has the appropriate data and methods in it.
Why is the launch file here is in the hardware_arduino package while it is calling a node from the hardware_camera package?
What exactly is the purpose of the vid_pub node? You can also look into the usb_cam and uvc_camera packages. They use nodelets which makes it faster to send images across nodes.
A few extra coments on what exactly the classes in here and node this do would help a lot to understand the code.
Use structures instead of the following:
p_param=config.p;
i_param=config.i;
d_param=config.d;
band_param=config.band;

Also fix the issue with README.md. There is a merge conflict occuring.
Let me know when you have some results of the tuning of the thrusters.

@Suryansh470 In case there are scripts which are only required during test time, make test packages accordingly which we can use, instead of having to delete the lines.

Closing this pull request since it has become too old, and there are merge conflicts which need to be resolved. Please send in a new one once it's completed and is working.


all: cyclic imports bloat go.sum

What version of protobuf and what language are you using?
github.com/golang/protobuf/protoc-gen-go: v1.4.2
github.com/golang/protobuf: v1.4.2
google.golang.org/protobuf: v1.25.0
go: go version go1.15.1 windows/amd64
What did you do?
Generated a simple message using go:generate protoc --go_opt=paths=source_relative --go_out=. example.proto
example.proto:
syntax = "proto3";

option go_package = "github.com/2767mr/prototest";

message Empty {

}

Then I run go mod tidy
What did you expect to see?
A simple go.sum without duplicated entries for github.com/golang/protobuf or google.golang.org/protobuf
What did you see instead?
A lot of duplicated entries referencing old version.
An example repo can be found at https://github.com/2767mr/prototest.
This issue does not seem to affect actual downloads. go mod download seems to only download the newest version.
A visualisation of the mod graph can be found at https://github.com/2767mr/prototest/blob/master/graph.png. There one can easily see that github.com/golang/protobuf imports an old version of google.golang.org/protobuf which imports an even older version of github.com/golang/protobuf.

This is a known issue. It's unfortunate, but relatively harmless. The cyclic dependency is necessary:

github.com/golang/protobuf depends on google.golang.org/protobuf because v1.4+ is implemented in terms of the newer module.
google.golang.org/protobuf "depends" on github.com/golang/protobuf only to enforce that v1.4+ be used. Aside from that constraint, it requires nothing from the older module. This is necessary to avoid problems with disjoint sets of type registries.

The cyclic relationship can't be broken.
If there's anything to be done, it probably be with the Go toolchain to prune useless go.sum entries for cyclic dependencies. If so, there's not much this project can do about this issue.

I did some experiments and I think I came up with a workaround:
It is possible to reference future releases inside a go.mod. This means that if both modules reference a future version and then both publish that version it will resolve. I made an example at https://github.com/2767mr/prototest2 v0.0.4 which refences https://github.com/2767mr/prototest3 v0.0.2 and the other way around.
Since google.golang.org/protobuf only "depends" on github.com/golang/protobuf as a constraint (that is also locked behind a build flag) I recommend never updating that reference in the future. That way a maximum of 2 separate entries in the go.sum can be achieved.

It is possible to reference future releases inside a go.mod.

Yes, for the go.mod file, but not for the go.sum file. The go.sum file contains a hash of the dependencies, but there's a problem. The hash of the dependencies covers the forward version reference to some unreleased module for which we do not know (or rather cannot compute) the hash for.

The go.sum of the imported package doesn't seem to matter. Even though the go.sum of  https://github.com/2767mr/prototest2 and https://github.com/2767mr/prototest3 contain references to v0.0.3, v0.0.2 and v0.0.1 but when importing<EMAIL_ADDRESS>it results in this go.sum:
github.com/2767mr/prototest2 v0.1.0 h1:VPBoYfI30vH+NyVowwfApjdhJs3RWZSksFJ15cmsUkA=
github.com/2767mr/prototest2 v0.1.0/go.mod h1:bgQNNDqWYqKPhU7fSfR+O40OHJBYAHv8ICPzpXGVJj4=
github.com/2767mr/prototest3 v0.1.0 h1:BHRrPhhBo4fwqPw7OVl+8KEo6QCNr88dAvIQqmSSI+g=
github.com/2767mr/prototest3 v0.1.0/go.mod h1:5IVjxmYTIaB2hQkZG1fsTJ40IJTauWED2kdJk0v99+g=

I'm not sure how your test repos address the root issue. Both https://github.com/2767mr/prototest2/blob/master/go.sum and https://github.com/2767mr/prototest3/blob/master/go.sum and contain cyclic references to the past history of the other's module.
Stepping back a bit, can you explain why this is an issue that needs resolving? Is this purely a bloat issue or is there a technical issue involved?

It is true that both test repos contain old versions in their go.sum. However, if you import one of these test repos from another module only the newest versions are written to the go.sum instead of all the current ones (see my previous comment)
The issue here is indeed simply a bloat issue, no technical issue involved. I found this while looking for potentially bad/unsafe/unused/outdated modules that were used by my project. At first I was quite shocked when I looked into my go.sum and found that more than half of my imports were either outdated, dev versions or completely unused. As a user I want to know what I am importing and if I see dev versions in there I have to assume it's not safe to use. I'd also appreciate if third party dependencies would be avoided but it's acceptable as is.

Given that this isn't a pressing issue, we're not going to do anything about this at the moment. It's a significant amount of release tooling work with little gain. Furthermore, it's really something the Go toolchain should do a better job at pruning useless go.sum entries.

I ran into this issue from a situation that happens in prometheus client as well, where this cyclic dependency causes a deep walk down a dependency spiral. It’s not really an easy thing to really fix for reasons laid out already. In their case, they’re only depending on the other module in order for their own internal stuff, which ends up getting pulled into every repo that depends on it.
It’s fine almost all the time, the walk is only made the first time to setup the go.sum, and check availability, and go.mod files from the dependencies. Then the solver decides on the newest versions and done, the older versions only ever get their go.mod downloaded, and they’re now in the module cache, with no need to download them again.
Really, the only negative is that it creates an unexpected scenario, where after cleaning out your dependencies and your go.sum, you find that there’s a whole lot more there than you expect. (And sometimes, in CI, you’ll get a fully clean build with no caching, and see the dependency walk again regularly.) But they’ve decided not to address the issue either, because it’s not really that big of an issue in the larger priorities of projects.

<EMAIL_ADDRESS>and<EMAIL_ADDRESS>did a little dance to clear out the go.sum bloat.
For those interested:

drop the dependency on github.com/golang/protobuf from google.golang.org/protobuf
release<EMAIL_ADDRESS>add a dependency on<EMAIL_ADDRESS>from github.com/golang/protobuf.
release<EMAIL_ADDRESS>add a dependency on<EMAIL_ADDRESS>from google.golang.org/protobuf
release<EMAIL_ADDRESS>upgrade the dependency to<EMAIL_ADDRESS>from github.com/golang/protobuf
release<EMAIL_ADDRESS>


drivers: ieee802154: improved driver support for enhanced ACK IE offloading

Problem Description
As has been pointed out in #61227, configuring IE offloading for enhanced ACK IEs could be improved to make it easier for drivers that do not want to implement their own IE parser/writer internally by introducing improved types and appropriate helpers to be re-used across all drivers (optionally including nRF5).
In #61227 this was referred to as "moving soft MAC parts out of proprietary drivers into cross-vendor L2 callbacks".
Proposed Solution
In the context of #50336 (TSCH roadmap) many types and IE parser/writer helpers need to be introduced into L2 (soft MAC). Some of these are immediately relevant to #61227 and make it easier for other drivers to support CSL IE offloading. More specifically the existing implementation could be moved forward immediately by providing more structured IE types that help driver maintainers to construct CSL IEs with little effort. Later on in the TSCH roadmap, additional writers and parsers will be introduced that will make it even easier to support IE offloading in any driver.
A PR with the proposed immediate changes will follow.
Possible Alternatives
nRF5's IE parser/writer could be ported out of the driver internals and placed into a cross-vendor layer shared by OT and native L2. The nRF5 IE parser/write is however less generic and complete than the one required for TSCH so it probably makes more sense to either keep it in parallel or successively replace it as additional re-usable helpers are introduced into Zephyr. These helpers already exist in the TSCH development branch and can be previewed there, see ieee802154_frame_ie.* there.
Additional Context
The changes proposed in this enhancement are a precondition to support hardware offloading for ACK IE injection in TSCH. Additionally, the TSCH roadmap not only introduces IEs specific to TSCH but will immediately provide types also that help to offload other IEEE 802.15.4 timing sensitive protocols that involve IE signaling in enhanced ACKs (one of which is CSL).

@edmont @jciupis @rlubos Another enhancement proposal, this time for improved (more flexible) enhanced ACK IE offloading. This is a precondition for TSCH support, too, but is more generally useful than that. PR follows as soon as the two blocking PRs #62413 and #62503. You can preview the proposed change here: https://github.com/fgrandel/zephyr/commit/e70933b9914687a437dcf90f88b90f885cb6f5c7

Hello sir,
From my understanding, the problem is about the CONFIG_GPIO_SCH311X configuration not being enabled for the nrf_sch311x board. To resolve this issue, the GPIO driver for the SCH311X chip needs to be enabled for the nRF Connect SCH311x board.
To fix this issue, we need to enable the CONFIG_GPIO_SCH311X configuration option for the nrf_sch311x board. This can be done by editing the board's Kconfig. board file. I guess this code snippet which help you enable it.
 config BOARD_NRF_SCH311X
 bool "nRF Connect SCH311x"
 source "drivers/gpio/Kconfig.gpio"
 config GPIO_SCH311X
 bool "GPIO Driver for SCH311X"
 select GPIO
 help
 Enable the GPIO driver for SCH311X

If I'm correct I can make a PR regarding this after some testing is done Locally. If I misunderstood the problem, You can let me know, I try my best to work on it.
Thank You
Regards
Prasanna


Support files upload for vulnerabilities on the frontend

We urgently need support for three buttons to facilitate the bulk upload of data through three entry points. This functionality should be implemented as a common VFC/FC, which will be utilized in three distinct locations:

[x] Above the 'Propose Vulnerability' view.

[x] At the organization level: on the page where vulnerability submissions are made.

[x] Near to the 'Propose Vulnerability' PLUS icon in the Organization Collection list view.

[ ] The 'Upload' button should only be accessible to users belonging to organizations that have been granted the 'can do bulk upload of vulnerabilities' privilege set by the SuperUser in the settings. To verify this permission, we require each user to be checked with a 'permissionControllerEvaluator' on the backend that will provide all the information. This evaluator will return a data class containing a field named 'isPermittedToBulkUpload'."

[ ] Temporary storage

[ ] Added endpoint for deleting file

[ ] endpoints should return a FileDtoResponse

Of course all permissions should also be checked on the backend as well.

@Cheshiriks please take a look at simpeFileUploader, it might help

@Cheshiriks @nulls if we cannot read file (there is a mistake in any file) - you need to propagate it to the FE

@nulls also check this one


Fix typos

grammerz
enforce semicolon-free style
fix .more class selector
use proper CommonJS casing

thanks! unfortunately i saw this a little after i already made some edits offline, but I've incorporated your changes.


branch2.0 fix doris jdbc catalog test case

Proposed changes

Fix doris_jdbc_catalog test case out file
Add log to debug 2 unstable test cases: pg_jdbc_catalog and oracle_jdbc_catalog

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

run buildall


[RFC] [Toolbar] Externalize getStyle() functions

@oliviertassinari @alitaheri @mbrookes
This isn't done, as I'm migrating the code, I wanted to get your feedback on this pattern of moving getStyles() outside of the class declaration (and changing the method signature to getStyles(props, state).
I think this approach has the following benefits:

Reduces component surface API (and imperative methods) which is safer and allows us to move more towards functional components
Prevents leaky abstractions and prevents developers from implementing custom styling and behavior from undocumented methods (Disclosure: I am not trying to say anything bad about this developer :grin:. I perfectly understand what and why he was doing what he was doing, but I still think we should find a better way for material-ui to handle his use case and prevent developers from falling into the trap of using internal API)
Discourages the use of other instance methods to calculate style such this.getTheme() and this.getSpacing()
Forces us (and other contributors) to think of style as a function of props and state (and ideally in the future just a function of props)
It's more functional, predictable, and reusable (could open up interesting opportunities in the future like composition and more)

Final note: This PR was originally the start of migrating the toolbar components off of style-propable. After we decide, I'll rename the PR and finish that work.
Signed-off-by: Neil Gabbadon<EMAIL_ADDRESS>

@newoga I think that it's an excellent idea!

@newoga I think that it's an excellent idea!

I'm glad, I think this change would make me very happy. :laughing:

Pure awesomeness and conciseness :+1: :+1: This will bring us very close to memoization :heart_eyes:

Pure awesomeness and conciseness :+1: :+1: This will bring us very close to memoization :heart_eyes:

Let's do it! :smile: :tada:
I applied that pattern to the rest of the components under ./toolbar. Take a look please :grin:

Done, change setState to nextContext.muiTheme || this.state.muiTheme

I'm all good. feel free to merge :+1:


feat(coapcore): Refactor authentication sources, add ACE-OSCORE profile

This contains changes to coapcore that enable running in an ACE context, eg. using the ACE OSCORE profile.
This started small (eg.generalizing crypto factory from fn() to F where F: Fn(): This is not needed in Ariel's concrete use case, but helpful in applications with less global state), but eventually now contains a large refactoring, which was due anyway to get rid of key material that was originally either hard-coded, or passed in without regard for future flexibility (like, starting a CoAP server does not always entail having a single EDHOC identity, could be 0 or 2).
General status
This has most of its migrations done, but is missing a few reapings of the changed responsibilities' benefits yet, and also examples.
Change checklist

[ ] I have cleaned up my commit history and squashed fixup commits.
[ ] I have followed the Coding Conventions.
[ ] I have performed a self-review of my own code.
[ ] I have made corresponding changes to the documentation.

This is now in a state that I'd call feature-complete for this PR -- it moves all parts that are supposed to be configured out of the coapcore crate (to ariel-os-coap, where now it is waiting for a follow-up around provisioning).
I'm starting a self-review run -- things I expect to change at this stage are documentation enhancements, maybe moving around or renaming types/traits, altering what is sealed, adding some testing code.
It is rebased onto main to resolve conflicts from recently addressed lints.


PtpClient in Windows Time

Hi,
I'm currently setting up Windows10 Enterprise 1809 LTSC to be synced by PTP. Apart from https://techcommunity.microsoft.com/t5/Networking-Blog/Windows-Subsystem-for-Linux-for-testing-Windows-10-PTP-Client/ba-p/389181 there is no documentation at all, that I can find. This blog-post is the only reason I've been able to get things up and running in the first place. Are there any other relevant registry-settings that can be of use? Any further configuration? Any way I can get the time-difference and offset like in "w32tm /stripchart"? And when will Microsoft make some proper Documentation about this feature?
Best regards

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

ID: 76f0d079-9e97-6b4f-a52d-913713755457
Version Independent ID: 5eaf5249-b527-28d3-2921-62e390e1eb46
Content: Windows Time Service
Content Source: WindowsServerDocs/networking/windows-time-service/windows-time-service-top.md
Product: windows-server
Technology: networking
GitHub Login: @shortpatti
Microsoft Alias: pashort

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Improve GitHub Actions for pull requests

See https://github.com/Senzing/community-roadmap/issues/71

Pull requests:

https://github.com/Senzing/docker-ibm-db2/pull/25


Update auger to a modern kubernetes and etcd version

This pull request updates auger to use a much more modern version of k8s and etcd dependencies.
This gets us roughly up to date with k8s 1.26 so we still have more work to do but it's a good increment of progress.
Noting that the scheme.go changes will eventually be superceded by autogen introduced in https://github.com/etcd-io/auger/pull/2. I've done some minimal updates so things work until that merged.

Converting to draft - need to figure out the test failure after bbolt dependency was bumped.  We might need to generate new cmd/testdata/boltdb/ content :/


[BUG]

What is the bug?
I am sending requests to opensearch engine like:
curl -X GET 'https://mercury.seargin.com:3005/test_cv/_search' -u 'joedoe:qwerty' --insecure

which correctly returns an answer.  I can also use correctly the following python code to send requests and receive answers:
import requests

#####################################
username = "joedoe"
password = "qwerty"
url = 'https://mercury.seargin.com:3005/test_cv/_search'
auth = (username, password)
response = requests.get(url, auth=auth, verify=False)

if response.status_code == 200:
    print("Request successful!")
    data = response.json()
    print(data)
else:
    print(f"Request failed with status code: {response.status_code}")
#######################################

But when I use opensearch python client:
#####################################
host = 'https://mercury.seargin.com'
port = 3005
auth = ('joedoe', 'qwerty')

client = OpenSearch(
    hosts = [{'host': host, 'port': port}],
    http_auth = auth,
    use_ssl = False,
    verify_certs = False,
    ssl_assert_hostname = False,
    ssl_show_warn = False,
)

query = {
  'size': 5,
  'query': {
    'match': {
    }
  }
}

response = client.search(
    body = query,
    index = 'test_cv'
)
##############################################

I get the following error:
Traceback (most recent call last):
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/socket.py", line 955, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/connection/http_urllib3.py", line 280, in perform_request
    response = self.pool.urlopen(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
    retries = retries.increment(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/util/retry.py", line 445, in increment
    raise reraise(type(error), error, _stacktrace)
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/util/util.py", line 39, in reraise
    raise value
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
    response = self._make_request(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 496, in _make_request
    conn.request(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connection.py", line 400, in request
    self.endheaders()
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 1278, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 1038, in _send_output
    self.send(msg)
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 976, in send
    self.connect()
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connection.py", line 238, in connect
    self.sock = self._new_conn()
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connection.py", line 205, in _new_conn
    raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x7583932fbb50>: Failed to resolve 'https://mercury.seargin.com' ([Errno -2] Name or service not known)

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/media/zbislaw/dane/Projekty/Seargin_NLP/opensearch_merkury/opensearch.py", line 28, in <module>
    response = client.search(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/client/utils.py", line 180, in _wrapped
    return func(*args, params=params, headers=headers, **kwargs)
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/client/__init__.py", line 2359, in search
    return self.transport.perform_request(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/transport.py", line 453, in perform_request
    raise e
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/transport.py", line 416, in perform_request
    status, headers_response, data = connection.perform_request(
  File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/connection/http_urllib3.py", line 295, in perform_request
    raise ConnectionError("N/A", str(e), e)
opensearchpy.exceptions.ConnectionError: ConnectionError(<urllib3.connection.HTTPConnection object at 0x7583932fbb50>: Failed to resolve 'https://mercury.seargin.com' ([Errno -2] Name or service not known)) caused by: NameResolutionError(<urllib3.connection.HTTPConnection object at 0x7583932fbb50>: Failed to resolve 'https://mercury.seargin.com' ([Errno -2] Name or service not known))

Any help is appreciated

I believe the host needs to be just the host, without the https part, host = 'mercury.seargin.com'. Closing this since I'm pretty sure this is the issue. Feel free to comment/reopen if it's not.
A good place to ask questions may be the #clients channel on the public slack. There are many working samples in https://github.com/opensearch-project/opensearch-py/tree/main/samples to try out first, too.

Hi. Thank you for your prompt answer. I have removed "https://" from host name (thank you for link to github samples, I should have had a look at this page earlier). The corrected code is however not working. Below is the log. On the client side I am using the latest version of Linux Mint (22 Wilma) - maybe it is the problem? The installation instructions at https://opensearch.org/docs/latest/getting-started/quickstart/ do not work for this linux release too (docker-compose exits with errors at 'sudo docker-compose up -d' command with opensearch example yaml file). And here is the error log for the corrected python source:
Traceback (most recent call last):
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
response = self._make_request(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 537, in _make_request
response = conn.getresponse()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connection.py", line 466, in getresponse
httplib_response = super().getresponse()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 1375, in getresponse
response.begin()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 318, in begin
version, status, reason = self._read_status()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 287, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/connection/http_urllib3.py", line 280, in perform_request
response = self.pool.urlopen(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
retries = retries.increment(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/util/retry.py", line 445, in increment
raise reraise(type(error), error, _stacktrace)
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/util/util.py", line 38, in reraise
raise value.with_traceback(tb)
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
response = self._make_request(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connectionpool.py", line 537, in _make_request
response = conn.getresponse()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/urllib3/connection.py", line 466, in getresponse
httplib_response = super().getresponse()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 1375, in getresponse
response.begin()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 318, in begin
version, status, reason = self._read_status()
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/http/client.py", line 287, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/media/zbislaw/dane/Projekty/Seargin_NLP/opensearch_merkury/opensearch.py", line 26, in
response = client.search(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/client/utils.py", line 180, in _wrapped
return func(*args, params=params, headers=headers, **kwargs)
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/client/init.py", line 2359, in search
return self.transport.perform_request(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/transport.py", line 453, in perform_request
raise e
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/transport.py", line 416, in perform_request
status, headers_response, data = connection.perform_request(
File "/home/zbislaw/anaconda3/envs/NLP/lib/python3.10/site-packages/opensearchpy/connection/http_urllib3.py", line 295, in perform_request
raise ConnectionError("N/A", str(e), e)
opensearchpy.exceptions.ConnectionError: ConnectionError(('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))) caused by: ProtocolError(('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')))

The "Remote end closed connection without response" error means the server didn't respond with anything the client expected.
Can you curl -u joedoe:qwerty https://mercury.seargin.com:3005?

Thank you very much, setting use_ssl to True solves the problem.
Best regards


PWN-8109 - Add balance update sockets, refactor Socket manager

Jira Ticket
https://p2pvalidator.atlassian.net/browse/PWN-8109

closed,
will be part of 2.7.0


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_e3efd928-2cd7-4a26-b6cd-08572e45e48b/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_e3efd928-2cd7-4a26-b6cd-08572e45e48b.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-02-14-01-49-38 has been deleted or has been force pushed

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


Never and range operators

Never operator: returns an Observable that never sends any items or notifications to an Observer
Modification of the Range operator to comply with Rx standards (start and count arguments, exceptions management)

Please note this PR is based on https://github.com/ReactiveX/RxGo/pull/101.

Pull Request Test Coverage Report for Build 188

136 of 146 (93.15%)  changed or added relevant lines in 1 file are covered.
16 unchanged lines in 3 files lost coverage.
Overall coverage increased (+5.7%) to 89.663%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

observablecreate.go
136
146
93.15%

Files with Coverage Reduction
New Missed Lines
%

optional/optional.go
3
100.0%

errors/errors.go
6
100.0%

options/options.go
7
100.0%

Totals

Change from base Build 179:
5.7%

Covered Lines:
824

Relevant Lines:
919

💛  - Coveralls


Added docs for AppDelegate.OnCommissioningSessionEstablishmentStarted

Added documentation to address feedback in https://github.com/project-chip/connectedhomeip/pull/28138#pullrequestreview-1541858963

Adding these docs and more in this new PR: #28138


Fix for used disk size not showing up on VMs

Fix a broken require which was throwing an exception when running
SSA on a VM.  This caused no XML to be returned for the disks
section of VmConfig, so the "Used Size" and "Partitions Aligned"
were always empty for a VM.
https://bugzilla.redhat.com/show_bug.cgi?id=1322902

@miq-bot add-label bug, providers/vmware, smart_state

@roliveri can you review?


MDT sensor alarms: If we have an alarm description, use it.

Currently, MDT sensor alarms just show "SensorAlarm " in the notes field on nightscout. This change should use the "alarm_description" field for the note if present (e.g. "High Glucose" or "Cal Reminder").
Not yet ready for merge, needs more testing first (from me, if not from others).

vs

Not seen any problems with this yet, other entries on Nightscout seem to still have the correct text.

LMK when you're ready and I'll merge it.

Probably best to just go for it.