Clarify entitlement to free corona test (Addresses #2607)

Description
This PR clarifies the entitlement to a free corona test in the FAQ entries vac_cert_red_warning & voluntary_self_quarantine.
What was changed

https://www.coronawarn.app/en/faq/results/#vac_cert_red_warning
https://www.coronawarn.app/de/faq/results/#vac_cert_red_warning
https://www.coronawarn.app/en/faq/results/#voluntary_self_quarantine
https://www.coronawarn.app/de/faq/results/#voluntary_self_quarantine

Screenshots
vac_cert_red_warning

German
English

voluntary_self_quarantine

German
English

Fixes #2607

I will attempt running the cypress test suite on this PR now. Let's see if I can do that successfully.

So, one hour later, Cypress tests have passed. There were 5 issue, three false positives and two reg. http://localhost:8000/assets/documents/setupEventQRCodeGenerator.bat.
assert Link: http://localhost:8000/assets/documents/setupEventQRCodeGenerator.bat: expected false to equal true

No idea if this is related to this PR or if this is a general problem. IMO this PR is good to be merged.

@MikeMcC399 @Ein-Tim Thanks!


[Feature Request] - Make URLs in headers clickable #1050

"Fixes #1050"
Tasks
[x] Write a function that parses the given string and returns true if it is a valid URL or false.
[x] Place it in the insomnia-url package directory.
[x] Import the function to the response-header-viewer.
[x] Pass the string to the function, if the function returns True, wrap the value with an anchor tag and assign the value to the href attribute and text content property of the element.
Specs of the implementation

Function considers only absolute URL
It should have a valid URL scheme, hostname, pathname

Things considered to find the parsed URL is valid

Check if the protocol is one of the valid application layer protocol.
Check if the hostname property has a non-empty string.

Validating specs:

A Hostname is should be a valid domain name, Ipv4 address, Ipv6 address.
A URI scheme must be one of the following (ftp, file, gopher, http, https, ws, wss)

Reasons

Reason for not considering relative URL is, we can't be sure that the resource is available at the base URL of the request, it can be in any location.

Resources referred:

https://url.spec.whatwg.org/
https://softwareengineering.stackexchange.com/questions/294588/what-is-a-uri-scheme

[X]  Wrote tests for the functions that validate URL, hostname, scheme
Things to be completed:
[ ] Validate shortened IPv6 URL
[ ] Validate file paths for "file:" scheme (Unix and windows)
[ ] Validate URL that comes with a port number attached.
Test Screenshot:

Decided to re write the module, will just be using URL method of 'url' module in node. Also will write test for the functions implemented. Will be back soon.


chore: bdd-gh-1592925378 to 0.0.1

chore: Promote bdd-gh-1592925378 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Use async_forward_entry_setups in async_setup_entry

Hope this will address #99 - I don't have a thorough understanding & have not tested but hope it saves time for someone.

Sharing some background info in case it is useful to someone. My understanding, again, is extremely limited but I'm reading it over a few times:

Before 2022.8, it was impossible to await config entry platforms forwards without a deadlock if one of the platforms loaded by the config entry was not already loaded.
Integrations need to be refactored to replace calls to hass.config_entries.async_setup_platforms with hass.config_entries.async_forward_entry_setups and/or await all hass.config_entries.async_forward_entry_setup to ensure that Home Assistant does not inadvertently reload the integration while entities and platforms are still being set up.
hass.config_entries.async_setup_platforms is scheduled to be removed in 2022.12.

Original: https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards/

Looks good to me. Can you just run black and isort on __init__.py?

There you go! Looks like the diff is ~1 line of space for black; no changes after isort.exe --profile black .\__init__.py (Windows filesystem; running through a Powershell prompt). Please don't hesitate to ask me to retry something in case that sounds wrong to you; I haven't used the utils much.


Add models

Closes #2
The definition of models closely follows the W3C working group note "Spatial Data on the Web Best Practices".
Examples:

an annotation (Coverage) can describe the extent (Measurement.geometry) of a hot dog (SpatialThing) within a photograph (Universe) with a confidence (Relationship.property) of 98%.
an annotation (Coverage) can segment (Measurement.tile.attribute) an image (Universe) into various objects (Measurement.tile.value). The units of these segmentations can be described (Coverage.metadata).

@manthey Would you look at these data models? It was a bit overwhelming to fit all of these various forms of annotation into a few models. Luckily, the W3C note I mentioned on the first post gave a very nice framework to think about these things.

I realized that GeoDjango has created indexes and geometries assuming a few things I don't want:

Assumes WGS84
Assumes 2D geometry

The geometries must be 4D and the SRS ought to be set by the Universe, not application-wide. I've converted this to a draft until this is fixed.

Raster imagery is removed for now. It adds complexity to querying not suitable for an MVP. Any information contained in a raster Measurement may still be expressed in a vector Measurement, albeit less performantly. See 475a673cf557f4bbd50eb6c2503512b82c7722fc to refer to the removal of raster support.


CMakeLists.txt: Minimal fixes, added GNUInstallDirs and fixed cmake c…

…onfig loc
Also set version for proper shared lib
Signed-off-by: Matthias Schoepfer<EMAIL_ADDRESS>

I don't have much experience with cmake, it was added in https://github.com/kgabis/parson/pull/120 by @ewertons. Is it possible that this pr might require changes from existing cmake users?

Hi!
I would not expect any problems. Basically, it does 2 things. When building a shared lib, it will add "versioned" symbolic link (libparson.so.1.0.0. -> libparson.so) which is considered good practice and QA from embedded Linux like yocto / OE will complain if this is not the case. The second part adresses the install directories, which can be magically be "the right ones" when using GNU Install Dirs from standard cmake.


Toyota: do not brake when accelerator is depressed

Simple PR, set PERMIT_BRAKING to 0 when accelerator is depressed.
This prevents openpilot long from fighting with the user when the user overrides the accelerator.
For #23538

Would it be preferable if we introduce a 0.75 second delay before setting PERMIT_BRAKING to 1 after releasing the accelerator?
Thinking of doing something like this.
      # handle permit braking logic
      # record accelerator depression frame
      if CS.out.gasPressed:
        self.last_gas_press_frame = frame
      # set permit braking to false briefly after accelerator release
      if CS.out.gasPressed or 0.75 / DT_CTRL > (frame - self.last_gas_press_frame) and actuators.accel > - 0.07:
        self.permit_braking = False
      else:
        self.permit_braking = True

Seems like it should be handled higher up in controlsd?

if it's appropriate, it should be done for all car ports, not just Toyota
disabling the actuator at the car port level could result in integral windup for the brake input
what about AEB? (if controlsd really really wants to brake, in the future)

Seems like it should be handled higher up in controlsd?

if it's appropriate, it should be done for all car ports, not just Toyota (and not by making eleven copies)
disabling the actuator at the car port level could result in integral windup for the brake input
what about AEB? (if controlsd really really wants to brake, in the future)

This is mainly to resolve how Toyota's PCM handles the brake when the user is overriding the accelerator. If this is set to 1 (which it is in the current version of openpilot), the car's PCM will try to fight the brakes with the user.

I think this is what’s happening on Hyundais, specifically my Sonata Hybrid. With gas override, the brakes will start and prevent acceleration.
I agree it should be higher up not just in Toyota.

Usually the car's PCM will prevent any braking when the user has their foot on the gas. Do you have a route with the car actually braking while you're accelerating @cydia2020? And windup is handled in longcontrol.py and longitudinal_planner.py, we treat it as disengaged.

I have added some other stuff to this, I have been testing this setup for a few days now, and it works great, the car responds better to acceleration commands during SnG.
Some notes:
On Toyotas, openpilot requests -2.0m/s^2 acceleration when the vehicle is stopped, I used -1.95 as a condition for when permit_braking should be 1, this is so that the car won't release the brakes and creep forward when say the user accidently bumps the resume button. It also ensures that openpilot can still request braking force if the lead decelerates suddenly.
After looking into the log data a bit, I have realised that the "fighting for brakes" condition was created by me pressing the accelerator only very lightly, so the accelerator depression did not register with the vehicle's PCM, creating the "fighting for brakes" condition.

Have you tried master after https://github.com/commaai/openpilot/pull/23639 was merged? I'm not seeing that much braking at low speeds at all anymore.

Is there any update to this?

Don't think this is needed anymore now, SnG has been smooth. Closing


feat(enricher): add runtime labels to resources.

This adds more labels to the created resources to better identify that this is a Node.js application in the Developer Topology view in Openshift 4.2

THere are also labels added to the BuildConfig, that allows for better ux when looking at the topolgy view.

fixes #374

Pull Request Test Coverage Report for Build 998

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 96.644%

Totals

Change from base Build 512:
0.02%

Covered Lines:
635

Relevant Lines:
660

💛  - Coveralls

Does a BuildConfig not follow the same pattern as other resources with the enrichers?

Correct.  It was just those "application" specific objects that would get "enriched".    In openshift 3.x, you could actually see the build running next to your deployed pod,  but in openshift 4, in order to get the little build circle thing,  the build config now needs some labels

The build circle is the one that is a green check in this picture,  when a build is happening that becomes revolving arrows


[storage] Rename NVMf -> Nvme

Naming NVMf caused proto to force "nv_mf" syntax which is weird.
Unify the naming to Nvme format utilized throughout all API components.
Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

Docker / call / test (pull_request) Failing after 2m

this is due to opi-spdk-bridge repo is not updated yet with the renaming code...

I think we also need to update file names NVMf -> Nvme

good catch. done


Wrong Documentation: Runtime parameters are not supported in Azure DevOps Server 2019

Runtime parameters are not supported in Azure DevOps Server 2019.
But the documentation is not correct, this section (https://docs.microsoft.com/en-us/azure/devops/pipelines/process/runtime-parameters?view=azure-devops-2019&tabs=script#use-parameters-in-pipelines) must be applied only for Cloud Version, not for Azure DevOps Server 2019.

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

ID: 790318bb-8220-3241-4ca7-73351074492f
Version Independent ID: db1da9db-3694-779b-17aa-1ed67fcecf86
Content: Use runtime and type-safe parameters - Azure Pipelines
Content Source: docs/pipelines/process/runtime-parameters.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

The versioning for this was fixed in July 2020.


Changing an object/list also changes other objects/lists if those got their initial value from the same variable.

Version
2.6.11
Reproduction link
https://jsfiddle.net/bf0qo19m/
Steps to reproduce
I've added buttons in the jsfiddle to add a value to the first list and change the message of the first object.
What is expected?
The value of the second list/object doesn't change when the first list/object changes.
What is actually happening?
When changing the first list or object the second one changes as well.

The provided jsfiddle is a simplified version of a problem I've ran into quite a few times now. It functions the same so it should demonstrate the problem.
I ran into the problem when i tried to save the same info from axios request in two different objects. One to keep track of the state in the database and another for user to alter. This way the two can be compared if needed. However changing one of the two objects also changed the other. So there is no way to now what the original state was.

Unfortunately, this is how JS works. You will need to create a copy of objects in order to make them different. Vue adds reactivity on top of them

Remember you can use the forum or the Discord chat to ask quick questions!


source

hey , I saw you wrote somewhere if you want any source of TS3 plugin just contact me , so I need TS3MassMover source can I have it ?

Its public just search it on github

what about AutoReplay plugin ? link


exploitdb: 2022-11-22 -> 2023-02-03

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/exploitdb/versions.
meta.description for exploitdb is: Archive of public exploits and corresponding vulnerable software
meta.homepage for exploitdb is: https://gitlab.com/exploit-database/exploitdb
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2023-02-03 with grep in /nix/store/xbx9fl1qv7m2nif0nsxmjivjjv38wpc2-exploitdb-2023-02-03
found 2023-02-03 in filename of file in /nix/store/xbx9fl1qv7m2nif0nsxmjivjjv38wpc2-exploitdb-2023-02-03

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
exploitdb

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xbx9fl1qv7m2nif0nsxmjivjjv38wpc2-exploitdb-2023-02-03
ls -la /nix/store/xbx9fl1qv7m2nif0nsxmjivjjv38wpc2-exploitdb-2023-02-03/bin

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

1 package built:

exploitdb

Maintainer pings
cc @applePrincess @fabaff for testing.

@ofborg eval

Result of nixpkgs-review pr 215302 run on aarch64-darwin 1

1 package built:

exploitdb


[CocoaPods] integration tests

Tests changes introduced in #431.
Runs tests against standard and standalone subspecs, for iOS/OSX/tvOS. The FTS4 integration test needs to be disabled for standalone builds since newer versions of SQLite need to explicitly enable custom tokenizers:
https://www.sqlite.org/compile.html#enable_fts3_tokenizer

😄 Excellent! Thanks for rounding things out with coverage!


Issue when testing a model factory using make()

I have a Thread model, that has Sluggable property on it & the sluggable() function for creating the slug.
When I create a test, using the factory for that Thread model & I use $thread = Thread::factory()->make() it is not generating the slug. This is my test (as below), when I try to assertNotNull($thread->slug) I get null is not null. I took me quite a while to figure out that the slug was causing the issue. Do you have any suggestions for how I can do testing on models that have sluggable?
    /** @test */
    public function an_authenticated_user_can_create_a_new_forum_thread()
    {

        $user = User::factory()->create();

        // Given we have a signed-in user
        $this->withExceptionHandling()->signIn($user);

        // Make a thread
        $thread = Thread::factory()->make();

        // Post the thread
        $this->post(route('discuss.store'), $thread->toArray())
            ->assertStatus(302)
            ->assertRedirect(route('discuss.show', $thread->slug))
            ->assertSessionHas('success', 'Post created successfully!');

        $this->assertNotNull($thread->slug);

        // Then their reply should be visible on the page
        $this->get(route('discuss.show', $thread->slug))
            // check to see if the thread creator's name is present
            ->assertSee($thread->creator->name)
            // check the inertia response
            ->assertInertia(function (AssertableInertia $page) use ($thread) {
                // check the component
                $page->component('Discussion/Index')
                    // check the component's data is present
                    ->has('conversations.data', 1)
                    // check the thread's title is present
                    ->where('conversations.data.0.title', $thread->title)
                    // check the thread's body is present
                    ->where('conversations.data.0.body', $thread->body);
            });

    }
    ```

Update: I found a work around (after reading the docs), but I am not sure it is how I should be handling testing with Sluggable. I would still like your response on how I should go about it?
Work around:
    public function an_authenticated_user_can_create_a_new_forum_thread()
    {

        $user = User::factory()->create();

        // Given we have a signed-in user
        $this->withExceptionHandling()->signIn($user);

        // Make a thread
        $thread = Thread::factory()->make();

        $thread->slug = SlugService::createSlug(Thread::class, 'slug', $thread->title);

        $topic = Topic::factory()->create();

        $thread->topic = $topic->slug;

        // Post the thread
        $this->post(route('discuss.store'), $thread->toArray())
            ->assertStatus(302)
            ->assertRedirect(route('discuss.show', $thread->slug))
            ->assertSessionHas('success', 'Post created successfully!');

        $this->assertNotNull($thread->slug);

        // Then their reply should be visible on the page
        $this->get(route('discuss.show', $thread->slug))
            // check to see if the thread creator's name is present
            ->assertSee($thread->creator->name)
            // check the inertia response
            ->assertInertia(function (AssertableInertia $page) use ($thread) {
                // check the component
                $page->component('Discussion/Show')
                    // check the component's data is present
                    ->has('conversation', 12)
                    // check the thread's title is present
                    ->where('conversation.title', $thread->title)
                    // check the thread's body is present
                    ->where('conversation.body', $thread->body);
            });

    }
    ```

Models are slugged when they are persisted to a database, i.e. on $model->save().
It looks like the make() method on a factory just instantiates the model, but doesn't persist it ... so those models won't yet be slugged.  If you used create() instead, I think things would work:
$thread = Thread::factory()->create();

Let me know if that works?

Yeah that works, but for this test I need to use make so it gets persisted when I post the data in the test. So i think just for testing purposes I need to keep using the SlugService::createSlug(Thread::class, 'slug', $thread->title); which is OK, I don't mind for testing. Thanks for your response.


Add table of contents to the readme

Brief Description 📝
I would like to add table of contents section in the readme for easier navigation and enhance the user experience.
Select the open-source program you are contributing to
GSSOC 2024 EXTD, Hacktoberfest 2024
Code of Conduct

[X] I agree to the CONTRIBUTING GUIDELINES of this project.

Hey @T-Fathima👋! Thanks for raising this issue and demonstrating your interest in contributing to our project!🚀
We value your engagement and eagerly anticipate your contributions. Should you wish to get involved, please use the /assignme command to self-assign the issue.
This issue provides an excellent opportunity for us to enhance our project, and we're excited to have you join us! Please take a moment to review our CONTRIBUTING GUIDELINES before getting started.
If you have any questions or need assistance, feel free to reach out to us on LinkedIn.❤


Update trytravis.py

This PR should give trytravis the option to just submit the tests to Travis and don't wait until they are done.
Fixes #17

Codecov Report

Merging #22 into master will decrease coverage by 0.86%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #22      +/-   ##
=========================================
- Coverage   43.36%   42.5%   -0.87%
=========================================
  Files           1       1
  Lines         196     200       +4
=========================================
  Hits           85      85
- Misses        111     115       +4

Impacted Files
Coverage Δ

trytravis.py
42.5% <0%> (-0.87%)
:arrow_down:

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 2f8e47a...f7dfdf9. Read the comment docs.

Might want to change your trytravis target repo from your fork to a different GitHub repository. :)

I was actually trying to run trytravis for my fork to stop all the unnecesary noise here, sorry about that.

How do you want to handle the CHANGELOG entry? Should I add it under the current version? What about the codecov fails?

You can add it under a new version labeled "Unreleased" or under the next incremented minor. Don't worry about the codecov fails.

Sorry for the late reply, just added this to the README.md

Thanks! This is looking good :)


Error when working with the database

Hello, we have encountered a problem while working with a database.
We have created two entities and linked them together as specified in the instructions.
When adding, everything works fine, but when we delete an item from either entity, it remains in the other one.
Looking at the code,we found that when we pull out the old data:

The function inside that tries to get the data out of the model tries to find it at the same level when the data in the standard model lies in data.

Is this an actual problem or is this us not handling the model correctly?
We are using the standard driver https://github.com/statamic/eloquent-driver

Would you be able to put together a test repo that contains your specific setup that I could look at? That would help to answer your question better. Thanks!

Hello, I apologize for the long reply.
It's actually quite simple.
I installed pure Statamic, configured the Eloquent driver to store Entry in the database.
2 entities were created through Statamic admin.
2 random fields were merged together. For us it was: Exhibits and Champions.
Communication via Provider was set up.
 Relate::manyToMany(             'exhibits.champions',             'champions.exhibits'         )->allowDelete(false);
After that when saving everything works fine, when deleting it does not work.

When you say deleting does not work, are you saying deleting itself does not work, or that nothing happens with the relationships?

When you delete a champion from an exhibit, for example, the exhibit remains in the champion.

@GertTimmerman Thanks for the comment! If you have time, would it be possible to put together a small repo that replicates this using the Eloquent driver and SQLite? This really helps to accelerate my side of things once I get into it

@GertTimmerman Thanks for the comment! If you have time, would it be possible to put together a small repo that replicates this using the Eloquent driver and SQLite? This really helps to accelerate my side of things once I get into it

I have created it here: https://github.com/GertTimmerman/statamic-entry-relationshop-db
When you change the author of a book, all the relations will mess up

Thanks for the repo! I'll take a look this week and get something going for this

Improved DB support with 2.2.1


Only allow user to select channels to add subscriptions to in which they are channel admins

Users should not be able to add subscriptions to Mattermost channels in which they are not admins for

@mickmister Is there any need for this feature as of now? Thoughts on this.

@Kshitij-Katiyar I think this is a valid feature. I think we can have a plugin config setting to limit this to:

System Admin
Team Admin
Channel Admin

Making this HW to see if others want to work on it


Use <IP_ADDRESS> SS

Parameter deviations are modelled differently in this version of SS, which will be influential in selectivity estimates. Though, this version is not officially released yet. More info to come.

JTC call - Kelli suggested 3.30.14 . Tick a box when you have it:

[ ] Kelli
[ ] Aaron
[ ] Chris
[ ] Andy

<IP_ADDRESS> is available in the google drive, though I changed the extension or here. Currently, there is only a build for Windows. Let me know if you need a different version.

I did a test earlier today comparing the SS version we did last year and this version and got the same results for SSB and stock status.  I have yet to look at all the results.  At any rate, this conversion will be part of the bridging analysis.  There was one minor change I had to make in the control file (new version wanted one less line, that being the second to last line, so I commented it out).  I.e.,
-1 # vector with growth std bin picks (-1 in first bin to self-generate)


Error when trying to flash Android image build to NXP IMXMQ

Hi,
I get this error when I try to run the following script:
sudo ./uuu_imx_android_flash.sh -f imx8mq -a -e
Error:
This script is validated with uuu 1.4.139 version, it is recommended to align with this version.
dtbo is supported
dual slot is supported
dynamic parttition is supported
vendor_boot parttition is supported
generate lines to flash u-boot-imx8mq.imx to the partition of bootloader0
generate lines to flash partition-table.img to the partition of gpt
generate lines to flash dtbo-imx8mq.img to the partition of dtbo_a
generate lines to flash boot.img to the partition of boot_a
generate lines to flash vendor_boot.img to the partition of vendor_boot_a
generate lines to flash vbmeta-imx8mq.img to the partition of vbmeta_a
generate lines to flash super.img to the partition of super
uuu script generated, start to invoke uuu with the generated uuu script
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.138-0-g051a8fe

Wait for Known USB Device Appear...
Error: fail open file: >/tmp/uuu.lst

I could see that the device has been configured correctly.

Connected Known USB Devices
	Path	 Chip	 Pro	 Vid	 Pid	 BcdVersion
	==================================================
	1:4	 MX8MQ	 SDP:	 0x1FC9	0x012B	 0x0001

./uuu_imx_android_flash.sh is not owned by me. It should be generate a file at /tmp/uuu.lst


NeonHelper.PartitionCount()

Add convenience methods for computing the number of partitions required to hold a specified number items where the number of items is capped.  This is a simple computation but it would be cleaner to have the logic centralized and unit tested.
We'll create four overrides for: int, uint, long and ulong

DONE


Grid header closing edit row

Hi guys ,
When I click on a row to edit it and then click on a column header to sort that column , the edit row is gone . I have tried using jquery as
$(".jsgrid .jsgrid-header-row .jsgrid-header-cell").click(function (e) {
            alert("Header clicked");
            $(".jsgrid-button.jsgrid-update-button").click();
});

but it doesnot work .
So , my requirement is that when a user is in edit mode and he does something like filter or search or page change , it should show a javascript alert and ask him if he wants to save or not . If he clicks yes , it will save the item and then sort , else it will perform the function like search or sort etc. When I used inspect element of chrome , I saw that on clicking the column header , the edit-row is deleted and then the alert is shown . So , the update-button doesnot exist at that time . What should I do to fulfill the requirement ?

Try to redefine cancelEdit method to have something like:
cancelEdit: function() {
    if(!this._editingRow)
        return;

    if(window.confirm("Save changes?")) {
    	this.updateItem();
    } else {
    	jsGrid.Grid.prototype.cancelEdit.call(this);
    }
}


Code folding options disappears after init

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:34:09.706Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author (truncated)
Version

html-snippets
abu
0.1.0

dakara-foldplus
dak
1.1.0

githistory
don
0.2.2

Angular2
joh
2.4.0

gitblame
wad
2.0.2

(1 theme extensions excluded)

Steps to Reproduce:

Launch vs code
After initialization is done (when proper folding is shown for code for around 1 second), lines disappear and i cannot enable folding again

Reproduces without extensions: Yes

Can you attach a screenshot?

Can you check the status bar if it says 'screenreader detected'?
I just learned that this would remove folding.

Yes, it was the active Screenreader, i discovered it after reporting this.
Everything's back in place now, thank you !
On Mon, Aug 14, 2017 at 9:48 AM Martin Aeschlimann<EMAIL_ADDRESS>wrote:

Can you check the status bar if it says 'screenreader detected'?
I just learned that this would remove folding.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/31756#issuecomment-322122069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF6WJzC0w5yzjmSxvgOlXWjmsYSkDQ9iks5sX_vegaJpZM4OoXrG
.

Assigning to @alexandrudima to follow up here.


fix logo and headers

@FidelChe, there are a few pull requests...whenever you have some time for it.

Done!


Add ability to modify and persist option choices

Options:

include videos
time delay between switching
automatically randomize
transition effects?
more?

There are now options, they just need to all be implemented


Karpenter deployment - one pod have "Insufficient cpu" while other one goes well

Description
Observed Behavior:
I've deployed 0.37 on my EKS using ArgoCD
After deployment is done, one pod is working OK, and one pod events say not CPU
0/2 nodes are available: 1 Insufficient cpu, 1 Too many pods, 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 1 Insufficient cpu, 1 Preemption is not helpful for scheduling.

EKS: 1.30
While using "inflate" for testing, I see a new node came up. so all good by karpenter. But it's driving me crazy.
Expected Behavior:
All pods will be up and good.
Reproduction Steps (Please include YAML):
Versions:

Chart Version: 0.37.0
Kubernetes Version (kubectl version): 1.30
My values:

  roleName: "xyz-node-group-20240801082441731100000005"
#  logLevel: debug
  settings:
    clusterName: "xyz-eks"
    interruptionQueue: "xyz-eks"
  serviceAccount:
    annotations:
      "eks.amazonaws.com/role-arn": "arn:aws:iam::****:role/xyz-karpenter"
  controller:
    resources:
      requests:
        cpu: 1
        memory: 1Gi
      limits:
        cpu: 1
        memory: 1Gi

Since karpenter can only schedule on the non-karpenter provisioned node pools, it has no choice but only schedule on the nodes from the native pool.
I'm guessing here that your native nodepool has small instances. Small AWS instances can only support small number of pods, its like 8 pods for m6.medium iirc.
So karpenter pod being regular priorityclass cannot scheduled because all 8 slots are likely already occupied on that one.
two solutions here:

Set karpenter prioritycass to system-node-critical via .Values.priorityClassName. This will inevitably boot some other pod from this node. In my case all pods are needed since they are daemonsets that are required for the node to function.
Increase the instance size to one size bigger.

@dcherniv  Thank you for fast reply.

It's already the default value, so if the values isn't overwrite by me, this is what been configured.
a. Why did you used deamonsets in here? What benefit you getting using DS for karpenter?
You mean the default instances for the cluster? The nodes we getting before karpenter?

Looking at the chart it sets itself as cluster critical by default: https://github.com/aws/karpenter-provider-aws/blob/main/charts/karpenter/values.yaml#L53 Cluster-critical doesn't guarantee scheduling 100% unfortunately. https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/ hence i suggested node-critical which is a stronger priorityclass and all but guarantees scheduling at the cost of evicting some other pod with lower priorityclass
I didn't use DS, it just appears that way because karpenter has affinity rule that only allows it to schedule on non-karpenter pods https://github.com/aws/karpenter-provider-aws/blob/main/charts/karpenter/values.yaml#L73
Yes the nodes you get initially that come with the cluster (usually configured via terraform or something). I use this https://registry.terraform.io/modules/terraform-aws-modules/eks/aws/latest/submodules/eks-managed-node-group to provision a nodepool with 2 small nodes which are used by karpenter.

I've changed to node-critical, didn't changed any behivor
Seem to be the same on my case
Same in my case.

Still the pod is stuck.

Hm... strange. It should have evicted something else.
Whats the output of the kubectl describe node for each of the nodes that are members of the pool where karpenter is expected to run?
Also, i think 1 core reservation is too much for a karpenter pod. On my relatively busy cluster it rarely goes over half a core:

@dcherniv While I'm trying to provide you the answer, I've figure out one node which installed from scratch is not showing up in nodes list.
I'v restart this node and removed all karpenter nodes, the karpenter detect it and used it to trigger the pod, and later all karpenter nodes started as needed.
All good now. Thx.


optimize:add a start banner for seata

Ⅰ. Describe what this PR did
optimize:add a start banner for seata
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #3955 (197b262) into develop (e2e5fa6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop    #3955   +/-   ##
==========================================
  Coverage      40.38%   40.38%
  Complexity      3070     3070
==========================================
  Files            685      685
  Lines          23194    23194
  Branches        2869     2869
==========================================
  Hits            9366     9366
  Misses         12958    12958
  Partials         870      870


Norwegian Language Pack

oh.... this is not good. I was merged into master.
Can you create a new PR? I'm going to revert this one


Potential issue with lpass adapter on a Mac?

I've got lpass installed via Homebrew on a Mac. I run kamal with the docker alias. Here is what happens when I try to run kamal secrets fetch --adapter lastpass --account<EMAIL_ADDRESS>--from MyFolder.

As you can see in the image above, I do have lpass installed. Is there anything I am doing wrong here? I took a peak at the code and there is nothing unusual, just a regular call to lpass here
Any help is appreciated, thank you!

@afgallo This is a known issue when running Kamal with the docker alias, check this issue https://github.com/basecamp/kamal/issues/1065

Thanks @tuladhar, sorry I've missed #1065 before creating this one.


Disabling Debug creates CSS/JS issues

When I set DEBUG=False in local.py, CSS/JS gets borked and the files my browser is looking for aren't there.  Wondering if I'm doing something wrong?

@akeym: Could you elaborate a little? What are the missing files named?

Set DEBUG=False and you should see what its asking for on your dev environment.  It was looking for cyder_prod*** files if I remember correctly.  If it doesn't show up in your local environment, feel free to set it on cyder-dev.nws and restart apache to see what happens.

Alright, I'm seeing it now. I think I tested the wrong thing before.


Feature Request: Windows Support

get_default_directory': uninitialized constant AutoChrome::ProfileBuilder::NotImplementedException (NameError)
used command:
ruby ./autochrome.rb -t Win_x64
I am using ruby with ming64, so usual command doesn't work. Please help!
On windows 10

?

Same issue for me

same issue

All hope is not lost. This seems to work just fine under WSL2.


Postgres 9.5 build issue with added record to /etc/apt/sources.list

Getting 404 from a repository source during command apt-get update after a new record is appended to the /etc/apt/sources.list file.


⚠ Bofrost.es has degraded performance

In 5722aed, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1662 ms

Resolved: Bofrost.es performance has improved in 3500b50 after 15 minutes.


⚠ Bofrost.be has degraded performance

In c24f196, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1229 ms

Resolved: Bofrost.be performance has improved in 67c710c after 20 minutes.


BadRequestError: Unsupported data type when using SimpeDirectoryReader Output

Bug Description
When we read any pdf file using SimpleDirectoryReader() function, when ever we pass the output document to any function like VectorStoreIndex.from_documents() or generator.generate_with_llamaindex_docs() , it is giving BadRequestError: Unsupported data type
Version
llama-index 0.11.17
Steps to Reproduce
documents = SimpleDirectoryReader("data_ragas").load_data()
vector_index = VectorStoreIndex.from_documents(documents)
(or)
testset = generator.generate_with_llamaindex_docs(
documents,
test_size=50,
distributions={simple: 0.5, reasoning: 0.25, multi_context: 0.25},
)
Relevant Logs/Tracbacks
BadRequestError                           Traceback (most recent call last)
Cell In[11], line 6
      4 Settings.llm = generator_llm
      5 Settings.embed_model = embed_model
----> 6 vector_index = VectorStoreIndex.from_documents(documents)
      8 query_engine = vector_index.as_query_engine()

File c:\Users\jothimalar.p.lv\Documents\LLM POCS\TestSet generation\testsetenv\Lib\site-packages\llama_index\core\indices\base.py:119, in BaseIndex.from_documents(cls, documents, storage_context, show_progress, callback_manager, transformations, **kwargs)
    110     docstore.set_document_hash(doc.get_doc_id(), doc.hash)
    112 nodes = run_transformations(
    113     documents,  # type: ignore
    114     transformations,
    115     show_progress=show_progress,
    116     **kwargs,
    117 )
--> 119 return cls(
    120     nodes=nodes,
    121     storage_context=storage_context,
    122     callback_manager=callback_manager,
    123     show_progress=show_progress,
    124     transformations=transformations,
    125     **kwargs,
    126 )
...
   (...)
   1066     retries_taken=retries_taken,
   1067 )

BadRequestError: Unsupported data type

Your error is truncated (notice the (...), so its hard to say what the actual issue here is
I've personally never encountered this. Maybe something to do with your embedding model or Llm setup

Without a google colab notebook or similar to reproduce, this will be near impossible to fix

@logan-markewich,
Thanks much for the tips and I managed to fix the issue now. The problem is related to using old embedding API and when I updated it, it is working as expected. Appreciate your pointer on this!


Add conditions object for finding JUNGFRAU constants

I have copied the details across from the internal calcat_interface code, but it would be good to double check that.
cc @kakhahmed

LGTM.
It's good to know about these cassettes. I guess there is no strategy for updating these cassettes as updating the response is something we control in the CAL team. Or do you think otherwise?

Thanks!
We've got tests running daily against CalCat, ignoring the cassettes. So if there's a change in the responses which makes the tests fail, we'll pick it up there, write a fix and re-record the relevant cassettes. There's no plan so far for picking up changes in the responses which don't cause test failures.


echo() or print() in custom artisan command disables terminal echo

If you implement a custom Artisan command and use echo() or print() to send info to the console, terminal echo is disabled (on Mac running Yosemite and iTerm at least).
Example code,
<?php namespace App\Console\Commands;

use Illuminate\Console\Command;

class ExampleCommand extends Command {

  protected $name = 'example:command';
  protected $description = '';

  public function __construct() {
    parent::__construct();
  }

  public function fire() {
    echo "Hello world";
  }

  protected function getArguments() {
    return [];
  }

  protected function getOptions() {
    return [];
  }
}

You can use $this->info("What ever the message") in CustomCommand@fire function.

You should ever use echo or print in there.

I would agree and I don't. The problem occurs when I'm using a third party package not designed for Laravel and it uses echo or print. I just used the above code as the simplest example.


add omitempty to 'Devices

Add 'omitempty' to 'Device'.
remove the 'seccomp' and 'device' from the example since they are not necessary
change the device type description c to "c" since it became a string.

Signed-off-by: liangchenye<EMAIL_ADDRESS>

LGTM

On Thu, Mar 10, 2016 at 10:25:56AM -0800, Michael Crosby wrote:

Why do we have to remove fields from the EXAMPLES?  They are
examples, if you don't have fields in examples where are people
going to learn about them?

I think we should either remove optional fields or fill them in with
meaningful values 1.  Discovery should be through the parent field's
documentation [2,3].

Same with Wking, I think we don't need the meanless unnecessary value.

@hqhq yes, remove the unnecessary change.
@vishh  new update also adds omitempty to 'namespace'

LGTM
and while this removes the empty values, i'll fix via https://github.com/opencontainers/specs/issues/344


Combine 8067 8069

Adding in #8073 also

#8074 was needed too

#8074 was needed too

Make that #8075

Closing in favor of #8083


IOS-13593 - Get BrowseSDK Sample app working with latest changes.

Hi @irvingruan, thanks for the pull request. Before we can merge it, we need you to sign our Contributor License Agreement. You can do so electronically here: http://opensource.box.com/cla
Once you have signed, just add a comment to this pull request saying, "CLA signed". Thanks!

+2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Irving Ruan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Irving Ruan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


integration_test: fix indentation for test formulae

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

I noticed in https://github.com/Homebrew/brew/pull/9490 that formulae returned by setup_test_formula have weird indentation. For example:
class Testball < Formula
  desc "Some test"
homepage "https://brew.sh/testball"
url "file://#{TEST_FIXTURE_DIR}/tarballs/testball-0.1.tbz"
# -snip-
end

Note how desc has one more level of indentation than homepage and url.
This PR fixes the indentation so that the previous example now looks like this:
class Testball < Formula
  desc "Some test"
  homepage "https://brew.sh/testball"
  url "file://#{TEST_FIXTURE_DIR}/tarballs/testball-0.1.tbz"
  # -snip-
end

Review period will end on 2020-12-23 at 00:25:43 UTC.

Review period skipped due to critical label.

Good catch, nice work @SeekingMeaning!


Update dataflows-create.md

Fixed a couple of typos.

@nachoalonsoportillo : Thanks for your contribution! The author(s) have been notified to review your proposed change.


TabController no expected results

Demo
As shown in the figure, Tab's page is not according to my expectation. When the drawer's Item is switched, it always shows the index of the previous click.
https://github.com/7449/flutter_example/blob/master/flutter_issues/flutter-issues.gif

thanks

Sorry for the late response.
Is this still an issue with recent Flutter versions?

no,commit version:9c49255f3eeb4873e6398c805b4bb6b9737be962

Thanks a lot for the feedback!


jax.numpy: better docstring for append function

New docstring and JAX-specific code examples are addd for jax.numpy.append.
Part of 21461.

@jakevdp all commits squashed into one.


⚠ Bofrost.es has degraded performance

In 2ab9a74, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1821 ms

Resolved: Bofrost.es performance has improved in e04cec1 after 12 minutes.


Add Split Screen Capabilities and Multiple Cameras

I have been inspired by another project that I am currently working on. So there is a nice feature that I would like to add to our engine. Currently we do not support local multi player or split screen and we also don't support having more than one main camera and registry. The goal of this feature is to change that.
Feature - Add Split Screen Capabilities

Add the ability to split the screen from 1 viewport up to a maximum of 4.

This would entail the following:

Use the NDC coordinates of the screen to split up multiple Frame buffers.
The frame buffers will need to have their own VAO and VBOs based on the split dimensions of the screen.
Each would also need it's own camera.
We would also need to adjust the FollowCamera lua bindings to take in a camera rather than assume there is a main camera.
The scene would need to be rendered to all active Framebuffers.

Add the ability to have multiple cameras.

Currently we assume there is only one Main camera. Need to add the ability to have more cameras in a scene.

Add the ability to have multiple Registries.

Currently we only have one registry; however, we need to create a MainRegistry class that will hold all of the classes that we only need one of.
Those would need to include:

SoundFXPlayer
MusicPlayer
Renderer
AssetManager

Changed severity to low. There are more important things that need to be handled atm.


[Feature] Enable openapi v3.1

Upgrade dependencies (fastify, typescript, ..) and allow for schema using openapi v3.1 to be parsed

Is the support for node v8 still wanted though ? I see @types/node@12 being installed, and it prevents upgrading eslint, typescript, ...

Support for node v8 could be safely removed

I suppose we could upgrade CI to check from v10 (even v12 ?) through v17, and maybe specify engine versions requirement, matching the type used, in the package.json.

CI should be updated to test v10, v12, v14 and v16 (only LTS releases).

PS: even npm conflicts : package.lock is v2, so uses npm v7, which requires node >=10

The package-lock.json should be removed from the repo (and added to .gitignore) since it's not part of the published package. It will force contributors to have latest versions of dependencies instead of locked one (better match the npm i fastify-oapi behavior).
This also means we should replace npm ci by npm install in CI workflows

There are some breaking changes:
https://github.com/OAI/OpenAPI-Specification/releases
See: 3.1.0, 3.1.0-rc1, 3.1.0-rc0
The most notable one is the removal of nullable.

We may also need to adjust ajv-openapi default options:

allow to specify target OpenAPI version
when 3.1: use draft-2020-12 jsonschema version
when 3.1: set nullable to false
when 3.1: do not include string format validator: byte

Maybe some others...


[SKIP-PREVIEW] Fix smoke tests - skipping preview because it is unavailable but tested on demo

Change description
Fixing smoke tests in the build
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X ] No

Codecov Report

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

@@          Coverage Diff           @@
##           master     #62   +/-   ##
======================================
  Coverage    88.8%   88.8%
======================================
  Files         237     237
  Lines        4233    4233
  Branches      311     311
======================================
  Hits         3759    3759
  Misses        422     422
  Partials       52      52

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 ad4c12f...252e4b9. Read the comment docs.


Fix for bad locale entry in lib/misc.zsh

LC_CTYPE was being set to $LANG, which is bad because

LANG expects a list, and LC_CTYPE expects a single value.
LC_CTYPE can be set by the environment at a different value than LANG, to cope with non-ASCII applications in a Latin environment, mainly for Asian languages.

It now checks if it is set by the environment, and if not picks the first entry of LANG or a safe default.

Just stumbled randomly on this issue.
LANG is not expecting a list. LANG is expecting a single locale. LANGUAGE is expecting a list of languages (this is used by GNU gettext). Setting LC_CTYPE to LANG when neither LC_ALL nor LC_CTYPE are defined is redundant. Applications are already using LANG in this case. See the GNU Libc manual.
So #3563 is a noop.
From my point of view, people should just set LANG correctly. Many programs will barf otherwise. Otherwise, something like that:
(($+LC_CTYPE || $+LC_ALL || $+LANG)) || {
  local -a available
  available=("${(f)$(locale -a)}")
  export LC_CTYPE=${${${${(@M)available:#*.UTF-8}[1]}:-${${(@M)available:#*.utf8}[1]}}:-C}
}

Hi @vincentbernat, sorry for posting so late. I appreciate some clarity on this (finally! :smile:), please post a PR with your solution and we'll test if it works well.

Unfortunately, from all the bug reports, I still don't understand what we are trying to fix. From #4091, it seems that some people have LC_ALL=C set. So, the solution I proposed above doesn't quite fix this kind of situation. I thought that the problem was for people where no variable at all were set. Overriding a user value seems more difficult.
The current code is the following:
# only define LC_CTYPE if undefined
if [[ -z "$LC_CTYPE" && -z "$LC_ALL" ]]; then
	export LC_CTYPE=${LANG%%:*} # pick the first entry from LANG
fi

Two problems:

LANG is not a list but a single locale
If LC_CTYPE is not defined, its value is the same as for LC_ALL. If LC_ALL is not defined, its value is the same as LANG.

I can do a PR just removing this block of code.
Thinking a bit about it, maybe the problem solved by this code is when people use a list in LANG (do you do that?). Its content becomes invalid and therefore defining LC_CTYPE to be the first component saves the day. However, the fix is easy: don't use a list. If you want a list, use LANGUAGE (which is a list of languages, not a list of locales).

The main issue is when people use a locale that is not utf8 compatible. So by overriding LC_CTYPE we ensure unicode characters are handled correctly. If LC_ALL is set we can't do anything about it, but let's supose it's set on purpose by the user and with unicode support. That part doesn't worry me.
The part that's important is that if LC_CTYPE doesn't use unicode we should set it to use unicode in the best way possible, similar to how this PR had it: setting it to locale known by the user but with UTF-8. So it's true that as is now nothing is done if, for example, LC_CTYPE=C. So we should change that. How does your snippet of code work exactly?

This one?
(($+LC_CTYPE || $+LC_ALL || $+LANG)) || {
  local -a available
  available=("${(f)$(locale -a)}")
  export LC_CTYPE=${${${${(@M)available:#*.UTF-8}[1]}:-${${(@M)available:#*.utf8}[1]}}:-C}
}

If neither LC_CTYPE, LC_ALL nor LANG is set, put the output of locale -a into the available array and take the first member matching *.UTF-8 and if there is nothing, take the first member matching *.utf8 and if there is nothing, takes C (but you could default to C.UTF-8).
The last line could be cut in several variables:
${(@M)available:#*.UTF-8}
${(@M)available:#*.utf8}

In zshexpn(1), search for ${name:#pattern} to understand this notation.
We could do something like that:
LC_CTYPE=${LC_CTYPE:-${LC_ALL:-${LANG:-C}}
case $LC_CTYPE in
   *.utf8|*.UTF-8)
    # All is correct
    ;;
   *)
    # Need to select an UTF-8 locale
    local -a available
    available=("${(f)$(locale -a)}")
    export LC_CTYPE=${${${${(@M)available:#*.UTF-8}[1]}:-${${(@M)available:#*.utf8}[1]}}:-C.UTF-8}
   ;;
esac
export LC_CTYPE

The export LC_CTYPE could be ignored if we only want to set it for the current shell, not any subprocess.
This way, if LC_CTYPE is already set correctly, we do nothing, otherwise, we select some UTF-8 locale.
I remember that C.UTF-8 is fairly recent (less than 5 years I think), so we cannot use it inconditionnaly.
Also, I absolutely don't know if you cannot just use inexistantlocale.UTF-8 and still get something correct. That would make C.UTF-8 always work and simplify a lot.
Also, locales can be aliased and an UTF-8 locale may not have UTF-8 nor utf8 in its name. However, I don't think this is reasonable to handle such special cases.
Moreover, if a user set LANG to fr_FR@euro, it is likely that their terminal doesn't support UTF-8 and they will get odd results. Generally, if the locale is not UTF-8, the user will likely run into other problems with other programs.

Sorry @vincentbernat, I forgot about this. Would you care to submit a PR? I like your last proposal a lot, you've made it very understandable thank you.

OK done. If people that were hit by this issue could test...


Clear all element value.

How can i clear all elements value?

You can go through the form elements and set their corresponding value in the FormModel to null.


KNOX-3042 - Correct KnoxToken comparator

What changes were proposed in this pull request?
Correct KnoxToken comparator so that TokenStateService.fetchTokens() would return all the tokens, even if their issue time is the same. If two tokens have the same issue time, then one with the smaller token id (uuid) will be revoked.
How was this patch tested?
So far only the existing tests are run and we could add a revocation test to TokenServiceResourceTest.

Hi @bonampak - could you add a unit test for this to clearly show what the failure was and that it is fixed and doesn't regress? Sorry for the delayed review here!


Not working with pnpm

I have an app that was using this with npm.  I switched to pnpm to install packages and now get this error for the same script.
><EMAIL_ADDRESS>start E:\app
> react-scripts -r @cypress/instrument-cra start

E:\app\node_modules\.pnpm\@cypress+instrument-cra@1.4.0\node_modules\@cypress\instrument-cra\index.js:72
require.cache[webpackConfigPath].exports = fakeConfig
                                         ^

TypeError: Cannot set property 'exports' of undefined
    at Object.<anonymous> (E:\app\node_modules\.pnpm\@cypress+instrument-cra@1.4.0\node_modules\@cypress\instrument-cra\index.js:72:42)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1244:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:475:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:72:3)
    at internal/main/run_main_module.js:7:1
 ELIFECYCLE  Command failed with exit code 1.

I'm getting the same error using "rush" tool.
Any updates on that?

Same issue with yarn and executing inside the cypress node docker

I'm having the same issue with pnpm (trying to switch from npm to pnpm).

If you are running inside the docker container, check out the node_modules path. My case was webpackConfigPath is different than where the actual node_modules folder is located.
check the require.cache object to see if there is the /node_modules/react-scripts/config/webpack.config.js


Provide an option to show editor title actions in custom title bar when editor tabs are hidden

Testing #196292
Provide an option to show editor title actions in custom title bar

Moving this to next milestone. Will also address making a single title bar menu (#195293)

verification steps:

Set workbench.editor.showTabs: none
Editor Actions will appear in the title bar
Right click title bar to open context menu, editor actions visibility can be hidden


Decrypt file with private key and passphrase

I read through the #20 thread and am still having some issues.
I have a key file mykey.asc that I received from a client. They key needs a passphrase to decrypt the file file.txt.pgp.
When I open the file.txt.pgp in a text editor, I think it's in binary. I do not see any PGP MESSAGE headers.
Here is my code. I'm using Laravel if that matters at all.
$ecryptedContents = Storage::get($filename);
        $asciiKey = Storage::get($keyfilename);

        $keyEncrypted = OpenPGP_Message::parse(OpenPGP::unarmor($asciiKey, 'PGP PRIVATE KEY BLOCK'));

        // Try each secret key packet
        foreach($keyEncrypted as $p) {
            if(!($p instanceof OpenPGP_SecretKeyPacket)) continue;

            $key = OpenPGP_Crypt_Symmetric::decryptSecretKey('passphrase', $p);

            $msg = OpenPGP_Message::parse(OpenPGP::unarmor($ecryptedContents, 'PGP MESSAGE'));

            $decryptor = new OpenPGP_Crypt_RSA($key);
            $decrypted = $decryptor->decrypt($msg);

            var_dump($decrypted);
        }

The var_dump statement just produces NULL. When I try to change the $msg variable to:
$msg = OpenPGP_Message::parse($ecryptedContents);

(since there is no header), I get a fatal error saying
ErrorException  : Decryption error
Totally new to all of this. I can decrypt it on the command line so that leads me to believe that it may be a configuration error.
Thanks

If $ecryptedContents is not in ASCII armor (no PGP MESSAGE headers) then you should not be calling OpenPGP::unarmor on it.

I tried it with 2048bits and the speed was fast.
test2048.php - Elapsed time:0.070176124572754 sec
test4096.php - Elapsed time:58.180878162384 sec
Source code:
test 2048 and 4096 bits.zip

i get the same issue. It's response NULL, any help, please

For anyone viewing this: check if both $msg and $key look reasonable -- if so, and decryption is still failing, please attach an example input file and key that you have the problem with so I can see if anything strange is happening.


占坑 database.md

I found translation also deepen my understanding

:+1:
注意：刚与英文文档做了同步，请将你本地的仓库与此仓库同步一下

ok


Development resume

Hi,
is there any chance of continued development in the near future?
Thanks

Hi, sorry for the long no reply.
Right now it's hard to predict when I'll be able to get back to the development of the thing.
I'm away from my equipment unfortunately and not sure when I'll be able to get a hold of it again until the war ends. Priority is now more toward projects helping to stop the war.
Can't promise much but I have a few ideas on how to leverage the community to help this project live.
Will try to put something out in the near future.

Courage to you especially


create NOTICE as stated in license guidelines

According to Apache License Document - Applying the license to new software, it's required to put a NOTICE file in the root folder with correct years and owners of the software.
I would recommend Swift to follow the best practices and hence made this sample NOTICE file. Feel free to change and edit this as appropriate.

I think the NOTICE file is only required (as a policy) for Apache Projects distributed by the ASF.
Other projects (outside the ASF) that use the Apache License only need the LICENSE file.

I think the NOTICE file is only required (as a policy) for Apache Projects distributed by the ASF.
Other projects (outside the ASF) that use the Apache License only need the LICENSE file.

Yes you were right. I missed that part in the LICENSE documentation.
Should I simply close this Pull Request or does Swift maintainers think we should still have it?

You can also search for other projects using the same license, and most of them don't have a NOTICE file.
Another issue is that 2014-2020 in the NOTICE file will probably not be updated (unless someone automates it).

You can also search for other projects using the same license, and most of them don't have a NOTICE file.
Another issue is that 2014-2020 in the NOTICE file will probably not be updated (unless someone automates it).

Thanks for the suggestion. I will probably close this PR.


tutorial: topology source host missing causes<EMAIL_ADDRESS>to crash

Hi,
I've tried to setup the freestanding SCION network as per the tutorial and ran into a few issues:
Using the default topology files from the website, the scion-router service always crashes because of an invalid source IP (see screenshot below):

@tobiasmoldan realized that this can be resolved by adding the source IP (or host name) to the local field in the topology:
"underlay": {             "local": "scion01:50012",             "remote": "scion02:50012"           },
Secondly, I was wondering if all ASes need to be up and running for the network to be fully functional? I have set up and configured scion01 and scion02 as per the tutorial. All services (daemon, router, control, dispatcher) are active and there is a direct link between the two VMs. The machines are pingable (via normal ICMP), however, there is no reachability via SCMP. I assume that, even without scion03-05, they should have connectivity?
I got scion addresses for scion01 and scion02 respectively,
42-ffaa:1:1,<IP_ADDRESS>
42-ffaa:1:2,<IP_ADDRESS>
and I have generated the certificate material on scion01 and shared it with scion02. Is there anything I'm missing - e.g., does path exploration need to be triggered somehow or should it happen automatically?
Thanks a lot for your help on this!
Best regards,
Thomas

This change is

Hi,
thanks for your response! Yes it's odd indeed. I have now configured scion03 as well (so all three core ASes are up and running). In Wireshark, I can even see path propagation packets being sent (and received) between all 3 ASes via UDP ports 50012, 50013, 50023, however, scion ping, showpaths and traceroute are still not working and outputting:
Error: fetching paths: no path available
I was wondering if you'd be available for a quick remote discussion sometime - then I could show you the setup?
Thanks,
Thomas

Hi @jiceatscion ,
I've now installed the SCION protocol dissector for Wireshark and I'm seeing the following messages being exchanged between the two ASes.

This is a request from scion01 -> scion02:

This is a response from scion02 -> scion01

Can you infer something from the BFD control messages?
Thanks!
Thomas

Not sure if we can learn much from the BFD messages. Those don't call for a response; they're just mutual keep-alive packets. If they weren't there, then we would have a hint of why paths aren't available.
Recently we found that Go v1.23 was including a ~bug in timers behavior that was breaking the control service RPCs. If you're building the last release, you shouldn't be affected. But if you're building from head, then make sure you've pulled past the fix that downgrades Go to 1.22.7

Hi @jiceatscion ,
Thanks for your reply! Unfortunately, that's not the case because I'm building the last release v0.11.0.


Slice of a polar plot

Is there a possibility of only displaying half of a polar plot?
As I can't seem to be able to do so.
Something like so:

Support for this was added in echarts version 5.5.0, we are currently using 5.4.2
I will try to create a PR soon-ish to upgrade to the new version.

If you are using the latest git version this will work now. In my PR I also attached a minimal example.


improve argument names in Widget trait

This removes the underscores in front of the argument names in provided Widget methods, in order to make an IDE-autofilled method signature more useful. This was done in a similar manner to https://github.com/Smithay/smithay/blob/bc1d7320f95cdf17f9e7aa6867cccc5903548032/src/xwayland/xwm/mod.rs#L330-L356
It also renames all instances where the Tree argument was named state, as Tree has a state field. This has led to confusion on my part a few times, with the IDE-autofilled method signature clashing with my own naming, in which case I assumed state was the widget's (downcasted) state, not the widget's tree. I can't think of any reasoning as to why it was named tree vs state in different methods, so it makes sense to me to make it consistent everywhere.

Assuming this change is desirable, would it not be better to favor #[allow(unused_variables)] over let _ = ...?

I don't really mind either way, I just copied how Smithay dealt with this issue. If #allow's are preferred I can take care of it as well.

You will rarely need to use all the arguments, so the usefulness is quite subjective.
I prefer to have to opt-in into arguments rather than opt-out.
In any case, this seems like we are adding complexity to the code for better IDE support. Shouldn't the issue be directly addressed in the LSP layer? Maybe a setting in rust-analyzer?

You will rarely need to use all the arguments, so the usefulness is quite subjective.

You do always need all of them if your widget has child widgets, which to be fair I'm not sure how common that is.
If that's not such a common scenario it would make sense to not remove the underscores, since this is just a small annoyance I noticed while working on a few widgets that had each other as children.

FWIW I've reverted the change with the underscores, only leaving the argument name changes, since that's the one that's caused me more confusion anyways.


Translation/traditional chinese

[ ] Integration tests (if applicable)

Closes #

Hi @kewang  — i'm not sure if you are trying to add a new translation, or replace the existing one. It is not clear from the description.
If you want to add a new translation, please add new README files and don't edit existing ones. Thanks!

Hi @mfix22
I just want to update current 臺灣 translation.


could this run on windows or does it rely on linux for the bluetooth

basicaly all in the title

I don't have a windows machine to test it, and my VM is notoriously picky about bluetooth.

ok i cant get it working on windows (also had issues that there is no official pyenv for windows), just wont detect the pinecil even though its paired and connected so im guessing the BLE stuff only works on linux and while i have plenty of linux machins around none of them have bluetooth

Ideally, you shouldn't have to pair anything. You turn on your iron, start the script and it should work. I'm using bleak library, and it says it's compatible with Win10. Do you see any errors in terminal?

nothing in the python console, in the web console it is just a device not found error, {status: 'ERROR', message: 'Device not found', command: 'GET_SETTINGS'}

im wondering if it is the address here https://github.com/builder555/pinecil-v2/blob/master/pinecil_ble.py#L76
is that the same for every pinecil? i know the BLE MAC address isnt

yup, i just noticed it, removed.

yep that did it

out of intrest, where did you get that full address? i can get the mac address but cant find any way to get the full one

That was a good old-fashioned "let me hard-code this just for now, i'll remove it before committing". Thanks for reporting it!
On MacOS it shows the UUID instead of the Mac address: https://bleak.readthedocs.io/en/latest/api/index.html?highlight=uuid

ah right that makes sense, so im guessing that if i put the mac address for mine in it would have worked too but i didnt think to try because i assumed it was a diffrent address

is that the same for every pinecil? i know the BLE MAC address isnt

the BLE name was  "pinecil"  for all of them  but Ralim asked me to put an Issue  Ticket into  main IronOS  a couple weeks ago for it to be "Pinecil+unique number". it probably will be changed in future  firmware as it's already being worked on.
https://github.com/Ralim/IronOS/issues/1545

are there  instructions  for how to set this  BLE settings for  Windows people?  Although I have access to  Mac,  I'm mostly on Windows testing the BLE features since  Joric's  Pinecil BLE browser pages  runs best on Windows PC and Android phones too.
if  I could get link to instructions that would be idea, then I could add link to Pinecil  Wiki for people to come to, or  work with someone to make instructions more clear and usable for larger number of people who are not familiar with Github.

@River-b i'll try to get a hold of a windows image to run on my machine and write down the steps tonight, haven't had the best luck with bluetooth on VMs.

this works  on any browser?  could it work on Android Phones too so people could have alternate display on phone and change set  temperature?

@River-b yes, but the backend has to run on a computer, then you can access it from any phone/tablet (including iphones) on the same network. The only caveat is that the iron needs to be within the bluetooth range of the computer running the backend. I'll update the repo in a couple of hours with those changes.

please try it out now

suddenly got busy with work. will give feedback when I can get to this later this week. thanks


[Question] Different multilingual identification methods

Hi
Thank you so much for making this available !
I had a question regarding the two different multilingual identification strategies mentioned in the code: StrictMultilingual and Multilingual.
Specifically, would it be possible to share why the StrictMultilingual strategy was preferred for dataset creation, and if there was any benchmarking done (downstream performance / human annotation / eyeballing results) to say one is better than the other ?
Would be grateful for any input on this : )
Thank you !

Hello!
Multilingual has been implemented before StrictMultilingual, and (if I recall correcltly) yielded results that were not sufficiently balanced in terms of "content by language", and had some issues with tiny documents.
StrictMultilingual ensures that you have a document that holds approximately the same minimum amount of data for each language, while keeping a threshold for non identified content.
While developing the two versions I did some eyeballing results and found a general better balance (and lower file size) using StrictMultilingual so we kept this one, and the performance cost seems marginal enough that it did not change drastically our corpus generation times. The multilingual subcorpus is now ~12GB (which is quite big compared to the median subcorpus size) and we may change/adapt the process following user feedback
However I agree (and it has been a subject before) that we should have some human-annotated test corpus to control results :)

Thank you for the response @Uinelj !
The one issue that I noticed in my experiments with the StrictMultilingual filter was that especially for documents that are bi-lingual, and FastText makes mistakes / incorrectly categorises some sentences as belonging to another language, the document is no longer classified as multilingual.
Eg: For an en - es document, FasText classifies  ~45% of sentences as en,  ~45% of documents as es, and 5% as it (usually incorrect). Then, by the strict filter logic, because it < 25%, the document is no longer classified as multilingual.
I have not looked at tiny documents w.r.t the Multilingual filter, but that is definitely a great point.


Introduce array of roleIds

https://github.com/HQ20/contracts/blob/4c4acb1328d35659f18f10f0bcdcd54a74071c31/contracts/access/Hierarchy.sol#L19
using an array instead of a single role would allow multiple roles to be granted access to a function.

Hi Alex. Yes, an array would allow several roles to be granted access to a function, but for this case I just needed to check membership to one role from addRole just below. I might implement your proposal in a separate contract. Let me think about it.

Hey Alberto, I proposed how this might be done here. Let me know your thoughts

That's a very well-written article, and interesting solution, congratulations.
There are two solutions to creating dynamic permissions. You can either leave the roles static and assign users to groups, which is what would happen with modifiers like onlyMinter. You can also leave the user groups static, and make dynamic modifiers like in your example, where instead of changing user membership to a role, you change roles required for a function.
So far, I've been able to use RBAC.sol (the precursor to AccessControl.sol) for everything I've come across in real life. AccessControl.sol just made it more efficient.
I wonder if the extra complexity is needed or not. If you come across a real world example where your solution was the best option it would make for a very interesting article.
I like your articles a lot, keep it up :+1:


Problem with Next 13

Hi. I'm trying to run MathView or just any mathlive component as client component in Next.js 13 :| but i just simply get a lot of errors.
Is there any way that somone here, way smarter than me (with is not hard) could provide working example?

There was recently a discussion on this topic at https://gitter.im/cortex-js/community.
I'm copying the relevant bits here:

The first step is to declare the web component as a JSX element in index.d.ts like so:

// index.d.ts

import { DOMAttributes } from "react";
import { MathfieldElementAttributes } from 'mathlive'

type CustomElement<T> = Partial<T & DOMAttributes<T>>;

declare global {
  namespace JSX {
    interface IntrinsicElements {
      ["math-field"]: CustomElement<MathfieldElementAttributes>;
    }
  }
}

Then create a component that wraps the <math-field> web component

// components>MathField.tsx

import { useEffect, useRef } from "react";
import {  MathfieldElement } from "mathlive";

const MathField = () => {
  // `MathfieldElement` works for TS
  const mathFieldRef = useRef<MathfieldElement>(null);

  useEffect(() => {
    mathFieldRef.current?.setOptions({
       // whatever
    });
  }, []);

  return (
    <math-field ref={mathFieldRef} />
  );
};

export default MathField;

and then import the component dynamically like this:

// MyApp.tsx

const ClientSideMathField = dynamic(() => import("components/MathField"), {
  ssr: false
})

const MyApp = () => {
// fancy stuff
  return (
    <ClientSideMathField />
  )
}

@arnog Sorry for late respond. I tried to implement it 1:1 how you show it here, but still I got errors from Next 13 :|
My general goal is to implement math-live & compute-enginge for displaying and calculating stuff...
Is it even possible on Next.13? And meaby CodeSandbox will help here?

Others have been able to do it, so it's certainly possible. I'm confident you will figure it out. Hard to provide more guidance without information about your code or the errors that you ran into, but best of luck.


dart:html inputMode should be nullable

https://api.dart.dev/stable/2.9.1/dart-html/Element/inputMode.html

Hey @mdebbar, I believe inputMode is nullable already. The docs you linked are for Dart 2.9.1 though which precedes the release of null safety.

@parlough thanks for the clarification! I linked to the one that showed up on Google Search and didn't notice the version number.
We don't need this issue anymore. Closing.


form feedback: show error response from backend

closes https://github.com/inveniosoftware/invenio-app-rdm/issues/1692
error message from backend

usual validation messages (to show they still work)

comment


Sensu server crash after a redis failover

Hi,
We observed that 3/5 sensu servers crashed after a redis failover exactly when master redis failed over to another node (we are using sentinel). We saw these in the logs. After we started the sensu server manually in 2/3 crashed ones, they identified the new master redis and started working again.
Here are my questions:

How many retry attempts will sensu attempt when it sees redis as slave? Our Haproxy settings for redis have RISE and FALL values as 1 right now. If needed we can revisit that.
Based on this observation, why didn't all 5 servers crash? 3/5 crashed and we manually started 2 of them. Is that expected?
Is it like sensu-servers crashed only on machines that were actively using redis and it is not necessary that all 5 sensu-server need to use redis at any given moment?

...skipping...
{"timestamp":"2015-11-25T00:59:57.202184-0800","level":"warn","message":"stopping"}
{"timestamp":"2015-11-25T00:59:57.202253-0800","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-11-25T00:59:57.202368-0800","level":"info","message":"completing event handling in progress","handling_event_count":0}
{"timestamp":"2015-11-25T00:59:57.202501-0800","level":"fatal","message":"redis connection error","error":"Redis server returned error code: READONLY You can't write against a read only slave."}
{"timestamp":"2015-11-25T00:59:57.202576-0800","level":"warn","message":"stopping"}
{"timestamp":"2015-11-25T00:59:57.202642-0800","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-11-25T00:59:57.202748-0800","level":"info","message":"completing event handling in progress","handling_event_count":0}
{"timestamp":"2015-11-25T00:59:57.202867-0800","level":"fatal","message":"redis connection error","error":"Redis server returned error code: READONLY You can't write against a read only slave."}
{"timestamp":"2015-11-25T00:59:57.202940-0800","level":"warn","message":"stopping"}
{"timestamp":"2015-11-25T00:59:57.203013-0800","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-11-25T00:59:57.203126-0800","level":"info","message":"completing event handling in progress","handling_event_count":0}
{"timestamp":"2015-11-25T00:59:57.203248-0800","level":"fatal","message":"redis connection error","error":"Redis server returned error code: READONLY You can't write against a read only slave."}
{"timestamp":"2015-11-25T00:59:57.203326-0800","level":"warn","message":"stopping"}
{"timestamp":"2015-11-25T00:59:57.203392-0800","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-11-25T00:59:57.203506-0800","level":"info","message":"completing event handling in progress","handling_event_count":0}
{"timestamp":"2015-11-25T00:59:57.203623-0800","level":"fatal","message":"redis connection error","error":"Redis server returned error code: READONLY You can't write against a read only slave."}

@kaushiksriram100 you can set "reconnect_on_error": true in your redis definition - https://sensuapp.org/docs/0.21/redis#definition-attributes This will cause Sensu to keep attempting to reconnect.

@portertech  got it. I will add that. thank you very much for that pointer. Also trying to see if you have any inputs on why only few crashed?

@kaushiksriram100 only a few of them attempted a Redis write operation during the failover time window.

@kaushiksriram100 I am going to close this issue, as it looks like "reconnect_on_error" solves it for you :+1:

My sensu-server still stops after I restart Redis with service redis onerestart. Here's the log:
{"timestamp":"2015-12-29T05:58:56.198354+0700","level":"warn","message":"reconnecting to redis"}
{"timestamp":"2015-12-29T05:58:56.198777+0700","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-12-29T05:58:56.199552+0700","level":"warn","message":"resigning as leader"}
{"timestamp":"2015-12-29T05:58:57.231074+0700","level":"info","message":"reconnected to redis"}
{"timestamp":"2015-12-29T05:58:58.246613+0700","level":"debug","message":"subscribing to keepalives"}
{"timestamp":"2015-12-29T05:58:58.247780+0700","level":"debug","message":"subscribing to results"}
{"timestamp":"2015-12-29T05:59:00.277057+0700","level":"fatal","message":"redis connection error","error":"Redis server returned error code: LOADING Redis is loading the dataset in memory"}
{"timestamp":"2015-12-29T05:59:00.277371+0700","level":"warn","message":"stopping"}
{"timestamp":"2015-12-29T05:59:00.277485+0700","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-12-29T05:59:00.277894+0700","level":"debug","message":"not currently the leader"}
{"timestamp":"2015-12-29T05:59:00.278003+0700","level":"info","message":"completing event handling in progress","handling_event_count":0}
{"timestamp":"2015-12-29T05:59:00.790844+0700","level":"warn","message":"stopping reactor"}

I wonder if this is related to the issue. Thanks!

My regis config looks like this:
  "redis": {
    "host": "localhost",
    "port": 6379,
    "reconnect_on_error": true,
    "auto_reconnect": true
  },

My Sensu version is 0.21. Here's gem list:
sensu (0.21.0)
sensu-extension (1.3.0)
sensu-extensions (1.4.0)
sensu-logger (1.1.0)
sensu-settings (3.1.0)
sensu-spawn (1.6.0)
sensu-transport (3.3.0)


Support for getters

I'm having trouble with my model getters not having access to the context  in the same way resolvers do, and therefore not able to batch some of my queries.
I'm not sure if this is a limitation in the library, or if i'm doing something incorrectly which means I have to pass a special context object around wherever I want batched queries.
My setup is as follows:
const context = createContext(sequelize); // must not be called before all models and associations are defined

const server = new ApolloServer({
  schema,
  context: async () => ({
    models,
    options: { [ EXPECTED_OPTIONS_KEY ]: context },
  }),
});

And when a custom resolver is hit, it looks like the below and this works with batching because of the context coming through:
someDate: async (someModel, params, context) =>
    someModel.getValueDateWithDefault(context, 8),

Where getValueDateWithDefault looks like:
async function ({ options }, valueId, defaultValue = undefined) {
  const value = (await this.getValue(options)) // method for an association created by sequelize
    // filter based on id
  return (value) ? value.valueDate : defaultValue;
};

So, I have been trying to create a pseudo property on the model which is in the form of a getter:
myPseudoProp: {
          type: VIRTUAL(FLOAT),
          get () {
              // context doesn't exist here so query isn't batched
              return this.getValueDecimalWithDefault(context, 18)
          },
        },

but this doesn't have the context coming through. Should I be doing something different or could the lib be extended to handle getters for models properties?

I'm not sure there's a way to get it to work, context has to be passed per call or you might get hit by a race condition. Not sure Sequelize passes down information passed to get so i don't think there's much you can do.


[Manual reviews] Some existing submissions not showing in the Review tab, then reappearing later on

There were multiple occurrences since last Friday when a student lab was showing "No submission" in the Review tab while there was a submission in the -labs repo. However, it shows all submission properly now even though there weren't any new pushes to the repositories (so it looks like the submissions have been recorded properly in the database on the initial push, just somehow not displayed in the Review tab).
Moreover, it looks like one TA could see a submission for several students, but it was showing "No submissions" for the same students and assignment for another TA.

Is this referring to the new frontend or the legacy one?

Is this referring to the new frontend or the legacy one?

Confirmed in the legacy UI, not sure about the new one, will update in case of any new information.

Closing as hopefully solved with the new frontend.


Boot process stuck at BOOT error

Hello, is the U500 project for nexys complete? I used the script Makefile.u500nexys4ddrdevkit to generate the mcs file and solidify it into the development board, and successfully generated the bbl.bin file in the freedom-u-sdk directory. Finally, the bbl.bin file was written using the script "sudo make DISK=/dev/sdb format-boot-loader", but during the subsequent startup process, it was stuck at BOOT

How can I fix it?

Is this fixed? Same issue happened here with Nexys A7-100T, Vivado 2020.2


WebUI - JWT token not sent search requests

Describe the bug
When using JWT tokens in the UI, searching always returns no results. Looking at the request made to /-/verdaccio/search/, the Authorization header is missing in the request.
If packages are protected by $authenticated in the config, this results in an authorization failure:
verdaccio_1  |  info <-- <IP_ADDRESS> requested 'GET /-/verdaccio/search/boo'
verdaccio_1  |  trace--- allow access for @boost/styles
verdaccio_1  |  trace--- [auth/allow_action]: user: undefined
verdaccio_1  |  trace--- [auth/allow_action]: hasPermission? false for user: undefined
verdaccio_1  |  trace--- forbidden access for @boost/styles. Error: authorization required to access package @boost/styles

Using:

Verdaccio 4.2.1 via docker-compose

Steps to reproduce the behavior:

Start verdaccio with below config and add any packages
Login to web portal
Note requests use JWT token
Attempt to search
Note missing JWT token in the search request
Note errors in verdaccio logs

Expected behavior
Search requests in the web UI should also include the JWT token if the user is logged in.
Docker || Kubernetes (please complete the following information):

Docker verdaccio tag: verdaccio:4
Docker Version 18.06.1-ce
Docker Compose Version: 1.24.1, build 4667896b

Configuration File (cat ~/.config/verdaccio/config.yaml)
Using defaults for security but enforcing $authenticated for all packages:
security:
  api:
    jwt:
      sign:
        expiresIn: 60d
        notBefore: 1
  web:
    sign:
      expiresIn: 7d

packages:
  '@*/*':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

  '**':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

Environment information
No changes to Dockerfile. For reference, here's verdaccio --info output:

  System:
    OS: Linux 4.14 Alpine Linux undefined
    CPU: (1) x64 Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
  Binaries:
    Node: 10.16.2 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm

Thanks @SamirMaina-districtm for reporting this. I'll move it to UI repo where is the perfect place for this.


TBLIS issue

Hi,
I tried to use Fermi on two Macs [M1 first, then Intel] both under Julia 1.6 and 1.8.
the failure on the Intel-Mac worries me, it's running Catalina, so that should be stable.
Fermi doesn't compile, because
Precompiling project...
✗ TBLIS
✗ Fermi
0 dependencies successfully precompiled in 4 seconds (103 already precompiled)
2 dependencies errored. To see a full report either run import Pkg; Pkg.precompile() or load the packages
Testing Running tests...
ERROR: LoadError: InitError: could not load library "/Users/marko/.julia/artifacts/bad39b751ed9b819c0e04ac492bb388e5b494858/lib/libtblis.0.dylib"
what am I doing wrong?
thanks.
marko

Hi @MarkoHorbatsch,
You are not doing anything wrong, I was having similar issues with TBLIS on mac. Unfortunately, I believe the problem is upstream.
TBLIS has been removed as dependency for that reason, but I haven't released a new tag. I should do it asap. If you still want to use TBLIS for tensor contractions within Fermi, you can simply import the blicontractor  library, which will overwrite the necessary functions from TensorOperatos.jl


Add connection pooling settings to LDAP documentation

Signed-off-by: cwillum<EMAIL_ADDRESS>Description
Upon request to add documentation for new pool pruning period and pool pruning idle time settings to LDAP documentation, it became apparent that all connection pooling settings keys needed to be added to LDAP documentation.
Issues Resolved
Added connection pooling settings to LDAP documentation:
pool.enabled: true
pool.min_size: 0
pool.max_size: 5
pool.idle_time: 2
pool.pruning_period: 1
Also created a new heading for advanced settings (which includes connection pooling settings) so that essential configuration for connection, authentication, and authorization are clearly distinct from these optional settings.
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@opensearch-project/security Could someone on the team have a look at this for technical accuracy? Thanks.

Will leave the v2.4 tag for this PR so that all five connection pooling settings are documented for this version of OS. I'll then create a new PR for v2.3 with only the three connection pooling settings pool.enabled, pool.min_size,  and pool.max_size. Then I'll backport this PR to 2.2, 2.1, 2.0, and 1.3.