Install not working

Hi
after installing kubelet.keep getting error in my logs.
time="2018-10-01T15:25:05Z" level=error msg="Pod watcher connection is closed unexpectedly" namespace= node=virtual-kubelet-virtual-kubelet-windows-eastus2 operatingSystem=Windows provider=azure
[Enter feedback here]

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

ID: acfb234b-c0db-3e6a-7938-cab614d530c0
Version Independent ID: 2adff671-6ccb-d84a-f689-8b0d72b1577c
Content: Run Virtual Kubelet in an Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/virtual-kubelet.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@abhiramani-iptiq Thanks for the feedback! We are currently investigating and will update you shortly.

@abhiramani-iptiq I ran through this doc but did not run into any issues.
Are you running the commands in Azure Cloud Shell or on a local instance of CLI?

Azure Cloud Shell
Abhijit Ramani | Cloud Infrastructure DevOps Engineer | ASSISTANT VICE PRESIDENT | iptiQ Americas L&H
iptiQ Americas Inc. | 175 King Street, 10504 ARMONK, UNITED STATES (USA)
Direct: +1<PHONE_NUMBER> Fax: +1<PHONE_NUMBER> Email: Abhijit_Ramani<EMAIL_ADDRESS>From: Micah<EMAIL_ADDRESS>Sent: Monday, October 01, 2018 1:40 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Abhijit Ramani<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Install not working (#15915)
@abhiramani-iptiqhttps://github.com/abhiramani-iptiq I ran through this doc but did not run into any issues.
Are you running the commands in Azure Cloud Shell or on a local instance of CLI?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/15915#issuecomment-425996809, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Am6WsaWHqCSsWLIBL9FW6fkFzPt1xkhLks5uglN5gaJpZM4XCaCd.

@abhiramani-iptiq can you try running through the doc again? I tested it again today and still did not run into any issues.

I tried removing and reenabling. not working
Here is error: time="2018-10-03T17:17:09Z" level=error msg="Pod watcher connection is closed unexpectedly" namespace= node=virtual-kubelet-virtual-kubelet-windows-eastus2 operatingSystem=Windows provider=azure
Can you make sure if this works without "http application routing" because we are not using this feature and we are using advanced networking.
Abhijit Ramani | Cloud Infrastructure DevOps Engineer | ASSISTANT VICE PRESIDENT | iptiQ Americas L&H
iptiQ Americas Inc. | 175 King Street, 10504 ARMONK, UNITED STATES (USA)
Direct: +1<PHONE_NUMBER> Fax: +1<PHONE_NUMBER> Email: Abhijit_Ramani<EMAIL_ADDRESS>From: Micah<EMAIL_ADDRESS>Sent: Wednesday, October 03, 2018 1:25 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Abhijit Ramani<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Install not working (#15915)
@abhiramani-iptiqhttps://github.com/abhiramani-iptiq any update on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/15915#issuecomment-426723891, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Am6WsQ2I8i3L7VingoofaKPCf4R9MVIWks5uhPLlgaJpZM4XCaCd.


error while building wheel

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04.3 x64
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version:  2.0.0-rc.0
Python version: 3.7.4 x64
Installed using virtualenv? pip? conda?: N/A
Bazel version (if compiling from source): 0.26.1
GCC/Compiler version (if compiling from source):  7.4.0
CUDA/cuDNN version: 10.1/7.6.2
GPU model and memory: GTX1080Ti GDDR5x 11GB X 6

Describe the problem
error while building wheels
Provide the exact sequence of commands / steps that you executed before running into the problem
bazel-bin/tensorflow/tools/pip_package/build_pip_package ~/tensorflow_pkgs/

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Traceback (most recent call last):
  File "setup.py", line 308, in <module>
    keywords='tensorflow tensor machine learning',
  File "/home/wmind/anaconda3/lib/python3.7/site-packages/setuptools/__init__.py", line 145, in setup
    return distutils.core.setup(**attrs)
  File "/home/wmind/anaconda3/lib/python3.7/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/home/wmind/anaconda3/lib/python3.7/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/home/wmind/anaconda3/lib/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/home/wmind/anaconda3/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 230, in run
    impl_tag, abi_tag, plat_tag = self.get_tag()
  File "/home/wmind/anaconda3/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 179, in get_tag
    assert tag == supported_tags[0], "%s != %s" % (tag, supported_tags[0])
AssertionError: ('cp37', 'cp@pyvernodots@m', 'linux_x86_64') != ('cp37', 'cp@PYVERNODOTS@m', 'linux_x86_64')

I downgraded python to 3.7.3 and then no problem.
looks like an issue with python 3.7.4

fixed with conda python update and tensorflow sh update


Push authentication causes Pop ups to appear twice

There are some pop up windows about untracked branches that show up, but the authentication makes them show up twice: once before and once after

Fixed. I chose not to spin off a separate thread for the prepare stages of the operation. In principle, this might cause ugly slowdowns of the application thread, but this appears not to be a problem in practice. Perhaps if someone adds 1000 branches before pushing, this might be a problem. We an always revisit this if this is an issue.


Translate login prompt

MOTD edition possible, but how to change "Username", "Password" strings at login prompt? Maybe a translation tool could be handy?

Dupe of #41


TimeSeriesAnomaly-MultiVendor_DataExfiltration.yaml

How can I determine what my baseline threshold should be when utilizing the query 'Time series anomaly for data size transferred to public internet'?
I'm confused about a few things, which is making me unsure.
Am I correct in understanding that the query is looking at data transfers to the public Internet per port?
Am I also correct in seeing the results as being in total bytes out per port versus the baseline, despite any resulting hits stating 'TotalBytesSentinMB'? Comparing to Firewall traffic logs, it appears impossible for the total bytes out to be measuring in MB, otherwise I'd be seeing a lot higher amount of traffic on the firewall.
And does changing the amount of days of history to look up affect the baseline in any manner?
Anything else I should know about "right-sizing" the query for my tenant?
Much thanks for any help/input!

Thank you! A very useful query for threat hunting indeed!
--
Mark Bell
[Signature of Mark E. Bell.]
IT Administrator (CompTIA SIS, ITOS, A+, Network+ & Security+ Certified)
Journeys in Community Living
1130 Haley Rd.
Murfreesboro, TN 37129
615-890-4389, ext. 45 (ofc)
615-295-3046 (cell)
www.journeystn.orghttp://www.journeystn.org/
www.fb.com/journeysincommunityhttp://www.fb.com/journeysincommunity
www.twitter.com/journeystnhttp://www.twitter.com/journeystn

From: @.*** @.>
Sent: Friday, November 29, 2024 5:28 AM
To: Azure/Azure-Sentinel @.>
Cc: Mark Bell @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] TimeSeriesAnomaly-MultiVendor_DataExfiltration.yaml (Issue #11359)
[EXTERNAL SENDER]
Handle with care! DO NOT open attachments or click links from unknown senders or unexpected email! This email originated from outside the journeystn.org domain!

JICL Helpdeskhttps://jicladmin.org/

Hi @mbell85https://github.com/mbell85 , Yes, the query looks at data transfers to the public internet per port and changing the number of days of history to longer provides more comprehensive baseline.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/issues/11359#issuecomment-2507622869, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKN3WZC34GNA5GCY3O3QBWT2DBFW3AVCNFSM6AAAAABQXWJJBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGYZDEOBWHE.
You are receiving this because you were mentioned.Message ID: @.***>
NOTICE: This email may contain confidential (including but not limited to) HIPAA-protected and/or privileged information intended only for specific, predetermined recipients. If you are not the intended recipient, you are hereby notified that any review, further dissemination, distribution or duplication of this communication IS STRICTLY FORBIDDEN. Please delete and/or destroy all copies of this message after notifying JICL IT of the error by reply @.***> or by calling<PHONE_NUMBER>.

Hi @mbell85 , Glad you found the query useful! Do you have any further questions or concerns regarding the issue?

Hi @mbell85 , Do you have any further questions or concerns regarding the issue?

Hi @mbell85 , Do you have any further questions or concerns regarding the issue?

Hi @mbell85 , since we have not received a response in the last 5 days, we are closing your issue as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time.
Thank you for your co-operation.

No. Thank you!
--
Mark Bell
[Signature of Mark E. Bell.]
IT Administrator (CompTIA SAP, SIS, ITOS, CySA+, Security+, Network+, A+ Certified)
Journeys in Community Living
1130 Haley Rd.
Murfreesboro, TN 37129
615-890-4389, ext. 45 (ofc)
615-295-3046 (cell)
www.journeystn.orghttp://www.journeystn.org/
www.fb.com/journeysincommunityhttp://www.fb.com/journeysincommunity
www.twitter.com/journeystnhttp://www.twitter.com/journeystn

From: @.*** @.>
Sent: Sunday, December 8, 2024 10:03 PM
To: Azure/Azure-Sentinel @.>
Cc: Mark Bell @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] TimeSeriesAnomaly-MultiVendor_DataExfiltration.yaml (Issue #11359)
[EXTERNAL SENDER]
Handle with care! DO NOT open attachments or click links from unknown senders or unexpected email! This email originated from outside the journeystn.org domain!

JICL Helpdeskhttps://jicladmin.org/

Hi @mbell85https://github.com/mbell85 , Do you have any further questions or concerns regarding the issue?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/issues/11359#issuecomment-2526821996, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKN3WZBPGL2CVSX5ESXGZE32EUJCZAVCNFSM6AAAAABQXWJJBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWHAZDCOJZGY.
You are receiving this because you were mentioned.Message ID: @.***>
NOTICE: This email may contain confidential (including but not limited to) HIPAA-protected and/or privileged information intended only for specific, predetermined recipients. If you are not the intended recipient, you are hereby notified that any review, further dissemination, distribution or duplication of this communication IS STRICTLY FORBIDDEN. Please delete and/or destroy all copies of this message after notifying JICL IT of the error by reply @.***> or by calling<PHONE_NUMBER>.


First class support for Promises

The pipeline operator could work like an infix version of R.pipeP, allowing asynchronous pipelines to have (nearly?) the same syntax as synchronous ones:
fs.readFile('./index.txt')
|> .split('\n')
    .map(fs.readFile)
|> Promise.all
|> .join("\n")
|> process.stdout.write
|> .catch(process.stderr.write)

So far, with things like async functions and async iteration the fact that it's async is explicit (usually with the keyword). I don't think it makes sense to introduce an operator that's sometimes async and sometiems sync since it doesn't follow the duality seen in other parts of the language.

@RangerMauve is right, the operator should always be synchronous. However, I think it would be interesting to add syntactical support for usage with the keyword yield:
// Assume fs.readFile is an `async` function
async function runTask () {
  './index.txt'
    |> yield fs.readFile
    |> file => file
       .split('\n')
       .map(fs.readFile)
    |> yield Promise.all
    |> all => all.join("\n")
    |> _ => console.log(_)
}

Wow, so it turns out this syntax already works as expected (at least in my babel plugin). No need to change anything; it's already supported :smile:

^ Awesome!

In my proposal, the operator is synchronous; if any of the functions return a Promise, the final value will always be a Promise, ie, a value returned synchronously (unless an await is used).  The point of my suggestion is to reduce boilerplate and mental overhead when dealing with asynchrony.
The await alternative has more boilerplate and more mental overhead than a regular Promises version:
fs.readFile('./index.txt')
.then(file=> file.split('\n').map(fs.readFile))
.then(Promise.all)
.then(files=>files.join('\n'))
.then(process.stdout.write)
.catch(process.stderr.write)

@kwijibo What's the cue that lets people know they're dealing with an async pipeline? Using await to wait for a promise to complete is definitely not mental overhead because it's obvious what's going on.

Hi @RangerMauve. Your concern is that asynchrony should be explicit, as with async/await, right? I don't think that's applicable here because the proposal is that
p = x |> f |> g
be equivalent to  p = R.pipeP(f,g)(x),
not p = g(await f(x))
await resolves the Promise to a final value asynchronously, R.pipeP composes a function that returns a Promise synchronously.
Supporting promises would mean something like, decorating each function in the pipeline with:
const acceptPromise = func => arg =>  isPromise(arg)? arg.then(func) : func(arg)

before composing them.
My understanding of |> is that it's about composing the functions to the right of the first |>, then passing the value to the left of the first |> to the resulting function
So to answer your question "what's the cue that lets people know they're dealing with an async pipeline?": they're not. They're dealing with a function that may return a Promise, or a String, or a Boolean, or an Array, or ...
This is exactly the same as any other javascript function; the only hint to what the return value is, is how it is used subsequently.
In the case of my example, the clues are the .catch at the end, and perhaps you just know that the readFile function returns a Promise.

I see where you're coming from, but I don't think it makes sense unless it was always equivalent to R.pipeP(f,g)(x). It seems like currently the pipeline operator is more equivalent to R.pipe(f,g)(x). Magically choosing between on or the other based on whether promises are detected somewhere in the chain doesn't seem like an intuitive way to go. It might make sense to wait until the non-promise version of the pipeline operator gets accepted, and then propose an async pipeline operator which deals with promises by default


Add my profile - Krish Jaiswal

Hey, I have added my Twitter Profile to this amazing project!

Why did you closed the PR?


DDC Volume doesn't work on Samsung Display M7

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Read through the Monitor-Troubleshooting Wiki
[X] Updated MonitorControl to the latest version (if applicable)

Describe the issue
I can't control the volume of the monitor Samsung M7 4K UHD Smart Monitor
Expected behavior
its a new monitor and also I use USB C to connect to the monitor, but I can't control the volume
Anything else?
No response
Environment Information (please complete the following information)
- macOS version:
macOS Monterey 12.2.1
- Mac model:
MacBook Pro (16", 2021)
- MonitorControl version:
Versione 4.0.2 Build 6965
- Monitor(s):
Samsung M7 Monitor
- Monitor Cable(s)/Connection(s):
MacBook Pro -> Usb type C -> Samsung M7 4K UHD Smart Monitor
- Apple Silicon/M1 (yes or no):
Yes

Does DDC brightness control work? If so then it is probably a display firmware issue if that does not work either then it might be something else. You could try alternate apps like m1ddc or Lunar and see if those can control the volume. If not, then probably there is nothing to do about it.


Capturing not working with addEventHard

attachEvent only takes two parameters (event name, function).
In commit 0c6a5a9fefb169d21a2ad80401bd2b1ff323b642 capturing was added as a third parameter to attachEvent and I believe it has no effect. I don't have a windows computer to test this in Internet Explorer, but I think setCapture is the solution.

Fixed in 1.3.0


chore: add core module

part of MBL-243
Changes

Added core module
Updated gradle scripts and CI workflows

Compare SDK binary size report is failing because the size of core module is currently in KBs (908.4KB). This is okay for this PR, as we do not need to support KB measurements. The size will increase to MBs once we add a few more classes, and the task should then work fine.

@Shahroz16 Yes, we could reuse base, but I avoided doing so for following reasons:

I believe core naming convention is more commonly used
I wanted to avoid the ripple effects that base module might cause as is it currently used by other modules
I'm still unsure whether we'll still need a lightweight separate base or just the core module eventually. So, I avoided making this decision too early to allow enough time to consider our options.


Template Fix For Futures- Golf (PGA, Euro Tour, LPGA)

retire old templates and add title property to template source
Use this title in the market list cards for SB
PGA
PGA: Which golfer will win the [Year] [Event]?
Header: PGA [Year] [Event]
Title: Who will win
PGA: Which team will win the [Year] Presidents Cup?
Header: PGA [Year] Presidents Cup
Title: Who will win
Euro
Euro Tour: Which golfer will win the [Year] [Event]?
Header: Euro Tour [Year] [Event]
Title: Who will win
Euro Tour: Which golf team will win the [Year] Ryders Cup?
Header: Euro Tour [Year] Ryders Cup
Title: Who will win
LPGA
LPGA: Which golfer will win the [Year] [Event]?
Header: LPGA [Year] [Event]
Title: Who will win

already updated: PGA: Which team will win the [Year] Presidents Cup?


context.exit is not called if with block returns

Please transcrypt the following code:
class Context:
    def __enter__(self):
        print("enter")

    def __exit__(self, exc_type, exc_val, exc_tb):
        print("exit")
        return False

def main():
    with Context():
        print("exit is not called")
        return

document.addEventListener('DOMContentLoaded', main)

The main function ist transcripted to
export var main = function () {
	var __withid0__ = Context ();
	try {
		__withid0__.__enter__ ();
		print ('exit is not called');
		return ;
		__withid0__.__exit__ ();
	}
	catch (__except0__) {
		if (! (__withid0__.__exit__ (__except0__.name, __except0__, __except0__.stack))) {
			throw __except0__;
		}
	}
};

As you can see the return statement is generated before calling exit.

Funny story, this kind of stuff is exactly why I coded with-as-a-functuon!

Specifically, you'll want to grab the manual_no_traceback.py file, either from GitHub or the sdist package on PyPI and save it as with_.py in your Transcrypt-using Python project.

Of course, using my with_ requires you to refactor your code a bit, so in this particular example it isn't much better than what you could do without with_.
Because both of these work, so it's arguably more about which you find nicer:
def main():
    should_return = False
    with Context():
        print("exit is called")
        should_return = True
    if should_return:
        return

from with_ import with_

def main():
    def _do_stuff(parameter_unused_in_this_case):
        print("exit is called")
    if with_(Context(), _do_stuff):
        return

Then again, I don't know what other broken edge cases that first one may have, but I am confident that the second one will be rock solid and exact to PEP-343 specification, at least as much as possible within Python without changing the underlying Python implementation's runtime, because I put an unhealthy amount of time and care into making sure of it.

More importantly, @JdeH and other maintainers are 100% welcomed to reuse any of my with_ implementation in the code they transpile with statements to!

Some notes I started back in June and just got around to cleaning up:
So the implementation of my with_ that works on Pythons without a correct native with is:
def with_(manager, action):
    exit_ = type(manager).__exit__
    value = type(manager).__enter__(manager)
    try:
        result = action(value)
    except _BaseException as exception:
        if not exit_(manager, type(exception), exception, None):
            raise
        return None
    exit_(manager, None, None, None)
    return result

Notice that this is different from the PEP-343 specification.
It can afford to be different because making it a function frees you from worrying about break and continue. And it needs to use less language features because avoids certain problems (including a problem in Transcrypt's implementation of either try-finally or try-else - maybe that's fixed by now though).
However it becomes incomplete if you want to substitute arbitrary code blocks into it, because blocks can jump out of the structure of a with block and the block around it, by using return, break, continue, yield, and yield from (and technically await, kinda).
Now one way to handle all those control statements is to just implement all of PEP-343 in JavaScript. This would require moving closer to the implementation in the PEP and further from that implementation of with_ above.
But one simpler way I wanted to think through: handle just the easy ones (return, break, and continue) by wrapping the with_ that I wrote.
First, the transpiler can define a few unique return values per with block:
const __withid0_done__ = Object.create(null)
const __withid0_break__ = Object.create(null)
const __withid0_continue__ = Object.create(null)
const __withid0_return__ = Object.create(null)

// For greater backwards compatibility, use `var` and
// `{}` instead of `const` and `Object.create(null)`.

Then the transpiler can

wrap the with block in a function closure named for example __withid0_closure__,
replace every

break with return [__withid0_break__, null]
continue with return [__withid0_continue__, null],
return with return [__withid0_return__, null], and
return ... with return [__withid0_return__, ...],

replace every instance of what the context manager gives add a return [__withid0_done__, null] at the end of the closure.

Now the with itself can be transpiled into:
const __withid0_result__ = with_(__withid0__, __withid0_closure__)
if (__withid0_result__[0] === __withid0_break__)
    break
else if(__withid0_result__[0] === __withid0_continue__)
    continue
else if(__withid0_result__[0] === __withid0_return__)
    return __withid0_result__[1]

For yield and yield from, we would have to use the iterable and iterator protocol, since yielding can move data bidirectionally. In with-as-a-function I held off on supporting generators inside with because I didn't have a great vision for what that looks like, short of manually implementing yield from.
await is basically a yield from in Python, but an entirely separate thing in JavaScript, and I haven't thought much yet about what that looks like.
Having thought this through, I personally don't like not having a good plan for implementing those three control flow constructs, so I think it's worth trying to implement PEP-343 properly and fully in JavaScript, not "as a function" like I did but the more intuitive way of just pasting the with body into the middle of it, and then deciding based on the result of that effort.
But if people are happy with just supporting break, continue, and return, then I think just transpiling my with_ function and then transpiling each with statement as described in this post is a robust solution.

I figured out how to extend my workaround to yield and yield from.

Write a iterator variant of with_ which wraps iteration on an iterable, use that "iwith"when the `with` body has yields.
def with_(manager, action):
    exit_ = type(manager).__exit__
    value = type(manager).__enter__(manager)
    try:
        result = (yield from action(value))
    except _BaseException as exception:
        if not exit_(manager, type(exception), exception, None):
            raise
        return None
    exit_(manager, None, None, None)
    return result

(Normally I am against naming things with cryptic single-letter abbreviations, but the use of i prefix to indicate the iterator version of something has precedent in Python's standard library - off the top of my head, at least islice from itertools.)
For clarity, here's what the with_ and iwith are implementing:
def with_(manager, action):
    with manager as value:
        return action(value)
    return None

def iwith(manager, action):
    with manager as value:
        return (yield from action(value))
    return None

Extremely simple, all that other code was just to manually reimplement the with statement behavior in a portable way.
So we add in iwith, you can also rewrite any with statement that features yield and yield from keywords.
Here's a comprehensive example:
def a_generator(foo, bar):
    while foo:
        with AContextManager(foo, 'whatever') as context:
            qux = a_function(context)
            if qux < 0:
                continue
            elif qux == 0:
                return "a string for some reason"
            foo = foo.update(qux)
            for x in an_iterator():
                if x > 20:
                    continue
                elif qux + x < 40:
                    break
            if foo < 0:
                break
            yield foo
            yield from bar
        logger.debug("this loop's foo: %r", foo)
    logger.debug("final qux: %r", qux)
    return qux

This example includes the following things in the with block:

yield from
yield
return
break (for a loop outside the with)
continue (for a loop outside the with)
break (for a loop inside the with)
continue (for a loop inside the with)
values of foo and bar from outside the with block  are used
use of the context manager's context value
values of foo and qux are set in a way visible outside the with block

So here's one way we could rewrite it with iwait:
def a_generator(foo, bar):
    with_continue = object()
    with_break = object()
    with_return = object()
    with_done = object()
    def with_body(context):
        nonlocal foo
        nonlocal qux
        qux = a_function(context)
        if qux < 0:
            return with_continue, None
        elif qux == 0:
            return with_return, "a string for some reason"
        for x in an_iterator():
            if x > 20:
                continue
            elif qux + x < 40:
                break
        foo = foo.update(qux)
        if foo < 0:
            return with_break, None
        yield foo
        yield from bar
        return with_done, None

    while foo:
        with_control, with_return_value = (
            yield from iwith(AContextManager(foo, 'whatever'), with_body)
        )
        if with_control is with_break:
            break
        elif with_control is with_continue:
            continue
        elif with_control is with_return:
            return with_return_value
        assert with_control is with_done
    logger.debug("final qux: %r", qux)
    return qux

Though one downside I realized about "fixing" with by building on top of my with-as-a-function implementations... The transpiler would need to do a little bit of bookkeeping as it parses every with statement:

replace break or continue? need to know if it is inside a loop nested inside that with.
replace return? need to know if it inside a function definition nested within that with.
use iwith instead of with_? need to first find yield or yield from in the with body, and need to know if those are inside a nested function definition.

That leaves just await, async with, and async for (unless I'm missing something else)
If one of those occurs in a with block, we'd need yetmore with_ variants, which are themselves async, but I think the solution shape is the same.
The more annoying thing is the amount of permutations that are needed - both awith and aiwith variants, and each of the action, iterator and context manager could be sync or async. Since each of those variations needs a syntactical difference, if you wanted to handle it in one function, you'd need to branch on various type checks.
But in principle, the interface could require all-async things, for both manager and action and the iterator to be async, and if people need to use sync stuff in them, you can always wrap a sync thing in an async thing - still blocking, but now compatible with async code paths.

I would fix the code generation like this:
	var __withid0__ = Context ();
        var __withid0_threw__ = false;
	try {
		__withid0__.__enter__ ();
		// with body
	}
	catch (__except0__) {
                __withid0_threw__ = true;
		if (! (__withid0__.__exit__ (__except0__.name, __except0__, __except0__.stack))) {
			throw __except0__;
		}
	}
        finally {
                if (! __withid0_threw__) {
                        __withid0__.__exit__ ();
                }
        }


sql: more EXPLAIN improvements

PR: https://github.com/cockroachdb/cockroach/pull/53003
From release notes:

Removed some unnecessary EXPLAIN fields, and relegated others to the VERBOSE variant. [#53003][#53003] {% comment %}doc{% endcomment %}

Close in favor of https://github.com/cockroachdb/docs/issues/8310


Update set_up_the_provisioner.md

Description
Fixed broken links

Karpenter has been updated to 0.16 recently, looks like link are ok now


Macros not importing

I'm having an issue importing macros into GSE 2.1.01.  I was trying to import a new Outlaw Rogue macro from WoW Lazy Macros.  GSE said the import was successful, and I was able to create an icon, put it on my bar, etc.  However, the macro itself wasn't working at all.  I figured I'd start over, deleted the macro in question, but every time I try to import a macro, regardless of class, after getting the pop up that tells me the import was successful, the macro does not appear in my Sequence Viewer.  I have received no error messages or anything.

sounds like the macro you tried to import has corrupted the GSE.lua file.  Does it report anything about a macro not being loaded when you login?


drawProjection import from node package failing

I'm trying to import drawProjection into my project using the npm install version 0.15.3
 ` import { drawProjection } from "replicad";`

drawProjection doesn't seem to exist in this version, I can't find it in my node package. Any idea of what might be happening or what I'm doing wrong?

We installed it with
 npm i replicad

Hi! Circling back to this. I figured out that for some reason not all the packages were being updated to the latest npm version on my project but I was finally able to force an update and drawProjection is importing now. Sorry for the trouble ! :)


ADD does not support FTP URLs

Hi,
I would like to use the ADD command in a Dockerfile with an FTP url, but it doesn't appear to work.
My Dockerfile has this line in it:
ADD ftp://ftp.stat.math.ethz.ch/Software/R/R-devel.tar.gz /tmp/R-source/

And when I attempt to build it, I get:
Step 5 : ADD ftp://ftp.stat.math.ethz.ch/Software/R/R-devel.tar.gz /tmp/R-source/

2014/11/24 10:49:46 ftp://ftp.stat.math.ethz.ch/Software/R/R-devel.tar.gz: no such file or directory

Unfortunately, the tarball I am trying to download is not available at an HTTP url. Can ADD be modified to support FTP URLs?
I am aware that I could use RUN curl... to download from this URL, but I want the behavior of ADD which checks to see if the URL contents have changed and invalidates the cache if they have.

+1

USER POLL
The best way to get notified of updates is to use the Subscribe button on this page.
Please don't use "+1" or "I have this too" comments on issues. We automatically
collect those comments to keep the thread short.
The people listed below have upvoted this issue by leaving a +1 comment:
@bw2

We haven't seen more requests for this, so I'm closing this as it's not a priority

+1 Need support for FTP and sambashare

+1

+1

Hey @thaJeztah, are we supposed to make additional requests to re-open this issue by adding comments? Or is subscribing to this page as @GordonTheTurtle suggests enough?
Either way, +1.

@ahwagner it would help if you could describe your use case; t.b.h., we're in doubt if we want to add more complexity to ADD, there's already a lot of things it does. Adding support for ftp would probably require implementing a whole ftp client (what about sftp, etc etc)

Also most providers are in the process of phasing out anonymous FTP support.
On 27 Feb 2017 13:30, "Sebastiaan van Stijn"<EMAIL_ADDRESS>wrote:
@ahwagner https://github.com/ahwagner it would help if you could describe
your use case; t.b.h., we're in doubt if we want to add more complexity to
ADD, there's already a lot of things it does. Adding support for ftp would
probably require implementing a whole ftp client (what about sftp, etc etc)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/9314#issuecomment-282860181, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdcPCRvj36GPaTaPEQr2PO2K7VH5JPhks5rg0BdgaJpZM4DAAl7
.

@thaJeztah while I can not speak for others, but my primary desire for this feature is rooted in the ability to pull public scientific data into Docker containers at deploy-time. Much of it is stored in public FTP servers which have not/will not be updated to another storage scheme in the foreseeable future.
Example:
https://www.ncbi.nlm.nih.gov/books/NBK158899/

If it's at deploy time, adding support for ftp to ADD won't be of much help, as that's only during build

+1 for FTP support.
I was trying to download a file with FTP using ADD, during build time, and I couldn't.
Also, some images, like Ubuntu:16.04 (the one I'm using), do not have cURL installed. So, instead of just adding one file to Docker's ADD command:
ADD http-file-01 \
    http-file-02 \
    ...
    ftp-file \
    ...
    <path>

I'd have to add one more Docker command, adding one more layer to the image, and increasing the size of the image for installing cURL:
RUN apt-get update \
 && apt-get install curl \
 && curl -u user:password 'ftp://host/file' -o myfile


Add portions, slides and aliquots to GDC

Add portions, slides, aliquots to GDC API call (extract-gdc).
Verify that gdc.entity_to_specimen works with portions, slides and aliquots.

Closed in e28ecbe240e6ef81b397b2a1ce651171d896cf75


Proxy Error with 1.13

What is the output link of /viaversion dump? https://dump.viaversion.com/99edc95366f960f2f04591586e021777d03f378b6c304ec055c46ee3c7a2f6f3
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
Running Waterfall (BungeeCord fork), latest stable build
Also running a full custom set of plugins
How does this error happen? login? Using an item?
Appears to happen on server switch. I am just observing this error in my logs.
Is there an error in the console? Use pastebin.com. Is there a kick message?
https://pastebin.com/m4Npxr3m
Seems to be happening a bunch of times, with what seems to be a serialized item. I can provide more logs if necessary.

Could you confirm if this is fixed in our latest build?
https://ci.viaversion.com/job/ViaVersion/
If no, could you provide the new error and we'll reopen the issue.


[Bug] Err returned in Rust not properly passed to Dart

Describe the bug
After upgrading to version 1.82.1, the Err returned by a function signature containing a StreamSink was not correctly passed to Dart.
For example, the following Rust code:
pub fn require_run_lock(_sink: StreamSink<()>) -> Result<()> {
     return Err(anyhow::Error::msg("already require run lock"));
}

In 1.81.0, the exception information thrown by Dart is FfiException(RESULT_ERROR, already require run lock, null)
In 1.82.1, the exception message thrown by Dart is Exception: tried to parse data but function is null
Here is a minimal example to reproduce the issue: https://github.com/OfficialBoyfriend/rust_demo, just switch to 1.82.1 to revert the issue.
Codegen logs with RUST_LOG=debug environment variable
-

To Reproduce
No response
Expected behavior
No response
Generated binding code
No response
OS
No response
Version of flutter_rust_bridge_codegen
No response
Flutter info
No response
Version of clang++
No response
Version of ffigen
No response
Additional context
No response

Looks like a bug. This looks similar to https://github.com/fzyzcjy/flutter_rust_bridge/issues/1387, and the cause may be that, after merging the PR of enhanced error handling, there are some problematic edge cases.
Feel free to PR (this looks not very hard to fix)! The first step may be to add a test case in this repository, and then debug that test case to see why "tried to parse data but function is null" is thrown and fix it.

@OfficialBoyfriend 我看了你的主页，你是四川的？我看了你的技术栈和我差不多，可以多多交流学习。。。


Segfault with v1.1.0

Hi Erik,
thanks for putting a lot of effort in updating freebayes! I'm getting some troubles running the newest version though.
With v1.1.0:
freebayes/bin/freebayes -b test-sorted.bam -f ../reference.fasta -v test2.vcf -d
Opening output file: test2.vcf ...
loading fasta reference ../reference.fasta
Opening BAM format alignment input file: test-sorted.bam ...
 done
Number of ref seqs: 720537
Number of target regions: 0
no sample list file given, reading sample names from bam file
found 1 samples in BAM file
Segmentation fault (core dumped)

Everything works well with v1.0.2:
freebayes -b test-sorted.bam -f ../reference.fasta -v test2.vcf -d
Opening output file: test2.vcf ...
loading fasta reference ../reference.fasta
Opening BAM fomat alignment input file: test-sorted.bam ...
 done
Number of ref seqs: 720537
Number of target regions: 0
no sample list file given, reading sample names from bam file
found 1 samples in BAM file
loading first target
to next target
processing position 8200 in sequence scaffold_10
alignment: 2_2205_3457_27131
[...]

Please let me know if I can help debugging this!

Hi Tomasz, can you run this in gdb and post the backtrace? Will be helpful in figuring this out.

FWIW, I also ran into an issue where a BAM worked in 1.02 and failed in 1.10.  My issue possibly had to due with ambiguous nucleotides and the traceback was generated by this line: https://github.com/ekg/freebayes/blob/25d07ae5541f276482b88c4880f7579ea77357ad/src/AlleleParser.cpp#L1015

Hi Jeremiah,
it gives:
Program received signal SIGSEGV, Segmentation fault.
0x00000000004b50af in strcpy (
    __src=0x7fffef0f8010 "##fileformat=VCFv4.2\n##fileDate=20161124\n##source=freeBayes v1.1.0\n##reference=../reference.fasta\n##contig=<ID=scaffold_1,length=16909>\n##contig=<ID=scaffold_2,length=34426>\n##contig=<ID=scaffold_3,le"..., __dest=0x7ffffdd9b960 <error: Cannot access memory at address 0x7ffffdd9b960>)
    at /usr/include/x86_64-linux-gnu/bits/string3.h:110
110       return __builtin___strcpy_chk (__dest, __src, __bos (__dest));

My reference.fasta does not include IUPAC codes (except N).

@TomaszSuchan Hmm, still not sure where this is coming from. Any way to provide a more verbose backtrace or narrow it down to a minimal BAM that is producing this?
For instance, I am wondering if you just trim your input to a single read, if it is still seqfaulting. Could be something unexpected in the header then.

I'm also getting a segfault with 1.1.0 at the same point. The original poster's reference has a large number of reference contigs, as do I. I cut down my reference file to 50,000 contigs and freebayes was able to run without a problem.
Opening BAM format alignment input file: bwa.bam ...
done
Number of ref seqs: 507413
Number of target regions: 0
no sample list file given, reading sample names from bam file
found 1 samples in BAM file
Program received signal SIGSEGV, Segmentation fault.
0x0000000000494248 in split (s=, delims="\n",
elems=std::vector of length 0, capacity 0) at split.cpp:21
21	split.cpp: No such file or directory.
in split.cpp
(gdb) bt
#0  0x0000000000494248 in split (s=, delims="\n",
elems=std::vector of length 0, capacity 0) at split.cpp:21
#1  0x0000000000494419 in split (s=,
delims=) at split.cpp:32
#2  0x00000000004b7fba in vcflib::VariantCallFile::parseHeader (this=0x82dc60,
hs=) at ../vcflib/src/Variant.cpp:1182
#3  0x000000000044e2c0 in openForOutput (this=0x82d5e0,
argc=, argv=)
at ../vcflib/src/Variant.h:124
#4  setupVCFOutput (this=0x82d5e0, argc=,
argv=) at AlleleParser.cpp:575
#5  AlleleParser::AlleleParser (this=0x82d5e0, argc=,
argv=) at AlleleParser.cpp:925
#6  0x0000000000407a8f in main (argc=5, argv=0x7fffffffde58)
at freebayes.cpp:78

It looks like freebayes is creating a single string containing the entire vcf header, which gets quite big when the reference has a lot of contigs with long names, causing stack space depletion. Increasing the maximum stack size with "ulimit -s" seems to take care of the problem.


Fatal error: Class 'Kirki_Init' not found

im getting Fatal error: Class 'Kirki_Init' not found in /public_html/wp-content/plugins/kirki/core/class-kirki.php on line 26
when i try to activate plugin, new installation from plugins menu in wordpress.
version 3.0.25
webserver nginx
php 7.0 fpm

That's extremely weird... perhaps something went wrong with the plugin installation? I'm using it on nginx+fpm servers without any issues and so are dozens of other people, this has never been reported before.
Any customizations that could possibly affect the paths where plugins get installed or something similar?

Hello there,
I send you an email with address and username and admin password. I cant believe it either and i just install clean wp for test just for this plugin. I try lots of things, default nginx config, defaul php, fpm config but cant found anything. Somehow autoload module does not load the php files without any errors even on /var/log/ error files and this error is only what i got.
Best regards.

Hello @abides , i'm Currently Facing the same problem as you, Please Can You Tell Me how did you Solve i, so i can move on, actually i tried everything i had on mind and nothing got me out of this .

I didnt get any help on this channel about this issue, so i try to update that ubuntu server to latest package version then i realized its 16.10 and its not support update anymore so i couldnt update. It seems, person who setup the system get wrong image for production server. I rebuild the system with Ubuntu 16.04.4 LTS and upgrade to latest packages. Then issue gone.

close #2026


GLFW_CURSOR_HIDDEN does not hide cursor

When using GLFW 3.1 with Ubuntu, hiding the mouse cursor via glfwSetInputMode() does not have any effect. The same code does hide the mouse cursor under Windows.
With GLFW 3.0, everything worked as supposed. Is this a bug?

This is a duplicate of #309.


Remove C Style Pointers

Through out the code especially when using closure's, C style pointers are used. To bring node-mapnik up to the style requirements with Mapnik core we should modify these pointers to either use shared_ptrs or unique_ptrs. This is ideal so that we do not ever have a situation where we unknowingly allow for a memory leak by failing to delete a closure object.

:+1: - all the C style stuff dates to my earliest attempts to learn how to write node C++ modules. Now that we've got C++11 on our side, this would be a fabulous thing to clean up. I made an attempt in a few places to use scope guards (just to avoid the error prone delete usage when argument validation fails), but I agree that unique pointers would probably be better (to avoid the delete used in the AfterSomething callbacks).


Removes constraints from parseField method default implementation.

Hello. Great library! This PR has a couple of changes, one of them simply removes a constraint that is technically not needed by the affected code. While the other refactors some code in order to remove another constraint. Wondering if you would like to merge one of these or both of these changes. Thanks.
The goal is to make it more convenient to reuse the parseField method by avoiding superfluous constraints on the default implementation.
When readField was added, the Read constraint on parseField is not required by the default implementation any more. I found myself needing to make dummy Read instances in order to reuse the default implementation.
The Typeable constraint is only used to derive the metavar within parseField. So I extracted metavar out as another type class method. A nice side effect of this is that now it's possible to customize the metavar and still reuse the default parseFields implementation. Using Proxy seemed like the right way to implementing this method, but I'm pretty new to type-level programming and generics, so I might be wrong.

Judging from CI it looks like this might require an explicit metavar definition for Any and All since they don't have a Typeable instance for GHC 7.8.4 and older

Ah, I forgot to try older versions of GHC. I'll fix it.

Awesome!  Thank you :)
I can release this to Hackage if you don't have any other pending changes in mind

I don't have anything else in mind. Thanks :)

You're welcome!


Support for angular 4+ is coming!

Is there any new version available for angular2?

I have not started on an Angular 2 version yet.

I've started on Angular 2 but need some help, please let me know what I should improve on.
https://mhlulani.github.io/datepicker
Thanks

Today, @alexw10 and I started working on the Angular 4+ version of this component. See the ngx branch.
Please 👍 this issue (and star this repository) if you want Angular 4+ support.
You can also leave a comment below if you have specific requirement that we should know about, or are willing to pitch in with the new version.

When this will be available. My project is waiting on this.

yeah，i am waiting for the version for angular4,how long willll i wait along...

Sorry, I don't have a date for you at the moment. Please stay tuned! Since this issue only has two votes it doesn't seem like there is much demand for it right now.

Well, there's 8 now, and I'm also waiting :P

I am also waiting :)

Hey everyone! Sorry about the delay. I was hoping for more of a response than 9. =)
My day job has been keeping me busy (got bills to pay!)
I will get to this and having higher numbers of people saying they will use it will help move this project up the priority list.

I need it too.fighting

Status update on this work. I've started working on the new version and the ngx2 branch is the working branch for this work. If you like, check out that branch and run npm start to play around (not much is implemented as of today)
The new version is focusing on improving usability. Adding support for keyboard usage, better A11Y, and styling.
Please comment here with additional feature requests.

I would like it possible to put the datetime picker as if it were an input field. And the hour view is possible to set the start and end time and the interval between the hours as well.

@pedrotcm I will add issues for these enhancements - please feel free to submit PR's for the changes you would like to see.


Cipla Stock Price Prediction Using LSTM, SVM, SVR, KNN and K Means Clustering

🛠 Related Issue
Fixed: #664
📝 Description
Predicting Bharti Airtel Stock Prices involves using various machine learning models like LSTM (Long Short-Term Memory), SVM, SVR, KNN and K Means Clustering to analyze historical stock data and forecast future trends. Each model leverages different algorithms and methodologies to enhance prediction accuracy and reliability.
🔍 Type of PR

[x] ✨ Feature enhancement
[x] 📚 Documentation update

✅ Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Hi @Akshat111111, Please assign labels GSSOC and level 2 to this PR. And Merge the PR
Resolves #664


Added more netctl commands and updated node IPam struct.

Coverage decreased (-0.01%) to 75.648% when pulling 1987ab7e23516b0aefedaa350f29bcbb8984d72b on omegaman123:master into cd3518f6166b528a6e0ad2f855511fa8f6ffa70b on contiv:master.


Operator refactor - validation and import cleanup

Round 1 - go!
Let's see what clean up we can do here @timflannagan1.
This has the following commits that can be reviewed independently

move the type declarations to their own file and try to comment them up for future readers
since the reporting operator was not exporting anything, introduce an interface and unexport the type.  Consumers deal with the interface now
move all the smaller validation blurbs from the various sections that are called during New, newOperator, and Run methods and consolidate on a single validation call to ensure the config is good during New.  No good config == no operator to run.  Bonus: Add tests for all validations
rename cb* imports to remove references to chargeback

There are a couple questions sprinkled in where things weren't obvious.

/assign @timflannagan1

Something else that I would like to tackle, but is probably out of the scope of this kind of work, is improving (or adding) comments to types/methods/functions to the various reporting-operator components, like what does New() ... or op.Run achieve such that a person not familiar with controllers would be able to see what we're trying to achieve with those functions.

improving (or adding) comments to types/methods/functions to the various reporting-operator components,

this is 100% a goal here.  Anything we touch in a refactor should get comments IMO, hence the API comments.

Some other observations for the discussion (perhaps this PR, perhaps future)

figure out why we have so many threads in a single operator pod and if we can reduce and maintain performance (possibly removing the need for any mutex guarded code depending on the answer)

reduce the configuration complexity where possible.  Example is the namespace configuration where we require AllNamespaces to be set with TargetNamespaces when we could just key on TargetNamespaces and do the right thing.  Same for the TLS configs with a boolean that turns it off or on when we could just have the existence of the certs enable it.

move items that are ancillary to the operator into their own packages

time="08-04-2020 13:35:39" level=debug msg="Created the mysql namespace" context=metering-validhdfs-mysqldatabase
error: multiple images or templates matched "mysql:5.7"

The argument "mysql:5.7" could apply to the following Docker images, OpenShift image streams, or templates:

* Image stream "mysql" (tag "8.0") in project "openshift"
  Use --image-stream="openshift/mysql:8.0" to specify this image or template

* Image stream "mysql" (tag "latest") in project "openshift"
  Use --image-stream="openshift/mysql:latest" to specify this image or template

time="08-04-2020 13:35:39" level=debug msg="Created the mysql namespace" context=metering-validhdfs-mysqldatabase
error: multiple images or templates matched "mysql:5.7"

The argument "mysql:5.7" could apply to the following Docker images, OpenShift image streams, or templates:

* Image stream "mysql" (tag "8.0") in project "openshift"
  Use --image-stream="openshift/mysql:8.0" to specify this image or template

* Image stream "mysql" (tag "latest") in project "openshift"
  Use --image-stream="openshift/mysql:latest" to specify this image or template

https://github.com/kube-reporting/metering-operator/pull/1353

/retest

/retest

/retest

Removing WIP from this - it's probably big enough that we shouldn't add anything else too it yet if we want to merge.  I am going to call out a few pieces (in review comments) that I think we need to be aware of though before we merge.

/retest

/retest

@bentito @timflannagan1 updates from the review in the last commit.  Thanks.

/retest

/retest

/retest

/retest

/retest

/retest

@pweil- @bentito where are we at with this? There's nothing in here that I think we should hold off until 4.7 master opens up so merging this sooner than later is probably best.

@timflannagan1 all review comments from @bentito have been addressed (left the prometheusDataSourceGlobalImportFromTime/prometheusDataSourceMaxBackfillImportDuration and removed the non-api host/port validations and tests).
Unless there is anything else I think this can merge.

/lgtm
/approve

/retest

:tada:


docs(client_core): :memo: Fix C API documentation

@ShootingKing-AM Let's merge this once you finished the PhoneVR integration rebase

Considering how clippy is complaining you better add the dead code and unused functions lint disable from the server c_api to this


Support HTTP Basic authentication when fetching dependencies

Hello!
I need to be able to supply HTTP Basic auth as part of the discovery process, so I modeled an implementation off of the rkt file format.
Can you take a look and let me know if this is along the lines of what you were thinking?
Thanks!

@jonboulle is this something you'd consider including?

Wow, so sorry about not getting around to this. I'm just now getting back into acbuild development. I'll review this now.

Would you be willing to move the authConfigDir into the ACBuild struct in lib/common.go, instead of having it be an argument to Begin? I feel as if it belongs there better.


Add link to 0.3.0 release notes

Index contains links to 0.2.0 and 0.1.0 release notes, doesn't include latest 0.3.0 release notes.

@jongalloway I'll send that to the Live site right now. :+1:


Update renovate config.

Remove label kokoro:run (it is being applied by the trusted contributors bot)
Removes prCreation: notPending (doesn't seem to be doing anything)
Groups a few similar packages together (less PRs for us to review)
Enables the "masterIssue" feature - I turned this on for Python, and it looks useful for tracking what Renovate plans to update

With not-pending we're going to have to monitor these more actively instead of relying on email notifications, since kokoro doesn't seem to want to run the tests by default without the kokoro:run label.

With not-pending we're going to have to monitor these more actively instead of relying on email notifications, since kokoro doesn't seem to want to run the tests by default without the kokoro:run label.

I don't think this will have any effect with our current workflow. The docs describes the following for prCreation=not-pending:
not-pending: Renovate will wait until status checks have completed (passed or failed) before raising the PR

We aren't actually running tests on any branch unless it's in master or when a PR is opened, so I don't think this is doing anything for us.


Adding MIT License

@matamalaortiz are there any images, fonts, or design elements that would be incompatible with the MIT license? I seriously doubt there are but just want to check before merging!

@shiffman yes I think there are no problems with the current version. There are no special design elements being used, system ui fonts and the Robin image is from public domain

ok!


Youp3 v1.0.3: The app crashes every time I try to launch it.

Describe the bug.
I had downloaded and launched the app for the first time. I used it for a couple of minutes and exited it. I launched the app again, and it kept crashing.
How to reproduce.

Download and launch the app.
Exit the app
Launch the app again
See error.

Expected behavior.
I expected that I could close and launch the app at anytime without any hassle.
Test Environment.
Device: Redmi Note 5 Pro
OS: Android 9.0
Software version: Youp3 v1.0.3
Screen recording.
https://youtu.be/j9782eYPW88
Logcat
	at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3722)
	at android.app.ActivityThread.access$1700(ActivityThread.java:200)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1704)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:201)
	at android.app.ActivityThread.main(ActivityThread.java:6810)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: java.lang.SecurityException: Permission Denial: startForeground from pid=19403, uid=10418 requires android.permission.FOREGROUND_SERVICE
	at android.os.Parcel.createException(Parcel.java:1953)
	at android.os.Parcel.readException(Parcel.java:1921)
	at android.os.Parcel.readException(Parcel.java:1871)
	at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:5144)
	at android.app.Service.startForeground(Service.java:695)
	at downloader.utils.DownloadExecutorService.onStartCommand(DownloadExecutorService.java:74)
	at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3700)
	... 8 more
Caused by: android.os.RemoteException: Remote stack trace:
	at com.android.server.am.ActivityManagerService.enforcePermission(ActivityManagerService.java:9569)
	at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked(ActiveServices.java:1226)
	at com.android.server.am.ActiveServices.setServiceForegroundLocked(ActiveServices.java:901)
	at com.android.server.am.ActivityManagerService.setServiceForeground(ActivityManagerService.java:21042)
	at android.app.IActivityManager$Stub.onTransact$setServiceForeground$(IActivityManager.java:10581)

The problem persists on Android 9. A simple patch will solve the issue.
On Thu, 20 Jun, 2019, 12:17 Harry<EMAIL_ADDRESS>wrote:

Describe the bug.
I had downloaded and launched the app for the first time. I used it for a
couple of minutes and exited it. I launched the app again, and it kept
crashing.
How to reproduce.

Download and launch the app.
Exit the app
Launch the app again
See error.

Expected behavior.
I expected that I could close and launch the app at anytime without any
hassle.
Test Environment.
Device: Redmi Note 5 Pro
OS: Android 9.0
Software version: Youp3 v1.0.3
Screen recording.
https://youtu.be/j9782eYPW88
Logcat
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3722)
at android.app.ActivityThread.access$1700(ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1704)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6810)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: java.lang.SecurityException: Permission Denial: startForeground from pid=19403, uid=10418 requires android.permission.FOREGROUND_SERVICE
at android.os.Parcel.createException(Parcel.java:1953)
at android.os.Parcel.readException(Parcel.java:1921)
at android.os.Parcel.readException(Parcel.java:1871)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:5144)
at android.app.Service.startForeground(Service.java:695)
at downloader.utils.DownloadExecutorService.onStartCommand(DownloadExecutorService.java:74)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3700)
... 8 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActivityManagerService.enforcePermission(ActivityManagerService.java:9569)
at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked(ActiveServices.java:1226)
at com.android.server.am.ActiveServices.setServiceForegroundLocked(ActiveServices.java:901)
at com.android.server.am.ActivityManagerService.setServiceForeground(ActivityManagerService.java:21042)
at android.app.IActivityManager$Stub.onTransact$setServiceForeground$(IActivityManager.java:10581)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ExploiTR/YouP3/issues/8?email_source=notifications&email_token=AE6DTZ53LJB6WMEJ63QJEZDP3MRXDA5CNFSM4HZP5SHKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2SKCUQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6DTZ4VAN53IFEI7ZHSYH3P3MRXDANCNFSM4HZP5SHA
.

Oh okay. Please help fix it as soon as possible. I'd really love to get back to using the app. Thanks a mil.

https://github.com/ExploiTR/YouP3/releases/tag/1.4.0
@HarryHeights
I have a very limited amount of time now, though I tried fixing it. Please check it and report me if any problem persists.

Alright. I'll do

The issue has been fixed. Thanks a lot.


fix git4go dependency

linguist forked git4go which points to the same fix I made in my fork.

@bacongobbler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Cap DC memory usage - limit # mutation threads

Each mutation thread can use a significant amount of memory due to batching up mutations before writing to truth.  Cap the number of mutation threads allowed using an AtomicInteger.  Note this number should be smaller than the total number of threads serving requests to allow for exports and other requests.
Also, reduce the default batch size.

data-coordinator #284 SUCCESS
This pull request looks good

Reviewed up to 6f05cc.

Addressed review comments.

data-coordinator #286 SUCCESS
This pull request looks good


[build-script] Add --santize option

https://github.com/apple/swift/pull/30963
@swift-ci please test

macOS: +2.5 minutes
Linux: +1 minute
Seems cheap enough to use in indexstore-db PR tests.
UBSan is showing a bunch of issues but the build isn't failing, so something is going wrong there.  Also, we might need a way to turn off ubsan for lmdb code.

apple/swift#30963
@swift-ci please test

apple/swift#30963
@swift-ci please test

apple/swift#30963
@swift-ci please test macOS

apple/swift#30963
@swift-ci please test macOS


Description Suggestion

It would help if the description would say what the default key is and that the key bind can be changed. Also including a screenshot of what the gui looks like in game would be a benefit. I have skipped over mods before because they did not give me any indication of how they worked or how it looked in game.

Added in 1.3.0+1.20.1 (coming soon™)


[$250] Expense - Expense can still be submitted after leaving workspace chat

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.84-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:

User is invited to a workspace

Go to staging.new.expensify.com
Go to workspace chat as workspace member
Go offline
Go to + > Submit expense > Manual
Proceed to confirmation page
Click on the workspace chat
Click Leave

Expected Result:
After leaving the workspace chat, user should be prevented from submitting the expense
Actual Result:
After leaving the workspace chat, user still can submit the expense
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/0402ab6b-ef85-492c-b6b1-7ada60bf30cf
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0194a281c56dd7cd3e
Upwork Job ID:<PHONE_NUMBER>325940224
Last Price Increase: 2024-06-24

Issue OwnerCurrent Issue Owner: @sobitneupane

@thienlnam  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

This seemed like it would have been from a BE PR, but I haven't seen anything that would change how this works. Going to open up externally for some more eyes on the App checklist

Demoting since this is an edge case bug and doesn't need to block deploy

Proposal
Please re-state the problem that we are trying to solve in this issue.
Offline when a user clicking "Submit expense" button from composer, and then clicking "Leave" button on Details page and then continuing submit expense, submit expense works though the user is already left the workspace.
What is the root cause of that problem?
https://github.com/Expensify/App/blob/2995925a6df751c4cf32c5238539d497d4454d06/src/pages/ReportDetailsPage.tsx#L124-L129
Here a user left the workspace (it means report.notificationPreference = hidden) but on policy the user doesn't get removed from employees. And Report.leaveGroupChat worked not Report.leaveRoom for workspace because the condition didn't check workspace or not. Since the user isn't removed from policy, the user can submit expense still.
What changes do you think we should make in order to solve the problem?
We should let Report.leaveRoom work and the user remove itself of the user. From this code
https://github.com/Expensify/App/blob/2995925a6df751c4cf32c5238539d497d4454d06/src/pages/ReportDetailsPage.tsx#L124-L129
Add isPolicyExpenseChat condition for checking leaving from workspace and add Member.removeMembers(accountIDsToRemove, report.policyID); for removing itself from policy. Add Navgation.resetToHome(); then just after clicking "Leave", RHPs will be closed.
        if (isChatRoom || isPolicyExpenseChat) {
           const isWorkspaceMemberLeavingWorkspaceRoom = (report.visibility === CONST.REPORT.VISIBILITY.RESTRICTED || isPolicyExpenseChat) && isPolicyEmployee;
           const accountIDsToRemove = [session?.accountID];
           Member.removeMembers(accountIDsToRemove, report.policyID);
           Report.leaveRoom(report.reportID, isWorkspaceMemberLeavingWorkspaceRoom);
  	   Navgation.resetToHome();
           return;
        }
        Report.leaveGroupChat(report.reportID);

Then when clicking Leave from workspace Report.leaveRoom does work and the user goes to report screen not to proceed to submit expense.
What alternative solutions did you explore? (Optional)
N/A
https://github.com/Expensify/App/assets/46774300/84ba80fc-6bc3-4c45-9a68-dfb636ba342b

I could not reproduce the issue because the leave option is no longer available on the details page.
https://github.com/Expensify/App/assets/25876548/c2580ce0-3b15-43e1-835d-13978267e816

@thienlnam what do you think re: @sobitneupane's comment above?

Hmm, it looks like you were invited to that workspace too. Did we end up removing / moving the leave button recently? Maybe this change?

hey @isabelastisser handing this one over for my parental leave K2 clear out. @thienlnam and @sobitneupane are still working out the details here of whether this is reproducible, and no proposals to review yet. Thanks!

@thienlnam This change probably removed the leave button.

Hmm, looks like along those same lines you shouldn't be able to leave a workspace chat ever so it shouldn't be showing the option to leave

Brought this up in product, but the expected functionality is that if you are part of the workflow/approval chain you should not be allowed to leave the workspace chat

Not overdue - pending proposals

The other cases were addressed here https://github.com/Expensify/App/issues/44237, so now we just need to handle the approver case

Not overdue - pending proposals

so now we just need to handle the approver case

@thienlnam Could you clarify how to handle the approver case? As I understand, the approver is assigned by workspace owner. Is it right? Also as I understand the case is when the approver can leave the workspace while submitting expense. Please fix me if my understanding is wrong.

Issue not reproducible during KI retests. (First week)

Bump @mvtglobally, can you please retest? Thanks!

https://github.com/Expensify/App/issues/43852#issuecomment-2214114421

Bump @mvtglobally. can you please retest? thanks!

Issue not reproducible during KI retests. (Second week)

Here is a video, issue no longer reproducible
https://github.com/Expensify/App/assets/93399543/2df79aca-95fb-49bf-951f-01e443ee9119


Flaking Test: consistent_replicate_s3

Which jobs are flaking?
cdc_ghpr_integration_test
Which test(s) are flaking?
consistent_replicate_s3
Jenkins logs or GitHub Actions link
[2022-07-04T07:23:39.702Z] table consistent_replicate_s3.check1 not exists for 41-th check, retry later

[2022-07-04T07:23:42.310Z] table consistent_replicate_s3.check1 not exists for 42-th check, retry later

[2022-07-04T07:23:44.258Z] table consistent_replicate_s3.check1 not exists for 43-th check, retry later

[2022-07-04T07:23:46.186Z] table consistent_replicate_s3.check1 not exists for 44-th check, retry later

[2022-07-04T07:23:48.351Z] table consistent_replicate_s3.check1 not exists for 45-th check, retry later

[2022-07-04T07:23:50.307Z] table consistent_replicate_s3.check1 not exists for 46-th check, retry later

[2022-07-04T07:23:52.340Z] table consistent_replicate_s3.check1 not exists for 47-th check, retry later

[2022-07-04T07:23:54.311Z] table consistent_replicate_s3.check1 not exists for 48-th check, retry later

[2022-07-04T07:23:56.327Z] table consistent_replicate_s3.check1 not exists for 49-th check, retry later

[2022-07-04T07:23:58.316Z] table consistent_replicate_s3.check1 not exists for 50-th check, retry later

[2022-07-04T07:24:00.294Z] table consistent_replicate_s3.check1 not exists for 51-th check, retry later

[2022-07-04T07:24:02.279Z] table consistent_replicate_s3.check1 not exists for 52-th check, retry later

[2022-07-04T07:24:04.274Z] table consistent_replicate_s3.check1 not exists for 53-th check, retry later

[2022-07-04T07:24:06.300Z] table consistent_replicate_s3.check1 not exists for 54-th check, retry later

[2022-07-04T07:24:08.341Z] table consistent_replicate_s3.check1 not exists for 55-th check, retry later

[2022-07-04T07:24:10.411Z] table consistent_replicate_s3.check1 not exists for 56-th check, retry later

[2022-07-04T07:24:13.045Z] table consistent_replicate_s3.check1 not exists for 57-th check, retry later

[2022-07-04T07:24:14.549Z] table consistent_replicate_s3.check1 not exists for 58-th check, retry later

[2022-07-04T07:24:16.686Z] table consistent_replicate_s3.check1 not exists for 59-th check, retry later

[2022-07-04T07:24:18.718Z] table consistent_replicate_s3.check1 not exists for 60-th check, retry later

[2022-07-04T07:24:20.820Z] table consistent_replicate_s3.check1 not exists at last check

[2022-07-04T07:24:20.820Z] Exiting on signal: INTERRUPT

[2022-07-04T07:24:43.130Z] make: *** [integration_test_mysql] Error 1

Anything else we need to know

Does this test exist for other branches as well?

Has there been a high frequency of failure lately?

/area ticdc

/type enhancement

/assign


Remove Version Update and Update Package to 2.3.0 (SWS-4906)

Motivation

I'd like to get this out there so I can use it
Looks like with GitHub actions, they've designed it such that the package.json should always match the latest release (no easy way to pull the version number from the release tag)

Modification

Removed npm version command
Updated to 2.3.0

https://centeredge.atlassian.net/browse/SWS-4906

/merge


Using Via HttpRequest get corrupted file

Hi I'm a Game developer, Currently I'm using Godot Engine , making a tool for it and one of it needs is get a specific folder from Github, Gitzip is perfect for this, but when downloading the file using Godot I get 21kb while the file has 121kb, I just using a HTTPRequest with a url like this:
https://kinolien.github.io/gitzip/?download=/godot-extended-libraries/abstract-state-machine/tree/master/addons&token=TOKEN
in the browser works perfectly, there is a way to solve this?
I was thinking on an API to get the direct link to the zip file i.e: https://github.com/file.zip

Their are different ways.
The browser execute javascript to fetch contents by using Github API, and use HTTPRequest just fetch HTML only, hence you can not get zip file.
I think there are 3 ways to achieve this:

Use SVN library (stackoverflow answer)
I make the service on server (i.e. implement the browser javascript to backend)
Copy gitzip algorithm and implement in Godot Engine

1th or 3th is recommended. And the 2nd must be a large cost, unless someone sponsored, I don’t want to do it :-(
Hope it helps.

3rd options seems to be the answer here, thank you very much for your time!!!


fix:tcp connection window size split from stream connection window size

What is the purpose of the change
see issue #14635
Brief changelog
details can see io.netty.handler.codec.http2.Http2FrameCodec#tryExpandConnectionFlowControlWindow
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

details refer to io.netty.handler.codec.http2.Http2FrameCodec#tryExpandConnectionFlowControlWindow

@oxsean  i'm sorry to say that  because some reason  i have to re-pr
PTAL

@EarthChen  PTAL


Add support  for emotion analysis and image text extraction

Hi I just added these two modes!
Please let me know, in case you'd like to merge it upstream, if you need me to change something and I'll provide a new pull request!
Cheers

sorry, fixing things according to contributing guidelines and pull requesting again :)


Fix bug with handling of encoding when using RestIO

Coverage remained the same at 100.0% when pulling 149cbc591eca5ac75331935fc6b82aae8ef23b95 on dnouri:bugfix/restio-encoding into 02c0bce2e1c16ae0651fdebc49de715313929c31 on ottogroup:develop.


Additional PT biases

Adds third-order and non-local bias.
Closes #900

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

15 of 18 (83.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 96.75%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/nl_pt/power.py
10
13
76.92%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
4019

Relevant Lines:
4154

💛  - Coveralls

Nice, I see you've tagged Jonathan and Shivam but let me know if you want me to take a look too.

@damonge @jablazek @shivamp1495 what's the status here?


Win GUI version?

Any ETA for Windows GUI version installer?

seno.uno
above is the URL to download

seno.uno
above is the URL to download

Why don't you add them to the readme for convenience. What does your website do that many people know!

Where are you guys from? :D Seno is Slovenian word... I should know... :D :D :D

seno.uno
above is the URL to download

Why don't you add them to the readme for convenience. What does your website do that many people know!

Im not a developer im just a miner like you :D

seno.uno
above is the URL to download

Why don't you add them to the readme for convenience. What does your website do that many people know!

 :D

bro wen binance

Where are you guys from? :D Seno is Slovenian word... I should know... :D :D :D

Certainly from one of Balkan countries. :)

Keep the change, this download channel has been cancelled, wait for two weeks to release the updated version

Do we have any peer list, we can add? App is having a hard time finding them, so not able to sync...

Do we have any peer list, we can add? App is having a hard time finding them, so not able to sync...

Install new version of the app SenoSetup-1.1.834


Breakpoint translate flag

Summary of the changes

Start running pull diagnostics through translate.

Break diagnostics translate out into a service to keep the multi-location use clean
Create an Integration test which covers the diagnostics scenario that was missed.
Remove SingleServerDiagnostics flag (if people feel strongly or there's some policy I'm unaware of this can be left in).

Fixes: Reversion of https://github.com/dotnet/razor/pull/7986.

Someone has breakpoints on the brain :)

WRT @davidwengier's concerns WRT HTML: We confirmed that HTML diagnostics ARE actually broken in CSHTML files ATM, but we also confirmed that this was not caused by the SingleServer move (because it pre-dates my original PR). I created a (skipped) Integration test in this PR which should start passing (and be un-skipped) once https://github.com/dotnet/razor/issues/8023 is complete.


Using generator assets in custom plug in

I want to use this script with a plug in that I'm making so that I can specify a file size. Can this script he called from my plugin? I'd so, is there an api for it?

It is possible to use this repo (generator-assets) as a dependency in your plugin.  An old example is here: https://github.com/adobe-photoshop/generator-spaces
You could also consider forking this repository and adding your file-size logic
the 2.9 branch is the most stable
further questions can be asked here:
https://groups.google.com/forum/#!forum/adobe-generator-dev


Duplicate keys throw an error with an unhelpful message

I am working on stylelint webpack plugin and I think it would be appropriate for stylelint itself to inform users that they have duplicate keys in their .stylelintrc. I have been trying to get a PR going but I haven't had success running the tests on master yet.
Raising the issue here because I don't think that it's difficult to fix but I'm kinda blocked right now.

@davidtheclark what's blocking me from fixing this is the tests failing from a clean state on master when I clone and run yarn install on my system with the latest stable node (v7.4.0 at time of writing). Does this package depend on a specific version of node?
couple questions: I noticed that node v0.12 support was added recently even though the LTS support dropped as of December. Are there plans to move forward again?

regardless, I'm quite sure that the tests should be written in ES2015+ since AVA transpiles them anyway.

@JaKXz How are the tests failing? What is the error? Have you tried seeing if the tests pass on Travis with Node 7 (by changing the .travis.yml file in a PR)?
I just tried rm -rf node_modules && yarn install && npm test and had no problem. I am on Node v4.7.0, Yarn v0.18.1.

Does this package depend on a specific version of node?

As specified in the package.json, this package should work on Node 0.12 and higher.

I noticed that node v0.12 support was added recently

It was re-added, because we removed support but then some users wanted it back, and it was easy to restore.

Are there plans to move forward again?

I don't understand "move forward" here. There shouldn't be a problem with higher versions of Node. Maybe your error message will clarify things.

I'm quite sure that the tests should be written in ES2015+ since AVA transpiles them anyway.

I disagree. I'd rather have the codebase stick to one feature set than write the tests differently than the rest of the code.

@davidtheclark the failures are here: https://travis-ci.org/davidtheclark/cosmiconfig/jobs/189389524
I had spent some time a few weeks ago attempting to debug the failures locally but made no progress without context.
re:

I'd rather have the codebase stick to one feature set than write the tests differently than the rest of the code

using t for all assertions is the compromise that I'm suggesting, then.

I've been meaning to give jest a whirl, would you mind that?

@JaKXz If you'd like to try, sure! It will be much more effort, though, since the syntax is more different from AVA's and the way of handling mocks will need to change. If that's the kind of challenge you seek, go for it.

Closing as stale, and probably out of scope for this package.


Usage without underlying entity + route params

Is it possible to use form type without underlying entity?
I have controller action (route) which offers on of backend-generated data sets, but there is no entity data is saved in. Unfortunately documentation says "class is your entity class. Required".

Is it possible to set remote_route params? I'd like to pick which backend-generated data set should be used.

Thanks

Second question - anyone?


feat: Enable GP3 storage class when enabling ebs csi driver

#1562

thank you for the PR! I don't believe we need to embed this into the addon since there are various ways in which the storage class can be created (i.e - Terraform, kubectl, ArgoCD, etc.). Instead, we have demonstrated in the stateful example how you can add the gp3 storage class and set it as the default storage class while retaining the gp2 storage class


Remove env file from repo

Remove cit3.0-web/public/static/env.js

Decided to keep file because the environment variables are not containing secrets.


[SPARK-5240][SQL] Adding createDataSourceTable interface to Catalog

1 Added createDataSourceTable interface to Catalog
2 remove DDLStrategy and HiveDDLStrategy by making CreateTempTableUsing and CreateTableUsing follow RunnableCommand
#3960

Test build #25515 has started for   PR 4036 at commit 4898c57.

This patch merges cleanly.

/cc @yhuai

Test build #25515 has finished for   PR 4036 at commit 4898c57.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25515/
Test PASSed.


TLF-103- Page titles should match h1 headings - changes done as expected

What

TLF LMR - LMR - Page titles should match h1 headings - TLF-103

Why

Per the GDS Service Manual, titles should be unique and they should match the H1 heading. The html contains three  elements

How

Analysed and Identified the code changes to fix the mentioned issues
Fixed the code as per the requirement
Added {{PageTitle}} in all the template file to overcome the issue.

apps/lmr/translations/src/en/pages.json
All template HTML files

Testing

[x] Local testing passed
[x] Unit test passed in Local
[x] Test Lint Passed in Local
[] Pipeline Check Passed
[] Branch Testing passed

Suggested workaround would be to extract the service name in the translations journey.json file.
"serviceName": "Landlords make a report"
Then add the copy layount.html template which will overwrite the default hof layout template.
The serviceName variable can then be used to construct the page title on layount.html template
  {{$pageTitle}}
    {{#errorlist.length}}{{#t}}errorlist.prefix{{/t}}{{/errorlist.length}} {{title}} – {{#t}}journey.serviceName{{/t}} – GOV.UK
  {{/pageTitle}}

This eliminates the need for duplicate code in pages.json and specifying the content of the pageTitle block in each template.


[Feature] On failures, post a number in the PR + link to the failing run

Wont do anyways, too much noise for now.


[FLINK-32403][table] Add database related operations in CatalogManager

What is the purpose of the change
This PR aims to add database operations in CatalogManager, then Create/Alter/DropDatabaseOperation can use catalog manager to do some operations for database and we can add a listener in catalog manager for them later.
Brief change log

Add create/alter/drop database method in catalog manager
Use catalog manager for database in Create/Alter/DropDatabaseOperation

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no) no
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no) no
The serializers: (yes / no / don't know) no
The runtime per-record code paths (performance sensitive): (yes / no / don't know) no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know) no
The S3 file system connector: (yes / no / don't know) no

Documentation

Does this pull request introduce a new feature? (yes / no) no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi @libenchao Please help to review this PR, thanks