Nuxt adding vuetify-theme-stylesheet on page with vuetifymodule.

Versions

nuxt:  v2.14.1
node: v12.18.3

Reproduction

Additional Details

Steps to reproduce
Hi, im using nuxt v2.14.1 and nuxt-vuetify-module v1.11.2"
im getting this extra style tag everywhere.
i saw this as an issue before in past year, but all the issues are closed now, and some of them said its fixed, i saw the merge file too.
this a merged file link: merged
but this wasnt fixed and i found this link too: jousepo thinks find the bug source
these are all i found, and im not sure where to open the issue.
and still having this problem.
will you please guide me to fix my problem?
tnx.
What is Expected?
expected a clean html , no extra style tag.
What is actually happening?
adding a large style tag to every page.

Though the large style block is annoying, I don't think this is a bug.
Vuetify renders this stylesheet by design (vuetifyjs/vuetify/issues/3329, vuetifyjs/vuetify/pull/2486). The mentioned PR is about duplicated theme stylesheet id.

hi,
I'm getting the same "extra style tag" - EST problem.
extractCSS on build works fine!
the EST in my case includes only v-application classes.
An interesting phenomenon is that the EST is not consistent -
after fast double or triple refresh, the EST was not rendered.

my workaround for the problem is to comment the applyVueMeta23() call -> after build update .nuxt/dist/server/server.js

Well, you have access to take action yourself to make a rendering, and if
you don't have access, please say to open access to the action thank you.
در تاریخ شنبه ۱۴ نوامبر ۲۰۲۰، ۱۷:۲۴ Yaniv Dukhan<EMAIL_ADDRESS>نوشت:

[image: applyVueMeta23]
https://user-images.githubusercontent.com/29441261/99148560-03c09c00-2691-11eb-91b4-2808079862a6.png
my workaround for the problem is to comment the applyVueMeta23() call ->
after build update .nuxt/dist/server/server.js
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/7859#issuecomment-727210432, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARWWVO5NZG345JLYLGUZ743SP2DZTANCNFSM4PVORWQQ
.

This seems to be an issue that should be raised directly with https://github.com/vuetifyjs/vuetify..


Related media heading sizes different in audio/image pages

Problem

The Related images uses a Heading 5 for screens above md and the Related audio always uses a Heading 6. These both should probably be Heading 5 above md, @fcoveram ?

Additional context

First reported by @zackkrida : https://github.com/WordPress/openverse/pull/3831#discussion_r1509533709
This issue is blocked because it needs input from @fcoveram
Changes necessary
https://github.com/WordPress/openverse/blob/868d764a619c187cee1a3d841502128dc571b80c/frontend/src/components/VMediaInfo/VRelatedMedia.vue#L15-L16
Should be changed to
class="heading-6 mb-6 md:heading-5"

The visual regression test snapshots will probably need to be updated. Here's the documentation on the update procedure: https://docs.openverse.org/frontend/reference/testing_guidelines.html#debugging

Yes, you are right. Heading 5 for screens above md in both pages.

Hi! I would like to work on this.

Hi, I would like to work on this issue


Update offsets for v1_0_877_1, fix versions

dev_v2 branch
Fix Steam versions taken as base to non-steam versions. (0, 1 are same,
2, 3 are same, 4, 5 are same. Previously script changed on 5, which is
wrong for NoSteam version.

Some ped field offsets are also changed, such as Ped.CanSufferCriticalHits.

Thank you to both @E66666666 and @kagikn!


Fabo/fixed delegation query loop

Closes #ISSUE
Description:

Thank you! 🚀

For contributor:

[ ] Added entries in CHANGELOG.md with issue # and GitHub username
[ ] Reviewed Files changed in the github PR explorer
[ ] Attach screenshots of the UI components on the PR description (if applicable)
[ ] Scope of work approved for big PRs

For reviewer:

[ ] Manually tested the changes on the UI

this is still failing, not spamming but still shows the error notification. @jbibla did you tested it ?


Error building with latest pip on Cygwin

# pip3.9 --version
pip 23.2.1 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)
# pip3.9 install ansible-vault-win
Collecting ansible-vault-win
  Using cached ansible_vault_win-1.0.0-py3-none-any.whl (21 kB)
Collecting cryptography (from ansible-vault-win)
  Using cached cryptography-41.0.3.tar.gz (630 kB)
  Installing build dependencies ... error
  error: subprocess-exited-with-error

  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [99 lines of output]
      Collecting setuptools>=61.0.0
        Obtaining dependency information for setuptools>=61.0.0 from https://files.pythonhosted.org/packages/c7/42/be1c7bbdd83e1bfb160c94b9cafd8e25efc7400346cf7ccdbdb452c467fa/setuptools-68.0.0-py3-none-any.whl.metadata
        Using cached setuptools-68.0.0-py3-none-any.whl.metadata (6.4 kB)
      Collecting wheel
        Obtaining dependency information for wheel from https://files.pythonhosted.org/packages/28/f5/6955d7b3a5d71ce6bac104f9cf98c1b0513ad656cdaca8ea7d579196f771/wheel-0.41.1-py3-none-any.whl.metadata
        Using cached wheel-0.41.1-py3-none-any.whl.metadata (2.2 kB)
      Collecting cffi>=1.12
        Using cached cffi-1.15.1.tar.gz (508 kB)
        Installing build dependencies: started
        Installing build dependencies: finished with status 'done'
        Getting requirements to build wheel: started
        Getting requirements to build wheel: finished with status 'done'
        Preparing metadata (pyproject.toml): started
        Preparing metadata (pyproject.toml): finished with status 'done'
      Collecting setuptools-rust>=0.11.4
        Using cached setuptools_rust-1.6.0-py3-none-any.whl (23 kB)
      Collecting pycparser (from cffi>=1.12)
        Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
      Collecting semantic-version<3,>=2.8.2 (from setuptools-rust>=0.11.4)
        Using cached semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
      Collecting typing-extensions>=<IP_ADDRESS> (from setuptools-rust>=0.11.4)
        Obtaining dependency information for typing-extensions>=<IP_ADDRESS> from https://files.pythonhosted.org/packages/ec/6b/63cc3df74987c36fe26157ee12e09e8f9db4de771e0f3404263117e75b95/typing_extensions-4.7.1-py3-none-any.whl.metadata
        Using cached typing_extensions-4.7.1-py3-none-any.whl.metadata (3.1 kB)
      Using cached setuptools-68.0.0-py3-none-any.whl (804 kB)
      Using cached wheel-0.41.1-py3-none-any.whl (64 kB)
      Using cached typing_extensions-4.7.1-py3-none-any.whl (33 kB)
      Building wheels for collected packages: cffi
        Building wheel for cffi (pyproject.toml): started
        Building wheel for cffi (pyproject.toml): finished with status 'error'
        error: subprocess-exited-with-error

        × Building wheel for cffi (pyproject.toml) did not run successfully.
        │ exit code: 1
        ╰─> [59 lines of output]

                No working compiler found, or bogus compiler options passed to
                the compiler from Python's standard "distutils" module.  See
                the error messages above.  Likely, the problem is not related
                to CFFI but generic to the setup.py of any Python package that
                tries to compile C code.  (Hints: on OS/X 10.8, for errors about
                -mno-fused-madd see http://stackoverflow.com/questions/22313407/
                Otherwise, see https://wiki.python.org/moin/CompLangPython or
                the IRC channel #python on irc.libera.chat.)

                Trying to continue anyway.  If you are trying to install CFFI from
                a build done in a different context, you can ignore this warning.

            /tmp/pip-build-env-t53239r6/overlay/lib/python3.9/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
            !!

                    ********************************************************************************
                    The license_file parameter is deprecated, use license_files instead.

                    By 2023-Oct-30, you need to update your project and remove deprecated calls
                    or your builds will no longer be supported.

                    See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
                    ********************************************************************************

            !!
              parsed = self.parsers.get(option_name, lambda x: x)(value)
            running bdist_wheel
            running build
            running build_py
            creating build
            creating build/lib.cygwin-3.4.7-x86_64-cpython-39
            creating build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/api.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/backend_ctypes.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/cffi_opcode.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/commontypes.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/cparser.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/error.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/ffiplatform.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/lock.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/model.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/pkgconfig.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/recompiler.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/setuptools_ext.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/vengine_cpy.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/vengine_gen.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/verifier.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/__init__.py -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/_cffi_include.h -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/parse_c_type.h -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/_embedding.h -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            copying cffi/_cffi_errors.h -> build/lib.cygwin-3.4.7-x86_64-cpython-39/cffi
            running build_ext
            building '_cffi_backend' extension
            creating build/temp.cygwin-3.4.7-x86_64-cpython-39
            creating build/temp.cygwin-3.4.7-x86_64-cpython-39/c
            gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DFFI_BUILDING=1 -I/usr/include/python3.9 -c c/_cffi_backend.c -o build/temp.cygwin-3.4.7-x86_64-cpython-39/c/_cffi_backend.o
            error: command 'gcc' failed: No such file or directory
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for cffi
      Failed to build cffi
      ERROR: Could not build wheels for cffi, which is required to install pyproject.toml-based projects
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Sorry for the noise. I'll look more careful about installing building tools.


upgrade and cleanup ember-cli

This updates a majority of the ember-cli code to version 2.13.2.  Major change is a move to ES2015 based code.
Files not modified:

ui/* -- major local modifications and moved into separate package upstream
models/blueprint -- will be removed with upcoming schematic package integration
tasks/* -- same as above (most are currently unused but integrated into above)

Note: The exit capture functionality is disabled as it does not currently work with the serve and e2e commands.
/cc @filipesilva

LGTM, it looks like this was a fair chunk of work so thanks for taking it on 👍


Task/brugger1/2023 01 06 mili reader

Description
Resolves #17729
I fixed a bug where variables that were only defined on a portion of the nodes weren't being placed on the correct nodes. This was handled properly for zonal variables. I fixed the bug by unifying the handling of nodal and zonal variables.
I also eliminated some warning variables from unused variables and comparisons between ints and unsigned ints.
Type of change

[X] Bug fix~~

How Has This Been Tested?
I compared pen1s - pen7s for the first and last time step with what griz shows.
I ran tests/databases/mili.py in the test suite and it passed, so no errors were introduced.
Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[X] I have commented my code where applicable.~~
[X] I have updated the release notes.~~
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[X] I have confirmed new and existing unit tests pass locally with my changes.~~
[ ] I have added new baselines for any new tests to the repo.
[X] I have NOT made any changes to protocol or public interfaces in an RC branch.~~

@durrenberger1 Can you look over this pull request and let me know if it looks correct to you? Thanks!

You would have to ask Nickolai whether this is export control or not.  In general,  things generated in Engineering are export controlled.  But I am not sure on this.

@durrenberger1 good catch on the unnecessary calculation. I removed it.


Amend I/O reform RFC to address issues with flush

rendered

After thinking about this a bit today, I'm not quite sure that we may want the split. I agree that other abstractions may want a flush method as well, but I'm not sure that this incarnation of Flush is appropriate for all use cases. My biggest concern is that the usage of io::Error may make it inadequate for the general use case. For example std::fmt::Write uses a different error type than I/O. Additionally, delegation of a flush method from one trait to another (if the flush method is duplicated among traits) arguably takes fewer lines to express than an explicit implementation of Flush itself.
I feel like there may be a place for a generic Flush, but I don't find the motivation compelling enough to try to introduce the general trait at this time.

cc @aturon

I'm not sure what the use-case of a generic Flush is. I can't think of any reason why a function or type would want to be able to flush() a stream without first having written something to it, and if it knows how to write to the stream then it obviously knows what type the stream is (and therefore is already bound on something like Write).
I also don't see what the benefit is of moving the declaration of fn flush(&mut self) -> io::Result<()> out of the Write trait and into a separate trait. Given the hypothetical TextWriter, having both Write and TextWriter declare fn flush(&mut self) -> io::Result<()> is not code duplication in any meaningful sense. Any implementation of these traits would need to implement flush() regardless of where it's declared, and the fact that both Write and TextWritermay want to have an identical methodfn flush(&mut self) -> io::Result<()>` does not necessarily mean that this is in fact a truly generic flush method that is appropriate for all stream types.
In fact, the only benefit that comes to mind is a type that implements both Write and this hypothetical TextWriter would only need to implement flush() once, instead of twice. But that seems like an edge case that's not worth worrying about, and it's also not necessarily obvious that the implementation would even want to be the same in both cases (I can think of some esoteric stream types that might want the ability to have flushing behavior that differs from Write::flush).

@alexcrichton:

For example std::fmt::Write uses a different error type than I/O.

This is actually an issue of its own: std::fmt::Error should expose std::io::Error as a possible cause.

I have filed issue rust-lang/rust#23386 to correct the documentation of into_inner, and #978 to amend the I/O RFC accordingly.
As the generic Flush trait did not get much support, I'm closing this PR.


[5.3] Type error in typescript.d.ts with exactOptionalPropertyTypes = true

🔎 Search Terms
"exactOptionalPropertyTypes", "JsDocParsingMode".
🕗 Version & Regression Information

This changed between versions 5.2.2 and 5.3.2
I think, this changed in commit or PR https://github.com/microsoft/TypeScript/pull/55739

⏯ Playground Link
No response
💻 Code
// "exactOptionalPropertyTypes": true,

import type { CompilerOptions } from "typescript";

export type { CompilerOptions };

🙁 Actual behavior
Error:
node_modules/typescript/lib/typescript.d.ts:3287:24 - error TS2420: Class 'Project' incorrectly implements interface 'LanguageServiceHost'.
  Types of property 'jsDocParsingMode' are incompatible.
    Type 'JSDocParsingMode | undefined' is not assignable to type 'JSDocParsingMode'.
      Type 'undefined' is not assignable to type 'JSDocParsingMode'.

3287         abstract class Project implements LanguageServiceHost, ModuleResolutionHost {
                            ~~~~~~~

Found 1 error in node_modules/typescript/lib/typescript.d.ts:3287

🙂 Expected behavior
No error.
Additional information about the issue
Minimal repository with bug reproduction: https://github.com/uid11/jsDocParsingMode-error-example.
As far as I can see, to fix this error, it is enough to replace the line
https://github.com/microsoft/TypeScript/blob/c266e47794fbd187425989448670238576523d4e/src/services/types.ts#L435
with
    jsDocParsingMode?: JSDocParsingMode | undefined;

Although, perhaps, such errors with exactOptionalPropertyTypes are corrected differently.

Working on this; there are more errors than just this one.


Implement AsFd for UnixStream

As the title suggest std has a impl AsFd for UnixStream, this requires bumping msrv to 1.63 or using the io_lifetimes crate

This is related to https://github.com/async-rs/async-std/pull/1036


Backport of go update 1.22.7 to 7.58.x

What does this PR do?
Backport of go update 1.22.7 to 7.58.x
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

/merge


onRedirect called twice

I don't understand why on onRedirect is being called twice. Here's a snippet of my code.
async function handleRedirect(params) {
    console.log("Params!", params);
    if (loading) return
    setLoading(true);
    setShowPaymentDialog(false);
    if (params.status == "cancelled") {
      return;
    }
    try {
      console.log("Verifying transaction", params.tx_ref);
      const transactionResponse = await verifyTransaction(params.tx_ref);
      const transaction = transactionResponse.data.transaction;

      setTransaction(transaction);
    } catch (error) {
      console.log("Error", error);
    } finally {
      setLoading(false);
    }
  }
<FlutterwaveCheckout
          onAbort={handleAbort}
          onRedirect={handleRedirect}
          link={paymentLink || undefined}
          visible={showPaymentDialog}
        />

Please what am I doing wrong?

Hi @georgeben, we will look into this but for now, can you look into debouncing your redirect handler?
First within your component, before the handleRedirect method, do the following.
let redirectTimeout = useRef();

Then in your handleRedirect do the following.
async function handleRedirect(params) {
  // clear scheduled action
  clearTimeout(redirectTimeout.current);
  // delay action to prevent from reoccurring
  redirectTimeout.current = setTimeout(() => {
    console.log("Params!", params);
    if (loading) return
    setLoading(true);
    setShowPaymentDialog(false);
    if (params.status == "cancelled") {
      return;
    }
    try {
      console.log("Verifying transaction", params.tx_ref);
      const transactionResponse = await verifyTransaction(params.tx_ref);
      const transaction = transactionResponse.data.transaction;

      setTransaction(transaction);
    } catch (error) {
      console.log("Error", error);
    } finally {
      setLoading(false);
    }
  }, 100);
}

Let me know if this helps.

Thank you @thecodecafe I was able to get it working.

This issue has cost us alot of money.

@habeebtheprogrammer apologies for this, we'll do our best to avert issues like this in the future, please can you try the solution here?

I'll be closing this issue for now but feel free to open the issue again should in case the solution proffered above does not solve your problem.


Add support for typescript bit-int types

NOTE: I can't seem to find a logger or default stream setup for writing to stdin, so I just opted for println!().

This would close
#24

I think testing is going to continue to fail until you remove the big-int-ish types from the list of blocklisted types:
https://github.com/1Password/typeshare/blob/main/core/src/rust_types.rs#L257


migrate public service to VPC

What changed, and why it matters

Minor fixes to language
Remove images and add descriptions to fill void
Change first to third person

Fixes #820

Since this is a migration article (https://help.aiven.io/en/articles/5408586), I'll add the required entries after merging the PR.


AzureIoTHubClient_SendTelemetry() returns success when the message is not successfully delivered

The expectation is that when calling AzureIoTHubClient_SendTelemetry(), if it’s not able to deliver the telemetry to iothub at that moment, it will return something like eAzureIoTErrorFailed, and block until delivered or timed out. However, what I’m finding is that it always returns eAzureIoTSuccess until the azure client has detected the disconnection. I notice that these messages are then going into some sort of queue because minutes later when I restore the internet connection, it delivers these messages. This isn’t the behavior we want to implement. It’s important that it’s known at the time of calling SendTelemetry whether or not the delivery of the message was successful, even if the call is blocking.
The scenario I am trying to prevent: Controller is successfully connected to azure. Internet connection is lost (in my testing, a firewall rule to block the controller's internet). AzureIoTHubClient_SendTelemetry is called and returns success. Eventually azure client recognizes connectivity is lost, then shortly after, there’s a power failure. The telemetry will never be delivered because it’s in the azure client queue. If AzureIoTHubClient_SendTelemetry returns something other than success, we know at that moment to write the message to flash and it’ll be delivered later when connectivity is restored.
I have tested defining the macro azureiotconfigKEEP_ALIVE_TIMEOUT_SECONDS and that does seem to be working well to reduce the likelihood of the aforementioned scenario. I’ve lowered it to 10 seconds for testing, and it behaves as expected. However, even if it is set very low, my example scenario can still occur since we send telemetry upwards of every 30 seconds, and sometimes we’ll send 3 messages at that 30 second interval.
Is there any way to get AzureIoTHubClient_SendTelemetry() to block until it is confirmed the message is delivered to IoT Hub?

Hi @rtheil-growlink
I think you can achieve the behavior you are looking for by providing a callback for the telemetry "send", which will be invoked when a PUBACK is received for a sent message. For QOS0 and QOS1, there is no way for us to know within AzureIoTHubClient_SendTelemetry() whether the hub actually received the message or not. If it's sent with QOS0, there is no guarantee that the message will ever be delivered. With QOS1, we could have put a "wait" loop in the API which waited for the puback for the message, but we decided to give flexibility to the developer to care (or not) about the puback for the QOS1 scenario. If it's important, they can provide the callback. If not, then they can have simpler code without it.
Let us know if that helps!

I think this becomes tough in my case because I'm implementing all this into an existing codebase that relies on a boolean response since older hardware submitted these messages via http(s). We'd know within a second or two if the delivery was successful, so when sending telemetry, in order to emulate the http method, there's an expectation of a boolean  response in order to tell the call stack that the delivery was unsuccessful, so write to storage for later upload.
I think I will play with the idea of using a callback with a short wait after the SendTelemetry call, and see if I can make that work. Would a callback tied to SendTelemetry be called when AzureIoTHubClient_ProcessLoop is run?

Correct. The callback is invoked here on an incoming event, processed in the _ProcessLoop():
https://github.com/Azure/azure-iot-middleware-freertos/blob/ccfda9716f39a70c6772b6fa22f8bf7fecacee90/source/azure_iot_hub_client.c#L145-L162
In theory the PUBACK should be quick so you could wrap the _Send() and _ProcessLoop() in one function and exit once the puback is returned, essentially making it a "sync" function. It's not a guarantee that the first message which the ProcessLoop will pick up is the puback, which is why we decided against putting it directly in the _SendTelemetry() API.

Yeah, I think that all makes sense. I have azure running itself in its own freertos task, which constantly calls _ProcessLoop(), so since messages are sent in a separate task, I should be able to do a loop that waits for a few seconds while calling vTaskDelay(1). If success, return true, if timeout, return false.
Thanks for all the help with this stuff!


Add background image support through optional background param

So I've gotten a bit tired of seeing continued discussion on a very old issue (#29); Either way, I decided to do something about it. I've included background-image support through an optional background param that you can set when creating a new imagesLoaded instance. Examples of how to use this:
// 1. Find elements with class .bg-image that have a background image
var imgLoader = new imagesLoaded('.bg-image', { background: true });

// 2. Find *any* children with a background image inside #container or #container itself
var imgLoader = new imagesLoaded('#container', { background: true });

The implementation for this has been simplified to allow for the most flexibility. That said, it’s better to be specific with your selector strings (as shown in example 1). Otherwise, we have no way of filtering an elements children and are subsequently forced to iterate and check each.
Please let me know if you’d like me to make any changes to the implementation, add more tests etc..

Yeah!

Great feedback @desandro! Some thoughts...

Done!
My original implementation actually utilized a className string, instead of the background boolean; I did indeed use it as a way to filter child elements instead of iterating over all children. That said, it seemed redundant when a developer is already passing a collection of elements or a selector string. The best way to filter elements is to be more specific with your selector string and not rely on element discovery (img elements or otherwise). Removing the child element discovery, as a whole, may be a good idea (ie. I'll remove mine if you remove yours :wink:).
Done-ish! (depending on your feedback/thoughts). I think ImagesLoaded is fine as it is. I think over engineering for a very specific use-case isn't that helpful (especially when ImagesLoaded really is about images... loading... and not elements).
That said, I've added an .originalElement property to the LoadingImage instance. As you might guess, it references the background image's origin. It doesn't solve the problem of firing an event based on when an element [with multiple background images] has completely loaded but it does give you context which wasn't there before.

If you really need to know when all of a specific element's background images were loaded you could just write something like:
var container = document.querySelector( '#container' );
var element = container.querySelector( 'div' );
var imgLoader = new imagesLoaded( container , { background: true } );

var progress = 0;
var regex = /\burl\s*\(\s*["']?([^"'\r\n\)\(]+)["']?\s*\)/gi;
var total = element.style.background.match( regex ).length;

imgLoader.on( 'progress' , function ( instance, image ) {
  if ( image.img.originalElement ===  element) {
    progress++;
  }
  if ( progress >= total ) {
    // all background images are loaded for that element...
  }
});

Either way, definitely feel free to look over the code again (as I've rewritten history a bit here... rebased, squashed, force-pushed etc.) and let me know your thoughts again.

Cool! This support is exactly what I am looking for! Would be a great help for me. Thank you all!

@desandro Like I said above, I think this is a good stop-gap for any kind of bigger refactor you're going to do in terms of firing events on both an image load and all images loaded on a multi-background image element. Definitely let me know if there's something I'm missing or anything terribly wrong with this implementation. Keys here are that it doesn't change the API at all but just adds unobtrusive support for background images.

Adding background images is a huge API change. While this may work as a stop gap, I don't feel comfortable implementing a stop-gap solution like this for such an important feature.

The API might change with
I haven't done extensive browser testing
There's other concerns I don't feel settled on: like if this should target only elements, and not their children; and if it's worth specifying when all the background images of an element have been loaded

In short, if we're going to add this feature, I want to be comprehensive about it.
I realize the waiting game is painful. But good news is that I have more personal availability to devote to code. I do appreciate your patience. This will happen.

Should I just close this PR then?

Let's keep it open. It'll help others to chime in or use your fork in the meantime.

Sounds good. Removed background image detection of child elements, for my own sanities sake.

Ping @desandro... it looks like no work has been done on this project in awhile and I'd like to think we don't want to fragment efforts. It looks like there's a number of PRs that could be merged in safely/easily. Any update, specifically, on the work relevant to this PR? I guess I still don't see why the work I've done can't be merged in.

Hello! Thanks for the ping. Man, I've let things get unkept here. Frustration is justified.
Thinking it over, I feel best course of action is to maintain your own fork if you want to see things moving. I don't feel ready to start making changes and I don't want to hold separate progress back.
This issue is just one of several that's I'm on the fence with. I needed imagesLoaded to support Masonry & other libraries, but its usage has grown outside that:

background images
SVG
srcset, <picture>

The bigger issue is whether or not imagesLoaded to should support stuff that Masonry + co. don't really need.

How stable is the background branch? Think it would be safe for production?

:tada: :star: :rainbow:  imagesLoaded v3.2.0 now supports background images :rainbow: :star: :tada:  Try it out!
Thanks again for getting the ball rolling on this. Closing this PR now.

Set { background: true } to detect when the element's background image has loaded.
// jQuery
$('#container').imagesLoaded( { background: true }, function() {
  console.log('#container background image loaded');
});

// vanilla JS
imagesLoaded( '#container', { background: true }, function() {
  console.log('#container background image loaded');
});

Set to a selector string like { background: '.item' } to detect when the background images of child elements have loaded.
// jQuery
$('#container').imagesLoaded( { background: '.item' }, function() {
  console.log('all .item background images loaded');
});

// vanilla JS
imagesLoaded( '#container', { background: '.item' }, function() {
  console.log('all .item background images loaded');
});


Slack alert channel support

Reading through the source, I only see support for email, pagerduty, and webhoot. Are there plans to support Slack alert channels?
https://github.com/logdna/terraform-provider-logdna/blob/main/logdna/resource_alert.go

@jsoh hi jimmy- thank you for your interest!! That is correct- we currently support email, pagerduty and webhook via the provider and we do plan to expand support to Slack alert channels

@dm36 Is this something that still could be expected?

@philippfrank yes, support for Slack as an alerting channel is still planned in our backlog

@jsoh @philippfrank one thing worth noting is that if you configure a webhook channel using the Slack webhook URL hooks.slack.com, you can accomplish essentially the same integration today. We do still plan to evaluate more explicit support for Slack (among other integrations) in the provider as well, but this might be a good solution in the meantime.

@mdeltito Can you provide an example on how this can be accomplished to achieve basically the same result as with the "native" slack channel

@mdeltito It is unnecessary complex though. The provider does already allow to define a (reusable) slack alert channel. Why isn't there a way to attach that channel to a view?

@philippfrank the slack_channel type was added after my comment above, we do now support that as a first-class channel type in the provider. it sounds like your other bug report is addressing a different concern, we'll take a look 👍


Rolling update playbook crashing on unnecessary migration from ceph-disk to ceph-volume

Bug Report
Hey guys, just started the rolling-update.yaml playbook to upgrade from Nautilus 14.2.1 to Nautilus 14.2.4. The playbook crashed on task activate scanned ceph-disk osds and migrate to ceph-volume if deploying nautilus. But we're already using ceph-volume.
Before that, some months ago, we updated our cluster from Mimic to Nautilus. We had to manually migrate from ceph-disk to ceph-volume (as I wrote here: https://github.com/ceph/ceph-ansible/issues/4055#issuecomment-500792350), since then it was running fine. Why does the playbook try to migrate it, if it's already running on ceph-volume?
How to reproduce it (minimal and precise):
On Nautilus 14.2.1:

Migrate your ceph-disk to ceph-volume as described here: https://docs.ceph.com/docs/nautilus/rados/operations/add-or-rm-osds/#replacing-an-osd
Run the rolling update playbook to upgrade the cluster from 14.2.1 to 14.2.4

Environment:

OS (e.g. from /etc/os-release): 18.04.3 LTS (Bionic Beaver)
Kernel (e.g. uname -a): Linux ceph1-40-10 5.0.0-16-generic #17~18.04.1-Ubuntu
Ansible version (e.g. ansible-playbook --version): ansible-playbook 2.8.6
ceph-ansible version (e.g. git head or tag or stable branch): stable-4.0
Ceph version (e.g. ceph -v): 14.2.1 / 14.2.4

Crash message:
TASK [activate scanned ceph-disk osds and migrate to ceph-volume if deploying nautilus] ****************************************************
Monday 11 November 2019  16:46:21 +0100 (0:00:01.319)       0:09:03.711 *******
fatal: [ceph1-40-10.rz1.barzahlen.de]: FAILED! => changed=true
  cmd:
  - ceph-volume
  - --cluster=ceph
  - simple
  - activate
  - --all
  delta: '0:00:00.243683'
  end: '2019-11-11 16:46:21.568056'
  msg: non-zero return code
  rc: 1
  start: '2019-11-11 16:46:21.324373'
  stderr: |-
    --> activating OSD specified in /etc/ceph/osd/0-95a0dc80-a3e8-4274-8acc-655ab1900d5f.json
    Running command: /bin/mount -v  /var/lib/ceph/osd/ceph-0
     stderr: mount: /var/lib/ceph/osd/ceph-0: wrong fs type, bad option, bad superblock on , missing codepage or helper program, or other error.
    Traceback (most recent call last):
      File "/usr/sbin/ceph-volume", line 11, in <module>
        load_entry_point('ceph-volume==1.0.0', 'console_scripts', 'ceph-volume')()
      File "/usr/lib/python2.7/dist-packages/ceph_volume/main.py", line 38, in __init__
        self.main(self.argv)
      File "/usr/lib/python2.7/dist-packages/ceph_volume/decorators.py", line 59, in newfunc
        return f(*a, **kw)
      File "/usr/lib/python2.7/dist-packages/ceph_volume/main.py", line 149, in main
        terminal.dispatch(self.mapper, subcommand_args)
      File "/usr/lib/python2.7/dist-packages/ceph_volume/terminal.py", line 194, in dispatch
        instance.main()
      File "/usr/lib/python2.7/dist-packages/ceph_volume/devices/simple/main.py", line 33, in main
        terminal.dispatch(self.mapper, self.argv)
      File "/usr/lib/python2.7/dist-packages/ceph_volume/terminal.py", line 194, in dispatch
        instance.main()
      File "/usr/lib/python2.7/dist-packages/ceph_volume/devices/simple/activate.py", line 280, in main
        self.activate(args)
      File "/usr/lib/python2.7/dist-packages/ceph_volume/decorators.py", line 16, in is_root
        return func(*a, **kw)
      File "/usr/lib/python2.7/dist-packages/ceph_volume/devices/simple/activate.py", line 178, in activate
        process.run(['mount', '-v', data_device, osd_dir])
      File "/usr/lib/python2.7/dist-packages/ceph_volume/process.py", line 153, in run
        raise RuntimeError(msg)
    RuntimeError: command returned non-zero exit status: 32
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>

@alfredodeza @andrewschoen is it expected to have the ceph-volume simple active failing on ceph-volume OSD previously scanned ?
If yes do we need something smarter by checking the ceph-volume inventory and ceph-disk OSD ?
Note that we're already doing something similar to this in ceph-container [1]
[1] https://github.com/ceph/ceph-container/blob/master/src/daemon/osd_scenarios/osd_volume_activate.sh#L6

@styleart Could you share the ansible inventory and the variables defined in group_vars/*.yml ?

@dsavineau the simple activate --all call looks in /etc/ceph/osd/*.json to activate everything that it finds. If there is nothing to activate then there shouldn't be anything in that directory. From the description in this issue, it seems that OSDs have already been migrated, but it is not clear to me if:

does that mean it is using ceph-disk OSDs that have been scanned?
Or nothing has been scanned and OSDs are LVs already?

If the OSDs are LVM already, created by ceph-volume, then there shouldn't be anything in /etc/ceph/osd/

@dsavineau sure! Maybe we just missed to reconfigure something after manual migration (beside switching from 'collocated' to 'lvm').
inventory (ini)
[mons]
ceph1-40-10.dc1.example.com
ceph1-40-11.dc1.example.com
ceph1-40-12.dc1.example.com

[osds]
ceph1-40-10.dc1.example.com
ceph1-40-11.dc1.example.com
ceph1-40-12.dc1.example.com

[mgrs]
ceph1-40-10.dc1.example.com
ceph1-40-11.dc1.example.com
ceph1-40-12.dc1.example.com

[rgws]
ceph1-40-10.dc1.example.com
ceph1-40-11.dc1.example.com
ceph1-40-12.dc1.example.com

[ceph:children]
mons
osds
mgrs
rgws

group_vars/osds.yaml
osd_scenario: lvm #we changed this one from 'collocated' to 'lvm' after manual migration
devices:
  - '/dev/sdc'
  - '/dev/sdd'
  - '/dev/sde'
  - '/dev/sdf'

osd_mkfs_type: xfs
osd_objectstore: bluestore

group_vars/ceph.yaml
ceph_mirror: http://download.ceph.com
ceph_origin: repository
ceph_repository: community
ceph_stable: true
ceph_stable_key: https://download.ceph.com/keys.release.asc
ceph_stable_release: nautilus
ceph_stable_repo: "{{ ceph_mirror }}/debian-{{ ceph_stable_release }}"
upgrade_ceph_packages: True

cluster: ceph
ceph_conf_key_directory: /etc/ceph
fetch_directory: fetch/
ntp_service_enabled: true
configure_firewall: false

monitor_interface: bond0
radosgw_interface: bond0

mon_group_name: mons
osd_group_name: osds
mgr_group_name: mgrs
rgw_group_name: rgws

ceph_mgr_modules:
  - status
  - dashboard

Btw: we managed to do the rolling update by commenting out two tasks:

name: scan ceph-disk osds with ceph-volume if deploying nautilus
name: activate scanned ceph-disk osds and migrate to ceph-volume if deploying nautilus

We also had to remove tasks for MDS, since we don't use it and playbook crashed on them. Just wondering, why it even tries to update MDS.
@alfredodeza that seems to be the reason, since we still have json files in /etc/ceph/osd/. Do we have to remove them? We just followed this guide for every disk: https://docs.ceph.com/docs/nautilus/rados/operations/add-or-rm-osds/#replacing-an-osd
Also, after the mimic to nautilus upgrade there's no ceph-disk binary anymore on hosts.

@styleart if all your OSDs are ceph-volume already, yes, remove all the /etc/ceph/osd/* files. You will also need to poke around at systemd and see if there are any unit files that were created in the process... you might need to delete any ceph-disk related ones

@alfredodeza just tested it out, removed files from /etc/ceph/osd and rebooted the node - everything came back automatically. I'll test the rolling update playbook again next days and give you a feedback. Thanks for the hint with json files so far :+1:

@styleart sure thing. I would ensure that there are no systemd issues, and all your (expected) OSDs are coming back fine. Thanks for reporting back!

@alfredodeza ok, just removed json files from all nodes and rebooted - no issues with systemd, everything came back and is running fine. Also did a playbook run - this time without any errors. Awesome, much thanks for your help! Issue can be closed :slightly_smiling_face:


Add more Python examples to create a Basic Kafka cluster

Just as the title states. This PR adds some examples Basic cluster creation. It mirrors the following examples from the upstream provider:
https://github.com/confluentinc/terraform-provider-confluent/tree/master/examples/configurations/basic-kafka-acls
https://github.com/confluentinc/terraform-provider-confluent/tree/master/examples/configurations/source-connector
Also a heads-up about the latest upstream provider version. It seems that they have renamed every resource and data source function to have a version suffix. See https://github.com/confluentinc/terraform-provider-confluent/commit/1662de74f435e9d0350ffdc7904a19fd1f0f79bc and the migration guide for 0.11.0.

Thanks for the PR, @praneetloke!


inlined imports should be rebased to current file

My problem is related to #42
Problem description
File import.css:
@import url(../otherdir/imported.css);
p.import
{
    background: url(import.png);
}

File otherdir/imported.css
p.imported
{
    background: url(import2.png);
}

Will fail by:
gulp.src(['dir/import.css'])
.pipe(cleanCSS({}))
.pipe(gulp.dest("out"))

with an Exception that ../otherdir/imported.css can not be resolved.
I had expected an outcome like this:
minified 'import.css':
p.imported{background:url(../otherdir/import2.png);}
p.import{background:url(import.png);}

I was not able to fix this problem by configuration, because the path of the current file is required to correct the rebaseTo option.
Solution
This fix always transports the file.path together with the contents to CleanCss.minify, which enables the imports of relative files.
A second problem occurred when inline: ['local'] is required. The image URLs defined in the imported css files were unexpected rebased to the current working directory. I had expected a rebase relative to the current file, so that the browser can import e.g. all images relative from the minified css file. Like in the sample above.
The patch ensures that the rebaseTo option is defined as the parent directory of the current processed file if not otherwise specified.

@jessebluemr thank you very much for your work! I've been trying to solve this one for a bit now and I'm very pleased to see you took the time to contribute for this one. I'll publish up a new version on npm shortly. Rock on!

@jessebluemr 3.4.1 now out in the wild

@scniro Thank you very much! It was a pleasure to contribute.


Added a navigation button to profile Page

Fixes : #93

@Akshithsaai
https://docs.google.com/forms/d/e/1FAIpQLSdnqJ5crpQFQEQXGTzekfKUxOJCXkSx8AykqvvHzlqBcNGMAQ/viewform
Nominate me if you liked my work and management

Ok @vansh-codes 👍🏻.
Thanks for giving me the opportunity to contribute.
I look forward to collaborate on any projects in future.
Reach me at<EMAIL_ADDRESS>

Sure @Akshithsaai
What about the image generation functionality, are you working on it? can you complete that?

Yeah I have read the api docs and I can show card showing those stats.
Should I generate an image having these stats or is it sufficient if I show them as info in a card?
@vansh-codes

show it as stats only, just I need the basic setup, then later modification can be done


support of fine-grained cpu orchestration in koordlet

What is your proposal:
Compatible with kubelet's existing CPU management policies. The CPU manager policy static allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity in the node. If enabled the static policy, the cluster administrator must configure the kubelet reserve some CPUs. There are some options for static policy. If the full-pcpus-only(beta, visible by default) policy option is specified, the static policy will always allocate full physical cores. If the distribute-cpus-across-numa(alpha, hidden by default) option is specified, the static policy will evenly distribute CPUs across NUMA nodes in cases where more than one NUMA node is required to satisfy the allocation.
Similarly, the semantics of the existing K8s Guaranteed Pods in the community should be compatible. The cpu cores allocated to K8s Guaranteed Pods with static policy will not share to the default best effort Pods, so it is equivalent to LSE. But when the load in the node is relatively low, the CPUs allocated by LSR Pods should be shared with best effort workloads to obtain economic benefits.
More details please refer to #96
Why is this needed:
Is there a suggested solution, if so, please add it:

[x] #232

[x] v0.5 #264
[x] v0.6 #345

[x] #233

[x] v0.5 #265
[x] v0.6 #346

[x] v0.6 #234

/assign @ZYecho

#232
#233
#234

/close


updated examples for train API

What this PR does / why we need it:
I have updated the HuggingFaceTrainerParams and trainer_parameters arguments in train API PyTorch examples.
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #2076

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 35.323%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
4380

Relevant Lines:
12400

💛  - Coveralls


Use of KMSKeyIDRef and KMSKeyIDSelector in all managed resources

What problem are you facing?

There are many places where KMS keys are used for different Crossplane managed resources.
Most of these managed resources only take KMSKeyID (eg: RDSInstance and Bucket) and others take KMSKeyID, KMSKeyIDRef and KMSKeyIDSelector (eg: DBCluster)
2 examples of theses resources that we frequently uses that don't have support for these fields are:
RDSInstance:
spec:
  forProvider:
    KMSKeyID: mykeyid

and
Bucket
spec:
  forProvider:
    serverSideEncryptionConfiguration:
      rules:
        - applyServerSideEncryptionByDefault:
            kmsMasterKeyId: mykeyid

How could Crossplane help solve your problem?

We would like to use these references and selectors in ALL the managed resources that don't have them
The following relates to #778 where we could use a KMS key alias as the KMSKeyID but prepended with "alias/" which could tell Crossplane to reference the key as an alias instead of an ID

The following resources are currently missing selectors for KMSKeyID:

[ ] cognitoidentityprovider/Userpools
[ ] database/RDSInstance (KMSKeyID)
[ ] database/RDSInstance (PerformanceInsightsKMSKeyID)
[ ] docdb/DBCluster
[ ] docdb/DBInstance (PerformanceInsightsKMSKeyID)
[ ] ec2/LaunchTemplateVersion
[ ] ec2/Cluster
[ ] kafka/Cluster (dataVolumeKMSKeyID)
[ ] mq/Broker
[ ] neptune/DBCluster
[ ] redshift/Cluster
[ ] s3/Bucket (replicaKmsKeyId)
[ ] secretsmanager/Secret (addReplicaRegions[].kmsKeyID)


[FEATURE]: Distributed computing

Describe the feature
I wanna do distributed training and inference on multiple node. How can I implement . Could you give me some examples codes? Thanks

Hi, you might want to check the Colossal AI tutorials: https://colossalai.org/docs/basics/launch_colossalai.


inventory: add new awx and bastillion servers

Signed-off-by: Stewart X Addison<EMAIL_ADDRESS>
Checklist

[x] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[x] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] inventory changes, ensure bastillion is updated accordingly

ACLs on infra machines TBC therefore not yet added into bastillion
Leaving the original ansible server in here for now as it is still available, although no longer being used

LGTM although I think we'll need to move critical services off GoDaddy.

Absolutely. I'm trying to collate that data and work to shut systems down on there under #1781. The bastillion server will be trivial to move


Minecraft in Linux

The first step is to download minecraft client (Java).
The you need to create an account: https://my.minecraft.net/en-us/store/minecraft/#register
The open account is not working, the "Loading store...." message never disappear an there is an error in JS console: TypeError: n is undefined All tried with Firefox and Chrome.

I have also downloaded a jar launcher at:
wget http://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.jar

Ok, time to close this ticket. The Java client is the one to be used in Linux. That's all.
For the server, we will see in the future the details.


Upgrade to v2.x results in 20+ load and 100% cpu usage

Hi @Webklex
For production we have a server with 32GB of RAM and 4vCPU's.
This server has been syncing 1000 folders every 2-3 minutes with no problem (using laravel's queue system and about 150 workers), RAM usage about 50-60% and CPU running at about 50 as well.
When upgrading to v2.x, the biggest changes came in with the namespaces and how we connect, but the syncing process still remained the same on my side:

Make connection
Get messages for folder
Loop over messages to process them
close connection

->all() also had to be added to the query along with the existing limit, as without this it seemed like no messages were getting returned, the query run for all these mailboxes are relatively straightforward, basically $folder->query()->setFetchBody(false)->all()->limit(10)->get()
When the version 2 update was deployed to production, we instantly started getting 20+ load on the server and 100% cpu usage. The specs on the server did not change, only the version of webklex/php-imap and webxklex/laravel-imap
From the below image you can see the spikes to 100% cpu usage whenever the sync got enabled

I had to revert back to v1 as I could not pinpoint why this was happening all of a sudden, with the only change being to the version of the package.
I tested on both a digital ocean and aws server with the same results, as soon as I enable v2 the server gets destroyed.
Do you have any idea what could be causing this drastic change in resource usage between the versions? Should I maybe not be calling ->all() even though I limit? Anything obvious you think I might have missed that could cause this when upgrading?

Hi @Webklex
Any idea on this one?

Hi @ricus-zero2one ,
thanks for your report.
I honestly don't know. I'm unable to reproduce this behavior.
Using Query::all() in general might be a bad idea - you'll fetch every available message. Try to limit the amount to only those ones you are actually interesting in. Using Query::since() might help :)
Additional information and available search criteria: https://www.php-imap.com/api/query
Best regards,

@Webklex The reason I added the all() was because just get() wasn't returning the results. But I think that might be the reason for the high resource usage if all() will def get all available emails.
What I want to do, is get the latest x amount of emails. On v1 I used the below:
$folder->query()->setFetchBody(false)->limit(10)->get()
But on v2 this doesn't return anything anymore, and that's when I added the all() as it then returned the emails. But I think me using limit in conjunction with all(), was resulting in it "seemingly" working as expected, because I would only get the x amount of emails, but behind the scenes it's requesting all of them?
My goal is simply to get the latest x amount of emails, what would be the v2 way to achieve this in the most efficient way?
I thought that ->get() would execute the query, but that doesn't seem to be the case with only limit being applied. Given the following: $folder->query()->limit(5)->get(); the result is just null as nothing seems to have been sent to the imap server yet:

If I add the since(), so now having $folder->query()->since(now()->subDay())->limit(5)->get() I do get the expected result:

However this seems like it will query all mails in the last day, so lets say for argument sake 200 for a busy mailbox, but then I only grab the latest 5 of that. With this I still queried way more than I need to.
Is there not a simple way to just get last x message in a mailbox? without querying more than I need and?
Regards

Hi @ricuss ,
please update to the latest release (>=3.2.0). There have been a lot of improvements :)
Feel free to reopen this issue if the problem persists.
Best regards,

Thanks @Webklex , I wasn't aware there is a new version 3, we are still running v1 in production (it's still syncing thousands of mailboxes every day without problem 👍  )
I'll take a stab at upgrading to v3 when I get a chance, thanks for the great work on this package!!


HTTP POST required for plugins since 2018-05-09

At once I get in a working setup (literally retriggering a Jenkins build from 2018-05-07):
TASK [geerlingguy.jenkins : Install Jenkins plugins
using password.] *********** failed: [my-jenkins-01] (item=ansicolor) =>
{"changed": false, "details": "HTTP Error 401: Invalid password/token for user:
admin", "item": "ansicolor", "msg": "Cannot get CSRF"}

This seems to be required since the 2018-05-09 release.
https://jenkins.io/security/advisory/2018-05-09/
SECURITY-794 / CVE pending

jenkins_plugin method doesn't support method=POST...

Testing versions: 2.107 / 2.107.2 were working.

@mkesper - What do you have set for jenkins_init_changes?

@mkesper you may want to add to that list:
  - option: "JENKINS_JAVA_OPTIONS"
    value: "{{ jenkins_java_options }}"

I do not gave found the fitting Java options, it seems. Did try:
jenkins_java_options: "-Djava.awt.headless=true -Djenkins.install.runSetupWizard=false"


Fix embargoed files download link not working on edit item page

References

Fixes #1361

Description
This fixes issue #1361 where you could not download an embargoed file from the edit item bitstream page.
Instructions for Reviewers

Created a new property in item-edit-bitstream.component.ts, bitstreamDownloadUrl: string

The property gets populated on the ngOnChanges method, calling getBitstreamDownloadRoute on the page's current bitstream

In the component's template the redirect is changed to this property, and the button is only shown if said property is not null

To test the fix:

Login as an administrator
Submit a new item with an embargoed file
Navigate to edit item
Navigate to the "Bitstreams" tab
Click on the download icon for the embargoed file
The file should now download as expected

Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

Merging this, as it was flagged for 1 approval & the code fixes here seem minor & obvious.


added resonsiveness in the Homepage

Closes #256
https://github.com/abi/screenshot-to-code/issues/256

@abi Can you review it fast, I have to delete the repo

Thanks for this!


introduce default log library

show and store more information for later use

branch feature/logger plans to tackle the issue

53dfccf7e9f34001982192a8102ff88f1deafae7 seems to resolve the issue


New NPM release?

Hey - love the library!
I'd like to take advantage of the new setDefaultLevel() method -- any chance we can get a new release on npm soon with that functionality?
Thanks :+1:

Thanks! There's a few more open changes that I'd like to get finalized and merged in the short term, but there'll definitely be one coming within the next few weeks.

hey @pimterry what's the latest with getting this on npm?

Hi @davetayls, done now! There's a 1.4.0 release out including all the recent changes.

Thanks!


Remove vendor directory.

Changes
This was something previously brought up in #1607, but was deferred to
allow for continued discussion.
Pros of making this change:

Reduces size of incoming PRs when new dependencies are used.
Removes confusion around source of truth for dependencies (e.g. vendor
vs mod). This was an issue that #1763 solved by pinning to vendor, this
will solve the same problem differently by always deferring to the
version in go.mod.
Allows easier use of upstream and dependent types without the use of vendor tools - see https://gist.github.com/wlynch/325293bc3fbc488d3b3d319f3a93bbea for an
example of why this is difficult today.

Risks of making this change:

Dependencies will not be present in initial clone. They will be
fetched dynamicly when needed, which may cause workflow distruptions.
This breaks compatibility with older versions of Go (though for
certain projects like triggers, we already require Go >= 1.13).

Third-party obligations (for things like making source available in
images) have already been addressed in #1607.
As with #1607, this change is more easily viewed by running git diff master -- ':!third_party' ':!vendor'
This should have no functional change for users (and ideally, even devs).

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[n/a] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

/cc @bobcatfish @ImJasonH @vdemeester

/hold

/hold

Pros of making this change:
* Reduces size of incoming PRs when new dependencies are used.

* Removes confusion around source of truth for dependencies (e.g. vendor
  vs mod). This was an issue that #1763 solved by pinning to vendor, this
  will solve the same problem differently by always deferring to the
  version in go.mod

Yes, this is kinda of a problem with go.mod. With vendor we should use -mod=vendor on the CI to make sure we are using it as soruce of truth.

* Allows easier use of upstream and dependent types without the use of
  vendor - see
  https://gist.github.com/wlynch/325293bc3fbc488d3b3d319f3a93bbea for an
  example of why this is difficult today.

What was the setup for this ^^. go env, …

Risks of making this change:
* Dependencies will not be present in initial clone. They will be
  fetched dynamicly when needed, which may cause workflow distruptions.

* This breaks compatibility with older versions of Go (though for
  certain projects like triggers, we already require Go >= 1.13).

This is already the case with pipeline, we require go 1.13 too (the error wrapping thing %w is used in the codebase).
There is additional problems, although more on go modules themselves that vendor or not:

Some tooling and "downstream" integration require vendor (or at least, we do at Red Hat).
go.mod is kinda unpredictable in what it gives, depending on the go version. This is a problem today with the vendor folder (that can change depending on who did what with which go version). This is something that worries me a bit.

As an example on this "unpredictability", cleaning my go setup (pkg, cache, …), I, somehow can't re-run successfully ./hack/update-codegen.sh
~/s/g/t/cli fix-thirdparty !102 ⛄ λ ./hack/update-deps.sh
Error: cannot register licenses from archive: open<EMAIL_ADDRESS>no such file or directory
Usage:
  licenses save <package> [flags]Flags:
      --force              Delete the destination directory if it already exists.
  -h, --help               help for save
      --save_path string   Directory into which files should be saved that are required by license termsGlobal Flags:
      --alsologtostderr                  log to standard error as well as files
      --confidence_threshold float       Minimum confidence required in order to positively identify a license. (default 0.9)
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory
      --logtostderr                      log to standard error instead of files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
  -v, --v Level                          log level for V logs
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered loggingF1223 15:11:26.148430  531560 main.go:43] cannot register licenses from archive: open<EMAIL_ADDRESS>no such file or directory

This worries me as, at least with a vendor folder, I have the guarantee it will work (as the code to compile it, …) is there, on the working directory.
Also go.mod and "tooling" acts in a really weird way, or more accurately, right now, our CI is a bit out-of-sync. We are using a tools.go to depend to tooling, which means few things

tooling dependencies become the project dependency, leading to, sometimes, dependency problems/conflicts…
depending on if you do a go install from the project or not, you will end up with a different version of the tool. This is true for the CI, where we install the tooling while creating the image it will run into. This has the advantage of not getting/installing it each time, but the disatvantage of having a version of the tooling that has nothing to do with what is present in the go.mod. This is probably what causes the error above.

* Allows easier use of upstream and dependent types without the use of
  vendor - see
  https://gist.github.com/wlynch/325293bc3fbc488d3b3d319f3a93bbea for an
  example of why this is difficult today.

What was the setup for this ^^. go env, …

This is the same main.go that you see, with no other files. Notably this would work if you created a go.mod or used dep, since the go tool would know how to handle and override these. This is only a minor win, but would help dependencies get up and running faster since if pipelines depended on the scm type directly tools could theoretically use it without go mod.

go.mod is kinda unpredictable in what it gives, depending on the go version. This is a problem today with the vendor folder (that can change depending on who did what with which go version). This is something that worries me a bit.

This is only for the initial version set though, right? This shouldn't change as long as you don't try and explicitly update (e.g. go get -u) a dependency.

This is only for the initial version set though, right? This shouldn't change as long as you don't try and explicitly update (e.g. go get -u) a dependency.

Well that’s my understanding. But depending on your go version, it doesn’t get the same deps, and.. on minor version like 1.13.1 vs 1.13.5 🤓

I'm thinking we close this for now until we make decisions around the vendor dir?

As an example on this "unpredictability", cleaning my go setup (pkg, cache, …), I, somehow can't re-run successfully ./hack/update-codegen.sh
~/s/g/t/cli fix-thirdparty !102 ⛄ λ ./hack/update-deps.sh
Error: cannot register licenses from archive: open<EMAIL_ADDRESS>no such file or directory
Usage:
  licenses save <package> [flags]Flags:
      --force              Delete the destination directory if it already exists.
  -h, --help               help for save
      --save_path string   Directory into which files should be saved that are required by license termsGlobal Flags:
      --alsologtostderr                  log to standard error as well as files
      --confidence_threshold float       Minimum confidence required in order to positively identify a license. (default 0.9)
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory
      --logtostderr                      log to standard error instead of files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
  -v, --v Level                          log level for V logs
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered loggingF1223 15:11:26.148430  531560 main.go:43] cannot register licenses from archive: open<EMAIL_ADDRESS>no such file or directory

This worries me as, at least with a vendor folder, I have the guarantee it will work (as the code to compile it, …) is there, on the working directory.

@vdemeester I'm running into the same issue, do you remember how you solved it? Asking 2+ years later 😅

For what is worth, it seems it's fixed by installing go-licences outside of the project folder (so that it doesn't use go.mod, etc.).


Bionic SRU

Please see https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1938286 for more information. TIA!

@mirespace, could you please TAL? TIA! \o/

Christian ack'ed the changes. Yay!


Fix the table format in expression-language.md

Add | to make the table correct and use \ to escape the | character inside the table. Not sure if this is the right way to fix but the preview page looks good.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yangminzhu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Deploy preview for preliminary-istio failed.
Built with commit 2f6dbba1585ce1e899f132ed19c2cdce16a0cb9e
https://app.netlify.com/sites/preliminary-istio/deploys/5b1042d411b73b07722cf03b

@geeknoid
I don't see how would this PR cause it? The log says it failed because unable (404) to find a lot of .png files.

Sorry, I've been playing with stuff and caused these 404. Once those are fixed, I'll rerun your changes and check them in after that.
Thanks for fixing this.


$scope.$watch is not a function in 0.13 ?

Title says it all. I seem to have trouble using $watch, basically a piece of code that worked. I noticed I am running 0.13. It does work with 0.12.30 so I am curious if there's a breaking change.
e.g
$scope.$watch('query', function(newValue) { console.log(newValue)});

0.13 has $watch (which uses ChangeDetector.watch), example https://jsfiddle.net/lega911/ubgv96ce/
the biggest change in 0.13, there are no local variables from al-repeat in scope, they are available via $getValue and declarative binding.
0.14 doesn't have scope and $watch, it uses ChangeDetector.watch directly.


Still using old version knex ?

Hi,
Is there a reason why @mikro/orm/knex  4.5.4 is still pinned on the old knex 0.21.19?
I see the the =version was updated in the repo almost two months ago but in all the npm packages released since the dependency is still the old one.
??

knex 0.95 is breaking as it drops support for TS and node versions that MikroORM v4 still supports, it will be part of v5


Add gomzyakov`s repositories to repositories.toml

ℹ Repository information
The repository has:

[x] At least three issues with the good first issue label.
[ ] At least 10 contributors.
[x] Detailed setup instructions for the project.
[ ] CONTRIBUTING.md
[x] Actively maintained.

@withshubh
Hello! Can you merge this PR?


Validate child component types

The protected XEO.Component#_setChild method should have the option to check the type of the given component, using XEO.Component#isType

Done.


Build UI

Build the outline of the UI and build the visual aspects of the components that will comprise it
Build the necessary CI/CD and or deployment processes that will automate the deploy of the site

Consider these resources:

https://tailwindcss.com/
https://github.com/thedevdojo/tails/


rtRemoteEnvironment log flooding causing log rotation issue

Reason for change: Huge number of identical log messages is being printed

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.


feat: Implemented region monitoring api

Added Userdefaults to save locations in the background/terminated state

Please don't merge this PR, close it. Thanks


Add Learning Resources domain to CDS website's security notice

📇 User story
The Learning Resources domain needs to be added to the CDS Security Notice because this informs the public that an vulnerability found within the Learning Resources website should be reported to CDS.
✅ Definition of Done

[ ] Inform the policy team of the Learning Resources domain to be added

📜 Acceptance criteria

[ ] The Learning Resources domain is present in the CDS Security Notice

Dependency, waiting for Caitlin come back from vacay to progress on this

resources.alpha.canada.ca is now added to the CDS security notice , as visible here


Advanced coin rotatation

The default coin rotation strategy is random.  We currently pick a coin from the configured list and run with it for the maximum amount of configured hours.
One enhancement would be to add analytics to the application to determine which configured coin holds the highest potential yield and rotate accordingly rather than rely purely on random selection.

Add configurable option in Settings to allow coin selection strategy to be picked.  Implement two strategies.
##Normal
Pick coins sequentially in the list based on the last coin rendered.  This gives the app a "playlist" feel so that the user can expect  which coin will be next.
##AI (Skynet)
Let the app pick the coin.  The first iteration of this will be randomized selection to give each coin an equal probability of running.  In later releases we can look into other factors such as analytics to make more educated selections.


Bump versions of Braket and PyBraket

Codecov Report
Base: 93.02% // Head: 71.57% // Decreases project coverage by -21.46% :warning:

Coverage data is based on head (ef9bf18) compared to base (bcf01d3).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #36       +/-   ##
===========================================
- Coverage   93.02%   71.57%   -21.46%
===========================================
  Files          33       33
  Lines        3684     3560      -124
===========================================
- Hits         3427     2548      -879
- Misses        257     1012      +755

Impacted Files
Coverage Δ

PyBraket/src/pyahs.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

PyBraket/src/pynoises.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

PyBraket/src/pyschema.jl
0.00% <0.00%> (-98.39%)
:arrow_down:

PyBraket/src/pygates.jl
0.00% <0.00%> (-97.06%)
:arrow_down:

PyBraket/src/PyBraket.jl
0.00% <0.00%> (-87.18%)
:arrow_down:

PyBraket/src/local_simulator.jl
0.00% <0.00%> (-81.09%)
:arrow_down:

PyBraket/src/pycircuit.jl
0.00% <0.00%> (-76.48%)
:arrow_down:

src/operators.jl
50.00% <0.00%> (-25.00%)
:arrow_down:

src/schemas.jl
97.05% <0.00%> (-2.95%)
:arrow_down:

src/qubit_set.jl
75.51% <0.00%> (-2.93%)
:arrow_down:

... and 16 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Outlined variant breaks a numerical TextField's arrow buttons

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When using a numerical TextField with variant="outlined" :

The cursor doesn't change to a pointer when hovering over the up/down buttons
Cant click the up/down buttons
Might be exclusive to firefox

Expected Behavior 🤔
Should be able to use up/down buttons to increment/decrement the value
Steps to Reproduce 🕹
https://codesandbox.io/s/relaxed-bouman-bxu8w?file=/src/Demo.tsx
Steps:

Create a TextField with type="number" and variant="outlined"
Open in firefox

Context 🔦
Cant use full functionality of the input element in forms with the desired styling
Your Environment 🌎
From my testing it appears to be OS independent, and only occurs with Firefox
   System:
    OS: Linux 5.8 Ubuntu 20.04.2 LTS (Focal Fossa)
  Binaries:
    Node: 15.11.0 - /usr/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 7.6.0 - /usr/bin/npm
  Browsers:
    Chrome: 89.0.4389.82
    Firefox: 88.0
  npmPackages:
    @emotion/styled:  10.0.27
    @material-ui/core: ^4.11.0 => 4.11.4
    @material-ui/envinfo: ^1.0.0 => 1.0.0
    @material-ui/icons: ^4.9.1 => 4.11.2
    @material-ui/lab: ^4.0.0-alpha.56 => 4.0.0-alpha.57
    @material-ui/pickers: ^3.2.10 => 3.2.10
    @material-ui/styles:  4.11.4
    @material-ui/system:  4.11.3
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react: ^16.9.56 => 16.14.5
    react: ^16.8.0 => 16.14.0
    react-dom: ^16.8.0 => 16.14.0
    styled-components: ^5.1.1 => 5.2.3
    typescript: ^4.0.5 => 4.2.4

I'm closing as we have no leverages


VSTS name change

Remove one reference to VSTS and change to Azure DevOps

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

ValidatePublishRequest
:warning:Warning

Details

[Error] Cannot sync git repo to specified commit because branch master has been deleted or has been force pushed: fatal: Could not parse object '1908f63791f06339a16f835daa5cb4c0547f7e62'.

ValidatePublishRequest

[Warning] Owner Pacort of repository https://github.com/MicrosoftDocs/vsts-docs has lost Admin permission. Please use Transfer Owner via OPS portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@ChristopherMank Thank you for your contribution. We have had some trouble with syncing between this public repo and our private repo, which has been resolved, but has caused an issue with PRs submitted during the interval in which the problem was unresolved. One of the side effects is a lot of extra files added to the PR and also some merge conflicts.
Can you respond and let me know which file in this PR has your changes and I will get them merged, or if you wish to close this PR and create a new PR with your changes in a branch based off the latest upstream master that would work as well (although that is more trouble and I apologize for that)
Thank you again for your contribution.

@steved0x No worries at all. I'll close this one and open a new one, no big deal. Thanks!


[Question]Any randomness in data reader? Any randomness in Model.fit?

Does data reader shuffle the input during loading? For example, shuffle within batch or inter-batch.
Does Model.fit shuffle the input during traning, so that, for example,  sample1/sample2/sample3 from input are trained out of order(assuming batch_size=1)?

Hi @heroes999 , which type of data readeryou're using?
Shuffle is supported for only DataReaderType_t.RawAsync and there is a knob  in AsyncParam to enable/disable the shuffle. The shuffle is inter batch.

Model.fit() would not do shuffle.

Get it. It seems shuffle is done by data prepare scripts. @JacoCheung


[1.2.0] UE4 activity no longer appears on WakaTime

Today I accidentally noticed that my UE4 activity is not being logged!
WakaTime receives the heartbeats, but they don't appear on the dashboard, so perhaps the raw heartbeat data is faulty.
The reason could be that the heartbeat's is_write param is null, but I'm not sure.
https://wakatime.com/api/v1/users/current/heartbeats?date=2021-08-01&show=machine_name,user_agent
To view raw heartbeat data for the currently logged-in account (change the date as appropriate).

Found the issue. You need to write at least one coding category heartbeat per session for it to appear on WakaTime. I tried it directly out of cmd and now all my UE4 activity for today appeared.

Make sure you do this once in a while, possibly when exiting the engine.

When submitting a heartbeat on save, it seems to be necessary to include --write true, so WakaTime understands and counts the activity correctly.

When submitting a heartbeat on save, it seems to be necessary to include --write true, so WakaTime understands and counts the activity correctly.

Ah, you have it there. Well, for me it doesn't work. That boolean is false when even when saving.

I believe I started working with it, however the engine was for some reason crashing, when I was using the --write; however, I can test if thats still the case (It was crashing the VR project template, so there might be a weird collision?).

I assume I never encountered this issue, as I never used just UE4 during a day; it was always combined with other IDE, or it was after work, which naturally already submitted the heartbeats with --write.
I will try to add it into the save event, as that feels like where it should be.

Tried it with the latest version, however, I am unable to reproduce the issue. (however, I do have cmd $ wakatime)

So I assume this only happens without it. As I promised, I will look into the plugin soon, to figure out this issue.
If it is no longer crashing the VR template, I will just enable --write for file save event.

I modified my local copy to fix the issue by forcing the --write param at all times, though I haven't used the VR template, so can't say if it's crashing or not.

Managed to get my time tracked properly even without any kind of wakatime installed (which means the plugin downloaded it on its own).
Sadly, I dont have much time to test it now, but I will get to it... soon... I promise!

Checked within the VR template after enabling --write in c99de9c73c0cf8d0f4552f490f047e43ebd083c5.
Everything looks correct, closing the issue as solved with version 1.2.1


messaging/unknown-error when using sendEachForMulticast

Operating System version: AWS Lambda
Firebase SDK version: firebase-admin 12.3.0 (but also previous versions)
Firebase Product: message notification
Node.js version: Node.JS 18
NPM version: 9

I have a project that send notification messages to Android and IoS. We use sendEachForMulticast method. It worked fine for several months. But recently we started to receive the following error:
{
"code":"messaging/unknown-error"
"message":"Operation is not implemented, or supported, or enabled. Raw server response: "{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}""
}

We create the messages, using the MulticastMessage type, with the following structure:
{
      tokens: [token1, token2],
      data: {
         // ... (string->string)
      },
      android: {
        priority: 'normal',
        ttl: TTL_SECONDS * 1000,
      },
      fcmOptions: {
        analyticsLabel: 'my-label',
      },
      apns: {
        payload: {
          aps: {
            alert: {
              titleLocKey: 'key1',
              locKey: 'key2',
              locArgs: ['value1'],
            },
          },
          contentAvailable: true,
        },
        headers: {
          'apns-expiration': `${Math.floor(Date.now() / 1000) + TTL_SECONDS}`,
        },
      },
    };

Any ideas of what can be the problem? It could be related to https://firebase.google.com/docs/cloud-messaging/migrate-v1?authuser=0&hl=en ?

Sorry, my fault. I still used sendMulticast deprecated method.

sendMulticast

hi what should we use instead?

sendEachForMulticast
From the latest version of the lib

Hi Team,
Issue :
Facing inconsistent push notifications. With same token without any changes push notifications works for some times and does not works some times.
Platform : Android and IOS
Codebase : node.js
Firebase-admin sdk version : 12.4.0
Node.js version: Node.JS 20
Sample node code :
let message = {
  tokens: array of fcm tokens
  notification:
    {
       title: "test_title",
       body: push notification message,
    },
  data:
    {
       data: payload,
       alertType: "crash",
    },
};

let response = await firebaseAdmin.messaging().sendEachForMulticast(message);

The error message is random and either one of them

{"success":false,"error":{"code":"messaging/mismatched-credential","message":"SenderId mismatch"}}

{"success":false,"error":{"code":"messaging/unknown-error","message":"Operation is not implemented, or supported, or enabled. Raw server response: "{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}""}}

{"success":false,"error":{"code":"messaging/registration-token-not-registered","message":"Requested entity was not found."}}

Hi Team,
Issue : Facing inconsistent push notifications. With same token without any changes push notifications works for some times and does not works some times.
Platform : Android and IOS Codebase : node.js Firebase-admin sdk version : 12.4.0 Node.js version: Node.JS 20
Sample node code :
let message = {
  tokens: array of fcm tokens
  notification:
    {
       title: "test_title",
       body: push notification message,
    },
  data:
    {
       data: payload,
       alertType: "crash",
    },
};

let response = await firebaseAdmin.messaging().sendEachForMulticast(message);

The error message is random and either one of them

{"success":false,"error":{"code":"messaging/mismatched-credential","message":"SenderId mismatch"}}
{"success":false,"error":{"code":"messaging/unknown-error","message":"Operation is not implemented, or supported, or enabled. Raw server response: "{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}""}}
{"success":false,"error":{"code":"messaging/registration-token-not-registered","message":"Requested entity was not found."}}

Same Issue

Where is it stated that sendEach is deprecated? https://firebase.google.com/docs/reference/admin/node/firebase-admin.messaging.messaging#messagingsendeach Its still in the docu. Thanks for the answer I couldnt find out whats wrong since they secretely changed the method and the error response is misleading, also tests are misleading because for some of the requests they let it go through while randomly others get refused!:D

same issue
Platform : Android and IOS
Codebase : node.js
Firebase-admin sdk version : 12.2.0,
Node.js version: Node.JS 20.12.1
use fn : sendAll()

Sometimes attempts with the same token will fail and sometimes they will succeed.

same issue
Platform : Android and IOS Codebase : node.js Firebase-admin sdk version : 12.2.0, Node.js version: Node.JS 20.12.1
use fn : sendAll()
Sometimes attempts with the same token will fail and sometimes they will succeed.
[ERROR]
[2024-09-12T04:43:08.339Z]  500   ERROR: (Error)Operation is not implemented, or supported, or enabled.
Raw server response:
"{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}"

try sendEachForMulticast
https://firebase.google.com/docs/reference/admin/node/firebase-admin.messaging.messaging.md#messagingsendeachformulticast

same issue
Platform : Android and IOS Codebase : node.js Firebase-admin sdk version : 12.2.0, Node.js version: Node.JS 20.12.1
use fn : sendAll()
Sometimes attempts with the same token will fail and sometimes they will succeed.
[ERROR]
[2024-09-12T04:43:08.339Z]  500   ERROR: (Error)Operation is not implemented, or supported, or enabled.
Raw server response:
"{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}"

try sendEachForMulticast https://firebase.google.com/docs/reference/admin/node/firebase-admin.messaging.messaging.md#messagingsendeachformulticast

nice!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

same issue
Platform : Android and IOS Codebase : node.js Firebase-admin sdk version : 12.2.0, Node.js version: Node.JS 20.12.1
use fn : sendAll()
Sometimes attempts with the same token will fail and sometimes they will succeed.
[ERROR]
[2024-09-12T04:43:08.339Z]  500   ERROR: (Error)Operation is not implemented, or supported, or enabled.
Raw server response:
"{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}"

try sendEachForMulticast https://firebase.google.com/docs/reference/admin/node/firebase-admin.messaging.messaging.md#messagingsendeachformulticast

Thanks u really save my day 😄 !!
According to the change log, we may upgrade to >=11.7.0
https://firebase.google.com/support/release-notes/admin/node#cloud-messaging_2

const response = await admin.messaging().sendEachForMulticast(messageSend);  // Use sendMulticast
use this function didnt get any response further

const response = await admin.messaging().sendEachForMulticast(messageSend); // Use sendMulticast use this function didnt get any response further

Any Error Response ?

sendEachForMulticast From the latest version of the lib

Thanks a lot.

Push notifications are not being delivered in the Android Edge browser when using:
await this.app.messaging().sendEachForMulticast(message); Notifications work as expected in all other browsers.


fix(jest): fix "jest/globals" is unknown

'jest/globals' env now is unknown for eslint. Used 'jest' instead like it was suggested here https://github.com/jest-community/eslint-plugin-jest/issues/44#issue-286150080

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


FBX animation - wrong orientation when actor is created

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior:
When actor is created from load FBX animation, it needs to be manually rotated by +90 degrees in X.
Expected Behavior:
We should either change how it is imported to fix it or add additional logic to automatically perform the rotation. @LiborBatek might have solution for correct steps during the FBX import?
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
Load published FBX animation and drop it to the level (instantiate an actor from it) - observe wrong rotation.
Are there any labels you wish to add?

[X] I have added the relevant labels to the bug report.

Relevant log output:
No response
Additional context:
No response

Resolved by  https://github.com/ynput/ayon-unreal/pull/35


Abstract MGM port: afuncon

References #49

[ ] port the afuncon function from Matlab
[ ] test the afuncon result compared to the matlab result

began porting over afuncon while waiting for  the constructer and interopOp functions to test the 2d class
extended the abstract testing class with a test for afuncon
got some uh before and after data of one of the rounds of afuncon from Matlab
began implementation of afuncon
having issues adding the lh sparse matrix * temp  to the 2401x1 matrix of the 2nd multiplication operation. thinking it might be because one is a sparse matrix and one isnt

[t:60]


Medusa float

new dbhandle;
EstablishConnection(dbhandle);

new string[128];
new Float:medusa = -9.170000;
printf("%f", medusa);
mysql_format(dbhandle, string, sizeof string, "%.2f", medusa);
print(string);
format(string, sizeof string, "%.2f", medusa);
print(string);

[19:05:38] -9.170000
[19:05:38] -9..70
[19:05:38] -9.17

I caught that in the wild causing me query errors. Usually %.2f works fine, just this error caught my eye

If that changes anything, I'm running MariaDB

https://github.com/pBlueG/SA-MP-MySQL/blob/8a4dc482ea66a33d0ff99b1598c8f897bf35768b/src/natives.cpp#L996 this is only instance adding dots that I can see

After a little bit of investigation I discovered that it happens for number such as -9, -99, -999, etc. with fraction part other than 0, so -9.01, etc.

Are you using R39 or R40?

R39-4

Yep, that's definitely a bug.


Update version of k8s and some tools in CI

This PR updates the version of Kubernetes and some tools in the CI.
After this CI passed, we can support new versions of Kubernetes (v1.26 and v1.27) in our Scalar Helm Chart.
Please take a look!

I ran the CI manually to test the deployment of all charts with these new versions. As a result, the CI succeeded.
https://github.com/scalar-labs/helm-charts/actions/runs/5263523003


Missing dependencies in instructions

Hello again, i'm just creating issues for the things i notice while trying to run the pipeline.
There seems to be a couple of dependencies missing in the installation instructions.

Mutect
SnpEff
VarDictJava

Thanks a lot for reporting these issues.
It's quite hard to notice them.

Duplicated with #120


Datasource 'localhost' navigator node not found

Description
Right after upgrading DBeaver community version to the newest version, I can't work with it at all. What I get is an error message on any tab I open that says "Datasource 'localhost' navigator node not found". Also, instead of exit, there is an "Emergency Exit" dropdown option in the File menu.
DBeaver Version
<IP_ADDRESS>406021658
Operating System
Windows 11
Database and driver
PostgreSQL (can't seem to find version in settings but I have PostgreSQL 15 running)
Steps to reproduce
Just upgrade and start.
Additional context
No response

Cannot reproduce.
Could you attach debug log file?
https://dbeaver.com/docs/dbeaver/docs/dbeaver/Log-files/ (or you can use main menu Help->Collect diagnostic info)

Thanks for the speedy answer. Here is the diag file.
dbeaver-diagnostic-info-1717397047239.zip

Thanks,
It looks like something is wrong with the app configuration.
Could you try to reset workspace state (Help->Reset settings).
It may delete some UI preferences but all connections and scripts will remain

I had the same issue. Happened since the last update. All good now, thanks.

Actually, for me also. I thought it waas sorted, but now it's happening again. Definitely something in the last update caused this. Resetting makes no difference.

Hello, I have the same issue since i changed my PC and updated DBeaver with the latest version V24.1.2 .
Every time I close DBeaver while I have some table tabs opened, when i re-open DBeaver, i have error messages like "Datasource 'localhost' navigator node not found"  and my database is automatically deleted. Not the connexion, only the database.
I didn't found any solution, and I have to re-create the database every time i close my pc, which is really annoying.
Resetting does not work for me, neither deleting and re-downloading DBeaver.


Paste File when filenames contain non-URI-safe characters

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[x] Misc (Choose this if your not sure)

Describe the bug
If I copy the path name of a file called, for example, John’s PhD Thesis.pdf and then invoke Dendron’s Paste File command, the PDF is copied as-is to the assets folder and the following link is created in my Dendron note:
[John’s PhD Thesis.pdf](assets/John’s PhD Thesis.pdf)

Unfortunately, due to the spaces in the file name this does not render as a link in the preview pane, instead the markdown is rendered literally. This may also cause problems (although I haven’t tested) during Site Build.
Expected behavior
At the very least file names should be URL-escaped. However, as the behaviour of Paste File is modelled on Paste Image I think it would be more consistent and probably more robust to kebab-case the file name when it is copied into Dendron, and to prepend the date to the filename to protect against the possibility of adding two different documents with the same filename.
Desktop (please complete the following information)

OS: macOS 11.4
Dendron Version: 0.43.0

This should be fixed in 0.43.1

@all-contributors add @ddbrierton for bug


fix(stable/cockroachdb): Add an explicit selector to the StatefulSet

This was preventing any upgrades because kubernetes made the selector
immutable and the chart version changes between upgrades of charts.
fix #8102
Signed-off-by: Rio Kierkels<EMAIL_ADDRESS>Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Upgrade path is tested with kubernetes 1.10 on minikube with versions:

1.1.1 -> 2.0.0
1.2.6 -> 2.0.0

Many thanks, @Rio!
/ok-to-test
/lgtm
/approve


JIRA SUBTASK action in JIRA pack

Currently we have the JIRA actions to create a JIRA ticket, to update JIRA fields , to link one issue with the other issue but could not see any action where in we can have the option to create a subtask under the same ticket.
Could we have it in the pack please?

👋 Hello @zsmanjot! Thankfully you can use the create_issue action to create a subtask under another ticket. Running it via the st2 client would look something like this:
st2 run jira.create_issue summary="Test Subtask" type="<name_of_subtask_issue_type>" extra_fields='{"parent": {"key": "<key_of_parent_jira_ticket"}}'

You'll need to know what type corresponds with subtasks in your JIRA org. Once you have that, you should be set. If you need to find out what issue types exist, you can use the jira api createmeta endpoint to discover which ones will work.

Also @zsmanjot if this is insufficient, it is possible to create an action that makes this more straight-forward, perhaps by using the jira python library to call createmeta(), accept a type as a parameter and a key for a parent. It could iterate over the available types and ensure the one specified is a subtask and fail if not.
Either way, if my suggestion above is sufficient, please respond. If not, I think I'd be up for creating an action to do this specific thing.

Thanks for the excellent suggestions @jpavlav . Apologies for not digging a little deeper on this one. @zsmanjot if the suggestions above work for you can we close this issue? Thanks!

Hi @jpavlav
Thanks for the help and yes i tried it but, it does ask for some extra inputs that needs to be provided. I will try it out again.
@floatingstatic Yes sure , this issue can be closed. I will update with my findings later.