Inline display not scrolling when it overlaps bottom of current page

The scroll bars don't appear, and the panel can't be scrolled in any direction, even though there is additional data to show.

I think this is really a bug with Atom Ink since this is using their inline display. I've filed an issue there to track it.

Thanks for reporting the bug in the right place. I should have realised that it was probably an Ink issue.
By the way, thanks for your amazing work on proto-repl. It's shaping up to be an excellent way to write Clojure code. 😄


admin/users table with update-claims #242

WIP for admin/users #242.

[x] admin/users lists users & allows updating roles
[x] search
[x] roles are currently check-boxes. Also, I'm considering roles == Firebase.claims; LMK if that assumption should be reconsidered
[x] how do we want /admin to look? Do we want tabs with inline content (admin/transactions, admin/users); or side-bar tabs?

Thanks for the review @dallashuggins! I'll tackle these bits.

Re: the roles - sorry not quite understanding. Do you mean that we're not validating which roles are available to use as the claims?

Just mean that currently (AFAIK), Firebase custom claims is synonymous with Roles (because there's only one claim I see in the codebase: and that's {admin: <bool>}). Ie, this PR assumes that to remain so: that FB custom-claims means Object(<role:string>=<bool>). If we anticipate using FB claims for non-role meta-data downstream, I'll want to reconsider this PR

Just mean that currently (AFAIK), Firebase custom claims is synonymous with Roles (because there's only one claim I see in the codebase: and that's {admin: <bool>}). Ie, this PR assumes that to remain so: that FB custom-claims means Object(<role:string>=<bool>). If we anticipate using FB claims for non-role meta-data downstream, I'll want to reconsider this PR

@lefnire Aw okay, gotcha - thanks for clarifying! No plans to use claims for anything outside of roles, I think it makes sense to have those be synonymous.

Updated PR with changes requested. The bit I'm not sure about is getServerSideProps  -> useAdmin, as the page/table shows for anon after that change (albeit empty of users)

@lefnire I actually don't see useAdmin({ redirectIfNotAdmin: true }) anywhere in the code right now BUT I also took a look at the other admin pages and I see that we're actually using isAuthenticatedUserAdmin in getServerSideProps there the same as you were, and also that it does in fact check the cookies. That's my bad, I must be remembering an earlier iteration of this before we pinned down the redirect behavior.

@afraser sorry, forgot to mention - <AdminLayout/> (which AdminUsersPage uses) has useAdmin. Also tried useAdmin directly inside AdminUsersPage, same. To verify, you thinking I should switch back to getServerSideProps then (per the other admin pages)?
Just noticed some changes I need to make; I was assuming axios (still on ky).

@lefnire Ah I forgot about the layout. And yes, I think it makes the most sense to keep it consistent with the other pages. Sorry for the run around. It's been a bit since I hooked up the admin views.

added getServerSideProps back, fixed ky v axios

@lefnire looks like CI isn't going to run until we get this into a branch. Everything looks good to me though. Appreciate the attention to detail on the sorting and filtering.


Error when building an app with firebase_performance: "class file for com.google.android.gms.internal.firebase-perf.zzf not found"

Build fails with error class file for com.google.android.gms.internal.firebase-perf.zzf not found on a fresh Flutter app when adding the firebase_performance plugin.
Affected versions
Flutter v1.3.8
firebase_performance: 0.1.0+4
Steps to reproduce

flutter create firebase_performance_test

Set up a Firebase project in the Firebase console and put google-services.json into ./android/app (as instructed in https://codelabs.developers.google.com/codelabs/flutter-firebase/#6)

Add the following configuration:

In ./pubspec.yaml, add under dependencies:
firebase_performance: ^0.1.0+4
In ./android/build.gradle, add under dependencies:
classpath 'com.google.gms:google-services:3.2.1'
In ./android/app/build.gradle, add in the end:
apply plugin: 'com.google.gms.google-services'

Run flutter build apk

Expected output
Build succeeds.
Actual output
For verbose output see: https://pastebin.com/Ci7p4Tzt
❯ flutter build apk
Initializing gradle...                                              2.0s
Resolving dependencies...                                           5.5s
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
/home/antti/tools/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_performance-0.1.0+4/android/src/main/java/io/flutter/plugins/firebaseperformance/FirebasePerformancePlugin.java:71: error: cannot access zzf
    trace.start();
         ^
  class file for com.google.android.gms.internal.firebase-perf.zzf not found
Note: /home/antti/tools/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_performance-0.1.0+4/android/src/main/java/io/flutter/plugins/firebaseperformance/FirebasePerformancePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':firebase_performance:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 8s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                       8.8s
Gradle task assembleRelease failed with exit code 1

flutter doctor -v
[✓] Flutter (Channel beta, v1.3.8, on Linux, locale en_US.UTF-8)
    • Flutter version 1.3.8 at /home/antti/tools/flutter
    • Framework revision e5b1ed7a7f (11 days ago), 2019-03-06 14:23:37 -0800
    • Engine revision f4951df193
    • Dart version 2.2.1 (build 2.2.1-dev.0.0 571ea80e11)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /home/antti/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /home/antti/Android/Sdk
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu<IP_ADDRESS>)
    • All Android licenses accepted.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).

[✓] VS Code (version 1.32.3)
    • VS Code at /usr/share/code
    • Flutter extension version 2.24.0

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

I'm getting the same error with firebase_performance 0.0.8+1 (the last pre-AndroidX version). So it doesn't seem to be an AndroidX issue.

RESOLVED. Downgrading from Java 10 to Java 8 fixed the problem.


Add debug action - Origin to Origin

https://github.com/mobu-of-the-world/emobu/pull/379
https://github.com/mobu-of-the-world/emobu/actions/runs/5631267283/job/15258050288?pr=380
mobu-of-the-world/emobu
mobu-of-the-world/emobu

This PR is a testing part for https://github.com/typescript-eslint/typescript-eslint/pull/7296


Fix: 25448 ESC keyboard shortcut shows up in modal on second render on login page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/25448
PROPOSAL: https://github.com/Expensify/App/issues/25448#issuecomment-1683898309
Tests

Sign out if you are logged in
Refresh the page
Press cmd+j to open the shortcut modal
Now you can observe escape key has been added
Close and open it again to verify.

Note for testing in native please use a physical Keyboard to open the modal.
We can't refresh in Navtive (Android, iOS) so please close and reopen the app i.e. step 2.

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Sign out if you are logged in
Refresh the page
Press cmd+j to open the shortcut modal
Now you can observe escape key has been added
Close and open it again to verify.

Note for testing in native please use a physical Keyboard to open the modal.
We can't refresh in Navtive (Android, iOS) so please close and reopen the app i.e. step 2.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/62904657/58fb026c-2731-4c04-a83c-44202cb9edbf

Mobile Web - Chrome

https://github.com/Expensify/App/assets/62904657/b68d18b6-e022-4182-b0a5-2988f105d581

Mobile Web - Safari

https://github.com/Expensify/App/assets/62904657/26f0fde3-ecbb-4be6-a2f4-00b7c8ad4aa0

Desktop

https://github.com/Expensify/App/assets/62904657/df73f464-bfcf-45d0-9f39-3088c55194ab

iOS

https://github.com/Expensify/App/assets/62904657/78561f0a-c2cd-4b4a-81e3-6bd5141da67b

Android

https://github.com/Expensify/App/assets/62904657/2f351ee8-e25d-45a1-8ed6-49d3ffc0c8f2

@Charan-hs Add the test step, please.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@Charan-hs I see that you commented on https://github.com/Expensify/App/issues/26829, Will the issue be fixed in this PR? I tried the steps in this PR, but the issue is still reproduced. Logically, that issue will be fixed with your solution. Could you check? Thanks!

@Charan-hs I see your suggestion for fixing the unsubscribe here. Is that all you need to fix https://github.com/Expensify/App/issues/26829, and this PR is also part of the fix? If yes, we should keep it separate so the original issue won't be out of scope and it easier to track the issue.

Thanks @Charan-hs
Since https://github.com/Expensify/App/issues/26829 it's already put external, we should fix the issue there. Feel free to post the proposal there, or you could ask them to wait for this PR to be merged to get a better result.

Merge freeze ends on Monday. I'll merge then

Hi @Charan-hs, the freeze season is past! Before we get this merge, could we pull the latest main and retest the PR? Thanks!

@arosiclair I tested it again with the latest commit, which still tests well. We can get this merged.
Sorry @Charan-hs, I can't merge any PR. Only the internal engineer can do it.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/arosiclair in version: 1.3.69-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.69-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/arosiclair in version: 1.3.70-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.70-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


feat(rules): add no-same-label-and-hint rule

Codecov Report

Merging #7 (3ad8b33) into main (57ff9dd) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   97.17%   97.30%   +0.12%
==========================================
  Files          29       30       +1
  Lines         319      334      +15
  Branches       91       95       +4
==========================================
+ Hits          310      325      +15
  Misses          9        9

Impacted Files
Coverage Δ

src/rules/basic/index.ts
100.00% <100.00%> (ø)

src/rules/basic/no-same-label-and-hint.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Feature/538 avoid negotiation loop

Ref #538
This fix the referred issue introducing an INITIAL state that goes between UNSAVED and REQUESTING.
However, there are still some problems, probably introduced (or, better, unearthed) by the correct evaluation of the futures.
Before, for every state there was a single intermediate state:

REQUESTED -> REQUESTING
PROVIDER_OFFERED -> PROVIDER_OFFERING
...

But now we would need another intermediate states, like:
INITIAL: the negotiation is initialized, and it's retrievable by the state machine loop for being processed
REQUESTING: the negotiation has been retrieved from the store and sent to the provider, it should be not retrieved anymore by the state machine loop, otherwise it would be sent multiple times
REQUESTED: the request has been successfully sent to the provider.
To better describe these async transitions there could be 3 states for every "real state":

TO_BE_xxxED
xxxING
xxxED
(replace xxx with, e.g. "REQUEST", "PROVIDER_OFFER", etc...)

This 3-state pattern need to be implemented for every state transition, otherwise there will be multiple and uncontrollable state changes.
I ask thoughts to those who worked on the state machines @jimmarino @paullatzelsperger @juliapampus @ronjaquensel , somebody else?

Hi @ndr-brt,
I think it makes sense to introduce this 3-state-pattern, to account for the time where the other party processes the request. I just ran sample 4 on your branch and introducing the INITIAL state already seems to break the infinite loop (now only the agreement is confirmed multiple times, but at least not infinitely), so introducing the intermediary state for all states should solve the issue.
One thing we have to think about though is the state count. Currently the state count is increased when a negotiation is transitioned to the same state as before. Since we will now always have an intermediary state, the transition will e.g. be requesting -> initial -> requesting instead of requesting -> requesting, therefore the state count will not be increased as is. I don't think this is crucial right now, as we are not using a retry strategy in the negotiation managers at the moment, but this should definitely be addressed later on.

@ronjaquensel thank you for the feedback.
I think that, when we do an async computation on the entitity (like in the "requesting" case), we should not check that entity anymore, it goes to a state that's "processing, waiting for the async computation to be completed", it will change to another state on the future completion, the state count should not increase, instead there should be a process that checks if there are entities in a "processing" state for some (configurable) time and that it applies some logic to avoid that stale state in ways that could be, e.g. retry it for some times and kill it after N retry.
I think this pattern would handle failing situations nicely.
anyway, I shared some thorough thoughts in this discussion #549

Also if this doesn't resolve all the problems, at least it will make the sample 04 work, I think it's important to merge it prior to monday since it will be shown at the workshop session in the afternoon.

I will test it regarding the sample 04 today

@ronjaquensel @florianrusch-cluetec
I managed to fix the "multiple confirmations" by adding an intermediate state between CONFIRMING and CONFIRMED, it's what usually I call "an ugly patch" but does the job, in the wait of the state machine review, this will permit a flawless demo on monday, I tried the sample 04.0 and it worked, other feedbacks are welcome

@ndr-brt I just tested sample 4 on your branch again and looks good. On the provider side I only get
DEBUG 2022-01-27T13:06:18.5138138 [Provider] ContractNegotiation initiated. db6b4616-ac5d-40c7-bc2c-2d20eef716e5 is now in state REQUESTED.
DEBUG 2022-01-27T13:06:18.5208097 [Provider] Contract offer received. Will be approved.
DEBUG 2022-01-27T13:06:18.5218082 [Provider] ContractNegotiation db6b4616-ac5d-40c7-bc2c-2d20eef716e5 is now in state CONFIRMING.
DEBUG 2022-01-27T13:06:19.127198 Response received from connector. Status 200
DEBUG 2022-01-27T13:06:19.1462043 [Provider] ContractNegotiation db6b4616-ac5d-40c7-bc2c-2d20eef716e5 is now in state CONFIRMED.

and on the consumer side I only get:
DEBUG 2022-01-27T13:06:13.7506063 [Consumer] ContractNegotiation initiated. a203bac2-ba50-42b7-8d36-88d3e4f98038 is now in state INITIAL.
DEBUG 2022-01-27T13:06:18.5628357 Response received from connector. Status 200
DEBUG 2022-01-27T13:06:18.6398487 [Consumer] ContractNegotiation a203bac2-ba50-42b7-8d36-88d3e4f98038 is now in state REQUESTED.
DEBUG 2022-01-27T13:06:19.1111958 [Consumer] Contract agreement received. Validation successful.
DEBUG 2022-01-27T13:06:19.1121933 [Consumer] ContractNegotiation a203bac2-ba50-42b7-8d36-88d3e4f98038 is now in state CONFIRMED.

Same for me ;-)

I just tried using the fix from this branch to run sample 5 and I get some exceptions.
This is from the provider (spammed in a loop)
DEBUG 2022-01-27T14:48:23.191292 [Provider] Failed to send contract agreement with id 1:1dff842f-85b9-4fff-8a19-d6f3da12d1c6. ContractNegotiation 80bb5f2f-884a-4648-bf6c-577594168def stays in state CONFIRMING.
org.eclipse.dataspaceconnector.spi.EdcException: Received an error from connector:500
	at org.eclipse.dataspaceconnector.ids.api.multipart.dispatcher.sender.IdsMultipartSender.lambda$send$0(IdsMultipartSender.java:209)
	at org.eclipse.dataspaceconnector.ids.core.message.FutureCallback.onResponse(FutureCallback.java:45)

And this is from the consumer (spammed in a loop)
Caused by: java.lang.IllegalStateException: Cannot transition from state CONFIRMED to CONFIRMED
	at org.eclipse.dataspaceconnector.spi.types.domain.contract.negotiation.ContractNegotiation.transition(ContractNegotiation.java:373)
	at org.eclipse.dataspaceconnector.spi.types.domain.contract.negotiation.ContractNegotiation.transitionConfirmed(ContractNegotiation.java:287)
	at org.eclipse.dataspaceconnector.contract.negotiation.ConsumerContractNegotiationManagerImpl.confirmed(ConsumerContractNegotiationManagerImpl.java:213)
	at org.eclipse.dataspaceconnector.ids.api.multipart.handler.ContractAgreementHandler.handleRequest(ContractAgreementHandler.java:123)
	at org.eclipse.dataspaceconnector.ids.api.multipart.controller.MultipartController.request(MultipartController.java:120)
	at jdk.internal.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52)

@DominikPinsel this is the typical hen-or-the-egg problem, we have to understand who of the two connector started flooding requests.
From what I see, the provider find the process in state CONFIRMING, try to send it to the consumer but it receive 500 because it's already CONFIRMED. I don't know if in the IDS there's a way to tell to the peer "already done, never mind" so that the process could be considered completed.
Another way to resolve it is to permit the transitions from CONFIRMED to CONFIRMED without throwing error, but that will clash with the stateCount pattern to detect failing states (not yet merged however).

I've tested it again and found maybe another problem were I'm not sure if it depends on the issues or fixes we already discussed here.
If the provider can't find the file he logs this in a loop:
INFO 2022-01-28T09:48:16.250353 Copying data from File to File
SEVERE 2022-01-28T09:48:16.250997 Error processing transfer request. Setting to retry: d861aab5-ee59-409d-8c97-e86394c24f45

But if I read the logs correctly, the consumer logs that the transfer process was completed:
DEBUG 2022-01-28T09:42:29.373446 [Consumer] ContractNegotiation initiated. 7979516d-df08-4da6-b015-3ea6a2a2bcdc is now in state INITIAL.
DEBUG 2022-01-28T09:42:31.244869 Response received from connector. Status 200
DEBUG 2022-01-28T09:42:31.353274 [Consumer] ContractNegotiation 7979516d-df08-4da6-b015-3ea6a2a2bcdc is now in state REQUESTED.
DEBUG 2022-01-28T09:42:35.266974 [Consumer] Contract agreement received. Validation successful.
DEBUG 2022-01-28T09:42:35.267726 [Consumer] ContractNegotiation 7979516d-df08-4da6-b015-3ea6a2a2bcdc is now in state CONFIRMED.

INFO 2022-01-28T09:48:07.643573 Received request for file test-document against provider http://localhost:8181/api/ids/multipart
DEBUG 2022-01-28T09:48:10.567869 Response received from connector. Status 200
INFO 2022-01-28T09:48:10.574536 Object received: org.eclipse.dataspaceconnector.ids.api.multipart.dispatcher.message.MultipartRequestInProcessResponse@36b1394a
DEBUG 2022-01-28T09:48:15.547119 Process 2ce3e43a-4180-4d9d-9c17-dd8e4949ff75 is now COMPLETED

Does this relates to the issues we had before?

@florianrusch-cluetec this problem was already in place, it's beacause the data request is not managed (so no provisioning needed), and there's no status checker implemented:
https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/69285ee2baac58e5f87dd6f1769f0172c500d59d/core/transfer/src/main/java/org/eclipse/dataspaceconnector/transfer/core/transfer/AsyncTransferProcessManager.java#L369
so the transfer process set it to completed.
I guess, to improve this, we could set the data request as managed, add a "FileResourceDefinition" that will create an empty file on the destination and a FileStatusChecker that will check if the file is not empty. Should work, let me try it out

I guess, to improve this, we could set the data request as managed, add a "FileResourceDefinition" that will create an empty file on the destination and a FileStatusChecker that will check if the file is not empty. Should work, let me try it out

That sounds like a workaround we'd better avoid or not? 🤣

I guess, to improve this, we could set the data request as managed, add a "FileResourceDefinition" that will create an empty file on the destination and a FileStatusChecker that will check if the file is not empty. Should work, let me try it out

That sounds like a workaround we'd better avoid or not? rofl

totally :D I think we are ok with this fix, setting an existing file on the provider side is a mandatory pre-requisite for the sample


What I studied today

list

[x] Using Express with TypeScript
[x] Made Simple REST API

References
https://dev.to/briandgls/using-typescript-with-express--e0k

Good job!


remark

Why is my Targets this way?

And here's what you demonstrated

There will be a bit of confusion when the client is connected much, can you add a column that can note custom information

I made a change to make -t group all the targets so it wouldnt just get endlessly long and break on small terminal sizes.
You can still get a space delimited version of ls by doing ls

There isnt a great way to set a comment like that, as Im trying to keep it in the format of the ssh authorized_keys file, you can rename your targets with the comment tho

Ok, thank you for your answer

Oh jeez, you're awesome, thanks for such a quick response , and for such an amazing tool
There seems to be a bug, there are more than 20 records each generated when viewing the history, this is the case for both linux and windows live

Was this comment suppose to go on the watch command feature request?
Could you potentially open this as a new issue, I'm not getting this problem when I use this on my Linux machine


not sorting values in an array if the array is a value of a key.

given:
let data = {
  "a": {
    "a": ["c", "b", "a"]
  }
}

running stringify(data, { space: 2 }); does not sort the array. instead, it was unsorted.
Result:
{
  "a": {
    "a": ["c", "b", "a"]
  }
}

Expected:
{
  "a": {
    "a": ["a", "b", "c"]
  }
}

Arrays imply a specific ordering, so most use cases would require that arrays do not get sorted as that would change the semantics of the object.

Indeed; I'm not sure why you'd expect it to become sorted.

If you want it sorted, it should be sorted before trying to stringify it - it doesn't really make sense to me to have a serialization option that fundamentally alters the data.


Write a Kotlin program to find the average of all numbers in an array

Description
Write a Kotlin program to find the average of all numbers in an array
Input  : [1, 2, 3, 4, 5]
Output : 3

How to contribute

Save the solution in program/FindTheAverageOfAllNumbersInAnArray.kt file
Add FindTheAverageOfAllNumbersInAnArray.kt file in find-the-average-of-all-numbers-in-an-array folder

!assign

!assign

!assign


Sometimes html2canvas doesn't catch table and fonts styles

I have an web-application built with React, I have some tables and I need to create a pdf file which contains my tables as images. I use html2canvas for creating canvas and images from html tables and jsPdf for creating PDF file.
The problem is - sometimes my image generated from canvas looks correct, but sometimes not, and there is no any dependence in appearing the problem, it looks like there are no styles for tables and fonts or they are not correct .It happens only in production mode.

it also can't support  transform

me too

same, any solution?

was this ever solved?


Recent section missing on app context menu of macOS Dock

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.94.2
OS Version: macOS 15.0.1

Steps to Reproduce:

Right click on VSCode icon on macOS Dock
The Recents files / workspace are missing on the top context menu

There's are files in File > Open Recent and "Recent" section of welcome page. I've make sure I already enabled macOS "Recent items".

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

@bpasero This bug is still happening on insider builds.
Version: 1.95.0-insider (Universal)
Commit: 912bb683695358a54ae0c67046173898

After rebooting and using it for ~5mins, the Recents files show in the Dock context menu (both public and insider builds).
So weird. 🤨


TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received undefined

The script from package.json
    ...
    "use:local": "env-cmd -f \".env.local\"",
    ...

yarn use:local
yarn run v1.22.10
$ env-cmd -f "./.env.local"
TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received undefined
    at validateString (internal/validators.js:124:11)
    at normalizeSpawnArguments (child_process.js:411:3)
    at Object.spawn (child_process.js:551:13)
    at Object.spawn (/Users/accounts-services/node_modules/cross-spawn/index.js:12:24)
    at Object.EnvCmd (/Users/accounts-services/node_modules/env-cmd/dist/env-cmd.js:59:26)
    at async Object.CLI (/Users/accounts-services/node_modules/env-cmd/dist/env-cmd.js:19:16) {
  code: 'ERR_INVALID_ARG_TYPE'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

the .env.local from same directory
DATABASE_URL="postgresql://user:password@localhost:5432/main?schema=public"

# AWS CREDENTIALS
AWS_ACCESS_KEY_ID=...
AWS_SECRET_ACCESS_KEY=......
AWS_REGION=us-west-1

PASSWORD_KEY=internal-dev-password-key
JWT_SECRET_KEY=internal-dev-jwt-secret-key

# SLACK BOT HOOK KEYS
SLACK_BOT_TOKEN=your-testing-bot-token
SLACK_AQUISITION_NOTIFICATIONS_CHANNEL_ID=C022DJ74CJD

#GITHUB CLIENT VALUES
GITHUB_CLIENT_SECRET=add-your-test-github-client-secret
GITHUB_CLIENT_ID=12345678;

# NODE_ENV
NODE_ENV=development

I am having the same issue, any update on this?

I'm having the same issue

I'm having this issue as well

Also having this issue.

Okay guys, I have the answer.
env-cmd -f .env.staging react-scripts build

env-cmd -f <my env file path> <commands for env>
We are assuming that env-cmd -f .env.staging works alone. However, you have to specify a command after it to which the environment applies.

Okay guys, I have the answer.
env-cmd -f .env.staging react-scripts build

env-cmd -f <my env file path> <commands for env> We are assuming that env-cmd -f .env.staging works alone. However, you have to specify a command after it to which the environment applies.

Thanks, i almost lost my mind because I used it with && like  env-cmd -f .env.staging && react-scripts start


Update toolbar screenshot.

@acearun We want the screenshot updating immediately with the pencil icon, correct?

Oh, that's a change from several weeks ago. We got rid of all of the icon labels.

I think he said to change it to the pencil now, then change it again when the icon change is deployed.


Text formatting/positioning of buttons on Quantum volume QED-C benchmarks page

Text formatting/positioning of "Export to CSV" and "Download to..." buttons of Quantum volume QED-C benchmarks needs cleanup.
See screenshot:

hi @WrathfulSpatula thanks for looking into this!
Yes on Chrome and Safari I still see the text running off the buttons. It can probably be inferred that it's supposed to say "download to CSV", but the file format is cut off from the "Export to" button, which could be confusing.
Is smaller text a viable option?

Misty, simplest and least invasive solution seems nonetheless, by now, to adjust the column increments (for smaller screens and windowed views) by 1. Thanks for raising it to my attention! It'll be on production, today.


Font Size isn't consistent with other editors

I have noticed that the rendered font size in VS Code is quite a bit smaller than other popular editors for the same font face. In General, I have to set a font size to 15 or 16 to match a 12 pt font in something like sublime. I Have included several screenshots of my windows 8 computer, with the monitor set to 1280x720 (to keep the images small & the differences noticeable), with side by side comparisons of VS Code, Sublime 3, and Word (for reference).
Notice that VS Code is at 16 pt font, and sublime and word are at 12pt font, and they are all darn close to showing the same # of lines. The line spacing also isn't significantly different.
My VS Code Settings

My Sublime settings

VS Code and Sublime side by side

Settings in Word

VS Code & Word Side by Side

Here I set both Sublime and VS Code to 16 pt font. The difference is stark.

And Finally, I have put the same word side by side with sublime and VS Code both at 16 pt font. Sublime has the dark background, VS Code the light one

The root cause is that our editor.fontSize is expressed in pixels (CSS pixels). I will make a change to make this clear in the setting description.


Groups

Hi,
I have no idea of react. But it works and I think it is correct.
Signed-off-by: Simon Körner<EMAIL_ADDRESS>

oh, phew - thank you for doing this! lgtm

and deployed!


CompareValidator client validation does not work with prefixed attributes

In case of using form fields with prefixed attributes, the ID of input will be model-prefix-attribute (for example bellow user-0-password). During the generation of client validation JS in CompareValidator, the compareAttribute (which have to contain ID of target input) will be set to model-password instead of model-0-password (see CompareValidator.php:219), so the JS will generate false errors during the validation.
view.php:
use yii\widgets\ActiveForm;

$form = ActiveForm::begin();
foreach ($models as $i => $model) {
    print $form->field($model, "[$i]password");
    print $form->field($model, "[$i]confirm_password");
}
$form->end();

model.php:
class User extents Model {
...
    function rules() {
        return [
            [
                    ['password'],
                    'compare',
                    'compareAttribute' => 'confirm_password',
                    'on' => ['create'],
                ],
        ];
    }
...
}

Workaround: set enableClientValidation to false in model and use ajax validation with ActiveForm::validateMultiple
And I don't know, how to pass full attribute with prefix form ActiveForm to CompareValidator

+1

:+1:

:+1:

Any ideas, team?

Verified :)

Duplicated in https://github.com/yiisoft/yii2/issues/10230

Thanks @SilverFire for your assistance in #10230. Any idea on how to solve it?

Any ideas how to fix it?
I thought before, that current client validation design may be enhanced. The main problem is that we are converting attribute names to IDs and get different problems:

We can not handle two forms of same model class on the page (DOM element ID is unique)
We are experiencing problems for validation, that depends on other attributes, especially for multiple forms with prefixed input names (as described in this issue)
It's hard to write custom JS that interacts with inputs in this item of multiple form
etc

I think that the most reliable option is to:

Add data-attribute to each input <input name="User[0][id]" data-attribute="id" />
Add a new logical container like model-item to disambiguate pointing on inputs.

For example:
<form>

      <input name="User[0][login]" data-attribute="login" />
      <input name="User[0][name]" data-attribute="name" />

      <input name="User[1][login]" data-attribute="login" />
      <input name="User[1][name]" data-attribute="name" />

</form>

Then, for example, when can easily add the following rule:
[['name'], 'required', 'whenClient' => "function (value, attribute) {
    return $(attribute).closest('.model-item').find('[data-attribute=login]').val().length > 0;
}"]

Of course, it will be easier to access login attribute of the current model-item with a proper support in yii.activeForm. For example: attribute.model.getInput('name').val().length > 0
It's a draft. Your thoughts? @yiisoft/core-developers

That's good idea. For 2.1 I've planned to make all Yii JS static so no JS is dynamically added to the page and data- attributes are used for everything.

@SilverFire, I've tried your solution but I can't get it to work.
My view:
<?php foreach($items as $i=>$item): ?>
    <tr class="model-item" data-id="<?= $i ?>">
        <?= $form->field($item,"[$i]quantity_start")->textInput(['data-attribute' => 'quantity_start'])->label(false); ?>
        <?= $form->field($item,"[$i]quantity_end")->textInput(['data-attribute' => 'quantity_end'])->label(false); ?>

<?php endforeach; ?>

My model's validation:
[['quantity_end'], 'compare', 'compareAttribute' => 'quantity_start', 'operator' => '<=', 'type' => 'number',
'whenClient' => "function (value, attribute) {
    console.log($(attribute).closest('.model-item').find('[data-attribute=quantity_start]').val());
}"],

I get undefined in my console.
What I'm doing wrong?


Add a C++ image processing library: Simd

Add a C++ image processing library: Simd
CxImag's link is no longer valid

Thanks for the patch. :)


Problem with CPU usage

It's a great library, I'm playing with it.
I want to use it to control a screen(1440X540). So, I created  a task (vTest_iChangePictur) by FreeRTOS, periodically call lv_task_handler in 5ms. I have also ported the Demo from the pc_simulator, I tracked the CPU usage rate. Not too good for me.
Logger		1402		<1%
vTest_iChangePictur		294451		83%
InputTask		0		<1%
OutputTask		0		<1%
vTest_iDMAFinish_Ta		0		<1%
IDLE		0		<1%
SchedTask		63906		15%
Ethernet_Task		5489		1%
Tmr Svc		710		<1%
I'm trying to provide an empty  ex_disp_flush  function to confirm whether the problem is caused by the underlying driver. But the results are the same.
Could you offer me some advice?
The attachment is my configuration file.
lv_conf.zip
Thank you every so much.

Hi,
What happens if you change LV_REFR_PERIOD to 500 ms?

I changed the LV_REFR_PERIOD, and do the some test.
the following is the result:

I randomly counted ten CPU usage for each LV_REFR_PERIOD.
It did change, but I didn't feel good enough.
Is there a better option?
thanks!

Thank you for the measurement!
Please try an other thing too:

Revert LV_REFR_PERIOD to 500 ms
Do not register any input devices. Often the input device driver blocks the CPU

Does it change something?

For now，I didn't register any input drivers.
void lv_display_init(void)
{
/***********************
* Initialize LittlevGL
***********************/
lv_init();
lv_disp_drv_t disp_drv;                         /*Descriptor of a display driver*/
lv_disp_drv_init(&disp_drv);                    /*Basic initialization*/

/*Set up the functions to access to your display*/
disp_drv.disp_flush = ex_disp_flush;            /*Used in buffered mode (LV_VDB_SIZE != 0  in lv_conf.h)*/

disp_drv.disp_fill = ex_disp_fill;              /*Used in unbuffered mode (LV_VDB_SIZE == 0  in lv_conf.h)*/
disp_drv.disp_map = ex_disp_map;                /*Used in unbuffered mode (LV_VDB_SIZE == 0  in lv_conf.h)*/

#if 0
/Optionally add functions to access the GPU. (Only in buffered mode, LV_VDB_SIZE != 0)/
disp_drv.mem_blend = ex_mem_blend;              /Blend two color array using opacity/
disp_drv.mem_fill = ex_mem_fill;                /Fill a memory array with a color/
#endif
/*Finally register the driver*/
lv_disp_drv_register(&disp_drv);

}

For now，I didn't register any input drivers.

Hi,
Thank for the new results!
The "core" functions like lv_obj_set_pos/size checks if the value is the same like the current and does nothing in this case. However this functionality is not added consequently in higher level function. I will review it for the next release!
Seeing your measurements there is something strange: 10 times slower screen refresh period (500 ms instead of 50 ms) leads to only  half CPU usage (30 % instead of 60 %). It seems to me not  the drawing is responsible for the high CPU usage.
I have a few other questions (please set the refresh period back to 50 ms):

What is the CPU usage if you do not refresh anything on the screen? (not create update_gauge)
What if you don't register the display driver? Now you should enable update_gauge. From this we will see the time of rendering (without transferring the image to the screen)
How did you call lv_task_handler and lv_tick_inv()?
What is the speed of your MCU?

Hi,
Thanks for your formatting.
1.yes, I have turned on compiler optimization.
2.My next plan is to use GPU.
When I use GPU, I will check the performance with the # benchmark application.
Thank you for your support and let me know more about # LV.

Okay, I'm waiting for the news. :)
On this large display the GPU should help a lot to speed up the drawing.


Game gets stuck loading a world indefinitely

Minecraft version
1.19.4
Simple Backups version
1.19.4-2.2.1
Forge version
43.2.0
The latest.log file
https://pastebin.com/GHMvSuAY
Issue description
Minecraft will not load a world, instead staying on the loading screen indefinitely.
Steps to reproduce

Open a world
Wait

Other information
The main reason I think this mod is causing it is because it seemed to be the only mod in the crash log too.
crash-2023-04-05_14.26.13-server.txt

Your MC version is 1.19.2, not 1.19.4.
Anyways, I think it was a problem that I released this file for older MC versions. I’ll just remove the tags for the old versions. If this still happens in 1.19.4, please comment here and I’ll reopen it.

There was no option to select 1.19.2, so I just chose the only 1.19 option I had

Oh true, I changed the template, sorry!


Update ordering or things

I find this ordering to be more clear IMO. I'm fine with this PR getting rejected =P

:+1: this is good, thx


5.1.x scrollbars do not scroll and exhibit strange behavior with external mice

Describe the bug

Scrolling does not scroll
Scrollbars remain visible when using an external mouse (i.e., in a desktop setup)

To Reproduce
Steps to reproduce the behavior:

Go to Storybook next branch. View the default story or the about page
See that scroll bars render strangely on in the default Storybook UI. And notice you cannot scroll on the about page.

Expected behavior

I expect the scrollbar to not have artifacts
I expect the scrollbar to scroll

Screenshots
Image of broken scrollbar:

Video recording of scrolling not working on about page:

System:

OS: Mac OSX Mojave
Device: Macbook Pro 2018
Mouse: Microsoft Intellimouse
Browser: Chrome
Version: 5.1.X

Additional context
This regression was introduced in 5.1.x. I've seen the visible scrollbars happen when simplebar is broken -- perhaps the update to simplebar-react 1.0-alpha could have caused this? This behavior does not exist in my 5.0.x Storybooks.

This behavior also shows on Windows machines.
This started to happen when I upgraded from alpha.31 to alpha.40

Hi,
SimpleBar maintainer here, I'll look into this, I think this is an upstream bug. I think I know the cause but I'm still unsure on why this is happening as the usage in Storybook seems quite straightforward.

Video recording of scrolling not working on about page:

After debugging quickly this, it seems like it's unrelated to SimpleBar and it's a z-index issue. An element on top is blocking any mouse interaction.

So after investigation, this is because SimpleBar V4 has breaking changes that have been taken into account in Storybook. Actually it's not due to the breaking changes exactly, it's just that you have hardcoded the core CSS of SimpleBar in this file so the CSS in there is outdated!
You should just have to update the CSS to the latest SimpleBar version and that should work again fine.
Thanks for using SimpleBar, please don't hesitate to file an issue in our repo if you encounter anything!

Thanks so much @Grsmto ! Much appreciated!

Having similar issue on Mac 5.1-beta0

Thanks @Grsmto 🙏. I totally forgot about that hack 😅, will have to figure out why we ended up doing that - a setting-specific reason I'm sure.

Tried to debug this using @Grsmto's suggestion to update the CSS; that ended up causing different layout bugs. @ndelangen can you lend a hand here?

I'm on it

@artyomtrityak are you on our discord by any chance?
https://discord.gg/sMFvFsG

Make sure to apply the right css properties on the host (element on which you apply SimpleBar). As it doesn't do it for you anymore (that's a breaking change on V4).
So for ex for the left sidebar it won't work unless you define max-height: 100%; on the element.

If you guys struggle let me know and I could work on a PR!
I had a quick look and was able to fix it with the tips I provided in my previous comment.

@Grsmto I'm running into a problem where (at least on my machine, I can't scroll all the way to the right, when scrolling on both axis:

I can reproduce this on http://grsmto.github.io/simplebar/examples too

@ndelangen what we can see in the video is actually the "normal" behaviour. If you check when you're testing the "Both axis + padding native" it's having the exact same behaviour.
If you apply a padding inside an overflow: auto element, the browser does not take that padding into account for the padding-right. I'm not sure exactly why but that's the native CSS behaviour!
If you want to fix this "issue" you can just apply the padding to an inner element instead of applying it on your SimpleBar host element.

browsers suck

@domyen or anyone else, are you able to confirm the issue is resolved in my PR?
https://github.com/storybooks/storybook/pull/6785

@ndelangen yes i am :)

Added theming support back in #6794. can @ndelangen or anyone confirm 🙏

w00t!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-beta.1 containing PR #6794 that references this issue. Upgrade today to try it out!
Because it's a pre-release you can find it on the @next NPM tag.
Closing this issue. Please re-open if you think there's still more to do.


Unable to dereference schema with $id 'session'

What version of Elysia is running?
latest
What platform is your computer?
MacOS 15.2 (24C101)
What steps can reproduce the bug?
Follow the tutorial where the optionalSession part gets explained.
It shows you to create optionalSession as an optional reference to the session model:
// repro of the issue without any of the tutorial context
import { Elysia, t } from "elysia";

const service = new Elysia()
  .model({
      session: t.Cookie({token: t.Number()}),
      optionalSession: t.Optional(t.Ref('session')),
    }
  )

const app = new Elysia()
  .use(service)
  .get("/", () => "Hello Elysia", {cookie: 'optionalSession',})
  .listen(3030);

console.log(`🦊 Elysia is running at ${app.server?.hostname}:${app.server?.port}`);

What is the expected behavior?
Reference should work
What do you see instead?
It throws an error: Unable to dereference schema with $id 'session'
Additional information
I worked around it by referencing the same object twice:
const cookieModel = t.Cookie({ token: t.Number() }, { secrets: 'seia' })
//
  .model({
    session: cookieModel,
    optionalSession: t.Optional(cookieModel),
  })

Have you try removing the node_modules and bun.lockb and try again yet?
Yes

Should have been fixed with 57b24c1

Fixed, and published under 1.2.7


add another component FormWithServerValidation

Reasons for making this change
Add another Component FormWithServerValidation with the ability of write custom login in onSubmit
function and based on the results of that validation we can pass errorSchema to show in the form
Checklist

[ ] I'm updating documentation

[ ] I've checked the rendering of the Markdown text I've added
[ ] If I'm adding a new section, I've updated the Table of Content

[ ] I'm adding or updating code

[ ] I've added and/or updated tests
[ ] I've updated docs if needed
[x] I've run npm run cs-format on my branch to conform my code to prettier coding style

[ ] I'm adding a new feature

[ ] I've updated the playground with an example use of the feature

Add a new component FormWithServerValidation


Sprite height/width @setters

In the app I am coding, I need to work with pixel sizes, not with scale. Seems to work now like this:
sprite = pyglet.sprite.Sprite(img=image)
sprite.width = 1920
sprite.height = 1440

Currently width/height are read-only.

I don't think there is a case where _scale is negitive, is there?

I don't think there is a case where _scale is negitive, is there?

There is. Negative scale is a quick way of mirroring along the X and Y axes, or only one axis if you only alter scale for one dimension.
The downside is that it produces negative apparent widths if handled naively. Using abs ensures meaningful return values which can be used for layout and packing.

I just used the formula to get width from scale:
width = self._texture.width * abs(self._scale_x) * abs(self._scale)

to get the scale from width (or height). As said by @pushfoo, a negative scale/width (or height) mirror the sprite.

This looks like a reasonably useful change, and doesn't break anything. Thanks for the PR.


How to disable stemcell image decompression for grootfs?

Initially I reported a bug report in grootfs project, but detailed debugging showed that it is a bosh-warden-cpi-release issue.
It looks like warden-cpi always decompresses a stemcell image.
I cannot create an instance because grootfs complain on directory structure. It expects to see a tar archive:
Creating VM with agent ID '{{eb2931fc-1e68-44ef-8492-876b7f01647f}}': Creating container: running image plugin create: invalid base image: directory provided instead of a tar file

How can I disable decompression feature?

Fixed by setting the ExpandStemcellTarball to false.

Was this fixed within a release or by specifying the above? If the above, how would I go about setting that property? Thanks

- type: replace
  path: /instance_groups/name=bosh/properties/warden_cpi?
  value:
    host_ip: <IP_ADDRESS>
    actions:
      expand_stemcell_tarball: false
    warden:
      connect_network: tcp
      connect_address: <IP_ADDRESS>:7777
    agent: # todo remove once cpi dont know about these
      mbus: nats://nats:((nats_password))@<IP_ADDRESS>:4222
      blobstore:
        provider: dav
        options:
          endpoint: http://<IP_ADDRESS>:25250
          user: agent
          password: ((blobstore_agent_password))


Publishing link is broken

+1

+1

Now exists here: https://github.com/preboot/angular2-library-seed/blob/master/PUBLISHING.md


gsl linked failed.

I'm trying to reproduce the tools, but link failed in my code, the error is below.  slopt succeussfully compiled and my code is same as slopt.
/usr/bin/ld: /tmp/ccdS8ocE.o: warning: relocation against `gsl_rng_default' in read-only section `.text'
/usr/bin/ld: /tmp/ccdS8ocE.o: in function `afl_state_init':
/home/paper/Desktop/final/src/afl-fuzz-state.c:122: undefined reference to `gsl_rng_env_setup'
/usr/bin/ld: /home/paper/Desktop/final/src/afl-fuzz-state.c:123: undefined reference to `gsl_rng_default'
/usr/bin/ld: /home/paper/Desktop/final/src/afl-fuzz-state.c:123: undefined reference to `gsl_rng_alloc'
/usr/bin/ld: warning: creating DT_TEXTREL in a PIE
collect2: error: ld returned 1 exit status
make: *** [GNUmakefile:450: afl-taint] Error 1

Hello, Ricardo.
Did you install libgsl?
Also, since we provide Docker images for build and you didn't modify the code, you can just use our docker image.


Added Android project

Added a Pokemon Quiz app built in Kotlin.

Hey @Seew0 I'm facing some conflicts while Making pr for my other web project as in pr#2, so you can consider merging this branch as of now.

@Heismanish It would be great if you can add some screenshots of your app while making the PR and try to add an https://appetize.io/ link of your app too.


HoldTillRename: Rename knative-sandbox to knative-extension

This is an automated PR to replace knative-sandbox strings to knative-extension. Do not merge until productivity renames knative-sandbox org to knative-extension.

changed to extensions


Auto Dashboard releases

Fixes #118

This should work after we get the change in the release-script. Now working on adding the github-action.

This should work after we get the change in the release-script. Now working on adding the github-action.

hmm, its failing for me at my local desk
><EMAIL_ADDRESS>dashboardRelease
> ts-node scripts/dashboard-release.mts

(node:68745) ExperimentalWarning: Importing JSON modules is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
file:///Users/nl69zh/Developer/community/opensource/ioBroker.esphome/scripts/dashboard-release.mts:42
    const response = await fetch('https://api.github.com/repos/esphome/esphome/releases')
                     ^
ReferenceError: fetch is not defined
    at getLatestDashboardVersion (file:///Users/nl69zh/Developer/community/opensource/ioBroker.esphome/scripts/dashboard-release.mts:42:22)
    at run (file:///Users/nl69zh/Developer/community/opensource/ioBroker.esphome/scripts/dashboard-release.mts:15:50)
    at file:///Users/nl69zh/Developer/community/opensource/ioBroker.esphome/scripts/dashboard-release.mts:47:7
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

This should work after we get the change in the release-script.

what change do we need? script itself runs great nice job!

what change do we need? script itself runs great nice job!\n\nedit: Understood, related to AlCalzone/release-script#154

Yes and no. Only seems to run fine. Because when you look at the script you can see that the actuall running of the release script is commented out for now so that i can test the rest.
And you already found the release script pr..
If you arent in a rush to add this feature instantly i would for now jsut leave this as it is and wait a bit to see if upstream gets merged,
otherwiese i could temporarily add some overidde for the upstream compile changelog-plugin.

If you arent in a rush to add this feature instantly i would for now jsut leave this as it is and wait a bit to see if upstream gets merged,

no rush I think the current concept and PR is the right way to go. Let's wait for feedback by maintainer of release script and follow-up.
Nice journey anyway, automated update/integration and suggestion for release script covered by an automated action.... like it

hmm, its failing for me at my local desk\n\nEdit: solved by 76d2b15

I dont know if its necessary to introduce another dependency as node 16 is already EOL and its run only inside the github action anyway , so the end user of the adapter does not need node18.

hmm, its failing for me at my local desk\n\nEdit: solved by 76d2b15

I dont know if its necessary to introduce another dependency as node 16 is already EOL and its run only inside the github action anyway , so the end user of the adapter does not need node18.

Only temporary so I am also able to run it locally until my it department finally deploys 18+ 😅

Nice journey anyway, automated update/integration and suggestion for release script covered by an automated action.... like it

yeah I may kind of tend to "overengineer" my contributions - sometimes simple bugs led me to things that i think can be improved and then it may escalate a bit :D.
for the esphome adapter my original issue was that I updated to debian 12 => new python version => broke the dashboard. and then, well stuff happened... :smile: .
Also always trying to get fixes upstreamed to help others (release script, actually also fixed typescript types for the client class in the nativeapi - dependency still needs to be updated here), ....
Had I similar journey a few months ago where another project had a dependency that updated which broke a template because the dependency changed from a default export to a named one.
So basically all I would have needed to do was change something like import func from 'dep' to import { func } from 'dep' in my code generated from the template. and well. ... I ended up fixing some stuff end re-writing the whole project generator to be in es-module format ...

Only temporary so I am also able to run it locally until my it department finally deploys 18+ 😅

Well... Good that I have root / sudo access to all of my devices :smile:

If you arent in a rush to add this feature instantly i would for now jsut leave this as it is and wait a bit to see if upstream gets merged,

no rush I think the current concept and PR is the right way to go. Let's wait for feedback by maintainer of release script and follow-up. Nice journey anyway, automated update/integration and suggestion for release script covered by an automated action.... like it

@DutchmanNL
Does the new implementation in the adapter directlly: https://github.com/DrozmotiX/ioBroker.esphome/issues/118#issuecomment-1837538091 mean this is now useless?


feat(topology): add permissions to topology plugin

Description
This PR adds permissions to the Topology plugin. These permissions, topology.panel.read and topology.view.read, to restrict access to the Topology plugin. Permission topology.view.read will limit access to the Topology view, see below. Permission topology.panel.read will limit access to the Topology sidebar.
Fixes

Fixes: RHIDP-1794

Screenshots
Edit - Removed the topology.panel.read permission per the suggestion from @divyanshiGupta. We concluded that limiting the topology view would be sufficient. So the screenshots for the sidebar are no longer relevant at this time. Leaving them up though in case there is further discussions.
topology.view.read

allow

deny (used TopologyEmptyState because the approach is similar to catalog.entity.read showing an empty state when navigating to the catalog when set to deny)
topology.panel.read

allow (details tab)

allow (resources tab)

deny (tabs are disabled) (went with the EmptyState from patternfly and passed in the text Unauthorized: Unable to view data, didn't know what text to include and whether or not we should use the TopologyEmptyState)
catalog.entity.read

allow

deny (before reload of browser)

deny (after reload of browser, view is originating from catalog plugin)
Special notes for the Review
How to test

Configure the Topology plugin, Kubernetes plugin, Kubernetes Backend plugin
Create a policy csv file for the permission policiesg, user:default/<YOUR_USERNAME>, role:default/topology

p, role:default/topology, topology.panel.read, read, allow
p, role:default/topology, topology.view.read, read, allow
p, role:default/topology, catalog-entity, read, allow

Configure the RBAC Backend pluginpermission:
  enabled: true
  rbac:
    policies-csv-file: ../<PATH>/<TO>/<CSV>/rbac-policy.csv
    policyFileReload: true

Ensure auth is configured
Ensure that there is a cluster to connect to, a deployment and catalog entity that can be referenced, and a user that you can sign into in the catalog
View the Topology side for you deployed catalog entity
Change above permission policies to denied and reload to restrict access

This is marked as a draft to get review and sign off on UI / UX / and the RBAC Backend team. I took the approach of getting everything implemented prior to getting review on how we want it to look because of the priority. Most of the changes are probably where we want them. The biggest things that need review are the text and whether we want to use an empty state or something more customized.
@ShiranHi @invincibleJai @divyanshiGupta @AndrienkoAleksandr

@PatAKnight it looks good. I have three questions regarding the content displayed when permission is denied:

deny (used TopologyEmptyState because the approach is similar to catalog.entity.read showing an empty state when navigating to the catalog when set to deny)
Can we change the text to be:
Title: Permission required
Text: To view Topology, contact your administrator to give you catalog.entity.read permission.

deny (before reload of browser)
Can we change the text in the tab to be "Permission required to view data."
I'm also curious about the image there. Where did it come from? I don't find it helpful 🤔

deny (after reload of browser, view is originating from catalog plugin)
Is this a default empty state page? Can we improve it to be a full empty state like this one?

Can we change the text to be: Title: Permission required Text: To view Topology, contact your administrator to give you catalog.entity.read permission.

Yeah, I can either expand upon the TopologyEmptyState to include additional options for denial text or create a separate TopologyDeniedState that covers the change in text. @divyanshiGupta What do you think?

Can we change the text in the tab to be "Permission required to view data." I'm also curious about the image there. Where did it come from? I don't find it helpful 🤔

I had a conversation with @divyanshiGupta the other day in which we agreed to remove the additional permission topology.panel.read. That permission was originally to block access to the sidebar that you are seeing there. It is no longer relevant. I can update the PR to remove those images, if that would help.

Is this a default empty state page? Can we improve it to be a full empty state like this one?

Yes, that is the default empty state page after the catalog-entity read permission has been set to deny. It blocks all access to the resource. And is coming from the catalog plugin

Can we change the text to be: Title: Permission required Text: To view Topology, contact your administrator to give you catalog.entity.read permission.

Yeah, I can either expand upon the TopologyEmptyState to include additional options for denial text or create a separate TopologyDeniedState that covers the change in text. @divyanshiGupta What do you think?

+1 for expanding the TopologyEmptyState and making it more generic so that it can be used for both usecases.

Can we change the text in the tab to be "Permission required to view data." I'm also curious about the image there. Where did it come from? I don't find it helpful 🤔

I had a conversation with @divyanshiGupta the other day in which we agreed to remove the additional permission topology.panel.read. That permission was originally to block access to the sidebar that you are seeing there. Since I removed it, the image is now out of date. I can update the PR to remove those images, if that would help.

+1

@PatAKnight the kubernetes plugin has a permission that can be setup for limiting access for viewing pod logs. Users can also see pod logs from topology node sidebar. So should we have a similar permission here as well?

@divyanshiGupta We are actually already utilizing the permission from the Kubernetes plugin. The kubernetesProxyApi is already protected by the Kubernetes proxy permission here. But I will go in and add it to the docs in the Topology plugin and the RBAC plugin to make sure users are aware that the Topology plugin uses that permission as well.

Updated screenshot

And updated the docs with the inclusion of kubernetes.proxy, use permission


Symbols in Tables named "Bold Italic, Latin" are not italic, in unimath-symbols.pdf

Description
The two symbol tables (sec 13.2.5 and 13.2.6 of unimath-symbols.pdf) named "Bold Italic, Latin, uppercase/lowercase" are not italic. The actual symbols in these two tables are the same as symbols in tables "Bold, Latin, uppercase/lowercase".
Check/indicate

[ ] Relevant for XeTeX
[ ] Relevant for LuaTeX
[x] Issue tracker has been searched for similar issues?
[ ] Links to <tex.stackexchange.com> discussion if appropriate

The mentioned symbols in the latest unimath-symbols.pdf (released with unicode-math v0.8p) look ok.


Live Editor is broken

Describe the bug
Since the update to 8.3.0 the live editor reports parsing error after editing code.
To Reproduce
Steps to reproduce the behavior:

Go to Live Editor
Click into the 'Code' field
Add space somewhere
See error

Expected behavior
See parsed chart
Screenshots

Desktop (please complete the following information):

OS: MAC OS, Windows 10
Browser Firefox, Chrome
latest Version

This has been fixed in 8.3.1. Please verify this and comment/close accordingly. Thanks.


[Task]: Use all fields when comparing examples on frontend

What needs to happen?
Currently in ExampleBase only path is used to compare examples.
This makes tests to compare example objects more complex than they should be.
Need to:

Refactor current comparison cases to only compare path if this is what they really should do.
Include all (or most of the) fields in comparison.

Issue Priority
Priority: 3
Issue Component
Component: beam-playground

.take-issue


bug: Application tried to present modally a view controller <UIViewController: 0x10392e710> that is already being presented by <Capacitor.CAPBridgeViewController: 0x10390bf60>.

Plugin version: 4.2.1

Platform(s): iOS

Current behavior:

App crashes
Expected behavior:

Steps to reproduce:

Seeing this crash log in crashlytics
Related code:

Fatal Exception: NSInvalidArgumentException
0  CoreFoundation                     0xed5e0 __exceptionPreprocess
1  libobjc.A.dylib                    0x2bc00 objc_exception_throw
2  UIKitCore                          0x7795f8 -[UIViewController _presentViewController:withAnimationController:completion:]
3  UIKitCore                          0x779d64 __63-[UIViewController _presentViewController:animated:completion:]_block_invoke_2
4  UIKitCore                          0x42218 +[UIView(Animation) performWithoutAnimation:]
5  UIKitCore                          0x779ce4 __63-[UIViewController _presentViewController:animated:completion:]_block_invoke
6  UIKitCore                          0x779f6c -[UIViewController _performCoordinatedPresentOrDismiss:animated:]
7  UIKitCore                          0x779bd8 -[UIViewController _presentViewController:animated:completion:]
8  UIKitCore                          0x77a028 -[UIViewController presentViewController:animated:completion:]
9  CapacitorCommunityPrivacyScreen    0x4b08 closure #1 in PrivacyScreen.handleWillResignActiveNotification() + 44 (PrivacyScreen.swift:44)
10 CapacitorCommunityPrivacyScreen    0x41b4 thunk for @escaping @callee_guaranteed () -> () (<compiler-generated>)
11 libdispatch.dylib                  0x26a8 _dispatch_call_block_and_release
12 libdispatch.dylib                  0x4300 _dispatch_client_callout
13 libdispatch.dylib                  0x12998 _dispatch_main_queue_drain
14 libdispatch.dylib                  0x125b0 _dispatch_main_queue_callback_4CF
15 CoreFoundation                     0x379bc __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
16 CoreFoundation                     0x346c8 __CFRunLoopRun
17 CoreFoundation                     0x33e18 CFRunLoopRunSpecific
18 GraphicsServices                   0x35ec GSEventRunModal
19 UIKitCore                          0x22f2fc -[UIApplication _run]
20 UIKitCore                          0x22e938 UIApplicationMain
21 Bakai24                            0x93f8 main + 7 (AppDelegate.swift:7)
22 ???                                0x1b4277d44 (Missing)

Other information:

Device Model:iPhone 14 Pro
Operating System Version:17.0.3
Capacitor doctor:

💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 5.5.1
  @capacitor/core: 5.5.1
  @capacitor/android: 5.5.1
  @capacitor/ios: 5.5.1

Installed Dependencies:

  @capacitor/cli: 5.5.1
  @capacitor/core: 5.5.1
  @capacitor/android: 5.5.1
  @capacitor/ios: 5.5.1

[success] iOS looking great! 👌
[success] Android looking great! 👌

can it be fixed with code below?
@objc public func handleWillResignActiveNotification() {
    guard self.isEnabled, !self.privacyViewController.isBeingPresented else {
        return
    }
    DispatchQueue.main.async {
        self.plugin.bridge?.viewController?.present(self.privacyViewController, animated: false, completion: nil)
    }
}

Does the problem still exist with the latest version?


no network in production, Failed to download PyTorch native library

production environment have no Internet access. how to make ai.djl work ?
my sbt dependencies:
"ai.djl" % "api" % "0.14.0",
"ai.djl.pytorch" % "pytorch-engine" % "0.14.0",
"net.java.dev.jna" % "jna" % "5.8.0",

classes I'm using:
Model.newInstance.newPredictor
NDList
Translator

error:
        ...
	at org.apache.spark.deploy.yarn.ApplicationMaster
Caused by: java.net.SocketException: Network is unreachable (connect failed)
        ...
	at ai.djl.pytorch.jni.LibUtils.downloadPyTorch(LibUtils.java:412)

workaround:
java -DENGINE_CACHE_DIR=xxx  and copy xxx manually to runtime environment.

@yinrong
You can install engine specific jar as your dependency, for example to include linux pytorch native library:
<dependency>
    <groupId>ai.djl.pytorch</groupId>
    <artifactId>pytorch-native-cpu</artifactId>
    <classifier>linux-x86_64</classifier>
    <scope>runtime</scope>
    <version>1.9.1</version>
</dependency>

See: https://github.com/deepjavalibrary/djl/tree/master/engines/pytorch/pytorch-engine#linux
If you distribute to multiple os/GPU system, and you don't care about the distribution size, you can include multiple pytorch-native-xxx.jar files in your distributon.

@frankfliu may I comiple native lib by myself?  still NOT working with dependency pytorch-native-cpu and pytorch-native-cpu-precxx11
Caused by: java.lang.UnsatisfiedLinkError:
/home/work/.djl.ai/pytorch/1.9.1-20211025-cpu-linux-x86_64/0.14.0-cpu-libdjl_torch.so:
/lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found
(required by /home/work/.djl.ai/pytorch/1.9.1-20211025-cpu-linux-x86_64/0.14.0-cpu-libdjl_torch.so)

buid.sbt
libraryDependencies ++= Seq(
  "ai.djl" % "api" % "0.14.0",
  "ai.djl.pytorch" % "pytorch-engine" % "0.14.0",
  "net.java.dev.jna" % "jna" % "5.8.0",
  "ai.djl.pytorch" % "pytorch-native-cpu" % "1.9.1" % "runtime" classifier "linux-x86_64",
)

unzip -l .out/xxx.deps.jar |grep djl|grep linux
  2752600  01-01-2010 00:00   jnilib/linux-x86_64/cpu-precxx11/libdjl_torch.so
  2850072  01-01-2010 00:00   jnilib/linux-x86_64/cpu/libdjl_torch.so
  3074520  01-01-2010 00:00   jnilib/linux-x86_64/cu102/libdjl_torch.so
  3074520  01-01-2010 00:00   jnilib/linux-x86_64/cu111/libdjl_torch.so

spark-submit ... \
--class com.aaa.DeepPredTest --jars \
hdfs://zjyprc-hadoop/user/s_ya/jar/xxx.deps.jar  \
hdfs://zjyprc-hadoop/user/s_ya/jar/xxx.jar

@yinrong Which version of linux are you using?
With DJL 0.15.0-SNAPSHOT version, you can set environment variable to point to where to load libtorch.so file:
PYTORCH_LIBRARY_PATH=/...
PYTORCH_VERSION=1.9.1

But the minimal glibc ABI version that python can support is: CXXABI_1.3.9  . I really doubt if you can build your own libtorch 1.9.1 if the system is that old.

@yinrong A couple of questions regarding your dependency

You are not using pytorch-native-cpu-precxx11, you must only include pytorch-native-cpu-precxx11 if you are running on ubuntu 16.04
I didn't see libtorch.so in your jar file, can you check if the file is extracted properly in the cache directory?

can I change setting by Model constructor, other than java property or system environment ? because I'm using spark / scala on a public yarn cluster, where environment can not change. (unless public decision is made)
my production servers: 3.18.6-2.el7.centos.x86_64

pytorch-native-cpu-precxx11 should work on centos7, we have customer running DJL with pytorch on Spark with centos7

I will get back with more info next week.

@frankfliu thanks.  the problem is sbt runtime scope is a little tricky to use. djl is good.


Need to terminate a CTRL-C event gracefully

When I am waiting for a test that I know will fail…….and I CTRL-C cancel.  During the next test run, the browser doesn’t launch….I need to kill the terminal window, restart another terminal and trigger the test.
This has happened many times.  Is there away I can avoid launching a new terminal window.

Pasting Dave's note: "probably we need to catch the CTRL-C event and gracefully terminate all child processes. "


Input组件使用溢出零点几的像素

tdesign-flutter 版本
^0.1.5
重现链接
wu
重现步骤
import 'package:flutter/material.dart';
import 'package:tdesign_flutter/tdesign_flutter.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    // ignore: avoid_print
    return MaterialApp(
      home: Scaffold(
        body: Center(
            child: Column(
          children: [
            TDInput(
              leftLabel: '标签文字',
              backgroundColor: Colors.white,
              hintText: '请输入文字(选填)',
              onChanged: (text) {},
              onClearTap: () {},
            ),
          ],
        )),
      ),
    );
  }
}

期望结果
解决溢出问题
实际结果
A RenderFlex overflowed by 0.000122 pixels on the right.
Flutter版本
Flutter 3.22.2
设备与机型信息
Android 14& android 8
系统版本
no
补充说明
`Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
√ Built build\app\outputs\flutter-apk\app-debug.apk
Connecting to VM Service at ws://<IP_ADDRESS>:51044/GYHnC4rTWWQ=/ws
════════ Exception caught by rendering library ═════════════════════════════════
The following assertion was thrown during layout:
A RenderFlex overflowed by 0.000122 pixels on the right.
The relevant error-causing widget was:
Row Row:file:///C:/Users/LS/AppData/Local/Pub/Cache/hosted/pub.dev/tdesign_flutter-0.1.5/lib/src/components/input/td_input.dart:269:24
The overflowing RenderFlex has an orientation of Axis.horizontal.
The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and black striped pattern. This is usually caused by the contents being too big for the RenderFlex.
Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size.
This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView.
The specific RenderFlex in question is: RenderFlex#e5583 relayoutBoundary=up9 OVERFLOWING
parentData:  (can use size)
constraints: BoxConstraints(w=65.0, 0.0<=h<=Infinity)
size: Size(65.0, 56.0)
direction: horizontal
mainAxisAlignment: start
mainAxisSize: max
crossAxisAlignment: center
textDirection: ltr
verticalDirection: down
child 1: RenderConstrainedBox#b5f8d relayoutBoundary=up10
parentData: offset=Offset(0.0, 28.0); flex=null; fit=null (can use size)
constraints: BoxConstraints(unconstrained)
size: Size(0.0, 0.0)
additionalConstraints: BoxConstraints(w=0.0, h=0.0)
child 2: RenderConstrainedBox#5c308 relayoutBoundary=up10
parentData: offset=Offset(0.0, 0.0); flex=null; fit=null (can use size)
constraints: BoxConstraints(unconstrained)
size: Size(65.0, 56.0)
additionalConstraints: BoxConstraints(0.0<=w<=81.0, 0.0<=h<=Infinity)
child: RenderPadding#f5eb1 relayoutBoundary=up11
parentData:  (can use size)
constraints: BoxConstraints(0.0<=w<=81.0, 0.0<=h<=Infinity)
size: Size(65.0, 56.0)
padding: EdgeInsets(0.0, 16.0, 0.0, 16.0)
textDirection: ltr
child: RenderFlex#94b94 relayoutBoundary=up12
parentData: offset=Offset(0.0, 16.0) (can use size)
constraints: BoxConstraints(0.0<=w<=81.0, 0.0<=h<=Infinity)
size: Size(65.0, 24.0)
direction: vertical
mainAxisAlignment: start
mainAxisSize: max
crossAxisAlignment: center
verticalDirection: down
child 1: RenderParagraph#497ba relayoutBoundary=up13
parentData: offset=Offset(0.0, 0.0); flex=null; fit=null (can use size)
constraints: BoxConstraints(0.0<=w<=81.0, 0.0<=h<=Infinity)
size: Size(65.0, 24.0)
textAlign: start
textDirection: ltr
softWrap: wrapping at box width
overflow: clip
locale: en_US
maxLines: 2
child 3: RenderConstrainedBox#ff4d5 relayoutBoundary=up10
parentData: offset=Offset(65.0, 28.0); flex=null; fit=null (can use size)
constraints: BoxConstraints(unconstrained)
size: Size(0.0, 0.0)
additionalConstraints: BoxConstraints(w=0.0, h=0.0)
child 4: RenderConstrainedBox#d3338 relayoutBoundary=up10
parentData: offset=Offset(65.0, 28.0); flex=null; fit=null (can use size)
constraints: BoxConstraints(unconstrained)
size: Size(0.0, 0.0)
additionalConstraints: BoxConstraints(w=0.0, h=0.0)
◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤
`

改过了，等新版本

0.1.6版本已修复


Deleting typo

'increment' instead of 'increament'

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks for the contribution, @VedranaR


Collections and IIIF

Request from Special Collections: can we set up the IIIF viewer for Collections so that a user can swipe through every image in the collection, even if the images come from different records and different resource types?
-Related: when there is no associated image for a record, will there be resource type-specific icon placeholders? (e.g., a document icon, photo icon, movie icon)

Thanks for the input. I am merging this with #270 .
There will not be a default icon for a record with no images. That record would be skipped. We are not planning on incorporating an image to the record/search results like in DigitalHub anymore (currently).


Issue using @apply with Nuxt.js

I have upgraded to the newest beta version and there is an issue with compiling css on a Nuxt.js project.
I have this line in the nuxt.config.js: css: ['~/assets/css/app.scss'].
Here is the tailwind.config.js file I use: tailwind.config.js
Here is the postcss.config.js I use: postcss.config.js
Here is the app.scss that should be compiled: app.scss
Here is the _buttons.scss where the issue happens:
.btn {
    @apply px-6 py-2 rounded-sm inline-block text-white text-2xs no-underline;
}

I get this error: "@apply" cannot be used with ".px-6" because ".px-6" either cannot be found ... .
This wasnt the case before upgrading, so it must be an issue with the newest release.
Thanks for your work on this amazing library Adam!

Not sure what the issue is, can you share the whole project?
Here is a Nuxt project with v1.0.0-beta.3 installed that worked as expected:
https://github.com/adamwathan/tailwind-1-nuxt-test

okay, so I found the issue. Instead of using padding: theme => theme('spacing'); I was using padding: theme => theme.spacing; because the old defaultConfig.js was referenced in the upgrade guide when I did the migration.
Sorry for the inconvenience Adam, you can close the issue now.

I have soimiliar issue. What is padding: theme => theme.spacing? I need to write this manually in config? What config do I need? Upgrade guide is so obscure.

@bdrtsky the padding: theme => theme.spacing was used in the config for the 1.0.0 beta1 version, but it changed to theme => theme('spacing'); in the latter version, which is why I had the issue, so I changed the values where the same issue was and then it worked. You should just follow the newest config values and change to reflect your needs.

ok, then what is theme => theme('spacing');. I have to writeit in config myself? Why do I needd it if this is default setting.

This is the case when you use your own custom config. I would suggest you copy the default config and then edit the values to fit your needs. Here is the default config for the latest version defaultConfig.stub.js

ok, then what is theme => theme('spacing');

https://next.tailwindcss.com/docs/theme#referencing-other-values

I have to writeit in config myself? Why do I needd it if this is default setting.

If you are upgrading an old config file to the new config file, then yes you have to type the new defaults yourself. We are working on a tool to automatically upgrade people's config files but it's not quite ready.

Upgrade guide is so obscure.

Can you show me a section that is unclear? I spent probably 30 hours writing it and making sure it walks through every single character you need to type step-by-step, so if you just read it and make the changes as you go it should go fairly smoothly.


Question: setting limit - higher value, less posts

Hi!
First of all, nice plugin. The only little issue is that all your tokens are just in de JS so everyone can see them; or is there a solution for that?
The real question: I don't really understand the setting 'limit' of social media channels. I'm using 3 channels (facebook, twitter and instagram) and I've set the limit of all 3 on 200. Then I get 336 post in total (I count the html elements). But, if I set an higher value for the limit (ex. 500) I only get 226 post back... What's the system? It also seems some post are not showing up (ex. instagram post from link)
Can you explain why it is like that? Or what I'm doing wrong?
Thx!
http://staging.karlienfabre.be/bas/timeline.php
https://instagram.com/p/smeuwBmYCW

Dear Karlienfabre,
I think the reason for such an error is that the social-feed is not
designed for the big feeds. Social-feed gets data from social-networks in
paginated JSONS. Social-feed does not parse the pages, but shows only the
posts from the first page.
Why there are 226 posts if you request more - to be honest, I don't know. I
suggest you to localize the problem and to check which social-network
exactly gives less posts (i guess it is Facebook). If it is Facebook - i
don't know the reason why does it work like this, the logic of how the open
graph api retrieves posts is not defined well anywhere.
Please feel free to investigate the issue and possibly contribute with your
solution. I am very happy to accept your pull-request.
On Tue, Mar 10, 2015 at 12:42 AM karlienfabre<EMAIL_ADDRESS>wrote:

Hi!
First of all, nice plugin. The only little issue is that all your tokens
are just in de JS so everyone can see them; or is there a solution for that?
The real question: I don't really understand the setting 'limit' of social
media channels. I'm using 3 channels (facebook, twitter and instagram) and
I've set the limit of all 3 on 200. Then I get 336 post in total (I count
the html elements). But, if I set an higher value for the limit (ex. 500) I
only get 226 post back... What's the system? It also seems some post are
not showing up (ex. instagram post from link)
Can you explain why it is like that? Or what I'm doing wrong?
Thx!
http://staging.karlienfabre.be/bas/timeline.php
https://instagram.com/p/smeuwBmYCW
—
Reply to this email directly or view it on GitHub
https://github.com/pavelk2/social-feed/issues/71.


Reformated due to OCD

from list() to []
passed in black
tested and seems to work without an issue

The code is structured exactly as I intended. Based on PEP8.


node_tests: Fix (non-fatal) error from i18n test

This was missed in commit cef2ecf00445fcff6ea40ddb910ffa3ddd3c5bbf (#18252).

lgtm, feel free to merge once CI passes.


[Task]: Delete profile folder whether it exist at bindings plugin

There is an issue reported when importing Stronghold snapshot with the error: The password is wrong. When the password is the correct one.
This happens when the profile folder exist, delete it and test if it fixed.
check asyncDeleteStorage()

I've been testing it, seems the folder is deleted as expected. The reported issue maybe could be related to previous app versions where there was a conflict with rename profile folder. I'll put on hold this task with the aim to reproduce it later if it's possible.


pyproject.toml does not appear to be supported

The generator mentions using requirements.txt.  However, the Python community is moving away from using requirements.txt to integrating the build system and all requirements into a pyproject.toml file.  Any chance this will be added to gh-python-generate-sbom?

@ciresnave - version 1.1.0 has been released today which adds support for poetry.lock parsing.
See https://pypi.org/project/cyclonedx-bom/ for details - would be great to get your feedback.


Should have native Typescript binding support

Is the work here to create Typescript types for the Kafka event?

Yes - I suggest to have Javascript / Typescript binding support for next implementation.

@kennetham can we get an update on the status of this, please

Closed by #133


Confusing use of Task Name: BPMN vs endpoints

Description
Consider the following config:

So the task name Must have no spaces.
If you arrive on this task the /tasks endpoint returns something like:
[
  {
    "id": "3c5ed889-65c1-4120-8de4-bb0fd29e4130",
    "name": "Row2Task",
    "state": 0,
    "phase": "active",
    "phaseStatus": "Ready",
    "parameters": {},
    "results": {}
  }
]

The confusion is the name property. The name prop showing the value in the "Task Name" property in the BPMN.  But this is not a unique value, and is a ~system value rather than a human value to display in a task list.
Implementation ideas
No response

The idea was that the "name" field in the task list returned by GET api can be used as path param for task endpoints as described here https://blog.kie.org/2021/05/kogito-user-tasks-process-api.html. Indeed, that name is unique and has nothing to be with the "name" property in the editor (which is just intended for visualization purposes)
When choosing the name of the field "Task Name" seemed redundant, hence the most short "name".
Due to the fact that is needed for pseudo HATEOAS (that name is part of the task URI) and that changing it will break backward compatibility, that name field must stay.
So,the question is;
should we display in that list the name used in the visual editor to make easier the identification of the task? I though no, but since you, a smart user, got confused, I'm now tempted to say that we can add an additional field called "visual name" that shows it.

well first it would see that "Task Name" in the modeler should be renamed to something like URI ID or equivalent.  But see https://github.com/kiegroup/kogito-tooling/issues/775 for further issues in this same space.

yes, I agree, that can be renames to "Task Id" and uniqueness enforced in the editor

Also, I have created JIRA for making the server fail if a process contains the same task name https://issues.redhat.com/browse/KOGITO-6592


Fix formulae parsing issue

Possible fix for https://github.com/Homebrew/homebrew-bundle/issues/822

Thanks @astromonkee!


Fix #584

Does this affect resource-level search as well as global?

Yes, it originally broke resource-level search, that's fixed now.


OSX: Support keyboard shortcuts like CMD+Q, etc.

OSX: Support keyboard shortcuts like CMD+Q, etc.

Is it fixed? I still have this problem.. Command q doesn't work in my Kivy App on OS X.