Is there a way to weight the line items in a YAML file?

I'd like to have one of the items in the array be used more often than the others.

That would be to weight the tokens usage in a particular line item.
I want to weight the usage of the line item itself.

Could you elaborate? Perhaps provide an example prompt? In the example above, blue would be chosen 50% of the time red 33% of the time and green 17%
If you want to weight a wildcard, you could do something like:
{0.7::warm_colors|0.3::cold_colors}
Is that what you mean?

The yaml file might look like this:
demoran:
  - line item 1
  - line item 2

I want to have line item one selected more often than line item 2 when prompting demoran.


Breakup main tasks into mockable subroutines, support "v1" or "v2" schema per https://github.com/cisagov/pen-test-portal/pull/3

🗣 Description
To address #15, some of the major actions of the task are broken up into subtasks, and try to give a descriptive outer exception on what went wrong, while passing a trace and inner exception to preserve the "actual" error.
Additionally, this now supports "v1" and "v2" schemas as described @ https://github.com/cisagov/pen-test-portal/pull/3
💭 Motivation and context
I think this helps with readability and testability, since unit tests can now mock up e.g. the s3 test or test them against ephemeral services to make sure things are working correctly.
This is going to be necessary to adapt the changes from the pen-test-portal project as currently testing this task outside of it's native environment is difficult.
🧪 Testing
The new validation and update functions have test coverage now where none existed before.
Mocked database calls are checked to see if the main logic is correctly updating the back end database.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[ ] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[ ] ❌ These code changes follow cisagov code standards. While the new changes try to adhere to the linting and style rules as best as possible, there are overall issues with this document that I think it would be more harmful than helpful to change at this point for the sake of readability and containing scope of this change
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass. (pre commit hook does not pass, but it succeeds more than it did before!)

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Add a tag or create a release.

#49  covers the earlier verison of this.
The only really important comment out of there is:

I refactored out the "finding extraction" function into rdi.extract_findings and added some sanity checks so that my tests would stop crashing. It now should work for "v1" or "v2" data interchangably and will require the following addition into the "live" mapping file:

"id": "RVA ID"

@Yablargo Apologies for the complication but you will need to rebuild this pull request because of the merge of #50.

@Yablargo Apologies for the complication but you will need to rebuild this pull request because of the merge of #50.

No worries, looking at the deltas I think I can just remove the (now unnecessary) workflow changes

Continued at #55


[9.x] Fix unique locking on broadcast events

This is a fix for #43416. The lock was not being acquired because the broadcast manager was pushing straight to the queue and not using the dispatcher. Acquiring the lock within the queue method seems like the best option, as rewriting to use a dispatcher seems like it could cause a ton of headaches.

Now uniqueVia is not respected right?

I think we can eliminate the UniqueBroadcastEvent, as it's not needed since we can generate the lock key from the event. I think there's also a potential issue with having uniqueVia be a property, as I believe the cache repository can't be serialized.


No test cases for replace is generated

Description
For the following code, only one successful test case (str = str.trim(); return str.toLowerCase();) is generated.
public String trimReplace(String str) {
    if (str.startsWith("1234567890")) {
        str = str.replace("3", "A");
    } else {
        str = str.trim();
    }

    if (str.startsWith("a")) {
        str = str.replace("a", "1");
    }

    if (str.charAt(0) == 'x') {
        return str;
    } else {
        return str.toLowerCase();
    }
}

It seems that this behavior is caused by the executeConcretely fallback in the UtString implementation of replace: see #74
To reproduce
Generate the test suite for the method.
Expected behavior
Several tests that cover all possible executions.
Actual behavior
Single test that covers only calls to trim and toLowerCase.
Environment
Any environment (it is an engine issue).

Requires additional investigation, related to Sat-1475


Updated Edit page hint text

CHANGED:
"For a short answer of up to x characters"
TO:
"For a short answer"
AND CHANGED:
"For longer answers of up to x characters"
TO:
"For a longer answer"
WHY:
Because even if we have an max limit, I don't think it's helpful to say what it is here as it will be very high.
CHANGED:
"The answer will be checked to make sure it's in the numeric format"
TO:
"Requires a numerical answer"
WHY:
shorter
CHANGED:
"To collect an address with separate input fields - line 1, line 2, town or city, county and postcode"
TO:
"To collect an address with separate fields for line 1, line 2, town or city, county and postcode"
WHY:
'input fields' is maybe a bit jargony.
CHANGED:
"The answer will be checked to make sure it's in the format of an email address"
TO:
"Requires an answer in the format of an email address"
WHY:
shorter. Also made this change for the phone number and National Insurance options.
CHANGED:
"The answer will be validated to check it’s in the selected format."
TO:
"The answer will be checked to make sure it’s in the selected format."
WHY:
'validated' is a bit jargony.

Awesome, looks great! You ok to press 'Merge' @hannahkc? x

dones! thank you!
On Tue, 26 Jul 2022 at 16:48, agz deberny @.***> wrote:

Awesome, looks great! You ok to press 'Merge' @hannahkc
https://github.com/hannahkc? x
—
Reply to this email directly, view it on GitHub
https://github.com/alphagov/forms-prototypes/pull/111#issuecomment-1195656731,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF3XHE6FW7RGXJ7D36D66E3VWACEXANCNFSM54WMUPDA
.
You are receiving this because you were mentioned.Message ID:
@.***>


pull request for e2e test at 12/15/2016 15:45:21

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat: convert image to grayscale

Closes #287
Summary of Changes

feat: Added method that returns converted grayscale image but leaves the original unchanged.

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ PYTHON
black
2
2
0
0.86s

✅ PYTHON
mypy
2

0
1.81s

✅ PYTHON
ruff
2
2
0
0.02s

✅ REPOSITORY
git_diff
yes

no
0.0s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by

:tada: This PR is included in version 0.14.0 :tada:
The release is available on:

v0.14.0
GitHub release

Your semantic-release bot :package::rocket:


Add timeout on secure websocket receive method

This PR closes #133 by adding a timeout on the Websocket's receive method. This way the lock on the client isn't held until the next message is received.

I can't currently add you as a reviewer @nshaaban-cPacket, but I've send you an invite to change this. If you've got time I would feel safer if you would review the PR, otherwise I would just trust my and Aarons tests.


Make complement_stain_matrix compute the cross-product.

What complement_stain_matrix currently computes is not the cross-product.
This change uses NumPy's cross method to compute the desired cross-product.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #260   +/-   ##
=======================================
  Coverage   44.26%   44.26%
=======================================
  Files           2        2
  Lines          61       61
=======================================
  Hits           27       27
  Misses         34       34

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 e3f3577...0522dde. Read the comment docs.

@cooperlab Can you please review this?

LGTM.
The original I believe is from the paper (which has some mathematical errors). We rarely use the complement so I don't think this was causing any issues.

In this repo itself, the only use of complement_stain_matrix is used in the (non-adaptive) color_deconvolution routine if only two stain vectors are passed (i.e., the third is all zeroes).


After activation you are left on a blank screen

Describe the bug
On first install after entering the activation code, you are left on a blank screen and have to refresh the page to be redirected to the workflows
To Reproduce
Steps to reproduce the behavior. Think about:

Install Flow into a fresh DB
Navigate to flow
Enter the activation code

Expected behavior
Automatically redirected to My Workflows
Additional context
Chrome. Using 3.4 Release Candidate.

Hey @BenjaminRuby did you make any progress on this since the Community call?

@timrbula @morarucostel to work together to fix this

@timrbula to try again

@morarucostel Can you try with the 3.9.0 build of flow.client.web?


Pulumi/Pulumi does not use Pulumi/Base

What happened?
The pulumi/pulumi image uses python as a base image.
Ideally, we'd like pulumi/pulumi (a.k.a. the kitchen sink image) to share layers with the base image, so that caching the base image speeds up downloading the kitchen sink image. This is useful in contexts where one cluster is deploying both the kitchen sink image and the base image.
Steps to reproduce
Inspect the shared layers between pulumi/pulumi and pulumi/base and see that no layers are shared.
Expected Behavior
Expected the kitchen sink docker image to start with (on line 16):
FROM pulumi/pulumi-base:${PULUMI_VERSION}

Actual Behavior
It actually starts with FROM debian:11-slim
Output of pulumi about
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

This doesn't provide us too much now that the base image starts with Debian.


Update consensus-basics.md

@Smurph1k is this an intentional PR?
If so, what is the purpose of it?
If not, feel free to delete or we will remove it later this week

Можете удалить
вт, 7 мая 2024 г. в 16:54, ClydeWallace22 @.***>:

@Smurph1k https://github.com/Smurph1k is this an intentional PR?
If so, what is the purpose of it?
If not, feel free to delete or we will remove it later this week
—
Reply to this email directly, view it on GitHub
https://github.com/Chia-Network/chia-docs/pull/555#issuecomment-2098467872,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVARZ44PSJIGVQDF3FQXVMTZBDMKJAVCNFSM6AAAAABHK6Y5ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYGQ3DOOBXGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Virustotal shows multiple threats

I scanned it with virustotal website and it shows harmful application
Virustotal Scan result for latest version.

That seems like a false positive.

#6 #7


Modify README.md

There are some mistakes in the README.md file ,
There are two places where (Website with Intermediate )tag is mentioned

should correct it
@ming-tsai can you assign it to me

@ming-tsai then can we modify that action manually

Well... I guess if modify manually it will replace it when the bot run.


Fix VQE result, add ansatz

Summary
On #8702 and #8640, the eigenstate was removed from the eigen-result classes, which has affected certain workflows in qiskit-nature (@mrossinek).
This PR adds the ansatz to the eigensolver/minimum_eigensolver results so that the eigenstates can be retrieved from the result directly (in other words, making the result self-contained).
Details and comments
In the future, I believe the VariationalResult class should be reviewed, and potentially include this ansatz property. But so far the eigensolver result does not inherit from VariationalResult, and for the sake of including this fix into the upcoming 0.22 release, I have decided to add it to the Eigen-results directly.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 19 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 84.645%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
61434

Relevant Lines:
72578

💛  - Coveralls


Use python-version instead of version in GitHub Actions

It's deprecated since https://github.com/actions/setup-python/commit/6f6fcee33085a7661a7333ea58b4e32714b0f91f.
Demonstration: https://github.com/atugushev/pip-tools/commit/812a4c8d439a42ae4f3f72b5a82e39471d41e85b/checks
I've cancelled travis and appveyor CIs manually to not waste a time.

@atugushev sorry, no idea / experience with GitHub actions.

Thanks, @codingjoe, as always!


RoyalApps.RoyalTS version 6.1.50425

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Not sure what I should do now. I used wingetcreate to submit the manifest. If it's not compliant, I'm not sure what else I can do.

Hopefully you saw https://github.com/microsoft/winget-pkgs/pull/58803#discussion_r858509271
Current issue:
Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest.
actual 'manifests\r\RoyalApps\RoyalTS\6.1.50425',
expected 'manifests\r\RoyalApps\RoyalTS\6.1.50425.0'

Press . to open VSCode Online and rename the version folder name from 6.1.50425 to 6.1.50425.0


handle undefined oldData initially (fixes side effect of https://github.com/aframevr/aframe/pull/2840)

apparently what happened is that now with latest aframe master, the first call to update() immediately after init() passed in undefined for oldData, which broke the previous code.


pnpm install 提示 ERR_PNPM_INVALID_OVERRIDE_SELECTOR  Cannot parse the "//" selector in the overrides

拉取代码后，安装依赖提示
pnpm install 提示 ERR_PNPM_INVALID_OVERRIDE_SELECTOR  Cannot parse the "//" selector in the overrides
fix
"resolutions": {
"//": "Used to install imagemin dependencies, because imagemin may not be installed in China. If it is abroad, you can delete it",
"bin-wrapper": "npm:bin-wrapper-china",
"rollup": "^2.56.3"
},
删除package.json 中的 //。一行

果然删除这行就行了


Updates to add completions for newer nx projects

Oh, wonderful! I haven't been using Nx for a while until this month where I started on a new project where it's already using the new (not that new though :D ) format. So I realized I need to update it – well not anymore! Thanks sir! 🙇

It looks there might be bug – or at least it does't work for my project. Let me try to wire some fix for it.

@jukben Have you got fd installed? If so, would you mind trying it instead of find and seeing if the performance improves for you?

That's just slightly better – like not 7s but 6.7s 😅. The problem is that (I guess) it runs sequentially (find -> read -> save to variable for later usage...).
I was thinking about some hack to overcome it and dig into Nx's caches and look! It's order of magnitude faster because they already precompile it as part of nx runs.. obviously it will require to run nx before, but it handles cache invalidations, etc. so I think this is good compromise, thougths?
function __nx_run
    if test -e nx.json; and type -q jq
        if test -e .cache/nx/nxdeps.jsona
            jq -r '.nodes | to_entries | map("\(.key as $project | .value.data.targets | keys | map("\($project):\(.)") | .[])") | .[]' .cache/nx/nxdeps.json
        end
    else if test -e workspace.json; and type -q jq
        jq -r '.projects | to_entries | map("\(.key as $project | .value.targets | keys | map("\($project):\(.)") | .[])") | .[]' workspace.json
    end
end

I think that's pretty awesome, but might cause issues on fresh projects. I'm not sure which commands make nx populate the cache, and in my project I don't even seem to have a .cache/nx/nxdeps.json so I'm not 100% sure the approach will work for every nx monorepo.
That said, I think the ideal solution would look like:

Check for .cache/nx/nxdeps.json

If found, use it for completions
If not found,

Run the nx command that will populate the cache
Otherwise parse using fd + jq (as I did in the PR)

WDYT?


Possible to add the ability to disable the fan and dry accessories in the Home app?

Sorry for the very late response. I haven't had any time for this project.
This seems like a good addition.

If the fan accessory is disabled, how would you control the split system in fan-only mode (or would you expect not to use that feature of the split system)?

I personally don't use the dry accessory, just be nice to have the option to disable whatever you don't use. The sensibo plugin uses this feature.

Makes sense.  I'll try and find some time to add that option.


SIGNATURE VERIFICATION FAILED!

I see there are other issues identical to mine in here. So I'm just posting to show this issue isnt limited to their setup/device. I'm running ubuntu 20.04 and I just installed it last week.

Which version of torbrowser-launcher are you running? How did you install it?

duplicate #605
duplicate #606


Incorrect scope alteration of function by redeclaring as 'var'

Tested with Closure compiler v20200614
in.js:
"use strict";

self.global1 = "foo";

{
	function foo(p) { self["external1"](p) }
	let local = self["external2"]();

	console.log(foo(local));
	console.log(foo(local));
}

Command:
java -jar ./closure-compiler.jar --js in.js --js_output_file out.js --compilation_level ADVANCED --language_in ECMASCRIPT_2015 --language_out ECMASCRIPT_2015 --strict_mode_input --formatting PRETTY_PRINT
This produces out.js:
'use strict';
self.a = "foo";
{
  var a = function(c) {  // <-- ERROR
    self.external1(c);
  };
  let b = self.external2();
  console.log(a(b));
  console.log(a(b));
}

Notice that:

self.global1 was renamed to self.a
function foo was redeclared as var a
var a outside a function overwrites the global variable, breaking code relying on self.global1

Note that some brief testing shows that inside the scope block, function foo is scoped to that block only. However a var declaration is global, even inside the scope block (presumably because it's not a function). Therefore by redeclaring a function with var inside a scope block, its scope is unintentionally expanded to global, where it trashes global variables that happen to have the same name.

I just realised this doesn't reproduce if you use window instead of self. So I guess Closure doesn't recognise that in a browser context self is an alias for window?

Thanks for the report.  There are a couple of things going on here.

Generally, the compiler treats property and variables as being in separate namespaces when renaming.  You can avoid this the conflict by using an "output_wrapper"  (--isolate_mode=IIFE).  It makes a best effort to avoid the conflict with "GatherRawExports" which recognizes window and top but not self currently.

It should be updated to recognize both self and globalThis.

"Normalize" was originally written for ES3 code, tries to avoid block scoped function whose behavior was not consistent between browsers and rewrote block scoped function declarations as var declarations .   ES5 changed that and specifically banned block scoped functions in strict mode.   Assuming strict mode behavior is useful for the compiler, and to foster adopting strict mode, we continued to rewrite block scoped function declarations when the compiler warnings were ignored or suppressed.

With ES2015 and later the behavior is simply wrong, and we should remove the normalization and the behavior is well defined but we might need to do that in a couple of steps to shake out optimizations that are intentionally or not assuming there are no block scoped function declarations.
Potentially, we just rewrite them as "let x = ..." to avoid the scope busting, if we don't do that in global scope (global function declarations appear on the global "this"  but "let", "const" and "class" do not.

We need to make sure that the "MoveFunctionDeclarations" doesn't also break it, but that is less important

This should now be fixed now that b3627dfcd0aa2ef01c975b0a5855d5ac828cc3ac has been committed and will be part of the next release if we don't need to roll it back for some reason.


Api temporali

You are applying for validated OSS program

[X] My project is OSS licensed and open to public. (Must have LICENSE file)
[X] My project is has more than 5 ⭐stars on Github, which is the required for this program.

Repository URL to your project
Sorry i don't have one yet
URL to your website
not use
Expected Quota of usage
5 maximum per day
Details
- Category:
- License:
- Date of release:

Anything else?
Hi, im a Student of University ORT and I have a project and i need the api to use with api replicate. Can you give us a extended API Key until August please? Thank you

I'm sorry to tell you that your application does not meet our policy : (


Implement update my profile endpoint

Description:
This issue involves implementing an API to update the profile details. The endpoint should allow clients to make a PUT request to {{baseUrl}}/api/me.
sample response body:
{
    "created_at": "2023-06-29T09:15:00Z",
    "updated_at": "2023-06-30T16:45:00Z",
    "primary_email"<EMAIL_ADDRESS>    "contact_email"<EMAIL_ADDRESS>    "first_name": "John",
    "last_name": "Doe",
    "image_url": "https://example.com/mentor_profile_image.jpg",
    "linkedin_url": "https://www.linkedin.com/in/johndoe",
    "type": "DEFAULT",
    "uuid": "12345678-1234-5678-1234-567812345678"
}

Tasks:

Create a controller for the /controllers/profile endpoint in the backend (create the route profile if not created).
Parse and validate the request body to ensure it matches the expected format.
Implement appropriate error handling and response status codes for different scenarios (e.g., validation errors, database errors).
Write unit tests to validate the functionality and correctness of the endpoint.

API documentation: https://documenter.getpostman.com/view/27421496/2s93m1a4ac#8744a3ee-970f-489a-853d-8b23fdee8de3
ER diagram: https://drive.google.com/file/d/11KMgdNu2mSAm0Ner8UsSPQpZJS8QNqYc/view
Acceptance Criteria:

The profile API endpoint /controllers/profile is implemented and accessible via a PUT request.
The request body is properly parsed and validated for the required format.
Appropriate error handling is implemented, providing meaningful error messages and correct response status codes.
Unit tests are written to validate the functionality and correctness of the endpoint.

Additional Information:
No
Related Dependencies or References:
No

Can i work on this ?


Print app pulic URL after upload

Print app public url from response. Output is like
Application uploaded successfully.
Application public url https://rink.hockeyapp.net/apps/1234567890abcdef1234567890abcdef

Thanks for your PR


Revert "Documentation for custom Node Selectors"

Reverts okteto/docs#736

@pchico83 , sorry I got button happy and Squashed and Merged before reading your comment to merge after chart 1.20 release

@pchico83 , sorry I got button happy and Squashed and Merged before reading your comment to merge after chart 1.20 release

No worries, it's a problem in our process :-)


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In b5d656b, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 8482 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in 444cad7.


Dev

update version from 1.1.4 to 1.2.0 and add version description include some features , details in readme

邮件已经收到，谢谢！


libvast/vast/expected.hpp:10:27: error: ‘no_error’ is not a member of ‘caf’  constexpr auto no_error = caf::no_error;

Make for VAST fails for most recent Version of CAF+VAST.
libvast/vast/expected.hpp:10:27: error: ‘no_error’ is not a member of ‘caf’
constexpr auto no_error = caf::no_error;

Hi Marcin,
I think no_error was only recently added and is not yet merged into the master.
VAST depends on the develop branch of CAF. Which branch are you using?
Raphael

I just did git clone https://github.com/vast-io/vast.git, is this the wrong branch?

For VAST that is fine, but for CAF you should git checkout develop.

I just did git clone https://github.com/actor-framework/actor-framework.git. Yep, that's the wrong branch. git checkout develop helped. @josephnoir thank you for the fast support!


Update urllib3 from 1.26.17 to fix vulnerability

Update urllib3 from 1.26.17 to fix vulnerability:

to 2.0.7 in e2e
to 1.26.18 in the rest of the components

This should fix 12 dependabot alerts.
Supersede and close #1994.
Supersede and close #1995.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (47171d7) 86.71% compared to head (404b5e1) 90.68%.
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1996      +/-   ##
==========================================
+ Coverage   86.71%   90.68%   +3.97%
==========================================
  Files          44      246     +202
  Lines        2597    15424   +12827
==========================================
+ Hits         2252    13988   +11736
- Misses        345     1436    +1091

Flag
Coverage Δ

jobs_cache_maintenance
95.30% <ø> (?)

jobs_mongodb_migration
86.32% <ø> (?)

libs_libapi
88.33% <ø> (ø)

libs_libcommon
92.23% <ø> (?)

services_admin
85.86% <ø> (?)

services_api
86.79% <ø> (ø)

services_rows
84.90% <ø> (ø)

services_search
80.04% <ø> (ø)

services_sse-api
94.16% <ø> (ø)

services_worker
92.56% <100.00%> (?)

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

Files
Coverage Δ

...worker/job_runners/split/descriptive_statistics.py
94.80% <100.00%> (ø)

...orker/src/worker/job_runners/split/duckdb_index.py
88.73% <ø> (ø)

... and 200 files with indirect coverage changes

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


Remove zeroes from input files

A large number of zeroes introduced through de-facing and de-earing of images (for HIPAA compliance) can impact some of the metrics in the QAP results falsely.
Introduce a feature to have true zeroes (which are very rare in MRI images/timeseries) removed before they are sent to the QAP metrics workflow.

This has been implemented in 1.0.7.


fix(deps): update aws-sdk-go-v2 monorepo

This PR contains the following updates:

Package
Type
Update
Change

github.com/aws/aws-sdk-go-v2/config
require
patch
v1.27.23 -> v1.27.24

github.com/aws/aws-sdk-go-v2/credentials
require
patch
v1.17.23 -> v1.17.24

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

github.com/aws/aws-sdk-go-v2/service/ssooidc
v1.26.1 -> v1.26.2


Replace synchronized method/block with reentrant lock

Virtual threads suffer when performing a blocking operation inside a synchronized method/block, and it is recommended that the synchronized method/block be replaced with a ReentrantLock.
More details: https://docs.oracle.com/en/java/javase/21/core/virtual-threads.html#GUID-04C03FFC-066D-4857-85B9-E5A27A875AF9

related: https://github.com/vavr-io/vavr/issues/2760

Would you be willing to backport it to version/0.x? If not, I will handle that for you

Would you be willing to backport it to version/0.x? If not, I will handle that for you

Yes sure, I can backport it to version/0.x branch.


Enhancement:  Add support for * and ? wildcards for file matching

Having support for wildcards would be very useful, such as when one needs to delete several files that match a pattern.
e.g. *DELETE *.BBC

@tonedef71 FYI support for this feature was added to the latest Console8 MOS 2.2.0 release

Improved support for wildcards in filenames, including support for the ? wildcard, is coming to Console8 MOS 3.0.  An alpha release of that is now available


Make commit a public method. Introduce a auto-commit config. Relates …

…issue https://github.com/uber/hoodie/issues/58

fixes #58

LGTM


brew update/brew upgrade failing with Error: Not a directory @ dir_s_rmdir error

Description
On some scheduled jobs on macOS, since few days the brew update and brew upgrade are failing.
Area for Triage:

Question, Bug, or Feature?:

Bug
Virtual environments affected

[x] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Ubuntu 20.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
The commands:

brew update
brew upgrade

Should work fine.
Actual behavior

brew update
brew upgrade
commands fail with error:

==> Summary
🍺<EMAIL_ADDRESS>4,304 files, 59.5MB
Removing<EMAIL_ADDRESS>(4,296 files, 58.9MB)
Removing<EMAIL_ADDRESS>(15.8MB)
Error: Not a directory @ dir_s_rmdir - /usr/local/Cellar/openssl
==> Upgrading<EMAIL_ADDRESS>1.1.1h -> 1.1.1h
Removing: /usr/local/Cellar/openssl/1.0.2t... (1,787 files, 12.4MB)
Error: Process completed with exit code 1.

Repro steps
A description with steps to reproduce the issue. If your have a public example or repo to share,
please provide the link.

Run brew update
Run brew upgrade

I do not have a mac so I can't try to reproduce this, but I checked online and it seems that it is affecting other CI systems: https://github.com/dotnet/runtime/pull/43299 .

Example of failing build: https://github.com/robotology/robotology-superbuild/runs/1248677157 .

Hey, @traversaro !
It seems that openssl (Cellar/openssl/1.0.2t) that is the cause of the error will be removed from macOS images soon, the link to corresponding PR
for now you can workaround this issue with
brew uninstall<EMAIL_ADDRESS>
command before
brew update
brew upgrade

I have tried to install your dependencies from https://github.com/robotology/robotology-superbuild/blob/master/.github/workflows/ci.yml and
          brew uninstall<EMAIL_ADDRESS>          brew cask install xquartz
          brew update
          brew upgrade
          brew install ace boost cmake eigen gsl ipopt jpeg libedit opencv pkg-config qt5 sqlite swig tinyxml
          brew install libmatio
          brew tap osrf/simulation
          brew install osrf/simulation/gazebo11
          brew install ninja

works correctly.
Could you please check the provided workaround?
Thank you!

Thanks!

Thanks a lot! I tried the workaround in https://github.com/robotology/robotology-superbuild/pull/493 , but doing that in my CI results in this failure:
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /usr/local/Homebrew/Library/Taps/local/homebrew-openssl failed!
Fetching /usr/local/Homebrew/Library/Taps/local/homebrew-python2 failed!
fatal: invalid upstream 'origin/master'
fatal: invalid upstream 'origin/master'

@traversaro , seems that happens because of homebrew version, could you please try to run:
brew uninstall<EMAIL_ADDRESS>brew uninstall<EMAIL_ADDRESS>brew untap local/openssl
brew untap local/python2
brew cask install xquartz
brew update
brew upgrade
brew install ace boost cmake eigen gsl ipopt jpeg libedit opencv pkg-config qt5 sqlite swig tinyxml
...

it should help.
Thank you!

Thanks a lot @LeonidLapshin , your workaround is working fine!

@traversaro This still not fixed and the issue was re-introduced yesterday, any idea when this will be fixed again?

Workaround is not working for me. That is, doing
brew uninstall<EMAIL_ADDRESS>
before
brew update

simply results in
Uninstalling<EMAIL_ADDRESS>(1,787 files, 12.4MB)
Warning: The following may be<EMAIL_ADDRESS>configuration files and have not been removed!
If desired, remove them manually with `rm -rf`:
  /usr/local/etc/openssl
<EMAIL_ADDRESS>
And, whether or not a manually rm -rf those directories, it is all followed by the same error I was getting before, namely ...
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /usr/local/Homebrew/Library/Taps/local/homebrew-openssl failed!
Fetching /usr/local/Homebrew/Library/Taps/local/homebrew-python2 failed!
fatal: invalid upstream 'origin/master'
fatal: invalid upstream 'origin/master'

@rdzman,
brew untap local/homebrew-openssl
brew untap local/homebrew-python2
brew update

Thanks @al-cheb. That worked.

So there's no fix for this, just the workaround for everyone to do themselves?

So there's no fix for this, just the workaround for everyone to do themselves?

And if that's the case, shouldn't this issue be left open until there is a real fix?

Reopening.
Fix was done in https://github.com/actions/virtual-environments/pull/1889 and will be deployed everywhere in 3-4 days

Even with the workaround suggested in this issue, now the brew upgrade step is failing with:
==> Pouring<EMAIL_ADDRESS>Error: The `brew link` step did not complete successfully
Warning: These files were overwritten during `brew link` step:
The formula built, but is not symlinked into /usr/local
Could not symlink lib/pkgconfig/python3-embed.pc
Target /usr/local/lib/pkgconfig/python3-embed.pc
is a symlink belonging to<EMAIL_ADDRESS>You can unlink it:
  brew unlink<EMAIL_ADDRESS>
I am not sure if this is related to https://github.com/actions/virtual-environments/issues/1929 .

The same error occurs even by removing the workaround mentioned in this issue, so it is probably a different problem, but it is anyhow still related to brew update/brew upgrade failing.

For the new problem mentioned in https://github.com/actions/virtual-environments/issues/1811#issuecomment-718475660, adding brew unlink<EMAIL_ADDRESS>as suggested by the Homebrew error seems to be effective, see https://github.com/robotology/robotology-superbuild/pull/509#issuecomment-718494055 .

@traversaro I believe the new issue you mention (reported in Homebrew/homebrew-core#63619) has also been fixed now, in Homebrew/homebrew-core#63665.

@traversaro the new image has been deployed and
brew update
brew upgrade

works just fine!
I'm going to close the issue, but please feel free to contact us if you have any concerns.
Thank you!

brew cleanup gives the same error

Just by running
brew cleanup

I get the following error:
Run brew cleanup
Error: Not a directory @ dir_s_rmdir - /usr/local/Cellar/openssl
Removing: /usr/local/Cellar/openssl/1.0.2t... (1,787 files, 12.4MB)
Error: Process completed with exit code 1.

The action doesn't run anything else... https://github.com/nunorafaelrocha/dotfiles/runs/1402373738?check_suite_focus=true

@miketimofeev the problem isn't because of brew update or upgrade.
Just by running
brew cleanup

I get the following error:
Run brew cleanup
Error: Not a directory @ dir_s_rmdir - /usr/local/Cellar/openssl
Removing: /usr/local/Cellar/openssl/1.0.2t... (1,787 files, 12.4MB)
Error: Process completed with exit code 1.

The action doesn't run anything else... https://github.com/nunorafaelrocha/dotfiles/runs/1402373738?check_suite_focus=true

@nunorafaelrocha Sorry for the late answer — this is also related to the outdated openssl formula, which will be removed in the following month. Could you please create a new issue if it's a severe problem for you and we'll try to find a temporary workaround?

Hi @miketimofeev 👋
Forgot to post here, I've founded a workaround 😄
Added a step where I delete openssl
      - name: Workarounds
         run: |
           brew uninstall<EMAIL_ADDRESS>           rm -rf /usr/local/etc/openssl
           rm -rf<EMAIL_ADDRESS>

Reply

The above solution is now invalid (not working).
So after many tests, I finally solved this problem.
Add it before brew update.

Fixed
    - name: TemporaryFix - Brew Package Management (Github/Action#1811)
      run: |
        brew uninstall --force --ignore-dependencies openssl
        brew cleanup -s openssl
        brew cleanup --prune-prefix
        brew install openssl
        brew link --overwrite openssl

Reply

The above solution is now invalid (not working).
So after many tests, I finally solved this problem.
Add it before brew update.

Fixed
    - name: TemporaryFix - Brew Package Management (Github/Action#1811)
      run: |
        brew uninstall --force --ignore-dependencies openssl
        brew cleanup -s openssl
        brew cleanup --prune-prefix
        brew install openssl
        brew link --overwrite openssl

Reply

The above solution is now invalid (not working).
So after many tests, I finally solved this problem.
Add it before brew update.

Fixed
    - name: TemporaryFix - Brew Package Management (Github/Action#1811)
      run: |
        brew uninstall --force --ignore-dependencies openssl
        brew cleanup -s openssl
        brew cleanup --prune-prefix
        brew install openssl
        brew link --overwrite openssl
        brew uninstall --force --ignore-dependencies python
        brew cleanup -s python
        brew cleanup --prune-prefix
        brew install python
        brew link --overwrite python

Reply

The above solution is now invalid (not working).
So after many tests, I finally solved this problem.
Add it before brew update.

Fixed
    - name: TemporaryFix - Brew Package Management (Github/Action#1811)
      run: |
        brew uninstall --force --ignore-dependencies openssl
        brew cleanup -s openssl
        brew cleanup --prune-prefix
        brew install openssl
        brew link --overwrite openssl
        brew uninstall --force --ignore-dependencies python
        brew cleanup -s python
        brew cleanup --prune-prefix
        brew install python
        brew link --overwrite python

Solution

The above methods are now invalid (not working).
After many tests, this can solve this problem.
Add this before brew update.

Action
    - name: TemporaryFix - Brew Package Management (Github/Action#1811)
      run: |
        brew uninstall --force --ignore-dependencies openssl
        brew cleanup -s openssl
        brew cleanup --prune-prefix
        brew install openssl
        brew uninstall --force --ignore-dependencies python
        rm $(which 2to3)
        brew cleanup -s python
        brew cleanup --prune-prefix
        brew install python

Solution

The above methods are now invalid (not working).
After many tests, this can solve this problem.
Add this before brew update.

Action
    - name: TemporaryFix - Brew Package Management (Github/Action#1811)
      run: |
        brew uninstall --force --ignore-dependencies openssl
        brew cleanup -s openssl
        brew cleanup --prune-prefix
        brew install openssl
        brew uninstall --force --ignore-dependencies python
        rm $(which 2to3)
        brew cleanup -s python
        brew cleanup --prune-prefix
        brew install python

Hi, I am running into the same error when running 'brew update':
(venv) (base) patrickchong@Patricks-MacBook-Pro microblog % brew update
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /opt/homebrew/Library/Taps/company/homebrew-team failed!
fatal: 'origin/master' is not a commit and a branch 'master' cannot be created from it
fatal: invalid upstream 'origin/master'
Any ideas how to fix this? I tried some of the above but it doesn't help!

Same here. Even after following instructions from https://github.com/actions/virtual-environments/issues/1811#issuecomment-764640553
Facing issue as follows
~ $brew update
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /usr/local/Homebrew/Library/Taps/rchawathe/homebrew-local-tap failed!
fatal: 'origin/master' is not a commit and a branch 'master' cannot be created from it
fatal: invalid upstream 'origin/master'

Same here. Even after following instructions from #1811 (comment) Facing issue as follows
~ $brew update
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /usr/local/Homebrew/Library/Taps/rchawathe/homebrew-local-tap failed!
fatal: 'origin/master' is not a commit and a branch 'master' cannot be created from it
fatal: invalid upstream 'origin/master'

Please Help If you've found the solution!!
Mine gives this output:
brew update
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core failed!


Export how long a lock is hold

The exporter will export the new metrics

locked_since_seconds

With labels share and user ID

locked_at

With labels share and user ID
As Unix Timestamp

Since this will expose user data, that some users may do not want to expose, the parameter -not-expose-user-data will be added

Will be set to closed with next release

Fix released with V1.21.9


use an official version of js-ipfs

As you an see from the API, this package already includes js-ipfs. This is to make life easier to app developers, and also because, currently, while this libp2p issue is not solved, we're using a fork of js-ipfs, which includes very slight changes.
This was meant to be temporary.
Currently blocked on https://github.com/libp2p/js-libp2p/pull/166

Now depends on this: https://github.com/ipfs/js-ipfs/issues/1451

Now depends on:

[ ] https://github.com/libp2p/js-libp2p/issues/222
[ ] https://github.com/libp2p/js-libp2p/issues/223

Reviewed https://github.com/ipfs/js-ipfs/pull/1470/files.
Now depends on:

[ ] https://github.com/ipfs/js-ipfs/issues/1463

Done.


pythonPackages.funcsigs: fix tests on pypy3

Motivation for this change
This package has a spurious test failure on PyPy3, which was reported
upstream a while ago: https://github.com/testing-cabal/funcsigs/issues/10
This is fixed thanks to the included patch, which was authored and is
also used by the Gentoo Python team.
With this, packages like 'pytest' and 'click' now work under PyPy3.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS

[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pypy3Packages.funcsigs pypy3Packages.click


Mistake in Support/run-predict.py

Line 87 and below reads as follows:
# Format the JSON string for REINVENT4 and write it to stdout
data = {
        "version": 1,
        "data": {
            "predictions": scores
       }
}

It should read:
# Format the JSON string for REINVENT4 and write it to stdout
data = {
        "version": 1,
        "payload": {
            "predictions": scores
       }
}

User will recieve the following error otherwise:
Traceback (most recent call last):
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent/runmodes/RL/run_staged_learning.py", line 377, in run_staged_learning
terminate = optimize(package.terminator)
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent/runmodes/RL/learning.py", line 131, in optimize
results = self.score()
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent/runmodes/RL/learning.py", line 204, in score
results = self.scoring_function(
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent/scoring/scorer.py", line 105, in compute_results
transform_result = compute_transform(
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent/scoring/compute_scores.py", line 111, in compute_transform
component_results = compute_component_scores(
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent/scoring/compute_scores.py", line 60, in compute_component_scores
component_results = scoring_function(smilies_non_cached)
File "/progs/all/opensource/reinvent/4.0.35/package/lib/python3.10/site-packages/reinvent_plugins/components/comp_external_process.py", line 85, in call
scores.append(np.array(data["payload"]["predictions"]))
KeyError: 'payload'

Many thanks.  Fixed in current release.


Drag and Drop to upload files not working after upgrade to 1.31.2

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.31.2
Regression From
1.26.0
Architecture
x64
Storage Explorer Build Number
20231003.6
Platform
Windows
OS Version
Windows 11
Bug Description
Upload of files via drag and drop is no longer working in latest version.
When I drag file from either Explorer of Total Commander over Azure Explorer window cursor changes to "can't drop" (crossed circle) and file can't be dropped / uploaded.
This is the first time that I installed 64-bit version of Azure Explorer.
It worked perfectly fine in earlier - 32-bit - versions.
Steps to Reproduce

Launch Storage Explorer
Expand Blob name
Drag'n'drop some file from Windows Explorer or Total Commander

Actual Experience
File fails to be dropped (cursor is "crossed circle") and is not uploaded
Expected Experience
File is dropped and uploaded
Additional Context
No response

The issue got resolved after rebooting the laptop.


Add PATCH {appGUID}/environment_variables

Is there a related GitHub Issue?
resolves #412
What is this change about?
implements PATCH {appGUID}/environment_variables
Does this PR introduce a breaking change?
No.
Acceptance Steps
See issue
Tag your pair, your PM, and/or team
@davewalter

Testing in a gke cluster, we couldn't get a cf space developer to login, but using the admin we were able to cf set-env
2022-01-14 11:19 ~/workspace/cf-acceptance-tests CF: https://api.breathable-squirrel.k8s-dev.relint.rocks Jobs: 0 K8s context: breathable-squirrel |develop ↓·27 ?:1|
aw+dw $ cf set-env foo PORT 999
Setting env variable PORT for app foo in org o / space s as<EMAIL_ADDRESS>Var[PORT] should not be equal to PORT
FAILED
2022-01-14 11:20 ~/workspace/cf-acceptance-tests CF: https://api.breathable-squirrel.k8s-dev.relint.rocks Jobs: 0 K8s context: breathable-squirrel |develop ↓·27 ?:1|
aw+dw $ cf set-env foo VCAP_MOO 999
Setting env variable VCAP_MOO for app foo in org o / space s as<EMAIL_ADDRESS>Key: 'AppPatchEnvVars.Var[VCAP_MOO]' Error:Field validation for 'Var[VCAP_MOO]' failed on the 'startsnotwith' tag
FAILED
2022-01-14 11:20 ~/workspace/cf-acceptance-tests CF: https://api.breathable-squirrel.k8s-dev.relint.rocks Jobs: 0 K8s context: breathable-squirrel |develop ↓·27 ?:1|
aw+dw $ cf set-env foo VMC_MOO 999
Setting env variable VMC_MOO for app foo in org o / space s as<EMAIL_ADDRESS>Key: 'AppPatchEnvVars.Var[VMC_MOO]' Error:Field validation for 'Var[VMC_MOO]' failed on the 'startsnotwith' tag
FAILED
2022-01-14 11:20 ~/workspace/cf-acceptance-tests CF: https://api.breathable-squirrel.k8s-dev.relint.rocks Jobs: 0 K8s context: breathable-squirrel |develop ↓·27 ?:1|
aw+dw $ cf set-env foo DATA2 two
Setting env variable DATA2 for app foo in org o / space s as<EMAIL_ADDRESS>OK

TIP: Use 'cf restage foo' to ensure your env variable changes take effect.
2022-01-14 11:21 ~/workspace/cf-acceptance-tests CF: https://api.breathable-squirrel.k8s-dev.relint.rocks Jobs: 0 K8s context: breathable-squirrel |develop ↓·27 ?:1|
aw+dw $ k get secrets -n fd563cbd-27ed-4f19-ba14-efef886f4c83 1d9fdc4b-1e12-4736-8321-1ecaeca41937-env -o yaml
apiVersion: v1
data:
  BLAH: bnVsbA==
  DATA2: dHdv


feat: adds gap_buffer.zig for TextInput

i'm not sure of the best place for gap_buffer.zig to live. definitely don't mind putting it in this repository, but maybe it might make sense as its own thing, since it's pretty general-purpose? your thoughts would be very much appreciated. also tweaked TextInput to use a GapBuffer(u8) to manage its text. it is maybe possible for temporarily silly things to happen if a user intentionally combines two previously-separate graphemes into a single one somehow? this is because in order to avoid unnecessary O(n) copies, i assume that the gap is always well-aligned to grapheme boundaries. i haven't had a chance to take this for a spin yet, since my program maybe wants the "Multi" version of GapBuffer too... the gap_buffer.zig file passes all of the tests (which are adapted from the std.ArrayList tests), so it ought to "just work", but thought you should know.

This didn't build initially, but it's just error handling and a couple calls to secondHalf. I haven't tried pushing to your branch but this is the diff that makes it build:
diff --git a/src/widgets/TextInput.zig b/src/widgets/TextInput.zig
index d4efb409f0c4..88bf300ea080 100644
--- a/src/widgets/TextInput.zig
+++ b/src/widgets/TextInput.zig
@@ -34,10 +34,10 @@ pub fn update(self: *TextInput, event: Event) !void {
         .key_press => |key| {
             if (key.matches(Key.backspace, .{})) {
                 if (self.cursor_idx == 0) return;
-                self.deleteBeforeCursor();
+                try self.deleteBeforeCursor();
             } else if (key.matches(Key.delete, .{}) or key.matches('d', .{ .ctrl = true })) {
                 if (self.cursor_idx == self.grapheme_count) return;
-                self.deleteAtCursor();
+                try self.deleteAtCursor();
             } else if (key.matches(Key.left, .{}) or key.matches('b', .{ .ctrl = true })) {
                 if (self.cursor_idx > 0) self.cursor_idx -= 1;
             } else if (key.matches(Key.right, .{}) or key.matches('f', .{ .ctrl = true })) {
@@ -47,9 +47,9 @@ pub fn update(self: *TextInput, event: Event) !void {
             } else if (key.matches('e', .{ .ctrl = true })) {
                 self.cursor_idx = self.grapheme_count;
             } else if (key.matches('k', .{ .ctrl = true })) {
-                self.deleteToEnd();
+                try self.deleteToEnd();
             } else if (key.matches('u', .{ .ctrl = true })) {
-                self.deleteToStart();
+                try self.deleteToStart();
             } else if (key.text) |text| {
                 try self.buf.insertSliceBefore(self.byteOffsetToCursor(), text);
                 self.cursor_idx += 1;
@@ -121,22 +121,22 @@ fn byteOffsetToCursor(self: TextInput) usize {
     return offset;
 }

-fn deleteToEnd(self: *TextInput) void {
+fn deleteToEnd(self: *TextInput) !void {
     self.cursor_idx += 1;
     const offset = self.byteOffsetToCursor();
-    self.buf.replaceRangeAfter(offset, self.buf.realLength(), &.{});
+    try self.buf.replaceRangeAfter(offset, self.buf.realLength(), &.{});
     self.grapheme_count = self.cursor_idx;
     self.cursor_idx -= 1;
 }

-fn deleteToStart(self: *TextInput) void {
+fn deleteToStart(self: *TextInput) !void {
     const offset = self.byteOffsetToCursor();
-    self.buf.replaceRangeBefore(0, offset, &.{});
+    try self.buf.replaceRangeBefore(0, offset, &.{});
     self.grapheme_count -= self.cursor_idx;
     self.cursor_idx = 0;
 }

-fn deleteBeforeCursor(self: *TextInput) void {
+fn deleteBeforeCursor(self: *TextInput) !void {
     // assumption! the gap is never in the middle of a grapheme
     // one way to _ensure_ this is to move the gap... but that's a cost we probably don't want to pay.
     var iter = GraphemeIterator.init(self.buf.items);
@@ -144,7 +144,7 @@ fn deleteBeforeCursor(self: *TextInput) void {
     var i: usize = 1;
     while (iter.next()) |grapheme| {
         if (i == self.cursor_idx) {
-            self.buf.replaceRangeBefore(offset, grapheme.len, &.{});
+            try self.buf.replaceRangeBefore(offset, grapheme.len, &.{});
             self.cursor_idx -= 1;
             self.grapheme_count -= 1;
             return;
@@ -152,10 +152,10 @@ fn deleteBeforeCursor(self: *TextInput) void {
         offset += grapheme.len;
         i += 1;
     } else {
-        var second_iter = GraphemeIterator.init(self.secondHalf());
+        var second_iter = GraphemeIterator.init(self.buf.secondHalf());
         while (second_iter.next()) |grapheme| {
             if (i == self.cursor_idx) {
-                self.buf.replaceRangeBefore(offset, grapheme.len, &.{});
+                try self.buf.replaceRangeBefore(offset, grapheme.len, &.{});
                 self.cursor_idx -= 1;
                 self.grapheme_count -= 1;
                 return;
@@ -166,7 +166,7 @@ fn deleteBeforeCursor(self: *TextInput) void {
     }
 }

-fn deleteAtCursor(self: *TextInput) void {
+fn deleteAtCursor(self: *TextInput) !void {
     // assumption! the gap is never in the middle of a grapheme
     // one way to _ensure_ this is to move the gap... but that's a cost we probably don't want to pay.
     var iter = GraphemeIterator.init(self.buf.items);
@@ -174,17 +174,17 @@ fn deleteAtCursor(self: *TextInput) void {
     var i: usize = 1;
     while (iter.next()) |grapheme| {
         if (i == self.cursor_idx + 1) {
-            self.buf.replaceRangeAfter(offset, grapheme.len, &.{});
+            try self.buf.replaceRangeAfter(offset, grapheme.len, &.{});
             self.grapheme_count -= 1;
             return;
         }
         offset += grapheme.len;
         i += 1;
     } else {
-        var second_iter = GraphemeIterator.init(self.secondHalf());
+        var second_iter = GraphemeIterator.init(self.buf.secondHalf());
         while (second_iter.next()) |grapheme| {
             if (i == self.cursor_idx + 1) {
-                self.buf.replaceRangeAfter(offset, grapheme.len, &.{});
+                try self.buf.replaceRangeAfter(offset, grapheme.len, &.{});
                 self.grapheme_count -= 1;
                 return;
             }

Yeah I'm not sure if this living in vaxis is ideal?? Someone has done some extra work on the Queue implementation I wrote and published as a separate lib as well, maybe something like that for this would be better for portability...for the Queue at least I still have it vendored (and probably will keep it that way since it's so small and simple).
I wonder if the gap buffer is something that could be in std at some point?
Anyways - awesome work. My initial testing has an assertion failure but I haven't debugged yet. I hit it when I paste "👩🚀" six times in the textinput

thanks for the catch! the problem was that i failed to adjust the starting point of the second half when allocator.resize succeeds. added a test to TextInput that covers this precise testing haha.
i'll throw up a GapBuffer repository now :)

tada! it's here: https://github.com/ryleelyman/GapBuffer.zig

Awesome!

happy to add the relevant stuff to build.zig in case you'd prefer a straight-up dependency :)

Yeah let's go that route. Thanks again!

great! should be ready to merge! still running into the weird "integer bit width out of range" error when trying to run the tests...


Release 2.2.0

Merge development to main to release 2.2.0.

Closed in favour of #313 (from release branch)


[INTERNAL] README: Align wording across repositories

Coverage: 94.608%. Remained the same when pulling a68b2e5e9245611f27c8337762facf8fa83b0b10 on update-readme into 125003d1aa28cae28b0b2386ef72bf1dd4666a5c on main.


setup conflicts

that was quick :-( , when installing the gem it wants to install a program setup. Way to general name, rename to setup_rexx ?
gem install 'tmdb_rexx'
Fetching: faraday_middleware-0.10.0.gem (100%)
Successfully installed faraday_middleware-0.10.0
Fetching: tmdb_rexx-0.6.0.gem (100%)
tmdb_rexx's executable "setup" conflicts with factory_girl_rails
Overwrite the executable? [yN]  n
ERROR:  Error installing tmdb_rexx:
Not that factory girl should have a setup binary (noone should).

@dancinglightning thanks for catching this I have not come across this yet. I suspect it is from this which I definitely agree is too general. An update for this should be coming soon.

This should be fixed with the new release. Please let me know if you still have any issues.


constrain tx gas price == effective gas tip

Description
constrain tx gas price == effective gas tip  for EIP 1559, new fields need more cells so increase step_width as well
Issue Link
[link issue here]
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Contents

[item]

Rationale
[design decisions and extended information]
How Has This Been Tested?
[explanation]

How to fill a PR description
Please give a concise description of your PR.
The target readers could be future developers, reviewers, and auditors. By reading your description, they should easily understand the changes proposed in this pull request.
MUST: Reference the issue to resolve
Single responsability
Is RECOMMENDED to create single responsibility commits, but not mandatory.
Anyway, you MUST enumerate the changes in a unitary way, e.g.
This PR contains:
- Cleanup of xxxx, yyyy
- Changed xxxx to yyyy in order to bla bla
- Added xxxx function to ...
- Refactored ....

Design choices
RECOMMENDED to:

What types of design choices did you face?
What decisions you have made?
Any valuable information that could help reviewers to think critically

Add comment somewhere, explain tx_gas_price is looked up from TxTable in zkevm-circuits/src/evm_circuit/execution/begin_tx.rs

Add comment somewhere, explain tx_gas_price is looked up from TxTable in zkevm-circuits/src/evm_circuit/execution/begin_tx.rs

added in this commit e1a0d3b


Fix fatal new command error

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
Resolves https://github.com/infinitered/ignite/issues/2163

Released in 8.0.0-beta.5


[Error] jekyll build fails with liquid exception using 'none' for max_width after upgrade to 1.4.1

Hello! First of all, thank you for maintaining this wonderful gem of a gem. I've used it on multiple sites. After a recent bundle update, I started seeing a new error that seems to point back to line 24 in tag.rb.
The error occurs when I go to build the site. I'm using bundler, so bundle exec jekyll build
I believe this error began when I upgraded with bundle udpate to the 1.4.1 version of the plugin.
The error message with the top part of the stack trace is as follows:
  Rendering Liquid: 03-bikes.html
/Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:17: warning: calling URI.open via Kernel#open is deprecated, call URI.open directly or use URI#open
  Liquid Exception: string not matched in 03-bikes.html
jekyll 3.8.7 | Error:  string not matched
Traceback (most recent call last):
        58: from /Users/sethbrown/.rbenv/versions/2.7.1/bin/bundle:23:in `'
        57: from /Users/sethbrown/.rbenv/versions/2.7.1/bin/bundle:23:in `load'
        56: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/exe/bundle:34:in `<top (required)>'
        55: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/friendly_errors.rb:123:in `with_friendly_errors'
        54: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/exe/bundle:46:in `block in <top (required)>'
        53: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/cli.rb:24:in `start'
        52: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
        51: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/cli.rb:30:in `dispatch'
        50: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
        49: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        48: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
        47: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/cli.rb:476:in `exec'
        46: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:28:in `run'
        45: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `kernel_load'
        44: from /Users/sethbrown/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `load'
        43: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/bin/jekyll:23:in `<top (required)>'
        42: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/bin/jekyll:23:in `load'
        41: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/exe/jekyll:15:in `<top (required)>'
        40: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        39: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        38: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        37: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        36: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        35: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/commands/serve.rb:75:in `block (2 levels) in init_with_program'
        34: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/commands/serve.rb:93:in `start'
        33: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/commands/serve.rb:93:in `each'
        32: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/commands/serve.rb:93:in `block in start'
        31: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/commands/build.rb:36:in `process'
        30: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/commands/build.rb:65:in `build'
        29: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/command.rb:28:in `process_site'
        28: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/site.rb:71:in `process'
        27: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/site.rb:192:in `render'
        26: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/site.rb:471:in `render_pages'
        25: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/site.rb:471:in `each'
        24: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/site.rb:472:in `block in render_pages'
        23: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/site.rb:479:in `render_regenerated'
        22: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/renderer.rb:62:in `run'
        21: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/renderer.rb:79:in `render_document'
        20: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/renderer.rb:126:in `render_liquid'
        19: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/liquid_renderer/file.rb:28:in `render!'
        18: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/liquid_renderer/file.rb:49:in `measure_time'
        17: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/liquid_renderer/file.rb:29:in `block in render!'
        16: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/liquid_renderer/file.rb:42:in `measure_bytes'
        15: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-3.8.7/lib/jekyll/liquid_renderer/file.rb:30:in `block (2 levels) in render!'
        14: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:220:in `render!'
        13: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:207:in `render'
        12: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:242:in `with_profiling'
        11: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/liquid-4.0.3/lib/liquid/template.rb:208:in `block in render'
        10: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:91:in `render'
         9: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/liquid-4.0.3/lib/liquid/block_body.rb:103:in `render_node_to_output'
         8: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:84:in `render'
         7: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:84:in `each'
         6: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:85:in `block in render'
         5: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:19:in `getImageLinks'
         4: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/nokogiri-1.10.9/lib/nokogiri/xml/node_set.rb:237:in `each'
         3: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/nokogiri-1.10.9/lib/nokogiri/xml/node_set.rb:237:in `upto'
         2: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/nokogiri-1.10.9/lib/nokogiri/xml/node_set.rb:238:in `block in each'
         1: from /Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:23:in `block in getImageLinks'
/Users/sethbrown/Sites/woc-bike/vendor/bundle/ruby/2.7.0/gems/jekyll-google-photos-1.4.1/lib/jekyll-google-photos/tag.rb:23:in `[]=': string not matched (IndexError)

Here's a code snippet from 03-bikes.html indicating how I'm invoking the plugin on my Jekyll site.

Back to top

Road Bikes

    The following road bikes are currently available as project stock from the
    bike pile. Check back soon as we add sizes and prices. In the meantime, if
    you're interested in a particular bike, please give us a call.

  {% google_photos https://photos.app.goo.gl/MxhGDu87H7jg6mY79 none %}

Thanks for reporting the issue @sethlbrown . Looks like Google has changed their page layout and that's what causing the problem. I'll try to work on a fix soon.

 Let me know if I can make a financial contribution to help out.

@sethlbrown That won't be necessary. Let me know if the new version works fine. Please consider starring the project if you liked it.

Yay, this worked! The new Bikes page is up and looking good at http://wocbikeproject.org/bikes
Thanks again!


doc: migrate filesets to doc-comment format

Description of changes
lib.filesets comments migrated to doc-comments.
Manual steps:

[x] File description headings should start with h1 not h2.  (consistency across doc-comments)
[x] reformatted some of the arguments/structured args documentation manually. Since they would be lost with our current automatism.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@DanielSidhion I'll add the indentation fixes to the tooling. Most of it was done manually anyways. I dont have tooling to automatically migrate structured arguments.
This is still an open question, so i did it by hand.

@DanielSidhion indentation should be fine now.


Schematic rework

Hi,
I noticed your project and I'm currently working on a rework of your not-so-ideal schematic and RT1062 Symbol.
It's far from done, but this is what I got so far. https://github.com/fabianmuehlberger/Teensy-4.1-example
If you are interested in a merge, let me know.
Best Fabian

Hi Fabian,
Sure! Did you test your version yet?
J
On Wed, Aug 17, 2022 at 4:09 PM fabianmuehlberger @.***>
wrote:

Hi,
I noticed your project and I'm currently working on a rework of your
not-so-ideal schematic and RT1062 Symbol.
It's far from done, but this is what I got so far.
https://github.com/fabianmuehlberger/Teensy-4.1-example
If you are interested in a merge, let me know.
Best Fabian
—
Reply to this email directly, view it on GitHub
https://github.com/jenschr/Teensy-4.1-example/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGKOXPBMG5RQ5PGV72IV3VZTXAXANCNFSM56ZWHKVQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Vennlig hilsen
Jens Chr Brynildsen
mob +47 90691786
www.flashgamer.com

I just did the rework today. I haven't run any tests on it
The footprint didn't link from your fork, so this will be the first thing I check. Have you made your own footprint or where did you get it from? If it is well done I would use it too.

Heya,
I can't remember exactly, but I'm quite sure that I used the generator
built into Kicad. I've done 5 different boards using this chip & setup by
now, so I'm quite confident that it works as intended.
J
On Wed, Aug 17, 2022 at 4:50 PM fabianmuehlberger @.***>
wrote:

I just did the rework today. I haven't run any tests on it
The footprint didn't link from your fork, so this will be the first thing
I check. Have you made your own footprint or where did you get it from? If
it is well done I would use it too.
—
Reply to this email directly, view it on GitHub
https://github.com/jenschr/Teensy-4.1-example/issues/1#issuecomment-1218115286,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGKOQXZYQZYYR3E6TF373VZT32HANCNFSM56ZWHKVQ
.
You are receiving this because you commented.Message ID: <jenschr/Teensy-4
<EMAIL_ADDRESS>
--
Vennlig hilsen
Jens Chr Brynildsen
mob +47 90691786
www.flashgamer.com

@fabianmuehlberger got your board tested and verified now? If so, I'd love to include it?

not finished, I think I'm pretty much done with the USB and power section, divided the schematic into hierarchical sheets and drew a few nets new.
You might want to check it though, its basically a new schematic

Heya. I just had a look now. Looks like you never finished? At least, I can't see any power pins to the chip? ;-)


[Elijah] -Sage- How to be a web3 developer

Thanks for submitting this tutorial for Celo Sage
Before you hit "Create Pull Request", make sure you have read the Tutorial Contribution Guidelines and reviewed the Sample Tutorial Structure.
Please confirm the following before submitting your tutorial for review -

[x] My tutorial follows the Tutorial Contribution Guidelines.
[x] The title of the Pull Request matches the title of my tutorial.
[x] I've followed the tutorial template structure.
[x] I've proofread the tutorial for spelling and grammar mistakes.
[ ] I've thoroughly explained the code, with inline code comments and text explanations.
[ ] I've run a linter & prettifier to format my code blocks.
[ ] I've run the tutorial to test it and the code works.

NOTE: We cannot review your Pull Request if it does not meet the standard outlined above.
Reviewers - @joenyzio & @viral-sangani

Hello @viral-sangani,
Kindly check my work and let me get an update.
Thanks.


cleaning up deadcode and adding tests for task detection.

first test in executor project
Improvements to the taskInfoBuilder as well.

@elingg @gabrielhartmann I ran across some code to clean up... it lead to this... looking for a review.

Thanks @kensipe. Took a quick look and it LGTM. It is a small change, but it might be worth testing to make sure we're not missing anything.

tested good.  merging!


Suggested API improvement for  and partial matching

One of the more complex things I've encountered with react-router, which I think is still the best of the options that I've tried, is handling the "partially-matched route" issue. I think this is because of the compositional way you put together routes, which TBH I like, and gives good flexibility (especially now with <Routes> in v6), but there still seems to be a challenge specifically in matching a given NavLink.
Problem
My route configuration looks something like this:
        <Routes>
          <Route path="/" element={<Home />} />
          <Route path="/whatsnew" element={<WhatsNew />} />
          <Route path="/:year">
            <Routes>
              <Route path="*" element={<ProgramRoot />} />
              <Route path="students" element={<Students />} />
              <Route path="students/:studentId" element={<StudentDetail />} />
              <Route path="posts" element={<Posts />} />
              <Route path="posts/:postId" element={<PostDetail />} />
            </Routes>
          </Route>
        </Routes>

My top navigation looks like this:

<NavLink to="/">Home</NavLink>

<NavLink to="/whatsnew">What's new</NavLink>

2021

<NavLink to="/2021">Program root</NavLink>

<NavLink to="/2021/students">Students list</NavLink>

<NavLink to="/2021/posts">Post list</NavLink>

What I'd like to do is not write complex components or specialized components for my NavLinks. Ideally I'd like a matched-route context to be present which can be accessible with hooks.
Proposed solution
Could we add a property to Route which is accessible via a hook? Here's what it might look like:
    <Route path="students/:studentId" element={<StudentDetail />} context="students" />

Then in my navigation, I can leverage a new hook, useRouteContext():
declare export function useRouteContext(): string[];

export const Nav = () => {
  const actives = useRouteContext();
  return (

<NavLink to="/" isActive={() => actives.length === 0}>Home</NavLink>

<NavLink to="/whatsnew" isActive={() => actives.indexOf('whatsnew') > -1>What's new</NavLink>

2021

<NavLink to="/2021" isActive={() => actives.indexOf('program') > -1>Program root</NavLink>

<NavLink to="/2021/students" isActive={() => actives.indexOf('students') > -1>Students list</NavLink>

<NavLink to="/2021/posts" isActive={() => actives.indexOf('posts') > -1>Post list</NavLink>

  );
};

This makes it trivial to wrap <NavLink> one time to detect whether a route context is present:
type MyNavLinkProps = NavLinkProps & {
  activeContext?: string;
};

export const MyNavLink = (props: MyNavLinkProps) => {
  const actives = useRouteContext();
  const isActive = (typeof props.activeContext === 'undefined') ?
      actives.length === 0 :
      actives.indexOf(props.activeContext) > -1;

  return (
    <NavLink {...props} isActive={() => isActive} />
  );
};

This simplifies my Nav futher:
export const Nav = () => {
  return (

<MyNavLink to="/">Home</MyNavLink>

<MyNavLink to="/whatsnew" activeContext="whatsnew">What's new</MyNavLink>

2021

<MyNavLink to="/2021" activeContext="program">Program root</MyNavLink>

<MyNavLink to="/2021/students" activeContext="students">Students list</MyNavLink>

<MyNavLink to="/2021/posts" activeContext="posts">Post list</MyNavLink>

  );
};

What do you think? Would you be open to accepting a PR in this direction?

This has been suggested before. You can already do this, just pass it as a prop:
<Route path="students/:studentId" element={<StudentDetail context="students" />} />

If you need it beyond that, you can pass it along props or use a Context to jump between levels of the tree. This is already a built-in React feature, so there's nothing for us to implement here.


esp-open-sdk and/or esp-open-rtos

Feature Request:
Please implement esp-open-sdk and/or esp-open-rtos support.
Thanks for a great product!!

Duplicate of #366 and #402.

Moved to https://github.com/platformio/platform-espressif8266/issues/14


 This seems to work, but obviously needs some tests. Options struct already supports several targets.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Looks like the CI is hanging?

Thanks! Can you also add a test for this?

Thanks! Can you also add a test for this?

Sure, I just hope that #3708  is merge first to avoid possible merge conflicts.

I've added the tests and turns out that testing examples does not work at all (both in stable and in nightly) =/
Looks like we don't set cfg=test when compiling example for cargo test --example ex, because I don't see compiler errors inside test functions in examples.

Ah yeah examples won't work out, but testing binaries and integration tests should work!

Ah yeah examples won't work out

And are they supposed to work? If not, then maybe we should just remove --example flag from test options altogether?

It's sort of up for debate but for backwards compatibility we probably can't remove :(

Hm, then the current behavior of just compiling examples is pretty reasonable, but the documentation is a bit misleading. I've tried to improve the command line flag description.

@bors: r+

:pushpin: Commit f7fa9cb has been approved by alexcrichton

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 3dfe72fa82e8e69bde1149fb453c1799a7d8dead to master...


Machine linux-37 lost external connection device.

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
infra task
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
Machine linux-37 lost external connection device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

External connection has been restored by rebooting phone device.


env.render() / vnc / go vnc driver throws exception "NSInternalInconsistencyException"

Hi, when I use env.render (or the --visualise) option for the A3C agent on OS X, my workers die due to some vnc/os x issue.
(universe-starter-agent) bash-4.4$ python train.py --num-workers 2 --env-id gym-core.PongDeterministic-v3 --log-dir /tmp/vncpong --visualise
output from one worker: (left off the first part of the output where stuff was running normally)
universe-bJY8M8-0 | [2017-02-02 06:51:03,129] Running environment: env_id=PongDeterministic-v3
[2017-02-01 22:51:03,131] [0:localhost:5901] Initial reset complete: episode_id=1
[2017-02-01 22:51:03,157] Resetting environment
2017-02-01 22:51:03.260 python[53025:1081291] WARNING: nextEventMatchingMask should only be called from the Main Thread! This will throw an exception in the future.
2017-02-01 22:51:03.261 python[53025:1081291] *** Assertion failure in +[NSUndoManager _endTopLevelGroupings], /Library/Caches/com.apple.xbs/Sources/Foundation/Foundation-1349.25/Misc.subproj/NSUndoManager.m:363
2017-02-01 22:51:03.262 python[53025:1081291] *** Assertion failure in +[NSUndoManager _endTopLevelGroupings], /Library/Caches/com.apple.xbs/Sources/Foundation/Foundation-1349.25/Misc.subproj/NSUndoManager.m:363
2017-02-01 22:51:03.263 python[53025:1081291] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '+[NSUndoManager(NSInternal) _endTopLevelGroupings]
is only safe to invoke on the main thread.'
*** First throw call stack:
(
        0   CoreFoundation                      0x00007fffbb776e7b __exceptionPreprocess + 171
        1   libobjc.A.dylib                     0x00007fffd0360cad objc_exception_throw + 48
        2   CoreFoundation                      0x00007fffbb77bb82 +[NSException raise:format:arguments:] + 98
        3   Foundation                          0x00007fffbd1c5d50 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
        4   Foundation                          0x00007fffbd1503f3 +[NSUndoManager(NSPrivate)
_endTopLevelGroupings] + 170
        5   AppKit                              0x00007fffb9213047 -[NSApplication run] + 1200
        6   go_vncdriver.so                     0x000000010fae3d5a initializeAppKit + 314
        7   go_vncdriver.so                     0x000000010fae3b1d _glfwPlatformCreateWindow + 29
        8   go_vncdriver.so                     0x000000010fadc7d0 glfwCreateWindow + 864
        9   go_vncdriver.so                     0x000000010fae9c62 _cgo_21dbbd5d2900_Cfunc_glfwCreateWindow + 82
        10  go_vncdriver.so                     0x000000010f92a3e0 runtime.asmcgocall + 112
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6

The last few lines of my /tmp/universe-*.log look like this:
[2017-02-01 22:51:03,131] [0:localhost:5901] RewardBuffer: dropping stale episode data: dropped={'0', None} episode_id=1
[2017-02-01 22:51:03,131] [0:localhost:5901] Initial reset complete: episode_id=1
[2017-02-01 22:51:03,133] [0:localhost:5901] RewardState: popping reward 0.0 from episode_id 1
[2017-02-01 22:51:03,133] [0:localhost:5901] Episode began: episode_id=1 env_state=running
[2017-02-01 22:51:03,133] [0] Sending out new action probe: [('KeyEvent', 782065, True), ('KeyEvent', 782065, False)]
[2017-02-01 22:51:03,156] [0] Could not find metadata anchor pixel
[2017-02-01 22:51:03,157] Resetting environment
[2017-02-01 22:51:03,183] [0:localhost:5901] RewardState: popping reward 0.0 from episode_id 1
[2017-02-01 22:51:03,183] [0:localhost:5901] RewardState: popping reward 0.0 from episode_id 1
[2017-02-01 22:51:03,203] [0:localhost:5901] RewardState: popping reward 0.0 from episode_id 1
(END)

This happens consistently, not sure why. Turning off env.render() works fine. Has anyone else run into this?

I was running on the vnc environment, so I guess render() doesn't make sense? Closing this because it works as expected on the non-vnc pong, and vnc works fine on vncpong.


Genqecrr dyn model

GENQEC documentation.docx

@tavovalmo this PR includes more models than just the Genqecrr right?

@tavovalmo I suggest splitting this PR in 3 separate PRs to make it easier to review.

new integrator blocks -> add tests to test_base.jl
The new AVR models -> add new dyr/raw files and PSSe results with 0.005 dt
The Genqecrr model -> is this model in PSSe already?

We can make another dev call to discuss how to integrate the tests

Here is the code that @tavovalmo you can add to ensure that the 3 last states of the GENQEC are algebraic:
In the file src/models/generator_models/machine_models.jl add the following code before the function mdl_machine_ode! for BaseMachine (around line 8)
function mass_matrix_machine_entries!(
    mass_matrix,
    machine::PSY.GENQEC,
    global_index::Base.ImmutableDict{Symbol, Int64},
) where {M <: PSY.Machine}
    mass_matrix[global_index[:I_d], global_index[:I_d]] = 0.0
    mass_matrix[global_index[:I_q], global_index[:I_q]] = 0.0
    mass_matrix[global_index[:Se], global_index[:Se]] = 0.0
    return
end

This function will set the right hand side time constants to zero on the states I_d, I_q and Se, making those equations algebraic.


The docker organization name was changed in catasb

dockerhub_org_name was changed to dockerhub_org.

This will fix the error seen in #446 . And #446 should get the gate back to green.


[#104308518] Prevent 500s if session expired on create-your-account-complete page

See: https://www.pivotaltracker.com/story/show/104308518
Before:

After:

Why does this happen, do we know?

I can only think because people refresh the page after their session has expired. Or maybe because the bookmarked that last page and try to visit it again later.  I haven't tried extracting user journeys from the logs leading up to these errors or anything though.

Well at that point everything is in the database anyway, right?
:+1: from me.


focus mode

[x] tapping on a term in the term-list should activate focus mode

[x] any further action should deactivate focus mode


cargo build on master

Caused by:
failed to load source for dependency vt
Caused by:
Unable to update https://github.com/asciinema/vt-rs.git?tag=v0.5.0#dd885473
I change Cargo.toml and removed vt's tag (using vt v0.5.0 (https://github.com/asciinema/vt-rs.git#c25b2c30)) and it builds OK

I assumed cargo would handle repo rename fine, but it hasn't. Just pushed a fix for this.