Add a rotating slate of placeholder text for Concierge chat

Details

This makes it so that we have multiple options for the placeholder text in the chat with concierge. Each time you go to your Concierge chat, it will randomly pick from from one of the options and set that as the placeholder text. I moved the placeholder text to get set when the component mounts instead of during render since the component can re-render multiple times after sending a message, which leads to a weird experience where the placeholder text changes rapidly.
Fixed Issues

$ https://github.com/Expensify/Expensify/issues/209924
$ https://github.com/Expensify/App/issues/10923
Tests

Log into new dot
Go to your chat with Concierge. The input placeholder should be one of these messages
Send a message. The placeholder should stay the same after sending.
Go to a chat with someone else that you've chatted with before. The input placeholder should be Write something...
Create a chat with someone you've never chatted with before. The input placeholder should be Say hello!
Go back to your chat with Concierge. The input placeholder should be a different one of these messages
Go to a chat other than Concierge. In the console, do Onyx.merge('private_blockedFromConcierge', {count: 1, expiresAt: '2022-09-11'}); with the expiresAt being a future date. Go back to your concierge chat. The placeholder should be Communication is barred.
Change your language preferences to Spanish and verify that everything works as above.

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

PR Review Checklist

Contributor (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 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)

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

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[x] MacOS / Chrome
[ ] 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 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 was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] 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] Any functional components have the displayName property
[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 a new CSS style is added I verified that:

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

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The Contributor+ will copy/paste it into a new comment and complete it after the author checklist is completed

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

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

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

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

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

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

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

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

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

QA Steps

Log into new dot with a test account
Go to your chat with Concierge. The input placeholder should be one of these messages
Send a message. The placeholder should stay the same after sending.
Go to a chat with someone else that you've chatted with before. The input placeholder should be Write something...
Create a chat with someone you've never chatted with before. The input placeholder should be Say hello!
Go back to your chat with Concierge. The input placeholder should be a different one of these messages
Find the Concierge chat with your user using this tool: https://www.expensify.com/concierge/#/tools/ChatSearchByUser
Open the chat, go to the user info tab, and block the user
Go back to new dot and refresh. The placeholder with Concierge should be Communication is barred.
Change your language preferences to Spanish and verify that everything works as above.

[ ] Verify that no errors appear in the JS console

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Will review this today!

@Santhosh-Sellavel thanks for the thorough testing! I've updated the PR to move the placeholder calculation back to render. And instead am just picking a random Concierge message on mount and setting it in state directly.

@puneetlath
Conceirge message will change after switching to another chat and opening it back right?
In mobile from chatlist open Conceirge chat -> hit back -> open Conceirge again
should the placeholder message change or not?
Now it's the same.

If you switch to a different chat and come back, the message should change. If you just go back to the home screen and then back to the Concierge chat, it won't change since the component doesn't unmount. But I think that's fine.

@Santhosh-Sellavel bump on review. Thanks!

Sorry I was out yesterday!

@puneetlath
Author's checklist is unfilled are fine with this?

PR Reviewer Checklist
LGTM Tests well!
C+ Reviewed
🎀 👀 🎀

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

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

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[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 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 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 was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] Any functional components have the displayName property
[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 a new CSS style is added I verified that:

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

[x] If the PR modifies 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Author's checklist is unfilled are fine with this?

Yes, for internal issues as long as one of us has tested on all platforms then we're good.
@cristipaval mind giving it the final review?

@cristipaval bump!

Sorry @puneetlath ! I've been ooo last week. Reviewing it asap.

Removing Emergency label since this is a PR from an internal engineer and was reviewed by C+.

🚀 Deployed to staging by @puneetlath in version: 1.2.7-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @roryabraham in version: 1.2.7-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Peek problems doesn't wrap or provide a horizontal scrollbar

Issue Type: Bug

VS Code version: Code - Insiders 1.43.0-insider (07c33977da255861edf71e65b18249d2f67d0762, 2020-02-24T05:33:18.353Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
AMD Ryzen 9 3900X 12-Core Processor             (24 x 3800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.95GB (16.31GB free)

Process Argv
--folder-uri file:///c%3A/Users/Eric/code/microsoft/vscode

Screen Reader
no

VM
0%

I am seeing the scrollbar. Did you try hovering on the message?

I guess there is a scrollbar there, it is just super thin:

It was like this from beginning.
@jrieken any history?

Ah, I would have expected it to be similar to the hover scrollbars:

Yes - we are rendering errors in monospace and without extra wrapping because diagnostic messages sometimes come as "ascii art" and that we don't want to break. That's the reasoning here but since this comes up over and over again we could revisit this

Would love to see a wrap option as well, and also in the Problems panel -- sometimes it's just not showing me quite the detail I need. :)

It seems that for some reason the CSS style selector for the peek box parent sets style of overflow: hidden. This flag prevents the scrollbar from being shown. This is set at the peek box parent widget zone-widget
(https://github.com/microsoft/vscode/blob/17958017682a60f58d0b190dc7c5eb62e39f2b18/src/vs/editor/contrib/zoneWidget/zoneWidget.ts)
// Render the widget as zone (rendering) and widget (lifecycle)
		const viewZoneDomNode = document.createElement('div');
		viewZoneDomNode.style.overflow = 'hidden';
		const lineHeight = this.editor.getOption(EditorOption.lineHeight);

You can see the difference when I manually change overflow: hidden to overflow: unset

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

Haha yes! Happy coding! Teehee!
migrates away from vscode


Issue while running agora flutter sdk in web browser ('createIrisApiEngine')

Describe the bug
I am trying to build a video call feature for a web app using the Agora Flutter SDK. When I try to run it in a web browser, it shows 'TypeError: Cannot read properties of undefined (reading 'createIrisApiEngine').' All the UI elements are loaded properly, but the Agora engine does not work as I expect.
To Reproduce
Steps to reproduce the behavior:

create a flutter project
add the agora_rtc_engine: ^6.3.0
permission_handler: ^11.0.1 dependency in the project
create a code for run a simple video call using agora and add app Id and channel name to the code .
try to run it in web browser

Expected behavior
Expected that agora engine will work
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: windows
Browser : chrome
Version : 122.0.6261.95 (Official Build) (64-bit)

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
video call is an important feature of my web app. so please reply as soon as possible

Have you set up the project
https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK?tab=readme-ov-file#web-alpha


[Site][UI]:  i18n and style issues on /zh/blog/tags/* pages

Current State
Description of the current state/issue:
There are three problems with the current blog's Chinese tags/* pages:

One post tagged with "xxx", View All Tags not translated
The number of posts is always One post
The style of View All Tags is black and difficult to be recognized by the human eye as a link (this problem also exists on the same page of the English blog, but of course, they use the same components, so it can be fixed at the same time)

Link to the page:
Example: https://apisix.apache.org/zh/blog/tags/community/
Screenshots (if relevant):

Desired State
Description of the change you are proposing:

translate One post tagged with "xxx", View All Tags
fix "one post"
refactor View All Tags style

Would you like to fix this issue?
No response

I will fix it.

I have found that translate command is different with 'docusaurus write-translations' in Docusaurus docs.
"write-translations": "docusaurus-write-translations"
It's confused for me to understand how did translation work execute in the past.

@uniqie pls see /apisix-website/blog/zh/i18n/zh/code.json, just as a example


Autocomplete does not pass the "name" attribute to the input

Hey, great library,
Problem
just noticed that the autocomplete has lost the name attribute on the  since redux-form-material-ui v4.1.4.
Have not had time to investigate why but if you look at the library's live demo and inspect the autocomplete components they don't have the name attribute.
Temporary Fix
after npm installing v4.1.3 of redux-form-material-ui the name attribute in the Autocomplete input is there as expected.
Reason why important
The only reason I caught this and also need it is because I have selenium integration/feature tests that use the name of the input to fill in the fields automatically

Try updating to v4.2.0, that worked for me.

This is not passed because the AutoComplete component doesn't take a name prop.

While that is the case @erikras, it didn't ever take a prop called name but if that was a problem then why does an earlier version(4.1.3) of redux-form-material-ui where the underlying Autocomplete input have the name prop? Material-UI didn't have the name prop for the Autocomplete in earlier versions as far as I'm aware.
Redux-Form fields I think should always have a name attribute, I know it technically adds complexity to this library because it is extra functionality but at least it will stay consistent. Not only this but for people who have browser-driven tests, it makes it easy to fill in the fields created by this library.
An example about my point of consistency:

Checkbox adds a name attribute to its underlying  when the Material-UI Checkbox does not take a name prop either

This library was causing several warnings from MUI about props that were going to be deprecated soon, so I went through and culled all the props that were not specifically in the MUI docs.  It was just housekeeping to better align the APIs.
That said, name seems like a pretty innocuous one to pass for all inputs, so I think we should add it back.

I get the following warning with<EMAIL_ADDRESS>Warning: Material-UI: We don't have enough information
      to build a robust unique id for the TextField component. Please provide an id or a name.
warning @ browser.js:49
componentWillMount @ TextField.js:243
(anonymous) @ ReactCompositeComponent.js:348
..
..

This comes from an AutoComplete component. Related?

So, yeah, the AutoComplete component doesn't take a name prop - but apparently it transparently passes most props to the contained TextField, including the name.


Get error message '(or helm init --client-only if tiller is already installed)' while pushing chart

Hi there,
I was trying to push chart to my local harbor (v1.9.3) repo but get below error message:

You might need to run helm init (or helm init --client-only if tiller is already installed)
Error: plugin "push" exited with error.

I installed helm push plugin from https://github.com/chartmuseum/helm-push and add the local Harbor repo. Then try to push a chart for testing as:

helm push --username test --password Test12345? mysql-1.4.0.tgz myrepo

The error message is:
Error: Couldn't load repositories file (/root/.helm/repository/repositories.yaml).
You might need to run helm init (or helm init --client-only if tiller is already installed)
Error: plugin "push" exited with error

Since there is no --client-only and no tiller, this error message may need to be changed right?
Not sure why I got this error and have no idea how to init the repositories.yaml locally for a harbor chart repo.

Output of helm version:
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

Hi @wantdrink. Neat handle name. ;)
It looks as though this plugin currently supports Helm 2, and hasn't been updated to support Helm 3 at this time. @jdolitsky may have more context on this particular issue.
I'm going to go ahead and close this as a duplicate of https://github.com/chartmuseum/helm-push/issues/37. Please go ahead and follow up there. Thanks!

Thanks @bacongobbler  totally understand now.


backend/query: filter out empty filters

certain individuals send sloppy queries to the backend with an empty specific filter, before it defaulted to true now it defaults to false to avoid unexpected behavior

Nice. LGTM. A more robust backend is always better.


Add list of previous talks to readme

@abarciauskas-bgse @maxrjones let me know if there are any other talks you have given that you would like me to add here


How to modify corresponding config files to change the inference settings of Open-Sora 1.1

How to modify corresponding config files to change the inference settings of Open-Sora 1.1

No need to modify the config files. Just use command line args: https://github.com/hpcaitech/Open-Sora/blob/main/docs/commands.md#inference-with-open-sora-11


[Automation] Generate Fluent Lite from securityinsights#package-preview-2021-09

[Automation] Generate Fluent Lite from securityinsights#package-preview-2021-09

/azp run prepare-pipelines

/azp run java - securityinsights - ci


Primary Address Type cannot be changed to "None"

If the Mailing Address fields are cleared, then when a user changes the Primary Address Type to "-None-" from "Home" then the field switches back to Home, regardless of user input.
Steps to Recreate

Create a Contact
Add an Address into Mailing Address
Set the Primary Address Type to "Home"
Delete the values in the Mailing Address fields
Change the Primary Address Type field to -None-

Result
Primary Address Type changes back to Home, despite the manual update to -None-
The order of Field History changes that occur shows the change of the field, and then the creation and deletion of a new address after Primary Address Type is changed by the user:

Workaround
There does not appear to be a way to update that field value once it has been changed from -None-

**lurch: add

Tracking W-040327

Related Hub post - https://powerofus.force.com/s/question/0D51E00005FzMZmSAN/cant-reset-primary-address-type-to-none-after-removing-address

The behavior changed in NPSP 3.201 -- now the value is changing to "Mailing". Closing this item out and created new item (per engineering team): https://github.com/SalesforceFoundation/NPSP/issues/6522


Remove expected value check from the _getAttributesToReportWithReport…

…edValues

Report the attribute only when the value has changed from the read cache.

Fix logging for use cases where we didn't report since there was an expected value or the attribute value didn't change from the read cache value.

Fixes: #33013

Fast-tracking platfom-specific change with platform owner review.


AZURE_OPENAI_API_KEY seems not supported, only OPENAI_API_KEY in source

Hi John and team, thanks for creating the package and I see the advantages but since we're in unsupported countries we must use Azure Openai, I cannot get the LLM function  working due to following error, which seems source code only support OPENAI_API_KEY, or if there're other workaround kindly let me know :)  THANKS !
ERROR
OpenAIError                               Traceback (most recent call last)
Cell In[31], line 1
----> 1 res = strict_json(system_prompt = 'You are a classifier',
2                     user_prompt = 'It is a beautiful and sunny day',
3                     output_format = {'Sentiment': 'Type of Sentiment',
4                                     'Adjectives': 'List of adjectives',
5                                     'Words': 'Number of words'})
7 print(res)
....
  File ~\anaconda311\envs\python-31013\lib\site-packages\openai\_client.py:98, in OpenAI.__init__(self, api_key, organization, base_url, timeout, max_retries, default_headers, default_query, http_client, _strict_response_validation)
 96     api_key = os.environ.get("OPENAI_API_KEY")
 97 if api_key is None:

---> 98     raise OpenAIError(
99         "The api_key client option must be set either by passing api_key to the client or by setting the OPENAI_API_KEY environment variable"
100     )
101 self.api_key = api_key
103 if organization is None:
OpenAIError: The api_key client option must be set either by passing api_key to the client or by setting the OPENAI_API_KEY environment variable
LLM FUNCTOIN CALL
def custom_llm(system_prompt: str, user_prompt: str):
# ensure your LLM imports are all within this function
# from openai import OpenAI
from openai import AzureOpenAI  # Import AzureOpenAI for Azure-specific configurations
import os
import configparser
import re
import json
# Read the configuration file
config = configparser.ConfigParser()
config.read('config_upgrade_auseast.ini')

# Read values from the config file
azure_openai_key = config.get('openai', 'api_key')
azure_openai_endpoint = config.get('openai', 'endpoint')

os.environ["AZURE_OPENAI_API_KEY"] = azure_openai_key
os.environ["AZURE_OPENAI_ENDPOINT"] = azure_openai_endpoint

# Create the OpenAI client
client = AzureOpenAI(
  api_key = azure_openai_key,
  api_version = "2024-02-15-preview",
  azure_endpoint = azure_openai_endpoint
)

# Make a chat completion request
response = client.chat.completions.create(
    model="molly-dev-gpt",
    temperature = 0,
    messages=[
        {"role": "system", "content": system_prompt},
        {"role": "user", "content": user_prompt}
    ]
)
return response.choices[0].message.content

i got it working by adding this chunk of code in base.py  and making a custom_llm block,   works not pretty because azure does not have model parameter, only deployment name
elif host == 'azure':
    # Get the API key and endpoint from environment variables
    azure_openai_key = os.environ.get("AZURE_OPENAI_API_KEY")
    azure_openai_endpoint = os.environ.get("AZURE_OPENAI_ENDPOINT")

    if not azure_openai_key or not azure_openai_endpoint:
        raise ValueError("AZURE_OPENAI_API_KEY and AZURE_OPENAI_ENDPOINT environment variables must be set.")

    # Create the OpenAIClient instance
    client = AzureOpenAI(
        api_key=azure_openai_key,
        api_version="2024-02-15-preview",
        azure_endpoint=azure_openai_endpoint,
        deployment_name=model   # Replace with your deployment name
    )

Does adding your custom_llm of the form llm = custom_llm into strict_json() directly solve this OpenAI key issue?
Example code (Refer to Tutorial 0)
### Put in your Azure OpenAI keys here ###
AZURE_OPENAI_KEY = ""
AZURE_OPENAI_ENDPOINT = ""

def azureOpenAiChat(
    system_prompt: str, user_prompt: str, model: str = "GPT3_5Turbo", temperature: float = 0, **kwargs
) -> str:

    azure_open_ai_client = AzureOpenAI(
        api_key = AZURE_OPENAI_KEY,
        azure_endpoint = AZURE_OPENAI_ENDPOINT,
        api_version = "2024-02-15-preview"
    )
    response = azure_open_ai_client.chat.completions.create(
        model=model,
        messages=[{"role": "system", "content": system_prompt}, {"role": "user", "content": user_prompt}],
        temperature=temperature,
        **kwargs,
    )

    return response.choices[0].message.content

def azure_chatgpt(system_prompt: str, user_prompt: str) -> str:
    return azureOpenAiChat(system_prompt=system_prompt, user_prompt=user_prompt, model="GPT3_5Turbo", temperature=0)

Run the Custom LLM
res = strict_json(system_prompt = 'You are a classifier',
                    user_prompt = 'It is a beautiful and sunny day',
                    output_format = {'Sentiment': 'Type of Sentiment',
                                    'Adjectives': 'Array of adjectives',
                                    'Words': 'Number of words'},
                                     llm = azure_chatgpt) # set this to your own LLM
print(res)

Dear John,
Yes it does, I didn't watch tutorial#0, works  great !
cheers
GLY


flatpickr doesn't work on pages that define jQuery but not jQuery.fn

https://jsfiddle.net/tesmqdcb/
Your Environment

flatpickr version used: v4.6.0
Browser name and version: Chrome 74.0.3729.169 (Official Build) (64-bit)
OS and version: macOS 10.13.6

I am trying to use flatpickr on a page that defines an object named jQuery, but not jQuery.fn. I am getting an error saying Uncaught TypeError: Cannot set property 'flatpickr' of undefined.
I think the check in src/index.ts should be changed from if (typeof jQuery !== "undefined") to if (typeof jQuery !== "undefined" && typeof jQuery.fn !== "undefined").

Wow, that was a fast fix. Thank you. Do you have any estimate as to when this will be in an official release of flatpickr?

@elias6 already out in 4.6.1


Add missing defaultPartitionExpirationMs to template

Exists in schema, but was not applied to the resource properties.

Can someone review and merge this?


Update to polkadot-v0.9.43

astar polkadot v0.9.40 was not released. Proceeding with this PR for polkadot-v0.9.43

Uplift handle in https://github.com/inkdevhub/swanky-node/pull/77


Inline CSS Sparkpost option

Hi and thank you for your extension!
There is a new SparkPost feature called inline_css and it is already implemented in sparkpost/sparkpost Composer package as 'inlineCss'.
Could you add this too?

Hi, thanks for the added option!

Hello, how can i turn on this inlineCss option on yii2?
can you give me an example code please?

i Found the answer!
\Yii::$app->mailer->compose(['template' => 'my-template'], [])
<EMAIL_ADDRESS>->setTo($emails)
->setOptions(["inline_css"=> true])
->send();


Custom install location of jupyter kernel

Is your feature request related to a problem? Please describe
I use docker for my development and have an image that I like to add net kernels to.
Usually I mount a folder as the home folder of the user in order to get things like ssh keys and configs in the container while the image remains general. I imagine this is quite common.
While I can install dotnet where I like and dotnet interactive as well, it seems “dotnet interactive install jupyter” always picks the home folder.
Thus when I volume mount the .dotnet folder is overwritten and doesn’t show up.
Describe the solution you'd like
Cmd option to point to a path, e.g /opt/.dotnet
Describe alternatives you've considered
Various workarounds which are OK but are invasive to my colleagues that use the same image.

You might have to change the way jupyter looks up the folders for kernel specs. With the pr #337  you can specify where you want the kernel spec file installed, just make sure jupyter or jupyter lab can read from there


migrate to proposed new grammar

Don't merge until https://github.com/jakartaee/data/pull/658 is merged.

@starksm64 I've rebased on main and updated this PR to the merged version of the grammar.

Scott, you should merge this now.

Ok, I will when I have a chance. I'm traveling to Newcastle today, so
probably on the flight over the pond tonight.
On Sun, Apr 7, 2024, 7:15 AM Gavin King @.***> wrote:

Scott, you should merge this now.
—
Reply to this email directly, view it on GitHub
https://github.com/jakartaredhat/hibernate-data-tck/pull/10#issuecomment-2041433586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACRDMQEKOPH66JXT7ZMAMDY4ETELAVCNFSM6AAAAABFYYOMNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGQZTGNJYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


type ComponentProps should not union with false

Problems:
Consider example below:
export interface MatterSpriteProps {
  sprite: Phaser.Physics.Matter.Sprite
}

export class MatterSprite extends Component<MatterSpriteProps> {
  public sprite?: Phaser.Physics.Matter.Sprite

  constructor(props?: ComponentProps<MatterSpriteProps>) {
    super(props)
    if (typeof (props) === "boolean") {
      throw new Error("expected `props?` to be `MatterSpriteProps`, got `false`")
    }
    this.sprite = props?.sprite
  }

  public copy(source: this): this {
    this.sprite = source.sprite
    return this
  }
}

Inside MatterSprite constructure we needs to handle props in boolean case because ComponentProps<P> in https://github.com/MozillaReality/ecsy/blob/dev/src/Component.d.ts#L7 declared it as P | false. I didn't see any place construct component by passing a boolean false to the component (except undefined which come from ObjectPool).
Solution:
Change type ComponentProps<P> to be P (not P | false) if there's no place to send false  value.

We handle passing false to the constructor here https://github.com/MozillaReality/ecsy/blob/dev/src/Component.js#L3
Passing false disables the default constructor implementation introduced by schemas. So instead of making ComponentProps a union type, we'll need to do it in the constructor definition here: https://github.com/MozillaReality/ecsy/blob/dev/src/Component.js#L3

Thanks for your clarify.

No problem 👍


Flush should be off by default - consistant

Flushing should be off by default, just like it is when you are on the site normally.
It's not obvious that tests always flush when they run and you have to pass flush=0 to turn them off. People expect to have to flush to clear the cache, and the documentation already covers mentions about flushing.
Flushing all the time is slow. It adds 5-6 seconds for the tests even with sqlite. When your doing them a couple of times a minute it's pretty painful.
-> http://doc.silverstripe.org/en/developer_guides/testing/unit_testing/
phpunit framework/tests '' flush=all *
*Run tests with optional $_GET parameters (you need an empty second argument)

Looks like this was changed intentionally in #3393. If that’s how things are going to stay, the docs should be updated to reflect that (i.e. remove references to flush=1 when running tests).

I've found that I don't flush much at all, and feel it makes more sense to have the default as off.
It'd be like having dev mode as always flushing and having to turn that off by default.

How does have flushing off affect tests when they are run repeatedly especially after changes?

It depends on the change of course. If you edit something which needs a flush then you'd have to flush - just like in the browser normally. However code inside a function or html code (generally) doesn't need a flush.
Depends on your testing/development workflow - I would run a test, tweak some code, run the test, tweak some code etc. Some people might just run the tests once at the end of the day and always need to flush.
Regardless, I think it makes it consistent across the board - just like using the cli-script that to flush you pass it in - not have it on by default.

I do tend to agree, to be honest.
@halkyon I think we need you to weigh in on your original thinking here

@halkyon original rationale: "We also flush the cache in any case when TestRunner::use_test_manifest()
is called. I don't see any reason why you wouldn't want to flush the cache when running tests."
I think that's probably a bit overshooting the goal. Auto-flush on test execution basically prevents you from doing TDD, at least in the way flush is currently implemented in SilverStripe (*cough* PSR4).
So +1 from me on merging this, pending insight from @halkyon

@chillu @dhensby
Any update on this?

@halkyon Can we go with a merge on this?

Documentation in docs/en/howto/phpunit-configuration.md needs to be updated, since it's now incorrect. Flushing is off by default for tests so we need to declare that.

@tractorcow indeed. I just saw that. I'll open a PR to fix it.

Damn, since the docs have all been moved around I have no idea where that page is now. =(

Hrm. Yeah. Looks like flush=0 is non-existent in the new docs too.

Probably needs to be re-added to https://github.com/silverstripe/silverstripe-framework/blob/3.1/docs/en/02_Developer_Guides/06_Testing/00_Unit_Testing.md

Here ya go: https://github.com/silverstripe/silverstripe-framework/pull/4554

Somehow auto-flush got re-introduced at https://github.com/silverstripe/silverstripe-framework/pull/4404. Doh!


paste: add more tests

cleaner impl for multi-stdin support
added some tests from gnu coreutils

This change is

Any idea why we are regressing in term of code coverage ?
62.15% (-0.06%) compared to 374a4fd

Thanks!


Make zooming controls customizable

Current zooming controls are not customizable at all and also they are not supporting dark mode.

If you would like to upvote the priority of this issue, please comment below or react with :+1: so we can see what is popular when we triage.
@vladcioricagoogle Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

Once the pattern is established for the My Location button in #347 you can implement this for the zoom controls or other map controls as needed, @vladcioricagoogle.

@kikoso after merging the PR for the location button is it possible to take care of this because you already have enough context on the subject and it should be pretty similar? Thanks!

@kikoso LGTM, thank you very much!


Optional per-tag descriptive content

I'm not confident I have the Hugo terminology right for this, but I think it's the taxonomy term list page…  Anyway, the page that comes up when you click on a tag, and shows the list of posts that have that tag.
It would be cool if there was a place to drop a Markdown file containing a little descriptive blurb introducing the topic of that particular tag, which would be pulled in by the template and appear above the list on the generated page. Presumably it would want to be optional, so the page for any tag that doesn't have that Markdown file would just omit it and render without errors.
Obviously, I can figure out how to do this on my own site, but I'm guessing that would mean overriding the whole tag-listing page template from Index, and if you think it's worthwhile to add as a feature of the theme itself, then I don't have to!

Good Idea, checkout here https://adityatelange.github.io/hugo-index/html/


Triggering a ref passed as a prop does not cause an update in the nested component

Vue version
3.2.45
Link to minimal reproduction
https://sfc.vuejs.org/#eNqlU01v2zAM/SuED7WDOlI/tku+0GLYYbdhWE91gaoxE7uxJUGiYxSB//uoOB9uV+yyiyHxke9RfPQuurdWbBuMJtHML11pCTxSYxeZLmtrHMEOfKGqyrS/cJUCuXK9Rrc/t4qWxffVCpeUgtEPujaNJsyhg5UzNcTMG594vim9Vf6ACNlfg3ScUaYzvTTaE+SKFMwHkonGFh5KTbc3986pt+R6NJpmGuBYwRC6rapCFdKPwy1JRjBfwI6Zqc9TznFK4BeMNxg4OPZ49XR5Gc4hy1QoKrNOhBAMjUL4/OAk1HKsS+H66ooPgycf5JYVKndq4djZiHMzLSX8LkoPrtEe2gI1PJ+5n4GRUm/NBvMUXhoCKnDf7L7QOmPBKu95uGSOo8wNeh0Hw7AO4da4zb7OqxrZnTeR6YFHxx4H7zxPI/Q4k/0GsPd8IaxtpQj5BjCzi4uKprwsF2uawt6JwESoyU9gt+tDIrjbz0m8mlIncQrxCLpuJsNGMc+h9UnImcfhG4NkaCZPelEa9SszrpUVr95oXk42ki0/AD6LWDNEQoxXKNyzqCCyfiJlo+1mLZamlneMSR44lTWOc1Pf3Yob8eWrzEtPw7hAX49fnGk9OlbMonRALjm4RTd2qHN06P4p9iH3neAH7C/RoNnxfvEAzn/HJz9mjqtS40/eCZ889jN8em/fp+b1nP/j39Ck7g+CjnZe
Steps to reproduce
Observe the output – the two lines should be identical, but they are not.
What is expected?
data is a shallowRef holding an array.
There is a setInterval that updates an array element, then triggers the data shallowRef.
The two lines of output should be the same – the first is the direct output of the App template and the second is the output of a nested Canvas component.
What is actually happening?
For some reason, despite the triggerRef calls, the reactivity does not propagate to the Canvas component instance.

System Info
No response
Any additional comments?
Curiously, if I pass the prop as :data='[data]'  instead of :data='data', then the two stay in sync.
I think this means that triggerRef causes the data prop to re-evaluate, and since each evaluation returns a new array object ([data]) this causes the Canvas component to be re-rendered.
But I think that data changing should be enough to cause the Canvas component to re-render, and it is puzzling why it doesn't.

as a workaround
<Canvas :data='[...data]' />

Hi @edison1105, thanks for the quick response! Your workaround is a good one for the specific example I gave in the issue, but has performance implications that  prevent it from being a workaround in my actual use case, where the data is a large Uint8Array representing the ImageData of a canvas.
An alternative workaround would be to wrap the data array in a new plain object each time, but so wonder if there’s a workaround that doesn’t require an allocation.

@yurivish
Another workaround without shallow copy the array.

I've seen variations on this theme a few times on Vue Land. I added a note about it a few weeks ago in the docs repo, https://github.com/vuejs/docs/issues/849#issuecomment-1382072571, as it's something we might want to consider documenting.
While I can understand why people find it counterintuitive, I don't think there's a bug here. triggerRef() is successfully triggering dependants of the ref's value property. The parent is being forced to re-render as it has a direct dependency on the ref, but there's no reason for the child to re-render.
It's effectively like calling $forceUpdate().
triggerRef() isn't 'deep' on any non-reactive objects it contains. I'm not sure whether such a thing would even be possible, as we've no way of knowing exactly where non-reactive objects are used.
Maybe there is some magical way to make this work, but I suspect it'd need a new API to do it, to avoid breaking changes to the existing APIs. Ultimately we might just need to document this better.

But I think that data changing should be enough to cause the Canvas component to re-render, and it is puzzling why it doesn't.

The parent is re-rendering, which updates the props on the child. But the props on the child are considered equal from a === perspective, so the child won't re-render.

I agree with @skirtles-code
When working with nonreactive data, it's better to then work with immutable data as @edison1105 suggested.

Thank you for the great explanation, @skirtles-code. The issue you linked containing explanations of problems with reactivity is also very useful.
I think my mistake here was actually in not understanding how props are passed – I knew that that triggering a ref without changing its value would cause re-evaluation only "one level" down – ie. any direct dependents would be re-evaluated, with the usual rules being followed beyond that – but thought that I could pass the ref down into the child component directly, where those changes could be directly observed by the child.
Here's an example I made in the SFC playground that clarified things for me. It explores the various options for passing a ref prop.
It looks like what's happening is that Vue will unwrap any ref values passed as props inside the render function of the parent component.

Using x.value if x is a ref
Using unref(x) if the type of x is not known to the compiler to be a ref

So the only way of giving the child component access to the ref from the parent is to use a function that returns it, and to define that function outside the template so that the unref transformation does not get applied.
By the way, thanks for your work on the Vue docs – they're really good and a big part of why I got interested in exploring Vue in the first place!

@yurivish The Playground you linked is slightly misleading. Both the parent and child templates will unwrap refs, so it isn't immediately clear in each example whether the unwrapping is occurring in the parent or the child.
The process of passing a prop doesn't directly unwrap anything.
Top-level refs are unwrapped automatically whenever they are used in the template. So if a ref is wrapped in a plain object it will not be unwrapped, Playground example.
{{ }} interpolation will also unwrap a ref if it is the final value of the expression. This can give the impression that nested refs are automatically unwrapped, but in general they aren't.
See also https://vuejs.org/guide/essentials/reactivity-fundamentals.html#ref-unwrapping-in-templates.

Thank you for the corrections and clarifications (and the example)! Learning a lot today. :)

@yurivish The Playground you linked is slightly misleading. Both the parent and child templates will unwrap refs, so it isn't immediately clear in each example whether the unwrapping is occurring in the parent or the child.

I was using the output of the handy JS inspector in the playground to see where the unwrapping was happening:
return (_ctx, _cache) => {
  return (_openBlock(), _createBlock(Canvas, {
    data: data.value,
    getData: getData,
    inlineGetData: () => data.value,
    wrappedData: wrappedData,
    inlineWrappedData: { data: data.value },
    renamedData: _unref(renamedData)
  }, null, 8 /* PROPS */, ["data", "inlineGetData", "inlineWrappedData", "renamedData"]))
}
}


 sprouts unexpected inline position: relative style

** PLEASE READ THIS BEFORE FILING AN ISSUE **
I'm submitting a:

[x] bug report
[ ] feature request

What OS are you using?
Mac OS
What browser(s) is this bug affecting:
Chrome
Current behavior:
<mwc-switch> sprouts an unexpected style="position: relative" attribute.
Expected behavior:
<mwc-switch> does not sprout unexpected attributes, particularly inline styles.
Steps to reproduce:

Put an <mwc-switch> on a page
Open it in your browser
Inspect the element and note the style attribute

Related code:
<mwc-switch></mwc-switch>

Other information:
This was discovered when creating this demo: http://lopsided-motion.glitch.me/090-mwc.html

This is probably due to how the ripple is applied.

Fixed in M3


Public API: Support URL handling

Promote the ProtocolHandler API to public API.
https://github.com/Microsoft/vscode/blob/00b0acb9fd237042e15e27c4264f68d1bbf90884/src/vs/vscode.proposed.d.ts#L708:L722

This is now called registerUriHandler.


Support TLS

Hi!  Amazing how useful such a tiny service can be...
Suggestion: It would be even more useful if it could support https :)
Thanks!

Done: https://www.aaron-powell.com/posts/2017-09-01-httpstatus-now-https/
We're not forcing HTTPS at this point though.


Add an option to select the ABCI port

The endpoint for query the node progress is mandatory as defined in the constant.
https://github.com/KYVENetwork/supervysor/blob/a84e13b2395b9e51aa6908c026ea998190eb4db3/types/constants.go#L4
it could be nice to be able to have a parameter to customise it.

Added in update: support custom ABCI Endpoint.


Create ur.json

added Urdu translation

Thanks!

https://github.com/AlexxIT/WebRTC/releases/tag/v3.6.0

Thanks @AlexxIT


Guidance creating new conversation vs new private channel

Would be good to see some guidance when shall the users create a new conversation (inviting many people) vs new private channel

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

ID: ce34b12b-aa50-608b-bbfa-a1fb4bb79f8d
Version Independent ID: 9ddeb6f4-f30a-1e72-fc94-ae66def91f40
Content: Private channels in Microsoft Teams
Content Source: Teams/private-channels.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@jeffangama  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @jeffangama, thank you for your feedback.
There is some information around the web. Do you still think that this is valuable information to add to the article?

@jeffangama We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Lock accessory status issue

After instaling latest 1.7.1 I get the following error:
Error: Trouble getting HomeKit accessory information for 100302700-2201
at ADCPlatform.statLockState (/usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:976:13)
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:340:20
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:335:26
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:295:22
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
All other accessories are working fine.  the garage door issue seems to be resolved and this is a great fix other than this one issue.  I have a Kwikset lock and it works fine on Alarm.com app and site.

i exercised the lock through homekit and it unocked.  I then locked it via homekit and then got the error
[2/8/2021, 8:34:32 AM] [Security System] TypeError: Cannot read property 'updateCharacteristic' of undefined
at ADCPlatform.statLightState (/usr/lib/node_modules/homebridge-node-alarm-dot-com/dist/index.js:625:17)
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:328:20
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:323:27
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:295:22
at processTicksAndRejections (internal/process/task_queues.js:93:5)
At the next read the initial error comes back again.

I believe this to be an issue with how I've setup the plugin to pull its dependencies. I'm sorry, and I'll make changed to avoid this in the future.
In the meantime, completely removing the plugin and then reinstalling it is likely your best bet. If you tell me whether you're using the Homebridge UI or the CLI I can give you instructions.

I believe this to be an issue with how I've setup the plugin to pull its dependencies. I'm sorry, and I'll make changed to avoid this in the future.
In the meantime, completely removing the plugin and then reinstalling it is likely your best bet. If you tell me whether you're using the Homebridge UI or the CLI I can give you instructions.

I am using the Homebridge UI on a RPi.  Thanks.

Go to plugins, click the wrench on the card for homebridge-node-alarm-dot-com, click uninstall. Don't remove your config or you'll need to set it all up again! Here's a screenshot from mine:

After that you can reinstall the plugin and the right dependency should be pulled in.

I uninstalled and reinstalled as above.  Now getting the following:
[2/12/2021, 7:40:44 PM] [Security System] Updating light Lock (ID:2) (100302700-1200), state=-1, prev=1
[2/12/2021, 7:40:44 PM] [Security System] TypeError: Cannot read property 'updateCharacteristic' of undefined
at ADCPlatform.statLightState (/usr/lib/node_modules/homebridge-node-alarm-dot-com/dist/index.js:625:17)
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:328:20
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:323:27
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:295:22
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
[2/12/2021, 7:41:44 PM] [Security System] Error: Trouble getting HomeKit accessory information for 100302700-2201
at ADCPlatform.statLockState (/usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:976:13)
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:340:20
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:335:26
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:295:22
at processTicksAndRejections (internal/process/task_queues.js:93:5)

It’s strange, still getting this error.
[Security System] Error: Trouble getting HomeKit accessory information for 100302700-2201
at ADCPlatform.statLockState (/usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:976:13)
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:340:20
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:335:26
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:295:22
at processTicksAndRejections (internal/process/task_queues.js:93:5)
but the lock works and I can unlock it and lock it in HomeKit but after a few minutes the error shows up again.

Go to plugins, click the wrench on the card for homebridge-node-alarm-dot-com, click uninstall. Don't remove your config or you'll need to set it all up again! Here's a screenshot from mine:

After that you can reinstall the plugin and the right dependency should be pulled in.

after reset and update to 1.7.1 I get the following
[Security System] Error: Trouble getting HomeKit accessory information for 100302700-2201
at ADCPlatform.statLockState (/usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:976:13)
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:340:20
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:335:26
at Array.forEach ()
at /usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:295:22
at processTicksAndRejections (internal/process/task_queues.js:93:5)
and then a few minutes later
[3/12/2021, 2:00:56 PM] [homebridge-node-alarm-dot-com] Error:
at LockCurrentState.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2164:105)
at LockCurrentState.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2114:14)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1517:24
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at LockCurrentState. (/usr/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:952:9)
at LockCurrentState.emit (events.js:315:20)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1493:14
at new Promise ()
at LockCurrentState. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1491:12)
at step (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)

I ran into a similar issue with my ZWave lock. I added a ZWave light switch plug module in between my panel and the lock to act as a repeater boosting the ZWave signal. This helped increase the reliability.

First off, thank you for your hard work on this module!  I am experiencing a challenge and I wanted to give you some backstory on it.  It is in regards to the ZWave lock that is tied to my alarm system.   For about a day it was working flawlessly.  The next day I was on the accessories page on my homebridge running on my RPi4 and I clicked on the icon there a few times.  After this, now when I click to lock or unlock the front door,  on my homekit on iphone it shows unlocking... or locking... but no lock status change occurs.   I am showing this error log in my homekit.  Any advice you have would be extremely appreciated and thank you again!                                                                                Error: GET https://www.alarm.com/web/api/devices/locks/?ids[]=99950106-1202 failed: request to https://www.alarm.com/web/api/devices/locks/?ids[]=99950106-1202 failed, reason: read ECONNRESET
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:466:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 3)
at async Promise.all (index 0)

I've never been able to get the lock functionality working in HK. It shows up, but gets stuck on "updating". I'm running the latest beta version of the plugin as I was effected by the 2FA from my ISP/ Alarm.com. The logs shows the following. Any suggestions:
[telus security] (un)secureLock)(96741200-1202, 0)
[29/06/2021, 08:51:09] [telus security] Updating lock front lock (96741200-1202), state=0, prev=1
[29/06/2021, 08:51:18] [telus security] (un)secureLock)(96741200-1202, 0)
[29/06/2021, 08:51:24] [telus security] /var/lib/homebridge/ADC-SystemStates.json written

Looks like there are a couple of issues being conflated in this thread. Are you guys still seeing this issue with the more up-to-date version?


[feature request] Support annotated_types.Predicate

I'd like to request that pydantic V2 & pydantic-core add support for annotated_types.Predicate. Though the functionality can be achieved with the @validator decorator, the motivation for including it is the same as supporting the length, and value-comparison annotations -- it lets the developer see the validations that they need to know about for a field without going through the whole model class' implementation.
i.e. A model like the following should be possible:
import sys
from pydantic import BaseModel
from annotated_types import Predicate

if sys.version_info < (3,9):
    from typing_extensions import Annotated
else:
    from typing import Annotated

def lookup_dynamic_length_constraint():
    return 20

func = lambda s: len(s) < lookup_dynamic_length_constraint()

class ErrorModel(BaseModel):
    attr: Annotated[str, Predicate(func)]

It currently raises an error:
# pydantic-2.0.0.dev0 - hash: ef3cc495a9c86553b62a95a6052fd9b6ebc045e9

pydantic_core._pydantic_core.SchemaError: Invalid Schema:
typed-dict -> fields -> attr -> schema -> str -> func
  Extra inputs are not permitted [type=extra_forbidden, input_value=<function <lambda> at 0x7fda9156aee0>, input_type=function]

Ideally, it would support multiple Predicates in an annotation:
class ErrorModel(BaseModel):
    attr: Annotated[str, Predicate(lambda x: ...), Predicate(lambda x: ...), ... etc]

It looks like this support would need to be added in pydantic-core, hence the ticket in this tracker rather than the main pydantic one.
A pydantic-core reproducer for the exception above follows:
from pydantic_core import SchemaValidator

func = lambda s: True
inner_schema = {'type': 'typed-dict', 'fields': {'attr': {'schema': {'type': 'str', 'func': func}, 'required': True}}, 'return_fields_set': True, 'ref': '__main__.ErrorModel'}
core_config = {'title': 'ErrorModel', 'typed_dict_extra_behavior': 'ignore', 'allow_inf_nan': True, 'populate_by_name': False, 'str_strip_whitespace': False, 'str_to_lower': False, 'str_to_upper': False, 'strict': False, 'ser_json_timedelta': 'iso8601', 'ser_json_bytes': 'utf8'}

SchemaValidator(inner_schema, core_config)

# pydantic-core-0.8.2

# Traceback (most recent call last):
#   File "testannotation.py", line 36, in <module>
#     SchemaValidator(inner_schema, core_config)
# pydantic_core._pydantic_core.SchemaError: Invalid Schema:
# typed-dict -> fields -> attr -> schema -> str -> func
#   Extra inputs are not permitted [type=extra_forbidden, input_value=<function <lambda> at 0x7fda9156aee0>, input_type=function]

Fine by me.
The question is around the other kwargs to validate and how we support them. I guess easiest to support using the validate function as an annotation.

Fine by me.
The question is around the other kwargs to validate and how we support them. I guess easiest to support using the validate function as an annotation.

I don't think that the Predicate case would take the other 'validate' kwargs. The definition of Predicate has the function defined as Callable[[Any],bool]. So, it would only be simple validation logic; those that wanted the full validation context and such would still need to use a @validator decorator on a separate method.

I get that, what I'm suggesting is supporting Annotated[str, validate(mode='wrap')(my_function)] just in case people what to use it that way.


Formatting is not correct in the letter

Able to see some blank lines in the bullet list.

saw it once...not able to reproduce again ..will keep an eye on that


Is there a way to use Mediapipe python on the web?

I have been trying to use Mediapipe python on the web. Is there a way to do it?

I have the same interest,  I want to avoid javascript and keep as much as possible in python.  I've looked at some python http server packages but haven't decided on one.
Streamlit looks like a nice low-code option for outputting reults.  https://streamlit.io/

Hi @Prana-S,
Currently we do not have such application build and tested using the Python. However, we can see this has already been implemented here and example codebase with Django that might be helpful for use-case mentioned. Thank you!

When I follow those steps, my application still opens in a new window. Heres is what I see:

Hi @Prana-S,
We do not have the official web application build/ tested using the Python. Reference shared here is by the GitHub community member implemented the application with mediapipe. It will be good practice if you can follow and raise same issue in member repo.


[SR-15058] Compute document semantic tokens on demand

Previous ID
SR-15058

Radar
rdar://81836061

Original Reporter
@ahoppen

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s
SourceKit-LSP

Labels
Bug

Assignee
None

Priority
Medium

md5: b10f4fa893a89b7f7933142ba5f922ce

Issue Description:
Once https://github.com/apple/sourcekit-lsp/pull/414 is merged we will have semantic tokens support in SourceKit-LSP.
It does, however, have two areas for improvement:

When SourceKit-LSP receives new semantic tokens from sourcekitd, it sends a WorkspaceSemanticTokensRefreshRequest, which causes the editor to update semantic tokens for all files and not just the current one. The request is intended for global changes like build config changes. We need to do this because before we receive semantic tokens, we serve the semantic tokens request by lexical tokens.
We currently eagerly parse all syntactic and semantic tokens into {{SyntaxHighlightingToken}}s, even if the client never requests semantic tokens

I think we could improve this by trying to only store the minimum amount of information to lazily construct {{SyntaxHighlightingToken}}s at first (e.g. just store the XPC responses or tokens in UTF-8 offset instead of converting them to UTF-16 up-front).
Once the client sends a DocumentSemanticTokensRequest, we will wait until the semantic tokens for the requested document have been computed and then compute the {{SyntaxHighlightingToken}}s.
This way we (a) reduce the amount of work that is done speculatively and (b) since we wait with the response to the DocumentSemanticTokensRequest until we actually have semantic tokens, we don’t need to send the WorkspaceSemanticTokensRefreshRequest anymore.

Fixed by https://github.com/apple/sourcekit-lsp/pull/912


Add search function to deposit asset selector

Acceptance criteria

[ ] Should be able to type the name of the asset I want and the list should filter down live
[ ] Also observed scrolll failing ... but the above hopefully will address this .... check scroll works when testing

Additional details / background info

This will become redundant with planned asset work


Field names are preceded by comma when preceded by a struct field

Currently running EMR 5.13 with Hue 4.1.0. When I create a table with the following structure:
CREATE TABLE test (
    f1 struct<f1:struct<f1:string>,f2:string>
)

The field f2 is shown with a leading comma:

This only happens within a struct.

Sounds like https://issues.cloudera.org/browse/HUE-7563, fixed in 4.2


Improve error message for missing runtime errors

@charlierudolph @allewun
I never liked the obscure error message undefined method 'errors' for nil when there were runtime errors expected and they didn't happen. This fixes it.

:santa:

All comments addressed

:ship:


Resolved: GO Portal is back up in 33c4fd2.


TimeSeriesScalerMeanVariance returns extra dimension then documentation

Describe the bug
TimeSeriesScalerMeanVariance returns 3 dimensions, when the data matrix (N x T) is 2 dimensions.
To Reproduce
X = np.random.random((87,120))
print(X.shape)
X = TimeSeriesScalerMeanVariance().fit_transform(X)
print(X.shape)

Expected behavior
It should be squeezed, or at least better documentation.
Additional context
Happy to submit a PR for this, but want to know if the problem is in documentation, versus just better squeeze output after fit_transform?

Hi @adam2392 and thanks for this report. This is in fact an expected behaviour since a dataset is supposed to be 3d on tslearn.
But you are perfectly right that the docs should make that clearer. I will fix this asap.
Best regards
Romain


Missing intersphinx links to other packages in how-to tutorials

In the "First descriptor computation" section, we have intersphinx links to other packages documentation, but these links are missing in the "Property Selection" example. I'm not sure why, but this should be fixed!

I have the impression it does not work in any of the how-to. Was this always the case or did we broke this?

I'm not sure, it might never have worked

Might the latter. I will take a look, so far our config looks consistent.


URL Authentication

Hi,
I would like to learn how to get credentials with Redirect URL authentication. Is there any full sample or guide to use it ? I have not mastered MVC yet, So I use basic knowledge to develop WPF apps.
Thanks

Please read the documentation for redirect url here.
Also you can find a real MVC example if you download the source code from github. There is a project Examplinvi.Web. '
And finally you can find a the example HomeController.

Can I close this?

Hi,
Sorry for my late reply, thanks for your help. I'm working on it.


Add pages to the keybinds menu for each mod's keybinds

Aside from what is mentioned in the title, there are a few additional miscellaneous tweaks in this pull:

hideKeybinds mod config to optionally hide all your mod's keybinds from the Main Menu (for mod authors who want to make thier own in-mod rebind system)
New keybind mod_rebind - Used to open the Mod Controls menu (see below)
Mod Controls menu - for mods that define keybinds, the mod_rebind key (default / on keyboard) can be pressed on the ModList screen to open up their specific keybind page (Will auto-switch between gamepad/keyboard if you change inputs!)
Input.mod_keybinds table - okay this isn't a real feature but if for some reason you needed to know what keybinds a mod uses this table has a list of them (only includes the keybind name and not the bound keys)
Input.resetBinds(gamepad, mod_id) - similar to above this is mainly for the controls menu but if you wanted to reset a specific mod's keybinds you can now do it with resetBinds here - or use "KRISTAL" as the mod_id to reset all of the kristal keybinds

An extra important clarification too: this does NOT change anything about how keybinds are stored, they continue to be shared between mods that define the same bind and will appear in all of those mods keybinds with the same bound key and update accordingly as it is changed

LGTM, thanks!


python311Packages.rich-argparse: 1.4.0 -> 1.5.1

Description of changes
https://github.com/hamdanal/rich-argparse/releases/tag/v1.5.1
https://github.com/hamdanal/rich-argparse/releases/tag/v1.5.0
Current version has a failed test when building with nix build nixpkgs#python311Packages.rich-argparse.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 317940 run on x86_64-linux 1

4 packages built:

python311Packages.rich-argparse
python311Packages.rich-argparse.dist
python312Packages.rich-argparse
python312Packages.rich-argparse.dist

Result of nixpkgs-review pr 317940 run on x86_64-linux 1

4 packages built:

python311Packages.rich-argparse
python311Packages.rich-argparse.dist
python312Packages.rich-argparse
python312Packages.rich-argparse.dist


Brenda (the business analyst) wants a way to automatically test, release, and promote business rule changes through the different environments (dev, test, staging, prod, etc)

Key features:

[ ] versioned releases of rule sets
[ ] validation of rules (unit tests and integration/regression tests) in the environment
[ ] ability to roll back a rule to a previous version if there is an issue

More detailed discussion in this card - https://github.ibm.com/gsi-labs/industry-cloud-planning/issues/601


Upper case "VM" for Add VM conditions selection

Substituted proper conversion to upper case "VM" when adding VM conditions
https://bugzilla.redhat.com/show_bug.cgi?id=1110656

@dclarizio @h-kataria Ready for review. Created new PR since older one was insisting on pulling all interim check ins. Old one closed.

looks good.


Fix multi-thread hang for cv2

cv2 sometimes hangs when used in sub-processes.
For example chainercv.links.model.ssd.resize_with_random_interpolation() does not work with chainer.iterators.MultiprocessIterator.
So I set single-thread using cv2.setNumThreads(0).

I found the documentation is added now in the documentation for chainer.
https://github.com/chainer/chainer/pull/4589
But I would still like to clarify the workaround from the point of practical use.

I mean the code is in chainercv library not in user-side and I think it is not easy to be modified even if there is documentation.

How about Add cv2.setNumThreads(0) right after import cv2 in your training script
https://docs.chainer.org/en/stable/tips.html#my-training-process-gets-stuck-when-using-multiprocessiterator
Also, this problem has been fixed in #572 .
Related: https://github.com/chainer/chainer/pull/4607