esm release tree shake is not pure

Reproduce
echo 'export {} from "./dist/js-yaml.mjs"' | rollup

Expected
output only LF
Actual
output 1023 lines

I'm not familiar with details. Could you explain where to read and why functions should be marked manually (that looks strange)?

Google does not shows too much. This is interesting to read: https://github.com/d3/d3/issues/3076#issuecomment-644265124
Also:

How standard is all that for libraries?
Shouldn't we use sideEffects option?
All mentioned marks are /*#__PURE__*/, not /*@__PURE__*/. Where to read about difference?

(rollup pure)[https://rollupjs.org/guide/en/]
(esbuild pure)[https://esbuild.github.io/api/#pure]
both 2 seems equal.
I choose the one has more google result.

Set sideEffects should work too. Haven't tested.
Scenario
foo depends on a bundlized library bar.
bar depends on js-yaml.
Plan A
Pro: easist
Con: pure may lost, may pollute final output.
Set sideEffects within js-yaml.
bar got pure js-yaml.
But after bundlized, toplevel function call has no magic comments.
As bar itself might be un-pure, foo might un-pure library bar.
Plan B
Pro: always pure, will never pollute final output.
Con: not easiest.
All js-yaml top level function call use magic comment.
bar got pure js-yaml.
Bundled bar still have magic comment, so it is pure too.
foo got pure bar.

@loynoir Sorry for delay with answer. I have no principal objections against marking required methods with comments, as you suggested.
Two more questions prior to move forward (sorry, if stupid, i'm not familiar with topic):

Why some functions of js-yaml stays unremoved? May be we could rewrite those (do some known recipes exist)?
How do you find, which functions  should be marked?

@puzrin
I'm no expert. Someday I look some source code, found some magic comments, and did some search. (sorry, forget which project)
I have some thinks, but not sure if they are right.

Why some functions of js-yaml stays unremoved?
I think ESM is stateless to make tree-shaking happens , so any might be un-stateless code are kept outside that tree. Eg, toplevel function call.

https://github.com/nodeca/js-yaml/blob/01d91e5a5e82a6533ec4419260ec035b08ac4888/dist/js-yaml.js#L410

May be we could rewrite those (do some known recipes exist)?
Maybe convert stateful function calls to stateless init functions,
and call them in a big initial function to only keep one __PURE__?

Or just keep multiple __PURE__?
I don't know if there is best practice.
But I'm sure I saw it in some source code, but not generated code, that's how I know this magic comment.

How do you find, which functions should be marked?

echo 'export {} from "./dist/js-yaml.mjs"' | rollup

Besides, I add a test.
https://github.com/nodeca/js-yaml/blob/01d91e5a5e82a6533ec4419260ec035b08ac4888/test/issues/0631.js#L23
Just see the command line output. Those stateful blocks are kept in output.
Besides, remember the location of those stateful thins, and check the output.
To make sure, certain stateful things are not shaked away.

How do you find, which functions should be marked?
For short, I think

top-level code,
ast parser thinks this kind of code can change state.


Represent BackgroundImageAlignment as ConvergedAlignment

backgroundImageAlignment is exposed as 1 setting in the JSON, but
stored as two separate settings (HorizontalAlignment and
VerticalAlignment). This PR introduces ConvergedAlignment as a flag
enum that can be a combination of horizontal and vertical Alignments.
TSM now solely uses this ConvergedAlignment, and TerminalSettings
performs a conversion from this new enum to the traditional
HorizontalAlignment and VerticalAlignment for consumption.
Validation Steps Performed
Manually tested changing the backgroundImageAlignment in my
settings.json and checking if the image updated appropriately.

@msftbot merge this in 2 minutes


Allow overriding Task methods without @Internal annotation

Try to fix https://github.com/gradle/gradle/issues/17500.

@bot-gradle test QFL

OK, I've already triggered the following builds for you:

QuickFeedbackLinux build

@bot-gradle test QFL

OK, I've already triggered the following builds for you:

QuickFeedbackLinux build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

There's a network problem. I created https://github.com/gradle/gradle-private/issues/3504 to track it.
@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


[Roadmap] poe compatibility

Why
will more confortable have all in one UI
Description
Like openroute, pls put poe.com compatibility
Requirements
really i dont know what need put here....

OpenRourer offers lots of losers with a good api. What does poe offer? Seems like a website/app for bots to me.
What are the benefits to supporting Poe?

[image: SNAG-0291.png][image: SNAG-0293.png][image: SNAG-0292.png]
offer claude-2 100k and another interesting....
El lun, 5 feb 2024 a las 9:31, Enrico Ros @.***>)
escribió:

OpenRourer offers lots of losers with a good api. What does poe offer?
Seems like a website/app for bots to me.
What are the benefits to supporting Poe?
—
Reply to this email directly, view it on GitHub
https://github.com/enricoros/big-AGI/issues/396#issuecomment-1927136469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADIWFEHAUILL4URIP7QC5LYSDUNVAVCNFSM6AAAAABC2F46JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXGEZTMNBWHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

offer claude-2 100k and another interesting....

yes is possible, im use this: https://github.com/sunner/ChatALL, and have
all POE, free and payed if u have subscription
El lun, 5 feb 2024 a las 17:20, Enrico Ros @.***>)
escribió:

I see what you mean. However those are available inside the Poe website,
but not accessible by Big-AGI or other clients, right?
—
Reply to this email directly, view it on GitHub
https://github.com/enricoros/big-AGI/issues/396#issuecomment-1928251084,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADIWFDWU656VDCOOSZMJIDYSFLMNAVCNFSM6AAAAABC2F46JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGI2TCMBYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks. This is based off reverse engineering of the Web Poe client. We don't want to go down that route (which violates poe's terms of service, I'm sure). I'll keep this open until the official API comes out.

Product decision: will not support Poe thought non-official API.


Glossarie Support

Hey it would be amazing if this library could have a basic implementation for the Glossaries Api :)
https://www.deepl.com/de/docs-api/glossaries

Glossary APIs have CRUD and list operations, it takes time to implement these APIs in Rust. Because I don't have that much free time, so it might take longer than you expected to finish. But anyway, the create glossary API is already implemented in commit d1ae77f1f11582f1c67e8662389ff87a6bca0ecf. You can take a look at it and see if you like this API design in Rust.

I'm trying to add multiple entires

This is how DeepL design their API. They don't provide API to batch update glossaries.
I can add another helper function for this, but all I can do is make this action more comfortable. It still require multiple http requests.

The way i understood the API is that once a glossary is created, it basically becomes unmutable. For my application, it is totally fine to create a glossary with all the required entries and then just delete it once it is finished being used

it basically becomes immutable

No it isn't. You can call the delete glossary API. All CRUD operation are supported. What I meant is that the DeepL official APIs doesn't support batch glossary update, so this Rust wrapper doesn't consider batch update at design stage.

it basically becomes immutable

No it isn't. You can call the delete glossary API. All CRUD operation are supported. What I meant is that the DeepL official APIs doesn't support batch glossary update, so this Rust wrapper doesn't consider batch update at design stage.
Here is the CRUD operation example https://github.com/Avimitin/deepl-rs/blob/b625f1ec565ab507a1566d19e4ecd6e55e1205c7/src/endpoint/glossary.rs#L219.

I do a final check on formats and finally know what you mean. https://www.deepl.com/de/docs-api/glossaries/formats

Should be fixed in v0.6.0.


🐛Bug: Combobox not selecting when filtered objects contain undefined property

Describe the bug
I have a problem with an item not being set as selected if the selected object has a property that is undefined.
To Reproduce
Reproduction link: https://stackblitz.com/edit/github-jjgjbl?file=src%2Froutes%2F%2Bpage.svelte
Steps to reproduce the behavior:

Open the stackblitz
Select any option except from "5656"
Open the options again and observe none is styled as selected.
Select option "5656" witch has no elements as undefined.
Open options again and observe "5656" is selected.

Expected behavior
Any of the available options should be selected.
Screenshots
5656 styled as expected:

2341 styled incorrectly:

OS: Windows
Browser: Brave
Version: Version 1.60.110 Chromium: 119.0.6045.105

Additional context
Not sure if its relevant but it seems like $selected.value strips away the undefined properties

Issue Investigation Update:
After investigation, I think ive identified the root cause of the bug. In the listbox/create.ts file, the value undergoes stringification and is stored in the 'data-value' attribute. This process results in the loss of undefined properties.
The isSelected check employs deepEqual, which returns false in scenarios like deepEqual({a: undefined}, {}) // => false. To address this, I propose two potential solutions:
Preserve Undefined in JSON.stringify:
Adjust the stringification process to preserve undefined values. Refer to this Stack Overflow discussion for guidance.
Remove Undefined Properties Before deepEqual:
Alternatively, we can eliminate undefined properties before performing the deep equal check in isSelected().
I can contribute a pull request with either solution. Could you provide guidance on the preferred approach, or is there any other direction you'd like to take? I'm eager to assist in resolving this issue. 😊

Hmm, I don't think we should adjust to make undefined the same as null. Let's remove undefined before doing the deepEqual check


Update authentication-authorization.md

Updating SMART User role

@mikaelweave can you please review ?

Learn Build status updates of commit 60752d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/healthcare-apis/authentication-authorization.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@mikaelweave

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Learn Build status updates of commit cf1c9b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/healthcare-apis/authentication-authorization.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


add bluepill, remove ycontributors

closes #184
Removed the ycontributors section because it only made sense if the
service was still up, we can put it back if the service comes back online

Just one thing, this link is not working: https://feel-the-yearn.app/vaults

will fix this!


Docs: Revised basic tutorials

Description
Completed the basic tutorials with the latest AutoRA version to be released.
If the issue is on Github, simply link to it using the '#' symbol; otherwise, provide a notion page link):

resolves #569

Type of change
Delete as appropriate:

docs: Documentation only changes

small point, but per our code style guidelines, notebooks should be "Camel case with spaces for Jupyter notebooks: Example Notebook.ipynb"
ie, no dashes


Manually trigger single play of animation.

 I can only find loop modes?

Also change the color?


CI: pin xdist for Azure windows

pin pytest-xdist version in Azure Windows CI
to prevent new issue causing multiple CI failures

the simple method of diagnosis was that pytest-xdist
2.0.0 was released yesterday, so a bit of an educated
guess really

note that we're also pinning pytest itself for these
multi-core Windows test jobs:
https://github.com/pytest-dev/pytest/issues/7592

I should get around to making this multi-line pip dep specification into a nicely-formatted multi line yaml spec, but keeping diff simple for now.

Note that I've chimed in on a similar upstream bug report here: https://github.com/pytest-dev/pytest-xdist/issues/580
Our CI fail is reproducible, and the workaround of bumping to bleeding-edge pytest is not likely safe for us because of the ilp64 Windows memory issue linked above.

CI restored to all-green so self-merging the trivial adjustment until we can safely unpin.

Thank you Tyler!

Needs to be backported based on CI failures observed in gh-12906


fix: console error on xero customers page.

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/41862
PROPOSAL:
Tests

Precondition: Create a WS and add a XERO account to it

Open New Expensify
Log in with the prepared account
Navigate to the WS settings with the added XERO account
Navigate to the Accounting menu
Click on "Import" in the XERO settings menu
Navigate to the Re-bill Customers
Confirm that you don't see the following console.error.

Repeat the steps for Export > Preferred Exporter.

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

Offline tests

QA Steps

Same as Test Steps.

[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/3069065/8c0d214f-58cb-4ac0-b528-f65a63b39481

Android: mWeb Chrome
https://github.com/Expensify/App/assets/3069065/63884308-2d93-4ac3-976f-db6c17adaf45

iOS: Native
https://github.com/Expensify/App/assets/3069065/a9963c96-b0cb-45f7-a927-616eb4c48334

iOS: mWeb Safari
https://github.com/Expensify/App/assets/3069065/45b666fd-a768-4541-855a-4cae12c692b0

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/3069065/d3d13ee3-e535-4511-ac65-f0ec20e7ddbb
https://github.com/Expensify/App/assets/3069065/52af0902-4842-4f2f-8d74-3e52d1f0585e

MacOS: Desktop
https://github.com/Expensify/App/assets/3069065/b81f8844-3775-497a-b5e4-bbc85d3eef27

@c3024 You can ignore this PR.
@lakchote @hungvu193 @rushatgabhane Can one of you take a look at this PR?

Yeah I can take a look 👀

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/16502320/1ab64448-7a35-4c3a-b788-cb37bd11f08b

MacOS: Desktop

@mananjadhav I think POLICY_ACCOUNTING_XERO_PREFERRED_EXPORTER_SELECT has the same issue there, would you mind to fix it as well?

@hungvu193 Updated. Added web screencast as well. Checked for others, these two were the only ones.

🚀 Deployed to staging by https://github.com/lakchote in version: 1.4.77-11 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/lakchote in version: 1.4.77-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.78-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


displaying bug of github id

all works fine but : http://t.co/W7plubrD

Easy to fix, thanks

Similar  issue, my github id is "mobilemind", but Issues menu items show up as "[obilemind/repoName] issueTitle" using QuickHub 1.4.

@mobilemind Oh really, this is strange. In the issues items, this type of display pattern is for organizations i.e. [orgName/repoName] Title.
Can you attach a screenshot?

@chamerling Working fine now. Consider this closed.
I am unable to reproduce the Issues menu items issue. I tried going online/offline, sleep/wake, accessing repos with Gitbox app (Mac), SourceTree app (Mac), running bash scripts that called git, etc. THose were all things I was doing yesterday when I saw it consistently. All I can come up with now is maybe some sort of special character encoding problem from a weird character in an issue I've recently closed.

@mobilemind thanks for the feedback, I also vote for something strange or github API issue sometime...

@mackristof Just removed all my profile information from github account and I can not reproduce your bug. It may have been fixed in the GitHub API.


Polymer + scrollify --> Not in chrome

If you use Polymer, scrollify not work in chrome (in FireFox is ok).
<link rel="import" href="https://www.polymer-project.org/0.5/components/paper-ripple/paper-ripple.html">

EDIT:
Work in Chrome:
<link rel="import" href="https://www.polymer-project.org/0.5/components/paper-ripple/paper-ripple.html">
<script src="js/jquery.scrollify.min.js"></script>
<script src="js/jquery.scrollify.js"></script>

Doesn't work in Chrome:
<script src="js/jquery.scrollify.min.js"></script>
<script src="js/jquery.scrollify.js"></script>
<link rel="import" href="https://www.polymer-project.org/0.5/components/paper-ripple/paper-ripple.html">

Thank you @Lifka I was going crazy with this issue!!!


set key frame flag for container format.

container format will use this information to build seek index.
This will make the mp4 seekable

Coverage remained the same at 80.563% when pulling bafc55a9d78485f176253af9dcad5fb82de89ebb on xuguangxin:seek into d3992e510b9c4e67ad99f8ceaa59943dc34534f7 on xiph:master.

Coverage remained the same at 80.563% when pulling bafc55a9d78485f176253af9dcad5fb82de89ebb on xuguangxin:seek into d3992e510b9c4e67ad99f8ceaa59943dc34534f7 on xiph:master.


[BUG][NOWEB] - stopped uploading status (story)

statuses not sent
Version
{
  "version": "2024.6.2",
  "engine": "NOWEB",
  "tier": "PLUS",
  "browser": "/usr/bin/chromium"
}

Expected behavior
When using endpoints /api/{session}/status/{type} (happened in types: text and image, the rest were not tried)
Status not sent
Although the response is success - 201
Engine I'm using NOWEB engine.

Update
For now, deleting the session and reconnecting solved the problem
I will update later if the problems return

Have You Tried Turning It Off And On Again

That would be our first question anyway :D That's great it helped!


Bookstore: Components

Hi, in this pull request I added the following:

Initialized create-react-app.
Created a directory for your components.
Added two pages with react-router:

BookList - the default view
Categories

Styling not implemented yet
Cheers :)

Hi @rloterh, thank you so much for your suggestions, I will consider them


load service config only once

Fixes #153

locally service tests now === 62 passed, 3 warnings in 3.42 seconds ===

I don't have the patience to deal with requre tests right now.


Document how to expose services

[ ] Document how end users are supposed to expose their services. This is usually done by creating new ingress objects.
[ ] Document how docker, kind, and core services work together.
[ ] Document how DNS work. Inside and outside cluster.

https://github.com/cnoe-io/website/pull/61


Additional instruction steps

To indicate the tools needed to build and serve the code.

Thanks, mate! So you got it to work OK?

I did! It's working wonders locally, now. So, thank you.


Create Route_Bootstrap::use()

As with BladeOne and Ajax, Route should have its Bootstrap class for incorporating into Perique.

Not needed


Add a link to the wiki

It seems like there is duplication between the wiki site and docs.substrate.dev, while the latter appears to be more comprehensive.

Simply adding a link to the top bar of this repo (where the tags are) to https://www.parity.io/substrate/, should be sufficient.


Use of _routerMicrolib.currentHandlerInfos private API is deprecated

See https://emberjs.com/deprecations/v3.x/#toc_remove-handler-infos
https://github.com/DockYard/ember-route-action-helper/blob/dc9ca2e0276f887b55639f6fb858c00bcbe53d76/addon/helpers/route-action.js#L10-L12

:+1: on getting this fixed, just updated to ember 3.7.x and getting this deprecation

I suspect #87 fixes thsi

I made a new PR #88 with passed tests.
I am waiting merge ..

Can confirm #88 works as expected

I suggest you stop waiting and instead use a local helper.

Closed by #88


Update Fabric CLI to handle attested memberships for networks

Currently, the Fabric CLI just creates and records an unattested membership structure. After the introduction of IIN Agents, the addition of local and foreign attestations to the basic membership protobuf, and the upgrading of the membership portion of the Fabric Interop CC, we need to upgrade the Fabric CLI to support the new protobufs and Fabric Interop Chaincode API.

Fixed in https://github.com/hyperledger-labs/weaver-dlt-interoperability/pull/316.


Release 0.12.0-rc0

This is a tracker issue to synchronise issues blocking 0.12.0-rc0 and PRs which shouldn’t be merged before 0.12.0-rc0 is released.
This issue should be updated to depend on any blocker, and any PR which is targeted post-0.12.0-rc0 should be updated to depend on this issue.
Depends on https://github.com/submariner-io/submariner-operator/pull/1838
Depends on https://github.com/submariner-io/submariner-operator/pull/1789
Depends on https://github.com/submariner-io/cloud-prepare/pull/198
Depends on https://github.com/submariner-io/shipyard/pull/721
Depends on https://github.com/submariner-io/submariner/pull/1676
Depends on https://github.com/submariner-io/shipyard/pull/723
Depends on https://github.com/submariner-io/submariner/issues/1635
Depends on https://github.com/submariner-io/submariner/issues/1636
Depends on https://github.com/submariner-io/submariner/issues/1637
Depends on https://github.com/submariner-io/submariner-operator/issues/1723
Depends on https://github.com/submariner-io/submariner-operator/pull/1843
Depends on https://github.com/submariner-io/lighthouse/pull/682
Depends on https://github.com/submariner-io/submariner/pull/1695
Depends on https://github.com/submariner-io/submariner-operator/pull/1845
Depends on https://github.com/submariner-io/submariner-operator/pull/1812
Depends on https://github.com/submariner-io/submariner-operator/pull/1848
Depends on https://github.com/submariner-io/submariner-operator/pull/1851
Depends on https://github.com/submariner-io/submariner/pull/1701
Depends on https://github.com/submariner-io/lighthouse/pull/689
Depends on submariner-io/submariner-operator#1866
Depends on https://github.com/submariner-io/submariner-operator/issues/1830
Depends on https://github.com/submariner-io/submariner-operator/pull/1863
Depends on https://github.com/submariner-io/submariner/pull/1704
Depends on https://github.com/submariner-io/submariner/issues/1700
Depends on https://github.com/submariner-io/admiral/pull/321
Depends on https://github.com/submariner-io/lighthouse/pull/691
Depends on https://github.com/submariner-io/shipyard/pull/728
Depends on https://github.com/submariner-io/submariner/pull/1707
Depends on https://github.com/submariner-io/submariner-operator/pull/1875
Depends on https://github.com/submariner-io/submariner-operator/pull/1877
Depends on https://github.com/submariner-io/shipyard/pull/742
Depends on https://github.com/submariner-io/submariner-operator/pull/1884

Dropping the ARM PRs since they’re not getting reviews and there’s no point in delaying the release for that.

Released


Refactor: clang tidy

Description
Refactor the existing code base to comply some c++ code standards. One good candidate is c++ core profile.
Step 1: assessment
Assess the current state of VAPOR code base to see how much it is adhering to a profile, and how much effort is required to refactor it to comply.
Step 2: decision making
Based on the outcome of Step 1, decide if we want to go fully comply with a c++ code standard.

Duplicate of #2759.


Testing existing notification bug

Working off @ankitmashu's create notif branch
Since the existing notification bug can be now be reproduced in testing, we make it a repeated test and run 150 times to see how may times it will get triggered

OK, all 150 of the existing notif tests failed! Locally, a handful failed
Pushing a commit to try and fix the issue
One guess is that the response is sent back from the service before the transaction is committed and due to this, the duplication check returns 0 rows instead of 1 row

Seems to work, retesting for good measure

retest this please

Closed (#221)


[BUG] crash when not connected to internet

Describe the bug
When your not connected to the internet, and you perform a task i.e. sending data to Firestore Database, the app crashes.
To Reproduce
Disable internet before submitting firebask task.
func upload_new_item(data : Dictionary):
	var firestore_collection : FirestoreCollection = Firebase.Firestore.collection(firestore_collection_id)
	var document_id = "document_id"
	var fields = data
	var add_task : FirestoreTask = firestore_collection.add(document_id, fields)
	var added_item : FirestoreDocument = yield(add_task, "task_finished")
	return added_item

Expected behavior
print(err code: Connection error   Error connecting to auth service)
return err

or something like that
Screenshots

Environment:

Windows 10

Additional context
Add any other context about the problem here.

@shafnaz any update on this?
Thanks
Chuck

well I just log in like this:

I disable my connection to wifi, and then run the project

OK. Can you break that code down for me since it does not look like the normal code we run.
I can only assume userinfo is another node somewhere?
Thanks
Chuck

Oh, right. Sorry about that.

pretty straight forward

What happens after that 4 second yield time. Can you share more of the code?

Well nothing relating to log in, I create a document after that. I just give it some space. The issue still happens even if I remove any code after that.

hold on, I'm getting something else. I removed the login code, I still get the error, it's coming from something else

Alright let's close this issue, The error is coming from a scene. _process is running a code


remove index of socketstream

the next first step in removing stream from phobos
https://github.com/D-Programming-Language/dlang.org/pull/1002

thanks


My English is not good, so I use translation software and attach the original Chinese text.

A lot of people coding with the old integrated IDE, because the IDE doesn't support UTF-8 and the original developer doesn't upgrade and maintain it, But it has a long-term audience.
For example, 8 - bit microcontrollers, low - cost appliances will not use 32 - bit ARM
VS CODE has a great reputation for being the best microeditor for all coders, but the hover prompt is garbled, and the hover code cannot be set, isn't it ironic?
Most people would never want to open and close a file with F12 if they could get a hover prompt.
Coding is also an important part of the development history of computer. We can't ignore the needs of developers of old products just because most users are now developers of Internet companies. We also want to happily produce low-cost daily products for the world.
But it's been five years since I first started using VS CODE in 2018, Although KEIL and IAR are sometimes used, But when I have to use an older IDE, I had to make a painful choice between coding, Is it normal programming in VS CODE, and then the IDE is full of gibberish (it still compiles), or is the IDE display normal, but VS CODE can't use hover prompts.
Besides ARM, there are a lot of older process manufacturers and older ides.
I saw some of the previous issues, Because there are not enough votes in a short period of time, it can't get into the backlog. I am sad, We embedded developers are often too busy programming and following up on the production floor, Little time to focus on VS CODE iteration planning and problem feedback.
https://github.com/microsoft/vscode/issues/100994
I don't believe TypeScript can only open file streams using UTF-8. If this is really difficult to fix, Can you add a new feature that converts hover characters to "Files:Encoding" set before output? or give the user a separate option.
If this requires the developer update iteration of the language plug-in, then many languages may take a long time to update. Use multiple languages such as c/ C ++, ASM, Makefiles. Can you give me a tutorial to change the display coding myself.
I know the VS CODE developers are working very hard, but please, think about this, or change the voting time to a permanent cumulative vote, so that users can vote when they search for a question like this, users can vote for it without having to go through a lengthy discussion like mine, thank you very much.
我的英文不好,使用翻译软件并附上中文原文
鼠标悬停智能感知提示固定为UTF-8编码,这是一个明显而愚蠢的错误。
大量使用旧集成IDE进行编码工作的人,由于IDE不支持UTF-8,原开发商也不会进行升级维护,但是它有长期稳定的用户。
例如8位单片机,低成本小电器不会使用32位ARM。
VS CODE有很好的口碑：最好用的微编辑器,适应所有代码工作者,悬停提示却是乱码,且无法设置悬停的编码,这不是很讽刺吗?
大多数人如果能获得悬停提示,就绝不想用F12打开文件再关闭文件。
编码也是计算机发展史中重要的一环,不能因为现在多数用户是互联网公司的开发者,编码随意切换或转换,就忽视了旧产品开发者的需求,我们也想开心的为世界生产低成本日常用品。
但我从2018年首次使用VS CODE发现这个问题,已经5年了,虽然有时候使用KEIL和IAR,但在我必须使用更旧的IDE时,我不得不在编码之间痛苦的选择,是在VS CODE中正常编程,然后IDE里面全是乱码(仍可编译通过),还是IDE正常显示,但是VS CODE无法使用悬停提示。
要知道除了ARM还有大量的旧工艺制程厂商和很有年代的IDE。
我看到之前的一些议题,因为短时间内投票数不足,就无法进入积压。我很伤心,我们嵌入式开发者经常忙于编程工作和跟进生产车间,几乎没有时间关注VS CODE的迭代计划与问题反馈。
https://github.com/microsoft/vscode/issues/100994
我不相信TypeScript只能使用UTF-8打开文件流,如果真的很难修复,能否增加一个新功能特性,在悬停字符输出前转换成"Files:Encoding"设定的编码,或给用户一个单独的选项
如果这需要语言插件的工发者更新迭代,那么多种语言可能需要很久才更新,我使用多种语言例如c/c++、ASM、makefile等,能否给我一个自己修改显示编码的教程
我知道VS CODE的开发者们非常辛苦,但求求你们了,请认真考虑这个问题,或者修改投票时间为永久的累积投票,这样用户在搜索到这样的问题时就可以顺手投上一票,而无需像我一样长篇大论,非常感谢

please...

The problem should be caused by extensions, many of which use the NodeJs fs module or workspace.fs to read files directly, which requires inferring the text encoding itself, but they will almost always use the default encoding (utf8)
If they use workspace.openTextDocument, it will apply the text encoding inferred by the editor, which will solve the above problem
I suggest adding a similar interface to the File System API

@cjr163 Please provide reproducible steps.

see https://github.com/microsoft/vscode/issues/100994#issue-645052704

I very much agree. I happen to have the same problem.
My more commonly used language is python, when my default encoding is gbk, when I try to introduce other py files in the main file, if the py file is open, then vscode can normally show code hints.
But if the file is closed, the vscode code hint will be displayed as garbled.

The editor hover doesn't hard-code any specific encoding. The editor hover displays the strings it receives via the VS Code HoverProvider API. Reading files in a certain encoding is something that the language servers need to support when they read files from disk.
@Weidong725 You mention that you have a problem in Python. Please create an issue against the Python extension.
@mjbvz The first comment here mentions TypeScript. Forwarding to you.

It's unclear what the issue is. Please provide a concise code example that demonstrates the problem

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

I found a issue.  It seem provide s setting to control, sadly I can't find where it is


No content is being returned in my template.

The title is updating, but the content I add to SquareSpace is not being added to the local site. I looked in the sqs-cache for my content, and the data includes my video and gallery, but it's not added to the page.
I am using a sandbox account, and I get no errors from the server. If you could point me in the right direction? Thanks

If you add content in the CMS, you have to bust your local cache manually. Either stop the server and run sqs buster or use the ?nocache query string parameter on the page. Let me know if that helps.

It does not. It does seem to work to a degree, the site title changes, and the color of the page seems to have changed. The content is configured as pages under the welcome page.

When I changed the background color from black, it seems there's a message "You must select a collection to display."

Hmm, what template are you using? Also, any more specifics? The more info I have the better I can help troubleshoot what may be happening.

I can appreciate that, I wish better knew what to provide. The theme is "Pacific".

That's a starting point. How much have you changed on it so far?

Also, even though it sounds like these aren't your issues, it may help to check this section of the readme out just in case: https://github.com/kitajchuk/node-squarespace-server#troubleshooting

Not much, content, and a little css

https: Check
"sandbox:true" in template.conf > server: Check
Cache buster tried: Check

there's a hyphen in my user name, could that be related?

I don't think so. As long as you are logging in fine locally that wouldn't be an issue. I just spun up a site using that template and have it running locally with what appears to be your issue: no content. This is also causing a Javascript error to be thrown locally in site.js. I'll dig around and see if I can resolve this problem.

Good news. It appears the problem is in the use of this predicate: {collectionTypeNameEquals? type}. I haven't run into this one yet and as far as I know, its not in the public docs. This resolve will actually require an update to https://github.com/kitajchuk/node-squarespace-jsont. Once that is published you can reinstall the server with npm and you should be clear on this issue. I'll let you know when this is ready.

Thanks for the effort!

I published the changes. The new version of the server:
<EMAIL_ADDRESS>And the version of jsont it should be pulling is:
<EMAIL_ADDRESS>Let me know if that helps. I would run sqs buster after updating your server install with npm just to start fresh again.

Success! Thanks so much! For the record, my update command failed, so I
 npm remove -g node-squarespace-server

then
 npm install -g node-squarespace-server

then
 sqs buster

then
 sqs server

Logged in, and watched your beautiful code render my site. Thanks! Id gladly buy you a beer, anytime.

Awesome! Glad we figured it out :)


component removed from the dom on backspace

Hi and thank you for an awesome, awesome component!
In case I've been missing something, in my app, the component is removed from the DOM when the last character is deleted
from the input field using the backspace key.
Is it to be expected and if yes, is there a way to prevent this behaviour? Otherwise, I'm happy to provide you with more info.
Regards,
Candide

@ckemmler thanks!
The component is removed because it the condition in the wrapping ngIf is false when there's no data.
At the moment there's no way to prevent this, but a version that will let you customize the CSS and HTML is under work - will take some time to complete though.

@ckemmler, you can now create a custom component that will have a different behavior.
hope it helps.


Docs: Top left logo should go to glaredb.com not docs.glaredb.com

Description
If you start in glaredb.com then navigate to the docs, there is no way to get back to the home page. I usually expect the top left logo to take me back to the home page. Instead it takes me back to the docs home page.
I find it mildly annoying that there's no way back to the home page once inside the docs.
Some examples of other sites that redirect back to the homepage instead of the docs home

https://clickhouse.com/docs
https://www.mongodb.com/docs/

--
Alternatively, the logo should reflect that it is for the docs. Such as is the case with github

https://docs.github.com/en

Solution here: https://github.com/just-the-docs/just-the-docs/discussions/1451#discussioncomment-8987126


MeshInstance2D (with ArrayMesh) lags occasionally when adding surfaces

Godot version
3.4.4 stable mono
System information
Windows 10, GLES2 / GLES3, GeForce RTX 2080 TI, 511.79
Issue description
I am trying to generate a terrain using MeshInstance2D instead of a tilemap. I generate the terrain in 8x8 chunks and I use AddSurfaceFromArrays to add the surface data to my ArrayMesh.
Most of the calls are fine and takes 0 ms, just a few ticks. However occasionally it can take as long as 70 ms, it looks like some buffer overflows or so and then it gets flushed.
Example Log from program:

492: Adding Surfaces (Surfaces: 4, Vertex Count:11418) took 0 milliseconds (7302 ticks)
522: Adding Surfaces (Surfaces: 3, Vertex Count:5592) took 70 milliseconds (703189 ticks)
522: Adding Surfaces (Surfaces: 3, Vertex Count:6510) took 0 milliseconds (5595 ticks)
[snipped out some here]
522: Adding Surfaces (Surfaces: 4, Vertex Count:17574) took 1 milliseconds (14659 ticks)
522: Adding Surfaces (Surfaces: 4, Vertex Count:15582) took 1 milliseconds (11847 ticks)
552: Adding Surfaces (Surfaces: 3, Vertex Count:5178) took 16 milliseconds (160357 ticks)
552: Adding Surfaces (Surfaces: 3, Vertex Count:5478) took 0 milliseconds (5478 ticks)
552: Adding Surfaces (Surfaces: 3, Vertex Count:4896) took 0 milliseconds (3831 ticks)

Steps to reproduce
I attached a project, you just need to run it with 3.4.4 mono and start it. Instructions are on the label.
Minimal reproduction project
MeshInstance2DProblem.zip

Can you reproduce this in a GDScript project? If not, this is likely due to a C# garbage collection stall.

Unfortunately I don't really have the time right now to reproduce this in GDScript, however I did try adding a GC.Collect() right before starting the stopwatch and calling AddSurfaceFromArrays and the problem persisted.
So my code looks like this now,
GC.Collect();
StopWatch.Start();
((ArrayMesh)MeshRenderers[key].Mesh).AddSurfaceFromArrays(Mesh.PrimitiveType.Triangles, segment.Meshes[key]);
StopWatch.Stop();

I think that should rule out garbage collection, it doesn't happen every frame either. This is the output with the garbage collection changes active, the same thing happens.

Adding Surfaces (Surfaces: 4, Vertex Count:10584) took 0 milliseconds (8023 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:10584) took 0 milliseconds (7416 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:10584) took 1 milliseconds (11794 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:2646) took 13 milliseconds (131741 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:2646) took 0 milliseconds (5160 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:5292) took 0 milliseconds (4602 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:2646) took 64 milliseconds (647854 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:2646) took 0 milliseconds (3100 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:2646) took 0 milliseconds (3258 ticks)
Adding Surfaces (Surfaces: 4, Vertex Count:2646) took 0 milliseconds (3218 ticks)

If this isn't good enough to rule out the garbage collection then I will see if I can get time to make a simple GDScript version sometime later.


Clarify why bins have Cargo.lock but libs don't

Closes #525
r? @wycats

What if my crate can be used both as lib and bin ?

@xieyuheng You can check in your Cargo.lock file if you want to.  When used as a lib dependency, it will be ignored.  Just beware if you want the Cargo.lock file to be honored for a binary with cargo install from a registry you'll need a nightly/unstable feature publish-lockfile.


[Segment Replication] Close writer on segment replication cancellation

Description
Close MultiFileWriter on segment replication cancellation.
This bug appears rarely and happen during failover where promoted replica cleans up its store while having multiple file copy operations in progress. The clean up deletes temporary replication files which conflict with one of file copy thread's validation. Existing cancellation skips writer close as target ref count does not goes to 0 when there are multiple file copy operations is in progress. Target is inc'ref with every file chunk handler but during cancellation the target is dec'ref once and thus closeInternal action (which closes writer) on target is prevented.
Timeline from one failing test
node_t2 is started as replica which performs segrep with older primary on node_t1.
[2023-04-07T19:10:23,524][INFO ][o.o.i.r.SegmentReplicationTarget] [node_t2] [test-idx-1][0] [31206] Replication diff for checkpoint ReplicationCheckpoint{shardId=[test-idx-1][0], primaryTerm=1, segmentsGen=3, version=11, size=93731, codec=Lucene95} RecoveryDiff{identical=[], different=[], missing=[name [_1.cfs], length [56235], checksum [1vl1wuo], writtenBy [9.6.0], name [_0.cfe], length [479], checksum [1gnw71m], writtenBy [9.6.0], name [_0.si], length [318], checksum [97u0s0], writtenBy [9.6.0], name [_1.cfe], length [479], checksum [qmaym9], writtenBy [9.6.0], name [_1.si], length [318], checksum [1bqh7cs], writtenBy [9.6.0], name [_0.cfs], length [35902], checksum [vzl70q], writtenBy [9.6.0]]}

Meanwhile older primary is stopped which promotes node_t2 as new primary. During node_t2 promotion, engine is reset, where replica commit its latest processed checkpoint, followed by store clean up. This clean up deletes all files not referenced in latest commit on store and clean up deletes the temporary replication files.
[2023-04-07T19:10:23,657][INFO ][i.s.deletes              ] [node_t2][test-idx-1][0] [31196] After commit: delete file replication.teSJpKFuT-6pgtOxNsffsA._0.cfe
[2023-04-07T19:10:23,658][INFO ][i.s.deletes              ] [node_t2][test-idx-1][0] [31196] After commit: delete file replication.teSJpKFuT-6pgtOxNsffsA._0.cfs
[2023-04-07T19:10:23,658][INFO ][i.s.deletes              ] [node_t2][test-idx-1][0] [31196] After commit: delete file replication.teSJpKFuT-6pgtOxNsffsA._0.si
[2023-04-07T19:10:23,659][INFO ][i.s.deletes              ] [node_t2][test-idx-1][0] [31196] After commit: delete file replication.teSJpKFuT-6pgtOxNsffsA._1.cfe
[2023-04-07T19:10:23,659][INFO ][i.s.deletes              ] [node_t2][test-idx-1][0] [31196] After commit: delete file replication.teSJpKFuT-6pgtOxNsffsA._1.cfs

The on-going replication process on replica is not aware of this clean up and thus fails while validating post file copy.
[2023-04-07T19:10:23,663][INFO ][o.o.i.r.SegmentReplicationTarget] [node_t2] [test-idx-1][0] [31206] --> Failure reported, current list of files [segments_5, write.lock]
java.lang.AssertionError: expected: [replication.teSJpKFuT-6pgtOxNsffsA._1.cfs] in [segments_5, write.lock]
...

Test
The test does not fail in 2k iterations locally, it fails after 2k success runs for a different reason. Created https://github.com/opensearch-project/OpenSearch/issues/7063 to track this.
Issues Resolved
Resolves #6762
Alternatives Considered

ensureOpen.run() inside innerWriteFileChunk method. It wouldn't work as target doesn't goes down to 0.
https://github.com/opensearch-project/OpenSearch/pull/7044 prevents store clean up with store commit. This fix is still needed as it performs important clean up of IndexOutput objects post writer close.
Don't incref target with every chunk handler.

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #7062 (a93f284) into main (53b128f) will increase coverage by 0.00%.
The diff coverage is 33.33%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##               main    #7062   +/-   ##
=========================================
  Coverage     70.78%   70.79%
- Complexity    59269    59301   +32
=========================================
  Files          4823     4823
  Lines        283985   283986    +1
  Branches      40953    40954    +1
=========================================
+ Hits         201026   201048   +22
- Misses        66403    66462   +59
+ Partials      16556    16476   -80

Impacted Files
Coverage Δ

...ter/snapshots/get/TransportGetSnapshotsAction.java
41.58% <0.00%> (ø)

.../indices/replication/SegmentReplicationTarget.java
90.35% <100.00%> (+0.08%)
:arrow_up:

... and 498 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


fix bug with sentinels and string arguments

Description
There are integration bug with actioncable and redis-client with sentinels config.
It is possible to reproduce within this repo https://github.com/moofkit/actioncable-redis-sentinel-bug
$ bundle && bundle exec rails test
Running 1 tests in a single process (parallelization threshold is 50)
Run options: --seed 7348

# Running:

E

Error:
ActioncableTest#test_broadcasts_to_test_channel:
ArgumentError: unknown keywords: "host", "port"
    test/integration/actioncable_test.rb:5:in `block in <class:ActioncableTest>'

rails test test/integration/actioncable_test.rb:4

Finished in 0.043971s, 22.7423 runs/s, 0.0000 assertions/s.
1 runs, 0 assertions, 0 failures, 1 errors, 0 skips

The problem is that config for the cable is a YAML file and sentinels are deep nested hash in the sentinels array and even deep_symbolize_keys don't convert it to the symbols. So sentinels keys should be converted to symbol explicitly like in this fix
# config/initializers/action_cable.rb
require "action_cable/subscription_adapter/redis"

# https://github.com/rails/rails/blob/da309a582e04183a85340ec0e1ed59b2d69ca9c2/actioncable/lib/action_cable/subscription_adapter/redis.rb#LL18C21-L18C61
ActionCable::SubscriptionAdapter::Redis.redis_connector = lambda do |config|
  # BUG: it needs to symbolize keys for redis gem >= 5.0.0
  config[:sentinels] = config[:sentinels].map(&:symbolize_keys) if config.key?(:sentinels)
  Redis.new(config.except(:adapter, :channel_prefix))
end

I'm not sure should it be fixed in actioncable or here, but this PR is a patch for redis-client to handle such configs without errors.
If this is not the right place, I will try to fix it on the rails side.

I'm not sure should it be fixed in actioncable or here

I believe it should be fixed in Action Cable. Please file a PR there and ping me, I'll review and merge it.


Status code as string

Of course it's trivial to convert between Number and String but maybe String is a better default as
statusCode.startsWith("2") /  statusCode.startsWith("4") type of operations seems
to naturally follow the response.

I think it makes more sense to use numbers so that you can do stuff like statusCode > 200. Long term it may be doing something like #41 where any request made to the server that receives a response will be treated as success. Only errors that can't reach the server will be treated as an error. It would be much more necessary in this case to allow something like statusCode >= 200 && statusCode < 300.
Should be easy enough to just do String(statusCode).startsWith('2').

Ah, maybe you're right.


Shenzhen, China IPFS

Meetup
Date：10, Mar
Details: http://mp.weixin.qq.com/s/imvW34IFW8JTbYWVv-Vg_g
and https://www.meetup.com/shenzhen-ipfs/events/248375272/
主题：IPFS和Filecoin的技术分享
主讲人：飞向未来
地点：银河创客咖啡
时间：2018.3.10 下午14：00
人数：80人

Machine translated version for those who are curious like me :)
Topic: Technical Sharing of IPFS and Filecoin
Speaker: Fly to the future
Location: Galaxy Chongke coffee
Time: 2018.3.10 at 14:00
Number of people: 80 people

Hi Tainyi, the QR Code for the wechat group says there are more than 100 members and an invite is needed to join.
I found your wechat contact on here (flytofuture_tt) and got in touch, but writing it here for others to see.
My Mandarin is limited, hope I'll understand something ;)

@ahoebeke  yes, flytofuture_tt is official wechcat. Thank you.
@diasdavid  This is cool. lol

@diasdavid  Too many people want to attend meetup(2018.3.10), I have decided one more meetup at 2018.3.11.

@dongtianyi  Having 2 events in one weekend might mean that lessons learned from the first event cannot so quickly be adapted to improve the second meetup. It also means that people who attended the first time will not come again the next day for the same presentation.. which splits the community a bit.
That being said, it's great that you have so much energy! and that so many people are interested.
@diasdavid  how do such meetups usually get organised? Is there an IPFS-meetup guidelines document, best practices, maybe recommended PPT to save some time and be sure we've got the latest info? (Shared resources for all meetups, which could be more useful for workshops, dev demos etc)

@ahoebeke

It also means that people who attended the first time will not come again the next day for the same presentation
Yes. This is right.

Ahaha @dongtianyi you are unstoppable! Great work on gathering so much interest so quickly :)
@ahoebeke all good questions! We are working on creating a set of materials meetups can use (slidedecks, tutorials and so on) but they are not ready yet. Meanwhile you can use the IPFS Examples -- https://ipfs.io/docs/examples/  + https://github.com/ipfs/js-ipfs/tree/master/examples -- and libp2p Examples -- https://github.com/libp2p/js-libp2p/tree/master/examples. As for best practices, definitely make sure to go through the IPFS Community Code of Conduct -- https://github.com/ipfs/community/blob/master/code-of-conduct.md.

@diasdavid  more and more meetups are planning.
Shanghai
Hangzhou
Fuzhou  (2018-03-24)
Chengdu
Xia'men
....
I am introducing IPFS/Filecoin to Chinese people.(Users, Developers, Miners,  and so on.)

Wow!!
Makes me wonder, are there Chinese resources for IPFS? A Chinese-language version of the Github IPFS homepage would be useful maybe? @diasdavid @dongtianyi

@ahoebeke   Yes, If so, It is very useful.  Actually, I have translated some blog for filecoin.io.
Maybe we can trans filecoin.io and ipfs.io homepage.

are there Chinese resources for IPFS

I am writing technical articles.
https://zhuanlan.zhihu.com/ipfsguide
or
Wechat Official account: IPFS指南 (ipfs_guide)

Sadly, the Chinese government already censored ipfs.io.
The reason, in my opinion, is that the best use case of IPFS in china is to break internet censorship.


fix codeGroup when multiple tabs, fix refs in stories, change z-index to 40 (tooltips)

Changes

Contains some minor fixes for CodeGroups (tabs).
Fix ref types in stories
Reduce z-index on tooltip to 40

It's not. Just thought we reserve 50 for overlays.


Add methil sword in the Readme also

(Oopsi, i forgot it, in this part lol...)

And also, if possible add a little comment on every item


Rhythmbox Python plugins don't work

Describe the bug
Rhythmbox ships a bunch of plugins that are written in Python, but they don't seem to work in Rhythmbox as it's currently packaged.
Steps To Reproduce
Steps to reproduce the behavior:

Install rhythmbox
Look in the settings, in the plugins tab
Observe that a large number of plugins (e.g. for replaygain support) are missing

Expected behavior
Rhythmbox's Python plugins should be usable.
Additional context
I got some way towards fixing this with the following overlay:
  (self: super: {
    rhythmbox = super.rhythmbox.overrideAttrs (old: {
      configureFlags = (old.configureFlags or []) ++ [
        "--enable-python"
      ];
      buildInputs = (old.buildInputs or []) ++ [
        super.python3Packages.pygobject3
        super.gobject-introspection
      ];
    });
  })

which at least makes the Python plugins show up in the settings menu, but enabling them fails, printing the following to xsession-errors:
Sep 30 21:33:15 the .rhythmbox-wrap[743623]: Error initializing Python Plugin Loader: PyGObject initialization failed
Sep 30 21:33:15 the xsession[743623]: ImportError: could not import gobject (error was: ModuleNotFoundError("No module named 'gi'"))
Sep 30 21:33:15 the .rhythmbox-wrap[743623]: Please check the installation of all the Python related packages required by libpeas and try again
Sep 30 21:33:15 the .rhythmbox-wrap[743623]: Loader 'python3' is not a valid PeasPluginLoader instance

I tried setting strictDeps = false; as suggested in other issues related to gobject-introspection, and also adding gobject-introspection to nativeBuildInputs, but couldn't get any closer to getting the plugins working.
Notify maintainers
@rasendubi
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.63, NixOS, 21.05.3065.b3083bc6933 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.15`
 - channels(ash): `"home-manager-21.05, nixos-unstable-21.11pre318500.51bcdc4cdaa"`
 - channels(root): `"nixos-21.05.3065.b3083bc6933"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Have you tried adding python modules to propagatedBuildInputs? Another option to try is adding python to dependencies—if I understand correctly, it should have a setup hook to set env variables for python to find its libraries later.

I tried moving python3Packages.pygobject3 to propagatedBuildInputs, but it still doesn't seem to work. And buildInputs already includes python3 in the nixpkgs derivation, right? https://github.com/NixOS/nixpkgs/blob/9a23237031b385945132c8dac7d7ad97ece67408/pkgs/applications/audio/rhythmbox/default.nix#L57-L58

The error come from here. I think libpeas must be patched to initialize using given PATH and PYTHONPATH or sys.path.

I'm able to take this further by wrapping rhythmbox with PYTHONPATH prefix.
{
  preFixup = ''
    gappsWrapperArgs+=(
      --prefix PYTHONPATH : "${super.python39Packages.pygobject3}/lib/python3.9/site-packages/"
      --prefix PYTHONPATH : "$out/lib/rhythmbox/plugins/"
    )
  '';
}


add APIRoute Feature

Implement an APIRoute, it's similar to Pait, but it's easy to register routes into the app.It is implemented as follows:
class APIRoute(object):
    def __init__(self, **kwargs) -> None:
        pass

    def inject(self, app: Any, **kwargs: Any) -> None:
        pass

    def include_sub_route(self, route: "APIRoute") -> None:
        pass

    def add_api_route(self, **kwargs) -> None:
        pass

    def add_route(self, **kwargs) -> None:
        pass

inject method: responsible for registering the routes in APIRoute into the app
include_sub_route:This method adds the route from another APIRoute, but modifies some attributes, e.g. APIRoute(path='/api').include_sub_route(path='/demo', func=demo), then demo ends up with a path of /api/demo.
add_api_route: Adding routes to APIRoute
add_route: Decorator implementation of add_api_route

Pait contains a large number of identical parameters, as does APIRoute, which uses Unpack[TypedDict] for ease of maintenance. However, only VSCode supports PEP692, and Pycharm hasn't supported this feature for two years. see: https://youtrack.jetbrains.com/issue/PY-55044.
Until Pycharm solves this problem, consider using Pyright Language Server to solve the problem.

Fortunately, Pycharm version 2024.1.2 already supports TypedDict and Unpack.  see: https://www.jetbrains.com/pycharm/whatsnew/


Video transfer

Hi there is a patchy areas that jump around between images in video transfer.
This isnt so much temporal issues with the style transfer of features as much as little patches of luminance change that flicker around....Is this something to do with theWhiten-Color Transform as it doesnt happen when using the Adain method with your implementation?

@Sugarbank I think so. Currently, our extension to video is not good and the SVD decomposition looks more unstable for consecutive frames than changing the mean in AdaIN.


Add a download failure message, rather than trying to unzip an HTML page

What does this change accomplish?
If you try to install a build where the URL it downloads gives you an HTTP 403 response, previously Tophat would ignore the status code and save the resulting response body to the target file. Later it would get a failure trying to unzip this file.
How have you achieved it?
Tophat now looks for a 200 response status code, and if it is not, it reports it as an error. The failure reason is attached to the the error enum so that we can display it to the user.
How can the change be tested?
Open up an install URL to a non-existent AWS S3 bucket:
http://localhost:29070/install/ios?virtual=https://some-bucket-we-dont-have-access-to.s3.us-east-1.amazonaws.com/foo/build.app.zip
See the error like this:

I have signed the CLA

Hey @subdigital, apologies for pulling the rug out from under these changes!  I spent the last couple of weeks making some architectural changes to Tophat.
HTTP downloads are now handled by HTTPArtifactProvider in TophatCoreExtension, which would be the appropriate place to handle this and throw a LocalizedError.  Should be able to move the logic over without too much trouble.

This PR Builds on top of #59 and re-applies the download error behavior for the new extension system.
To do this I had to move the error enum up a level to TophatFoundation so that extensions could use it and the host app could reference it so the error information could be unwrapped to show the alert.
I also got some weird linker errors about using Logger so I stuck with print() for now. Let me know if this works!

The new alert looks like this


Problems in running the quickstart

Hi, thanks for your great work! I am trying to follow the three steps shown in https://textgrad.com/index.html#application but failed in the second step:

Did I miss anything? Thanks a lot.

Hello! you need to set an engine as global in this context.
import textgrad as tg

tg.set_backward_engine("gpt-4o", override=True)

Could you point me to where the example is? We might need to update that!

Sure, I will have a try. The original design does not include requests for such steps:
import textgrad as tg
# Step 1: Get an initial response from an LLM
model = tg.BlackboxLLM("gpt-4o")
punchline = model(tg.Variable("write a punchline for my github package about optimizing compound AI systems", role_description="prompt", requires_grad=False))
punchline.set_role_description("a concise punchline that must hook everyone")

The example can be found in : https://textgrad.readthedocs.io/en/latest/index.html


Someone: Watch tinyurl.com

Someone requests the watch of the watch_keyword tinyurl\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

tinyurl\.com has been seen in 60 true positives, 76 false positives, and 10 NAAs.

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'too many fp in metasmoke'


重启渲染引擎有异常报错

`<?php
namespace App\HttpController;
use EasySwoole\Http\AbstractInterface\Controller;
use EasySwoole\Template\Render;
class Index extends Controller
{
function index()
{
    $this->response()->write(Render::getInstance()->render('index.tpl',[
        'user'=>'easyswoole',
        'time'=>time()
    ]));
}

function reload(){
    Render::getInstance()->restartWorker();
    $this->response()->write(1);
}

}`
访问index/reload 报以下异常
[2020-06-06 16:27:01 $4478.0]	WARNING	swManager_check_exit_status: worker#7[pid=4490] abnormal exit, status=0, signal=11
A bug occurred in Swoole-v4.4.16, please report it.
The Swoole developers probably don't know about it,
and unless you report it, chances are it won't be fixed.
You can read How to report a bug doc before submitting any bug reports:

https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md
Please do not send bug reports in the mailing list or personal letters.
The issue page is also suitable to submit feature requests.

[2020-06-06 16:27:01][debug][error]:[Argument 1 passed to EasySwoole\Http\Response::write() must be of the type string, null given, called in /www/wwwroot/cxy.qcq.cc/App/HttpController/Index/Base.php on line 201 at file:/www/wwwroot/cxy.qcq.cc/vendor/easyswoole/http/src/Response.php line:76]
[2020-06-06 16:27:01 $4478.0]	WARNING	swManager_check_exit_status: worker#6[pid=4489] abnormal exit, status=0, signal=11
A bug occurred in Swoole-v4.4.16, please report it.
The Swoole developers probably don't know about it,
and unless you report it, chances are it won't be fixed.
You can read How to report a bug doc before submitting any bug reports:

https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md
Please do not send bug reports in the mailing list or personal letters.
The issue page is also suitable to submit feature requests.

[2020-06-06 16:27:01 @6330.0]	WARNING	swSignalfd_setup: signalfd has been created
[2020-06-06 16:27:01 @6331.0]	WARNING	swSignalfd_setup: signalfd has been created

解决了吗这个问题

按目前代码来看 worker进程被kill 应该是无法响应的

解决了吗这个问题

https://github.com/easy-swoole/easyswoole/issues/342#issuecomment-988526423

您的邮件我已经收到！


#6: create skeleton of the library

@rultor merge

@rultor merge

@proshin-roman OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@proshin-roman Done! FYI, the full log is here (took me 3min)


build(electron): exclude node modules from production app

Description:
Since flattening the repo in #1895 the linux builds have been broken. On investigation I've discovered that it's attempting to package a bunch of node_modules that it should not be.
By default, electron-builder packages app production dependencies and ignores devDependencies. Since we bundle all of our code with webpack, technically everything is a development dependency so one solution would be to move all dependencies to devDependencies. However, I think it's cleaner for us to just exclude node_modules and to keep the dependencies section referencing only the dependencies that we actually use in the app.
Additionally, this adjusts how we package the about window code and resolves an issue where it was not correctly displaying the logo when running yarn start
Motivation and Context:
Fix build issues.
How Has This Been Tested?
yarn dev, yarn start, yarn package
Types of changes:
Build gfixes
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 19.453% when pulling 2a05029f37a8b8b4b81083d62ee51ace9b74b2fb on mrfelton:fix/packaging into 4741fb464f3a96eeb4ffed1944e9f0152fad7706 on LN-Zap:master.

Coverage remained the same at 19.453% when pulling 2a05029f37a8b8b4b81083d62ee51ace9b74b2fb on mrfelton:fix/packaging into 4741fb464f3a96eeb4ffed1944e9f0152fad7706 on LN-Zap:master.


Move Documentation from Word to github

Hi,
I was just looking for some documentation for the tool and thought Brent Ozars blog might be the best place. However, there is actually Documentation hidden in the src folder https://github.com/ErikEJ/SqlQueryStress/blob/master/src/SQLQueryStress/SQLQueryStress_Documentation.doc .
I would suggest to remove the file and move the content to the github wiki. For an example see https://github.com/d3/d3/wiki. However, I do not know what permission one needs to edit the SqlQueryStress wiki.
regards
Felix

I have done a proof of concept of the idea at https://github.com/fmms/SqlQueryStress/wiki.
However, as wikis seem not to support pull requests this page might be better handled in a subfolder of the project.
regards

I Think you Can do PRs to wiki, so I will add it there

http://mikehadlow.blogspot.dk/2014/03/how-to-add-images-to-github-wiki.html

That is exactly the post i followed to add the images to the wiki. PRs are not possible for the wiki repository, cf. http://stackoverflow.com/questions/10642928/how-to-pull-request-a-wiki-page-on-github.

I think your suggestion of creating and docs folder with an .md file is better then. Can you do a PR of that?  (docs folder with readme.md file and images)

I have added a wiki page, thanks very much for the contribution


Fix compatibility with Flutter 3.10 and 3.13

This PR downgrade stack_trace to 1.11.0 to make package compatible with Flutter 3.10 and Flutter 3.13
Closes #41

@kentcb can you take a look at this?

@kentcb can you review this PR please?

@all-contributors Please add @robsonsilv4 for code

Thanks for your patience, and thanks for the PR @robsonsilv4. Version 4.0.1 is now available on pub.


[BUG] strict_date_optional_time date format does not handle negative epoch millis with leading zeros correctly

Describe the bug
When trying to index negative epoch millis timestamps with leading zeros the strict_date_optional_time will incorrectly try to parse these as Years.
These negative epoch millis timestamps are able to be parsed just fine by the epoch_millis format, however when the default format strict_date_optional_time||epoch_millis is used the parsers are evaluated left to right and strict_date_optional_time throws an exception in this case. This is not how the || operator is supposed to behave for formats as if one parser is not able to parse the value then it should try with the others.
Related component
Indexing
To Reproduce
Reproduced this on a local OpenSearch cluster in a few different scenarios:

The default format strict_date_optional_time||epoch_millis cannot parse timestamp -9392400000. The "verbose" epoch millis for this timestamp should be -0009392400000, however OpenSearch also does not allow ingesting numerics with leading zeros.

dengjay@88665a3f24d4 OpenSearch % curl -XPUT "http://localhost:9200/testindex" -H 'Content-Type: application/json' -d'
{
  "mappings" : {
    "properties" :  {
      "release_date" : {
        "type" : "date",
        "format" : "strict_date_optional_time||epoch_millis"
      }
    }
  }
}'
{"acknowledged":true,"shards_acknowledged":true,"index":"testindex"}%                                                                                dengjay@88665a3f24d4 OpenSearch % curl -X PUT "localhost:9200/testindex/_doc/14?pretty" -H 'Content-Type: application/json' -d'
{ "release_date": -9392400000 }
'
{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "failed to parse field [release_date] of type [date] in document with id '14'. Preview of field's value: '-9392400000'"
      }
    ],
    "type" : "mapper_parsing_exception",
    "reason" : "failed to parse field [release_date] of type [date] in document with id '14'. Preview of field's value: '-9392400000'",
    "caused_by" : {
      "type" : "date_time_exception",
      "reason" : "Invalid value for Year (valid values -999999999 - 999999999): -9392400000"
    }
  },
  "status" : 400
}

epoch_millis is able to parse timestamp -9392400000 just fine

dengjay@88665a3f24d4 OpenSearch % curl -XPUT "http://localhost:9200/testindex2" -H 'Content-Type: application/json' -d'
{
  "mappings" : {
    "properties" :  {
      "release_date" : {
        "type" : "date",
        "format" : "epoch_millis"
      }
    }
  }
}'
{"acknowledged":true,"shards_acknowledged":true,"index":"testindex2"}%                                                                                dengjay@88665a3f24d4 OpenSearch % curl -X PUT "localhost:9200/testindex2/_doc/14?pretty" -H 'Content-Type: application/json' -d'
{ "release_date": -9392400000 }
'
{
  "_index" : "testindex2",
  "_id" : "14",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 2,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 0,
  "_primary_term" : 1
}

Parsers seem to parse left to right, so using mapping epoch_millis||strict_date_optional_time works just fine as well:

dengjay@88665a3f24d4 OpenSearch % curl -XPUT "http://localhost:9200/testindex33" -H 'Content-Type: application/json' -d'
{
  "mappings" : {
    "properties" :  {
      "release_date" : {
        "type" : "date",
        "format" : "epoch_millis||strict_date_optional_time"
      }
    }
  }
}'
{"acknowledged":true,"shards_acknowledged":true,"index":"testindex33"}%                                                                                dengjay@88665a3f24d4 OpenSearch % curl -X PUT "localhost:9200/testindex33/_doc/14?pretty" -H 'Content-Type: application/json' -d'
{ "release_date": -9392400000 }
'
{
  "_index" : "testindex33",
  "_id" : "14",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 2,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 0,
  "_primary_term" : 1
}

Whenever one parser is not able to parse a value, other parsers should be used. This is how it works for positive epoch timestamps. Timestamp<PHONE_NUMBER>00 is not able to be parsed by strict_date_optional_time, however unlike with negative epoch millis it is able to be parsed by strict_date_optional_time||epoch_millis

dengjay@88665a3f24d4 OpenSearch % curl -XPUT "http://localhost:9200/testindex4" -H 'Content-Type: application/json' -d'
{
  "mappings" : {
    "properties" :  {
      "release_date" : {
        "type" : "date",
        "format" : "strict_date_optional_time"
      }
    }
  }
}'
{"acknowledged":true,"shards_acknowledged":true,"index":"testindex4"}%                                                                                dengjay@88665a3f24d4 OpenSearch % curl -X PUT "localhost:9200/testindex4/_doc/14?pretty" -H 'Content-Type: application/json' -d'
{ "release_date":<PHONE_NUMBER>00 }
'
{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "failed to parse field [release_date] of type [date] in document with id '14'. Preview of field's value: '999999999000'"
      }
    ],
    "type" : "mapper_parsing_exception",
    "reason" : "failed to parse field [release_date] of type [date] in document with id '14'. Preview of field's value: '999999999000'",
    "caused_by" : {
      "type" : "illegal_argument_exception",
      "reason" : "failed to parse date field [999999999000] with format [strict_date_optional_time]",
      "caused_by" : {
        "type" : "date_time_parse_exception",
        "reason" : "Text '999999999000' could not be parsed at index 0"
      }
    }
  },
  "status" : 400
}

dengjay@88665a3f24d4 OpenSearch % curl -XPUT "http://localhost:9200/testindex5" -H 'Content-Type: application/json' -d'
{
  "mappings" : {
    "properties" :  {
      "release_date" : {
        "type" : "date",
        "format" : "strict_date_optional_time||epoch_millis"
      }
    }
  }
}'
{"acknowledged":true,"shards_acknowledged":true,"index":"testindex5"}%                                                                                dengjay@88665a3f24d4 OpenSearch % curl -X PUT "localhost:9200/testindex5/_doc/14?pretty" -H 'Content-Type: application/json' -d'
{ "release_date":<PHONE_NUMBER>00 }
'
{
  "_index" : "testindex5",
  "_id" : "14",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 2,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 0,
  "_primary_term" : 1
}

Will try to add a UT/IT demonstrating these scenarios in the near future.
Expected behavior
Date time parsers should all be evaluated on a given timestamp for negative epoch times. Ingesting timestamp -9392400000 should not fail.
Additional Details
Discovered on OpenSearch 2.5, reproducible on main (3.x) as well.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: Reprocued on OS 2.5 and 3.
Version [e.g. 22]

Additional context
Add any other context about the problem here.

[Triage - attendees 1 2 3 4 5 6]
@jed326 Thanks for filing and providing all the details on the reproduction. Looking forward to seeing a fix here.

Hello @jed326 @andrross Please find the below observations.
OpenSearch git:(srikanth-bug-fix-11180) curl -X PUT "localhost:9200/my-index-000009?pretty" -H 'Content-Type: application/json' -d' {   "mappings": {     "properties": {       "date": {         "type":   "date",         "format": "strict_date_optional_time||epoch_millis"       }     }   } } ' {   "acknowledged" : true,   "shards_acknowledged" : true,   "index" : "my-index-000009" } “” ➜  OpenSearch git:(srikanth-bug-fix-11180) curl -X PUT "localhost:9200/my-index-000009/_doc/example?refresh&pretty" -H 'Content-Type: application/json' -d' { "date": -292275055 } ' {   "error" : {     "root_cause" : [       {         "type" : "mapper_parsing_exception",         "reason" : "failed to parse field [date] of type [date] in document with id 'example'. Preview of field's value: '-292275055'"       }     ],     "type" : "mapper_parsing_exception",     "reason" : "failed to parse field [date] of type [date] in document with id 'example'. Preview of field's value: '-292275055'",     "caused_by" : {       "type" : "arithmetic_exception",       "reason" : "long overflow"     }   },   "status" : 400 } “” ➜  OpenSearch git:(srikanth-bug-fix-11180) curl -X PUT "localhost:9200/my-index-000009/_doc/example?refresh&pretty" -H 'Content-Type: application/json' -d' { "date": -292275054 } ' {   "_index" : "my-index-000009",   "_id" : "example",   "_version" : 1,   "result" : "created",   "forced_refresh" : true,   "_shards" : {     "total" : 2,     "successful" : 1,     "failed" : 0   },   "_seq_no" : 0,   "_primary_term" : 1 }
For below mentioned years is the max it is working and if I go even one second back, it is throwing long overflow exception.
GMT: Tuesday, September 27, 1960 4:29:06 AM
My time zone: Monday, September 26, 1960 11:29:06 PM [GMT-05:00]
Relative: 64 years ago


Icon disappear when located plugin in the 'topright' or 'bottomright'.

Hi Igor,
Thanks for your simple yet useful plugin.
I can use your plugin with very easy steps. But when I located the plugin in 'topright' or 'bottomright', the printer icon is disappear when I hover the mouse over it.
Need your guidance please.
Thanks.
note: L.browserPrint({position: 'topright'}).addTo(map);

Hi there,
You are right, internal problems with styling. Now it should work as expected. Please check latest v0.3.7.
Regards,
Igor

Thanks for your super quick response.
Now it's worked perfectly.


Plugin with id 'kotlin-android' not found

Issue Description
FAILURE: Build failed with an exception.

Where:
Build file 'node_modules/react-native-camera-kit/android/build.gradle' line: 2

What went wrong:
A problem occurred evaluating project ':react-native-camera-kit'.

Plugin with id 'kotlin-android' not found.

Steps to Reproduce / Code Snippets / Screenshots
Updated library version from
"react-native-camera-kit": "^8.0.4",
to
"react-native-camera-kit": "^11.1.0",

Environment

React Native Navigation version: 4.0.10
React Native version: 0.62.2
Platform(s) (iOS, Android, or both?): Android
Device info (Simulator/Device? OS version? Debug/Release?): All

You need to add Kotlin to your project.
https://github.com/teslamotors/react-native-camera-kit/blob/master/docs/kotlin.md

I am facing this error

You need to add Kotlin to your project. https://github.com/teslamotors/react-native-camera-kit/blob/master/docs/kotlin.md

this link is empty

It's showing on the package front page.

https://github.com/teslamotors/react-native-camera-kit/blob/master/docs/kotlin.md


Always use synchronous XHR, when using polyfill

For browsers that don't support navigator.sendBeacon,
which means they are really old,
I'd rather always use synchronous XHR.
Also, in 2020, I am using the page visibility api instead of unload/beforeunload events

@miguelmota I'm not in favor of merging this.
The point of sendBeacon, apart from ensuring it is sent even on unload, is to be deprioritized compared to regular ajax (browser sends it on CPU idle time and when no other requests are being sent).
Using asynchronous XHR in all cases apart from on unload makes polyfill as close as possible in behavior to sendBeacon.
@vladimyr, thoughts?

Maybe this package should export an init function where you can pass in a little config. Could
init({
  syncXHR: true_false,
  // or:
  syncXHR: (eventName) => {
    if (eventName === 'unload' || eventName === 'beforeunload') {
      return true;
    } else {
      return false;
    }
  } // end callback
});

It's fine to take a stance of "this library supports a fast web" because most developers (like me) are just trying to get a feature done and not have to go back and fix bugs with it later. Maybe it'd be good to support an option like this. My stance is that if a browser doesn't support sendBeacon, I will just do sync XHR to try and ensure the event comes through.

Agree that keeping the polyfill behavior as close as to the spec is preferred, however, I wouldn't be opposed to the optional configuration method suggestion ie. sendBeacon.config({syncXHR: true})


drivers: clock_control: add support for PLL3 on STM32 H7

Add support for enabling and configuring PLL3 on STM32 H7 series. PLL3
is used as a clock source by certain peripherals, e.g. LTDC.
Signed-off-by: Gerard Marull-Paretas<EMAIL_ADDRESS>

@fzawadiak would you mind having a look and approve if that's fine with you ?

@fzawadiak would you mind having a look and approve if that's fine with you ?


Feature/update requirements with hashes

What? and Why?

What does this pull request change/fix? Why was it necessary?

Update requirements to include hashes the benefit of this is to reduce risk of accidental and malicious changes.
Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   28.32%   28.32%
=======================================
  Files           4        4
  Lines         519      519
=======================================
  Hits          147      147
  Misses        372      372

Continue to review full report at Codecov.

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

 Turn on PIP hashed requirements.txt (3)


🎶Song Request

HumanAcc
Music-Informations
Title: You Leave Me Away (feat. AVANNA)
Genre: Future Bounce | Future House | Emotional Future Bounce
Tag: Emotional Future Bounce
Released: 2022-09-25
Producer: WerewolfwolfyXD
Other-Authors: [AVANNA, CHROUS:OLIVER (Owned by VocaloidBanks Generation)]
Co-Producer: WerecatcathayXD
Other-SemiGeneration
No-Thumbnail-Generation
No-Profile-Generation
No-Release-Generation

HumanAcc
RequestState:
Hooray!
Your song request was accepted!
RequestInformation:
Record ID: 0003
Copyrights: WerewolfwolfyXD, WerecatcathayXD, Opensource-Lightning Bolt Records
Message:
感谢您的投稿！您的投稿已被受理
IssueInfo
Date&Time: 2024/9/6 1:12
IssueID: 3


More tweaks to play nicer on Windows

Rename file to avoid build error about Logo.png being wrong dimensions (that's a special image name for Windows apps and needs to be 150x150, but it's 1200x1200); tweak layout a tiny bit on Windows.

Approved. Merging.


Add CLI cmd tls invalide-pem-cache

Proposed Changes
Adds a cli command vmq-admin tls invalidate-pem-cache, which invalidates PEM certificates. Supports immediate replace of TLS certificates without listener restart.
Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes issue #XXXX)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, styles...)
[ ] DevOps (Build scripts, pipelines...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

[ ] I have read the CODE_OF_CONDUCT.md document
[ ] All tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if needed)
[ ] Any dependent changes have been merged and published in related repositories
[ ] I have updated changelog (At the bottom of the release version)
[ ] I have squashed all my commits into one before merging

Further Comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

This is great!
Procedure will be:

Replace the server cert/key files (with files named exactly the same). Keep around the old files, in case of issues.
Run vmq-admin tls clear-pem-cache on the node

We could add an info command to check when the cert was last cached. But that's optional.
@mths1 have you already done some manual testing to ensure it's working for an SSL listener?

@ioolkos : I tested it and it worked "out of the box". The clear-pem-cache is more of a convenience function, as after some time (some sources say 2 minutes, in my case it was longer) the new certificates are picked up by erlang anyway. All active connections remained active, and new connections received the new certificate.


Add support for P4estMesh

This is basically done, but the P4estMesh needs to be in a Trixi release first, so that we can update the required version here.


Query keeps running after stopped successfully

Expected
When a query is stopped, the next poll will receive an answer including status: "CANCELED".
Actual
When I stop a query successfully, (DELETE with status 204), the next poll for that query's status still returns a query object with status RUNNING.
Steps to reproduce

Start a query that takes a long time
Stop the query, before it's finished
See the frontend continue polling the results in the network tab, because the status is still RUNNING

This isn't working yet, right?

Ist jetzt implementiert :D


agc account activate fail to create VPC in China region

Try running agc account activate without specifying custom --vpc results the following error:
2022-05-22T22:49:10-06:00 ✘  Agc-Core | 10:47:18 PM | CREATE_FAILED        | AWS::EC2::VPCEndpoint                 | Vpc/AgcEcrDkrEndpoint (VpcAgcEcrDkrEndpointXXXXXXXX) The Vpc Endpoint Service 'com.amazonaws.cn-northwest-1.ecr.dkr' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidServiceName; Request ID: xxxxxxxx; Proxy: null)

I guess this is related to the version of CDK bundled with amazon-genomics-cli. See https://github.com/aws/aws-cdk/issues/9864
AGC Version: 1.4.0

One other error which is related to agc context deploy (after creating and using a custom cromwell ECR mirror):
Partition "aws" is not valid for resource "arn:aws:ecr:cn-northwest-1:<account_id>:repository/aws/cromwell-mirror".
(Service: AmazonIdentityManagement; Status Code: 400; Error Code: MalformedPolicyDocument; Request ID: xxx; Proxy: null)

Hi @Marlin-Na ,
Amazon Genomics CLI is not officially supported in AWS China regions. It is something we are evaluating for a future release based on customer feedback.
Per your individual errors:
When agc creates a VPC on its own (the default), it will also create a few VPC endpoints to help reduce costs by reducing traffic through the NAT Gateway - e.g. one for S3 and another for DynamoDB. As the issue you've identified is upstream in the CDK we'd need to wait for it to be resolved there before it can be fixed in agc.
Can you describe how you are creating a custom Cromwell mirror? It looks like the partition is incorrect for pulling a container from an ECR registry in cn-northwest-1.

Hi @Marlin-Na, you may also need to ensure the repository name is aws/cromwell-mirror, however if that is what you are using then it could be that CDK is not looking up the container as expected.