Complete API javadoc with code examples

I'm happy with the actual state, minor improvements can always be done but it's globally ok.


fix: no search bar in category list while categorizing

Details

This PR fixes the issue that no search bar in category list while categorizing.
Fixed Issues

$ https://github.com/Expensify/App/issues/41773
PROPOSAL: https://github.com/Expensify/App/issues/41773#issuecomment-2098865937
Tests

Precondition: User has no workspace.

Create a track expense
Press Categorize it
Verify search bar appears in category list

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

Offline tests

NA
QA Steps

Precondition: User has no workspace.

Create a track expense
Press Categorize it
Verify search bar appears in category list

[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: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

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

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/113963320/a6bdf471-f6af-43ae-b8d9-13ea3a73162d

Android: mWeb Chrome

iOS: Native

https://github.com/Expensify/App/assets/113963320/d5182ce4-4b7b-4f64-ba3d-aa9af5757fb7

iOS: mWeb Safari

https://github.com/Expensify/App/assets/113963320/51cda66f-e3dc-484f-841d-d1304ad62967

MacOS: Chrome / Safari

MacOS: Desktop

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
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] 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)
[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 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: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[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 reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/3069065/dd2f27ec-97d7-436f-9fb8-de7aa017fb50

Android: mWeb Chrome
https://github.com/Expensify/App/assets/3069065/34a1bd17-28d9-40c5-8586-e100a57fadcc

iOS: Native
https://github.com/Expensify/App/assets/3069065/7c1bfb19-502a-4138-9fb8-589bd2379296

iOS: mWeb Safari
https://github.com/Expensify/App/assets/3069065/4f7ac220-2896-4641-8792-0ff1ac58e6ae

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/3069065/b2ed7b14-07f4-4e66-8605-8d58f1a10ba2

MacOS: Desktop
https://github.com/Expensify/App/assets/3069065/895491ee-75c2-4cf7-bebd-adcb27db7b77

Is it possible to add a jest test to prevent this bug from happening again in the future?

@tienifr Quick bump

🚀 Deployed to staging by https://github.com/blimpich in version: 1.4.75-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.75-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


🐛 Use product name instead of module name when patching XCFrameworks

Description

When patching support files, we should use just product.name to replace XCFrameworks paths. This is because module name is used for importing modules in swift, which doesn't allow special characters like '-', so for modulemap search path we should use module name; however for header search path and library search path, special characters are allowed. Therefore when we have targets whose name has characters not supported in Swift, such as "foo-bar", using product.moduleName makes the regex pattern for patching XCFrameworks be "${PODS_XCFRAMEWORKS_BUILD_DIR}/foo_bar", which causes search path "${PODS_XCFRAMEWORKS_BUILD_DIR}/foo-bar" cannot be substituted because regex pattern doesn't match.
For example:

For patching modulemap path, we should use product.moduleName which doesn't include special characters like '-', but for patching XCFramework, we should use product.name
Checklist (I have ...)

[x] 🧐 Followed the code style of the rest of the project
[ ] 📖 Updated the documentation if necessary
[x] 👨🏻🔧 Added at least one test that validates that my change is working, if appropriate
[x] 👮🏻♂ Run make lint and fixed all warnings
[x] ✅ Run make test and fixed all tests

❤ Thanks for contributing to the 🏈 Rugby!

@swiftyfinch Ah sorry, wasn't checking GitHub notifications on weekends... I fixed them and now it should be OK.

@PRESIDENT810 Thank you for your contribution! 🚀


Replace macOS native osuTK reflection

Replaces the reflected osuTK calls in MacOS.Native with real implementations.  Required as part of dropping osuTK.  Implementations loosely borrowed from osuTK.
Note that the FoundationLibrary reference is not required and has been removed.
Related to #2448

Reason?

The reason is direct: if there's framework provided functionality, always use it instead of directly calling into the OS.
Although this is not portable code, use NativeLibrary on every platform still looks cleaner.

Maybe I've misunderstood something. TryGetExport is mainly for loading function exports, not sure about string constants. But it at least worth a try.

I’m planning on replacing most of this native code with NativeLibraryLoader anyway.
https://github.com/mellinoe/nativelibraryloader

I didn't qualify it, but I meant System.Runtime.InteropServices.NativeLibrary. Please prefer it when it's suitable. .NET Core has worked a lot for cross-platform interop.

I'm not interested in increasing the complexity of implementation by using a new tool which may or may not have its own problems. This is just intended to take us further away from osuTK.


feat: add the workflow name in the response when a blueprint is publi…

What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds the workflow name in the response when we publish new blueprints.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Renaming contract function to register

Description
This PR adds minor change of renaming the contract function named addToGroup to more App oriented register.

Merging for speedy work.


windows with Fancy zone on don't stick on initial screen anymore when switching between virtual desktops

Microsoft PowerToys version
0.59.1
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce

put windows on both primary and secondary screens
switch to another (windows native) virtual desktop
put windows on both primary and secondary screens again
switch back and forth between

✔ Expected Behavior
Windows will always stay on corresponding screens
❌ Actual Behavior
some windows move to another screen
Other Software
No response

/bugreport

Currently, I've turn off the "fancy zones" due to this bug.
PowerToysReport_2022-07-07-14-23-55.zip

Is it reproducible in 0.65? Should be fixed there.
/needifo

I’m on holidays do it will be a few weeks before I can validate.
Regards, Wei Pien
On 19 Dec 2022, at 12:44, Seraphima Zykova @.***> wrote:

CAUTION: This email is from outside the organization. Do not click on links or open attachments unless you trust the sender.
Is it reproducible in 0.65? Should be fixed there.
/needifo
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/19161#issuecomment-1357612600, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJDTUNWTGC6BQHMKMYFD3LWOBKB5ANCNFSM52SXYKXQ.
You are receiving this because you authored the thread.Message ID: @.***>

The information contained in this email may be confidential and/or legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original email.

Classified
Hi Seraphima Zykova,
I’m on v0.66.0 since the update “jump” immediately to this. However, it seems it is fixed. Tnx.
Best regards / Met vriendelijke groet,
Wei Pien

Signify Research
High Tech Campus 7
Eindhoven, The Netherlands
Mobile: +31 6 11357579
From: Wei Pien Lee
Sent: Monday, 19 December, 2022 3:26 PM
To: microsoft/PowerToys @.>
Cc: microsoft/PowerToys @.>; Author @.***>
Subject: Re: [microsoft/PowerToys] windows with Fancy zone on don't stick on initial screen anymore when switching between virtual desktops (Issue #19161)
I’m on holidays do it will be a few weeks before I can validate.
Regards, Wei Pien
On 19 Dec 2022, at 12:44, Seraphima Zykova<EMAIL_ADDRESS>wrote:

CAUTION: This email is from outside the organization. Do not click on links or open attachments unless you trust the sender.
Is it reproducible in 0.65? Should be fixed there.
/needifo
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/19161#issuecomment-1357612600, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJDTUNWTGC6BQHMKMYFD3LWOBKB5ANCNFSM52SXYKXQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
The information contained in this email may be confidential and/or legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original email.

Classified
Hi Seraphima Zykova,
I sorry but unfortunately it has not been resolved completely. One situation still remains so far as I tested:

One screen/display only
1 window of the same application (e.g. outlook) on 2 virtual desktops
*   1 window on 1 virtual desktop fitted in fancy zone
*   1 window on other virtual desktop in fancy zone, but after that full screen
Switch (might need multiple times) between virtual desktops
The full screen window will revert back to fancy zone

Best regards / Met vriendelijke groet,
Wei Pien

Signify Research
High Tech Campus 7
Eindhoven, The Netherlands
Mobile: +31 6 11357579
From: Wei Pien Lee
Sent: Monday, 9 January, 2023 11:33 AM
To: microsoft/PowerToys @.>
Cc: microsoft/PowerToys @.>; Author @.***>
Subject: RE: [microsoft/PowerToys] windows with Fancy zone on don't stick on initial screen anymore when switching between virtual desktops (Issue #19161)
Classified
Hi Seraphima Zykova,
I’m on v0.66.0 since the update “jump” immediately to this. However, it seems it is fixed. Tnx.
Best regards / Met vriendelijke groet,
Wei Pien

Signify Research
High Tech Campus 7
Eindhoven, The Netherlands
Mobile: +31 6 11357579
From: Wei Pien Lee
Sent: Monday, 19 December, 2022 3:26 PM
To: microsoft/PowerToys<EMAIL_ADDRESS>Cc: microsoft/PowerToys<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/PowerToys] windows with Fancy zone on don't stick on initial screen anymore when switching between virtual desktops (Issue #19161)
I’m on holidays do it will be a few weeks before I can validate.
Regards, Wei Pien
On 19 Dec 2022, at 12:44, Seraphima Zykova<EMAIL_ADDRESS>wrote:

CAUTION: This email is from outside the organization. Do not click on links or open attachments unless you trust the sender.
Is it reproducible in 0.65? Should be fixed there.
/needifo
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/19161#issuecomment-1357612600, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJDTUNWTGC6BQHMKMYFD3LWOBKB5ANCNFSM52SXYKXQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
The information contained in this email may be confidential and/or legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original email.

/dup https://github.com/microsoft/PowerToys/issues/23292


feature request: scramble column

To maintain confidentiality when presenting data, a feature to scramble column would be nice.
scrambling changes the column in place and hides the keys in the table.metadata

overcome by events.


using a custom layer, loaded_model cannot give the same predicted value compared with original model [results not reproducible]

System Info

Tensorflow Version: 2.4.3
Custom Code: Yes
OS Platform and Distribution: CentOS Linux release 8.2.2004
Python version: 3.8
CUDA/cuDNN version: CUDA11, cuDNN8
GPU model and memory: RTX 3090, 24268MiB

Current Behaviour:
I implemented a custom layer, and use this layer to build a model. After training it, the original model gave a predicted value A, and the original model is saved as a h5 file. Then I load model from the h5 file, but the loaded model gave a different predicted value B, which means the results are not reproducible. Normally, the two models are supposed to give the same predicted value.
The custom layer is as simple as a Dense layer, and I have already locate that the custom layer caused the above problem. Actually, if I comment the line of custom layer, and uncomment the line below it (which is an original tf Dense layer), both the original model and the loaded_model gave the same results.
Standalone code to reproduce the issue
https://colab.research.google.com/drive/19_8DqzfC2JadKM9ZykJRLDEcxEkzjrT7?usp=sharing
Can also refer to the link where the issue is firstly posted: https://github.com/tensorflow/tensorflow/issues/59041
Relevant log output
2022-12-29 10:33:52.034627: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2022-12-29 10:33:53.136713: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2022-12-29 10:33:53.138072: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2022-12-29 10:33:53.198743: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:3d:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6
coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s
2022-12-29 10:33:53.198834: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2022-12-29 10:33:53.203166: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2022-12-29 10:33:53.203273: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2022-12-29 10:33:53.204328: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2022-12-29 10:33:53.204657: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2022-12-29 10:33:53.209031: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusolver.so.10
2022-12-29 10:33:53.209857: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2022-12-29 10:33:53.210030: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2022-12-29 10:33:53.212456: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2022-12-29 10:33:53.335970: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-29 10:33:53.348062: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2022-12-29 10:33:53.349549: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:3d:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6
coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s
2022-12-29 10:33:53.349604: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2022-12-29 10:33:53.349644: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2022-12-29 10:33:53.349654: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2022-12-29 10:33:53.349664: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2022-12-29 10:33:53.349673: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2022-12-29 10:33:53.349682: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusolver.so.10
2022-12-29 10:33:53.349691: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2022-12-29 10:33:53.349701: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2022-12-29 10:33:53.352041: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2022-12-29 10:33:53.352076: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2022-12-29 10:33:53.873305: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1261] Device interconnect StreamExecutor with strength 1 edge matrix:
2022-12-29 10:33:53.873357: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1267]      0
2022-12-29 10:33:53.873366: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1280] 0:   N
2022-12-29 10:33:53.877072: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1406] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 22430 MB memory) -> physical GPU (device: 0, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:3d:00.0, compute capability: 8.6)
/usr/local/lib64/python3.8/site-packages/tensorflow/python/data/ops/dataset_ops.py:3503: UserWarning: Even though the tf.config.experimental_run_functions_eagerly option is set, this option does not apply to tf.data functions. tf.data functions are still traced and executed as graphs.
warnings.warn(
2022-12-29 10:33:53.990568: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:116] None of the MLIR optimization passes are enabled (registered 2)
2022-12-29 10:33:53.997553: I tensorflow/core/platform/profile_utils/cpu_utils.cc:112] CPU Frequency:<PHONE_NUMBER> Hz
2022-12-29 10:33:54.015124: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2022-12-29 10:33:54.679072: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2022-12-29 10:33:54.679260: I tensorflow/stream_executor/cuda/cuda_blas.cc:1838] TensorFloat-32 will be used for the matrix multiplication. This will only be logged once.
625/625 [==============================] - 5s 7ms/step - loss: 0.4327
[[0.44245386]
[0.6916534 ]
[0.49306032]
[0.98741436]
[0.7631112 ]]
[[0.48893338]
[0.54947186]
[0.40105245]
[0.56347597]
[0.32270208]]

@h44632186 Sorry for the late response!
I don't have access to the drive link you have shared.
I tried to replicate the issue as mentioned in this ticket , please find the gist here and confirm the issue reported.
Thank you!

@sushreebarsa  Thank you for your response. The gist you posted is exactly the same as the ticket I mentioned.
As you can see, the predicted value (predicted_val in the code) of the original model, is different from the predicted value (predicted_val2 in the code) of the loaded model, so I confirm that you have already replicated this issue.

@sushreebarsa Btw, I have already identified it is the custom layer that caused the above problem. If I replace the custom layer with an original Dense layer (referring to the code), both the original model and the loaded_model gave the same results. So I think the problem is caused by the custom layer.

Hi @h44632186 ,
I was able to replicate the behaviour you mentioned and attached the gist here. Also requesting you to cross check and confirm.

Hi @SuryanarayanaY , I have checked the gist you posted, and confirmed it is correct.

Hi @h44632186 , I was able to replicate the behaviour you mentioned and attached the gist here. Also requesting you to cross check and confirm.

@SuryanarayanaY Hi, do you have any suggestions to solve this issue?

I think the issue here is that in your custom layer, you are creating a new dense layer every time you call the model. So each new call to the model will create a new dense layer with new random weights. This will mean you often totally lose the state of your model (and might get extra confusing with function tracing, where your traced model will not create new weights).
The recommended approach would be to not create variables or layers inside call like this. If you change your custom layer as below, everything works.
@tf.keras.utils.register_keras_serializable()
class Custom_Layer(tf.keras.layers.Layer):
    def __init__(self, units, **kwargs):
        super(Custom_Layer, self).__init__(**kwargs)
        self.units = units
        self.dense = tf.keras.layers.Dense(self.units)

    def call(self, x):
        x = self.dense(x)
        return x

    def get_config(self):
        config = super(Custom_Layer, self).get_config()
        config.update(units = self.units)
        return config

https://keras.io/guides/making_new_layers_and_models_via_subclassing/ has an in depth guide.

Hi @h44632186 ,
As mentioned in above comment, when using sub_classing of models or layers you need to define the layers inside the constructor to make them serializable and stateful.
I have modified your code as suggested above and now both models are able to reproduce same outputs. Please refer to attached gist. Thanks

@SuryanarayanaY , The constructor here has a layer but still the model is is serializable without explicit serialization and deserialization in get_config() and from_config() methods.   As per documentation  the layer should be serialized and de-serialized in get_config() and from_config() methods right?   What am I missing here ?


If we are using vote weight on open proposals we should remove vote summary as the data isn't there.

summary on list page highlighted

summary on vote page

We aren't using weight anywhere.
For this:

we're doing:
0.00%: proposal.votes.no.totalTokens * 100 / (proposal.votes.no.totalTokens + proposal.votes.yes.totalTokens)%
0: proposal.votes.no.totalTokens

participationMet = (proposal.votes.no.totalTokens + proposal.votes.yes.totalTokens) > totalSupply * requiredParticipation

okay. totalTokens isn't behaving the way we'd expect either.
I say lets go ahead with removing all the vote summaries. (worth keeping this branch bookmarked for future use)

We have now removed the summary view from Update Network Governance Proposal detailed view


Restore the ability to have content type facets when searching pages with an empty query

This restores the ability to have content type facets when searching pages with an empty query:

We lost the ability to do this in 5.1 when the view was refactored from an FBV to a CBV: https://github.com/wagtail/wagtail/pull/10615/commits/52abcee04363ea9dae36ecbd87b01f4137a7ce3e#diff-dc3a1012fc5394a6a1abd8e254ed29cfd5107ba2fc6bb7b6127b4e6386d8dea9L108
The facets are only applied if there's a search query. Previously this was detected with if "q" in request.GET, but it was changed to if self.q (with self.q = request.GET.get("q", "")), so empty queries (e.g. clicking search on the left menu and press enter without typing anything) will not show the content type facets.
In addition, the adoption of #10645 to make the header search use the Stimulus SwapController would mean the facets will also be lost if you type something in the header search and clear it afterwards, as the q query param will be removed:
https://github.com/wagtail/wagtail/blob/ba17ef19d333570d9cca0195178e5e15babae93c/client/src/controllers/SwapController.ts#L178-L183
To fix this, we can either:

always do a search and apply the facets even if the query param is empty (which I've done here)
or, make a distinction between and empty q vs a non-existent q, and then also update SwapController so that it doesn't remove empty query params. I tried doing it this way in 7ec15f7aa08f25df5d27e273d43d98fe3fe13b4e, but it seems more intrusive.

This will probably be made redundant with page type filters in Universal Listings (#10446), but at the moment there's no alternative when you'd like to see all pages filtered by the page type. (Maybe #10850, but that's a separate topic.)
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?

[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Merged in 3af26aa30e82bbb6d5c9988fc7d23e1fcc9fe74b (main) / e8ff6a2fa3 (stable/5.2.x).


Login to Hypothesis not intuitive

Description
Continuation of #21
A description of the bug
Despite the login to hypothesis banner, users are still unable to grasp that they should use the Hypothesis annotation sidebar to login to see their annotations.
Solution

make sign up text in the banner more prominent with same color and font size as the sign up text in the sidebar
reference that the sidebar is in the right of the screen

@adam3smith One benefit I could see from using OAuth for Hypothesis login is that this problem will go away. Users will be logged into Hypothesis throughout the AnnoRep app after they have logged in at the login page.


feat: Support for custom context and/or debug html files

Adding support for custom context.html and debug.html
module.exports = function(config) {
  config.set({

    client: {
      // paths must be relative to CWD ( current working directory )
      contextFile: '/context.html',
      debugFile: '/debug.html'
    },

    ...

Ref: #488

Stumbled upon this from #488. I'm keen on this idea, as I'm struggling with QUnit and es6 module loaders, the problem is QUnit racing against the async module loaders, which appears to mandate something akin to the following as a solution (but as yet untested) https://github.com/jrburke/requirejs/wiki/Test-frameworks#qunit

I'm trying to migrate our test suite (10,000+) from jasmine-rails to Karma and this would definitely help. A lot of our legacy tests insert into a specific div in our current runner html.

@jrolfs for what it's worth (and, that's "not much", I know) I "solved" my problem by using https://github.com/opudalo/generator-es6-lib which is a completely different stack of tools…

@leehambley thanks for the suggestion (will be useful for other projects :smiley:), however unfortunately it's not really an option for the project in question.

Thanks, this looks mostly good, a few things to do please

follow our commit message convention
update the docs so people can find these options
these options shouldn't be nested in the client configs, they should be top level and default to the ones karma brings
path normalization and setting defaults should be done in lib/config.js
please rebase onto the canary branch and make the PR against canary as this will become the new stable version in the next days

Ok. I will try to fix all of those point as soon as possible. Is it ok if in the end I'll make a new pull request ?

Is it ok if in the end I'll make a new pull request ?

Sure, github doesn't let you change the branch sadly

Ok. I will mention new pull request here..

I signed it!

I have applied the changes to the 0.13.9 release here: https://github.com/Sanjo/karma/tree/0.13.9%2Bcustom-context-html.
I have signed the CLA in the past.

@Sanjo could you open a new pr with your changes please?

Closing due to inactivity


Ship a templated system systemd unit

Older versions of systemd have problems with the user unit.
See https://github.com/cdr/code-server/issues/1747#issuecomment-639150485

Should also switch from exec service for this file as older systemd's don't recognize it.
For anyone who just wants to use the bundled service now, you can easily fix by running:
sudo cp /usr/lib/systemd/user/code-server.service /etc/systemd/system
sudo vim /etc/systemd/system/code-server.service
sudo sed 's/\(Restart=always\)/\1\nUser=$USER/' /etc/systemd/system/code-server.service
sudo systemctl daemon-reload
sudo systemctl enable --now code-server

It'll make code-server a system service and add your current user into the service file and start it for you.

To be clear, the above will fix errors similar to "Failed to get D-Bus connection" which is what happens when using a user unit on an old version of systemd.

@nhooyr Thanks for your solution. After run above cmd, I successed created symlink in default.target, but I can't start code-server, until I change the line 'User=$USER' in code-server.service to 'User=admin' with a real username , and its failed status below:
$systemctl status code-server

● code-server.service - code-server
   Loaded: loaded (/etc/systemd/system/code-server.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2020-06-09 21:25:00 CST; 39min ago
  Process: 8866 ExecStart=/usr/bin/code-server (code=exited, status=217/USER)
 Main PID: 8866 (code=exited, status=217/USER)

Jun 09 21:25:00 instance-1 systemd[1]: code-server.service: main process exited, code=exited, status=217/USER
Jun 09 21:25:00 instance-1 systemd[1]: Unit code-server.service entered failed state.
Jun 09 21:25:00 instance-1 systemd[1]: code-server.service failed.
Jun 09 21:25:00 instance-1 systemd[1]: code-server.service holdoff time over, scheduling restart.
Jun 09 21:25:00 instance-1 systemd[1]: Stopped code-server.
Jun 09 21:25:00 instance-1 systemd[1]: start request repeated too quickly for code-server.service
Jun 09 21:25:00 instance-1 systemd[1]: Failed to start code-server.
Jun 09 21:25:00 instance-1 systemd[1]: Unit code-server.service entered failed state.
Jun 09 21:25:00 instance-1 systemd[1]: code-server.service failed.

So I want to know the cmd
sudo sed -i 's/\(Restart=always\)/\1\nUser=$USER/' /etc/systemd/system/code-server.service

should  replace single quote with double quote  to add the current real username.
sudo sed -i "s/\(Restart=always\)/\1\nUser=$USER/" /etc/systemd/system/code-server.service

@yaerda Great catch!

@nhooyr Thank you so much!  This works great.
@yaerda And thank you for the input.
You're answer got my instance up and running.

Also see the linger issues #1673 #1882 #1861

So the reason I couldn't reproduce before is I use ssh connection sharing which kept my ssh connection open even after I exited. So definitely need this to fix that.

v3.5.0 with VS Code v1.48.2 has been released, fixing this issue! 🍻


feat: fix apple toolchain apple framework

I've just been roughly trying to get this to work for my local setup. some of this is a bit hacked away to get this to work but I think its in the general right direction.
this is what I have in mind for resolving the apple tools
find_apple_tools(
    name = "apple",
    architecture = "amr64",
    sdk_name= "macosx",
    visibility = ["PUBLIC"],
)

here is the working code I'm trying to test

apple_binary(
    name = "main-apple",
    srcs = ["main.mm"],
    link_style = "static",
    frameworks =  ["$SDKROOT/System/Library/Foundation.framework"],
    compatible_with = ["config//os:macos" ],
    target_sdk_version = "14.5",
    deps = [":print"],
)

here is my sample application that  I've been testing these changes with: https://github.com/OSS-Cosmic/buck2-samples/tree/main/hello_world
I need to build this locally and verify it on my own system but this is what I have so far.

I added a small example to hello world to demonstrate this working. how does cxx_library and cxx_binary fit into this because those break if they don't have an sdk version available


setNextRequest

Postman provides this capability:
https://www.getpostman.com/docs/v6/postman/collection_runs/building_workflows
Typically, this is used after a response param is evaluated

Possible implementation:
version: 1

requests:
  todoOne:
    url: https://jsonplaceholder.typicode.com/posts
    method: POST
    data:
      json:
        foo: 1
  todoTwo:
    if:
      operator: Value(todoOne.skip)
      value: 2
    url: https://jsonplaceholder.typicode.com/todos/2
    method: GET

Only the first request above would execute.  todoTwo should create a logging event as skipped


Sending Quite Large File from BLE device to App

Hi everybody. I need to send a file .txt from a device to my app (worst case almost 2mb). The BLE device divide the file into packages. I don't know if my method is correct, but I create a loop of characteristic.write/characteristic.read telling everytime what package the device has to send.
Here's my code:
`for(int i = 0; i < packNumber.length; i++) {
initialValue = '9,50,100,$i,0,$checksumId,0/';
await characteristic
.write(utf8.encode(
initialValue))
.then(
(wValue) async {
await Future.delayed(Duration(milliseconds: 100)).then((value) async {
await characteristic.read().then((rValue) {
//do something with rVlaue
});
});
});
}`
It works, but is it the best solution? And in case how can I speed up the transfer (for now I have to set a delay before reading, waiting for characteristic.write to finish)?
Thank you guys

Nobody has any suggest? I need to know if I am on the right way or not

Nobody has any suggest? I need to know if I am on the right way or not

I tried to do this, but there was a packet loss anyway.
It's hard to get all the packets.
Note: my file size is about 20m

I tried to do this, but there was a packet loss anyway.
It's hard to get all the packets.
Note: my file size is about 20m

I don't have a packet loss with withoutResponse:false, but is not so fast

I don't have a packet loss with withoutResponse:false, but is not so fast

Maybe this repo helps you:
https://github.com/KevinRohn/flutter_ble_data_handler

Maybe this repo helps you:
https://github.com/KevinRohn/flutter_ble_data_handler

Thank I will try it.
To optimize the transfer instead of using c.read i tried with c.value.listen(....) which detect any values changing. Maybe is the right way, but why packages I receive with c.read are 64byte long and packages with c.value.listen are maximum 20byte long??

Thank I will try it.
To optimize the transfer instead of using c.read i tried with c.value.listen(....) which detect any values changing. Maybe is the right way, but why packages I receive with c.read are 64byte long and packages with c.value.listen are maximum 20byte long??


Twitter Alerts

And player.me if possible.

What do you mean by this

Basically @spy functionality with twitter.

Oh my...


panic: block: expected 3 arguments (columns: id, name, action_time), got 6

tx.MustExec("INSERT INTO test.test (id,name,action_time) VALUES ($1, $2, $3),($4, $5, $6)",
"888", "desct", "2019-12-13",
"666","desct", "2019-12-13"
)

This seems to work in general.  The error message leads me to believe that this isn't the line that is in error, but some call to NamedExec or similar somewhere.  If you can provide a failing test or more context feel free to re-open.

This seems to work in general.  The error message leads me to believe that this isn't the line that is in error, but some call to NamedExec or similar somewhere.  If you can provide a failing test or more context feel free to re-open.


Add show constraint to the input of display blocks

Probably doesn't make a big difference, but changed anyway.

Great, thanks!


default method found in version 50.0 classfile

Error:(19, 20) error: cannot access Editable
bad class file: D:\ANDROID\DEVELOPMENT\ADT\sdk\platforms\android-24\android.jar(android/text/Editable.class)
default method found in version 50.0 classfile
Please remove or make sure it appears in the correct subdirectory of the classpath.

Similar to this: https://github.com/anggrayudi/android-hidden-api/issues/24

Yes, it's same.

Already fixed, using this version.
https://goo.gl/08ZeXy
please check and update if needed

This issue was fixed in hidden API v25.


Wrong parents for Java annotations

Scalac adds fake superclasses / superinterfaces to parents of Java annotations. This has semantic importance, so it's gotta be fixed in metacp.

I have changed my opinion on this ticket since opening it. I think it is wrong to change the list of parent classes of a class based on the language. It's a pretty weird concept as is, given otherwise great interop between Java and Scala, and we don't even have the infrastructure to accommodate this notion in SemanticDB. I'll be closing as wontfix.

Looks like this won't be a problem soon: https://github.com/scala/scala/pull/6869.


[BUG] tasker-integration not working when alternate symbol is active

When "alternate Icon" is enabled in the settings, tasker-intents are not working.
As soon as the box is unchecked, everything is fine again.

Please don't just delete the issue template, I added it for a reason.


Type 1: support a REST API: Warning about PAT expiry

Summary
When authenticating with a personal access token (PAT) a duration until the expiry of the token is returned by the login request.
This information is dropped by the python client, yet would be useful to have it logged as a warning when the expiration date is near.
Description
As users of the python client, we have automated some data-engineering tasks, and authenticate with PATs.
Since the PATs may be configured to expire after a given period of time, it is necessary to keep track of when tokens need to be renewed.
The time until expiry is available in the following REST Request:
https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_auth.htm#make-a-sign-in-request-with-a-personal-access-token
Since this request is already made as a part of the authentication process in the python client, I would like to extend the client to pass two optional parameters to the sign_in method:

token_expiry_warning_threshold: Optional[int] = 60
token_expiry_warning_callback: Optional[Callable[[str], None]]

The provided threshold should be an integer which represents days. If the token is set to expire in less days than in the threshold, a warning should be logged. I think 60 days is a sane default given the default expiration period is after 1 year.
A callable may also be provided which will be called with the string containing the time until expiry as received from the API. Its format is "days:hours:seconds".

I'm willing to add this myself

I'm now unsure if the value returned from the login request contains the time until the PAT expires, or the session token. Could someone confirm which of the two it is, if it is the later, then this feature request would require an API change.

This will require an API change, but it's already a known customer request so it might be in the works.
From https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref.htm#sign_in
An estimatedTimeToExpiration value is returned when you sign in using a PAT. The value represents the approximate time until the token returned from the PAT sign in will expire

Thanks for the update!
Could you help me find a link to the customer request, so that we can get an update here once the server-side-update is complete?
That way we can get started on this once the blocker is out of the way.

Hmm I'm not sure there is one, but if I find it I will add it here.

@jacalata any update on whether expiration_date will be added to response when calling server.auth.sign_in()?
It's already a manual effort to refresh an expired token.
But it would be nice to have this expiration_date, so we can preemptively alert our team that the token is expiring.
The best solutions our team has found:

(Proactive) Hardcode the "known" expiration_date in our logic, and alert when that date is approaching
(Reactive) Try-Except for ServerResponseError when calling server.auth.sign_in(), to raise alert about expired token

Note that:

the first solution requires code changes (every time our token expires)
the second solution means our process breaks (every time our token expires)

CC @aharcarik-branch

This has been implemented server-side (in List Personal Access Tokens), but we haven't got it in tsc yet.


Tag a Release

I am writing a port file for VCPKG to make this library easy to install with the VCPKG package manager.  However, I do need this repository tagged with a release.  I created a fork at https://github.com/DigitalInBlue/iowahills_dsp, and you can see how I tagged a release.
My pull request with Microsoft to add this library to VCPKG is in process. I would greatly appreciate it if you could expedite tagging a release!

just noticing your issue. what version or tag name would you suggest?
be aware, that most stuff isn't tested!

I don't have a strong opinion, but if you could tag it v0.1.0, that would be enough to get the VCPKG portfile complete.

Done so, yesterday


Helper idea: add branchIfTruthy()?

I ran into a use case for branchIfTruthy() (the opposite of branchIfFalsy()). Probably wouldn't do any useful type-narrowing (I guess could narrow out true) but would be a useful shorthand

Fixed by #30


Improve docstrings for Pydantic models

Pydantic model classes had completely unhelpful docstrings. This is a design decision by the Pydantic folks, but they provide a workaround (the ability to change the __doc__ attribute via a post-initialization hook). This is implemented. Resolves #303

Can you document this Pydantic design decision in the PR?
@gordonwatts - I'm going to wait for you to verify your docstring woes

Can you document this Pydantic design decision in the PR?
Done - link to github thread added


Configure TX power = 30 dbm?

With a working 1W custom ESP32/LoRa board now (thanks to you & Bob-N6RFM!), I noticed that the default tinyGS "Power" parameter (5 dbm) did not take advantage of this device's power output capability.
Using the "Configure Parameters" screen on the tinyGS web GUI (direct LAN IP connection to the device), I entered a value of "30" on the Modem Startup line.
.
.

.
However, after applying it, an error appears on the serial monitor:
 failed, code<PHONE_NUMBER>
... reviewing the tinyGS code (including libraries), I see the following comment in "lib/RadioLib/src/modules/SX126x/SX1268.h":
 \brief Sets output power. Allowed values are in range from -9 to 22 dBm.
... indeed, the largest value that I can enter (with no error) on the 'Modem Startup' line in the web GUI is "22"
What steps are required to allow for a value of 30 dbm (i.e., 1W) to be used in this context?
Thanks!

You can't enter 30 dBm directly into RadioLib configuration methods, since those are limited by the SX1268 limitations, in this case by the maximum output of the internal PA, which is 22 dBm.
Ebyte 400M30S has an external PA, labeled as H0606E - some Chinese wunderwaffe. Googling a bit yields this datasheet: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/RELL-2D00-LDMOS.pdf
According to that, it should have a 19 dB gain (up until 13 dBm input), so to set 30 dBm on the output of the module, you have to set 11 dBm as the output from SX1268. I'm still trying to verify those numbers with an actual RF power meter, since this sort of parts always makes me suspicious.

Hello!
Any update on the proper way to use full TX power?
I see that the limits can be changed in /lib/RadioLib/src/modules/SX126x/SX1268.h ... but I don't have a watt meter to verify the device's output if it's set to '30' after adjusting that upper limit setting.
Thanks!

As per my previous message, you don't set the SX1268 power output to 30 dBm when using the ebyte module. Instead, you have to set to the SX1268 power output in such a way that the external PA will output 30 dBm. The PA gain is 19 dB, so to get 30 dBm total power, you have to set SX1268 power to 11 dBm by calling setOutputPower(11);.

Ah, thanks so much!   You had mentioned doing a verification to see if that really resulted in the desired max output, so I didn't know if that had been possible to check on yet.
Appreciate everything!

Unfortunately not yet, I don't have access to a good RF power meter at the moment due to lockdown-induced logistics issues.

what is the smallest gain of these modules? (max is 30db (set 11) and min?

You can't enter 30 dBm directly into RadioLib configuration methods, since those are limited by the SX1268 limitations, in this case by the maximum output of the internal PA, which is 22 dBm.
Ebyte 400M30S has an external PA, labeled as H0606E - some Chinese wunderwaffe. Googling a bit yields this datasheet: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/RELL-2D00-LDMOS.pdf
According to that, it should have a 19 dB gain (up until 13 dBm input), so to set 30 dBm on the output of the module, you have to set 11 dBm as the output from SX1268. I'm still trying to verify those numbers with an actual RF power meter, since this sort of parts always makes me suspicious.

If you set SX1268 output greater than 11dBm does it fry the board?

@SlitheringMule it shouldn't, you just won't get much extra gain. You're also risking compromising the signal integrity, since you're out of the linear region of the gain curve.


Fixed npm warnings in package.json

Linked the license file
Added the repository field
Removed duplicate 'grunt-contrib-watch'

Made this based on the output of npm install:
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>license should be a valid SPDX license expression
npm WARN package.json Dependency 'grunt-contrib-watch' exists in both dependencies and devDependencies, using<EMAIL_ADDRESS>from dependencies
npm WARN deprecated<EMAIL_ADDRESS>use grunt-ng-annotate instead
npm WARN deprecated<EMAIL_ADDRESS>Package renamed to phantomjs-prebuilt. Please update 'phantomjs' package references to 'phantomjs-prebuilt'
npm WARN deprecated<EMAIL_ADDRESS>breaking interface change
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"~0.8.0"} (current: {"node":"4.4.3","npm":"2.15.1"})
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Deprecated, use jstransformer
npm WARN deprecated<EMAIL_ADDRESS>use ng-annotate instead
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

 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.


Crash on end-block = -1

I have noticed that the indexer will consistently crash with these settings as soon as it hits the last block available on that chain.   PLEASE INVESTIGATE

@pharr117 can we close this?  I think this is resolved for transaction indexing, but not sure about rewards indexing.  I have a feeling this gets resolved when we add back in sequential rewards indexing

Kyle implemented a fix for this one, notified in this comment:
https://github.com/DefiantLabs/cosmos-tax-cli/issues/336#issuecomment-1482149097
The fix he pushed should treat all TX parsing the same, there was a bug in the secondary fallback that was not treating the logs correctly.
As far as rewards indexing with -1 end block is concerned, we will track work here:
https://github.com/DefiantLabs/cosmos-tax-cli/issues/380


Module 'numpy' has no attribute 'object'.

Describe the bug
I attempted to run sourcecode/main.py and received the following error:
AttributeError: module 'numpy' has no attribute 'object'.np.objectwas a deprecated alias for the builtinobject. To avoid this error in existing code, use objectby itself. Doing this will not modify any behavior and is safe.  The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:     https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did you mean: 'object_'?
If I replace instances of 'np.object' with 'object', the error is resolved, but I also have to do the same with 'np.str' and 'np.float'.
This is a Windows environment. Is there a suggested environment? I did not see any in the documentation.
I saw this was referenced in issue #87, so I also tried to run on Ubuntu 22.04.2 LTS (via WSL2) and received the same error. The comments on the issue said the Python script was meant to run in *nix environments, but it's not clear which.
To Reproduce
Steps to reproduce the behavior:

With data files present in the 'sourcecode' folder and command prompt at the same folder, run:
python .\main.py --enrollment .\userEnrollment-00000.tsv --notes .\notes-00000.tsv --ratings .\ratings-00000.tsv --status .\noteStatusHistory-00000.tsv --outdir scored_notes.tsv
Observe output for errors.

Expected behavior
The script should execute without error.
Environment
Windows 11 Pro (22621.1702)
Python 3.11.3
numpy 1.24.3
Also:
Ubuntu 22.04.2 LTS (via WSL2)
Python 3.10.6
numpy 1.24.3

I've also had the same error and fixed it the same way. My guess is that they're using a numpy version < 1.20.
I originally hoped to just install numpy 1.19 instead of having to patch the deprecated calls, but numpy 1.19 doesn't build on ARM Macs.

I attempted to do install numpy 1.19, as you suggested, but the build dependencies failed during pip install on both Windows and my Ubuntu installation. We're going back 2 years there and 1.20 was apparently a major update, so I'm not surprised.
It looks like it would be best to just update the code to work with latest versions. I'd be willing to try, but I've never contributed to an open source project, so I'd have to do some reading first. I'd also need to know the target environment currently used so I could test that my changes (which seem rather minor to me) don't break anything on the target *nix system.

Thanks, that helps. Could you possibly provide a pip list with the versions of the dependencies? Specifically:
numpy (1.19.2)
pandas
matplotlib
torch

Are you having success running it now, @intheweeds ?
I see above that 'numpy 1.19 doesn't build on ARM Macs' and I'm on an ARM Mac, so I can't run the code on one?  I tried and failed.   Could help troubleshoot the two bugs I've opened.

Thank you! Please reopen this if my fix doesn't resolve this for you.

Failure ... and success!
FYI, this did not help:
https://github.com/twitter/communitynotes/commit/0191c30410e217f5a02fa7c3f58b60a1bceea98d
It  (the virtual environment) resulted in the errors below* when I tried pip install -r requirements.txt.
On the other hand, I did have success, after:

Updating my source with git pull origin main
Adding export PATH="/opt/homebrew/opt/python@3.11/libexec/bin:$PATH" to my .zshrc, per https://apple.stackexchange.com/a/450306/33389,
running brew update
giving up on the virtual environment
Optimistically installing the default (latest) versions of pandas, matplotlib and torch.
Running python3 ../main.py from .../communitynotes/sourcecode/data worked on data files from May.

*errors (also posted to the path):
Collecting numpy==1.19.2 (from -r requirements.txt (line 1))
  Downloading numpy-1.19.2.zip (7.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.3/7.3 MB 9.3 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [58 lines of output]
      Running from numpy source directory.
      setup.py:470: UserWarning: Unrecognized setuptools command, proceeding with generating Cython sources and expanding templates
        run_build = parse_setuppy_commands()
      warning: _philox.pyx:19:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310

      Error compiling Cython file:
      ------------------------------------------------------------
      ...
                  self.rng_state.ctr.v[i] = counter[i]

              self._reset_state_variables()

              self._bitgen.state = <void *>&self.rng_state
              self._bitgen.next_uint64 = &philox_uint64
                                         ^
      ------------------------------------------------------------

      _philox.pyx:195:35: Cannot assign type 'uint64_t (*)(void *) except? -1 nogil' to 'uint64_t (*)(void *) noexcept nogil'
      Processing numpy/random/_bounded_integers.pxd.in
[...]

Doh!  Of course my attempt to use the venv didn't wor - it was still trying to install numpy 1.19, which isn't possible on M1.


New definition files

Adding multiple definition files for:
Anonymizers
bittorrent
cracks_keygens
critical_processes
bitcoin miners
proxies, intercepts
screensaver bypass
sysinternals suite

In general, do we want to get into the business of maintaining past and
future hashes for some of these items? I believe that I understand why
they're present, but given that these are survey definitions as opposed to
detection criteria, I think that we may be signing up for unnecessary
maintenance.
On Tue, Aug 9, 2016 at 1:14 PM Michael Haag<EMAIL_ADDRESS>wrote:

Adding multiple definition files for:
Anonymizers
bittorrent
cracks_keygens
critical_processes
bitcoin miners
proxies, intercepts
screensaver bypass
sysinternals suite
You can view, comment on, or merge this pull request online at:
https://github.com/redcanaryco/cb-response-surveyor/pull/1
Commit Summary

Critical Process Check
Additional critical processes
Update critical_process.json
Definition Files

File Changes

A definitions/anonymizer.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-0
(8)
A definitions/bittorrent.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-1
(8)
A definitions/cracks_keygens.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-2
(30)
A definitions/critical_process.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-3
(36)
A definitions/miners.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-4
(52)
A definitions/proxies_intercepts.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-5
(9)
A definitions/screensaverbypass.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-6
(12)
A definitions/sysinternals.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-7
(205)

Patch Links:

https://github.com/redcanaryco/cb-response-surveyor/pull/1.patch
https://github.com/redcanaryco/cb-response-surveyor/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/redcanaryco/cb-response-surveyor/pull/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AGjvOozD35QBF-q_h3K29yh0F-zrFOpgks5qeLVmgaJpZM4JgT1C
.

The content of this message is the proprietary and confidential property
of Red Canary, Inc., and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by reply
e-mail. Any unauthorized use or distribution of the content of this message
is prohibited.

It occurred to me that you might not get emails from Github when I reply to
these. I've no idea how that works.
Anyway, see below :)
On Wed, Aug 10, 2016, 7:08 AM Keith McCammon<EMAIL_ADDRESS>wrote:

In general, do we want to get into the business of maintaining past and
future hashes for some of these items? I believe that I understand why
they're present, but given that these are survey definitions as opposed to
detection criteria, I think that we may be signing up for unnecessary
maintenance.
On Tue, Aug 9, 2016 at 1:14 PM Michael Haag<EMAIL_ADDRESS>wrote:

Adding multiple definition files for:
Anonymizers
bittorrent
cracks_keygens
critical_processes
bitcoin miners
proxies, intercepts
screensaver bypass
sysinternals suite
You can view, comment on, or merge this pull request online at:
https://github.com/redcanaryco/cb-response-surveyor/pull/1
Commit Summary

Critical Process Check
Additional critical processes
Update critical_process.json
Definition Files

File Changes

A definitions/anonymizer.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-0
(8)
A definitions/bittorrent.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-1
(8)
A definitions/cracks_keygens.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-2
(30)
A definitions/critical_process.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-3
(36)
A definitions/miners.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-4
(52)
A definitions/proxies_intercepts.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-5
(9)
A definitions/screensaverbypass.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-6
(12)
A definitions/sysinternals.json
https://github.com/redcanaryco/cb-response-surveyor/pull/1/files#diff-7
(205)

Patch Links:

https://github.com/redcanaryco/cb-response-surveyor/pull/1.patch
https://github.com/redcanaryco/cb-response-surveyor/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/redcanaryco/cb-response-surveyor/pull/1, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGjvOozD35QBF-q_h3K29yh0F-zrFOpgks5qeLVmgaJpZM4JgT1C
.

The content of this message is the proprietary and confidential property
of Red Canary, Inc., and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by reply
e-mail. Any unauthorized use or distribution of the content of this message
is prohibited.

Correct. Makes sense to start now without MD5's before we get too deep and unable to manage.
Removed MD5's.

Two new definition files added:
Network sniffers
Network scanners

This is a test comment. Ignore.


Text summarization in C#

Hi,
I am new to tensorflow. I have requirement to use text summarization from .Net code.I have taken the latest code but it has erros and it's not building.How to use this code for text sumarization and guide how can we integrate tensorflow with c# for summarization. Thanks.

Use the NuGet package.
As for text summarization, that is beyond the scope of the Github issues, it is only to report issues with the binding itself.


Fixes #39: Topics stop refreshing

Background
During initialization, kbrowse starts a separate thread that intermittenly
refreshes the topics lists from the kafka brokers.
If an exception was thrown during a refresh, the thread died,
and topics would stop refreshing.
This could happen if a cluster were down for long enough to trigger a
timeout exception, for example.
Fix
This adds exception handling around the refresh call.
If we catch an exception, we log it, but continue on.
Test Plan

Start Kafka/Zookeeper:

./run-zookeeper-and-kafka

Start kbrowse:

KAFKA_TOPICS_CACHE_SLEEP_SECONDS=5 ./lein run server

Ctrl-C Kafka/Zookeeper

Wait for kbrowse timeout to log

Restart Kafka/Zookeeper

Create new topic:

./kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --create --topic kbrowse-2 --partitions 10 --replication-factor 1

Verify that the new topic shows up in running kbrowse:

http://localhost:4000

This looks good to me.  Thanks for tackling it!


Fix mounts

main changes:

make the mounts shared
mount more stuff (/dev/pts, /sys/kernel/security, /dev/shm, etc...)
create dirs with proper permissions
creates some special nodes for devices (migth be possible to remove)
move existing mounts from / to /sysroot
cp -r the dirs in rootfs that are not mounts into /sysroot as we are deleting the old sysroot afterwards
only create target dirs if they are not there
move /sysroot to be the new mount (hint, do it after chdir)
do not chroot to run initramfs stage if we are on uki.

hard for me to understand some of the changes but code wise LGTM

yes indeed, you are missing 3 days of backstory. In the end the result is the same. Nobody knows why but this fixes it xDDDDDDD

I guess I'm glad I missed the context then lol

This works?! So it was pretty much everything we tried at the same time, plus some things on top :DDDD! Good job @Itxaka ! I'll give it a spin later today. You deserve a beer (or two).

ok afaict, works with no problems. Let's merge!


Not support blob.

local protobuf = Type({
device = SQLiteRecordDevice("data.db"),
schema = Schema('protobuf', function(schema)
schema:text('body')
schema:blob('buff')
end),
}, Record)
local t = protobuf()
t.body = cjson.encode(body)
t.buff = '\0\0\0'
t:save()

I had recheck.
Now the current version doesn't binary statement.
So it may need some day to make it supported.


mail/send rate limit inconsistency

https://sendgrid.com/docs/API_Reference/api_v3.html (MAIL SEND / Limitations) says:

3000 requests/sec is the maximum rate at which you may call v3 Mail endpoint.

https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html says:

10,000 requests/sec is the maximum rate at which you may call v3 Mail endpoint.

See this related commit: 5903889c36f601e125ad1bced4d0a3770c798043

@ewirch - great catch, and thanks for the related commit for reference! I've updated it in the swagger docs - this should propagate out to the docs in the next hour or so.


add rapids-get-pr-wheel-artifact for quickly downloading cpp wheels

This idea comes from a slack DM with Viyas:

OK, so the first piece I'm thinking of is artifact download. If you look at the raft PR, we have snippets like this:
artifact_name=$(RAPIDS_PY_WHEEL_NAME="librmm_${RAPIDS_PY_CUDA_SUFFIX}" RAPIDS_REPOSITORY=rmm RAPIDS_PY_VERSION="3.11" rapids-package-name wheel_python)
commit=$(git ls-remote https://github.com/rapidsai/rmm.git refs/heads/pull-request/1512 | cut -c1-7)
librmm_wheelhouse=$(rapids-get-artifact "ci/rmm/pull-request/1512/${commit}/${artifact_name}")

The snippet above demonstrates two issues:
There isn't an easy way to download arbitrary PR wheel artifacts. However, there is such a tool for conda artifacts. That was added in https://github.com/rapidsai/gha-tools/pull/85. What we want is to generalize this tool to work for wheels.
The librmm wheel should not be specific to a particular Python version because it's a pure C++ wheel. However, our current naming scheme on downloads.rapids.ai doesn't know that. I'm currently hacking it by specifying the RAPIDS_PY_VERSION="3.11". This is working because I'm restricting the C++ wheel build CI job to only run with Python 3.11. There was another recent gha-tools PR that added support for pure Python wheels. What we want is to generalize this tool to also work for C++ wheels. The main difference is that C++ wheels have to care about arch, whereas pure Python wheels do not

I think a good starting point would be to make PRs to gha-tools to address the above issues. Does that make sense?

At the time that I'm submitting this, I haven't yet found examples of the wheels_cpp files. Vyas is working on fleshing those out, and I will be taking over that work from him once he gets it on the right track.

Note that we may not update every repo that's using these tools to the new wheels strategy, but we will at least have to ensure that we update them for the breaking changes here.

On second thought, the breaking change here may not be the best approach. I thought it would be a helpful guide for which repos need fixing to add wheel support. If it's going to disrupt things with a lot of repos for no change to those repos, then I think it might be better to preserve the wheel_python default behavior.
Maybe something like:
# default assumes wheel_python. If manually specified, do that instead.
pkg_name="$(rapids-package-name wheel_python)"

if [ "$1" = "cpp" ] || [ "$1" = "python" ]; then
	pkg_type=$1
	pkg_name="$(rapids-package-name "wheel_${pkg_type}")"
	# remove pkg_type from args because we handle it in this script
	shift;
fi

It would also be good to update the docs showing how this works once we finalize and merge this tool.

/merge


Add sample orgs and rename project section to "Explore"

For preview:
https://htmlpreview.github.io/?https://github.com/oviohub/oviohub.github.io/blob/explorer/index.html

Make sure categories are similar.
Ex: either you choose general ones for all such as Humanitarian, Healthcare... or you choose general ones  +a sub-category such as data management, mapping...
Humanitarian ToolBox is similar to Open Data Kit so its category would be Humanitarian Data Management as well or both should have just Humanitarian.
The rest is great!


loss alarm should be set solely based on the current state

The quicly_loss_update_alarm function implements SetLossDetectionTimer.
In contrary to what the recovery draft has been suggesting (IIUC from the very beginning), we have been updating the timer only when the value calculated by the most recent state is smaller than the current value of the loss detection alarm.
This PR fixes the issue.

@janaiyengar would you mind checking if this is the correct thing to do. No need to hurry, I am not stumbling upon this bug. I just noticed this while trying to fix a different issue.

Yeah my intuition is that this would fix the occasional failure we are seeing in the first test of e2e.t. When it fails, we see something like:
        # {"type":"quictrace-recv-stream", "time":1552725032120, "conn":0, "stream-id":0, "off":0, "len":12, "fin":1}
        # {"type":"stream-receive", "time":1552725032120, "conn":0, "stream-id":0, "off":0, "len":12}
        # {"type":"send", "time":1552725032121, "conn":0, "state":2}
        # {"type":"packet-prepare", "time":1552725032121, "conn":0, "first-octet":64, "dcid":"4d6afaf1387e1671"}
        # {"type":"transport-close-send", "time":1552725032121, "conn":0, "error-code":256, "frame-type":0, "reason-phrase":""}
        # {"type":"packet-commit", "time":1552725032121, "conn":0, "pn":7, "len":32, "ack-only":1}
        # {"type":"quictrace-sent", "time":1552725032121, "conn":0, "pn":7, "len":32, "packet-type":3}
        # {"type":"send", "time":1552725032174, "conn":0, "state":2}
        # {"type":"packet-prepare", "time":1552725032174, "conn":0, "first-octet":64, "dcid":"4d6afaf1387e1671"}
        # {"type":"transport-close-send", "time":1552725032174, "conn":0, "error-code":256, "frame-type":0, "reason-phrase":""}
        # {"type":"packet-commit", "time":1552725032174, "conn":0, "pn":8, "len":32, "ack-only":1}
        # {"type":"quictrace-sent", "time":1552725032174, "conn":0, "pn":8, "len":32, "packet-type":3}
        # {"type":"send", "time":1552725032175, "conn":0, "state":2}
        # {"type":"packet-prepare", "time":1552725032175, "conn":0, "first-octet":64, "dcid":"4d6afaf1387e1671"}
        # {"type":"transport-close-send", "time":1552725032175, "conn":0, "error-code":256, "frame-type":0, "reason-phrase":""}
        # {"type":"packet-commit", "time":1552725032175, "conn":0, "pn":9, "len":32, "ack-only":1}
        # {"type":"quictrace-sent", "time":1552725032175, "conn":0, "pn":9, "len":32, "packet-type":3}
        # {"type":"receive", "time":1552725032175, "conn":0, "dcid":"923ed342da7896d983de46d59c12c3d80d", "scid":"dc96b22161fb8d", "len":39, "first-octet":193}
        # {"type":"send", "time":1552725032175, "conn":0, "state":3}
        # {"type":"send", "time":1552725032228, "conn":0, "state":3}
        # {"type":"send", "time":1552725032229, "conn":0, "state":3}
        # {"type":"free", "time":1552725032229, "conn":0}

The test expects a sequence of transport-close-send -> packet-commit -> quictrace-sent -> send -> free. But as can be seen, what is observed is excessive calls to quicly_send. That's what this PR is trying to fix.

Let's merge this considering the fact that it might fix an actual issue we have been observing.

Oh, interesting. Yes, that seems like a good candidate. The old code seems like it was correct behavior, even though it's not the most efficient. Thanks for fixing this.


Enable pipeline for bulk_helper

Crossed communications - was implemented in https://github.com/elastic/elasticsearch-perl/commit/331ed18628316a1cf8e1b3342ea1ccea440767d9


[Feature] Add a Dark Mode feature

Description
I want to add a dark mode feature here such that it produces less strain on eyes of people who are accessing website on night
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSoC'24 contributor.
[X] I want to work on this issue.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Hey, allow me to work on this under GSSOC' 2024


Create/Modify Constants Files

Is your feature request related to a problem? Please describe.
It would be amazing to allow users to be able to submit values for data which then get made into a .js file inside the constants folder.
Let's take an example, I want to have users add new heroes onto my wiki when they are released. Or even update current values on it. I have Netlify CMS working great for writing guides and posts but I was wondering if it would be possible to do it in a way it could be used to update constants. This would allow the wiki to be entirely maintained by the community.
Describe the solution you'd like

collections:
  - name: "hero"
    label: "Hero"
    folder: "src/constants/heroes"
    create: true
    editor:
      preview: true
    fileType: ".js"
    fields:
      - { label: "File Name", name: "id", widget: "string" }
      - { label: "Hero Name", name: "heroName", widget: "string" }

Instead of making a markdown file if we added fileType that could tell the CMS that we want this as a .js constant file. Which could then convert the data and create a file:
export default {
  heroName: "whatever they entered",
  // Add other fields here.
}

Describe alternatives you've considered
I tried to find a tool that could convert Markdown into Javascript constant files but then i asked myself if that was even a good idea. It would be a much bigger pain to try and convert Markdown to JS and then JS back to markdown when JS is updated. Netlify CMS does most of the heavy lifting for all of this already.
Additional context

N/A

Are you specifically looking to output to JavaScript, or are you looking for functionality similar to Forestry's Blocks? It isn't quite clear to me. This could be an XY Problem.

Can those files be JSON files? Because JSON outputs are already supported, you don't have to parse Markdown to JS but can easily parse JSON in JS: https://www.netlifycms.org/docs/configuration-options/#extension-and-format

@gungorbudak Thank you so much I was not aware it could be done with JSON.


Migrate CronJob from batch/v1beta1 to batch/v1

W1018 09:49:01.504879 1398543 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob
W1018 09:49:01.750729 1398543 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob

https://kubernetes.io/releases/_print/#release-history
We should clarify since batch/v1 is supported in k8s and OCP.

@rubenvp8510 yes
We need to upgrade the k8s Golang package to v0.21.0 or newer. Is that ok?

I think is fine, eventually we will upgrade some dependencies here: https://github.com/jaegertracing/jaeger-operator/pull/1561

I gave a try but it seems the task is more complex than expected. Some dependencies require k8s.io/api/batch/v2alpha1 but that is not longer available... One of those dependencies seems to be the operator-sdk so... that work seems to be part of #1561

I'm going to work on this


promptfoo eval failing in TS project, giving "TypeError: Cannot add property prompts, object is not extensible"

Describe the bug
When trying to run promptfoo eval on a simplified project following node-package-typescript, console errors out with:
$ npm test -- --verbose
2024-11-07 10:59:26-08:00

> test
> cross-env NODE_OPTIONS="--import tsx" promptfoo eval -c src/index.ts --verbose

Running migrations from C:\Users\mwiemer\llm-tests\node_modules\promptfoo\dist\drizzle...
Setting default prompt because there is no `prompts` field
Reading prompts from "file://prompts/prompt.txt"
Inserting prompt 846191a2cdb1449c2857d65d73bc96352b1ce6c19b29a63a5fab2cb54d59ac02
Inserting dataset c1d47eeb14b6f19b60468154233e9fcc982a096b20c445d9b231c6502f7c62f9
Running 1 concurrent evaluations with 4 threads...
Prompt: Write something about Hello world, vars: {"body":"Hello world"}
Eval #1 complete (1 of 1)
C:\Users\mwiemer\llm-tests\node_modules\promptfoo\dist\src\util\config\load.js:186
        ret.prompts = ['{{prompt}}'];
                    ^

TypeError: Cannot add property prompts, object is not extensible
    at readConfig (C:\Users\mwiemer\llm-tests\node_modules\promptfoo\src\util\config\load.ts:195:16)
    at async combineConfigs (C:\Users\mwiemer\llm-tests\node_modules\promptfoo\src\util\config\load.ts:223:22)
    at async resolveConfigs (C:\Users\mwiemer\llm-tests\node_modules\promptfoo\src\util\config\load.ts:420:18)
    at async runEvaluation (C:\Users\mwiemer\llm-tests\node_modules\promptfoo\src\commands\eval.ts:120:51)
    at async doEval (C:\Users\mwiemer\llm-tests\node_modules\promptfoo\src\commands\eval.ts:385:3)

Node.js v20.18.0

To Reproduce

Download and extract the attached zip: llm-tests.zip
Follow the readme (just setting up Node, npm, and running npm i)
Monitor console output after running npm test or npm test -- --verbose
See error

Expected behavior
Results are printed to console without error
System information (please complete the following information):

Promptfoo version: 0.95.0

Additional context
Still digging around the promptfoo source to find potential issues, will update as I learn

Maybe related to how types are constructed:
https://github.com/promptfoo/promptfoo/blob/main/src/types/index.ts#L1-L3
// Note: This file is in the process of being deconstructed into `types/` and `validators/`
// Right now Zod and pure types are mixed together!
import { z } from 'zod';

Many types are created via z.foo

Currently we are working around this with a custom script:
// package.json scripts

"test:workaround": "tsx src/index.ts",

We updated the index.ts to throw an error if any test fails to ensure we could move it into CI/CD pipelines

Looked into this and the problem is you are passing a typescript file as a config:
    "test": "cross-env NODE_OPTIONS=\"--import tsx\" promptfoo eval -c src/index.ts",

Instead of passing code as a config, you can run the code directly with tsx src/index.ts or equivalent and it works!
I've improved the error message in #2114

Perfect, we used tsx sec/index.ts as a workaround, wasn't sure if we were missing something without calling promptfoo! Closing :)


How to deal with this error? Thanks

I use 100 videos to check if I can run this project,but while training I got this error. I can't find what is wrong. Help me ,please.Thanks.

save opt details to ../data/save/opt_info.json
vocab size is  85
number of train videos:  100
number of val videos:  0
number of test videos:  0
load feats from ['../data/feats/resnet152']
max sequence length in data is 10
/usr/local/lib/python3.6/dist-packages/torch/nn/modules/rnn.py:51: UserWarning: dropout option adds dropout after all but last recurrent layer, so non-zero dropout expects num_layers greater than 1, but got dropout=0.5 and num_layers=1
"num_layers={}".format(dropout, num_layers))
/usr/local/lib/python3.6/dist-packages/torch/nn/_reduction.py:43: UserWarning: size_average and reduce args will be deprecated, please use reduction='none' instead.
warnings.warn(warning.format(ret))
/usr/local/lib/python3.6/dist-packages/torch/optim/lr_scheduler.py:100: UserWarning: Detected call of lr_scheduler.step() before optimizer.step(). In PyTorch 1.1.0 and later, you should call them in the opposite order: optimizer.step() before lr_scheduler.step().  Failure to do this will result in PyTorch skipping the first value of the learning rate schedule.See more details at https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate
"https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate", UserWarning)
Traceback (most recent call last):
File "train.py", line 133, in
main(opt)
File "train.py", line 120, in main
train(dataloader, model, crit, optimizer, exp_lr_scheduler, opt, rl_crit)
File "train.py", line 32, in train
for data in loader:
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/dataloader.py", line 346, in next
data = self._dataset_fetcher.fetch(index)  # may raise StopIteration
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/_utils/fetch.py", line 44, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/content/drive/My Drive/data/video-caption.pytorch/dataloader.py", line 63, in getitem
captions = self.captions['video%i'%(ix)]['final_captions']
KeyError: 'video57'

This error is due to "dataloader.py". You need to change the getitem function of the class VideoDataset.According to the "idx", get your video id
video_feat = np.load(os.path.join(self.feats_dir[0], your video id + ".npy")) captions = self.captions[your video id]['final_captions']


feat: rewrite the scanner in C

Closes #206
Closes #207
Pending #220
libFuzzer is happy as well

@tausbn Having a C++ scanner prevents Neovim from bundling this parser since we only require a pure C toolchain. This (plus a release) would unblock this, so Neovim users can have tree-sitter highlighting for Python out-of-the box (which we already have for C).

Thanks!


Issues with Prima

Is there an existing issue for this?

[X] I have searched the existing issues

Description of Issue
When I do "cd resources/[soz]/soz-core && yarn run prisma migrate deploy" I get these errors:
Invalid default value for 'end' in 'phone_calls'
Invalid default value for 'created_at' in 'add_player_creation_date'
After this everything else works (I put "DEFAULT CURRENT_TIMESTAMP(0)" directly on both to bypass the issue meanwhile)
Expected Behavior
It shouldn't do errors
Reproduction Steps
"cd resources/[soz]/soz-core && yarn run prisma migrate deploy"
Does it happen all the time ?
Yes

What is your mariadb version, it should work fine on latest versions (at least it work on our current version : mariadb 10.7.1)

My version is 10.4.25-MariaDB. I'll try the newest one

Works well in version 10.6.10 too.

Update on the issue:
https://stackoverflow.com/questions/36374335/error-in-mysql-when-setting-default-value-for-date-or-datetime
It's because we need to activate the Strict mode for it to accept 0000

Update on the issue:
I had NO_ZERO_IN_DATE,NO_ZERO_DATE, in the sql mode in "Variables" so it worked when deleting it. It's the default configuration of Xampp. All good thanks :)


IS_benchmarks

Traceback (most recent call last):
File ~.conda\lib\site-packages\spyder_kernels\py3compat.py:356 in compat_exec
exec(code, globals, locals)
File c:\users\user\edibles\examples\is_benchmarks.py:47
pars = singe_component.make_params(b_Cloud0=fit_result.params["b_Cloud%i" % (i)].value,
KeyError: 'b_Cloud1'

Description

Expected behavior

Actual behavior

Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

# Put your Python code snippet here.

System Details

I think that is a problem with the example code parameters. known_n_components is 5, but i only see two RV components

this example is also broken for Python 3.7. I don't see a point in fixing this


Proper way to paste a link

Environment data
PS version: 5.1.16299.251
PSReadline version: 1.2
os: 10.0.16299.15 (WinBuild.160101.0800)
PS file version: 10.0.16299.15 (WinBuild.160101.0800)

Steps to reproduce or exception report
Well this is not a bug but a question.
I have this binding in profile.ps1
Set-PSReadlineKeyHandler -Chord Ctrl+V -ScriptBlock {
    $clipboard = Get-Clipboard -Raw
    $clipboard = $clipboard -replace "&","``&"
    [Microsoft.PowerShell.PSConsoleReadLine]::Insert($clipboard)
 }

When I press Ctrl-V, it will paste the data from system clipboard and & character will be escaped.
It is convenient when the clipboard data is a web link like https://example.com?a=b&c=d .
However, if the clipboard data contains double quotes like this "https://example.com?a=b&c=d" , then there is no need to escape the & character.
How can I do a smart pasting. Thanks :)

You could use the PowerShell parser to tokenize the text so you know the extents to avoid replacing anything.

This is a workaround:
Set-PSReadlineKeyHandler -Chord Ctrl+V -ScriptBlock {
    $clipboard = Get-Clipboard -Raw
    if ($clipboard -match '^http') {
      $clipboard = $clipboard -replace "&","``&"
      $clipboard = $clipboard -replace "\(","``("
      $clipboard = $clipboard -replace "\)","``)"
      $clipboard = $clipboard -replace ",","``,"
    }
    [Microsoft.PowerShell.PSConsoleReadLine]::Insert($clipboard)
  }

Works for most cases.

Better solution:
Set-PSReadlineKeyHandler -Chord Ctrl+V -ScriptBlock {
    $clipboard = Get-Clipboard -Raw
    if ($clipboard -match '^\s*(http|ftp|magnet)' -or `
        (Test-Path $clipboard.Trim()) ) {
        $clipboard = $clipboard.Trim()
        $clipboard = "'${clipboard}'"
    }
    [Microsoft.PowerShell.PSConsoleReadLine]::Insert($clipboard)
  }


How can I show the chart in Fullscreen by default?

You cannot.
Please use the appropriate channel for support questions (support@seats.io), as this is not a seatsio-react-native issue.
Thank you.


⚠ Bofrost.es has degraded performance

In 1b18955, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1595 ms

Resolved: Bofrost.es performance has improved in 368e7d9 after 6 minutes.


Autoplay Muted Video on Android sample

R: @PaulKinlan @beaufortfrancois @ebidel @samdutton etc.
This takes the sample that Sam was hosting on simpl.info and moves it over to the official samples repo, which will be linked to from https://github.com/google/WebFundamentals/pull/3105

LGTM but nit.

LGTM apart from François's nit :).
Thanks for doing this!
On 1 August 2016 at 09:10, François Beaufort<EMAIL_ADDRESS>wrote:

LGTM but nit.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/samples/pull/395#issuecomment-236515899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMhqv1E-0pxQCY6gcbzCMgXD1pesjlIks5qbanvgaJpZM4JYjxU
.


REACT APP CONVERSION

Description
Converting this HTML, CSS, JS project to REACT JS. Making reusable components. Adjusting script.js, etc.
Wanna Work upon[y/n] ??
YES

Get the latest Remote repo or whatever the latest version you have.
We will try to resolve merge conflicts later.
Best of Luck.

Tomorrow morning


"Issue"

Hey,
first of all I just want to say that this is very nice component!
This is not an issue, it's more suggestion that you could add some @Output so we could use password strength for form validations in future version.
Thanks! 👍 :)

Take a look at roaringbits fork, he is doing exactly that


Investigate why Husky and Radix don't use the same rules for linting and code check

The problems on Radix came up during the next build part. I don't recall the specific error and can't find it in the log on Radix anymore.
It might be caused by the fact that we run the linting from the root of the repository, but Radix only builds & runs the web directory - it could be that Radix doesn't have access to some of the lint configuration in the root.

As Sven said, we don't run the next build task locally. Let's keep an eye on this problem to see if it happens again. It hasn't been a problem for the last couple of weeks, so I suggest we reopen it if this changes.
At least we are on the latest version of Husky now.


Undocumented dependency on SVM-rank

Some tests fail without this dependency. Simply installing SVM-rank binaries to /usr/local/bin solves the problem:
https://www.cs.cornell.edu/people/tj/svm_light/svm_rank.html

Thanks Andrew!
We addressed this issue a while ago, but forgot to document. Please see the new section on External Dependencies in the README.