Add hover explanations

During our Healey School start of school year pilot we heard from many educators spanning grades, subjects, etc. Not all educators understood the terminology asking:

"What does <= 2 level of need mean?"
"What does 4.3 ACCESS level mean?"

@alexsoble @AmirHadjihabib: Let's add a hover for the items that we received the most questions on "what does this mean?"

Level of Need

http://www.doe.mass.edu/sped/iep/forms/pdf/PL3.pdf

ACCESS

https://www.wida.us/assessment/access/#scores

Have this design from an earlier version. Working on creating the metaphor of dotted underlined items  being hoverable with explanations.

https://www.dropbox.com/sh/88i1idb70xovhkk/AACJAf60rZ-b_7-MsgBat_MGa?dl=0

Yes @AmirHadjihabib exactly, we should add hovers with explanations for:

ACCESS
Disability: Level of Need
Language Fluency (bunch of acronyms)

... and possibly a few more although the above two are the main ones we heard repeatedly.
I can draft the language of what the descriptions will sound like.

Another hover explanation:
"Could a small text box with the cut-off scores be added to EACH assessment (MCAS, STAR, etc) . Teachers may not know what score constitutes a Needs Improvement vs a warning. Maybe the student just missed proficient by one point. Providing the ranges is helpful." - Cheryl

Need to split this up, we will implement this for individual pages.


Add blend modes and adjust composition to use Porter Duff

Add blend modes as specified in composition and blending level 1 spec. Blending will perform the blend and alpha composition using Porter Duff Source Over.
We will rename the overlay method so as not to be confused with the overlay blend mode. It will now be called composite and will be a shortcut for c1.blend(c2, 'normal').
Still have to write unit tests, but general testing was done and compared with Chrome, Firefox, and Safari. We were able to get similar results for both sRGB and Display P3.

Should we combine blend and composite into one function? Currently, it is one function even if the API exposes two. Or, should we somehow separate them?

So, everything is consolidated into the compose method now (much better than composite). It is possible to turn off blending by setting the blend parameter to False. It is also possible to turn off the alpha compositing by setting operator (for compositing operator) to False. I'm not sure we need a blend function that only does blending or an alpha_compose function. But I guess if a convenience function was desired, we could add it in the future.
In the process, we went ahead and added all the different Porter Duff composing methods for fun.

@gir-bot lgtm


What is good value of total loss or  another loss ?

Hello,
I want to know some of recommendation for value in loss to stop training. For example, in your case with dataset what is the loss final of best ckpt. Thank you !
Best regard

@hoangkhoiLE For yolox-l, it should be 2 or 3 on COCO. For yolox-nano, it should be 6~7.

@Joker316701882 Thank you for your help


Revert "Added support for restic --verify flag"

This reverts commit ac70167844cd464e8fbf5dda0b3cbdf35cbb1a23.
Reverting on konveyor_1.7.1 -- once we have a refactored commit with
non-CRD-changing functionality, this revert and the original commit
will be removed.

The plan here is roughly as follows:

Revert restic verify on 1.7.1, use that as the base for OADP 1.0 GA
In the meantime, use the last OADP release which includes the reverted commit for MTC development/testing
Refactor restic verify on konveyor_dev to implement the same functionality without modifying upstream CRDs. Instead, we'll use annotations.
Future OADP release will re-introduce this functionality with the refactored commit, preserving the upstream CRDs, and this will the basis for the next MTC release.


Short solution needed: "Using GD example " (php-gd)

Please help us write most modern and shortest code solution for this issue:
**Using GD example ** (technology: php-gd)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

Using GD example


Send push notifications if a nearby location needs an image

Suggested by Tobias1984 on my grant page:

Would be good if users could set up a Radius where they get push notifications if a missing image location is for example just 1 km away. --Tobias1984 (talk) 09:40, 3 July 2016 (UTC)

I think this could be doable later on after the 'display nearby images lacking articles' task has been completed, what do you think? If we do this we should probably have a setting for users to choose whether they want the notifications or not.

Nice idea!
We would probably need to run some server-side code to achieve this.
I am not sure we can use Google's push service, so anyone feel free to post ideas of the technology we could use to develop this feature, thanks!
Client-side library must be open source and service must be compatible with Wikimedia's privacy policy.

Sounds like #79 if I am not mistaken?

Oh, yeah, sorry. I missed that one. :)


graphql-code-generator IResolvers types are not compatible with IResolvers from graphql-tools

Describe the bug
When I try to use graphql-codegen-typescript-resolvers  on my resolvers with makeExecutableSchema from graphql-tools I get a type error.
To Reproduce
When using this code
import { makeExecutableSchema } from "graphql-tools";
import { IResolvers } from "@generated/apollo";

const resolvers: IResolvers = {
  Query: {},
  Mutation: {},
};

const schema = makeExecutableSchema({
  typeDefs: importSchema("./src/schema.graphql"),
  resolvers,
});

I get the following error message
Type 'IResolvers<ApolloContext>' is not assignable to type 'IResolvers<any, any> | IResolvers<any, any>[] | undefined'.
  Type 'IResolvers<ApolloContext>' is not assignable to type 'IResolvers<any, any>'.
    Index signature is missing in type 'IResolvers<ApolloContext>'.

I think this happens because the types from graphql-code-generator for IResolvers types are not compatible with IResolvers types from graphql-tools.
Environment:

OS: macos
Codegen: ^0.16.0
Node: v10.13.0

Hi @ellipticaldoor ! Thank you for reporting it.
There is an existing issue related to it: https://github.com/dotansimha/graphql-code-generator/issues/1133


Improve Promise type definition

This change modifies the overloads for then and catch of Promise<T>, and the overloads for then of PromiseLike<T> to provide better type inference.
Fixes #4903

@sandersn, @vladima: care to take a look?

:+1:

The change in 9d4219a fixes an existing issue with assignability between Promise<T> and PromiseLike<T>. Unfortunately, this means that some cases in this change that should result in Promise<never> retain the T of the antecedent promise. This is a result of how we erase uninstantiated generic type parameters to any and how any compares to never. A more comprehensive solution to address this is out of scope of this PR, as this still provides an improvement over our existing type definition for Promise<T>.

@sandersn, @vladima can you take another look at these typings? The order of the overloads is intentional and very specific to get the best typings with respect to never and how undefined | null are handled depending on the value of strictNullChecks.

👍

@mhegazy, do you want to take this change for release-2.0 as well?

no. jsut 2.1 please.


Improve parameter naming and documentation in GraphEdit and GraphNode

Closes https://github.com/godotengine/godot/issues/37227.
Supersedes https://github.com/godotengine/godot/pull/40043.
This PR revives the aforementioned PR and improves on it. I've tried to clean up the language and introduce some consistency to the terms slots and ports. Slots are child controls, ports are their left and right connection acceptors. As such, GraphEdit doesn't work with slots, it only works with ports and their connections.
Like the original PR I've added a method to retrieve the slot index from the port, but it's actually two methods to keep in sync with the rest of the API for similar things. I've also renamed some internals for consistency and clarity. But the most important part for the users is the improvements to the documentation. Parameters should now have clear names respecting their quality without any mix-ups, and the descriptions have been tuned up.
I think this should reduce the confusion around slots and ports to the minimum without breaking any compatibility. (So it can be backported to 3.x if anyone is willing).

@fire Now GraphEdit uses only the term port because that's what it works with. It was always ports, it was just mislabeled in a lot of cases. GraphNode, in turn, uses both terms, where slot is the "row" added by the child control and "port" is one of the slot's two connection dots.


cli: implement ps command

ps command is used by docker top to show
the processes running inside the container
partially fixes #95
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

depends on https://github.com/containers/virtcontainers/pull/269

Still blocked on https://github.com/containers/virtcontainers/pull/269.

@devimc please rebase this PR in order to get the CI properly running.

@sboeuf  changes applied

@devimc Thanks !

LGTM

The code looks good, but:

Terminal 1:

$ sudo docker run -ti busybox sh

Terminal 2:

$ sudo cc-runtime ps
panic: runtime error: slice bounds out of range

goroutine 1 [running, locked to thread]:
panic(0x7e3a40, 0xc1df20)
        /usr/lib/go-1.8/src/runtime/panic.go:531 +0x1cf fp=0xc4200cd848 sp=0xc4200cd7b0
runtime.panicslice()
        /usr/lib/go-1.8/src/runtime/panic.go:35 +0x5e fp=0xc4200cd868 sp=0xc4200cd848
main.glob..func9(0xc420086640, 0x0, 0xc420086640)
        /home/james/go/src/github.com/clearcontainers/runtime/ps.go:37 +0x104 fp=0xc4200cd8d0 sp=0xc4200cd868
github.com/clearcontainers/runtime/vendor/github.com/urfave/cli.HandleAction(0x7cc4c0, 0x865788, 0xc420086640, 0xc42005c500, 0x0)
        /home/james/go/src/github.com/clearcontainers/runtime/vendor/github.com/urfave/cli/app.go:485 +0xd4 fp=0xc4200cd8f8 sp=0xc4200cd8d0
github.com/clearcontainers/runtime/vendor/github.com/urfave/cli.Command.Run(0x84ec62, 0x2, 0x0, 0x0, 0x0, 0x0, 0x0, 0x860c14, 0x34, 0x0, ...)
        /home/james/go/src/github.com/clearcontainers/runtime/vendor/github.com/urfave/cli/command.go:207 +0xb72 fp=0xc4200cdcd8 sp=0xc4200cd8f8
github.com/clearcontainers/runtime/vendor/github.com/urfave/cli.(*App).Run(0xc42008c680, 0xc42000c300, 0x2, 0x2, 0x0, 0x0)
        /home/james/go/src/github.com/clearcontainers/runtime/vendor/github.com/urfave/cli/app.go:250 +0x7d0 fp=0xc4200cdef8 sp=0xc4200cdcd8
main.createRuntimeApp(0xc42000c300, 0x2, 0x2, 0xc420017200, 0xc4200171d0)
        /home/james/go/src/github.com/clearcontainers/runtime/main.go:297 +0x1be fp=0xc4200cdf40 sp=0xc4200cdef8
main.createRuntime()
        /home/james/go/src/github.com/clearcontainers/runtime/main.go:338 +0x4a fp=0xc4200cdf78 sp=0xc4200cdf40
main.main()
        /home/james/go/src/github.com/clearcontainers/runtime/main.go:345 +0x20 fp=0xc4200cdf88 sp=0xc4200cdf78
runtime.main()
        /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc4200cdfe0 sp=0xc4200cdf88
runtime.goexit()
        /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc4200cdfe8 sp=0xc4200cdfe0

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420034fe8 sp=0xc420034fe0

goroutine 2 [force gc (idle)]:
runtime.gopark(0x865d18, 0xc49230, 0x8532a9, 0xf, 0x865c14, 0x1)
        /usr/lib/go-1.8/src/runtime/proc.go:271 +0x13a fp=0xc420022768 sp=0xc420022738
runtime.goparkunlock(0xc49230, 0x8532a9, 0xf, 0xc420000114, 0x1)
        /usr/lib/go-1.8/src/runtime/proc.go:277 +0x5e fp=0xc4200227a8 sp=0xc420022768
runtime.forcegchelper()
        /usr/lib/go-1.8/src/runtime/proc.go:226 +0x9e fp=0xc4200227e0 sp=0xc4200227a8
runtime.goexit()
        /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc4200227e8 sp=0xc4200227e0
created by runtime.init.4
        /usr/lib/go-1.8/src/runtime/proc.go:215 +0x35

goroutine 3 [GC sweep wait]:
runtime.gopark(0x865d18, 0xc49440, 0x852786, 0xd, 0x41e814, 0x1)
        /usr/lib/go-1.8/src/runtime/proc.go:271 +0x13a fp=0xc420022f58 sp=0xc420022f28
runtime.goparkunlock(0xc49440, 0x852786, 0xd, 0x14, 0x1)
        /usr/lib/go-1.8/src/runtime/proc.go:277 +0x5e fp=0xc420022f98 sp=0xc420022f58
runtime.bgsweep(0xc420052000)
        /usr/lib/go-1.8/src/runtime/mgcsweep.go:56 +0xb6 fp=0xc420022fd8 sp=0xc420022f98
runtime.goexit()
        /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420022fe0 sp=0xc420022fd8
created by runtime.gcenable
        /usr/lib/go-1.8/src/runtime/mgc.go:212 +0x61

goroutine 4 [finalizer wait]:
runtime.gopark(0x865d18, 0xc647f8, 0x852e4f, 0xe, 0x14, 0x1)
        /usr/lib/go-1.8/src/runtime/proc.go:271 +0x13a fp=0xc420023718 sp=0xc4200236e8
runtime.goparkunlock(0xc647f8, 0x852e4f, 0xe, 0x14, 0x1)
        /usr/lib/go-1.8/src/runtime/proc.go:277 +0x5e fp=0xc420023758 sp=0xc420023718
runtime.runfinq()
        /usr/lib/go-1.8/src/runtime/mfinal.go:161 +0xb2 fp=0xc4200237e0 sp=0xc420023758
runtime.goexit()
        /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc4200237e8 sp=0xc4200237e0
created by runtime.createfing
        /usr/lib/go-1.8/src/runtime/mfinal.go:142 +0x62
[1]    7338 abort (core dumped)  sudo cc-runtime ps

@jodh-intel  good catch!
fixed, thanks

@sboeuf @jodh-intel  changes applied
thanks

Hi @devimc - the code looks good, but if I test this branch with  https://github.com/clearcontainers/agent/pull/90 (using osbuilder) I still get this error:
$ sudo cc-runtime ps 23ed87733d1e2258d7d31b0bee5adf46b86d15b019e94164cdbaeb1228075403
unknown command 'pscontainer'

@jodh-intel cc-proxy was updated, can you please try again?

Still no joy I'm afraid:
$ sudo docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
f91b2811adfc        busybox             "sh"                6 seconds ago       Up 3 seconds                            laughing_knuth
$ sudo cc-runtime list
ID                                                                 PID         STATUS      BUNDLE                                                                                CREATED                          OWNER
f91b2811adfc8d1ce315c26bfbcf930795c06a77a82a5a04cd05c082b1fa1b26   10685       running     /run/docker/libcontainerd/f91b2811adfc8d1ce315c26bfbcf930795c06a77a82a5a04cd05c082b1fa1b26   2017-11-14T08:47:09.121827607Z   #0
$ sudo cc-runtime ps f91b2811adfc8d1ce315c26bfbcf930795c06a77a82a5a04cd05c082b1fa1b26
ERROR received from VM agent

That (not terribly helpful error) seems to be coming from:

https://github.com/containers/virtcontainers/blob/master/pkg/hyperstart/hyperstart.go#L444

There isn't anything else useful in journald fwics.

I've just re-tested with latest runtime + latest agent but same problem :(
(It would be great to get this landed soon as I know how tricky it's been to add the required functionality to various parts of the system).

Hi @jodh-intel , still waiting for https://github.com/clearcontainers/agent/pull/90

@jodh-intel it works for me
$ docker run -dti debian bash
264d40dd43f376b37dbd1af3783d9e6b2e2d0c0ec4d66111a6f6777c140e1ff0
$ sudo cc-runtime list
ID                                                                 PID         STATUS      BUNDLE                                                                                CREATED                          OWNER
264d40dd43f376b37dbd1af3783d9e6b2e2d0c0ec4d66111a6f6777c140e1ff0   6166        running     /run/docker/libcontainerd/264d40dd43f376b37dbd1af3783d9e6b2e2d0c0ec4d66111a6f6777c140e1ff0   2017-11-27T14:12:53.493966351Z   #0
$ sudo cc-runtime ps 264d40dd43f376b37dbd1af3783d9e6b2e2d0c0ec4d66111a6f6777c140e1ff0
UID        PID  PPID  C STIME TTY          TIME CMD
root       163   146  0 14:12 ?        00:00:00 bash

probably we are doing something different

I'm still seeing the problem with image 18860 and also using osbuilder + latest agent. I've tested with busybox and debian docker images. Could you try on another system, or else maybe someone else can try testing this?

Hi @jodh-intel
I'm using fedora + CL container image [1] + latest agent [2]
$ /usr/libexec/clear-containers/cc-proxy --version
Version: 3.0.8-2-g8bae402
$ /mnt/usr/bin/cc-agent --version
{"level":"info","msg":"","name":"cc-agent","pid":28094,"time":"2017-11-28T09:56:11.265027193-06:00","version":"0.1.1+-b1d92e2aa14d915680e8fe770745a511857ac7ff"}
{"level":"info","msg":"agent_started<PHONE_NUMBER>21383","name":"cc-agent","pid":28094,"time":"2017-11-28T09:56:11.265258871-06:00"}
{"error":"open /sys/class/virtio-ports: no such file or directory","level":"error","msg":"Could not open channels","name":"cc-agent","pid":28094,"time":"2017-11-28T09:56:11.265343982-06:00"}
$ cc-runtime --version
cc-runtime  : 3.0.8
   commit   : b9c924320b05a6edeaefd8717aefee97df6aece3
   OCI specs: 1.0.0-dev
$ docker run -dti busybox sh
6f4155a11426e1daa6afb70f7c5ee367f235cf73ce666fc8d8eab19a19cc7497
$ sudo cc-runtime ps 6f4155a11426e1daa6afb70f7c5ee367f235cf73ce666fc8d8eab19a19cc7497
UID        PID  PPID  C STIME TTY          TIME CMD
root       164   148  0 15:56 ?        00:00:00 sh

btw osbuilder does not include ps (procps-ng-bin)
[1] - https://download.clearlinux.org/releases/18860/clear/clear-18860-containers.img.xz
[2]  - https://github.com/clearcontainers/agent

I added the procps package (like https://github.com/clearcontainers/osbuilder/pull/41), but I'm still seeing ERROR received from VM agent.

After a rebase (required due to proxy changes), I am now getting the correct ps output! ;)
Could you rebase and we can get this merged?

@jodh-intel great! thanks

Hi @devimc - could you re-push? The CI seems to have got confused.

err - it just updated as I was typing! ;)

@jodh-intel changes applied, thanks

lgtm

Coveralls is stuck (surprise!) - https://coveralls.io/jobs/31802016.
Merging...


Add table of contents option for output?

For very long documents, automatic generation of a TOC based on headers would be super useful. Pandoc already has options for this:

--toc, --table-of-contents
Include an automatically generated table of contents (or, in the case of latex, context, docx, odt, opendocument, rst, or ms, an instruction to create one) in the output document. This option has no effect on man, docbook4, docbook5, or jats output.
--toc-depth=NUMBER
Specify the number of section levels to include in the table of contents. The default is 3 (which means that level 1, 2, and 3 headers will be listed in the contents).

So it seems like it should be relatively straightforward to add for pandoc builds. Not sure about the others (I personally need it most for markdown to html and markdown to ipynb. I could take a stab at this, but I'm not super familar with this codebase so any direction would be helpful

I added a pandoc_options keyword to pass options directly to pandoc so now you can get table of contents if you like using:
weave("somefile.jmd", doctype="pandoc2html", pandoc_options=["--toc"])

It would not be very difficult to get a table of contents using Julia Markdown, but it could be better to implement pandoc-like features in some other package than Weave.


separate cobra commands and otelcli

Refactors otel-cli's server to remove the CliEvent abstraction. It seemed like a good idea at the time but it turns out, it was a bad decision. The protobuf spans and span events don't look as nice but are fine to work with and ultimately using them directly is more precise.
One feature added: otel-cli server tui and otel-cli server json now support http. I was working on that code anyways and it was easy to add along the way.
The test suite now has a separate map for checking server metadata. Previously it was serialized to a single line, sorted lexically. It worked OK but this is cleaner, easier to read, and easier to maintain.

Somehow I put the wrong description on this PR. Besides, I didn't like how the diffs came out so I reworked the branch in #223.


Add mypy

Codecov Report

Merging #31 (fd9a312) into main (c93aa1c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #31   +/-   ##
=======================================
  Coverage   92.74%   92.74%
=======================================
  Files          26       26
  Lines        1777     1777
=======================================
  Hits         1648     1648
  Misses        129      129

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


[REQUEST] Provide More Hooks in ProjectPlugin

Is your feature request related to a problem? Please describe.
More dependency on the nodestream.yaml has been added since the introduction of configuration and targets. For this reason, its probably beneficial for there to be more hooks in ProjectPlugin to allow for more management of the project loading process.
Describe the solution you'd like
At the minimum, I think we need to add before_project_load and after_project_load hooks which are needed to have nodestream-plugin-dotenv work when using !env in your nodestream.yaml file. Additionally, it may be worth exploring other possible use cases.
Describe alternatives you've considered
There is no real other alternative.

Targeted for #184

Slated for 0.10.0


hacktoberfest TODO: Asuka assets

Need assets for Asuka
These will be the assets the app will render to the terminal after timer is up. keep in mind do to the nature of terminals we a limited to 80x80 (characters spaces), large images will be shrunk. The image will also appear pixelated due to the same factors previously indicated.
Specifications for asset

jpg format
at least 2 images, and less than 6
must be SFW
file size must be less than 10kb(each)
dimensions should be 80x80 or 160x160 depending on if you can meet the required < 10kb
If you are having trouble getting it below 10kb without ruining the image try sqoosh
create a branch, with a name appropriate to the feature you are working on
place them in the directory /images/asuka (you have to make the asuka directory)
create a pull request

can you give a sample of an asuka asset

You can find an example of the current assets in the images/ directory of the project. If you aren't sure of who Asuka is, you'll  have to google "Asuka Evangelion" as this is a Evangelion themed project.

Thank you for you appreciation, let me know if I can contribute on any other issues too.


Uber title not encoded when in display

When sending a title to Uber it is displayed as not encoded.  Is there something we can do to fix that? Google, Apple and Waze work just fine.
const result = await getApps({
        latitude: data?.data?.dirs?.lat,
        longitude: data?.data?.dirs?.lng,
        title: data?.t,
        googleForceLatLon: true,
        alwaysIncludeGoogle: true,
      });

We might have to encode this differently, for example by using + instead of %20, or maybe it likes just no encoding whatsoever. I'm not able to give this a try at the moment, but happy to accept a PR to fix this.

Should be easy fix


Update recipe for py312_patch

Preparation for py312 release.

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: clone/recipe/meta.yaml:30: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: BSD-3-Clause
INFO: clone/recipe/meta.yaml:33: invalid_url: https://pythonhosted.org/webencodings : URL domain redirect pythonhosted.org ->
WARNING: clone/recipe/meta.yaml:35: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:38: invalid_url: https://pythonhosted.org/webencodings : URL domain redirect pythonhosted.org ->
WARNING: clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
Warnings were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:38: invalid_url: https://pythonhosted.org/webencodings : URL domain redirect pythonhosted.org ->
WARNING: clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
Warnings were found


[warning] failed package validation and/or copy for commit 6b6de00d619a34dfdde0ab6989a307727faa2c16

Hi @conda-forge/nordugrid-arc! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid feedstock token

Hi @conda-forge/nordugrid-arc! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid feedstock token

Hi @conda-forge/nordugrid-arc! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid feedstock token

Retrying the build seems to have worked 😕
In the hope this isn't a widespread issue I'll close and worry more if it appears elsewhere.


feat: add charmbracelet/log as optional text handler for the logger

Motivation
We currently only offer an ugly json handler for the logger.
Since this is really annoying when debugging, I've took some time and improved our logger so we can opt into a pretty text logger.
Changes
I've introduced a prettier text handler for the logger (charmbracelet/log). This enables us to choose the text logging format over the default JSON format by setting the environment variable LOG_FORMAT=text.
This enhances readability and usability for log analysis when we're debugging.

feat: add text logger
test: add unit tests for handler creation
chore: test naming

For additional information look at the commits.
Tests done
I've provided some unit tests for the handler creation.

[x] Unit tests succeeded.
[x] E2E tests succeeded.

The pretty logs look like this (colors aren't displayed here, for more info on that please refer to charmbracelet/log):
$ go run main.go run --config .tmp/sparrow.yaml
Using config file: .tmp/sparrow.yaml
01:44:01 INFO <cmd/run.go:81> Running sparrow
01:44:01 INFO <targets/gitlab.go:77> Starting global gitlabTargetManager reconciler
01:44:01 INFO <api/api.go:76> Serving Api addr=:8080
01:44:11 ERRO <gitlab/gitlab.go:344> Failed to post file status="400 Bad Request"
01:44:11 ERRO <targets/gitlab.go:180> Failed to register global gitlabTargetManager error="request failed, status is 400 Bad Request"
01:44:11 WARN <targets/gitlab.go:104> Failed to register self as global target error="request failed, status is 400 Bad Request"

TODO

[x] I've assigned this PR to myself
[x] I've labeled this PR correctly

Slog already has a text logger, doesn't it? I don't see the necessity to import a dependency we do not actually need.

@puffitos But it's prettier 🥺 Nevertheless I can change it to the slog.TextHandler if you think we shouldn't introduce another dependency.

I'll let the others decide as well @y-eight @y-eight , this should be a team decision 😊

I like the charmbracelet logger, but since this is mostly a debugging thing, I don't think we need to introduce a dependency for this. I'm fine as long as there is some alternative to the JSON logger, as I find myself building one every time I work on a feature anyways, only to throw it away before posting the pr

The default slog loggers output is now like this:
❯ go run main.go run --config .tmp/sparrow.yaml
Using config file: .tmp/sparrow.yaml
time=01:17:02 level=INFO source=/home/tom/dev/sparrow/cmd/run.go:81 msg="Running sparrow"
time=01:17:02 level=INFO source=/home/tom/dev/sparrow/pkg/sparrow/targets/gitlab.go:77 msg="Starting global gitlabTargetManager reconciler"
time=01:17:02 level=INFO source=/home/tom/dev/sparrow/pkg/api/api.go:76 msg="Serving Api" addr=:8080
time=01:17:12 level=ERROR source=/home/tom/dev/sparrow/pkg/sparrow/gitlab/gitlab.go:344 msg="Failed to post file" status="400 Bad Request"
time=01:17:12 level=ERROR source=/home/tom/dev/sparrow/pkg/sparrow/targets/gitlab.go:180 msg="Failed to register global gitlabTargetManager" error="request failed, status is 400 Bad Request"
time=01:17:12 level=WARN source=/home/tom/dev/sparrow/pkg/sparrow/targets/gitlab.go:104 msg="Failed to register self as global target" error="request failed, status is 400 Bad Request"
time=01:17:23 level=ERROR source=/home/tom/dev/sparrow/pkg/sparrow/gitlab/gitlab.go:344 msg="Failed to post file" status="400 Bad Request"
time=01:17:23 level=ERROR source=/home/tom/dev/sparrow/pkg/sparrow/targets/gitlab.go:180 msg="Failed to register global gitlabTargetManager" error="request failed, status is 400 Bad Request"
time=01:17:23 level=WARN source=/home/tom/dev/sparrow/pkg/sparrow/targets/gitlab.go:104 msg="Failed to register self as global target" error="request failed, status is 400 Bad Request"

Please add a few lines in the Readme as well, to document this new feature. Eventually, this should also be part of the chart values.


⚠ API Next - load whole book has degraded performance

In e1cef02, API Next - load whole book (https://h-edu.cz/content.api/book/book-a/chaptersContent) experienced degraded performance:

HTTP code: 200
Response time: 22414 ms

Resolved: API Next - load whole book performance has improved in f12425b after 10 minutes.


reorg cleanup query timeout

It is possible that the query used to delete data during a reorg is too slow for the default 10s database timeout. During a reorg Shovel will delete data from shovel.task_updates with this query and all the integration's tables with this query.
It is possible that one of these two queries is taking longer than 10s. Since Shovel automatically creates an index on shovel.task_updates, I'm wondering if we are missing an index on the integration tables.
The ideal fix is to make these queries fast. Perhaps with a better index.
If you are experiencing this problem please use the postgres logs to show the exact query that is timing out. Also please share the table DDL so we can look for missing indexes.

Hi Ryan, first time caller, but we've been successfully using shovel for a bit now. I'm bumping up against this bug consistently with my poly integration and I'd love to help debug.
Logs =>
2024-11-01 23:55:26 UTC [4086392]: [67256a57.3e5a78-6] 186145559 redacted@redacted,app=redacted [57014] CONTEXT: while deleting tuple (37,36) in relation "task_updates" 2024-11-01 23:55:26 UTC [4086392]: [67256a57.3e5a78-7] 186145559 redacted@redacted,app=redacted [57014] STATEMENT: delete from shovel.task_updates where src_name = $1 and ig_name = $2 and num >= $3 2024-11-01 23:55:26 UTC [4086392]: [67256a57.3e5a78-5] 186145559 redacted@redacted,app=redacted [57014] ERROR: canceling statement due to statement timeout 2024-11-01 23:55:30 UTC [4086394]: [67256a57.3e5a7a-10] 186145284 redacted@redacted,app=shovel-task-polygon-default-nativeTokenTransfers-0648 [25P03] FATAL: terminating connection due to idle-in-transaction timeout
Not sure exactly what you're looking for on DDL but here's the create tx =>
  shovel.task_updates (
    num numeric NULL,
    hash bytea NULL,
    insert_at timestamp with time zone NULL DEFAULT now(),
    src_hash bytea NULL,
    src_num numeric NULL,
    nblocks numeric NULL,
    nrows numeric NULL,
    latency interval NULL,
    src_name text NULL,
    stop numeric NULL,
    chain_id integer NULL,
    ig_name text NULL
  );`

things I've done that haven't affected anything:

* the task_updates table only has about 1400 rows in it. so is pretty tiny. I've cleaned out old irrelevant logs (hasn't affected anything)
* extended the statement_timeout on the connection string (which I suspected is being overridden by the pool connection)
* extended the statement_timeout on the user as default (same result)
* manually ran the delete as the user (it was fast and always deleted 0 rows) (explain analyze was always like 0.5ms execution time or something dramatically lower than even the 5s timeout you place on the connection string)

happy to provide whatever else I can. shovel is a great piece of kit.

a few more points. this is always during reorg. and when this happens (which always seems to be poly), the entire thing grinds to a halt and none of the integrations continue. it's the last bit that makes this bug be a killer because I would expect that even if the poly integration falls over the rest would progress.
for now i have poly turned off and everything is running ok, but happy to turn it back on to help debug if i can.

@lexomis can you share the shovel logs during the time of the reorg / halt?

@lexomis can you give me a minimal config that has a chance of reproducing the issue? I bet if I can hit it locally then I can fix it quickly.

well this is quite annoying. i woke up to make a few changes and then get the logs and try to build a recreateable pattern for you and it unblocked. now it's running fine again polygon.
not sure if this helps but when i was trying to recreate I am pretty sure i'd need to dump a portion of my task_updates table to you. When I went to clean it out with what appeared to be old blocks that were hours before the noted reorg blocks and update my startAt to the first block in my task_updates table, that unblocked the system.
this is about the third time I've seen this with poly so I suspect it won't be terribly long until I can reproduce again. Will be in touch at that time.

Interesting. If you can give me your config.json to run on my local machine then I will have a good chance of reproducing and then fixing. I don't need your data. Just the config.json. Please remove anything that isn't related to the integration that is causing the problems.
Also, per your last comment, I still suspect that the delete on the task_updates table is timing out because of too much data. One way you could test this hypothesis is to:

Periodically delete from task_updates where insert_at < now() - '1 day'::interval
or
If it gets stuck, psql into the database and run the query in #1

Yes. I was following your hypothesis and the first time that I performed a delete there was not too much data there and the execution was less than 10ms so there couldn't have been a real timeout happening unless the timeout was set at 0.
I was convinced it was a permissions thing and weird erroring by the go library but that didn't seem to be the case either.
I'll keep watch. Config below:
{   "pg_url": "$DATABASE_URL",   "eth_sources": [     {       "name": "polygon-default",       "chain_id": 137,       "concurrency": 1,       "poll_duration": "2s",       "urls": [         "$PRIMARY_PROVIDER_POLYGON_HTTP"       ],       "ws_url": "$PRIMARY_PROVIDER_POLYGON_WS"     }   ],   "integrations": [     {       "enabled": true,       "name": "nativeTokenTransfers",       "sources": [         {           "name": "polygon-default",           "start": "63771860"         }       ],       "table": {         "name": "native_token_transfers",         "columns": [           {             "name": "block_unix_timestamp",             "type": "int"           },           {             "name": "chain_id",             "type": "int"           },           {             "name": "block_hash",             "type": "bytea"           },           {             "name": "transaction_hash",             "type": "bytea"           },           {             "name": "from",             "type": "bytea"           },           {             "name": "to",             "type": "bytea"           },           {             "name": "tokens",             "type": "numeric"           },           {             "name": "call_type",             "type": "text"           }         ]       },       "block": [         {           "name": "block_time",           "column": "block_unix_timestamp"         },         {           "name": "chain_id",           "column": "chain_id"         },         {           "name": "block_hash",           "column": "block_hash"         },         {           "name": "tx_hash",           "column": "transaction_hash"         },         {           "name": "tx_signer",           "column": "from"         },         {           "name": "tx_to",           "column": "to"         },         {           "name": "tx_value",           "column": "tokens",           "filter_op": "gt",           "filter_arg": [             "0"           ]         }       ]     }   ] }

  "pg_url": "$DATABASE_URL",
  "eth_sources": [
    {
      "name": "polygon-default",
      "chain_id": 137,
      "concurrency": 1,
      "poll_duration": "2s",
      "urls": [
        "$PRIMARY_PROVIDER_POLYGON_HTTP"
      ],
      "ws_url": "$PRIMARY_PROVIDER_POLYGON_WS"
    }
  ],
  "integrations": [
    {
      "enabled": true,
      "name": "nativeTokenTransfers",
      "sources": [
        {
          "name": "polygon-default",
          "start": "63771860"
        }
      ],
      "table": {
        "name": "native_token_transfers",
        "columns": [
          {
            "name": "block_unix_timestamp",
            "type": "int"
          },
          {
            "name": "chain_id",
            "type": "int"
          },
          {
            "name": "block_hash",
            "type": "bytea"
          },
          {
            "name": "transaction_hash",
            "type": "bytea"
          },
          {
            "name": "from",
            "type": "bytea"
          },
          {
            "name": "to",
            "type": "bytea"
          },
          {
            "name": "tokens",
            "type": "numeric"
          },
          {
            "name": "call_type",
            "type": "text"
          }
        ]
      },
      "block": [
        {
          "name": "block_time",
          "column": "block_unix_timestamp"
        },
        {
          "name": "chain_id",
          "column": "chain_id"
        },
        {
          "name": "block_hash",
          "column": "block_hash"
        },
        {
          "name": "tx_hash",
          "column": "transaction_hash"
        },
        {
          "name": "tx_signer",
          "column": "from"
        },
        {
          "name": "tx_to",
          "column": "to"
        },
        {
          "name": "tx_value",
          "column": "tokens",
          "filter_op": "gt",
          "filter_arg": [
            "0"
          ]
        }
      ]
    }
  ]
}```

Thank you for the config. I'm running it locally. Let's see if I can hit the issue too.

Cool. I'm running too and watching as well.

quite annoying slash working like a charm! lol.

Ok. Let's keep an eye on it. This actually makes me think the bug is related to database size.

@lexomis I was finally able to reproduce the issue. I believe I have a fix that I just landed on main. The description of the bug and its fix are in the commit message. Please try 51f0111d9b54cd64b13db913ba30fbbeacc806f6

Wonderful. I am glad this bug has been put to rest.


Jump Gate shows no targets

The Jumpgate shows no target Jumpgates. It doesnt matter if the jumpgates are in the same galaxy or not, no possible target gates are shown.
All files with the latest changes, no custom changes. Error log shows nothing.

I fixed it and added a reduction for the recharge time.

Thanks, I got your mail.

I will close it, if the patch is applyed.

I fixed the appaerence of the jumpgate but when i try to jump i get this error
Message: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens
Query-Code:UPDATE uni1_planets SET big_ship_cargo = big_ship_cargo - 2, light_hunter = light_hunter - 100, last_jump_time =<PHONE_NUMBER> WHERE id = 25;

It's about the PDO parameter bindings. Can you please provide the code?

See here: https://github.com/jkroepke/2Moons/blob/master/includes/pages/game/ShowInformationPage.class.php#L118
Problem is that the subquery is a PDO parameter. This is wrong here. It must be like here: https://github.com/jkroepke/2Moons/blob/560c52f30250c72d52e1e327598712772e5be8ce/includes/classes/class.PlanetRessUpdate.php#L709


theme not loading

It seems that I encounter a problem.
Since I am a newbie and this is my first hugo installation, I really don't know what to do.
The page is loading without css.
ERROR: 2018/08/08 23:05:42 template.go:350: template: theme/_default/list.html:4: function "default" not defined
ERROR: 2018/08/08 23:05:42 template.go:350: template: theme/gallery/list.html:3: function "default" not defined
ERROR: 2018/08/08 23:05:42 template.go:350: template: theme/partials/head.html:12: function "default" not defined
ERROR: 2018/08/08 23:05:42 template.go:350: template: theme/posts/single.html:1: function "default" not defined
ERROR: 2018/08/08 23:05:42 template.go:119: html/template: "theme/partials/head.html" is an incomplete template in theme/partials/head.html
0 draft content
0 future content
0 pages created
1 non-page files copied
0 paginator pages created
0 tags created
0 categories created
in 6 ms
Any thoughts?

What hugo version are you using (command: hugo env)?
Have you installed it using a package manager like apt or dnf? In that case it may be very outdated and doesnt now the function default yet.
You can get the newest version of hugo here.

I installed via apt and it was so very outdated (0.16).
You are right.
Installed now with snap and all are good.
Thank you so much!


Handlebars parent of parent not possible

Hi,
I got an parsing issue with the Handlebars I am not able to solve.
I have the following data structure:
{
    "testtext": "test",
    "entries": [
        {
             "output": "test2",
             "subentries": [
                 {
                     "output": "test3"
                 }
             ]
        }
    ]
}

and the following handlesbars template
{{#each entries}}
    {{output}} - {{../testtext}}
    {{#each subentries}}
        {{output}} - {{../../testtext}}
    {{/each}}
{{/each}}

The first testtext is displayed as I expect, the second one (in the subentry-each) is not displayed, it seems the veil-parser can't handle this kind of context traversing, while "normal" handelbars would do (i checked at http://tryhandlebarsjs.com/).
Do you have an idea how to solve this problem?
Thanks in advance

see https://github.com/namics/TerrificNet/commit/77eeabb20acd9a2d861c848a3b770b1c52b9ddd4


LedgerSigner.connect always throws an error

Describe the bug
calling connect on a LedgerSigner instance throws an error
Likely related to the underlying HID transport holding the device, and the new signer making a second acquisition attempt that fails
Reproduction steps
import { LedgerSigner } from '@ethersproject/hardware-wallets'
import * as ethers from 'ethers'

const provider = ethers.providers.getDefaultProvider()
const signer = new LedgerSigner()

signer.connect(provider)

/// Error: cannot open device with path

Environment
ts-node w/<EMAIL_ADDRESS>on an M1 macbook

Can you try out this latest version and see if you still have issues with it? I believe the underlying issue may have been fixed by Ledger, as this package creates a new Eth object for each necessary call, and it has worked for me.


[polling] level3 messages are too large

Error:
2017-09-25 00:21:24,847 - apscheduler.executors.default - ERROR - Job "produce_level3_book (trigger: interval[0:00:30], next run at: 2017-09-25 00:21:52 UTC)" raised an exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/apscheduler/executors/base.py", line 125, in run_job
    retval = job.func(*job.args, **job.kwargs)
  File "polling.py", line 39, in produce_level3_book
    produce_book(3)
  File "polling.py", line 31, in produce_book
    value_schema=value_schema,
  File "/usr/local/lib/python3.6/site-packages/confluent_kafka/avro/__init__.py", line 74, in produce
    super(AvroProducer, self).produce(topic, value, key, **kwargs)
cimpl.KafkaException: KafkaError{code=MSG_SIZE_TOO_LARGE,val=10,str="Unable to produce message: Broker: Message size too large"}

Some level 3 order book messages can be more than the default max message size.
This can be solved by increasing and. Keep in mind that these settings are per-topic. So, existing topics will possibly need these settings.


[QUESTION] 'ZipArchive::close(): Failure to create temporary file: No such file or directory'

I'm using Laravel 5.2 and pulling package "maatwebsite/excel": "~2.1.0",  using composer. on localhost I have windows and the plugin works fine. but when I uploaded into production server where I have linux debian and php 5.6 installed I get following error in laravel.log and the plugin stops working.
local.ERROR: exception 'ErrorException' with message 'ZipArchive::close(): Failure to create temporary file: No such file or directory' in /home/admin/...
Stack trace:

I did composer update after uploading to production , also I make storage/exports and storage/cache forlders writable.
what I'm doing wrong?

Closing this as you solved it here: https://laracasts.com/discuss/channels/servers/ziparchiveclose-failure-to-create-temporary-file-no-such-file-or-directory


New first responder badge credential for medical technician

TODO: Add SVG images for renderMethod

Resolves - adds new first responder badge credential for medical technician

What kind of change does this PR introduce?

New VC example for first responder badge.

What is the current behavior?

No current FR EMT badge credential.

What is the new behavior?

FR EMT badge credential.

NOTE: This uses the examples context instead of the appropriate context, because VC v2 and renderMethod are not yet stable.

Does this PR introduce a breaking change?

[ ] Yes
[X] No

How has this been tested?

Locally rendered, issued, and verified.

Screenshots: n/a

@BigBlueHat
Medical Technician SVG is looking great here! A few notes:

I'm seeing we are using 3 different FR blue star logos: Without words, with words in a circle (the iconography, and with horizontal words on issuer's image
SVG needs rounded boarders to mimic a card
SVG needs a background color as it currently blends into the UI background

You also noted:

font issues
Utopia background

For reference:

SVG with values

I'm seeing we are using 3 different FR blue star logos: Without words, with words in a circle (the iconography, and with horizontal words on issuer's image

Not quite sure how to resolve these... One is the icon image.png used on the VC Playground, so I could drop the words there (as I expect they'll be illegible). The other one standalone image is for the issuer...so not keen to change their colors...and not keen to match that blue either. Any preference here, @jameseaster?

SVG needs rounded boarders to mimic a card

Not sure we need to do this one. The ecosystem will certainly do both (at various points). I can if you want me to, but I think it'll depend on the designer of the SVG in the future and since these sort of simulate "random" credentials...maybe it's fine? 😁 Let me know if you really want that changed.

All other issues should be addressed.

@BigBlueHat

One is the icon image.png used on the VC Playground, so I could drop the words there (as I expect they'll be illegible).
Let's match these, maybe just override the png file with a png version of the logo you're using in the svg

Rendered locally and looks awesome! Thanks @BigBlueHat


Can't Edit Existing Claim if Deposit Value is Changed

If you click in to the deposit area and change the value, you can no longer edit unless you have that entire value in your wallet, which isn't necessary because you've already made your claim.
Solution to this can also be the solution to @tzarebczan's filed issue: https://github.com/lbryio/lbry-app/issues/634
Before Value Changed Then Changed Back

After Value Changed Then Changed Back

Ah, good point... Completly forgot about this when I made the ux enhancements.
@seanyesmunt do you think we can get the current claim deposit and add that to the balance for this simple check? I'll look into this.

Just noticed - Styling issue with "I agree to the" text in above screengrab,

I'm not seeing the same in the prod version. But I think I saw something similar on another screen via Dev mode/master. Let me see if it's something to do with Dev mode, or a recent change.

Fixed in https://github.com/lbryio/lbry-app/pull/1725


[RFC] About fonts.googleapis.com/css2 in template

How do you envision this feature/change to look/work like?
No external network resource access
What is the purpose of this change/feature? Why?
Framework should be completely static , should not access network resource. It may cause slow in areas with network problems .
(OPTIONAL) Example implementations
I found this https://github.com/PlasmoHQ/plasmo/blob/f50f553b203d66e26d70eee8013d6f21c9693cd6/cli/plasmo/templates/static/react18/index.html#L7
(OPTIONAL) Contact Details
No response
Verify canary release

[X] I verified that the issue exists in plasmo canary release

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

Please upvote this if anyone else also having the same concern. If the demand for the removal of the font is high, we will remove it in the next version :P (I kept it there bc it's convenient for my own project :d)

Will implement this in #183


[Feature Request] "Save as..." Feature

When playing around with a build I sometimes change so much in an original build that I want to save the changes as a new build. It would be cool to have a "save as ..." button right next to the "save" button to create a completly new build.
I am currently working around this with the import/export feature, so I guess this is mainly a QOL improvement.

This will be in the next update.


I cant open OR delete DS4Windows off of my computer

It says File in use
This action cant be completed because file is in use.

You need to open task manager and close the program.

يقول  ! C:\Users\PC\Downloads\DS4Windows.zip: لا يمكن فتح C:\Users\PC\Downloads\DS4Windows.zip
The system cannot find the file specified.
! لا يمكن تنفيذ "C:\Users\PC\AppData\Local\Temp\Rar$EXa2364.29943\DS4Updater.exe"


go/links lists all of the go links

no paging or anything, just the most basic possible listing

solves #6 although if you already have a golink for /links you may be mad

Arg, I think I totally screwed you up when I went mucking around last night. Let me rebase some things.

The diff looks ok to me, possible I screwed up resolving the conflict though

I rebased everything. I went and made some meaningless changes last night, but it was easy to merge them.

Closing as this is actually merged now.


embed template tag seems to be broken

Found a bug? Please fill out the sections below. 👍
Issue Summary
{% embed %} seems to be broken
Steps to Reproduce

Make a StructBlock with an EmbedBlock in it and an optional field for max_width
point it to the following template...

{% load wagtailembeds_tags %}

{% if self.max_width %}
{% embed self.url max_width=self.max_width %}
{% else %}
{% embed self.url %}
{% endif %}

fill out that block in a page body and preview the page

I get the following error:
'EmbedValue' object has no attribute 'encode'

The last error in the chain refers to:
def get_embed_hash(url, max_width=None, max_height=None):
    h = md5()
    h.update(url.encode("utf-8"))

Oddly, I put a pdb trace in that function and ran through it manually, and it seems to work...
(Pdb) url.encode('utf-8')
b'https://youtu.be/MghSXEvg734'

(Pdb) hgt = md5()
(Pdb) hgt.update(url.encode("utf-8"))
(Pdb) hgt
<md5 HASH object @ 0x7fc235911da0>

(had to rename h variable because h is reserved for 'help' in pdb)
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
I tried taking the max_width field out and just running {% embed self.url %} on twitter rather than youtube, but got the same result at the same place in the same function.
Technical details

Python version: 3.6.8
Django version: 3.2.9
Wagtail version: 2.15.1
Browser version: Safari 15.2

Hi @awhileback,
You don't use the {% embed %} tag with EmbedBlock - it's one or the other. The {% embed %} tag converts the given URL into an embeddable HTML fragment, but the value returned by EmbedBlock is already a representation of the embeddable HTML - so you end up passing an embeddable HTML value to the {% embed %} tag when it just wants a URL.
If you want to call the {% embed %} tag yourself, to have control over the size, then you should use a plain URLBlock instead of EmbedBlock.


License statement

Currently there is no license statement. Could you please add a LICENSE file that contains the license text or add details to pyproject.toml?
For Nixpkgs shell-genie is marked as unfree for now but a clarification about the license would be much appreciated.
Thanks.

Hey @fabaff, I just added the license (MIT). Let me know if this fixes the issue.

Thank you.


Bold Number

https://s3.postimg.org/nvd336ifn/Screenshot_18.png
Could you fix this bug, please?

I'll send the file via email.

ou wow Thanks Jan


Filter User Agent by the word 'bot' and whitelist

Hello!
I come here to ask if someone can help me to configure some rules that I have tried to do in a thousand ways and I am not able to do it.
I need to block all those headers whose "User agent" contains the word 'bot' with a 403, but if that "User agent" is in a whitelist, let it pass with a 200. After a thousand attempts, the best that has worked for me is this rule:
SecRule REQUEST_HEADERS:User-Agent ".bot." "id:1,phase:1,nolog,pass,setvar:tx.block_bot=1"
SecRule REQUEST_HEADERS:User-Agent "@rx ^(Google|Uptime|Bing|Semrush)" "id:2,phase:1,nolog,pass,setvar:tx.allow_bot=1"
SecRule &TX:allow_bot "!@eq 1" "id:100,phase:1,deny,status:403,msg:'Bot blocked'"
However, there are times when it gives 403 errors when it shouldn't and I don't know why.... That is to say, I am going to give some examples:

ahrefsbot -> It should block it with 403.
Googlebot -> I should let it pass with 200 (whitelist)
SemrushBot -> You should let it through with 200 (whitelist)
Anything -> I should let it through with a 200 because it doesn't even contain the word bot, ergo the whitelist shouldn't even be consulted.
Hellobot -> You should block it with 403
Github -> You should let it through with a 200 because it doesn't even contain the word bot, ergo the whitelist shouldn't even be consulted.

All this is to massively block all requests that come with the user agent containing 'bot' except those that interest me like Google or crawlers that interest me.
Could someone help me?

Hello @AngelSamuel ,
Your first rule (id:1) is probably not working the way you expect. If no operator is specified, then @rx is assumed. Your pattern '.bot.' requires there to be at least one character before the 'b' and at least one character after the 't'. -- so that would mean 'ahrefsbot' could never match.
There are a few ways you could adjust that rule including a) just change the pattern to bot, b) leave '.' s but include Kleene stars: .*bot.*, or c) use a string equality operator instead like @streq bot.
A second problem appears to be that, after possibly setting tx.block_bot it is never tested by any other rule. There are multiple ways to address this, but perhaps the simplest is to use only 1 variable (tx.block_bot), have your second rule set the value to 0 if good-bot strings are detected, and then have your third rule test for the value of the variable rather than whether the value exists (e.g. SecRule TX:block_bot "@streq 1" "id:100 ...
As a general piece of advice: examining the output of the ModSecurity debug log (at level 9) is often a good way to better understand what is happening with your rule logic.

Hi @martinhsv !!! Sorry for the delay in responding. Based on your comments, we have created this rule and it works frankly well. We are still testing but it seems very effective!
SecRule REQUEST_HEADERS:User-Agent "(?i)bot" "id:1,phase:1,nolog,pass,setvar:tx.block_bot=1"
SecRule REQUEST_HEADERS:User-Agent "(?i)^(?=.(?:Google|Uptime|Bing|Semrush)).$" "id:2,phase:1,nolog,pass,setvar:tx.block_bot=0"
SecRule TX:block_bot "@streq 1" "id:100,phase:1,deny,status:403,msg:'Bot blocked'"
One last question I wanted to ask you and that is that I see that on servers running LiteSpeed it seems that this rule does not quite work, reading in forums and in the official documentation apparently ModSecurity should be very compatible with both Apache and LiteSpeed. Do you have any idea about it?
Thank you very much for your help, very kind!


Can't find plink!

I'm not sure why this is happening now. It was working fine and there haven't been any changes on the server. This happened after the latest upgrade (1.0.3)
Traceback (most recent call last):
File "/home/akil_lab/huzefak/.local/bin/snprocess", line 33, in
sys.exit(load_entry_point('snprocess==1.0.3', 'console_scripts', 'snprocess')())
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/click/core.py", line 1130, in call
return self.main(*args, **kwargs)
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/snprocess/main.py", line 159, in main
markup = QC_1(settings)
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/snprocess/qc/qc_1.py", line 36, in QC_1
output, data = plink(
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/snprocess/qc/model.py", line 31, in plink
output = run_command(cmd)
File "/home/akil_lab/huzefak/.local/lib/python3.10/site-packages/snprocess/qc/model.py", line 18, in run_command
process = subprocess.Popen(cmd.split(), stdout=subprocess.PIPE)
File "/usr/lib/python3.10/subprocess.py", line 966, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 1842, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: './plink'

Ahhh my bad, I had forgotten to revert some code I use to debug on my machine. View changes in qc/model.py if you’re curious.


Serving certificate isn't particularly clear

https://github.com/jetstack/cert-manager/blob/660184552c6e7643fd984c3bb1d7b9d9a6fab64a/pkg/webhook/server/tls/dynamic_source.go#L169
I'm not at all sure what this is.
If this is cert-manager's certificate for itself, there are better ways to say this.
If this is someone else's certificate, the identity should be specified.

Severity
Date
System
Message

Info
2021-12-09 12:00:53.001 EST
cert-manager
cert-manager/webhook "msg"="Serving certificate requires renewal, regenerating"

Info
2021-12-09 12:00:53.001 EST
cert-manager
cert-manager/webhook "msg"="Serving certificate requires renewal, regenerating"

Info
2021-12-09 12:00:53.689 EST
cert-manager
cert-manager/webhook "msg"="Updated serving TLS certificate"

Info
2021-12-09 12:00:53.689 EST
cert-manager
cert-manager/webhook "msg"="Updated serving TLS certificate"

This is webhook's serving certificate (for when kubeapiserver talks to the webhook).
Improvements to the logs are welcome 👍🏼
/remove-lifecycle rotten
/help-wanted
/good-first-issue

@irbekrm what exactly is the ask here? When a renewal is triggered, should we be printing out some specifics about the soon-to-be renewed certificate? What information would be valuable?

I think changing serving to cert-manager webhook would be a significant improvement.
If it has a DNS name/subject, printing that out would be helpful. If it has a kubernetes resource name (it does), printing that out might be helpful (not sure this is my first preference).

@jsoref Thanks!

@jsoref is #5142 what you had in mind?

I'm pretty sure there are at least two code blobs that contributed to the logs above, I suspect your changes cover the first two. In general, they look good, although I'd like to see corresponding output.

@jsoref gotcha, so you want to see this line updated as well?

Seems right.


Fix prependRange logic

Quick Rundown

There was a bug in the prependRange logic. That was the root cause of most of the failures.
The order of didInsertElement calls is consistent, just reversed from what we were expecting previously. Accordingly, I reversed some logic and component ordering in some templates.
There's one failing test that will require some rework of the prepend/replace logic.
Several test failures in 1.10.x. Upgrading to 1.11.x and 1.12.0 fixed things. So I left 1.12.0 as the new default and moved on.
Somewhat surprisingly/unsurprisingly, things are broken in different ways on canary. I hope to chat with some folks, get a simplified repro, open an issue if necessary.

@chrislopresto You are amazing :heart:
Thanks for this. I'll keep this ticket open until we're green :)

Closing this because it's irrelevant now that I've moved all the work this addon does into a helper :)
There is still a bit of work before this is good to go. Mainly deprecations for the helper.


Deregister unhealthy backends

Let the LB deregister some backends automatically after a configurable number of failed health checks.

Fixed as of https://github.com/FlorinBalint/flo_lb/commit/acefa0b8dc32ec52fe42cf987435b36e151167eb


Critical Biographer Bot Updates

[x] create required bots at login
[x] Critical Biographer Bot Updates

[x] new YAML for MyLife Biographer Bot GPT
[x] new schema for API GPT functions

[x] storySummary.json

[x] backend parse instructions

summary, keywords, phase/age, relationships, title

[x] populate stories
[x] respond after save
[x] update biographer-bot instructions

[x] default in Cosmos
[x] current assistants (via Cosmos/Postman)

Note
This branch was duped from the atm current state of 181-version-005-updates
The aim is to deploy it independently to production asap (5/3 morning) for board review


Registration link to Volunteer Induction Handbook (pdf) is broken

Although users can still tick the box, they cannot actually get access to the volunteer induction handbook as the link is broken:
https://www.freeukgenealogy.org.uk/files/Documents/VolunteerInductionHandbook.pdf
Other links seem to work fine, so need to investigate what has gone wrong here.

@DeniseColbert assigned to you to take a look as the link is a FUG file, although @PatReynolds may be able to assist. Flagged urgent as creates issue for any new sign-ups (although registration can still be completed).

Double-checked and all fine. Closing.


Rework the type checker

Rework the type checker so it's less bad.

It uses an actual algorithm that you can reason about.

i.e. we can probably prove it's Turing complete

Time complexity is, for n expressions inferred, roughly O(n) rather than O(n^2) as it was before.

This assumes that the time for replacing a type is roughly constant time.
Note that n is not usually linear with the length of a Chirp program.
For example, in let x = 0 in loop: loop(\.x), loop will recursively instantiate itself with every instantiation, which means infinite instantiations, and thus infinite n.

Recursion limit on instantiations.

Something like let x = 0 in loop: loop(\.x) will overflow this limit and error nicely.
This takes a long time though, because the types get fairly large, and thus type replacement also becomes slow.

I don't understand the Mac OS CI error so I'll merge anyway.


Prospector fails (sometimes)

After building a new environment and installing the tool, I got these new error messages:
pylint 2.3.1 has requirement astroid<3,>=2.2.0, but you'll have astroid 2.0.4 which is incompatible.
prospector <IP_ADDRESS> has requirement pycodestyle<=2.4.0,>=2.0.0, but you'll have pycodestyle 2.5.0 which is incompatible.
prospector <IP_ADDRESS> has requirement pylint==2.1.1, but you'll have pylint 2.3.1 which is incompatible.

In addition, for several days now (after an update) my prospector fails sometimes with the error
Messages
========

.
  Line: None
    pylint: failure / Tool pylint failed to run (exception was raised)

prospector -X ... gives this error
AttributeError: 'MessagesStore' object has no attribute 'get_message_definition'

which was already reported here.
Is there anything we can do about this? Or is this rather an issue of prospector itself?

To fix it locally, run pip install pylint==2.1.1. I guess we could pin pylint, but I expect this issue will solve itself fairly soon.

also, the first bits are Debian (Ubuntu?) messages - I might be Dr Obvious here, but did you do a sudo apt-get update && sudo apt-get upgrade? :grin:

No, but I can't because I run the tool on DKRZ's mistral :grimacing:
You mean those?

pylint 2.3.1 has requirement astroid<3,>=2.2.0, but you'll have astroid 2.0.4 which is incompatible.
prospector <IP_ADDRESS> has requirement pycodestyle<=2.4.0,>=2.0.0, but you'll have pycodestyle 2.5.0 which is incompatible.
prospector <IP_ADDRESS> has requirement pylint==2.1.1, but you'll have pylint 2.3.1 which is incompatible.

These are error messages of pip install -e ".[develop]".

yesh, those ones. Darn! Tell those mistral admins to stop watching cats on the internet and update their system :grin:

I close this since it is not an ESMValTool issue.

It is actually an issue with our installation scripts, I think we may need to pin some dependencies.

For the current environment, the fix mentioned above (pip install pylint==2.1.1) does not work for me anymore.

Solved by #120 in Core.


debug.RemoveBreakpoint doesn't work in version 1.74.1 VScode

Type: Bug
When I try to delete breakpoint by using vscode module, unfortunately i am not able to delete it, on the other hand it was possible on prevous version of vscode.
Sample code :
import * as vscode from "vscode";
...
...
private async deleteBreakPoint(id: string) {
         const removebpts: vscode.Breakpoint[] = [];
            for (const b of vscode.debug.breakpoints) {
                if (b.id == id) {
                    removebpts.push(b);
                    vscode.debug.removeBreakpoints(removebpts);
                }
         }
 }

As I mentioned above, same code was working as expected in previous version of vscode
VS Code version: Code 1.74.1 (1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a, 2022-12-14T10:30:51.966Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.73GB (16.54GB free)

Process Argv
--crash-reporter-id 526d94d7-378a-4ca7-9c7e-9ae729a59785

Screen Reader
no

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

abend-analyzer
Bro
1.0.1

ccf
Bro
1.0.4

cobol-language-support
Bro
1.1.1

data-editor-for-mainframe
Bro
1.0.0

debugger-for-mainframe
Bro
1.6.1

explorer-for-endevor
Bro
1.3.2

hlasm-language-support
Bro
1.5.0

jcl-language-support
bro
1.0.1

vscode-eslint
dba
2.2.6

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.10.3

vscode-docker
ms-
1.23.3

isort
ms-
2022.8.0

python
ms-
2022.20.1

vscode-pylance
ms-
2022.12.20

jupyter
ms-
2022.11.1003412109

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.12

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

vscode-extension-for-zowe
Zow
2.5.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vsccc:30610678
pyindex848cf:30577861
nodejswelcome1:30587005
282f8724:30602487
gswce1:30612156
iaj6b796:30613358
89544117:30613380
fim-prod:30623723

Will be fixed by https://github.com/microsoft/vscode/pull/166722

Fixed in https://github.com/microsoft/vscode/pull/170316

Any workarounds for this at the moment? I would like to remove all breakpoints only on the currently active editor, so "workbench.debug.viewlet.action.removeAllBreakpoints" is not ideal (I believe it removes all breakpoints over all open files).

The fix will be out next week. Sorry for the long lead time on this fix


[WIP] STUN support

this PR adds support for modern STUN, as specified in RFC 5389. Once merged this will close #18.
I've opened the PR early to get some feedback.

Pull Request Test Coverage Report for Build 154

0 of 35 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 7.995%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

examples/stun/main.go
0
16
0.0%

rtcpeerconnection.go
0
19
0.0%

Totals

Change from base Build 139:
-0.2%

Covered Lines:
122

Relevant Lines:
1526

💛  - Coveralls


[stdlib] Manually propagate integer documentation

This includes a few fixes as well, such as places that reference DoubleWidth or still describe functions rather than the operators that replaced them.

@swift-ci Please smoke test

@swift-ci Please smoke test


jest-react-native Warning: @providesModule naming collision

We have initialized a new repo for a react-native app. It only contains .babelrc and package.json so far. After configuring jest as described in https://facebook.github.io/jest/docs/tutorial-react-native.html and then calling npm install && npm test (or jest directly) we get the expected message "No tests found".
But we also get hundreds of warnings like (different module names):
ap: @providesModule naming collision:
Duplicate module name: babel-runtime
Paths: /..../node_modules/react-native/node_modules/babel-register/node_modules/babel-runtime/package.json collides with /..../node_modules/react-native/node_modules/babel-plugin-transform-flow-strip-types/node_modules/babel-runtime/package.json
This happens as soon as we include "jest": { "preset": "jest-react-native"  } in package.json.
We are using nodejs 5.11 and newest versions of react-native and the babel and jest libraries (jest 15.1.1).
We assume that the warnings point to some problem that will prevent it from running correctly?
Package.json:
{   "name" : "myapp",   "version" : "0.0.1",   "license": "UNLICENSED",   "private": true,   "repository": "100DAYS/<myrepo>",   "engines" : {      "node" : ">=4.0"    },   "scripts": {     "test": "jest"   },   "jest": {     "preset": "jest-react-native"   },     "dependencies": {     "react": "15.3.1",     "react-native": "0.32.0"   },   "devDependencies": {      "babel-jest": "^15.0.0",      "babel-preset-react-native": "^1.9.0",      "jest": "^15.1.1",      "jest-react-native": "^15.0.0",      "react-test-renderer": "^15.3.1"   } }
jest --debug output:
jest version = 15.1.1
test framework = jasmine2
config = {
"haste": {
"defaultPlatform": "ios",
"platforms": [
"android",
"ios"
],
"providesModuleNodeModules": [
"react",
"react-native"
]
},
"moduleNameMapper": [
[
"^image![a-zA-Z0-9$-]+$",
"GlobalImageStub"
],
[
"^[./a-zA-Z0-9$-]+\.(bmp|gif|jpg|jpeg|png|psd|svg|webp)$",
"RelativeImageStub"
]
],
"modulePathIgnorePatterns": [
"/node_modules/react-native/Libraries/react-native/",
"/node_modules/react-native/packager/"
],
"preprocessorIgnorePatterns": [
"node_modules/(?!(jest-)?react-native|react-clone-referenced-element)"
],
"setupFiles": [
"/node_modules/jest-react-native/build/setup.js"
],
"testEnvironment": "/node_modules/jest-environment-node/build/index.js",
"preset": "jest-react-native",
"rootDir": "",
"name": "-home-....",
"testRunner": "/node_modules/jest-jasmine2/build/index.js",
"scriptPreprocessor": "/node_modules/babel-jest/build/index.js",
"usesBabelJest": true,
"automock": false,
"bail": false,
"browser": false,
"cacheDirectory": "/tmp/jest",
"colors": false,
"coveragePathIgnorePatterns": [
"/node_modules/"
],
"coverageReporters": [
"json",
"text",
"lcov",
"clover"
],
"globals": {},
"mocksPattern": "mocks",
"moduleDirectories": [
"node_modules"
],
"moduleFileExtensions": [
"js",
"json",
"node"
],
"noStackTrace": false,
"notify": false,
"resetModules": false,
"testPathDirs": [
""
],
"testPathIgnorePatterns": [
"/node_modules/"
],
"testRegex": "(/tests/.*|\.(test|spec))\.js$",
"testURL": "about:blank",
"timers": "real",
"useStderr": false,
"verbose": null,
"watch": false,
"cache": true,
"watchman": true,
"testcheckOptions": {
"times": 100,
"maxSize": 200
}
}

Are you using npm2? If so, you can probably safely ignore this warning. I recommend updating to npm3, where this shouldn't be happening. You can also probably add node_modules/react-native/node_modules/ to your modulePathIgnorePatterns.
(Closing because this is unlikely something we can fix)

using npm 3.10.6, node 15.1.1
but if it is ok to ignore the warnings, i will do for now :-)
thanks

adding node_modules/react-native/node_modules/ to modulePathIgnorePatterns did the job, thanks


Async support for interpreter.

Add EvalAsync() to Interpreter and plumb async through EvalVisitor and functions.
Add tests demonstrating true async.
Still a few .Results to chase down.

                return OperatorBinaryAdd(this, context, node.IRContext, args);

These delegates are still async :(
This is because they go through StandardErrorHandling.cs, which produces async delegates.

Refers to: src/libraries/Microsoft.PowerFx.Interpreter/EvalVisitor.cs:200 in 068dcf4. [](commit_id = 068dcf4ffc7da9a7db8e5386324ed4449461c099, deletion_comment = False)

Hi 👋
This feature will be very usefull for us !
(async execution + cancellable task to avoid overloading server by heavy formula)
I don't know if it is the right place to leave this comment, but there is another place we would need Async interface : in the IPowerFxScopeFactory
We create the engine in async way, so we need to sync over async the GetOrCreateInstance method to respect interface 😞
Should I declare and issue about this ?

@Felx-B - can you file a new issue about IPowerFxScopeFactory? We can tackle that separately - those changes would be in separatee files from these. Do you have any feedback on additional test cases to add here?

Ok, I'll do a separate issue for this.
I think it would be interesting to add a test case with concurrent formula evaluations.
To illustrate, with the use case I showed with the gif :
I aim to evaluate every values in parallel and then wait for all task to be completed.
I don't know yet if the RecalcEngine would support this, and how thread safe it is.

good idea - recalc engine is not thread safe - but multiple recalc engines should be able to interleave on a single thread.

In reply to:<PHONE_NUMBER>


[PR-23132] Add the ability to store certificates in the database

Specs will be added and modified after the review of the main logic.

as an idea, we can pass intermediate and p12_certificate into as it looks like this is one place where certificate actually used https://github.com/talkable/passkit/blob/83c9c8ddcf6a7c8b1aa6a971f9c0dc02aef8323f/lib/passkit/generator.rb#L131-L142
how this can be used:
module Passkit
  class Factory
    class << self
      # generator is an optional ActiveRecord object, the application data for the pass
      def create_pass(pass_class, generator = nil, options = {})
        pass = Passkit::Pass.find_or_create_by!(klass: pass_class, generator: generator, **options)
        p12_certificate = OpenSSL::PKCS12.new(db.certificate, db.password)
        intermediate_certificate = OpenSSL::X509::Certificate.new(File.read(INTERMEDIATE_CERTIFICATE))

        Passkit::Generator.new(pass).generate_and_sign(p12_certificate, intermediate_certificate)
      end
    end
  end
end

feel free to reach out and set up a quick call to with me and @zhuravel


Remove label from classes applied for syntax highlighting

Text that matches constant.other.object.key.js is being matched and having the classes string.unquoted.label.js applied. The .label class applies Bootstrap's CSS which has bold, a different font size, and padding, which all contribute to making the rendered text a headache to edit because the visible location of the cursor does not match the actual cursor position, and therefore I end up editing the wrong characters.
Example
Now the testWithLabel is default syntax highlighting. ing key is that is detected by another grammar pattern and correctly highlights. testWithoutLabel is what I expect to see, and I was able to accomplish by manually removing the label class from the element in the DOM.
Screenshot

Code
let obj = {
  testWithLabel: null,
  testWithoutLabel: null,
  ing: function() {

  }
};

Bug
See https://github.com/gandm/language-babel/blob/master/grammars/Babel Language.json#L197
Code
 "literal-labels": {
      "patterns": [
        {
          "begin": "(?<!\\?)(?<!\\?\\s)(?=(((')((?:[^']|\\\\')*)('))|((\")((?:[^\"]|\\\\\")*)(\")))\\s*:)",
          "end": ":",
          "endCaptures": {
            "0": { "name": "punctuation.separator.key-value.js" }
          },
          "patterns": [
            { "include": "#literal-string" }
          ]
        },
        {
          "name": "constant.other.object.key.js",
          "match": "(?<!\\.|\\?|\\?\\s)([_$a-zA-Z][$\\w]*)\\s*(:)",
          "captures": {
            "1": { "name": "string.unquoted.label.js" },
            "2": { "name": "punctuation.separator.key-value.js" }
          }
        }
      ]
    },

Good catch. Someone else had this issue and I knew it was something else styling it but I couldn't recreate it and their issue went away on a reload of Atom. You say Bootstrap CSS is styling it but from where? a package? a theme?

Not sure, it could be Atom's core styles? In case it's a theme, here is my current theme settings:

UI Theme: Atom Dark
Syntax Theme: One Dark

Static screenshot showing what I see as the source style file of the .label rule:

It doesn't appear to be either of those themes, nor does it seem to be core, at least not on my system. I'm happy enough to accept the pull request but I'd like to understand what is doing this. Things shouldn't style text without being asked! I don't suppose you could list your installed packages and themes?

Gladly. I am also curious.
✗ apm list --installed
/Users/glavin/.atom/dev/packages (1)
└──<EMAIL_ADDRESS>
/Users/glavin/.atom/packages (65)
├── .bin
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Thanks. I'll look at that list. FYI when I put your example code in my editor it looks fine and inspector shows that that the computed style is generated from app.asar\node_modules\one-dark-syntax\index.less

One further thing. If you revert your PR and reload Atom is the issue still present. I can't see why bootstrap.css is selected on your system when on mine it is the one-dark-syntax styling it!


Color Twist - Optimizations in sse/avx2 for tensor implementation

Adds color_twist optimizations in sse and avx2 for host
Uses a tensor based implementation
Support for NCHW<->NHWC, U8/F16/F32/I8
Adds the corresponding unit tests and performance tests

@rrawther This PR adds the new color_twist tensor based implementation.

@rrawther @r-abishek There are potential issues with this PR. I have contacted Abishek regarding them. I will get the images that look wrong and share them via email.

@rrawther I've increased dst static allocation by 1 due to the writes. This should fix the issue. @paveltc Please let me know if all the issues are fixed.

@rrawther @r-abishek I ran the tests and I don't see the issues.

@paveltc Thanks for verifying, @rrawther I have added the minor fix here - https://github.com/GPUOpen-ProfessionalCompute-Libraries/rpp/pull/81/commits/bb0252dd2ca52505510766b6db974f2c1bc55237

@kiritigowda: this is ready to merge


can directly edit and modify the original text in the pdf

can directly edit and modify the original text in the pdf

Duplicate of #601


Remove constant_function for AutoEnzyme

[!WARNING]
This PR and the associated release are breaking wrt 1.6.1, but we will yank 1.6.1 and 1.6.0 right after

Checklist

[x] Appropriate tests were added
[x] Any code changes were done in a way that does not break public API
[x] All documentation related to code changes were updated
[x] The new code follows the
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
[x] Any new documentation only uses public API

Additional context
Following a long discussion with @ChrisRackauckas and @wsmoses, we decided to remove the constant_function setting for now, and reinsert it later with different defaults (once Enzyme implements a few changes on their side). This PR does the removal and bumps ADTypes to v1.6.2, after which we will need to yank v1.6.0 and v1.6.1.

https://github.com/EnzymeAD/Enzyme.jl/issues/1669

Let's wait for a review from Billy and Chris before merging

Let's just go straight to the nothing default then?

I wanted to wait until the implementation exists on the Enzyme and DI side before reintroducing this kwarg. Our mistake last time was to introduce it before it actually did anything, and as a result we got the design wrong.

But if @wsmoses is confident that constant_function=nothing is the right third option I can modify this PR to just change the default instead of removing the kwarg

I would probably do the yank now then design when ready.
Being even more forward looking this should likely actually be a Union{Nothing, Enzyme.Annotation}, since the function could be nothing, constant, duplicated, or even active

This constant function is not the appropriate name

function_activity

I mean that sounds like a good name to me, but it also might be wise to
wait til things are settled before choosing
On Fri, Aug 2, 2024 at 11:42 AM Christopher Rackauckas <
@.***> wrote:

function_activity
—
Reply to this email directly, view it on GitHub
https://github.com/SciML/ADTypes.jl/pull/74#issuecomment-2265672216, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJTUXABNMKRVTSUUD2VQGTZPOSEXAVCNFSM6AAAAABL333KG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVGY3TEMRRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Okay then removing everything first is the right move. In this spirit, do you approve this PR?


Low readability problem of strong tag | I Changed theme's strong tag font-weight 500 into 700(default bold)

Description of Problem
The strong tag's style can not differ itself with others text
Proposed Solution
Change style of strong like below
Additional Information
Latest version - strong tag's font-weight: 500
First Original Theme strong tag (font-weight: 600)
https://github.com/vuejs-kr/docs-next/blob/ada000ad54551f1fc79c5ecd50203dd77f88dbc4/src/.vuepress/theme/styles/index.styl
1. Previous

2. Proposal

Expected result (font-weight was 500 before)

Maintainer should see in below site to test this problem
https://v3.ko.vuejs.org/guide/single-file-component.html#소개
Thanks for informing Low readability problem of strong tag @grighth12

Thank you!


Add std::panic::RefUnwindSafe marker trait to the Custom proxy type.

The gotham engine requires that StateData contain types that are RefUnwindSafe. This particular type seems to be the primary cause of the issue.

Thanks for the PR!
This would unfortunately be a breaking change (adding new trait bounds, so code that previously compiled might not anymore). Also, it's not typical to find this particular trait as bounds in most places. However, you can fix the issue in your app directly, putting your state inside an AssertUnwindSafe.


Fix code scanning alert - DOM text reinterpreted as HTML

Tracking issue for:

[x] https://github.com/carlesloriente/nocc-bootstrap-theme/security/code-scanning/1

Fixed in v1.2.0


Option to override the automatic host-id generation on K8s Nodes

Hello,
Is there an option to override the host-id generation for the oneagent rolled out via the operator to k8s nodes?
I'm working with a dynamically sized K8s Cluster on GCP with preemptible nodes that can die at any time.
In Dynatrace this results in a VERY long host list over time as nodes come and go. For every Node a new host in created.
Now Dynatrace has this host-id option for some time already and I think it would make sense to leverage this to consolidate nodes into the same entities based on IP address for example.
E.g.:
all the hosts with the same name (host naming rule ending in the last octet of the IP address) would truly become one host entity instead of multiple. And I'd not get thousands of (inactive) host entities over time but only the size of my hosts IP pool)

kR

Hi, that is currently not possible.
Dynatrace reviews feature requests in the Dynatrace community rather than Github. This helps our team consolidate, rank, and prioritize important input like yours.
Please search for similar requests, collaborate, and ask questions using the link above. Remember to add the labels "kubernetes" and "dynatrace-operator" to help get the attention you deserve.
Thanks for your help!

that is currently not possible.
Hence the feature request :-)

But this is rather inconsistent. Some feature requests are handled here, some are handled (or mostly forgotten and never followed up with) on the community.
The "official" OSS project page of the operator has been moved here, but discussed it should be on the community. That is tedious....
But I created an RFE there

It hosuld work via OneAgent arugument --set-host-id-source, it's not listed under the limitations .
@luhi-DT is there any reason why this argument shouldn't work?


aggregate Identity creation

Summary
aggregated Identity creation logic to make platform SDK's job easier. i.e. merged create_from_legacy and create_to_be_signed into one function.
Instead of requiring platform SDK to choose what it wants, we just let them pass in address and Option<legacy_key> and take care of the rest.

#721  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @37ng and the rest of your teammates on  Graphite

Added the logic to assert that address matches legacy_signed_private_key.
Less LoC and more concise for Identity::new()

Think I made a mistake that removed fallback flow... Will mark this as ready for review once it's fixed.


Duplicates charts to rag folder so the Marketplace release can work

When we release RAG QSS on Marketplace, we zip the whole rag folder and upload it to a GCS bucket so Marketplace can use it to do terraform apply. With the current setup to install gmp-engine for rag, the Marketplace will not be able to find the charts since it's not in the GCS. It is also not possible to modify the chart path to point to the github patch like what we do for the other modules in RAG, because it is not supported with the current setup of the gmp-engine chart. As a mitigation, duplicating the charts to the rag folder so it can be zipped together and uploaded to GCS.

/gcbrun


504 modal intro page

This PR adds a modal that deploys on initial page load. It has welcome text and allows the user to either take a tour, view an example analysis, or just use the tool. If they are loading a saved state, it does not show them the example analysis option and replaces it with a button to view the saved analysis (this just closes the modal, since the saved analysis is being loaded regardless).
If the user closes the modal before the page is ready to use, it opens a page dimmer with a "loading" spinner until the filterViewLoaded event occurs (which is not 100% at the end of the load process but it is close).
The example analysis button is disabled until the page is finished loading, to avoid triggering the state change before the app can handle it.
The 'tour' functionality is not yet implemented.
This replaces the 'loading saved state' dimmer used previously. The dimmer is only shown on map view - when loading a saved specific project in the project-view, no 'loading' page is shown anymore (the page loads quickly enough that I don't think we need it in that context).

@ostermanj the one thing that would be useful for you to QA (besides an overall test drive) is the way that I implemented the loading of an example. I used the decodeState to do this, so that the proper setState AND UI updates would occur. I did this by triggering the window history, and then telling the router to decode.
My question was whether I'm ok using the (useless) object that I put into the first parameter of the replaceState call. Elsewhere, you put the router.stateObj into this, but becuase the state has not been decoded we don't have a proper state object available to us anywhere. It looks like you're not actually using this state object though - it would just be used if you called popState as described here. It looks like you're always using the URL as the master of truth for the state to decode rather than using that state object. Some testing proved it out.
I will be adding the tour to this next, can merge either before or after this.

You're right that router.js passes in router.stateObj but that's not really doing the work. The work is all in the paths. My early attempts in router.js tried using the stateObj and popState but I could not get that method to work on a fresh load of a saved state. So instead it always just parses the url parameters. I had a better handle on it a month ago:

router.js sets the window's history.state but in the end this is not ever read back in. the history.state would only be available on browser back or forward, not on a fresh load of a paramified URL, so I opted to rely only on the encoded URL for forwards, backs, and fresh loads. This might avoid some cross-browser issues, too.

Hopefully that's true :)

Looks really great! There's one weird thing: when I load the page without my developer tools open, the modal extends below my screen (1280x800) and won't scroll.

When I open the tools, the modal will scroll; when I close it again, the modal is fully visible.
The tour is really cool.
One thought: should we provide a "don't show again" option? Would require setting a cookie.

Thanks @ostermanj. I had a surprising amount of trouble getting the modal to behave as expected - maybe there's some bootstrap/semantic ui conflicts as they both have 'modal' classed objects. I'll mess with the modal to get it viewable.
I figured it's easier to not set the 'don't show again' option because it won't improve performance - they still have to wait the same amount of time for the page to load. I did verify that using both the in-app back and the back button after viewing a project page only display the modal the first time you see the map view and not again (unless you refresh the page)


Change the header background color & use logo instead of text

To do:

Change the color of header and render the logo at src/assets/logo.png
Add a favicon. Use the logo for the favicon

I will pick it up


filtering an array using .filter()

Challenge Waypoint: Filter Arrays with filter has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var oldArray = [1,2,3,4,5,6,7,8,9,10];

// Only change code below this line.

var newArray = oldArray.filter(function(val){
  return val > 5;

});

// Only change code above this line.

(function() { return newArray; })();

I'm trying to filter oldArray[1,2,3,4,5,6,7,8,9,10] to take out any numbers greater than five so I'm using the filter method with the function return val > 5 and storing it in newArray. My code seems to be creating newArray with the numbers 6 -10 but I still can't pass the waypoint.

The waypoint is about filtering out numbers greater than 5. So your function should return true for numbers that are less than 5.
return val <= 5;


a couple of bugs with svg export

lorien v0.6.0 official build
system: debian 12 bookworm, amd64
After using some space on the right, export to svg still exports that part of the canvas into the image as well.
Also, the text on top (TOM 1) has not been exported completely. Attaching the file for you to see.

Could you test the lastest version on the main branch? You can download automated builds from here: https://github.com/mbrlabs/Lorien/actions/runs/10816442683
The only thing i can think of right now is that there were still some brush strokes left on the far right side when you exported the svg. Would it be possible to share your savefile here (you probably have to zip it)?


For Mac: screen will turn black and have to close the app.

Creating new folder or deleting file gives out full screen confirmation dialog and then turns black.

Can you be a little more specific?
Which version of Storage Explorer?  Which version of Mac OS?
Is this for Blob? File Shares?  ADLS Gen2 account?  or something else?
Does this happen to other dialog or just these two?

Hi @jinglouMSFT We also met this issue.
Platforms: MacOs 10.13.6
Repro Steps:

Launch Storage Explorer -> Make it full screen.
Execute an action to open one dialog.
Select and click one button on the prompt dialog.
Check the result.

Actual:
The screen turns black.

Can you be a little more specific?
Which version of Storage Explorer?
Version: 1.10.1
AzCopy Version: 10.2.1

Platform: macOS
Architecture: x64
Build Number: 20190919.2
Commit: 868c6dff1
Support ID: e6a2b7fc-8e8c-88ba-2db7-d8fce1f406cb

Which version of Mac OS?
Mac OS Catalina 10.15.1 ,

Is this for Blob? File Shares? ADLS Gen2 account? or something else?
Blob, gen2

Does this happen to other dialog or just these two?
So far these two, not always but most of the times.

@amtsha09 great bug find. None of us have ever noticed this. For now, you'll need to not run in full screen, but we'll look into getting this fixed.

@MRayermannMSFT happy to help :-)
Thanks.

Fix merged into master. Will ship with 1.13.0. Thank you again @amtsha09


Why use a synchronous API (writeFileSync) for file writing

Sentry is a great project, we use it on the Electron client, and there's a question I don't quite understand: Why use a synchronous API (writeFileSync) for file writing?On some low-end devices, especially computers that use mechanical disks, the main process execution can be blocked

Thanks for opening an issue about this.
It looks like writeFileSync is used in the Store which has gone virtually untouched for over 3 years when it was pulled from @sentry/utils.
I did quickly have a go at making the store entirely async and got some test failures, so it looks like the session handling is at least partially relying on the sync writing.

Thank you for your attention to this feedback, looking forward to the optimized version

Re-opening as fix was reverted in https://github.com/getsentry/sentry-electron/pull/552