Remove dependencies that were added by mistake during conflict resolution

Details

While resolving conflicts in: Remove MoneyTemporaryForRefactorRequestConfirmationList PR, I reintroduced dependencies that were previously removed here PR.

This issue is now again reproducible for tags. #comment

We will update the dependencies accordingly in this new PR.
Fixed Issues

$ N/A
PROPOSAL: N/A
Tests

Preconditions: Should have a collect policy with only one tag and one category and both should be required.

Go to the global FAB > Submit an Expense > Enter any amount > Proceed.
Select the collect policy that matches the preconditions.
Go to Category selection page > select a category and
Verify there is no noticeable delay before the selected category shows up.
Return to Category selection page > deselect the category and
Verify there is no noticeable delay before the selected category disappears.
Go to Tag selection page > select a tag and
Verify there is no noticeable delay before the selected tag shows up.
Return to Tag selection page > deselect the tag and
Verify there is no noticeable delay before the selected tag disappears.
Create the request and check that everything works as before.
Open the Collect policy chat report that matches the preconditions.> Click on the plus icon inside the compose box >Submit an Expense > Enter any amount > Proceed.
Go to Category selection page > select a category and
Verify there is no noticeable delay before the selected category shows up.
Return to Category selection page > deselect the category and
Verify there is no noticeable delay before the selected category disappears.
Go to Tag selection page > select a tag and
Verify there is no noticeable delay before the selected tag shows up.
Return to Tag selection page > deselect the tag and
Verify there is no noticeable delay before the selected tag disappears.

Note: There should be consistent behavior when selecting/deselecting tags and categories.

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

Offline tests

Same as Tests
QA Steps

Same as Tests
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/95647348/de00fe5e-ddd4-4731-921e-40ffd141b856

Android: mWeb Chrome

https://github.com/Expensify/App/assets/95647348/1da61fe9-4716-4b80-bce9-1d6b61fb714b

iOS: Native

https://github.com/Expensify/App/assets/95647348/21c2b237-18d5-4f48-aa6c-cd4977d4e29e

iOS: mWeb Safari

https://github.com/Expensify/App/assets/95647348/3d8ab9e7-cc44-456a-a571-98eedd9d455a

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/95647348/ca5b41f6-3a7b-4309-b97f-757856dd7f28

MacOS: Desktop

https://github.com/Expensify/App/assets/95647348/8dfb02b6-e59d-4307-a571-e3f806a751df

Krishna2323 identified an issue:
I think that while you were resolving conflicts, you mistakenly added back the dependencies that were removed https://github.com/Expensify/App/pull/40176#issuecomment-2079801206
I believe the fix is simple, can you check it please?
Thank you and sorry for the inconvenience.
cc: @eh2077, @tgolen, @Krishna2323, @sobitneupane

Sorry @bondydaa, I didn't mean to assign you

Reviewer Checklist

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

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

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

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

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

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

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

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

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

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

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

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

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If 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:

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

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

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

🚀 Deployed to staging by https://github.com/bondydaa in version: 1.4.69-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Beamanator in version: 1.4.69-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Are the fonts needed if the client has them

Vs code and host system would have the fonts, not the devcontainer.  is that right?

No, but that isn't really needed with the p10k configure configuration I have installed


Use git hash-object for blob id if available

This commit updates file blob_id generation by first shelling out to git hash-object. If git or the file is unavailable, we'll fallback to our sha1
computation.
@codeclimate/review :mag_right:

LGTM


rpc api: add missing fields to listvaults response

[x] address
[x] derivation_index
[x] updated_at

check doc/api/listvaults

Arf blockheight is missing too!


Feature: ASB-1987 - Add active filters to relevant representations page

https://pins-ds.atlassian.net/browse/ASB-1987?atlOrigin=eyJpIjoiMWJjMGU5ODQ4M2FkNDI5Njk2MDg5YmRkZjgyOTljYWQiLCJwIjoiaiJ9
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[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 update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[x] I have made corresponding changes to the documentation
[x] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Test common config sections pass through config validation

Closes #2128

Codecov Report

Merging #2135 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2135      +/-   ##
============================================
+ Coverage      80.5%   80.53%   +0.02%
  Complexity     2015     2015
============================================
  Files           336      336
  Lines          5802     5809       +7
  Branches       1064     1064
============================================
+ Hits           4671     4678       +7
  Misses          564      564
  Partials        567      567

Impacted Files
Coverage Δ
Complexity Δ

...ch/detekt/api/internal/ValidatableConfiguration.kt
88.57% <100%> (+2.85%)
0 <0> (ø)
:arrow_down:

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 0e8c7e7...72c1d8d. Read the comment docs.


Wrong page

Hi,
just to inform you that when clicked on Always On Availability Group --> Concept --> Interoperability -->Failover Cluster Instance, it return wrong page "Analysis Services with Always On Availability Groups".
Best Regards,
Bojan Jekic

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

ID: 1b51d16a-4c42-977f-665e-b3211510f136
Version Independent ID: 1962a422-949b-c2b3-3232-26718184605e
Content: Analysis Services with availability groups - SQL Server Always On
Content Source: docs/database-engine/availability-groups/windows/analysis-services-with-always-on-availability-groups.md
Product: sql
Technology: availability-groups
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@jekic -- thank you for bringing this to our attention.  I am updating the table of contents.

@MashaMSFT -- Masha, I'm not sure whether the toc's name or href should be changed for this entry:
        - name: Failover cluster instances
          href: database-engine/availability-groups/windows/analysis-services-with-always-on-availability-groups.md

It seems to me the name should be updated to "Analysis Services with Always On Availability Groups".

Hi @jekic , thanks so much for contacting Microsoft and helping improve our docs! My apologies for the delay as we've been working through a large backlog of Issues. I've processed a change to update this that should be live later this week. I'll go ahead and close out this Git Issue but please feel free to comment should you need anything further.
Thanks again and I hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#please-close


chore(staking): fix LW-9618 storybook

Checklist

[ ] JIRA - LW-9618
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
yarn && yarn dev from packages/staking, storybook should run and be accessible
Screenshots
Attach screenshots here if implementation involves some UI changes

@mchappell not sure if this is related but the first story of the staking package seems to be broken/empty?

coverage: 52.338%. remained the same
when pulling 26e429f5e6549661f4285a19d3de899d69f57bf0 on fix/lw-9618
into ec4d22498fcff13c288718f0378de8eab8db1d06 on main.

@mchappell not sure if this is related but the first story of the staking package seems to be broken/empty?

It's a similar, but unrelated issue, node_modules/@cardano-sdk/wallet/dist/cjs/index.js?v=2d576b5f' does not provide an export named 'PersonalWallet


Feature to unregister all commands that conflict

Description
It would be nice to have something to unregister all the commands that conflict, or even unregister a specific command. I think this will be a good addition because CommandAPI commands tend to have lower priority and the other plugins which aren't as important (such as Essentials and WorldEdit) tend to overwrite them. It's definitely very annoying to type minecraft: every time this happens.
Expected code
No response
Extra details
I was making a plugin with /info and then WorldEdit decided to take priority. It wasn't a good experience.

My bad I didn't see a similar feature was already implemented.

For converted commands (e.g. using the CommandAPI plugin command converter for Essentials/WorldEdit), the CommandAPI still has to be able to access the underlying command in order to run it. If we unregister the underlying command, then the CommandAPI won't be able to run it!
This seems like a very nuclear option. What would be ideal is to try and get namespaces working, so the commands are registered via your plugin namespace instead of minecraft:, and command resolving comes down to however Bukkit decides to handle that

Mmmm yeah I would love to see it not in just generic minecraft: namespace.


Limit slackbot responce to certain channel

I know how to use "listen_to" when anyone mentions certain words in a comment. Is it possible to limit this to certain channels?

I have not started using this bot yet so there might be a better and/or cleaner way but I think you can check the channel name in the callback like this:
message.channel._body['name']

I use a decorator like this:
def in_allowed_channel(func):
    def allowed_channel(message, *args, **kwargs):
        if message.body['channel'] not in ALLOWED_CHANNELS:
            message.reply('Please ask that in <#C12345|#botchannel>'
            return
        return func(message, *args, **kwargs)

    # Copy the docstring to the decorated func so help works
    allowed_channel.__doc__ = func.__doc__
    return allowed_channel```


Prerender does not work properly after the optional parameter path.

Describe the bug
I started writing code with the following structure.

And when I did npm run build I got the following error:
Error: The following routes were marked as prerenderable, but were not prerendered because they were not found while crawling your app:
  - /[[lang=locale]]/(app),  - /[[lang=locale]]/(app)/about,  - /[[lang=locale]]/(auth)/account-recovery,  - /[[lang=locale]]/(app)/contact,  - /[[lang=locale]]/(app)/dashboard,  - /[[lang=locale]]/(auth)/login

I started svelte for the first time yesterday so I have no idea what the problem is.
I can't use prerender with optional parameters ?
Should I write everything like below?
prerender: {
    concurrency: 1,
    crawl: true,
    entries: ['*', '/ko/', '/ko/contact', '/en/', '/contact', '/about', '/dashboard']
},

Reproduction
routes/+layout.ts
export const prerender = true;
export const ssr = false;

svelte.config.js
import preprocess from "svelte-preprocess";
import adapter from '@sveltejs/adapter-static';
import { vitePreprocess } from "@sveltejs/kit/vite";
import path from "path";

/** @type {import('@sveltejs/kit').Config} */
const config = {
    preprocess: [
        vitePreprocess(),
        preprocess({
            sass: true,
            postcss: true,
        }),
    ],

    kit: {
        adapter: adapter({
            fallback: 'index.html' // may differ from host to host
        }),
        prerender: {
            concurrency: 1,
            crawl: true,
        },
        alias: {
            '$src': path.resolve('./src'),
            '$components': path.resolve('./src/components'),
        },
    },
};

export default config;

Logs
No response
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 14.49 GB / 31.87 GB
  Binaries:
    Node: 16.19.1 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 112.0.5615.140
    Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.35)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.0.1
    @sveltejs/adapter-static: ^2.0.2 => 2.0.2
    @sveltejs/kit: ^1.5.0 => 1.16.3
    svelte: ^3.54.0 => 3.59.1
    vite: ^4.3.0 => 4.3.5

Severity
annoyance
Additional Information
No response

Please provide a proper reproduction for the issue as instructed by the issue template:

A link to a repository, or a fork of https://node.new/sveltekit, that reproduces the issue. Reproductions must be short, self-contained and correct and must not contain files or code that aren't relevant to the issue — please do NOT just paste a link to your project. Explaining how to reproduce is generally not enough. It pushes the burden of creating a reproduction project onto a small set of volunteer maintainers and isn't scalable. If no reproduction is provided, the issue will be closed.

If you explain it with an actual url, the structure becomes as follows.
Each page has links connecting them to each other.
/        =>              /[[lang=locale]]/(app)/+page.svelte
/en/     =>              /[[lang=locale]]/(app)/+page.svelte

If the first page is /en/
Include the following link on a later page.
/en/about
/en/dashboard
/en/contact

If the first page is /
Include the following link on a later page.
/about
/dashboard
/contact

For example, each page has a link like this:

/
/about
/login
/dashboard
/contact
/account-recovery

The entries value in the config file had no effect.

Once again, explaining arbitrary parts of your file structure through text is not enough. Upload a minimal reproduction in the form of a git repo otherwise I'm going to assume this works as intended based on the following example.
https://stackblitz.com/edit/sveltejs-kit-template-default-cmrtok?file=src%2Froutes%2F[[lang]]%2F(app)%2F%2Bpage.svelte&terminal=build

https://github.com/yahao87/svelte-ssg-build-fail-example
I just created a new project to reproduce the error situation.
Can you check the github link by putting it there?

You have SSR disabled so there won't be any links to crawl. So you can't use the crawler to find the links. If you do actually want to prerender the whole thing then yes, you need to list them all out.
The bigger issue though is that the * entry bails on a route if it sees a [ in the route id. The question would be whether it should pick up /[[foo]]/bar as /bar instead of just bailing but then that might be a breaking change cause it starts trying to render routes that weren't previously called and builds start failing on HTTP errors.

@gtm-nayan Thanks for pointing out that ssr must be enabled to crawl.
Actually, I couldn't understand the second sentence you wrote because I'm not good at English.
However, I solved it by referring to what you said.
add file routes\[[lang=locale]]/+layout.ts
export const trailingSlash = "always";

And I succeeded in building the desired form.

thank you!

Wouldn't it be nice to see in the document below that even if you want to use only prerender for the purpose of creating static file like me, crawl does not work if ssr is inactive?
https://kit.svelte.dev/docs/configuration#prerender

We do already explain this: https://kit.svelte.dev/docs/page-options#prerender-prerender-and-ssr
Going to close this since there's not actually a bug -- glad you got your issue figured out! 😁


improper mapping when srv_enabled

i am testing dns drv_enabled with ats v8.0.3,  bellow is my config:
map http://cftest.example.com/ http://cftest.example.com.origin.com/
map http://<IP_ADDRESS>/        http://hahaha.example.com.origin.com/
while cftest.example.com.origin.com has dns srv record,
hahaha.example.com.origin.com only has dns a record,
and <IP_ADDRESS> is an ip address which cftest.example.com.origin.com resolved to...
with the above setting, dns srv only works about 10 seconds, after that, ats return 502,
when remove the ip address mapping , dns srv works properly.

This might've been fixed with https://github.com/apache/trafficserver/pull/5989

I got it. i 'll try v8.0.6 later.

@randall
mapping issue have been fixed,
but there is a new problem,
when there were two origins with weight set to 5 and 1 respectively,
the two origins will be took as 6 (5+1) seperated servers,
when take down server into consideration, they should be take as 2 servers...


Revert "apply bettertransformer by default for causallm"

Reverts huggingface/optimum-intel#605

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@echarlaix, please revert because it breaks the expected form of stateful models. It requires more thorough validation on our side.


[ca support] patch node with hived resource

Coverage remained the same at 34.607% when pulling 8f932f3374c75df922fe69c4a8a3d6d8635bedef on yuye/ca-resource-support into 0988d254c6ee5b8d475ceaedbaf6f12c0e63c13f on master.


@iot-app-kit/source-iotsitewise tries to aggregate string data

Describe the bug
When requesting aggregated data and panning an error is thrown to the console and datapoints are missing.
To Reproduce
Steps to reproduce the behavior:

Go to testing ground and add a line chart with a query for a string property

            <iot-line-chart
              widgetId="line-chart"
              viewport={{ duration: '10m' }}
              queries={[
                this.query.timeSeriesData({
                  assets: [
                    {
                      assetId: DEMO_ASSET,
                      properties: [
                        {
                          propertyId: DEMO_STRING_PROPERTY,
                        },
                      ],
                    },
                    {
                      assetId: DEMO_ASSET,
                      properties: [
                        {
                          propertyId: DEMO_PROPERTY,
                        },
                      ],
                    },
                    {
                      assetId: DEMO_ASSET2,
                      properties: [
                        {
                          propertyId: DEMO_PROPERTY,
                        },
                      ],
                    },
                    {
                      assetId: DEMO_ASSET3,
                      properties: [
                        {
                          propertyId: DEMO_PROPERTY,
                        },
                      ],
                    },
                    {
                      assetId: DEMO_ASSET4,
                      properties: [
                        {
                          propertyId: DEMO_PROPERTY,
                        },
                      ],
                    },
                  ],
                }),
              ]}
            />

Zoom in on the line chart
Errors are thrown as shown in the recording and screenshots

Expected behavior
String data is should not be aggregated and always be raw.
Screenshots
https://user-images.githubusercontent.com/6397726/193126694-e36e5038-5b48-4374-bd87-77d6ef53d2b6.mov

I was actually also requesting one more string stream. Looks like we are trying to aggregate string stream.

String data can be aggregated (as count) but we don't currently have great support for string data in time-series charts. This is because [1] in most cases it doesn't make sense to display the string data (e.g. as a series on a line chart) and [2] we don't currently have support for specifying different aggregation types in source-iotsitewise.
I do agree that there is probably a better user experience when specifying asset properties that have data types which aren't supported by certain charts. Short term, this could take the form of better documentation and more descriptive error messages. Long term, we could add some form of asset type discovery and adjust behaviour accordingly (e.g. automatically select "COUNT" aggregation for string asset properties).


[Request]: App Request for JB bypass

App to request
SC Pakistan
App Store link
https://apps.apple.com/pk/app/sc-mobile-pakistan/id645859445
App version
3.0.0
Jailbreak
unc0ver 8.0.2
Bypass tried

[X] A-Bypass
[X] Liberty Lite (Beta)
[X] Hestia
[X] Shadow
[X] HideJB
[X] iHide
[X] KernBypass (iOS 12.0 - 14.2)
[X] vnodebypass
[ ] Disabling tweak injection with Choicy or libhooker-configurator

Which bypass worked?
No response
Checklist before submission

[X] The app is missing from the table, or bypasses are not working anymore.
[X] I have checked through all open issues and none matched my app.
[X] I have tried at least one bypass before submission.

will test soon and add to list


Update spacing value on button press

Spacing can remain un-updated if cursor is still active in spacing field when go button is pressed. Force update of all variables before executing process

can throw an undefined variable error if a value is entered but not updated before go is pressed


[RFC] DietCode: An Auto-Scheduler for Dynamic Tensor Programs

@comaniac @junrushao1994

As one of the co-authors, it glad to see this RFC finally out :)
cc @masahi @ZihengJiang @Laurawly @Hzfengsy @MasterJH5574 @jinhongyii please help review and share your thoughts. Thanks.

We are more than happy to collaborate on AutoTIR side to make good things happen :-)

hey guys, thanks for the RFC! would you guys be up for doing a short walkthrough of it at a Community Meeting?

@ArmageddonKnight we might present/demo DietCode and introduce this RFC in a community meeting. Maybe in 5/25 or 6/1?

@areusch @comaniac Sure. I would be happy to. I will be traveling on 6/1 so 5/25 looks good.

@ArmageddonKnight @comaniac ok--let me do some agenda shuffling (we now have 3 topics for that meeting) and hopefully we can accommodate your travel schedule here.

@junrushao1994 yep, we will post meeting notes here per the TVM Community Meeting guidelines.

@ArmageddonKnight just confirming, we have on the agenda to discuss tomorrow

@areusch BTW, may I ask whether there is anything I should prepare for the meeting? Alternatively, any particular thing that the community might be interested in? How much time am I given for the presentation?

We discussed this at the TVM Community Meeting this morning. Here are notes (thanks to mbs-octoml for taking these):

Most discussion was around whether the approach could help the related
problem of long training time and a large number of distinct kernels
for fully statically-shaped models. Eg resnet50 with its dozens of
static shape instances for conv2d.
It is useful to consider kernel compilation in two steps:

Start with the N instances of the same operator, with different
shapes.
After tuning those independently, may end up with M << N schedules.
However, each schedule is instantiated for the original static shape
so that no dimension variables are left behind at run time,
thus we are back at N implementations.

There's a significant perf impact to having only M kernel implementation
which retain their parameterization on dimension variables. However, TVM
could support not doing that inlining today.
DietCode could be used to reduce M. The learned decision tree would dispatch
from a fully shape polymorphic implementation to the specific schedule
implementation. But at this stage the focus is on dynamic shape workloads.

No changes to Relay are required. Though Relay's dynamic shape functions
support data-dependent output shapes, currently DietCode does not search
over output shape and assumes only input shapes need to be inspected. But
sounds like this could be addressed in future work.

@areusch @cgerum Thank you for your feedback. I have addressed your feedback. Please review it again.

@areusch It's good to merge from my side

@ArmageddonKnight
hello, i have a question looking forward to you reply.
Is it workable to use DietCode + vm compiler + vm runtime to implement graphlevel dynamic shape inference ?
do you have any suggestions?

It is workable. The VM can gather the workloads and pack them as a single dynamic-shape workload and forward it to DietCode. DietCode does the auto-scheduling and send the generated code back to the VM.

It is workable. The VM can gather the workloads and pack them as a single dynamic-shape workload and forward it to DietCode. DietCode does the auto-scheduling and send the generated code back to the VM.
Thank you very much for your prompt reply. :-D, b（￣▽￣）d


added an object diagram

Pull Request Test Coverage Report for Build 384

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.02%

Totals

Change from base Build 378:
0.0%

Covered Lines:
2212

Relevant Lines:
3252

💛  - Coveralls


Add missing refs for RowCopied

Fixes #505

LGTM

When do you currently plan to publish preview3 ?

Hi @ErikEJ
Our plan is to release Preview 3 sooner in 2-3 weeks, definitely in this month.

Perfect! I will postpone my blog post till then!


[BACKEND] Supply a sizePerThread array instead of a single element to get BlockedEncodingAttr

Should we get rid of the constructor that takes a scalar? I don't see how that's ever correct.

I think we don't ever have a constructor that takes a scalar, but unsigned might be implicitly converted to ArrayRef<unsigned>?

template<typename T > llvm::ArrayRef< T >::ArrayRef	(	const T & 	OneElt	)


[Feature] Should we also set PublishNotReadyAddresses if the service is not headless?

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
In the PR https://github.com/ray-project/kuberay/pull/2117, we found a Ray worker may have a serious delay in connecting to the Head through its headless service with the default PublishNotReadyAddresses=false. So we set PublishNotReadyAddresses=true for headless services in the PR.
This issue is meant to track the following questions:

Determining the source of the delay. Why a RayCluster with one worker node with a default headless service can take 100 seconds to be fully ready in a fresh kind cluster?
Should we also set PublishNotReadyAddresses=true for other service types?

Use case
https://github.com/ray-project/kuberay/pull/2117/files#r1603897666
Related issues
https://github.com/ray-project/kuberay/pull/2117
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Regarding the source of the delay when PublishNotReadyAddresses=false, I have recorded a demo of creating a RayCluster with one worker in a fresh Kind environment:
Full Demo Recording:
https://github.com/ray-project/kuberay/assets/2727535/29c5e8a3-80de-463c-8b40-9ca2a79ddaa5
Timeline Breakdown:

The Kind took about 36 seconds to download the Ray image.
The worker took about 53 seconds to pass the ray health-check.
The worker took another 10 seconds to pass the k8s readiness check.

Result Screenshot:

The result is the RayCluster took about 100 seconds to be fully ready.
Root Cause Analysis
From the above timeline breakdown, we can see that most of the time was spent on multiple retires of ray health-check.
To inspect what is happening underneath, we can add the GRPC_VERBOSITY=DEBUG before doing the ray health-check and preserve its output:
diff --git a/ray-operator/controllers/ray/common/pod.go b/ray-operator/controllers/ray/common/pod.go
index 9939e63..1d747b7 100644
--- a/ray-operator/controllers/ray/common/pod.go
+++ b/ray-operator/controllers/ray/common/pod.go
@@ -172,16 +172,19 @@ func DefaultWorkerPodTemplate(ctx context.Context, instance rayv1.RayCluster, wo
 			Args: []string{
 				fmt.Sprintf(`
 					SECONDS=0
 					while true; do
 						if (( SECONDS <= 120 )); then
+							export GRPC_VERBOSITY=DEBUG
-							if ray health-check --address %s:%s > /dev/null 2>&1; then
+							if ray health-check --address %s:%s; then
 								break
 							fi
 							echo "$SECONDS seconds elapsed: Waiting for GCS to be ready."

Then we apply the RayCluster again to a fresh Kind environment:
Full Debug Recording:
https://github.com/ray-project/kuberay/assets/2727535/20a78408-3a2d-43dd-902f-52a26d4ace59
Debug Screenshot:

We now clearly confirm that the ray health-check can fail multiple times with the Domain name not found error which is indeed caused by PublishNotReadyAddresses=false.

Regarding the second question: Should we also set PublishNotReadyAddresses=true for other service types?
My previous thought was that other service types would not raise the Domain name not found error because they had a virtual IP, so there is no need to PublishNotReadyAddresses=true.
However, given that

KubeRay guarantees the Head service will apply to only one Pod at any given time. No worry about accessing a wrong Head.
Allowing users to access the Ray dashboard for troubleshooting through the service when readiness fails is a big use case.

I think we can safely set PublishNotReadyAddresses=true for all Head service types. WDYT @kevin85421? I'd value your feedback on this.

The worker took about 53 seconds to pass the ray health-check.

Interesting. I am very surprised that DNS registration takes much longer than my expectation, although the head Pod is already ready. Thank you for the investigation!

I think we can safely set PublishNotReadyAddresses=true for all Head service types.

Make sense to me.


error: Bad link to repo

@glebcha  I noticed that in the master branch there is an error, now it picks the<EMAIL_ADDRESS>repo url instead of the https, can yout take a look at it?

The solution is to parse url taken with git config --get remote.origin.url, get provider if it is in known list and replace common variations with https.

@rafinskipg Should be fixed with https://github.com/rafinskipg/git-changelog/pull/95


"Designed" should probably be "designated"

Also added a period since the sentence seemed complete.

@psy-q : Thanks for your contribution! The author(s) have been notified to review your proposed change.


1-click installer and updater. Uses micromamba to install git and conda into a contained environment (if necessary) before running the normal installation script

Hi,
This PR enables a user to install this project without requiring them to have anaconda or git pre-installed. This reduces unnecessary friction for users who aren't programmers or very technical. If a user already has anaconda or git pre-installed, these scripts will just pass-through and won't affect them. Honestly, it's just more straightforward for a user to use. :)
Current installation process for a user:

Install Anaconda
Install Git
Run the commands for a git pull (on Windows)
Run the webui script

Suggested new process (for Windows, Linux and optionally Mac):

Download the install.bat or install.sh script for their OS (linked below, or better, from a release on your project)
Run the script

That's it.
Main improvement: The user doesn't need to have python/anaconda/git pre-installed. This reduces unnecessary friction for non-technical users.
1-click Installers:

Windows: https://raw.githubusercontent.com/cmdr2/InvokeAI/main/installer/install.bat
Linux: https://raw.githubusercontent.com/cmdr2/InvokeAI/main/installer/install.sh
Mac: https://raw.githubusercontent.com/cmdr2/InvokeAI/main/installer/install.sh (but mac users will get an "unknown internet file" warning, and they'll need to open their System Preferences > Security and click the Allow micromamba button)

I've tested this on Windows x64 and Linux x64. I've tested this with and without Anaconda pre-installed. I've also tested it works if the installer gets interrupted mid-way, and needs to be re-run.
Disclosure: I'm the author of the cmdr2 UI and 1-click installer (https://github.com/cmdr2/stable-diffusion-ui). We use a similar approach and it's been working quite well (~1k installs/day) for over 2 months. None of the support issues have been due to this bootstrapping process, but rather due to the usual pip failures, VPN issues, bad system config etc.
How it works:

This script will install git and conda (if not found on the system PATH) using micromamba (an 8mb static-linked single-file binary, conda replacement). The micromamba binary will be downloaded if necessary using curl.

For users who already have git and python, this step will be skipped.

Next, it'll checkout the project's git repo, if necessary.

Next, it'll run the usual conda create commands (from the docs) to download the dependencies.

Finally, it'll then run the preload_models.py script to download the weights (except the SD 1.4 model).

After installation, users can run the new invoke.bat or invoke.sh scripts to enter a pre-activated conda environment. They can also do it the old way (of manually activating conda). It'll use either the git/python/conda that was installed through this installer, or the user's existing git/python/conda installation.
Finally, the user can run the new update.bat or update.sh script to update the git repo and the conda environment.
Next steps (if you wish to adopt this)
If you're willing, then the next steps are:

Merging this PR will get the installer scripts into the installer folder
Uploading the installer files to a GitHub release, or using the uploaded links inside this PR
Updating the README with the download links for the installer. I can submit the PR for the README, if you're interested.

If you're interested in this, I'd definitely suggest phasing this in gradually, maybe suggested as an easier alternative on the docs, until it is judged stable to use.
Thanks! :)

@cmdr2 ; Please do a rebase and flatten this to a single commit.

We really need to stress to users that they should put the install script in a new folder/dir before they launch it - currently it dumps everything in the script's pwd, which makes a serious mess if one runs it in e.g. $HOME

We really need to stress to users that they should put the install script in a new folder/dir before they launch it - currently it dumps everything in the script's pwd, which makes a serious mess if one runs it in e.g. $HOME

Yes - And potentially add a confirm step to the install process to verify they've done it

@Vargol tagging you b/c you were running different requirements (requirements-mac-MPS-CPU) vs. environment-mac.yml.
If so, a single Mac install may not cut it.

No cut off point, just a series of poor experiences with conda, I don't want that thing any where my mac.
As far as I'm concerned it adds nothing of value, and many of the things people say are pro's are con's to me.

As soon as this is fully tested and merged, I intend to replace conda with pip and venv. mambathingy can stay as an easy way to install git.

Get an error (already have invoke, of course)
sh /Users/artur/Downloads/install.sh
Installing InvokeAI..

Initialized empty Git repository in /Users/artur/.git/
remote: Enumerating objects: 10352, done.
remote: Counting objects: 100% (348/348), done.
remote: Compressing objects: 100% (171/171), done.
remote: Total 10352 (delta 185), reused 282 (delta 148), pack-reused 10004
Receiving objects: 100% (10352/10352), 85.80 MiB | 3.16 MiB/s, done.
Resolving deltas: 100% (6732/6732), done.
From https://github.com/cmdr2/InvokeAI
 * [new branch]      Any-Winter-4079-Any-Winter-4079-Textual_Inversion -> origin/Any-Winter-4079-Any-Winter-4079-Textual_Inversion
 * [new branch]      backend-processor-schema -> origin/backend-processor-schema
 * [new branch]      development             -> origin/development
 * [new branch]      development-invoke      -> origin/development-invoke
 * [new branch]      gh-pages                -> origin/gh-pages
 * [new branch]      img2img-on-all-samplers -> origin/img2img-on-all-samplers
 * [new branch]      inpainting-improvement  -> origin/inpainting-improvement
 * [new branch]      installation-directory  -> origin/installation-directory
 * [new branch]      invoke-development      -> origin/invoke-development
 * [new branch]      invoker-framework       -> origin/invoker-framework
 * [new branch]      main                    -> origin/main
 * [new branch]      model-switching         -> origin/model-switching
 * [new branch]      release-candidate-2     -> origin/release-candidate-2
 * [new tag]         2.0.0-rc1                -> 2.0.0-rc1
 * [new tag]         2.0.0-rc2                -> 2.0.0-rc2
 * [new tag]         2.0.0-rc3                -> 2.0.0-rc3
 * [new tag]         2.0.0-rc4                -> 2.0.0-rc4
 * [new tag]         2.0.0-rc5                -> 2.0.0-rc5
 * [new tag]         2.0.0-rc6                -> 2.0.0-rc6
 * [new tag]         2.0.0-rc7                -> 2.0.0-rc7
 * [new tag]         2.0.0-rc8                -> 2.0.0-rc8
 * [new tag]         release-0.95             -> release-0.95
 * [new tag]         release-1.02             -> release-1.02
 * [new tag]         release-1.03             -> release-1.03
 * [new tag]         release-1.04             -> release-1.04
 * [new tag]         release-1.05             -> release-1.05
 * [new tag]         release-1.06             -> release-1.06
 * [new tag]         release-1.07             -> release-1.07
 * [new tag]         release-1.08             -> release-1.08
 * [new tag]         release-1.09             -> release-1.09
 * [new tag]         release-1.10             -> release-1.10
 * [new tag]         release-1.11             -> release-1.11
 * [new tag]         release-1.13             -> release-1.13
 * [new tag]         release-1.14             -> release-1.14
 * [new tag]         release-1.14.1           -> release-1.14.1
 * [new tag]         release-2.0.0            -> release-2.0.0
 * [new tag]         release-candidate-1.14   -> release-candidate-1.14
 * [new tag]         release-candidate-1.14.1 -> release-candidate-1.14.1
 * [new tag]         release-candidate-1.14.2 -> release-candidate-1.14.2
 * [new tag]         release-candidate-1.14.3 -> release-candidate-1.14.3
 * [new tag]         release-candidate-1.14.4 -> release-candidate-1.14.4
 * [new tag]         release_0.91             -> release_0.91
 * [new tag]         release_0.96             -> release_0.96
 * [new tag]         release_1.0              -> release_1.0
 * [new tag]         release_1.01             -> release_1.01
 * [new tag]         show                     -> show
 * [new tag]         v2.0.0                   -> v2.0.0
 * [new tag]         version_0.9              -> version_0.9
Branch 'main' set up to track remote branch 'main' from 'origin'.
Switched to a new branch 'main'

CondaValueError: prefix already exists: /Users/artur/miniconda3/envs/invokeai

Traceback (most recent call last):
  File "/Users/artur/scripts/preload_models.py", line 6, in <module>
    from transformers import CLIPTokenizer, CLIPTextModel
ModuleNotFoundError: No module named 'transformers'

Now you need to install the weights for the stable diffusion model.
Please follow the steps at https://invoke-ai.github.io/InvokeAI/installation/INSTALL_MAC/ to complete the installation

Seems it works
Installing InvokeAI..
CondaValueError: prefix already exists: /Users/artur/miniconda3/envs/invokeai
NOTE: Redirects are currently not supported in Windows or MacOs.
Installing bert tokenizer (ignore deprecation errors)......success
Installing Kornia requirements......success
Loading CLIP model......success
/Users/artur/miniconda3/envs/invokeai/lib/python3.9/site-packages/torchvision/models/_utils.py:208: UserWarning: The parameter 'pretrained' is deprecated since 0.13 and will be removed in 0.15, please use 'weights' instead.
  warnings.warn(
/Users/artur/miniconda3/envs/invokeai/lib/python3.9/site-packages/torchvision/models/_utils.py:223: UserWarning: Arguments other than a weight enum or `None` for 'weights' are deprecated since 0.13 and will be removed in 0.15. The current behavior is equivalent to passing `weights=None`.
  warnings.warn(msg)
Installing models from RealESRGAN and facexlib......success
Loading models from GFPGAN
Installing CodeFormer model file......success
Installing clipseg model for text-based masking......success
Installing safety model for NSFW content detection......success
mkdir: models/ldm/stable-diffusion-v1: File exists

But as a user, I’ve been stuck with this
Now you need to install the weights for the stable diffusion model.
Please follow the steps at https://invoke-ai.github.io/InvokeAI/installation/INSTALL_MAC/ to complete the installation

Are we going to do a fully automatic installation or to leave it like that?

Thanks everyone, I plan on working on the PR comments later today.

M1, macos Ventura 13.1. Webserver error
>> Point your browser at http://<IP_ADDRESS>:9090
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] code 400, message Bad request version ('&\x89\x00*ÊÊ\x13\x01\x13\x02\x13\x03À,À+Ì©À0À/Ì¨À')
ò£òí{â?wûbk(ß,ks Oct/2022 03:37:23] "üPköpcyvrÊ
                  Ñ¹rÎßÎ{Hý;Î\ÒQ«ñ~u&*ÊÊÀ,À+Ì©À0À/Ì¨À" 400 -
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] code 400, message Bad request version ('\x83\x00,jj\x13\x01\x13\x02\x13\x03À,À+Ì©À0À/Ì¨À')
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] "ürØ2hÖNÄÏ#óD\Z²Æ·}S´&WAjJ <?	ôjÔü¬+zÈÁE±®¡%f(=pj®5,jjÀ,À+Ì©À0À/Ì¨À" 400 -
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] code 400, message Bad request version ('Òª\x00\x00\x14À')
ÒªÀ 400 -- - [29/Oct/2022 03:37:23] "ÈL©ÔÞÊbchZ)ÈÑùmy7ûÂ
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] code 400, message Bad request version ('\x00*ÚÚ\x13\x01\x13\x02\x13\x03À,À+Ì©À0À/Ì¨À')
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] "üßÔð«76?wÂýÞ:§)K½ê´B-Ñ¶S
                                                                    õ GÏ¡öeqítý_I0/"/BïYAÄS"¼o*ÚÚÀ,À+Ì©À0À/Ì¨À" 400 -
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] code 400, message Bad request version ('(\x05¬R\x00,\x1a\x1a\x13\x01\x13\x02\x13\x03À,À+Ì©À0À/Ì¨À')
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] "ü¿Æf;á°Í¼ÔÍ}æÔéñÎ·Ù
                                                              ¦FXyÖ ÍÏY4óéCË¸æ¤d©æ=µoNg	(¬R,À,À+Ì©À0À/Ì¨À" 400 -
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] code 400, message Bad request version ('\x90\x00\x00\x14À')
<IP_ADDRESS> - - [29/Oct/2022 03:37:23] "Ò1è`	GR^þ±ÌÙ²óúÒï¦l$À" 400 -

I've just rewritten the preload_models.py script to interactively download, install and configure the user's preferred weights files. It is in PR #1290 . Once this is accepted, the installer script here will be able to do a full end-to-end install with minimal user intervention.
At that point, there's just a little documentation and videography, plus the debugging. I'll make a release branch when the preload script is tested and merged.

Thanks, I've made the changes based on the PR comments, and I think this PR is ready (from my end) to be considered for merging.
After merging, 4 things need to happen:

The git repo path in install.sh/bat needs to change to the main invokeAI repo
The micromamba.exe download path in install.bat needs to change to a release URL from the invokeAI repo
The installer zips need to be hosted on the invokeAI repo
The documentation needs to be changed (I'd suggest in a phased manner).

PR feedback and changes:

Squashing commits - I squashed the commits in my development branch, but I can't change this PR's source branch. If you can do that, then you'll get a squashed commit. Squashing in my main branch is tricky because the commit history is merged with other unrelated commits by other folks.

Otherwise, you can always just press the "Squash and Merge" in this PR, using the arrow next to the "Merge" button: https://stackoverflow.com/a/36377439

Showing the next steps - I've updated the invoke.sh/bat scripts to allow the user to select the command-line or web UI (or a developer console, useful for debugging broken installations). And the install.sh/bat script now tells the user to run invoke.sh/bat after the installation has finished.

Distribute installer zips instead of direct script files - This is to avoid users running the install.sh/bat script inside their Download or home folder, and having the entire repo explode into that folder. Another benefit of a zip is that we include a simple readme.txt to guide the user what to do. But mainly, this ensures that the install script is always run inside a new invokeAI folder.

I've also included a few minor tweaks, based on the learnings from the production usage of this installer on our cmdr2 UI repository as well. To reduce the chances of support tickets (for e.g. re-downloading micromamba if it only downloaded partially before failing).


Casehistory/balboa

Simple transformation of google doc to rst for balboa ztem case history.
Check how this looks like @dougoldenburg @lheagy

I'll handle comments soon (figname and references). But still, can we merges this?
It might be good to show Jean that it could be on live pretty fast.
Let me know what you guys think? @lheagy @dougoldenburg

Nice work @sgkang, this looks good! There are a few low-hanging items that I would appreciate if you are willing to take care of before we merge this in. The updates to the figure names will change their external links, so if we want to point to them from outside, it would be nice if those do not change. I realize the other items are small, but it gets harder to keep track of these minor things once a pr has been merged.

Thanks @sgkang !


Does this work in React 18

Hi. I'm using the component as per the docs, but in a React 18 app. I'm seeing the network request come back with results, but no suggestions are displayed. The <ul> in the DOM for the address suggestions has no child <li> elements, and it is hidden - both of which imply the component is not correctly setting the suggestions even though the network request is successful and contains suggested addresses.
Presumably this component does work in React 17, so I'm wondering whether there's something about the implementation that makes it not work in React 18. Any chance it's been tested in React 18?

We are running this package in production in multiple React 18 projects.


api endpoint and cli command for changing freight aliases

Fixes #1074 #1076
It made sense to tackle these together.
If you ignore codegen, this PR isn't nearly as big as it appears.

This needs some webhook modifications in case the alias is modified using kubectl.


Added support for Android NDK r10e

Doesn't quite work for building boost-1.53.
I took the changes made as part of this commit and applied them to the build-android.sh script and added the changes made to the configs/user-config-boost-1_55_0.jam file and applied them to the equivalent 1_53 config.  It would be useful if all of the boost configurations in Boost-for-Android were updated as part of this merge rather than just the latest one.

Cleaning up old issues, NDK r10e is quite ancient by now.


Fix crash relating to annotated attributes

Fixes #3830 - don't allow annotation types to set the type of cdef class class-level attributes
(originally part of https://github.com/cython/cython/pull/3845)

Thanks, LGTM, will merge when travis is happy.

It looks like a different check is now catching these annotations before my warning is detected. I'll look at it again later but it may be that this patch is no longer needed. (I suspect the new check is going to break my dataclass PR but that's a separate problem...)

Thanks


Update ids.psv

added me

You seem to have misunderstood the task. You were supposed to edit the file "names.psv". You seem to have edited "ids.psv". Please try again. I'll close this pull request without taking any further action.


ImportError: cannot import name MiddlewareMixin in django 1.9

Hi, I am using django 1.9 and I'm getting this error.

I have fixed It for django old version.

How did you fix it @sainipray , Not fair


ROX-14127 Updated test to use multiarch image

Updates test image to use the multiarch version
Following changes have been made in the test case for the mulitarch image

Updated total number of CVE's in image
Updated CVE in graphQL query from CVE-2017-18190 to CVE-2017-12611
Updated base image from debian:8 to ubuntu:20.04

/test ocp-4-10-qa-e2e-tests
/test ocp-4-12-qa-e2e-tests
/test gke-qa-e2e-tests

@jdao-rh can you re-run the build for this PR? I think when you first committed your changes you were not in the org. Thanks, -Gavin

/retest
/test ocp-4-10-qa-e2e-tests
/test ocp-4-12-qa-e2e-tests
/test gke-qa-e2e-tests

duplicate of https://github.com/stackrox/stackrox/pull/6569


[infra] Set preventAssignment for rollup-replace

This removes the error:
(!) Plugin replace: @rollup/plugin-replace: 'preventAssignment' currently defaults to false. It is recommended to set this option to `true`, as the next major version will default this option to `true`.

I checked. But also, every replacement we have ends in a boolean literal that would be a syntax error if it were followed by an assignment.


Add option to ignore guard clauses in ReturnCount rule

Expected Behavior of the rule
ReturnCount rule has an option to ignore use of guard clauses.
Context
In some functions it is cleaner to have a series of guard clauses at the top of the function to return early than some other methods of achieving the same result.
An option to ignore guard clauses can be added to the rule. When enabled the logic could be to ignore returns for all statements at the beginning of a function, but only when statements are in one of the following forms:
if (expression) return
val x = person.name ?: return

These would have to be the first declarations in the function body. As soon as a statement not in that form appeared then ReturnCount would start counting instances of return.
To be debated is whether or not require or check functions could appear before guard clauses. They serve a very similar function. IMHO these functions (and variants) could appear before guard clauses as well, since it would be better for the function to throw an exception due to unexpected/incorrect state before guard clauses are checked, as guard clauses are part of normal program flow.

Picking this feature up.
Targeting to support if condition guard clauses (need not be the first statement necessarily).
Planning to add the configuration excludeGuardClauses for this purpose with a default value of false.

Thanks @amitdash291! I'd still like to see the guard clauses be ignored when they're the first statements (or following require or check statements) as returns from other areas of the function, even as part of a simple if statement, couldn't really be considered "guards", instead they're just part of the function's logic.
Also ignoreGuardClauses would be better as the config option name I think.
Looking forward to the PR!

Thanks @amitdash291! I'd still like to see the guard clauses be ignored when they're the first statements (or following require or check statements) as returns from other areas of the function, even as part of a simple if statement, couldn't really be considered "guards", instead they're just part of the function's logic.
Also ignoreGuardClauses would be better as the config option name I think.
Looking forward to the PR!

@3flex, thanks for the response.
Support for the Elvis operator guard clauses (eg: val x = person.name ?: return) is also possible. The only remaining piece of the puzzle is to make sure the clauses are the first statement of the functions. I am working on it.

@3flex, the PR is ready and approved. It would be great if you could review it too :)

Currently, the PR doesn't support excluding return count for guard clauses followed by require and check functions. I had a few questions to be clarified before the same can be done with corresponding test cases.
For eg: does the following cases also qualify as exclusion scenarios:

fun testFun(testVal: String?) {
requireThat(testVal != null)
checkIf(testVal != null)
if (testVal != null) return
}

2. ```kotlin
fun testFun(testVal: String?) {
 require(testVal != null)
 checkValidations(testVal != null)
 if (testVal != null) return
}

Or should we watch out for only check and require strings in the function name?
I would recommend doing this in the next iteration, possibly as a part of a follow-up issue, where we can get these questions clarified. I would be happy to pick it up.

@amitdash291 thanks for implementing this feature. Could you please formulate the missing improvements in a new issue? Otherwise, it becomes hard to track the details here.

@schalkms thanks a lot for merging the PR!
I will go ahead and copy the remaining improvements in a new issue soon.


python310Packages.mobly: 1.12 -> 1.12.1

Description of changes
Diff: https://github.com/google/mobly/compare/refs/tags/1.12...1.12.1
Changelog: https://github.com/google/mobly/blob/refs/tags/1.12.1/CHANGELOG.md

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

3 packages failed to build:

python311Packages.home-assistant-chip-core
python311Packages.mobly
python311Packages.python-matter-server

4 packages built:

home-assistant-component-tests.matter
python-matter-server (python310Packages.python-matter-server)
python310Packages.home-assistant-chip-core
python310Packages.mobly


Validate logdetective updates in stable Fedora

This is a followup to https://github.com/fedora-copr/logdetective/issues/86
We should create a simple smoke test for logdetective via tmt that will just print logdetective --help.
In python-llama-cpp we should run the test suite in Testing Farm, ideally with some small, basic models.
Updates of llama-cpp should be gated on these 2 test suites - we need to make sure that whole dependency stack won't break easily.

Initial work:
https://src.fedoraproject.org/rpms/python-llama-cpp-python/pull-request/12
https://src.fedoraproject.org/rpms/llama-cpp/pull-request/9#


support Guids in Event Pipe metadata

Fix for https://github.com/dotnet/coreclr/issues/16105

Looks good to me.


Demo is broken

These endpoints return 503 http error in the demo app https://next.medusajs.com/store

https://production-like-starter.herokuapp.com/store/carts
https://production-like-starter.herokuapp.com/store/customers/me
https://production-like-starter.herokuapp.com/store/regions
https://production-like-starter.herokuapp.com/store/products?limit=12&offset=0&is_giftcard=false
https://production-like-starter.herokuapp.com/store/collections?offset=0
https://production-like-starter.herokuapp.com/store/collections

Thanks for reporting it @MatteoGauthier
@olivermrbl can we get the server up and running again?

@kasperkristensen same error at 2023-03-18 :thinking:.

Seems like there the demo https://next.medusajs.com/ is still broken. The backend APIs are failing because of CORS configuration.

Still broken 👀

Thanks @kasperkristensen for the fix, Just wanted to check if there are any specific steps we need to take on our instance to avoid this bug in the future. It would be helpful if you could share some details on how you fixed the issue. Thanks again, byee!

@MatteoGauthier Not sure what you mean? The reason why the demo was broken was that the server got taken down by Heroku, because we forgot to update it when their old Redis service was deprecated, and then we just kept not getting around to setting up the server again 😄


Feature Request

Add more weather providers like AccuWeather , Weather.com , etc if possible .

Yes, I'd like to see them too, especially AccuWeather.

Hey guys, I've just added a few new weather providers in the new beta version.
I'm still working on the AccuWeather support but it seems that the APIs don't permit a lot of day requests. Are you going to use a "premium" account? Or do you want to use a freemium one?
I'm trying to figure out how to handle the limit and to reduce the APIs calls.


Reclaiming Size/Calculating Size Beta

Anyone have experienced this issue yet?
I have downloaded and installed NSL for the past few weeks now but I started to experience this issue 2 days ago.
Back then when I launch bnet from the library everything works smooth but now I've noticed that it takes a while before you can hit the Play button to launch a game on Bnet launcher. Status that it shows at that time was Queued then after a few minutes it goes > Reclaiming Space... Then Play button would light Green and you can start to play.
I thought Queued indicated that there are other applications being update by the launcher but there is no other game installed other than Diablo 4. After checking further I noticed that the Beta option of the launcher seems to be downloading something. (picture attached).
Seems like its trying to download something which was probably the reason for Queue. I have never selected any option with this Beta Menu which makes me confused.
Things I've attempted to do:
-Ran desktop script and chose Fresh start to wipe everything.
-Also tried to ran desktop script and specifically choose Bnet to be uninstalled
-Reimaged Steam deck
-After reimaging, and re-installatin of NSL and Bnet launcher. I am now unable to install the Diablo 4 as it is stuck now on calcuating its size. My bet on this is because of the Beta Software trying to download something and putting everything else on queue.

It's battle.net problem not related to Non-steam launchers.  Launcher just doesn't update itself and tries to redownload update every time you launch it. You will experience same problem if you install battle.net via Lutris,  directly via proton  and even on windows.


Wiremod Inputs randomly defunct

This is a very strange issue which I've had for a bit.
The only way I can summarise it is that one moment, Wiremod inputs such as pod controllers were working fine, and the next, they weren't.
I've tried verifying my game cache, reinstalling Wiremod and even reinstalling Garry's Mod, but the issue persists. They just don't work.
Button inputs and such are fine, but anything requiring keyboard or possibly mouse inputs do not work.
On further investigation, E2 does appear to register inputs, but doesn't do anything about it, if that makes any sense. It'll recognise a key is pressed, but it just does nothing. No output, nothing.
Very strange.

Post a dupe of the contraption that has the issue pls

qTestRig_2.txt
I have confirmed that the dupe is fine, since when spawned in other people can use it just fine. It just doesn't work for me.
Would me using the x64 beta be an issue? Because all of a sudden this has happened to all of my computers running Garry's Mod. I'll try using x86 to see if that solves it, actually.

Using the x86 build did not solve the issue. The issue is now happening on all of my computers that have Garry's Mod installed, so perhaps there's an addon conflict or something like that?

People have reported problems with the x64 beta so yes that is the problem.

Try a fresh re-install. Switching back to x86 probably set back some things.

Completely unsubscribing from the x86-64 beta solved the issue.


Exclude the Hue Bridge .. I would like to use only RaspBee II ..

Sorry for the "simple" question. But how can I use it only with my deCONZ RapsBee II ?? When I delete the HueBridge User, the PlugIn asked to connect to hue every time :-((
TheHue: press link button on the bridge to create a user - retrying in 15s .. I'll "remove" this.

Set hosts in config.json to disable discovery and specify only the deCONZ hostname/port.

This is my config, yet ..
    {
        "platform": "Hue",
        "name": "Hue",
        "brightnessAdjustment": 100,
        "heartrate": 5,
        "lowBattery": 25,
        "timeout": 5,
        "waitTimePut": 50,
        "waitTimePutGroup": 1000,
        "waitTimeResend": 300,
        "waitTimeUpdate": 20,
        "users": {
            "001788FFFE220AB6": "...",
            "00212EFFFF0A5728": "..."
        },
        "sensors": true
    }

This doesn't work:
    {
        "platform": "Hue",
        "name": "Hue",
        "hosts": ["<IP_ADDRESS>"],
        "brightnessAdjustment": 100,
        "heartrate": 5,
        "lowBattery": 25,
        "timeout": 5,
        "waitTimePut": 50,
        "waitTimePutGroup": 1000,
        "waitTimeResend": 300,
        "waitTimeUpdate": 20,
        "users": {
            "001788FFFE220AB6": "...",
            "00212EFFFF0A5728": "..."
        },
        "sensors": true
    }

With Port :443 .. doesn't work, too :-((

21.12.2022, 20:29:29HOOBS starting
21.12.2022, 20:29:39HOOBSLoaded plugin 'homebridge-broadlink-rm-pro'
21.12.2022, 20:29:39HOOBSLoaded plugin 'homebridge-eveatmo'
21.12.2022, 20:29:40HOOBSLoaded plugin 'homebridge-hue'
21.12.2022, 20:29:40HOOBSLoaded plugin 'homebridge-midea-air'
21.12.2022, 20:29:41HOOBSLoaded plugin 'homebridge-xiaomi-fan'
21.12.2022, 20:29:41HOOBSLoading 5 platforms...
21.12.2022, 20:29:41HOOBSeveatmo platformLoading new data from API for: weatherstation
21.12.2022, 20:29:41HOOBSBroadlink[INFO] Automatically discovering Broadlink RM devices.
21.12.2022, 20:29:41HOOBSBroadlink[INFO] Running Bridge Broadlink RM Plugin version 4.4.11
21.12.2022, 20:29:41HOOBSBroadlinkSomplex Accessory Ready
21.12.2022, 20:29:41HOOBSBroadlinkTV Accessory Ready
21.12.2022, 20:29:41HOOBSBroadlinkSoundbar Accessory Ready
21.12.2022, 20:29:41HOOBSHuehomebridge-hue v0.13.42, node v16.18.1, homebridge v1.5.0
21.12.2022, 20:29:41HOOBSHueWARNUNGwarning: planned changes, see https://github.com/ebaauw/homebridge-hue/issues/1070
21.12.2022, 20:29:41HOOBSHuesearching bridges and gateways
21.12.2022, 20:29:41HOOBSmidea-airLoading accessory from cache: AirCon_5204
21.12.2022, 20:29:41HOOBSmidea-airLoading accessory from cache: Living Room
21.12.2022, 20:29:41HOOBSxiaomifanInit - initializing devices
21.12.2022, 20:29:41HOOBSxiaomifan[Ventilator] Init - got fan configuration, initializing device with name: Ventilator
21.12.2022, 20:29:42HOOBSBroadlink[INFO] Discovered Broadlink RM4 Mini (5216) at <IP_ADDRESS> (ec:0b:ae:9e:e4:69)
21.12.2022, 20:29:42HOOBSHuemeethue: request 1: GET /
21.12.2022, 20:29:42HOOBSHueWARNUNGmeethue: request 1: http status 429 Too Many Requests
21.12.2022, 20:29:42HOOBSHuemeethue: request 1: GET /
21.12.2022, 20:29:42HOOBSHueWARNUNGmeethue: request 1: http status 429 Too Many Requests
21.12.2022, 20:29:43HOOBSmidea-airCreated device: AirCon_5204, with ID: ***, and type: 172
21.12.2022, 20:29:43HOOBSmidea-airCreated device: Living Room, with ID: ***, and type: 161
21.12.2022, 20:29:46HOOBSHueTheHue: Signify Netherlands B.V. BSB002 bridge v1955082050, api v1.55.0
21.12.2022, 20:29:46HOOBSHueWARNUNGTheHue: warning: not using recommended Hue bridge api version 1.52.0
21.12.2022, 20:29:46HOOBSHuePhoscon: dresden elektronik deCONZ gateway v2.19.3, api v1.16.0
21.12.2022, 20:29:46HOOBSHueWARNUNGPhoscon: warning: support for deCONZ will be deprecated in favour of Bridge deCONZ
21.12.2022, 20:29:46HOOBSHueWARNUNGPhoscon: warning: not using recommended deCONZ gateway version 2.17.1
21.12.2022, 20:29:46HOOBSHuePhoscon: 3 accessories
21.12.2022, 20:29:46HOOBSHuePhoscon: websocket connected to ws://<IP_ADDRESS>:443
21.12.2022, 20:29:47HOOBSHueTheHue: 21 accessories
21.12.2022, 20:29:47HOOBSHuemasked debug info dumped to /var/lib/hoobs/hoobs/homebridge-hue.json.gz
21.12.2022, 20:29:47HOOBSHueTheHue: 2 services
21.12.2022, 20:29:47HOOBSHuePhoscon: 2 services
21.12.2022, 20:29:47HOOBSBridge is running on port 51826.
21.12.2022, 20:29:47HOOBSHueTheHue: event stream connected to https://<IP_ADDRESS>/eventstream/clip/v2
21.12.2022, 20:29:52HOOBSHuenpm registry: request 1: GET /homebridge-hue/latest
21.12.2022, 20:29:52HOOBSHueWARNUNGnpm registry: request 1: timeout after 5 seconds

Wrong Port .. 1881 in hoobs. Is working now ;)


ScreenshotPlugin: Fix level up widget ids

Causing no screenshots being taken on level up

This should now fix all the used widget ids that were changed


branding does not work if changing the plugin name

issue:
when changing the plugin name for branding (for example mtv-plugin instead of forklift-console-plugin) the plugin fails to load
suspected reason:
in some places in the code we hard-coded the plugin name, for exmaple:
https://github.com/kubev2v/forklift-console-plugin/blob/main/pkg/web/src/app/queries/helpers.ts#L82

need to find the reason the plugin fail to load when a branded name is used
need to fix it

cc:// @mnecas @rszwajko @sjd78


Fix expandDims

The original implementation only worked for a single case: dimensions = 1
Also I don't see a good reason to use Indexing, if a simple reshape should work just fine.

I've tried to make it Work with NDArrayIndex, but even after fixing the wrong position of newAxis it still returned the wrong shape. Maybe there is a bug in there too?
This updated version now uses more thorough tests and preserves the input ordering.

Looks good, assuming tests pass... so my only remaining question is whether we want to enforce the expanded one always being a view - and if so, we should also test for that. I'm inclined to do that, but could perhaps be persuaded otherwise
(one simple way to test: modify the original, check the expanded one also changes)

According to .isView() the result isn't a view, yet when I run the following, it doesn't fail.
testMatrix.assign(Nd4j.rand(shape));
assertEquals(message, testMatrix.ravel(), expanded.ravel());

I'm confused a bit by that.

@treo it's possible it's not always a view... some of the arrays returned by NDArrayCreationUtil aren't views (but most are). If that's not simply what's going on here - maybe open an issue.
I'm happy with the assign + assert approach though.

@AlexDBlack I meant that expanded.isView() returns false, yet, assign to testMatrix changes it.

@treo yes, that was my interpretation and what I was referring to. Specifically, you could legitimately imagine that Nd4j.create(10,10).transpose().isView() could return false (not sure if it actually does) - it's contiguous in buffer and is offset 0...

@AlexDBlack Done.


New issue

Before opening:

Search for duplicate or closed issues
Validate and lint any HTML to avoid common problems
Read the contributing guidelines

Bug reports must include:

Operating system and version (Windows, macOS, Android, iOS, Win10 Mobile)
Browser and version (Chrome, Firefox, Safari, IE, MS Edge, Opera 15+, Android Browser)
Reduced test case and suggested fix using CodePen or JS Bin

Modal title

×

Modal body text goes here.

Close
Save changes


Load image

Golang 1.16 use new embed package to Embed Files.
Will there be a function like this?
//go:embed img/test.png
var testPng []byte
img, _, _ := image.Decode(bytes.NewReader(testPng))

Bm := robotgo.ImgToBitmap(img) // <-this
fx,fy := robotgo.FindBitmap(Bm)
if fx > 0 && fy > 0 {
	// Do...
}

Thank you for your answer.

robotgo.OpenBitmap(file) there is a method that opens an image
https://github.com/go-vgo/robotgo/blob/master/examples/bitmap/main.go#L141

robotgo.OpenBitmap(file) there is a method that opens an image
https://github.com/go-vgo/robotgo/blob/master/examples/bitmap/main.go#L141

This is in the plan, maybe next.


Error: It looks like Git is not installed on your system

I recently installed VSC Insiders x64 and stable x64 on a new computer (Windows 10 PC)
I clicked on Clone Git Repository and received the following INFO: It looks like GIT not installed on your system
I openeded a previosuly working workspace with .git and it fails to show Gir repository in VSC.
I'm stumped ! please help.

VSCode Version: 1.17.2
OS Version: Windows 10 Pro

Steps to Reproduce:

Reproduces without extensions: Yes/No

Did you install git?

I thought it was already part of the VSC build; is that not the case ?
I've installed it separately now

It's not included in VS Code. You must install it.


Feb23 updates

Overall Review of Changes:
A lot of changes.
Thanks to all those who have provided feedback
Issue Fixes:
#1
#2
#3
thanks to @vbotka
#63
thanks to @makefu
#67
thanks to @CFoltin
#68
#69
thanks to @hackery
#70
Enhancements:
List and standard outputs
Changelog added (started from Feb23 devel)
fqcn
Assertions for root and grub passwords
import tasks to allow tags to be used
lint files updated
ansible version updated
changed to rules improvements
<IP_ADDRESS> - checks for snap being used and skips as not possible to enforce
1.4.2
1.5.1 speed up test
1.7.1 ability to stop motd_dynamic from being loaded (optional)
1.9 rediscover pkgs after patching
4.4. logrotate
5.5.4 tidy up regex
6.1.14 sgid optional fix
Audit enhancements
audit path now /opt
goss version update
alignment of rules and variables used in audit
As well as addressing alot of controls in the audit itself
How has this been tested?:
Thoroughly tested locally alongside audit

Thanks! What's the story with the failing checks?

new controls i've added in. Shows that they work :)

Welcome message failed due to new version once merged.


Force latest Python in empty environment in conda install CI test

Closes #2063
Currently testing on me machine, env still solving but at least memory doesn't go up the roof anymore and stays stable at ~1.6GB
UPDATE after some 12min the darn thing solves and the installation goes ahead!
I think I know why we were getting hit badly - the Python version that comes in the empty environment right before installing esmvaltool is Python=2.7 (really, conda?)

OK conda install straight from conda now works fine (both on my machine and on the CI machine ) and I have updated the documentation with the instructions -> @bouweandela please review when you haz time :beer:

frenly ping @bouweandela to approve this so we can have us a working conda install test plese :beer:

@bouweandela it'd be really nice if we got this in today pls man, I want to show that (among other things) Circle tests pass OK during my presentation at the CRESCENDO GA tomorrow - not a nice note if our README badge shows FAILED :grin:

Sorry for being slow to respond @valeriupredoi. I'm not entirely happy about these changes, because it shows that it has (again) become incredibly hard to solve the conda environment for a proper installation. If you have a look at the conda build, you'll see that it's been taking about 2 hours recently. I think it would be better to create a new conda package that is easier to solve.
However, if you prefer proceeding like this, I would recommend being at least a bit less specific about the Python version, e.g. use 3.9 (instead of 3.9.2), because if you're that specific about the version we would need to update the installation instructions every time there is a new minor Python release.
By the way, I noticed that the conda build is also broken since Friday for both the ESMValCore and ESMValTool packages.

not a worry, bud, sorry for rushing you :) Yes, I completely agree with changing the forced version to a more generic Python 3.9, let me just commit that. About creating a new package - how would that change the situation? We still have the same deps and dep relations, unless you think of breaking the package down in smaller packages? Let's just go with this for now since this fixes the situation (or, was fixing it at the time of commit, lemme try again) and talk about the next steps after? :beer:

About creating a new package - how would that change the situation? We still have the same deps and dep relations, unless you think of breaking the package down in smaller packages?

No, we would just need to add some more lower bounds on acceptable versions of dependencies and hope that makes the environment easier to solve, as usual.

Let's just go with this for now since this fixes the situation (or, was fixing it at the time of commit, lemme try again) and talk about the next steps after?

It doesn't solve the problem, because the conda build is broken too (takes forever), so just fixing this won't make CircleCI look green again.

It doesn't solve the problem, because the conda build is broken too (takes forever), so just fixing this won't make CircleCI look green again.

hahaha, communist Circle it is :grin: sooo we can temporarily turn off the conda build test until we fix it :imp:

No, we would just need to add some more lower bounds on acceptable versions of dependencies and hope that makes the environment easier to solve, as usual.

Right you are! But beats me if I have the patience to do that anymore man :stuck_out_tongue_closed_eyes:

Same here..

I just updated the installation instructions a bit and changed the command on CircleCI so it looks the same, hope that's OK with you.

looks good, dude! Just approve this once the tests have passed and we should be OK for now :+1:

cheers for the changes and approval @bouweandela - looks like conda build is hanging again so I'll merge this (even if it hangs forever, at least conda install now works). We'll have to look into the build again (sigh!) :+1:


In included file: too few arguments provided to function-like macro invocation

After I configured gcc-13 and conan according to Configure option 2: invoice conan, then cmake, it prompted "In included file: too few arguments provided to function like macro invoice". Why is this?
OS: macOS 14.4.1 23E224 arm64
SDK:
xcode-select: version 2406
gcc: gcc-13 (Homebrew GCC 13.2.0) 13.2.0
clangd: Homebrew clangd version 18.1.5
XCode: 15.3 (SDKVersion 14.4)

In fact, this problem can be easily solved through brew upgrade gcc --greedy.

To clarify, the issue might be caused by the update of XCode as you mentioned. Just executing brew reinstall gcc should be enough to solve this problem, as I did before.
I was too lazy to mention this. Sorry for the misleading.

related to Homebrew/homebrew-core#173647


Update link to Typhoon in README

typhoonframework.org is now a parked domain, and bizarrely redirected to some NSFW advertising when I first clicked it.

Thanks 👍


added mirroring to virtual services. (Do Not Merge Yet)

This change will mirror primary traffic to canary pods.
If there is update in original flagger repo, we would be able to update this forked repo easily because this change is very straight forward and no complexity is added.
I need to update repository name if this change looks good.

Sorry, it's a wrong repo.


Add Factory Method to SynonymMap to Create from File

Fixes #20329
This PR adds a factory method to SynonymMap to enable creating it from a given file.

/azp run java - search - tests


Alt for discussion: CB-8866: add "Mixed Platforms" and "Win32" and CB-8869: Windows Universal without Windows 8.0

This PR is an alternative to PR #67 and PR #68 for discussion and mutually exclusive to both. It is intended to solve two problems in one shot:

CB-8866: missing "Mixed Platforms" and "Win32" causes problems when installing a plugin such as Cordova-sqlite-storage with C++ component
CB8869: remove Windows 8.0 from Windows Universal target. The Windows 8.0 target is not supported by some newer tools (such as Visual Studio Express 2013) or Windows Universal plugins (such as Cordova-sqlite-storage), and can confuse newer Windows Universal app developers.

If we cannot drop Windows 8.0 right now, then please ignore this PR as well as PR #68.
As I said in #67 and #68, my ICLA for Apache was already accepted for apache/cordova-wp8#72.

Withdrawn for reasons described in #68.


How to handle unglossed words?

Quite often, people will not gloss words like person or place names or unparsable words, so some words may only be present in Primary_Text, but not in Analyzed_Word or Gloss.
The most transparent way to store an example like that in CLDF is to have an empty list item in these two columns:
Primary_Text:  "x y Person z"
Analyzed_Word: "x\ty\t\tz" (["x","y",None,"z"] once read by pycldf)
Gloss: "xg\tyg\t\tzg" (["xg","yg",None,"zg"])
This passes validation, but for example cldf createdb does not work (TypeError: sequence item 1: expected str instance, NoneType found) and I've been doing things like ex["Analyzed_Word"] = ["" if x is None else x for x in ex["Analyzed_Word"]] in initializedb.py scripts.
Should empty items in a gloss column raise an error upon validation? If yes, is the way to handle unglossed words to simply leave them out? (i.e. "x\ty\tz" ["x","y","z"])? Or, if empty items are allowed, would it be OK for pycldf to yield "" instead of None (i.e. "x\ty\t\tz" ["x","y","","z"])?

Hm, the most transparent practice I've seen in this regard is using ellipsis … (ideally the Unicode character U+2026, and not three dots ...) in both, Analyzed_Word and Gloss. Admittedly, this is also often used very inconsistently - leaving out the ellipsis in the Gloss, etc. But from my point of view, recommending this practice would also raise awareness of the fact that the ellipsis is part of the example, and must be considered for consistency.

That's a very reasonable solution, works for me.
Should None in tab-delimited columns raise a validation error?

Should None in tab-delimited columns raise a validation error?

Yes, I would say so. After all, one of the main reasons for using ellipsis for unglossed words is that we get lists of str for both aligned properties.

Yes, I would say so. After all, one of the main reasons for using ellipsis for unglossed words is that we get lists of str for both aligned properties.

Maybe we could keep some sort of backwards compatibility (with somewhat undefined bahaviour) by converting None to ellipsis upon reading.


feat: support remote $refs in dialog schema.

Description
Resolve remote $refs when reading dialog schema. Note: this does not support relative file $refs at this time.
Task Item
closes #8271

Coverage increased (+0.02%) to 55.842% when pulling 42e235a3dea4275cd7d4ab2a01782cc991be03b1 on abrown/dialog-schema-rel-refs into 3eeeccc3006db1cd9ef76f577c56a3ec4bad2321 on main.


fix: using --release/debug and --profile together becomes an error

What does this PR try to resolve?
part of #13629
issue https://github.com/rust-lang/cargo/issues/13629#release-is-ignored-when-paired-with-profile

Is there something this PR is waiting on for why it is a Draft

Is there something this PR is waiting on for why it is a Draft

Sorry, I thought there would be some documentation that would need to be changed, but it doesn't seem to be there when I looked today.

Should we leverage clap's conflict support?  We likely would need validation lower level like this.  Unsure which style of error messages we'd prefer.
    fn arg_release(self, release: &'static str) -> Self {
        self._arg(
            flag("release", release)
                .short('r')
+              .conflicts_with("profile")
                .help_heading(heading::COMPILATION_OPTIONS),
        )
    }
...
        .arg(flag(
            "debug",
            "Build in debug mode (with the 'dev' profile) instead of release mode",
-        ))
+       ).conflicts_with("profile"))

You don't need to put it on --profile.

Should we leverage clap's conflict support? We likely would need validation lower level like this. Unsure which style of error messages we'd prefer.

This sound better and we can remove most of those tests. (maybe leave one for preventing regression?)

@bors r+
Thanks!

:pushpin: Commit 5d8022c9e82490347a732834809106bdf8777616 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 5d8022c9e82490347a732834809106bdf8777616 with merge 580dbc602bcbbeeebefeb04dea3e4d6b0572958c...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 580dbc602bcbbeeebefeb04dea3e4d6b0572958c to master...


feat: show works using new recs model for the new works for you

This PR resolves []
Description

Show works using new recs model for the new works for you

https://user-images.githubusercontent.com/11945712/213172864-14bc754a-7c92-485b-b9f2-c2054184c8a4.mov
PR Checklist

[x] I tested my changes on iOS / Android.
[x] I added screenshots or videos to illustrate my changes.
[x] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[x] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

show works using new recs model for the new works for you - mounir

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

@olerichter00 I forgot to link the ticket. will do it now

Thanks for the quick review @olerichter00 . Very appreciated


Removing invalid fallback helpUri

https://github.com/microsoft/sarif-js-sdk/issues/89
Please see details in message is not a valid URI.

@scalvert - What do you think?

@microsoft-github-policy-service agree company="Datadog"


Testing on multiple client request

Hello Everybody !
I'm looking for testing GraphQL Apollo request in case of multiple client.
Project are based on micro service architecture so there are many client.
In the component, i wrote : this.apollo.use('domain_1'), that's works fine !
https://www.apollographql.com/docs/angular/features/multiple-clients/
But my problem concerns of testing this component !
In my case i would like to test my request on 'domain_1' client.
Here's the error : "TypeError: Cannot read property 'query' of undefined"
I don't know how to mock the "use()" function of Apollo. Use() is undefined !!!
Component :
`public callDummyAPI(): any {
    apollo.create({
      link: httpLink.create({ uri }),
      cache: new InMemoryCache(),
    });
    return this.apollo.use('domain_1').query<QueryType>({
      query: MY_QUERY,
    })
    .pipe(
      map(result => result.data.hello)
    );
  }`

Test component :
`it('should test search', (done) => {
    const fixture = TestBed.createComponent(DummyComponent);
    const component = fixture.debugElement.componentInstance;
    component.callDummyAPI().subscribe(result => {
      expect(result).toEqual('tetete');
      done();
    });
    controller.expectOne('/', MY_QUERY).flush({
      data : {
        hello: 'tetete'
      }
    });
  });`

Does anyone knowing to resolve this problem ?
Thank you very much in advance.
Val

Same problem for me +1

Solution not perfect but it's works:
 .....
 import { ApolloTestingModule, ɵa as ApolloTestingBackend } from 'apollo-angular/testing';
 .....

 let apollo: Apollo:
 let backend: ApolloTestingBackend;

 beforeEach(() => {
    TestBed.configureTestingModule({
      providers: [
        ...
      ],
      imports: [
        ...
        ApolloTestingModule,
      ],
    });

  apollo = TestBed.get(Apollo);

  apollo.createNamed(ApolloClientName.API_V2, {
        link: new ApolloLink(operation => backend.handle(operation)),
        cache: new InMemoryCache({
          addTypename: false,
        }),
      });

  apollo.use(ApolloClientName.API_V2);

  });
....

Hi,
Apologies for hijacking the thread, However there is no correct sample it seems which shows the apollo.createNamed scenario.
We also do have multiple micro-services and hence need to connect to multiple clients.
Also on top of that, we are using NestJS
NestJS, allows us to inject the httplink using Factory provider,
Inside AppModule providers:[]
useFactory: (httpLink: HttpLink) => {
                return {
                    cache: new InMemoryCache(),
                    link: httpLink.create({
                        // uri: config.servicesBaseUrl
                        uri(operation) {
                            if (!operation.operationName) {
                                return config.servicesBaseUrl;
                            }
                            return operation.operationName.toLowerCase() === 'login'
                                ? config.servicesLoginUrl
                                : config.servicesBaseUrl;
                        },
                    }),
                };
            },](url)

However we are not able to do so with the ApolloLink.from OR apollo.createNamed ,
It would be good if someone can suggest how to achieve this with the NestJS.
Thanks

#1365 will enable to test named clients

Released v1.8.0 - check out "Testing named clients" in docs