gods, this is an awesome lib.  btw, call this program support WebUI pattern?

Thanks! Yes! But since --headless is its default, you need to pass a --headful parameter to override that.

hello i also need this functionality. However, analyzing the source code, I saw that --headless is being called directly in the ssh command. I tested it with --headful and was not successful.
Follow the path: https://github.com/SvenskaSpel/locust-swarm/blob/master/bin/swarm#L242

init Command:
swarm -t 10 --loadgen-list <IP_ADDRESS> --loadgens 1 --processes-per-loadgen 16 --headful -f 01_banner_v1.py
Error Return:
raise subprocess.CalledProcessError(retcode, process.args)
subprocess.CalledProcessError: Command 'ssh -q <IP_ADDRESS> ' LOCUST_RUN_ID="2021-12-13T21:03:30.632264+00:00" PYTHONUNBUFFERED=1 locust --worker --master-port 5557 --headless -f 01_banner_v1.py --headful & read; kill -9 $! '' returned non-zero exit status 255.

The sequence insert --headful is wrong ?  ... has to be before the -f argument

There should be an additional error message in the output before that. If not, try executing the exact ssh command manually and see what it sayd.


Bug: Ec2 runner

When I try to use the ec2 runner I do get following error message in the step-function.
"error": {
    "Error": "Ec2.Ec2Exception",
    "Cause": "The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances. (Service: Ec2, Status Code: 403, Request ID: 0ed21094-6fec-467b-bc8f-777207682f73)"
  },

Added this to my cdk code ...
    new iam.CfnServiceLinkedRole(this, 'spot-instance-service-role', {
      awsServiceName: 'spot.amazonaws.com',
    });

another solution is to use the cli
aws iam create-service-linked-role --aws-service-name spot.amazonaws.com

I guess that would be worth to be documented in the readme...


Trading platforms

Would be great to have the trading platforms on BlueAsset, at least Binance, Kraken and Coinbase for now.

Would be great to have the trading platforms on BlueAsset, at least Binance, Kraken and Coinbase for now.

Did that already ;)

Oh, but there is an issue
platforms: asset.contract_address needs to be platforms

Nvm, it's correct, platforms contains the contract addresses for the different platforms.


Update tf to 2.6.0  (#452)

I think the modification is incomplete

@shiyingjin Please review this PR, especially the struct of bazel project files.

bors r+

bors retry

bors retry

bors r+

bors retry

bors r+

bors retry


fix private messages command

This fixes an issue where private messages would always use the other person's name instead of the sender of the message. The type of message is checked and if it is an outgoing private message the local player name is used instead.

Been a little swamped recently. I'll get this merged and pushed out to an update this weekend.


feat: add NullCount and DataSize to datablock statistics

The statistics here is different from arrow array statistics.
One way to think about the concept here is that the array statistics are logical statistics and datablock statistics are physical statistics
It is data type agnostic and it aims to facilitate encoding selection and to provide a centralized calculation of encoding parameter

Codecov Report
Attention: Patch coverage is 80.18018% with 88 lines in your changes missing coverage. Please review.

Project coverage is 78.85%. Comparing base (73ab2b5) to head (71667ff).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

rust/lance-encoding/src/statistics.rs
79.03%
50 Missing and 2 partials :warning:

rust/lance-encoding/src/data.rs
83.45%
23 Missing :warning:

rust/lance-encoding/src/encodings/physical/fsst.rs
0.00%
8 Missing :warning:

...t/lance-encoding/src/encodings/physical/bitpack.rs
50.00%
2 Missing :warning:

...-encoding/src/encodings/physical/block_compress.rs
0.00%
2 Missing :warning:

...ust/lance-encoding/src/encodings/logical/binary.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##             main    #2986    +/-   ##
========================================
  Coverage   78.84%   78.85%
========================================
  Files         236      237     +1
  Lines       73552    73995   +443
  Branches    73552    73995   +443
========================================
+ Hits        57995    58348   +353
- Misses      12550    12631    +81
- Partials     3007     3016     +9

Flag
Coverage Δ

unittests
78.85% <80.18%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


DEP Enrolled Machines that cannot Escrow

"[WARNING] FileVault key was generated, but escrow cannot be confirmed. Please verify that the redirection profile is installed and the Mac is connected to the internet."
Occasionally receiving this message. The drive is fully encrypted and running either 10.12.6 or at least 10.13.4.
On machines that are User Initiated Enrollment / Quick-Added to our Jamf Pro environment I am able to remove the mdm profile and re-enroll via sudo jamf removeMDMprofile followed sudo jamf mdm. The policy then runs without issue and updates in our Jamf Pro environment.
However, if a computer is enrolled in DEP the issue persists even after the removal and re-addition of the configuration profiles. I am attempting to see if the drive being unencrypted and encrypted again resolves the issue but the device I am testing this with has not finished that process. Also posting to Jamfnation in case.

This was an Issue with a Jamf configuration profile conflict.
Units running High Sierra and Newer can simply check the box to Escrow FileVault Recovery Keys.
Units running Sierra and older need to have a separate Security and Privacy payload, as well as a FileVault Recovery Key Re-Direction payload.


Cannot load runtime for 4.6

Hey folks,
I get following exception when trying to load MD generated on 4.6+
Diagnostics.Runtime.ClrDiagnosticsException: This runtime is not initialized and contains no data.
   at Microsoft.Diagnostics.Runtime.RuntimeBase..ctor(DataTargetImpl dataTarget, DacLibrary lib)
   at Microsoft.Diagnostics.Runtime.Desktop.LegacyRuntime..ctor(DataTargetImpl dt, DacLibrary lib, DesktopVersion version, Int32 minor)
   at Microsoft.Diagnostics.Runtime.DataTargetImpl.CreateRuntime(String dacFilename)

Example is 4.6.1085 mscordacwks.dll version, but it seems to take place for all 4.6 =\
What steps should I take to help you overcome the behavior ?
Thanks.

It looks like it picks the wrong runtime. I had that problem in some older version of this library but thought it had already been fixed. Did you build the library from source or used some prebuilt version, if so which?

Hi @weltkante,
Thanks for looking in to this request :)
Referenced assembly seems to be outdated indeed (0.8.25 modified in January, 2015).
I`ll try to use a newer version, and will let you know the results.
Thanks again.

Hi @weltkante,
Using a newer runtime did the trick, thanks !


comma and period key are broken on my macbook help

i downloaded this software hoping i could just swap my comma and period keys with a different key maybe ; and \ but i  was not able to figure out the software please someone thats is smarter than me helpe me out

Please use new setting by this private.xml:
https://raw.githubusercontent.com/tekezo/Files/master/Karabiner/private.broken_keyboard_7/private.xml
How to use private.xml:
https://pqrs.org/osx/karabiner/document.html#privatexml

hahah thank you soooooooo much!!!!!!! sweet mother of god


Positional fields for Records should be indexed at 1 not 0

This would conform with the recent spec update to Records: https://github.com/dart-lang/language/blob/master/accepted/future-releases/records/records-feature-specification.md#120
FYI @derekxu16 @bkonyi

I think this should be a P1 for beta 2 given it's such a big API change

The change will probably land today.
https://dart-review.googlesource.com/c/sdk/+/284722


Fixes #29: Move lib code from cmd/app/kubernets_exec.go to pkg

Fixes #29: Move lib code from cmd/app/kubernets_exec.go to pkg

Moved code to pkg/helm, pkg/config, pkg/kubernetes
Make functions public
Updated all references

Signed-off-by: Markus Hartmann<EMAIL_ADDRESS>
Description

Motivation and Context

[ ] I have raised an issue to propose this change (required)

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I've read the CONTRIBUTION guide
[ ] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

TODO

[x] revert substitution of kubectl in comments

You "mentioned it already" where? Please get your PR fixed up and ping me when you're ready for review.

In the PR description. I will fix it no problem.

@alexellis fixed the issues and aliased the package. Change the PR from WIP to "Ready for review"

Please tell me if the change is wanted and needed. I need to make the PR and get all new changes from master, because I'm changing everything. So maybe we can synchronize it. I will get an okay and 15 minutes time to make the PR and somebody will merge it after that.

@alexellis I fixed the issues, rebased and added the currently added or changed apps.

@alexellis I think we can close this PR, because you merged an another implementation already.


Friction per body?

Hi,
I'm trying to create multiple bodies in the environment with differing friction coefficients. However, I couldn't find anywhere how to do this. It seems that most examples have a global friction coefficient of 0.6 but no difference across bodies.
I'd appreciate any thoughts on this. Thanks.

You're quite right - we only support friction for the whole scene.  Agreed it would be nice to have!
Adding per-collider friction in the config and plumbing it through would be a pretty small PR  I've marked it as a good issue for anyone who wants to help - otherwise we'll do this in one of the upcoming releases.

#59

Thanks for the PR! Each body (collider) may have some friction (and restitution) coefficient. For a contact, the two friction coefficients often get combined to get a 'combined friction'. You may want to make it more clear in your PR.

@erwincoumans Aha, that makes sense.

For a contact, the two friction coefficients often get combined to get a 'combined friction'.

Interesting. The global friction coefficient was the only thing being multiplied to impulse in _collide(): https://github.com/google/brax/blob/464aff88bed7c6b805a2397ef9c8f33de66be8b9/brax/physics/colliders.py#L518
So with the per-body friction/restitution scenario, I'll want to add the friction coefficients into a shared number instead? E.g. in box-plane collision, friction = friction(box) + friction(plane) and apply that to L518 above.

hi,
you probably know it already and/or it is not directly related to this issue, but at least a nice video :)
https://www.youtube.com/watch?v=CfJ074h9K8s


Added blackbox integration test.

This test uses an old fedora 34 repo supplied by @tdawson and simple environment, view  based on eln and workload based on bash package as defined in test_input. It runs all of the parts of feedback pipeline as defined in it's __main__ entrypoint. Then it compares the subset of results that are  in json to ones already stored in test_ouptut

Hey, thanks! Couple things:
Any reason you're not using the existing test_configs folder? You don't need to add test_input/configs/*.
You probably didn't want to include all the test_output/*?

Ah, I see. You remove all _static,*.html, *.txt and compare it to your directory.
That's a very interesting approach I'd advise against, because it feels very fragile and many changes will require changing all of the files in test_output. Even adding one data file or adding one test config will break the tests.
What I was hoping for was a test targetting specific pieces of the output such as

a list of packages in a workload
a list of packages in a view, including buildroot
... and just those, as data extracted from the output files, with a reference. That way adding anything to the output or changing the format of the files slightly won't fail the tests.

Using Troy's repo with Fedora 24 (a dead release which no longer gets updates) ensures we get consistent data over time.
Does that make sense?

Also Pytest is great for unit testing, not really for blackbox testing. I'd run it in a command line as described in README and then had something look at the output. This way you won't have to basically rewrite the main function to make it work within Pytest.

To be clear, I'm happy you're contributing, please don't feel discouraged, I'm here to support/help you.
A few pointers... if you look at the github workflow yaml, you'll see it:

runs on pull-requests
executes Content Resolver with the test configs - this needs to be updated with --dev-buildroot
runs pytest

So when writing tests, you already start with a directory (output) full of results. So all you need to do is to look at the results and test those.
You could add this to your tests:
def load_data(path):
    with open(path, 'r') as file:
        data = json.load(file)
    return data

And then load one workload:
workload_data = load_data("workload--bash--base-eln--repo-eln--aarch64.json")

... then, for example, get a list of added packages:
added_packages = workload_data["data"]["pkg_added_ids"]

... and compare that with a reference which you can just have in the script itself. It's not that long. This specific workload has:
...
"pkg_added_ids": [
      "ncurses-base-6.3-3.20220501.eln120.noarch",
      "ncurses-libs-6.3-3.20220501.eln120.aarch64",
      "glibc-2.36.9000-8.fc38.aarch64",
      "glibc-common-2.36.9000-8.fc38.aarch64",
      "basesystem-11-14.eln120.noarch",
      "bash-5.1.16-4.eln121.aarch64",
      "glibc-minimal-langpack-2.36.9000-8.fc38.aarch64",
      "tzdata-2022d-1.eln121.noarch",
      "filesystem-3.18-2.eln121.aarch64",
      "setup-2.14.2-1.eln121.noarch",
      "libgcc-12.2.1-2.eln121.aarch64"
    ],
...

This way you can target specific things, which:

makes the tests more focused
makes the tests less fragile, because it won't fail with irrelevant changes in the output

If you use the repo Troy added (Fedora 34), the results will be always the same. Let me know if you want me to walk you through the config structure, it's not complicated but can be complex if you look at it the first time.

Oh and to run the same thing locally, you can just add test.sh with something like:
./feedback_pipeline.py --dev-buildroot --dnf-cache-dir /dnf_cachedir test_configs output
pytest

@asamalik I still really like the idea of thorough comparisons of json files.
I.e. one of the things a good test should do is to fail once we start changing things.
If the repo that Troy added is as stable as we want it to be, this shouldn't be a problem.
I looked the files and I don't see a place where irrelevant changes in the output would be happening.
Ok, apart from the fact the lists are unsorted, but I account for that.
Other thing, if we are running tests, they should be self-contained.  I really don't want to rely that
there exists a specific folder with contents of a specific previous run.
But I agree, that with a test like this, it shouldn't fail if we add unrelated new files,
so I only check that the files I have in test_data/*/output have counterparts in the output
with same content.

In my opinion tests should fail when we break things not when we change things. For example adding information to a file shouldn't fail a test.
Please don't re-run Content Resolver for every single test. For example, it pulls hundreds of MB of repodata with every run. If we need to run it with different sets of configs to test different things, then sure. But not as a rule of thumb.


Fix extraction sync build

@wtrocki I have needed to add a lot of classes back because of the interdependencies

@danielpassos Thank you for helping. I will merge this and continue improvements on the other branch.


Improve Array.wrap in ActiveSupport

This change better reflects the return value of Array.wrap.
It handles the three cases outlined in the original code:
https://github.com/rails/rails/blob/ced86070009881362446b5dbbaa36bde36c64b6a/activesupport/lib/active_support/core_ext/array/wrap.rb#L39-L47

Array.wrap(nil) #=> []
Array.wrap([1, 2]) #=> [1, 2]
Array.wrap("string") #=> ["string"]

I used the RBS code for Array(...) as inspiration:
https://github.com/ruby/rbs/blob/8afce66c2a9a5e0919af9671a715e9f126481938/core/kernel.rbs#L442-L444

/merge

Array.wrap has been implemented since 6.0 and the implementation has not changed for more than 10 years.
Signatures that have not changed from version to version are appropriate to be written at https://github.com/ruby/gem_rbs_collection/blob/main/gems/activesupport/6.0/activesupport.rbs.
(Sorry for the lack of clarity.)

Oh, that is definitely good to know. I didn't quite know how all the files combined together in the end. I've moved it to the suggested file.
I wasn't quite sure of its location within that file. I'd be happy to move it to a better place within that file if you want.

Thanks for the review @ksss

/merge


Allow heroicon names containing "-"

In #44 I fixed the render method for heroicons to work with strings. Before the names of the icons were atoms and the dashes in their names were replaced with underscores, but since we're using strings now there is no reason to use underscores.
This PR uses String.replace to replace all "-" with "_" before calling the function which makes the names from heroicons.com work out of the box, but icon names with underscores should keep working.
Edit:
Regarding the atoms existing in the last PR

I just assumed they were since module names are atoms too, and it seems to work (I tested it with a project that uses a lot of different icons and they all showed up correctly using the new syntax for render).

Function names do not count as atoms. I think they all exist because they are created in the generator.

Nice, makes sense. Can you add a test to heroicons_test.exs?

Yeah, sure!


Placeholder that verify permission based on given world context

Taken from lucko/LuckPerms#838

It's possible to implement a PlaceHolder that verify permission giving a specific World context?
Example: %luckperms_check_permission_world%
I'm building a DeluxeMenu and this would make possible to hide some stuff based on permission that players may have multiple times in different worlds context, every permission in every world may be equal but it means different things for my logic on this menu that I'm building! Hence the need for World context placeholder!

There's no easy way to accept more than one argument within a single placeholder string.
I don't really like the idea of just adding more delimiters. :/

cc @hsombini


Allow batches to group ops together

AB#3643
How contribute to this repo.
Guidelines for Pull Requests.
Description
With chunking and compression, the next throttling limit that will be hit is number of ops being sent. With compression, a large number of empty messages could be sent to the service for reserving sequence numbers.
This change will allow for batches to be grouped together into a single op to be sent to the service. For example:

5 ops are sent in batch
Ops are grouped together under sequenceNumber 1 and sent to service
After un-grouping, all the ops will have sequenceNumber 1
Client sequence numbers will be assigned when un-grouping and can be used to determine order when the sequenceNumbers are equal

As called out below, this feature has some changes in expectations around ops and their potential structure.

Breaking change
The IContainerRuntimeOptions.enableGroupedBatching option has been added to the container runtime layer and is off by default. This option will group all batch messages under a new "grouped" message to be sent to the service. Upon receiving this new "grouped" message, the batch messages will be extracted and given the sequence number of the parent "grouped" message.
Upon enabling this option, if any issues arise, use the Fluid.ContainerRuntime.DisableGroupedBatching feature flag to disable at runtime.
This option will change a couple of expectations around message structure and runtime layer expectations. Only enable this option after testing and verifying that the following expectation changes won't have any effects:

batch messages observed at the runtime layer will not match messages seen at the loader layer
messages within the same batch will have the same sequence number
client sequence numbers on batch messages can only be used to order messages with the same sequenceNumber
requires all ops to be processed by runtime layer (version "2.0.0-internal.1.2.0" or later https://github.com/microsoft/FluidFramework/pull/11832)

Noted test failures with feature turned on

back compat with an old assert in merge-tree 0x030. This was removed in v2int 3.0 by https://github.com/microsoft/FluidFramework/pull/13703
SharedTree EditManager (called out in doc)

There are some test failures for assert code 0x030. This was removed in v2int 3.0 by PR#13703.
The assert tests that the sequence number is always increasing, which is not true for this prototype.

There are some test failures for assert code 0x030. This was removed in v2int 3.0 by PR#13703. The assert tests that the sequence number is always increasing, which is not true for this prototype.

Can we patch code (change from > to >=) to see if it's the only problem / see what's hiding behind it?
The other alternative is to move to next branch, but given that all the changes are in runtime, I'd not do it (feels like if we take this route, we can ship them dark sooner by having in main)

@kian-thompson can you try adjusting https://github.com/microsoft/FluidFramework/blob/main/packages/test/test-end-to-end-tests/src/test/messageSize.spec.ts#L321 to have 10k messages and enable this feature in the runtime configuration of that test? Without the feature, the test will surely fail. When it succeeds, it is definitive proof of the value added by the feature.

I like charts in description. Can it make it into some readme.md in the repo as part of this change (or follow up)?


Cannot read property 'split' of undefined - Atom

[Enter steps to reproduce:]

...
...

Atom: 1.24.1 x64
Electron: 1.6.16
OS: Ubuntu 16.04.4
Thrown From: platformio-atom-ide-terminal package 2.8.1
Stack Trace
Uncaught TypeError: Cannot read property 'split' of undefined
At /home/kaustubh/.atom/packages/platformio-atom-ide-terminal/lib/status-bar.coffee:153

TypeError: Cannot read property 'split' of undefined
    at StatusBar.module.exports.StatusBar.createTerminalView (/packages/platformio-atom-ide-terminal/lib/status-bar.coffee:153:26)
    at StatusBar.module.exports.StatusBar.newTerminalView (/packages/platformio-atom-ide-terminal/lib/status-bar.coffee:293:24)
    at /packages/atom-pdf-view/node_modules/space-pen/lib/space-pen.js:220:36)
    at HTMLElement.dispatch (/packages/atom-pdf-view/node_modules/jquery/dist/jquery.js:4435:9)
    at HTMLElement.elemData.handle (/packages/atom-pdf-view/node_modules/jquery/dist/jquery.js:4121:28)

Commands

Non-Core Packages
file-icons 2.1.3
atom-ide-ui 0.3.2
atom-material-syntax 1.0.6
atom-material-ui 2.0.4
Atom-MD-Icon undefined
pdf-view 0.57.0
pigments 0.40.2
autocomplete-emojis 2.5.0
git-time-machine 1.5.9
minimap 4.27.1
platformio-ide-terminal 2.8.1

Please retest again with platformio-atom-ide-terminal 2.9.0.
These type issues all so far seem fixed with this release due to using node-pty-prebuilt instead unmaintained and outdated pty.js


Add AMI for Seoul Region(ap-northeast-2)

Hi folks,
I add AMI information for the Seoul Region (ap-northeast-2).
Please merge this PR.
Thanks a lot.

@sebsto Hello. Could you review this PR and merge?

It doesn't look like anyone is maintaining this code base anymore :\


Fix: Update phpunit/phpunit

This PR

[x] updates phpunit/phpunit

💁 For reference, see https://github.com/sebastianbergmann/phpunit/compare/4.8.21...4.8.24.

:+1:

Thank you, @zcuric!


MAINT: pre-commit fix and master->main

This PR

[x] migrates from master to main
[x] fixes various maintenance items.

@DrDrij all the npm builds are failing on the testing side of things.
Would you have time to take a look. I think there are a LOT of old versions.


pipenv install output should not show paths that do not exist

When running pipenv install, I see the following output:
⊙  pipenv install                                                                                Julian@Macnetic ●
Warning: Your Pipfile requires python_version pypy, but you are using 2.7.13 (/Users/Julian/L/A/v/M/bin/python).
...

But that path is clearly the truncated version of some real path (which I can make an educated guess is ~/Library/Application\ Support/virtualenvs/<myapp>/bin/python), but it's unhelpful to show an artificially truncated path.

Thanks for the feedback.  This is quite a common convention and I don't believe we are interested in changing it at the moment -- it's a bit less overwhelming from an 'overload you with text'.  We are open to changing it, but not just yet.  If we continue to hear back about this being a negative user experience we will revisit
Thanks again!

FWIW I've never seen anything else do this :), but fair enough, response is still appreciated.

I think it’s inspired by the fish shell path shortener but windows also shortens paths for horizontal space management


OPCN3

The update by the aphasense firm of its OPC-N2 sensor to N3 causes that the library can no longer be used in new projects have any update available for the new sensor ... the user marlon360 (https://github.com/marlon360/opcn3-arduino) recently published a library in this regard but lacks documentation for use or examples

Contact marlon360 and publish a first version of the library for arduino Mega or UNO. I just tried it with a Mega and except for some details that are not understandable at the start it seems to be operating correctly!


Environment Variable is not working on VITE 5.0.12

Describe the bug
Please help !! I still cannot access the variables. The .env file is in the root and with preflix. I tried VITE_ and REACT_APP. VITE 5.1

What is wrong???? I can not understand. It is a brand new installation of react + vite.
Reproduction
No need
Steps to reproduce
npm create vite@latest boomerango
√  react
√<EMAIL_ADDRESS>√ Select a variant: » JavaScript
npm install
npm run dev
Port 5173 is in use, trying another one...
VITE v5.0.12  ready in 333 ms
System Info
Windows 10, Chrome and Opera

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It seems that the issue cannot be reproduced. Have you customized the envPrefix field in the vite configuration file?
https://stackblitz.com/edit/vitejs-vite-nuxaf5?file=src%2FApp.css

It seems that the issue cannot be reproduced. Have you customized the envPrefix field in the vite configuration file?
https://stackblitz.com/edit/vitejs-vite-nuxaf5?file=src%2FApp.css

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
// https://vitejs.dev/config/
export default defineConfig({
plugins: [react()],
})

It seems that the issue cannot be reproduced. Have you customized the envPrefix field in the vite configuration file?
https://stackblitz.com/edit/vitejs-vite-nuxaf5?file=src%2FApp.css

Very interesting @XiSenao - I saw your code and all pages are exactly the same as mine. However, the code works in your Virtual environment but not local in my visual studio code software.

You can try calling loadEnv in your environment to check if the value is obtained correctly.
import { loadEnv } from 'vite';
console.log(await loadEnv('development', process.cwd(), ['VITE_']));

The implementation logic is not complicated. If you find any abnormal phenomena, you can easily debug it, and the truth will soon come out.

I figured out the problem. You cannot create the .env file by command line. It needs to be created by left click of the mouse. Somehow the .env got corrupted by command line.


Enable the send email option when user don't receive any confirmation email

After the sign up process don't receive any confirmation email, the user must be able to request for a send email back again. Also is very important to tell him that the mail could be under the spam section.

[x] Create content ES & EN @ldrojas
[ ] Button placement design @murillojorge
[ ] Create dialog box

Steps to test:

Go to sign up section
Sign up
Request for send email again

Own: @steph222
Sup: @leisterfrancisco

EN: "We sent you a confirmation email to your inbox. If you can't find it, please check your spam folder. If you still don't find it, you can [ask for another one]." (link to -ask for another email-)
ES: "Te enviamos un correo de confirmación. Si no lo puedes encontrar, revisa tu carpeta de spam. Si todavía no lo encuentras, puedes [solicitar otro correo]." (link to -ask for another email-)

We'll use a banner. https://material.io/components/banners#anatomy
Component can be found here: https://zpl.io/awz9z6n
Usemos el texto:
EN: "We sent you a confirmation email to your inbox. If you can't find it, please check your spam folder. If you still don't find it, you can resend it."
ES: "Te enviamos un correo de confirmación. Si no lo puedes encontrar, revisa tu carpeta de spam. Si todavía no lo encuentras, puedes reenviarlo."
Botón: "Resend", "Reenviar"


Pin the requests package to the latest version

In this way, dependabot will start updating the requests package.
As a side effect, this could fix #1932.
Checklist

[ ] Type annotations added to new functions
[ ] Docs added to functions touched in main classes
[x] Dry-run produced the expected results
[ ] The to-be-announced tag added if this is worth announcing

With >= it means we were already using the latest version, weren't we?

With >= it means we were already using the latest version, weren't we?

Yes, but this is when doing a fresh installation. If the environment has an older version installed (in our case not older than 2.20.0), you will get "requirement already satisfied".


Use TBB's concurrent queue implementation

TBB is a C++ library for multithreading. Currently we do use it in the repo, but only indirectly: gcc uses it as its backend for the STL parallel algorithms, so you need it on Linux if you actually want the algorithms to run in parallel. The thing is that you have to remember to install it manually. It would be easier to just have it installed with vcpkg along with the other dependencies. This does mean that it would therefore become a dependency for Windows too, but it's not a big one (< 2MiB on my machine). The other advantage of making TBB a requirement is that we can make use of some of its features. Notably, it contains threadsafe versions of various containers, which, aside from being safer than doing the locking yourself, are also often faster, so we could use these in many places in the code base (#159). Currently the CPU usage is poor, which might be due to lock contention (#80) and in that case, using TBB's containers would likely help.
This PR makes TBB a hard requirement and integrates it with vcpkg. I also replaced the custom ThreadsafeQueue implementation with tbb::concurrent_queue and removed the former from the code base (fixes #151).
The motivation for this PR was that I was getting failures for the ThreadsafeQueue tests on macOS runners. After looking at the tests, it seems that the problem was probably just that the tests relied on things happening within a certain timeframe (eww), but rather than trying to fix the tests, I thought it was better just to rip this class out altogether as it was on my hit list anyway.

@jamesturner246 Yep. It will behave in exactly the same way.

TBB is Intel's Threading Building Blocks library: https://github.com/oneapi-src/oneTBB
It basically just provides a bunch of useful bits for multithreaded applications, including tools for parallelising work and threadsafe containers (which I'm using here). Newer versions of the C++ standard include parallelised versions of common algorithms (e.g. sort) and gcc's implementation just uses TBB under the hood, so we need it for that anyway, so it kind of makes sense to just have it as a "proper" dependency and then we can use some of the nice features on all platforms.


Yellow Pandas

i had a dream from days gone by

Motivation

Proposed changes

Test

Code:
Result:

needs fix, not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Efficient, Reusable, Not maintainable

looks clean

Sema Reaction: :ok_hand: This code looks good | Sema Tags: Elegant

Needs fix - not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Unreadable, Inefficient, Inelegant, Not maintainable

Looks good!

Sema Reaction: :ok_hand: This code looks good | Sema Tags: Readable, Elegant, Maintainable

Needs fix. Not maintainable.

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Unreadable, Brittle, Not maintainable

Breaks feature#12.

Sema Tags: Inefficient, Brittle

Thank you for this Soumo
The software contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.

Sema Reaction: :hammer_and_wrench: This code needs a fix

Needs fix not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Efficient, Inelegant, Not reusable, Fault-tolerant, Not maintainable

Needs fix not maintainable.

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Unreadable, Inefficient, Not maintainable

Interesting thoughts.

Sema Reaction: :question: I have a question | Sema Tags: Efficient, Not reusable

Needs fix, not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Readable, Inefficient, Brittle, Not maintainable

Interesting approach, might require some refactoring to support a cleaner extension method but it's a good first try.

Sema Reaction: :ok_hand: This code looks good | Sema Tags: Readable, Secure, Efficient, Inelegant, Not reusable, Maintainable

//Needs Fix, not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Unreadable, Inefficient, Not reusable, Not maintainable

Looks better.

Sema Reaction: :ok_hand: This code looks good | Sema Tags: Secure, Fault-tolerant

Needs fix, not maintainable.

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Inelegant, Fault-tolerant, Not maintainable

It's another comment!

Sema Tags: Not secure, Reusable, Fault-tolerant

Needs fix, not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Secure, Fault-tolerant, Not maintainable

Heres another comment

Sema Tags: Unreadable, Not secure

Needs fix, not maintainable.

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Not secure, Efficient, Reusable, Not maintainable

Hello world.

Sema Tags: Secure, Inelegant, Fault-tolerant

needs fix, not maintainable

Sema Reaction: :hammer_and_wrench: This code needs a fix | Sema Tags: Not reusable, Not maintainable

Let's consolidate that regex into a helper function. We also need to lint this

Sema Tags: Inelegant, Not reusable

catch the error!
Using Hibernate to execute a dynamic SQL statement built with user-controlled input can allow an attacker to modify the statement's meaning or to execute arbitrary SQL commands.

Sema Reaction: :hammer_and_wrench: This code needs a fix

SCR-518

Sema Reaction: :trophy: This code is awesome

SCR-518 ?

Sema Reaction: :question: I have a question

SCR-518 ?

Use arrow functions to close over local variables. It is handy when you need to pass additional data to an event handler.
See Supporting Document for considerations, though.
📄 AirBnB
__
  Summary: :hammer_and_wrench: This code needs a fix

Data should be held in one location, duplicates of that data should be by reference only.
📄 One single source of truth

Sema Reaction: :hammer_and_wrench: This code needs a fix

test 12/14/2021

Logic is the beginning of wisdom, not the end. - Spock
📄 Star Trek
__
  Summary: :hammer_and_wrench: This code needs a fix

Link Source comment
📄 Wiki
__
  Summary: :hammer_and_wrench: This code needs a fix

Wiki Source Comment

Wiki Source Comment
__
  Summary: :hammer_and_wrench: This code needs a fix

Wiki Source Comment 1

test 2/10/2022
__
  Summary: :ok_hand: This code looks good  |  Tags: Readable, Efficient, Not reusable, Fault-tolerant

lsdksdfk;lsdf;l

р

ffsfsf

пвап

ваавыав

test

jjj

test 3/24/2022

test 3/24/2022

test

test my snippets

test 3/31/2022 ex2
__
  Summary: :ok_hand: This code looks good

test comment 4.11.22
__
  Summary: :trophy: This code is awesome  |  Tags: Not secure, Inefficient

test 4/15/2022 5

е

ккк

кккк

test

test
__
  Summary: :trophy: This code is awesome  |  Tags: Fault-tolerant, Maintainable

test 4/20/2022
__
  Summary: :trophy: This code is awesome

test 4/20/2022
__
  Tags: Elegant

sgsgsgsg

fdffdf

wewe

hfh

smoke test 5/17/22 fix
__
  Summary: :hammer_and_wrench: This code needs a fix  |  Tags: Not secure, Efficient, Reusable

test 6/9/2022
__
  Summary: :trophy: This code is awesome

retfsfd

test

test
__
  Tags: Efficient

test
__
  Tags: Efficient

snippet 70
__
  Summary: :trophy: This code is awesome

test 6/24/2022
__
  Summary: :trophy: This code is awesome  |  Tags: Elegant, Not reusable

test 6/24/2022
__
  Summary: :trophy: This code is awesome

test 6/24/2022
__
  Summary: :ok_hand: This code looks good

test 8/1/2022
__
  Summary: :ok_hand: This code looks good  |  Tags: Secure, Inelegant, Fault-tolerant


Camera Imgui Widgets

Here a list of issues referring to camera options:

#55,
#56,
#62,
#86,

Removing CLI option in favor of a dedicated Imgui widgets


SGP40 VOC algorithm

Hello,
I know in the datasheet say sampling rate for VOC algorithm should be 1Hz. In the code I don't see any constraint to increase this to few seconds, and turn off the heater in the meantime. Or that would render the VOC index unusable?

Hi @qati
Indeed the algorithm is tuned for a sampling rate of 1Hz and will behave differently when used with a different sampling rate. See also https://github.com/Sensirion/embedded-sgp/issues/136

Hi @qati
Please have a look here, for the latest version of the Gas Index Algorithm.
https://github.com/Sensirion/gas-index-algorithm
If you decide to change the sampling interval, make sure to also adjust the definition of the sampling interval in the h.file of the algorithm. The setup is tuned for 1Hz. If you decide to use a different sampling interval and turn off the heater in the mean time, then the MOX will react differently and the behavior of the sensor may differ. The algorithm allows to use different sampling interval, but the sensor may react differently to it's environment.
For Sensor Specific details beyond the source code, please contact<EMAIL_ADDRESS>


upgrade prettier to 2.7.1

Thanks. I suggest we can get Dependabot set up to check for new versions of updates, perhaps on a monthly basis so as not to create too many PRs.
Dependabot won't be able to handle Tesseract updates, so some other system would be needed for that.


[CK] Move computations of problem-invariant kernel arguments from Invoker to InvokerFactory

The issue affects host-side performance.
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/a6837540fbbe19d7fc59c114a9f3568ee45308ff/src/solver/conv_hip_implicit_gemm_fwd_xdlops.cpp#L185-L215
MIOpen builds an unique instance of Invoker per each Problem. Therefore arguments like N, C, K are actually constants within each Invoker instance. The computations of these should reside in the InvokerFactory. In addition, this would allow us to avoid copying-by-value the whole instance of ProblemDescription into Invoker (we should only pass the values required to run the kernel(s)).
More info can be found at #216
[Attribution] @junliume @johnny-keker https://github.com/ROCmSoftwarePlatform/MIOpen/labels/performance https://github.com/ROCmSoftwarePlatform/MIOpen/labels/complexity_low https://github.com/ROCmSoftwarePlatform/MIOpen/labels/quality https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_high Proposed assignees: @iq136boy

Update: Please pass only config.index to Invoker. PerformanceConfigHipImplicitGemmFwdXdlops contains std::string which is not used and not free when passed by value.

@atamazov Thanks for the comments. This issue will be addressed.

@iq136boy Has this issue been resolved? Thanks!


The build failed. Fix the build errors and run again.error MSB3552

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/run
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
Imtiaz@ImtiazMacBook ~ % dotnet run
/usr/local/share/dotnet/sdk/6.0.202/Microsoft.Common.CurrentVersion.targets(3261,5): error MSB3552: Resource file "**/*.resx" cannot be found. [/Users/Imtiaz/Imtiaz.csproj]
The build failed. Fix the build errors and run again.
Imtiaz@ImtiazMacBook ~ %

Sorry issue has been solved .It was very minor thing means i have to change the working directory.


Update scalardl and scalardl-audit chart for grafana

Summary

Fixed the dashboard because the scalardb metrics name changed.
Changed datasource name to Prometheus.
Add and fix missing manifest for metrics.

Related

https://github.com/scalar-labs/scalardb/pull/274

@miseyu Thank you!
Since it's a public repo and Helm/K8s-related PRs will be reviewed by external reviewers (like superbrothers),
it would be great if you don't refer to Jira links and explain the PR. (possibly with some backgrounds)

@feeblefakie
Thank you for your understanding.
From now on, we will try to describe the details of the Public repository without referring to the Jira link.
I apologize for the inconvenience. :bow:
Thanks also for assignees and label.
We will try to set them in the future.

@miseyu Thank you! (and sorry for not having really explained it 🙇 )

Changed datasource name to Prometheus.

Has the default name been changed?

@superbrothers
Thank you very much for your confirmation. :bow:
The default was set to Prometheus, so this is a change to match the default.
https://github.com/scalar-labs/helm-charts/pull/24/files#diff-d9909689e538fc7e3038fdde6f743657876a15d1fe4bd338ac666c7242e8aabdR106
Sorry for the confusion. :bow:


Meta issue for discussion of a lazy API

Do we need to provide lazy casting/parsing?  That is, instead of eagerly casting, instead return delegating (and probably memoizing) implementations of the returned type that only cast on reads.
It's not clear that laziness makes sense for the parsing case, but it's possible.  For the cast conversion case, converting lazily would be beneficial when reads are sparse, but harmful when reads are dense.

Pub definitely needs this. It's crucial that we not eagerly fail for pubspecs, because they might be written for newer versions of pub than the version reading the pubspec. We generally want to fail only if we actually need to read a part of the pubspec that's invalid.


raidboss/oopsy: add AMR (work in progress)

This is a work in progress of my own personal Another Mount Rokkon triggers. Largely untested.
I am trying to do this content blind for once (scheduling is also hard, so it might be a little) so please do not correct me or tell me if I'm right or wrong or whatever. I will probably not merge these until I'm done, mostly so that I don't have people trying to give me feedback and spoiling me in ways I don't want to be spoiled.
Feel free to grab any part of this and submit your own PR (that I will not look at) if you think it's a good idea.

I know you've stated you're progging this blind, but it appears you have already progged past the first boss. Do you want the rest of the timeline for it?

I know you've stated you're progging this blind, but it appears you have already progged past the first boss. Do you want the rest of the timeline for it?

Thanks for asking, but at the moment no!

on first boss, during the blue shadow phase (find safespot + stack/spread) it sometimes calls the wrong spot for me. Most times when the first safespot is north, it calls south for me (not sure if this is 100% of times but most of them i would say)

I had yesterday again the case where safespot north got called out as south (and as i saw the boss3 timelines i am sure that i compiled the latest version after the fix)

Just for reference these are the replacements i made in ACT itself for this trigger:

I am trying to do this content blind for once (scheduling is also hard, so it might be a little) so please do not correct me or tell me if I'm right or wrong or whatever. I will probably not merge these until I'm done, mostly so that I don't have people trying to give me feedback and spoiling me in ways I don't want to be spoiled.

Sorry, I know this is awkward but I'm trying to do this blind (and with bad scheduling, we've only gone twice ;;) because I don't get to do that many things blind.  I was trying to put this draft PR up because I was trying to be slightly helpful and didn't want folks to bother duplicating work that I was doing for my own use if they want to grab things that I had done. However, I really don't want feedback on this about things that are wrong. Feel free to write down anything you think is wrong or not working and I'll take a look once we're done and I'm ready to land this.

Sorry for the super delay, but I think this is ready to go.
I took a look through PF strats vaguely and I think the biggest difference is second boss second towers, where we had different strats for if the debuffs were "full mixed" (everybody has two colors) and "half mixed" (some people have two colors some have all the same colors), but it seems like other people maybe have different strats and so I'm not sure what should be called out here.
@xiashtra @Akurosia @valarnin @g0shu Did y'all have any additional feedback about this before I merge it?

Maybe call out if at least 1 person has 3 of the same colored buffs, as from my expirience that is what most groups do (have 2 different strats depending if all player have blue and red buffs or if 3 same colored debuffs are available)
Other than that most of the stuff was working for me when i tried it a few days ago and i did not noticed any major flaw in callouts.

Sorry for the super delay, but I think this is ready to go.
I took a look through PF strats vaguely and I think the biggest difference is second boss second towers, where we had different strats for if the debuffs were "full mixed" (everybody has two colors) and "half mixed" (some people have two colors some have all the same colors), but it seems like other people maybe have different strats and so I'm not sure what should be called out here.
@xiashtra @Akurosia @valarnin @g0shu Did y'all have any additional feedback about this before I merge it?

The PF strat I've seen for Malformed Reincarnation (the final towers) uses the same strat regardless of number of same colored buffs.  This is likely a situation where there's completely different strats floating around.
I'm not sure if there's any remaining issues still present.  I might get a chance to look this weekend.

Maybe call out if at least 1 person has 3 of the same colored buffs, as from my expirience that is what most groups do (have 2 different strats depending if all player have blue and red buffs or if 3 same colored debuffs are available)
Other than that most of the stuff was working for me when i tried it a few days ago and i did not noticed any major flaw in callouts.

FWIW, our strat was something like this: https://raidplan.io/plan/9tVR4vj9kPjgF3PM

if "half-mixed" (i.e. half the group has mixed colors, i.e. some people have all red or blue):

look at your first tower color, go to the quadrant with two towers of that color
no flexing, doesn't matter who is where on that side
"easy mode"

if "full mixed" (i.e. everybody has mixed colors):

go to quadrants with one tower of each color instead
need to flex to make sure you have one of each color in each mixed quadrant
also need to stand opposite the first tower you have

I think there's no way around the place tower -> cross over to inside tower 1 -> outer corner tower 2-> placed tower 3 dance, it's just about where you start.
But I saw https://www.youtube.com/watch?v=TzoNEWbMpQ0#t=7m53s which seems like a different setup that always flexes and gets people on mixed quadrants always

Neither one of these is what I've seen in pf 😬.

Do you have a link to a PF strat?

I'll see if I can find something, but honestly, it's just skipped most of the time.

Neither one of these is what I've seen in pf 😬.

Do you have a link to a PF strat?

This is what I've seen: https://ff14.toolboxgaming.space/?id=938195953989861&preview=1  No adjusts regardless of full- or half-mixed.

Ok, so sounds like a basic strategy that could account for most of this would say something like:

alertText: drop blue, first orange
infoText: (all mixed colors) / (half mixed colors)

or something like this

EDIT: I don't think any strat cares about the color you are dropping, so maybe:

alertText: blue -> blue -> orange (half mixed)

I think that would probably satisfy everyone.

Is there a way to setup the final boss shadow clone mechanic using this simplier strat?
https://www.youtube.com/watch?v=KghjI7xn6X0
It keeps calling out my position wrong regardless of what Role > Stack thing I set.

Could you file a separate issue for this rather than a comment on a pull request that I might lose track of?

Is there a way to setup the final boss shadow clone mechanic using this simpler Strat?

Maybe there's some confusion. What do you think the cactbot strat is doing vs this strat? (Which mechanic specifically do you mean here? I thought you meant soldiers of death, but then you talk about "final arrow mechanic" after, which makes me think that's not true.

Same for the final arrow mechanic, keeps telling me to go to weird places. We use role-based positions for the last one. Tanks South or North, DPS East or West.

Sorry for the confusion. It doesn't tell you where to go. It tells you what tether you have and who should be together.

Sorry I'm new to github so I don't know exactly where to post things. I also don't know really how to explain it other than how I already have. I'll try though.
In the video the first part I was talking about starts at 2:55. I'm either S or W and if there's any adjustment, the healer and other DPS swaps. Oftentimes it tells me to pair with the wrong person or I don't even know what info it's trying to give because I don't know the strat that it's trying to use at all. The bait callout for tether doesn't work either, I think it's assuming I'm somewhere else.
For the second part 5:07, soldiers of death. It's telling me to go where the tanks are supposed to go. We do role based regardless of tethers, So tanks would take south and north safe spots, DPS on east and west. I'm always with the other DPS so it shouldn't even be telling me any info regarding who to be with, just where to go.

In general, cactbot isn't assuming any strat at all, and is just telling you what you have / what other people have, if that helps.

In the video the first part I was talking about starts at 2:55. I'm either S or E and if there's any adjustment, the healer and other DPS swaps. Oftentimes it tells me to pair with the wrong person or I don't even know what info it's trying to give because I don't know the strat that it's trying to use at all. The bait callout for tether doesn't work either, I think it's assuming I'm somewhere else.

Yeah, I wonder if the callout is just confusing. In this case, it tells you who has the same thing you do (in case you are flexing). So if you and somebody else have tether, it'll say "Back Tether (w/Somebody Else)" or something. This one (for whatever reason) never got switched over to use the melee/roles logic. It's similar to triggers  earlier where it will tell you that you have blue tower or spread w/ another player. That person is not the person you stack with, but the person who has the same thing you do.
What isn't working about the bait tether?

For the second part 5:07, soldiers of death. It's telling me to go where the tanks are supposed to go.

This call doesn't tell you to go anywhere, it's trying to tell you what you have. It will say "Left (roles together)" meaning you have the left safe tether and you should be on the cardinal with your role partner. You can use this info with any pre-positioning.

Ahh I see I had assumed "AMR Moko Soldiers of Death Blue Add" was a safespot callout, since he has 8 spawns and none of them are NESW cardinals to match the call. His arrow distance is also dictated by which side he spawns in, N/S always shoots short, E/W always shoots long. So you can often find the safespots as soon as he spawns, I imagine cactbot could figure this out for you easier and be able to call safespots?
Tethers on the last mechanic definitely aren't random, or in the very least the angles it gives you aren't.  you can always 100% pair with your fellow DPS/Support, find which of your two safespots is or isn't safe and go to it. You'll always be in a pair that can show your safe angle towards mid after facing away from each other. This is why I was confused that cactbot wasn't telling me which direction my second cleave would face, since that's really the only info you might miss after you've found your safespot.
For the bait tether I am just reading it wrong. I just noticed it's telling you both mechanics on your side in reverse order depending on what you get, but I might just edit mine to only say where tether needs to be and obviously I'm the opposite of it if I'm not tether. We'll be doing a few clears tonight and I'll keep an eye on it.

I am nearly positive this is not true. We were doing roles together by default and there were a couple of times where we had to flex because the two dps both had lefts and the tank and healer both had rights. In true ffxiv rng, mooostly it was roles but there were a couple where it wasn't.

Soldiers of Death tethers should always be support pair and dps pair, no flex needed.  I suppose it might scramble if there's a badly timed death, like some other mechanics do, but for a clean run, role pairs should always work.

Soldiers of Death tethers should always be support pair and dps pair, no flex needed. I suppose it might scramble if there's a badly timed death, like some other mechanics do, but for a clean run, role pairs should always work.

Oh, I see what the confusion is on my part. Our healer and dps swapped roles midway through, but we continued to call it airquotes "roles" stacks for our original jobs and I forgot about the airquotes part. The blue add having a set long and short distance checks out from video, so I'll add that in.


DEPS.xwalk: Roll chromium-crosswalk (ed0646f -> 9a9776f)

9a9776f Merge pull request #231 from huningxin/crosswalk-11
1fd40ce Allow universal access from file if flag is set and url is file scheme.

To fix https://crosswalk-project.org/jira/browse/XWALK-3344. @rakuco , please take a look. Thanks.


model gives issue when more contents are added

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'model'
Click on 'open model'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.

Should have close icon
content should be inside model with scrollbar
footer should be visible.

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
I would be willing to submit a PR to fix this issue
[ ] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No

Error screenshot :-


Proposal for separating cortex-m into smaller parts

Summary
The cortex-m crate provides facilities for using peripherals and special
instructions on the ARM Cortex-M series. This makes it useful in a wide range of
embedded applications. However, the crate also does a few other things that
restrict its applicability. I would like to propose finding a seam in the crate,
between its low-level generally-applicable bits and its higher-level bits, and
separating it into two.
Context
Most Rust applications using the cortex-m crate are what I would call
monolithic applications: they consist of a single program, compiled/linked
together, and do not use memory protection to isolate components, nor the
processor's privileged/unprivileged distinction to isolate a kernel.
There are (for the sake of this discussion) three other kinds of Cortex-M
applications, however: those that use limited memory protection and privilege
within a single linked application (FreeRTOS CM3_MPU port); those that isolate
a kernel and run drivers in privileged mode (Tock; uCLinux and programs running
atop it); and those that use memory protection to run drivers in unprivileged
mode (so-called "multiserver" systems). The current APIs aren't well suited for
any of these applications.
As an example, consider issue #223. The memory safety properties of the current
cortex-m API rely on critical sections, and they turn out to be void in
unprivileged mode -- because the library assumes a particular method of
implementing critical sections.
A taxonomy of cortex-m APIs
I've been thinking about this a lot recently, while using cortex-m in both the
kernel and userland of an isolated multiserver operating system (not yet
released). I see the following broad groups of functionality. Each of these is
probably not a separate crate, to be clear, these are merely categories.
The Universally Relevant
Things that make sense to use in a kernel, in userland, with or without
protection, etc. Stuff in this category should include:

Operations that are reasonable in both privileged and unprivileged mode.
(Note: operations that reliably trap in unprivileged mode are OK. MSR, MRS,
and CPS do not trap and should be exposed only very carefully.)

Operations that do not assume a single linked program (e.g. they must not use
a static to coordinate access to a shared resource).

This list may be really short; even with MPU shenanigans, you cannot make the
peripherals on the Private Peripheral Bus (which is to say, most of those
defined in cortex-m) accessible to unprivileged code.
At first glance, here are some things that belong in this level:

wfi/wfe, probably sev
bkpt
delay, were it correct (see #236)
nop
udf
isb/dsb/dmb
ITM output support (ITM ports can be set to unprivileged)
The user-visible register accessors apsr, lr, pc
Access to the STIR.

Peripheral Register Definitions
The address and layout of memory-mapped peripherals. This information isn't
dangerous to expose to unprivileged code, because direct accesses to PPB
peripherals from unprivileged code won't work. However, a system might
reasonably opt to intercept the MPU or Bus faults and emulate the peripheral.

All peripheral layouts currently named RegisterBlock.
All register access types (W/R proxies and friends if you're using svd2rust).

Handy Algorithms
Pre-built code that implements the "right way" to do certain operations, such as
enabling/disabling the caches or adjusting system handler priority.
Ideally, these would be as widely applicable as possible, so that people don't
keep reinventing the wheel. (Particularly if the wheel is reinvented
incorrectly.) Currently, they contain Concurrency-Model Dependent Bits (below)
in some cases, and are tied to Opinionated Peripheral Access in others (farther
below).
Concurrency-Model Dependent Bits
interrupt::free, CriticalSection, etc. These operations assume a particular
concurrency model, namely

All code is privileged.
Critical sections are imposed by stopping all interrupts.

These assumptions aren't general; the first fails on Tock (userland) or uCLinux,
and the second fails on many real-time systems, which tend to have a few
interrupt priority levels reserved as "never disable" (with attendant safety
restrictions).
Opinionated Peripheral Access
take() and friends. There's a fair amount of surface area in cortex-m
devoted to controlling peripheral access and aliasing. This is useful stuff, but
it only makes sense in monolithic programs, for two reasons:

It relies on the type system for safety. In general, guarantees from the type
system cannot be extended to separate programs.

It relies on static flags for mutual exclusion. In a system containing
multiple separately compiled programs, every program has a taken flag, and
the guarantees rapidly fall apart.

Proposed crate seam
The split that makes the most sense to me has three parts. We can debate names
later; here are placeholder names for the sake of discussion. I'm starting at the
current level of abstraction and working down.

cortex-m-monohal - the Opinionated Peripheral Access and Concurrency-Model
Dependent Bits, which provide abstractions over the actual hardware (i.e.
take() is not a hardware operation) and only make sense in monolithic
programs. This API would be fairly safe (equivalent to the current cortex-m
surface area).

cortex-m-raw - the lower level systemsy bits that are mostly needed if
you're writing a kernel or driver: Register Definitions and Handy Algorithms.
This layer cannot make assumptions about privilege or concurrency model for
correctness. As a result, it's going to have a lot of unsafe API; the
monohal above it can provide safe wrappers. This crate might get pulled into
very strange unprivileged programs that want knowledge of register layouts.

cortex-m-intrinsics - all the Universally Relevant bits for accessing WFI
and the like. This would be as useful in a userland program on uCLinux as it
would be in a kernel. This API would be mostly or entirely safe. (It's
possible that some of the Handy Algorithms wind up here.)

The monohal parts would be implemented in terms of raw and intrinsics. An
application could use monohal and reach into raw for particular things, but
doing so would potentially violate monohal's safety guarantees -- though the
raw bits are likely unsafe so that's not surprising.
Really, I feel like the monohal bits above belong in the cortex-m-rt crate,
along with things like #[exception] and other niceties for writing safe code
that make assumptions about system architecture.
NAME vs name::RegisterBlock
Currently, if you're working in a context where take() doesn't make sense, you
wind up dealing with types named RegisterBlock a lot. This is kind of
unfortunate, because it's verbose -- you need to always partially qualify the
types (gpioa::RegisterBlock, scb::RegisterBlock) to have any idea what's
going on. However, the conveniently named types in the monohal (e.g. SCB) do
not have new() operations, even unsafe ones, for getting an instance. (Yes,
you could do a steal() of the entire peripheral set and chop it down, but that
seems odd.)
This is also an issue because some Handy Algorithms are provided on the NAME
types, and others on the name::RegisterBlock types -- and the former ones are
unavailable to people not using the monohal. (For instance, having a
&scb::RegisterBlock is enough for me to enable the instruction cache, but only
if I'm willing to write the code myself -- the canned algorithm is on SCB.)
I bring this up because, in the split I'm proposing, the Handy Algorithms would
need to get split up in many cases: a reusable core, likely unsafe, that can
operate on the RegisterBlock; and a safer counterpart, using critical sections
and the like, in the monohal.
I would also like to register a vote for distinct names, instead of having a
whole bunch of types named RegisterBlock. ScbRegisters would do in this
case. :-)

Discussion from todays meeting: Probably best to toy around with the idea and see how that would work and if people are motivated to see it through. Also if people are interested in working on this, please speak up.

Briefly discussed this in todays meeting. We might come back to this after the next release.
Unnominating for now.

I would fully support extracting the register definitions into a separate crate.  Register definitions are pretty much fixed by the hardware and the only reason to change them is due to bugs or a new cpu revision (and corresponding SVD from the vendor).  Everything else in the cortex-m crate is essentially open to change for any number of reasons.
When writing very low level code, or when implementing solutions that have very specific requirements (e.g. vector tables, linker scripts, debugging requirements), much of the other stuff that the crate provides either causes problems (even when unused, as compile times are still increased), gets in the way and can cause developer confusion as to which part of the crate can/should be used, or needs working around.
If your first cut at splitting things up a bit was to just extract the register access into a separate crate and make it a dependency, whilst also allowing it to be used directly, that would be awesome.

Discussion from todays meeting: Probably best to toy around with the idea and see how that would work and if people are motivated to see it through. Also if people are interested in working on this, please speak up.

I've just started using rust for embedded and this is something I'm definitely interested in. The current implementation is monolithic and includes much that is not needed or wanted in my project. For many applications it just includes to much extra code, while for many just the registers and other low level code is what they need.

Discussion from todays meeting: Probably best to toy around with the idea and see how that would work and if people are motivated to see it through. Also if people are interested in working on this, please speak up.

I'd be interested in cooking up a prototype if there's interest from upstream. We've been using cortex-m in unprivileged isolated environments for a little over a year now, and just avoiding touching the parts that are unsound there. :-)

I created a for-discussion PR #353 as another alternative to this problem which might be worth also considering.

@cbiffle I agree with all of that.


chore: Update npm run start scripts and documentation

no jira.
This is a quick PR that aims to make npm run start* scripts consistent across Insights frontend applications.

Relates to https://github.com/RedHatInsights/vulnerability-ui/pull/2013

We're currently processing your upload.  This comment will be updated when the results are available.


Add trial user's forms to their new organisation when changing from the trial role

What problem does the pull request solve?
When a user gets their account changed from trial to editor we want to have their forms added to their new organisation. This PR uses a new endpoint on forms-api to update the org for forms with the same creator_id as the trial user who have had their role changed to editor.
Trello card: https://trello.com/c/esvZIXnn
Checklist

[x] I've used the pull request template
[x] I've linked this PR to the relevant issue (if mission work)
[x] I've written unit tests for these changes (if code change)
[ ] I've updated the documentation in (If any documentation requires updating)

[ ] README.md
[ ] Elsewhere (please link)

Woops, looks like I've got a broken test and moved from draft too soon... 😨


Delete from all alt-allele-related tables when deleting alt alleles.

The delete commands hadn't been updated after adding the new alt_allele tables "alt_allele_attrib" and "alt_allele_group".

Coverage increased (+0.28%) to 74.69% when pulling 7be38fa982138d16581ed458289170998c30cc87 on ens-carlos:master into e98487df8f8074c4a25654ca81a363cec0012851 on Ensembl:master.


Add responseName field to clusters in endpoint config

Per spec (Spec <IP_ADDRESS>, <IP_ADDRESS>), the GeneratedCommandList are the commands that in response to another command in AcceptedCommandList
This PR will include a "responseName" in the cluster info in endpoint config, to generate the above attributes correctly.

Minor feedback: the RESPONSE_REF is intended to be a "reliable" reference to the response. RESPONSE_NAME can technically contain gibberish that came from XML, however it was gibberish, so the linking code during the RESPONSE_REF linking would keep that as null.
Do you wish in this case to properly get nothing (for which you would need to not use RESPONSE_NAME, but a RESPONSE_REF link), or you are ok to retrieve gibberish that was typed in the XML and didn't correspond to any real command (which is the case where RESPONSE_NAME would contain gibberish, but RESPONSE_REF would stay null)?

Thanks for the advice, after checking the SQL and the usage, what I really want here is the command id ofr the response
for code gen (https://github.com/project-chip/connectedhomeip/pull/17833)
I updated the code to use the response_ref to lookup for the actual command code, and use the response name as comment in the code. (since the response ref itself is meanful only in zap's scope)

Merge this since it is verified by https://github.com/project-chip/connectedhomeip/pull/17833


Notebook tutorial for FWI

Make a notebook using era5 data to compute the FWI indices, with and without overwintering, in order to compare with https://essd.copernicus.org/articles/12/1823/2020/ or other sources.
I think we could extract the same years and points as in our "era5 can cities" data from the public datasets they provide. But because of the data differences (mean temp vs. temp at noon) we might need to create a new testdata set anyway.
This notebook would also act as a more advances xclim/xarray example and integrated test for the whole FWI submodule.

Include computation of FWI7x, the annual max of the 7-day moving average, known to have a good correlation with the area burned when averaged over a region (Van Oldenborgh et al., 2021).


[meta] wiki page permissions?

Attempted to add my project μsic but i don't think the edit permissions on the wiki are open enough, and afaik there's no PR workflow for wikis.
thanks for the library btw, it works well for my use case :heart:

I'll add it for you. Just give me a short description of the project, please.

@rozap have a description?

Oops, sorry.
It's a tool for learning songs by ear. You can slow down youtube audio without change pitch, and add section annotations.

Added, thanks!


Clustream k-means processing time

Currently, CluStream does a k-means from the microclusters, to generate the final clusters. In the current implementation, this is done in every batch, in the train loop.
This is normal, if we want to evaluate the clusters which are generated by CluStream. However, since k-means is set by default to iterate 1000 times, this generates a scheduling delay in the processing of batches.
To give an example, for a synthetic dataset of 3 features, dense, a socket stream sending ~600 records/sec, and a window of 10 seconds:

each batch is processed between 15 to 20 seconds,
this, in turn, generates at least 10 seconds of delay between the batches, which, obviously, adds up.

My solution would be to process k-means "lazily"; that is, to only process it when we need an assignment to evaluate, in assign. This makes sense for two reasons:

normally, assignment would only be on demand, and not in every loop,
since assignment is a different stream thread, it can be parallelised (i.e., performed at the same time as the train loop).

I suspect the same observation might hold for StreamKM++, although I'm not sure.

Some benchmarks on the Cover Type dataset (54 features, sparse), for k=10 clusters, using 1000 microclusters and an initial buffer of 10,000. The generator was the socket streamer.
First experiment: vary the batch window, keep the generator at 1000 instance/sec theoretical, which is around 500-600 /sec in practice. Results:

window
batch time
max delay
k-means time

1s
4s
1h
2s

5s
16s
37m
2s

10s
43s
1.5h
2s

30s
2.3m
2h
2s

60s
3.5m
1.8h
2s

It can be seen that increasing the window does not help. Bigger window means higher processing time so the delay is still there. This suggests that the batch time is due to the data size.
Second experiment: vary the throughput in the socket, keep window at 10seconds. Results:

thoughput
batch time
max delay
k-means time

100/sec
9s
0
1s

250/sec
19s
32m
2s

500/sec
27s
46m
2s

1000/sec
43s
1.5h
2s

After all, it seems that the k-means type is not such a big factor - it is likely that the update of microclusters has an issue (most likely, cluster assignment).


simulation Gravity and bouniness

when a rigidbody (give  material bouniness, something like 0.8f ),   the body down to the floor because of gravity,    the body up and down even when the body has litter higher than floor.
As my experience， and in PhyX, the body will be still instead of dithering.

Hello,
I am sorry but I did not really understand what is going on. Can you please explain precisely what happens ?

hi,
I cannot reappear the problem. when it reappear,  I try to describe in details.

I am closing this issue because it is quite old and it might already be fixed in the last versions of the library. Feel free to reopen if that's not the case


Refactor Tekton interaction in webhook interceptor

Add labels to identify pipelines for cleanup (closes #358)
Refactor Tekton interaction in webhook interceptor

Preparation for #153. That PR will require an extension to the Tekton client (dealing with PipelineRun resources as well).
Tasks:

[x] Updated design documents in docs/design directory or not applicable
[x] Updated user-facing documentation in docs directory or not applicable
[x] Ran tests (e.g. make test) or not applicable
[x] Updated changelog or not applicable

I am a bit confused by the lint error. https://github.com/opendevstack/ods-pipeline/runs/4618181458?check_suite_focus=true complains about unused os imports (without stating the filename). Locally make lint-go works without errors. In GH Actions and locally I have Go 1.17 and golangci-lint 1.41 installed ... ?!

I believe the lining errors were due to some caching issues.
The fix is in https://github.com/opendevstack/ods-pipeline/commit/b756a81734e506a0e4fdc96b47cec72cb40fb688, now merged into this branch as well. However, I am unsure why the issue was not flagged in https://github.com/opendevstack/ods-pipeline/pull/353.


chore(deps): Updated jinja2 from 3.1.4 to 3.1.5

SUMMARY
jinja2 @ 3.1.4  is vulnerable to GHSA-q2x7-8rv6-6q7h and GHSA-gmj6-6f8f-6699 which were addressed with 3.1.5

you'll want to run pip-compile-multi -P jinja2 or CI is going to fail, could also be good to bump the lower bound here -> https://github.com/apache/superset/blob/master/pyproject.toml#L64 .
I just realized that jinja2 isn't listed as a direct dependency in our pyproject.toml though it should be since we use it directly in the package. Guessing we never added it since it's a sub-dependency of Flask and other packages we import.
Since we use it directly, let's add an entry:
# 3.1.4 has a known security vulnerability
"jinja2>=3.1.5",

You'll want to:

add this line to pyproject.toml
run pip-compile-multi -P jinja2
commit and push


Added Horsepower Conversion Calculator

Fixes Issue🛠

Closes #
Description👨💻

In this calculator we can calculate the horsepower of a vehicle. If we have force in Newton and Velocity in m/s we can find out the horsepower.
Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

-[ ]  Tested the results from an already existing online horsepower calculator
-[ ] Manually verified all the results from the formula
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

It was my first time doing open source. It was fun and i was a bit nervous but tried my best to give the best product. Please provide feedback so that i can improve myself and gain experience for Open source more.


[Composer] Update to latest versions add missing tags

https://github.com/composer/composer/releases/tag/2.3.8
https://github.com/composer/composer/releases/tag/2.2.15

both were added yesterday in the automated release data, but that was not
yet triggered today.
https://github.com/endoflife-date/release-data/commit/7f066baa887d8f4fa47bfed428cf821e3f8ff9f5
On Sat, Jul 2, 2022 at 5:09 PM Ömer Fadıl USTA @.***>
wrote:

https://github.com/composer/composer/releases/tag/2.3.8
https://github.com/composer/composer/releases/tag/2.2.15
You can view, comment on, or merge this pull request online at:
https://github.com/endoflife-date/endoflife.date/pull/1377
Commit Summary

f05baf1
https://github.com/endoflife-date/endoflife.date/pull/1377/commits/f05baf18203ba4e1d06bc649fbb5edba6929b1ca
[Composer] Update to latest versions add missing tags

File Changes
(1 file https://github.com/endoflife-date/endoflife.date/pull/1377/files
)

M products/composer.md
https://github.com/endoflife-date/endoflife.date/pull/1377/files#diff-5de6470a70d6287438312dda5d146a7aab628b46ea422422a7216079a9002d5f
(16)

Patch Links:

https://github.com/endoflife-date/endoflife.date/pull/1377.patch
https://github.com/endoflife-date/endoflife.date/pull/1377.diff

—
Reply to this email directly, view it on GitHub
https://github.com/endoflife-date/endoflife.date/pull/1377, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK3OC2CGYVNMDLB7J5X6VLVSBLRXANCNFSM52PGBWXA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Our automation only works on weekdays😁


Do not block on stream server close.

In e2e test, I sometimes see that when cri-containerd is starting, it is killed by health-monitor, and then stuck forever:
Started Kubernetes containerd CRI shim.
time="2018-02-13T02:26:55Z" level=info msg="Run cri-containerd "
time="2018-02-13T02:26:55Z" level=info msg="Start profiling server"
time="2018-02-13T02:26:55Z" level=info msg="Run cri-containerd grpc server on socket "/var/run/cri-containerd.sock""
time="2018-02-13T02:26:55Z" level=info msg="Get image filesystem path "/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs""
I0213 02:26:55.155330    2490 interface.go:360] Looking for default routes with IPv4 addresses
I0213 02:26:55.155351    2490 interface.go:365] Default route transits interface "eth0"
I0213 02:26:55.155458    2490 interface.go:174] Interface eth0 is up
I0213 02:26:55.155516    2490 interface.go:222] Interface "eth0" has 2 addresses :[<IP_ADDRESS>/32 fe80::4001:aff:fe80:5/64].
I0213 02:26:55.155538    2490 interface.go:189] Checking addr  <IP_ADDRESS>/32.
I0213 02:26:55.155548    2490 interface.go:196] IP found <IP_ADDRESS>
I0213 02:26:55.155559    2490 interface.go:228] Found valid IPv4 address <IP_ADDRESS> for interface "eth0".
I0213 02:26:55.155569    2490 interface.go:371] Found active IP <IP_ADDRESS>
time="2018-02-13T02:26:55Z" level=error msg="error updating cni config: Missing CNI default network"
time="2018-02-13T02:26:55Z" level=info msg="Initial CNI setting failed, continue monitoring: Missing CNI default network"
time="2018-02-13T02:26:55Z" level=info msg="Start cri-containerd service"
time="2018-02-13T02:26:55Z" level=info msg="Connect containerd service"
time="2018-02-13T02:26:55Z" level=info msg="Stop cri-containerd service"
time="2018-02-13T02:26:55Z" level=info msg="Start subscribing containerd event"
time="2018-02-13T02:26:55Z" level=info msg="Start recovering state"
time="2018-02-13T02:26:55Z" level=info msg="Start event monitor"
time="2018-02-13T02:26:55Z" level=info msg="Start snapshots syncer"
time="2018-02-13T02:26:55Z" level=info msg="Start streaming server"
time="2018-02-13T02:26:55Z" level=info msg="Start grpc server"
time="2018-02-13T02:26:55Z" level=error msg="Failed to serve grpc request" error="grpc: the server has been stopped"
time="2018-02-13T02:26:55Z" level=info msg="Stop cri-containerd service"
time="2018-02-13T02:26:55Z" level=error msg="Failed to handle event stream" error="rpc error: code = Canceled desc = context canceled"
time="2018-02-13T02:26:55Z" level=info msg="Event monitor stopped"

The reason is that there is a race condition between http.Server.Serve() and http.Server.Close(), which are used by stream server. (The issue https://github.com/golang/go/issues/20239). There is no reliable, race free way to wait for stream server to stop. So we add a timeout here. In most cases, we'll still wait for stream server to stop. However, if we hit the race condition, we'll wait for 2 seconds, throw out an error and continue stopping.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Mark P0 because this causes a lot of test flakes.https://k8s-testgrid.appspot.com/sig-node-containerd#e2e-ubuntu


New release of Gio?

Any plan for a new release, given that https://crates.io/crates/gio still refers to the old repository and some rather broken builds?

See https://github.com/gtk-rs/gtk-rs/milestone/1

Closing it then.


Use separate redis pool

Sidekiq redis pool is capped to the concurrency level, thus we need to initialize our own connection pool for the eventually consistent refresher.

No need to. Sidekiq has internal pool for this kind of tasks, thus processors are note affected.


Gh-1101 Improved the Parquet store add elements operations

Removed aggregation of Edge data twice for both Source and
Destination sorted data.
pre-aggregate the new data when importing form an RDD
removed use of Tuple2 in favour of Pair

Closing while solving conflicts from merging in the latest develop branch

Codecov Report

Merging #1147 into develop will decrease coverage by 0.18%.
The diff coverage is 75.98%.

@@              Coverage Diff              @@
##             develop    #1147      +/-   ##
=============================================
- Coverage      65.05%   64.86%   -0.19%
- Complexity      1314     1322       +8
=============================================
  Files            623      625       +2
  Lines          19334    19381      +47
  Branches        2420     2430      +10
=============================================
- Hits           12577    12571       -6
- Misses          5752     5807      +55
+ Partials        1005     1003       -2

Impacted Files
Coverage Δ
Complexity Δ

...parquetstore/utils/GafferGroupObjectConverter.java
76.92% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../operation/addelements/impl/ExtractKeyFromRow.java
87.5% <ø> (ø)
0 <0> (?)

.../java/uk/gov/gchq/gaffer/commonutil/pair/Pair.java
48.27% <ø> (ø)
7 <0> (ø)
:arrow_down:

.../addelements/impl/AggregateGafferRowsFunction.java
96.22% <100%> (ø)
0 <0> (?)

.../addelements/impl/GenerateIndexForColumnGroup.java
86.88% <100%> (ø)
0 <0> (ø)
:arrow_down:

.../addelements/impl/RDD/AggregateGafferElements.java
100% <100%> (ø)
0 <0> (?)

...n/addelements/impl/RDD/ExtractKeyFromElements.java
100% <100%> (ø)
0 <0> (?)

...ements/handler/ImportJavaRDDOfElementsHandler.java
79.36% <100%> (ø)
0 <0> (?)

.../uk/gov/gchq/gaffer/parquetstore/ParquetStore.java
87.32% <100%> (ø)
0 <0> (ø)
:arrow_down:

...tion/getelements/impl/ParquetElementRetriever.java
83.33% <100%> (ø)
0 <0> (ø)
:arrow_down:

... and 77 more

Continue to review full report at Codecov.

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

trying out the improvements with large volumes of data, so there may be more improvements to make

Ready to be merged


✨[Feature Request]: Resyling the footer

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

Restyling with a proper layout, coloring and hover effects.
Use Case
Restyling with a proper layout, coloring and hover effects.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@varshith257 please assign this issue to me

/assign @ayush-848


refactor(ui): Remove primary color for sort selector + add t…

Design improvements:

Remove primary color CTA for sorting selector
Display the name "sort" for default relevance sorting
Adding tooltips
Adding more clarity to the names in dropdown

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

unrelated smoke test failing. merging !


Add a favicon site

hello @fykaa I added  a very simple site where we can create favicons easily.
pls, can you accept this under hacktoberfest  label
I have already given a ⭐

Even if i accept this pr, it wont be accepted for hacktoberfest checks since its a very minute no-code update.


Play H.265 RTSP Streams

Hello,
Is there any way to play H.265 RTSP streams from the modern IP-cameras/DVRs?
Thanks

Hi
The only way will be switching to vlc 3.x version support.
No time for that for now, sorry :(
#37


Cannot navigate to a split terminal using quick pick

Testing  #44446
Pls see the screenshot below, I can navigate to the combo split, cmd but I cannot navigate to split or cmd

@kieferrm since I know you use the terminal picker quite a bit I'm curious how you would like split panes to be presented?

@Tyriar I've pretty much finished the term quick open, currently searching for the view.
Gonna upload a temporary PR for the term quick open to get a code review


Missing certificate authentication mechanism

We are missing TLS based authentication here. The documentation for the same can be found here: TLS Certificates - Auth Methods.
This is needed to get the token. Right now, we can create the client to use the client certificate and private key, but there's nothing to get the token:
const client = vault({ apiVersion: 'v1', endpoint: 'https://localhost:8200', requestOptions: { key: fs.readFileSync('./config/vaultClientAuthKey.pem'), cert: fs.readFileSync('./config/vaultClientAuthCert.pem'), ca: fs.readFileSync('./config/vaultCaCert.pem') } });

We need to add support for certAuth, so we can get the token, something like this:
client.certLogin(res => client.token = res.auth.client_token);

Hey @sudiptosarkar
Saw your PR, lgtm
We're in the middle of a handover so this will get merged asap; Thx for yur contribution!


Add the option to annotate with READONLY

Could be useful if you manage to add a parsing in the comments to allow for specifying that the element is readonly

This sounds like a good idea. Thank you for the suggestion

I did some testing and went trough the documentation here. Adding readOnly: true doesn't provide additional benefit because JSON schema is used for: lint, template, install and upgrade. This property makes more sense in api context like mentioned in release notes https://json-schema.org/understanding-json-schema/reference/annotations

I agree that this property is aimed to schema being used in form generation; that is also a fundamental usage for it.

BTW having the schema richer with properties does not hinder lint, template and install but opens up the door of generating values.yaml that is at the moment under valued.
I believe that having this plugin enriched with these options could open new paths for development


add post support

Implemented post

test: passed the unittest
Signed-off-by: Liang1XZhao<EMAIL_ADDRESS>

It will be change to "add post support"


sort does not have --parallel option

On our system sort does not have the --parallel option which makes ProteoStorm crash.

We could add coreutils to a conda package to circumvent this.

@bernt-matthias I was ask to assist in developing a Galaxy integration for this tool, but as far as I know you, you have done this already right? :)

Apologies for the late reply! As I am the only person working on developing this tool, things are moving slower than usual. I have been working on an updated version of ProteoStorm, where we no longer use Unix sort (and thus no --parallel option necessary), and will be updating the repository within the next few days. The main difference will be on the approach we take when creating database partitions.

@miinslin wonderful. thanks a lot.
@bgruening no I did not start yet. I was just evaluating the tool from the command line. If it works well I could imagine to do the integration. we could share the work. you do the conda package and I do the galaxy tool :)

Deal, I will just wait for @miinslin to publish the new version.

btw. @miinslin it is completely ok to use unix-sort, it better to use it than to implement this by yourself. Such errors will go away with proper packaging, e.g. as conda or debian packages.

solved?

Dear All, the database partitioning step no longer uses Unix sort, so I have closed the issue. Our manuscript is also now published on Cell Systems as a tool article, and we have a detailed description of the software and algorithms in the STAR methods section. You can access the manuscript online [Beyter and Lin et al., 2018.


Overflow error when using opengl, doublebuf and fullscreen

Hi,
I came across this overflow error when trying to do a simple change to fullscreen using pygame, opengl and the imgui integration.  The attached file reproduces it.
If you perform this line:
pygame.display.set_mode((0,0), pygame.OPENGL | pygame.DOUBLEBUF | pygame.FULLSCREEN)

Then the pygame integration will fail with the error:
Traceback (most recent call last):
  File "/path/to/reproducer.py", line 61, in <module>
    impl.process_event(event)
  File "/path/to/venv/lib/python3.11/site-packages/imgui/integrations/pygame.py", line 127, in process_event
    pygame.display.set_mode(
OverflowError: signed integer is greater than maximum

This is produced because the surface.get_flags() function returns the value<PHONE_NUMBER>.  The workaround is to catch this and re-enter the flags.
117         if event.type == pygame.VIDEORESIZE:
118             surface = pygame.display.get_surface()
119             # note: pygame does not modify existing surface upon resize,
120             #       we need to to it ourselves.

// BEGIN WORKAROUND
123             flags = surface.get_flags()
124             if flags ==<PHONE_NUMBER>:
125               flags=pygame.OPENGL | pygame.DOUBLEBUF | pygame.FULLSCREEN
// END WORKAROUND

126
127             pygame.display.set_mode(
128                 (event.w, event.h),
129                 flags=flags,
130             )

Packages are:
imgui==2.0.0
numpy==1.26.4
pillow==10.2.0
pygame==2.5.2
PyOpenGL==3.1.7
pygame 2.5.2 (SDL 2.28.2, Python 3.11.6)
The attachment includes both minimal reproducer and the output.
reproducer.py.txt

At first glance this seems like it is a pygame issue, not specific to pyimgui?

Ran into this issue as well. pygame.Surface.get_flags() returns its flags as uint32, while pygame.display.set_mode() expects its flags as int32.
Another workaround that works without hardcoding flags is adjusting the sign of the flags manually:
diff --git a/imgui/integrations/pygame.py b/imgui/integrations/pygame.py
index bfd65b9..74f37b6 100644
--- a/imgui/integrations/pygame.py
+++ b/imgui/integrations/pygame.py
@@ -118,9 +118,12 @@ class PygameRenderer(FixedPipelineRenderer):
             surface = pygame.display.get_surface()
             # note: pygame does not modify existing surface upon resize,
             #       we need to to it ourselves.
+            flags = surface.get_flags()
+            if flags >= 2**31:
+                flags = flags - 2**32
             pygame.display.set_mode(
                 (event.w, event.h),
-                flags=surface.get_flags(),
+                flags=flags,
             )
             # existing font texure is no longer valid, so we need to refresh it
             self.refresh_font_texture()

I agree that this looks more like a pygame issue, but on first glance it doesn't look like pygame documents anywhere that the flags returned from pygame.Surface.get_flags() can be used with pygame.display.set_mode(), so that use case might not be officially supported.


Bugfix/issue 830 support kotlin 1 4

Updated Kotlin plugin to v1.4.0 and Gradle to v.6.6
PS: contributing for first time here, any feedback appreciated.
Couldn't publish to maven local:
Invalid publication 'maven': multiple artifacts with the identical extension and classifier ('jar.asc', 'all')
Is it be because of the verification-metadata.xml?

closed unmerged by mistake

Also Kotlin 1.4 is already handled by the version https://github.com/pinterest/ktlint/releases/tag/0.38.0-alpha01.
I think the will release a non-alpha 0.38.0 into the next days.

@eduardompinto thanks for comments. We were kinda blocked by this issue in the project, that's why I wanted to contribute for the latest Kotlin support.
Would be happy if this PR helps. Also fine if anyone else is already about to release it.

@eduardompinto Could find the changeset with updated Kotlin plugin to 1.4.0. Found only this branch.
https://github.com/pinterest/ktlint/compare/0.37.2...0.38.0-alpha01

I think one of the project maintainers can talk about the release date, but the alpha version is already available in the maven repository
https://search.maven.org/artifact/com.pinterest/ktlint/0.38.0-alpha01/jar

Thanks for the PR @Vakhturov. I'm actually likely going to close this in favor of another upcoming diff; myself and the other maintainers just have to chat a little bit about ongoing preview Kotlin versions.
In general, we'd also prefer diffs that do one thing, e.g. upgrade Kotlin OR Gradle, but not both.
And like @eduardompinto said, you can use the alpha01 version if you need to be immediately unblocked.
Looking forward to your future contributions to ktlint. Thanks!

@shashachu thanks for the feedback. Looking forward for the upcoming release!


OSSM-5558 Remove usage of kustomize and replace with helm

This really simplifies our manifest creation (300 lines removed) and by using helm it'll also be much easier to introduce new things in the future. The biggest advantage is the ability to pass in a custom values.yaml on the product side to quickly create product manifests from the exact same templates as the community ones.

/retest

/retest