BayesianSignatureOptimizer - missing 1 required positional argument: 'example'

as explained in the title, I'm getting this error from the following code:
TypeError: TemplateV2.__call__() missing 1 required positional argument: 'example'
import dspy
from dspy.teleprompt.teleprompt import Teleprompter
from dspy.signatures import Signature
from dspy.evaluate.evaluate import Evaluate

lm = dspy.OllamaLocal(model="mq8", max_tokens=4000, timeout_s=120, temperature=0.7)
# This sets the language model for DSPy.
dspy.settings.configure(lm=lm)

import csv

# Load the dataset from the file
with open('notes-dataset.csv', 'r') as file:
    reader = csv.DictReader(file)
    data = list(reader)

# Convert each entry into a DSPy example
dataset = []
for item in data:
    example = dspy.Example(
        inputs={'document': item['document']},  # Use 'document' column as input
        outputs={'notes': item['notes']},  # Use 'notes' column as output
    )
    dataset.append(example)

# Choose size of each set
train_size = 0.5
dev_size = 0.3
test_size = 0.2
# Calculate the number of examples for each set
num_examples = len(dataset)
num_train = int(num_examples * train_size)
num_dev = int(num_examples * dev_size)
num_test = num_examples - num_train - num_dev

# Split your dataset into train, dev, and test sets
trainset = dataset[:num_train]
devset = dataset[num_train:num_train + num_dev]
testset = dataset[num_train + num_dev:]

print(f"Trainset size: {len(trainset)}, Devset size: {len(devset)}, Testset size: {len(testset)}")

class Notes(dspy.Signature):
    """Bulleted Markdown Notes, Headings and Terms in Bold"""

    document = dspy.InputField()
    notes = dspy.OutputField()

document = """POLYVAGAL SAFETY Attachment, Communication, Self-Regulation STEPHEN W. PORGES A NORTON PROFESSIONAL BOOK+ Introduction: An Embedded History of a New Science+ When the Polyvagal Theory was initially conceptualized, I did not consider it as an expansive paradigm-shifting model. In developing it, I thought it was consistent with antecedent research and theory. In a way, I thought it was the obvious next step. During the 25 years following the initial presentation of the Polyvagal Theory, through my experiences with the scientific community across many disciplines, I learned that the theory provides the framework for a new brain-body or mind-body science. Moreover, I learned that as health-related disciplines embraced the theory, a new polyvagal-informed strategy could be embedded in mental and physical health treatment models. This strategy would focus on recruiting the nervous system of the client or patient as a collaborator on a shared journey toward wellness. Embracing this strategy would emphasize that the body’s quest for safety is embedded in the actions of the nervous system in promoting health. Thus, safety and threat are not only psychological constructs, but have parallels in the autonomic nervous system. When the autonomic nervous system is in a state of calmness and social accessibility, then treatments for both mental and physical disorders can be efficiently implemented. In contrast, when the autonomic nervous system is in a state of defense and vulnerability, then it is in an antagonistic state that blunts the effectiveness of treatment. Simply stated, the theory uncovered the structures and portals through which our neurobiological quest for safety through connectedness with others may be implemented. When a new theory is presented, its intellectual accessibility is dependent on several complex and often not acknowledged historical features. Most importantly, there is a need to understand (1) antecedent theories, (2) the language used to describe the hypothetical constructs illustrating the functions described in the theory, and (3) questions that the theory proposes to answer. Since evolution is an organizing principle in Polyvagal Theory, in which neuroanatomical structures are proposed to facilitate specific adaptive functions, an understanding of vertebrate evolution and neuroanatomy of the neural regulation of the autonomic nervous system are required for a critical dialogue. In addition, since the theory leads to testable hypotheses based on dynamic adjustments in autonomic function, a sophisticated understanding of the metrics of measurement (e.g., time series analyses) is necessary. Scientists are intellectually focused and affiliated with peer groups defined by a shared commitment to study common problems. They see the world through their research questions, explicit and implicit theories, and methodologies. My scientific origins are rooted in the world of psychophysiology, a science that emerged in the 1960s to study how physiological responses paralleled psychological phenomena such as mental effort, attention, expectancy, stimulus detection, decision making, truthfulness, and preference. At the time I first presented the Polyvagal Theory, arousal theory was prevalent in psychophysiology. Although arousal theory had a long, influential history in science, it had a relatively simplistic underlying model. Basically, arousal theory emphasized that arousal was a linear construct indexing a dimension from low to high levels of activation that could be measured or inferred from observing behavior or physiology. The relationship between arousal and performance was often portrayed as an inverted U-shaped function in which optimal performance occurred within a midlevel range, while poor performance was observed at low and high levels of arousal. This relationship was known as the Yerkes-Dodson law (Yerkes & Dodson, 1908). Metaphorically, arousal represented the energy of the human nervous system. Arousal was easily understood, since when it was reflected behaviorally it could be quantified as greater activity and when reflected autonomically it could be observed as increases in sweating and heart rate. Early psychophysiological research assumed that peripheral autonomic measures provided sensitive indicators of arousal. This view was based on a rudimentary understanding of the autonomic nervous system in which changes in electrodermal activity (e.g., sweating) and heart rate were assumed to be accurate indicators of sympathetic activity. As the activation arousal theory developed, a continuity between peripheral autonomic responses and central mechanisms was assumed (see Darrow et al., 1942), and sympathetic activity was assumed to parallel activation of the brain. According to this assumption, organs influenced by sympathetic efferent fibers, such as the sweat glands, blood vessels, or the heart, were potential indicators of limbic or cortical activity (Duffy, 1957; Lindsley, 1951; Malmo, 1959). Although the specific pathways relating these various levels were never outlined and are still sketchy, electrodermal (e.g., GSR) and heart rate became the primary focus of research during the early history of the Society for Psychophysiological Research. This was due to their presumed sympathetic innervation and, in part, to their measurement availability. By default, this emphasis created a research environment that neglected several important factors: (a) parasympathetic (e.g., vagal) influences, (b) interactions between sympathetic and parasympathetic processes, (c) peripheral autonomic afferents, (d) central regulatory structures, (e) the adaptive and dynamic nature of the autonomic nervous system, and (f) phylogenetic and ontogenetic differences in structural organization and function. Polyvagal Theory proposed a more complex nonlinear model of autonomic regulation that focused on identifiable and potentially measurable neural pathways that contribute to autonomic regulation through a definable feedback system that could promote homeostatic function. The theory required a conceptualization of autonomic regulation that was challenging to psychophysiologists. At the time, psychophysiology emphasized a top-down representation of central nervous system function in measurable peripheral physiology (e.g., autonomic response patterns). Thus, many psychophysiologists hypothesized that systematic quantification of peripheral autonomic responses would provide reliable information linked to brain function and mental processes. Prior to the Polyvagal Theory, my research was consistent with this top-down perspective. For example, I wrote an article titled “Heart Rate Patterns in Neonates: A Potential Diagnostic Window to the Brain” (Porges, 1983)."""

# Baysian signature optimizer
from dspy.teleprompt import BayesianSignatureOptimizer
teleprompter = BayesianSignatureOptimizer()
bayesian_compiled_classifier = teleprompter.compile(Notes(), devset=devset,
                                                optuna_trials_num=3,
                                                max_bootstrapped_demos=4,
                                                max_labeled_demos=4,
                                                eval_kwargs=kwargs)

bayesian_compiled_classifier.save(path="saves/BayesianSignatureOptimizer.json")

I'm having the same issue. I'd love it if someone would fix it...  I've spent about 40 hours on this one problem. I've tried fixing this every which way I can.

cc @XenonMolecule @klopsahlong

Thanks for reporting this @cognitivetech @bryonmccoy . Can we get a full stack trace of the error?

Seeing a full trace of the error stack will probably make this pretty easy to spot

I took a look at this, and managed to recreate it with a relatively small subset.
import dspy

class Notes(dspy.Signature):
    """Bulleted Markdown Notes, Headings and Terms in Bold"""
    document = dspy.InputField()
    notes = dspy.OutputField()

Notes()

I am including the Notes(), cause you are passing the Signature directly into the Teleprompt, in this way.
If you take a look at the way __new__ and __init__ are set up for dspy.Signature, it appears that simply declaring the Notes class itself, instantiates the object.
Ie. Calling only the below
import dspy

class Notes(dspy.Signature):
    """Bulleted Markdown Notes, Headings and Terms in Bold"""
    document = dspy.InputField()
    notes = dspy.OutputField()

Will call both the dspy.Signature.__new__, and then dspy.Signature.__init__, without instantiation in the python file directly.
Later on when Notes() is being called, this is not instantiating the Notes object, but rather calling the Notes.__call__  method. It is at this point that __call__ requires an 'example' argument to pass to `TemplateV2'.
If for example, you get around this by Simply passing Notes as opposed to Notes() into the teleprompt, you bypass the Example error, but the teleprompt tries to deepcopy the signature. A deepcopy method is used for dspy.Module but not dspy.Signature.
Should a dspy.Signature be directly passed into Teleprompters?

Yep I suspect this is the issue.   BayesianSignatureOptimizer takes a dspy.Module to optimize.  I acknowledge the naming is a bit confusing and we are likely going to update the optimizers soon with the official release.
Good sleuthing @KCaverly!
For this example making a dspy.Module wrapper for the Notes() signature should resolve this particular problem.  You can use either dspy.ChainOfThought or dspy.Predict.
You can either pass dspy.Predict(Notes) to the optimizer, or create a custom wrapper module:
class WriteNotes(dspy.Module):
    def __init__(self):
        super().__init__()
        self.generate_notes = dspy.Predict(Notes)

    def forward(self, document):
        return self.generate_notes(document=document)


No Discovery Settings in Teams

Oddly, everything under "Set whether existing private teams are discoverable" is not true. The PS script does not make a team appear in search, and there is no "Team Discovery" section under the Team settings tab. Did something change since this was written?

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

ID: f5920152-5fee-41ed-56df-ad7b51b25cc2
Version Independent ID: 88cfc850-5e36-48ee-ba99-088b2b653f1e
Content: Manage discovery of private teams in Microsoft Teams - Microsoft Teams
Content Source: Teams/manage-discovery-of-private-teams.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

We can probably put a pin in this for now. I opened a ticket with support, they are "researching". They said the following: That Preview features are rolled out by Datacenter, so if the Preview hasn't reached my tenant's DC yet then they won't see it. They also said that they can "turn on" Preview for my tenant, but they wanted to see what it will do to the tenant. So...?
I thought I had Preview on, based upon my tenant's organization settings. All I know for sure is that MS support doesn't know what Preview is or how it works, so this entire article, which appears to have been published for 2 months (!), should probably go away until this feature is actually rolled out.

@kstario  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @kstario, thank you for your feedback.
I found the ShowInTeamsSearchAndSuggestions parameter in the latest Teams PowerShell module (1.0.6). But I cannot find "Turn on discoverability check box" in the Admin Center.
Do you have more information from support?
Thanks!

I have a ticket open with support. They’ve escalated. Nothing from them yet… I will post back when they have something for me.
From: Dario<EMAIL_ADDRESS>Sent: Friday, April 24, 2020 1:56 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] No Discovery Settings in Teams (#4577)
Hi @kstariohttps://github.com/kstario, thank you for your feedback.
I found the ShowInTeamsSearchAndSuggestions parameter in the latest Teams PowerShell module (1.0.6). But I cannot find "Turn on discoverability check box" in the Admin Center.
Do you have more information from support?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4577#issuecomment-619211747, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALIKTGOKTGF6TXKT4EVRTJTROHVF3ANCNFSM4MKE5YTA.

Thank you @kstario!

@kstario Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

The issue has not been resolved...

From: Manuela Scanu<EMAIL_ADDRESS>Sent: Sunday, April 26, 2020 9:10 PM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness<EMAIL_ADDRESS>Cc: kstario<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] No Discovery Settings in Teams (#4577)
@kstariohttps://github.com/kstario Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4577#issuecomment-619686217, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALIKTGOR2XC37OSUVHEDNF3ROTZTHANCNFSM4MKE5YTA.

Hi @kstario,
As you wrote in your second comment, it is a preview feature. It may not be available to all tenants worldwide.
Please share the support information, if there is anything to update in this article we can reopen it.

I have the same Issue.
I opened a ticket, but the microsoft support did not help me. they did not understand the issue and gave me to do's without any sense.

Hi @Teimoon, thank you for your comment.
This is a preview feature and that's why you probably don't have this option in the Admin Center yet.

Dario- The issue here is that MSFT uses the word “preview” in other circumstances to mean a features that can be enabled or disabled by the customer. Insider builds, admin centers, etc. all have used preview. Thus, it seems many of us Admins are expecting the Teams “preview” to also be something that we can enable/disable. Thus you can see why it’s confusing to respond stating that preview status is the reason for why it’s not available.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Dario<EMAIL_ADDRESS>Sent: Thursday, April 30, 2020 6:37 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] No Discovery Settings in Teams (#4577)
Hi @Teimoonhttps://github.com/Teimoon, thank you for your comment.
This is a preview feature and that's why you probably don't have this option in the Admin Center yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4577#issuecomment-621806882, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALIKTGL5I4YADQAKX3U4LDTRPFWKDANCNFSM4MKE5YTA.

Hi All-
I finally received an update from Microsoft regarding Discovery:
“I (MS Support) was informed by the product team that new requests for Preview Release are no longer being responded to.
They also informed me that the discovery feature will be made available by the end of September.”
Hopefully we see the feature in September!

@kstario Thank you for this information!
In September when this feature reach GA, we can remove the preview sentence.


[WIP] Multi image

WIP support for multi-image building.
Must be applied simultaneously with https://github.com/zephyrproject-rtos/zephyr/pull/13672
See the Zephyr PR for details.

Some of those changes were already merged as part of 048168aa377e40f5e103a48d634a1c7b7035bedd, please rebase!

Done

Unless I'm misreading something, the commit is titled "dump: dump\n\ndump". Perhaps a better description is in order.
I'm also wondering if we need a better name for this than "multi image", since we are using multi image to refer to having multiple images that MCUboot knows how to load. I'm not sure what terms are best here. But, "multi-image" from MCUboot's perspective makes sense as MCUboot itself handling multiple images. Maybe "multi build"? I'm not real sure.

Unless I'm misreading something, the commit is titled "dump: dump\n\ndump". Perhaps a better description is in order.

The commit message has been improved.

I'm also wondering if we need a better name for this than "multi image", since we are using multi image to refer to having multiple images that MCUboot knows how to load. I'm not sure what terms are best here. But, "multi-image" from MCUboot's perspective makes sense as MCUboot itself handling multiple images. Maybe "multi build"? I'm not real sure.

Since these are two different domains, I'm hoping it will always be obvious from context what we are talking about. It will be difficult to change this terminology as it is in wide use already. To disambiguate when not obvious from context we can try to be more verbose, e.g. multi-image building.

@SebastianBoe Please rebase on latest master!

Closing, https://github.com/zephyrproject-rtos/zephyr/pull/13672 was not accepted.


not working

tried installing many times but every time i hit alt+r, nothing happens.

same problem here..

Please provide steps to reproduce the issue (did you open a file? Create a new one? What language was it set to? etc) including details about your system environment (Operating System, plugin version, etc). I can't provide much help with this issue as is.

Closed with no reproduction steps.


Is there a way to declare global options (global flags) to be printed with every command?

my question is...
Is there a way to declare global options (global flags) to be printed with every command?
Hi,
I am looking for a way to be able to have global options printed regardless of whether the command is a top-level or a sub command.
One solution that I came up with was to make the flags a Global var and then pass it through my top-level flags and through sub-command flags, but that doesn't seem to be what I seek, since in the second case the flags are been shown like OPTIONS rather than GLOBAL OPTIONS.
Again, if a subcommand has another flag, then those "global flags" are overridden and are not being shown at all.
Followed the issue #795, but that didn't seem to find what I was looking for.
Anyone has any idea on if there's something I can use?
Thanks!

Any news on that? ^^
Thanks!

@dsotirakis do you want to only print global options in help for command or to be able to use specify them on cmdline after command ? For the former case you could override command help template to achieve it

No way to do it right now. Nothing is planned for it yet


Update README.md

Update docs to make it clear how to get hold of the current text state in block mode.

:+1: Had to check source myself as well.


"Keep updated" not working for exports

Debug log ID
9MAKWMJ8-euc/6.7.251-7
What happened?
Exports that were made with the "keep updated" flag set do not automatically update anymore. If I create a new export file with this flag set, the initial export works ok but it does not update after that.
Attempting to force an export for a  "keep updated" file from the Zotero/Better BibTeX preferences pane has no effect.

I have now found this problem on a second computer running macOS 15.1. The debug log ID for the second computer is MKW8ZXE9-euc/6.7.251-7

Can you get me a new log from 7306?

My mistake: keep updated seems to be working ok, but the "Updated" field in the Better BibTeX preferences is not reflecting the new update. This combined with some other problem (maybe just a slow update) meant that I thought the whole update process was failing.
Anyway: the "Updated" field does not appear to reflect the actual last updated time. The log is QEW5C6ME-euc/<IP_ADDRESS>06-7

Cool, thanks,I'm looking into it.


Adds BLAST+7 format to skbio/io/format

Adds module, tests, and test data. Finishes addressing #1110.

@Kleptobismol this looks great! Just had a couple minor comments.

Merged, thanks @Kleptobismol!


Increase minimum required python version to 3.10

Given that since JAX 0.4.31, the minimum required Python version is 3.10, shouldn't this repo also increase the minimum Python version too?

jax 0.4.31
Changes
The minimum Python version is now 3.10. 3.10 will remain the minimum supported version until July 2025.

(Which also means we could use the union operator for types | :D)

Wouldn't that also mean bumping the jax dependency (a fair amount, from jax>=0.4.13)?

Yeah, I don't see a reason to bump this until we also find ourselves needing to depend on JAX 0.4.31+.


Performance Issue When Upgrading from EFCore 1.x to EFCore 2.0 - Solved But Should Be Noted

I recently joined an organization as an Architect to help improve the way in which the company utilizes technology. The company had embarked on creating several "microservices" using .NET Core 1.x and EFCore 1.x. We are planning to move these services to Docker and K8's in the near future. I know there were performance improvements as well as a more complete API footprint in .NET Core 2.0 and had done this migration in the past at a previous company. So I decided to spend an afternoon and convert one of the current applications to .NET Core 2.0 and EFCore 2.0. This went pretty well so we decided to deploy the application into our non production environments and test. We did this without issue.
We then proceeded to move the application to production. Immediately, we started seeing CPU & Memory spikes of 98% to 100% CPU and almost 1GB of RAM. We obviously rolled this back and proceeded to question what had changed. Our code hadn't changed, I quite literally just upgraded the project references, Nuget references, and target framework references. I left the code completely as I had found it.
I searched through the release notes and found nothing that would warn me of this type of problem. I spent some time looking at the forums and known issues finding a few instances where people were experiencing performance issues but nothing seemed to match my exact problem.
To make a long story short, I found 1 line of code that was causing the issue of crazy CPU & Memory spikes. It seems like it was a design decision to make this change in EFCore 2.0 as this worked great in EFCore 1.x
The problem was we were using string.Equals() in the Where clause. I can see how we would have made this mistake as in all the years I've been programming. StringComparisons are the most efficient way to compare two strings.
This code executed in a performent manner in EFCore 1.x
            var agreementsQuery = await _context.AgentAgreements
                .Include(x => x.Contracts)
                .Where(a =>
                    string.Equals(a.CompanyCode, companyCode, StringComparison.IgnoreOrdinalCase)
                .ToListAsync();

But in EFCore 2.0, the above code actually pulls all the data back from the database and executes that Where clause on the client side. (i.e. application code side) A bit of sql profiling gave us the 411. Removing the StringComparison code did the trick.
EFCore 2.0 - Without the StringComparison
            var agreementsQuery = await _context.AgentAgreements
                .Include(x => x.Contracts)
                .Where(a => a.CompanyCode == companyCode)
                .ToListAsync();

Understandably, you've made some very clear and good choices about which part of the queries operate on the sql server (i.e. the provider) and which part of the queries operate on the application side.
https://docs.microsoft.com/en-us/ef/core/querying/client-eval
I have two reasons for bringing this to your attention.
First, it's possible this is an oversight and you didn't realize you made this change. Unlikely.
Secondly, and more importantly, if others run into the same issue it would be great for them to find this early.
I'm wondering if this is not an oversight, can we put a notice of this in the migration notes that everyone bings or googles to figure out how to migrate from EFCore 1.x to EFCore 2.0?
Further technical details
EF Core version: 2.0
Database Provider: (e.g. Microsoft.EntityFrameworkCore.SqlServer)
Operating system: Windows Server 2012 R2 & SQL Server 2012 R2
IDE: (e.g. Visual Studio 2017 15.4)

@BradCurry Question: when EF decides to evaluate something like this on the client it will write a warning out to the log. Did you see this warning? If not, it would be good to figure out why not.

I didn't actually look in the entity framework logs because I didn't know it did that until after I found the solution. I also haven't checked to see if the warning was written in the logs. That is something I could easily do and report back if you'd like.

@BradCurry We discussed this in triage and to answer your questions:

The change was made intentionally since in general we cannot translate the StringComparision semantics to SQL. This is complicated by the fact that, even without any specific comparison specified, there may be differences between the database string semantics and the C# string semantics. This general issue is tracked by #673. However, if you specifically specify a comparison, then we honor that by forcing client eval, which is why your application was impacted.
The way we warn people about client evaluation in their queries is through the warning in the log. This can optionally be configured (on the DbContextOptionsBuilder) to generate an error (exception) instead of a warning. At this time we don't plan to add any other mechanism to warn about these things, but it is something that we are aware can cause problems so we are open to doing more in the future if it proves valuable.

@ajcvickers thanks for the follow up on this. I completely agree with the path you've chosen here. Had I known about the warning system built into the DbContextOptionsBuilder earlier, it would have made this a pretty trivial find.
Thanks again for the work you guys are doing here.


Add a charmcraft.yaml, add support for jammy and remove EOL groovy, hirsuite series

Charms now need a charmcraft.yaml file to define what series to build on and for.
Also remove groovy, which is EOL since July 2021.

@mthaddon , could you add
tests/data/model-config.yaml with the contents:
---
image-stream: daily

after that update the tox.ini use the --model-config option i'm adding to pytest-operator.  Hopefully i'll get it reviewed and added soon
[testenv:integration]
deps =
    pytest
    pytest-operator
    ipdb
commands = pytest --tb native --show-capture=no --log-cli-level=INFO -s --disable-warnings --model-config tests/data/model-config.yam {posargs} {toxinidir}/tests/integration


LG Companion powering off display when I load full screen game after switching GPUs

Today I upgraded from a 3060 ti to a 3080. Now when I launch full screen games, I am noticing my LG C2 turn off (being used as a monitor). I tried removing the C2 and re adding it to the LG companion but the issue still occurs.

hi @jsaltzman congrats on the new hardware! What version LGTV Companion are you running? Please paste the full log here and I'll have a look at what's going on

hi @jsaltzman any update on this issue?

Thanks for the response. I have not responded because it seems like this sort of ironed itself out.

Good to know thanks!


Widen ember-get-config dependency requirement

This addon works fine with 0.2.x and requiring 0.3.0 can cause dependency version conflicts, so let's widen the requirement so that users can choose a version that does not cause them any conflicts.
/cc @samselikoff

Looks good!


cleanup config loader

Don't merge untill new deployment is in.
Best reviewed commit by commit

Done in individual prs


Bump version of hibernate to 6.0.1.Final - so we can leverage various (performance) improvements

Environment Details

Helidon Version: 2.5.0
Helidon MP
JDK version: 17.0.2
OS: Ubuntu 22.04 LTS
Docker version (if applicable): n/a

Problem Description
Version 6.0.1.Final of Hibernate provides a number of performance improvements.
https://github.com/hibernate/hibernate-orm/blob/main/changelog.txt
In order to benefit from these improvements, Helidon MP should consider bumping the version to 6.0.1.Final

We can't do this on the 2.x line; Hibernate 6 relies on Jakarta Persistence 3.0, which involves jakarta.persistence packages, not javax.persistence packages.

Ah - I see, that's unfortunate.
I actually checked the FAQ earlier and it points to the 3.0 specification: https://jakarta.ee/specifications/persistence/3.0/jakarta-persistence-spec-3.0.html
From there I took it that this potentially would be doable.

Perhaps we're talking past each other: Jakarta Persistence 3.0 features jakarta.persistence package names.  Helidon 2.5.0 relies on Jakarta Persistence 2.2, which features javax.persistence package names.

Perhaps we're talking past each other: Jakarta Persistence 3.0 features jakarta.persistence package names. Helidon 2.5.0 relies on Jakarta Persistence 2.2, which features javax.persistence package names. I'll change the FAQ information, which was written to be against our master branch, which will eventually become the Helidon 3.x line.

I guess we are the FAQ that I was referring to is from MP 2.5.0 and it points to 3.0.0 JPA. So that is confusing, the link in the FAQ should probably be update.

This is addressed in master with #4484.


Incomplete tests: HTTP/gRPC routing support

Context: production readiness proposal and plan
The feature “HTTP/gRPC routing support” is identified as incomplete test coverage. As a measure to reach Istio production quality in 0.3, this issue is opened to track the progress of providing sufficient test coverage for the feature in question.
This issue is initially assigned to the working group leads.
Recommendations:

Come up with a test plan for how the feature should be tested. Identify and document (in this issue, or a separate document this issue will link to) test cases and whether each will be covered by an integration test (with some level of mocking and/or starting up selected components in test environment), or end to end test (aka system test, which brings up the whole Istio to exercise the feature; currently live in the istio/istio repo).
If you expect the test plan is complex and controversial, consider having it formally reviewed.
State an ETA in the issue, and assign this to a developer who will execute the test plan.
Execute the test plan as the highest priority for 0.3.
For any bug or defect identified by the new test cases, file a new issue and link it from this one.
Close this issue only when the test plan is completely executed, and all additional issues identified in step 3 are fixed.

If you see a risk of not fixing this issue by end of 0.3, please contact<EMAIL_ADDRESS>as soon as possible. We will also periodically ping the issue for update.

Please close. This makes no sense. We have plenty of tests for http (and gRPC as well).

Do we still want this? @rshriram has anything changed since your comment?

Don't we need some tests for conversion http <--> grpc or some scale tests? While we can limit fault injection or multi-zone tests to a small scale, if we need to test with a higher scale, this is the area where we could do it.
Are we happy with what the tests check for?

Issue moved to istio/istio #1477 via ZenHub


Prevent multiple validation from multiple events

Prior to this change, it was possible for the handler to process multiple events in the same contextual run. This meant that if a validator used fetch() there would be multiple fetch() for each event triggered. This isn't ideal. Instead we ignore events while waiting on the first validator to complete.
Code should be awaiting anyway so a race condition between different values should not occur.

I really think it would be better if instead of a on off latch. We were to make this a keepLatest style deferral￼


🐛 Deformed preview image

What's happening?
I just updated from v2.15.4 to v3.8.2, I upgraded to get access to the camera for iPhone 15.
But now I have a strange image when I'm in my ScreenCam.
This is the preview of the picture (Sorry for the car):

This is the picture after it is taken :

My preview is deformed and I don't understand why.
When I go to the front camera and I come back to the back Camera, the preview picture is fine.
I've tried adding  resizeMode="contain", to see if it's a size issue, but nothing changes.
Reproduceable Code
const [isFrontPhoto, setIsFrontPhoto] = useState(false);
const camera = useRef<Camera>(null);
const device = useCameraDevice(isFrontPhoto ? 'front' : 'back');

<Camera
  ref={camera}
  photo
  style={sharedStyles.flex}
  device={device}
  isActive={isFocused}
  enableZoomGesture
  resizeMode="contain"
/>

Relevant log output
WARN  Non-serializable values were found in the navigation state. Check:

LoggedInStack > Camera > params.finallySetImages (Function)

This can break usage such as persisting and restoring state. This might happen if you passed non-serializable values such as function, class instances etc. in params. If you need to use components with callbacks in your options, you can use 'navigation.setOptions' instead. See https://reactnavigation.org/docs/troubleshooting#i-get-the-warning-non-serializable-values-were-found-in-the-navigation-state for more details.
    at BaseNavigationContainer (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:203434:28)
    at ThemeProvider (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:208345:21)
    at NavigationContainerInner (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:208238:26)
    at RootNavigation (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:134936:29)
    at PortalProviderComponent (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:234636:33)
    at RNGestureHandlerRootView
    at GestureHandlerRootView
    at RNCSafeAreaProvider
    at SafeAreaProvider (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:238468:24)
    at App (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:106130:89)
    at LocaleProvider (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:323508:41)
    at AuthProvider (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:213896:41)
    at QueryClientProvider (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:212744:23)
    at PersistQueryClientProvider (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:338538:22)
    at ProvidersWrapper (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:106160:91)
    at ReactNativeProfiler (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:127162:36)
    at RCTView
    at View (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:47073:43)
    at __Sentry.TouchEventBoundary (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:128534:36)
    at RootApp
    at RCTView
    at View (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:47073:43)
    at RCTView
    at View (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:47073:43)
    at AppContainer (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:46954:36)
    at myapp(RootComponent) (http://localhost:8081/index.bundle//&platform=android&dev=true&minify=false&app=myapp&modulesOnly=false&runModule=true:85106:28)

Camera Device
{
  "formats": [],
  "sensorOrientation": "landscape-right",
  "hardwareLevel": "limited",
  "maxZoom": 4,
  "minZoom": 1,
  "maxExposure": 20,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": false,
  "isMultiCam": false,
  "minFocusDistance": 5,
  "minExposure": -20,
  "name": "BACK (0)",
  "hasFlash": true,
  "hasTorch": true,
  "position": "back",
  "id": "0"
}

Device
Samsung Galaxy A32
VisionCamera Version
3.8.2
Can you reproduce this issue in the VisionCamera Example app?
No, I cannot reproduce the issue in the Example app
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Hi,
I have a similar issue.
They shipped a fix that worked for many people, you might want to try with version 3.9.0-beta.3.
For me it didn't work however.

Seems like this is a known issue by a few people recently. I too am experiencing this on Android (IOS works fine)
I will try 3.9.0-BETA.3 and report back.

Same error here using Google Pixel 2XL

3.9.0-BETA.3 did not work either. (I am testing with a Samsung A14)

I have the same issue

Same here. Pixel 7 Pro

Same Samsung s10+

Created a PR to fix this: https://github.com/mrousavy/react-native-vision-camera/pull/2564 💪

I think I fixed this now. I don't have a device with a different sensor orientation than landscapeLeft here to test it, so could you guys please test if v3.9.0-beta.5 fixed the issue for you guys? :)

Awesome, quite important to fix such a critical bug 💪
If you appreciate my time and dedication, please consider sponsoring me on GitHub!


Datetime format

I'm trying to write a XPT file with some fields in DATETIME22.3 format, but it gives an error every time:
"TypeError: must be real number, not str"
In which format should I input the data?

I'm going to have trouble debugging this, without an example XPT document that uses that DATETIME22.3 format. I suggest you use a string format instead.
Or, could you tell me more about what that format does? What's the .3 for?


Fix fail test in TestWebUi.testNoPasswordAuthenticator

#5558 catch all RuntimeException which cause testNoPasswordAuthenticator in TestWebUI.java fail.
This test will check if Exception is thrown when PasswordAuthenticator is not loaded.

thanks,
being fixed in https://github.com/prestosql/presto/pull/5644


Other SD WAN platform support

Team,
I know current solution is purely based on cisco platform, but do you have some plan to support for other SD WAN platform also.
if you come across any of such requirement from other team or have some input to share with me, would be great.
Also can you tell me what would be the possible change (may be where to change), if i need to integrate this solution with other SD WAN platform.
thanks in advance.
BR,
Nilesh

@nilesh150883, the Cloud Native SD-WAN project was architected from the beginning with support for multiple SD-WAN platforms in mind. Cisco Viptela SD-WAN is the first supported platform, and we may support others in the future, but we don't have any committed roadmap at this time.
Adding support for other SD-WAN platforms should be relatively simple, if one knows the target platform well. The interface between the reader and the adaptor is well defined, and the server part of this project can be reused. Then, the adaptor_server/configure_controller.py file imports the sdwan library, and calls the appropriate functions for each event type. You will need to make changes in adaptor_library/metadata_adaptor/core_lib.py to implement support for a different platform.

@nilesh150883, the Cloud Native SD-WAN project was architected from the beginning with support for multiple SD-WAN platforms in mind. Cisco Viptela SD-WAN is the first supported platform, and we may support others in the future, but we don't have any committed roadmap at this time.
Adding support for other SD-WAN platforms should be relatively simple, if one knows the target platform well. The interface between the reader and the adaptor is well defined, and the server part of this project can be reused. Then, the adaptor_server/configure_controller.py file imports the sdwan library, and calls the appropriate functions for each event type. You will need to make changes in adaptor_library/metadata_adaptor/core_lib.py to implement support for a different platform.

Thank you for the input. As you suggested let me explore for other platform and if any finding will share with you guys.
Cheers.

Thank you for the input. As you suggested let me explore for other platform and if any finding will share with you guys.
Cheers.

@nilesh150883 keep us posted of the progress. Would it be possible to share what the other SD-WAN platform is? We would like to be able to keep track of the different efforts, so that we can avoid duplicating work. In case someone else is interested in the same platform, we could point them to you. Thanks!

@nilesh150883 keep us posted of the progress. Would it be possible to share what the other SD-WAN platform is? We would like to be able to keep track of the different efforts, so that we can avoid duplicating work. In case someone else is interested in the same platform, we could point them to you. Thanks!

@ljakab I'm from business team and doing research on new areas. So not sure as of now what would be my target SD WAN system but once our team is ready to work in this space will surely guide to you guys for more input and sharing.

@ljakab I'm from business team and doing research on new areas. So not sure as of now what would be my target SD WAN system but once our team is ready to work in this space will surely guide to you guys for more input and sharing.


Faceverification QA server goes down after some time worked

[x] check why it happens
[ ] fix

@sirpy
I've downloaded and checked the Docker logs for the container running custom ZoOm server
Unfortunately i couldn't got any possible reason why server got stuck sometimes.
The logs contains the generic messages only - access logs, FV errors (such as enrollment doesn't exists, already enrolled, liveness failed etc)
But, i got the backend logs from goodserver-qa - we receiving an 504 Gateway Time-out error during FV serve call in that case.
This means the nginx proxy and event the web server on ZoOm container are working and trying to process incoming request, but the Java backend is stuck from some unknown, internal reason. I'm not experienced in the Java backend and JSP so i couldn't provide any additional info. We have to ask Facetec regarding that issue. I could just to suppose it could be caused by the low RAM amount on the fvqa instance (like the issue with v9 backend where server couldn't even start due to 'unknown & unexpected error')
For now, to fix the issue, i added the following cron job running each minute:
* * * * * /usr/bin/curl -v --silent -m 5<EMAIL_ADDRESS>2>&1 | grep '"ok":true' || /bin/systemctl restart facetec

It monitors the FV server status and automatically restarts it if /status endpoint call reaches 5sec timeout

ok 10x. yeah probably memory issues


Feature/kas 4044 minutes pdf export

Merged this because the addition in itself was ok and wouldn't break anything.
But the service in the docker-compose.yml simply doesn't exist.
Failed to realize that pre merge.
Commented that service on DEV branch


Output Directories Used by gen-plugin

Description
If not set, test_output and doc_output will now be sent to the same directory as the aac plugin file when generate is called.
Linked Items:
Closes/Fixes/Resolves #833
Added

Describe any new features.

Changed

Describe any changes in existing functionality.

Deprecated

Describe any deprecated features.

Removed

Describe any removed features.

Fixed
Fixed the bug where the given code_output parameter was being applied to test and doc output as well.
Security

Describe any security-related changes.

Checklist:

[ ] I updated project documentation to reflect my changes.
[ ] My changes generate no new warnings.
[ ] I updated new and existing unit tests to account for my changes.
[ ] I linked the associated item(s) to be closed.
[ ] I bumped the version.
[ ] I added the labels corresponding to my changes.

Would like this to be evaluated as part of this bug work. Response of cancelling the generation command.
/workspace/AaC/python (output-directory-flag) $ aac gen-plugin features/docs_examples/dev_guide_plugin_dev_guide/docs_do_stuff.aac --code-output ./example_plugin
AaC will generate code and tests in the following directories:
   code: ./example_plugin
   tests: /workspace/AaC/python/features/docs_examples/dev_guide_plugin_dev_guide
   docs: /workspace/AaC/python/features/docs_examples/dev_guide_plugin_dev_guide
Do you want to continue? (y/n): n
Traceback (most recent call last):
  File "/workspace/AaC/python/src/aac/plugins/generate/generate_impl.py", line 45, in generate
    code_out_dir, test_out_dir, doc_out_dir = get_output_directories(
  File "/workspace/AaC/python/src/aac/plugins/generate/generate_impl.py", line 275, in get_output_directories
    raise OperationCancelled("User cancelled operation.")
aac.execute.aac_execution_result.OperationCancelled: User cancelled operation.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/workspace/AaC/python/venv/bin/aac", line 33, in <module>
    sys.exit(load_entry_point('aac', 'console_scripts', 'aac')())
  File "/workspace/AaC/python/venv/lib/python3.9/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/workspace/AaC/python/venv/lib/python3.9/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/workspace/AaC/python/venv/lib/python3.9/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/workspace/AaC/python/venv/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/workspace/AaC/python/venv/lib/python3.9/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/workspace/AaC/python/src/aac/execute/command_line.py", line 83, in wrapper
    return func(*args, **kwargs)
  File "/workspace/AaC/python/src/aac/plugins/gen_plugin/__init__.py", line 74, in run_gen_plugin
    gen_plugin_generate_result = after_gen_plugin_generate(
  File "/workspace/AaC/python/src/aac/plugins/gen_plugin/gen_plugin_impl.py", line 57, in after_gen_plugin_generate
    return generate(
  File "/workspace/AaC/python/src/aac/plugins/generate/__init__.py", line 26, in run_generate
    generate_result = generate(
  File "/workspace/AaC/python/src/aac/plugins/generate/generate_impl.py", line 55, in generate
    result.add_message(ExecutionMessage(e.message, None, None))
TypeError: __init__() missing 1 required positional argument: 'location'


update to eslint v9

Fixes https://github.com/jhipster/generator-jhipster-react-native/issues/1958

@react-native-community/eslint-config was renamed to @react-native/eslint-config and does not support eslint v9.
It’s just a pre-defined config for others plugins.
Drop it and use some plugins and configs directly.


Don't install requests with security extra

It's not needed in Python 2.7.6+, and it causes requests to use pyOpenSSL instead of the stdlib ssl module.
Critical Changes
Changes
Issues Closed

never mind, it's still required by simple-salesforce


Were to download the build from app veyor?

 Or were on appveyor (VS 2017 Relase) can i download the zip with the libraries? :D Under Artifacts theres nothing :(

Yeah, I don't collect artifacts, I use CI just to make sure it builds. You'll have to build it locally.


Custom reporters option eats all following arguments up to the next option

#10191  🐛 Bug Report
When using the --reporters option, it takes its argument and all following arguments up to the next option to be custom reports.
This differs from the documentation which suggests that you should repeat --reporters once for each reporter.
To Reproduce
$ yarn jest --reporters=default xyz
Error: Could not resolve a module for a custom reporter.
  Module name: xyz
    at /home/ubuntu/app/node_modules/jest-config/build/normalize.js:557:15
    at Array.map (<anonymous>)
    at normalizeReporters (/home/ubuntu/app/node_modules/jest-config/build/normalize.js:539:33)
    at normalize (/home/ubuntu/app/node_modules/jest-config/build/normalize.js:632:5)
    at readConfig (/home/ubuntu/app/node_modules/jest-config/build/index.js:224:68)
    at async readConfigs (/home/ubuntu/app/node_modules/jest-config/build/index.js:404:26)
    at async runCLI (/home/ubuntu/app/node_modules/@jest/core/build/cli/index.js:230:59)
    at async Object.run (/home/ubuntu/app/node_modules/jest-cli/build/cli/index.js:163:37)
$ yarn jest --reporters=default --runInBand xyz
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In /home/ubuntu/app
  16908 files checked across 3 projects. Run with `--verbose` for more details.
Pattern: xyz - 0 matches
$ yarn jest --reporters=default xyz --runInBand xyz
Error: Could not resolve a module for a custom reporter.
  Module name: xyz
    at /home/ubuntu/app/node_modules/jest-config/build/normalize.js:557:15
    at Array.map (<anonymous>)
    at normalizeReporters (/home/ubuntu/app/node_modules/jest-config/build/normalize.js:539:33)
    at normalize (/home/ubuntu/app/node_modules/jest-config/build/normalize.js:632:5)
    at readConfig (/home/ubuntu/app/node_modules/jest-config/build/index.js:224:68)
    at async readConfigs (/home/ubuntu/app/node_modules/jest-config/build/index.js:404:26)
    at async runCLI (/home/ubuntu/app/node_modules/@jest/core/build/cli/index.js:230:59)
    at async Object.run (/home/ubuntu/app/node_modules/jest-cli/build/cli/index.js:163:37)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Expected behavior
If I use --reporters=xxx yyy or --reporters xxx yyy it should only add xxx as a reporter and leave yyy as a leftover argument to jest.
envinfo
  System:
    OS: Linux 5.4 Linux Mint 19.3 (Tricia)
    CPU: (6) x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
  Binaries:
    Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node
    Yarn: 1.19.0 - /usr/bin/yarn
    npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm
  npmPackages:
    jest: 26.1.0 => 26.1.0

Workaround
Ensure that --reporters has an option between it and any non-option command line arguments.

This is still happening with Jest 26.6.3
  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 14.16.1 - ~/.nvm/versions/node/v14.16.1/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.12 - ~/.nvm/versions/node/v14.16.1/bin/npm
  npmPackages:
    jest: ^26.4.0 => 26.6.3

Another workaround is use --:
yarn jest --reporters=default -- xyz


Upgrade cargo-api-linter to latest nightly

[x] Upgrade cargo-api-linter
[x] Upgrade smithy-rs nightly to match cargo-api-linter nightly
[ ] Run cargo-api-linter against crates it used to ICE against to get full set of public external types

Still can't successfully run cargo-api-linter against aws-endpoints.


How to use a defined query template in our query?

How to use a defined query template find_user_tpl, in our query?
query := elastic.NewTemplateQuery("find_user_tpl").Var("query_string", "Lin")
parse to "query": "find_user_tpl"..

Hi there! Do these tests help?

Got it, very useful. I have another question, does it support wrapper several kinds of query in a Query?
Thanks very much!

You mean something like boolean queries (docs on elastic.co)?
In case you missed it, Elasticsearch - The Definite Guide is a fantastic online book for learning many of the details of Elasticsearch. Elastic, the Go client, is simply a DSL to all that, and the tests in this repository will probably help you find out about the correct syntax.
Hope this helps :-)

I notice this, your code generate this json:
{"template":{"id":"find_user_tpl","params":{"query_string":"Lin"}}}
Actually, below json code is needed.
curl -XGET localhost:9200/users/_search/template -d '{
"template": {
"id": "find_user_tpl"
},
"params": {
"query_string": "Lin"
}
}'

Are you sure this is correct? The docs state that params is below template and on the same level as id.

I'm sure, you can find in the end of this official page below:
http://www.elastic.co/guide/en/elasticsearch/reference/current/search-template.html#_more_template_examples

I test the docs you provided, using the following command:
curl -XPUT localhost:9200/_search/template/my_template1 -d '{
"template": { "query": {"match": { "name": "{query_string}" }}}
}'
curl -XGET localhost:9200/users/_search -d '
{
"query" : {
"template": {
"id": "my_template1",
"params": {
"query_string": "sbzt1234"
}
}
}
}'
I cannot get any result. But using the query below, I can fetch the result.
curl -XGET localhost:9200/users/_search -d '{
"query": {"match": { "name": "sbzt1234" }}
}'

if I use this query,
curl -XGET localhost:9200/users/_search -d '
{
"query" : {
"template": {
"id": "my_template1",
"params": {
"query_string": "Lin"
}
}
}
}'
I find errors in elasticsearch logs:
org.elasticsearch.search.SearchParseException: [users][1]: from[-1],size[-1]: Parse Failure [Failed to parse source [
{
"template": {
    "id": "tpa",
    "params": {
      "query_string": "Lin"
    }
}

}]]
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:721)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:557)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:529)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:291)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:231)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:228)
at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:559)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.search.SearchParseException: [users][1]: from[-1],size[-1]: Parse Failure [No parser for element [template]]
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:703)
... 9 more
[2015-04-24 14:28:22,930][DEBUG][action.search.type       ] [White Tiger] [users][0], node[Ns63JdBSTsyhhTtAeS-8bA], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchRequest@455da0f6] lastShard [true]

I see. Search templates are really confusing IMHO. Let's figure this out...

# Set up the index and add some documents
echo Delete index...
curl -XDELETE 'localhost:9200/test/'
echo
echo Create index...
curl -XPUT 'localhost:9200/test/' -d '{"settings":{"index":{"number_of_shards":1,"number_of_replicas":0}}}'
echo

# Add some documents
echo Add documents...
curl -XPOST 'localhost:9200/test/testtype/1' -d '{"text":"value1_foo"}'
curl -XPOST 'localhost:9200/test/testtype/2?refresh=true' -d '{"text":"value2_foo value3_foo"}'
curl -XPOST 'localhost:9200/test/_refresh'
echo

# Now set up a template for querying by name via match
echo Delete search template...
curl -XDELETE 'localhost:9200/_search/template/my_template2'
echo
echo Create search template...
curl -XPUT 'localhost:9200/_search/template/my_template2' -d '{
  "template": {
    "query": {
      "match": {
        "text" : "{{my_value}}"
      }
    }
  }
}'
curl -XPOST 'localhost:9200/_refresh'
echo

# Now use the search template to search by keyword
echo Searching with template...
curl -XGET 'localhost:9200/test/_search/template' -d '{
  "template": {
    "id": "my_template2"
  },
  "params": {
    "my_value": "value1_foo"
  }
}'
echo

It should return the first document in the index (value1_foo).
The output should be something like this:
Delete index...
{"acknowledged":true}
Create index...
{"acknowledged":true}
Add documents...
{"_index":"test","_type":"testtype","_id":"1","_version":1,"created":true}{"_index":"test","_type":"testtype","_id":"2","_version":1,"created":true}{"_shards":{"total":1,"successful":1,"failed":0}}
Delete search template...
{"found":true,"_index":".scripts","_type":"mustache","_id":"my_template2","_version":3}
Create search template...
{"_id":"my_template2","_version":4,"created":true}{"_shards":{"total":117,"successful":116,"failed":0}}
Searching with template...
{"took":1,"timed_out":false,"_shards":{"total":1,"successful":1,"failed":0},"hits":{"total":1,"max_score":1.0,"hits":[{"_index":"test","_type":"testtype","_id":"1","_score":1.0,"_source":{"text":"value1_foo"}}]}}

BTW: There seems to be something wrong on the Elasticsearch documentation page. I posted this issue to clarify. IIRC Mustache tags must be written as {{...}}. The Search Template docs use the {{...}} syntax, while the Template Query docs use {...}.
Can you check your code against this, too?

As far as i can tell it turns out that it works like this.
The template gets expanded as is. So there's two ways to make your query work.
a) Searching with the /_search/template endpoint
# Register template
curl -XPUT 'localhost:9200/_search/template/my_template2' -d '{
  "template": {
    "query": {
      "match": {
        "text" : "{{my_value}}"
      }
    }
  }
}'

# Search
curl -XGET 'localhost:9200/test/_search/template' -d '{
  "template": {
    "id": "my_template2"
  },
  "params": {
    "my_value": "value1_foo"
  }
}'

b) Searching with the /_search endpoint
# Register template
curl -XPUT 'localhost:9200/_search/template/my_template3' -d '{
  "template": {
    "match": {
      "text" : "{{my_value}}"
    }
  }
}'

# Search
curl -XGET 'localhost:9200/test/_search?pretty' -d '{
  "query": {
    "template": {
      "id": "my_template3",
      "params": {
        "my_value": "value1_foo"
      }
    }
  }
}'

Notice the subtle differences both in registering the template (the query is missing in b)) and the way to pass parameters when searching.
Can you confirm my findings?
As far as I can see, Elastic (the Go client) currently only supports b).

Thanks very much for your explanation. I try several method include with two {{. Thanks to your comment, I notice there is no "query" following template when PUT the template.

Yes. When you think of it, it's pretty clear. The defined template just gets expanded and replaced in-place. So when you add a query to it (like in a)), you get `{"query":{"query":{...}}}" if you use it in b).
Does this solve your issues with search and search templates?
P.S.: I have some tests for the search templates here in case you need working code.

Nice, it's working in my project. Thanks for your useful golang client, and the clear test cases.

You're welcome. I'll close the issue then. Feel free to create another one when necessary.


Roll Engine from 04a46cc6567a to 9b63414a3797 (1 revision)

https://github.com/flutter/engine/compare/04a46cc6567a...9b63414a3797
2020-10-04<EMAIL_ADDRESS>Roll Skia from 2d7973afc29d to 223ffcdff922 (8 revisions) (flutter/engine#21591)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


Add set of testsystem

Taking inspiration from openmmtools we should add a small set of testsystems for which we know the analytical solution to most properties we want to calculate using sampling.

Was provided by PR #3


Paste support

It would be cool to be able to use paste (via right-click/Paste /whatever) as in normal bash.
Reasoning, use case:
There can be many use cases for that.
Example:
I am using your awesome component as UI for remote terminal to IOT devices (it is much nicer to do it directly in the web page, rather then finding out devices IP, switching to actual Terminal etc.). I use passthrough feature for that.
So I often need to paste things from manuals. Typing them by hand is kind of tedious.
Thank you!

@AndreyDodonov-EH have you been able to modify the package yourself to implement this?

@AndreyDodonov-EH have you been able to modify the package yourself to implement this?


update to spec 9381

⚠ THIS PR CONTAINS BREAKING CHANGES AND SHOULD BE MERGED ASAP ⚠
This app supports specs 9370 and 9381.
BREAKING CHANGES from spec 9370 to 9381:

polkadotXcm: v0 and v1 has been deprecated in favour of v2 and v3
authorship: this pallet has been removed
xcmpQueue, dmpQueue: now this pallets use Weight instead of XcmWeight

Changes:

polkadotXcm: support teleportAssets and teleportAssetsLimited
proxy: methods createPure and killPure now support nesting

Other changes:

Version some types to support xcm v0 and v1 in spec 9370
Improve how ChargeAssetId is shown
Zemu tests are now concurrent
Change build system to support Ledger unified sdk

Closes https://github.com/Zondax/ledger-statemint/issues/28


Document the configured git branch must already exist

Syncing to a branch that does not yet exist will not create it.

I was initially confused by this and it appears I'm not alone :)


warning about sharing axios instance

Warning about sharing axios instance was added to the documentation.

DO NOT set token or any other user related headers in the SSR phase

Thanks but I'm not sure this statement is 100% correct. nuxtServerInit and server-side Store are isolated for each request. Do you have any reporoducable example of such data leak?

I mean to not use the $axios.setToken function because it operates on the global axios instance. in the SSR phase.
Store and nuxtServerInit  is of course isolated.
I will edit the statement.

If you don't like the message. - no problem, you can remove it. I just wanted to warn other user. For me it was a surprise.
https://github.com/nuxt-community/modules/issues/89#issuecomment-318165164
But I will appreciate version update and merge because I want to use the request interceptor in production :)

@awronski Sorry for delay. That shared problem with setToken should be obviously a bug if exists and i try to fix it soon. Meanwhile of transfer axios into a separated repo with some unit tests, I've published 3.1.0 with your enhancement :)


fix fix nullable() of lead/lag

Proposed changes
Issue Number: close #xxx
Problem summary
fix bug when we use NULL as default value for window function lead() and lag().
Checklist(Required)

[ ] Does it affect the original behavior
[x] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

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

run buildall

run p0

run p0

run p0

run compile


[EventRequest] Codeunit 6620 - After CopySalesDoc

We have custom code in the CopySalesDoc function and request a new event publisher at the following location.
CASE TRUE OF
  MissingExCostRevLink AND (LinesNotCopied <> 0):
    MESSAGE(Text019 + Text020 + Text004);
  MissingExCostRevLink:
    MESSAGE(Text019);
  LinesNotCopied <> 0:
    MESSAGE(Text004);
END;

// New event request >>
OnAfterCopySalesDocument(FromDocType,FromDocNo,ToSalesHeader);
// New event request <<

Signature:
OnAfterCopySalesDocument(FromDocumentType: Option; FromDocumentNo: Code[20]; VAR ToSalesHeader: Record 36)

Event already exists.


Use more CPU cores/threads for runtime

Describe the feature
I see that reth caps out at 9-10 CPU cores used during sync, even when say 128 cores are available. It should use all available cores.

which part of sync?

Stages 2/3


Admin page

Hi All,
taking in account the fact that you're moving all the stuff from wekan's pull requests here (I do appreciate that!) I think that it would be nice to have some kind of admin page (maybe even per each board).
Let me explain ... I believe that the most of pull requests weren't merged by @mquandalle because of he would like to them as pluggin ... and I agree with him about this decision. Not all pull-request features are useful for all wekan/wefork users and there should be mechanism to disable one or several features. It would be less messy on the screen for users which want some kind of base functionality and I hope it would be faster a bit for them as they are not trigger odd database requests

@davydov-vyacheslav
I added this to wefork roadmap.
There is existing pull request on for admin page on original wekan/wekan project, I don't remember where. It would be helpful for somebody to find it and add link here.
I have not yet looked at status of plugin system. Anyway with or without it, there will settings option to enable or disable features in settings. Some platforms like Sandstorm turn those features off that Sandstorm platform already provides.
@mquendalle tried to do complete rewrite, and after that he has not had energy to review and accept pull requests for some months, that's why wefork exists. We are happy to merge back if he sometime comes more active.

I don't remember if it was that pull request https://github.com/wekan/wekan/pull/618

@soohwa
Thanks, that's the one I was looking for! There was probably something else also mentioned on original Wekan Gitter chat but I did not have time to scroll back chat history. If someone could find that that then it would be very helpful.
@kramer65
Did you get my email? Please see:
https://github.com/wefork/wekan/wiki/FAQ
https://github.com/wefork/wekan

I found https://github.com/wekan/wekan/issues/353 and https://discuss.wekan.io/t/restrict-registration/71/3
And with the filter : https://github.com/wekan/wekan/issues?q=is%3Aissue+is%3Aopen+label%3AFeature%3AUser-accounts
And on the original chat at Mar 20 18:42 (Mahan @laupkram)
AccountsTemplates.configure({                                          // 11
  forbidClientAccountCreation: true,
  defaultLayout: 'userFormsLayout',                                    // 12
  defaultContentRegion: 'content',                                     // 13
  confirmPassword: false,                                              // 14
  enablePasswordChange: true,                                          // 15
  sendVerificationEmail: true,                                         // 16
  showForgotPasswordLink: true,                                        // 17
  onLogoutHook: function () {                                          // 18
    var homePage = 'home';                                             // 19
    if (FlowRouter.getRouteName() === homePage) {                      // 20
      FlowRouter.reload();                                             // 21
    } else {                                                           //
      FlowRouter.go(homePage);                                         // 23
    }                                                                  //
  }                                                                    //
});                                                                    //
                                                                       //
['signIn', /*'signUp',*/ 'resetPwd', 'forgotPwd', 'enrollAccount'].forEach(function (routeName) {
  return AccountsTemplates.configureRoute(routeName);                  //
});

@soohwa
Thanks! I'll assign this to myself and start working on this.

There's

translation updates mixed with pull request
comments for variable naming that need to be checked

etc so this will take some time.

No pb, anyway it's a good news that is underway ^^

This issue was moved to wekan/wekan#790


Question about kernelmode sockets (wsk.h)

Hi Pavel, good day,
I'm a bit more than halfway through your book (which has been great so far), and I noticed there were no sections regarding kernelmode sockets, in particular how a driver can act as a client to a remote server. Would you happen to have any working examples of this, such that a driver can act as a TCP client and connect to a remote server & send/recv data? I'm aware that wsk.h and netioapi.h are used for this, but the examples I'm finding online either don't compile or simply don't work. I think it could make a good addition to your book in any future versions that you release, as there are probably many others who would be interested in this.
Cheers,
AlSch092

Thanks for the suggestion, it's a great idea for a future edition!
I know about the official sample in the WDK and also this one: https://github.com/wbenny/KSOCKET


Keeping model in state doesn't work with conditional rendering

Hi @caduandrade :)
It seems like the recommended approach of keeping the model in the widget state doesn't work in case of conditional rendering, meaning when the Davi isn't rendered at all due to a condition preventing it. For example, if a custom loader is rendered while data is loaded.
See the below example code, which is based on the "external sort" template code, but it renders a different widget instead of the Davi table when it is loading.
import 'dart:ui';

import 'package:davi/davi.dart';
import 'package:flutter/material.dart';

void main() {
  FlutterError.onError = (details) {
    FlutterError.presentError(details);
    print("Unhandled Flutter error: ${details.exception} ${details.stack}");
  };
  PlatformDispatcher.instance.onError = (error, stack) {
    print("Unhandled Flutter Platform error: $error $stack");
    return true;
  };

  runApp(const MainWidget());
}

class MainWidget extends StatefulWidget {
  const MainWidget({super.key});

  @override
  State createState() => MainWidgetState();
}

class Person {
  Person(this.name, this.age);

  final String name;
  final int age;
}

enum ColumnId { name, age }

class MainWidgetState extends State<MainWidget> {
  late DaviModel<Person> _model;
  bool _loading = true;

  @override
  void initState() {
    super.initState();
    _model = DaviModel<Person>(columns: [
      DaviColumn(id: ColumnId.name, name: 'Name', stringValue: (row) => row.name),
      DaviColumn(id: ColumnId.age, name: 'Age', intValue: (row) => row.age)
    ], onSort: _onSort, ignoreSort: true);
    loadData();
  }

  void loadData([DaviColumn<Person>? column]) {
    Future<List<Person>>.delayed(const Duration(seconds: 1), () {
      List<Person> rows = [
        Person('Linda', 33),
        Person('Pamela', 22),
        Person('Steven', 21),
        Person('James', 37),
        Person('Amanda', 43),
        Person('Cadu', 35)
      ];
      if (column != null) {
        final TableSortOrder order = column.order!;
        rows.sort((a, b) {
          switch (column.id) {
            case ColumnId.name:
              return order == TableSortOrder.ascending
                  ? a.name.compareTo(b.name)
                  : b.name.compareTo(a.name);
            case ColumnId.age:
              return order == TableSortOrder.ascending
                  ? a.age.compareTo(b.age)
                  : b.age.compareTo(a.age);
          }
          return 0;
        });
      }
      return rows;
    }).then((list) {
      setState(() {
        _loading = false;
        _model.replaceRows(list);
      });
    });
  }

  void _onSort(List<DaviColumn<Person>> sortedColumns) {
    setState(() {
      _loading = true;
      _model.removeRows();
    });
    final DaviColumn<Person>? column = sortedColumns.isNotEmpty ? sortedColumns.first : null;
    loadData(column);
  }

  @override
  Widget build(BuildContext context) {
    if (_loading) {
      return const MaterialApp(
          home: Scaffold(
        body: Center(child: Text('Loading...')),
      ));
    } else {
      return MaterialApp(
          home: Scaffold(
        body: Davi(_model,
            tapToSortEnabled: !_loading,
            lastRowWidget: _loading ? const Center(child: Text('Loading...')) : null),
      ));
    }
  }
}

The above renders fine the first time, but if you click on any of the headers, which will set _loading=true and unmount the Davi, you will then get the following exception:
Once you have called dispose() on a DaviModel<Person>, it can no longer be used.
#0      ChangeNotifier.debugAssertNotDisposed.<anonymous closure> (package:flutter/src/foundation/change_notifier.dart:147:9)
#1      ChangeNotifier.debugAssertNotDisposed (package:flutter/src/foundation/change_notifier.dart:154:6)
#2      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:330:27)
#3      DaviModel._updateRows (package:davi/src/model.dart:275:7)
#4      DaviModel.replaceRows (package:davi/src/model.dart:104:5)
#5      MainWidgetState.loadData.<anonymous closure>.<anonymous closure> (package:qfiler/test4.dart:79:16)
#6      State.setState (package:flutter/src/widgets/framework.dart:1114:30)
#7      MainWidgetState.loadData.<anonymous closure> (package:qfiler/test4.dart:77:7)

I ran into this issue previously as well, but up until the "external sort" feature I was able to work around it by re-creating the model on each build call. The "external sort" feature doesn't work if the model is recreated on each render (seems like the model keeps _sortedColumns as state which is lost if the model is recreated), so I had to move the model to the widget's state.
I tried the lastRowWidget approach, but it only allows the loader to be rendered as the last row, whereas what I want to achieve is a full screen loader that will be rendered instead of the table, or have the table expand to take up all the available space but allow me to render a custom widget inside that space. To be fully accurate - I want to render the table header and have a custom loader take up the rest of the available space on screen.
What I've been doing so far for loading is rendering a Column with an empty Davi so it displays the table header, and below it as a ListView a bunch of skeleton shimmering rows with the height manually set to the height of Davi rows (See screenshot below). So if Davi supported this natively, that'd be nice. But I'd also want to be able to display a centered full-screen error state in case of error, so the overall most flexible solution would be to allow the model to be re-used somehow after being disposed. If that doesn't make sense, what other options do I have to achieve what I'm trying?

I suppose the root cause is that disposing of Davi also disposes of the model: https://github.com/caduandrade/davi_flutter/blob/main/lib/src/davi.dart#L108
Maybe this shouldn't happen if the model is managed outside of the Davi?

The model disposal in the Widget is very weird. Does not make sense. I'll take a look at it.

It shouldn't be a dispose (of course), it should just remove the listener. Fixing...
Thanks for pointing out the problem. It was accurate.

I noticed that Davi is changing the scroll offset to zero if it receives a new instance of the model. Maybe it should keep the same offset as well. Any other problems just let me know.
Thanks for reporting the bug.

Thanks for doing a great job on handling these :)

Works well now 🥇


Bumping the version as M92 has been bumped up

Bumping up the Task Agent version

approved

approved. create a new pr to bump up the version in master as well

make sure the tasks are exactly the same in both branches if we are keeping the version the same


Include a library of default commands

Being able to require('yuuko/commands/help') to get a reliable default help command would make things much easier for newcomers.
This will also involve restructuring things slightly so the compiled JS files live in the root of the project. That way you won't need /dist in the require path or whatever. Not a huge deal but it's something.

Functionally this works in v1, closing as I'll probably end up exporting them as properties of the module rather than require('yuuko/.../stuff').


Loadbalancing principle with Ribbon

Hi,
I have a quick question about the way Ribbon chooses a server.
Assuming I have two services which can be selected by Ribbon.
How Ribbon knows which service to select? Does it check both services in order to know which one is less overloaded? If yes, does it call /metrics and which metric is taken into account?
Thanks a lot for your answer

I think I have found. It depends on the chosen implementation of IRule, right?

That is correct. See https://github.com/Netflix/ribbon/wiki/Working-with-load-balancers#common-rules
The default is a zone aware load balancer that does round robin.

Please don't cross post. We watch both places https://stackoverflow.com/questions/44177345/loadbalancing-with-ribbon

Ok, sorry.

@oterrien stack overflow is better for questions.


Need to upgrade ballerina version in IDP and Config Deployer services

Problem
Need to upgrade ballerina version in IDP and Config Deployer services
Solution
Need to upgrade ballerina version in IDP and Config Deployer services
Affected Component
None
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response

fixed by https://github.com/wso2/apk/pull/2585


Replace pickle with pyyaml

snyk complains about pickle and requires a replacement

it was decided to ignore pickle warning from snyk
pyyaml decreases the speed of uploading points by ~60 times and increases db folder size by ~2 times


Added Original HKQuantity as it was required to Convert unit

Status
READY
Migrations
YES
Description
When converting unit, we require HKQuantitySample, since the codable QuantitySample converted metadata to [String: String], when we try to create HKQuantitySample with QuantitySample it crashes as it expects some of the values of metadata to be in actual type instead of String.
Related PRs
List related PRs against other branches:
branch	DEV
other_pr_production	link
other_pr_master	link
Todos
Tests
Documentation
Deploy Notes
Notes regarding deployment the contained body of work. These should note any db migrations, etc.
Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
git pull --prune
git checkout <feature_branch>
Impacted Areas in Application
Small description about what will be changed in the app if this PR will be merged
List general components of the application that this PR will affect:
The direct changes inside the app made by this PR

Please sorry for a really long time of this PR pemding.
I doubt we need this code, since the idea was to get away from orignal HK in order to provide the Codable extensions. Adding original HKQuantitySample as a property of the Codable struct does not fullfill the library's goal.
If it would possible though to provide Codable extensions to HKObject, the half of the code in this library could be deleted  :)


Date, Time, Datetime-local and Month inputs : incorrect line-height on Edge

On Microsoft Edge browser, Date, Time, Datetime-local and Month inputs types contents are not displayed properly (with an incorrect line-height so the text is not vertically centered).
Demo here: http://www.bootply.com/ynEsXe67Hg
On Edge line-height is overridden by: (since it should not)
https://github.com/twbs/bootstrap/blob/master/dist/css/bootstrap.css#L2608
@media screen and (-webkit-min-device-pixel-ratio: 0) {
  input[type="date"].form-control,
  input[type="time"].form-control,
  input[type="datetime-local"].form-control,
  input[type="month"].form-control {
    line-height: 34px;
  }
  input[type="date"].input-sm,
  input[type="time"].input-sm,
  input[type="datetime-local"].input-sm,
  input[type="month"].input-sm,
  .input-group-sm input[type="date"],
  .input-group-sm input[type="time"],
  .input-group-sm input[type="datetime-local"],
  .input-group-sm input[type="month"] {
    line-height: 30px;
  }
  input[type="date"].input-lg,
  input[type="time"].input-lg,
  input[type="datetime-local"].input-lg,
  input[type="month"].input-lg,
  .input-group-lg input[type="date"],
  .input-group-lg input[type="time"],
  .input-group-lg input[type="datetime-local"],
  .input-group-lg input[type="month"] {
    line-height: 46px;
  }
}

Hi @Seb33300!
You appear to have posted a live example (http://s.bootply.com/render/ynEsXe67Hg), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

line 5, column 9 thru column 30: A document must not include both a meta element with an http-equiv attribute whose value is content-type, and a meta element with a charset attribute.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

This issue seems to only exists in Bootstrap v3.3.x, for which support was dropped. In v4.0.0beta4 this issue doesnt exist.

This problem (in the current version v3.3.7!) also happens on iOS and Android.


Missing features:

[ ] Can't use another VerbalExpression as an argument in a VerbalExpression Chain. This is a common use-case explained in the original JS version of the library.
[ ] No .or method

Fixed both in #5


Fixed spelling errors in readme

Hello. Was bored and just looking around for projects to contribute to, so I corrected multiple spelling/grammatical errors in your readme file.

Coverage remained the same at 33.191% when pulling 82423fd10a22f2fff1a7a564612a63b369619ce9 on dlwebdev:master into 19465561e3ab960af868689a5e3a1e397f336056 on luruke:master.

This is great!
Thank you.
Any chance you can review the documentation on the website as well?
That would be awesome 🤓

Would be happy to. Will open a new pull request for anything I find.


Remove version: StrawberryMusicPlayer.Strawberry version 1.0.22

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/strawberrymusicplayer/strawberry/releases/download/1.0.22/StrawberrySetup-1.0.22-msvc-x64.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 911)


[SP-3423][PDI-15801]  [Check if column exists in a table] Multiple er…

…rors in step result and logs

Fix step execution logic
Unit test

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/job/entries/columnsexist/JobEntryColumnsExist.java
  engine/test-src/org/pentaho/di/job/entries/columnsexist/JobEntryColumnsExistTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.job.entries.columnsexist.JobEntryColumnsExist

Branch Change:  + 41.30%
Complexity Change:  + 31.11%
Instruction Change:  + 30.66%
Line Change:  + 40.00%
Method Change:  + 31.82%

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.95%

org.pentaho.di.job.Job

Complexity Change:  + .38%
Instruction Change:  + .24%
Line Change:  + .42%
Method Change:  + .72%

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change:  + 1.28%
Complexity Change:  + .79%
Instruction Change:  + .04%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 1.18%
Complexity Change:  + 1.35%

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -.07%:small_red_triangle_down:


Is it possible to have text on button

Instead of using an image as the icon for the button, is there a way to use text instead? I am wanting to have the names of cities displayed on the maps.
Thanks

Had an issue with styling but now I have fixed it. Got text working.

how did you do that? please help me!

for reference, it's in the examples:
L.easyButton( 'Disable me', function(){
  this.disable();
}).addTo(map);


Removed stop kwarg from I2CDevice.reads, moved to write_then_readinto

Fixes #5 by moving to the newer I2CDevice model of using write_then_readinto for reading registers into buffers.

For good measure I fixed some typos and added type hints and some typing fixes for booleans in 2f852bc and 8caa5a7.

Just realized that @imandel submitted #6 with a prospective fix for this issue at the beginning of the year. Definitely take a look at that PR while reviewing this one.
I think the shift to write_then_readinto is more comprehensive than just removing the kwarg but I'll be happy to close this PR if the approach in that PR is preferred.

@fourstix Happy to help! Thanks for taking a look and getting it merged in and, of course, taking the time to maintain this stuff. <3


embedded-plots crate

Hi!
I have recently published plotting lib based on your crate. I would be grateful if you could review it since this is my first crate ever.
If you'll find it any good, please also consider adding link to it into your docs.
embedded-plots

That's awesome! Thanks for sharing :). I've added it to the list in the README in #559

Great, thanks!


Error when launching the app from teams

Description
When everything is set up and you try to start the Request a Team app from a test user, the error message from the screenshot always appears. Another user was used and the app was uploaded again. Unfortunately, always the same error.
Steps to reproduce

Open Teams
Start the Request a Team app in a Channel

Expected results
Actually, the app should load all things and not show any error.
Actual Results

Solution component
Power App
Operating system (environment)
Windows
Additional Info
No response

Hello @BennyFeuch87
May I suggest having a look at [https://github.com/OfficeDev/microsoft-teams-apps-requestateam/issues/336](Issue 336)?
One of the errors I see on your screenshot has been discussed about there. The problem is Caching. You have to go to your app, go to Information and delete all the older versions but the latest. There is also a "Live" Tag on one of the versions, I don't know how this works exactly but it may be indeed a cache-and-wait type of problem.

Thank you. :-) It works:


How to package integration to deploy it into a private k8s cluster without internet connection

Newbie here
Is it possible to package Camel K integration as a self-sufficient container image?
If not, what is the package strategy for Camel K integration?
Given that the k8s cluster is private, what do we need to pre-package on the private k8s cluster for running the integration?
thank you

I got a bit ahead, but have more questions on kamel local
I used kamel local build basic.java --image xxxx/basic-image
which creates an image xxxx/basic-image on my local development machine.
Then move the image to the private k8s cluster and run kamel local run --image xxxx/basic-image
and it executed: docker run --network=host -t xxxx/basic-image:latest and started to output logs
{"timestamp":"2021-11-08T23:44:44.255Z","sequence":95,"loggerClassName":"org.slf4j.impl.Slf4jLogger","loggerName":"org.apache.camel.k.Runtime","level":"INFO","message":"Apache Camel K Runtime 1.9.1","threadName":"main","threadId":1,"mdc":{},"ndc":"","hostName":"docker-desktop","processName":"io.quarkus.bootstrap.runner.QuarkusEntryPoint","processId":9}
{"timestamp":"2021-11-08T23:44:44.281Z","sequence":96,"loggerClassName":"org.jboss.logging.Logger","loggerName":"org.apache.camel.quarkus.core.CamelBootstrapRecorder","level":"INFO","message":"Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime","threadName":"main","threadId":1,"mdc":{},"ndc":"","hostName":"docker-desktop","processName":"io.quarkus.bootstrap.runner.QuarkusEntryPoint","processId":9}
{"timestamp":"2021-11-08T23:44:44.3Z","sequence":97,"loggerClassName"

Questions:
What is the usage of the base image (ex. xxxx/integration-base-image) created from
kamel local build --base-image --container-registry xxxx ?
Can I use this image to run the integration-directory created from kamel local build basic.java --integration-directory ~/test/int ?
Tried to run kamel local run --containerize --image xxxx/integration-base-image --integration-directory ~/test/int
Got the following error
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Executing: docker run --network=host -t xxxx/integration-base-image:latest
Exception in thread "main" java.nio.file.NoSuchFileException: /quarkus/quarkus-application.dat
	at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
	at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:219)
	at java.base/java.nio.file.Files.newByteChannel(Files.java:371)
	at java.base/java.nio.file.Files.newByteChannel(Files.java:422)
	at java.base/java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:420)
	at java.base/java.nio.file.Files.newInputStream(Files.java:156)
	at io.quarkus.bootstrap.runner.QuarkusEntryPoint.doRun(QuarkusEntryPoint.java:41)
	at io.quarkus.bootstrap.runner.QuarkusEntryPoint.main(QuarkusEntryPoint.java:25)
integration image did not run successfully: exit status 1

Is it feasible to pre-package one base image? and use it to run/load different integrations from their own integration-directory

Not sure if the kamel local is the best strategy to adopt. It involves too many low level details that are coming for free using an operator. I think it would be better if you have a connected environment where installing an operator and leverage the IntegrationKit as a way to package your self-contained resources. Then you can move those kits into the private cluster and be able to reuse there.

@squakez really helpful suggestion.
I have revised the workflow
kamel kit create kit_name -d denpency
This created an image without tag
docker_registry/camel-k-kit_name@sha256:3a0cb7ddb5917df8e9a0f16e7ebac746777bd02257c0078e6919db658375f229
Is there a way to give a tag when creating the kit?

Hi @elainhelen, I don't think we have that option available now. The images created have a unique autogenerated ID instead. I understand that in your situation it may help in order to simplify versioning. I don't know the impact of including any additional property (ie, a tag) when we create the IntegrationKit, so, I suggest you to create a new issue describing the feature requested. Of course, feel free to have a look to the code and contribute to the analysis/development as well.
Let me know if there is anything else I can help you with.

@squakez I haven't done a lot on kamelet.
With kamelet in the picture, what is the shareable artifact we can build locally and then load into a production env?
Thanks

A Kamelet is essentially a descriptor that will be somehow translated at runtime. In the context of this deployment requirement, I don't think you will need it, once you have your IntegrationKit and Integration defined.

@elainhelen if I may join in this thread, I have a question with regards to how you manage to perform kamel local build xxx.java as I'm too looking for a solution to a use case similar to yours.
I'm using Camel K Client 1.6.0, and when I did a kamel local build --integration-directory test Basic.java, it is returning an error without stack trace.
> kamel local build --integration-directory test Basic.java
failure while building project: exit status 1

Is there anything in particular you have to set up in advance before running the above command?

@elainhelen if I may join in this thread, I have a question with regards to how you manage to perform kamel local build xxx.java as I'm too looking for a solution to a use case similar to yours.
I'm using Camel K Client 1.6.0, and when I did a kamel local build --integration-directory test Basic.java, it is returning an error without stack trace.
> kamel local build --integration-directory test Basic.java
failure while building project: exit status 1

Is there anything in particular you have to set up in advance before running the above command?

The local is performed on your machine, so you must make sure that you have all the expected tools required by the build process, ie, maven, jdk, quarkus, ... it seems that your error happens when you try to package the application, so, likely, you don't have all the required configuration needed to run.


we need to implement zk storage

we need to have the scheduler be able to survive a failure, to-do this the storage state needs to be zk

Done in #10 and created #11 and #12 as follow-up issues to make use of the data stored.


Fix updating markers and managing popups

Lots of logic for marker updating was contained in the addMarkerWatch callback. If you didn't watch individual markers, then markers weren't getting updated properly. This used to work because the directive simply replaced markers on update, but with recent refactors, this is no longer the case. The addMarkerWatch callback has been renamed _updateMarker and made available to the marker directive. It is used to update markers in _addMarkers.
See #812 for more info about how this deals with the popup problem

Will have a look through but I'll say this before @nmccready does :)  - you need to use these commit message guidelines https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#-git-commit-guidelines in your commit messages http://stackoverflow.com/questions/179123/edit-an-incorrect-commit-message-in-git

Okay, I'm off for the weekend. Might not get to this until early next week.

@jessertaylor Thanks for merging the pull request. Now that these commits are public, I don't think I can edit the commit messages without rewriting history (commit --amend rewrites the commit id). Please correct me if I'm wrong. Sorry about this, I should have observed the contribution guidelines from the get go.

No worries, rather get the fix in. I can add a commit message in on doing the pre-release. If you have a commit msg in mind; just leave it here. I'll copy it in.

@nmccready
feat(leafletMarkersHelper, markers): Fix updating markers and managing popups
Lots of logic for marker updating was contained in the addMarkerWatch callback. If you didn't watch individual markers, then markers weren't getting updated properly. This used to work because the directive simply replaced markers on update, but with recent refactors, this is no longer the case. The addMarkerWatch watch callback is now _updateMarker and made available to the marker directive. It is used to update markers in _addMarkers. Before this commit, _addMarkers just ignored markers that already exists, now it updates.
We now use marker.popupOpen() to handle popup logic (when focus is set to true, ensure popup gets opened). When the popup event is fired, manageOpenPopup will be used to compile the popup if necessary.
Fixes #812