US EPA AQI Updates

The US EPA has updated their "Technical Assistance Document for the Reporting of Daily Air Quality – the Air Quality
Index (AQI)" available here: https://document.airnow.gov/technical-assistance-document-for-the-reporting-of-daily-air-quailty.pdf.
This includes a new color blind friendly color scheme and additional guidance on computing US AQI.

added in a356bd4


calculate physical memory used on z/OS

Use the already existing uv_resident_set_size to retrieve the physical memory used by the process.

Codecov Report

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

@@          Coverage Diff           @@
##           master    #507   +/-   ##
======================================
  Coverage    60.8%   60.8%
======================================
  Files          49      49
  Lines        3215    3215
======================================
  Hits         1955    1955
  Misses       1260    1260

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 d702f6e...2de4f51. Read the comment docs.


App: HTML planes punchthrough broken

This is probably due to the post processing step not supporting a punch-through alpha strategy like we were using: https://local.webaverse.com/?src=.%2Fscenes%2Fclassroom.scn
Note that if you delete the classroom.glb (so you do not have any depth overwrite) then you can see the intended HTML page punches through the alpha:

The scene can be edited: https://github.com/webaverse/app/blob/master/scenes/classroom.scn

The way the punch-through alpha (used to) work is that not only do we use a CSS matrix to position the DOM node, but we also render the equivalent plane in the world and make sure it clears alpha.
Then the dom node goes undernerath the transparent canvas, with the hole perfectly punched though.
That was broken because something in our new post processing stack does not correctly pass through this alpha zero render.

Here is where we render the plane as well as manage the CSS matrix for this node: https://github.com/webaverse/metaversefile/blob/cf1021962fef13cd21c7680f864b7ea2ef7740d1/type_templates/html.js#L23

Solved


Draft of Detail 1997

Note that this includes an iecodebook approach to appending for the moment

completed draft 97 up to labor module (not including) but this will be a separate PR


SUS-701 Kick user on logout

This change should prevent a hack that is allowing chat users to become "unbannable",
see more: SUS-701
@mixth-sense

:+1:


Hi. I am new to Android. I just want to use mobile microphone to record wav audio and just find your repository. I ran it & it compiled successfully. But the problem is that the path you have used to store wav file is not actually having this file. Means i could not get the file, if i want to use that file for further processing. Note that i want to use this wav file for speech recognition purpose done in another device running on python. Any help would be more than welcome, as i am new bae.

Sorry but please use stackoverflow to ask question.


Validator "unjail" command not working [unsuppored sign mode SIGN_MODE_TEXTUAL): unauthorized]

Using okp4d 6.0.0:
build_tags: netgo,ledger
commit: 0830f530f0f1ff0cba56b2c852f2199d33ff6938
cosmos_sdk_version: v0.50.1
go: go version go1.21.4 linux/amd64
name: okp4d
server_name: okp4d
version: 6.0.0
Tried to unjail validator on okp4-drunemeton-1, but I get the following error:
okp@hostname:~$ okp4d tx slashing unjail --from <keyname> --chain-id "okp4-drunemeton-1" --trace
Enter keyring passphrase (attempt 1/3):
auth_info:
  fee:
    amount: []
    gas_limit: "200000"
    granter: ""
    payer: ""
  signer_infos: []
  tip: null
body:
  extension_options: []
  memo: ""
  messages:
  - '@type': /cosmos.slashing.v1beta1.MsgUnjail
    validator_addr: okp4valoper1pju9r03ywzd8s8tc0d3tkksgttemlheyqf9fqp
  non_critical_extension_options: []
  timeout_height: "0"
signatures: []
confirm transaction before signing and broadcasting [y/N]: y
code: 4
codespace: sdk
data: ""
events: []
gas_used: "0"
gas_wanted: "0"
height: "0"
info: ""
logs: []
raw_log: 'signature verification failed; please verify account number (10) and chain-id        <<<<<<<<<<<<<<<<<<<<<<<<<<<
  (okp4-drunemeton-1): (unsuppored sign mode SIGN_MODE_TEXTUAL): unauthorized'    <<<<<<<<<<<<<<<<<<<<<<<<<<<
timestamp: ""
tx: null
txhash: 5E4D0B7587B92D067308E7C2A8838F3D89D35735012A070412459767368ACC09

After many unsuccessful retries, I found a similar behavior on Babylon chain: https://github.com/cosmos/cosmos-sdk/issues/19165
I downloaded older version 5.0.0 and TX was successful, using same command input:
okp@hostname:~$ ./okp4d-5.0.0-linux-amd64 tx slashing unjail --from <keyname> --chain-id "okp4-drunemeton-1"
Enter keyring passphrase (attempt 1/3):
auth_info:
  fee:
    amount: []
    gas_limit: "200000"
    granter: ""
    payer: ""
  signer_infos: []
  tip: null
body:
  extension_options: []
  memo: ""
  messages:
  - '@type': /cosmos.slashing.v1beta1.MsgUnjail
    validator_addr: okp4valoper1pju9r03ywzd8s8tc0d3tkksgttemlheyqf9fqp
  non_critical_extension_options: []
  timeout_height: "0"
signatures: []
confirm transaction before signing and broadcasting [y/N]: y
code: 0
codespace: ""
data: ""
events: []
gas_used: "0"
gas_wanted: "0"
height: "0"
info: ""
logs: []
raw_log: ""
timestamp: ""
tx: null
txhash: D9199D7B6E5913BBF2031DDBA0B1AA13FBECED4BE52B9C3BE69893103AF9DF00

Thanks for pointing this out. From what I understand, this issue is clearly related to the upgrade to version 0.50 of the Cosmos SDK and is particularly attributable to AutoCli. By following the fix applied by Babylon chain (see: https://github.com/babylonchain/babylon/pull/435/files), we should be able to resolve the issue.

:tada: This issue has been resolved in version 7.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bicep - Add GitOps deployment

⚠  PLEASE MERGE https://github.com/microsoft/nubesgen-actions/pull/1 and create v0.3.0 tag before merging this PR (and test the whole result)

See #213


Don't use the hadd built-in function in the basic:barrier test

It is not strictly required and tested by the integer_ops suite.
This change enables passing the barrier test with clvk+clspv ahead
of adding support for hadd in clspv.
Signed-off-by: Kévin Petit<EMAIL_ADDRESS>

Do we really need to check workarounds into the trunk?  Why can't this stay in a branch?

The reason I'm proposing it for inclusion instead of keeping it on my stack of workarounds is that it gets us closer to unit-type testing. The built-in function under test is barrier here.

Seems like converting existing conformance tests to be more unit-like is an independent project.  Are we meaning to start that here?  The conformance tests are already pretty simplistic and their occasional use of features not strictly being tested has been valuable.

Seems like converting existing conformance tests to be more unit-like is an independent project.

Yes and no. I don't see any of us doing this just for the sake of it. I think it's more likely to happen gradually as part of work towards other goals.

Are we meaning to start that here?

Why not? :)

The conformance tests are already pretty simplistic and their occasional use of features not strictly being tested has been valuable.

Agree, I've found that to be valuable as well in some cases. We do need to be careful with this but as long as we check that there is adequate coverage otherwise (which I believe is the case here), I think we shouldn't be afraid.


feat(LinearAlgebra): replace Submodule.restrictBilinear by BilinForm.restrict

As discussed in this thread, there were 3 different definitions for the restriction of a bilinear form to a subspace. This PR deletes the definition Submodule.restrictBilinear, and replaces all its occurrences by the LinearMap.BilinForm.restrict one.
Surprisingly, I ran into issues with BilinForm.flip when performing this refactoring (if someone can explain ...). After quite some amount of fiddling, I ended up with what I think is a good enough solution (see commit). In particular, I had to change the ker_restrict_eq_of_codisjoint lemma to another file which seems better suited now.
Also, I did not change LinearMap.BilinForm.restrict to be an abbrev (instead of def) of LinearMap.domRestrict₁₂, because GitHub Actions complained about the @[simps! apply] annotation in this case.

Also, I did not change LinearMap.BilinForm.restrict to be an abbrev (instead of def) of LinearMap.domRestrict₁₂, because GitHub Actions complained about the @[simps! apply] annotation in this case.

I think you could replace this with @[simp] or maybe just remove it altogether; but fine to leave that to a separate PR.


Refactor pcli transaction viewing to be an extension trait on TransactionView

Is your feature request related to a problem? Please describe.
pcli has existing code to render transactions, which uses comfy_table to render data in a terminal.  This code was written before we even had transaction views, so it assumes that the full viewing key is present.  But the design we're aiming at is that the TransactionView is supposed to be a self-contained, pre-computed view of the transaction.
Describe the solution you'd like
To reflect this, we could refactor the transaction viewing code in pcli into a method on TransactionView in an extension trait:
// in pcli/src/transaction_view_ext.rs
pub trait TransactionViewExt {
    /// Render this transaction view on stdout.
    fn render_terminal(&self);
}

impl TransactionViewExt for TransactionView {
    fn render_terminal(&self) {
        // use comfy_table to render transaction contents
    }
}

This would be similar, in spirit, to the TransactionView => HTML pipeline we're planning for the web extension.  We could adapt the existing code, but it's not necessary to stick to it, we can do whatever format we want.

I recently came across a post on Bluesky from @aubrika , one of your team members, mentioning that you're hiring Rust engineers. I wanted to take a look at Penumbra and get familiar with what it is and how it works. This seemed like as good a jumping off point as any.
Will be pushing the code to a GitHub repo later today, but wanted to post this to get some feedback. It's more or less "playing with the fonts and margins", but I've added a visualization for encrypted ActionViews that is a bit more human friendly. Might be a bit loud though.

Anyway, let me know what you think!

That looks really cool! I think the colors are a bit loud, but maybe in black and white it would convey the "this data is encrypted" part really well...

Another cool idea for the aesthetics would be to use a random string of braille characters, which kind of has this look to it:
⠨⡳⠡⡳⡸⢠⠌⢊⠋⣢⣶⣑⣕⠃⢻⠜⢮⡬⢌⠎⣴⣓⣿⡮⣈⣽⠓⣹⡷⡜⡤⢘

I agree. It also dodges the case where the foreground_color and background_color happen to be the same color.
Also like the idea of using braille characters to make it feel like a paper receipt.
Another question I have, is if this method could ever be called with less than a FullViewingKey? If so, it could be made generic over different key types.

There shouldn't need to be any key in use at all -- the purpose of the TransactionView is to have a pre-decrypted, pre-interpreted view of the transaction contents from a particular perspective, so that no keys or other data are necessary to interpret it. (See our blog post for details).
However, the current transaction code in pcli was written before we created the TransactionView, so it still makes use of viewing keys. Once this change is made, however, the viewing process would look like:

Get a TransactionView from the view service (which will use the FVK and other data internally)
Render the pre-computed view using the new TransactionViewExt code.

Ah, I see. I didn't realise the TransactionView was "always decrypted" in that sense. That simplifies things.

To put it another way: if there's data in the TransactionView that can only be understood with extra key material, we'd consider that a bug, for instance https://github.com/penumbra-zone/penumbra/issues/2780

Pushed here: https://github.com/jackmcasey/penumbra/tree/2312
Will open a PR when I have the rest of the ActionViews implemented.

I believe this is now ready for review: #3240


ABAP File Format Review for API Catalog

ABAP File Format Review for API Catalog

@schneidermic0 : Please review ABAP File Format for API Catalog


Replace obsolete EFO IDs with new MONDO equivalents

A user has pointed out some EFO terms are showing the prefix "obsolete" in the Search UI. This is because they have been made obsolete in EFO in favour of equivalent terms from MONDO (see EFO ticket https://github.com/EBISPOT/efo/issues/1750).
Task:
Replace the following EFO IDs with their MONDO equivalents. The trait name can remain unchanged.
cancer:
http://www.ebi.ac.uk/efo/EFO_0000311 --> http://purl.obolibrary.org/obo/MONDO_0004992
coronary stenosis:
http://www.ebi.ac.uk/efo/EFO_1000882 --> http://purl.obolibrary.org/obo/MONDO_0006715,
glaucoma:
http://www.ebi.ac.uk/efo/EFO_0000516 --> http://purl.obolibrary.org/obo/MONDO_0005041
bipolar disorder:
http://www.ebi.ac.uk/efo/EFO_0000289 --> http://purl.obolibrary.org/obo/MONDO_0004985
systemic lupus erythematosus:
http://www.ebi.ac.uk/efo/EFO_0002690 --> http://purl.obolibrary.org/obo/MONDO_0007915
cognitive disorder:
http://www.ebi.ac.uk/efo/EFO_1001457 --> http://purl.obolibrary.org/obo/MONDO_0002039

mentioned in this ticket

To work on w/c 3rd Jan

Close after DR


Configured Dependabot (Fixes #532)

Fixes
Fixes #532 by @nimishbongale
Description
Checks in a .github/dependabot.yml for configuring the dependabot.
Technical details
Dependabot is now native to github, provides a handy automatic way of handling dependency upgrades.
Tests
Dependabot has been successfully configured in my fork.
Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

That's good to know, I didn't realize Dependabot was part of GitHub now. Thanks!

@aldenstpage It's a very recent update, but a great addition to incorporate! Must have for almost any repository. I have configured it for CC-vocabulary, planning on doing it for a few others as well!


Show copy link button when QR code is loaded

Changes

fix: Wait till qr code is loaded to show copy link button

Associated Issues
closes https://github.com/WalletConnect/web3modal/issues/1443

Yes was aware of that

LGTM ⚡
Causes a layout shift but I think it's still good since we have layout animation;
Screen.Recording.2023-12-15.at.16.00.43.mov

Yes was aware of that, but I think it is not disruptive or anything


Allow implicit cast for directionless args

I would like to propose allowing implicit cast for directionless method / function / constructor arguments, following the discussion made in #1312.
Regarding it, the current spec section 8.20 mentions that:

The calling convention is copy-in/copy-out (Section 6.8). For generic functions the type arguments can be explicitly specified in the function call. The compiler only inserts implicit casts for direction in arguments to methods or functions as described in Section 8.11. The types for all other arguments must match the parameter types exactly.

So as per the spec, we cannot apply implicit cast for directionless method / function / constructor arguments.
As a side note, directionless action arguments can be implicitly cast as per the spec since it mentions the following in section 6.8.1.

Actions can also be explicitly invoked using function call syntax, either from a control block or from another action. In this case, values for all action parameters must be supplied explicitly, including values for the directionless parameters. The directionless parameters in this case behave like in parameters.

So, like the case for action, I am proposing to allow implicit cast for directionless method / function / constructor arguments.
I believe it better reflects the use cases in the p4c test suite. Below is a drop-down list of tests that expect such a feature.

List of tests

extern-funcs-bmv2.p4
extern2.p4
gauntlet_extern_arguments_2.p4
gauntlet_hdr_in_value-bmv2.p4
issue1001-1-bmv2.p4
issue1001-bmv2.p4
issue1043-bmv2.p4
issue1334.p4
issue1642-bmv2.p4
issue1653-bmv2.p4
issue1653-complex-bmv2.p4
issue1660-bmv2.p4
issue1765-1-bmv2.p4
issue2648.p4
issue3246-1.p4
issue383-bmv2.p4
issue562-bmv2.p4
issue933-1.p4
named-arg1.p4
v1model-special-ops-bmv2.p4
bfd_offload.p4
calc-ebpf.p4
constructor_cast.p4
issue1006.p4
issue1097-2-bmv2.p4
issue1097-bmv2.p4
issue1814-1-bmv2.p4
issue1814-bmv2.p4
issue1958.p4
issue2844-enum.p4
issue298-bmv2.p4
issue4288.p4
issue754.p4
list7.p4
pr1363.p4
psa-action-profile1.p4
psa-action-profile3.p4
psa-action-profile4.p4
psa-basic-counter-bmv2.p4
psa-counter1.p4
psa-counter2.p4
psa-counter3.p4
psa-custom-type-counter-index.p4
psa-end-of-ingress-test-bmv2.p4
psa-example-dpdk-byte-alignment_1.p4
psa-example-dpdk-byte-alignment_2.p4
psa-example-dpdk-byte-alignment_3.p4
psa-example-dpdk-byte-alignment_5.p4
psa-example-dpdk-byte-alignment_6.p4
psa-example-dpdk-byte-alignment_7.p4
psa-example-dpdk-byte-alignment_8.p4
psa-example-dpdk-byte-alignment_9.p4
pse-example-dpdk-counter.p4
psa-example-dpdk-externs.p4
psa-example-dpdk-meter-execute-err.p4
psa-example-dpdk-meter.p4
psa-example-dpdk-meter1.p4
psa-example-dpdk-varbit-bmv2.p4
psa-meter1.p4
psa-meter3.p4
psa-meter7-bmv2.p4
psa-random.p4
psa-register-complex-bmv2.p4
psa-register-read-write-2-bmv2.p4
psa-register-read-write-bmv2.p4
psa-register1.p4
psa-register2.p4
psa-register3.p4
rcp.p4
rcp1.p4
register-serenum-bmv2.p4
simple-firewall_ubpf.p4
unused-counter-bmv2.p4
value-sets.p4

From LDWG: This is clarifying and making something more explicit that was implicit in the spec before. We have tests currently that have this assumption baked in, and p4c implements the behavior described in the change.


docs(ngClass): added known issue to documentation

PR of issue https://github.com/angular/angular.js/issues/16183
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs Update
What is the current behavior? (You can also link to an open issue here)
https://github.com/angular/angular.js/issues/16183
What is the new behavior (if this is a feature change)?
This is a docs update
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ *] Docs have been added / updated (for bug fixes / features)

Other information:

I signed it!

Where did you get the info that this is deprecated, causes memory leaks and is bad for performance? Only the latter is a valid point, although that depends on the complexity of the function.
It's also possible to use any kind of AngularJS expression in ngClass as long as the result is one of the 3 forms that are documented.

I think that adding this to the ngClass docs is not a good idea as this is also true for other directives, not only ngClass.

I'm going to close this issue because we haven't got required feedback. Feel free to reopen this issue if you can provide new feedback.


How to fix this ??

An unknown error occured
An unexpected error happened. If you want to help this error get fixed, please report it to the GitHub issue tracker. DO NOT SHARE YOUR PRIVATE KEY WITH ANYONE (begins with an S).
Your funds are safe and not affected by this error. This error is just a display error in StellarTerm.
Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
at removeChild (https://stellarterm.com/:23:460360)
at i (https://stellarterm.com/:23:407393)
at commitDeletion (https://stellarterm.com/:23:408938)
at t (https://stellarterm.com/:23:412915)
at E (https://stellarterm.com/:23:418591)
at w (https://stellarterm.com/:23:418292)
at h (https://stellarterm.com/:23:417421)
at p (https://stellarterm.com/:23:416811)
at Object.enqueueSetState (https://stellarterm.com/:23:391412)
at t.d.setState (https://stellarterm.com/:23:532272)
at https://stellarterm.com/:23:596044
in div
in div
in div
in Unknown
in t
in div
in t
in div
in t

google chrome!!

Can you give me the error output on the new version of StellarTerm? And also steps on how to recreate this. Thanks


Glitchy UI

Describe the bug
A clear and concise description of what the bug is.
The display looks like this:

The white boxes are me censoring the hardware and IP addresses
To Reproduce
Describe steps to reproduce the bug:
Open sniffnet 1.1.4 (installed via cargo) on a 1920x1080 resolution hi dpi screen with 150% scaling (Intel UHD Graphics 620; Win 11 latest)
Expected behavior
Show GUI properly
Screenshots
Already added
Desktop (please complete the following information):

OS: Windows
Browser NA
Version 1.1.4

Additional context
Add any other context about the problem here.
Ran the app with RUST_BACKTRACE=full and there were no error logs.

You can try running the app from the glow-renderer branch, which uses a different renderer and most of the times this solves the problem

@arnabanimesh can you please confirm that switching to the glow-renderer solves the problem?
Thanks in advance!

@GyulyVGC glow-renderer is working fine. It should be the default IMO.

I'm happy to know it's working well for you!
I think that wgpu has more compatibility in general though, and for this reason iced set it as default.


Add client codegen guide to docs

A section under 'Guides' was added to the docs, 'Generating code'. It covers updating the model from the Quick start guide to enable codegen, adding the client codegen plugin, and using the generated client. The example uses the TypeScript code generator.
A hyperlink target was also added to the implementations doc for the 'Client code generators' section to make it easier to refer to in the new guide.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I just started a guide on creating a code generator. Given it'll also be a new section, and I called my section "codegen", I'm wondering if this section could be something like, "using-codegen"?

I just started a guide on creating a code generator. Given it'll also be a new section, and I called my section "codegen", I'm wondering if this section could be something like, "using-codegen"?

This should only matter for clarity when developing the docs, and in the URLs right? Its a little verbose, but I feel like "creating-a-code-generator" would be a more descriptive name for a guide on creating a code generator. For me, "using-codegen" vs "generating-code" isn't a big semantic difference so I can change it if you are intent on keeping your's as just "codegen"

This should only matter for clarity when developing the docs, and in the URLs right? Its a little verbose, but I feel like "creating-a-code-generator" would be a more descriptive name for a guide on creating a code generator. For me, "using-codegen" vs "generating-code" isn't a big semantic difference so I can change it if you are intent on keeping your's as just "codegen"

I'll change the location of the docs I'm adding to something more specific. I think generating-code could be ambiguously interpreted as teaching someone how to write a generator rather than how to use a generator. I don't feel strongly about it though.

This should only matter for clarity when developing the docs, and in the URLs right? Its a little verbose, but I feel like "creating-a-code-generator" would be a more descriptive name for a guide on creating a code generator. For me, "using-codegen" vs "generating-code" isn't a big semantic difference so I can change it if you are intent on keeping your's as just "codegen"

I'll change the location of the docs I'm adding to something more specific. I think generating-code could be ambiguously interpreted as teaching someone how to write a generator rather than how to use a generator. I don't feel strongly about it though.

Ah I see what you mean, I agree using-codegen resolves that ambiguity.


Request: Add a command to access the Aurebesh key for user reference

Add a command the user can send for the bot to reply with the an Aurebesh key

Added in commit 1d37cede51bb3920e96209b866635278b4ca159b.
Possible future update: delete after a period of time?


base16 request.

This is more of a request than a bug. I love this theme, but.. I love the consistency of base16. Can you guys port this over to base16-shell? This would require base16-shell, base16-vim, vim-airline-themes changes, if you do.

I do not have time to do this, sorry :(. Contributions are more than welcome though, so if you want to give it a try, I would be happy to review :)

I'm gonna close this one @bytebeast as there was no contribution on it. Feel free to open a PR if you put something together :)

Here's one I just made. Feel free to contribute it or steal it or whatever.
scheme: "Gotham"
author: "Brett Jones (https://blockloop.io)"
base00: "0c1014"
base01: "11151c"
base02: "091f2e"
base03: "0a3749"
base04: "245361"
base05: "599cab"
base06: "99d1ce"
base07: "d3ebe9"
base08: "c23127"
base09: "d26937"
base0A: "edb443"
base0B: "33859E"
base0C: "2aa889"
base0D: "195466"
base0E: "888ca6"
base0F: "4e5166"

Thanks @whatyouhide  and @blockloop .  I packaged the above scheme in sboysel/base16-gotham-scheme.  Let me know if there is any issue with the attribution.


Release v1.27.0

Description of the change:
Release commit for 1.27.0
Motivation for the change:
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/lgtm


Update DefaultMQProducerImpl.java

Delete extra commas and format code
Make sure set the target branch to develop
What is the purpose of the change
Delete extra commas and format code
Brief changelog
Delete extra commas and format code
Verifying this change
Delete extra commas and format code
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Delete extra commas and format code


Show Python environments from the VS Code server

Version: 1.75.0-insider (user setup)
Commit: 1379f0375440df946adc62f7afb8375dd45d5adf
Date: 2023-01-17T05:21:07.217Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes
When connected to a VS Code server, I expect to see all the Python environments from the tunneled server (like remote SSH-ing). Instead, I see:

Steps to repro:

Start a code tunnel (code-insiders tunnel)
Open the URL in the browser and open an ipynb file
Click on the kernel picker. I would expect to be able to see and select my kernels on the the code server I'm connected. Since I didn't, my workaround was to start up a new Jupyter server from the integrated terminal (i.e., jupyter notebook --no-browser in the terminal and then copy the Jupyter server URL by going to the kernel picker -> Existing Jupyter Server).

cc\ @rebornix

When connected to a VS Code server, I expect to see all the Python environments from the tunneled serve

Are you able to see all of your Pythohn environments in here when using the python extensions Python: Select Interpreter command

Actually, no, I get this error:

I also just saw that the extension is stuck on loading...:

cc\ @luabud


Refocus on calandar after selecting event in ikhal

After pressing enter and focusing on an event it is not clear how to focus on a other day. Pressing 'left' works, but pressing 'h' doesn't while 'h' has the same function as left in other UI elements.

Fixed!


CH592 support?

Good day
Thank you for your hard work on making these flash tools. Any plans to support the CH592?

I have added support for the CH592, among others, to chprog. Since I do not have the chip myself, it is untested.

Awesome! Thank you, I tested it with a Weact CH592 and flashing a .bin file works flawlessly

Not sure if I should continue on this issue or open a new one, but when I flash my ch592 with chprog it seems to all work fine (chip id and flash verification succeed), but the firmware does not run. Also not after a power cycle.
When I flash this same fw with wchisp it does work, so it's definitely a flasher issue it seems.

Only .bin files work. It will flash the other types, but the firmware does not run.

Only .bin files work. It will flash the other types, but the firmware does not run.

Yes indeed, makes sense actually. I just did not read the instructions well enough (sorry for the noise).

Oh yes, when I have some time again, I will add support for .hex and .elf.

Adding .hex support will be great! So far when building in Mountriver I'm doing this in linux to convert the hex file into bin
 objcopy --input-target=ihex --output-target=binary source.hex target.bin


How can I add a new colormaker

I have a working CodePen that colors the residues based on machine learning probabilities from a CSV. I want to add this functionality as a colormaker available in examples.
I have extended colormaker similar to resname-colormaker.ts and colormakerRegistry.add the scheme. I also added the staging js file in the examples/scripts/color directory.
When I click on the file in the webapp, I get a console message THREE.COLOR: unknown color 'compvis' (the scheme id I assigned)
I noticed that my colormaker is not included in the ngl.dev.js file, and it is also missing from the build directory when I open Sources in chrome dev tools. But when I look in the build directory locally, the files are there.
Can anyone help me understand what I am missing that is preventing me from accessing my colormaker scheme?

Rollup is possibly ignoring the file as it isn't imported anywhere? You
could try importing it from the top level src/ngl.ts (registering it as a
scheme is a side effect of import)
On Fri, 23 Oct 2020, 22:06 Brad Alexander<EMAIL_ADDRESS>wrote:

I have a working CodePen that colors the residues based on machine
learning probabilities from a CSV. I want to add this functionality as a
colormaker available in examples.
I have extended colormaker similar to resname-colormaker.ts and
colormakerRegistry.add the scheme. I also added the staging js file in the
examples/scripts/color directory.
When I click on the file in the webapp, I get a console message
THREE.COLOR: unknown color 'compvis' (the scheme id I assigned)
I noticed that my colormaker is not included in the ngl.dev.js file, and
it is also missing from the build directory when I open Sources in chrome
dev tools. But when I look in the build directory locally, the files are
there.
Can anyone help me understand what I am missing that is preventing me from
accessing my colormaker scheme?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nglviewer/ngl/issues/805, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG33N5P7EKIHZYZI3TVJOTSMHV6HANCNFSM4S5BEQRQ
.

Ah yes! Forgot about that 🤦♂. Thanks! Now I just need to get the csv parser working.

Got it working! I found out autoLoad in loader-utils can be used as a CSV parser -- made things a lot easier. Now I need to add some user input options to the html page, and make a coloring gradient.
I also want to make a proxy for the CSV so when you hover over the residue it will tell you the probability, and what residue the neural net thinks should be there. I might have to ask a new question for that.


Jenkins hangs due to disk full

What would you like to be added:
auto clean-up disk space
Why is this needed:
improve efficiency.
Without this feature, how does the current module work：
do it manually
Components that may involve changes:
Jenkins

We have setup the auto cleanup on Jenkins, for both Jenkins nodes and PAI nodes.
In any case we found disk full issue again, will need to check it manually, and figure out the root cause.
There are two cases, and we have handled both:

Jenkins nodes disk full. We have set cleanup policy, will automatically clean data older than 5 days.
Pai nodes(node used for installing PAI) disk full. We cleanup each time after the job finished, the disk usage shouldn't full.

@hao1939 , thanks for the explanation. If you consider this case solved, please close this issue.

@hao1939
I think this case is stale image.

@mzmssg , thank you!
Docker images were kept for speeding up.
We now have cleaner, ideally cleaner would clean up stale images if there is not enough space.
So if we fix the cleaner, everything would be fine.

@hao1939, cleaner does not have image clean-up feature yet.

The speeding up is obviously, it's about 2x, so I suggest to keep the image cache.
From previously recording, it may takes 2-3 months before the disk full.
So what about put it on the DRI handbook, and take a manually check on CI/CD system when it happens again?
I like the idea of auto maintenance.
But if it's not frequently, manually check is acceptable, and we may figure out more problem via regularly diagnostic.

Could we move docker storage to /mnt?

@mzmssg, sure.

Yeah, have mounted the large disk to /var/lib/docker.

@hao1939
Might you forget to move the jenkins docker repo to the mounted disk. Jenkins failed again due to can't push image.

@mzmssg You are right. I will do that.

For jenkins disk usage:

jenkins master stores jobs data (log, metadata etc.) and workspaces (cloned repo). Jobs data is under ${JENKINS_HOME}/jobs/branches and workspaces data is under /mnt.
Need to clean jobs data manually, one time per half year is enough:$ cd ${JENKINS_HOME}/jobs/branches
$ find ./* -maxdepth 0 -type d -ctime +100 | xargs sudo rm -rf

pai nodes store Docker images and pai data, all of them will be cleaned each time running jenkins pipeline.
https://github.com/microsoft/pai/blob/817bd75ed7ddd99d58f8f6df9640772d59995759/tests/jenkins/stage_prepare.sh#L35-L41
Build cache is only needed on one jenkins worker, which won't increase disk usage by time.
Azure Linux auto-upgrade will leave many kernel/header packages, which use lots of disk.
After cleaned by sudo apt autoremove, every node's os disk usage is under 50%.


feat(router): support non-text links as external

Please describe the changes this PR makes and why it should be merged:
Closes #223
Currently draft.
Status

[x] Code changes have been tested against prettier, or there are no code changes
[x] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[x] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[x] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 60.98%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1379

Relevant Lines:
2349

💛  - Coveralls

This is really well written. LGTM and thanks for the help


Migration content update

Docs Build status updates of commit d2d2b2b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 0ace911:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3b2fdd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2de45df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 77b9d03:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b1b966d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Hi @f4rty - this is ready for your review.

Docs Build status updates of commit 1f51698:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:bulb:Suggestion
View (graph-powershell-1.0 || graph-powershell-beta)
Details

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/migration-steps.md

Line 50, Column 220: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: /powershell/module/psscriptanalyzer/?view=ps-modules
Line 69, Column 15: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: /graph/api/overview?view=graph-rest-1.0

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 936f98c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b517567:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 17e768a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@f4rty, please review this. I have incorporated feedback from our discussions. Thanks.

Docs Build status updates of commit 3ef4005:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b7f8ea9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoftgraph/docs-conceptual/migration-steps.md
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

microsoftgraph/docs-conceptual/toc.yml
:white_check_mark:Succeeded
View (graph-powershell-1.0 || graph-powershell-beta)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Reviewed and approved

@adamedx , requesting for your review of the updated migration content. Thanks.

Docs Build status updates of commit f058921:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@timayabi2020, please merge this.


Challenge Drop It - Uses a recursive algorithm and fails tests, console logs correct

Challenge Drop it has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
// jshint esversion:6
// jshint -W033

// take the first val of an arr
// if first val passes func test
// return the arr
// else drop the first val
// repeat
// if arr.length === 0, return []

console.log("----------START----------")

function dropElements(arr, func) {
  if (!arr.length) {
    console.log("Returned: ", arr)
    return arr // this will be [] if we cut out all the arr vals
  }
  if (!func(arr[0])) {
    let cut = arr.splice(0,1)
    console.log("Cut out: ", cut)
    dropElements(arr, func)
  }
  else {
    console.log("Returned: ", arr)
    return arr
  }
}

dropElements([], function(n) {return n >= 3;})

SCREENSHOTS:

Hi @149203, thanks for reporting. That's an interesting solution, but unfortunately it's not quite correct!
I will leave it as an exercise for you to think about why this is the case, but your code will return the correct results only if the last line within your second if statement is changed from dropElements(arr, func) to return dropElements(arr, func)
Remember that the HelpJavaScript chat should be your first port of call when something isn't working quite right with your code, before raising an issue.
Happy coding!

@BKinahan thanks for the quick reply! Will do!


Document how to SSH into kubernetes nodes

Sometimes, we might need to actually SSH into the kubernetes nodes themselves to fix issues. For example, there's an automatic update rolled out to all Ubuntu 18.04 nodes on Azure that cause them to lose network access (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119), the quickest solution is:

ssh into all nodes,
run sudo reboot

However, this can be really simple (on GCP) or complex (hello, Azure!). We should document how to do this!

This looks like a helpful blog post for the Azure case: https://trstringer.com/aks-ssh-to-node/

Adding a doc on using kubectl debug that works across clusters in #2654


Using trans(simple_string) instead of namespaced backpack.simple_string

Hi,
Sorry for writing after the question was closed, but I thought you would look for all cases where the trans('one_word') structure is used and fix them.
<label class="form-label" for="{{ $username }}">{{ trans(config('backpack.base.authentication_column_name')) }}</label> - resources/views/vendor/backpack/theme-tabler/auth/login/inc/form.blade.php
trans(config('backpack.base.authentication_column_name')) == __('Email') and it will also throw an error if there is an email.php file in the lang folder.
Originally posted by @smart4you in https://github.com/Laravel-Backpack/theme-tabler/issues/96#issuecomment-1632675374

@promatik picked up a PR I had https://github.com/Laravel-Backpack/theme-tabler/pull/97 (it was good but not complete).
I've also found this issue that the user now mentioned but I haven't gone back to work on the PR.
We still have this place where we use trans('string') instead of trans('namespace.string').

Sorry for writing after the question was closed, but I thought you would look for all cases where the trans('one_word') structure is used and fix them.

We don't have a way to look for all places, since it can be a simple string like before but it can also be a config (like here) that just outputs a string. So we're counting on you to tell us if there are more places where we do this, thanks.

@smart4you I can't seem to replicate your error.
I've created an email.php lang file:

But the login form is loading fine for me:

Do I need to do anything else to reproduce this? Are you sure this is the cause for your error? Can you please share your full error stack? You can do that using the Share button in the Flare error page.
Cheers!

Hi,
Yes, you are right, there is indeed a nuance. I installed a new Laravel project and Backpack and everything worked, but when I added the translation to the file, I immediately got an error. Probably the email.php file is somehow ignored if it is empty without translations. I just added "test" => "test" for the test and the error appeared.
So far I've only seen this behavior on the Login and Register forms.

@pxpm sorry, I didn't know there was more, the first mistake was actually mine 🙃 I did the __('Admin') while working on themes. So I though it was only that one.
Anyway, I searched for all the trans( and __( and I couldn't find more.
I found 2 using the same config config('backpack.base.authentication_column_name').
But I don't think this one is an issue.

It should never be an array, it should be a string.
It is a column with a name provided by the developer, not on the backpack scope.

Let me know if I'm wrong, otherwise I think we can close this one.

Hi, My appeal to the Backpack team was to inform you that there is a recommendation in the official documentation of Laravel https://laravel.com/docs/10.x/localization#defining-translation-strings about the fact that it is better not to use this behavior. And the fact that this situation is real and not theoretical.

Key / File Conflicts
You should not define translation string keys that conflict with other translation filenames. For example, translating __('Action') for the "NL" locale while a nl/action.php file exists but a nl.json file does not exist will result in the translator returning the entire contents of nl/action.php.

But you yourself will decide whether it is worth taking this recommendation or can be ignored.

Hey everyone, I searched on the project for not namespaced translations, and carefully went one by one and I couldn't find any.
I'll close this one for now, if anyone finds something, please reopen 🙌

In your image, on the form.blade.php there is one of those cases. trans(config('backpack.base.authentication_column_name)) that will translate into something like: trans('email').
Cheers

Fixed with https://github.com/Laravel-Backpack/theme-tabler/pull/145 👌


Define capabilities and API for sl-loading-icon

This issue is where discussion about all of the things we want to change about the sl-loading-icon component should occur and the final definition of its capabilities and API are defined.  As these items are discussed and vetted, issues will be created to work any individual tasks, with this issue serving as the overall source of progress.
To indicate that a capability of the component needs to be verified, add a comment with **VERIFY** as the first line.
To propose a change to the component, add a comment with **PROPOSAL** as the first line.
To indicate that something needs to be researched, add a comment with **RESEARCH** as the first line.
As you are leaving comments regarding any of these VERIFY, PROPOSAL, or RESEARCH comments, link back to the comments link in your own so that the conversation can be more easily followed (in absence of threaded conversation support in Github).  This should be done on the first line of the comment via **RE: <url>**
Capabilities and API

[ ] ARIA support
[ ] ...

Tasks
Adding them here until issues are created

Update documentation for each change
Complete review of documentation against capabilities

Issues tracking these efforts
https://github.com/softlayer/sl-ember-components/issues?q=is%3Aopen+is%3Aissue+milestone%3A"v0.13.0+(Final+push+for+a+1.0.0+release)"+label%3Asl-loading-icon

RESEARCH
I thought we removed this component?

Agreed.  This component has been removed.


Revert "Allow solana dependecies above 1.10 (#174)"

This reverts commit a12a55947632764a31274c24a41af3aed68c944b.

Sorry I accidentally merged, then reverted it. I'm going to be a bit careful about upgrading all the packages. Needs to be tested on devnet etc.

Makes sense!


gerbera: 1.7.0 -> 1.8.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/gerbera/gerbera/releases.
meta.description for gerbera is: "UPnP Media Server for 2020"
meta.homepage for gerbera is: "https://docs.gerbera.io/"
meta.changelog for gerbera is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/fll567mhafzc9fflam1piys5967qac9m-gerbera-1.8.0/bin/gerbera passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 1.8.0 with grep in /nix/store/fll567mhafzc9fflam1piys5967qac9m-gerbera-1.8.0

found 1.8.0 in filename of file in /nix/store/fll567mhafzc9fflam1piys5967qac9m-gerbera-1.8.0

directory tree listing: https://gist.github.com/26b90f4fc0c472527d3bb6b681ef9d01

du listing: https://gist.github.com/e1daabaf1b9b6087a73a1617b0d7dcc5

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gerbera
tests.nixos-functions.nixos-test

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fll567mhafzc9fflam1piys5967qac9m-gerbera-1.8.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gerbera https://github.com/r-ryantm/nixpkgs/archive/13f9b58c5963e4c52dc7b6be93e8771eb8a5916a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fll567mhafzc9fflam1piys5967qac9m-gerbera-1.8.0
ls -la /nix/store/fll567mhafzc9fflam1piys5967qac9m-gerbera-1.8.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gerbera

Maintainer pings
cc @ardumont for testing.

Result of nixpkgs-review pr 119000 run on x86_64-linux 1

1 package blacklisted:

tests.nixos-functions.nixos-test

1 package built:

gerbera

Besides the failing tests.

Which tests?

Besides the failing tests.

Which tests?

Possibly the mediatomb service ones (which runs some with gerbera instead of mediatomb, gerbera being the fork of mediatomb).


chore: bdd-sbhg-1584772750 to 0.0.1

chore: Promote bdd-sbhg-1584772750 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Create rust.yml

https://github.com/aurora-is-near/near-plugins/pull/112#issue-1882624024

Does it matter? Fatal error found! I can play the game! But I thought you were responsible for "said"
Надіслано з Proton Mail mobile
-------- Оригінальне повідомлення --------
5 вер. 2023 р., 23:32, Michael Birch пише:

@birchmd commented on this pull request.
Looks like a duplication of workflows already present in https://github.com/aurora-is-near/near-plugins/blob/master/.github/workflows/test.yml
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@Garrybrayn

#115
Duplicate of #
https://github.com/aurora-is-near/near-plugins/pull/112#issue-1882624024


[WIP] v1.5 to v1.6 upmerge

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[x] Read the contribution guide
[x] Commands include options for Linux, MacOS, and Windows within codetabs
[x] New file and folder names are globally unique
[x] Page references use shortcodes instead of markdown or URL links
[x] Images use HTML style and have alternative text
[x] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
v1.5 to v1.6 upmerge
Issue reference
N/A

abandoning this for one more update needed in v1.5 before upmerging


raftstore: distinguish empty and size uninitialized region

What problem does this PR solve?
Issue Number: close #11114
Problem Summary:
What is changed and how it works?
Use zero to identify size uninitialized regions and 1 to identify empty regions.  The PR to adapt to PD in here: https://github.com/tikv/pd/pull/4243.
What's Changed:
Related changes

Need to cherry-pick to the release branch

Check List
Tests

No code

Side effects
Release note
None

/cc @5kbpers @BusyJay
PTAL

/test

/lgtm

/merge

/retest

/test

/run-all-tests

/merge


Issue with strict:true on tsconfig.json

Don't publish ts file to npm package to prevent strict check.

Compile each packages using strict:true option
good luck 😄


added palindrome and DLL reverse for linked list

Added two questions under linked list data structure.

One checking if the linked list is palindrome or not.
Other one for reversing a doubly linked list.

The "check_if_linkedlist_is_a_palindrome" solution is great as you have used a different approach than this.
Please give a brief description of your approach at the top of the file.
Also for reverse_a_double_linkedlist program add a description of the problem and add comments wherever necessary above that particular statement.
Make these changes and you are good to go ! Great work BTW.

@smv1999  I have made the  requested changes, kindly check the commits.

@smv1999 I have made the requested changes, kindly check the commits.


[FEATURE REQUEST] Support for UI toolkit

Please add support for unity UI toolkit for runtime use

This would be nice to add, but at the moment UI toolkit is missing a lot of the features that we'd need to implement this. A core part of Unity Figma Bridge is a custom material/shader that we use to render Figma objects, and right now custom shaders aren't planned for UI Toolkit until at least 2024. You can read the thread here. You could definitely do a basic layout right now but it's too early to have a truly useful importer right now.

+1


Refactor Nearlib

There are few things we want to improve:
Configuration search:

[ ] For Node.js use cases, search for .near/ folder with config and keys. Main uses cases:

local to project (so go up to folder with node_modules / package.json and check for .near). This can be official TestNet and custom network.
running node connected to official TestNet (~/.near/ for configs). Want to use it, but need to use contract helper for account creation.
running custom network with local node (~/.near/ for configs). Want to use local key pair for account creation.

[ ] Create various types of transactions functions that support creating and signing transactions (without having connection).
[ ] ConnectProvider interface that various providers like RPC, RPCv2, Network, WebSockets can implement (e.g. current NearClient is RPC provider). Provides sendTransaction(txBytes, [timeout]) -> Promise<FinalTransactionResult> and query(path, data) -> Promise<QueryResult> interfaces.
[ ] AccountCreatorProvider - interface, that either uses helper or given keys to create accounts.
[ ] connect that is configured / or searches for configuration and uses given ConnectProvider, AccountCreatorProvider and KeyStore.
[ ] Account abstraction, that provides accessors to account state (balance, etc), access keys (with permissions per key), etc. Allows to initialize Contract with it to send Tx from it.
[ ] Wallet API is defined via 2 URLs: "Authorize App" API and "Sign Tx" API.
[ ] Contract handles itself sending to Wallet if currently signed Tx is not allowed by access key or access key is missing.
[ ] KeyStore should have some form of Wallet to provide what are current accounts available for given network, and allow to change accounts and networks. Also this should use Wallet API to "login" to retrieve current account id if unavailable.

setItem for localstorage tokens/secretket is kinda inbetween nearwallet and nearlib.  The secretket is set in nearlib and the account id and tokens are set in nearwallet. Should these be all set in nearlib, or shipping to wallet?

@vans163 it's perfectly valid use case not not use wallet at all. From our POV wallet is basically a special type of Signer.

Yea I am thinking that thin API in wallet repo should be moved into nearlib

Could "Create various types of transactions functions that support creating and signing transactions (without having connection)" be made into an issue alone? I can do it if you want (basically we really need the ability to sign a tx, then send it on a different machine)

@DanielRX feel free to do it

After thinking about it, "Create various types of transactions functions that support creating and signing transactions (without having connection)" is impossible, so I'm not sure what you want to do about that? Do you want to scrap the idea of doing so without a connection?


Release Note

Release Note
This release contains 3 bug fixes and 4 Documentation improvements.
🐞 Bug Fixes
Make DocList.to_json() return str instead of bytes (#1769)
This release changes the return type of the methods DocList.to_json() and DocVec.to_json() in order to be consistent with to_json() in BaseDoc and in pydantic models.
After this release, they will return str types instead of bytes.
Since the return type is changed, this is considered a breaking change 💥.
Casting in reduce before appending (#1758)
This release introduces type casting in the reduce helper function before appending to the final results.
This should allow reducing documents whose schemas are compatible but are not exactly the same.
Skip doc attributes in __annotations__ but not in __fields__ (#1777)
This release fixes an issue in the create_pure_python_type_model helper function such that only attributes in the class __fields__ are considered during type creation.
This resulted in issues where introducing a ClassVar in an input class breaks a Jina application:
class MyDoc(BaseDoc):
    endpoint: ClassVar[str] = "my_endpoint"
    input_test: str = ""

    field_info = model.__fields__[field_name].field_info
KeyError: 'endpoint'

Kudos to @NarekA for raising the issue and contributing a fix in the Jina project, which was ported in DocArray.
📗 Documentation Improvements

Explain how to set Document config (#1773)
Add workaround for torch compile (#1754)
Add note about pickling dynamically created Doc class (#1763)
Improve the docstring of filter_docs (#1762)

🤟 Contributors
We would like to thank all contributors to this release:

Sami Jaghouar (@samsja )
Johannes Messner (@JohannesMessner )
AlaeddineAbdessalem (@alaeddine-13 )
Joan Fontanals (@JoanFM )

This release contains 3 bug fixes and 4 documentation improvements, including 1 breaking change.

This release changes the return type of the methods DocList.to_json() and DocVec.to_json() in order to be consistent with BaseDoc .to_json() and other pydantic models. After this release, these methods will return str  type data instead of bytes.
Since the return type is changed, this is considered a breaking change 💥.

Since this is a brraking change @alaeddine-13 , I will release a minor and not a patch

Add a clear list of breaking changes as we have done before. I believe @JohannesMessner did something on some release notes in the past


feat(about): add process section

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


fixed the search button functionality

Issue: The search Icon(magnifying glass) on the student search Page was not functional(not clickable). It only worked after clicking the enter key on the keyboard.
Task: We had to make the icon functional and work without exclusively relying on the enter key on the keyboard.
solution: We solved this by creating an id in HTML for the search icon which we used in a javascript file to make its functionality work. "
Test: You can test this by entering a  full name in the search bar and instead of hitting enter click on the search Icon on your right. It should flash a message if the name is not in the database or show student information if the name is in the database.
Solve issue #1016

it looks good


Using GSM module as Backup plan to connect Firebase

Hi @mobizt, I would really like to thank you for creating such a useful library,
I am thinking of interfacing the GSM module (SM 800) with ESP32 as a backup plan if wifi/internet connection is lost.
I was checking this article it uses the TinyGSM library to do an HTTP request. can we somehow use TinyGSM to connect to firebase and update values using the GSM module?

It's not supported and I also reply here.
The 2G has no future and not available in many mobile operators worldwide.

I dont know if this helps but I faced the same problem, however, I managed to solve it and I have posted my solution as a GitHub Repo


bug: character killer with summons not parsed correct

Character Lester Padrin
Crushed at Level 416 by Hawker Dashzik, Atestado Di Obto, Dadau Rush, Nadica, Mindubina Lovers, Fogosz, Bino Pally Rox, Seborredelson, Miko Miner and knight familiar of Lekinho Destroyer.
Actual parsing:
{
  "name": "knight familiar of Lekinho Destroyer",
  "player": true,
  "traded": false,
  "summon": ""
}

Expected parsing:
{
  "name": "Lekinho Destroyer",
  "player": true,
  "traded": false,
  "summon": "knight familiar"
}

rel #341

Created bug-344-summon-killer-parser-issue branch with updated html-testdata and prepared the tests to align as it should be.


Allow export * as, as it is in tc39 stage 4

"export ns from" is now in stage 4 so shouldn't need a warning.
https://github.com/tc39/proposal-export-ns-from

this flag is deprecated and enabled by default now! 🎉


i lost me 420th post mr squidfart

What is your question?
#420

#420?

AT THIS POINT, IT'S NOT EVEN FUNNY ANY MORE, ITS STARTING TO LITERALLY TURN TO HARASSMENT. FROM YOUR OTHER ISSUES.

 Yro'ue*


[Merge on 6/27] Hub - remove repo management from prod

Continues the series of #66, #75, #139.
Remove "Repo Management" Ansible Automation Hub nav from prod-beta & prod-stable.
(Already removed from stage.)
(No replacement nav items.)
Cc @Hyperkid123
(https://issues.redhat.com/browse/AAH-2257, https://issues.redhat.com/browse/AAH-2334)

@himdel is there any specific release date or can we deploy this whenever?

OK. I am going to convert this one to draft and create a ticket, to merge and deploy the change in 6/13

We're postponing the release to 6/27, apologies :) (updated the ticket too)

Confirming 6/27 deploy, feel free to merge please :)

ping @Hyperkid123 :)


Incompatible with Python 3

The program does not work on Python 3.
Python 3.4.0 (default, Apr 11 2014, 13:05:11)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from lcdproc.server import Server
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.4/dist-packages/lcdproc/server.py", line 46
    if self.debug: print "Telnet Request:  %s" % (command_string)
                                             ^
SyntaxError: invalid syntax
>>>

The print statement syntax changed from Python 2 to 3 try the utility script 2to3

#10 is a pull request that contains a python3 compatability fix.  I had to fix both the print statement (using future) and also deal with urllib compatibility issues.


[Misc]: Investigate issues with async execution of TT-llama for serving

Anything you want to discuss about vllm.
When enabling TTExecutorAsync to execute TT-llama asynchronously, the following error occurs during serving (with server_example_tt.py):

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

This issue only occurs when trying to run the TT model using ttnn's async mode since it is not aware that a thread other than the main thread is being used to launch ops. Upon further investigation with assistance from @tt-asaigal, it was discovered that the output tensor from an operation prior to the all gather (in this case, the embedding op) did not contain the correct worker IDs due the output not being properly assigned through tt::tt_metal::operation::launch_op.

This issue can be fixed once https://github.com/tenstorrent/tt-metal/issues/13447 is completed.


JavaOnlyMap and ReadableNativeMap harmonization about key presence

JavaOnlyMap implementation behaves differently than ReadableNativeMap implementation about key presence.
Description
If you try to get a missing key in a ReadableNativeMap, It throws a NoSuchKeyException whereas It just returns null for JavaOnlyMap implementation.
Though my code is tested when I convert data sent over bridge, I came accross a bug on a real device.
I know I made a false assumption about key presence and there is a method to check if map includes a key but I felt confident because of my unit tests.
I think JavaOnlyMap implementation should throw a NoSuchKeyException if key is missing when trying to get a value.
React Native version:
0.63.3 but not specific to this version.

This is fixed in https://github.com/facebook/react-native/commit/1015194ba1a81eab99000d589914100e4b9ea037, and will be releases in 0.63.4 and 0.64. Thanks


Document: setting ContractResolver overrides custom JsonConverter passed into JsonApiSerializerSettings constructor

I have some non-trivial customizations to JsonApiSerializer (which may be interesting to the larger community, but I'll leave that for another time).
I overrode ResourceObjectConverter, but could not figure out why it wasn't being called. I tried debugging - it wasn't being touched.
Finally, I looked through JsonApiSerializer source, and saw in the constructor of the settings
public JsonApiSerializerSettings(JsonConverter resourceObjectConverter)
{
  ...
  ContractResolver = new JsonApiContractResolver(resourceObjectConverter);
  ...

Which meant that when I set the ContractResolver property post construction, I was losing my custom JsonConverter!
The solution, of course, was to pass in my custom JsonConverter to my custom ContractResolver constructor.
However, I think that should be documented, to save others the - experience that I had.

🙄
Considering that this pull request only effects the README, I don't think it should be able to fail the build.

I agree that the documentation doesn't make this particularly clear
Although i'm not sure that mentioning while discussing how to deserialize different types is the right place.
It might be worth having another section for "Json.net compatibility" and explain that the functionality is hinged off the JsonApiContractResolver so using any other contract resolver will cause issues. Then it can be followed up with settings that you can change such as NamingStrategy (which is what 99% of people want to change the ContractResolver for)

Maybe the new section should be "Customizing JsonApiSerializer"
I feel like that more closely matches what people want to know, namely "How do I customize this?".
It is within that context, after they read that customization is via the standard Json.Net patterns, that there is interest in Json.Net compatibility.
Then in that section we could discuss

Compatibility with Json.Net, that there are properties of the JsonSerializerSettings that could be set, as documented on newtonsoft
JsonApiSerializer relies on the ResourceObjectConvertor (JsonConverter) being used by the JsonApiContractResolver (ContractResolver)
Passing in a custom JsonConverter to the constructor is implemented via the ContractResolver, and if you want to specify the ContractResolver also, make sure that it inherits ResourceObjectConvertor and construct that with your custom JsonConverter instead of JsonApiSerializerSettings

JsonApiSerializer only serializes classes with a string Id property as a JSON:API resource. Because in our code base we have mostly/exclusively integer ids, I made a custom ResourceObjectConverter to de/serialize integer Id properties as strings.
It works by setting the type of the Id property to string, and then using a custom ValueProvider to work with the integer property on the class.
See my gist here.


Context.startForegroundService() did not then call Service.startForeground()

Hello! Thank you for providing a Godot 4 plugin v2 for android notifications.
I got my notification sent successfully, but I have an error crashing my app when the notification is received.
godot::NotificationService: onHandleIntent():: received notification id...  <--- success log
[...]

Context.startForegroundService() did not then call Service.startForeground()

(side note: also I had to rename the init() function to _ready() to initialize the Node properly)

Thanks, @chrisdugne.

(side note: also I had to rename the init() function to _ready() to initialize the Node properly)

Is this the method that you renamed?: https://github.com/cengiz-pz/godot-android-notification-scheduler-plugin/blob/f534f2608ed3c8fd150a050f6d8cb9bf2c953711/notification/addon_template/NotificationScheduler.gd#L19
Alternatively, you could call the init() method of your NotificationScheduler node in the _ready() lifecycle method of your root node.

I got my notification sent successfully, but I have an error crashing my app when the notification is received.

I will take a look at it.  Do you have any more data on the crash?

Just wanted to post in here that I'm getting the same crash. Here's my code, and let me know if you need anything else!
extends Node2D

var label: Label;
var pressed = 0;
# Called when the node enters the scene tree for the first time.
func _ready():
	$NotificationScheduler.init()
	label = get_node("Label")
	if !$NotificationScheduler.has_post_notifications_permission():
		$NotificationScheduler.request_post_notifications_permission()
	$NotificationScheduler.create_notification_channel("my_channel_id", "My Channel Name", "My channel description")

func _on_button_pressed():
	label.text = "Pressed! " + str(pressed);
	pressed += 1;
	var my_notification_data = NotificationData.new()
	my_notification_data.set_id(9).\
			set_channel_id("my_channel_id").\
			set_title("My Notification Title").\
			set_content("My notification content").\
			set_small_icon_name("ic_notification")

	$NotificationScheduler.schedule(
			my_notification_data,
			5
		)

Hi @wychwitch, this is an issue affecting Android 12 and later versions.  The issue is caused by behavior changes that were implemented by the Android team for Android version 12.  Among affected functionality are foreground services, which is causing the crash mentioned on this ticket.
Link: https://developer.android.com/about/versions/12/behavior-changes-12#foreground-service-launch-restrictions
I've started looking into this yesterday.  Will release a new version of the plugin when solved.

@chrisdugne, @wychwitch, please let me know if the new release (1.1) fixes your crashes. It is working on my test environment.

@chrisdugne, @wychwitch, please let me know if the new release (1.1) fixes your crashes. It is working on my test environment.

YES this works now!! thank you!! no crashing issues or anything. Thank you so so much ;u;

I confirm 1.1 is now working properly on my side as well, thank you very much @cengiz-pz !


Figure out an easier way to download SAMI data products from DataCentral

See title. It would be nice to use the API to do this.

According to folks from datacentral, using the API is considerably more complicated than I suspected. Users will have to make do with using the downloads page mentioned in the documentation.


Call history table

Issue #618

added tabs to "PeopleStoriesCard.vue"
added tab styling
created "CallHistory.vue" to components/phone dir
- imported into PeopleStoriesCard.vue
- added column headers
- added computed placeholder data (commented out)
- added space in header between phone # & case #
created "CallSummary.vue" to components/phone dir
- imported into CallHistory.vue
- Added Placeholder information
- added mustache data (commented out)
made tabs work properly
converted from flex to CSS Grid Table
- added css grid elements
- added column sizing via CSS grid-template-columns
- fixed CallSummary.vue sizing
- added grid-template-columns
- reformatted from ol to table with CSS Grids
added basetext
fixed header font, color & weight
added css grid elements
fixed text colors
coverted from Table -> Div Wrapper container
- deleted all table elements & css
- added div "wrapper" class w/ CSS
- put each column element within a "box" div class
- added "box" & "row" css
fixed sizing & margins
deleted unnecessary CSS/comments, unnecessary stories header & content

Chart in Action


Clarify version of Angular

Client requested Angular 2.0 as a requirement.
Angulars newest version right now is 4.
We have to clarify if it's ok to use the latest version.

Also important there are two major Angular releases until march 2018. Version 5 in September 2017 and Version 6 in March 2018. Should we at least keep up with Version 5?
Source: Link

Keeping up with version 5 might be useful:

long term support with version 4 is only granted till October '18
we might be able to postpone work on web app till September/October '17 (release of Angular 5)

At least we should aim for the current version (4) in order to benefit from long term support.

This has been clarified by the supervisor. The latest version of Angular will be used.


Payu doesn't find updated filepaths

I've been testing out ESM1.5 configurations with new input filepaths however run into a payu: error: through the following steps:

Clone the pre-industrial configuration from https://github.com/ACCESS-NRI/access-esm1.5-configs/tree/pre-industrial using payu clone.
Edit the config.yaml file, adding in the updated filepaths (which lie in tm70).
Run the simulation with payu run.

This leads to the following error in the PBS error logs:
payu: error: Input directory /g/data/tm70/sw6175/esm1p5-input-restructure/restructured-inputs/modern/pre-industrial/atmosphere/aerosol/global.N96/2020.05.19/OCFF_1850_ESM1.anc not found; aborting.

which looks like it occurs as tm70 isn't included in the storage flags:
qsub -q normal -P tm70 -l walltime=7200 -l ncpus=384 ... -l storage=gdata/access+gdata/vk83

First running payu setup then payu run -f lets the job run without any issues, and it includes gdata/tm70 in the storage flags.
I'm not 100% sure on this, but I think payu is finding the storage paths for the restarts, executables, and input files from the manifests here:
https://github.com/payu-org/payu/blob/c83489e1cf5af27f94aa8d255330cc50b6cb34fe/payu/schedulers/pbs.py#L119
And so if the payu setup step is skipped, the manifests aren't updated and I don't think the new file paths aren't found.
I just wanted to check whether this is what is meant to happen, ie is payu setup meant to be run whenever changes to the filepaths are made?

Yeah I think you are right, that payu is finding the storage paths for restarts, exes and inputs using the manifests, so maybe payu setup is required when updating those paths. @aidanheerdegen any thoughts on this?
My only idea at the moment at how to get around that is changing payu to auto-run setup and sweep before it submits the pbs payu-run job. It would take longer to run and have a bunch of logs..

Yeah I think you are right, that payu is finding the storage paths for restarts, exes and inputs using the manifests, so maybe payu setup is required when updating those paths. @aidanheerdegen any thoughts on this?

You're spot on. It's a known issue with the storage flags on gadi. It's a chicken and egg problem, which is why I always suggest users do payu setup every time they clone an experiment, or make changes like this. It's a great test to make sure you have access to all the paths in the config.yaml, and also updates manifests etc when paths change, which allows payu to choose the correct storage flags.
We've got it in our trouble-shooting section for OM2
https://access-hive.org.au/models/run-a-model/run-access-om/#trouble-shooting
I think I had it as a recommended step after cloning the experiment, but was convinced that it was better as a trouble-shooting measure.

I'll close this issue as the solution is just to run payu setup first!


[Feature] AddBond event is needed back

Feature Description

Add back the AddBond event when a bond is added for management, with the daoId in addition to bondAddress and whoever added it/.
Additional Information

This code previously existed but was removed due to Slither warning, but as this event is needed to tie together the bond and dao 🤷
(either re-enntry guard to Slither ignore)

Closed by https://github.com/windranger-io/windranger-treasury/pull/255


Bug: Default Mode doesn't take affect when hover wikilinks in frontmatter

test in sandbox:
Obsidian 1.4.14,
Hover Editor 0.11.14, Default Mode is "Match current view".

Here is the GIF:

Sorry, could you please explain in text what is happening and what you expect to happen instead?  The gifs are too fast for me and lack explanation, and since the view headers are not visible I can't even see what modes things are in.  It would also help to know what behavior occurs when a fixed default mode is used (i.e. always edit or always read).  Thanks.

Sorry, could you please explain in text what is happening and what you expect to happen instead? The gifs are too fast for me and lack explanation, and since the view headers are not visible I can't even see what modes things are in. It would also help to know what behavior occurs when a fixed default mode is used (i.e. always edit or always read). Thanks.

Sorry I didn't make it clear.
test1.md:

test2.md:

in test1.md hover [[test2]], it's in editing view, so it matches current view :

then hover wikilinks in frontmatter which in [[test2]] float window, it's in reading view, so it doesn't match current view:

Ok, so this is technically not a bug but a feature request - Hover Editor doesn't have any specific support for property links, which are a new feature of Obsidian 1.4.  (In any previous version of Obsidian, you wouldn't have been able to hover those links at all.)
Probably won't be too hard to add, but I'm not sure when I'll get to it; I'm not using 1.4 myself yet.


PT Run suggestion in text box, and words typed do not match

ℹ Computer information

PowerToys version: 0.21.1
PowerToy Utility: PowerToys Run
Running PowerToys as Admin: yes
Windows build number: [run "winver"] Version 2004 (OS Build 19041.329)

📝 Provide detailed reproduction steps (if any)

Open PowerToys Run textbox
Start typing (with fast speed if possible)
Error in autocomplete (explained below)

✔ Expected result
The autocomplete suggestion characters should be perfectly under the typed text and should change with each keystroke.
❌ Actual result
You will notice that autocompleted suggestion seems to be a little offset and the provided suggestion does not change even when 2-3 characters (different from the suggestion) have been typed.
📷 Screenshots
Difficult to screenshot as the effect lasts only a few seconds

Can you press print screen to make a screenshot? Or make a delay screenshor with Snipping Tool


pico_sdk_import: don't recursively update submodules

When cloning from git, CMake will recursively update submodules by default. Updating all of tiny-usb's submodules takes ages, and isn't required for pico-sdk. The official instructions for manual SDK installation don't do this, in fact. CMake has an option to fix this as of 3.17, and using it should prove harmless for those on older versions (the project officially only requires 3.13, but it will silently ignore this unknown option).

Closed in #772.


Doc: fix docstring of rfft, rfft2, rfftn, irfft, irfft2, irfftn add some function links.

Reference issue
to fix #11566
What does this implement/fix?
Doc: fix docstring of rfft, rfft2, rfftn, irfft, irfft2, irfftn add some function links.

@peterbell10 approved also I checked the links' functionality. Thanks @AtsushiSakai, keep 'em coming!


🔑 Update key for Beth Griggs

I ran the CLI command and committed 	gpg/pubring.kbx and 4ED778F539E3634C779C87C6D7062848A1AB005C.asc. It also created gpg/tofu.db, is that to be ignored?
➜  release-keys git:(bethkey) ./cli.sh add 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg: WARNING: unsafe permissions on homedir '/Users/bgriggs/release-keys/gpg'
gpg: key D7062848A1AB005C: "Beth Griggs<EMAIL_ADDRESS>1 new user ID
gpg: key D7062848A1AB005C: "Beth Griggs<EMAIL_ADDRESS>8 new signatures
gpg: Total number processed: 1
gpg:           new user IDs: 1
gpg:         new signatures: 8
keys.list <- 4ED778F539E3634C779C87C6D7062848A1AB005C
➜  release-keys git:(bethkey) ✗ git status
On branch bethkey
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   gpg/pubring.kbx
	modified:   keys/4ED778F539E3634C779C87C6D7062848A1AB005C.asc

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	gpg/tofu.db

Maybe some folks more well versed in GPG internals can chime in, but from what I can tell, tofu.db is spurious, at least for the purpose of verifying signatures. That could probably be added to .gitignore.

From https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration-Options.html:

TOFU stands for Trust On First Use. In this trust model, the first time a key is seen, it is memorized. If later another key with a user id with the same email address is seen, both keys are marked as suspect. In that case, the next time either is used, a warning is displayed describing the conflict, why it might have occurred (either the user generated a new key and failed to cross sign the old and new keys, the key is forgery, or a man-in-the-middle attack is being attempted), and the user is prompted to manually confirm the validity of the key in question.
Because a potential attacker is able to control the email address and thereby circumvent the conflict detection algorithm by using an email address that is similar in appearance to a trusted email address, whenever a message is verified, statistics about the number of messages signed with the key are shown. In this way, a user can easily identify attacks using fake keys for regular correspondents.
When compared with the Web of Trust, TOFU offers significantly weaker security guarantees. In particular, TOFU only helps ensure consistency (that is, that the binding between a key and email address doesn’t change). A major advantage of TOFU is that it requires little maintenance to use correctly. To use the web of trust properly, you need to actively sign keys and mark users as trusted introducers. This is a time-consuming process and anecdotal evidence suggests that even security-conscious users rarely take the time to do this thoroughly and instead rely on an ad-hoc TOFU process.
In the TOFU model, policies are associated with bindings between keys and email addresses (which are extracted from user ids and normalized). There are five policies, which can be set manually using the --tofu-policy option. The default policy can be set using the --tofu-default-policy option.
The TOFU policies are: auto, good, unknown, bad and ask. The auto policy is used by default (unless overridden by --tofu-default-policy) and marks a binding as marginally trusted. The good, unknown and bad policies mark a binding as fully trusted, as having unknown trust or as having trust never, respectively. The unknown policy is useful for just using TOFU to detect conflicts, but to never assign positive trust to a binding. The final policy, ask prompts the user to indicate the binding’s trust. If batch mode is enabled (or input is inappropriate in the context), then the user is not prompted and the undefined trust level is returned.


Missing Folder Icons

Describe the bug
Some folder icons do not display anymore.
To Reproduce
After upgrading Intellij IDEA to 2021.2.2 (from 2021.2.1) and plugin version 41.0.0 (from 40.0.0) some folder icons stopped showing. It was working on previous versions.
Expected Behavior
All folder icons should be visible
Environment
IntelliJ IDEA 2021.2.2 (Ultimate Edition)
Build #IU-212.5284.40, built on September 14, 2021
Runtime version: 11.0.12+7-b1504.28 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.13.13-200.fc34.x86_64
GC: G1 Young Generation, G1 Old Generation
Memory: 2000M
Cores: 4
Registry: ide.intellij.laf.enable.animation=true, debugger.watches.in.variables=false, ide.balloon.shadow.size=0
Non-Bundled Plugins: com.mallowigi.idea (16.0), com.mallowigi (41.0.0), izhangzhihao.rainbow.brackets (6.21), zielu.gittoolbox (212.7.7), JRebelPlugin (2021.3.2)
Kotlin: 212-1.5.30-release-409-IJ4638.7
Current Desktop: GNOME (Fedora 34)
Screenshots
Previous version:

Current version:

Settings:

Reproduced... I'll issue a fix asap

Version 41.1.0 fixed the issue for me


[WIP, macOS] Implement seamless display scaling.

Use the highest display scale to calculate window/screen coordinates and for rendering, downscale on lower scale displays. Also, should fix popup positions.
Before (moving from hiDPI to lowDPI display):

After:

Fixes #5688 I presume?

Fixes #5688 I presume?

Yes

Thanks hugely!

It should be possible to do similar change for 3.2, but this will involve fully rewriting macOS OpenGL context from View backed to Layer backed (eventually should be done for 4.0 GL support anyway).


update responsive header

Reconstruct the navbar which is responsive for all the devices using bootstrap-4 framework.

Reconstruct the navbar which is responsive for all the devices using bootstrap-4 framework.

Why You change the background image?


Buffer was empty error

With the last version of flutter 0.2.9 i'm receiving this error:
[VERBOSE-2:codec.cc(76)] InitCodec failed - buffer was empty
[VERBOSE-2:dart_error.cc(16)] Unhandled exception:
'package:flutter/src/painting/image_stream.dart': Failed assertion: line 362 pos 12: '_codec != null': is not true.
#0      _AssertionError._doThrowNew (dart:core/runtime/liberrors_patch.dart:37:39)
#1      _AssertionError._throwNew (dart:core/runtime/liberrors_patch.dart:33:5)
#2      MultiFrameImageStreamCompleter._handleCodecReady (package:flutter/src/painting/image_stream.dart)
#3      _RootZone.runUnary (dart:async/zone.dart:1381:54)
#4      _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
#5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:633:45)
#6      Future._propagateToListeners (dart:async/future_impl.dart:662:32)
#7      Future._complete (dart:async/future_impl.dart:467:7)
#8      _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#9      AdvancedNetworkImage._loadAsync (package:flutter_advanced_networkimage/flutter_advanced_networkimage.dart)
<asynchronous suspension>
#10     Ad<…>

Thanks

Sorry for the long wait, this should be fixed now :)


Mention kernelBlur on mirror documentation

http://doc.babylonjs.com/how_to/reflect#mirrors
Sample:
https://www.babylonjs-playground.com/#LVTTQX

(should mention adaptiveBlurKernel which will compute the blur kernel based on viewport size and blurKernel which will use a static one)

Done