Use vscode log path

path changes from
{temp}\azuredatastudio\mssql
to
{temp}\azuredatastudio\logs{dateStamp}\exthost1\Microsoft.mssql

Can you verify that the following issues are addressed:
https://github.com/microsoft/azuredatastudio/issues/4509
https://github.com/microsoft/azuredatastudio/issues/4510
if not we should take a quick look as to why not.

It would fix #4509 since thats what the "exthost1" part of the new part handles. I'm not sure about the second one.

@ranasaria I think this might be the chance to move the sqltoolslog output from being built into the product to contributed by the extension. Was the goal of that edit to map the sqltools log file to a vscode output window? That should be doable from the extension side using the same lib that vscode uses sqdlog

Yeah they were both related.
Thanks! – I will check out the 2nd one after your fix is in. Can you please reference the 4509 but in your pull request.

Arvind.

From: Anthony Dresser<EMAIL_ADDRESS>Sent: Monday, August 5, 2019 4:07:29 PM
To: microsoft/azuredatastudio<EMAIL_ADDRESS>Cc: Arvind Ranasaria<EMAIL_ADDRESS>Review requested<EMAIL_ADDRESS>Subject: Re: [microsoft/azuredatastudio] Use vscode log path (#6599)
It would fix #4509https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fazuredatastudio%2Fissues%2F4509&data=02|01|Arvind.Ranasaria%40microsoft.com|8e1aef90c1c74a8de62908d719f9b0ed|72f988bf86f141af91ab2d7cd011db47|1|0|637006432516364628&sdata=u%2BDZxCR10%2BRLMqPOMhBIsfz9fnjvyBxW9Pyyfqy6ImU%3D&reserved=0 since thats what the "exthost1" part of the new part handles. I'm not sure about the second one.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fazuredatastudio%2Fpull%2F6599%3Femail_source%3Dnotifications%26email_token%3DAJ5JMVV6IZ2Z4T27JJCKVCLQDCXDDA5CNFSM4IJPATTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3TKXTQ%23issuecomment-518433742&data=02|01|Arvind.Ranasaria%40microsoft.com|8e1aef90c1c74a8de62908d719f9b0ed|72f988bf86f141af91ab2d7cd011db47|1|0|637006432516364628&sdata=ntAzAJ5Pjdn4337B1Aw7Bqe0SKRDr%2FQCwOvkP71GXcM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ5JMVTTDZIC3HUNW7M2HELQDCXDDANCNFSM4IJPATTA&data=02|01|Arvind.Ranasaria%40microsoft.com|8e1aef90c1c74a8de62908d719f9b0ed|72f988bf86f141af91ab2d7cd011db47|1|0|637006432516374622&sdata=Pelzsz8wpKOZM9lopckeikkK8Ig0TqiUgq54jCLSa6c%3D&reserved=0.

Yes, I agree. I will sync up with you later to do the needful next week.

Arvind.

From: Anthony Dresser<EMAIL_ADDRESS>Sent: Monday, August 5, 2019 4:12:34 PM
To: microsoft/azuredatastudio<EMAIL_ADDRESS>Cc: Arvind Ranasaria<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/azuredatastudio] Use vscode log path (#6599)
@ranasariahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Franasaria&data=02|01|Arvind.Ranasaria%40microsoft.com|abf261773b1e42eb6b3d08d719fa66a0|72f988bf86f141af91ab2d7cd011db47|1|0|637006435561813299&sdata=VkCws97PoOTB4nqAAhGWzvhY7EoXNTTPTuKv8xok6JQ%3D&reserved=0 I think this might be the chance to move the sqltoolslog output from being built into the product to contributed by the extension. Was the goal of that edit to map the sqltools log file to a vscode output window? That should be doable from the extension side using the same lib that vscode uses sqdlog
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fazuredatastudio%2Fpull%2F6599%3Femail_source%3Dnotifications%26email_token%3DAJ5JMVRVVFQWJ5GLI7JOJXTQDCXWFA5CNFSM4IJPATTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3TK7MY%23issuecomment-518434739&data=02|01|Arvind.Ranasaria%40microsoft.com|abf261773b1e42eb6b3d08d719fa66a0|72f988bf86f141af91ab2d7cd011db47|1|0|637006435561823294&sdata=P1faXdFBXzcldnJBuWeaF19uHkjYSBjNYC%2FDxuHMwIc%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ5JMVXQ555E2GYMZSLKRPDQDCXWFANCNFSM4IJPATTA&data=02|01|Arvind.Ranasaria%40microsoft.com|abf261773b1e42eb6b3d08d719fa66a0|72f988bf86f141af91ab2d7cd011db47|1|0|637006435561823294&sdata=twkgYaZE%2BeY0zjpPfn8H0iqAbxQ4w5PVCd%2Fi30pQa7M%3D&reserved=0.

I think we will need that change for this PR, since currently this PR will just break the output window, since the log path is now generated, vs in the code you point to a hard coded log path. I can just implement it as part of this PR if you have thoughts on implementation.

@ranasaria is it fine if we remove the vscode edit where we add the sqltoolsservice log and instead add an action to the command pallete to open the log file? I think it achieves the same purpose of easily seeing the sqltoolsservice log. Currently there is no built in way to link a file to a output channel from an extension.

Let's discus the alternatives face to face
Arvind

From: Anthony Dresser<EMAIL_ADDRESS>Sent: Tuesday, August 6, 2019 6:22:27 PM
To: microsoft/azuredatastudio<EMAIL_ADDRESS>Cc: Arvind Ranasaria<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/azuredatastudio] Use vscode log path (#6599)
@ranasariahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Franasaria&data=02|01|Arvind.Ranasaria%40microsoft.com|ee2936695d2c4075b53408d71ad5b5b8|72f988bf86f141af91ab2d7cd011db47|1|0|637007377482642510&sdata=2w7of6NUycnLWkz5l4cQrNOp3PyuyiVLp0O902vFj8s%3D&reserved=0 is it fine if we remove the vscode edit where we add the sqltoolsservice log and instead add an action to the command pallete to open the log file? I think it achieves the same purpose of easily seeing the sqltoolsservice log. Currently there is no built in way to link a file to a output channel from an extension.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fazuredatastudio%2Fpull%2F6599%3Femail_source%3Dnotifications%26email_token%3DAJ5JMVWBQVIIV2KCPZ5LZHDQDIPVHA5CNFSM4IJPATTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3W46FI%23issuecomment-518901525&data=02|01|Arvind.Ranasaria%40microsoft.com|ee2936695d2c4075b53408d71ad5b5b8|72f988bf86f141af91ab2d7cd011db47|1|0|637007377482652499&sdata=KZTAWSOz264rAG1%2Fxe3g6z0KGi6osp9YrGeP7YDDuRU%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ5JMVW2UYFVDCBVDI6SNFDQDIPVHANCNFSM4IJPATTA&data=02|01|Arvind.Ranasaria%40microsoft.com|ee2936695d2c4075b53408d71ad5b5b8|72f988bf86f141af91ab2d7cd011db47|1|0|637007377482662498&sdata=xu0QCT1PLTfBwGF5cg6og4moSsvI8I2mPWJonOa3sMw%3D&reserved=0.


Feat/game on sui

This pull request has been deployed to Vercel.

Latest commit:
5cbc9bc

✅ Preview:
https://sui-bootcamp-2024-nt84rqffy-vbi-academy.vercel.app

🔍 Inspect:
https://vercel.com/vbi-academy/sui-bootcamp-2024/4zeT5oW6xSj3YmEEjPQN1FE3bjLv

View Workflow Logs


1.7.2 bugfix

step hook times are now considered in step time

Codecov Report

Merging #137 into master will increase coverage by 0.71%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #137      +/-   ##
==========================================
+ Coverage   91.47%   92.19%   +0.71%
==========================================
  Files          56       56
  Lines        1232     1242      +10
  Branches      118      120       +2
==========================================
+ Hits         1127     1145      +18
+ Misses         61       54       -7
+ Partials       44       43       -1

Impacted Files
Coverage Δ

...in/java/com/trivago/cluecumber/json/pojo/Step.java
95.45% <100%> (+1.33%)
:arrow_up:

...java/com/trivago/cluecumber/json/pojo/Element.java
89.23% <100%> (ø)
:arrow_up:

.../com/trivago/cluecumber/json/pojo/ResultMatch.java
96.42% <0%> (+7.14%)
:arrow_up:

...os/pagecollections/AllScenariosPageCollection.java
97.36% <0%> (+10.52%)
:arrow_up:

...go/cluecumber/rendering/TemplateConfiguration.java
100% <0%> (+15.38%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d046974...20d4140. Read the comment docs.

Codecov Report

Merging #137 into master will increase coverage by 0.71%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #137      +/-   ##
==========================================
+ Coverage   91.47%   92.19%   +0.71%
==========================================
  Files          56       56
  Lines        1232     1242      +10
  Branches      118      120       +2
==========================================
+ Hits         1127     1145      +18
+ Misses         61       54       -7
+ Partials       44       43       -1

Impacted Files
Coverage Δ

...in/java/com/trivago/cluecumber/json/pojo/Step.java
95.45% <100%> (+1.33%)
:arrow_up:

...java/com/trivago/cluecumber/json/pojo/Element.java
89.23% <100%> (ø)
:arrow_up:

.../com/trivago/cluecumber/json/pojo/ResultMatch.java
96.42% <0%> (+7.14%)
:arrow_up:

...os/pagecollections/AllScenariosPageCollection.java
97.36% <0%> (+10.52%)
:arrow_up:

...go/cluecumber/rendering/TemplateConfiguration.java
100% <0%> (+15.38%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d046974...20d4140. Read the comment docs.


Specify ephemeral container on attach rather than driver policy

This PR pulls out just the driver layer changes of #19544 -- no AzureClient changes are included.  It also removes ephemeral container support from webpack-fluid-loader - adding support for customizing the attach call is possible but not worth the effort since we're not investing in that pattern anymore.
This is enough for customers of the @alpha APIs to move to the new pattern while we decide the final shape of the AzureClient portion.
AB#7205

Changes look good to me, as an FRS member working on ephemeral containers. One question though, with the webpack ephemeral flag removal will we still be able to test clicker and other test apps for ephemeral containers? As I understand, these apps are served through webpack.
In any case, we can also just do ephemeral clicker on an older build, or use Zach's fluid-chat app for testing, so it's not a big concern for me. Approved

The best immediate way to do this would be to use ModelLoader with a customized generateCreateNewRequest and urlResolver (matching what was in the draft PR approximately) and then follow the model loader pattern used in the other examples outside the /data-objects subdirectory.  I frequently use /examples/view-integration/external-views as my "trivial" example -- the usage of the TinyliciousModelLoader would be 1:1 with any custom ModelLoader.
Once we have AzureClient exposure, that will probably become the easiest way.


drivers: pcie: Compile pcie.c only in X86

PCIe requires some symbols that are implemented only in X86
architecture like pcie_conf_read. This pr is conditionally compiling
pcie.c only for X86. This condition is not in Kconfig because there is
support to PCIe endpoint drivers.
Signed-off-by: Flavio Ceolin<EMAIL_ADDRESS>

@Abhishek-brcm I'm not a 100% sure about this pr. But it seems that this file should not build in !x86 targets, there are several symbols no defined in other platforms, that was the reason the PCIE_SHELL was broken ...

@Abhishek-brcm I'm not a 100% sure about this pr. But it seems that this file should not build in !x86 targets, there are several symbols no defined in other platforms, that was the reason the PCIE_SHELL was broken ...

Right way should be to have CONFIG_PCIE=y in x86 boards if they want to use PCIE. Drivers should not be tied to architecture.
I am not sure if I understand PCIE_SHELL statement. If you set CONFIG_PCIE=y like I said above (CONFIG_PCIE_ENDPOINT is n by default), PCIE_SHELL will be enabled by default.

@Abhishek-brcm I'm not a 100% sure about this pr. But it seems that this file should not build in !x86 targets, there are several symbols no defined in other platforms, that was the reason the PCIE_SHELL was broken ...

Right way should be to have CONFIG_PCIE=y in x86 boards defconfig if they want to use PCIE. Drivers should not be tied to architecture.
If you set CONFIG_PCIE=y like I said above (CONFIG_PCIE_ENDPOINT is n by default), PCIE_SHELL will be enabled by default.

But if I understood correctly, even if you select CONFIG_PCIE_ENDPOINT this file will be built and it has a lot of calls to platforms specific functions. What is happening is that the linker is discarding these symbols because they are not being used, but if the application try to use it will be a problem.
So if I understood correctly this pcie.c file should be a X86 pcie drivers, correctly ? CONFIG_PCIE is highlevel option to pcie_endpoint and for this "new" x86 driver. Am I right ?
Currently these drivers can be built in any target, for instance you can select CONFIG_PCIE_ENDPOINT for qemu_nios2

But if I understood correctly, even if you select CONFIG_PCIE_ENDPOINT this file will be built and it has a lot of calls to platforms specific functions. What is happening is that the linker is discarding these symbols because they are not being used, but if the application try to use it will be a problem.

Yes, that is a problem. I noticed the same during https://github.com/zephyrproject-rtos/zephyr/pull/26573. This has to be addressed. If any application/driver tries to use it, it will cause linking failure- that's expected behavior, i.e. if it wants to use pcie.c, it has to provide corresponding APIs through arch/SoC/board code - as mentioned in include/drivers/pcie/pcie.h. However, I agree that this has to be handled better way- i.e. pcie.c should not be compiled at all if platform does not intend to use it.

So if I understood correctly this pcie.c file should be a X86 pcie drivers, correctly ? CONFIG_PCIE is highlevel option to pcie_endpoint and for this "new" x86 driver. Am I right ?

pcie.c file generic for all devices wanting to use PCIe RC, not only for x86 pcie. Let me have a look for better way to handle this as I explained above.

we can go back to having PCIE and PCIE_ENDPOINT completely independent

Yes PLEASE do this.
We'll cross the bridge when we get there if and when we end up having common code (lots of ways to solve this, it can be library code discarded by gc-sections if not used)

we can go back to having PCIE and PCIE_ENDPOINT completely independent

Yes PLEASE do this.
We'll cross the bridge when we get there if and when we end up having common code (lots of ways to solve this, it can be library code discarded by gc-sections if not used)

That sounds good to me. Just opened this pr to address the problem and was not sure about how to do it ;)

we can go back to having PCIE and PCIE_ENDPOINT completely independent

Yes PLEASE do this.
We'll cross the bridge when we get there if and when we end up having common code (lots of ways to solve this, it can be library code discarded by gc-sections if not used)

okay, will make the 2 completely independent. However, isn't current implementation fine from this point of view? Linker is currently taking care of discarding pcie.c symbols and will throw up error if using symbols(e.g. pcie_conf_read), but not defining them.

@Abhishek-brcm thanks a lot !


Project actions should only be available if caller is an owner

Project actions that are restricted to owners should only be returned in GET /v1/projects[/:id] if the caller is an owner.

v local project build - Verified fixed (recheck in 0.19.0)

v0.19.2
Verified fixed


Data link has expired

Thank you very much for your work, but the data link has expired. Could you please update it?

Thank for your feedback. We will restore the data link as soon as possible.


Update TPIP schedule

Codecov Report

Merging #99 (ad1c4d2) into main (e267825) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main      #99   +/-   ##
=======================================
  Coverage   96.76%   96.76%
=======================================
  Files           9        9
  Lines        3396     3396
=======================================
  Hits         3286     3286
  Misses         76       76
  Partials       34       34

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Cassette path calculation from function outside of decorator?

[Updated] I would like to calculate the path name of cassettes from a function object as is done when used as a decorator but not using a decorator and retaining access to the built cassette.
What I've come up with is pretty gnarly but I don't see a better way to do it with the current code base (I'm using 1.12.0).
What I've got looks like this:
# conftest.py

sample_vcr = vcr.VCR(
    path_transformer=compose(vcr.VCR.ensure_suffix('.yaml'),
                                                    ensure_prefix('sample_')),
    func_path_generator=compose(strip_test, lambda f: f.__name__),
    cassette_library_dir=str(samples_path() / 'vcr')
)

@pytest.fixture
def vcr_cassette(request):
    f = request.function
    ccd = Cassette.use_arg_getter(partial(sample_vcr.get_merged_config,
                                                                     record_mode='all'))
    fargs_getter = ccd._build_args_getter_for_decorator(f)
    ccd2 = Cassette.use_arg_getter(fargs_getter)
    with ccd2 as cassette:
        yield cassette

# test_vcr.py

def test_vcr_fixture(vcr_cassette):
    assert vcr_cassette is not None
    assert hasattr(vcr_cassette, 'responses')
    import requests
    assert requests.get('http://httpbin.org/headers')
    assert vcr_cassette._path.endswith('sample_vcr_fixture.yaml')

This works, but as you can see, I have to create two instances of CassetteContextDecorator and use the explicitly non-"public" method _build_args_getter_for_decorator.
It seems to me that the work done in _build_args_getter_for_decorator could be done at the end of VCR.get_merged_config, although I have not tested it:
class VCR(object):
    ...
    def get_merged_config(self, **kwargs):
        ...
        path = kwargs.get('path')
        if path:
            merged_config['path'] = path
        return merged_config

to
class VCR(object):
    ...
    def get_merged_config(self, **kwargs):
        ...
        path = kwargs.get('path')
        if path:
            merged_config['path'] = path
        else:
            function = kwargs.get('function')
            if function:
                name_generator = (merged_config.get('func_path_generator') or
                                  self.get_function_name)
                path = name_generator(function)
                kwargs['path'] = path

        return merged_config

(Plus a few other changes, of course.)
I want to do this because I am attempting to make a pytest fixture, rather than using the decorator.
Why bother? Mostly because I don't want to have to import the vcr.VCR instance from conftest.py (or add a local module for helpers).
Upon further consideration, there are several better reasons for making it a fixture:

The fixture can be used by a class, module or globally and generate separate cassettes for every test function.
A fixture explicitly used by a test function would expose the various properties of Cassette that are (or seem to be) provided to make assertions against: all_played, play_count, etc.
A command-line parameter to change the recording mode would be easier with a fixture (probably).

Would there be any interest in pursuing this further or is my use-case too limited?

Upon further consideration and experience actually using VCRpy with pytest, I have come to realize that while my initial motivation was perhaps trivial, not being able to easily use it as a pytest fixture is problematic because I cannot easily mix it with other fixtures, which might themselves make HTTP calls that VCRpy needs to intercept.
Examples:

Testing Celery tasks with the celery_worker fixture, where the tasks themselves make HTTP requests that need to be intercepted. The celery_worker starts a new thread/process, so the VCRpy recording needs to start before the worker is started.
Performing cleanup before and/or after the tests would ordinarily be a fixture, but because I have to use VCRpy as a decorator (or context manager), the best I've been able to do is cleanup in a context manager.

Being able to use the built-in name generation is also essential, because having to explicitly specify the cassette name means that the fixture is not reusable, so I would need a separate fixture for every test.
Now that I've written all this, I'm looking over the VCRpy's own tests, which I see are also written with pytest, I see a potential near resolution: Make a pytest fixture, manually calculate the cassette path from the request fixture and yield the cassette from a context manager:
@pytext.fixture(scope='function')
def my_vcr_recording(request, samples_path):
    cassette_name = calculate_cassette_file_name(request.function.__name__)
    with vcr.use_cassette(cassette_name, cassette_library_dir=samples_path) as cassette:
        yield cassette

What's missing is the implementation of calculate_cassette_file_name, which will be very much redundant with the built-in functionality of path_transformer and func_path_generator. That said, that could be just one compose call with the callables from the two parameters in my example except for the lambda.

I seem to have resolved the problem--I seem to have not realized until a few minutes ago that func_path_generator and path_transformer where somewhat redundant as I was using them; the former being used to extract the function name (to base the cassette file name on) when used as a decorator and the latter being used to modify either the name from the former (when used as a decorator) or the name provided as an argument (when used as a context manager).
If I move my strip_test into the compose chain in path_transformer, I can do away with func_path_generator altogether:
def strip_test(s):
    """Strip a leading 'test_' or trailing '_test' from s."""
    ...

sample_vcr = vcr.VCR(
    path_transformer=compose(vcr.VCR.ensure_suffix('.yaml'), ensure_prefix('sample_'), strip_test),
    cassette_library_dir=str(samples_path() / 'vcr')
)

@pytest.fixture
def vcr_cassette(request):
    with sample_vcr.use_cassette(request.function.__name__) as cassette:
        yield cassette

Now I can use @sample_vcr.use_cassette as a decorator or vcr_cassette as a pytest fixture!


Upgrade d3.js to version 3.5.3

GWT-D3 Official Repo » gwt-d3 #4 SUCCESS
This pull request looks good
(what's this?)


What versioning scheme is micro using (if any)?

I'm asking this because while it does look like semantic versioning, the newest release (v2.0.12) is not conformant. To conform to semver, v2.0.12 should really be v2.1.0 because it introduces new backward-compatible features.
Anyways, please clarify. Thank you.

Micro uses a "lite" version of semantic versioning, where the middle version is only incremented for significant new backwards-compatible features. In the latest release I deemed the new features not significant enough to warrant a new middle version (only some minor options/actions were added).

Okay thanks for the swift clarification!


First startup is sloooow

to install the basic, requires apps and services from the registry takes a long time.
Here are my thoughts on how we could solve this:

Create a way to "pre-install" things (pre populate the Me/node_modules dir?)
Make the registry FASTER (varnish? pay them some money?)

Any other thoughts?

This also results in being able to click over to the CREATE section before dev docs is available.

I added the ability to locally install stuff last night (see email :)
that will totally solve this when first boot speed is important :)
I also set up a fastly.com account today that is a turn-key cdn to
front our registry and aggressively cache, didn't have time to test it
yet!
On Tue, Jan 24, 2012 at 8:08 PM, Simon Murtha-Smith
<EMAIL_ADDRESS>wrote:

to install the basic, requires apps and services from the registry takes a long time.
Here are my thoughts on how we could solve this:

Create a way to "pre-install" things (pre populate the Me/node_modules dir?)
Make the registry FASTER (varnish? pay them some money?)

Any other thoughts?

Reply to this email directly or view it on GitHub:
https://github.com/LockerProject/Locker/issues/623

Jer's tweaks plus a few more I put in 1c6fed90c0c215e4917f8d5f4c3624846b9a85b0 should close this out.  Issues related to using these changes can be a new issue.


Corrected name of an area and fixed major grammatical errors

Codecov Report

Merging #6250 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6250   +/-   ##
=======================================
  Coverage   76.85%   76.85%
=======================================
  Files          47       47
  Lines        9393     9393
=======================================
  Hits         7219     7219
  Misses       2174     2174

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af38d25...47cd778. Read the comment docs.

A good place to start is the "Starter Task" label on our list of issues. Those issues should be fairly self-contained and generally a good place to start contributing.
As to how onboarding a project at the ASF, the process of joining the incubator is very well documented, I would encourage you to read that. Depending on your network, the hardest part may be to find mentors and a champion.

Thanks. @mistercrunch


__toString swallows twig errors

$context['sidebar'] = Timber::get_widgets('sidebar');
Timber::render('template.twig', $context);

The return object of Timber::get_widgets('sidebar') is TimberFunctionWrapper that is passed into main twig template,  which calls the object's __toString which in turn renders a twig subtemplate. When there are some errors inside that subtemplate, twig throws an exception with details about the error. However, because all this happens inside the __toString method, replaces that helpful information with useless
Fatal error: Method TimberFunctionWrapper::__toString() must not throw an exception in /tmp/a0/28/e67cd7e4062ab71579e38606b2ce904d472372c32e272d896153313c4fd5.php on line 0

(More info about this)
I found a nice workaround and adopted it for TimberFunctionWrapper https://gist.github.com/chetzof/3607bceac78ca875341c

@chetzof Is this still something you're actively working on or need addressed? Please respond in two weeks or we'll close this thread?


feat: Add localisation to "Version Info" field on module page

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I used npm instead of yarn sorry


tana: init at 1.0.15

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.
This should also close #291639

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3562

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3613


Release notes

First, thanks so much for such an awesome library!
If possible, could release notes be added when a release is made?
Current:

Suggested example:

Generally I use GitHub releases in my repos, but for this one I'm trying a changelog

@jxnblk Oh cool! Sorry I totally missed that :) Thanks again for all you do!

Not sure if it is hard to do but linking to the changelog from each release might be helpful. Like Prettier does:
https://github.com/prettier/prettier/releases
https://github.com/prettier/prettier/releases


feat: add ut by tongyilingma and fix some error message

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

/kind feature
What this PR does / why we need it:
feat: add ut by tongyilingma and fix some error message
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

@rambohe-ch
other Note

/LGTM


Release Google.Cloud.Domains.V1Beta1 version 1.0.0-beta03

Changes in this release:

Commit ac367e2: feat: Regenerate all APIs to support self-signed JWTs

Created release for Google.Cloud.Domains.V1Beta1-1.0.0-beta03


Build instructions

Very nice library. Thank you for your hard work.
I note that the repository doesn't store a set of import libraries - and when I tried to build against the tip of TimeSpan2 I got numerous errors. Are there any plans to identify the proper dependencies to use when building, or perhaps to store those dependencies in the repo?
Originally posted: 2011-12-19T17:35:23

You can find all the missing assemblies in the TaskSchedulerEditor.zip file in the downloads section. I like the idea of adding them to the source code repository and will look at how I might do that so pulling the code also pulls the dependencies.
Originally posted: 2011-12-20T16:20:44

That's what I ended up using. One thing is that the solution/projects are referencing projects, not binary dependencies.
Originally posted: 2011-12-20T18:49:34


Add files via upload

@AntonyStreet providence.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


[ALLUXIO-1896] test equals and hashCode for options

https://alluxio.atlassian.net/browse/ALLUXIO-1896

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9401/Failed Tests: 16org.alluxio:alluxio-core-client: 11alluxio.client.file.options.CompleteFileOptionsTest.testEqualsalluxio.client.file.options.CreateDirectoryOptionsTest.testEqualsalluxio.client.file.options.CreateFileOptionsTest.testEqualsalluxio.client.file.options.DeleteOptionsTest.testEqualsalluxio.client.file.options.FreeOptionsTest.testEqualsalluxio.client.file.options.InStreamOptionsTest.testEqualsalluxio.client.file.options.LoadMetadataOptionsTest.testEqualsalluxio.client.file.options.MountOptionsTest.testEqualsalluxio.client.file.options.OpenFileOptionsTest.testEqualsalluxio.client.file.options.OutStreamOptionsTest.testEqualsalluxio.client.file.options.SetAttributeOptionsTest.testEqualsorg.alluxio:alluxio-core-server: 5alluxio.master.file.options.CompleteFileOptionsTest.testEqualsalluxio.master.file.options.CreateDirectoryOptionsTest.testEqualsalluxio.master.file.options.CreateFileOptionsTest.testEqualsalluxio.master.file.options.MountOptionsTest.testEqualsalluxio.master.file.options.SetAttributeOptionsTest.testEquals
Test FAILed.

Thanks for adding the tests! Can you resolve the test failures? Otherwise LGTM

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9404/Failed Tests: 1org.alluxio:alluxio-core-server: 1alluxio.master.file.options.CreateFileOptionsTest.testEquals
Test FAILed.

This is cool! I left one question.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9405/
Test PASSed.

@aaudiber thank you for this PR, left one comment ... could we give the lineage options similar treatment (toString, equals, hashCode, and tests)?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9413/
Test FAILed.

@jsimsa sgtm, I'd rather do it in another commit though since this one is already pretty big.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9422/
Test PASSed.

just one minor nit, looks good to me otherwise

@jsimsa done

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9427/
Test PASSed.

Merged build finished. Test PASSed.

LGTM


Presentation and Kahoot Contest for the french community "Hacking France"

This presentation quickly presents crowdsec to the "hacking france" community (about 2000 people).

Then I would like to deploy two dockers to attack and defend with crowdsec - if someone can guide me on the deployment of two dockers I take it otherwise I will manage

and finally a kahoot (multiple questions and answers based on the speed of response) with a reward at stake. Normally, I should have 5 winners and crowdsec should take care of sending the 5 lots by ups from my home (I already have all the lots).

@rr404 can someone from the tech team help Billy with the docker deployment? more details on what he plan to do:

This presentation quickly presents crowdsec to the "hacking france" community (about 2000 people).

Then I would like to deploy two dockers to attack and defend with crowdsec - if someone can guide me on the deployment of two dockers I take it otherwise I will manage

Hello,
Do you want to setup and experience like the one in our sandbox: https://killercoda.com/iiamloz/scenario/crowdsec-setup
Have you tried it yet ?
I'll ask core team to get in touch with you to help set it up


remove tracing deps for integration-tests

https://github.com/near/cargo-near/pull/251/files#diff-ca620c1799a0fbfe846664793344b0d95a4f906636d2fbf307bff69f6ec81849R12-R13

resolved in scope of #263


Use UUID generator instead of database id generator

As suggested in this Camunda document the BPE should be configured to use the StrongUuidGenerator instead of the default DbIdGenerator to allow better performance when executing concurrent processes.

Fixed as part of the v1.3.2 release. Merge into develop via #141 for the 1.4.0 release tbd.

Merged into develop via 586a84a


fetchDepth documentation

fetchDepth string.
Depth of Git graph to fetch.

This is usually "1" in practice, but this document wouldn't help me get there.  Also, what are the range of reasonable string values?  "7"?  "1000"?  a date string?

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

ID: b28abf7f-ecdf-8037-acd9-722690424372
Version Independent ID: b28abf7f-ecdf-8037-acd9-722690424372
Content: steps.checkout definition
Content Source: content/steps-checkout.md
Service: azure-devops-pipelines
GitHub Login: @steved0x
Microsoft Alias: sdanie

Thank you for your feedback. We are migrating this issue to our new documentation feedback system, and closing this issue.
As we phase out GitHub issues for this repository, we encourage you to propose changes using public PRs or submit feedback through our updated control at the top of the page. For more information on our feedback systems, see https://aka.ms/contentuserfeedback.


fix: fix continous deployment docker

Codecov Report

Merging #24 (26bfa89) into main (d20acc0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #24   +/-   ##
=======================================
  Coverage   68.91%   68.91%
=======================================
  Files           4        4
  Lines         193      193
=======================================
  Hits          133      133
  Misses         42       42
  Partials       18       18

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d20acc0...26bfa89. Read the comment docs.


Update to Mojo 24.3.0

There are some incompatible changes in Mojo v24.3

The SIMD.to_int() is changed into int(value)
The constructor of Tensor now takes shape as the first argument
AnyPointer is changed into UnsafePointer

This contains some little changes to keep up with the latest version.

Hi @JuniMay , we just merged another PR that was there for a few weeks. Could you please pull latest changes?
If you still see that PR is needed , feel free to fix conflicts and send it for review. Thanks!

Indeed, it works great! I think this one is no longer needed. I will close my PR. Thank you!


More Project Info

Right now the featured project section just links to Github.
We should have some more information about the projects. Case study/blog post/page about them? It would be awesome to have a few words from the people working on each project, as well as the researcher chiming in. Then some information on the project, what our process was, what went well, what could be improved, and a demo link that doesn't interfere with the real data.
Should we just host that on Medium?

I think MVP for this is a project page with more details about the purpose of the project, who worked on it, who it's for, tech details, etc. Blog posts and case studies can come later.

I think blog posts should come later, and this expanded view on the details of each project can link to to the blogpost rather than the details being the blogpost.


Ruleset rebalance tweaks from Gray Alien

Gray Alien's fixes for SpawnCategories so that there are:

no Wyverns on floor 1
better chance of chestgoblins so that there can be more loot.. but you have to work for it.

Thanks for all the help Jim. Couldn't have done it without you!


Add built-in status Checks

Would be great if Hoist Apps came out-of-the-box with some basic status checks,  to illustrate the concept and indicate that app and status check system functioning correctly

Some ideas from Toolbox:

Current memory usage, as a percentage of Xmx
Longest page load in past n minutes, as per activity tracking

Could also consider:

Something to explicitly test/exercise primary database connection
JDBC connection pool stats, if we can figure out how to get them
A look at new built-in health status checks provided by Grails5/spring-actuator (more of a research project - I would not block this ticket on understanding what we can do here, but interesting to look at some point - see https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html#actuator.endpoints.health)

Also:
LDAP Service is responding

Jacob H already completed this.  Score!


Fix duplicate marker name check logic for MarkersState.addMarker

Issue described here: https://github.com/TesteurManiak/map_controller_plus/issues/13
Fixed logic here by doing a containsKey check on _namedMarkers to determine if we need to replace vs add the marker.
I also removed the marker parameter from _markerAt which was not being used in the method at all.
Tested this by ensuring that icons were being properly added and removed by calling addMarker and removeMarker

Hi @TesteurManiak if you have a chance could you take a look at this PR? No rush though, and thank you for this package it's been a big help since the original map_controller was archived :)


links to KEGG and FIGFAM in gene landing page from private genome rewrite page...should open new page

Started here

and when I clicked on FIGfam or Kegg it overwrote the page.  I hate that.  Just saying.

I thought the rule underlying is that open a new window if it goes outside PATRIC, replace current page if it is PATRIC page.
But, as we discussed, we can change it if it disrupts the workflow.

Harry, please open both kegg and figfam links in a new tab.
-Maulik

fixed and available on beta.


AggregateException (PNP version installed: 3.22.2006.2)

PS C:\sp-starter-kit\provisioning> Apply-PnPTenantTemplate -Path .\starterkit.pnp                                       Apply-PnPTenantTemplate : Mindestens ein Fehler ist aufgetreten.                                                        In Zeile:1 Zeichen:1                                                                                + Apply-PnPTenantTemplate -Path .\starterkit.pnp

  + CategoryInfo          : WriteError: (:) [Apply-PnPTenantTemplate], AggregateException

+ FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Provisioning.Tenant.ApplyTenantTemplate

Do you have english available within this tenant? Also, would you please enable debug logging in PS and forward that along? Lastly, please pull the latest master branch / download the latest project. We recently pushed a few bug fixes to address a few common issues that have been reported.
Also, I had problems installing the kit with PnP PS version 3.22.2006.2. I suggest removing all versions of SharePointPnPPowerShellOnline on your workstation, then installing April 2020 release as a test (3.20.2004.0) i.e.
Install-Module -Name "SharePointPnPPowerShellOnline" -RequiredVersion 3.20.2004.0

Yes english is available in the tenant now. I followed your instructions and it worked! Thank you so much! I can confirm that PnP PS version 3.20.2004.0 solved it for me. I will try to use PnP PS version 3.22.2006.2 and pull the latest project as soon as possible.


Optionally install dependency libraries

All core deps or individual? What about PECL deps?

Core dependency support available as of v0.3 (5c27dff2215363d96ff963fe6d20a7f0772107d6).
PECL dependencies not yet supported, though.

Quick question: is there a way to get a full list of recent Windows compatible PECL dependencies? https://windows.php.net/downloads/pecl/deps/ looks hilariously outdated.

https://windows.php.net/downloads/pecl/deps/ looks hilariously outdated.

Indeed, but this is the latest we have. Unfortunately, none of the PECL deps builds have been automated so far (well, a few are in https://github.com/winlibs/winlib-builder), so updating might take considerable time.

There is a simplistic build script for imagemagick: https://github.com/winlibs/winlib-builder/blob/master/.github/workflows/imagemagick.yml.
Other than that, a serious issue with the PECL deps is that there are no series files; this should better change.

From what it looks to me as an outsider (a php user who prefers to code on a native Windows environment) is that native Windows builds other than core have very low priority or don't even exist; and now with Windows having a Linux subsystem that can run Linux extensions, i get the feeling that native builds for Windows will be abandoned entirely in the foreseeable future. So i get it why the PECL directories are outdated...

This GH action is superseded by https://github.com/php/setup-php-sdk. Please report any issues there.


Typo in fish setup

Describe the bug
I believe this line should be
if test -n "$XDG_CONFIG_HOME"

Thanks! I've just merged a fix for the issue


[piwheels], filter out versions with no files

Refs conversation in https://github.com/piwheels/piwheels/issues/216#issuecomment-1061178476
Only include versions which have >=1 compiled wheels.

Warnings

:warning:
This PR modified service code for piwheels but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against 064c486667e4d05be0e4c6aa374e9b0b8570133d


Committing dob_mismatch screen only. Routing to be added later.

Adding screen.
Tests to be carried out during routing story.
https://companieshouse.atlassian.net/browse/IDVA3-2287

CI: Security warnings found!

CI: Security warnings found!

CI: Security warnings found!


Spike - Can we make the debugger work with "-i" flag in args

See if we can make the debugger work by passing "-i" in the args field on launch.json

Hi 👋 I'm closing issues for housekeeping week.

We haven't talked about this in a while, so I'll just close it. I can open a new one if/when this becomes of interest again 😊


feat: update old version of prettier package

Current version of Prettier npm package is pretty old.

nice catch there

yes a little update is needed


Develop

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

-6 of 54 (88.89%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+3.6%) to 64.808%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

aws_message/crypto.py
18
24
75.0%

Files with Coverage Reduction
New Missed Lines
%

aws_message/crypto.py
2
67.05%

Totals

Change from base Build<PHONE_NUMBER>:
3.6%

Covered Lines:
320

Relevant Lines:
471

💛  - Coveralls


15.11-stable, Restore unavailable

The entrypoint.sh script currently does not include any available restore methods. Having a restore method is essential for server migration purposes.
If you attempt to perform a migration from a container using the shell command docker compose exec gitlab sh, you may encounter the following error:
Backup::Error: gitaly-backup binary not found and gitaly_backup_path is not configured

This error occurs because the GitLab main image does not include the gitaly_backup binary from the gitaly image, which is required for the restore process.
Please note that in the prepare_dirs() method, the following directories are also required for installation during the restore scenario:
/home/git/gitlab/shared/terraform_state
/home/git/gitlab/shared/packages

I've never used the restore feature of gitlab, so I'd have to look into how to support that.

I have a makeshift solution
Dockerfile
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,7 +1,9 @@
 ARG ALPINE_VERSION
 ARG RUBY_VERSION
 ARG GITLAB_SHELL_VERSION
+ARG GITALY_SERVER_VERSION
 FROM alpinelinux/gitlab-shell:${GITLAB_SHELL_VERSION} as gitlab-shell
+FROM alpinelinux/gitaly:${GITALY_SERVER_VERSION} as gitaly

 FROM ruby:$RUBY_VERSION-alpine$ALPINE_VERSION

@@ -10,6 +12,7 @@ ENV GITLAB_VERSION=$GITLAB_VERSION

 COPY overlay /
 COPY --from=gitlab-shell /home/git/gitlab-shell /home/git/gitlab-shell
+COPY --from=gitaly /usr/local/bin/gitaly-backup /usr/local/bin/gitaly-backup

 RUN setup.sh

Taskfile
--- a/Taskfile.yml
+++ b/Taskfile.yml
@@ -119,6 +119,7 @@ tasks:
     deps:
       - .build-args
       - build-gitlab-shell
+      - build-gitaly
       - deploy-libs-gitlab
     sources:
       - build-args.env
@@ -150,6 +151,7 @@ tasks:
       - build-args.env
       - gitaly/*
       - gitaly/**/*
+    run: once
     status:
       - docker image inspect {{.GITALY_IMAGE}}
   save-image-gitaly:

docker-compose.yml
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -9,6 +9,7 @@ services:
         - RUBY_VERSION
         - GITLAB_VERSION
         - GITLAB_SHELL_VERSION
+        - GITALY_SERVER_VERSION
     hostname: ${GITLAB_HOSTNAME:-gitlab}
     restart: always
     ports:

But there is problem with tar utility. While gitlab restores data it fails
rake aborted!
Backup::Error: Restore operation failed: tar: unrecognized option: unlink-first
BusyBox v1.35.0 (2022-08-01 15:14:44 UTC) multi-call binary.

Usage: tar c|x|t [-ZzJjahmvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [LONGOPT]... [FILE]...

Create, extract, or list files from a tar file

	c	Create
	x	Extract
	t	List
...

But if install full version of tar (add to setup.sh)
# add runtime dependencies
apk add --no-cache --virtual .gitlab-runtime \
        tar \
        git \
...

than build image fails
#0 802.0 Extracting libxml2-2.10.4.tar.xz into
#0 802.0 tmp/x86_64-pc-linux-musl/ports/libxml2/2.10.4... ERROR, review
#0 802.0 '/usr/local/bundle/gems/nokogiri-1.14.3/ext/nokogiri/tmp/x86_64-pc-linux-musl/ports/libxml2/2.10.4/extract.log'
#0 802.0 to see what happened. Last lines are:
#0 802.0 ========================================================================
#0 802.0 tar (child): xz: Cannot exec: No such file or directory
#0 802.0 tar (child): Error is not recoverable: exiting now
#0 802.0 tar: Child returned status 2
#0 802.0 tar: Error is not recoverable: exiting now
#0 802.0 ========================================================================
#0 802.0 *** extconf.rb failed ***
#0 802.0 Could not create Makefile due to some reason, probably lack of necessary
#0 802.0 libraries and/or headers.  Check the mkmf.log file for more details.  You may
#0 802.0 need configuration options.
#0 802.0
#0 802.0 Provided configuration options:
#0 802.0 	--with-opt-dir
#0 802.0 	--without-opt-dir
#0 802.0 	--with-opt-include

This is some kind of mystery. May be You know how to resolve this?

You need to install xz as well  to be able to unpack tar.xz

Yes, it works


Rename PartialTagHelper asp-for to for.

#7379

Don't think any of our templates use partial + asp-for, but do scan Identity, Templating and MusicStore for reaction PRs

Checked those repos and looks like we're clear 👍


Include relative path of scenario in report

fixes #347
This looks like a lot of files but that's mostly because I added another field to be captured in run-details.json for feature tests so had to update all the expected files.
This is what the report looks like for the feature test I added:

That test that fails in Travis passes locally 😢

@MykolaGolubyev the test that fails in Travis passes locally.  It looks to me like the order of file traversal somehow differs between my Mac and Travis' linux boxes, either an OS or JVM version difference.  One possible fix would be to deserialize scenarioDetails into a set rather than a list or sort it.  Any other ideas/thoughts?

Scenarios themselves should be a list since order must be guaranteed. Is the problem with files resolved in different order?

Is the problem with files resolved in different order?

Yes.  Maybe a better solution would be to sort the files we discover?

@tsiq-karold sorting files may be not idea as there could be a reason user wants a specific order without using *. You already have containerId captured, so maybe we can sort by that before comparison?


What is the akashjs equivalent of provider-services lease-status

Hiya, trying to write a script in akashjs that gets the URIs for a lease. As a reminder the Akash CLI invocation for this looks like:
provider-services lease-status --dseq $AKASH_DSEQ --from $AKASH_KEY_NAME --provider $AKASH_PROVIDER

Which returns a response like this:
{
  "services": {
    "web": {
      "name": "web",
      "available": 1,
      "total": 1,
      "uris": [
        "rga3h05jetf9h3p6dbk62m19ck.ingress.ewr1p0.mainnet.akashian.io"
      ],
      "observed_generation": 1,
      "replicas": 1,
      "updated_replicas": 1,
      "ready_replicas": 1,
      "available_replicas": 1
    }
  },
  "forwarded_ports": {}
}

However, the get_lease_status.ts example does not return any services information at all. There is a function in the create_deployment.ts example called queryLeaseStatus which I thought would do the job, but that doesn't seem to work either - I get an UNABLE_TO_GET_ISSUER_CERT every time. Is there a third method I should be trying?

Hi, I believe this example this is the example you're referring to? https://github.com/akash-network/akashjs/blob/5db497dfcc23bd7982ef90864a780eea2220ab85/examples/create_deployment.ts#L244

Yeah that's the one. Always returns UNABLE_TO_GET_ISSUER_CERT for me.

Closing this because it's actually a bug in the node:https API in Bun! For anyone who cares, here's the issue: https://github.com/oven-sh/bun/issues/8616

@debrisapron Thanks for the clarification! Can't wait for bun to be on feature parity with node.


Better search experience and more accurate results

Problem context:

Wox's search mechanism uses character matching- in a given query string "sql" matching with program title compare string "Microsoft SQL Management Studio" scenario, the match fails for 'Regular' search precision level. This is due to 'RawScore' obtain as 26, not enough to make the Score required for 'Regular' search precision level of 50.

Searching for results that may contain partial words such as "term" should return "Windows Terminal' without having to type in "Windows Te".

Just an overall more nature searching experience while retaining the capability of using character search as well.
Also fixes issues https://github.com/jjw24/Wox/issues/84 & https://github.com/jjw24/Wox/issues/92

@jjw24 something feel wrong about that change and the code of fuzzy match seems a little broken, also when i tried to take the changes (manually because honestly I wasn't able to take the same branch and clone it [I'm still a git novice)) not all the tests worked.

With the tests in this PR I haven't had the time to update them yet, so expect a couple to fail.
A good git client that will help you learn is GitKraken I'd recommend it.
Do you mean the changes in this PR feels wrong?Could you be more specific please.

Mainly performance wise but also order of the words won't matter now and some of the code become obsolete (with previous PR) - I will open a PR that we can maybe both work on?

hmm usually linq performance and side effects are called in to question when using it in EF, shouldn't be too much of a problem for an application like this.
Happy to both work on a PR, lets what can be cooked up.

Reworked in PR https://github.com/jjw24/Wox/pull/112


Candidates for a modern video codec suitable for both playing and recording

The same way we have support for some modern formats like WebP and CRN alongside the legacy TGA format, we may want a modern codec alternative for playback and recording.
The usages
The Unvanquished game (including community content) has two usages:

videoMap playback on in-game surfaces.
Video recording of demos.

Dæmon-based games may have a third usage:

Cinematic playback.

What we have
videoMap playback is on a road to be working again with legacy RoQ format, with legacy limitations (max size being 256×256, no keyframe), see:

https://github.com/DaemonEngine/Daemon/pull/954

Video recording of demos writes AVI files with MJPEG video codec and no sound.
Cinematic playback was removed as it was broken, see

https://github.com/DaemonEngine/Daemon/pull/391

The OGM+Theora+Vorbis format was removed at the same time as it was broken and unsafe.
So we currently have code for:

RoQ as playback (videoMap)
AVI+MJPEG as recording (demo).

Candidates
We need a format usable for both playback and recording, it's better if it's not already obsolete and won't be in a short time, it's especially better if the codec has very high chance to live for very long and be like the codec for the next generations, because we don't want to maintain a modern codec alone, and we don't want to drop support in the future to data (maps, etc.) we may produce today.
It is considered good if the format is usable for both playback and recording, to limit the amount of libraries to deal with.

WebM+VP9+Opus: Matroska container with VP9 video codec and Opus audio codec.
WebM+AV1+Opus: Matroska container with AV1 video codec and Opus audio codec.

It looks like both MP4 and WebM are used out there for AV1, maybe WebM+AV1+Opus is a good way to go fro AV1.
It's possible to use other audio codecs than Opus with AV1 but Opus is good enough and widely used with videos and is a very good candidate for accompanying AV1. We already support Opus in the engine and use Opus with the game.
AV1 is meant to replace VP9 so it's probably a good idea to directly jump to AV1.

Should recording be a priority? There are already lots of tools to record games, most of which will do the job better than if we implemented something in the engine... there's already OBS (or even ffmpeg screenrecording...)

Not a priority. As you said, ffmpeg, OBS or even SimpleScreenRecorder do the job well.
@slipher mentioned this video recording usage recently so I mentioned it too.


samples: add no-timers configuration which is runtime tested

Add no-timers configuration to sample.minimal to check that it's actually working in runtime.
This is added as a test case for issue fixed in #59704

LGTM, but would like @nashif to take a look


There is a plan for R version?

He guys, I would like to know if there is a plan to have this great tools for a R software.
Tks

Hi @TuSKan,
We don't currently have plans to rewrite Featuretools in R. It does seem that there are packages available to call python functions and scripts. If that's something you're interested in you should definitely try it out. Let us know if you get stuck on Stack Overflow with the featuretools and R tags.
I'm going to close this issue for now.

There is a new R wrapper out there: https://github.com/magnusfurugard/featuretoolsR


eslint needs updating to v9

Currently other TypeScript dependencies haven't updated to support v9 yet, so we are blocked. See https://github.com/eslint/eslint/issues/18391
I believe once @typescript-eslint/eslint-plugin and @typescript-eslint/parser release v8, this should be unblocked.

Fixed via #758


Add a method on Compress to dynamically update compression level.

I don't know if this is possible, but it'd be nice if I could reuse Compress at a different compression level.

I think ZLIB has deflateParams for this, but I can't find any equivalent in miniz[_oxide].

Oh nice! I think this'd also be fine as a zlib-only feature


Need log format for my nginx log

Hi,
Please find my nginx log below.
0.001 0.001 [23/Jan/2017:04:06:22 -0800] GET /app/ajs/xxxx.js HTTP/1.1 304 0 "hostname" "https://refererurl" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" "-" 988 - 10.x.x.x -  4710110 31 10.x.x.x -

Can you please post which field is which? Thanks.

hi Allinurl,
This is the log format,
log_format  main  '$request_time $upstream_response_time [$time_local] $request $status $body_bytes_sent "$host" "$http_referer" "$http_user_agent" "$gzip_ratio" $request_length $http_client_ip $remote_addr $remote_user  $connection $connection_requests $upstream_addr $upstream_cache_status';

This does it:
log-format %T %^ [%d:%t %^] %m %U %H %s %b "%v" "%R" "%u" %^ %^ %^ %h %^
date-format %d/%b/%Y
time-format %T

Closing this. Feel free to reopen it if needed.


Background color gets lost when clock displayed on dashboard

Have a countdown clock on one of our dashboards with a custom background color (red), but when switching back and forth between dashboards or refreshing a dashboard the background color is lost. When I first set the background color it works as expected, but then when I come back to the dashboard the panel does not display the custom color (editing the panel does show the color is still selected).
Used the Grafana CLI to install the plugin, and the package.json shows version 1.0.0 in grafana-clock-panel.

Confirmed. Thanks for the report.

Fixed by this commit and a new version, 0.0.7 released.
This fix depends on a change to Grafana which will be released with the new beta so it won't work straight away. I had another fix that would work right now but using the new panel-initialized event (thanks @torkelo for adding it!) is much cleaner.


:memo: Existing database tutorial for ASP.NET 5

Staged at http://ef.readthedocs.org/en/staging/getting-started/aspnet5/existing-db.html


Updated CODEOWNERS for Batch service

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/check-enforcer override


Added CoPilot to example implementations.

This is a version of AdminLTE that makes it easy to use Vue.js. It has been catching good traction. Would be honored if it were included in the implementation section of the documentation.

You have to add this line in documentation/build/include/implementations.html. Otherwise, it will be overridden by Grunt-include.
Thanks!


MNT: Unify command line and Python API command name

Previously, I would have needed to import the main command of
this extension like this in its Python API:

from datalad.api import catalog_cmd

This created a mismatch between the CMD line API (datalad catalog)
and the Python API (catalog_cmd). To resolve this mismatch
and unify command naming to how it is done in most other parts
of the DataLad universe, this commit changes the Python API
name to 'catalog', such that the necessary import becomes

from datalad.api import catalog

Fixes #115

Yay, nice and easy!


Feat/add translation

I have made the feedback function compatible with translation.

I had mistakenly merged the contents of the main branch, so I did a force-push to undo the merge.


simiki init 添加-y 或 -n 参数

CI部署的时候，卡在创建Dockerfile的问题上
Create Dockerfile? (y/N)
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

或者说可不可以将这个创建dockerfile设置为可选的，包括fabric file
尽管这个可以通过 yes | simiki init 解决，个人感觉不是很友好

好的，我考虑下


[Nginx] make the operation id from Create to CreateOrUpdate

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Hi @JeffreyRichter The change will cause breaking for SDK. Could you help review it?

What is motivating this break? Why is it necessary to break all the SDK customers?

What is motivating this break? Why is it necessary to break all the SDK customers?

@JeffreyRichter this is feedback from F5 who owns NGINX service. They think the method name 'Create' is not very clear to the customers. 'CreateOrUpdate' will be more clear. The SDK was released only a few weeks ago. It won't break many customers.

Azure's policy is to not break customers and this change is gratuitous. Also, a PUT is actually create it replace (not update). You can add text to the documentation that this Create method can also be used to replace the resource.

Azure's policy is to not break customers and this change is gratuitous. Also, a PUT is actually create it replace (not update). You can add text to the documentation that this Create method can also be used to replace the resource.

@weidongxu-microsoft @ArcturusZhang @tadelesh @qiaozha What's your opinion about the potential breaking for SDK?

Java SDK is in preview, also we wrap the "PUT" method so it does not break in this particular case (after this change, SDK would add an "update" code flow https://github.com/azure-sdk/azure-sdk-for-java/pull/2115/files#diff-d229328808a3fcca9ddd38b48a57d48c8bf0fb8e83d01840dc51817fe6105be0).
Since there is no PATCH method on this certificate resource, the rename kind of make sense. Though the only justification of the change would be that it only affect SDK and SDK only released a few months back.

I'm curious: How many months does an SDK have to be available before we would decide not to break customers?

Maybe it is backend's responsibility to show from ARM telemetry data that none of the GA SDK ever called the endpoint in question (aka, "PUT" to "/providers/Nginx.NginxPlus/nginxDeployments/{deploymentName}/certificates/{certificateName}")?
ARM data has userAgent, so it should be possible and not hard.

Hi @ArcturusZhang @qiaozha Please help review SDK breaking

@JeffreyRichter Regarding it will cause Go major version pump, could you help to approve?

Do we have to make this change? What if this function was always called Create she we just change the documentation to say that it can also update?
By the way, PUT means create or replace while PATCH means create or update.

Do we have to make this change? What if this function was always called Create she we just change the documentation to say that it can also update?
By the way, PUT means create or replace while PATCH means create or update.

Hi @JeffreyRichter
I think the main goal for this PR is to make our operation naming convention consistent - for example, in our PUT config API, we have "CreateOrUpdate" operation ID while we have "Create" in PUT deployment/certificate. This will cause inconsistent SDK user experience.
The service is going to GA in Nov, while the SDK has not been announced so that we don't expect much customer impact.

OK then. I approved this because no customers would actually be broken since no SDKs were ever produced.

Approved for Go SDK breaking. The package [sdk/nginx/armnginx/v1.0.0](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/nginx/armnginx) seems not imported by any other libs yet.


[Task]: Signup form visible to invited users

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks

Disable signup form for invited users, so they can go directly to their intended task

Closed due to duplicate issue
https://github.com/appsmithorg/appsmith/issues/13549


Add habitica API

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Reopened previous PR. There were conflicts because of auto-formatter. Now it's clear


Get focusable ancestor/get non-navigable focusable nodes

Adds function getPreviousFocusableAncestor which returns the nearest focusable ancestor of a given node.
Updates isFocusable to optionally return true if a node is focusable, but not keyboard navigable (ie, tabindex="-1".

Looks good!


Shotguns fix

Description
Add a different application of shotgun spread to each bullet when fired.  The shotgun fires like it's a machine gun and there's no fixing it.  (Perhaps I did not see something, but even with the standard setting it is so)
Configuration
My_Feature:
  Feature_Option: <true/false>
  Other_Option: <amount>
  etc.

Payment (optional)

[ ] I'm willing to pay for this feature

Use discord for support.
All projectiles fire have different spread and you can use things such as delay between shots to prevent shotgun spam

^ that was meant to fix #299


remove storage

update description for app-dir
check for and create app-dir
remove storage resource
fix perms token
import host
modify npm input type to string
fix docstring in for app-dir

were able to do a new charm without these changes?

@battlemidget no .. I can't get the legacy storage to work for the life of me.


[Event Request] Table 83 Item Journal Line - OnAfterGetLocation

Hi Team,
In table 83 we need possibility to replace standard code with our own. Having event at the end of the procedure GetLocation would help us to have more checks before getting the correct Location as a record:

    [IntegrationEvent(false, false)]
    local procedure OnAfterGetLocation(var Location: Record Location; LocationCode: Code[10])

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


annoying clones

sometimes when I'm editing a bin I save a snapshot, and when I come back I type something in the editor, and the bin gets cloned. this is annoying because I want to embed my bins in my website, but if the url changes I have to update it every day.

If you don't own the original (i.e. version 1) bin, then it'll clone the bin. If you do, it won't ever clone unless you tell it to (at which point you'll own version 1 and it won't clone).


Update Tool install old version

Hello,
I was on version 7.2.2 and I press the update tool button. This downgraded me to 7.1.8.

Also seeing this, I just manually grabbed the DAT.exe from the repo and replaced the .exe in the program folder.


Attempting to Subscribe before the connection is fully authenticated caused crash

Problem
In some scenarios, a Consumer fails to startup because it receives a {:error, :stream_not_available} when calling RabbitMQStream.Connection.subscribe/5.
Initially it seemed that this happened when although the tcp/ssl connection would already be open, the authentication process was not yet complete. But later It I found out that it actually happened when attempting to connect to a replica other than the Main for that stream.
Solution
Implement an abstraction on top of RabbitMQStream.Connection that auto-discovers all the nodes and routes each requests based on the defined metadata
Testing
Add replication to the services setup and create related tests.

Reopening this issue as it is still present.

Updated the description with describing the mapped issue after the root cause was found.


[stable/rabbitmq] disable rbac by default

By default, we should not create RBAC resources unless using the values-production.yaml.

/assign @prydonius

/hold

Our current RBAC best practices suggest to enable it by default.

You're right, it is ok that RBAC is enabled by default. Closing this PR


OS X APPDATA

macOS env.APPDATA should be undefined, but cross-env created a 'undefined' string.
this could be better:
if (process.env.APPDATA) {
  envVars.APPDATA = process.env.APPDATA;
}

Would you like to http://makeapullrequest.com ?

I'll try it.


feat(client): add codeally_down feature flag

This adds a codeally_down feature flag to the client which we can toggle on the GrowthBook dashboard.
Also, fix type errors with hotkeys. I was unable to push these changes without the fix.

Test

Add the dev URI to the GROWTHBOOK_URI env var.
Go to the dashboard
Toggle the development feature on
Go to any of the RDB pages to see the alert

can the type PR https://github.com/freeCodeCamp/freeCodeCamp/pull/49830 merge before this, you are fixing the types here as well


Add CI to push a latest git tag for every stable Meilisearch release

Fixes partially #3147.

Add a CI to add/update a latest git tag ONLY when releasing a stable version of Meilisearch (not for pre-release or for custom tag for prototypes)
Update the Docker CI to avoid being triggered when latest git tag is pushed: the CI is still triggered when a git tag is pushed, except for the latest tag.
Reminder: the latest Docker image is already created and pushed when releasing a stable version of Meilisearch. This step is already present in our current Docker CI.

bors merge


[about_lectures] needs to be updated for new context

@jstac the about_lectures page needs to be updated for the new context.
Should this page remain?
https://preview.python-programming.quantecon.org/about_lectures.html

Hi @mmcky, all of this can go --- be deleted --- except for the credits down the bottom.
I'm not sure how we can work the credits in but I think that we should find a way to recognize those who don't have commit histories.  Any ideas?  (CC @DrDrij)

By the way, @sayaikegawa has been collecting names for people to give credit to.
@sayaikegawa, could you please collect the names mentioned above and add them to your list?

I understand @jstac . I'll add names in the credit to my list.

Hi @jstac , This is the name list.
NAMES.xlsx

thanks for capturing the names @sayaikegawa. Would you mind to post that as a overall issue in lecture-source-py issues list?


Add JSON-LD support for all pages

Description
It creates JSON-LD support by adding the json-ld script to the React Helmet. There are 4 main structures:
1.- ArticleJsonLd - For blog posts
2.- WebsiteJsonLd - For index (with integrated searchbox)
3.- AuthorJsonLd - For authors page
4.- WebpageJsonLd - This is the most generic one. Is used in all the rest of pages.
I've checked results with different values at https://search.google.com/structured-data/testing-tool, and I believe is working fine.
For Article the image appears to be a recommended/important field and not every time a post has a featuredImage, so when #13 is solved would be great to include it as the default image for the post in case there is no featureImage.
Fixes #92

this is looking good @GuilleAngulo - a few comments there
its interesting, google's updated rich testing tool (https://search.google.com/test/rich-results) doesnt show anything for categories like https://deploy-preview-93--next-wordpress-starter.netlify.app/categories/lorem/ but it clearly works when testing on the old tool at https://search.google.com/structured-data/testing-tool
i wonder if it specifically only tests and shows rich actions, not general structured data
anyways lookin good

I was checking this last issue you are mentioning, and I think I figured out why: So aparently Google indicates at their guide which structures/features they will considerate in order to show rich results. From the 4 structures, only Article (blog post) and Sitelinks Search box (index) qualify for this. Author and WebPage will have structured data but will be ignore by Google rich results...
Also checking this one I found that logo  could qualify as rich result. Shall I include a logo structure at index page? Would be an interesting default feature?

ah thats interesting
maybe the logo can be an opt-in feature? 🤔  only thinking is right now there's no logo on the site, but maybe i can come up with a simple logo later just for the purposes of having a placeholder image for people to swap in their own, then we can include it in this

Yeah, I will leave the structure of LogoJsonLd() prepared inside the file. So you can use whenever is ready 👍
Just another note: Now the logo is taken like this:
const { homepage = '', faviconPath = '/favicon.ico' } = config;
Because I was not sure where should the logo path come from. So by default is taking 'favicon.ico' or faviconPath property if exists at package.json... Any thoughts?

i think that works for now until we get it set up. thanks @GuilleAngulo

I sent the dates wrong again  ... I think I had a mental block with that part :sweat_smile:. Thanks for fixing!

haha np, didn't wanna bug ya again for the quick tweak


Net::ReadTimeout with 2.5.4, but not 2.5.3

I'm consistently getting a Net::ReadTimeout exception with version 2.5.4. With the same exact configuration but using mail 2.5.3 everything works. I tested this by changing the version number in Gemfile.lock directly (there were two instances), and nothing else.
So, for now, with Rails 3.2.14 and Rails 4.0.1, I change the version number of mail to 2.5.3 in Gemfile.lock when I deploy and everything works fine.
The configuration used with both versions (in config/initializers/mailer.rb)
ActionMailer::Base.delivery_method = :smtp
ActionMailer::Base.smtp_settings = {
  :address                => "mail.domain.net",
  :port                   => "465",
  :domain                 => "domain.net",
  :authentication         => :plain,
  :enable_starttls_auto   => true,
  :openssl_verify_mode    => "none",
  :user_name              =><EMAIL_ADDRESS>  :password               => "password"
}

The backtrace I get with 2.5.4
NOTIFICATION ERROR: Net::ReadTimeout
/usr/local/lib/ruby/2.0.0/net/protocol.rb:158:in `rescue in rbuf_fill'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:152:in `rbuf_fill'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:134:in `readuntil'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:144:in `readline'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:931:in `recv_response'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:554:in `block in do_start'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:941:in `critical'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:554:in `do_start'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:519:in `start'
/var/www/app/shared/bundle/ruby/2.0.0/gems/mail-2.5.4/lib/mail/network/delivery_methods/smtp.rb:112:in `deliver!'
/var/www/app/shared/bundle/ruby/2.0.0/gems/mail-2.5.4/lib/mail/message.rb:248:in `deliver!'
/var/www/app/releases/20131121134619/app/models/notification.rb:25:in `block in daily_summary'
/var/www/app/releases/20131121134619/app/models/notification.rb:8:in `each'
/var/www/app/releases/20131121134619/app/models/notification.rb:8:in `daily_summary'
/var/www/app/releases/20131121134619/lib/tasks/notifications.rake:61:in `block (4 levels) in <top (required)>'
/var/www/app/shared/bundle/ruby/2.0.0/gems/activerecord-4.0.1/lib/active_record/relation/delegation.rb:13:in `each'
/var/www/app/shared/bundle/ruby/2.0.0/gems/activerecord-4.0.1/lib/active_record/relation/delegation.rb:13:in `each'
/var/www/app/releases/20131121134619/lib/tasks/notifications.rake:58:in `block (3 levels) in <top (required)>'
/var/www/app/shared/bundle/ruby/2.0.0/gems/activerecord-4.0.1/lib/active_record/relation/delegation.rb:13:in `each'
/var/www/app/shared/bundle/ruby/2.0.0/gems/activerecord-4.0.1/lib/active_record/relation/delegation.rb:13:in `each'
/var/www/app/releases/20131121134619/lib/tasks/notifications.rake:38:in `block (2 levels) in <top (required)>'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:236:in `call'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:236:in `block in execute'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:231:in `each'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:231:in `execute'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:175:in `block in invoke_with_call_chain'
/usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:168:in `invoke_with_call_chain'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/task.rb:161:in `invoke'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:149:in `invoke_task'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:106:in `each'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:106:in `block in top_level'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:115:in `run_with_threads'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:100:in `top_level'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:78:in `block in run'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:165:in `standard_exception_handling'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:75:in `run'
/usr/local/lib/ruby/gems/2.0.0/gems/rake-10.1.0/bin/rake:33:in `<top (required)>'
/usr/local/bin/rake:23:in `load'
/usr/local/bin/rake:23:in `<main>'

I'm happy to provide more information if needed, and to debug if someone has pointers.
Thanks!

When I try to send mail again and again " Net::ReadTimeout (Net::ReadTimeout) " this error comes . My present mail version is (~> 2.5, >= 2.5.4) , when I tried to change my mail version to  2.5.3 its throughing an load error . My rails version  is 4.2.4 and ruby version is 2.2.1 . Please help me if possible . Thanks


[PT Run] PT Run got an error

While typing a message in MS Outlook, I got a popup entitled "PT Run got an error".
While trying to copy the exception message, I got a further popup that PowerLauncher had crashed and the original window closed.
PowerToys version: V0.20.1
Windows version: 20H2
I've attached the log file.
2021-02-10.txt

@StarNamer you're on 0.20.1  Please upgrade to 0.31.  20 is pretty old in terms of releases.
@enricogior  this however does have same stack trace parts as #9619

Please update and see if it still occurs


Use api-elasticsearch on all calculators-frontend environments

This finishes the work started in #4871 and continued in #4916 to make
the calculators_frontend machines use the api-elasticsearch.api cluster
instead of the elasticsearch.backend cluster.

Flagged as DNM because, just like the precursors, there's a process beyond just deploying a puppet for rolling this out to avoid downtime.

Removed DNM, going to deploy puppet (will disable puppet on the machines we care about on production to follow rollout).


BatchNorm: Make running mean/std estimation optional

Introduce a new constructor argument update_averages. If it is set, then there are no updates to the running_mean and running_std members.
If this change sound good to you, I would get a pull request ready.

Can you provide a use case of when it could be useful to add another constructor to BatchNormalization?
That will help.
Thanks.

When you don't have a test phase, e.g. you only evaluate your model at the end of a long training phase. The running_mean/std can then be estimated during the last epoch. My special use-case are GANs, they don't have a test time.

I don't think that would be widely useful, at least not enough justify inclusion in the codebase. But if it is very easy to add to your own fork of Keras, for your own needs.


Fix symlink to file is not resolved correctly

Implement suggestion described in issue #27848.

Fixes the first exception, but now another appears at a later stage:
Exception has occurred: AssetException
Error with code: [Errno 2] No such file or directory: '../../config.json'
  File "/anaconda/envs/my-workspace/lib/python3.10/site-packages/azure/ai/ml/operations/_operation_orchestrator.py", line 256, in _get_code_asset_arm_id
    code_asset = self._code_assets.create_or_update(code_asset)

however this is beyond my grasp of the code.

Fixed in #27960


There are 5.5 GB more LocalDispatchQuery objects In coordinator's GC stack after a lone time pressure test.

There are more and more LocalDispatchQuery object in coordinator's GC stack after a long time pressure test(6 more hours).
Then the performance of presto will be very low.
So I dumped the hprof file of jvm and I found that there are 5.5 GB more LocalDispatchQuery object.
I am using a presto-hbase connector to fetch data from HBase.
What should I do? Is this a bug of presto?

My presto version is prestosql-312.

@Crossoverrr there was a know memory leak in 312. Could you please redo your test in 315?

Do you mean the #843 "Fix leak in operator peak memory computations" in prestosql-313?

Thank you very much @findepi , I will try that 315.

@Crossoverrr no, not this one. I don't remember which exactly, but you should be good with 315 anyway.
Let me close the issue for now. If you still experience the same memory leak in 315, please reopen.
If you experience some other problem, please create a new issue.
Also, I recommend you join the #troubleshooting channel on Presto Slack (https://prestosql.io/community.html) if you haven't yet joined.
Thanks!

Thanks again!
According to our pressure test results, most of the query scenarios showed a 10% to 20% improvement in performance, which made us very excited!

@Crossoverrr glad to hear that! This is huge!  If you consider blogging about this, let us know (eg link here). We can tweet it further.
Also, I see you joined our slack. Welcome to the community! :)

It's my pleasure to join the presto community ! :)
Yes, if the result is good I will spend some time to write a blog, hahaha.

If you don’t have your own blog or would like to contribute the Presto community blog, its easy, just write some markdown for the post and send a pull request.
https://prestosql.io/blog/
https://github.com/prestosql/prestosql.io

OK. I got it. I will try that as soon as I finished my test on prestosql-315. :)

We didn't found this problem in prestosql-315, and the performance is as good as prestosql-312, thank you all. You are GREAT!     lol


Histogram should be combined for color correction

When color correcting multiple scenes, the histogram only represents the first color correction returned. We should see if it is possible to combine multiple histograms as we go.

Closed by #870


fix(deps): update github.com/tubenhirn/dagger-ci-modules/v2 digest to 985921b

This PR contains the following updates:

Package
Type
Update
Change

github.com/tubenhirn/dagger-ci-modules/v2
require
digest
7a3edc2 -> 985921b

⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the logs for more information.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: ci/go.sum
Command failed: go get -d -t ./...
go: errors parsing go.mod:
/tmp/renovate/repos/github/tubenhirn/doggl/ci/go.mod:7:2: require github.com/tubenhirn/dagger-ci-modules/v2: version "v2.0.0-20230311114427-985921bba436" invalid: go.mod has non-.../v2 module path "github.com/tubenhirn/dagger-ci-modules" (and .../v2/go.mod does not exist) at revision 985921bba436


Python 2 compatibility is broken

The function definition of notify in daemon.py is python 3 format.
https://github.com/mosquito/cysystemd/blob/d9c9a8e7044331cb668b109b36ee82b7117cfda4/cysystemd/daemon.py#L31
Introduced in https://github.com/mosquito/cysystemd/commit/91bf53235b5499da4899570d4968e2674d461e01

python2 is not supported


Inconsistency in query param with array value

Given a route with a query param key that has an array as a value
route('route', ['foo' => ['a', 'b', 'c']])
Laravel's route helper returns /route?foo[0]=a&foo[1]=b&foo[2]=c while ziggy returns /route?foo=a,b,c. When getting the param from the request object it handles it as a string and not an array.
Currently installed Laravel version:
5.7.*
Currently installed Ziggy version
0.6.0

Is there any reason #219 hasn't been accepted yet? Just busyness?
In case it's helpful, I copied the changes locally and confirmed URLs are generated as I expected.

Closed by #228.


Support audio stream

ref #8

In this PR, I added AudioBufferList related functions to screencapturekit-rs.

@all-contributors add

@all-contributors add @tokuhirom

https://github.com/all-contributors please add @tokuhirom Code

@all-contributors please add @tokuhirom Code


Add SparseEfficiencyWarning and warn inefficient comparison

==, <=, and >= are inefficient for sparse matrices (because a.nnz + b.nnz + result.nnz >= row * col).  This PR makes CuPy warn the inefficiency like SciPy does.
cupyx.scipy.sparse.SparseEfficiencyWarning is scipy.sparse.SparseEfficiencyWarning if SciPy is available.  Otherwise, CuPy defines a new warning class for it.  It is similar to the case with numpy.AxisError until #3096.
https://github.com/cupy/cupy/blob/25b68333154c5aa59750fb6a83ef12f7dc0552f7/cupy/core/_errors.py#L4-L5

LGTM!
pfnCI, test this please.

Jenkins CI test (for commit 145eb64edf823d48368627e16766c5a49aba7b80, target branch master) failed with status FAILURE.

LGTM! Test failures are not related to this PR.


I implemented all the code but chromecast button not showing in Vimeo video

Here you can check my implemented code https://dev.strokeinfotech.com/pgvcl/

@udayankoliya For what it's worth, the chromecast button is showing up for me in your demo. Did you make a change to fix the issue you were encountering?

@matthewdickinson Yes, I modified some code and the button is showing now. due to buttonPositionIndex its not showing properly.


[Feature request] Crop image by ratio

Would be nice to have something like cropRatio next to all other image manipulation methods.
Eg. if image is 1800x900 (2:1) calling cropRatio(3, 1) should end up in 1800x600 or (1, 1) - 900x900

Probably something we would look to add when we move away from Gregwar Image library in Grav 2.0.

Can I follow this somehow now that issue is closed or you have some private ToDo list? :)

There is no todo/roadmap for 2.0 currently. That's something we want to work on this year.  We will probably have a public facing issue to track major features/changes though.


NULL is not printed in the resulting table

Hi,
When I used mysql client to connect the SQL server, I got the following table in which there were some empty fields that were supposed to be printed as NULL.
What I got:
$ mysql -h <IP_ADDRESS> -u root
mysql> select * from tbl where timestamp = 3;
+--------------+-----------+-----------+-------------+
| id           | timestamp | col1      | col2       |
+--------------+-----------+-----------+-------------+
| id1          |         3 |           |           3 |
| id2          |         3 |           |           3 |
| id3          |         3 |         3 |             |
+--------------+-----------+-----------+-------------+
3 rows in set (0.51 sec)

What I expect:
$ mysql -h <IP_ADDRESS> -u root
mysql> select * from tbl where timestamp = 3;
+--------------+-----------+-----------+-------------+
| id           | timestamp | col1      | col2        |
+--------------+-----------+-----------+-------------+
| id1          |         3 |   NULL    |           3 |
| id2          |         3 |    NULL   |           3 |
| id3          |         3 |         3 |    NULL     |
+--------------+-----------+-----------+-------------+
3 rows in set (0.51 sec)

It seems to me that in https://github.com/src-d/go-mysql-server/pull/753/files#diff-654bac6a55597b15c4a5d404095b4e69R306, shouldn't we handle both nil and nullT? For example:
if _, ok := v.(nullT); ok || v == nil {
  return sqltypes.NULL, nil
}

I don't think it's related to that PR. nullT is a type, and that function never receives a type, only a value. The value of a nullT type is always nil.
Not printing null is a bug, though.


test: add coverage for new attribute-related items

add tests over the items used to implement the generic attribute system
fix mistakes in implementation highlighted by new tests

Scope

[x] Code: if relevant, add affected target

Type of change

[x] Fix
[x] Testing

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.61%. Comparing base (8775ee5) to head (d6c6724).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #106      +/-   ##
==========================================
+ Coverage   79.79%   81.61%   +1.81%
==========================================
  Files          27       27
  Lines        2861     2910      +49
==========================================
+ Hits         2283     2375      +92
+ Misses        578      535      -43

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


Enable gem package listing

This commit adds commands to base.yml to collect gem packages,
versions, licenses and proj_url information using the gem language
package manager.
When the gem package manager does not have license or homepage
information for a package, it renders as a blank line. Since Tern
requires the number of packages to be the same number of elements as the
list of licenses, we print 'Unknown' as the license or homepage instead
of an empty license or proj_url value.
Works towards #609.
Signed-off-by: Rose Judge<EMAIL_ADDRESS>Signed-off-by: abhaykatheria<EMAIL_ADDRESS>

Snippet of output from running Tern with this PR for rails:latest:
------------------------------------------------

        Layer: 35357a2185:
                info: Instruction Line: RUN gem install bundler --version "$BUNDLER_VERSION"
                info: Layer created by commands: /bin/sh -c gem install bundler --version "$BUNDLER_VERSION"
                info: Retrieved by invoking listing in command_lib/base.yml
versions:
        in container:
        pkgs=`gem list 2> /dev/null | cut -f1 -d' '`
        for p in $pkgs; do gem list $p 2> /dev/null | head -2 | cut -f2 -d'(' | cut -f1 -d')' | cut -f2 -d' '; done

proj_urls:
        in container:
        pkgs=`gem list 2> /dev/null | awk '{print $1}'`
        for p in $pkgs; do proj_url=`gem spec $p homepage | head -1 | cut -f2 -d' '`; if [ -z $proj_url ]; then echo 'Unknown'; else echo $proj_url; fi; done

names:
        in container:
        gem list 2> /dev/null | cut -f1 -d' '

licenses:
        in container:
        pkgs=`gem list 2> /dev/null | cut -f1 -d' '`
        for p in $pkgs; do lic=`gem spec $p license | head -1 | cut -f2 -d' '`; if [ -z $lic ]; then echo 'Unknown'; else echo $lic; fi; done

        Invoking commands from command_lib/base.yml:
                warning: No listing for key copyrights. Consider adding this listing to command_lib/base.yml.
No listing for key srcs. Consider adding this listing to command_lib/base.yml.

        File licenses found in Layer:  None
        Packages found in Layer:  bigdecimal-1.2.8, bundler-1.13.7, did_you_mean-1.0.0, io-console-0.4.5, json-1.8.3, minitest-5.8.5, net-telnet-0.1.1, power_assert-0.2.6, psych-2.1.0, rake-10.4.2, rdoc-4.2.1, rubygems-update-2.6.8, test-unit-3.1.5
        Licenses found in Layer:  ruby, MIT, BSD-2-Clause, Unknown, 2-clause, Ruby
------------------------------------------------


Configure Laravel Passport Authentication

What changed in the app.css file? Diff is too large to display.

@saadj55 can you remove the app.css file please?

Alright

I compared the my branch with master and made them equal. Hope this resolves the issue

awesome, thanks!