Add teachers of Snitz Gymnasium

Added the teachers of Snitz Gymnasium which I added here: https://github.com/JetBrains/swot/pull/3336

@aetea Pull request merged. Thank you!


Create first boot "custom default" BMC configuration

Before first boot: prepare the BMC with some custom options as:

delete all boot options from BIOS, but IPv6 PXE boot
delete all users but the default one
on Lenovo: disable crappy USB Ethernet adapter, which causes issues with system-networkd marking the network too early as "online"
…

/cc @afritzler @gehoern @5kt @MalteJ
Following our discussion last week


What type of workflow is recommended for VSCode / Azure?

I'm curious why one would integrate an editor with a cloud-services: To me it seems to circumvent the effort put into CI/CD pipelines and go with the meme: "I don't test my code, but when I do its in production...". This leads me to the related question: What's the workflow you suggest and is this integration meant for startups (give Azure a quick try) or Enterprise (long lasting mature code)?
Thanks in Advance,
Jason.

No thought 'eh?


Refactor overlay styles to use lumo-menu-overlay

Remove copy-paste code and use the lumo-menu-overlay mixin directly.
Use CSS media queries instead of the fullscreen property for the overlay behavior adjustments (consistent with the menu-overlay styles).
A couple of other small style fixes related to sizing and touch device styles.
Use --vaadin-infinite-scroller-buffer-offset instead of a transform to shift the first month in the scroller closer to the middle of the overlay.
Depends on https://github.com/vaadin/vaadin-lumo-styles/pull/9

This change is

 (except for the formatting nitpick)

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

theme/lumo/vaadin-date-picker-overlay.html, line 19 at r1 (raw file):

        padding: 0;
        height: 100%;
        overflow: hidden;

BTW unexpected scrollable content part, but that is introduced in the lumo-styles PR.
Not a blocker here, just reminding.

theme/lumo/vaadin-date-picker-overlay-content.html, line 25 at r1 (raw file):

      [part="months"] {
        --vaadin-infinite-scroller-item-height: calc((var(--lumo-size-s) + var(--lumo-space-s)) * 6 + var(--lumo-font-size-l) + var(--lumo-space-m) + var(--lumo-font-size-xs) + var(--lumo-space-s) + var(--lumo-space-s));

I’m nitpicking, but could you please make more readable?
For example, make every summand on its own line with a comment.

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, 2 unresolved discussions.

theme/lumo/vaadin-date-picker-overlay-content.html, line 25 at r1 (raw file):
Previously, platosha (Anton Platonov) wrote…
I’m nitpicking, but could you please make more readable?
For example, make every summand on its own line with a comment.

Done. Can’t have comments on the same line (inside the calc), so I added a comment above the calc.

theme/lumo/vaadin-date-picker-overlay.html, line 19 at r1 (raw file):
Previously, platosha (Anton Platonov) wrote…
BTW unexpected scrollable content part, but that is introduced in the lumo-styles PR.
Not a blocker here, just reminding.

Yeah, this needs to be overridden in date-picker, unfortunately. I don’t know how to avoid the scrolling content part in the menu-overlay styles, as mentioned in that PR.

Comments from Reviewable

@tomivirkki, what do you mean by closeTo assertions?

Review status: 0 of 3 files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Noticed that the tests were failing due to some rounding error on Edge & IE11 https://travis-ci.org/vaadin/vaadin-date-picker/builds/351337193#L929 Of course a cleaner fix than closeTo would be preferred

Comments from Reviewable

Should I fix that, or can I expect the team to handle it?

Review status: 0 of 3 files reviewed at latest revision, 2 unresolved discussions, some commit checks broke.

Comments from Reviewable

I will take care of that.

Reviewed 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks broke.

Comments from Reviewable

Reviewed 1 of 3 files at r2, 3 of 3 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable


model: h2oautoml: Add h2o AutoML

#959

Codecov Report

Merging #982 (205133f) into master (0b84ca2) will decrease coverage by 0.52%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #982      +/-   ##
==========================================
- Coverage   85.89%   85.36%   -0.53%
==========================================
  Files         141      141
  Lines        9086     9158      +72
  Branches     1516     1540      +24
==========================================
+ Hits         7804     7818      +14
- Misses        958     1008      +50
- Partials      324      332       +8

Impacted Files
Coverage Δ

dffml/util/testing/docs.py
81.81% <0.00%> (-5.28%)
:arrow_down:

dffml/util/packaging.py
80.64% <0.00%> (-4.55%)
:arrow_down:

dffml/util/testing/consoletest/runner.py
83.67% <0.00%> (-3.57%)
:arrow_down:

dffml/df/memory.py
78.98% <0.00%> (-2.80%)
:arrow_down:

dffml/util/data.py
74.03% <0.00%> (-2.77%)
:arrow_down:

tests/util/test_net.py
98.24% <0.00%> (-1.76%)
:arrow_down:

dffml/cli/cli.py
62.50% <0.00%> (-1.74%)
:arrow_down:

dffml/noasync.py
78.18% <0.00%> (-1.13%)
:arrow_down:

dffml/cli/dataflow.py
80.12% <0.00%> (-0.49%)
:arrow_down:

dffml/df/types.py
82.59% <0.00%> (-0.39%)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

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


No Docker client strategy found with podman

Hi @cristianrgreco ,
I read other posts about podman but not totally sure how people succeeded in using it with testcontainers (for basic usage I mean). (Note that I used your library with Docker without troubles previously).
When running a test I get No Docker client strategy found.
From what I understand testcontainers is not finding the socket. So to find it I use:
podman machine inspect --format '{{.ConnectionInfo.PodmanSocket.Path}}'

That gives me /Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock.

So I tried to customize it:
export DOCKER_HOST=/Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock

It says [ERR_INVALID_URL]: Invalid URL

Then tried:
export DOCKER_HOST=unix:///Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock

It says
(HTTP code 500) server error - fill out specgen: unix:///Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock:/var/run/docker.sock:rw: incorrect volume format, should be [host-dir:]ctr-dir[:option]

I also unset DOCKER_HOST and then try both:
export TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock
export TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=unix:///Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock

But nothing changes...

I'm a bit lost, do you know what's needed please?
Thank you,
Environment Information

Operating System: MacOS
Testcontainers version: v9.5.0

@cristianrgreco found a working solution by using both:
export DOCKER_HOST=unix:///Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock
export TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/Users/sneko/.local/share/containers/podman/machine/qemu/podman.sock

But I'm not sure to understand. Why I need to have both at the same time? Can't testcontainers infer DOCKER_HOST according to TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE? Or vice-versa?
Thank you,

Hi @sneko,
Take a look at how Podman is setup and used in this project's CICD pipeline: https://github.com/testcontainers/testcontainers-node/blob/main/.github/workflows/test.yml#L70-L84
One difference is the location of the socket that's used.
Note that there is a PR that's been merged to improve Podman support: https://github.com/testcontainers/testcontainers-node/pull/515, but it hasn't yet been released.

I saw https://github.com/testcontainers/testcontainers-node/blob/main/.github/workflows/test.yml#L70-L84 but for whatever reason I did something wrong. Indeed just retested and TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE is not needed.
Thank you 👍

Hi @sneko, I recently updated the supported container runtimes doc with a section for MacOS/Podman: https://node.testcontainers.org/supported-container-runtimes/
Could you please have a look and let me know if the workaround fixes your issue?

Using export TESTCONTAINERS_RYUK_DISABLED=true was the solution! Thank you for the reactivity.
About https://node.testcontainers.org/supported-container-runtimes/ you should probably replace XDG_RUNTIME_DIR by running podman machine inspect --format '{{.ConnectionInfo.PodmanSocket.Path}}'. On my MacOS $XDG_RUNTIME_DIR is empty.

About https://node.testcontainers.org/supported-container-runtimes/ you should probably replace XDG_RUNTIME_DIR by running podman machine inspect --format '{{.ConnectionInfo.PodmanSocket.Path}}' because on my MacOS $XDG_RUNTIME_DIR is empty.

This is a good point, I will update the docs.

(curious to know how to use Ryuk? Because I tried podman machine set --rootful so I thought permissions would work properly?)

I also would love to know how to make it work :slightly_smiling_face: As of now I don't know what's the issue. Ryuk is also working fine in colima and rancher, so the issue may be Podman specific.


Packagist badges: invalid response data

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] gh-badges NPM package

:beetle: Description
MIT Packagist license is not set. Display information: "invalid response data".
:link: Link to the badge
https://img.shields.io/packagist/l/cse/helpers-json.svg

Problem looks to be related to the schema we're using.
Relevant snippet from the API response shows that the dev-master object key does not contain an extra key
"dev-master": {
  "name": "cse/helpers-json",
  "description": "The helpers allows you to JSON processing. Encode, decode, check error, throw exception - all this is available in this library.",
  "keywords": [],
  "homepage": "https://github.com/cs-eliseev/helpers-json",
  "version": "dev-master",
  "version_normalized": "9999999-dev",
  "license": [],
  "authors": [],
  "source": {...},
  "dist": {...},
  "type": "library",
  "time": "2019-03-25T08:37:18+00:00",
  "autoload": {...},
  "require": {...},
  "require-dev": {...}
},

But I believe the schema has extra as a required key: https://github.com/badges/shields/blob/master/services/packagist/packagist-base.js#L11

I'm getting this as well with downloads when I never used to have an issue:

Same underlying issue, I'm working on fixing it now

Oh okay awesome thanks so much! :smile:

Alright I believe I've got it fixed in the linked PR, viewable/testable in the associated staging app @ https://shields-staging-pr-3239.herokuapp.com/
Here's the corresponding badges mentioned in this thread using the staging app endpoint:
https://shields-staging-pr-3239.herokuapp.com/packagist/l/cse/helpers-json.svg

https://shields-staging-pr-3239.herokuapp.com/packagist/dt/adldap2/adldap2.svg

https://shields-staging-pr-3239.herokuapp.com/packagist/dt/adldap2/adldap2.svg

I'm signing out for the night but if anyone else has any other badges that are currently broken, try checking them out in the staging app, and let me know if they're still broken even in the staging app

I have the badge broken too:

And shields-staging-pr-3239.herokuapp.com fix it:

Thanks, hope to see it merged.

Okay awesome thanks so much! =)

Hello, I see you closed this but right now as you can see in my comment, the version on img.shields.io is still "invalid response data" and the herokuapp is not available neither. Would we see this on shields.io soon?

Sorry, I did not understood the procedure, it's a auto-close from the PR and deployment is in progress. Great!

FYI the fix has been deployed, so your packagist badges should be working again @ https://img.shields.io/packagist/**

Thanks again for the quick fix @calebcartwright, much appreciated!


gmaps4rails.*.js coming up blank causing js error Gmaps not defined error.

Here is my site  http://www.camphurricane.com/locations/hermann-park   I'm using heroku for hosting but i'm not sure if it makes a difference.  I'm using Rails 3.0.10  works fine locally in development but after pushed out doesn't work.

run:
rails generate gmaps4rails:install
On Oct 8, 2011, at 8:43 PM, Justin Sunsri wrote:

Here is my site  http://www.camphurricane.com/locations/hermann-park   I'm using heroku for hosting but i'm not sure if it makes a difference.  I'm using Rails 3.0.10  works fine locally in development but after pushed out doesn't work.
--
Reply to this email directly or view it on GitHub:
https://github.com/apneadiving/Google-Maps-for-Rails/issues/104

the js files are already in my javascript folder.  does that make a difference?

They don't seem to be found, see here:
http://www.camphurricane.com/javascripts/gmaps4rails/gmaps4rails.base.js

no kidding....  ;-)    http://pastie.org/2662036   here you can see all what i did in the console same result...  no files

Ok I see: you have an old version of the gem and there was a bug in the generator.
simply move your js files from javascripts to javascripts/gmaps4rails

I don't know why i didn't see that the folder wasn't there  :-/


emit assets with unknown info

System Info
System:
OS: macOS 13.0
CPU: (8) arm64 Apple M1 Pro
Memory: 56.33 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
Yarn: 1.22.15 - ~/.nvm/versions/node/v16.14.2/bin/yarn
npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
pnpm: 6.11.0 - ~/.nvm/versions/node/v16.14.2/bin/pnpm
Browsers:
Chrome: 114.0.5735.198
Safari: 16.1
npmPackages:
@rspack/cli: 0.2.4 => 0.2.4
Details
When emit assets with unknown info, it doesn't work.
In this example, I emit asset with { compressed: true }, but it doesn't appear in stats
rspack:

webpack:

I'm currently working on #3677 this pr,  but blocked by this bug
Reproduce link
https://github.com/faga295/rspack-reproduce/tree/emit_assets_with_unknown_info
Reproduce Steps

pnpm run build:rspack
pnpm run build:webpack
compare the difference of output

bump

StatsAsset.info has been aligned by https://github.com/web-infra-dev/rspack/pull/6951. I will close this issue, and if you encounter new problems, you can just reopen it.


video/jxsv

Making a start on JPEG XS per [Work In Progress] BCP-006-01.

I'm happier with this now.
Some questions:

I was trying to keep everything to do with JPEG XS in the new nmos/video_jxsv.h file but since we're going to reuse several of the new Flow and Sender parameters, do you think we should move these (profile, level, st2110_21_sender_type, etc.) into nmos/json_fields.h or into new headers for e.g. the Flow Attributes, Sender Attributes and Capabilities registers in the NMOS Parameter Registers?
I'm still missing the new format-specific parameters introduced in the forthcoming ST 2110:2022 revision. I've got the definitions of the necessary C++ types/constants stashed locally. But since these apply really to ST 2110-10, ST 2110-21/-22, not a specific media type, we'll end up with a lot of duplication in some of the functions that use them (even more than already between video/raw and video/jxsv format-specific parameters!)... I'm wondering about little sub-structs and helper functions therefore, or maybe function templates... It would be good to chat it through...

Conclusions from review with @jonathan-r-thorpe and @lo-simon:

SDP specs for particular formats (both IETF RFCs and SMPTE ST 2110 docs) tend to treat each other as inspiration, or tool bags, rather than as OO classes to inherit from or aggregate. Therefore, although it feels wrong in the C++ codebase, it is better to do the same and accept repetition of member variables, e.g. between video_raw_parameters and video_jxsv_parameters and future ones. If there is function body duplication in the manipulation of these we could consider using function templates later.
Although the values for Flow profile for JPEG XS in the NMOS Parameter Registers are by definition equal to the SDP profile format-specific parameter values defined in RFC 9134, that exact mapping is unlikely to be repeated for other formats like H.264 and H.265, which express profiles and levels in a different way in the SDP file. Therefore, the video_jxsv_parameters struct should use an sdp::video_jxsv_profile or sdp::rfc9134::profile or some such, which for now has the same values as nmos::profile, and similarly for level and sublevel. That then also makes these member variables consistent with the other ones that already exist like sdp::colorimetry (cf. nmos::colorspace).

For the same reasons, but a little less confidently, we felt the video_jxsv_parameters struct should have separate transmode and packetmode member variables, slavishly representing the SDP format-specific parameters, rather than the combined nmos::packet_transmission_mode variable.

Defining types like nmos::profile in separate headers than nmos/video_jxsv.h now makes sense since we expect to use them for more codecs. The same goes for the related nmos::fields::profile, nmos::caps::format::profile, etc. However, sdp::fields::profile can stay in nmos/video_jxsv.h for now.


[javascript] No intellisense for javascript objects created with new?

From @raghur on July 4, 2016 16:31

VSCode Version:1.2.1
OS Version:Windows 8.1 x64

Steps to Reproduce:

I have a nodejs library generated with AutoRest which also generates d.ts files.
It's package.json has "typings": "path to d.ts file" generated by autorest.
In a project where I have the npm package above referenced, there is intellisense only for the main class constructor. Once an instance is created, intellisense doesn't work on the created object to suggest completions.

gif below to explain

Copied from original issue: Microsoft/vscode#8738

@raghur the information provided is not enough to understand what is going on. please share more context. ideally a repro project that we can use to identify the problem.

The issue is that I see vs code reading in type definitions for the api object. Hovering over it shows class and parameter into. However over an instance is newed, there is no intellisence available on the object (methods or properties).
I will try to get an example using open source code

Without information about the declaration this issue is unactionable. closing for now. please reopen if you have more information.

vscode-bug-9519.zip
Ok - here's a sample project illustrating the issue. It's generated from swagger pet store spec json here - https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v2.0/json/petstore.json
Here's a gif as well showing

The issue is that I see vs code reading in type definitions for the api object. Hovering over it shows class and parameter into. However over an instance is newed, there is no intellisence available on the object (methods or properties).

I see. the issue here is that petstore definition has "required" arguments, and the type system can not figure out a call signature that matches the target.. here is a simpler repro:
function foo(a, b) { return "";}
foo(). // expect length, actual non.

I should add, in a js file, we should allow omitting arguments in a call site.


Scan code which contains embed images or logo

How can I scan a code which has a image inside of the QR code?
For example:

That QR code scans fine for me on a Huawei RNE-L22 (nova 2i) running 7.0 and a Xiaomi Mi 6 running 8.0.0, added "react-native-camera": "^1.2.0" to dependencies with RN 0.55.4.
{"bounds":[{"y":"682.5","x":"838.5"},{"y":"690.0","x":"465.0"},{"y":"291.0","x":"469.5"},{"y":"364.0","x":"796.75"}],"type":"QR_CODE","data":"http://1qr.fr/whb0","target":864}"

@hoanghaihuy is this still an issue?


implementations: Reference the CNI as a Linux network hook

Based on @philips' post.  Container-ID injection would take a
wrapping shell instance or some such (e.g., see here), but I
imagine config authors can figure that out (or just write an
alternative wrapper script that extracts the container ID from stdin's
state JSON on its own).

LGTM

Not against the change but there is literally nothing in this pr or the script that would tell me how to use it with an OCI container.  Its like a having a link to some random script saying that it could be used as a hook.

On Thu, Dec 17, 2015 at 10:53:04AM -0800, Michael Crosby wrote:

Not against the change but there is literally nothing in this pr or
the script that would tell me how to use it with an OCI container.
Its like a having a link to some random script saying that it could
be used as a hook.

In the absence of a runtime that is compatible with v0.1.0 (currently
our only release) of this spec, providing detailed examples seemed
premature ;).  As it stands this PR is just to help discovery,
pointing folks upstream to CNI docs and over to our hook docs for the
details.
If we added a detailed example, would you prefer it to be in this
file?  Upstream in the CNI repository?  Somewhere else?

I think maybe a simple example or link can be given at the first, then we can enrich it step by step with the feedback from OCI community.

lets put examples on the wiki, until we formalize patterns like this
https://github.com/opencontainers/specs/wiki

Honestly, lets put tangential examples like this in the wiki for now.


Anatomy load data from settings

Changes

Anatomy object load data from settings
Templates and Roots can't be self contain object, must be related to Anatomy object
Templates and Roots can't save data
Anatomy can be used as dictionary to get anatomy data (only get)

should not be used for "templates" and "roots"

environment variable prefix for roots was changed from PYPE_ROOT to PYPE_PROJECT_ROOT
removed keep_updated attribute (never used)
disabled Anatomy creation in prepare project action (as it's not possible to do that same way)

this is really hard to test when it's based of 3.0/refactor. I tried copying to develop adding to API and testing in there, however that starts throwing many errors. for example it is still using config in the imports

for example it is still using config in the imports

Because config contain usefull functions, it's was not just get_presets :)


RFC: Create documentation for REPL aliases

Checklist

Please ensure the following tasks are completed before submitting a feature request.

[x] Read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.
[x] The issue name begins with RFC:.

Description

Description of the feature request.

This RFC proposes to create a different version of the docs for the REPL usage of stdlib. Instead of the namespace-oriented (and thus tree-based) organization of the docs, the sidebar menu of the REPL docs could be organized along the objects the respective functions are attached to (identified by their alias).  For each function, we could create special README.md documentation files tailored around interactive usage.
Related Issues

Does this feature request have any related issues?

No.
Questions

Any questions for reviewers?

Any comments on the implementation details provided below? Any problems which need to be resolved in order to proceed?
Other open question:

The repl.txt files contain documentation for the parameters and return values of each function. Which of these (if any) should be included in the documentation? It seems to me that the return value description could be included at the beginning of the ##### Notes section?
Where should the tooling live to turn a repl.txt file into a README.md for the website documentation?
What other tooling do we need?

Other

Any other information relevant to this feature request? This may include screenshots, references, sample output, and/or implementation notes.

We need tooling for generating the documentation for the alias version of the functions. This could be based on the repl.txt files, which are already specifically tailored for describing how to use the respective functions int he REPL environment.
However, I would propose to merge parts from both the README.md and repl.txt files:

We could keep the intro section from the README.md files, as it provides useful context for the function. In contrast to usage in a command line, where real estate is more limited, I do not see a disadvantage from keeping it for the docs on the website
We would generate the usage section from the repl.txt docs. Specifically, we would need a script which performs the following steps:

take the function signature and add #### as a prefix to create heading.
take the first line of the description and insert under the signature heading.
take the examples for that signature and add a code block.
if a signature has options, add the following line: “The function accepts the following options :”
take the option fields and map to a Markdown list, along with the option descriptions
If a signature has an extended description, we’d add a ##### Notes section with each line in the extended description mapped to a Markdown list element.

I propose not including the examples section from the main README.md files. Sometimes, the examples are rather long or include for-loops etc., which are not representative of REPL usage and might be rather cumbersome to execute.
For packages that contain multiple exported functions (e.g. an additional factory method), we would need to have multiple signature headings inside the usage section.

We could keep the intro section from the README.md files, as it provides useful context for the function. In contrast to usage in a command line, where real estate is more limited, I do not see a disadvantage from keeping it for the docs on the website

Agreed.

take the function signature and add #### as a prefix to create heading.

We'll need to ensure proper escaping. E.g., \[.

If a signature has an extended description, we’d add a ##### Notes section with each line in the extended description mapped to a Markdown list element.

Agreed. This makes sense, except it would not be each "line", but each "item", which may span multiple lines and include multiple sentences. Further, we'll have to account for "special" cases, where we've included lists (in which case, we need to generate a nested list) or used indentation to add an equation or something similar. Handling the extended description in a robust manner will be the trickiest aspect of README generation.

I propose not including the examples section from the main README.md files. Sometimes, the examples are rather long or include for-loops etc., which are not representative of REPL usage and might be rather cumbersome to execute.

Agreed. We should not copy over the Examples section from the main README files.

For packages that contain multiple exported functions (e.g. an additional factory method), we would need to have multiple signature headings inside the usage section.

Agreed.

The repl.txt files contain documentation for the parameters and return values of each function. Which of these (if any) should be included in the documentation? It seems to me that the return value description could be included at the beginning of the ##### Notes section?

Yeah, this could be tricky. When writing repl.txt files, I have often included extended comments regarding parameters and return values in the respective descriptions. We could...
# alias

<insert intro from README if present>

#### alias( x, \[options,] y )

This is the main description.

``javascript
<insert code examples>
``

The function has the following parameters:

-   **x**: `<type>` this is the lowercased first letter description. If includes `Default:` then the value which follows should be surrounded by backticks.
-   **options**: `<Object>` function options description.
-   **options.foo**: `<number>` description for first option.
-   **options.bar**: `<string>` description for second option.
-   **y**: `<boolean>` parameter description.

The function returns:

-   **result**: `<Object>` this is the lowercased first letter return value description.
-   **result.beep**: `<number>` if the result value is an option with documented properties, then these would follow.

##### Notes

-   First item of extended description (this may span multiple lines and sentences)
-   Second item of extended description (this may span multiple lines and sentences)

* * *

#### alias.factory( \[options] )

This is the main description.

``javascript
<insert example code>
``

The method has the following parameters:

<insert parameters>

The method returns:

<insert results>

##### Notes

-    <insert items from extended description>

* * *

## References

<insert references if they are present>

* * *

## See Also

<insert related hyperlinked aliases>

Where should the tooling live to turn a repl.txt file into a README.md?

https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/_tools/repl-txt

For example, @stdlib/_tools/repl-txt/to-markdown. This tool would take a repl.txt string and convert it to Markdown. The CLI would either read from stdin or accept a file name from which to read a repl.txt file.
Once this tool is written, we can add additional abstractions (i.e., tools) for converting multiple files or working with globs.
Questions
Lastly, we'll want to think about how we'll present aliases in the side menu, given that the namespace is flat and we don't have a natural means for grouping based on alias alone. One idea would be to keep the same top-level namespaces and on expansion show the aliases which originate from that namespace. For example, @stdlib/math/base/special/sin would map, in the side menu to
math
  |- base.sin
  |- base.tan

This would at least allow users to collapse categories. We could allow further segmentation with
math
  |- base
       |- sin
       |- tan
  |- sin
  |- tan

Hence, allowing base aliases under a particular category to be collapsed/expanded.
Thoughts?

@Planeshifter Now that the website is updated, we could revisit this. 😃


Enter amount currency selection button update enhancement

Suggest changing the currency selection button on found on all of the "Enter Amount" pages.

I did not realize I could switch the currency between CAD and NAV at first.
Suggest having a button kind of like this to emphasize that the balance can be switched between currency type:

or (have the selected currency highlighted in purple)

I has considering this one myself as well. Took me a bit to realise that you had to click it to change, it wasn't obvious enough for the end users.

done


npm package error

the md-data-table.js in the package get from npm registry is error, in this line of code:
isPositive(self.total) ? Math.ceil(self.total / (isPositive(self.limit) ? 1 : self.limit)) : 1;
the right on should be:
isPositive(self.total) ? Math.ceil(self.total / (isPositive(self.limit) ? self.limit : 1)) : 1;

I fixed this not to long ago mdTablePagination.js#L65 but I overwrote the last tag so I think npm's cache is stale. Let me just go ahead and release another version.

Okay I just published v0.10.5 to npm.

it's ok now,thanks.


Connection state metrics for dockerized agent and host networking

Output of the info page
====================
Collector (v 5.22.3)
====================

  Status date: 2018-05-15 05:16:49 (1s ago)
  Pid: 6095
  Platform: Linux-4.14.32-coreos-x86_64-with
  Python Version: 2.7.14, 64bit
  Logs: <stderr>, /opt/datadog-agent/logs/collector.log

  Clocks
  ======

    NTP offset: 0.0011 s
    System UTC time: 2018-05-15 05:16:51.565257

  Paths
  =====

    conf.d: /opt/datadog-agent/agent/conf.d
    checks.d: /opt/datadog-agent/agent/checks.d

  Hostnames
  =========

    ec2-hostname: ip-10-0-2-200.ec2.internal
    local-ipv4: <IP_ADDRESS>
    local-hostname: ip-10-0-2-200.ec2.internal
    socket-hostname: ip-10-0-2-200.ec2.internal
    public-hostname: ec2-34-229-87-92.compute-1.amazonaws.com
    hostname: i-0de44ea41cc34c069
    instance-id: i-0de44ea41cc34c069
    public-ipv4: <IP_ADDRESS>
    socket-fqdn: <IP_ADDRESS>

  Checks
  ======

    linux_proc_extras (1.0.0)
    -------------------------
      - instance #0 [ERROR]: 'get_subprocess_output expected output but had none.'
      - Collected 6 metrics, 0 events & 0 service checks

    network (1.4.0)
    ---------------
      - instance #0 [WARNING]
          Warning: Cannot collect connection state: currently with a custom /proc path: /host/proc/1
      - Collected 20 metrics, 0 events & 0 service checks

    ntp (1.0.0)
    -----------
      - Collected 0 metrics, 0 events & 0 service checks

    cassandra_nodetool (0.1.1)
    --------------------------
      - instance #0 [OK]
      - Collected 16 metrics, 0 events & 3 service checks

    consul (1.3.0)
    --------------
      - instance #0 [OK]
      - Collected 1 metric, 0 events & 0 service checks

    disk (1.1.0)
    ------------
      - instance #0 [OK]
      - Collected 34 metrics, 0 events & 0 service checks

    docker_daemon (1.8.0)
    ---------------------
      - instance #0 [OK]
      - Collected 29 metrics, 0 events & 1 service check

    cassandra (5.22.3)
    ------------------
      - instance #cassandra-localhost-7199 [WARNING] collected 350 metrics
          Warning: Number of returned metrics is too high for instance: cassandra-localhost-7199. Please read http://docs.datadoghq.com/integrations/java/ or get in touch with Datadog Support for more details. Truncating to 350 metrics.
      - Collected 350 metrics, 0 events & 0 service checks

  Emitters
  ========

    - http_emitter [OK]

====================
Dogstatsd (v 5.22.3)
====================

  Status date: 2018-05-15 05:16:41 (9s ago)
  Pid: 6093
  Platform: Linux-4.14.32-coreos-x86_64-with
  Python Version: 2.7.14, 64bit
  Logs: <stderr>, /opt/datadog-agent/logs/dogstatsd.log

  Flush count: 147
  Packet Count: 64202
  Packets per second: 56.6
  Metric count: 420
  Event count: 0
  Service check count: 0

====================
Forwarder (v 5.22.3)
====================

  Status date: 2018-05-15 05:16:51 (0s ago)
  Pid: 6094
  Platform: Linux-4.14.32-coreos-x86_64-with
  Python Version: 2.7.14, 64bit
  Logs: <stderr>, /opt/datadog-agent/logs/forwarder.log

  Queue Size: 7704 bytes
  Queue Length: 3
  Flush Count: 498
  Transactions received: 404
  Transactions flushed: 401
  Transactions rejected: 0
  API Key Status: API Key is valid

Additional environment details (Operating System, Cloud provider, etc):
CoreOS 1688.5.3 running on AWS
Steps to reproduce the issue:

Build a docker image based off the latest alpine image with the following network.yaml check configuration built-in:

init_config:

instances:
  - collect_connection_state: true
    excluded_interfaces:
      - lo
      - lo0
      - docker0
    # Ignore Docker's virtual interfaces:
    excluded_interface_re: veth*

Run the datadog agent container with the following mounts:
-v /var/run/docker.sock:/var/run/docker.sock -v /proc/:/host/proc/:ro -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro -v /etc/passwd:/etc/passwd:ro
Run docker exec -it datadog /opt/datadog-agent/bin/agent info

Describe the results you received:
The network check fails to capture some host network metrics.
Describe the results you expected:
The network check should work as it did in previous versions of the agent.
Additional information you deem important (e.g. issue happens only occasionally):
This is the same issue as #1131. I don't believe the solution provided in that issue was correct. The problem occurs due to a combination of issues.
First, the solution in #1131 suggested setting the procfs_path in process.yaml. However, not only is that deprecated, it won't actually work. The check will ignore any value of procfs_path that is different from the agent config.
The suggested solution also mentions overriding procfs_path for the network check. However, the network check does not read a procfs_path from its init_conf. It only honors the procfs_path from the agent config.
Also, since the procfs_path is now an agent-wide setting, it seems problematic to override it to a value that only fixes one check. Instead, the warning should be ignorable when host networking is used in a container.

I would happily submit a PR to fix the issue, but the best fix is not entirely evident.
Some options are:

A new config option could be introduced that forces the connection state checks to occur
Allow overriding procfs_path at the check level
Somehow detect that host networking is being used and problem the correct logic implicitly

@jalaziz Sorry for the late answer here, but did you try to set the procfs_path directly in the datadog.conf.example as here ? (on agent 6: here
In this kind of matters don't hesitate to send us a support case along with opening the github issue

@antoinepouille Sorry for the late response myself. I was out of town and forgot to respond when I got back.
Seeing the procfs_path in the datadog.conf (or via the docker environment variable) file works fine, but then connection state metrics fail to work. Basically, the procfs_path can only be set such that the process checks work or the network connection state checks work, but not both. However, using docker and host networking, it should be possible to support both.
The advice from #1131 suggested using the network check's procfs_path parameter, but that simply won't work as it is not a valid parameter to the network check. Setting it for the process check is also not an option as the parameter is ignored if it doesn't match the procfs_path in datadog.conf. Finally, the whole idea of setting procfs_path for individual checks was deprecated long ago.
I'm happy to help submit a PR to fix this, but I wanted some direction from DataDog employees on which option from those outlined above (or any new options) they'd prefer.

@jalaziz Thanks for describing all this. Indeed, we'll probably need to update the checks so that this is made possible. I'll communicate this to our team managing agent integrations so that we can evaluate this.

@antoinepouille Any update on this? Happy to contribute a fix if there's a general consensus on the correct approach.

Using the following docker-compose and Dockerfile I got data for the system.net.tcp4.[opening|listening|established|...] metrices.
The main key point here is that the environment variable DD_PROCFS_PATH is set to /proc which is by default /host/proc in a dockerized environment, the network_mode is set to host and that the relevant tools like ss and netstat are installed. The last one is the reason I needed a custom Dockerfile.
The package iptools installs ss and net-tools installs netstat.
Without the Dockerfile or the (ss and netstat) command, I got the error Error collecting connection stats. (see https://github.com/DataDog/integrations-core/blob/master/network/datadog_checks/network/network.py#L363).
Dockerfile:
FROM datadog/agent:6.9.0

RUN apt-get update && apt-get install -y iproute2 net-tools

docker-compose.yaml:
version: '2'
services:
  datadog:
    build: .
    container_name: dd-agent
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /proc/:/host/proc/:ro
      - /sys/fs/cgroup/:/host/sys/fs/cgroup:ro
      - /mnt/asset/:/mnt/asset:ro
      - /:/mnt/root_partition:ro
      - ./conf.d:/conf.d:ro
    environment:
      - DD_LOG_LEVEL=warning
      - DD_API_KEY=12345
      - SD_BACKEND=docker
      - NON_LOCAL_TRAFFIC=false
      - DD_APM_ENABLED=true
      - DD_PROCFS_PATH=/proc
    network_mode: host
    restart: always
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
        max-file: "3"

I'm not quite sure if network.d/conf.yaml and/or process.d/conf.yaml is relevant, but here is my config:
conf.d/network.d/conf.yaml
init_config:
  procfs_path: /proc

instances:
    # Network check only supports one configured instance
  - collect_connection_state: true # set to true to collect TCP connection state metrics, e.g. SYN_SENT, ESTABLISHED
    excluded_interfaces: # the check will collect metrics on all other interfaces
      - lo
      - lo0
# ignore any network interface matching the given regex:
#   excluded_interface_re: eth1.*

conf.d/process.d/conf.yaml
init_config:
  procfs_path: /proc


Floating Windows Background Color Different from v1 to v2

Description
In v1, floating windows (e.g. as generated with Nui Popup) had their own background color (bg_float), distinct from the global background color (bg)

in v2, floating windows use bg0. If I set that, and dim_inactive is true, I'll get the same bg color in inactive windows.

This is also relevant to lsp signature help, hover, whichkey tables, etc.
Behavior
Expected behavior
Rather, I'd like to keep my background for dim_inactive and for status bars, lualine, etc, but specify a background color for floating windows only.
Screenshots
see above
Configuration
  nightfox.setup {
    options = {
      dim_inactive = true,
      modules = {
        native_lsp = true,
        treesitter = true,
        whichkey = true,
      },
    },
    palettes = {
      duskfox = {
        bg1 = "#000000",
        bg0 = "#010101",
        -- I'd prefer this for floating windows, but not for `dim_inactive`
        -- bg0 = "#1d1d2b",
        bg3 = "#121820", -- 55% darkened from stock
        sel0 = "#131b24", -- 55% darkened from stock
      },
    },
  }

Reproduce

run with minimal_init.lua
invoke which key (e.g. press c in normal mode)
note that the which-key binding table shares a background colour with the main buffer

minimal_init.lua
-- `minimal_init.lua` used for reproducible configuration
-- Open with `nvim --clean -u minimal_init.lua`

local is_windows = vim.fn.has("win32") == 1
local function join(...)
  local sep = is_windows and "\\" or "/"
  return table.concat({ ... }, sep)
end

local root_tmp = is_windows and os.getenv("TEMP") or "/tmp"
local site_path = join(root_tmp, "nvim", "site")
local pack_path = join(site_path, "pack")
local install_path = join(pack_path, "packer", "start", "packer.nvim")
local compile_path = join(install_path, "plugin", "packer_compiled.lua")
vim.opt.packpath = site_path

local function load_plugins()
  local packer = require("packer")
  local use = packer.use
  packer.reset()
  packer.init({ compile_path = compile_path, package_root = pack_path })

  use("wbthomason/packer.nvim")
  use("EdenEast/nightfox.nvim")
  -- ADD PLUGINS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE

  -- this could be any plugin which uses floating buffers, or even native lsp e.g. hover
  -- simply installing which key was the easiest way to write a minimal repro
  use("folke/which-key.nvim")

  packer.install()
end

_G.load_config = function()

  -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
  require("nightfox").setup({
    options = {
      dim_inactive = true,
      modules = {
        native_lsp = true,
        treesitter = true,
        whichkey = true,
      },
    },
    palettes = {
      duskfox = {
        bg1 = "#000000",
        bg0 = "#010101",
        -- I'd prefer this for floating windows, but not for `dim_inactive`
        -- bg0 = "#1d1d2b",
        bg3 = "#121820", -- 55% darkened from stock
        sel0 = "#131b24", -- 55% darkened from stock
      },
    },
  })

  require'which-key'.setup()

  vim.cmd("colorscheme duskfox")
end

if vim.fn.isdirectory(install_path) == 0 then
  vim.fn.system({ "git", "clone", "--depth=1", "https://github.com/wbthomason/packer.nvim", install_path })
end
load_plugins()
vim.cmd([[autocmd User PackerComplete ++once echo "Ready!" | lua load_config()]])

Additional info / context
NVIM v0.7.0
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by brew@BigSur

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.7.0/share/nvim"

Run :checkhealth for more info

From my understanding you would like to have float and inactive color different. Looking at your config there is no real difference between #000000 and #010101  but if you are looking for something all dim_inactive does is set NormalNC to bg0. You can change this value to be something else.
Now that #138 landed, you can define values for all styles. This change also allows you to create your own palette and spec values to be used in groups. An example of this would be something like:
require("nightfox").setup({
  palettes = {
    duskfox = {
      bg1 = "#000000",
      bg0 = "#1d1d2b", -- alt backgrounds (floats)
      bg3 = "#121820", -- 55% darkened from stock
      sel0 = "#131b24", -- 55% darkened from stock
    },
  },
  specs = {
    all = {
      inactive = "bg0", -- Default value for other styles
    },
    duskfox = {
      inactive = "#090909", -- A value that I can tell the difference
    },
  },
  groups = {
    NormalNC = { fg = "fg1", bg = "inactive" },
  },
})

Thanks that's p. good


Feature / Tags

Codecov Report

Merging #87 (63b2da5) into master (e323a23) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #87      +/-   ##
============================================
+ Coverage     99.66%   99.69%   +0.03%
- Complexity      721      789      +68
============================================
  Files           122      131       +9
  Lines          2096     2303     +207
============================================
+ Hits           2089     2296     +207
  Misses            7        7

Impacted Files
Coverage Δ

app/src/Controller/Tags/TagsController.php
100.00% <ø> (ø)

app/src/View/UserView.php
100.00% <ø> (ø)

app/src/View/WalletView.php
100.00% <ø> (ø)

app/src/View/WalletsView.php
100.00% <ø> (ø)

app/src/Controller/Tags/ChargesController.php
100.00% <100.00%> (ø)

app/src/Controller/Tags/CommonController.php
100.00% <100.00%> (ø)

...c/Controller/Wallets/Charges/ChargesController.php
100.00% <100.00%> (ø)

app/src/Repository/ChargeRepository.php
100.00% <100.00%> (ø)

app/src/Service/Filter/Filter.php
100.00% <100.00%> (ø)

app/src/Service/Filter/FilterType.php
100.00% <100.00%> (ø)

... and 8 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


close producer when kafka-producer-actor terminates

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.10 :tada:

Comparison is base (73ed185) 59.77% compared to head (6cb7560) 59.87%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #360      +/-   ##
==========================================
+ Coverage   59.77%   59.87%   +0.10%
==========================================
  Files         152      152
  Lines        3254     3255       +1
  Branches       92      108      +16
==========================================
+ Hits         1945     1949       +4
+ Misses       1309     1306       -3

Impacted Files
Coverage Δ

.../surge/internal/kafka/KafkaProducerActorImpl.scala
77.70% <100.00%> (+0.37%)
:arrow_up:

... and 3 files with indirect coverage changes

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


Add README instructions for polyfilling atob

Description
With atob not being available in platforms such as react-native, we are adding readme instructions for polyfilling it.
References
#241
Checklist

[x] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[x] All active GitHub checks for tests, formatting, and security are passing
[x] The correct base branch is being used, if not the default branch

Anybody tried this? Because I tried and looks it don't works.

'core-js/actual/atob' also doesn't works
In both cases error is:
Maximum call stack size exceeded (native stack depth), js engine: hermes

What else polyfill can I try?

Anybody tried this? Because I tried and looks it doesn't works.

I have not tied running this code, as I don't have a React Native project set up. @hrastnik are you experiencing a similar issue?

I've tried it and had the same results. At the end I fixed it like this:
Add the package core-js-pure
yarn add core-js-pure

or
npm install core-js-pure

Then add this code somewhere in the app (like index.js).
import atob from "core-js-pure/stable/atob";
import btoa from "core-js-pure/stable/btoa";

global.atob = atob;
global.btoa = btoa;

This seems to be specific to react-native, I assume it does not work well with how core-js detects the global here: https://github.com/zloirock/core-js/blob/master/packages/core-js/internals/global.js#L7-L15
Based on my testing, on React Native, it would use globalThis, while it seems like you want global as per comment above.
I will update this PR .

@Bardiamist Are you by any chance using MobX, and decoding the token inside a getter/computed?
I did some experiments and noticed everything works as expected when I use a plain string and decode the jwt, but since I use MobX, and I've decoded the token inside a computed function. I'm guessing the atob somehow accesses or writes something on the original string which causes an infinite render loop.
So, after some consideration I've ended up using the base-64 package since it works well and it's a smaller package than core-js-pure.
Here's my final polyFill
import { encode, decode } from "base-64";

global.atob = decode;
global.btoa = encode;

I don't use MobX.
base-64 works.
Also possible to exctract polyfill from https://github.com/auth0/jwt-decode/blob/14b61ecc2c6e46c2f70f86ccb9a3fd7cf72cfbf4/lib/atob.js

I have not been able to reproduce the issues folks in this thread are having in regards to core-js not working in React Native, specifically importing core-js/stable/atob in Hermes.
I set up Android Studio and set up my phone for development, I then followed the instructions for setting up a React Native development environment:
npx create-expo-app AwesomeProject
cd AwesomeProject
npm install core-js jwt-decode
npm run android

I then added the following code to the App.js file:
import "core-js/stable/atob";

const message = atob("SGVsbG8sIHdvcmxk");
console.log(message); // "Hello, world"

I can confirm the message shows up as expected, and does not cause any issues, and that this code breaks as expected when removing the import of core-js. Also expanding this code to use jwt-decode does not seem to make a difference:
import "core-js/stable/atob";
import { jwtDecode } from "jwt-decode"

const token = "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmb28iOiJiYXIiLCJleHAiOjEzOTMyODY4OTMsImlhdCI6MTM5MzI2ODg5M30.4-iaDojEVl0pJQMjrbM1EzUIfAZgsbK_kgnVyVxFSVo";
const decoded = jwtDecode(token);

console.log(decoded); // { "exp":<PHONE_NUMBER>, "foo": "bar", "iat":<PHONE_NUMBER> }

This code runs perfectly fine, I am not seeing issues here. @Bardiamist @hrastnik are you able to reproduce the issue in a minimal example like this? Perhaps you are running outdated dependencies, and this is a bug that has since been fixed, that might explain why I cannot reproduce this.

'base-64' package LGTM, I'll use it

Just be aware that base-64 has not been maintained since October 2020. It probably doesn't matter for such a small dependency, but still.

Function looks similar with used before https://github.com/auth0/jwt-decode/blob/14b61ecc2c6e46c2f70f86ccb9a3fd7cf72cfbf4/lib/atob.js

@Bardiamist @hrastnik are you able to reproduce the issue in a minimal example like this?

Its difficult, I don't know where is problem. App is completely broken if add import 'core-js/stable/atob'; even if don't call jwtDecode.

It's don't metter because import 'core-js/stable/atob'; completely breaks something in the app.
import "core-js/stable/atob";

const message = atob("SGVsbG8sIHdvcmxk");
console.log(message); // "Hello, world"

and
import "core-js/stable/atob";
import { jwtDecode } from "jwt-decode"

const token = "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmb28iOiJiYXIiLCJleHAiOjEzOTMyODY4OTMsImlhdCI6MTM5MzI2ODg5M30.4-iaDojEVl0pJQMjrbM1EzUIfAZgsbK_kgnVyVxFSVo";
const decoded = jwtDecode(token);

console.log(decoded); // { "exp":<PHONE_NUMBER>, "foo": "bar", "iat":<PHONE_NUMBER> }

works without errors

I'll add a minimal reproducible example.

Here's a working example:
import { AppRegistry } from "react-native";
import { name as appName } from "./app.json";
import { jwtDecode } from "jwt-decode";
import { Text, SafeAreaView } from "react-native";
import "core-js/stable/atob";
import "core-js/stable/btoa";

const state = {
  token:
    "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
  get decoded() {
    return jwtDecode(this.token);
  },
  get decodedAsString() {
    return JSON.stringify(this.decoded);
  },
};

export const App = function App() {
  return (
    <SafeAreaView style={{ flex: 1, justifyContent: "center" }}>
      <Text style={{ color: "#000000" }}>{state.decodedAsString}</Text>
    </SafeAreaView>
  );
};

AppRegistry.registerComponent(appName, () => App);

...which stops working once you make the state object observable using mobx:
import { AppRegistry } from "react-native";
import { name as appName } from "./app.json";
import { jwtDecode } from "jwt-decode";
import { observable } from "mobx";
import { Text, SafeAreaView } from "react-native";
import "core-js/stable/atob";
import "core-js/stable/btoa";

const state = observable({
  token:
    "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
  get decoded() {
    return jwtDecode(this.token);
  },
  get decodedAsString() {
    return JSON.stringify(this.decoded);
  },
});

export const App = function App() {
  return (
    <SafeAreaView style={{ flex: 1, justifyContent: "center" }}>
      <Text style={{ color: "#000000" }}>{state.decodedAsString}</Text>
    </SafeAreaView>
  );
};

AppRegistry.registerComponent(appName, () => App);

This could also be the case with other similar proxy/getter based state management solutions like valtio (https://github.com/pmndrs/valtio), but I haven't tried it.

This could also be the case with other similar proxy/getter based state management solutions like valtio

I also thought that import 'core-js/stable/atob'; breaks redux but not sure.
@reduxjs/toolkit, proxy-memoize, @react-native-firebase uses Proxy.

I think it has to do with core js overwriting/modifying toString method

core-js package is big ~15MB

core-js package is big ~15MB

Does all of that get included if you only import core-js/stable/atob? React Native doesn't do Tree Shaking?

It does look like not to be an issue with jwt-decode.
If i understand correctly, corejs' stable atob works but not when combined with mobx, which again is not something we can do anything about and something you want to look into on the RNA/ mobx / corejs side.
Additionally, there are other polyfills or you can even use our old atob and copy it in your project if needed.

@frederikprijck Using base-64 package to polyfill atob works without issue even with MobX.
import { encode, decode } from "base-64";
global.atob = decode;
global.btoa = encode;

Additionally, the package is quite small which is nice for reducing download times on the CI.
IMO, it would be nice if this code snippet is listed on the Github page for jwt-decode as it will probably avoid some headaches for RN devs in the future.

If i understand correctly, corejs' stable atob works but not when combined with mobx
I don't use mobix, I can't detect that exatly broken when import import 'core-js/stable/atob'; maybe @reduxjs/toolkit and more.

Would be good if you will recommend best solution in the README.

After some investigation, I've found it's a known issue with CoreJS on React Native:
https://github.com/zloirock/core-js/issues/1237

I am still not able to reproduce the issues in this thread, even adding MobX to the equation. Here is the code I am running:
import "core-js/stable/atob";
import { jwtDecode } from "jwt-decode";
import { observable } from "mobx";
import { SafeAreaView, Text } from "react-native";

const state = observable({
  token: "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
  get decoded() {
    return jwtDecode(this.token);
  },
  get decodedAsString() {
    return JSON.stringify(this.decoded);
  },
});

export default function App() {
  return (
    <SafeAreaView style={{ flex: 1, justifyContent: "center" }}>
      <Text style={{ color: "#000000" }}>{state.decodedAsString}</Text>
    </SafeAreaView>
  );
}

@Bardiamist @hrastnik does the comment in https://github.com/facebook/hermes/issues/135#issuecomment-808817771 perhaps solve the issue for you? Or the other suggestions in that thread.
If anyone is interested in making this issue reproducible, perhaps download my project and see if you can modify it so it breaks.

Good news, the Hermes team has decided to implement this functionality, so polyfilling these APIs should no longer be needed in the future for React Native (see https://github.com/facebook/hermes/issues/1178#issuecomment-1813460137).


Add Profile: + Adding

Profile Submission

Profile Category
Please select one or more categories for your profile:

[ ] Badge 🎖
[x] Minimalistic ✨
[ ] Dynamic 🔄
[ ] Icons 🎯
[ ] Backgrounds 😎
[ ] GIFS 🖼
[ ] Game Mode 🚀
[ ] Code 👨💻

Next Steps
Once you've filled out the information, please comment below:
'@all-contributors please add @somnath0904 for review'

https://github.com/all-contributors please add @SOMNATH0904 for review

@all-contributors please add @SOMNATH0904 for review


Fix nodegit dependency

This is a new issue which combines these issues:

https://github.com/kimmobrunfeldt/git-hours/issues/14
https://github.com/kimmobrunfeldt/git-hours/issues/11

Workaround for the nodegit issues is to use node version 0.12x. You can do it either by using nvm or following the vagrant installation guide in readme.
The real solution is to update nodegit dependency or open up a new issue to nodegit repo if it isn't working with a new node release. I have now tested to update nodegit to version 0.8.0. It seems to work with node 5.0.0 but there's a new bug which makes it useless: https://github.com/nodegit/nodegit/issues/866. Let's wait until nodegit gets their releases together.

Now released in https://github.com/kimmobrunfeldt/git-hours/releases/tag/1.2.0


1.11.2 (2020-08-28T21:19Z)

added "Documentation" button
added "Report a Bug" button
added AGR batch .FBX export

@Devostate,d shouldn't @darkhandrob be credtied for it in https://github.com/advancedfx/contrib ?


shared_preferences blocks the debugging [web]

I am working on flutter web project which has to save some key values in local storage. On inspecting, i found that shared_preferences package of version ^0.5.6 supports the web functionality. I could do the integration without any hiccups. But i cannot run the debug of project which fails with the below message
Steps to Reproduce

add dependency shared_preferences: ^0.5.6 on puspec.yaml
try to start the app in debug mode (ctrl+f5 in vscode)
you cannot start the debugging.

Logs
> Launching lib/main.dart on Chrome in debug mode...
Incompatible options with current running build daemon.
Please stop other flutter_tool instances running in this directory before starting a new instance with these options.
Exited (sigterm)

Output of flutter doctor -v
[✓] Flutter (Channel beta, v1.12.13+hotfix.6, on Linux, locale en_GB.UTF-8)
    • Flutter version 1.12.13+hotfix.6 at /home/athul/flutter
    • Framework revision 18cd7a3601 (2 weeks ago), 2019-12-11 06:35:39 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/athul/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /home/athul/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[!] Android Studio (version 3.5)
    • Android Studio at /home/athul/android-studio
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.41.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.7.1

[✓] Connected device (2 available)
    • Chrome     • chrome     • web-javascript • Google Chrome 79.0.3945.88
    • Web Server • web-server • web-javascript • Flutter Tools

Update: issue got fixed by rebooting the machine. Thanks!


Rename and clean Zeppelin initialization action

Sorry to delete authorship, I couldn't figure out how to set the rename threshold on github.

No worries on my end. Customers > vanity. :)
LGTM. If you want me to merge and sync, LMK.


A monitor scale change was detected pop up screen, couldn't close this screen.

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I run a program for 4 days using Spyder (3.10). The results are done and I want to save the final output data. However, I encountered an pop-up screen that "A monitor scale change was detected. We recommend restarting Spyder to ensure that it is properly displayed. If you don't want to do that, please be sure to activate the option". I couldn't close this pop-up screen.The only way to close this is to click on the Restart now.
My question is that after my program finishes, is there anyway that I could access my final result variable from the anaconda prompt or somewhere else? I am desperately need the final output. As long as I could have access to this final result variable, I am good. I am afraid that I will lose my variables from here since I have deadlines.
Thank you very much for your help and I really appreciate it.
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

It is Spyder (Python 3.10).

Hey @xywust2014, thanks for reporting and sorry for the inconvenience. You said:

My question is that after my program finishes, is there anyway that I could access my final result variable from the anaconda prompt or somewhere else? I am desperately need the final output.

Unfortunately, it's not possible, sorry.
Please be sure to update to our latest version (5.4.3 if you're in Anaconda or 5.5.1 otherwise) because this problem should be fixed in it. To update you need to close Spyder, open the Anaconda Prompt or a system terminal, and run there the commands mentioned in our documentation.


[Wiki] Add wiki explaining the assembly loading mechanism

https://github.com/RSuter/NSwag/wiki/Assembly-loading


Rename the validity and checkValidity APIs

😯 Problem to Solve
We were inspired by the HTML 5 constraint validation API to make validity and checkValidity methods for the Table and that pattern is being leveraged by additional controls such as wafermap and rich-text.
While that pattern seems mostly successful it seems like it was the wrong idea to use the exact names of the HTML 5 Validity API. We should rename our API surface area to avoid conflicts as our Contributing guidelines suggest.
This will become a blocking issue once we have a Form Associated control that is complex enough to need validation apis. None of the controls currently listed are form participating (though richtext certainly could be updated to do that) but it would be better to rename sooner rather than later.
💁 Proposed Solution
Switch to the names:

controlValidiity and checkControlValidity

Alternatives considered:

componentValidity and checkComponentValidity (verbose)
nimbleValidity and checkNimbleValidity (too nimble specific, would be nice to have a name flexible to spright without api break)
have inconsistent APIs between form participating components and non-form participating components. A component changing to form participating would have a breaking API change.

📋 Tasks

[ ] This is a subtask of the feature. (It can be converted to an issue.)

@rajsite and I decided on elementValidity and checkElementValidity. This is ready for someone to work on.


Video width inconsistencency x264

I just encoded a video from normal 1920x1080, down to supposedly 720x430,
all my software says it is 720x430, like VLC, Mediainfo, properties in Windows and so on, but when played on a Windows machine, it plays back in 785x430, I have tried encoding the same both in <IP_ADDRESS>, <IP_ADDRESS>, and stable 1.7, same results.
It plays back fine on a Mac. Tried different media players, VLC, Windows Media Player and Meida Player Classic, also 3 different computers running different versions of Windows, in addition to the Mac.
I decided to try and encode it in an old version of Stax I had saved, <IP_ADDRESS>, and there it worked perfectly.
I can provide all kind of logs and proof if needed... It has me stumped what causes this...

Yeah, sorry about this ...
After 6+ hours of testing, it was of course just the --sar command that somehow had found its way into my script ...


Feature: add og:title metadata as alternative title

Summary
Open Graph Tags is a mechanism for a website to provide metadata when an URL is shared through social media. I encountered some rare cases that the webpage's <title> tag is set through Javascript dynamically at page load, but an og:title metadata is present.
This PR make use of open graph tags as a fallback for grabbing page title (also has the potential to gather other metadatas). It extend the title extractor with HTMLParser, not breaking any existing behaviour. The <title> tag content is still the highest priority.
I did not extend the existing regex expression because the HTML is complicated and contains many special cases that cannot be handled easily by regex. In examples below, two attributes in <meta> is in different order and only the second one has <xxx /> form. I didn't even try to parse it through regex. 💫
examples:
link2: Blogspot
<meta content="分析台湾可取icatch DVR固件" property="og:title">

link1: WeChat Platform ,
<meta property="og:title" content="Cocos2dx-js 逆向分析乘凉" />

Changes these areas

[ ] Bugfixes
[x] Feature behavior
[ ] Command line interface
[ ] Configuration options
[ ] Internal architecture
[ ] Archived data layout on disk

Thanks for the PR!
Taking the og tag was part of the plan, so this is aligned with it. The code looks good to me. Can you maybe add some test in tests/test_extractors.py? We have a mock server and some templates in there you can use to fetch a title. You could add a small template that has an og tag instead to test that case, and have yet another one with no title tag for the case where it returns None.
Other than the missing tests, this looks great. @pirate can you have a look at it?

I like it, can it fallback to the regex if the HTML parser bails out?  The regex was nice because it also worked on HTML that wasn't valid or had errors, not sure how HTMLParser will handle something like <html/><head <title>abc for example.

The regex was nice because it also worked on HTML that wasn't valid or had errors

Oh... in that case failover to regex is essential. my fault. I'll add the code back later.
Saying the tests, is there any documentation for setting up the test environment? I may missed something. If i could spin it up, I may also help with writing testcase.

The test dependencies are in the setup.py. You should be able to install it with pip install -e .[dev]. After you have pytest and bottle, you just need to run pytest -s to run the whole test suite. You can check the github actions file, it is configured and run in there.

regex fallback added: f727ece

I will add the tests in another PR.


Docs

The docs are awful in the latest versions. There used to be a very easy to use and follow API guide that has since vanished.
Now we get these plain .md files that basically explain nothing. I can't even figure out how to stop my app from using the hash location in the URL.
Please consider upgrading your documentation.

Hey @DannyiCracked we work hard on making the React Router great. And is definitely sad to hear the feedback like yours. Let me know which parts need more focus and what they are lacking. I'd try to fix it or I'd be happy if you send the PR with your suggested changes.
Going back to your "question":

I can't even figure out how to stop my app from using the hash location in the URL

You should use Browser History to get rid off # in the URL


Hello Spring application started

Hi all! I created a basic "Hello World" level setup to get started on our project. Can someone please review and merge with main?

Looks good!


west.yml: Update NXP HAL to pull in latest USB driver

Update the SDK USB driver to 2.13.1.
Fixes https://github.com/zephyrproject-rtos/zephyr/issues/57269

cc @hakehuang


Fixes #796 Adding provision to have a result processor for workers

We want to do additional processing on the incoming and outgoing variables of the worker before they can go into/come from SaaS. Adding the provision to have a custom result processor.
This PR also contains review comments fixes from previous closed PR (https://github.com/camunda-community-hub/spring-zeebe/pull/797). I closed the other one because of the wrong account was used mistakenly for commits.
closes #796

Hi @jonathanlukas. Could you please check this one. I closed the other PR (https://github.com/camunda-community-hub/spring-zeebe/pull/797) because I mistakely used a wrong account to push the code. This PR also contains the fixes for your review comments.

Jonathan's review comments from the other PR.
_Thank you for your PR.
I really like the proposed change. However, I would like to reiterate on some details:

ResultEnricher is a opinionated term, I would prefer ResultProcessor
I would split up the ResultProcessor into 2 parts (this approach is equal to the ParameterResolver):
-the actual ResultProcessor that is able to map the result

a ResultProcessorStrategy which allows for finding the right ResultProcessor for a @JobWorker function based on the available information

please add unit tests to verify the desired behaviour_

@hem-verma there are formatting issues with the PR. Please make sure to run mvn clean package locally and push the resulting changes to be aligned the formatting

One question. When the release version will be created with this change which we can use?

I see that the feature is already closed. :)

@hem-verma this feature is released with 8.6 of the client.
Also, this feature will be proposed to be added to the official SDK to be used there as well.

Thanks @jonathanlukas. Good to know about the official SDK because I also asked the same question to Sean recently.


Accept authenticated proxy params via Scala CLI config file

The proxy documentation now says something about configuring the proxy via  scala-cli config httpProxy.user _encoded_user_. I could not find anything about config in the documentation:  https://scala-cli.virtuslab.org/docs/reference/proxy-authentication/#coursier-or-scala-cli-configuration-files
Where is this 'scala-cli config' information stored?


Does not install

after cloning the repo, running npm install:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/webpack
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/extract-text-webpack-plugin
npm ERR!   dev<EMAIL_ADDRESS>from the root project

I tried --force, but that just results in a broken install, building or running doesn't work.
I'm running this on a Mac,
npm version: 8.3.0
node version: v17.3.1

The repo is out of date and not maintained. But you can extrapolate it for your needs.


Filesync

Filesync PR

This change is

Looks like this is failing a number of CI checks

This is failing python formatting check: https://travis-ci.com/github/whamcloud/integrated-manager-for-lustre/jobs/390551199

This is failing a number of checks.

Ok, it's failing due to #2270 . @beevans please rebase on latest master.

Test pass in https://build.whamcloud.com/job/manager-for-lustre/2407/


MODELIX-520 Make concept alias available in generated source code

I would like to have a more type safe way of accessing the "concept properties" by generating a separate field for each property instead of this generic metaInfo field.
The generated code should then look like this:
interface C_BaseConcept {
    val alias: String? get() = null
    companion object : C_BaseConcept {
        val alias: String? = null
    }
}
interface C_MyConcept {
    val alias: String? = "myConcept"
    companion object : C_MyConcept {
        val alias: String? = null
    }
}

This requires to first analyze all concepts and collect the defined concept properties (they can then be stored in ProcessedLanguageSet) to then generate them into the whole concept hierarchy.

If we want to do it like that, we will probably need to generate interfaces for each metaInfo attribute e.g.
interface IHasAlias {
   val alias: String?
}

So that we can access this meta info generically across concepts.

:tada: This PR is included in version 3.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


HP: Implement GroupId -> Registry config lookup

For the hidden path server we need a module that looks up Registries for a list of GroupIds.
Input: List of GroupIds, List of config files, localIA
Output: map[GroupIds]->Registry (more or less addr.IA)
The lookup should return an optimal mapping of GroupIds to Registries.
Where optimal means:

Whenever the local IA is a Registry for the GroupId it should be the local IA.
For all other GroupIds a minimal amount of Registries should be returned.

This is HPS internal functionality and should be under hidden_path_srv/internal.

This sounds like a variant of the set cover problem which is NP-complete. It is often solved with a polynomial-time greedy algorithm which approximates an optimal solution.
Another thought: Would it make sense to map from Registry to a set of GroupIds instead (i.e. map[Registry] -> []GroupIds)? Then we could directly pack the hp_seg_request for every Registry.

I guess we can relax the minimal amount requirement. In the end we just need something that takes a list of GroupIDs as input and produces a set of registries where we need to send requests as output. So your proposal makes sense.


Configuration for Rspec should go to rails_helper.rb not spec_helper.rb ?

Looks like Rspec doesn't know about PublicActivity when it is called from spec_helper.rb but it seems to work when it's required and called from within rails_helper.rb
  # PublicActivity off
  require 'public_activity/testing'
  PublicActivity.enabled = false

PublicActivity doesn't load itself in test environments. It's programmer's responsibility to require it, usually this is taken care of by Bundler.

I think that we're misunderstood. It does load when you use require ... in rails_helper.rb. Your README says to put that code into spec_helper.rb
It seems that you need to update README file.

Ah! I understand now, yeah you are correct :)

I submitted a PR for this tiny fix: #303


build: remove netlify CLI from node_modules and related scripts

We now only have a single package which uses Netlify, docs-website, and since our usage of Netlify builds is dramatically lower right now (since we aren't changing code for xstate-wallet, web3torrent, etc on each commit) we can probably ask Netlify to build this stuff for us on their servers instead of on CircleCI.
Also, the netlify-cli package is huge, by far our largest dependency.

Will want to update Netlify config

https://app.netlify.com/sites/nitro-protocol/settings/deploys


Link is not working

Issue description
The "Watch video" link in this page goes to 404 not found page.

Why are you looking at such ancient documents?

Why are you looking at such ancient documents?

Result of a Google search. Maybe the page shouldn't be there anymore if it's so ancient...


[MsTeams / Power Automate] [Including image/png;base64 Image Uri breaking Post Adaptive Card to Teams Channel]

I've been using a ms forms -> power automate -> post adaptive card to teams for a few months now. no issues up until a few days ago, no changes on our end and now the only error message I am getting is a "Http request failed: the content was not a valid JSON." during the post adaptive card to teams channel stage.

The card renders perfectly (no errors) in the adaptive card designer

Up until this issue started, it rendered fantastic in teams

If I pull the two instances out of the card json, processing completes without issue, but of course this is reduced functionality.
       {             "type": "Image",             "url": "data:image/png;base64,@{outputs('Compose_2')}"         }
and
                        {                             "type": "Image",                             "style": "person",                             "url": "data:image/png;base64,@{outputs('Compose')}",                             "size": "Small"                         }
I hope this is the right place to post this, it's not easy to find support on this stuff.  Thanks for all the hard work you guys do on this stuff.
and finally here's the card json incase you guys can find something I'm missing (but one last time -- I'm sure this isnt anything I did on my side)
{     "type": "AdaptiveCard",     "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",     "version": "1.2",     "body": [         {             "type": "TextBlock",             "size": "large",             "weight": "bolder",             "text": "Service Bulletin for @{body('Get_response_details')?['rbb64344f8df54902857ceebcbe7a5a03']}"         },         {             "type": "ColumnSet",             "columns": [                 {                     "type": "Column",                     "items": [                         {                             "type": "Image",                             "style": "person",                             "url": "data:image/png;base64,@{outputs('Compose')}",                             "size": "Small"                         }                     ],                     "width": "auto"                 },                 {                     "type": "Column",                     "items": [                         {                             "type": "TextBlock",                             "weight": "bolder",                             "text": "@{body('Get_user_profile_(V2)')?['displayName']}",                             "wrap": true,                             "size": "small"                         },                         {                             "type": "TextBlock",                             "spacing": "none",                             "text": "Posted {{DATE(@{variables('createdUtc')}, SHORT)}} at {{TIME(@{variables('createdUtc')})}}",                             "isSubtle": true,                             "wrap": true,                             "size": "small",                             "weight": "lighter"                         }                     ],                     "width": "stretch"                 }             ]         },         {             "type": "FactSet",             "facts": [                 {                     "title": "Client name:",                     "value": "@{body('Get_response_details')?['rbb64344f8df54902857ceebcbe7a5a03']}"                 },                 {                     "title": "Location(s):",                     "value": "@{body('Get_response_details')?['rec1cfbeb91704283a429ffca57288c5d']}"                 },                 {                     "title": "Timeframe:",                     "value": "@{body('Get_response_details')?['r97c751307fef499590b7ca3b53ba47db']}"                 },                 {                     "title": "Services affected:",                     "value": "@{outputs('ServicesAffectedCatchForwardSlash')}"                 },                 {                     "title": "Support team:",                     "value": "@{body('Get_response_details')?['r1fdf4105a7b5421d8c33bed633d79896']}"                 },                 {                     "title": "Bulletin expires:",                     "value": "@{body('Get_response_details')?['r3dd06956adf442889bff75b1bb984a2e']}"                 }             ]         },         {             "type": "TextBlock",             "text": "@{outputs('MainDescriptionCatchForwardSlash')}",             "wrap": true         },         {             "type": "Image",             "url": "data:image/png;base64,@{outputs('Compose_2')}"         }     ] }

@dblyth-msft can you help diagnose this?
@ffulkerth thanks for sharing your Flow definition, but we also need the Runtime values to help diagnose. Can you provide those? Also one thing to check, sometimes we see this because an image is too large. Can you tell us how big that image you're trying to render is?

@ffulkerth All we need is the flow run URL from the portal (ie. https://flow.microsoft.com/manage/environments/flows/abc/runs/xyz)

@ffulkerth All we need is the flow run URL from the portal (ie. https://flow.microsoft.com/manage/environments/flows/abc/runs/xyz)

Last successful run Aug 10th (with the image data included)
https://us.flow.microsoft.com/manage/environments/Default-3d9bab48-5f52-4b7d-a481-771eae5e6ed4/flows/57d2ddbd-9760-4b56-9295-cecd016fd482/runs/08586045371593193107505850600CU127
Three samples of failures.  The oldest (3rd on the list - aug15th) was when it started failing.

https://us.flow.microsoft.com/manage/environments/Default-3d9bab48-5f52-4b7d-a481-771eae5e6ed4/flows/shared/57d2ddbd-9760-4b56-9295-cecd016fd482/runs/08586040319248004734551582517CU43

https://us.flow.microsoft.com/manage/environments/Default-3d9bab48-5f52-4b7d-a481-771eae5e6ed4/flows/shared/57d2ddbd-9760-4b56-9295-cecd016fd482/runs/08586040325903382222177287736CU126

https://us.flow.microsoft.com/manage/environments/Default-3d9bab48-5f52-4b7d-a481-771eae5e6ed4/flows/57d2ddbd-9760-4b56-9295-cecd016fd482/runs/08586040578119472134606999542CU27

I have attached the footer image (42.9KB) and the other one is just the data provided by "get user photo v2"

Thanks again guys.  I do appreciate this.


Unable to change order of camera or add

Great program!
Question
2x2 trying to change the order of a camera it will accept writing it in the "layout.conf.default" but doesn't actually change in the display.
Then tried for a 5 camera setup 2 top three bottom I couldn't get that to display as well.
So I started from scratch reformatting reinstalling, started with the 2x2 again this time I got one camera to display and a second camera trying to flash in.
all this is new to me so I'm sure i may be missing something simple.
The help is appreciated!

Make sure you're editing the working file in /etc/displaycameras/ folder.
If that's not the problem, post a redacted version of your layout file.
On Mon, Aug 10, 2020, 4:45 PM sm2b<EMAIL_ADDRESS>wrote:

Great program!
Question
2x2 trying to change the order of a camera it will accept writing it in
the "layout.conf.default" but doesn't actually change in the display.
Then tried for a 5 camera setup 2 top three bottom I couldn't get that to
display as well.
So I started from scratch reformatting reinstalling, started with the 2x2
again this time I got one camera to display and a second camera trying to
flash in.
all this is new to me so I'm sure i may be missing something simple.
The help is appreciated!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/71, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKJBWK27UKHGUHUONODSABL7JANCNFSM4P2KWT6Q
.

Confirm working in /etc/displaycameras folder, did not touch the "layout.conf.default".  Also I am pushing this to a 4k tv and it works 2x2 but can't change order.  Also if I change the resolution as in the file it breaks. I wasnt able to get the 5 camera (2 on top 3 bottom) to work at all.
thanks!
Original 2x2 redacted.txt

Unlese you change something the system almost always uses the default
layout file.
On Mon, Aug 10, 2020, 4:45 PM sm2b<EMAIL_ADDRESS>wrote:

Great program!
Question
2x2 trying to change the order of a camera it will accept writing it in
the "layout.conf.default" but doesn't actually change in the display.
Then tried for a 5 camera setup 2 top three bottom I couldn't get that to
display as well.
So I started from scratch reformatting reinstalling, started with the 2x2
again this time I got one camera to display and a second camera trying to
flash in.
all this is new to me so I'm sure i may be missing something simple.
The help is appreciated!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/71, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKJBWK27UKHGUHUONODSABL7JANCNFSM4P2KWT6Q
.


Add HaRe

Addresses https://github.com/RefactoringTools/HaRe/issues/8 cc @wolftune
Note: The elisp should still move to MELPA

@alanz There are test failures: https://gist.github.com/bergmark/05d1fb372b5413d363df so I'll disable HaRe until I know how to proceed: fix tests? does the stackage bulider need something installed? should we ignore the test suite?

Up to line 107 is a normal compile of HaRe, which happens without problems.
The problem starts when the test suite is run, because HaRe makes use of
ghc-mod as a library. This needs to install cabal-helper  in
~/.ghc-mod, and the one error is because it cannot write to it in the
test environment.
The other is because the syb library is missing, but may be bogus due to
the write permission problem.
@DanielG, do you have anything to add here?
On Tue, Oct 20, 2015 at 8:48 PM, Adam Bergmark<EMAIL_ADDRESS>wrote:

@alanz https://github.com/alanz There are test failures:
https://gist.github.com/bergmark/05d1fb372b5413d363df so I'll disable
HaRe until I know how to proceed: fix tests? does the stackage bulider need
something installed? should we ignore the test suite?
—
Reply to this email directly or view it on GitHub
https://github.com/fpco/stackage/pull/906#issuecomment-149664641.

What is the status of this at present? Has anything changed with recent stack and/or ghc-mod?

Stack isn't involved in this process, so changes there wouldn't be relevant. I'm unaware of any changes in stackage-curator that would be related to this.

I just noticed it is in the nightly and lts-4, so the testing must have got
bypassed, no further action required
On Wed, Jan 6, 2016 at 5:55 PM, Michael Snoyman<EMAIL_ADDRESS>wrote:

Stack isn't involved in this process, so changes there wouldn't be
relevant. I'm unaware of any changes in stackage-curator that would be
related to this.
—
Reply to this email directly or view it on GitHub
https://github.com/fpco/stackage/pull/906#issuecomment-169366622.


App sandbox issue when trying to upload the app build to app store connect

I am using agora_rtc_engine flutter package and trying to upload my app to app store connect and facing this issue.

You should enable the App Sandbox in your project if you need to distribute your APP to Mac App Store
https://developer.apple.com/documentation/security/app_sandbox?language=objc

Yes, I have done that in both DebugProfile.entitlements and Release.entitlements files.

Is it works or not?

No, If I remove the package it is working but not with the package. How can I fix this?

Same issue, any solutions for this?

Still waiting for this to publish my macos app. :/

Same issue here, also waiting for publishing to macos app.

By following the guide https://developer.apple.com/documentation/xcode/embedding-a-helper-tool-in-a-sandboxed-app?language=objc, maybe you can try the steps below but without testing:

Go to AgoraRtcWrapper.framework/Resources path

cd /The/path/to/your/flutter/project/macos/Pods/AgoraIrisRTC_macOS/AgoraRtcWrapper.framework/Resources

Create an entitlements file

/usr/libexec/PlistBuddy -c "Add :com.apple.security.app-sandbox bool true" "AgoraRtcScreenSharing.entitlements"
/usr/libexec/PlistBuddy -c "Add :com.apple.security.inherit bool true" AgoraRtcScreenSharing.entitlements

Sign the AgoraRtcScreenSharing

codesign -s - -i io.agora.iris.rtc.screensharing -o runtime --entitlements AgoraRtcScreenSharing.entitlements -f AgoraRtcScreenSharing

Then try to rebuild your APP see if works or not.

But for the disclaimer, I didn't test these steps cause my personal development account can't publish the APP to the APP store, so I can't verify twhether he steps work or not. And this is just a temporary solution.

I try to build our example and upload it to the Mac App Store, it failed with the AgoraRtcScreenSharing not signed error, run the following command to sign the AgoraRtcScreenSharing:
codesign -o runtime -f -v --timestamp --deep -s "YOUR CODE_SIGN_IDENTITY" /Users/workspace/Agora-Flutter-SDK/example/macos/Pods/AgoraIrisRTC_macOS/AgoraRtcWrapper.framework/Resources/AgoraRtcScreenSharing

Then process the archive follow, it works fine for the example.

I'm not very sure if there are any configs missing in your's project.

@littleGnAl Confirm it working, i can push the macos app to Testflight now. Thank you.


capture of erb content in a nested component not behaving as expected

I'm trying to build a component with a nested component, similar to the example on the homepage, though capturing multiple blocks of content in the nested one. A parent component with title, then a (collection of) nested component(s) which each do two captures in order to produce rows with 'left' and 'right' content.
What I'm finding is that in the nested component, the blocks of content I'm trying to capture are a) being written to the output before the component itself renders and then b) when rendered into the component, the content produced by an erb tag within that content is then missing.
Parent component:
class CardComponent < ApplicationComponent
  include Phlex::DeferredRender

  attr_accessor :title

  def template
    div(class: "overflow-hidden bg-white shadow sm:rounded-lg") do
      div(class: "px-4 py-5 sm:px-6") do
        h3(class: "text-base font-semibold leading-6 text-gray-900") do
          title
        end
      end

      div(class: "border-t border-gray-200 px-4 py-5 sm:p-0") do
        dl(class: "sm:divide-y sm:divide-gray-200") do
          rows.each do |row|
            render(row)
          end
        end
      end
    end
  end

  def add_row(...)
    rows << CardRowComponent.new(...)
  end

  def rows
    @rows ||= []
  end
end

Nested component:
class CardRowComponent < ApplicationComponent
  include Phlex::DeferredRender

  def template
    div(class: "py-4 sm:grid sm:grid-cols-3 sm:gap-4 sm:py-5 sm:px-6") do
      dt(class: "text-sm font-medium text-gray-500") do
        left
      end
      dd(class: "mt-1 text-sm text-gray-900 sm:col-span-2 sm:mt-0") do
        right
      end
    end
  end

  def left(&block)
    if block_given?
      @left = block
    else
      capture(&@left)
    end
  end

  def right(&block)
    if block_given?
      @right = block
    else
      capture(&@right)
    end
  end
end

Used in a typical Rails erb view (a fresh Rails 7 codebase):

  <%= render CardComponent.new do |card| %>
    <% card.title = 'Item details' %>

    <% card.add_row do |row| %>
      <% row.left do %>
        Length
      <% end %>
      <% row.right do %>
        <%= @vessel.length_ft %>ft
      <% end %>
    <% end %>
  <% end %>

Result, showing how the content in the left and right blocks have been rendered before the component (@vessel.length_ft = 27.0):

With markup:

  Length
  27.0ft

Item details

            Length

            ft

Thanks, loving my Phlex experience so far. 🙏

@jongilbraith I think I found a fix. Could you try this branch in your Gemfile?
gem "phlex-rails", git: "https://github.com/joeldrapper/phlex-rails.git", branch: "contagious-unbuffered"

Once I've written a test, I’ll try to ship this in a patch.

Phlex bumped 1.5.1 > 1.60 and all looks great now 👍

Also, you shouldn't use <%= for deferred render blocks since they are output when the containing component is rendered.

👍 thanks, will do

@jongilbraith I thought 0.8 required phlex 1.6 so I had to push a release quickly. 😅
I believe this issue is now fixed in 0.8.1 which is now released. I’ll write a test against regression now, but I tested it manually and it seems to work.

Brilliant, thanks for the quick resolution @joeldrapper, I'll pull in 0.8.1 and refit the views I built yesterday with the components I was working on before.
Looking forward to seeing how this codebase gets on with adopting components for the UI!

Awesome! Thanks for opening the issue.


Windows Terminal Shortcut in Quick Launch is incorrect.

Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce

Install Windows Terminal
Launch Windows Terminal
Pin Windows Terminal To Quick Launch
Click Windows Terminal in Quick Launch
Be sad

Expected behavior
Expect that the quick launch will pin the correct shortcut. Perhaps the shortcuts could be edited somehow
System information:

Windows version: windows 10 22h2
Cairo version: 4.370.35207
32-bit or 64-bit: 64-bit
In Cairo Settings > Advanced, is Cairo set as shell?:

Additional context
Windows terminal seems to be an odd-bird.  There is an executable called WindowsTerminal.exe which is ultimately what is run by the shortcuts in windows, or when you launch it through other means, however the only way to manually launch it is via the wt.exe executable.
It is weird.
Screenshots

Did you pin it to quick launch by right-clicking it on the taskbar?
If you instead add it via App Grabber you should see better results.


Support Linode Cloud API in Let's Encrypt Plugin

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
[x] When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
The Let's Encrypt plugin supports "Linode API" as a way of doing DNS-01 validation. However, this is the old API
which Linode is migrating away from in favour of its "Cloud API" aka Linode API v4.
acme.sh supports this API with --dns dns_linode_v4 option, so it's just a matter of setting up a suitable UI to
configure it.
Describe the solution you'd like
Extend Let's Encrypt plugin's UI to support Linode API v4.
Describe alternatives you've considered
Using the old Linode API. I'd prefer not to because it doesn't give enough access control.
Additional context
Add any other context or screenshots about the feature request here.

@jsgf I've seen that you've already made the required changes in your private fork. Could you please submit a pull-request with your changes?

@fraenki Yep, just working out how to test them first.

@jsgf Thanks for your contribution!


[Editor] (MacOS) crash when clicking "AssetBrowser"

Describe the bug
Open Prowl on MacOS
To Reproduce
Steps to reproduce the behavior:

Create a new Project and try to click on the AssetBrowser window
It crashes

Expected behavior
You should be able to browse assets and see little icons for each one.

o.0

Pretty sure we fixed this? Or did we not?

I click it, and prowl goes bye bye

@all-contributors
please add @PaperPrototype.

@all-contributors
please add @ for help with MacOS support.

https://github.com/all-contributors
please add @PaperPrototype for help with MacOS support.

@all-contributors
please add @PaperPrototype for help with MacOS support.

@ll-contributors
please add @PaperPrototype for platform

@all-contributors
please add @PaperPrototype for platform

@all-contributors
please add @PaperPrototype for platform

god damnit you stoopid bot


Update ark_survival_ascended.psm1 to fix ServerAdminPassword

Moved ?ServerAdminPassword to the end, to fix the error of incorrectly writing the admin password to GameSetting.ini

I noticed that issue. But since today I cannot reproduce it, I think it was fixed in the latest update.
Can you validate if you're still seeing this issue ?

resolved by ARK update.


[ci:component:github.com/gardener/logging:v0.36.1->v0.36.2]

*Release Notes:
Disable the parallel input processing of the `fluent-bit-to-loki` output plugin

The Sorted client does not leak promtail Loki clients anymore.

/assign @vlvasilev
/invite @vlvasilev

/close
new PR is opened


Use better name?

E.g. overview, in case you want to render an overview of items on other pages than the homepage?
https://github.com/follywolly/web-app-from-scratch-18-19/blob/129e3c7de7e32b32a2eef8e74dfca60315437b4b/src/js/modules/render.js#L6

This was just for purposes to make the basic router. All these routes will be refactored so this will be removed anyway

fair enough!


feat(minifier): implement calculations for NumberValue

#6419  👈
main

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

Join @7086cmd and the rest of your teammates on  Graphite

Merge activity

Oct 10, 7:48 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
Oct 10, 7:48 AM EDT: A user added this pull request to the Graphite merge queue.