Issue with Patrol Flutter tests

Steps to reproduce
It is hard to reproduce this issue, since it doesn't happen all the time...
Actual results
I have a question regarding running tests in Flutter using Patrol framework. Sometimes when I run the test it passes and sometimes it just fails with this message in report.
Logs

Logs
EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK
The following message was thrown: Multiple exceptions (3) were detected during the running of the current test, and at least one was unexpected.

at pl.leancode.patrol.PatrolJUnitRunner.runDartTest(PatrolJUnitRunner.java:135)
at care.incision.teams.MainActivityTest.runDartTest(MainActivityTest.java:31)

Patrol version
patrol: ^3.6.1
Patrol Doctor output

Patrol Doctor output
Patrol CLI version: 2.7.0
Flutter command: flutter
  Flutter 3.19.6 • channel stable

Flutter Doctor output

Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.19.6, on Microsoft Windows [Version 10.0.22631.3447], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.9.4)
[√] Android Studio (version 2021.3)
[√] Android Studio (version 2023.2)
[√] IntelliJ IDEA Community Edition (version 2022.2)
[√] VS Code (version 1.89.0)
[√] Connected device (4 available)
[√] Network resources

• No issues found!

Hi. Please attach a logcat from failing tests run.
Steps:

clear logcat (adb logcat -c),
run logcat in another tab and redirect it's output to some file (adb logcat > logcat.txt),
run patrol test,
after the test fails stop the logcat and share the logs file.


Query sometimes returns no results from the same input

Hello!
Firstly, a big thanks for creating this library for Firestore. I've used the geofire library for the realtime database so it's great that it's been recreated for Firestore. Your work is much appreciated.
I've written some geohashed data to Firestore and I'm querying it using the geoFirestore.query() method. It mostly works but on some occasions it fails to trigger the key_entered event even though the query is currently hard-coded for testing.
Here's the code:

Am I missing something obvious with the way the geohashing works? I can't understand why it doesn't return the same data each time as the initial query doesn't change.
Thanks,
Marc

Thanks @MichaelSolati. Here's an image of the data in my database:

This only has 6 documents in the collection and I've found that it even happens with just a couple.
All of the geohashes are lowercase but not sure if there's anything I need to do in the query.

Ughh, ok, so this is really odd (and painful), as the tests should catch this. As this may be a nuisance, would you mind making a sample repo as minimal as possible with it not working? (This would seriously help)

Hey @MichaelSolati. Thanks for investigating.  Thanks.

Try this project @MichaelSolati. It should be a basic test and I've put instructions in the README. Thanks for your help.
https://github.com/MarcL/geofirestore-test

Hey @MarcL, try replacing geofirestore with npm i MichaelSolati/geofirestore. I think I pinned down the issue (THINK), and pushed up a tweak for this. But I'd like to make sure it works for you first. (I tried running the get like 50 times after the fix and had no issues)

Thanks @MichaelSolati. I've just tried the version from this repo in the test project and seems to work as expected. Thanks!

@MichaelSolati - Is Firestore a lot slower than the realtime database? I'm just doing some test queries locally using the above fix and I'm seeing an average query time of ~2000 ms. I then do a similar test with the Firebase realtime database and geofire-js and I'm getting average query times with the same query of 400 ms. The data schema is a bit different to account for the advice on denormalisation for the realtime database, but I just wondered if there was anything obvious to speed up the Firestore queries. Thanks.

So I don't think I've explicitly seen anything saying that the RTDB is faster than Firestore, but I completely think that's true. The RTDB is advertised as "low-latency", while nothing is explicitly stated about Fitestore's speed...
Looking here they don't mention anything about speed under "Reliability and performance" as well as "Scalability."
So, IMHO, you'll get speed with the RTDB, you'll get a more powerful database and queryability with Firestore.

Thanks for the info. I wanted to use Firestore as I'd not used it before, and I thought it might be quicker for my queries (tagging of geohashed locations).  I'll investigate RTDB again too. Thanks for all of your help.

Version 2.2.1 is deployed on NPM.

Looks like this problem now exists in version 3.3.1

@hindsricardo can you build a sample application with this issue persists?


v8.0.2 introduced horizontal scrollbar to <Table />

If you visit https://bvaughn.github.io/react-virtualized/#/components/Table (the official preview for the Table component). You will see it has a horizontal scrollbar for no reason. I suspect it's related to the scrollbar as the scroll value is about the width of the scrollbar.
There appears to be no way to remove this scrollbar via any props or CSS styling. This issue was not occurring in v7.x.x

Thanks for pointing this out @EvNaverniouk!

Fixed via 8.0.4!


Confusing or incorrect information

In this page, to identify what fixes went to PQU it says:
In the exported file, filter and select the Build version that is less than or equal to build number 10.0.1265.89. You should now be able to see the delta payload.
When we click on View Update, it will show all quality updates that the current environment does not have, so all the versions are higher and those updates that went in the system no longer can be seen there.
[Enter feedback here]

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

ID: 6edd9a5f-8212-173c-16fb-8868c5d4b4d9
Version Independent ID: 6edd9a5f-8212-173c-16fb-8868c5d4b4d9
Content: Proactive quality updates - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/fin-ops/get-started/quality-updates.md
Service: dynamics-365-cross-app
GitHub Login: @rashmansur
Microsoft Alias: rashmim

Bug 776107 has been logged to address this issue.

Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Showing Discord Presence

How can I show my RPC on my website?  @Phineas

You should ask this question in the Lanyard discord in the support channel. Issues on this repo aren't really for that type of support.
However that depends on your site, if it's react you can use the hook Alistair made use-lanyard
If it's vanilla javascript and html, you can use something like js-lanyard but there is plenty of options visible in the projects section of this Lanyards readme.


Custom filters for activity layers

Overview
There's a request to have more complex filters to drive what activities show up in an activity layer. This would enable users to create more focused rows that reduced clutter and kept things focused on the task at hand. For example, a row could be built by a few related subsystems where a certain parameter was met, or where a specific tag was included. This approach would allow further refinement after dragging a group of starting activities on to the filters.
Feature request

Chain together filters with dropdowns for logic selection
Chained filters can be specified if they are And / Or
Ability to select "activity type" or "span" as the target for filtering
Show filter results below for feedback on how filters are applied.
This could leverage activity groups or typescript grouping in the future.
This could also support better grouping in the timeline
Should include a method for "show all" https://github.com/NASA-AMMOS/aerie-ui/issues/973
Should also include a method for toggling visibility of child activities https://github.com/NASA-AMMOS/aerie-ui/issues/635

Background
There's a couple of related ideas we can chain together to improve the row building and filtering experience. The overall goals are to simplify how rows are built and filtered, make filters more dynamic so they don't get stale as a mission model shifts, and add the ability for people to drill down and customize them if needed. We don't want to expose a lot of that complexity up front, but it should be easy to access.
Current issues
Some of the pain points with our approach to filtering that this design direction aims to address:

We don't support custom filters, making it tricky to build meaningful rows with multi-spacecraft missions #671
Filtering is generally tedious, settings are buried in the row details, and our multi select approach doesn't scale well to thousands of activities. #592
Because filtering is limited and tedious, it's easy to get a row that is focused on information specific to a task. With large plans, this means lots of information on the timeline that isn't relevant, creating clutter and visual noise.
Row building isn't set up for exploring the mission model. #634. We have a broad list of all activity types in the mission model, but these aren't tied to the process of creating row filters. This section can only be used to drag and drop or add an activity instance to the timeline, an uncommon workflow as instances are typically placed using procedural scheduling. Exploring resources is even more limited as the only section to view what's in the mission model is from the small popover ui in resources filtering.
Activity filters are static and don't leverage logical categories like subsystem or all. After selecting individual activity types, that list doesn't stay up to date as a mission model shifts. The current workaround is to use a text search and batch add for activities, which works well if a subsystem has a name included. https://jira.jpl.nasa.gov/browse/ECGDSITD-517 #973

"There's no capability to select all the AVS activities, short of clicking on each one-at-a-time.  This is onerous but possible because all the AVS activities begin with the string "AVS".

The hierarchy and labeling of layers within row details doesn't match the system. We've made improvements to the timeline rendering so that activities and resources show up in a logical way: all activities pack or group together and don't overdraw. And there's a default stacking that supports most use cases: lines on top, activities in the middle, and x range charts on the bottom. The concept of layers may not even need to be surfaced when building a row.

Proposed solutions
1) New browse panel: a better way to browse activities and resources (heavily inspired by the workflow in raven)

Dedicated space to browse and filter activities and resources
Filters that support subsystem tags
Quick actions to add results to a new or existing row. Preserve current action for adding an instance to timeline
Multi select to add single items from filtered results
Future considerations

similar workflow for external events
More logical grouping or hierarchy in list

2) Improved filters in row details

Filters from browse panel are carried over here
User can filter based on text includes or subsystem tag which shows a dynamic list of results that stay up to date with the mission model
List the activity types that match the filters for immediate feedback
For each resulting activity type, show filters based on the type's parameters. For each type, these filters can be chained together to build queries like Param: Spacecraft = A OR Param: Spacecraft = B.
Stretch / maybe not needed: When expert filters are displayed, show a list of the resulting instances for quick feedback on what the filters are doing. This could be more visible
Future considerations

save filters so they can be re-used
parameter filters on a group

3) Clear up hierarchy in row details

Two sections for activities and one for resources. (and in the future events)
Resources are changed between line and x-range in their settings

Open questions + design

Settings panel for activities and resources. How do we integrate the current filters?
Empty state for filters from row details / adding a new "layer" from here.
Details around boolean logic and populating parameter list
Dealing with enum / hierarchy parameters (not sure the name for this)

Prototype:
https://www.figma.com/proto/gsWLcy9UuqSQVqbyHf4Lw6/AERIE-Filtering%2C-Activity-UX%2C-Timeline-Density?page-id=885%3A65354&node-id=1007-150579&viewport=35%2C-7458%2C0.55&t=Ia1AyYjoyOCSVWUg-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=1007%3A64472&show-proto-sidebar=1
Design files:
https://www.figma.com/board/PE4EJhU1GM7eEeJOyfdN3I/Aerie-Filters-and-Row-Building?node-id=0-1&t=9YbmVWV1sPhJOqlj-1
https://www.figma.com/design/gsWLcy9UuqSQVqbyHf4Lw6/AERIE-Filtering%2C-Activity-UX%2C-Timeline-Density?node-id=885-65354&t=5O7Q5GIEuaSAPokb-1

Notes

How do we set the subsystem tags up? How do we set a mission model up for doing this?
Should we add tagging UI as a workaround to mission models? Probably not first pass.

Thanks for the great summary @lklyne - I've copied the main requirements from above into a new ticket for implementation: #1391
Feel free to keep this one open for more notes/design ideas, or close when you feel it's design complete.


0 byte files when uploading files using SAF

I'm migrating my Android app off the deprecated Drive Android API as suggested here https://developers.google.com/drive/android/deprecation. I've opted to use the Storage Access Framework to meet my requirement, however I'm seeing odd behaviour from Drive's (Android app) content provider. When saving files, I'm constantly seeing files saved with 0 bytes (quite often works the first time, then intermittently afterwards - same content written). Remote files are never fetched, resulting in...
java.io.FileNotFoundException: StorageFileLoadException[io_error]
    at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:144)
    at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:698)
    at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1458)
    at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1295)
    at android.content.ContentResolver.openInputStream(ContentResolver.java:1015)

Please help!

Thanks for inquiring. Unfortunately this issue tracker is only for reporting issues with the particular samples. For general help, I suggest StackOverflow or one of the other support resources at https://developer.android.com/support.

This sample shows the same exact behavior so I don't know how it could be off topic...


Add code formatting of xml files

@pmanko thanks for filling,,, kindly could you add a description to this issue

@pmanko @bashir2 @kimaina kindly review https://github.com/GoogleCloudPlatform/openmrs-fhir-analytics/pull/87


Change result type of validator from () to Bool

This is more intuitive, and most validators are already of the form if condition then () else error so we can remove a bit of code in a few places.

How are we going to check what the result is? The simplest thing I can think of is to apply \b -> if b then error else () to the whole thing and check if it's error.

Working on it.


fix: images

:tada: This PR is included in version 0.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Verify that pyUNO path is set correctly with alpine 3.18 and LibreOffice > <IP_ADDRESS> and then remove workaround

The current Dockerfile contains a workaround that was expressed in this upstream bug.

The fix is available in alpine from libreoffice <IP_ADDRESS>.
Alpine 3.17.x has libreoffice <IP_ADDRESS>-r0 as of now. edge has 7.5. Will have to wait for 3.18 release.

Relates: #6

Alpine 3.18 has been released: https://www.alpinelinux.org/posts/Alpine-3.18.0-released.html


Add workflow to link startrek ticket

Add workflow to link with startrek issue ticket. The issue name is parsed from a branch name.
Example of an appropriate branch name MDB-24383_link_pull_request_with_startrek

Let's add the changes from https://github.com/yandex/ch-backup/pull/14


Open the console on preview

Creators that use the Creator Hub to run a preview don't see any debug messages.
We need to add the option to open a read-only console window to output the error messages that today get printed out to the console.
See the designs here:
https://www.figma.com/design/3NfkzCCumOmxjgMGSpSZao/🧰-Creator-Hub-|-Debug-Terminal-|-Cycle-9%2B?node-id=17433-4431&node-type=section&t=nhvQG98rTlvThhU9-0
The default configuration should be with the console off.
If the console is turned on, the Creator Hub should remember this configuration and implement the new behavior when running preview all projects.
The designs also include a setting for toggling the debug panel, this I assume is a minor task, as we can add or remove a param for that when calling the command to open the explorer
In the future, we might expand this list of options

Duplicate


Reflect outlet information change in UI

Solve #84

Pull Request Test Coverage Report for Build 212

15 of 15 (100.0%) changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.81%

Totals

Change from base Build 209:
0.0%

Covered Lines:
2246

Relevant Lines:
2420

💛  - Coveralls


Update Documentation - Optional properties

The code was already in place.
Just informing users on how to play with it.

Found bug in ruler documentation as well ... removing this pull request and submiting another with all changes


Firefox 77 and 78 fails to connect

Firefox 76 seems to work correctly, 77 and 78 fails silently.

cannot reproduce anymore...


[BUG] Russell's video tutorial for BP mods (as linked in UE4SS docs) doesn't work

Branch or Release
gddee25c

Game and Engine Version
PalWorld UE 5.1
Describe the bug
When Trying to load Blueprint Mods created with the Youtube Tutorial mentioned in the Docs,
always throws the following Error when it seemingly recognizes the Mod:
[13:11:37] Error: [Lua::call_function] lua_pcall returned LUA_ERRRUN => ...\Pal\Binaries\Win64\Mods\BPModLoaderMod\scripts\main.lua:202: ModClass is not valid
To Reproduce
Steps to reproduce the behavior:

Put .pak file into the  LogicMods Directory
Launch Game
See error in log

Expected behavior
The Mod loads as expected
Screenshots and UE4SS Log

Desktop (please complete the following information):

OS: Win10

Additional context
none

Just tried version 3.0.0 and the BP mods seem to work as expected again.
I'll close this issue for now.


Channel without claims shows "fetching content...", console error

The Issue
Going to a channel without any claims (lbry://@blankchanneltest) makes it seem like the app is trying to pull something back but can't.  The console produces an error:
Uncaught (in promise) TypeError: claims.forEach is not a function
    at reducers.(anonymous function) (webpack:///./js/reducers/claims.js?:149:12)
    at reducer (webpack:///./js/reducers/claims.js?:224:23)
    at combination (webpack:///./~/redux/es/combineReducers.js?:124:29)
    at batchingReducer (webpack:///./js/store.js?:108:16)
    at eval (webpack:///./~/redux-persist/es/autoRehydrate.js?:33:16)
    at dispatch (webpack:///./~/redux/es/createStore.js?:170:22)
    at eval (webpack:///./~/redux-logger/dist/redux-logger.js?:1:7760)
    at eval (webpack:///./js/store.js?:96:16)
    at eval (webpack:///./~/redux-thunk/lib/index.js?:14:16)

Steps to reproduce

Open lbry://@blankchanneltest in LBRY
App shows "fetching content..."
Console will show error

Expected behaviour
App should say that no content exists yet
Actual behaviour
App looks like its fetching, but console errors
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

@tzarebczan is this fixed on ->  0.16.1rc1 ?

if not I'll send a PR ^

It is not fixed.
Also, FYI, 0.16.1rc1 is a "draft", which means it is not public. You can only see it since you're a collaborator on this repo.

so myPR is not working ?

@btzr-io I just tried on rc1, had same result as reported on this issue.

@tzarebczan yeah this is fixed in  fix-empty-channels (#638) ^

Oops! My previous message was quite unclear. I meant it was not fixed in the RC.
AFAIK, your fix works. @tzarebczan you can test this in master if you like, or just wait for 0.17 rc.


NWChem interface

NWChem interface from QCDB has been moved and partially adapted (substantially working).

Cool, thanks for the PR!


github accounts with 2FA fail

@TimothyJones greetings! first off, thanks for the hard work on open sourcing this repo. I'm interested in providing support after getting a working example up and running in quick time thanks to this repo (i'll connect with a proposal i'm building in the near future).
in the meantime...one issue i'm running into is that github users with two-factor authentication enabled are unable to sign in. this is the result after entering (correct) credentials into the cognito-initiated github auth flow:

i've verified with a different github user account with two-factor disabled, and things work as expected. i already have our cognito user pool working with google, but this is my first attempt at an openid cognito provider.
have you run into this issue before? i've been digging most of the day, however have not had much luck. thanks in advance for any help you can offer!

I believe it's a bug with either Cognito or GitHub, but I wasn't able to determine which. It's described in Issue #24.
It's possible to work around it with a bit of extra infrastructure (described in #24), but it's hard to provide a general recommendation that works for all loads, and since adding a Dynamo DB table is a fair bit of extra work (and potentially operational costs that not everyone will need), I haven't been able to merge it in to this repo yet.

I'm going to close this in favour of keeping discussion over at #24 - please feel free to add your thoughts there.

thanks for the quick response @TimothyJones - i'll take a look at the issue and fork in more detail tomorrow. i'd like to contribute back to this repo as i think it's a very valuable resource. appreciate your time.


The lack of the experimental environment introduction in the paper

Thank you very much for such a detailed introduction to data curation and providing open-source code.
However, in the paper, I couldn't find information about the experimental testing environment, specifically what type and how many CPUs and GPUs were used to process the DCLM-baseline dataset?

We do not use GPUs for processing the dataset. We spin up ray clusters of CPUs from AWS and use it to do HTML extraction, RW v2 processing, and fast-text scoring. The specific instance matters less because these steps are easily parallelizable with our provided python code, but these steps vary in terms of computational requirements. For deduplication, we do this in a sharded manner to reduce computational requirements and use rust code.

@afang-story Could you provide the data how much CPU resources your are using?

I am sorry but we do not have the specific number of cpu hours readily available.

Thanks anyway!


Model.eval()?

Given that we are using Batch Normalization layers here, shouldn't we be calling model.eval() before getting accuracy numbers on the test set?

Just kidding, I just noticed that momentum = 1.


added documentation header to comms.ts

Added some documentation as lined in my last pull request #198

Ok will do.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Jazcash @.>
Sent: Wednesday, April 12, 2023 5:08:26 AM
To: beyond-all-reason/bar-lobby @.>
Cc: knoxy5467 @.>; Author @.>
Subject: Re: [beyond-all-reason/bar-lobby] added documentation header to comms.ts (PR #199)
@Jazcash requested changes on this pull request.

In src/renderer/api/comms.tshttps://github.com/beyond-all-reason/bar-lobby/pull/199#discussion_r1163845566:

This documentation comment created on 12APR2023 by @knoxy5467

last updated on 12APR2023 by @knoxy5467

@class CommsAPI

@classdesc Comms API

Can you remove this fluff? I'm keen on adding more overview documentation to classes, but I'd like to keep it to only the bare necessitities. If we ever get into auto-generating frontend documentation based on the code comments, a lot should be able to be inferred from Typescript.
Looking as JSDoc, I think this should probably be:
@fileoverview This class is a extension of the TachyonClient class. It is used to communicate with the server. All communication with the server should be done through this class, includeing matchmaking, chat, direct messages, and other lobby related functions.
—
Reply to this email directly, view it on GitHubhttps://github.com/beyond-all-reason/bar-lobby/pull/199#pullrequestreview-1380869585, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM6WLMB3TY3VSOFJHUK23TXAZWIVANCNFSM6AAAAAAW3GLBME.
You are receiving this because you authored the thread.Message ID: @.***>

Done removed the fluff


⚠ Fortnite has degraded performance

In b0fc740, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1651 ms

Resolved: Fortnite performance has improved in a0ced47.


Uncaught TypeError: onerror is not a function   at FileReader. (offline-tpk-src.js:2427)

Expected behavior

Which offline library are you using (e.g. OfflineEditBasic.js, OfflineTilesAdvanced, etc)?
offline-tpk-src.js
What's the offline library version number?
esri-offline-maps - v3.7.0 - 2016-11-01
Describe what you expected or wanted to happen.
"http://esri.github.io/offline-editor-js/samples/tpk-layer.html",   browse a tpk file about 11G
What you are trying to achieve?
browse a tpk file about 11G

Actual behavior

Describe what occurs in your code.
it threw a error:"Uncaught TypeError: onerror is not a function   at FileReader. (offline-tpk-src.js:2427)"
Specifically, what seems to work differently than you intended?
Provide any error messages you see in the console.
Uncaught TypeError: onerror is not a function   at FileReader. (offline-tpk-src.js:2427)

Steps to reproduce the behavior
We can only help you if we're able to reproduce the behavior you describe above. Please provide:

What operating system, browser and browser version are you using?
win7,chrome 63.0.3239.108
Steps to reproduce the behavior
A link to an app where we can carry out those steps (either our example pages, your publicly facing app, JSFiddle, JSBin, etc)
Relevant code snippet(s) (only if not easily obtained from the above link)

Closing. Feel free to reopen if needed.


MultipartUtils.parseParameterField method is not a safe method, throws StringOutOfBoundException or ArrayOutOfBoundException

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
The ApiListenerServlet tries to determine if a multipart part is of binary type by checking the filename attribute of the related Content-Disposition header.
When the related Content-Disposition header is incorrectly specified, i.e: Content-Disposition: attachment; filename= or Content-Disposition: attachment; filename=", the MultipartUtils.parseParameterField throws different type of exceptions, resulting in 500 internal server error responses..

Besides that, it also seems to handle filenames which contain the = or ; characters incorrectly:

I believe that the framework should validate the attribute before trying to parse it. If it's invalid, it should reply with a 400 Bad Request and a clear message which part of the request is invalid.
Reporter
Laurens

Appearently when a filename starts with = character, the error related to the stacktrace can be reproduced

Eens, het 'parsen' of lezen van multipart berichten kan sowieso wel een likje krijgen...

Fix is in 7.8.3-hotfix4, and will be in 7.9-RC1-hotfix5.


Proposal: Kaia Foundry Template update

Description

A Foundry boilerplate to deploy smart contracts on Kaia with more integration with ecosystem projects and updated docs
Hopefully I can get CREATE3 integrated as well

Bounty track

Developer tooling

This issue is an update of: #18

Alright. Approve to proceed.

Reverting back with the update:

Major revamp for docs and comments. Now every piece of code has comments. Added docs.
Added CREATE3 deployment guide
Added test cases and Kaia tokens

https://github.com/blockcmd/kaia-foundry-template

Approved for 1500 KLAY payout. Clean up a few typos, add a few more test cases and useful make commands for me.

Closing this issue. Open new issue if you want to add an update.


Update _index.md

Description

Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment:
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

Adding users from the commad line.
The fastest way to create a user is by executing the following command:
    ./ocis accounts add --username johndoe --mail<EMAIL_ADDRESS>--password p123p123 --description  "John Doe's account" --displayname "John Doe" --enabled
For detailed information just type:
      ./ocis accounts add --help
     NAME:
        ocis accounts add - Create a new account

      USAGE:
        ocis accounts add [command options] [arguments...]

      OPTIONS:
        --grpc-namespace value                Set the base namespace for the grpc namespace (default: "com.owncloud.api") [$ACCOUNTS_GRPC_NAMESPACE]
        --name value                          service name (default: "accounts") [$ACCOUNTS_NAME]
        --enabled                             Enable the account (default: false)
        --displayname value                   Set the displayname for the account
        --username value                      Username will be written to preferred-name and on_premises_sam_account_name
        --preferred-name value                Set the preferred-name for the account
        --on-premises-sam-account-name value  Set the on-premises-sam-account-name
        --uidnumber value                     Set the uidnumber for the account (default: 0)
        --gidnumber value                     Set the gidnumber for the account (default: 0)
        --mail value                          Set the mail for the account
        --description value                   Set the description for the account
        --password value                      Set the password for the account
        --password-policies value             Possible policies: DisableStrongPassword, DisablePasswordExpiration
        --force-password-change               Force password change on next sign-in (default: false)
        --force-password-change-mfa           Force password change on next sign-in with mfa (default: false)
        --help                                Show the help (default: false)

How to delete users.
First of all, get the user id, to know it run the following command.
    ./ocis accounts list | grep "John"
    | dd8bc84c-ff57-4c72-9db7-e6ff435acfd8 | John Doe |<EMAIL_ADDRESS>| true |

The ID is "dd8bc84c-ff57-4c72-9db7-e6ff435acfd8", so to proced to delete it just run the command.
    ./ocis accounts rm dd8bc84c-ff57-4c72-9db7-e6ff435acfd8

Thanks for your PR, @erwinpalma
If you work on the PR again, could you please also fix the typo "proced" -> "proceed" in the How-to-delete paragraph? Thanks!

we are planning to move user management out of ocis, with that step docs for it will become outdated, which is why I am closing this. Take a look at https://github.com/libregraph/idm which we plan to integrate instead of building our own identity management.


geth run guide

Initialize the node
In the node directory, initialize the first node:
geth --datadir data init ../network/genesis.json
must be
../network/testnet/genesis.json

@maxzonder good catch - thank you! We will update in the next release and consolidate the genesis file into one location. You can view this on the new release branch

This has been included in this branch: https://github.com/masa-finance/masa-node-v1.0/tree/v1.02


watch for added and deleted files

Subtasks:

#34 ...would automatically copy new images to the dist folder.
#17  ...would include new script files automatically
#10 Automatically remove files from watcher when they are deleted

I "merged" the issues in this one because the global handling will be the same.
I was able to get the watch tasks listening for add/remove events, but only with a big performance losses. My script task took 6 seconds when using browserSync for the watches, it normally takes about 3 seconds.
The code to make it work like this:
    var watchOptions = {
      //persistent: true,

      //ignored: '*.txt',
      ignoreInitial: true,
      //followSymlinks: true,
      //cwd: '.',

      usePolling: true
      //alwaysStat: false,
      //depth: undefined,
      //interval: 100,

      //ignorePermissionErrors: false,
      //atomic: true
    };

    browserSync.watch(config.app.js, watchOptions, function (event, file) {
      gulp.start('scripts')
    });


Avoid creating many atomtypes for the same molecules when convert to GROMACS top

Hi,
I created a system of N molecules of the same molecule, then converted the system to gromacs .top file, I found that the .top file contains as N times the atomtypes which is redundant as we only need atomtypes for 1 molecule. Also, in the [ molecules ] section, each molecule type is listed as a separate line when I expect to have one molecule type with N molecules. Below is the code I tried.
`from openff.toolkit import *
from openff.interchange import *
ethane = Molecule.from_smiles("CC")
ff = ForceField("openff-2.0.0.offxml")
topology = Topology.from_molecules(10 * [ethane])
out = ff.create_interchange(topology)
out.to_top('foo.top')`

The [ atomtypes ] section:

And the [ molecules ] section:

I am wondering if there would be a quick fix for this behavior.
Thanks,

Thanks for the reproduction - I'm aware of this issue and, believe it or not, it's intentional. This one is tricky and a little more complicated than it initially seems. I understand that printing out each molecule separately makes the files more difficult to inspect, but it's the easiest way to avoid a number of corner cases that would produce incorrect - not simply verbose - files. I'll try to articulate why this looks unappealing and justify why it's actually better than the alternatives.
Jeff's correct to bring in atom type explosion as an issue and it explains why virtually all GROMACS/Amber files of SMIRNOFF systems look comically verbose compared to those prepared with conventional Amber-like force fields. There are a few ways the atom types could be compressed, but file size is extremely cheap and a chance of mis-reporting parameters, no matter how small, is prohibitively expensive, so we have not prioritized this.
A separate issue is how similar molecules are collated into the [ molecules ] section. If you're anything like me, you saw those lines of repeated x0 1 and thought "surely these can be condensed down to 1!" as I did. In your example it certainly looks like they could be. However, defining molecular identity in a way that handles the problem broadly is not straightforward.

It's non-negotiable that condensing duplicates in [ molecules ] must only ever condense two molecules that would produce the same energy given the same coordinates, non-bonded settings, etc.
Molecule names are borderline arbitrary and not usually provided, and the same goes for residue information, so we can't use that.
There are some cases in which isomorphic molecules might be assigned different parameters, so the built-in solutions offered by the Molecule class probably won't be enough.
I could imagine a hashing function that looks into every character of what's written out in a moleculetype section and is used for deciding which are equivalent enough to be considered copies of each other. But that's non-trivial to implement and error-prone (any modifications to object models may change the behavior of this function and accidentally introduce a hash collision) so I decided not to implement it the last time I thought about it.

As far as I remember, GROMACS is the only engine that groups molecules up in this specific way, which is another reason why I haven't optimized it. OpenMM doesn't even keep track of molecules in its System object, LAMMPS only includes an integer molecule ID in each row of the Atoms section, and Amber barely has the concept of molecules at all.
With this context in mind, I hope you understand why it looks a little funny. In the future this may look nicer, but Interchange is not (and may never be) heavily optimized for file size or manual user modification. (If for some reason you want to modify parameters, I imagine doing so via the API instead of by hand or with scripts later.) Are you running into issues with file size?

Thank you for clarification. I got your point now. I had thought initially that it would create N separate topologies for each identical molecule present in the system, which could have been a problem. However, upon further examination, I realize that even though it creates atomtypes for all the atoms in the system, it only creates 3 or 4 moleculetypes that are used to construct the system. Moreover, the atomtypes in each molecule under [ atoms ] section are correctly linked to the atomtypes in the global [ atomtypes ] section. As a result, the redundant atomtypes will not be used and that is fine. And I agreed if we can do a bit of housekeeping to make the final top file looks cleaner that could be perfect. BTW, many thanks for the good work in creating such useful tools.

Thanks!
I will also try to document this in a better way.

Hi Matt,
I got another issue related to this. When I ran a simulation with GROMACS using the converted .gro and .top files, the system just crashed with the following error (on both my computer and a supercomputer):
Memory allocation failed:
std::bad_array_new_length

I removed the redundant atomtypes (those are not found under the [ atoms ] section in [ moleculetype ]), and the simulation ran just fine. I suspect that the issue is caused by the large number of atom types listed under [atomtypes], which may be causing a high memory load. I wonder if it could be an easy fix by keeping only atomtypes that present under [ moleculetype ] sections instead of listing all the atomtypes based on the number of atoms in the system.

I agree with your assessment of the problem and that sounds like a reasonable solution to try. Unfortunately I'm in the middle a huge refactor of that code (#635) so fixing this behavior based on the current state might not make it into a release just based on logistics. Is it possible that manually modifying these files can hold you over for a few weeks? (I'm also assuming that it produces the same results.) After the 0.3.0 release, the next priority is improving GROMACS and then Amber parsers, which should actually come with improvements to those exporters.
Additionally, are you able to share more details of your system? Either general terms (number of atoms, etc.) or specific scripts/files with which I can run tests myself. They can be less interesting (i.e. swapping out another ligand/protein for the ones you're actually studying) since I'm just after performance evaluations.

Hi Matt,
I attached here the system of 10000 ethanol molecules using openff-2.0.0.offxml force field. I ran the following command to generate a .tpr file and got similar error as above:
gmx grompp -f SMILES_CCO_10000_using_Interchange.mdp -c SMILES_CCO_10000_using_Interchange.gro -p SMILES_CCO_10000_using_Interchange.top -o SMILES_CCO_10000_using_Interchange.tpr -maxwarn 2
10000_CCO.zip

Thanks!


Change default merge strategy to squash

In order to have more linear history and cleaner ways to revert and see what changed we could change the default merge strategy to squash.

Changed the Pull Request merge settings to be:

I chose to add PR title and commits to the merge message.
Let me know if this looks good 👍

After merging the latest PR, we have the first example of the Squash merge. Looks good! 🎉

Awesome!


Add functionality to correctly resolve AWS:NoValue when using Amplify mock

Is your feature request related to a problem? Please describe.
I see that a lot of people have problems with environment variables for lambda functions when using amplify mock api.
Since mock doesn't support using for example resolve:ssm it translates it into the to the litteral value which works incorrectly when working locally. I tried using the AWS:NoValue instead to remove all env variables from the cloudformation template when using mock but that also translates in to en env variable with the value "AWS::NoValue"
Describe the solution you'd like
I would like mock to be able to handle the pseudo parameter AWS:NoValue to correctly remove a property instead of translating it to a string value. This would enable me to declare my environment variables locally which is something I use when developing other applications and lambda functions.
Describe alternatives you've considered
My current solution is to read what ENV is running and use that to select "ENV_VAR_LOCAL" instead of "ENV_VAR" for all variables that are required to run the function locally. Solutions proposed in other issues either involve a separate env file or hardcoding values during development and reverting before pushing. Neither of those solutions work for me since they involve risking to committing sensitive information when pushing to GIT.
Additional context
AWS - Pseudo parameter reference

@cbude thanks for raising it, I marked it as an enhancement

Hi all, I'd like to take this issue up :slightly_smiling_face:


chore: ADDON-57381 improve error message in the frontend

https://splunk.atlassian.net/browse/ADDON-57381
improving error messages visible to user:
before:

after:

before:

after:

before:

after:

before:

after:

I checked with [addonfactory-ucc-library v6.1.0-beta.1](https://github.com/splunk/addonfactory-ucc-library/releases/tag/v6.1.0-beta.1]
I logged in as a regular user and tried to open UCC Example.
What I got from BE:
Unexpected error "<class 'splunktaucclib.rest_handler.error.RestError'>" from python handler: "REST Error [403]: Forbidden -- This operation is forbidden.". See splunkd.log/python.log for more details.

how it is rendered:

So, it is working as expected


CASImpl with Default TicketId Generator

This pull addresses issue https://github.com/Jasig/cas/issues/509

I'm not sure to understand the link with #834.

What's the use case you try to address here?

I corrected the referenced issue in the description. That should help with the use case and functionality intended here.

So, are we all in agreement as far as intention and objective of this pull goes? any objections and/or other comments?

I'm not very enthusiastic on this, neither feels @battags I guess.
@mmoayyed : do have a real use case in mind (from a Unicon's client for example)?

Sure. Most often we run into this when dealing with specialized requirements for a client app that wishes to pass param1 and param2 to the /cas/login endpoint. Another example is the cas-mfa module we work on where apps can opt into MFA by providing a specialized authentication method to /cas/login and /cas/serviceValidate. All such scenarios typically require a new extension of Service via a new Argument Extractor. However, none of such scenarios require a specialized ticket id generator for the new service type. We simply just use the default.
In other words, for example:
public class SomeNewService extends SimpleWebApplicationService...
Because ticket id generators are defined by exact class names for services, this forces me to do the following mapping:
SomeNewService -> DefaultTicketIdGenerator

My argument is that this last step is unnecessary. There should be a default fallback.

OK. +1

Merging by next Monday...Please speak up if you see an issue.

"Sure. Most often we run into this when dealing with specialized requirements for a client app that wishes to pass param1 and param2 to the /cas/login endpoint. Another example is the cas-mfa module we work on where apps can opt into MFA by providing a specialized authentication method to /cas/login and /cas/serviceValidate. All such scenarios typically require a new extension of Service via a new Argument Extractor."
This sounds like this solution just merely circumvents the problem/fixes a symptom.  And if we introduce it, then we have to keep it.
How does passing "param1" and "param2" to the /cas/login endpoint affect service generation?  What are they doing with this parameter such that its tied to the service?  And if this is that common, why don't we solve that problem (such that new services don't need to be created).
If there's no other option then this change is fine, but I want to make sure we're not introducing short-term solutions/workarounds that are trouble to get rid of (since at this point, it would basically become public functionality).

How does passing "param1" and "param2" to the /cas/login endpoint affect service generation?
Parameters in various cases either define what the service should do additionally. Layers below attempt to cast to a new service type, read out the values of these parameters and operate. There is not one pre-defined behavior obviously. Every use case and deployment is different.

What are they doing with this parameter such that its tied to the service? And if this is that common, why don't we solve that problem (such that new services don't need to be created).

Unfortunately, we cannot solve that problem universally, I don't think. Each deployment could come with  N number of custom parameters to endpoints, that would indicate either a new service type to be created or additional behavior that would be stuffed into the existing service (which would be a new service type anyway) Examples could be, additional custom processing for notifications, prompts, alternate flows, authn methods, legacy reasons, etc. These are just examples, not a common use case. The commonality is that a new service type is required one way or another. What it does and why is different for every case.
This wouldnt be a public API exactly, because the default fallback generator is a private field stuffed into CASImpl as of latest commits of this pull. It will not affect the API and can later be removed and reworked.

Its not public API but it is public behavior (for that implementation of the CentralAuthenticationService API).  That said, if we're not tracking a better solution to this scenario, we should for the long term.
So +1 for the short term solution (because I don't think this is a bad public behavior) but if we haven't we should track for a better solution to needing to create Service classes for each of these scenarios.

Cool. One other possible solution would be to allow the extractor to grab all other non-standard parameters, and stuff them into same WebApplicationServiceImpl as Map or something. That would take care of the issue, and will remove the need for further casting down and creating a new service.
At the same time, API-wise one is always allowed to create a service for super special cases for who knows why! API can -> API will :) fallback seems in order nonetheless.
Another possible solution would be to have each service declare a "service.getTicketIdGenerator()" with a default created at a parent inherited by all others and overridden later.


Adding "end" event when recorder stops

Per the spec https://developer.mozilla.org/en-US/docs/Web/API/MediaRecorder

I haven't tested this (literally wrote it in the GitHub Web UI) but it should work per the spec.

Maybe hold off on this, I just added this locally in an app I'm building and there's a write() happening after "end" is emitted.
Looks like the spec was not clear enough about the data-available stuff.


Camera is not really switched off after triggering arSystem.pause()

Calling arSystem.pause(false) switches off the camera feed in the a-frame, but the camera remains active. At least on iOS, the status-light remains switched on. For user-security reasons it would be good if it could be switched off completely during pause, or at least optionally. Especially as the camera is also a drain on energy consumption.

@HeimMatthias Yes, the arSystem.pause(false) function translate to video.pause(), which keeps the video so the light indicator will still be on.
 There is still a bit of extra overhead when restart, but I think should be much faster than the first time.

Thanks, I'll try that.


Can`t get any result from query.

Hello ! I`m experiencing some problems with that code :
<?php
require_once "../vendor/autoload.php";
$user = '***********';
$pass = '***********';

$loop = \React\EventLoop\Factory::create();
$factory = new \React\MySQL\Factory($loop);

$connection = $factory->createLazyConnection(
    rawurlencode($user) . ':' . rawurlencode($pass) . '@localhost:3306/admin_default'
);
$timer = $loop->addPeriodicTimer(0.1, function () use($connection){
$query = "SELECT * FROM settings";
$connection->query($query)->then(function (QueryResult $command) {
    echo "query";
    if (isset($command->resultRows)) {
        // this is a response to a SELECT etc. with some rows (0+)
        print_r($command->resultFields);
        print_r($command->resultRows);
        echo count($command->resultRows) . ' row(s) in set' . PHP_EOL;
    } else {
        // this is an OK message in response to an UPDATE etc.
        if ($command->insertId !== 0) {
            var_dump('last insert ID', $command->insertId);
        }
        echo 'Query OK, ' . $command->affectedRows . ' row(s) affected' . PHP_EOL;
    }
}, function (Exception $error) {
    // the query was not executed successfully
    echo 'Error: ' . $error->getMessage() . PHP_EOL;
});
});
    echo "Allive";
$loop->run();
?>

I just can't get any result from this query. Also I found that the request is being executed. What I'm doing wrong ?

Hi @Nereg, good question!
It looks you're missing some imports for QueryResult. You have to import React\MySQL\QueryResult.
Because this import is missing, your code will yield a TypeError that will cause the resulting promise to be rejected. You should be able to see this problem by appending another ->then(null, 'printf') after the first then(). I understand this default behavior is frustrating, that's why we're working on https://github.com/reactphp/promise/issues/87 to improve default error reporting.
I hope this helps :+1:

Yes that worked for me ! Thank you very much for your help !


UITOOL-810/bump to react 18

Proposed Changes
UITOOL-810 part 4
Actually bumping React to version 18 😎
Also, bumping RTL and friends to latest + fixing/removing/skipping uts
I did not bother too much in fixing them since the lib is deprecated 🙃
My next step is to actually REMOVE enzyme and all the uts using it

Potential Breaking Changes
React 18 is needed as peerDependecies
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[X] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

There seem to be a lot of stuff in this PR, is it possible that some of these changes are already on master? If it is the case it would be worth merging master in next first to clear the diff up

https://github.com/coveo/plasma/pull/2849 👀


Client steering forced diversity

What does this PR (Pull Request) do?

Add a Traffic Router profile parameter that enables the Client Steering Forced Diversity feature. With this feature enabled, Traffic Router will modify its default consistent-hashing behavior w.r.t. CLIENT_STEERING in order to force a more diverse result (one that includes more unique edge caches). This is beneficial for clients to have a better chance at recovery in case of edge cache failures, because they are more likely to retry a different edge cache. With the default behavior, a client can sometimes receive a result with the same edge multiple times, causing a client to potentially retry a failed node multiple times.

[x] This PR fixes #REPLACE_ME OR is not related to any Issue

Which Traffic Control components are affected by this PR?

Documentation
Traffic Router

What is the best way to verify this PR?

Run the Traffic Router tests: mvn clean verify -Djava.library.path=/usr/local/opt/tomcat-native/lib # replace path with your system's path to tc-native
Manually: create a parameter called client.steering.forced.diversity with file = CRConfig.json and value = "false", link it it your Traffic Router profile, and snapshot. Make requests to a CLIENT_STEERING delivery service and observe the default (non-diverse) responses. Now, set the value to "true", snapshot, and make the same requests. Observe that the responses contain a more diverse set of edges for all requests.

If this is a bug fix, what versions of Traffic Ops are affected?

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3661/
Test FAILed.

nice work! any reason why this doesn't just override the default behavior. In other words, why does it have to be enabled via a parameter?

Thanks! I was mostly for just changing the behavior without requiring a new parameter, but if we don't like the behavior for some reason, this allows us to turn the feature off without having to downgrade. If in the future we think the new behavior should be standard, I guess we can bring it up on the mailing list to remove the parameter and just go forward with the new behavior.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3677/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3696/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3706/
Test FAILed.

I was trying to test this in CiaB and it appears that the both the CZF and deep CZF json file will need to be updated for the integration test to work properly (at least for the correct code path(s) to be tested).  Both the CZF and dCZF json files in CiaB are completely invalid, so all results are based on the maxmind dataset.  Given that CiaB contains almost zero cache group data , it is a lot of work to test this PR in CiaB without writing a script to add a ton of data to TO.
For local testing (outside of CiaB), I haven't tested the latest commits from yesterday, but it does seem necessary to update the deep CZF json file to make sure all code paths are tested with respect to the changes of this PR.  In my testing, it seems just the CZF is being hit and not the dCZF which suggests that the data in the integration test dczmap.json file may not be valid.
For example the IPs in $src/trafficcontrol/traffic_router/core/src/test/resources/dczmap.json seem to be completely ignored by the traffic router integration test and the fail back is to only return a CZF result (which then gets filtered by the diversity code).
{
	"deepCoverageZones":
	{
		"cache-group-01":
		{
			"network6":
			[
				"1234:5678::/64",
				"1234:5679::/64"
			],
			"network":
			[
				"<IP_ADDRESS>/24",
				"<IP_ADDRESS>/24"
			],
			"caches":
			[
				"host1",
				"host2",
				"host3",
				"host4"
			]
		}
	}
}

The only way to test this in CiaB is add a ton of cache groups and associated data with a script and also populate the deep CZF with randomly allocated IP/subnets for each edge cache once they have been created via this same script.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3731/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3815/
Test PASSed.


User Settings causes file can not load！

VSCode Version: Code - Insiders 1.9.0-insider (0347c19753f279a0c56ab2c8833de844f3be0e5d, 2017-01-04T07:09:56.180Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

githistory
donjayamanne
0.1.4

output-colorizer
IBM
0.0.9

cpptools
ms-vscode
0.9.3

vscode-icons
robertohuertasm
4.3.0

Steps to Reproduce:

open a file
open User Settings  and switch to opened file

Duplicate of #18055


GO: 83. Remove Duplicates from Sorted List

File(s) Modified: 83-Remove-Duplicates-from-Sorted-List.go.
Language(s) Used: Go
Submission URL: _https://leetcode.com/submissions/detail/769624024/_

Thanks, @MaratKhakim!


Support for graph databases.

Are there plans to support graph databases like neo4j.

With the substantial backlog right now it's just not realistic. SQL will be the focus for now with better separation between the JS models and the layer that maps to the database.

While direct support won't come right away, there will be a significant focus on making a clearly defined relation and relation loading / pairing specification that will be decoupled from the model. Ideally long term Bookshelf will be more of a generic data management library which happens to support SQL without incurring any of the tradeoffs typically found in object relation mappers.
So in theory, eventually it will be possible to support graph databases and such, it just won't be a core focus of Bookshelf's development. I'll keep this one open for now just for anyone looking for stuff about this, and add any additional thoughts as progress on the new features move further along.

The project leadership of Bookshelf recently changed. In an effort to advance the project we close all issues older than one year.
If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.
We also started an open discussion about the future of Bookshelf.js here https://github.com/bookshelf/bookshelf/issues/1600. Feel free to drop by and give us your opinion.
Let's make Bookshelf great again


perf(opentelemetry-node): plugin loader search required cache

Which problem is this PR solving?

fixes #1805

Short description of the changes

in pluginLoader, check if plugins are already required by executing require.resolve once per plugin, and searching for the result in require.cache object in O(1) instead of looping on the entire keys array

I assume the failing test is due to #1799 (also not passing on master).
Will merge master into the branch once the issue is resolved to fix required checks.

I assume the failing test is due to #1799 (also not passing on master).
Will merge master into the branch once the issue is resolved to fix required checks.

Change need to be made in the instrumentation package too (sorry we are in the process of migrating the loader so there are redundant code)

@vmarchaud
thanks for pointing it out.
pushed an update

Change need to be made in the instrumentation package too (sorry we are in the process of migrating the loader so there are redundant code)

@vmarchaud
thanks for pointing it out.
pushed an update


add tests to internet group as they require a dns

To avoid having to filter these test during build without internet connection, without dns

Indeed, seems an old leftover of some old versions


problem when install mmdet3d

Dear author,
I am trying to install mmdet3d on the server following your instruction. I installed pytorch1.13 + cu11.6. Other packages are the same as yours. When I running pip install --no-cache-dir -e ., it gives the error:
The detected CUDA version (12.5) mismatches the version that was used to compile
    PyTorch (11.6). Please make sure to use the same CUDA versions.

I installed a cuda 11.6 in the conda environment, but it looks like it didn't detect it. Do you know how to solve it?

Looks like the problem of your pytorch installation, so i can not help with it. Btw this code was only tested with pytorch==1.8.1 and cuda10.2. For newer versions you may try FCAF3D implementation directly from mmdetection3d repo.


fix: context resolution #15580

Fixes #15580

What kind of change does this PR introduce?
Fixes a bug where path resolution is incorrect

Did you add tests for your changes?
Yes

Does this PR introduce a breaking change?
No

I'd ideally like to add a regression test but I have no idea how to change the webpack config for a single test

answered in issue


Would it be possible to use utf8 characters?

First of all, thanks for the great library. I generated a form filled with English words, it worked like a charm However, when I tried to fill with French or any other languages, I got some weir characters like à1•à ̧€à ̧aà ̧±à ̧à ̧ ̈à ̧2à. Is there any work around to come across this problem?

Can you provide an example of input characters and their corresponding outputs?

I am sending .fdf  data like this:
data =
'last_name' : 'Johnамва' (with 4 russian letters)
and in PDF I got this:
'last_name' : 'John'
Pls help me solve this problem, I've read if I will send .xfrf data it could help but also I dont know how to set in PDF required fields, I mean I tried to send data to empty PDF and nothing changes, so I need to prepare PDF somehow, but how?Thx.

Seem like this is due to lack of utf8 support in one of our dependencies, https://github.com/countable/js-fdf

This has been fixed. See PR#30

@johntayl this should be closed


MCM option to disable perfect block?

Hi. I was wondering if Valhalla might include an MCM option to disable the Perfect Block feature, and what configuration options it might have for the Exhausted state.
I generally prefer parrying mechanics like in your other mod, Elden Parry (and Breath of the Wild), over timed Block mechanics as described in this mod's README (also present in Ordinator).
I also find that the combination of the two is kind of silly.
I'd love to use both Valhalla and Elden Parry, but if there were an option to disable the Perfect Block feature in Valhalla, I'm sure it would help the two feel better together.
Please consider this a feature request, and let me know if there's any way I can help make it happen.

Hi, Valhalla Combat comes with a highly customizable MCM that provides toggles for every single feature and sub-features. You can surely turn it off.


Added ability to add text color for ios

In this pull request I have added ability to change iOS text color. I have added a new parameter in iOS option where users can specify text color for iOS.

Thanks

@nericode Thanks for merging the change.
By when this change should be visible in the plugin?  Please advise. I just tried and it was pulling old code.
Thanks.

@harishchopra86 I have to update the plugin in NPM, give me time please

@harishchopra86 check the new version, please.

@nericode I just updated to new version 1.0.4. I am getting this error with the update: Module not found: Error: Can't resolve 'nativescript-tooltip-ns'
It appears that the update is missing some files. Please see attached screenshot of module files with version 1.0.3 and 1.0.4.
In version 1.0.4 all the common, android and iOS files are missing.

@harishchopra86 I'm uploading version 1.0.5, just update the repo and publish, I don't know what's wrong


Wrong position of textwrap

I am integrating textwrap in a zoomable treemap visualization directly on d3.js (not using d3plus :(
The issue I have perceived is the "dy" attribute of the original text is used to position the new tspan into the "text" SVG, but the textwrap function is not considering the units of the dy attribute.
I have prepared a fiddle showing it, I have fixed "dy" to "0.75em" and textwrap uses it as it was measured in pixels. http://jsfiddle.net/miceno/jte74dj5/

Yeah this is strange. A hot fix if interested is to change line 16 in this textwrap source file to "em" instead of "px" and then recompile your own version of the library. OR you can edit the compiled version manually on line 19505 and again change "px" to "em".
I'll keep this issue open and investigate how changing this effects our tests and fix it in the next d3plus release.

Thank you for the workaround!
I am afraid the library should take into account the kind of units developers provide, since developers will provide the values of x, y and other parameters in different units. I guess a way to "propagate" the units to the function you appointed in your comment will be great.

Considering it more thoroughly, the library should "normalize" units to pixels and use them accordingly, since all along the different functions, operations should be consistent.
If "font-size" is given in "em" and "y" is given in "px", most of the operations on tspan.coffee will not be consistent.

True... all good points. We're working on a 2.0 branch currently and will consider these comments. Thanks for your interest in the project!


Recommended setting of CouchDB configuration: {couch_httpd_auth: timeout} parameter

Hi!
Is there a recommended setting of the CouchDB configuration: {couch_httpd_auth: timeout} parameter?
The reason for asking is that the default cookie refresh time is 10 minutes in pouchdb-authentication, and  without being 100% sure I seem to get problems if I set the timeout parameter to less than 10 minutes.
Best,
Sinan

What kinds of problems do you get?

I seem to get an error 500 when trying to access the db after timeout time where timeout is less than 10 minutes: but I will check this again as this seems to be a new observation.

I tried, for the experiment, to set couch_httpd_auth: timeout=60 (corresponding to: 60 seconds=1 minute).
After about 5 minutes I could not read or write to the database. A pop-up came up and asked for re-login to the database.
I am by the way using your fine guideline about using:
ajaxOpts = {ajax: {headers: {Authorization: 'Basic ' + utf8_to_b64(user.name + ':' + user.password) }}};

PS I tried again today, and this time it took about 9 minutes before the request to read from the database failed, and the sign-on pop-up opened - by cancelling the sign-on a '401 (Unauthorized)' is replied in the browser console window.
Doing a db.allDocs() directly in the browser console window the error.status 500 is returned: '{status: 500, name: "unknown_error", message: "Database encountered an unknown error", error: true, toString: function}'

It sounds like your CouchDB is not accessible from your browser. Did you set the bind_address to <IP_ADDRESS> and enable CORS?

I am experimenting on a local single machine, and yes, CORS is set, and the bind_address is <IP_ADDRESS>
Note that if the {couch_httpd_auth: timeout} parameter is set to a large number such as e.g. 1,209,600 (two weeks) then I do not experience any problems accessing data: then everything seems fine.
In other words, is there a lower limit of the value of the {couch_httpd_auth: timeout} parameter, given a default cookie refresh time of 10 minutes in pouchdb-authentication? (Here I presume that there is a relationship between these two parameter settings)

Hm, I don't recall setting a timeout anywhere in pouchdb-authentication. That's really weird.

Sorry: I mean the {couch_httpd_auth: timeout} parameter in the CouchDB configuration (i.e. not PouchDB or pouchdb-authentication library).

Yeah sorry, I still don't know. :) This might be a CouchDB bug.

No prob. I can pose the question at the CouchDB forum and see if anybody else have experienced this.
Thanks for now!


Setting container security context generates invalid YAML

When container.postfix.securityContext is set in values.yaml, the template generates invalid YAML that looks like this snippet:
      containers:
        - name: smtp
          image: "boky/postfix:v3.5.1"
          imagePullPolicy: IfNotPresent
          securityContext:            allowPrivilegeEscalation: false
            capabilities:
              drop:
              - ALL
            runAsUser: 1000
            seccompProfile:
              type: RuntimeDefault
          ports:

Fixed in the latest master, thanks for reporting.

Is it possible to run the container with runAsUser: 1000 ?
I get an error with this:
sed: can't create temp file '/etc/rsyslog.confXXXXXX': Permission denied
I thought it only works with runAsUser 0 (root)

https://github.com/bokysan/docker-postfix#security


Transitive dependency licensing information for Chef Client

This PR goes with https://github.com/chef/omnibus/pull/705 and https://github.com/chef/omnibus-software/pull/714 and adds licensing information collection for the transitive dependencies of Chef Client.
An ad_hoc build with all these branches are tested at:
http://manhattan.ci.chef.co/job/chef-trigger-ad_hoc/157/downstreambuildview/
Note that the PRs linked from here do not contain the msys2 changes that are currently sitting in the private branches of omnibus and omnibus-software pointed to by this project. Once they are merged we will need to rebase the private branches on top of master and re-test.

:+1:  on green


For version 1.14b?

Could you add a 1.14b version in the latest updates?

should be possible :)

Yes! The most up-to-date version of its program, but compatible with version 1.14b of Diablo 2.

We'd need to find the new memory table for that version since the way data was read was changed a while back, which made a lot of the new features possible. Adding this would be great but someone would have to do the work.

How could I help?

@filaname
take a look at the pre release: https://github.com/Zutatensuppe/DiabloInterface/releases/tag/v0.3.4.PR.1


commander add parameters for eph, eph, evh thresholds

This PR adds separate parameters for required eph, eph, evh thresholds. Previously eph and epv thresholds were set from COM_HOME_H_T and COM_HOME_V_T.
COM_POS_FS_EPH
COM_POS_FS_EPV
COM_VEL_FS_EVH
https://github.com/PX4/Firmware/issues/8260

We should also start thinking about how to handle VTOL differently. @sanderux @bresch FYI

If we make these params FW and MC i think we solve both problems at once and allow setting suitable standards for both

Ok, let's think about a good way to introduce this kind of thing to the system for VTOL. We don't want tons of parameters to be split FW/MC where possible.
Is there some other architecture that really defines what's needed? For example could the position controller be the one stating the required position and velocity error thresholds?

How about scaling it on ground speed?

@sanderux some kind of scaler might work short term, but there's a lot more we're going to need to do in this area.
@priseborough my suggestion above may also (inadvertently) let us jump straight into changing the thresholds based on context.
FW

takeoff (at different stages)

includes pretakeoff (on the ground about to arm and then launch)

general cruise flight (waypoints at sufficient altitude)
landing (at different stages)
MC
takeoff
general navigation
regular landing
descend (landing velocity only in a failsafe)
VTOL
need to think about transitions only
otherwise respects regular MC or FW

With all of this information we can set the thresholds appropriately based on vehicle type and the specific situation. We need to get the architecture right to handle all of this without commander complexity continuing to explode.

I like the direction this conversation is heading.  Is it worth setting thresholds based on vehicle type or is scaling according to actual dynamics both simpler and more appropriate?  My guess is ground speed and/or acceleration would be useful in modeling appropriate error thresholds.

What if we added a new message that's something along the lines of "navigation requirements".
navigation_requirements

maximum eph
maximum epv
maximum evh

This could either come from the currently active position controller, or from the land detector, which has effectively turned into "vehicle model". It's now also publishing things like a maximum altitude (based on remaining battery capacity) for limiting navigation altitude. We could also finally rename land_detector -> vehicle_model.

That moves us closer to context based thresholds which is where we should be aiming.

Agree

@dagar @priseborough here is a fixed wing flight log that shows a short period of "loss of global position"
https://logs.px4.io/plot_app?log=99e99083-379d-43fe-869c-f0e41b77ba3b
I don't see anything obvious in the logs as to why, but there is a growth in vert and horz accuracy coinciding with a change in "GPS Fix" from 4 to 3.

Is this loss of global position failsafe kicking in too prematurely?
Would the new params in the PR be an appropriate method to improve this?

@Antiheavy that looks like an actual loss of GPS (temporary). For about 10 seconds there was no data published from the GPS.

This triggered the loss of GPS nav state (fixed bank loiter). These GPS checks were only just removed recently (https://github.com/PX4/Firmware/pull/8914). If the same thing were to happen again the failure state would only trigger as a result of estimated position error (green & red above). So coming back to this PR you can now tolerate a loss of GPS until the errors passes a defined threshold, and that threshold is now by default set much larger for FW.

I've rebased on master to resolve the conflicts.
@priseborough could you please review?

The changes look OK. How have you tested it (noting that our CI does not appear to include tests for these types of failsafe events)?

Going through some testing in SITL by killing GPS and condition_local_position_valid is going to false very quickly.

About 1 second after GPS loss, the EKF reports vehicle_local_position xy isn't valid.

@priseborough should commander bother using the valid flags?
https://github.com/PX4/Firmware/blob/877d212a335e9113c8ddd8f133c27794504cf9fc/src/modules/commander/commander.cpp#L2012-L2013

Make sure you have sideslip and airspeed fusion running so it can dead reckon

It looks like it wasn't defaulting on for SITL.

Rebased and updated the plane SITL model to enable EKF2 airspeed and synthetic sideslip fusion.

SITL test flight with GPS stopped (:52), restarted (05:45), and stopped again (06:35).
https://logs.px4.io/plot_app?log=8c3267bd-91b5-4031-93d4-6c81d58f587f

Questions

why didn't vehicle_global_position deadreckoning ever change?
why did the commander flags for local position and local velocity validity change so frequently?

@priseborough I did some debugging and the consistent blips of !xy_valid and !v_xy_valid are the result of the time between each synthetic side slip measurement (https://github.com/PX4/ecl/blob/041886a28957c17505b19367eb8703444123a4c3/EKF/control.cpp#L1119), and the no aid timeout max check in Ekf::inertial_dead_reckoning() (https://github.com/PX4/ecl/blob/041886a28957c17505b19367eb8703444123a4c3/EKF/ekf_helper.cpp#L1259).
What would you recommend? Is it appropriate to increase the timeout for last beta fuse?

Increasing the synthetic sideslip fusion frequency would also work.

I think increasing the frequency of fusion is the answer. I would reduce beta_avg_ft_us from 1000000 to 150000 (avoid 5 and 10Hz because it is used by other sensors)

ECL PR decreasing synthetic sideslip fusion interval. https://github.com/PX4/ecl/pull/407

That's better. https://logs.px4.io/plot_app?log=ac75a8f5-07fe-4dcb-9adc-c94e7175952b
GPS is killed (gpssim stop), and you can watch eph grow until it exceeds 62.5 (2.5 * COM_POS_FS_EPH), then the plane enters the fixed bank angle.

Here's vehicle_global_position (estimated global position) vs gazebo groundtruth.

Here's another one after the last two commits. https://logs.px4.io/plot_app?log=05010450-ac7c-4336-b720-7e2712eed991
Condition flags plotted with small offsets for visualization.

@priseborough @RomanBapst this should be good to go, please review again.

flight with pixhawk 3 pro V4pro. Good flight no isuuses.
https://review.px4.io/plot_app?log=4b8c5f52-53a1-4c52-8ef8-ea5e45400cfc
Flight with pixhawk 2.1 V3.  Good flight, no issues.
https://review.px4.io/plot_app?log=9025fe1c-dd95-4bf8-8128-5bcbe4cf0387

Few flights on a Pixracer (v4)
indoor flight after a full reset and a re-calibration using all default parameters:
https://logs.px4.io/plot_app?log=3a548922-1207-42fb-875d-16113efd2c80
full outdoor test using all default parameters:
https://logs.px4.io/plot_app?log=7328b415-8e37-4edf-b0f2-4901df44eb16
manual take-off; good manual flight; seamless transition from stabilized to altitude mode; very abrupt cornering in auto
https://logs.px4.io/plot_app?log=3e064843-776f-408e-90dd-2a56f882272b
adjusted a few MC and MPC values; improved cornering; good flight but I feel it could still be improved by changing some of the default parameters for the Flamewheel F450 frame

FW testing pending

flight pixmini v3 great:
https://logs.px4.io/plot_app?log=7fd2af8e-b8b7-48e6-8f34-f3729148167c

Normal flight testing is not sufficient for these changes. It requires SITL or flight testing with a rotated magnetometer or incorrect declination value to induce a loss of navigation.

That's what my SITL testing above was trying to accomplish. Killing the simulated GPS and explicitly testing commander failsafe thresholds that are now parameterized. I also found and fixed a few other minor check_posvel_validity issues along the way.
I requested additional flight testing to catch any other general regressions given the amount of commander churn.

Was that testing restricted to FW?

Above was FW with dead reckoning, but I also tried MC briefly. Commander almost immediately changes the validity flag once GPS is lost because the EKF local position reports xy_valid = false.

That is current behaviour. Given the  inability of the nav to dead reckon without airspeed and sideslip constraints we could extend it by 5 seconds.  Are you stopping GPs lock using the  'gpssim set -t 0' command or stopping data completely?

Stopping GPS entirely, although gpssim set -t 0 looks about the same.

The timeout to report position invalid after a period of inertial deadreckoning is set by a no_aid_timeout_max parameter inside the EKF. It is currently set to 1 second (1000000 uSec)
It could be added to the list of tuneable parameters in ekf2_main.cpp

I will submit a PR with the ekf2 module changes required to adjust it. I think a default value of 5 seconds would be acceptable for most applications. If required for indoor experiments, a  smaller value can be set.

Would it make more sense to add the patch to this PR?

Yes we might as well test it altogether.

When I try building this branch, it is unable to access the mavlink submodule reference:
Submodule ‘mavlink/include/mavlink/v2.0’ (https://github.com/mavlink/c_library_v2.git) registered for path ‘../../../mavlink/include/mavlink/v2.0’
error: Server does not allow request for unadvertised object 37d14af47d783eb516959cc10e4cf70d66e927c0
Fetched in submodule path ‘../../../mavlink/include/mavlink/v2.0’, but it did not contain 37d14af47d783eb516959cc10e4cf70d66e927c0. Direct fetching of that commit failed.
error: Server does not allow request for unadvertised object 37d14af47d783eb516959cc10e4cf70d66e927c0
Fetched in submodule path ‘../../../mavlink/include/mavlink/v2.0’, but it did not contain 37d14af47d783eb516959cc10e4cf70d66e927c0. Direct fetching of that commit failed.

There are no mavlink changes in this PR. I would try make distclean followed by make submodulesclean. If you're using a git gui it might be different.

You might also have an old reference, this branch has been rebased and force pushed multiple times.

Thanks. The usual 'make distclea'n and 'make submodulesclean' didn't work, so I ended up deleting all files in the Firmware directory and checking out the branch and all submodules again.

Flight on flying wing running pixhawk mini (v3)
https://logs.px4.io/plot_app?log=12c76c64-2028-4ff6-b115-8d5eda4bfe0b
roll input was not responsive in stabilized, had to opt out with manual

@santiago3dr that's unrelated to this PR.
You need to reset the fixedwing maximum rollrate (FW_R_RMAX). There's a somewhat recent change in master that means 0 is now interrupted as maximum rate of 0 (disabled).
I would try to periodically reset all of your parameters from the stock airframes so that any bogus setting don't persist.

Fresh flash; reset parameters and it seems the default for Generic Flying Wing is 70 deg but when loading the frame for Phantom FPV Flying Wing is 0.0 by default
Can we check other fixed wing configurations to assure said parameter does not default to 0.

@santiago3dr that's definitely wrong. Fixed here https://github.com/PX4/Firmware/pull/9135
I also did a quick sanity check of the other airframes and didn't see anything else quite that egregious.

The priority test to conduct in SITL is to verify for multirotor platform types that the system correctly failsafes into land following takeoff initiated by console command 'commander takeoff' when the magnetometer is misaligned by a large amount.
In the past for SITL testing I have tested with yaw misalignments of 45, 90, 135 and 180 degrees but ended up applying the rotation in the ekf2_main.cpp file because the SITL mag driver does not support use of the CAL_MAG*_ROT parameter. I have performed the 90 and 180 degree tests with this branch and both transitioned to land as expected with the following console output:

However neither case disarmed after landing which was unexpected. This behaviour was present for master so is not a problem with this PR. If the landing was commanded from the console, then the vehicle does disarm, so there is something inside commander to investigate as a separate issue.

Rebased on latest PX4 master requiring a switch to the new parameter wrappers.
TODO

mag sim add rotation
investigate land detector issue (https://github.com/PX4/Firmware/pull/8771#issuecomment-375146157)
investigate GCS altitude display/update after loss of valid position
SITL test multicopter with mag rotation

Requires https://github.com/PX4/ecl/pull/413.

Magnetometer sim driver rotation is ignored because the system thinks it's internal.

Multicopter SITL test with mag driver rotated yaw 90 degrees.
https://logs.px4.io/plot_app?log=05a0600d-75c9-4377-94e7-9194e304dcc3

However neither case disarmed after landing which was unexpected. This behaviour was present for master so is not a problem with this PR. If the landing was commanded from the console, then the vehicle does disarm, so there is something inside commander to investigate as a separate issue.

Land detector debugging - https://github.com/PX4/Firmware/pull/9157

vehicle_global_position dead reckoning flag still not reporting correctly.
This is after gpssim stop with gazebo plane.

Small issues with vehicle_global_position continuing to publish briefly after "EKF stopping navigation" with eph and epv set to 0. This makes commander think global is valid again temporarily.

Can you describe the steps you followed to produce that result? I have tried with the MC sim and was unable to.

I tested using the FW sim using the following procedure:
'make posix gazebo_plane'
'commander takeoff'
switch to attitude control and climb to 250m
switch back to hold mode
turn off gps using 'gpssim stop'
switch to attitude mode and glide down.
The EKF does stop air data dead reckoning eventually because the numerical stability of the air data fusion deteriorates over time. I will raise a bug report for it and fix.

Updated ECL (https://github.com/PX4/ecl/pull/413) and rebased on master.

For FW at the moment, would it be beneficial to change to COM_POS_FS_EPH 25 and COM_POS_FS_EPV 50 for now until this gets merged?
Same for change to EKF2_MAG_TYPE 1 with EKF2_MAG_ACCLIM 0 and EKF2_MAG_YAWLIM 0?

Rebased on master.

The orb_copy(ORB_ID(airspeed), _airspeed_sub, &airspeed) function call in ekf2_main is returning false

The orb_copy check was wrong. It returns OK (0) on success, which is completely wrong when treated like a bool.
Once this settles we should talk about CI tests covering a range of core features. For example in this case we could enable wind in gazebo plane, run a basic mission test, then once it's finished validate from the ulg (EKF control status, wind estimate matches gazebo configuration, etc).

I found the bug in ecl causing the failure and have pushed the fix to https://github.com/PX4/ecl/pull/413

FW test (gps stop) - https://logs.px4.io/plot_app?log=876c333b-a9cf-4290-8c7a-465f4a23142c

We're still slightly out of sync with local_position xy_valid.

@priseborough there are still minor issues here, but to be honest this is still much better than what's currently in master. I think we should consider merging and then continue iterating (https://github.com/PX4/Firmware/pull/9363).

https://github.com/PX4/ecl/pull/413 is merged, I updated this branch to ecl master and squashed into
8caf3ae.


Properties that are inferred Zod types are always dropped from any mapped types that involve key mapping.

I'm tracking an odd issue with Zod in this StackOverflow thread: https://stackoverflow.com/questions/75778970/why-is-an-inferred-generic-zod-string-type-considered-assignable-to-never/75779088#75779088
It seems that any property with a z.infer'd type from a generic type gets dropped whenever participating in a conditional key mapping.
export type FilterNothing<T> = { [P in keyof T as T[P] extends T[P] ? P : P]: T[P] }

class Test<Z extends z.ZodString> {
    foo(args: FilterNothing<{ key: number, value: z.infer<Z>, bar: Date }>) {

        const { key, value, bar } = args;
    }
}

Playground here
In the above code, the condition is a noop... all keys are always mapped, and yet value is still dropped.
Any idea why / how this could be possible?

Seems like this is not related to zod, since the same is exhibited with a plain generic type too:
export type FilterNothing<T> = { [P in keyof T as T[P] extends T[P] ? P : P]: T[P] }

class Test<Z> {
    foo(args: FilterNothing<{ key: number, value: Z, bar: Date }>) {

        const { key, value, bar } = args;
    }
}

Closing this issue in pursuit of broader answers!


add mesos_exporter to list of exporters

This commit adds the mesos_exporter for tasks in mesos in the documentation.
Thanks!

@antonlindstrom Thanks! So far, the list only has exporters in the prometheus organization because those are vetted to a certain degree to adhere to code and metrics conventions. But I think it's time to mention the various external exporters as well. Just wondering if we should mark them as external in the doc (but I can add that later). Or perhaps you're interested in moving this to the prometheus org and maintaining it there anyways? Either way is fine...

Btw., it looks like your code is already 95% following our conventions anyways, so we would probably only want to change minor things when including it in the prometheus org.

What about a github.com/prometheus/exporters repo? Should be easier to handle than tens of repos.

@grobie Then we'd have to be ok with every exporter maintainer to have push access to the entire repo. We might be ok with that, but we should at least give it some thought - especially in the scenarios where such an approach would be most helpful (like 100 exporters), we'd also potentially have a huge amount of people with commit access to everything. At the moment, I don't see a big problem with adding more exporters to the main org yet.

I'm merging this for now because I don't want to hold things up regardless of outcome - I might add some things later to point out prometheus-org vs. external repos.

@juliusv Thanks! I don't mind moving it to the prometheus org, just let me know what do to to make it happen.
Cheers!

@antonlindstrom Cool! I'll try to have a closer look soon and then it'd be cool to make it happen :)

@antonlindstrom Hey, if you're still interested in moving this to the prometheus GitHub org, we could do https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization. I think I'll need to give you temporary admin access to the org to make that work. Alternatively, I could create a new repo and give you push access to that. Let me know what you prefer :)

@juliusv Sorry for the late reply. Would be awesome, I'm fine with transferring the repository to the Prometheus Github org. Let me know when I can do it and I'll transfer it right away.
Thanks!

@antonlindstrom Sorry, I'm a bit slow/overloaded these days as well. I made you a temporary admin user on github.com/prometheus, so you should be able to move the repo now! One thing though to clarify, we enforce the same LICENSE/AUTHORS/etc. boilerplate (and copyright "The Prometheus authors") for all projects, in order to stay consistent and not become insane. Just want to check if that's ok with you first. We might also want to change some of the metric names in the
Mesos exporter a tiny bit to match our conventions (i.e. secs->seconds), but probably nothing major.

@juliusv No worries. Just tried to move and it didn't seem to work. Maybe it takes some time to propagate?
No worries about updating license and authors, you are free to update it as you see fit. Just let me know what to change and I'll do it.
Thanks!

@antonlindstrom Ah, when trying to add you to the Admin group again, GitHub says, "Invitation already sent". So I think you have to accept the invitation first before you're in the group...

@juliusv Ah, thanks! I thought that would show up in the web ui but it didn't. Transferring the repo now.

@antonlindstrom Awesome, thanks! Will send followup PRs about the above-mentioned topics soon!

@juliusv Perfect, thanks!


Rounded Box Component

Summary
Rounded box styling was appearing in a lot of places.  A  component has been created to make it easier for reuse. Contains two styles: true for roundedBox1, false for roundedBox2.

If you're already setup for this, validating the new work would be much easier for me by having before/after screenshots of the affected screens!

If you're already setup for this, validating the new work would be much easier for me by having before/after screenshots of the affected screens!

work would be much easier for me by having before/after screenshots of the affected screens!

@aklef
I spoke to @dsamojlenko about this - he'll give you the game plan to automate this :)

work would be much easier for me by having before/after screenshots of the affected screens!

@aklef
I spoke to @dsamojlenko about this - he'll give you the game plan to automate this :)

Please hold from merging this until after the next release.

Please hold from merging this until after the next release.

@omartehsin1 please fix up the conflicts and we'll merge this one.

There is now a e2e testing script using Detox that iterates through every page of the app available on the debug menu that takes screenshots as it goes. Should now be able to use that to get before/after images and then use Tim's test-galery script to generate an html page of before after...


Add documentation regarding file upload

We have documentation regarding the file download process. We need to add documentation regarding the process of uploading a file and downloading and saving it.
from robyn import Robyn, jsonify
from pathlib import Path

app = Robyn(__file__)

@app.post('/upload')
async def upload(request):
    body = request.body
    file = bytearray(body)

    # write whatever filename
    with open('test.txt', 'wb') as f:
        f.write(body)

    return jsonify({'message': 'success'})

if __name__ == "__main__":
    app.start(port=8001)

Addressed now


Fix benchmark regression in layer.find(Offset)

Description
This fixes a benchmark regression introduced in #32350.  The performance is improved by just reverting the Layer.find<S> routines to use their old definitions, instead of defining them in terms of the findAll<S> lazy iterators.
Related Issues
Fixes #32387

Should we consider replacing the sync* implementation with something that returns a List (once we have a benchmark covering it?).

Yeah, maybe.  I'll look at that after this.


 invalid syntax

Hi! When I import the ypoy package to my python program and run it, it gives me this error in console:
`Traceback (most recent call last):
File "yo.py", line 1, in
import yopy
File "/usr/local/lib/python2.7/dist-packages/yopy.py", line 5

^
SyntaxError: invalid syntax
`
What can I do?

My mistake.


Add redirect for broken link, update READMEs

Resolves Azure/azure-sdk-for-python/issues/15796.
This also brings the package overviews up to date with azure-sdk-for-python READMEs.

Docs Build status updates of commit b57f8cd:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/azure-docs-sdk-python, working directory: W:\zfce-s, target branch: smoke-test, target branch commit: e55c70d8f894a65ec4990f58ff0e327d070b9ae3, source commit: b57f8cda40d7437e3c5a3b767aea33b1e9e33ef5.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b57f8cd:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/azure-docs-sdk-python, working directory: W:\zfce-s, target branch: smoke-test, target branch commit: e55c70d8f894a65ec4990f58ff0e327d070b9ae3, source commit: b57f8cda40d7437e3c5a3b767aea33b1e9e33ef5.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Orange Pi java.lang.UnsatisfiedLinkError

Getting an "java.lang.UnsatisfiedLinkError: org.sqlite.core.NativeDB._open(Ljava/lang/String;I)V" exception when trying to getConnection().
sqlite-jdbc-<IP_ADDRESS>.jar
Orange Pi PC (http://www.orangepi.org/orangepipc/)
H3 Quad-core Cortex-A7 H.265/HEVC 4K
Lunbuntu 14.04
Sorry for my lack of detail because I am not an expert with this kind of thing. Please tell me what other information I may need to provide.
Thanks!
NOTE: I tried sqlite-jdbc-3.7.2.jar and it seemed to at least get a connection, but my PreparedStatements would return syntax errors then.

Sorry, I followed the build instructions and it works now.