Internel Server Error in process renew certificate Let's Encrypt, Wildcard Namecheap

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
When you click to renew the certificate, an internal error occurs.
Certificate is Wildcard in Namecheap.
Nginx Proxy Manager Version
v2.10.3
To Reproduce
Steps to reproduce the behavior:

Go to 'SSL Certificates'
Click on the three points of the certificate that we want to renew and click on the opicon renew now.
See error "Internal Error"

Screenshots
Log error:
[6/14/2023] [7:06:50 PM] [SSL      ] › ℹ  info      Command: certbot renew --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-39" --disable-hook-validation --no-random-sleep-on-renew
[6/14/2023] [7:06:56 PM] [Express  ] › ⬤  debug     Error: Command failed: certbot renew --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-39" --disable-hook-validation --no-random-sleep-on-renew
Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Failed to renew certificate npm-39 with error: Unable to determine zone identifier for domain.net using zone names: ['domain.net', 'net']
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-39/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org.
  See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

Operating System
Docker in Debian.

Hi, it was a false alarm.
I leave here the reason for the problem and solve it in case it happens to someone else (probably to me in a few months when I don't remember). hehehehe
It turns out that the error is caused by a security filter that namechepa has when using the API since they control the IPs of the clients that connect.
It turns out that I was connecting to another ip that was not on the whitelist and that is why the error occurs.
Add the new ip to the whitelist and everything has been fixed.


Enable CI integration

PRs should be checked with a CI tool (e.g. travis, circleci, etc) to avoid pushing breaking changes to master. The api has bundle exec rake command to run tests and rubocop.

Does anyone have a preference for which CI tool we should use?

Java, Python, Protobuf and Service projects are all on TravisCI: https://travis-ci.org/open-telemetry


There is no gap between DEAD and the player's nickname.

Title says it all.

Hmm, for some reason italic text seems to ignore spaces around it

Turns out it was a very small oversight


feat: Adding Dockerfile to simplify development

I want to create a dockerfile to simplify development and also allow folks to run it on their local machine using docker.

I will plan on adding an action to push to our ghcr.io registry in a separate PR.


Add maza ad blocker

This looks good Andros @tanrax.
Merging.

Whoops I acted too soon Andros @tanrax.
The change you make here should be applied to readme_template.md.
Because all the readme files in this repo are auto-generated from the template,

No problem, I will change you shortly


ajax support doc

Need doc update on the gh page.

I'll take a look at getting this added.

@craigweston thanks man. I know the doc is crappy so bare with me. LOL

@lodev09 I created a pull request here for this. Let me know what you think.

Merged! Thanks @craigweston

@lodev09 that escaping problem with & and < issue on the gh page seems to be an issue with the marked library being used.
See here:

Issue 625
Issue 287

yes I noticed that too.. I tried to edit/fix it but it didn't work so it seems like it's an issue with the plugin. I guess will have to wait for an update


Run unit tests on AMDGPU CI

We have two main CI pipelines:

https://github.com/iree-org/iree/blob/main/.github/workflows/ci.yml
https://github.com/iree-org/iree/blob/main/.github/workflows/pkgci.yml

Pipeline overview
ci.yml
The main testing flows for hardware targets are:

build_all -> test_nvidia_a100, test_nvidia_gpu
build_all -> cross_compile_and_test [riscv_64, riscv_32, emscripten]
build_all -> build_and_test_android [moto edge, pixel 6 pro]

The test jobs cover these areas:

Building the runtime from source
Building iree-test-deps

check test .vmfb files for tests/e2e/ like tosa_ops, stablehlo_ops
matmul and convolution test suite .vmfb files

Running unit tests

e.g. iree/hal/drivers/cuda/dynamic_symbols_test, iree/hal/drivers/cuda/cts/cuda_graph_driver_test

Running 'check' and matmul/conv tests

e.g. iree/tests/e2e/linalg_ext_ops/check_vulkan-spirv_vulkan_winograd_input.mlir, iree/tests/e2e/matmul/e2e_matmul_cuda_f32_large_splitk_cuda_cuda

pkgci.yml
This runs a slightly different testing flow:

build_packages -> regression_test_amdgpu_vulkan

At the moment, all of these tests are written in Python and operate using just the package files (iree-compile and iree-run-module binaries, not other C/C++ sources or unit test executable files)
Tests cover these areas:

test_llama2.py and test_ukernel.py from https://github.com/iree-org/iree/tree/main/experimental/regression_suite/tests/pregenerated
Selections of ONNX op tests and PyTorch model tests from https://github.com/nod-ai/SHARK-TestSuite/tree/main/iree_tests

Expanding test coverage
Notice that ci.yml, where unit tests (like the HAL CTS) and 'check' tests (like the matmul test suite) are run, is not running on AMD GPUs right now. The simplest way to fix that will be to add test jobs like test_nvidia_gpu for test_amd_gpu_w7900, test_amd_gpu_mi250, etc. to ci.yml. We could instead expand on pkgci.yml, but the ci.yml setup makes more sense to expand.
A word of warning though - we've been skating around machine availability and reliability issues with our self-hosted w7900 and mi250 runner(s). Pkgci.yml failures do not block merging PRs, while ci.yml failures do. If we want to add tests to the core pipeline, the machines those tests run on need to be reliable at all hours of the day.

We can also include collectives (multi-gpu) tests on the AMDGPU machines. See this discord discussion. The mi250 and w7900 runners both have 4 GPUs.
Enabling multi-gpu testing once we have the baseline jobs might just be a matter of flipping the IREE_MULTI_DEVICE_TESTS_DISABLE=0 environment variable at first. We may instead want per-target filters or more fine-grained labels like requires-multiple-rocm-devices though.
cc @sogartar

This is sort of done and stable. Still needs a dedicated owner though. I'm auditing some of our test suites now and finding areas that are only tested on CPU/Vulkan/CUDA and not ROCm (or Metal, or WebGPU, ...)


Add a flag to specify the cert validity period

The hard-coded default of 10 years works for most applications. However, some applications enforce that the certificate is only valid for a short period and this default is too long.

v20240923


Getting started issue in Windows

Check screenshot it appears after installation.

Are there any related issues?

Bugs
What operating system are you using?
Windows 7
What version of Nylas Mail are you using?
Latest 2.0
Bug?
Do you have any third-party plugins installed? If so, which ones?
No
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
No
Is the issue reproducible with a particular attachment, message, signature, etc?

...

--
Feature Request?
Does this feature exist in another mail client or tool you use?
N/A

I got it working when I disabled my Antivirus.
thanks


Out of memory crash in 0.0.6

This issue is a follow-up to https://github.com/igorshubovych/markdownlint-cli/issues/108
Trying markdownlint-cli2 "**/*" in a project that has a large folder in .markdownlintignore results this output in about 5 mins:
<--- Last few GCs --->

[57132:0x102d52000]   340958 ms: Mark-sweep 2346.6 (2408.0) -> 2348.5 (2399.5) MB, 1070.8 / 0.0 ms  (average mu = 0.113, current mu = 0.028) allocation failure scavenge might not succeed
[57132:0x102d52000]   341633 ms: Mark-sweep 2348.5 (2399.5) -> 2346.6 (2391.3) MB, 675.3 / 0.0 ms  (average mu = 0.070, current mu = 0.000) allocation failure scavenge might not succeed

<--- JS stacktrace --->
Cannot get stack trace in GC.
FATAL ERROR: MarkCompactCollector: semi-space copy, fallback in old gen Allocation failed - JavaScript heap out of memory
 1: 0x1011c2ff5 node::Abort() (.cold.1) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 2: 0x10009fbc9 node::Abort() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 3: 0x10009fd2f node::OnFatalError(char const*, char const*) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 4: 0x1001e3907 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 5: 0x1001e38a7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 6: 0x1003695e5 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 7: 0x1003bd837 v8::internal::EvacuateNewSpaceVisitor::Visit(v8::internal::HeapObject, int) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 8: 0x10039b58b void v8::internal::LiveObjectVisitor::VisitBlackObjectsNoFail<v8::internal::EvacuateNewSpaceVisitor, v8::internal::MajorNonAtomicMarkingState>(v8::internal::MemoryChunk*, v8::internal::MajorNonAtomicMarkingState*, v8::internal::EvacuateNewSpaceVisitor*, v8::internal::LiveObjectVisitor::IterationMode) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
 9: 0x10039acc8 v8::internal::FullEvacuator::RawEvacuatePage(v8::internal::MemoryChunk*, long*) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
10: 0x10039aa06 v8::internal::Evacuator::EvacuatePage(v8::internal::MemoryChunk*) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
11: 0x1003c24ce v8::internal::PageEvacuationTask::RunInParallel(v8::internal::ItemParallelJob::Task::Runner) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
12: 0x10038b7f2 v8::internal::ItemParallelJob::Task::RunInternal() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
13: 0x10038bc78 v8::internal::ItemParallelJob::Run() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
14: 0x10039dfb5 void v8::internal::MarkCompactCollectorBase::CreateAndExecuteEvacuationTasks<v8::internal::FullEvacuator, v8::internal::MarkCompactCollector>(v8::internal::MarkCompactCollector*, v8::internal::ItemParallelJob*, v8::internal::MigrationObserver*, long) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
15: 0x10039daa5 v8::internal::MarkCompactCollector::EvacuatePagesInParallel() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
16: 0x10038ff17 v8::internal::MarkCompactCollector::Evacuate() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
17: 0x10038d92e v8::internal::MarkCompactCollector::CollectGarbage() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
18: 0x10036992f v8::internal::Heap::MarkCompact() [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
19: 0x1003671b5 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
20: 0x100365670 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
21: 0x10037149a v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
22: 0x100371521 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
23: 0x10033f73a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
24: 0x10068e808 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
25: 0x1009d39b9 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
26: 0x1009d488d Builtins_StringAdd_CheckNone [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
27: 0x100a1060f Builtins_RegExpReplace [/Users/me/.nvm/versions/node/v12.18.3/bin/node]
error Command failed with signal "SIGABRT".

Repro steps are the same as in markdownlint-cli2 "**/*" except that the ignored folder is even bigger (354K files distributed across about 6K subfolders)

In version 0.0.6 and later of CLI2, the .markdownlintignore file is no longer used. Because of that, the command line you are giving is telling it to lint every file (Markdown or not) in what you say is a very large directory tree. Eventually this will run out of memory. Could you please try again, either passing the ignore patterns on the command line or using the new ignores option in￼￼ .markdownlint-cli2.jsonc.
If it runs out of memory with a reasonable set of Markdown files, there are some things I can do to try to fix that, but if the only issue here is that it is trying to process huge swaths of other files, that's not a use case I feel is important.￼

Thanks for your reply @DavidAnson, I missed the new rule around .markdownlintignore indeed. Gonna give the CLI another shot in a few days, thanks for clarifying!
Speaking of this trap I fell into, WDYT of emitting a warning of some sort if the number of files to process becomes ridiculously large? Looking at how Prettier handles formatting and linting, there's also scope for refactoring the app so that it emits to std on every processed file and does not hold too much in the memory heap. This way, the tool will be more fault-tolerant and will emit the output as it goes, which will be useful for users. If I started seeing messages like "error in file temp/abc, error in temp/xyz" in my stdout, I'd press ctrl+c without waiting till the tool crashes.
Another random thought: how about checking for .markdownlintignore and showing a warning right at the start if the file exists?

Streaming output would not work with the current implementation of output filters. But maybe it could write some status to stdout by default. Probably just a summary of inputs, then the file count, then a count of errors.
With that in place, it should be pretty clear when too many files are being looked at. I'd rather not introduce a whole warning system just for that one scenario that should only ever happen once to people who are migrating.￼￼

I've added progress to stdout here: https://github.com/DavidAnson/markdownlint-cli2/commit/bb7c4ddf563c549deead9e056b3c2697470eef00
It can be turned off via the noProgress option.
Example output:
Finding: **/*.md
Linting: 3 file(s)
Summary: 9 error(s)

Thanks for your reply @DavidAnson!
I tried 0.0.8 and generally managed to get a fast result without crashing. Removing .markdownlintignore and adding .markdownlint-cli2.jsonc with the ignores section helped here.
Two observations:

When it comes to suppressing progress status, it might be useful to consider different expected behaviours for TTY and non-TTY stdout devices. When we are in TTY mode (local Terminal), it's expected to see the animated progress. When we run a tool in CI, the output that works fine locally may look pretty odd. Context:

https://github.com/prettier/prettier/blob/370844cc4cbe3c43b8e699e3e4bcec215bd94e08/src/cli/is-tty.js
https://github.com/doczjs/docz/issues/597

I'm wondering if the format of ignores entries could support negation itself. This would allow running markdownlint-cli2 for "**/*" and ignores section would exclude all, and then re-include *.md, *.mdx and so on. At the moment, adding something like !*.md to ignores produces !!*.md and not *.md.

Since the above observations are not related to the out-of-memory crash, feel free to close this issue 🙂

Great, thank you, I will close this! By the way, I made a couple of other refactorings intended to avoid unnecessary memory pressure. They will be in the next release.
Regarding your point about progress, note that the kind of progress used here is not the fancy kind that updates the same line in the console or anything like that. It just outputs three lines of plain text at the relevant parts of execution. And they can be turned off entirely if wanted.
Regarding double negation in the ignores property, I'm afraid that might get confusing. Remember that ignores are applied after the original globs from the command line, so they can not add back in files that were excluded there. They could add back in files that were excluded by the ignore pattern itself, but I'm afraid trying to explain and understand that might be difficult. I'm going to wait and see if this becomes an issue for users.

Commit referenced above: https://github.com/DavidAnson/markdownlint-cli2/commit/3404146adb570177d9c0f76766e15701941a543f


Flagsmith open feature provider

Hi!
I created a PR for open feature provider implemetation https://github.com/open-feature/dotnet-sdk-contrib/pull/89
Can somebody from Flagsmith make a review to be sure that this is right using of Flagsmith sdk?
Thanks :)

Thanks @vpetrusevici - I have added a review there. I will go ahead and lose this issue and we can continue the conversation on the PR thread. Thanks again for submitting the PR, really appreciate it!


Printing a struct after casting, prints the (additional) fields of the original struct.

Consider below program
function main (string[] args) {
    Student s = {name:"John", age:30, gpa:3.78};
    Person p = (Person) s;

    // printing Person. Should only print two fields
    println(p);
}

struct Person {
  string name;
  int age;
}

struct Student {
  string name;
  int age;
  float gpa;
}

But when we print after casting, it prints all three fields (see below).
{name:"John", age:30, gpa:3.78}

The underlying issue is that the type of the struct value remains unchanged as Student at runtime, even though it is casted to Person. Hence the struct to string conversion (during println) occurs assuming that the struct type is Student.
This is the same root cause for the issue #4253

The new syntax is as follows
import ballerina/io;
function main (string... args) {
    Student s = {name:"John", age:30, gpa:3.78};
    Person p = <Person> s;

    // printing Person. Should only print two fields
    io:println(p);
}

type Person record{
  string name;
  int age;
};

type Student record{
  string name;
  int age;
  float gpa;
};

This is not an issue. The reason being that, whatever the conversion, the storage type remains the same as the original type before any conversion. A conversion does not change the storage type and hence if we do a print, it will print the storage value.


No separator characters should be possible

When disabling all separator characters, all except the last two are restored to being selected. I expect no separator between words.

Needed to set empty_values: [] in call to Ecto.Changeset.cast/4.
Also, :separator_character may not be listed in validate_required. Doing so bypasses the cast exemption for empty_values and forces the default value to load.


Make navbar of pages more responsive for smaller screen #182

Click on the image for the video (it was big in size)

Resolved the issue #182

Used Popover from Shadcn UI
Added some steps in Readme file that I felt were necessary
If necessary, I can change the exit Popover after select feature.

Someone has already solved this.
You're free to solve the issue on your own, but please avoid raising a PR if there is already a PR which is going to be merged. (ref #205)
It gets difficult for the maintainers if there a lot of duplicate PRs.

Sorry 😔


Add aria timer role

What Changed
Added the ARIA: timer role in react-snippets and Readme (#16 )
Why
Todo:

[ ] Add Semantic Version Label
[ ] Add tests
[ ] Add docs

closes(#16)


Fitsnap: Unknown dependency

https://github.com/pyiron/pyiron_potentialfit/blob/1db95608d5ec4ea80c1e99a3beecbe3a77287480/pyiron_potentialfit/fitsnap/common.py#L2
@mgt16-LANL @jan-janssen It seems the fitsnap job class depends on a pybispectrum module that I can find neither on PyPI or conda.  Is this code still maintained?

That was one of y developments, the function is:
def calc_bispectrum_names(twojmax):
    lst = []
    for j1 in range(0, twojmax + 1):
        for j2 in range(0, j1 + 1):
            for j in range(j1 - j2, min(twojmax, j1 + j2) + 1, 2):
                if j >= j1:
                    lst.append([j1 / 2.0, j2 / 2.0, j / 2.0])
    return lst


CARDS-1596: Text/Print exports expose data that shouldn't be accessible

To test:

log in as admin
create a new Patient Information with login credentials
create a new Visit Information with a visit date in the future
create new data forms
generate a token for the visit
in a private browsing window, log in with the token
fill in the forms, submit
back as admin, make sure the score and interpretations are correct
copy the URL for each form, remove the content.html, append .deep.json or .txt or .md and open them in the patient's private browsing session
make sure the scores and interpretations are not present for the patient

tested in the dev branch after merge - all good!


[Feature]: Better support for CI and local development

Does the upstream have similar features?
playwright-go is just a community-driven client for playwright. For feature requests, please refer to other officially supported clients first. Nodejs / Java / .Net / Python
Upstream doesn't have such feature, but implementing it in playwright-go might be easier due to the golang ecosystem.
Is your feature request related to a problem? Please describe.
When doing development with playwright-go and testing screenshot difference between CI (usually Linux) and local environment (usually Windows and MacOS). Solution to this is to setup a remote browser solution, but this create additional complexity. It is usually assumed that if things render in one OS, they will render close enough on any other OS.
Describe the solution you'd like
Automate the creation of a browser in a docker container locally and proxy all communication to enable local and CI tests to have the same result. I do have the code to do exactly that using testcontainer-go and goproxy, but before starting a PR, knowing if there is interest and how to shape it would be best.
Additional context
So how it work:

Create a http proxy on a random port using Go standard http server and goproxy
Wait for service to start
Create a container that will idle, but can run playwright node service and will have access to the proxy port
Exec node and serve browser using launchServer using a set of prefixed port to listen on and with the proper proxy setup (note that testcontainer-go does not allow HostAccessPort during the startup of the container, but they are only accessible during Exec).
Wait for the websocket port to start answering request
Use pw.Browser.Connect appropriately.

Overall it is maybe around 100 lines of code, but there is a lot of quirks to know about to get this working. It would be better if this is included in playwright-go directly.
Benefit, 100% pixels match between CI and local as they run in exactly the same environment.

I prefer to do this in a new repo, since it doesn't matter whether the client is playwright-go or playwright-python.

I guess the Dockerfile and resulting image would be something that can be shared across language (There is just one requirement is that the version of playwright installed in the image as to match the one of the playwright-*), but the helper that does glue together playwright, testcontainer and a proxy logic will be per language I would think.
What do you think of one new repository for the image and one per language that implement the glue? Do you have any suggestion for the name? I think I can create a repository for the image that will be automatically kept up to date with github action and the go implementation (python is not my forte) and link them here.

I have put the beginning of such an idea here: https://github.com/cedric-appdirect/playwright-ci-go . Still need to write documentation, but would be interested to start getting some feedback.


Increment version to 1.2.3

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Coming from https://github.com/opensearch-project/opensearch-build/issues/1365, increment version to 1.2.3.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I dont think I've seen this before.
> Task :server:test

Tests with failures:
 - org.opensearch.BuildTests.testEqualsAndHashCode

start gradle check

I dont think I've seen this before.
> Task :server:test

Tests with failures:
 - org.opensearch.BuildTests.testEqualsAndHashCode

Of course we would use 1.2.3 as an example in a test ...

start gradle check


chore: supports php 8.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 96.548%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
979

Relevant Lines:
1014

💛  - Coveralls


Added annotation typing to densenet

Hi there!
As per #2025, annotation typing are welcome in torchvision. So, this PR focuses on torchvision.models.densenet this PR!
Any feedback is welcome!

@frgfm Before I review could you enable mypy be removing
https://github.com/pytorch/vision/blob/65591f14e59140b17b0a496c964a32b9f0d769bd/mypy.ini#L19-L21
I remember I deactivated it in the first step because they were already errors present.

@frgfm Before I review could you enable mypy be removing
https://github.com/pytorch/vision/blob/65591f14e59140b17b0a496c964a32b9f0d769bd/mypy.ini#L19-L21
I remember I deactivated it in the first step because they were already errors present.

Sure, just did it!

I'm still getting some errors, I'm not sure how you prefer to handle:
torchvision/models/densenet.py:32: error: "add_module" of "Module" does not return a value
[func-returns-value]
            self.add_module('norm1', nn.BatchNorm2d(num_input_features)),
            ^
torchvision/models/densenet.py:33: error: "add_module" of "Module" does not return a value
[func-returns-value]
            self.add_module('relu1', nn.ReLU(inplace=True)),
            ^
torchvision/models/densenet.py:34: error: "add_module" of "Module" does not return a value
[func-returns-value]
            self.add_module('conv1', nn.Conv2d(num_input_features, bn_size *
            ^
torchvision/models/densenet.py:37: error: "add_module" of "Module" does not return a value
[func-returns-value]
            self.add_module('norm2', nn.BatchNorm2d(bn_size * growth_rate)),
            ^
torchvision/models/densenet.py:38: error: "add_module" of "Module" does not return a value
[func-returns-value]
            self.add_module('relu2', nn.ReLU(inplace=True)),
            ^
torchvision/models/densenet.py:39: error: "add_module" of "Module" does not return a value
[func-returns-value]
            self.add_module('conv2', nn.Conv2d(bn_size * growth_rate, growth_rate,
            ^
torchvision/models/densenet.py:47: error: "Tensor" not callable  [operator]
            bottleneck_output = self.conv1(self.relu1(self.norm1(concated_features)))  # noqa: ...
                                ^

We could directly set the attribute modules, but that would be extra changes. I'd need some minimal change suggestion on this one :sweat_smile:

Maybe @pmeier knows of a trick, but I would prefer to disable mypy in this block instead of rewriting the code.

We will always face issues if we dynamically assign attributes, since mypy is a static type checker. The only thing we can do here is to add lines that annotate this statically
self.norm1: nn.BatchNorm2d
self.add_module('norm1', nn.BatchNorm2d(num_input_features))

Alright, I'll change that then!
Quick question: any specific reasons why there are commas at the end of each self.add_module line?
Should I remove then?

Quick question: any specific reasons why there are commas at the end of each self.add_module line?

Probably an artifact from a previous implementation.

Should I remove then?

Since we don't need to touch the lines for the typing, you could do so in a follow-up PR.

We will always face issues if we dynamically assign attributes, since mypy is a static type checker. The only thing we can do here is to add lines that annotate this statically
self.norm1: nn.BatchNorm2d
self.add_module('norm1', nn.BatchNorm2d(num_input_features))

FYI @pmeier, I tried and unfortunately, on my hand, it's still throwing the same error :/

Any suggestion about this error @pmeier ? The same thing goes for #2864

@frgfm
This checks fine:
from torch import nn

class DenseLayer(nn.Module):
    def __init__(self, num_features: int):
        super().__init__()
        self.norm1: nn.BatchNorm2d
        self.add_module("norm1", nn.BatchNorm2d(num_features))

Could you compile a minimal example where the error you are seeing happens?

OK I think I found why I'm still getting errors @pmeier : mypy seems to be taking the commas at the end of line quite badly. The error is gone if I remove them, but stays if I leave them. Should I remove the commas?

Should I remove the commas?

Sure. I only suggested otherwise before, since I thought they are unrelated to this PR. If that is not the case, we can act on this.

@frgfm As of lately, you are required to sign CLA as detailed in https://github.com/pytorch/vision/pull/2860#issuecomment-720669592. Without that the work that you have done cannot be committed into our repository.

@pmeier done :heavy_check_mark:

Just waiting on the CLA to get propagated and will merge the PR


Added more basic-level jQuery questions and answers

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Adds additional jQuery Q&A objects to the list.

What is the current behavior? (You can also link to an open issue here)
N/A

What is the new behavior (if this is a feature change)?
N/A

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:
Was unsure about filling the checkboxes. I didn't see a guideline for commit messages, and unsure about adding tests/documentation for this specifically.

@coymeetsworld awesome. thanks!


Add gestures to RangeDatePicker

Known issues

Types - I was unable to find proper types for events from react-native-gesture-handler
For now iOS only. Next platforms will come later, there will be a lot of shared code. It works great on real device, but it's laggy in the simulator.
there are few optimization issues., I will deal with them in next PRs
Tests are missing, I will add them in another PR.
There is still one issue during crossing months. Also will be fixed in some of next PRs.

You have a flow error 🙈

You have a flow error 🙈

Fixed


Recent search areas tab

Save recently searched place #10

will save three recent searches
enabled cookies to persist the recent searches for 7 days
Display them under the search field
Display them in horizontal stack
Each of these items should be clickable and once clicked it should trigger the find schedule function.
They should only show before the user has searched.

work sample

Hi @OlivierJM , changes are made. I have attached a sample video of the working too. But I don't know why its failing in vercel. I'm not able to look at its log. Let me know if anything needs to be changed

Hi @OlivierJM , changes are made. I have attached a sample video of the working too. But I don't know why its failing in vercel. I'm not able to look at its log. Let me know if anything needs to be changed
build is failing due to a new package I installed : js-cookie . kindly let me know if you don't want it


Consider switching from caller to raising exceptions to get backtrace for improved performance

There are a number of places in rspec-mocks where we use caller (generally via RSpec::CallerFilter).  We've known for a while that caller is extremely slow.  Another way to get the backtrace is to raise an exception and use Exception#backtrace to get it.  A benchmark shows that, unsurprisingly, using raise to get a backtrace is slightly slower than caller:
require 'benchmark/ips'

def create_stack_trace(n, &block)
  return create_stack_trace(n - 1, &block) if n > 0
  yield
end

[10, 50, 100].each do |frames|
  create_stack_trace(frames) do
    Benchmark.ips do |x|
      x.report("use caller (#{caller.count} frames)") do
        caller
      end

      x.report("use raise (#{caller.count} frames)") do
        exception = begin
          raise "boom"
        rescue => e
          e
        end

        exception.backtrace
      end

      x.compare!
    end
  end
end

Calculating -------------------------------------
use caller (16 frames)
                         5.204k i/100ms
use raise (16 frames)
                         4.350k i/100ms
-------------------------------------------------
use caller (16 frames)
                         58.244k (±11.1%) i/s -    291.424k
use raise (16 frames)
                         49.039k (± 7.7%) i/s -    247.950k

Comparison:
use caller (16 frames):    58244.5 i/s
use raise (16 frames):    49039.1 i/s - 1.19x slower

Calculating -------------------------------------
use caller (56 frames)
                         2.083k i/100ms
use raise (56 frames)
                         2.020k i/100ms
-------------------------------------------------
use caller (56 frames)
                         22.368k (±10.1%) i/s -    112.482k
use raise (56 frames)
                         21.176k (±10.0%) i/s -    107.060k

Comparison:
use caller (56 frames):    22368.3 i/s
use raise (56 frames):    21175.7 i/s - 1.06x slower

Calculating -------------------------------------
use caller (106 frames)
                         1.254k i/100ms
use raise (106 frames)
                         1.231k i/100ms
-------------------------------------------------
use caller (106 frames)
                         13.076k (± 9.3%) i/s -     65.208k
use raise (106 frames)
                         12.389k (± 9.3%) i/s -     61.550k

Comparison:
use caller (106 frames):    13075.8 i/s
use raise (106 frames):    12388.7 i/s - 1.06x slower

However, if you remove the call to exception.backtrace, the results look very, very different:
Calculating -------------------------------------
use caller (16 frames)
                         5.184k i/100ms
use raise (16 frames)
                        26.722k i/100ms
-------------------------------------------------
use caller (16 frames)
                         55.945k (±13.8%) i/s -    274.752k
use raise (16 frames)
                        400.459k (±15.1%) i/s -      1.951M

Comparison:
use raise (16 frames):   400458.6 i/s
use caller (16 frames):    55944.8 i/s - 7.16x slower

Calculating -------------------------------------
use caller (56 frames)
                         2.229k i/100ms
use raise (56 frames)
                        22.596k i/100ms
-------------------------------------------------
use caller (56 frames)
                         22.769k (± 9.8%) i/s -    113.679k
use raise (56 frames)
                        331.157k (± 9.5%) i/s -      1.650M

Comparison:
use raise (56 frames):   331156.9 i/s
use caller (56 frames):    22769.3 i/s - 14.54x slower

Calculating -------------------------------------
use caller (106 frames)
                         1.294k i/100ms
use raise (106 frames)
                        19.634k i/100ms
-------------------------------------------------
use caller (106 frames)
                         12.954k (±10.4%) i/s -     64.700k
use raise (106 frames)
                        244.556k (±10.2%) i/s -      1.217M

Comparison:
use raise (106 frames):   244555.6 i/s
use caller (106 frames):    12953.6 i/s - 18.88x slower

In this case, caller is an order of magnitude slower than raise.  I think this means that there's an opportunity for a large, noticable perf win if we switch away from using caller to raise for situations where we don't immediately need the backtrace but are merely storing it for possible later use.  This is the case, for example, for much of rspec-mocks usage of caller: when a test double is declared, we store the backtrace so that if there's a mock expectation error, we can use the declaration site in the stacktrace.  But if there is no mock expectation error, we don't use the stacktrace and the fact we called caller was wasted work.  Given that the more common case is for a spec to pass, I think it would be worthwhile to switch.
Here are the places in rspec-mocks that could potentially benefit from this:
➜  rspec-mocks git:(master) ack CallerFilter lib
lib/rspec/mocks/matchers/receive_messages.rb
8:          @backtrace_line = CallerFilter.first_non_rspec_line

lib/rspec/mocks/message_expectation.rb
588:            "Called from #{CallerFilter.first_non_rspec_line}."

lib/rspec/mocks/proxy.rb
51:        location = opts.fetch(:expected_from) { CallerFilter.first_non_rspec_line }
113:        location = opts.fetch(:expected_from) { CallerFilter.first_non_rspec_line }
435:        source = CallerFilter.first_non_rspec_line

Given that we use RSpec::CallerFilter here, the change for this will probably involve rspec-support changes to provide a RSpec::CallerFilter.lazy (or some similar API).
It's probably also worth looking at the rspec-core and rspec-expectations usage of caller and RSpec::CallerFilter as there could be some places there that could similarly be improved.
/cc @rspec/rspec

Did you benchmark this against caller_locations too? We already use that where available rather than caller for performance reasons.
Anyway I'm in favour of doing something here at least for the caller case so, I've opened a PR on rspec-support (rspec/rspec-support#) that uses the raise and capture trick but lazily finds the line from the backtrace based on a to_s call. I figure most places we return a caller line will be interpolated into a string giving us this "lazy"ness with much less work. (I use this trick in Rails apps to wrap values with presenters but don't convert the values until the last second, interpolating into templates ;))

Did you benchmark this against caller_locations too? We already use that where available rather than caller for performance reasons.

Nope, I haven't done a benchmark yet.  I expect raise to be significantly faster, though; our caller vs caller_locations benchmark shows a 2-3x perf benefit out of using caller_locations but my benchmark here shows a 7-19x perf benefit so raise is almost certainly going to be faster than caller_locations.

Anyway I'm in favour of doing something here at least for the caller case so, I've opened a PR on rspec-support (rspec/rspec-support#199)

Thanks...I'll go comment there :).

nice find

See the discussion on rspec/rspec-support#199 it's not actually faster in practise.


[DPE-5104] update libs/deps

Update libraries and dependencies to have MongoDB k8s up to date

@Gu1nness should we have a validation of requirements.txt in charmcraft.yaml like here?


updateCache breaks in the IntegrationTest phase

I just realised I never submitted this.
We are unable to use the updateCache in ensime-server as it will randomly (yes, unfortunately it sometimes passes) fail to add shapeless to our integration test phase.
Reproduction (not necessarilly minimal) in https://github.com/ensime/ensime-server/tree/08be528a2e4eb33acd5cc499e416e32189e61919/project and anything before that for about a year. Caching not enabled here https://github.com/ensime/ensime-server/blob/08be528a2e4eb33acd5cc499e416e32189e61919/project/EnsimeBuild.scala#L102

For clarity, you mean cached resolution here, right?

That's right yes

For the benefit of not introducing confusing alternative vocabulary like "updateCache" and "IntegrationTest phase", I tweaked your title a little.

I can't remember how sporadic this was, but it seems to work again. Will reopen if it crops up.


Exact two layer solution

I tried to implement the exact solution to the two-layer problem (sum of a fast-timescale exponential and a slow-timescale exponential) rather than the one-exponential deep-layer model we have now.
For some reason, introducing a second timescale makes the problem unsolvable by Ipopt via JuMP. The algorithm solves successfully for time horizons less than about 2150, but then I get errors of "search_direction_too_small" or "iterations_diverging". I'm going to try out NLopt and see if it's any better.

NLopt unfortunately no longer supported in JuMP because they didn't switch to MathOptInterface, which is required as of JuMP v0.19.0
It may be possible to speed up MARGO (and deal with divergence issues) by being smart about warm starts, e.g. by setting the variables
set_start_value(M[1], 0.0)
```

Another unfortunate problem with the exact two-layer solution. Forward finite differences results in huge errors if the timestep is on the order of– or longer– than one-third of the fast timescale (~4 years for CMIP5 values). In practice, I found I need to keep the timestep below about 0.5 years to achieve good results. This could be improved somewhat with a better time-stepping scheme but with the 10–20 year timesteps we want for the web-app, I'm not sure we will be able to get around this.
We might be able to write discrete approximate solutions to the integral kernels... Not sure if it would be worth it.


Good and Brilliant moves

Chess.com has a system of declaring some moves: good, best, great, brilliant. There is great demand for this kind of stuff on lichess.
The problem is that no one can properly define what a good move and even the various ideas they have cannot be easily implemented on the client side. But it is worth thinking about.

Idea 1: we can compute from ratings what is the probability that a player will win. Then we can compare the result of the current game, giving it a "game rating" in the context of the player rating. Then we determine which moves were most consequential to the result. If the game rating is very high (a resounding victory) and the determining moves were yours and not opponent blunders, when those moves are "great".

Idea 2: for each sequence of two moves calculate the delta (increase/decrease) in both eval and material. A move that has high eval increase and high material decrease is "flashy". The difficulty here lies in determining if this is a local value, like the first part of an exchange or a series of exchanges, or a relevant move. The eval should not change significantly for a few moves, perhaps, but this eliminates the brilliant moves followed by terrible blunders.

Idea 3: moves that increase the eval significantly but are rare in Opening Explorer can be badged as "interesting" or "rare". However this only works for the beginning of games, when moves are stored in the database.

Idea 4: multiple algorithms determine a value for each move. You don't call them anything in particular, but the intersection of the lines plotted on the chart could be significant. The advantage is that you have no false positives, you just report numerical values, which allows individual players to draw their own conclusions based on their personal preferences.

Possible ideas of numerical values:

aggressiveness
positional (restricting enemy options while increasing yours)
number of different threats created/blocked
ply difference between eval jump and materialization of attack

Note that all of these computations must be done on the spot, when opening a game, since there is no server component to store this information.

Extra charts implemented in v2.0.30

Idea 5: (which seems to be working) is to codify as many chess principles as possible and then compare it with the computer eval. If a move is principled, then it might be good, but it is also boring. If a move is unprincipled, while still being a good move, then it is brilliant. I think we are unconsciously splitting moves into beginner, expert and master. The beginning needs to know the principles, the expert knows them, the master breaks them.

The newest incarnation shows the pure material advantage and how principled the position is. Note interesting moves when the evaluation jumps up, but the material and/or the principled position go down.
Closing this for now, since I don't think I am going to work directly on showing brilliant moves, just updating the charts.


I18n

Internationalisation or i18n is critical for most production apps these days.
I recommend adding an API for i18n.
Have it return a JSON with all the tokens for all languages.
Also an endpoint for only a specific language.
Could setup a system to bring language contributers on board.
Could implement a select in the UI to change language.

I agree that I18n is important, but it's also a huge amount of work. Specifically, purchasing translation files is too much to ask for an open source project.
I think this is outside the scope of the project though. The goal is to provide users with a high-quality codebase that introduces them to a language/framework. I18n doesn't help achieve that goal, so I think we should avoid it.

No need to purchase translations. We can put everything in English only and setup a way for people to translate.

It's still outside the scope of the project. @EricSimons Thoughts?

I am willing to implement this in Ember

I think basically since the V1 api is "frozen" with multiple back and frontends already completed and many more actively in work, it would be too much work to enhance it to support i18n.
But out of curiosity, for discussion, what would this API look like?
Could you expand on this:

Have it return a JSON with all the tokens for all languages.
Also an endpoint for only a specific language.

Does the backend expose extra endpoints? Or is this purely on front end. How exactly would the new API look in comparison to v1 api.
Also, about:

I am willing to implement this in Ember

Since an important teaching point of this project is to sort of compare and contrast different stacks all trying to achieve the same thing, we would need a common API with clear implementation possible in most if not all stacks.

About the endpoint:
While this could be a static translation of only English to start with. I think it would work better as an API.
JSON would look like:
en: {
	hi: "Hi",
	article: "article
	etc...
}

The Endpoint could be something like: apiUrl/i18n
Which brings all languages or with a parameter to only bring one language.
Most libraries/frameworks that I looked at can consume this format of translations.
Pretty much just a matter of consuming key value pairs.
Even if we don't add a new endpoint to the spec. Having a static JSON file with just English wouldn't be bad as well.

We've agreed on what the minimum testing spec should be in the discussion in issue #90 so I think we can close this.


fix: lack of default branch name causes repo display issue

Describe what this PR does / why we need it
When a repo doesn't have a default branch name (i.e. a totally empty repo) then Octo gives an error when trying to view that repo.
This fixes that. Additionally, because when using the fzf-lua picker since the repo is previewed the error can show up when that repository is highlighted.
Does this pull request fix one issue?
Fixes https://github.com/pwntester/octo.nvim/issues/519
Describe how you did it
Check for the default branch ref and if it's vim.NIL the name just becomes nil. This will prevent displaying the name as well as fetching the README from the default branch.
Describe how to verify it
Make a repo on Github and don't configure anything (no README, no .gitignore, no license file, etc.), then run :Octo repo view you/your-repo. Make sure there is no error as seen in #519
Special notes for reviews
N/A

@MadKuntilanak would you be able to verify this one?

would you be able to verify this one?

yup i verified this with:

Create an empty folder and make repo with zero git suff
Open octo repo list or ocro repo view <repo_link>
Doing this doing that, success, no errors

Thanks!


Design Challenge registration page for Organizations

This current design will make it so a user will make a request, then we will create the organization account for them. (That way, we can monitor what gets added).  Not sure if we want to approach things this way in the long-run, but I think for now, we can take on this burden.
Link to full design on Figma


[Event Request] table 6550 "Whse. Item Tracking Line" - OnAfterSetTrackingFilterFromItemLedgerEntry

We would like to add a new event OnAfterSetTrackingFilterFromItemLedgerEntry and a new procedure:
procedure SetTrackingFilterFromItemLedgerEntry(ItemLedgerEntry: Record "Item Ledger Entry")
begin
    //A200F0000.Event.ns
    SetRange("Serial No.", ItemLedgerEntry."Serial No.");
    SetRange("Lot No.", ItemLedgerEntry."Lot No.");
    //A200F0000.Event.ne

    OnAfterSetTrackingFilterFromItemLedgerEntry(Rec, ItemLedgerEntry); //A200F0000.Event
end;

Event Signature:
[IntegrationEvent(false, false)]
local procedure OnAfterSetTrackingFilterFromItemLedgerEntry(var WhseItemTrackingLine: Record "Whse. Item Tracking Line"; ItemLedgerEntry: Record "Item Ledger Entry")
begin
    //A200F0000.Event
end;

Function SetTrackingFilterFromItemLedgerEntry does not exist

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. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Add Elasticsearch/bonsai.io to services doc.

Hip hip for OSS! 🙌

 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 merged this without looking, but you need to open this PR in https://github.com/gohugoio/hugoDocs/pulls

Done:

https://github.com/gohugoio/hugoDocs/pull/664


added gif in the help menu

Added a mockup gif in the help menu.
WIll update the gif when we will find something better.

allright, sure!


[GLUTEN-1632][CH] Daily Update Clickhouse Version (20230803)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

Compatible with current gluten


Backtraces on windows

Currently short backtraces on windows seem to be somewhat broken and just don't work for the shipped rust-analyzer binaries at all and while the user can now overwrite the RUST_BACKTRACE env var for the server to enable full backtraces they just turn into a bunch of <unknown> frames. This is most likely due to us not shipping the pdb files(just guessing I don't know how these things work).
Zulip discussion: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/panic.20backtrace

This is most likely due to us not shipping the pdb files(just guessing I don't know how these things work).

Just wanted to chime in. This is definitely due to not shipping pdbs. Windows relies on debug info to demangle Rust symbols and without it, it really has no idea what's going on.

Small update here: we can publish the PDBs, but downloading them automatically is less easy because our Windows artifacts are GZ files. Since we're planning to bundle the server binary with the extension, we'll probably wait for that.

@Veykril can you try with the latest release?

Already tried earlier today, wasn't sure if we shipped the PDBs already now but no it does not work unfortunately, the stacktrace is still missing(bunch of <unknown> for a FULL one)

:sob: the PDB should be in there, at least.

Does it work if you rename the pdb to rust-analyzer.pdb (from rust_analyzer.pdb)?

I checked and the .exe seems to reference rust_analyzer.pdb, not rust-analyzer.pdb. But yeah, it's worth a try.

Nope 😕

Can you check that it's actually running the bundled server and not some random one in %HOME%/.cargo/bin or somewhere else?

running the version command from vscode gives me the latest nightly so that seems correct.

So it looks in the working directory but not the location of the exe


No extension = no load

When the extension is not installed, the web app shows a blank screen. We should still load the UI, but show the connection button in the top right that directs user to install the extension.

throwIfExtNotInstalled is still present and works, but it is called during render and the page tries to create a transport client before rendering anything.

That sounds like an issue with the way we create grpc clients. I think we need to change createChannelTransport to be lazy loaded and only attempt to open connections when a request is attempted for the first time. Creating a client should be a zero-cost thing.

more specifically, it is the transport creation that is failing. it used to succeed unconditionally and then surface failures on attempted use, but after much discussion i learned it was desirable to have some immediate indication of connection success or failure before requests were attempted.
in the webapp, the clients are all pre-created and imported from a file where they are created at the top level. last time i looked at this i avoided making creation async, because our es target doesn't allow top-level await, and some of the clients are used in react components where async things are problematic.
some locations in the webapp use dynamic import of the clients, this delays them appropriately. if that's an acceptable solution we could try to generalize that.

alternatively, could just provide async wrappers something like getViewClient and most of the refactor would still apply. i think that one component is the only sticking point


close application if is closed

if the youthclub is closed, the client need a message

check in 10 sec interval state of youthclub. next step is a seperate issuse #12


Update the websocket API

Describe the bug
The websocket API is outdated.
Expected behavior
The grid_node_websocket_api.rst should contain the correct functions.

@IonesioJunior Made a PR with the documentation update, but I see there are no tests for the websocket REST API. Should I include some tests in this issue or should I create a separate one?

Yes, please!


Include codes

Description
Some weather data use codes instead of physical values with units.
Proposal
Include a map of the codes. If we can retrieve them from the API, that would be nice, otherwise, we can include them in a JSON file.

https://opendata.smhi.se/apidocs/metobs/schemas.html#generic


NgModules support

Which scope/s are relevant/related to the feature request?
astro-angular
Information
Documentation says:

The Astro Angular integration only supports rendering standalone components:

Are there any plans to support NgModule sometime in the future?
And if I decide to add NgModules support, is there any technical limitation, why it can be impossible?
P.S. I understand that probably NgModules will be deprecated at some time, but my codebase heavily relies on it.
Describe any alternatives/workarounds you're currently using
Migration component to standalone one by one.
I would be willing to submit a PR to fix this issue

[ ] Yes
[ ] No

You can still import modules in standalone components..?

@marcus-sa
Can you elaborate, on what do you mean under "you can import modules in standalone components", please?
I have dependency on 3rd party library: https://github.com/Sitecore/jss/tree/dev/packages/sitecore-jss-angular
If I try to use something from that library without modification, I get
The directive, imported is not standalone. Did you forget to add the standalone: true flag?
Or console exception if it is not a standalone component.

@marcus-sa Can you elaborate, on what do you mean under "you can import modules in standalone components", please?
I have dependency on 3rd party library: Sitecore/jss@dev/packages/sitecore-jss-angular If I try to use something from that library without modification, I get The directive, imported is not standalone. Did you forget to add the standalone: true flag? Or console exception if it is not a standalone component.

@Directive({
	selector: '[test-dir]',
})
class TestDirective {}

@NgModule({
  declarations: [TestDirective],
  exports: [TestDirective],
})
class TestModule {}

@Component({
	selector: 'test-cmp',
	standalone: true,
    imports: [TestModule],
    template: `<div [test-dir]></>div>`,
})
class TestComponent {}

There are no plans to support NgModules as the primary import to use an Angular component in Astro. I tried this before standalone components were introduced and it was not worth the effort to use.
Consuming the JssModule in your standalone component is probably the best option that lib is migrated.


For Azure Cloud Solution Providers (CSP) subscriptions, changing the Azure AD directory for the subscription isn't supported.

Hello,
there is a NOTE which does mention "For Azure Cloud Solution Providers (CSP) subscriptions, changing the Azure AD directory for the subscription isn't supported.".
But there is another article which does mention that moving Subscriptions between AAD for CSP would be possible:
https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/transfer-subscriptions-subscribers-csp
Could you explain why this Note exist on this document?
thanks
Christian

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

ID: 9afab524-67c2-2e76-fd7a-46238cb9d249
Version Independent ID: ae2da577-6026-f322-1c09-dbcc6068c01a
Content: Transfer an Azure subscription to a different Azure AD directory
Content Source: articles/role-based-access-control/transfer-subscription.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@cpinotossi Thank you for your feedback . We will investigate and update the thread.

@cpinotossi : You are right with your understanding that the tenant of CSP subscriptions cannot be changed. In the document I see that there are grammatical issues when it says "Note that the change directory isn't the CSP subscription." It should have been isn't supported for CSP subscription.
If you read further it says "For example, you're transferring from a CSP to a pay-as-you-go subscription. You need change the directory of the pay-as-you-go subscription to match the directory."
Which means in a case where you want to transfer data between subscriptions under different tenant. To bring them on same tenant to enable the transfer you should change the tenant for Pay As You Go as we cannot change it for CSP subscription.
Regards,
Srinath Patil

@cpinotossi Hope the above explanation helps. I have corrected the grammatical error that Srinath have talked about and the change should go live in the next 48 hours on public documentation. In case you do not have any other queries on this , we will be closing this issue by tomorrow.

@cpinotossi Please let us know if the above explanation helped or if you have any further queries on this . We will be happy to help you further.
Thank you.

@cpinotossi As per my discussion internally with @SrinathPAtil , he has engaged with you to help you understand about the CSP subscription and directory linking. We are going to close this issue now. In case of any further queries , please feel free to ping me .
Thank you.


npm script to call out image quality

Is it possible to specify image quality when use imagemin in npm script ? Thanks,
I was using the following, I want to further compress the image so to reduce size. Can't find any instructions around about passing in the parameters for quality or other.  Please help.
"scripts": {
    "imageminall": "imagemin --plugin=mozjpeg images/* --out-dir=dist"
  },

Mozjpeg can be replaced with other plugin if needed. Thanks again.

Duplicate of #171


errors and valid? are not Thread Safe

As discussed in #14 - I goofed in testing and will make sure to set up the right solution.

As part of the solution, the naming of these creates an unintended conflict with ActiveModel::Validations which should also be considered when crafting the solution.
As for the bug, most likely resolved simply by moving the two values from class-level to instance-level.

I've already got a surface level fix for this by moving errors to be an instance variable rather than a class variable. Making sure there aren't other issues in the same code.

Fixed in the last commit.
However, these methods are deprecated and will be removed before GA.


[RESOLVED] High ICMP ping response time

Problem started at 02:08:32 on 2023.07.10
Problem name: High ICMP ping response time
Host: S100-Santiago
Severity: Warning
Operational data: Value: 169ms
Original problem ID: 32029
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23518&eventid=32029

Problem has been resolved in 2m 1s at 02:10:33 on 2023.07.10
Problem name: High ICMP ping response time
Host: S100-Santiago
Severity: Warning
Original problem ID: 32029


Update rebuild command reference to replay

A reference to the old rebuild command got missed here in the docs.

Thanks!


Document UWOP_EPILOG and .beginepilog

I'd like to ask for documentation of UWOP_EPILOG in version 2 of unwind info and the MASM macro .beginepilog. The unwind code is partially documented and used here while the MASM macro is completely undocumented but used in the crt in memset.asm

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

ID: 35cf8590-8a4f-91c3-8fa4-b225c247eb9d
Version Independent ID: 062a75f5-f5c8-89db-4dec-1c3d0095f5c2
Content: x64 exception handling
Content Source: docs/build/exception-handling-x64.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

Bump, would like to know this information as well.

https://github.com/dotnet/coreclr/blob/a9f3fc16483eecfc47fb79c362811d870be02249/src/unwinder/amd64/unwinder_amd64.cpp#L1532
coreclr documents how it works... it requires version=2 for the unwind code. Its purely for optimization purposes.

We are in the process of moving away from GitHub issues for C++ documentation (we still accept pull requests). For details, please see Announcing a new way to give feedback on Microsoft Learn This issue will be closed after it is copied to an internal tracking system.


Add Note shortcut key (n) doesn't enter note mode

Clicking in the map data tab and selected 'notes' option does present the note mode, but just hitting 'n' seemingly does nothing.

Dupe of #520, closing.


sentry_cpu_profiler-v83-linux-arm64-glibc.node: cannot open shared object file: No such file or directory

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/profiling-node/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

How do you use Sentry?
Sentry Saas (sentry.io)
SDK Version
7.36.0
Link to Sentry event
n/a
What environment is your node script running in?
AWS Lambda, Node.js 14.x, arm64
How is your code deployed and bundled?
Lambda package deploy (zip file bundling our code, node_modules, etc)
Steps to Reproduce
Custom code wrapping lambda, looks something like this:
export function wrapLambdaHandler<TEvent, TResult>(
    dsn: string,
    handler: Handler<TEvent, TResult>,
    options: IWrapperOptions = {},
): Handler<TEvent, TResult> {
    const integrations: Integration[] = [];
    const initOptions: Sentry.NodeOptions = {
	    dsn: dsn,
	    environment: 'stage',
	    tracesSampleRate: options.tracesSampleRate ?? 0.1,
	    beforeSend: beforeSendToSentry,
	    ignoreErrors: ['ProvisionedThroughputExceededException', 'TimeoutError', /Possible function timeout/],
	    integrations: [],
    };
    const profilesSampleRate = options.profilesSampleRate ?? 0.1;
    if (profilesSampleRate > 0) {
	    initOptions.profilesSampleRate = profilesSampleRate;
	    initOptions.integrations.push(new ProfilingIntegration());
    }
    AWSLambda.init(initOptions);
    return AWSLambda.wrapHandler(handler);
}

Stack trace (below) doesn't really show if the failure happens during the library load, or during the init phase.
Expected Result
A functional lambda.
Actual Result
Lambda fails with<EMAIL_ADDRESS>cannot open shared object file: No such file or directory
The full error looks like:
{
  "errorType": "Error",
  "errorMessage"<EMAIL_ADDRESS>cannot open shared object file: No such file or directory",
  "code": "ERR_DLOPEN_FAILED",
  "stack": [
    "Error<EMAIL_ADDRESS>cannot open shared object file: No such file or directory",
    "    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18)",
    "    at Module.load (internal/modules/cjs/loader.js:950:32)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:790:12)",
    "    at Module.require (internal/modules/cjs/loader.js:974:19)",
    "    at require (internal/modules/cjs/helpers.js:101:18)",
    "    at importCppBindingsModule (/var/task/node_modules/@sentry/profiling-node/lib/cpu_profiler.js:20:12)",
    "    at Object.<anonymous> (/var/task/node_modules/@sentry/profiling-node/lib/cpu_profiler.js:26:25)",
    "    at Module._compile (internal/modules/cjs/loader.js:1085:14)",
    "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)",
    "    at Module.load (internal/modules/cjs/loader.js:950:32)"
  ]
}

I've downloaded the .zip file that was deployed to Lambda and can confirm that the sentry_cpu_profiler-v83-linux-arm64-glibc.node file does exist, so this appears to be a problem internal to the lambda itself.
Unfortunately, since this is a problem with Sentry initialization, I don't have a Sentry issue with more detailed info. 😉

@ex-nerd, can you verify that bundling and execution arch are the same? This could happen if you run bundling on a glibc based image, but execute on a musl based image (or vice versa)

This could be related to this documentation.

Deployment packages with C or C++ libraries
If your deployment package contains native libraries, you can build the deployment package with AWS Serverless Application Model (AWS SAM). You can use the AWS SAM CLI sam build command with the --use-container to create your deployment package. This option builds a deployment package inside a Docker image that is compatible with the Lambda execution environment.

I'm just poking this to let you know that "roadmap work" has prevented me from doing any further debugging on this. The issue isn't yet resolved, but I also don't have any new information.

@ex-nerd Thanks for the updated. To be fair, I have not had the chance to actually attempt to build a package for aws lambdas myself. Let us know once you get back around to debugging this - I will update here in case we get to it first.

Just checking in here again. Bundling and execution arch are not the same, and we will eventually get that migrated … however, the lambda is being invoked from a .zip file stored in S3. That file is confirmed to contain the appropriate binary for the arch (and all of the other ones), so any help in debugging this would be appreciated.

I'll also add that we're deploying via cloudformation, e.g. (semi-redacted)
{
	"Type": "AWS::Lambda::Function",
	"Properties": {
		"Architectures": ["arm64"],
		"FunctionName": "LambdaName",
		"Description": "LambdaDescription",
		"Runtime": "nodejs14.x",
		"Handler": "lambda.handler",
		"Role": "LambdaRoleArn",
		"Code": {
			"S3Bucket": "S3_BUCKET_NAME_GOES_HERE",
			"S3Key": "LAMBDA_CODE_PATH.zip"
		},
		"Environment": {
			"Variables": {
				"NODE_OPTIONS": "--enable-source-maps",
				"SENTRY_CLOUD_DSN": "3.14159265359",
				"SENTRY_TRACES_SAMPLE_RATE": "0.1",
			}
		}
	}
}

docs for AWS::Lambda::Function available here
There doesn't seem to be a way for us to specify the build architecture of the lambda other than what's shown here. I'm still digging, just thought I'd send this update in case it sparks an idea.

@ex-nerd I will look into this today as there have been a few reports, thanks for the added info

@ex-nerd I have not setup the lambda deploys, but I suspect the cause here could be a missing shared library like libstdc. We've had a couple of reports of the same nature in different runtimes so I'm trying to see what the cause could be here.
Out of curiosity, does the same error happen if you attempt to use node 16 or 18?

I don't currently have a way to test lambda with node 16 or 18, sorry.

@yasirtrimulabs you are using nodejs v12 which has been end of life for almost 3 years. We do not provide precompiled binaries for this node version so we would recommend you to update to node v16 or 18 which is the current LTS.
Since only one of the instances gives this error, is it possible that this instance is the only one running node v12 while other run newer versions of node?
With all that said, you should be able to use the package with node v12, but you need to ensure that the binary can be properly compiled from source after installation. If upgrading your node version is not possible, can you please tell me how the package is installed? Additionally, can you please cd into '/{APPLICATION_NAME}/node_modules/@sentry/profiling-node/ and run npm run build:configure and npm run build:bindings and tell us if you see any errors?

@JonasBa thanks for the quick reply.
I am using node v16 already. I have set v16 as default using nvm. Can it be that the pm2 is overwriting it?
Here's the output for npm run build:configure
><EMAIL_ADDRESS>build:configure
> node-gyp configure

gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"
gyp http GET https://nodejs.org/download/release/v16.14.0/node-v16.14.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v16.14.0/node-v16.14.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v16.14.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v16.14.0/SHASUMS256.txt
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args   '/{APPLICATION_NAME}/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args<EMAIL_ADDRESS>gyp info spawn args   '-I',
gyp info spawn args   '/{APPLICATION_NAME}/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/root/.cache/node-gyp/16.14.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/root/.cache/node-gyp/16.14.0',
gyp info spawn args   '-Dnode_gyp_dir=/{APPLICATION_NAME}/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/root/.cache/node-gyp/16.14.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/{APPLICATION_NAME}/node_modules/@sentry/profiling-node',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info ok

And here's the output for npm run build:bindings
><EMAIL_ADDRESS>build:bindings
> node-gyp build && node scripts/copy-target.mjs

gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/{APPLICATION_NAME}/node_modules/@sentry/profiling-node/build'
  CXX(target) Release/obj.target/sentry_cpu_profiler/bindings/cpu_profiler.o
  SOLINK_MODULE(target) Release/obj.target/sentry_cpu_profiler.node
  COPY Release/sentry_cpu_profiler.node
make: Leaving directory '/{APPLICATION_NAME}/node_modules/@sentry/profiling-node/build'
gyp info ok
Target file already exists, overwriting it
Renaming<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

@yasirtrimulabs yes, that is possible. If you would have installed with node v12, then the binaries would have been built for that version (or you would have seen an install error)
The reason I know you are using node v12 at runtime is because the binary is looking for sentry_cpu_profiler-linux-x64-glibc-72.node meaning you are have x64 linux arch and node version 72 of nodejs ABI. You can cross reference version 72 at https://nodejs.org/en/download/releases that this points to node v12

So it is likely that something is running your process with node v12 here

@JonasBa thanks for helping. For some reason, the pm2 on this instance was using node v12. It is working now. Thanks again, you are a life saver


clean up error messages

We can use this issue to dump all the simple error message rewordings we want.

[ ] Bentley G. Coffey in a message to stan-users suggested the following message for the Jacobian warning:In addition to being monotonic and differentiable, the transform of the variable before
the ~ must be invariant with respect to the parameters to be estimated, in which case
this warning can be ignored, or else the transform's log Jacobian determinant must
be accounted for in the model block via a call to increment_log_prob()

The only real issues here are included in other issues.


Bug: Query builder crash when date_format is set with '%H:%i:%s'

Describe the bug
Query builder is binding incorrectly the statement with date_format (eg. %d/%m/%Y %H:%i:%s) - 22/09/2021 10:45:00 and crash.
<?php

$id = 1;
//Works
$sql = " SELECT mytable.id, DATE_FORMAT(mytable.created_at,'%d/%m/%Y %H:%i') AS created_at_uk FROM mytable WHERE mytable.id = ?";
$query = $this->db->query($sql, [$id]);

//DOES NOT work
$sql = " SELECT mytable.id, DATE_FORMAT(mytable.created_at,'%d/%m/%Y %H:%i:%s') AS created_at_uk FROM mytable WHERE mytable.id = ?";
$query = $this->db->query($sql, [$id]);

As you can see, the only difference between both SQL is the :%s. This should not be binding as the (%s) means seconds on date_format.
CodeIgniter 4 version
CI 4.1.3
Affected module(s)
Not sure but looks like is Query.php
Expected behavior, and steps to reproduce if appropriate
Should return the query with day/month/year hour:minute:second
Context

OS: Mac
Web server Apache
PHP version 8.0

:%i: matches the following regexp:
https://github.com/codeigniter4/CodeIgniter4/blob/fd824042df6be1375d6ea8ae5919a3d61c109b4b/system/Database/Query.php#L278
See https://regex101.com/r/lSp7qq/2

Ref #4769

Refs #5138.


youtube-dl is not getting proper auto-sub but getting not-auto-sub

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.05.01. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl --skip-download --write-auto-sub --proxy http://<IP_ADDRESS>:9090 https://www.youtube.com/watch?v=Bv961ZmBL80 -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--skip-download', '--write-auto-sub', '--proxy', 'http://<IP_ADDRESS>:9090', 'https://www.youtube.com/watch?v=Bv961ZmBL80', '-v']
[debug] Encodings: locale cp936, fs mbcs, out cp936, pref cp936
[debug] youtube-dl version 2018.05.01
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.16299
[debug] exe versions: ffmpeg N-89343-g83ecdc9a92, ffprobe N-89343-g83ecdc9a92
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:9090', 'https': 'http://<IP_ADDRESS>:9090'}
[youtube] Bv961ZmBL80: Downloading webpage
[youtube] Bv961ZmBL80: Downloading video info webpage
[youtube] Bv961ZmBL80: Extracting video information
[youtube] Bv961ZmBL80: Looking for automatic captions
[debug] Default format spec: bestvideo+bestaudio/best
[info] Writing video subtitles to: Duck Roast recipe by the BBQ Pit Boys-Bv961ZmBL80.en.vtt
...

youtube-dl --version
2018.05.01

<end of log>

Description of your issue, suggested solution and other information
youtube-dl is not getting proper auto-sub but getting not-auto-sub
i use
youtube-dl --skip-download --write-auto-sub --proxy http://<IP_ADDRESS>:9090 https://www.youtube.com/watch?v=Bv961ZmBL80

and downloaded Duck Roast recipe by the BBQ Pit Boys-Bv961ZmBL80.en.vtt
it looks like this.
WEBVTT
Kind: captions
Language: en

00:00:18.068 --> 00:00:26.777
 Roasted duck

00:00:34.170 --> 00:00:37.460
 Welcome to BBQPitBoys.com

00:00:37.460 --> 00:00:40.100
 What we are going to do today is roast ducks

00:00:40.100 --> 00:00:42.320
 It's easy to do

but it should looks like this
WEBVTT
Kind: captions
Language: en
Style:
::cue(c.colorCCCCCC) { color: rgb(204,204,204);
 }
::cue(c.colorE5E5E5) { color: rgb(229,229,229);
 }
##

00:15:33.660 --> 00:15:36.150 align:start position:0%

well<00:15:34.660><c> we're</c><00:15:34.809><c> drawing</c><c.colorE5E5E5><00:15:34.959><c> towards</c><00:15:35.589><c> the</c></c><c.colorCCCCCC><00:15:35.739><c> evening</c></c>

00:15:36.150 --> 00:15:36.160 align:start position:0%
well we're drawing<c.colorE5E5E5> towards the</c><c.colorCCCCCC> evening
 </c>

00:15:36.160 --> 00:15:38.549 align:start position:0%
well we're drawing<c.colorE5E5E5> towards the</c><c.colorCCCCCC> evening
now<00:15:36.279><c> as</c><00:15:36.399><c> you</c><00:15:36.519><c> can</c></c><c.colorE5E5E5><00:15:36.610><c> tell</c></c><c.colorCCCCCC><00:15:36.670><c> dark</c></c><c.colorE5E5E5><00:15:37.480><c> got</c><00:15:38.230><c> the</c><00:15:38.350><c> fire</c></c>

It seems that if the video have a human write subtitle, even not in English, youtube-dl will not get the auto-sub, but the auto-translated-sub, which doesn't contain any word-time info, but only the start time and end time.

--write-sub for regular subtitles.
You're getting exactly what Youtube provides.

I mean I want to get the auto-sub, the regular subtitles is not what I want.


4.4.7 broke array types in Context

What version of Hono are you using?
4.4.7+
What runtime/platform is your app running on?
Cloudflare Workers
What steps can reproduce the bug?
I am attempting to upgrade to the latest 4.4 versions and I get a types issue with Array based elements in the HonoContext.
Sample context:
export interface DC {
  name: string;
  url: string;
}

declare module 'hono' {
  interface ContextVariableMap {
    jwt: JWTInterface;
    dcs: DC[];
    allowAllOrigins: boolean;
    allowedOrigins: string[];
    appToken: string;
    appEnv: string;
  }
}

What is the expected behavior?
No type errors should happen. This doesn't happen on 4.4.6, so maybe related to https://github.com/honojs/hono/pull/2987?
What do you see instead?
➜ pnpm run -F gateway-router tsc

><EMAIL_ADDRESS>tsc router
> tsc --noEmit                                 ~~

src/file.ts:327:16 - error TS7006: Parameter 'dc' implicitly has an 'any' type.

327       .filter((dc) => userDcs.includes(dc.name))
                   ~~

src/file.ts:328:13 - error TS7006: Parameter 'dc' implicitly has an 'any' type.

328       .map((dc) => {
                ~~

src/file.ts:50:40 - error TS7006: Parameter 'dc' implicitly has an 'any' type.

50     if (!body.dc || c.get('dcs').find((dc) => dc.name === body.dc) === undefined) {
                                          ~~

src/file2.ts:180:55 - error TS7006: Parameter 'allowed' implicitly has an 'any' type.

180         const allowed = c.get('allowedOrigins').find((allowed) => origin === allowed);
                                                          ~~~~~~~

Additional information
No response

Hi @dustinsmith1024
Is this way of reproducing it correctly?
https://github.com/user-attachments/assets/52a1fe57-c3a1-434e-a64c-a8c6976ba9a0
If so, it does not throw errors. Can you provide a minimal project to reproduce it?

Here you go: https://github.com/dustinsmith1024/hono-types-issue

@dustinsmith1024 Thanks. Will be fixed soon.

Awesome thanks - Should I be doing something different with Context to prevent it?

@dustinsmith1024

Should I be doing something different with Context to prevent it?

It's a bug, so you don't have to add anything. Just wait for a new version!

Hi @dustinsmith1024
This may be fixed in the latest version v4.5.0. Can you try it?

We can close this issue now. If you still have a problem, feel free to reopen.


Fix NSData convertation for iOS 13

This PR is supposed to fix iOS 13 NSData-to-hex conversion.
#283
#519
AB#71688
AB#70228

Refer to my comment for more details on new implemetation

I'll reopen PR from this repo, and not fork. Link


{HDInsight}Remove the allowed TLS version 1.0 and 1.1 in --minimal-tls-version help message

Remove the allowed TLS version 1.0 and 1.1 in --minimal-tls-version help message
Related command

only affect the output of  az hdinsight create -h
Description

Azure ARM has enforced TLS 1.2, but in az hdinsight create help message, we still have the allowed version 1.0 and 1.1, we need to remove it from help message. There is not customer impact.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

HDInsight

Hi @kairu-ms could you please help review this PR? Thanks

Hi @kairu-ms @jsntcy could you please help review this PR? Thanks

Hi @aim-for-better, it seems a breaking change. So please update History Notes part in your PR.

Hi @aim-for-better, it seems a breaking change. So please update History Notes part in your PR.

Hi @kairu-ms , Thanks, I have updated the History Notes. Could you please help merge this PR?

Hi team, could you please help merge this?  Thank you

The history note's [] part is wrong

[az hdinsight] BREAKING CHANGE: az hdinsight create: Remove the enum value 1.0 and 1.1 from the --minimal-tls-version, HDInsight doesn't support TLS version which is less than 1.2 now.


Update to Angular 17

TODO:

Fix tooltip and popover components
Use signals

Remaining:

#78
https://github.com/Rikarin/xui/blob/master/apps/web/src/templates/angular.ts

Fix https://github.com/Rikarin/xui/issues/79

https://github.com/Rikarin/xui/issues/117

https://github.com/Rikarin/xui/issues/70

Fix #78

:tada: This PR is included in version 1.45.0-develop.1 :tada:
The release is available on:

v1.45.0-develop.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.45.0 :tada:
The release is available on:

v1.45.0
GitHub release

Your semantic-release bot :package::rocket:


Removing manager packages with vulns

- What I did
- How to verify it
- Description for the changelog

Duplicate on #75


Confusing storage auto-grow example for MySQL Flexible Server

The "Storage auto-grow" section of the MySQL Flexible Server documentation gives an example of automatically growing provisioned storage from 10 GB to 15 GB of storage if less than 1 GB is available and auto-grow is enabled. However, is 20 GB not the minimum possible amount of storage as stated earlier in the documentation? If so, then may I suggest changing the numbers in the example to reflect a real life scenario instead of being theoretical, or maybe I have misunderstood how the service works? :)

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

ID: ecba95e1-af55-5a99-5c44-585b10b26ac5
Version Independent ID: 0f008812-6b29-7545-0318-f39b386d5c5b
Content: Azure Database for MySQL - Flexible Server service tiers
Content Source: articles/mysql/flexible-server/concepts-service-tiers-storage.md
Service: mysql
Sub-service: flexible-server
GitHub Login: @Bashar-MSFT
Microsoft Alias: bahusse

@tlaur Thank you for your feedback. We are reviewing this and will get back shortly.

@Bashar-MSFT Coud we please update the storage auto-grow section with the minimum number of storage amount which is 20GB.

@Oury-MSFT can you please assign this to @VandhanaMehta as she owns storage from the PM perspective

@Oury-MSFT this is completed by Vandhana, please close this one


Networks with certain names prevent connecting to containers

Output of docker version:
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.6.2
 Git commit:   5604cbe
 Built:        Mon May  2 00:06:51 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.6.2
 Git commit:   5604cbe
 Built:        Mon May  2 00:06:51 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 2
 Running: 2
 Paused: 0
 Stopped: 0
Images: 277
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-8:6-155885-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 4.859 GB
 Data Space Total: 107.4 GB
 Data Space Available: 10.33 GB
 Metadata Space Used: 13.85 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.134 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.122 (2016-04-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.5.4-1-ARCH
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 7.741 GiB
Name: amarmac
ID: 5PE5:IJQC:N6CV:KS47:TCGF:IX3K:AKBA:6OKX:RLEW:CDAA:LNNJ:CQ62
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/

Additional environment details (AWS, VirtualBox, physical, etc.):
~ » uname -a
Linux amarmac 4.5.4-1-ARCH #1 SMP PREEMPT Wed May 11 22:21:28 CEST 2016 x86_64 GNU/Linux

Steps to reproduce the issue:

Launch a Docker container that exposes and publishes a port, but without specifying a host port. For example, this hello-world web server:
docker run -d -p 80 --name c1 tutum/hello-world

Get the port, and browse to it in your favourite web browser (or curl, or whatever). Notice that everything works just fine.
docker port c1 80

Create a Docker network called "a" (or anything starting with an a) and connect your container to it. Notice that now connections to the container are refused.
docker network create a
docker network connect a c1

Repeat 1-3 but this time with a container name that does not start with "a". Notice how connections are not refused.

Proceed to tear your hair out after days of debugging.

Describe the results you received:
Host connections to containers connected to a Docker network with a name that starts with "a" are refused, but not for ones named anything else.
Describe the results you expected:
Host connections to containers connected to a Docker network with any name are not refused.
Additional information you deem important (e.g. issue happens only occasionally):

The steps for reproduction use the Docker CLI, but I can confirm that the issue persists when using the Docker remote API.
This only happens when you do not specify a host port (i.e. you let Docker map to some ephemeral port).
This always happens when the name of the network begins with an "a", though it could happen for other names too; I haven't tested that many names.

Perhaps this may be fixed by https://github.com/docker/docker/pull/23011 for some cases, but I guess this is due to the order in which the container is connected, and the port is published on the first network (alphabetically). Also, the random port may change on network connect, which should be fixed in docker 1.11.2 (see https://github.com/docker/docker/pull/22997, https://github.com/docker/docker/issues/22836)

I think there's an existing issue about this, but I should look it up

Thanks for the reply! I've just tested this with 1.11.2 and the problem persists.
You're absolutely right though - I can confirm that it happens when the network is named "bridgd" (< bridge), but not when the network is named "bridgf" (> bridge). I don't think #23011 fixes it (maybe that's only for container links?).
Do you know if there's a way to control which network the port is published on (or lock it on bridge)? Could you link me to that part of the docs if so?

Perhaps it helps to create the custom networks with --internal, so that the port is not published on that network. The user guide contains a section on container networking; https://docs.docker.com/engine/userguide/networking/dockernetworks/

Thanks for the tip @thaJeztah! For posterity: making the networks internal doesn't seem to have an effect, but at least for now I can make sure that my network names are just > bridge.

Fixed by #22997


Release 2.3.0

Descriptive summary

Version: 2.3.0
Release Manager: @VivianChu
Product Owner and Reviewer: @gamontoya
Operations: @rstanonik

To Verify
Tickets to review are noted in the release notes:
https://github.com/ucsdlib/dmr/releases/tag/2.3.0

@rstanonik - Could you please deploy new DMR release to production at your earliest convenient? Thanks

@gamontoya - The release has been deployed to production.
For example
https://library.ucsd.edu/dmr/analytics?utf8=✓&type=audio&start_date=01%2F04%2F2020&end_date=01%2F07%2F2020


Error when run example server !

Hi guys,
I am a newbie about QUIC. I follow the instructions to install and update the dependencies. I use go v1.9. However, I get some errors when running the example server.
This is my error:
example/main.go:22:2: use of internal package not allowed
example/main.go:23:2: use of internal package not allowed
Anybody know how to fix this?
Thank you in advance !

It's probably a problem with your GOPATH. Please check your Go installation.


Custom name for the mask

I didn't find the way (via the parameter file) to define a variable mapping for the mask... in our IPSL outputs we do have the land-ocean mask, but named "fract_ter".
Can we already control this from the param file? If not I can propose a fix for this.

@jservonnat does the code found in https://github.com/PCMDI/pcmdi_metrics/blob/master/doc/parameter_files/input_parameter_file_all_options.py#L15-25 help out here?
So "variable_mapping" : { "fract_ter" : "sftlf"} may work?

@durack1 I think that the mechanism of a dictionary to define a variable mapping is indeed the way to go (it surely works for our 'IPSL to CMIP5' variable names matching) but apparently the driver does not handle the variable mapping for the mask variable name. Is that correct?
I tried to add the 'sftlf':'fract_ter' to the list of variables mapped, but it didn't work.

@doutriaux1 with the variable remapping, we need to define this a bit better - is it "user_varName" : "cmip_varName" or the other way around, it wasn't clear to me in the parameter or driver files..

Good idea... sftlf id remapping should be done consistent mapping different variable names, e.g.,
"GFDL-ESM2G" : {
"variable_mapping" : { "tas" : "tas_ac"},
},

@doutriaux1 what's the status of this?


Add flashcards for French vocabulary

All of the 'General'-type vocabulary has been added (the remaining vocabulary types are 'Foundation' and 'Higher').


Configurable number of processors in RP

THIRD attempt at new branch/PR to get a fresh CI build.

/test-destroy-env

/test-destroy-env

/test-destroy-env

/test-destroy-env


Wallet crashes when staking

This issue was fixed after completely started our wallet project over. The new ticker/wallet went live on CryptoBridge on November 23rd, 2018.