Dependency updates (Spring Boot, Spring Cloud, Spring Core)

As ... , security minister
I want ... , that the dependencies of trace-x are up to date
so that ... . no security vulnerabilities can occur
Hints / Details

We can not simply merge those pull request as there are some changes in our codebase necessary.

https://github.com/eclipse-tractusx/traceability-foss/security/code-scanning/5109
https://github.com/eclipse-tractusx/traceability-foss/pull/647
Additionally several security issues occur because of spring boot, spring security, spring core and spring cloud. Those dependencies should be all updated to the latest stable version.

Acceptance Criteria

The mentioned links in the details section have been addressed
All mentioned spring dependencies are up to date

Not possible to test. Security alerts regarding the spring version are resolved now -> Confirmation that spring dependencies were successfully updated.
Ready for review @jzbmw.


Validate EFS functionality as part of E2E test(s)

Closes #228
To-Do:

[x] Create a PVC and job
[x] Update the golang test code to validate that the job completed successfully -- https://stackoverflow.com/questions/44686568/tell-when-job-is-complete

/test all
(last one was the "insufficient capacity" error 😭

/test all
(insufficient capacity again)

/test all

Ready for review and merge


Fix building on FreeBSD

Closes https://github.com/owncloud/ocis/issues/1217

Extracted common error methods to errtypes package
Fixed type error on Bavail ( https://golang.org/src/syscall/ztypes_freebsd_arm64.go#L125 )
Alias ENODATA to ENOATTR

Still pending:

I am not sure how to implement error methods on Windows
Wait for https://github.com/c-bata/go-prompt to depend on not-yet-released 1.2.0 version of https://github.com/pkg/term

term fixed the build issues recently https://github.com/pkg/term/issues/57

How to test this on Linux:
export GOOS=freebsd
make

UPD: go-prompt patched https://github.com/c-bata/go-prompt/pull/224 (waiting for a release)

Hmm,
pkg/storage/fs/ocis/ocis_unix.go:31:18: unnecessary conversion (unconvert)
    bavail := uint64(stat.Bavail) // stat.Bavail is int64 on FreeBSD

will be nice to somehow enable -all flag on unconvert linter (ref: https://github.com/mdempsky/unconvert )
Using the -all flag, unconvert will analyze the Go packages under all possible GOOS/GOARCH combinations, and only identify conversions that are unnecessary in all cases.

E.g., syscall.Timespec's Sec and Nsec fields are int64 under linux/amd64 but int32 under linux/386. An int64(ts.Sec) conversion that appears in a linux/amd64-only file will be identified as unnecessary, but it will be preserved if it occurs in a file that's compiled for both linux/amd64 and linux/386.

OK. Now only need to figure out how to resolve unconvert lint issue https://github.com/golangci/golangci-lint/issues/1809
Let me know if you have some ideas.

Seems like it will take a while to update golangci-lint so I split into more freebsd specific files as you suggested.

@ishank011 How can we continue with these changes?

zerrors_windows.go has a comment above defined contants.
// Invented values to support what package os and others expects.

Also syscall package is deprecated

Deprecated: this package is locked down. Callers should use the corresponding package in the golang.org/x/sys repository instead.

I am not sure that Windows has exact same errors as unix systems. golang.org/x/sys/windows defines completely different error types. Do you still want me to implement XattrIsNoData method on Windows using syscall.ENODATA constant? I am not familiar with file systems but to me it seems that ENODATA will never happen on Windows since there is no such thing there.

@zaynetro ah okay, we can let it be then. Can you rebase?

Done.

@zaynetro could you rebase? I think @ishank011 would like to get this in.

Rebased.

@micbar you had a look at the ENOATTR ENODATA and sent an upstream PR https://github.com/pkg/xattr/pull/63/files
@C0rby don't you have a bsd variant running?
I know this PR bitrotted a bit, still @zaynetro could you retarget this PR against the edge branch? It might be easier to get it in there.

Is there any update on this bug?
OCIS still does not build on FreeBSD due to this bug.

oCIS is now building on the edge branch which means it uses reva 2.x releases.
This fix would need to go to the edge branch.

Is there any update on this bug?
OCIS still does not build on FreeBSD due to this bug.

I've just attempted to build oCIS v2.0.0 (their stable release) on FreeBSD today and can confirm this bug is still present in reva, preventing a successful compilation.. What can I do to help speed this up?

@joramkruijer please try the latest master.

@joramkruijer please try the latest master.

Thanks, that resolves the compilation issue! There's an issue preventing ocis from running due to a bug in reva, for which I've opened a pull request (#3650).

any news?


Relax visibility of verify function

Render the plonk/verifier's verify() function public to allow for proofs verification in external applications.

External applications can already verify proofs by using the public verify method from VerifierCircuitData.


MB-16456 - Fix ShipmentDisplay styles to fit SIT display maximum width

Jira ticket
Summary
These small changes should set a minimum width for the shipment display to fit the maximum width of the SIT Display.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Create a move with the test harness scenario HHGMoveIn200DaysSITWithPendingExtension
Access the office app as a TOO
Navigate to the move MTO page
Verify that the pending extension tag is not split between two rows and that the mto agent information is word-wrapped.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-16456

  Generated by :no_entry_sign: dangerJS against 2951ce9a1852dcfca8c0a90d5b8f1e20fbbe201c


fix: ACNA-2371 - OAuth Server-to-Server incorrect parameter documentation

Closes #132
How Has This Been Tested?
Markdown preview.
Types of changes

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

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

Trivial change


.github/workflows/todo-issue.yml / build (push) Successful in 6s check could be more readable

.github/workflows/todo-issue.yml / build (push) Successful in 6s could be more human-readable.

Thanks @hamirmahal but this is just an internal workflow that only I use.

You're welcome @ChrisChinchilla.


Bump dependencies for Jackson and Spring

Bump dependencies to fix a security  bug in Jackson.
Add OWASP dependency check plugin.

:+1:

Thanks for the contribution! :tada: I released it as 1.5.5 to maven central.


stable/mssql-linux Allow a NodePort to be specified.

Signed-off-by: Tim Moore<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test


Add a benchmark for creating large uninit allocations

Extracted from https://github.com/rust-lang/miri/issues/3637
I used this program to confirm that https://github.com/rust-lang/rust/pull/125633 has the desired effect.

That is strange. The only docs I can find suggest this should fit comfortably on a GitHub-hosted runner: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories

Note that on Windows we're using a 32bit target as the host. Not sure how Windows manages the address space there, maybe it keeps half of it for the kernel so there's only 2GB total for the program?

Right. I was trying to avoid doing that because the effect size shrinks, but of course a little loop fixes that.

How long does the benchmark take (with the fix)?

https://github.com/rust-lang/rust/pull/125633 landed, but a ./miri rustc-pull will be needed before we have it available in the repo.

How long does the benchmark take (with the fix)?

200 ms per iteration with the fix. Without the fix, it's 800 ms per iteration. So I think it would be fair to land this without the fix, because it's already one of our faster benchmarks.

Makes sense, thanks!
@bors r+

:pushpin: Commit 88a24967c6cbb08adb52aa3e6b8ea515d7d7cd35 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 88a24967c6cbb08adb52aa3e6b8ea515d7d7cd35 with merge 952aa4d59772d3c0f7de5313392e28e8fec75302...


Replace Wrapper div with <>

The extra div is really messing up my styles. Can we replace that with a <> or <React.Fragment>?

This should be fixed now in https://github.com/plaid/react-plaid-link/pull/81/
v2.0.0 was just released, so please test it out by checking the updated README and let me know!
There's also a storybook to test using Hooks and the Component wrapper:
https://plaid.github.io/react-plaid-link


enhancement: More flexible built-in component styling

I noticed that the built-in components don't have very good style configuration. There's PRs like #422 that add more style properties to components, but I don't think that's not sustainable. Could there be a better way than just adding more style properties? Maybe a stylesheet?

That's what Themes are for, they are kind of a stylesheet. Although they mostly contain visual styling and not layout styling, perhaps I could also move the layout styling (margin, padding, etc) to Themes? What do you think?

That's what Themes are for, they are kind of stylesheets.

Using themes is annoying when you try to change the style of just one component instead of the entire app or all of the render! macro contents. I think components could have an optional theme property that would override the inherited theme. For example:
render! {
    Button {
        theme: ButtonTheme {
            background: "red",
            ..LIGHT_THEME.button
        }
    }
}

I could also add the layout styling (margin, padding, etc) to Themes (beside passing via prop)? What do you think?

Yeah I think layout should be in the themes. The split is pretty arbitrary, and it doesn't seem to be followed properly :P (#422 added shadow and corner_radius properties which are not layout) And if you go forward with my theme property suggestion, it would also mean that all style properties would be separated from the "functional" properties.
I also want to point out that the components don't fully utilize themes. As in, there's some properties which just have a hardcoded value (e.g., border is always 1 solid in Input). That's not really an API issue though.

render! {
    Button {
        theme: ButtonTheme {
            background: "red",
            ..LIGHT_THEME.button
        }
    }
}

Yeah, I think I like that, I'll see what I can do

Yeah I think layout should be in the themes. The split is pretty arbitrary, and it doesn't seem to be followed properly :P (#422 added shadow and corner_radius properties which are not layout) And if you go forward with my theme property suggestion, it would also mean that all style properties would be separated from the "functional" properties.

You are 💯 right

I also want to point out that the components don't fully utilize themes. As in, there's some properties which just have a hardcoded value (e.g., border is always 1 solid in Input). That's not really an API issue though.

I also noticed this yesterday when doing https://github.com/marc2332/freya/pull/422

Yeah, I think I like that, I'll see what I can do

I would be happy to make a PR


When snapping elements, sometimes coordinates don't match

Bug Description
When you drop an element to a snap target, sometimes (actually quite often) the coordinates don't actually match the expected target.
This is probably due to rounding errors.
Expected Behaviour
When dropping an element using a snapping guideline (either to page or to an object), the coordinates of the elements should match (as well as possible - sometimes it's not possible for center snapping due to the requirement of whole pixels).
Steps to Reproduce

Add two elements to a page
Move one element to x=100
Try to align the second element to have the same left edge as the first element
Notice that the x of the second element varies on subsequent drops, only occasionally matching the 100 of the first element

Screenshots

Additional Context

Plugin Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief
This should (probably) be fixed by remembering which (if any) snap targets an element is dropped near, and if so, use the coordinates of that target instead of the regular original position + delta movement  math currently used (as it suffers from rounding errors.

@barklund / @carlos-kelly - can we get confirmation of which pod will be taking this on for 1.2 thankls

Amy reported that this bug also makes it hard to snap elements to be exactly next to each other and has been reported by some users -- there's a 1px area between the two elements when trying to snap next to each other.


Orca does not work on Windows

I want to use orca() through package plotly in R. I installed orca on Windows 10 following the instructions:

https://github.com/plotly/orca#installation

All the commands I describe next were called from Command Prompt, not from R.
Command orca did not work. Thus I added C:\Users\my_pc\AppData\Local\Programs\orca\orca.exe to the path manually. Now if I write C:\Users\my_pc\AppData\Local\Programs\orca\orca.exe in the prompt, it works. But writing command orca doesn't. By writing PATH I see that the last element is the path to orca.exe.
What should I do next to make orca work?

I renamed from C:\Users\my_pc\AppData\Local\Programs\orca\orca.exe to C:\Users\my_pc\AppData\Local\Programs\orca in PATH variable and it works. Most probably I copied "Target" field instead of "Start in" in point 4 of instructions for Windows (https://github.com/plotly/orca#installation).

C:\Users\Andrew\Desktop\Pocket Tools\ORCA-0.1.0-win64\ORCA-0.1.0-win64\bin\   See I had to put the last \ in the path, and then it worked.


console-teleprompt "sampleQuotes.txt" link "Page not found".

When attempting to access the "sampleQuotes.txt" file I get a 404 not found error.
Assumed cause: Rename in branch from master -> main and GitHub not correctly redirecting for the raw file:
Current link in the doc:
https://github.com/dotnet/samples/raw/master/csharp/getting-started/console-teleprompter/sampleQuotes.txt
Updated branch path to the file:
https://github.com/dotnet/samples/raw/main/csharp/getting-started/console-teleprompter/sampleQuotes.txt

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

ID: a4a28322-944d-73c3-177c-d9bec577c08b
Version Independent ID: 15ce52df-1eb1-7743-8440-dbef3169487c
Content: Console Application
Content Source: docs/csharp/tutorials/console-teleprompter.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for pointing this out and submitting the fix @Liamdoult
I'll review the PR shortly.


FiniteAutomaton from regex can't use "."

FiniteAutomaton(".")

hangs indefinitely. Probably because . means any character, and a FiniteAutomaton's alphabet is finite. Though I'd at least assume something like this would be returned:
#<FiniteAutomaton initial state: 0
state 0 [reject]:
  \u0000-\u9999 -> 1
state 1 [accept]:
>

Yes, that's a known problem.
The . expresses that all letters from the alphabet are acceptable; in our case, all values from Character.MIN_VALUE to Character.MAX_VALUE.
Then, the automaton is populated and all valid transitions from all known states are built; in our case, there are 65536 states and all possible transitions are valid, that is,<PHONE_NUMBER> iterations to add (or not) a digit to the alphabet...
To avoid (temporarily) this, we added the following constructor:
  /**
  * ..
  * @param min    an overall minimum value for transitions
  * @param max    an overall maximum value for transitions
  */
public FiniteAutomaton(String regexp, int min, int max) {...}

A realistic patch would be to reimplement the REGULAR constraint on the basis of a more accurate library (we already have one in the pipes, but it is based on Java8 only).


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 985

Questions ?
Please refer to the Backport tool documentation


Trezor One slow to connect or not at all

I see an issue on multiple PCs running Windows 10 where a Trezor One will be slow to connect (30-60sec) at every step. It will also fail to recognize a correct PIN.
This does not occur on every PC, however, I think the common factor between the two that it failed on is Bitdefender Total Security (Virus Scan).
I tried entering in all Sparrow folders in the exceptions settings as well as disabling virus scan. I also tried running Sparrow as admin. However the issue persists. It seems as though something is high-jacking the USB connection to the Trezor One.
Note: Trezor T and Ledger X do NOT have this problem.
For example: Trying to add a Trezor One in the "connect hardware screen" and runing a scan will take over 30sec to find the Trezor. Clicking "Unlock" will take another 30+sec for the pin entry graphic to show. Entereing the correct pin (either manually in the text field or using the dots) will result in an immediate failure with the error message "LIBUSB_ERROR_ACCESS [-3]"
The pin numbers will remain on the Trezor One screen.

Note: About 1 in every 10 tries the Trezor One will connect.

Unfortunately there's not much Sparrow can do about an anti-virus, but you can set the anti-virus to exclude the internal utility Sparrow runs to communicate with the hardware wallet. Configure the anti-virus to ignore the hwi folder in Sparrow Home. See this FAQ to find it: https://sparrowwallet.com/docs/faq.html#where-does-sparrow-store-data

I had already excluded that folder. it didn't make a difference.
Considering that other apps, including the Trezor suite, don't have access problems, is there some other reason why sparrow would have difficulty with only the Trezor one?

Any update here? If there's nothing that can be done on the Sparrow side, I'd like to close this off.

It is in the hwi folder I mentioned previously, although the name is longer as it is extracted from the Sparrow install on use. You can still call it as normal though: hwi-2.1.1.xxxxx...exe enumerate.

I think this may be part of the problem. The only file (including hidden files) that appears in C:\Users\USER\AppData\Roaming\Sparrow\hwi  is hwi-2.1.18667571028405941001.tmp.   I even tried calling hwi-2.1.18667571028405941001.exe enumerate in command prompt anyway, and it said it doesn't exist.

Try calling hwi-2.1.18667571028405941001.tmp enumerate - sorry, I wasn't near a Window machine previously to check.

Figured it out. It's the bitdefender firewall. Excluding in virus scan section did nothing, nor did allowing sparrow.exe full access through firewall. I had to turn the feature off completely. Once I do, HWI enumerate went from 45 seconds delay to 5 seconds.
Thank you.


Update SoapUI testrunner version up to 5.3.0

Update SoapUI testrunner version up to 5.3.0

Coverage remained the same at 33.871% when pulling f2dae0482c031381cabe25a561cc770b08480233 on daggerok:master into a228233009cc0e404fbada77cae38cde6ddc7b92 on byte-shifter-ltd:master.


Can't compile C++ files (api.hpp missing)

I made a new C++ script, and when I try to compile it, i get this error in the console:
In file included from assets/scripts/Ground.cpp:1:
assets/scripts/Ground.hpp:2:10: fatal error: api.hpp: No such file or directory
    2 | #include <api.hpp>
      |          ^~~~~~~~~
compilation terminated.

I think i just forgot to compile the CppScripting.cpp file.. cause it works after i compiled it
This is definitely strange

Probably fixed this issue, needs testing

Probably fixed this issue, closing until further notice


405: Method Not Allowed

Hi,
Rich-Cards-Bot# python show me this message.

@xronsx - Can you explain a bit more about what you're doing? I have a few questions.

Did you follow the instructions in that sample's README?
Did you have any difficulty getting the sample to run?
Is the message being shown on startup or when you send a message to the bot?
Where is the message being shown?
Were you able to determine any additional info about the error, such as what method is not allowed?
Are you using Visual Studio Code?
Are you running the sample in command prompt or a VS Code terminal?

@xronsx - Are you still working on this?

Closing due to inactivity


Blockchain snark failure when producing a block during catchup

We saw this blockchain snark failure in ITN:
"Constraint unsatisfied (unreduced):
Checked.Assert.equal
get_req: File "src/lib/snarky/src/base/merkle_tree.ml", line 447, characters 2-465
File "src/lib/consensus/proof_of_stake.ml", line 717, characters 21-28
get_vrf_evaluation: File "src/lib/consensus/proof_of_stake.ml", line 707, characters 6-1743
check: File "src/lib/consensus/proof_of_stake.ml", line 750, characters 8-1141
update_var: File "src/lib/consensus/proof_of_stake.ml", line 2178, characters 6-7348
next_state_checked: File "src/lib/consensus/proof_of_stake.ml", line 3437, characters 8-822
File "src/lib/blockchain_snark/blockchain_snark_state.ml", line 193, characters 15-22
step: File "src/lib/blockchain_snark/blockchain_snark_state.ml", line 141, characters 0-9581
rule_main
step_main

Constraint:
((basic(Equal(Var 8959)(Var 16837)))(annotation(Checked.Assert.equal)))
Data:
Equal<PHONE_NUMBER>883902739236776858773952015557165966707513751241091166217980840633<PHONE_NUMBER>274587516628819691165535377305385322414858796520817553439500966335"

here's the logs from gcloud
The cause of this blockchain snark error is that when producing block it's using the curr_epoch_snapshot instead of the last_epoch_snapshot as it should be. The root cause of this is that block producer didn't wait for catchup to finish before it does the vrf evaluation.
When vrf evaluation happens, we only have the root transition and the next_epoch_data.epoch of the root transition is less than k, which means epoch_is_not_finalized and this condition determines that we would pick curr_epoch_snapshot instead of the last_epoch_snapshot. see https://github.com/MinaProtocol/mina/blob/44af5c2865deb8b0363b8d976cb56f5624969b0c/src/lib/consensus/proof_of_stake.ml#L2660
If the node finished catchup, this condition would be false.
More generally, if we didn't finish catchup, then the snapshot returns by select_epoch_snapshot could be wrong. This commented out assertion would actually catch this: https://github.com/MinaProtocol/mina/blob/44af5c2865deb8b0363b8d976cb56f5624969b0c/src/lib/consensus/proof_of_stake.ml#L3105C39-L3105C39 But this should not be an assertion, otherwise the node would crash.
My suggestion is to make block producer be aware of the frontier length at least. If we don't want to deal with the status of the node, we should at least have the node to only do vrf evaluation until we have a full frontier (unless it's in the first epoch). Another thing we could do is that pass the current frontier length to get_epoch_data_for_vrf and modify the select_epoch_snapshot function so that it would also consider the transition frontier length. This would prevent what we saw here.

A similar failure was reported right after the stop-slot release for berkeley upgrade.
Failure:
{"timestamp":"2024-05-21 15:36:00.704803Z","level":"Error","source":{"module":"Prover","location":"File \"src/lib/prover/prover.ml\", line 395, characters 6-18"},"message":"Prover failed: $error","metadata":{"error":{"commit_id":"039296a260080ed02d0d0750d185921f030b6c9c","exn_name":"Base__Exn.Sexp","exn":["monitor.ml.Error",["Snarky.Checked_runner.Runtime_error(_, _, _, _)\n\nEncountered an error while evaluating the checked computation:\n  (Failure\n   \"Constraint unsatisfied (unreduced):\\\n  \\nChecked.Assert.equal\\\n  \\nget_req: File \\\"src/lib/snarky/src/base/merkle_tree.ml\\\", line 466, characters 2-471\\\n  \\nFile \\\"src/lib/consensus/proof_of_stake.ml\\\", line 697, characters 19-26\\\n  \\nget_vrf_evaluation: File \\\"src/lib/consensus/proof_of_stake.ml\\\", line 687, characters 4-1470\\\n  \\ncheck: File \\\"src/lib/consensus/proof_of_stake.ml\\\", line 727, characters 6-1090\\\n  \\nupdate_var: File \\\"src/lib/consensus/proof_of_stake.ml\\\", line 2144, characters 4-7081\\\n  \\nnext_state_checked: File \\\"src/lib/consensus/proof_of_stake.ml\\\", line 3510, characters 6-787\\\n  \\nFile \\\"src/lib/blockchain_snark/blockchain_snark_state.ml\\\", line 95, characters 15-22\\\n  \\nstep: File \\\"src/lib/blockchain_snark/blockchain_snark_state.ml\\\", line 70, characters 0-8243\\\n  \\nrule_main\\\n  \\nstep_main\\\n  \\n\\\n  \\nConstraint:\\\n  \\n(((basic(Equal(Var 13058)(Var 19151)))(annotation(Checked.Assert.equal))))\\\n  \\nData:\\\n  \\nEqual<PHONE_NUMBER>8582155473642761626705275725063783935662720841902624035777508751549<PHONE_NUMBER>5791422621947821151777945949077654236985877203523091637427140698613\")\n\nLabel stack trace:\nget_req: File \"src/lib/snarky/src/base/merkle_tree.ml\", line 466, characters 2-471\nFile \"src/lib/consensus/proof_of_stake.ml\", line 697, characters 19-26\nget_vrf_evaluation: File \"src/lib/consensus/proof_of_stake.ml\", line 687, characters 4-1470\ncheck: File \"src/lib/consensus/proof_of_stake.ml\", line 727, characters 6-1090\nupdate_var: File \"src/lib/consensus/proof_of_stake.ml\", line 2144, characters 4-7081\nnext_state_checked: File \"src/lib/consensus/proof_of_stake.ml\", line 3510, characters 6-787\nFile \"src/lib/blockchain_snark/blockchain_snark_state.ml\", line 95, characters 15-22\nstep: File \"src/lib/blockchain_snark/blockchain_snark_state.ml\", line 70, characters 0-8243\nrule_main\nstep_main\n\n\nRaised at Stdlib.failwith in file \"stdlib.ml\", line 29, characters 17-33\nCalled from Snarky_backendless__Checked_runner.Make_checked.add_constraint in file \"src/lib/snarky/src/base/checked_runner.ml\", line 188, characters 8-329\nCalled from Snarky_backendless__Checked_runner.Make.handle_error in file \"src/lib/snarky/src/base/checked_runner.ml\", line 345, characters 8-12\n"],["Raised at Snarky_backendless__Checked_runner.Make.handle_error in file \"src/lib/snarky/src/base/checked_runner.ml\", line 355, characters 8-419","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 417, characters 20-65","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_handler in file \"src/lib/snarky/src/base/checked_runner.ml\", line 214, characters 16-66","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 425, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Checked_runner.Make_checked.with_label in file \"src/lib/snarky/src/base/checked_runner.ml\", line 140, characters 16-46","Called from Snarky_backendless__Checked_runner.Make.run in file \"src/lib/snarky/src/base/checked_runner.ml\", line 413, characters 19-43","Called from Snarky_backendless__Snark0.Run.Make_basic.run in file \"src/lib/snarky/src/base/snark0.ml\", line 1808, characters 22-47","Called from Blockchain_snark__Blockchain_snark_state.rule.(fun) in file \"src/lib/blockchain_snark/blockchain_snark_state.ml\", line 304, characters 10-135","Called from Snarky_backendless__Snark0.Run.Make_basic.with_label in file \"src/lib/snarky/src/base/snark0.ml\", line 2476, characters 14-18","Called from Pickles__Step_main.step_main.main.(fun) in file \"src/lib/pickles/step_main.ml\", line 152, characters 10-80","Called from Snarky_backendless__Snark0.Run.Make_basic.with_label in file \"src/lib/snarky/src/base/snark0.ml\", line 2476, characters 14-18","Called from Snarky_backendless__Snark0.Run.Make_basic.handle in file \"src/lib/snarky/src/base/snark0.ml\", line 2461, characters 14-18","Called from Snarky_backendless__Snark0.Run.Make_basic.Proof_system.mark_active in file \"src/lib/snarky/src/base/snark0.ml\", line 2370, characters 20-24","Re-raised at Snarky_backendless__Snark0.Run.Make_basic.Proof_system.mark_active in file \"src/lib/snarky/src/base/snark0.ml\", line 2375, characters 10-19","Called from Snarky_backendless__Snark0.Run.Make_basic.as_stateful in file \"src/lib/snarky/src/base/snark0.ml\", line 1814, characters 14-18","Called from Snarky_backendless__Snark0.Make_basic.Checked.auxiliary_input in file \"src/lib/snarky/src/base/snark0.ml\", line 207, characters 13-27","Called from Snarky_backendless__Snark0.Make_basic.Run.generate_witness_conv.(fun) in file \"src/lib/snarky/src/base/snark0.ml\", line 1132, characters 12-132","Called from Pickles__Step.Make.f.(fun) in file \"src/lib/pickles/step.ml\", line 505, characters 6-1023","Called from Pickles.Make.compile.f.wrap in file \"src/lib/pickles/pickles.ml\", line 726, characters 12-63","Called from Prover.Worker_state.create.extend_blockchain.(fun) in file \"src/lib/prover/prover.ml\", line 122, characters 25-690","Called from Async_kernel__Monitor.Exported_for_scheduler.schedule'.upon_work_fill_i in file \"src/monitor.ml\", line 295, characters 42-51","Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5","Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47","Caught by monitor at file \"src/lib/prover/prover.ml\", line 119, characters 52-52"]]}

In this case-

The block failed was for height 355917 and global slot 557592
Parent block is at height 355916 and global slot 557585 . This was the latest block at the time (there is no other block between 557585 and 557592 . The node must have synced?
The parent block is 355th block of the epoch and so local consensus state should have updated by then?
It fails here which suggests the staking ledger could be incorrect but as per (3) it shouldn’t be?
The winning slot was determined much earlier (the node just bootstrapped around this time, still hadn’t caught up to the network

{"timestamp":"2024-05-21 15:12:36.572187Z","level":"Info","source":{"module":"Block_producer","location":"File \"src/lib/block_producer/block_producer.ml\", line 1080, characters 23-34"},"message":"Block producer won slot $slot in epoch $epoch","metadata":{"epoch":"78","slot":"672"}}

and used the ledger jxxZUYeVFQriATHvBCrxmtfwtboFtMbXALVkE4y546MPy597QDD
{"timestamp":"2024-05-21 15:12:36.572170Z","level":"Debug","source":{"module":"Consensus__Proof_of_stake","location":"File \"src/lib/consensus/proof_of_stake.ml\", line 3206, characters 6-18"},"message":"Using curr_epoch_snapshot root hash $ledger_hash","metadata":{"ledger_hash":"jxxZUYeVFQriATHvBCrxmtfwtboFtMbXALVkE4y546MPy597QDD"}}

In the blocks produced for this epoch (78), I see jxxZUYeVFQriATHvBCrxmtfwtboFtMbXALVkE4y546MPy597QDD as the next staking ledger and jxXwNfemxGwZcxKGhfrwzfE4QfxxGm5mkYieHQCafFkb6QBf9Xo as the staking ledger, confirming the issue with staking ledger selection when a node restarts during the first 290 blocks of a epoch


我的FIREFLY錢包地址無法收款

Issue description
atoi1qpaxxfagwejxzs0qg247svlm0gpd4ftmwywqfkpqu7sz9aleyzfwx0ya3ac
我的錢包地址長這樣
不能收IOTA
要如何解決
Firefly version
1.3.0
OS details
Windows 10
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue
照步驟來~沒辦法收款
Expected behaviour
幫我解決讓我能明日前收款成功我要質押
Actual behaviour
沒辦法收款IOTA
Errors
atoi1qpaxxfagwejxzs0qg247svlm0gpd4ftmwywqfkpqu7sz9aleyzfwx0ya3ac
為什麼我最前面不是iota

Issue description
atoi1qpaxxfagwejxzs0qg247svlm0gpd4ftmwywqfkpqu7sz9aleyzfwx0ya3ac 我的錢包地址長這樣 不能收IOTA 要如何解決
Firefly version
1.3.0
OS details
Windows 10
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue
照步驟來~沒辦法收款
Expected behaviour
幫我解決讓我能明日前收款成功我要質押
Actual behaviour
沒辦法收款IOTA
Errors
atoi1qpaxxfagwejxzs0qg247svlm0gpd4ftmwywqfkpqu7sz9aleyzfwx0ya3ac
為什麼我最前面不是iota

Hi,
You can create a new config without using a developer profile.

請你左下角按登出  "添加個人檔案" > 開發者設定檔的選項不要勾選  創立好的錢包位址開頭應該就是iota了

Do not use developer profiles in the Firefly Wallet if you are not a Developer. A developer Profile will connect you to the Testnet and generate addresses that do not work on IOTA Mainnet. These testnet addresses start with "atoi1" instead of the mainnet addresses "iota1".
If you have accidentally created a developer profile and did send funds to an "atoi1" address you have not lost your funds.
To make these funds accessible you need to use the "recover a wallet" function in Firefly while creating a new profile.
Create a "non developer" profile and use the 24 words that you have saved from your "developer profile" to restore this new profile (non developer).
Your funds will show up in this new profile.

非常感謝回答的各位大大~解決這個蠢問題了~^^

Issue can be closed


Fix multiple flaky tests in spring

Issue:

Rootcause:
Ordering in distinct is not guaranteed. Change the tests to ignore orders.

/azp run java - cosmos

/azp run java - spring - tests


Create feature/body branch

Create a new feature/body branch (based on develop), push to the remote repository - git push -u origin feature/body, and use it to edit the main content.

Done


EKS general pod failures (caused by kubelet crash?)

What happened:
We've had several instances where multiple nodes (1.24.16-20230825) have become unable to reliably launch Pods. Here's an example of the kinds of errors we see:
 Events:
   Type     Reason       Age                From               Message
   ----     ------       ----               ----               -------
   Warning  FailedMount  27s (x2 over 27s)  kubelet            MountVolume.SetUp failed for volume "lakefs" : mount failed: fork/exec /usr/bin/mount: resource temporarily unavailable
 Mounting command: mount
 Mounting arguments: -t tmpfs -o size=63510704128 tmpfs /var/lib/kubelet/pods/1cbf573e-2101-468e-b6df-9251edd3ada2/volumes/kubernetes.io~secret/lakefs
 Output:
   Warning  FailedMount  27s (x2 over 27s)  kubelet  MountVolume.SetUp failed for volume "kube-api-access-w866f" : mount failed: fork/exec /usr/bin/mount: resource temporarily unavailable
 Mounting command: mount
 Mounting arguments: -t tmpfs -o size=63510704128 tmpfs /var/lib/kubelet/pods/1cbf573e-2101-468e-b6df-9251edd3ada2/volumes/kubernetes.io~projected/kube-api-access-w866f
 Output:
   Warning  Failed   19s                kubelet  Error: failed to prepare subPath for volumeMount "input-artifacts" of container "wait"
   Warning  Failed   19s                kubelet  Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to start init: fork/exec /p
 roc/self/exe: resource temporarily unavailable: unknown
   Warning  Failed   18s                kubelet  Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF: unknown

What you expected to happen:
Nodes resilient under load.
How to reproduce it (as minimally and precisely as possible):
Nodes are under high CPU load, but there're other nodes under the same load that don't have this problem. We've only started seeing it in the last week but haven't changed the AMI since August, or any other configuration, like networking.
Clues of what I can look at next very welcome!
Anything else we need to know?:
Nodes in this state have restarting kubelets, which might be this.
Dec 19 16:22:16 ip-10-0-0-159 kubelet: runtime: failed to create new OS thread (have 12 already; errno=11)
Dec 19 16:22:16 ip-10-0-0-159 kubelet: runtime: may need to increase max user processes (ulimit -u)
Dec 19 16:22:16 ip-10-0-0-159 kubelet: fatal error: newosproc

I've also seen this ulimit error as Pod Events. When I run ulimit -u on the node using nsenter it tells me it's unlimited.  journal is also suppressing a lot of kubelet messages - so it's going quite nuts.
Nodes that get into this state do not recover reliability (some Pods do get scheduled) even after every workload is drained.
Environment:

AWS Region: us-east-1
Instance Type(s): m5.4xlarge
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.14
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.24
AMI Version: 1.24.16-20230825
Kernel (e.g. uname -a): Linux ip-10-0-0-159.ec2.internal 5.10.186-179.751.amzn2.x86_64 #1 SMP Tue Aug 1 20:51:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Release information (run cat /etc/eks/release on a node):

BASE_AMI_ID="ami-0f2b325398f933a81"
BUILD_TIME="Fri Aug 25 20:04:37 UTC 2023"
BUILD_KERNEL="5.10.186-179.751.amzn2.x86_64"
ARCH="x86_64"

@djmcgreal-cc check what's LimitNPROC in your /etc/systemd/system/containerd.service file?

[root@ip-10-0-0-159 /]# cat /etc/systemd/system/containerd.service
cat: /etc/systemd/system/containerd.service: No such file or directory
[root@ip-10-0-0-159 /]# grep -r LimitNPROC /etc
/etc/systemd/system.conf:#DefaultLimitNPROC=
/etc/systemd/user.conf:#DefaultLimitNPROC=
/etc/systemd/system.conf.d/50-limits.conf:DefaultLimitNPROC=infinity:infinity

[root@ip-10-0-0-159 /]# go version  /usr/bin/containerd
/usr/bin/containerd: go1.20.7
[root@ip-10-0-0-159 /]# go version /usr/bin/kubelet
/usr/bin/kubelet: go1.20.6

Does that mean it's not related to https://github.com/golang/go/issues/49438 (and https://github.com/golang/go/commit/14018c8becc385f79f62f9cdf24cab93fe3e0cdc?). If so I'm sad because you guys would've really have pulled it out of the bag there!

Then again, the errno is definitely 11, so either the retryOnEAGAIN isn't being called, or it's failing 20 times in a row?

@ ing @cartermckinnon due to https://github.com/awslabs/amazon-eks-ami/issues/899#issuecomment-1112702498.


Exception error when sending any prompts.

I have not been able to get LlamaSharp to work since version 0.2.0 - I am about to give up trying.  I'm trying to output to a rich text box and I previously had this working in older versions.
            ```

    public async static void ProcInput()
    {
        string userPrompt = Program.MainForm.txtInput.Text; // Get the user's input from the TextBox

        Program.MainForm.txtOutput.AppendText("\nUser: " + userPrompt + "\n");
        MainForm.txtInput.Text = "";

        // Call ChatAsync with the correct arguments
        await foreach (var text in Program._session.ChatAsync(Program.chatHistory, true, new InferenceParams() { Temperature = 0.9f, AntiPrompts = new List<string> { "User:" } }))
        {
            Program.MainForm.txtOutput.AppendText(text);
        }

        if (Program.MainForm.txtOutput.Lines.Length > 0)
        {
            // Remove the last line
            int lastLineIndex = Program.MainForm.txtOutput.Lines.Length - 1;
            Program.MainForm.txtOutput.Text = string.Join(Environment.NewLine, Program.MainForm.txtOutput.Lines.Take(lastLineIndex));
        }
    }

    public static void InitAI()
    {
        // Load a model
        var parameters = new ModelParams(Program.modelPath)
        {
            ContextSize = 1024,
            Seed = 1337,
            GpuLayerCount = 80
        };

        // Initialize chat history
        Program.chatHistory = new ChatHistory(); // Reset chat history to start fresh

        // Concatenate the user prompt to the existing prompt
        Program.chatHistory.AddMessage(AuthorRole.System, "Transcript of a dialog, where the User interacts with an Assistant named Bob. Bob is helpful, kind, honest, good at writing, and never fails to answer the User's requests immediately and with precision.");
        Program.chatHistory.AddMessage(AuthorRole.User, "Hello, Bob.");
        Program.chatHistory.AddMessage(AuthorRole.Assistant, "Hello. How may I help you today?");

        InferenceParams inferenceParams = new InferenceParams()
        {
            MaxTokens = 256, // No more than 256 tokens should appear in answer. Remove it if antiprompt is enough for control.
            AntiPrompts = new List<string> { "User:" } // Stop generation once antiprompts appear.
        };

        var model = LLamaWeights.LoadFromFile(parameters);
        var context = model.CreateContext(parameters);
        var executor = new InteractiveExecutor(context);
        ChatSession session = new ChatSession(executor, Program.chatHistory);
        Program._session = session;
    }

This exception was originally thrown at this call stack:
    LLama.ChatSession.AddMessage(LLama.Common.ChatHistory.Message)
    LLama.ChatSession.ChatAsync(LLama.Common.ChatHistory, bool, LLama.Abstractions.IInferenceParams, System.Threading.CancellationToken)
    LlamaSharp10.Program.ProcInput() in Program.cs

    ArgumentException: Cannot add a system message after another message (Parameter 'message')

    System.Reflection.TargetInvocationException: 'Exception has been thrown by the target of an invocation.'

Hi, the problem is that you use Program.ChatHistory to initialize the session and again feed it to the session when generating output. Thus, the system message is fed to the session after the chat has started, which is not allowed. Please construct a new ChatHistory or HistoryMessage object in ProcInput, rather than reuse Program.ChatHistory there.
I wrote these words on my phone so some spells may be not correct. I believe you could find them according to the semantic. ：）

Thanks for the quick response, I still get the same error unfortunately.
I have not been able to get LlamaSharp to work since version 0.0.2 and the old versions do not support GGUF models.
{
    string userPrompt = Program.MainForm.txtInput.Text; // Get the user's input from the TextBox

    Program.MainForm.txtOutput.AppendText("\nUser: " + userPrompt + "\n");
    MainForm.txtInput.Text = "";

    Program.chatHistory = new ChatHistory(); // Reset chat history to start fresh

    // Concatenate the user prompt to the existing prompt
    Program.chatHistory.AddMessage(AuthorRole.System, "Transcript of a dialog, where the User interacts with an Assistant named Bob. Bob is helpful, kind, honest, good at writing, and never fails to answer the User's requests immediately and with precision.");
    Program.chatHistory.AddMessage(AuthorRole.User, "Hello, Bob.");
    Program.chatHistory.AddMessage(AuthorRole.Assistant, "Hello. How may I help you today?");

    // Call ChatAsync with the correct arguments
    await foreach (var text in Program._session.ChatAsync(Program.chatHistory, true, new InferenceParams() { Temperature = 0.9f, AntiPrompts = new List<string> { "User:" } }))
    {
        Program.MainForm.txtOutput.AppendText(text);
    }

    if (Program.MainForm.txtOutput.Lines.Length > 0)
    {
        // Remove the last line
        int lastLineIndex = Program.MainForm.txtOutput.Lines.Length - 1;
        Program.MainForm.txtOutput.Text = string.Join(Environment.NewLine, Program.MainForm.txtOutput.Lines.Take(lastLineIndex));
    }
}```

Hi， please don't add system message in ProcInput. Instead, add it only when initializing _session and only add user message when chatting

Hi， please don't add system message in ProcInput. Instead, add it only when initializing _session and only add user message when chatting

Thanks, there are errors now but it's not sending any output at all regardless of which model I pick. Each time LlamaSharp is updated I try each version in the hope I can get it to work in c# but to no avail.
I tried to ask for some help in the discord again.   I feel very pessimistic, is there another simpler version of LlamaSharp or a fork for dummies?

I'd recommend to pick an example in LLama.Example folder to see if you could get it to work, then try to integrate it into your project.
Of course, asking it in discord is also okay.


Upgrade dependencies

Codecov Report
Patch coverage has no change and project coverage change: -7.43 :warning:

Comparison is base (f52eb0f) 58.80% compared to head (f6d05ec) 51.38%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #218      +/-   ##
==========================================
- Coverage   58.80%   51.38%   -7.43%
==========================================
  Files          75       21      -54
  Lines        6178     1372    -4806
==========================================
- Hits         3633      705    -2928
+ Misses       2002      603    -1399
+ Partials      543       64     -479

see 54 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Problem getting data from firebase

Hi all,
First, thank your help.
I have the collection notes, with different documents and in them there is the field called description which is an array. In it there are different string which is what I want to print.
I know I have it mapped as a string, but nowhere do I see how to retrieve that data as if it were an array.
If you want to see the complete code you have it on my github, the project is called notas.

https://github.com/santiseijas/notas

The link is a screenshot of my firebase.

https://github.com/santiseijas/notas/blob/master/screenshots/firebase.png

I hope that I  have explained well and I hope you can help me. Thank you very much for taking this time with me.
════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following _TypeError was thrown building StreamBuilder<QuerySnapshot>(dirty, state: _StreamBuilderBaseState<QuerySnapshot, AsyncSnapshot<QuerySnapshot>>#9eb25):
type 'List<dynamic>' is not a subtype of type 'String'

The relevant error-causing widget was:
  StreamBuilder<QuerySnapshot> file:///C:/Users/seija/OneDrive/Escritorio/flutter/notas/lib/main.dart:72:12
When the exception was thrown, this was the stack:
#0      new Notas.fromMap (package:notas/firebase/model.dart:12:21)
#1      new Notas.fromSnapshot (package:notas/firebase/model.dart:16:14)
#2      _MyHomePageState._buildItem (package:notas/main.dart:116:25)
#3      _MyHomePageState._buildList.<anonymous closure> (package:notas/main.dart:111:40)
#4      MappedListIterable.elementAt (dart:_internal/iterable.dart:417:29)
...
════════════════════════════════════════════════════════════════════════════════════════════════════

import 'package:cloud_firestore/cloud_firestore.dart';

class Notas {
  final String titulo;
  final String descripcion;
  bool check;
  final DocumentReference reference;

  Notas.fromMap(Map<String, dynamic> map, {this.reference})
      : assert(map['titulo'] != null),
        titulo = map['titulo'],
        descripcion = map['descripcion'],
        check = map['check'];

  Notas.fromSnapshot(DocumentSnapshot snapshot)
      : this.fromMap(snapshot.data, reference: snapshot.reference);

  @override
  String toString() => titulo;
}

Hi @santiseijas
This 'List<dynamic>' is not a subtype of type 'String' indicates an issue with your code
This platform is not meant for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow. Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


Gui Overhaul, Part 2

Pull Request checklist
Note: these are not necessarily requirements

[ ] I reformatted the code with clang-format
[x] I checked to make sure my submission worked
[x] I am the author of submission or have permission from the original author
[ ] Requires update of the PS2SDK
[ ] Requires update of the gsKit
[ ] Others (please specify below)

Pull Request description
A lot of commits, most notably:

Optimise gfx/new logo
Multiple default/overlay/attribute image texture support for internal theme
Reset colors button in Display Settings
New English/Polish fonts
Update internal theme to Korium by Berion
Font scaling fix
Reorganise Menu options
Updated About page
Modes fix
4-bit/8-bit/1024x1024 PNG support
Info Page attribute text keys now translatable

Team effort with @KrahJohlito
Thanks to Berion for his gfx and @J013k for testing.
Test build - https://www.sendspace.com/file/eg8oh5

Can someone else try to save new settings when there is only one memory card inserted in 2nd port.
I mean OPL should create OPL folder and add settings there, instead of that I'm getting:
Error writing settings.


Scrapy run errors filenotfound

The scrapy run logs currently show two errors after execution on every run. Our setup is using scrapy to crawl a bunch of xml files so this error is really related to its default settings which apply more so for crawling URLs instead of files. The error appears to be related to a missing robots.txt file.
To fix this bug, the default scrapy settings need to be adjusted to disable searching for this file. We should be cautious with this if we decide to actually scrape urls in the future.
Stackoverflow question
Scrapy settings

Fixed with #11


502 Response Code

I've literally changed nothing and run zappa update dev
And now hitting the root path on the domain returns.
Error: Warning! Status check on the deployed lambda failed. A GET request to '/' yielded a 502 response code.
"{'message': 'An uncaught exception happened while servicing this request. You can investigate this with the zappa tail command.', 'traceback': ['Traceback (most recent call last):\n', '  File "/var/task/handler.py", line 570, in handler\n    with Response.from_app(self.wsgi_app, environ) as response:\n', '  File "/var/task/werkzeug/wrappers/response.py", line 287, in from_app\n    return cls(*run_wsgi_app(app, environ, buffered))\n', '  File "/var/task/werkzeug/test.py", line 1233, in run_wsgi_app\n    app_rv = app(environ, start_response)\n', "TypeError: 'NoneType' object is not callable\n"]}"
If I look at the cloud watch logs I get nothing back that is helpful. No stacktrace or anything useful. All that I get is
'NoneType' object is not callable
Python: 3.8.x
Zappa: Latest Version
from flask import Flask, request, jsonify, abort
import os
import traceback

env = os.environ.get("NODE_ENV", "local")
app = Flask(__name__)

@app.route('/', methods = ['GET'])
def index():
    return 'HELLO'

@app.route('/home', methods = ['GET'])
def home():
    return 'HELLO'

Zappa Settings
{
"dev": {
        "app_function": "api.app",
        "aws_region": "us-east-1",
        "profile_name": "xxxxxx",
        "project_name": "xxxxxx",
        "runtime": "python3.8",
        "s3_bucket": "zappa-xxxxxx",
        "slim_handler": true,
        "aws_environment_variables":{
            "NODE_ENV":"development"
        },
        "memory_size":2048,
        "timeout_seconds":30
    }
}

Requirements.txt
certifi==2021.10.8
click==8.0.4
cycler==0.11.0
elasticsearch==7.16.3
Flask==2.0.3
fonttools==4.29.1
imageio==2.16.1
itsdangerous==2.1.0
Jinja2==3.0.3
kiwisolver==1.3.2
MarkupSafe==2.1.0
matplotlib==3.5.1
networkx==2.7
numpy==1.22.2
packaging==21.3
Pillow==9.0.1
pyparsing==3.0.7
python-dateutil==2.8.2
PyWavelets==1.2.0
scikit-image==0.17.2
scipy==1.8.0
six==1.16.0
tifffile==2022.2.9
urllib3==1.26.8
Werkzeug==2.0.3

I've tracked this down to having openCV installed on the virtual environment. Even though it wasn't in the requirements it still gets packaged up.
However, I would actually like to have openCV installed. As I said this is returning no errors at all. Has anyone else had this issue with openCV?

Looks like getting openCV working is going to require using Layers.


feat: add a preloader aniamtion to the site

Description
animation that appears before the js files loaded (before first rendering)
and stops when js starting to render react components
screenshots
https://github.com/hasadna/open-bus-map-search/assets/1336862/685cbffb-962a-498e-9b46-98ddb860afdd

cool!


V4 single day fetch

Added queries to get data for single day charts. Haven't used these technologies before, so feedback is more than welcome.
TanStack has default behavior to refetch all queries on page focus. This meant if you switched tabs, clicked on dev tools, etc. then the data will be fetched when you return to the site. I disabled this on the queries I added. Not sure if people agree with that. Might be worth discussing.
I also added React Queries Dev tools. Shows up as a little flower icon on the page when in development. It didn't end up helping me much with the bug I was working on but it seems useful. I'm fine with keeping or removing it.
One really cool thing with react queries I didn't know about was the queryKeys. Lets you define what causes the query to refetch. So I set it up that headways and dwells don't rely on toStopIds changing, since the values won't change, as they only rely on fromStopIds.
I added a rewrite in next.config.js, which takes the place of the proxy we had before switching to next.js. It's included based on process.env.DEV_NODE === 'development'. Which is when the command next dev is used. Pretty sure that's what we want but if someone knows better lmk.

Added the query client defaults, I ended up not using keepPreviousData since it was causing some odd behavior on the charts. (more on that below).
I also did some kinda funky stuff to get the SingleDayAPIOptions type to work as I wanted. Open to suggestions on that.
weird chart behavior: When I change the date, the old data stays at first but since the date is changed, the x axis on the graph changes. For example if I start with 11/19/22 then switch to 11/01/22 the X axis will be from 11/01/22 6:00 AM to 11/20/22 1:00 AM. All the existing data squishes up to the right side until the new data loads. I'm also concerned it might not be the best user interface since if the new data fails to fetch there wouldn't be any indication that it has failed, and the old data would still be there. We could probably solve that by watching the query and displaying some sort of error. But at that point I'm wondering if we're gaining anything from keeping the data.

Not sure if this is a result of this PR or the last, but looks like the legend is now underneath the chart instead of on the side. I think some css was lost. Doesn't need to be addressed here, just noting it


Add versioning to ProofCI GitHub Actions workflow file

@kstribrnAmzn asked during a demo of the ProofCI GitHub Actions whether the workflow file is versioned.  It currently isn't.
We should add a comment within proof_ci.yaml that indicates the version of the CBMC starter-kit that generated/contributed this workflow file à la Makefile.common

Thanks for tagging me here! I'll keep my eyes on this issue as it progresses.

Resolved.


⚠ Bofrost.ch has degraded performance

In c7fe0a0, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 2139 ms

Resolved: Bofrost.ch performance has improved in 1bc892a after 7 minutes.


error oon upload to /api folder on local

im uploading file and get error during uploading .. where can i put "/api" folder in my local or remote url ?
thank you

Hi is it possible you had the validate size plugin installed? if so, please update the plugin 2.2.4, it contained a bug.


Incorrect value for pretrained in the readme

model = torch.hub.load("chenyaofo/pytorch-cifar-models", "cifar_resnet20", pretrained=true)
should be
model = torch.hub.load("chenyaofo/pytorch-cifar-models", "cifar_resnet20", pretrained="cifar10")
or
model = torch.hub.load("chenyaofo/pytorch-cifar-models", "cifar_resnet20", pretrained="cifar100")

Yes. I am working to fix it.
I plan to train more models and release them recently . In the meanwhile, the api of this repo will be changed.
Thank you.

I have corrected the readme and code.


Removes certmanager's certificates from preview environments

Description

Related to https://github.com/gitpod-io/gitpod/issues/6291, this PR removes all certificates that were added to preview environments by this repository.

Closing this one as we decided to not move forward with replacing certificates on previews


test: improve error messages

If a response status assertion fails or a response body can't be
parsed as JSON, then ensure the response status and body are included
in the error message.

Closes #269
Closes #275
Closes #276

way better 💃


Breakpoints and media queries not taken into account

This may be due to to the fact that I'm using a development server build (create-react-app) but other than this Hypothesis, I really don't know why this doesn't work.

I love this tool, however, the "breakpoints view" does not work as it did in the previous version. It does not recognize all the media query CSS breakpoints.

I can't get it to work either. Even the main website shows no breakpoints.

Anyone know of an alternative or anyone developing? Came looking for Re-View after a long hiatus and would love the tool back.


Ship Stuck in Planet

I was in the imperialBig ship on the first planet, the rocky planet, and got stuck inside the planet.
Seems like it's happened a few times before: http://steamcommunity.com/app/342980/discussions/1/606068060828393540/

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Yup have heard about this before, it just seems really tricky to reproduce and thus troubleshoot further.
Had coincidentally mentioned it to @grauerkoala earlier today in relation to #58 since it is probably some obscure bug like that which can cause it (but not that one)

Another report - suggests (again) maybe the Vanguard (aka imperialBig) in particular can hit this issue. Problem with its hit box?
http://steamcommunity.com/app/342980/discussions/1/520518053428477307/

More details from the last post, with possible reproduction instructions:
"go to a flat spot on a planet then move your mouse in a clockwise circle around the ship for a minute or two thats how it worked for me"
So maybe you can sort of "wiggle" your way through the surface with a Vanguard.

This just happened to me with the Beetle on 1.3.0, so it's not Vanguard-specific.

Thanks for the extra detail @Viech :-)

And another: http://steamcommunity.com/app/342980/discussions/1/520519112496560688/
Tendency for ships to "jump" slightly / be able to skip physics/collissions briefly? Seems related.

What if you changed the rendering of the planet, so the it is no-longer renders as lots of little objects... what if you tried to do something more along the lines of pre-made planets. This would work by joining together the images and make a single .png and then load and scale that into the game.

Anyone got an image of this?

I got this problem too - when the tower on the snow planet shot me with a paralysing weapon, i teleported in the ground, under the tower.

Ok thank you @OxidizeMonk.
Out of respect to the developers, here is how to fix it.   @Cervator.
You need to re-do the collision boxes, probably make them 3 pixels bigger than what they need to be.
This will compensate for the code not joining them to pixel perfection.

Thanks @crazywolf132. Is that something you've tested in your fork, or just a theory? Did you redo your collision shapes successfully using some fixed version of the Box2D editor? Is it accessible somewhere?

Our fixed box2D we lost... We got crypto Virus. As far as i am aware it is what we tested in our fork, but seen we are re-basing it, it wont be there. I will do some work on it tonight and get back to you with the result and the code if it checks out and doesn't cause any bugs.

Another screenie of it happening via Steam:
http://steamcommunity.com/sharedfiles/filedetails/?id=884620460
From http://steamcommunity.com/app/342980/discussions/1/133259956004535197/

Do you have a log for that @Cervator ?

Old issue, still happens. Got a screenie for once and thought it interesting you can see a tiny spot of sky in the ground - seems highly likely that the "ground chunks" are being placed with gaps that are too large at times letting there be incomplete collision shapes that ships can sneak through (as usual this was an imperial large)


ReCaptcha needs do be enabled in resident IDP in each tenant domain in multi tenant environment.

Is your suggestion related to an experience ? Please describe.
When checking for 'ReCapthca' validation the 'ReCapthca' validation, the configurations of the resident IDP of the login user's tenant domain[1] will be captured. Since the publisher/devportals are used as Saas applications and since were enabling the 'ReCaptcha' for the relevant Saas application hope configurations of the resident IDP of SaaS application's tenant domain(the tenant domain which the relevant application is created) should be considered instead of the login user's tenant domain resident IDP configurations.
Describe the improvement
It is better if we can consider the configuration of the SaaS application instead of the relevant user.
Additional context
N/A

Fixed by

identity-governance #598
identity-local-auth-basicauth #143


update query param Link to

Updated the query param syntax on the active-links example. When trying the example, couldn't get the code to compile at first in the example, and noticed the query param syntax had changed, so updated it, and am making this PR.

The example has the correct syntax against master.


Support for SIMD improved

Unfortunately, MLIR does not lend itself to easily simdized code that compress results to different bit width.
For IsInf, the inputs are float, and the output are bits. Now most SIMD arch would represent "true" or "false" using the same number of repeating bits as in the input (e.g. 32 bit float, IsInf would result in 32 bit of zero or 32 bits of 1). That is relatively easy to generate code for. But MLIR generates a single bit vector. So a 4x 32 bit SIMD unit of 128 bits would need to generate a 4x1 bit result... but SIMD units typically only generate 128 bit results, not a subset of it.
Thus, element wise operations that reduces (or increases) the sizes of their output with respect of their inputs cannot be easily handled at this time.
This PR nevertheless enable SIMD for INF constants, so that if their outputs are used in a select, they would be able to be used as SIMD operations.
This PR responds to issue #2279

Jenkins Linux amd64 Build #11661 [push] support for SIMD improve... started at 14:43

Jenkins Linux ppc64le Build #10718 [push] support for SIMD improve... started at 15:50

Jenkins Linux s390x Build #11671 [push] support for SIMD improve... started at 15:43

Jenkins Linux amd64 Build #11661 [push] support for SIMD improve... failed after 1 hr 18 min

Jenkins Linux s390x Build #11671 [push] support for SIMD improve... passed after 1 hr 40 min

Jenkins Linux ppc64le Build #10718 [push] support for SIMD improve... passed after 1 hr 53 min


[ignore] test

Signed-off-by: Ahmet Alp Balkan<EMAIL_ADDRESS>

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Policiy refactor. Renamed Bucketers to Dimensions

Description
First step of policy refactor. Renamed bucketers to dimensions to fit the policy draft.
This implies to rename packages, maven modules, class names and example policies
Note: I think StreamingContextService needs a refactor. This class is responsible of too many things: input, output, parsers, ... creation and spark-streaming-context creation. One way would be to create a factory for each component (InputFactory, ParserFactory,...)
Reviewer
@anistal
Test
1 test added
Scalastyle
All test passed.

Done! @anistal


Improvements to K6 Load and Performance Tests

Description:

Fixed Typo on README.md
Included P95 (Percentile 95) on the markdown report at the final step of the performance tests

Related issue(s):
N/A
Fixes #867
Notes for reviewer:

a.
Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Base: 74.33% // Head: 74.75% // Increases project coverage by +0.42% :tada:

Coverage data is based on head (5be29bd) compared to base (419ea9f).
Patch coverage: 62.85% of modified lines in pull request are covered.

:exclamation: Current head 5be29bd differs from pull request most recent head fa280a7. Consider uploading reports for the commit fa280a7 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #899      +/-   ##
==========================================
+ Coverage   74.33%   74.75%   +0.42%
==========================================
  Files          29       29
  Lines        1835     1838       +3
  Branches      341      344       +3
==========================================
+ Hits         1364     1374      +10
+ Misses        373      367       -6
+ Partials       98       97       -1

Impacted Files
Coverage Δ

packages/relay/src/lib/clients/sdkClient.ts
20.70% <0.00%> (-0.43%)
:arrow_down:

packages/relay/src/lib/errors/SDKClientError.ts
62.50% <0.00%> (-4.17%)
:arrow_down:

packages/relay/src/lib/eth.ts
84.74% <65.21%> (+1.84%)
:arrow_up:

packages/relay/src/lib/clients/mirrorNodeClient.ts
94.42% <100.00%> (+0.09%)
:arrow_up:

packages/relay/src/lib/errors/JsonRpcError.ts
72.72% <100.00%> (+2.72%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Do we care about other P values (P50, P99)?

Do we care about other P values (P50, P99)?

@lukelee-sl, we are already persisting the Average or (P50).
I also thought on including P(99) but was not sure if we wanted that information, I could add it if you think we should. personally I was not sure it would be valuable.

Do we care about other P values (P50, P99)?

@lukelee-sl, we are already persisting the Average or (P50).
I also thought on including P(99) but was not sure if we wanted that information, I could add it if you think we should. personally I was not sure it would be valuable.

Maybe you are right.  I think having a P99 might help to point out how often extreme outliers are encountered but we can always add this later if it becomes necessary.

@AlfredoG87 is this the version that doesn't add setup logic to populate contracts etc so that eth_call and eth_sendRawTransaction work?

@AlfredoG87 is this the version that doesn't add setup logic to populate contracts etc so that eth_call and eth_sendRawTransaction work?

@Nana-EC, That is correct. running them against previewnet or testnet, there is no problem, only issue is with local-node.


Question: Compiling for all of Windows, Linux, and MacOS when you do not have access to all

Hello,
I've been using Nukita to compile my Python code and it's been working great. However, I'm not sure how to compile my code for my friend, who runs MacOS. I'm running Nukita on Windows myself and I was wondering if it's possible to compile my code for both Windows and MacOS.
Any help would be greatly appreciated. Thank you!

This is a duplicate, cross compilation is not supported. However, GitHub can compile for you, check out: https://github.com/Nuitka/Nuitka-Action which will build for you.


hapi versions in README.md were out of sync

This has already landed on master I believe. Let me know if there is another concern here. Closing for now.


Performance Issues

This tool is really cool, but if you're working on a vertical solution with a few big files it slows the development really down.
For example, try to create a new Posting routing, just copy the Sales Post Codeunit and try to work in it.
This Codeunit got over 9500 lines it takes around 2 Minutes to save changes if the AL XML Documentation is enabled.
If you disable this extension it takes around 1 sek.
In 8 of 10 times it's faster to save, cancel the process, close VSCode and restart it, than waiting for the process to end.
If you need help to create an environment to get this issue just write me.
Perhaps it's possible to optimize this extension.

Thank you @TCMatthiasMartin for reporting.
We did some performance enhancements in the upcoming version, but I will look into it and try find out whats taking that much time in saving document.

You're absolutely right, we've two performance issues here.
First, the procedure detection takes way to long:

Second, the process is fired each time you change anything in the file. So If you for example do type 4 characters the update process is exectued 4 times and we do not wait 5 seconds, but 20 seconds.
To be honest our files are much smaller than for example Sales Post Codeunit, but it is a bug that we will fix as soon as possible.
Thanks again for bringing this issue to our attention.

@sirhc101 normally we have smaller files too, but in a few cases the files are (in my opinion) way to large.
I'm happy that I could help you to find an issues.
Thanks for reacting that fast to my request!
Thumbs up!


Fixing typos & updating stats

I updated a few statistics like the npm count of packages since it is relatively bigger now, and additionally corrected a few typos I came across as I browsed. Hopefully I'll be able to migrate a bit of info to the wiki and make this Readme a bit smaller and more friendly to newcomers.

Forgot about this, sorry :-P

All good! Hahah

;-) When we launch the 1.0 release we'll need to look into split NodeOS in several subprojects specially the cross-compiler, it's too much heavy and almost all the build errors comes from there... :-/

@piranna hahaha that's a good idea!

We could start by packaging an publishing noGUI and later do the same with GCC and QEmu.

The binaries are stored on github, right ?

@Coretool which binaries?
@piranna I'm forking and going to attempt to rip QEmu out of the build process.

@lite20 the prebuilt ones

@Coretool which binaries?
@lite20 the prebuilt ones

The only prebuild binaries that are currently available are NodeOS prebuild images, we would need to publish the QEmu and gcc ones using the prebuild module I told you the other day. This could have the advantage that would allow to install a working version of gcc inside NodeOS and allow to install compiled modules... :-) But it will need some work to get to that point, being the first step to make the cross-compiler an independent module and use it as dependency of nodeos-barebones.

What makes the cross-compiler 'special' ?

It looks pretty independent from my point of view ... (I am refering to the nodeos-cross-toolchain repo). Do you just want it to be a(-nother) prebuilt package ? Or do you want to make gcc a prebuilt package ? (Or even both)

What makes the cross-compiler 'special' ?

Nothing itself, only the point that if we set it as dependency of all the layers, it would be installed several times... but if we create prebuild images, this would not be a huge problem because we would not spend time generating it several times.

It looks pretty independent from my point of view ... (I am refering to the nodeos-cross-toolchain repo). Do you just want it to be a(-nother) prebuilt package ? Or do you want to make gcc a prebuilt package ? (Or even both ?)

I'm thinking only about nodeos-cross-toolchain, having inside gcc, binutils and friends pre-generated for all the platforms NodeOS is ported, somewhat similar to how it's packaged on regular Linux distros, only that this package would all all the cross-toolchain. with compiler, linker, libraries... Don't remember if there's already a cross-toolchain repo, but if so it will be outdated, so we would need to update its content. Would you be able to point us to what have you found?

It's at github.com/nodeos/nodeos-cross-toolchain... This repo just contains the build scripts, I think...  Sounds great... ;)

It's at github.com/nodeos/nodeos-cross-toolchain... This repo just contains the build scripts, I think...

I supposed so... This repo is one year ago, it needs to get updated, but yes, it's the correct one :-) You could start working on it if you want and later I'll update it, this way we don't loose the commits history :-)

So you wanna create a prebuilt package with all the build utils and their friends and families (...) Sounds great... ;)

Yes, and this one could also be used to install native modules inside of NodeOS or being use as basis for other cross-compiled related projects making them easier to use :-)

What makes the cross-compiler 'special' ?
Nothing itself, only the point that if we set it as dependency of all the layers, it would be installed several times...

Oh. Could we not have the scripts install it globally? Or have the modules arranged in a way where the path of it could be fetched relatively? (navigate from current location say to the nodeos node modules folder where it's expected to be, and import from there)
Just an idea for that issue.

Or have the modules arranged in a way where the path could be fetched relatively

That's what I thought about too... Which platforms should these prebuilt packages support ?

Could we not have the scripts install it globally?

npm don't support this and never will do, sorry :-(

Or have the modules arranged in a way where the path of it could be fetched relatively?

Yeah, I was thinking about using this solution, some modules like phantomjs does it :-) We could put it (by the moment) as a direct dependency of nodeos module the same way as the different layers. I didn't do it before because they are resolved in alphabetical order and the championship needed to have only one repository, but since external dependencies in a same level are fetched and processed before the included ones, this could work... :-)

I'll start compiling some binaries today, which platforms should these prebuilt binaries support ?

By the moment only the ones supported by NodeOS, it's said, linux i686 and linux x86_64, both as host and target. This will lead to having two packages, one for i686 and other for x86_64 (that the host platform, and each one will contain binaries to generate for i686 and x86_64 thenselves).

So I'll make a normal gcc binary first, are there any things I have to look at ?

nodeos-crosscompiler module is somewhat autonomous and independent. By default it detect the platform where is running and generate a cross-compiler for itself, so start it (just npm install). You can be able to set different platforms and CPUs using environment variables, take a look at scripts/adjustEnvironment.sh to generate both the i686 and x86_64 versions. After that, they'll be generated on the out folder, would be good to add a .npmignore file with everything except that folder. Finally you could publish this package on npm but it will be too heavy, so it's better you take a look about how to publish it on GitHub using prebuild.
I think I've not left anything... :-P

Then let the compilation begin ;)
Publishing to github using prebuild isn't hard; it's just prebuild --upload
Afterwards, we have to add prebuild --install to the package.json's install command...

Woah! :-D When you get it working create a repo for it and publish the prebuild images there, later we'll see how to organize it :-)


Rejection modal - Empty dropdown

This dropdown for rejections probably shouldn't be here. It shows no estimation fee and nothing to edit, this is because tx rejections don't have anything that can be edited in the advanced options (The nonce is already set in stone by the tx that will be rejected, so you can't edit that one)

Originally posted by @francovenica in https://github.com/gnosis/safe-react/pull/3373#issuecomment-1028938991

@francovenica fixed it and merged into #3373 for QA there

I checked in the 3373.
For 2/x safes is fine, the dropdown is not there anymore and the dropdown that is there shows the fields grayed out.

For a safe 1/x safe the situation is different because trying to reject the tx already tries to execute it, so the dropdown and form look like this, although no input can be edited for the same reason stated in the other comments (nonce is not editable for rejections)

I think we should agree on how this should work before doing any changes.

Nevermind. The issue reported in the previous comment was addressed here https://github.com/gnosis/safe-react/issues/3429
We can close this one since is already merged in the main Epic


To find the path of this (and other) assemblies (dll and exe) in VS 2017 and later, use vswhere.exe

This is how to find TextTransform.exe using powershell and vswhere.exe
#the path to VSWhere.exe is always in programfiles(x86)

$progFilesx86Path = [System.Environment]::ExpandEnvironmentVariables("%programfiles(x86)%")
$vsWherePath = Join-Path $progFilesx86Path "\Microsoft Visual Studio\Installer\vswhere.exe"

# this tells vswhere to use paths of the latest version of visual studio installed
# to locate this exe anywhere in those paths, and return a single textual value (not a json object or xml payload)
$ttExe = & $vsWherePath -latest -find **\TextTransform.exe -format value
if (-Not(Test-Path $ttExe)){
	throw "Could not locate TextTransform.exe"
}

#then to invoke a transformation
& "$ttExe"  c:\Source\YourTransform.tt

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

ID: e8177d9b-f8d7-419e-d81d-ce25a44b084f
Version Independent ID: 43a69770-1eab-06e1-868c-3d8f1c32716d
Content: Generating Files with the TextTransform Utility - Visual Studio
Content Source: docs/modeling/generating-files-with-the-texttransform-utility.md
Product: visual-studio-windows
Technology: vs-ide-modeling
GitHub Login: @jillre
Microsoft Alias: jillfra

@StingyJack Thank you for the feedback, assigning this to the author for review.

Closed as this isn't a doc issue. If you'd like to suggest a change to the documentation, please feel free to open a GitHub pull request.

@JoshuaPartlow  there is a section in the doc that lists default, but possibly incorrect pathing. This is a reliable way to get the path.


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 001a6e8, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 12397 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 36d69a2 after 28 minutes.


Fix: Updated PackageSupplier to type Organization for JAR files

Issue:
The PackageSupplier and PackageOriginator are set to type 'Person' for JAR files. For example:
PackageName: jackson-annotations
SPDXID: SPDXRef-Package-java-archive-jackson-annotations-55544ed7d2a352e0
PackageVersion: 2.9.10
PackageSupplier: Person: FasterXML
PackageOriginator: Person: FasterXML

Fix:
Updated to set the type as 'Organization' if vendor is specified in the metadata file of the JAR.
Result:
PackageName: jackson-annotations
SPDXID: SPDXRef-Package-java-archive-jackson-annotations-55544ed7d2a352e0
PackageVersion: 2.9.10
PackageSupplier: Organization: FasterXML
PackageOriginator: Organization: FasterXML

As we discussed, I think this is a good change, could you consider adding a test so we don't regress here?

As we discussed, I think this is a good change, could you consider adding a test so we don't regress here?

The tests were there, the file was not checked in. Can you please re-trigger the workflow to run the tests? Thanks


Input new 2023/2024 Program Year Calculations (Tables) PT

Policy Manual for 23/24
https://studentaidbc.ca/sites/all/files/school-officials/policy_manual.pdf

Being completed on #2301


fix: use custom text-area component for bio

Description
Fixed design of bio section. Replaced in-built textarea with Textarea component.

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

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

Related Tickets & Documents
Fixes #2046

Mobile & Desktop Screenshots/Recordings
Bio section
Before

After

Additional Changes
Before

After

Before

After

Added tests?

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

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[X] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@itskish0re, thanks for the PR!
This relates to work we have around setting some base styling for all elements in the app, e.g. focus states for form elements. For this current issue, let's avoid updates to the custom textarea component. For now, replicate the focus styles directly on the bio textarea. We'll have some near future work that will render focus styles uniform in the app. See https://github.com/open-sauced/app/issues/2149#issuecomment-1811762611

@nickytonline, I have made the changes.


Open access to all endpoints by default

Being closed by default is making it hard to diagnose issues in this early stage. We will revisit this decision.

All clear now.


Crash when immediately stopping the image acquirer

Describe the Issue
I'm trying to run harvesters with with a GigE Vision camera, but if I start an image acquisition and immediately stop it, python crashes with the attached traceback.
To Reproduce
Steps to reproduce the behavior:
Execute the following sample code with python.exe .\test.py
Sample Code
from harvesters.core import Harvester as HarvesterCore
import time

hc = HarvesterCore()
hc.add_file("C:/Program Files/MATRIX VISION/mvIMPACT Acquire/bin/x64/mvGenTLProducer.cti")
print(hc.files)
hc.update()
image_src = hc.create(0)
image_src.start()
image_src.stop()  # dead

print ("pause")

The following traceback happens:
traceback.txt
Expected Behavior
This sequence of calls should not crash.
Screenshots
If applicable, add screenshots to help explain your problem; Note that it is not necessary to put everything as a screenshot! If the source is a text just paste the text because that is much helpful for us.
Configuration

OS: Windows 11
Python: Python 3.10.4
Harvester: https://github.com/genicam/harvesters/commit/3b2333c250e2e54725721d4affb71619244dba79
GenTL Producer: MATRIX-VISION mvIMPACT Acquire 2.48.0
Camera doesn't seem to matter

Reproducibility
This phenomenon can be stably reproduced:

[x] Yes
[ ] No.

Actions You Have Taken
I have tried with harvesters 1.4.0, same result.

[x] I've read the Harvester FAQ page.

@kazunarikudo I've checked the GenTL spec and found that my pull request #382 is not correct and it is probably the cause of this issue.
_flush_buffers method is implemented using DSFlushQueue with the ACQ_QUEUE_ALL_DISCARD command, which flushes all buffers from all queues and additionally it revokes all of them, which is the thing I missed.
Because I wrongly implemented the ACQ_QUEUE_ALL_DISCARD in my producer by not revoking the buffers, I was not seeing the issue in my tests.
Subsequent calls to revoke_buffer fail due to this.
The best solution would be to remove the for loop which revokes all the buffers because _flush_buffers already takes care of that. (but the revoke debug message would disappear too)
My sincere apologies


DataTarget.CreateSnapshotAndAttach error: Unable to find an entry point named 'PssCaptureSnapshot' in DLL 'kernel32.dll'

This line of code produces the error below:
  var target = DataTarget.CreateSnapshotAndAttach(Process.GetCurrentProcess().Id);
System.EntryPointNotFoundException: Unable to find an entry point named 'PssCaptureSnapshot' in DLL 'kernel32.dll'.
       at Microsoft.Diagnostics.Runtime.WindowsProcessDataReader.PssCaptureSnapshot(IntPtr ProcessHandle, PSS_CAPTURE_FLAGS CaptureFlags, Int32 ThreadContextFlags, IntPtr& SnapshotHandle)
   at Microsoft.Diagnostics.Runtime.WindowsProcessDataReader..ctor(Int32 processId, WindowsProcessDataReaderMode mode)
   at Microsoft.Diagnostics.Runtime.DataTarget.CreateSnapshotAndAttach(Int32 processId)
   at ServerAdminPlugin.StackTraceAnalyzer.GetAllStackTraces()

Environment: .NET 5 app running on Windows Server 2008 R2 Standard, with, among other things, latest .NET 5 SDK installed.  Same error happens on .NetFramework 4.8 app running on Windows Server 2008.
Same code works on dev machine (Win 10).
End result is this terminates the app, even though it's wrapped in try-catch.

I may have answered my own question.  Microsoft states that this function is only supported on:

Minimum supported client
Windows 8.1 [desktop apps only]

Minimum supported server
Windows Server 2012 R2 [desktop apps only]

Researching elsewhere, I found this function was only included on kernel32.dll version 6.3+.
Would be nice if this was noted somewhere in the docs around CreateSnapshotAndAttach use on Windows.

I encountered the same problems when back port cpython 3.12 to windows 7, and I rewrite the usage of PssCaptureSnapshot.
See https://github.com/liudonghua123/windows-python-installer/commit/d1ad543a51ce00e574b9aeeb768f7fa1c5020a0b, https://github.com/adang1345/PythonWin7/blob/master/patches/restore-win7-handling.patch.


Add ffmpeg version info

I'm not sure how you feel about this, but I can't really keep track of all the different version of ffmpeg internal libraries. the "friendly name" is really useful to know.
Let me know what you think.

For ffmpeg 6.1.2. this returns "6.1.2"
For ffmpeg 7(.0.0) this returns "7.0"
For ffmpeg 7.0.2 this returns "7.0.2"
For ffmpeg 7.1(.0) this returns "7.1"

I find the alignment with the branding much easier to communicate across developers.

Wow thanks for the quick review!


Changed DataQuery API batch size from 10 to 20

Changed the DataQuery API batch size from 10 to 20 requests; as per @lsimonsen

Codecov Report
Base: 60.62% // Head: 60.62% // No change to project coverage :thumbsup:

Coverage data is based on head (908dc04) compared to base (9e43f86).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head 908dc04 differs from pull request most recent head 67171ff. Consider uploading reports for the commit 67171ff to get more accurate results

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #578   +/-   ##
========================================
  Coverage    60.62%   60.62%
========================================
  Files           26       26
  Lines         2809     2809
========================================
  Hits          1703     1703
  Misses        1106     1106

Impacted Files
Coverage Δ

macrosynergy/dataquery/api.py
41.44% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add table add and remove methods

Create branch from main
issue-133-add-table-add-and-remove-methods


Retain flag per device

Is there anyway to set if the retain flag should be true/false for a particular device?
I have buttons in SmartThings, that i don't want the "press" action to be retained in the broker.
Thanks,!

I'm running into the same challenge -- button presses (events) get published with retain which causes downstream consumers (like Home Assistant) to trigger whenever they are restarted because it thinks a new event was fired.  Turning retain off globally would fix his problem but introduce sync issues with all the stateful devices.  Perhaps the configurable precision should be down to the type/property level.  For example, I have devices that expose both a switch and a button.  I'd want "smartthings/device/switch" to be published with retain and "smartthings/device/button" not to be.
Looking at the code, this would need to be implemented in the nodejs component.  I see two viable options:

Extend the configuration to allow specification of retain by device, property, or device and property.
Add logic for "button" and other event-type properties to always publish retain = false.  (Why would someone ever want a button press event to be retained anyway?)  Other portions of the code have intelligence for specific properties (switch and level) so I don't see this as a major SOC issue.

Thoughts on the approach?  I'm learning more to the second option because it would be far simpler to implement and can work on a PR if others agree. :)

Also running into this issue. Was resetting the docker container every night at 11 pm, coincidentally lights were turning on-off off-on at that time which I wasn't sure why until I realized the retain flags send the press or push along on the restart of this docker container.

Also running into this issue. Was resetting the docker container every night at 11 pm, coincidentally lights were turning on-off off-on at that time which I wasn't sure why until I realized the retain flags send the press or push along on the restart of this docker container.


Inconsistent Crash while resolving

We're seeing a crash in DIP when creating the initial view controller which through it's references winds up trying to resolve a type which results in a crash.  This type can be described as such (using made-up names to simplify):
struct Configuration {}

protocol Foo {}

open class SuperClass: Foo {
   var configsByUser: [String: Configuration] = []
}

class SubClass: SuperClass {}

We register SubClass into the dependency container using the type Foo.  When we resolve, there seems to be a crash at https://github.com/AliSoftware/Dip/blob/0193aa6bf6151f7ecd88ff26dba6c0525c3eabd6/Sources/AutoInjection.swift#L48
In this specific case it seems to be trying to deal with the property configsByUser above.  In the debugger I am able to see the following:
(lldb) po type(of: child.value)
Swift.Dictionary<Swift.String, Configuration>

It seems that the data in the Mirror is neither AutoInjectedPropertyBox nor ImplicitlyUnwrappedOptional.  Accessing child.value at all seems to crash as the debugger cannot do anything with it beyond querying the type as far as I can tell.  I saw https://bugs.swift.org/browse/SR-2282 that you filed but that doesn't seem to be the same issue.
I'm unsure if this shows a problem with how things are registered or what but I wasn't sure how to chase this further.  Any input would be greatly appreciated as this error happens very frequently in the simulator which is destroying our automated testing.   We do not think we've seen this at all on an actual device so that could be another data point.

Ah I should also note that we are building with Xcode 11.0 and this issue started during our conversion on the Beta this summer so it seems to be new to this version of the compiler.

If you don't use autoinjected properties you can disable them. See https://github.com/AliSoftware/Dip/commit/a8777c067e28f2c6d9e7876ae475a08169a66b64

@SlashDevSlashGnoll is this still relevant?

Turning off autoinjected properties avoids the problem for us yes.  Thanks for the advice.  It feels like there's still an issue in there but since we didn't need that feature we could just disable it.
Sorry for not reporting in earlier!


Release/list by tag

Added the ability to list by tags the resources. Did a small refactor because it looked like the group feature. Added README part also.

This looks good, but there's conflicts.

This looks good, but there's conflicts.

Fixed!

Thanks!


Changed #tfop signature to always return TensorHandle

(some TF ops also return resource handles and variant handles, which can be supported later).
The APIs in RawOps (and other APIs in TensorFlow stdlib) will continue to consume
and produce Tensor's, as Tensor is the user-facing class.
A #tfop can return one or a tuple of TensorHandle/[TensorHandle] elements, as
illustrated in the following example in the generated code. In this case, the
#tfop is returning a tuple of 3 elements, where the first element is a tensor
list.
@inlinable @inline(__always)
public static func batch<T: AccelerableByTensorFlow>(
  inTensors: [Tensor<T>],
  numBatchThreads: Int64,
  maxBatchSize: Int64,
  maxEnqueuedBatches: Int64 = 10,
  batchTimeoutMicros: Int64,
  allowedBatchSizes: [Int32],
  gradTimeoutMicros: Int64,
  container: String,
  sharedName: String,
  batchingQueue: String
) -> (batchedTensors: [Tensor<T>], batchIndex: Tensor<Int64>, id: Tensor<Int64>) {
  let ret: (batchedTensors: [TensorHandle<T>], batchIndex: TensorHandle<Int64>, id: TensorHandle<Int64>) = #tfop("Batch",
    inTensors,
    num_batch_threads: numBatchThreads,
    max_batch_size: maxBatchSize,
    max_enqueued_batches: maxEnqueuedBatches,
    batch_timeout_micros: batchTimeoutMicros,
    allowed_batch_sizes: allowedBatchSizes,
    grad_timeout_micros: gradTimeoutMicros,
    container: container,
    shared_name: sharedName,
    batching_queue: batchingQueue)
  return (ret.0.map(Tensor.init), Tensor(handle: ret.1), Tensor(handle: ret.2))
}

@LaurentMazare I haven't written much python code for serious projects, so I'd welcome any feedback on style, etc. Thanks!

Thank you all for the review!


chore: bump version to 0.10.0-beta.2

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

chore: bump version to 0.10.0-beta.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.004%) to 70.918%

Files with Coverage Reduction
New Missed Lines
%

kclvm/sema/src/core/symbol.rs
3
51.59%

Totals

Change from base Build<PHONE_NUMBER>7:
0.004%

Covered Lines:
51507

Relevant Lines:
72629

💛  - Coveralls


Making travis work with the framework

Hot damn, thank you!!
Before I merge, why do we need another scheme? Can we update the existing one? Having two schemes in the main project seems weird, right? Happy to accept updates to the existing one instead of creating a new one.

Last night when I looked there were no schemes and travis didn't see it either.. Is it possible one of the schemes you have is on your local machine and not shared?

Yup you're right, my .xcuserdatad stuff had it. This should be good :)