Migrate Composer index.ios.js to function component

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/16128#issuecomment-1627787100
PROPOSAL:
Tests

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

Offline tests

QA Steps
This PR updated the composer related to text input on iOS. So make sense to test it fully
Test Case 1: Input Functionality

Input random characters in the text box and verify that the entered characters are correctly displayed.
Try to input various types of text, such as emojis, special characters, numbers, and a mixture of these.
Check for proper functionality in both normal and capitalized modes.

Test Case 2: Multiline Input Functionality

Try to input a multiline text in the text box.
Verify that the text formatting (like new lines, spaces, etc.) is correctly retained and displayed.
Check the scrolling functionality for multiline inputs.

Test Case 3: Focus Functionality
-Switch between the text box and the emoji picker multiple times, and verify that the focus is correctly switched each time.
-Verify that the text box regains focus when coming back from the emoji picker.
Test Case 4: Style Functionality

Try to input a text that should trigger style changes (like shrinking or expanding).
Verify that the style changes are correctly displayed.
Check if these changes are retained when switching between different interfaces (like going to the emoji picker and coming back).

Test Case 5: Message Sending Functionality

After inputting a message, hit the send button and verify that the message is sent.
Verify that the text box is cleared after the message is sent.
Check if the sent message is correctly displayed in the chat history.

[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 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

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS
https://github.com/Expensify/App/assets/48593211/e4cb1e67-bd6b-44de-a0f3-8d1ce6bdee22

Android

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] 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)

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

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

[x] 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
[x] I verified proper code patterns were followed (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] 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 verified that this PR follows the guidelines as stated in the Review Guidelines
[x] 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)
[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] 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] 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 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

iOS
https://github.com/Expensify/App/assets/85645967/1da36da6-4e5b-41de-8a7d-0e73dd5ed2fd

@perunt Could please add steps for QA

: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/Gonals in version: 1.3.41-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.41-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/Gonals in version: 1.3.42-0 🚀

platform
result

🤖 android 🤖
cancelled 🔪

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
cancelled 🔪

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.41-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.42-26 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add test to look for races in refcounted cache

These tests pass, but if we've got them they're nice to have, so I want to keep them!

Reviewer: Easier to review commit-by-commit.

Reviewer: Easier to review commit-by-commit.

Codecov Report

Merging #1298 (c0a7e2c) into master (a195478) will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1298      +/-   ##
==========================================
- Coverage   47.57%   47.38%   -0.20%
==========================================
  Files         202      203       +1
  Lines       15779    15786       +7
==========================================
- Hits         7507     7480      -27
- Misses       7293     7320      +27
- Partials      979      986       +7

Impacted Files
Coverage Δ

graveler/committed/apply.go
31.32% <0.00%> (-40.97%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
59.25% <0.00%> (-3.71%)
:arrow_down:

graveler/graveler.go
39.54% <0.00%> (-0.21%)
:arrow_down:

graveler/errors.go
100.00% <0.00%> (ø)

graveler/committed/range_manager.go
100.00% <0.00%> (ø)

api/api_controller.go
40.41% <0.00%> (+0.07%)
:arrow_up:

pyramid/tier_fs.go
58.77% <0.00%> (+1.75%)
:arrow_up:

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 a195478...c0a7e2c. Read the comment docs.

Codecov Report

Merging #1298 (c0a7e2c) into master (a195478) will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1298      +/-   ##
==========================================
- Coverage   47.57%   47.38%   -0.20%
==========================================
  Files         202      203       +1
  Lines       15779    15786       +7
==========================================
- Hits         7507     7480      -27
- Misses       7293     7320      +27
- Partials      979      986       +7

Impacted Files
Coverage Δ

graveler/committed/apply.go
31.32% <0.00%> (-40.97%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
59.25% <0.00%> (-3.71%)
:arrow_down:

graveler/graveler.go
39.54% <0.00%> (-0.21%)
:arrow_down:

graveler/errors.go
100.00% <0.00%> (ø)

graveler/committed/range_manager.go
100.00% <0.00%> (ø)

api/api_controller.go
40.41% <0.00%> (+0.07%)
:arrow_up:

pyramid/tier_fs.go
58.77% <0.00%> (+1.75%)
:arrow_up:

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 a195478...c0a7e2c. Read the comment docs.

No current need for review: added tests revealed that OnlyOne is currently used in 2 incompatible ways.

No current need for review: added tests revealed that OnlyOne is currently used in 2 incompatible ways.

Closing -- this has been superseded by other work, notable #1332 .

Closing -- this has been superseded by other work, notable #1332 .


Add password confirmation to add user flows in SEGSAdmin

Summary
Add password confirmation to add user flows in SEGSAdmin
Issues closed
Closes #856
Additions/modifications proposed in this pull request:

Nice work, @miles200. The new SEGSAdmin password and confirm text fields work as expected.


toRelativeString not supported in swift 3.0?

I've installed pod 'SwiftDate', :git => 'https://github.com/malcommac/SwiftDate.git', :branch => 'feature/swift-3.0'
But unable to implement toRelativeString() function on both NSDate/DateInRegion
All I'm trying to achieve is to convert a date into "timeago" style

+1

in SwiftDate 4.0.0 you can use colloquialSinceNow() or colloquial() function

When I used this method i always get the following error: "fatal error: 'try!' expression unexpectedly raised an error: SwiftDate.DateError.MissingRsrcBundle: file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-8<IP_ADDRESS>/src/swift/stdlib/public/core/ErrorType.swift, line 178"
I tried the example from here http://malcommac.github.io/SwiftDate/formatters.html#colloquial
let dateA = DateInRegion() - 1.months
let (colloquial,relevantTime) = try! dateA.colloquialSinceNow()
The device is an iPhone5 (iOS9) Simulator.
I  used SwiftDate 4.0.1 and Swift3. Any idea what's the problem is?

I'm getting the same error as @hackolein with this code.
let date = try! eventDateString.date(format: .iso8601(options: .withInternetDateTime))
let (colloquial,_) = try! date.colloquialSinceNow()

But it is working for me on a generically created Date object.
let dateFormatter = DateFormatter()
dateFormatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss.SSSZ"
let sinceDate =  dateFormatter.date(from: published_at)
let (colloquial,_) = try! sinceDate.colloquialSinceNow()

Check out with 4.0.2. It should be solved now.

@malcommac  I'm still getting the same error, but it's breaking on a generic Date init as well.
It works fine in my iPhone 7 simulator, but crashes on my iphone 6 (iOS10) and on my 6/6s simulators running 9.3. Not sure if that helps at all.

@malcommac  I'm still getting the same error. I solved the problem, by adding a new translation for my language. Maybe it makes sense, to have a fallback, if the language not exists.

You are absolutly right. I've scheduled it for the upcoming 4.0.3 release. See #271

Ready :)


Set version (1.12) for StackTraceFlags

If understand correctly, StackTraceFlags was added to gstinfo.h after version 1.10.

I also noticed a suspicious version 1.0.10 for extract_dup in Gst-1.0.gir.
I can change that to 1.10 in this PR if you want me to.

I also noticed a suspicious version 1.0.10 for extract_dup in Gst-1.0.gir.
I can change that to 1.10 in this PR if you want me to.

That's actually correct. It was added in 1.0.10, and there's a v1_0_10 feature because of that

If understand correctly, StackTraceFlags was added to gstinfo.h after version 1.10.

It was added in 1.12, yes. Let's fix this in GStreamer as a first step, then I'll merge your PRs.

http://cgit.freedesktop.org/gstreamer/gstreamer/commit/?id=f649f0a44f42fda56c8eb912b7ffca0f1178b905


Node.js Alpha SDK

Complete with: https://github.com/open-feature/node-sdk/issues/6, https://github.com/open-feature/node-sdk/issues/7


'>>' applied to an unsigned number shall result in a logical shift

Please, see
http://stackoverflow.com/questions/38486442/logical-right-shift-in-numba
Thanks

I cannot reproduce your example. Which platform are you using?

Ok, I can reproduce if I try hex(foo(2**64 - 1)) instead.

I've submitted a fix in PR #1995.


Add Malbolge operation in new esoteric programming category

I added a new category: "Esoteric Programming"
and the first language operation for the esoteric language "Malbolge".
It uses a 3rd party node package (no license).
It currently uses the common language "syntax". There's no mode for the normalized form yet.
You can specify user input in a string which will be given to the program during execution on request.
Please let me know what you think about this new category. I planned to add more to it like brainfuck, piet etc.

@kassi Been a long time, if you're still around would you be willing to fix some of these merge conflicts and I'll get this merged in? ❤

Actually, I'm not confident we want to be importing a library that current averages around 4 downloads a month.  Instead of importing via npm, could you add the malbolge-vm code to our vendor folder?


Using pushgateway in a NiFi Cluster

Hello - This is more of a question.
How would you see pushgateway in a NiFi cluster.  Say in a 3 node cluster,  do we run pushgateway on every node?

Default setup is an external pushgateway that is running separately to the nifi cluster.


Added UIActivityIndicator

It's useful to notify the user that something is going on with the images.

Why was the pull request closed? Was it added to the project? (Sorry I'm quite new to GitHub and how it works)


SlowQueryListener always shows time as 0, QueryLoggingListener shows correct time.

It appears that while using the SlowQueryListener as shown below, the Time property in the logging is always 0. But the time appears to work correctly when using the QueryListener (without threshold specified, logs everything). I've run it a few times to ensure the query are not too quick and are genuinely being shown as 0. I feel like i'm missing something basic..
I'm testing against both H2 and MySQL via Hikari, JPA+Hibernate is actually executing the queries, full range of SELECTs, INSERTs, UPDATEs etc if that makes any difference. Using the latest versions of everything on Java 8 b121.
return ProxyDataSourceBuilder
                .create(dataSource)
                .logQueryBySlf4j(SLF4JLogLevel.INFO)
                .build();

2017-03-17 11:14:29:174 INFO  QueryLoggingListener - 02cbe638-eb5e-498c-b5c1-9daf154b0601 - Name:, Time:1, Success:True, Type:Prepared, Batch:False, QuerySize:1, BatchSize:0, Query:["..."], Params:[(...)]
2017-03-17 11:14:29:191 INFO  QueryLoggingListener - 02cbe638-eb5e-498c-b5c1-9daf154b0601 - Name:, Time:2, Success:True, Type:Prepared, Batch:False, QuerySize:1, BatchSize:0, Query:["..."], Params:[(...)]
2017-03-17 11:14:29:207 INFO  QueryLoggingListener - 02cbe638-eb5e-498c-b5c1-9daf154b0601 - Name:, Time:2, Success:True, Type:Prepared, Batch:False, QuerySize:1, BatchSize:0, Query:["..."], Params:[(...)]

return ProxyDataSourceBuilder
                .create(dataSource)
                .logSlowQueryBySlf4j(0, TimeUnit.MILLISECONDS)
                .build();

2017-03-17 11:17:14:620 WARN  F4JSlowQueryListener -                                      - Name:, Time:0, Success:False, Type:Prepared, Batch:False, QuerySize:1, BatchSize:0, Query:["..."], Params:[(...)]
2017-03-17 11:17:14:639 WARN  F4JSlowQueryListener -                                      - Name:, Time:0, Success:False, Type:Prepared, Batch:False, QuerySize:1, BatchSize:0, Query:["..."], Params:[(...)]
2017-03-17 11:17:14:654 WARN  F4JSlowQueryListener -                                      - Name:, Time:0, Success:False, Type:Prepared, Batch:False, QuerySize:1, BatchSize:0, Query:[""], Params:[(...)]

Regular query logging listeners write out query after execution has finished. So, it has time populated.
For slow query loggers, it writes out query when it passed threshold time. For example, if a query takes 10min and threshold time is set to 1min, the slow query logger prints out query when it passed 1 min while query is still running.
Currently, slow query logger is not updating execution time(elapsed time). So, it'll always show 0 in time.
I'll update to populate the time with current elapsed time. So, for slow queries, it will show threshold time(or threshold time +alpha based on when scheduler execute the thread) in time field.
(1min for above example).
Meanwhile, you can update slow query class like this to achieve same behavior:
SLF4JSlowQueryListener slowQueryListener = new SLF4JSlowQueryListener(...) {
    @Override
    protected void onSlowQuery(ExecutionInfo execInfo, List<QueryInfo> queryInfoList, long startTimeInMills) {
        execInfo.setElapsedTime(System.currentTimeMillis() - startTimeInMills);
        super.onSlowQuery(execInfo, queryInfoList, startTimeInMills);
    }
};

Ah right so that's what I was missing, the slow query listener just isn't what I thought it was =) make makes more sense than it being a bug.
What I really want is a way of logging queries (and their query time) over a certain threshold. the threshold reduces the verbosity of logging such that I can reasonably run it in prod and generate warnings off it. The slow query listener sounds like that, but it's obviously for another purpose. Possibly it would be less confusing to not log the time rather than have 0, or show "Time: >threshold" to be more explicit.
Can the query listener be augmented to only logger when the time hits a certain threshold? That would give me what I want I think.
Thanks for all the help.

Ok, so you want to log queries after they have finished which includes actual query execution time, only when they exceed threshold time.
In that case, you can use regular query logging listeners extending them to write query only when it took longer than threshold.
long thresholdInMills = ...
SLF4JQueryLoggingListener listener = new SLF4JQueryLoggingListener(){
    @Override
    public void afterQuery(ExecutionInfo execInfo, List<QueryInfo> queryInfoList) {
        if (execInfo.getElapsedTime() >= thresholdInMills) {
            super.afterQuery(execInfo, queryInfoList);
        }
    }
};
listener.setLogLevel(SLF4JLogLevel.WARN);

Perfect thanks

I was confused with that too. Good that I checked closed issues.
A hour ago I was ready to submit a new bug. 😄
I think this information should to add in the documentation with this example.

@binakot wrote a wiki page for that.
https://github.com/ttddyy/datasource-proxy/wiki/Logging-slow-queries

@ttddyy Awesome! Thanks!


Bugfix/fetch offsets interface

Codecov Report

Merging #729 into master will decrease coverage by 0.84%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #729      +/-   ##
==========================================
- Coverage   84.69%   83.85%   -0.85%
==========================================
  Files          26       26
  Lines        3392     3395       +3
  Branches      545      546       +1
==========================================
- Hits         2873     2847      -26
- Misses        380      404      +24
- Partials      139      144       +5

Impacted Files
Coverage Δ

pykafka/simpleconsumer.py
79.9% <66.66%> (-4.25%)
:arrow_down:

pykafka/topic.py
78.72% <0%> (-5.32%)
:arrow_down:

pykafka/managedbalancedconsumer.py
80% <0%> (-4.83%)
:arrow_down:

pykafka/utils/error_handlers.py
79.41% <0%> (-2.95%)
:arrow_down:

pykafka/connection.py
74.46% <0%> (-1.07%)
:arrow_down:

pykafka/protocol.py
96.66% <0%> (-0.28%)
:arrow_down:

pykafka/balancedconsumer.py
91.32% <0%> (ø)
:arrow_up:

pykafka/rdkafka/producer.py
89.13% <0%> (+0.31%)
:arrow_up:

pykafka/cluster.py
73.04% <0%> (+1.73%)
:arrow_up:

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 c61a816...f3c1e00. Read the comment docs.


I can't use this app on my nimbus+

I have tried to use the nimbus mapping but it didn't work. So I tried to make a new mapping but it didn't work too. Buttons don't work. Only the d-pad and axis' works. Also, it doesn't work on Forza Horizon 4. Windows says the controller is Xbox 360 controller but FH4 doesn't.

This issue is being discussed in #62 but it doesn't seem like they're having much luck either. It looks like you can't even remap the Nimbus+ with the remapping tool as the Nimbus+ shares inputs for multiple buttons.

:/


all the Construct(%Intl.xxx) should be done during the call to the constructor

In the specification, we have the following calls

Let numberFormat be ? Construct(%Intl.NumberFormat%, « locale, opts »).
b. Let pluralRules be ? Construct(%Intl.PluralRules%, « locale, opts »).
Let dateTimeFormat be ? Construct(%Intl.DateTimeFormat%, « locale, opts »).

Is there any reason these call cannot be done during the time of
1.1.2 InitializeMessageFormat ( messageFormat, source, locales, options )
It looks like all the necessary information needed in order to construct them from either source, locales, or options and once they are constructed, they can be cached inside the message format and do not need to be recreated again.
The current spec seems mandate the creation to be called during the format call and unnecessary costly.
Assuming we have the following call
let mf = new Intl.MessageFormat("some valid message", "en", {invalid  options})
for ( /* loop 1000 times */) {
  try {
      fm.format([1]);
  } catch(e ) {
     // ...
  }
}

In the current spec, the call to the oncstructor  will not throw, but the fm.format will (and need to) throw 1000 times. But if you move the consturction call to the Construct(%Intl.*) , it will throw in the constructor only.

We can't do this in all cases, because options can be set by variables. For example, with a message like
Your total is {$sum :number style=currency currency=$currency}.

we can't construct the number formatter until we know the currency we'll be using.

I see... hum....


fix: trigger onPress for accordion and progress

@hsu022210 @theurbanspectacle can I get a review please 🥺


Notes about dump function

Hi, while compiling my project I am getting many those notes:
note: see reference to function template instantiation 'std::basic_string<char,std::char_traits<char>,std::allocator<char>> nlohmann::basic_json<std::map,std::vector,std::string,bool,int64_t,uint64_t,double,std::allocator,nlohmann::adl_serializer>::dump(const int,const char,const bool,const nlohmann::basic_json<std::map,std::vector,std::string,bool,int64_t,uint64_t,double,std::allocator,nlohmann::adl_serializer>::error_handler_t) const' being compiled. Earlier I was compiling my project on windows 7 and it was fine, now i am on windows 10 and i have those notes. It is a bit annoying because it is thousands of this. I am using VS Code, custom build system based on MSVC 19.25.2861 x64 and dev branch of this library. Any solution for that?
Best regards, Aleksander.

Do you have a complete error message, including a line number?

Here is full error: ...\external\json\include\nlohmann/json.hpp(8104): note: see reference to function template instantiation 'std::basic_string<char,std::char_traits<char>,std::allocator<char>> nlohmann::basic_json<std::map,std::vector,std::string,bool,int64_t,uint64_t,double,std::allocator,nlohmann::adl_serializer>::dump(const int,const char,const bool,const nlohmann::basic_json<std::map,std::vector,std::string,bool,int64_t,uint64_t,double,std::allocator,nlohmann::adl_serializer>::error_handler_t) const' being compiled additionally I am compiling it using c++17, but earlier I was compiling it in this standard too.

Thanks the line in question is the return in
/// hash value for JSON objects
template<>
struct hash<nlohmann::json>
{
    /*!
    @brief return a hash value for a JSON object

    @since version 1.0.0
    */
    std::size_t operator()(const nlohmann::json& j) const
    {
        // a naive hashing via the string representation
        const auto& h = hash<nlohmann::json::string_t>();
        return h(j.dump());
    }
};

Any ideas how to fix this?

@MisterVento3 please provide full log with all notes.


[BUG] increasing seed when shouldn't

for each line, it increase the seed when seed is defined, and it make things unstable in "Split prompt by lines" mode.
for each line it should pin the seed, or at least an option to pin or not seed is welcome.

Thanks, I found the place of the bug.
Do you mind making this change and seeing if it works better for you?
https://github.com/rsxdalv/tts-generation-webui/blob/main/src/bark/generation_tab_bark.py#L406
change from
                    waveform_temp=waveform_temp,
                    history_prompt=history_prompt,
                    history_prompt_semantic=history_prompt_semantic,
                    seed=seed, # ORIGINAL
                    index=i,
                )

to
                    waveform_temp=waveform_temp,
                    history_prompt=history_prompt,
                    history_prompt_semantic=history_prompt_semantic,
                    seed=_original_seed, # Fix
                    index=i,
                )

I'm in the middle of making the React UI so it's a bit hard to finalize this fix now.

The fix has been shipped already, and this problem should be gone. I will close the issue, please feel free to reopen or comment if there's lack of clarity or possible bug remaining.


How can I use UserInfo in which is in Redux store instead of axios request?

Hi there,
User informations is already stored in redux-store( home.list{} ). However, When I click the any user, User informations getting via axios request (fetchUser is in /container/UserInfo/actions).
I'm wondering, Is there any way to use this stored data instead of use extra axios request. I mean How can I use this data instead of extra axios request?
Thanks in advance!

@ilkertuna, Of course you can, remove the fetching data action from UserInfo page. Then use the corresponded data of user id from the store of home to render the UserCards directly.

@wellyshen
Thank you,
Can you give example about access store from any page which has connected with redux store.

@ilkertuna I will show you it soon when I on holiday.

@ilkertuna
Here you are:
Change the code of ./src/container/UserInfo/index.js:
/* eslint-disable react/sort-comp */
/* @flow */

import React, { PureComponent } from 'react';
import { connect } from 'react-redux';
import type { Connector } from 'react-redux';
import Helmet from 'react-helmet';

import * as action from '../Home/action';
import type { Home, Dispatch, Reducer } from '../../types';
import UserCard from '../../components/UserCard';
import styles from './styles.scss';

type Props = {
  home: Home,
  match: Object,
  fetchUsersIfNeeded: () => void,
};

export class UserInfo extends PureComponent<Props> {
  componentDidMount() {
    // You need to fetch the data of Home or you will get error after refresing browseer
    this.props.fetchUsersIfNeeded();
  }

  render() {
    const { home, match: { params } } = this.props;

    return (

        <Helmet title="User Info" />
        {/* Pass the data of Home reducer according to user id */}
        <UserCard info={home.list[params.id - 1]} />;

    );
  }
}

const connector: Connector<{}, Props> = connect(
  // Access the store from Home reducer
  ({ home }: Reducer) => ({ home }),
  (dispatch: Dispatch) => ({
    fetchUsersIfNeeded: () => dispatch(action.fetchUsersIfNeeded()),
  }),
);

export default connector(UserInfo);

Change the code of ./src/routes.js:
/* eslint-disable react/sort-comp */
/* @flow */

import React, { PureComponent } from 'react';
import { connect } from 'react-redux';
import type { Connector } from 'react-redux';
import Helmet from 'react-helmet';

import * as action from '../Home/action';
import type { Home, Dispatch, Reducer } from '../../types';
import UserCard from '../../components/UserCard';
import styles from './styles.scss';

type Props = {
  home: Home,
  match: Object,
  fetchUsersIfNeeded: () => void,
};

export class UserInfo extends PureComponent<Props> {
  componentDidMount() {
    // You need to fetch the data of Home or you will get error after refresing browseer
    this.props.fetchUsersIfNeeded();
  }

  render() {
    const { home, match: { params } } = this.props;

    return (

        <Helmet title="User Info" />
        {/* Pass the data of Home reducer according to user id */}
        <UserCard info={home.list[params.id - 1]} />;

    );
  }
}

const connector: Connector<{}, Props> = connect(
  // Access the store from Home reducer
  ({ home }: Reducer) => ({ home }),
  (dispatch: Dispatch) => ({
    fetchUsersIfNeeded: () => dispatch(action.fetchUsersIfNeeded()),
  }),
);

export default connector(UserInfo);

By the way, for this kind of question please ask on stack overflow. Because I'm really busy recently.


[10.x] Bump to Symfony 6.1

Already bump Symfony to v6.1 to test their dev version to catch bugs early on.

If Symfony 6.1 requires PHP 8.1 then Laravel probably should too?
https://symfony.com/blog/symfony-6-1-will-require-php-8-1
https://laravel.com/docs/9.x/upgrade

Thanks @GrahamCampbell.
I'm developing with Sail (thus 8.1) but deploying to 8.0, so this caught me.


nz-menu-item nzDisabled doesnt work

Reproduction link
https://stackblitz.com/edit/angular-htjltx?file=src%2Fapp%2Fapp.component.ts
Steps to reproduce
Hover dropdown and select 1st menu item
What is expected?
click shouldn't be triggered
What is actually happening?
click is triggered

Environment
Info

ng-zorro-antd
10.0.0

Browser
chrome

nz-menu-item and (click) are the same host and cannot be intercepted, please use (nzClick)


Improved captions

Why
Some snippets exceeded Twitter 240 character limit and the whole caption didn't make sense.
What

added ability to open a snippet directly from the tweet by adding a direct URL to it
added 2 new hashtags that seem to be very popular #LearnToCode and #100DaysOfCode
added truncate functionality to tweets so we don't exceed a 240 char limit.

here's a small throwback to last December when we built this bot together


New version: Google.Chrome version 94.0.4606.61

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

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

I'm having trouble pulling down this one in US Central. You might have to close and reopen a few times.

Pretty sure the bot have cached the previous installer so this will probably take a day to update...

/azp run

/azp run


Testing, please ignore. (osqrrz)

This is a bug bounty test. Please ignore.. Please DO NOT APPROVE THIS! (osqrrz)

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


Imprint Location filter not working

None of the filter choices return any results -- broken link to the data field, I guess?

Should be fixed now

Looks good!


Feature/eco 808 scrutinizer

A new inspection was created.

The inspection completed: No new issues

A new inspection was created.

The inspection completed: No new issues


[REVIEW] Kanishk Chhabra Portfolio

Portfolio link
https://www.kanishkchhabra.in/
Repo Link: https://github.com/mrkc2303/Personal-Portfolio

Nice portfolio.
Maybe try to apply the theme based on the browser preference.
Otherwise nice work!

I love the design of this portfolio! A few ideas from me:

I'd be wary of rating your skills out of 100%. I'd rather see the list of skills straight away without having to expand. It depends who your target audience is, but if it's a recruiter/employer, they may only have a minute to skim read your page.
Qualifications section - again depending on your audience, if it's to get a job, I'd put work first rather than education. What do you want them to see first if they don't have time to click through?
Projects could even be moved up above qualifications if that shows best your experience. I love how you have a video and the GitHub and live link.

I really like your portfolio, you've done an excellent job.

Hey @schmelto
Thanks for reviewing my portfolio.
Yeah I have tried to implement this but i was facing some issues and hence code for that has been commented out for now.
But I am trying to fix it.  :)
Thanks

Great portfolio.
You should try to put an image of yourself in the home page rather than the animated blob.


feat: support session-id

Coverage remained the same at 100.0% when pulling 521d73d579b8b88bcf70f85d7c86571ecd71de54 on BlackHole1:feat-ses-id into 226a10bd0370245d24602b98fd4b866cf42fdc7e on fastify-userland:main.

Coverage remained the same at 100.0% when pulling 521d73d579b8b88bcf70f85d7c86571ecd71de54 on BlackHole1:feat-ses-id into 226a10bd0370245d24602b98fd4b866cf42fdc7e on fastify-userland:main.


converted header into it's own component

Oh hey! Thanks for contributing, I encourage you to check out the new README.md at /package/react/README.md  😄
Feel free to ping us on Discord if you want to chat about design or hang out! Less chances for conflicts that way 👍


Panning with mousewheel or right mouse button

According to my knowledge, panning is by default "LMB-only":
// Ignore right-click, since that should open the context menu.
function defaultFilter() {
  return !event.button;
}

I am experiencing an issue where I would like to be able to pan with the mousewheel or as the RMB as well. Unfortunately however, in the zoom function there is no way to change this behavior.
export default function() {
  var filter = defaultFilter,
  // [...]
};

It would be nice to have the possibility to change the default filter, for example like this
export default function(opts) {
  var opts = opts || {};
  var filter = opts.filter || defaultFilter;
};

which allows one to do
var zoom = d3.zoom(function() {
  // This should allow RMB panning.
  return window.event.button === 2;
});
selection.call(zoom);

See zoom.filter to change the filter function.

My apologies, did search for it for over an hour, probably not in a good way. -_-

d3.zoom().filter(function () {
    switch (d3.event.type) {
        case "mousedown": return d3.event.button === 1
        case "wheel": return d3.event.button === 0
        default: return false
    }
})


runtime: reduce StackGuard

We raised it to 512 in the run up to Go 1.4 and I'm raising it to 640 now for
Windows/amd64 + write barriers. I'd like to get it back down to something like 256.

Definitely not going to happen for Go 1.5.

I note that StackGuard has moved in the wrong direction, as it is now 880 (as of https://golang.org/cl/27159).

928 as of Go 1.18.


Intrusive variants

Thanks for making this library, the design is very cool.
I have a high performance scenario where I want to avoid heap allocations, and am happy to manage memory more manually.
Would it be possible to provide "intrusive" variants of the oneshot channels where the user provides heap memory to initialise, and have a callback for drop?
In my case, I have a mbuf-style implementation with a custom allocator, where the mbufs are reference counted, and it would be nice to be able to embed the kanal values into the mbuf header. I can treat kanal's OneshotInternal as a live reference to the mbuf itself, which would work nicely. It would enable me to acquire an IO request buffer with metadata + data + completion notification mechanism in one alloc.

Hi, I'm glad you like it!
I thought about your problem, but unfortunately, the rust allocator API is unstable: https://doc.rust-lang.org/std/alloc/trait.Allocator.html .
every other implementation that I thought about had some unnecessary overhead on the default one-shot channel which most other users will use. as your use case is highly specific I recommend you write specific code for it too.
a suggestion that may help you is if you are spawning the thread or coroutine in the same place that you are constructing the buffer struct you can receive data from its handler just like a one-shot channel by returning the message inside the spawned code.
https://doc.rust-lang.org/std/thread/struct.JoinHandle.html#method.join

Thanks for the swift reply, and for your consideration.
I'll think about a more specific messaging solution :)

Anytime!
Goodluck


GlobalKey.currentState is null when the element is assigned with the key in Flutter inspector

Simplified widget tree of my application is
+ Scaffold
++ Body
+++ PageView
++++ FooView  (with GlobalKey 'FooViewKey')
++++ BarView  (with GlobalKey 'BarViewKey')

Most times, the currentState of FooViewKey or BarViewKey is returned with a null value. I tried debugging and found that those GlobalKeys are missing from the GlobalKey._registry. I'm not able to predict the cases when they have values and when they are null.

How to fix this issue? (happy to provide any required info)
Is there any restrictions on when setState() can be called.

Can you provide some code that leads to this issue?

I created a simple proof. Try that out.
@dnfield https://gist.github.com/RyanAfrish7/c9a9553cf9f821769347f1b7f9ddc9c7

The reason currentState comes up as null is that the PageView doesn't keep the widget around when it's not on screen.  You can see this if you refactor your PageView to something like a Column.  You're also not calling setState when you modify the state, so even if the state was non-null, the changes wouldn't reflect in the UI.
Generally speaking, you should probably try to avoid managing state from one widget to another like this.  There are several patterns available for state management, and you can read up on a bunch of examples here.  You should also seek to use GlobalKeys as sparingly as possible, and generally only try to use them in such a way that you can be sure that the widget it's Keyed to is actually onstage.

I understand that it's better to design the app without using GlobalKeys. But can you provide a solution for the the use case I mentioned above. In my real use case, I have a TextField in place of int i and I'm trying to change the value of TextField based on input from another sibling widget.

A very simple way to do that can be found here: https://github.com/brianegan/flutter_architecture_samples/tree/master/example/vanilla
Or, using InheritedWidgets, here: https://github.com/brianegan/flutter_architecture_samples/tree/master/example/inherited_widget
The basic idea is that you want updates to that TextField to change something in a state repository.  There are tons of ways to handle that, and designing it will depend on your app.  We don't currently have a single recommended way to maintain state across the whole app, but the architecture samples repo provides at least some starting points.


Trigger-linkable "Clear Queue" action

maybe it should also clear stopped tracks if playback is stopped and the queue is already cleared?

resolved in 5fc2410


Dev koanf

newer version of https://github.com/bricks-cloud/BricksLLM/pull/61

once you fixed the typo, i can merge this in.

Done. thanks.


Snyk upgrade 2844d7e6a001540ce7b54fe98a0f8732

Purpose

* ...
Does this introduce a breaking change?

[ ] Yes
[ x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Please fix merge conflicts to merge this PR in.


Unabled to get mission.

I tried to make an script that get the mission of the drone to acces the individual items.

I get this timeout error:

Im using MavSdk 1.4.9 in Ubuntu 22.04

Does the connection work? Check with these instructions: http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/#debug-connection-issues
Also, likely you want to connect to "udp://:14550", check this comment:
https://github.com/mavlink/MAVSDK/blob/v1.4/src/mavsdk/core/include/mavsdk/mavsdk.h#L78-L81


Escaped quotes with variables inside interpreted as unescaped quotes

(Original issue 1017 created by superjamie on 2014-07-18T09:43:30.262083+00:00)
Given the following PHP code:
#!php

$trackname = str_replace(".mp3","", $trackname);
$thisline = "
$trackname
\n";
fwrite($handle, $thisline);

The line beginning fwrite is incorrectly interpreted as part of a string (in red on GitHub) when it's not.
The syntax highlighter seems confused by the use of escaped quotes \" inside unescaped quotes " on the line beginning $thisline.
By replacing the variables $item/$file with static data like item/file does not result in this happening:
#!php

$trackname = str_replace(".mp3","", $trackname);
$thisline = "
$trackname
\n";
fwrite($handle, $thisline);

Obviously that isn't valid for this application, but might help you pinpoint where the problem lies.
I discovered this on Line 68 of this file
I think this might be a duplicate of your existing Issue #899. If so, please close this and let me know, so I can ask GitHub to update their copy of Pygments.

(Original issue 1017 last updated on 2014-10-05T22:29:37.968425+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by cvuorinen on 2014-08-08T07:36:11.654035+00:00)
Same thing also happens here:
https://github.com/kriswallsmith/Buzz/blob/v0.12/lib/Buzz/Message/Form/FormRequest.php#L132
I think it is not duplicate of issue #899 because that seems to be already fixed in GitHub.

(Original comment by tshatch on 2014-10-05T18:04:58.234205+00:00)
This is because we think $file\ is a valid variable name (due to choice of namespace separator).

(Original comment by superjamie on 2014-10-05T22:29:31.607314+00:00)
This appears to be fixed on GitHub now, both on my and Carl's like. Assuming they are still using Pygments, this is resolved.


Need help: how to get detailed data about failed validation?

Hello. Could anyone recommend or explain how to extract detailed validation errors? Which field, error type, etc?
Thanks.
I'm using such a code in symfony event listener
$validator = (new \League\OpenAPIValidation\PSR7\ValidatorBuilder)->fromYamlFile($openapiFilePath)
                          ->getRequestValidator();
$validator->validate($psrRequest);

p.s. I've looked through the code and I do not see any public method to get such an info

👍
This would sure be a handy thing to have

Validation failure is expose through exception tree, it's documented in the readme. Basic exceptions are ValidationFailed for common PSR-7 validator process. You can inspect exception chain to get exact reason.
Some of the exceptions have programmatically accessible data, like breadcrumbs https://github.com/thephpleague/openapi-psr7-validator/blob/master/src/Schema/Exception/SchemaMismatch.php#L13

How does this \League\OpenAPIValidation\PSR7\Exception\Validation\InvalidBody tell me where to look in my json body?

Apologies, but yes, dumping the whole exception it does indeed include way more helpful information! 🎉

@jokaorgua I'm using this code. I don't know your use case, but probably you can adjust it to your needs
private function getValidationMessage(ValidationFailed $exception): string
    {
        $ex = $exception->getPrevious();

        if ($ex === null) {
            return $exception->getMessage();
        }

        if ($ex instanceof SchemaMismatch) {
            if ($ex->dataBreadCrumb() === null) {
                return $exception->getMessage();
            }

            $field = implode('.', $ex->dataBreadCrumb()->buildChain());

            return sprintf(
                'Validation against spec failed for "%s": "%s"',
                $field,
                str_replace(['Keyword validation failed: '], '', $ex->getMessage())
            );
        }

        return $exception->getMessage();
    }

@scaytrase thanks. But as for me, the interface should be created for getting errors normally without hacks
@canvural thanks!

Interpreting validation errors is pure userland responsibility. Every project can have it's own implementation and it's own usecase (some use psr-7 validator, some validate raw data, etc). And there is nothing hacky in using fields exampled in the readme (yeah, maybe not that explicitly but anyway)


Error in rule wide_fdr_peaks

I'm getting  "Error in rule wide_fdr_peaks" regardless of whether I use the new "min_per_acc_peak".
My input data is phased reads mapping to a ~200 kb region of chromosome 19.
I sent you more details on slack. Let me know if I can help with the troubleshooting.

Fixed by #3!


Add support for I2C sensors (using Austin's sensor library)

I would like to close this. A new approach would be required with the many different target devices we support now.


Kali Linux on Raspberry Pi - kickthemout issue

Having serious issues getting kickthemout to work have cloned it from github, and downloaded scapy and still not working. Have tried to uninstall scapy but wont let me I try running the command "sudo pip uninstall scapy" and I get a message "Not uninstalling scapy at /usr/lib/python2.7/dist-packages, outside enviroment/usr. I have tried a lot of the solutions given to no avail. Any help would be greatly appreciated!
Edit - Works fine on a Kali Linux Virtual Machine, could it be to do with the pi being a fresh install or something?

It's probably because Scapy is installed on Kali out of the box.
Try removing it with apt-get:
sudo apt-get remove scapy
And after it reinstalling it with pip:
sudo pip install scapy

Thanks for getting back to me, but that is still not working. I try to run "python kcikthemout.py" and I get the same error " Requirements have not been properly satisfied. Please try running.."

I would have to guess that it doesn't work on your RPI, because it is ARM.

It works on RPI for sure, running fine for me on Raspbian.

same here. doesnt work. This its maby because of different python release? will try to "rewrite" some of the errors i got earlyer and try again. Il post if i fix it :)

Sounds good. Let us know how it goes. :)
@Met4crypt

did yhis ever work for you? im planning on doing this on my pi

Forgot the whole thing and never tried.
I think its the Python versions or something.
Sendt fra min iPhone

mar. 2018 kl. 22:14 skrev 0rigin5<EMAIL_ADDRESS>
did yhis ever work for you? im planning on doing this on my pi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Playground: upload component modifications

Playground: upload component modifications

To Do

[ ] Update the content of the instructions to the content specified in the Figma file.
[ ]  Add a divider, a "New" badge, and content to the instructions container
[ ]  Implement spacing and layout adjustments in the upload interface
[ ]  Color the asterisk after "Data" red
[ ]  Implement the Upload File button update
[ ]  Implement the No file loaded copy under the new Upload button

Resources

Figma design file: Playground upload component
OMAP Compare Template (Link to be added when it is delivered to me)

User Stories

As a user, I want to know what data I can upload into the Playground, so that I can generate useful visualizations and reports from the ASCT+B Reporter.
As a user, I want to have helpful instructions, so that I can successfully use this feature.
As a user, I want the upload component to be intuitive, so that I can quickly generate visualizations and reports that further my research.
As a user, I want a button with an upload icon instead of a vague attachment icon without a label, so that I can learn how to use this interface faster.

@libby-maier any reason why you closed this?

Wrong Repo - Apologies! I didn't know how to delete it, so I closed it and recreated it in CCF ASCT Reporter: https://github.com/hubmapconsortium/ccf-asct-reporter/issues/622

Oh right, got it! I'll actually delete this one for you.


fix: update scalar to v1.13.0

lot's of great fixes in v1.13.0!
97cd84e9: feat: client ignore list
5dac9c51: fix: open section on search result click
0e0f34b3: fix: cleanup safari bugs
7582e82a: fix: classic layout stylings
d5d55407: feat: expose dark mode light mode property in config
7d502131: fix: add markdown rendering for body schema
3e7c4cf7: feat: add fetch examples
859977f8: feat: Add dynamic content type selection for request body
0b66933d: fix: declare theme font for buttons and fix regressed font weight
87ed7f01: fix: markdown second level margin issue
4513c725: feat: add intro flare for gradients

@marclave
maybe add something like "latest" version by default?

That would be amazing to keep it always at default, then we can override it if a user specifies a version ✨
I'll do this and make a new PR

@marclave Can we get #95 in on this?

yes we certainly can ✨ , let me polish up that PR right now!

@kravetsone @jmcudd added both feedback to this PR :)
now we:

default to use latest (much better)
add optional override scalarCDN parameter :)


RFC: retire patch-v0.7.x branch & Rollup 0.x support

I am now maintaining patch-v0.7.x branch to support react-recompose with Rollup 0.x, with some upcoming updates as discussed in issue #8.
Assuming that I can update react-recompose to use Rollup v2(+), with updates from main branch of this plugin, then I would like to drop support for Rollup 0.x from patch-v0.7.x branch.

patch-v0.7.x branch is now retired see https://github.com/react-recompose/react-recompose/issues/29


Missing /run/opengl-driver/lib/dri/vboxvideo_dri.so

Don't know if expected or unexpected, but doing a nixos-rebuild boot, then reboot but the /run/opengl-driver is still the old one. Had to do nixos-rebuild switch to fix it.

(triage) @lethalman can you still reproduce this?

No response, so close @zimbatm.

hi, how do you "put "virtualbox" in your drivers, "?
thanks

services.xserver.videoDrivers = [ "virtualbox" ] but note that virtualisation.virtualbox.guest.enable = true; should include it automatically.

Hmm.. unfortunately I have both, and it still didn't help...
glxinfo| grep "renderer string" OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 bits)

@husnoo OpenGL acceleration has never worked as mentioned above.
In trying to understand how everything fits together I've managed to get the vboxvideo_dri.so file to show up in my /run/opengl-driver/lib/dri folder using
{ pkgs
, config
, ...
}:

let
  makeVideoDrivers = p: p.buildEnv {
    name = "mesa+vbox+txc-${p.mesa_drivers.version}";
    paths =
      [ p.linuxPackages.virtualboxGuestAdditions # for the DRI driver
        # p.mesa_drivers # (replaces this)
        p.mesa_drivers.out # mainly for libGL
        (if config.hardware.opengl.s3tcSupport then p.libtxc_dxtn else p.libtxc_dxtn_s2tc)
      ];
  };
in
{
  hardware = {
    opengl = {
      enable = true;
      extraPackages = [pkgs.linuxPackages.virtualboxGuestAdditions];
    };
  };
}

but I haven't yet clarified for myself what the relationship (if any) between the vboxvideo_dri.so and VBoxOGL.so / libGL.so.1 is (which you mentioned in https://github.com/NixOS/nixpkgs/issues/18457#issuecomment-268750395) so I may well be grasping at straws.

Please move discussions like those to new issues.


Heart failure

🔍 Problem Description:
Heart failure is a chronic illness affecting millions globally, leading to increased morbidity, mortality, and healthcare costs. Early detection and effective management are crucial for improving patient outcomes and alleviating strain on healthcare systems. Predictive modeling utilizing advanced statistical and machine learning techniques can help identify individuals at high risk for heart failure, enabling timely interventions and tailored therapies.
🧠 Model Description:
We will develop predictive models using historical patient data, including demographics, clinical features, test results, and medical history. The primary algorithm will be Random Forest, which has demonstrated strong performance with an accuracy of 0.93 in previous tests. We will also explore other machine learning methods, including Neural Networks, to compare effectiveness. The model will be validated using appropriate metrics to assess its predictive power, accuracy, precision, and recall.
⏲ Estimated Time for Completion:
The estimated time to complete the project, including data gathering, preprocessing, model training, evaluation, and validation, is approximately 4-6 weeks.
🎯 Expected Outcome:
The expected outcomes include:

Accurate Predictive Models: Development of effective models capable of predicting the likelihood of heart failure, facilitating early interventions.
Improved Clinical Decision-Making: Tools for healthcare practitioners to optimize patient management, leading to better patient outcomes.
Personalized Care: Treatment plans tailored to individual risk profiles, reducing the incidence of heart failure and its complications.
Healthcare Efficiency: Enhanced resource allocation and reduced healthcare expenditures through early detection and intervention.

📄 Additional Context:
This project will utilize a dataset comprising clinical features, medical histories, test results, and patient demographics. The development environment will include Python IDEs (e.g., VS Code or Google Colab) with libraries such as Pandas, NumPy, Scikit-learn, Matplotlib, and Seaborn. The final model will be implemented through a Streamlit application, allowing healthcare professionals to input patient data and receive real-time risk assessments. Future enhancements will focus on expanding the dataset and integrating real-time data from multiple hospitals to improve accuracy and clinical applicability.
To be Mentioned while taking the issue:

Participant role: GSSOC Participant

Note:

I will review the project documentation and ensure that my code aligns with the project structure.
The predict.py file will include a properly implemented model_details() function to print a detailed model report.
I will create a new branch for this work to maintain the stability of the main branch.
I will strictly follow the provided pull request template when submitting my changes.

Request for Review of Upcoming Pull Request
Dear Project Admin,
I hope this message finds you well. I, Abhisek Panda, am currently working on developing predictive models for heart failure, as outlined in my previous issue submission. I plan to complete this work within the next two days.
Once I finish, I will create a new pull request for your review. I would greatly appreciate it if you could verify and accept it at your earliest convenience.
Thank you if you support me!
Best regards,
Abhisek Panda


I couldn't build the example in my local

Test your changes using the example folder npm run build cd example npm start

Since there are package.json files in only the example and package folders. And there is the cd example command in the explanation, i assume that we run npm run build in the package folder. And npm start in the example folder.
Before running commands, i of course did npm install.
After i do npm start all i see is this;

Sooo, i tried to change to render to createRoot but other errors just stayed as they are.
So i just wanted to ask what i was doing wrong.
Thanks

My guess is that you have multiple versions of React installed somewhere, run this command and see what is returned

I just did a clean clone
cd react-chessboard/package && npm i && cd ../example && npm i && npm run rebuild

I followed my way from the beginning and then your way, in both situations the result and npm ls react was the same.
as you suspected, in the example folder i have react 18, and 16 in the package folder. But i do the same things as you. I don't understand what's the case. Pardon my noobiness xd
example folder;

package folder;

I checked out the package.json files, and example folder has   "react": "^18.2.0" in the dependency section whereas the package folder  has "react": ">=16.14.0" in the PeerDependency section.
My pc for some reason is installing react 16.14.0 even though there is the >= in the PeerDependecy part. and example installs 18.2.0. I mean it's not doing anything wrong after all xD
So, i did npm update  in the package folder to match the versions and i checked them afterwards with npm ls react command. And error was still the same.
So i did the other way, and tried to match the versions at 16.14.0 by changing the package.json files, and then checked them afterwards by npm ls react. And the result was the same BUT i didn't get the createRoot error in the console. I just got the other errors. Here's one;

So, what do i do here? Am i doing something wrong?
Thanks <3

I think it's something to do with npm link
see https://stackoverflow.com/a/69457966/19574735

I did npm link in package folder, and then npm link react-chessboard  in the example folder.
Then did npm install in both.
And finally npm run build in the package folder and npm start in the example folder.
Result was the same, same errors.
Here are the npm ls react s;
-- example folder

-- package folder

So, everything was the same.
I'm linking this issue to my noobiness and will not take your time anymore xD So, closing the issue.
There was just a little bug in the Click To Move example. When you click a piece, then click an empty square and then click to a valid square.  It just does nothing even though it shows the option squares. I fixed it in my own project and wanted to fix this one as well but not a big deal anyway.
Thanks man <3

Have you tried starting again completely from scratch?
git clone git@github.com:Clariity/react-chessboard.git
cd .\react-chessboard\example
npm i
npm start

I just did this from my desktop and it worked as expected

I was trying every method from scratch just to be sure already xd
Now, i did only npm i and npm start and it worked.  And since i was going to fix the issue in the example. i'm set.
But i'm still curious about what was going on when i was building the package. I don't get it.

i'll be honest I'm not too sure myself, it looks to simply be something to do with having multiple versions of react somewhere, but I'm glad it worked finally, and I look forward to your example fix, I'll close this issue now

@Clariity Facing the same issue, the following solution you have shared does work:
git clone git@github.com:Clariity/react-chessboard.git
cd .\react-chessboard\example
npm i
npm start

But if we I want edit the package and rebuild it for testing-
cd ..\package
npm i
npm run build

Then the example code stops working with the following error:
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

I have tried the npm link solution as well but that is not working for me, please let me know if I am doing anything incorrectly

I just cloned the project onto my desktop and ran the following
git clone git@github.com:Clariity/react-chessboard.git
cd .\react-chessboard\example
npm i
npm start

Worked fine, stopped the server and then ran:
cd ../package
npm i
cd ../example
npm run rebuild

Worked as expected. You may have some global version of React installed somewhere?
node -v
// v14.15.1

npm -v
// 6.14.8


Feat/test menus

Description

Add menu linting support in CMS
Update linter config

Checklist

[x] I have opened this pull request against develop
[x] I have added or modified the tests when changing logic
[x] I have followed the conventional commits guidelines to add meaningful information into the changelog
[x] I have read the contribution guidelines  and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

Does the linter config change?

Does the linter config change?

yes, added an extra line here:
https://github.com/django-cms/django-cms/pull/7534/files#diff-c94729f5aa1afabfd250d3a929cdc840199d92facd4c83fcbc37b661d784d4acR28

Ah, ok! I thought you ment the pyproject.toml or something.


System.Threading.Tasks.Task Discord.IUserMessage.RemoveReactionAsync Method not found

Hello, Im using Discord.Addons.Interactive (latest version) and I recently updated to Discord.Net 2.2.0, it seems that the paged messages aren't working anymore. The bot adds the reactions but the ReactionAdded handler is throwing an unhandled exception when I react. Is there a way to fix this?
6:10 PM [Gateway] A ReactionAdded handler has thrown an unhandled exception.
Method not found: 'System.Threading.Tasks.Task Discord.IUserMessage.RemoveReactionAsync(Discord.IEmote, Discord.IUser, Discord.RequestOptions)'.
   at Discord.Addons.Interactive.PaginatedMessageCallback.HandleCallbackAsync(SocketReaction reaction)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at Discord.Addons.Interactive.PaginatedMessageCallback.HandleCallbackAsync(SocketReaction reaction)
   at Discord.Addons.Interactive.InteractiveService.HandleReactionAsync(Cacheable`2 message, ISocketMessageChannel channel, SocketReaction reaction)
   at Discord.EventExtensions.InvokeAsync[T1,T2,T3](AsyncEvent`1 eventHandler, T1 arg1, T2 arg2, T3 arg3)
   at Discord.WebSocket.DiscordSocketClient.TimeoutWrap(String name, Func`1 action)
Method not found: 'System.Threading.Tasks.Task Discord.IUserMessage.RemoveReactionAsync(Discord.IEmote, Discord.IUser, Discord.RequestOptions)'.

Could we have a look at your code?

Answered in #33


Underscore in katakana

Is there a reason as to why _ are not replaced by ー when converting from romaji to katakana? I mean sure, you may want to type an actual underscore, but the same reasoning applies to the minus sign. When using IME mode to convert romaji to katakana, you generally type everything in upper case, so a - becomes _. Before changing this in the code, I wanted to make sure that this is not intended behaviour.
EDIT: Used back ticks to escape and highlight markdown symbols

Aside:
You'll want to enclose terms in backticks ` ` to write anything that can be interpreted as markdown. IE. underscores denote italics.
Short Answer:
The reasoning is to keep in line with normal IME conversion, in a sense of WYSIWYG.
Typing ge-mu_.,<>() in Google IME converts to げーむ＿。、＜＞（）
Similarly in katakana mode you will get ゲーム＿。、＜＞（）
Long Answer:
Using capitals with the IME does nothing, that's just a minor convenience feature with Wanakana since we don't provide a kana shift shortcut (maybe we could, though better left as an exercise for the developer to add a button that will then re-convert or set the input mode as hira or kata).
Originally there was no punctuation conversion, though I extended it to convert visually equivalent symbols for the more common instances like 、。（）［］ etc
I will admit, I took a liberty in deciding on smart quotes ‘’’ => 「」 and “” => 『』 whereas [] => ［］ rather than the normal IME equivalent of [] => 「」. This was based on their actual usage in text IE: quotations so I was getting too clever for Wanakana here. It was nice to see ‘tasuketekure’tosakenda converted to the Japanese equivalent of 「たすけてくれ」とさけんだ (and converting nicely in reverse but I was probably pushing my luck with this approach :smile:
This diverges from the WYSIWYG approach, so it's something I would be willing to change to be more in line with the original idea. It's not clear that to type 「 you need to enter “ which most users aren't even aware is different to '. A better solution might be better to map [] to 「」 in toKana and 「」 to “” in toRomaji... but I digress.
As it stands, I don't see that _ should convert to ー even if it's a hassle to disable caps / release shift. Is there something more I'm missing here, or it's just a question of typing in caps when converting?

Alright, thank you for your thorough explanation, that does make a lot of sense. Maybe we could implement an API to customize the default behaviour, like an update_mapping function or something along those lines?

Could potentially be added to options, and merged with the pre-defined mappings.
I'm concerned that edge cases handled at different stages of toKana might end up different to what's expected with an updated mapping. I'm thinking of sequences along the lines of kkou, nya, ltsu and n'.
Not sure I can think of a specific example that would definitely go wrong, but since the actual 1 -> 1 map that we would be updating happens midway through toKana there's potential for things to get weird.
kanaChar = FROM_ROMAJI[chunkLC];

Perhaps not though, it's worth a shot and testing if it's feasible. If it's just updating punctuation/symbol mapping that is far safer and I don't think would run into issues.

Alright so everything is now merged to dev, and I'm going to try to find some time and devices to manually test input with the dev branch :+1:

FYI: after further thought I actually removed ヶヵ from toRomaji
The ヶ ヵ forms can be read as "ka, ga, or ko" in different situations and are effectively being used as symbols/kanji (and not as kana) when seen in 一ヶ月 etc. Therefore we should make no assumptions about converting them.
However, allowing the individual small forms to be entered specifically via (x|l)(ke|ka) in toKana() is still a valid use case roma -> kana and that functionality has been retained.

You can npm install wanakana@beta if you want to easily try out your changes in a local project. I still want to do some more device testing before releasing normally.