Removing unused code.

How do I remove unused JS and CSS code?

You will have to be more specific. What unused code are you trying to remove?

You can use linting to help you find unused JS, but there's no safe way to eliminate all unused JS/CSS; the duck-typed nature of the language makes it impossible, along with the string references to CSS.
This is a question better suited for Stack Overflow, so I'll close it here.
Thanks!

@ianschmitz I'm trying to remove unused CSS code. I tried using purifycss plugin, but could not get it working.
The CSS code to be removed is the one that's not used by the components.

The fact webpack is capable of doing tree-shaking via a plugin it means those plugins are capable ot elimating some code. Can they also display what code is not being included, so we can verify and clean up the codebase itself as well? Aside from create-react-app doing code-elimation.


Breaking change doc (3.0): The "BEGIN TRUSTED CERTIFICATE" syntax is no longer supported for root certificates on Linux

The "BEGIN TRUSTED CERTIFICATE" syntax is no longer supported for root certificates on Linux
Root certificates on Linux (and other Unix-like systems, not including macOS) can be presented in two forms: the standard "BEGIN CERTIFICATE" PEM header, and the OpenSSL-specific "BEGIN TRUSTED CERTIFICATE" PEM header.  The latter syntax allows for additional configuration that has shown to cause compatibility issues with .NET Core's X509Chain class, and is not loaded by the chain engine on newer versions of .NET Core.
Version introduced
.NET Core 3.0
Old behavior
Both the "BEGIN CERTIFICATE" and "BEGIN TRUSTED CERTIFICATE" syntaxes were used to populate the root trust list.  If the "BEGIN TRUSTED CERTIFICATE" syntax was used, and additional options were specified in the file, X509Chain may surprisingly report that the chain trust was explicitly disallowed (X509ChainStatusFlags.ExplicitDistrust), unless the certificate was also specified with the "BEGIN CERTIFICATE" syntax via an earlier-loaded file.
New behavior
"BEGIN TRUSTED CERTIFICATE" contents are no longer read.  If the certificate is not also specified via a standard "BEGIN CERTIFICATE" syntax then X509Chain will report that the root is not trusted (X509ChainStatusFlags.UntrustedRoot).
Reason for change
Incompatibilities with the X509Chain class and the X509_AUX options in "BEGIN TRUSTED CERTIFICATE" certificates leading to surprising interactions around file load ordering.
Recommended action
Many Linux distros write root certificates into two locations: a one certificate per file directory, and a one file concatenation.  On some distros the one certificate per file directory uses the "BEGIN TRUSTED CERTIFICATE" syntax while the one file concatenation uses the standard "BEGIN CERTIFICATE" form.  Ensure that any custom root certificates are added as "BEGIN CERTIFICATE" in at least one of these locations, and that both locations can be read by your application.
The typical directory is /etc/ssl/certs/ and the typical concatenated file is /etc/ssl/cert.pem, but the platform specific root may differ from /etc/ssl/, as reported by the command openssl version -d.  For example, on Ubuntu 18.04 the directory is /usr/lib/ssl/certs/ and /usr/lib/ssl/cert.pem; though /usr/lib/ssl/certs/ is a symlink to /etc/ssl/certs/ and /usr/lib/ssl/cert.pem does not exist.
$ openssl version -d
OPENSSLDIR: "/usr/lib/ssl"
$ ls -al /usr/lib/ssl
total 12
drwxr-xr-x  3 root root 4096 Dec 12 17:10 .
drwxr-xr-x 73 root root 4096 Feb 20 15:18 ..
lrwxrwxrwx  1 root root   14 Mar 27  2018 certs -> /etc/ssl/certs
drwxr-xr-x  2 root root 4096 Dec 12 17:10 misc
lrwxrwxrwx  1 root root   20 Nov 12 16:58 openssl.cnf -> /etc/ssl/openssl.cnf
lrwxrwxrwx  1 root root   16 Mar 27  2018 private -> /etc/ssl/private

Most applications are unaffected by this change, but applications which cannot see both root certificate sources because of permissions problems may experience unexpected UntrustedRoot errors after an upgrade.
Category
CoreFx
Affected APIs
System.Security.Cryptography.X509Certificates.X509Chain

Issue metadata

Issue type: breaking-change

Should the category actually be Cryptography?

Should the category actually be Cryptography?

If that's a category now, sure.  It doesn't seem to be in the template.

Ah, thanks. I'll add it to the template.
https://github.com/dotnet/docs/pull/18034


Wrappers for Form Validation around the Stardust's form related components

Feature Request
Problem description
We need to provide to the user easy to use API for validating the forms created by Stardust components.
Proposed solution
I've taken look into several libraries for form validation and it seems that formsy-react will be the one we are going to use (open for other alternatives if someone has). We should create wrappers around our components, similar as there is for SUIR - https://github.com/zabute/formsy-semantic-ui-react This would offer the users consistent usage of the components from Stardust, when it comes around form validation.

This will be turned into a backlog item, we will carry the information over. Closing this.


React Select fullWIdth props does not work

Describe the bug
When using Select component the fullWidth does not work. This is due to the root <div /> of Select component does not have width: 100% in its style. And currently no way to put styles or css to the <div /> element
Steps To Reproduce
Steps to reproduce the behavior:

Implement Select
apply fullWidth like <Select fullWidth={true} />
see the component will not be full width of its parent

Expected behavior
Be full width of its parent
Screenshots
N/A

Note: This happened only when parent element is flex box. I will fix this soon.


PTZ control location on screen

Is there a possibility to define PTZ controls' position on screen? Somehow in most browsers I tested, PTZ down control location is under the pop-out control so it is impossible to pan down.

You need to read docs carefully.

when you are right, you are right
my bad, sorry
thanks


dropdown element link should work on secound touch

Hi,
I'm creating some dropdown menus with the dropdown element using hover on desktop.
I was expecting that the link of the dropdown, the trigger, would work on the second touch (like in a touch dropdown menu). But it doesn't work at all.
I think I have to add a condition in line 1890 of foundation.js
if (!settings.is_hover || Modernizr.touch) {
but I don't know how to get the state of the respective dropdown content.
Any hints?
Thx in advance.
PS: It's Foundation 5.5.2

You are adding an href to the dropdown trigger correct?
The dropdown trigger is clicked to open the dropdown. If the user wants to close the dropdown, they typically click the trigger again, or tap outside of it. It may be jarring for them to be sent to another page as most users wouldn't expect that to happen.
The e.preventDefault(); would be what's your looking for to change that behavior. It's not on our roadmap to change this behavior but hopefully the explanation is helpful.


Csharp: Seperate Mathf into Maths and Mathd and use Mathf as name for real_t

Somewhat related to https://github.com/godotengine/godot-proposals/issues/5403
Overview

Split the current Mathf class into seperate classes for single and double.
if REAL_T_IS_DOUBLEis double Mathf is used as name for Mathd else for Maths
Function for int are included in Mathf

Notes

Generic Math (preview feature) would be nice to reduce code (no clue if and when godot wants to update csharp version)
I used Mathf as name to avoid compability break, but I would prefer MathGD or something similar
A global alias in a namespace is not possible

To-do

code is alot of ctrl-c + ctrl-v and replace all real_t $\to$ double / single

clean up unnecessary casts
check if everything is correct

Why? If you need explicitly single or double precision math, you can use C#'s own Math and MathF classes.

MathF classes.

System.Mathand System.MathF do not have RadToDeg, DegToRad, MoveToward, MoveTowardAngle, Lerp`, ...

in Mathf if the F in System.MathF means float

Due to double-precision support in Godot, Mathf can also be seen as a retronym for "Math functions".

Why not keep the double overloads in Mathf? double type is just a double precision float, that is it too is a floating-point value.

Why not keep the double overloads in Mathf? double type is just a double precision float, that is it too is a floating-point value.

Overloads can't be used for constants (PiF or PiD don't look good) and only a double version must be casted and only a float version loses precision.


<EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>

<EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>Can anyone please help to resolve this issue asap.

This is not an issue with the package. You need to install moment yourself, that's why it's declared as a peerDepencdency.
See https://nodejs.org/en/blog/npm/peer-dependencies/


Fixdocs

Docs are not building because of issues with the OSMMakie example... this PR fixes that and does some light editing on the ice loss example

Your ice loss example is broken for some reason

it looks like the project toml for the docs doesn't contain Extents.jl

I think this should be good now. There were issues with the test failing because tiles were taking too long to load... causing test to fail


Read outside of Json buffer

The printf format to LogDebug expects pJson to be null-terminated, but its length is given by messageLength. Thus it will read more than expected.
https://github.com/aws/ota-for-aws-iot-embedded-sdk/blob/406415ef38d9f0fbabd69735623008fd090043b3/source/ota.c#L1821
Something like this should fix the issue.
    LogDebug(("JSON received: %.*s", messageLength, pJson));

Thank you for bringing this to our attention! We will be looking further into this issue as soon as we can, thank you for your patience

Hi @gonzzor,
Sorry for late response. The PR is created to apply this change back to OTA library.

The PR - https://github.com/aws/ota-for-aws-iot-embedded-sdk/pull/493

I'm closing this issue since PR's merged


Feature/dash

This PR introduces a Dash based cohort builder

Note : these commits are not part of the PR, rather part of other effort. (will clean up shortly)


Issue 861: Small wording issue with JupyterLab preview

Fixes: https://github.com/jupyter/jupyterlab/issues/861
Preview:

Thanks!

Thanks @Deborah-Digges :smile: Nice to see you contributing over here. Hope all is well.

Hi @willingc 😄
Thank you! All is well - I'm resuming my contributions to open source and thought this would be a great project to contribute to.
If there's anything in particular I can help out with, do let me know - I'd be really excited to help out 😄

Thanks @Deborah-Digges!  All contributions are warmly welcomed.  Feel free to ping us on gitter if you have any questions.


where documentation ! how can use this package

You could start out viewing the example files for starters

https://github.com/cmgmyr/laravel-messenger#examples


Adding v1alpha2 blog post

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This builds on #903 and adds a new blog post to cover the highlights of v1alpha2. This does some nav restructuring to make room for a blog section, this may not make sense. I'm not sure if a blog is actually necessary or helpful, but wanted to test it out. For reference, this is a simplified version of the mkdocs-material blog. This also upgrades our mkdocs versions and adds a few new plugins.
Does this PR introduce a user-facing change?:
NONE

/hold until at least #903 merges

/lgtm
Blog post looks great, I think it's an excellent idea to have a project blog.


Support ColorResolvable via "color" ArgumentType.

It's a little messy, so I welcome anyone to improve it, but this adjustment allows common names, hex values (with and without #), 'RANDOM', RGB array, and numbers to be used as values for the 'color' ArgumentType.
Note that when using an RGB array, either the array must not have spaces in it, or quoted: true must be applied to the argument.
This method takes advantage of the resolveColor() method from discord.js. This theoretically means that anything that can be considered ColorResolvable should work. I've tested it with hex with and without #, RGB array with and without spaces/quotes, numbers, common names, and RANDOM, as listed here  in the Discord.js documentation.
This method also will not break the existing method which is to simply use a hex code as the value of an argument with type: 'color'.

Review
This change is great since it can now parse HEX values, RGB values, and CSS keywords.
I have no problem with the current way it parses but I feel spaces need to be replaced with underscores in order for the resolveColor function to work properly if you supply it with a CSS keyword.
Regex Matching
If anyone feels this would perform better with regex, I've made one regex pattern that matches the three colour types.
/^(?:(?<hex>#[0-9A-F]{6})|\[(?<r>[0-9]|[0-9]{2}|[0-1][0-9]{2}|2[0-4][0-9]|25[0-5]),(?<g>[0-9]|[0-9]{2}|[0-1][0-9]{2}|2[0-4][0-9]|25[0-5]),(?<b>[0-9]|[0-9]{2}|[0-1][0-9]{2}|2[0-4][0-9]|25[0-5])\]|(?<string>[A-Z_]{1,19}))$/i

Here's a link if you want to test it. Although it might need a small change for matching CSS keywords, since it currently matches the pattern strictly to have underscores instead of spaces, and have a maximum length of 19, as the longest CSS keyword that discord.js can parse is LUMINOUS_VIVID_PINK, which is 19 characters long.
It has named groups, so you know which type is detected.

hex - for hexadecimal value matches
r, g, b - for RGB value matches (those are 3 groups not one)
string - for CSS keyword matches.

Note: string currently matches any word, and is not limited to CSS keywords strictly.

To sum up, this change will open a lot of chances for matching colors as a built-in type. More helpful for programmers who have no idea of TypeResolver#addType. Looking forward to this PR getting merged!

I never knew CSS keywords were supported. If that's really true, it could certainly be accounted for.

Yeah, check it out https://discord.js.org/#/docs/main/stable/typedef/ColorResolvable

Oh, those. I'm still not quite sure what you're talking about, because underscores work just fine with this as seen in the screenshot.

resolveColor doesn't work normally if you add spaces
This is what I mean, notice the difference.
const { resolveColor } = require('discord.js');

console.log(resolveColor('DARK_RED')); // 10038562
console.log(resolveColor('DARK RED')); // 218

I think I understand now. I'll do some tinkering.

Very simple fix. Just had to add .replace(' ', '_').

Finally, jfc...


Fix undo redo not adjusting TextEdit viewport to caret

Since we now restore the carets directly and not through set_caret_line|column the viewport was no longer being adjusted.
closes #67453

Thanks!


Support stdlib 5.x

Pull Request Checklist

Description

Support stdlib 5.x
Move puppet6 specific fixtures into main fixtures
Related Issue

Fixes #989
Motivation and Context

Support new versions of modules and no need to have puppet 6 specific fixtures file by using latest puppetlabs_spec_helper.

Released in v2.58.0


[0.27.2 android] Image can not be load from text

The following code is not working in 0.27, but it works in previous version.
const source =  {
      uri: 'data:image/gif;base64,R0lGODlhIAAgALMAAP///7Ozs/v7+9bW1uHh4fLy8rq6uoGBgTQ0NAEBARsbG8TExJeXl/39/VRUVAAAACH/C05FVFNDQVBFMi4wAwEAAAAh+QQFBQAAACwAAAAAIAAgAAAE5xDISSlLrOrNp0pKNRCdFhxVolJLEJQUoSgOpSYT4RowNSsvyW1icA16k8MMMRkCBjskBTFDAZyuAEkqCfxIQ2hgQRFvAQEEIjNxVDW6XNE4YagRjuBCwe60smQUDnd4Rz1ZAQZnFAGDd0hihh12CEE9kjAEVlycXIg7BAsMB6SlnJ87paqbSKiKoqusnbMdmDC2tXQlkUhziYtyWTxIfy6BE8WJt5YEvpJivxNaGmLHT0VnOgGYf0dZXS7APdpB309RnHOG5gDqXGLDaC457D1zZ/V/nmOM82XiHQjYKhKP1oZmADdEAAAh+QQFBQAAACwAAAAAGAAXAAAEchDISasKNeuJFKoHs4mUYlJIkmjIV54Soypsa0wmLSnqoTEtBw52mG0AjhYpBxioEqRNy8V0qFzNw+GGwlJki4lBqx1IBgjMkRIghwjrzcDti2/Gh7D9qN774wQGAYOEfwCChIV/gYmDho+QkZKTR3p7EQAh+QQFBQAAACwBAAAAHQAOAAAEchDISWdANesNHHJZwE2DUSEo5SjKKB2HOKGYFLD1CB/DnEoIlkti2PlyuKGEATMBaAACSyGbEDYD4zN1YIEmh0SCQQgYehNmTNNaKsQJXmBuuEYPi9ECAU/UFnNzeUp9VBQEBoFOLmFxWHNoQw6RWEocEQAh+QQFBQAAACwHAAAAGQARAAAEaRDICdZZNOvNDsvfBhBDdpwZgohBgE3nQaki0AYEjEqOGmqDlkEnAzBUjhrA0CoBYhLVSkm4SaAAWkahCFAWTU0A4RxzFWJnzXFWJJWb9pTihRu5dvghl+/7NQmBggo/fYKHCX8AiAmEEQAh+QQFBQAAACwOAAAAEgAYAAAEZXCwAaq9ODAMDOUAI17McYDhWA3mCYpb1RooXBktmsbt944BU6zCQCBQiwPB4jAihiCK86irTB20qvWp7Xq/FYV4TNWNz4oqWoEIgL0HX/eQSLi69boCikTkE2VVDAp5d1p0CW4RACH5BAUFAAAALA4AAAASAB4AAASAkBgCqr3YBIMXvkEIMsxXhcFFpiZqBaTXisBClibgAnd+ijYGq2I4HAamwXBgNHJ8BEbzgPNNjz7LwpnFDLvgLGJMdnw/5DRCrHaE3xbKm6FQwOt1xDnpwCvcJgcJMgEIeCYOCQlrF4YmBIoJVV2CCXZvCooHbwGRcAiKcmFUJhEAIfkEBQUAAAAsDwABABEAHwAABHsQyAkGoRivELInnOFlBjeM1BCiFBdcbMUtKQdTN0CUJru5NJQrYMh5VIFTTKJcOj2HqJQRhEqvqGuU+uw6AwgEwxkOO55lxIihoDjKY8pBoThPxmpAYi+hKzoeewkTdHkZghMIdCOIhIuHfBMOjxiNLR4KCW1ODAlxSxEAIfkEBQUAAAAsCAAOABgAEgAABGwQyEkrCDgbYvvMoOF5ILaNaIoGKroch9hacD3MFMHUBzMHiBtgwJMBFolDB4GoGGBCACKRcAAUWAmzOWJQExysQsJgWj0KqvKalTiYPhp1LBFTtp10Is6mT5gdVFx1bRN8FTsVCAqDOB9+KhEAIfkEBQUAAAAsAgASAB0ADgAABHgQyEmrBePS4bQdQZBdR5IcHmWEgUFQgWKaKbWwwSIhc4LonsXhBSCsQoOSScGQDJiWwOHQnAxWBIYJNXEoFCiEWDI9jCzESey7GwMM5doEwW4jJoypQQ743u1WcTV0CgFzbhJ5XClfHYd/EwZnHoYVDgiOfHKQNREAIfkEBQUAAAAsAAAPABkAEQAABGeQqUQruDjrW3vaYCZ5X2ie6EkcKaooTAsi7ytnTq046BBsNcTvItz4AotMwKZBIC6H6CVAJaCcT0CUBTgaTg5nTCu9GKiDEMPJg5YBBOpwlnVzLwtqyKnZagZWahoMB2M3GgsHSRsRACH5BAUFAAAALAEACAARABgAAARcMKR0gL34npkUyyCAcAmyhBijkGi2UW02VHFt33iu7yiDIDaD4/erEYGDlu/nuBAOJ9Dvc2EcDgFAYIuaXS3bbOh6MIC5IAP5Eh5fk2exC4tpgwZyiyFgvhEMBBEAIfkEBQUAAAAsAAACAA4AHQAABHMQyAnYoViSlFDGXBJ808Ep5KRwV8qEg+pRCOeoioKMwJK0Ekcu54h9AoghKgXIMZgAApQZcCCu2Ax2O6NUud2pmJcyHA4L0uDM/ljYDCnGfGakJQE5YH0wUBYBAUYfBIFkHwaBgxkDgX5lgXpHAXcpBIsRADs=',
      isStatic: true
};

function _renderLoading(isLoading: boolean) {
    if (isLoading) {
        return <Image source={source} style={{width: 20, height: 20, marginRight: 10}} />;
    } else {
        return <Text />;
    }
}

Hey there and thank you for using React Native!
React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
Do the checklist before filing an issue:

[ ] Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
[ ] Have a usage question? Ask your question on StackOverflow. We use StackOverflow for usage question and GitHub for bugs.
[ ] Have an idea for a feature? Post the feature request on Product Pains. It has a voting system to surface the important issues. GitHub issues should only be used for bugs.

None of the above, create a bug report
Make sure to add all the information needed to understand the bug so that someone can help. If the info is missing we'll add the 'Needs more information' label and close the issue until there is enough information.

[ ] Provide a minimal code snippet / rnplay example that reproduces the bug.
[ ] Provide screenshots where appropriate
[ ] What's the version of React Native you're using?
[ ] Does this occur on iOS, Android or both?
[ ] Are you using Mac, Linux or Windows?

I am having a similar issue displaying base64 images in Android 6.

I think the key here is "Android, and not iOS, requires height/width/flex information." I'm going to close this issue as answered, thanks for reporting!


fix Gride range_max + return ranks/datasets sizes in ID scaling functions

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (f1d07a2) 79.13% compared to head (b5f1b7e) 79.14%.

Files
Patch %
Lines

dadapy/id_estimation.py
95.83%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #112      +/-   ##
==========================================
+ Coverage   79.13%   79.14%   +0.01%
==========================================
  Files          15       15
  Lines        2506     2512       +6
==========================================
+ Hits         1983     1988       +5
- Misses        523      524       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to determine BIOS of SCHP-1001

Hello, all!  I heard about this project a little while ago and finally got time to looking into it.  I dug out my early NA model PS-X.  The sticker on the bottom says "SCPH-1001".  I see there are different BIOS and some hardware revisions all called by this same model #.  I can't find any good information on how to tell which version my box has.
I should probably plug it in to see if it even still works.  I don't think I've had it powered on since the 90's.

It's always a bit of a chicken and egg issue. If you can already run arbitrary code, then running the latest version of Unirom will show you a CRC32 of the bios you have, and you can then look it up. The other option if you can easily rewrite memory cards is to simply test multiple versions until one works. Be aware that once you've written one image, it may be difficult to write another one.

The box has a very early mod chip, so I should be able to run homebrew.  I
will try that angle.  I will eventually have to slap together the arduino
based card reader, but it will be easier to put that off for a bit.
Thank you for your help!  I will close the issue once I am back at my
computer if someone else hasn't already done so by then.
On Mon, Apr 26, 2021, 8:22 PM Nicolas Noble @.***>
wrote:

It's always a bit of a chicken and egg issue. If you can already run
arbitrary code, then running the latest version of Unirom
https://github.com/JonathanDotCel/unirom8_bootdisc_and_firmware_for_ps1/releases
will show you a CRC32 of the bios you have, and you can then look it up.
The other option if you can easily rewrite memory cards is to simply test
multiple versions until one works. Be aware that once you've written one
image, it may be difficult to write another one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brad-lin/FreePSXBoot/issues/52#issuecomment-827222086,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPEX7G7KHQZ5CSRUMBY4Z3TKX7TJANCNFSM43TRGUEQ
.

Great! If you burn a CD-R with Unirom on it, and manage to boot it, then you will be able to flash all of the images you want from the CD-R itself, without issue.

The hacked memory card can be plugged in once the cd boots and it will be
okay?  I guess I would expect an open project to have the bugfix for this
exploit. ;)
On Mon, Apr 26, 2021, 9:35 PM Nicolas Noble @.***>
wrote:

Great! If you burn a CD-R with Unirom on it, and manage to boot it, then
you will be able to flash all of the images you want from the CD-R itself,
without issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brad-lin/FreePSXBoot/issues/52#issuecomment-827245070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPEX7BJ3EXJVLNEHA6XYPTTKYIHFANCNFSM43TRGUEQ
.

You can properly run unirom from the CD at boot time with a memory card that hosts the exploit, yes.

Now to figure out what Unirom is and how it works. :)  Thank you!


Create accommodation-Nijmegen.md

New folder and .md file focused on finding an accommodation in Nijmegen. I've want it to appear at the bottom of lab_basics, similar to how SOP and int-serv-roles are arranged."

I'm afraid I can't see these new changes. I mean, I can't find any section named "housing Nijmegen" or similar when I search through the lab wiki website.


GLSL: NV_ray_tracing support seems forgot shaderRecordNV.

Hi guys-
We already have GLSL_NV_ray_tracing support but it looks that we forgot shaderRecordNV. It turns out to be nothing but enums if I search "ShaderRecordBufferNV".

Seems like callable shaders are not supported. Ping @pmoursnv.


Fail to refactor the bf section

Hi all,
I import the app into android studio and get successful build, but whan i try to refactor (rename package name), always fail when try to change the bf  into com,  please help how to solve this.
The error message is  .....file already exits.
I suspect that there is  "com" folder and "bf"  folder in same parent folder so whent try to refactor the com folder is already there (conatining google etc)
Please help how to do it correctly
Regards,
Bun Hin

You have to change whole folder structure for example: https://abhiandroid.com/androidstudio/how-to-change-package-name-android-studio.html

@ZelvaJan thank you for reply, actually i did the step by step, but i will try again


Introducing patternfly-ng

This replaces components from ngx-widgets with patternfly-ng, including:

The tooblar component
The filter/sort components used by toolbar.

This also introduces the latest dropdown from ngx-bootstrap for compatibility with patternfly-ng.
See: https://github.com/fabric8-ui/fabric8-ui/pull/1738

@dlabrecq fabric8/fabric8-ui:SNAPSHOT-PR-2075-1 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2075-fabric8-planner.badger.fabric8.io


Dev

@LakshmanDhullipalla9 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


A more usable BOM and a new Guice Platform BOM

Refactored pom files to provide a more usable BOM and a new Guice Platform BOM to ease Guice Integration.

Thanks for the patch!
@tbroyer, you initially added the BOM, and @mcculls, you know the most about Maven... WDYT of this?

With these changes, users can use the Guice BOM as a parent and override individual dependencies. For instance, if you wish to downgrade guice persist, you can just add the version property and that is it. Master doesn't allow you to do that, a user would need to add a dependency management entry.
Also, I thought of the "platform" as a way to easily inherit all the Guice dependency management. For instance, Guice uses google dagger and the version being used is 2.0, a user inheriting from the the platform will not need to specify the version of dagger BUT if the user wants to upgrade it to 2.0.2 (current), only the version property is needed.
Examples are in the README.md of each module.
Guice BOM: https://github.com/jccarrillo/guice/tree/bom/bom
Guice Platform BOM: https://github.com/jccarrillo/guice/tree/bom/platform
Thanks for looking at this.

Master doesn't allow you to do that, a user would need to add a dependency management entry.

What's wrong with that?
Actually, I don't think one should use a BOM as a parent POM.
If you want to override a dependency-management entry from a BOM, either add it as a dependency with a version (and/or scope), or as a dependency-management.
Using properties and a "BOM as parent POM" feels just wrong to me; even more so that its only "added value" is to save you a few lines (override property value vs. override dependency-management entry), and it comes at the expense of maintainability (one day, a developer will come, see that property, grep for it, find nothing, and simply delete it; if you want a dependency-management entry, use a dependency-management entry; verbosity should not be an excuse).
I'm OK with introducing a Guice BOM separate from guice-parent, but only as a way to separate build-related dependencies (e.g. JUnit) and other transitive dependencies (Dagger, Spring, etc.) from Guice artifacts.
I don't think the “platform” BOM is useful (see above wrt usage of properties).
Similarly, Guava should IMO be left as a transitive dependency and its version not fixed in the BOM.

It's not about being right or wrong. It's about giving users "options".
A user can import a bom in the dependency management and apply those overrides in the dm as always.
Being come from a spring background, the usage of spring's platform as a parent is beneficial for me and I'm sure plenty of other developers.
Again, this patch is not a must use as a parent, it's about providing the user the option of using it as a parent, either the Guice BOM or the Guice Platform BOM.
See springs platform documentation as reference: http://docs.spring.io/platform/docs/current/reference/html/getting-started-using-spring-io-platform.html
Regards,
-JC

On Feb 7, 2016, at 10:55 AM, Thomas Broyer<EMAIL_ADDRESS>wrote:
Master doesn't allow you to do that, a user would need to add a dependency management entry.
What's wrong with that?
Actually, I don't think one should use a BOM as a parent POM.
If you want to override a dependency-management entry from a BOM, either add it as a dependency with a version (and/or scope), or as a dependency-management.
Using properties and a "BOM as parent POM" feels just wrong to me; even more so that its only "added value" is to save you a few lines (override property value vs. override dependency-management entry), and it comes at the expense of maintainability (one day, a developer will come, see that property, grep for it, find nothing, and simply delete it; if you want a dependency-management entry, use a dependency-management entry; verbosity should not be an excuse).
I'm OK with introducing a Guice BOM separate from guice-parent, but only as a way to separate build-related dependencies (e.g. JUnit) and other transitive dependencies (Dagger, Spring, etc.) from Guice artifacts.
I don't think the “platform” BOM is useful (see above wrt usage of properties).
Similarly, Guava should IMO be left as a transitive dependency and its version not fixed in the BOM.
—
Reply to this email directly or view it on GitHub.

@sameb I agree with the points that @tbroyer already made (I also added some more comments inline)

I have addressed all concerns, if there are any others, please let me know. Thanks for having looked at this patch!

@jccarrillo I still have concerns with this patch:

I really don't think we should be promoting use of the BOM as a parent POM, so any changes relating to this should be removed from the patch
The overuse of version properties should be removed or scaled back, since most of those are specific to using the BOM as a parent POM
The platform BOM doesn't bring much value and should be dropped to avoid confusion

Since the original goal was to improve the BOM, perhaps it would be better to start with with changes focused on that part of the build, such as disconnecting it from guice-parent, and avoid changing other non-BOM parts of the build?

@mcculls,

Promotion of BOM as a parent has been removed and changes related to that has been removed as well.
Version properties have been reduced to two, guice and guice-extentions.
The platform BOM has been removed.

Please let me know if there is anything else needed.

Sorry that this was left for so long. Things have likely shifted a lot things it was sent as far as the poms go, so I'm going to close this.  If you'd like to pursue it, please re-open and we can go from there.


LanguageClient ServerOptions not spawning when Server in Path

I am developting an extension that uses the LanguageClient class to provide a connection to a language server. The language server is installed globally on the OS and can be started using a <command> as it is in $PATH (installed via npm -g i <package>).
Now, the client fails to start the server. My first approach was using these server options:
const serverOptions: Executable = {
    command: "<command>",
    args: ["--stdio"],
}

This does not work, as child_process#spawn does not get the environment variables. This is the relevant section in the code:
https://github.com/Microsoft/vscode-languageserver-node/blob/583ba3878faa9e550461337afefb1618505a4601/client/src/main.ts#L397-L405
My second attempt was to pass process.env as env option:
const serverOptions: Executable = {
	command: "<command>",
	args: ["--stdio"],
	options: {
		env: process.env,
	}
};

This also did not work. I also tried to pass cwd: undefined via options.
One thing that worked for me was to use shell: true in options. However, both declarations of ExecutableOptions do not include a shell?: boolean:
https://github.com/Microsoft/vscode-languageserver-node/blob/583ba3878faa9e550461337afefb1618505a4601/client/src/main.ts#L37-L42
https://github.com/Microsoft/vscode-languageserver-node/blob/c7d5ab633672f5b38886ee54f5dd10c3a8d3646d/client/src/client.ts#L190-L195
But child_process#spawn's options does (ref to docs).
As this behaviour is rather unintuitive to me, I think this might be a bug or or there is some documentation missing on this. I just want to start <command> --stdio to use it as a language server. According to this issue it should suffice to provide options: { cwd: undefined, env: process.env }. But it does not seem to work. It works with options: { shell: true } only, but shell is not included in ExecutableOptions.

OS: Windows 10
Dependencies:

"vscode": "^1.1.18",
"vscode-languageclient": "^4.2.1"

Yes, I see the point. The thing is that npm -g i very likely installs a shell script and that script can't be run using spwan without using the shell option.

For now cast the options to any and set the shell property. It will be passed to spawn correctly.

Thanks!


Fresh installation, openvpn server won't start

I made fresh install on debian 12 and openvpn-aws. But seems openvpn server is not starting. I did not edit any configuration files. Just ran the commands shown for setting it up to test it as proof of concept. Got ui running at port 8080 and it works. But openvpn docker wont start.
Snippet on the end of log:

net.ipv4.ip_forward = 1
net.ipv4.ip_forward = 1
net.ipv4.ip_forward = 1
net.ipv4.ip_forward = 1
net.ipv4.ip_forward = 1
Configuring iptables...
NAT for OpenVPN clients
Blocking ICMP for external clients
Blocking internal home subnet to access from external openvpn clients (Internet still available)
No additional firewall rules to apply.
IPT MASQ Chains:
MASQUERADE  all  --  <IP_ADDRESS>/24         anywhere
MASQUERADE  all  --  <IP_ADDRESS>/24         anywhere
IPT FWD Chains:
       0        0 DROP       1    --  *      *       <IP_ADDRESS>/24         <IP_ADDRESS>/0            icmptype 8
       0        0 DROP       1    --  *      *       <IP_ADDRESS>/24         <IP_ADDRESS>/0            icmptype 0
       0        0 DROP       0    --  *      *       <IP_ADDRESS>/24         <IP_ADDRESS>/24
Start openvpn process...
Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/server.conf
Use --help for more information.
EasyRSA path: /usr/share/easy-rsa OVPN path: /etc/openvpn
PKI already set up.

Hi @jannoke
As per the logs its can't find your server.conf file and I know why - the latest commit with server.conf relocation has not been merged from dev to main branch.
Thanks to you, it is now done.
Please fetch all the latest changes (git pull origin master --force) and run the playbook again. All should works fine.

Thanks. I was able to run it no problem after that.


Updated NuGet packages

Changed NewtonSoft.Json references to 'netstandard1.0'

Fixes #2290

:memo: After we fix this in the stabilization branch (#2325) I'll merge it forward so it applies to master as well.


Localredirectpolicies (lrp) on OKD breaks openshift-dns dns-node-resolver. Cilum 1.9.5

Bug report
On http://okd.io/ cilium with Local redirect policies for dns service breaks resolving in openshift-dns/dns container dns-node-resolver.
Confirmed in 4 clusters.
apiVersion: cilium.io/v2
kind: CiliumLocalRedirectPolicy
metadata:
  name: nodelocal-dns
  namespace: openshift-dns
spec:
  redirectBackend:
    localEndpointSelector:
      matchLabels:
        dns.operator.openshift.io/daemonset-dns: default
    toPorts:
      - name: dns-tcp
        port: '5353'
        protocol: TCP
      - name: dns
        port: '5353'
        protocol: UDP
  redirectFrontend:
    serviceMatcher:
      namespace: openshift-dns
      serviceName: dns-default

General Information

Cilium version:  Client: 1.9.5 079bdaf 2021-03-10T13:12:19-08:00 go version go1.15.8 linux/amd64
Kernel version: 5.10.19-200.fc33.x86_64
Orchestration system version in use: 4.7.0-0.okd-2021-03-21-094146 / Kubernetes Version: v1.20.0-1054+bafe72fb05eddc-dirty

How to reproduce the issue

Open terminal in any openshift-dns/dns-default-XXXX pod. Container dns-node-resolver.
Try (env comes from openshift dns pod). Thats how openshift collects image registry ip for /etc/hosts
dig -t A @"${NAMESERVER}" +short "${svc}.${CLUSTER_DOMAIN}"
it will respond with image registry service ip
Create LRP policy from "bug report"
Try resolve again. It will fail with " ;; connection timed out; no servers could be reached"
Remove LRP policy - resolving from this container works.
Note: resolving works nice in other containers. Maybe openshift dns is somehow special. With LRP container connects to dns in the same pod(to itself).

@msheldyakov From what you described, you might be hitting this case - https://docs.cilium.io/en/v1.10/gettingstarted/local-redirect-policy/#miscellaneous. We purposely disallow loops (i.e. when LRP backends connect to the VIP, and the service translation selects the same backend).

@msheldyakov From what you described, you might be hitting this case - https://docs.cilium.io/en/v1.10/gettingstarted/local-redirect-policy/#miscellaneous. We purposely disallow loops (i.e. when LRP backends connect to the VIP, and the service translation selects the same backend).

However, such translation is skipped using sk_lookup BPF helpers for traffic that originates from the backend and is destined to the frontend .

From my understanding, "skip" here means that the traffic will be processed as without a policy, and the other backend will simply respond to request. In my case, turning off the LRP repairs the service. Am i wrong?

@msheldyakov No, what the document note implies is that traffic is forwarded to the service VIP since it's not translated. I have created a PR to clarify this in the guide.
Coming back to the issue, how does node-local dns work on OKD without LRP?


[3pts] Connect the frontend and the backend applications

Connet React and RoR applications

@thasipablo i want to work on this can you assign it to me


Fix printing order

Fixes issues #2 and #8
Balanced list of b branch is mixed,
because b.append(..) is used.
b.insert(0, ..) should be used instead.
This code:
from pptree import *

shame = Node("shame")

conscience = Node("conscience", shame)
selfdisgust = Node("selfdisgust", shame)
embarrassment = Node("embarrassment", shame)

selfconsciousness = Node("selfconsciousness", embarrassment)
shamefacedness = Node("shamefacedness", embarrassment)
chagrin = Node("chagrin", embarrassment)
discomfiture = Node("discomfiture", embarrassment)
abashment = Node("abashment", embarrassment)
confusion = Node("confusion", embarrassment)

print_tree(shame, horizontal=False)

Currently prints:
 shame
conscience   selfdisgust                                             embarrassment
                              selfconsciousness   shamefacedness   chagrin   confusion   abashment   discomfiture

But it should do:
 shame
conscience   selfdisgust                                             embarrassment
                              selfconsciousness   shamefacedness   chagrin   discomfiture   abashment   confusion

Also this line in balanced_branches changes the order:
    a = sorted(children(current_node), key=lambda node: nb_children(node))
If you change it to, the order will be the same as user defined:
    a = children(current_node)
It seems that it works fine without this sorting.

@clemtoy What do you think about my previous comment? Are there any reasons to change the order specfied by client/user/developer? The balancing itself can be done without reordering/sorting.

do good job!

@kanunnykov Thanks for the suggestion, It worked for me.

Good job! Thanks for your code!


oamlGodotModule Node Inheritance

This pull request makes the oamlGodotModule class inherit from Node instead of from Reference, for the reasons detailed in issue #8 . Namely, it can now be instanced directly, without needing to be a member variable of a node.
For example: without this change, I had to have an otherwise empty node containing OAML in order to use the latter. I called this node "music_player", and the oamlGodotModule instance "oaml_module". To interact with OAML, then, I needed to make calls like this:
music_player.oaml_module.play_track("MenuTheme")

With this pull request, I can instance OAML directly as a node. So I removed the parent node from the process, and renamed the oamlGodotModule instance to "music_player", and now I call it directly, like this:
music_player.play_track("MenuTheme")

Thanks!


Filter with time component

Hi,
I'm looking to add a native video filter which changes over time, in the same way as the DynamicWaveFilter. Can I achieve this with the library? Can other uniforms be provided to the shaders?
Thanks in advance, and sorry for asking in English :)
varying mediump vec2 textureCoordinate;
uniform sampler2D inputImageTexture;
uniform float iGlobalTime;

uniform vec2 noDraws;

void main()
{
    vec2 position = textureCoordinate * 256.0;

    vec2 uv = 0.5 + (position-0.5)*(0.9 + 0.1*sin(0.2*iGlobalTime));

    vec3 oricol = texture2D( inputImageTexture, textureCoordinate).rgb;
    vec3 col;

    col.r = texture2D(inputImageTexture,vec2(uv.x+0.003,-uv.y)).r;
    col.g = texture2D(inputImageTexture,vec2(uv.x+0.000,-uv.y)).g;
    col.b = texture2D(inputImageTexture,vec2(uv.x-0.003,-uv.y)).b;

    col = clamp(col*0.5+0.5*col*col*1.2,0.0,1.0);

    col *= 0.5 + 0.5*16.0*uv.x*uv.y*(1.0-uv.x)*(1.0-uv.y);

    col *= vec3(0.95,1.05,0.95);

    col *= 0.9+0.1*sin(10.0*iGlobalTime+uv.y*1000.0);

    col *= 0.99+0.01*sin(110.0*iGlobalTime);

    col = mix( col, oricol, clamp(-2.0+2.0*position.x,0.0,1.0) );

    gl_FragColor.bgra = vec4(col.b, col.g, col.r,1.0);
}

Of course, you can try it.
PS: The whole repo will be open source in a few days/weeks.
You can add more custom functions at that time.😋

Great :) Is this achievable at the moment? I can't see how to provide iGlobalTime or noDraws to the shader

Yes, you can override the 'render2texture' function, and pass these values every frame.
Or you have to write a wrapper for java-layer, and pass the uniforms as you wish.

Thanks, I'll give it a try 👍

Could you please provide an example code for this?
For instance, how can I send a value from a seekbar to a custom filter as uniform?

@chimanaco

Thank you. I tried it but I haven't gotten luck yet. The below is the flow I followed and I overrided the setIntensity function in CustomFilter_0. I just want to pass a value without changing an intensity of a filter itself.

CameraDemoActivity.Java
 public void onProgressChanged(SeekBar seekBar, int progress, boolean fromUser) {              float intensity = progress / 100.0f;              mCameraView.setFilterIntensity(intensity);          }

CameraGLSurfaceView.Java
public void setFilterIntensity(final float intensity) {      queueEvent(new Runnable() {          @Override          public void run() {              if (mFrameRecorder != null) {                  mFrameRecorder.setFilterIntensity(intensity);              } else {                  Log.e(LOG_TAG, "setFilterIntensity after release!!");              }          }      });  }

CGEFrameRenderer.Java
//set the intensity of the filter  public void setFilterIntensity(float value) {      if(mNativeAddress != 0)          nativeSetFilterIntensity(mNativeAddress, value);  }

cgeFrameRendererWrapper.cpp
JNIEXPORT void JNICALL Java_org_wysaid_nativePort_CGEFrameRenderer_nativeSetFilterIntensity (JNIEnv *env, jobject, jlong addr, jfloat intensity) {  CGEFrameRenderer* renderer = (CGEFrameRenderer*)addr;  renderer->setFilterIntensity(intensity); }

cgeFrameRenderer.cpp
`void CGEFrameRenderer::setFilterIntensity(float value)
{
CHECK_RENDERER_STATUS;
 m_resultMutex.lock();
 auto& filters = m_frameHandler->peekFilters();
 for(auto& filter : filters)
 {
 	filter->setIntensity(value);
 }
 m_resultMutex.unlock();

}`

CustomFilter_0.cpp
`
#include "customFilter_0.h"

using namespace CGE;
static CGEConstString s_fsh = CGE_SHADER_STRING_PRECISION_H
(
varying vec2 textureCoordinate;
uniform sampler2D inputImageTexture;
uniform vec2 vSteps;
uniform float intensity;
void main(void)
{
vec4 originalColor = texture2D(inputImageTexture, textureCoordinate);
vec4 invertedColor = vec4(((intensity * 0.5+0.5) - originalColor.rgb), originalColor.w);
gl_FragColor = invertedColor;
});
bool CustomFilter_0::init()
{
if(m_program.initWithShaderStrings(g_vshDefaultWithoutTexCoord, s_fsh))
{
m_program.bind();
mStepLoc = m_program.uniformLocation("vSteps");
return true;
}
return false;
}
void CustomFilter_0::render2Texture(CGEImageHandlerInterface* handler, GLuint srcTexture, GLuint vertexBufferID)
{
handler->setAsTarget();
m_program.bind();
const CGESizei& sz = handler->getOutputFBOSize();

glUniform2f(mStepLoc, 1.0f / sz.width, 1.0f / sz.height);

glEnableVertexAttribArray(0);
glVertexAttribPointer(0, 2, GL_FLOAT, GL_FALSE, 0, 0);
glActiveTexture(GL_TEXTURE0);
glBindTexture(GL_TEXTURE_2D, srcTexture);

glDrawArrays(GL_TRIANGLE_FAN, 0, 4);

}
CGEConstString CustomFilter_0::paramIntensity = "intensity";
void CustomFilter_0::setIntensity(float value)
{
m_program.bind();
m_program.sendUniformf(paramIntensity, value);
}
`
Thanks in advance.

You can make a fork and push your code.
I'll try your code.

Ok. This is my test code.
https://github.com/chimanaco/android-gpuimage-plus/tree/features/customfilter
After building the native library, go to CameraDemoActivity, find Custom and tap it. You will see an inverted image.
What I expect is changing value instead of intensity of filter itself.
Thanks in advance!

Please see the PR
You can sync the latest code, and pass false for arg useWrapper


Trainning not stop in the 2nd statge

I have set lpips_start_iters: 140_000 max_updates: 150_000 in file 'lm3d_radnerf_sr.yaml'
and  set lpips_start_iters: 140_000 num_updates: 150_000 in file 'lm3d_radnerf_torso_sr.yaml'
However, training of the head-NeRF can stop at 150,000 steps while training of the torso model does not.

please set max_updates instead of num_dates


[T6A1][W14-C3]

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


Mangagezgini changed thema and domain

Source information
MangaGezgini 1.4.38
Source language
Turkish
Steps to reproduce
Mangagezgini.com changed https://noxscans.com/ and changed thema
Expected behavior
Opened
Actual behavior
Notopened
Tachiyomi compatible app name & version
Mihon 0.16.5
Android version
Android 11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the tachiyomi compatible app.
[X] I have the latest extension version.
[X] I will fill out all of the requested information in this form.

Hi @Thekages.
This repo only support extension that communicate with self-hosted servers. Please ask the right repo.


Cb 148 configure parameter file for ampliseq pipeline

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description

nextflow_schema.json updated with our chosen defaults for the ampliseq pipeline. This includes ideal truncation lengths along with links to our s3 references.
One problem is the pipeline doesn't support the dataset/sample sheet input of other nf-core pipelines. Probably not stupendously hard to fix, but I couldn't figure it out in one try so I'm not going to bother. Will revisit if I come to regret this choice.
Jira Task

CB-148 configure parameter file for ampliseq pipeline
Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📕 notebook(s)
[x] ⌨ Adjusted schema help text
[ ] 🙅 no documentation needed

Code Quality

[x] 🎯 The code is properly formatted and adheres to the project's style guide
[x] 🎯 The code runs without any errors or exceptions

Compute Environment

This can run locally, on EC2, and on tower. It is designed to run best on Tower
Testing

https://tower.nf/orgs/ArkeaBio/workspaces/Computational_Biology/watch/5Xyf1L5cegLYak
In lieu of testing, please admire this run and how nicely it completed.

That'd be neat! I figured the metadata aspect was secondary to the actual
parameters being set up correctly.
On Tue, Jul 18, 2023 at 1:55 PM Laura Holland @.***>
wrote:

@.**** approved this pull request.
Yay, another pipeline ready to go! Glad there wasn't a need for any major
changes. I can also put together a metadata file for the dataset we'll be
getting if we want to test do a test run with stats/plots (we can just pair
it with random samples from the same test dataset).
In nextflow_schema.json
https://github.com/Arkea-Bio-Corp/ampliseq/pull/1#discussion_r1267109144
:

                 "description": "DADA2 read truncation value for forward strand, set this to 0 for no truncation",

                 "help_text": "Read denoising by DADA2 creates an error profile specific to a sequencing run and uses this to correct sequencing errors. This method prefers when all reads to have the same length and as high quality as possible while maintaining at least 20 bp overlap for merging. One cutoff for the forward read `--trunclenf` and one for the reverse read `--trunclenr` truncate all longer reads at that position and drop all shorter reads.\nIf not set, these cutoffs will be determined automatically for the position before the mean quality score drops below `--trunc_qmin`.\n\nFor example:\n\n```bash\n--trunclenf 180 --trunclenr 120\n```\n\nPlease note:\n\n1. Overly aggressive truncation might lead to insufficient overlap for read merging\n2. Too little truncation might reduce denoised reads\n3. The code choosing these values automatically cannot take the points above into account, therefore checking read numbers is essential",
                 "fa_icon": "fas fa-ban"
             },
             "trunclenr": {
                 "type": "integer",

               "default": 250,

these trunc values will likely change depending on the quality of our
dataset, but hopefully not by too much!
—
Reply to this email directly, view it on GitHub
https://github.com/Arkea-Bio-Corp/ampliseq/pull/1#pullrequestreview-1535594270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7NVQEXY7TCCO6JCSMGCDTDXQ3EYJANCNFSM6AAAAAA2OQJOEE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Taylor Falk (he/him)
Bioinformatics Engineer I
arkeabio.com http://www.arkeabio.com

Yep, it is. Not a super high priority, but still worth testing eventually nonetheless.


atuin: 0.10.0 -> 11.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ellie/atuin/releases.
meta.description for atuin is: "Replacement for a shell history which records additional commands context with optional encrypted synchronization between machines"
meta.homepage for atuin is: "https://github.com/ellie/atuin"
meta.changelog for atuin is: ""
Updates performed

Rust 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
found 11.0.0 with grep in /nix/store/pa7spbf1695775gmqvxpc30mllsmvkzl-atuin-11.0.0
found 11.0.0 in filename of file in /nix/store/pa7spbf1695775gmqvxpc30mllsmvkzl-atuin-11.0.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
atuin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pa7spbf1695775gmqvxpc30mllsmvkzl-atuin-11.0.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 atuin https://github.com/r-ryantm/nixpkgs/archive/5ca81b4df61dbe3de7cb80d7c6b67fb455eeceb3.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/pa7spbf1695775gmqvxpc30mllsmvkzl-atuin-11.0.0
ls -la /nix/store/pa7spbf1695775gmqvxpc30mllsmvkzl-atuin-11.0.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:

atuin

Maintainer pings
cc @onsails @SuperSandro2000 @Sciencentistguy for testing.

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

1 package built:

atuin


Edgeisdead

Not that it matters much for this tiny app anyways

Bumped node version from 18.x to 20.x in Vercel.


Fix #28: escape special characters in mongo credentials

Escapes any special characters in the mongodb username or password.

Great, thanks!


Parsing of timedata is buggy (?)

https://github.com/equinor/fmu-dataio/blob/b35a3176af2c809083536c5d629b91424e14bbf3/src/fmu/dataio/_export_item.py#L409
Working on a string from the timedata list, but then taking the first element, which becomes the first character. Leads to this in the wild:
ValueError: time data '2' does not match format '%Y%m%d'

Input to dataio is e.g.:
timedata=["20150101", "20210101"]

Actually, probably works as expected - it expects input as list of lists. Suggest to include a check for this and throw error if input is not list of lists. Alternatively, allow for list of dates in addition to list of lists.

Actually, it seems like this may be intentional, but it makes no sense.  At least, the sequence of them should not be switched. When 20210515 is input as the first list, it should show up first in the file name.

It was not intentional that filenames had clock times (although it can be discussed; what if timedata for e.g. a well test comes within the same date?). File names with ":" are not windows compatible so of course that shall change.
The order of the dates was also something we discussed and we need to land on that: Given [[20100101, "first"], [20200101, "second"], then technically the diff map or property is "second-first"?
A last comment is that file names are purely informal. The file names themselves are not parsed in SUMO; it is the metadata file only.

From seismic best practice: monitor-base: [[20210101, "monitor"], [19990101, "base"]] giving filenames some--20200101_19990101. A rewording in the docs is also needed

Think this can be closed now? @perolavsvendsen @berland ?


moving the cursor causes text area sync to be off on windows

use a screen reader and run a few commands in the terminal
press up arrow and use the left arrow to navigate through the command
run the command
🐛 text area is no longer synced correctly

@meganrogge what is the "text area"? I tried to repro the issue on stable and I looked at the accessible view, but I'm not sure what I'm looking for.

Enable "terminal.integrated.developer.devMode" to check the contents are right

Or use a screen reader and ensure that when navigating w arrow keys, the right chars are announced.
In either case, need to be in screen reader optimized mode

Very cool to see this actually working for history 👏


Removed Iron Alloy Block

Description
Removed the Iron Alloy Block. Also ran runData to remove it from the generated data.
Closes #243
Checklist:

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you).
[x] I have performed a self-review of my own code.
[x] I have commented my code in areas it may be challenging to understand.
[x] I have made corresponding changes to the documentation.
[x] I have added relevant player-facing changes to the CHANGELOG.md file.
[x] My changes are ready for review from a contributor.

Oops didn't even think about that!


Disable XCTestPluginIntegrationTest until Swift 6 is supported

We need this to unblock RfR for 8.11.1 following infrastructure changes
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test RfR

I've triggered the following builds:

Ready for Release (Trigger) (Check)

Build Scan


Cannot compile on raspberry pi 4B due to sh: 1: ./ptr_size_generator: Exec format error

Describe the bug
PicoRuby cannot be compiled on anything other than x86-64 due to the ptr_size_generator executable in mruby-pico-compiler
To Reproduce
Run rake on a non x86-64 architecture
sh: 1: ./ptr_size_generator: Exec format error
rake aborted!
To Fix
simply delete picoruby/mrbgems/mruby-pico-compiler/lib/ptr_size_generator and recompile before running rake in picoruby/
This is all that is needed to get picoruby working on Linux raspberrypi 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
Additional context
Perhaps rake can compile a test program to determine the pointer length, like configure does, to avaoid having to have a pre compiled binary. Or just pre generate the header file with known values.

@mormyrid1 Thanks for the report. I think I could fix it


How to make this model work for 24k/48kHz sampling rates?

Is only thing required is retraining WavLM to the respective sampling rates?

I've updated tips here.

Cheers. Is there a way to train on 24kHz dataset, or it wouldn't make much difference ?

Yes. Just follow the training example here.

Thank you!


fix: left pad Jaeger header

Summary
In our setup, Kong 3 -> OpenTelemetry collector with the Jaeger headers, the [otel] plugin is logging a bunch 400's telling that the TraceID lenght is invalid. It feels odd to pad the various elements before doing the from_hex rather than after the to_hex
Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

[Implement ...]

Issue reference

Fix #8119

Hello @greut , this fix seems correct, it needs only two things:

Rebase over master
Modification of the tests that now fail because of the changed headers (you can see them failing here https://github.com/Kong/kong/actions/runs/3620849084/jobs/6103577526 )


Training does not stop at target achievement

Description
Training does not stop when both validation and test targets are reached, resulting in a final score always equal to max_allowed_runtime. The issue appears both in wandb logs and in standard out.
Source or Possible Fix
By inspecting submission_runner.py, I spotted a bug in the code.
Simplifying, this is how train_once looks like now:
goals_reached = ..
  while not goals_reached:
    # train

However, goals_reached is not updated anymore after declaration! This is how this block look like:
goals_reached = ..
  while not goals_reached:
    # train
    goals_reached = ...

Thanks for catching this and proposing a fix! I'll merge in a fix since the CLA process might take a few days.


SLR CIS beta preview updates

[x] default to dark style basemap
[ ] add draft about content
[ ] add resources

 SLR CIS: beta updates prior to CEC review


Add a "last week" page

I consistently want to know what links I added in the last week.

Maybe I should have a page that groups all notes by week of last update?

I might want to see that I mentioned all links I saw last week

closed in 226344d67cbaa4f7757c65236ba8f73a9fce7a8c


Update simple icons dependency to 5.7.0

Update simple icons dependency to 5.7.0
Signed-off-by: Engin Diri<EMAIL_ADDRESS>

Hi, thanks for opening a PR but I'm going to close this.
Our policy and process for incorporating Simple Icons updates is discussed here and we're not going to do ad-hoc ones like this

hi @calebcartwright , link is not working…

hi @calebcartwright , link is not working…

#5369

Thanks for the link @calebcartwright. Why i cant argue about the content and the procedure behind, i just can say that simple-icons release on a Sunday.
So it may help, to check on a Monday for the dependabot. This could help to reduce "waiting" time 😅 At the end, its just creates a PR, the time to merge it is still on your hand. Just a suggestion, especially when a feature part of the shields functionality relies on simple-icons.
Nevertheles, you folks a the shields.io project to good work and i think everybody appriciate the work you put in! ❤

Nevertheles, you folks a the shields.io project to good work and i think everybody appriciate the work you put in! heart

Thanks for the kind words!

Why i cant argue about the content and the procedure behind, i just can say that simple-icons release on a Sunday.

So it may help, to check on a Monday for the dependabot. This could help to reduce "waiting" time sweat_smile At the end, its just creates a PR, the time to merge it is still on your hand. Just a suggestion, especially when a feature part of the shields functionality relies on simple-icons.

Feels like you may be missing the point here. We are well aware that we don't always have the absolute latest bleeding edge version of every dependency in our dependency tree; that's not a goal of our project. We balance the maintenance/operational overhead of applying dependency upgrades by updating our dependencies consistently on a regular, weekly schedule.
We quite literally just did an update of Simple Icons to v5.6 a couple days ago as part of our regularly scheduled cadence. As noted in the linked discussion, we run our dependency updates, via Dependabot, on Friday. Not Monday. It doesn't matter if one of our dependencies publishes a new release in between our regular updates (outside some emergency security concern) because we'll pull the newer version in during our next dependency update.
We simply aren't going to update the package and deploy it on a daily basis/instantaneously every time Simple Icons (or any of our other dependencies) release a patch update. There's essentially a maximum possible wait of 7 days if SI happen to release another new version immediately after we update on Friday, and that doesn't happen too often.
I appreciate folks' desire to use some brand-new icon just released by SI, but they'll either have to wait for a few days if they want to use that icon with our badges via a logo slug, or if they are unwilling to wait then they can use our custom logo feature with the base 64 encoded version of the SI logo
https://github.com/badges/shields/blob/master/doc/logos.md#custom-logos


Override default constructors for primitive types. [Fixes #296]

Two minor requests, but this looks great, thanks!

I took the nuclear option to fixing this instead—no more default constructors at all! :)
Getting rid of them makes a few tiny class definitions a bit more verbose, but it lets you easily create abstract base classes that can be inherited but not constructed. It also simplifies the VM a bit and fixes this bug.


dev: run cargo clippy --  -W clippy::pedantic -W clippy::nursery -W clippy::expect_used and implement fixes

In order to improve the codebase's code quality, run:
cargo clippy --  -W clippy::pedantic -W clippy::nursery -W clippy::expect_used on the whole workspace and implement the advises it gives.

Hi Elias, can i take this one?

Sure!


The request multipart/form-data is truncated unexpectedly if its size exceeds 1mb in Next Js api hosted on Amplify.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d3rm9tzrpvwvtt
Region
eu-west-2
Amplify Hosting feature
Not applicable
Describe the bug
The request multipart/form-data is truncated unexpectedly if its size exceeds 1mb in Next Js api (/api/file-test.ts) hosted on Amplify.
This results in an error when parsing the body. Here is example of error when parsing is done via 'multiparty' but it is similar when another body parser is used.(e.g. busboy):
ERROR BadRequestError: stream ended unexpectedly
at Form.<anonymous> (/var/task/chunks/6485.js:795:24)
at Form.emit (events.js:412:35)
at finish (internal/streams/writable.js:657:10)
at finishMaybe (internal/streams/writable.js:644:9)
at afterWrite (internal/streams/writable.js:473:3)
at onwrite (internal/streams/writable.js:446:7)
at processTicksAndRejections (internal/process/task_queues.js:77:11)

Everything is ok when request is less then 1 mb. Everything is ok when it is run outside of amplify (e.g. localhost).

pages/file-test.tsx - form that will be submitted:

import type { NextPage } from 'next';
import { useCallback, useRef } from 'react';
import request from '../lib/request';

const TestFile: NextPage = () => {
  const ref = useRef(null);
  const onSave = useCallback((event) => {
    event.preventDefault();
    request('/api/file-test', {
      method: 'POST',
      // @ts-ignore
      body: new FormData(ref.current),
    })
  }, []);
  return (

      MULTIPARTY

      <form onSubmit={onSave} ref={ref}>
        <input type="file" name="file1" />
        <input type="file" name="file2" />
        <input type="file" name="file3" />

        <button type="submit">submit</button>
      </form>

  );
}

export default TestFile;

/lib/request.ts:

export default async function request(url: string, props: any = { headers: {} }) {
  const params = {
    ...props,
    headers: {
      ...(props.headers || {}),
    }
  };

  const response = await fetch(`${url}`, params);
  return await response.json();
}

pages/api/file-test.ts - api that process request and should return files metadata:

import type { NextApiRequest, NextApiResponse } from 'next';
import { Response } from '../../types';
import multiparty from 'multiparty';

type Res = Response<any>;

export default async function myHandler(
  req: NextApiRequest,
  res: NextApiResponse<Res>
) {
  if (req.method === 'POST') {

    try {

      const multipartyForm = new multiparty.Form({ autoFields: true, autoFiles: true });
      const parsedForm = await new Promise((resolve, reject) => {
        // @ts-ignore
        multipartyForm.parse(req, function (err, fields, files) {
          if (err) reject(err);

          resolve({ fields, files });
        });
      });
      // @ts-ignore
      res.status(200).json(parsedForm);
    } catch (err) {
      console.error(err);
      // @ts-ignore
      res.status(500).json({message: err.message});
    }
  } else {
    res.status(405).end();
  }
}

export const config = {
  api: {
    bodyParser: false
  }
}

package.json:

{
  "name": "testproject",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@emotion/react": "^11.9.0",
    "@emotion/styled": "^11.8.1",
    "@fontsource/frank-ruhl-libre": "^4.5.7",
    "@fontsource/poppins": "^4.5.8",
    "@mui/icons-material": "^5.6.2",
    "@mui/material": "^5.6.3",
    "@prismicio/client": "^6.4.3",
    "async-busboy": "^1.1.0",
    "axios": "^0.27.2",
    "cookies": "^0.8.0",
    "countries-json": "^1.0.1",
    "formdata-node": "^4.3.2",
    "formidable": "2.0.1",
    "formik": "^2.2.9",
    "got": "^11.8.2",
    "mime-types": "^2.1.35",
    "multiparty": "^4.2.3",
    "next": "^11.1.4",
    "next-auth": "4.0.0-beta.3",
    "next-connect": "^0.12.2",
    "node-fetch": "^3.2.4",
    "prismic-reactjs": "^1.3.4",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-intersection-observer": "^8.33.1",
    "yup": "^0.32.11"
  },
  "devDependencies": {
    "@types/async-busboy": "^1.1.1",
    "@types/cookies": "^0.7.7",
    "@types/formidable": "^2.0.5",
    "@types/mime-types": "^2.1.1",
    "@types/multiparty": "^0.0.33",
    "@types/node": "17.0.23",
    "@types/react": "17.0.43",
    "@types/react-dom": "17.0.14",
    "eslint": "^8.12.0",
    "eslint-config-next": "12.1.2",
    "typescript": "4.6.3"
  }
}

Expected behavior
Multipart/form-data request is not truncated and can be parsed correctly.
Reproduction steps

create next js project
Add files from "Describe the bug" section
Host next js project with ssr on Amplify
open /file-test
add files larger then 1 mb and submit form

Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information
No response

Hi @apetrov-monivolt 👋🏽  thanks for raising this issues. According to our docs:

This is caused by a Lambda@Edge limit that restricts the size of a response that is generated by a Lambda function, including headers and body, to 1 MB.


"You're not trained to use that"

I can't use many items. writes "you are not trained to use". How can I fix this?

Can I unlock ALL classes with one command?

If you're trying to use the RPG configs, they are not really ready yet.
Otherwise I think that must be something you have configured? None of the other default configs should do that, except for lightsabers needing a jedi/sith choice and bending powers needing an element choice.

Did you get this figured out? Were you trying to use the RPG configs?


[URGENT] Trying to replicate results on 3.4.1

i am creating a bar/line chart on the same xaxis. however i seem to be having multiple labels of the xaxis stacking up on each other.

i am getting the results in @nagix second example but want the result from the first in terms of the xaxis.
https://github.com/chartjs/Chart.js/issues/5224#issuecomment-494746290
** the line and one of the bars are sharing the same xAxisId while the other is on its own.
my data arrays are generated using javascript calculations after user input in html.
sorry my code is quite messy still a newbie at this **
here are my chart options:
var options = {
          scales: {
            x: [{
              stacked: true,
              id: "bar-x-axis1",
              barThickness: 70,
              display: false,
            }, {
              stacked: true,
              id: "bar-x-axis2",
              barThickness: 70,
              // these are needed because the bar controller defaults set only the first x axis properties
              type: 'category',
              categoryPercentage: 0.8,
              barPercentage: 0.9,
              gridLines: {
                offsetGridLines: true
              },
              display: false,
              offset: true,
            }],
            y: [{
              stacked: false,
              ticks: {
                beginAtZero: true
              },
            }]

          }
        };

in V3 the scales have changed from an array to objects where the key of the object is the ID of the scale.
Then you can set display: false so you will get something like this:
scales: {
  "bar-x-axis1": {
    stacked: true,
    barThickness: 70,
    display: false
  },
  "bar-x-axis2": {
    stacked: true,
    barThickness: 70,
    // these are needed because the bar controller defaults set only the first x axis properties
    type: 'category',
    categoryPercentage: 0.8,
    barPercentage: 0.9,
    gridLines: {
      offsetGridLines: true
    },
    display: false,
    offset: true,
  },
  y: {
    stacked: false,
    beginAtZero: true
  }
}

after implementation i get this

:

A better solution might be to use the floating bar feature because otherwise the bars draw on top of each other and the colours do not blend well. https://jsfiddle.net/3wfsodct/

I actually want them to be drawn on top of each other since i will eventually change the two colours to different shades of grey and considering that my data will be generated through calculations it will be harder to have the code automatically form it an array within an array...

Ah, ok. In that case I think you can just removing the floating bar from the fiddle above. The axes are already close to your ideal image

Thank you soo much for your help @etimberg the fiddle really helped!! :)


Confused about SGDet

Hello ,
Thank you for this great work.
I have read the paper and tried to compare the results I reproduced by running your code. I'm confused a small thing. I read the below snippet from the Neural MOTIF paper  :
" scene graph detection (SGDET): predict boxes, box labels, and edge labels."
to my understanding this means that running the model with the aforementioned mode will produce a complete graph with classes ( objects ) and their edge labels ( predicate). However when I run the inference using SGDet with pretrained check points, I get the following  output:
'pred_boxes', 'pred_classes', 'pred_rel_inds', 'obj_scores', 'rel_scores'
which I presume are bounding boxes , objects , relationships types between the objects and the score confidence of objects and relations. respectively. Am I right in this assumption ?
if so , I have successfully converted pred_class to object labels without issues. But I'm really struggling with  pred_rel_inds, how is this mapped to the relationship type/name.
appreciate your help.
Thank you

pred_rel_inds stores which object IDs a given relationship is between (column 1- head object, column 2 - tail object), and then for evaluation I stack on a 3rd column of the relationship type  - see https://github.com/rowanz/neural-motifs/blob/5f6522fc535a126a9798900e13f207b6ae1eb013/lib/evaluation/sg_eval.py#L147 for more info. thanks!


Separate build phase to test our packages

It would be nice if, after the build, we insert another build step that tests the nuget packages (+ other packages, like vsix)

change PortableTask so it depends on the freshly built nuget packages and not on the projects
publish the local nuget packages into some local nuget feed
test that they restore
test that Portable task works with them

Stretch goals:

deploy msbuild from the local feed and test that it builds some sample projects
figure out how to test the vsix

The sample projects could also use the freshly built packages.

The packages aren't built in CI because they now contain both full framework and .net core assemblies.  They are built in the official build after building both so it can pack up what it needs. :(
We would need a new set of projects that don't get built except in the official build after the packages are created...

We could also create a new set of CI jobs that don't run tests and just build and test the packages.


Flow support

This library compiles itself into dist/index.js using Babel which strips out the Flow annotations, but what about those of us using this in a flowtyped project that are using babel to compile later down the line? Is there any way to get autocompletion/type checks?
The only thing I can think of is writing a separate flowtype interface file and including it in my project, but given the definitions are already written it seems like there should be a way to load them from the node module.

Yeah, let's get a flow type file directly into the npm bundle. The Flow team is working on better tools for this, but I think we have a workaround to use in the meantime that should work just fine.

@leebyron I just discovered this myself. Thanks for responding so quickly to the original question and getting a PR merged. Any releases planned soon that would include this?

Sorry @leebyron you mentioned a workaround... is there some more information about that? I'm currently using create-stub in flowtyped to create stubs for libs like dataloader that already have type annotations...


[Configuration] Ordering of registers by related resources last updated

Name of feature to enhance
Ordering of registers by last updated resource.
At the moment, when a new family is registered it shows at the top of the register - this implementation is using the group resource. However, there is a need to enhance this so that the family's last update will appear at the top. This will also apply to the commodity register.
Describe the enhancement

On the registers, order the list by the last updated resource [relatedresources].
On the household register, if any member of the family record is updated, this family will appear at the top of the family register.
On any other register, the client with the most recently updated record will appear at the top of the list, the rest will be organized in chronological order from the most recent to the furthest updated.
On the stock/inventory register, the commodity that was adjusted/ restocked last will appear at the top of the list, and the rest will be on order of the latest updated to the furthest.

Acceptance criteria

[ ] The household register shows the most recently updated family using [relatedresources] - the family with clients with the most recently updated will be at the top of the register list.
[ ] In other registers, the client with the most recently updated record is shown at the top of the register list.
[ ] Stock/inventory register, the commodity with the most recently updated physical count [adjustment/restock] is shown at the top of the register list.

@AnnieMungai @dubdabasoduba
so essentially, we change the filter from latest updated family to the latest updated family member?

@FikriMilano it should be both. If a new family is registered, it appears at the top of the register list. However, if the last action by the user was updating a family member, then that family will be at the top of the register list.

For the household ordering, I think as long as we update the household Group resource every time a member in the Group is updated, this issue will be resolved.
@ahsanbhatti49

We follow the same approach to any type of resource with relationship to other resources.

@ellykits  In case of resource update, Group information  is not passed on the questionnaire page. So we need to add group id in the config and handle the same on app side. I have started looking at it.

@ellykits In case of resource update, Group information is not passed on the questionnaire page. So we need to add group id in the config and handle the same on app side. I have started looking at it.

Discussed the challenges with @roywanyaga and @dubdabasoduba, we will have a call tomorrow on this with @SebaMutuku included to discuss the implementation plan. Because we need to come up with a generic solution, as suggested by both @dubdabasoduba & @ellykits

Progress updates:
We are able to update the group resource(lastupdated) everytime when there is any update in the child resource.
But registers sorting on the main page is not working as expected. for example :
here are two registers,
1- lastupdated is 2023-02-28T07:57:33.866+00:00 for the first register( so this should be displayed on the top)
2-lastupdated is 2023-02-23T16:12:03.832+00:00  this is currently displaying on the top
This is blocker issue, I need to discuss with @ellykits  @roywanyaga
cc: @f-odhiambo  @dubdabasoduba

Progress updates: We are able to update the group resource(lastupdated) everytime when there is any update in the child resource. But registers sorting on the main page is not working as expected. for example : here are two registers, 1- lastupdated is 2023-02-28T07:57:33.866+00:00 for the first register( so this should be displayed on the top) 2-lastupdated is 2023-02-23T16:12:03.832+00:00 this is currently displaying on the top
This is blocker issue, I need to discuss with @ellykits @roywanyaga
cc: @f-odhiambo @dubdabasoduba

I couldn't replicate this but I tested the implementation and left some comments on the PR.

@SebaMutuku cc @dubdabasoduba re-opening as it failed QA.

@AnnieMungai
This Fails QA.
App:  https://github.com/opensrp/fhircore/releases/tag/v0.2.3-rc1
G60 3GB RAM 64GB ROM android 9
App ID -- cha
See below observations:

A House hold where the family members careplan was last edited is not going to the top of the register
In the other registers, client with most recent record updates is Not being shown at the top of the list e.g in sick child, ANC
Stock/inventory register, the commodity with the most recently updated physical count [adjustment/restock] is not being shown at the top of the register list.

@madrinekariuki Retest with v0.2.3rc3


Fixed #25110 -- Assertion error in method test_duplicates_ignored fixed.

Thanks claudep for the patch.

merged in 199a02d1e2adef39b6346a254b097c9ac64a9ec4, thanks!


Slices no bounds

I have a LOT of method of the following shape:
func algorithm(_ base: inout Base)
func algorithm(_ base: inout Base, in range: some RangeExpression<Base.Index>)
func algorithm(_ base: inout Base, in range: Range<Base.Index>)

algorithm(&base, in: index...)

Using slices is both simpler and nicer, however:
func algorithm(_ base: Base)

 // it just works because slice == base + range

algorithm(&base[index...])

Note: I considered doing it this way, at some point, but I encountered severe performance limitations while implementing my pending flexible width types. After way too much profiling, I believe I have solutions for most of them.

Slices work like other collections, so testing is also much simpler. Writing range-bound test cases was tedious.


Broken Link in Teams Rooms Install Documentation

The PS1 script download link is broken, goes to a 404 page.  Kinda throws a wrench in my day...
https://download.microsoft.com/download/9/0/D/90D4826A-9FD2-47D2-B911-97BF1737F4F7/CreateSrsMedia.ps1
[Enter feedback here]

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

ID: 6f8b204f-9650-d268-8566-7a75ba0a1b6a
Version Independent ID: 9a963e63-6716-7522-8abe-c8a407d3a46d
Content: Configure a Microsoft Teams Rooms console - Microsoft Teams
Content Source: Teams/rooms/console.md
Service: msteams
GitHub Login: @dstrome
Microsoft Alias: dstrome

@PvilleStang thank you for reaching out and helping improve MS Docs. It seems like it's working now as I managed to download the script. Please check from your side and let me know.

@PvilleStang . The link is working, i downloaded the script.

@scanum this can be closed thank you.


GA4GH 0.6.0 updates

Updates for GA4GH API 0.6.0. Includes 9 new endpoints and requires new configs.

@sarahhunt we're branching on Thursday, did you get a chance to reorganise some bits of code or should we take it in its current form?

@magaliruffier - sorry - I was busy elsewhere. Can you take it as is for e!84?

Yes, that's ok


[SQL-DS-CACHE-47]PlasmaTimeOutWrapper

What changes were proposed in this pull request?
PlasmaTimeout wrapper
How was this patch tested?
e2e

@jikunshang

Quick note. Please associate with a JIRA ID.

I will close this one since we have another fix(#56 ), will re-open this one if it doesn't work.


ARROW-7098: [Java] Improve the performance of comparing two memory blocks

We often use the 8-4-1 paradigm to compare two blocks of memory:

First compare by 8-byte blocks in a loop
Then compare by 4-byte blocks in a loop
Last compare by 1-byte blocks in a loop

It can be proved that the second loop runs at most once. So we can replace the loop with a if statement, which will save us a comparison and two jump operations.
According to the discussion in https://github.com/apache/arrow/pull/5508#discussion_r343973982, loops can be expensive.

A simple proof that the second loop can run at most once:
Let's use n to denote the number bytes left after the first loop. It can be seen that n <= 7, because if n >=8, we can have one more iteration of the first loop, which contradicts our assumption that the first loop is finished.
For n <= 7, we have two cases:

if 4 <= n <= 7, the loop run one iteration.
if n < 4, the loop terminates immediately

+1.


Two $ prices in one line interpreted as LateX

Describe the bug
If there are two $ symbols on the same line, such as two prices, Quartz interprets it as LateX. Replacing the $ symbols with $ does not help.
To Reproduce
Steps to reproduce the behavior:

Write two prices on the same line, using the dollar symbol for both. For example: "The scooter was $599 but is now $799."
Observe how Obsidian correctly renders the dollar amounts with no issue.
Publish the note to Quartz
Observe that the published note in Quartz now has formatting errors.

Expected behavior
Published notes in Quartz using single $ should not trigger LateX. At the very least, explicit $ should not trigger latex.

This seems to be a Katex issue, will look into this further (you can disable Katex if you don't need it as well)

Hi! I'm also having this issue - where can I see how to disable Katex? I've tried adding math: false to the header and escaping the $s with a \$  but I'm still getting the issue of text between dollar signs being imterpreted as a formula.

This issue should be fixed in Quartz 4. I'll be closing it for now but please reopen this issue if this persists in the new version.


Update to the cli for M365 version

Update to the cli for M365 version as start date and end date more than 24 hours apart for the cli for m365 equivalent.

Good morning @reshmee011 - processed this one, thank you for the cool updates! This will be live shortly 🎉


Elasticsearch - Disable source and refresh

set refresh_interval to -1 to speed up indexing
https://www.elastic.co/guide/en/elasticsearch/reference/8.7/tune-for-indexing-speed.html#_unset_or_increase_the_refresh_interval

exclude vector from source
https://www.elastic.co/guide/en/elasticsearch/reference/8.7/tune-for-disk-usage.html#disable-source

@mjmbischoff How does this affect the benchmark? Is the plot in the README up to date?

@mikelam92 Currently the readme has not been updated, It was confirmed that they would rerun the benchmarks but I guess they are busy/burdened with other things like the rest of us.
Both settings has a non trivial impact - there are quite some other things that could be done to collect additional percentage points, but focussing on the low hanging - and easier to explain - changes.
Setting the refresh to -1 disables the time-based refreshing which works best with batch imports. Meaning refresh(flushing / creating segments happens only when refresh is explicitly called or if the buffer is full) Merging currently isn't super efficient although improvements were made in newer version, it's still an area that's a focus for improvement. If not (force)merging to a single segment then this change has a bigger impact.
Disabling source: since checking the results is done by checking the returned ID's only it's not required to fetch more fields. This is still realistic in some real life use-cases as well where the id's are passed on to a different system. While limiting which fields are fetched can save bandwidth as it requires fewer bytes to be transferred (ES first selects the documents and then retrieves them(fetch) in a second stage) I'm unsure if ES will short circuit the action by omitting the fetch operation at all (since it already has the document id's) but if fetch happens it just has very little to do, improving performance.


IIS Deployment - Cannot match any routes. URL Segment: 'projectXXX/Home'

Stack; ASP.NET Core Web API 5 + Angular 8 + Identity Server 4
I have tested both development and production mode, it is working fine. Once I publish and deploy it to IIS with the folder name "WorldCities2" then modify the base href from / to /WorldCities2/. The error "ERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'worldcities2/Home'" occur. worldcities2/Identity/Account/Register and worldcities2/Identity/Account/Login also working just fine.

Sorry to hear you're having problems! But without a clear way to reproduce this issue, we can't be of much help. I also think that Angular 8 is too far back for the community here to be able to support.
Could you please create a minimal way to reproduce this for us, using the latest version of the library? Thanks!