fix illustration is sitting too far down

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/38594#issuecomment-2063503322
PROPOSAL:
Tests

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

Offline tests

QA Steps

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

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

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

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

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

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/113963320/d950e3a1-dea1-48a1-b0d4-44e1e50f17d2

Android: mWeb Chrome

https://github.com/Expensify/App/assets/113963320/6da42b17-25a8-4425-9e90-e2a9ca7e6387

iOS: Native

https://github.com/Expensify/App/assets/113963320/5a0f37cb-4c76-4efe-a546-7f15fbad2b13

iOS: mWeb Safari

https://github.com/Expensify/App/assets/113963320/1632b708-85db-4b6e-be26-b3db535feffb

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/113963320/3de44ff5-9505-4145-8977-7e61f1b70bc9

MacOS: Desktop

https://github.com/Expensify/App/assets/113963320/49f1aba3-da39-49b7-8a8c-43c85db5c57f

Are you sure we need a new file? I feel like we wanted the illustration to sit downwards on all platforms, so why can't we address this with styles but use those same styles everywhere?

Can you elaborate on why the style failed on iOS though? Can we try something different that might work everywhere?

Sorry was busy with other issue, I will catch up with this and leave my feedback soon

Looks like we are in dead end. I am really confused on root cause of this and why it is only happening in troubleshooting page. But comparing it directly to other pages is also misleading since each page is utilizing different illustration with different sizes and animations.
@tienifr If we were to replace the file what exactly should be different in it?

Hmm before replacing the file, I'm mostly interested to understand why the negative margin isn't working on iOS, as it seems to work fine on other platforms?

No, I am really confused on what should be our next step. As I understand we are not sure on exact root cause here?

@tienifr Yes, go head please

Reviewer Checklist

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

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

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

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

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

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

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

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

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

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

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

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(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 form input styles:

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

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

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 production by https://github.com/luacmartins in version: 1.4.81-11 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Don't double-free an UnparsedSource

github.com/containers/image/image.FromUnparsedImage() "takes ownership" of the UnparsedImage that we pass to it, so we shouldn't also Close() the UnparsedImage ourselves after we've wrapped it up in an Image object.
Since creating an Image is the only thing we do with the UnparsedImage after creating it from a SourceImage, just use the FromSource() function to handle both steps at once.

LGTM

Looks good. Need to wait for tests.


names of jitted functions not shown in repr

In [1]: import jax.numpy as jnp
In [2]: jnp.dot
Out[2]: <CompiledFunction at 0x7f9fc7213c80>

re-landed in #8185


solc: 0.8.19 -> 0.8.21

Description of changes
closes https://github.com/NixOS/nixpkgs/issues/255482
change log: https://github.com/ethereum/solidity/releases/tag/v0.8.21
diff: https://github.com/ethereum/solidity/compare/v0.8.19...v0.8.21
removes tests patch as it no longer seems required for the derivation to build successfully

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

[ ] 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.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

solc

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

1 package built:

solc

https://github.com/NixOS/nixpkgs/pull/255581/commits/66867a88354d9db75a72e0d1460b1437f12ed5df fixes the hash issue on darwin.


refact fix: Flatpak

Type of Change

[ ] New feature
[x] Bug fix
[ ] Documentation update
[x] Refactoring
[ ] Hotfix
[ ] Security patch
[ ] UI/UX improvement

Description

Moved flatpak handling to common-script due to path conflicts when setup-flatpak is called from different tabs.
The following error was reproduced by removing the pacman installation section, forcing the script to use flatpak for installation:

[!NOTE]
This issue was originally identified on another laptop running openSUSE. Since no screenshots were captured in openSUSE, the workaround was applied to reproduce the error.

Testing

Tested on arch and openSUSE, works as expected.

Additional Description

Office script is excluded from this PR as it requires a rework. It should be split into separate scripts for better maintainability.
This implementation is basic and can be improved in future.

Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no errors/warnings/merge conflicts.

@jeevithakannan2 this is going to break a lot of things and this is bloating up common script, you're doing too much here man, literally its a 1 dot fix...

setup-flatpak is in the dir before zoom... just add an extra dot, why are you adding all of this bloat into linutil?

DONT merge this yet, needs more discussing, this implementation is a bit dirty and i feel like we can just combine the flatpak command_exists with the reg one

It's tricky to implement it that way. I tried multiple ways and came up with this just for now. This is a basic implementation and can be changed in future !!

if any other scripts use flatpak be sure to include these changes

Included all the scripts except office setup. It needs a rework splitting them would be better for maintaining the code

DONT merge this yet, needs more discussing, this implementation is a bit dirty and i feel like we can just combine the flatpak command_exists with the reg one

Combined both


add hide_chat_border to config

This will add the undocumented option hide_chat_border to config, I was not aware of it until I searched through the issues.
Thanks.

Thanks for bringing this up. I've gone through the default config and found that tick_config is also not a thing that exists, but it should be delay. I'll commit that after this.


fix description of openapi-chat  in upgrade-notes

Motivation:
There are some incorrect descriptions and 404 page-link in the https://docs.spring.io/spring-ai/reference/upgrade-notes.html, and I have made some modifications based on the code and the configuration page on the official website.
Other
Thank you for taking time to contribute this pull request!
You might have already read the [contributor guide][1], but as a reminder, please make sure to:

Sign the contributor license agreement
yes, done

Rebase your changes on the latest main branch and squash your commits
yes,done

Add/Update unit tests as needed
fix document, not nedd

Run a build and make sure all tests pass prior to submission
fix document, not nedd

Thanks @laglangyue


[link-raw] log frame tx attempt failures

This commit adds logs to indicate frame tx attempt failures on
LinkRaw class for RCP model.

LGTM!


bug?

I'm not sure if I'm misunderstanding something, or if I've discovered a bug. But I got a small code example to reproduce it:
We start with these data:

y/x
0
1
2

2
n
5
n

1
0
n
n

0
1
n
n

from pykrige.ok import OrdinaryKriging
import numpy as np
import pykrige.kriging_tools as kt
z = [[0,0,1],
     [0,1,0],
     [1,2,5]]
data = np.array(z)
gridx = np.arange(0.0, 2.1, 0.5)
gridy = np.arange(0.0, 2.1, 0.5)
OK = OrdinaryKriging(data[:, 0], data[:, 1], data[:, 2], variogram_model='linear',
                     verbose=False, enable_plotting=False)
z, _ = OK.execute('grid', gridx, gridy)
kt.write_asc_grid(gridx, gridy, z, filename="output.asc")

I would assume the output would be (preserving the three original values, with interpolated x values):

y/x
0
0.5
1
1.5
2

2
x
x
5
x
x

1.5
x
x
x
x
x

1
0
x
x
x
x

0.5
x
x
x
x
x

0
1
x
x
x
x

But the output file contains the following:
NCOLS          5
NROWS          5
XLLCENTER      0.00
YLLCENTER      0.00
DX             0.50
DY             0.50
NODATA_VALUE   -999.00
2.67            5.00            2.67            2.53            2.44
2.28            2.29            2.28            2.25            2.23
1.86            -0.00           1.86            1.96            2.02
1.62            1.54            1.62            1.74            1.83
1.50            1.00            1.50            1.60            1.69

From my interpretation of this, the original values have all been placed at X=0.5

Well that's really weird. The problem is that your data array is an array of integers. I tried to recreate your problem: by making the data array an array of floats, I recover the correct answer, but by making that array all integers, I get the (wrong) answer that you got. I'm not sure why this is happening. Probably something weird happening with ints vs. floats deep in the code that I didn't anticipate. Are you using Python 2.x? In the mean time, I'd say just make sure you're working all with arrays of floats. But thanks for bringing this to my attention, I'll have to look into this more.

This was addressed in PR #47, so closing the issue.


Configure whether tax should be based on gross or net prices

Describe the solution you'd like
A simple configuration key for defining if the tax should be calculated on a product's gross or net price.

Related to #26


[Vote] Keep support for C++ Network Library

Currently, ppconsul supports either of two network libraries: libCURL or C++ Network Library. I'm thinking about dropping support for the latter one to simplify adding of TLS support (#12).
Before getting rid of C++ Network Library support I'd like to know how harmful it will be for ppconsul users. Thus I'm asking for feedback on this.
If you use ppconsul with C++ Network Library and have a reason to avoid switching to CURL then please vote for this ticket. I will appreciate if you also add a comment why do you need/want to use a C++ Network Library instead of CURL.

I have just recently started using this library and libcurl has been sufficient.

+1 to no boost, libcurl works for me.

+1 to no boost, libcurl works for me.

Actually this is not bad idea. Since boost is included all networking (and support also) should go throw boost libraries.

@d36u91 Actually this is not bad idea, since boost is already part of project. Json11 and libb64 libraries also can be replaced with boost counterparts.

C++ Network Library is finally removed. Now user can implement its own HTTP client implementation if default one based on libcurl does not work for them.


Master

Fixed package_data configuration to include py.typed
What was wrong?
How was it fixed?
Cute Animal Picture

Yeah, this is not ready for review. It doesn't do what it says it does. It also doesn't include any commits by you which is unusual. Feel free to reopen if you can explain what was wrong, and how you fixed it. (in the summary sections of the PR)


Removing armv7 support and bumping version to 1.0.2

Codecov Report

Merging #6 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage   71.78%   71.78%
=======================================
  Files          17       17
  Lines         638      638
=======================================
  Hits          458      458
  Misses        180      180

Impacted Files
Coverage Δ

Code/Extensions/SwiftUIView+TypeErasure.swift
100.00% <ø> (ø)

Code/Protocols/MVVM/Router+MVVM.swift
40.00% <ø> (ø)

Code/Protocols/Routable.swift
0.00% <ø> (ø)

...tensions/NavigationRouter+NavigationHandling.swift
32.58% <ø> (ø)

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 5b6e3e2...aebdcd6. Read the comment docs.


README update

Write content on how extension is automatically updated from the Chrome webstore.
Connect with either Vishal or Pranjal on Whatsapp group for hacktoberfest https://chat.whatsapp.com/FGZcPzZr1J9FIcdVnkSyYefor details.

the WhatsApp link is mentioned twice - unable to open it sir

I'm Interested on working on this issue

Closing due to inactivity.


loadConfig swallows errors

finally in loadConfig (config package) swallows any errors thrown within try block, if finally itself errors

solved with { force: true } in #804


Move openassetio to requirements.txt

What
Remove openassetio from setup.py /pyproject.tomland move to arequirements.txt`
Why
Otherwise installing BAL breaks the execution environment as the pin will transparently uninstall any other version already installed (eg integrations.yaml)
ACs

Docs (installation and test instruction) updated as required.

Fixed in #32


Add a request rate limit for embeddings model

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windows 11
- Continue version: 0.8.57
- IDE version: VS Codium
- Model: Mistral Embed API

Description
So my embeddings settings look something like this:
config.ts
mistral_embeddings: {
    model: "mistral-embed",
    apiKey: apiKeys.MISTRAL,
    maxChunkSize: 2048,
    maxBatchSize: 16,
    requestOptions: {
      timeout: 1001
    },
    provider: "mistral",
    apiBase: "https://api.mistral.ai/v1"
  },

When using this configuration to generate embeddings, I get this console msg:
[Extension Host] error when indexing:  Error: Failed to generate embeddings for 129 chunks with provider: MistralEmbeddingsProvider::mistral-embed::2048: Error: {"message":"Requests rate limit exceeded"}
  at LanceDbIndex.getEmbeddings (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:175314:17)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async LanceDbIndex.computeRows (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:175262:28)
  at async LanceDbIndex.update (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:175418:24)
  at async CodebaseIndexer.indexFiles (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:540456:39)
  at async CodebaseIndexer.refresh (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:540328:30)
  at async Core.refreshCodebaseIndex (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:541322:26)

Same issue I am facing in voyage too:
[Extension Host] error when indexing:  Error: Failed to generate embeddings for 271 chunks with provider: VoyageEmbeddingsProvider::voyage-code-2: Error: {"detail":"You have not yet added your payment method in the billing page and will have reduced rate limits of 3 RPM and 10K TPM.  Please add your payment method in the billing page (https://dash.voyageai.com/billing/payment-methods) to unlock our standard rate limits (https://docs.voyageai.com/docs/rate-limits).  Even with payment methods entered, the free tokens (200M tokens for Voyage series 3) will still apply. See our pricing docs (https://docs.voyageai.com/docs/pricing) for the free tokens for your model."}
	at LanceDbIndex.getEmbeddings (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:175314:17)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async LanceDbIndex.computeRows (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:175262:28)
	at async LanceDbIndex.update (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:175418:24)
	at async CodebaseIndexer.indexFiles (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:540456:39)
	at async CodebaseIndexer.refresh (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:540328:30)
	at async Core.refreshCodebaseIndex (c:\Users\Lakshit\.vscode-oss\extensions\continue.continue-0.8.57-win32-x64\out\extension.js:541322:26)

So i request you to resolve this. Thanks!
Also btw, is there a way to index the contents ? I just read the difference between indexing and embedding and would love if my model know where a particular function is used etc and that seems to be done by indexing maybe??

I think that the solution will have to be increasing rate limits in this case

No the mistral embed has 1 request per second limit and its context length is 32k tokens so I guess this will work pretty well if i send requests within limits


HTML Preview: Fix Iframe auto-resize

This fixes #379
This PR prevents content overflowing out of an iFrame by setting
How to Test
Open two separate ChatCraft conversations and supply one prompt to each:

First conversation: Show me a few example HTML pages with Plotly.js
Second conversation: Show me three example HTML pages of varying sizes

Explanation
By default, the IframeResizer heightCalculationMethod option calculates the iFrame height by converting the body margin to px then adding the top and bottom figures to the body tag's offSetHeight (bodyOffSet).
With this default heightCalculationMethod, HTML content tends to overflow outside the body:

There are four main values for heightCalculationMethod:

bodyOffset uses document.body.offsetHeight
bodyScroll uses document.body.scrollHeight
documentElementOffset uses document.documentElement.offsetHeight
documentElementScroll uses document.documentElement.scrollHeight

A heightCalculationMethod value of max uses the largest value of the above 4, preventing overflow:

To keep or remove scrolling
I've experimented with other values for heightCalculationMethod. For example, bodyScroll also prevents text overflow, but when ChatCraft generates HTML pages with Plotly.js, scroll-bars are added to the preview. Using heightCalculationMethod={max} prevents both of these from happening.
Using max will render entire HTML previews, making scrollbars unnecessary. It is important to note that the default setting, bodyOffset, already renders ~95% of an HTML preview body.
We must determine whether we want to render entire IFrames, or add a maxHeight property to the Iframe to make scrollbars necessary.
However, in my tests, adding a maxHeight property to the IFrame allows text overflow/cutting off

Very good explanation.
If user inputs a very long HTML page, should we preview all the HTML page or provide a scrollbar if the height is bigger than a value?

Very good explanation. If user inputs a very long HTML page, should we preview all the HTML page or provide a scrollbar if the height is bigger than a value?

If we provide a scrollbar after a maxHeight threshold, we risk the last line of text being cutoff at that maxHeight.
Currently, a user's long messages are treated with the "Show More/Show Less" buttons, see here for an example.
It looks like very long HTML code from ChatCraft's responses is already given this treatment, as seen here:

, based on the 5000 character threshold in MessageBase.tsx
https://github.com/tarasglek/chatcraft.org/blob/a1ab66515a39e06684cc455a36263c67c95f5f33/src/components/Message/MessageBase.tsx#L117

I like the "Show More..." UI taking over for really long content.  Let's not do a scrollbar.

@rjwignar  Your screenshot "Show more" is perfect, but my test show all the html code and preview page. Maybe it's because the HTML page is long, but it hasn't exceeded the word limit we set.
https://cc8cd9a7.console-overthinker-dev.pages.dev/c/chatcraft_dev/Lg8_sJvyWuPWwrAcPi2Kl

@WangGithub0 we added a fix to not hide long messages when they are the last message.  The idea being that whatever you just asked the LLM about, you are going to want to see it.  If you add another message to that chat, it should shrink the long HTML+Preview.

@WangGithub0 we added a fix to not hide long messages when they are the last message. The idea being that whatever you just asked the LLM about, you are going to want to see it. If you add another message to that chat, it should shrink the long HTML+Preview.

Yes, it make sense. After adding a new message, it still shows all the html code and preview page:
https://cc8cd9a7.console-overthinker-dev.pages.dev/c/chatcraft_dev/awjajAaEyfB4KP6jFz4Pb

cc @mingming-ma, what do you think about @WangGithub0's findings in https://cc8cd9a7.console-overthinker-dev.pages.dev/c/chatcraft_dev/awjajAaEyfB4KP6jFz4Pb (e.g., it's not the last message, and not using Show More...)?

Yes, it make sense. But after adding a new message, it still shows all the html code and preview page:
https://cc8cd9a7.console-overthinker-dev.pages.dev/c/chatcraft_dev/awjajAaEyfB4KP6jFz4Pb
should we also consider about the height, not only the word number for html?

cc @mingming-ma, what do you think about @WangGithub0's findings in https://cc8cd9a7.console-overthinker-dev.pages.dev/c/chatcraft_dev/awjajAaEyfB4KP6jFz4Pb (e.g., it's not the last message, and not using Show More...)?

After check, here is my findings: it's not the last message, and not using Show More, This is only happening at the first time of this chat. i.e. an interactive way messaging on and on, user will see the previous last massage still expanded. I think it might be good to let user see the last message unchanged for not being distracted.
And when user open the chat again from Saved Chat or get it from a shared link, all long message is folded except the last one.
How do you think about this behaviour? Should I do always collapse the reviewed message?
@WangGithub0 's  example does not show the button. This is because the message's height is huge, however the characters are still within the threshold. It depends on how LLM response, for the height checking , maybe continue checking the '\n' including in long message would impact the performance. Let me know if there are better way to fix this situation.


Version stucked at 0.97.6 in NUGET

Description
Presently, it seems as the latest materialize version in NUGET (VS2017 ) including prerelease is stucked to 0.97.6.
Is there any plan to FIX this or is this normal behavior ?
Repro Steps
Not related
Screenshots / Codepen
nuget-materialize-stucked-in0 97 6

We don't officially support a nuget version. This must be a thirdparty nuget thingy

Thanks,
It was a wee bit confusing as far as he was referring to the official website.
So the only way to include the official version for now is to download directly from the official website right ?
There is no plan to make the it accessible in NUGET ?
In fact, we are testing frameworks to compare which one to use in a project and yours seems to be winner.
Realy thanks.

Can you post a link to that nuget package? I can look into it, but promise nothing

Sure here are the info when you look through NUGET:
materialize 0.97.6: https://www.nuget.org/packages/materialize/0.97.6
Licence: https://github.com/Dogfalo/materialize/blob/master/LICENSE
Project URL: http://materializecss.com/ . This is the weird part !
Here is how it looks in VS

I don't have a nuget account, but you could  try to contact the creator of this package.

Sure,
I will download it in the official website for now while waiting to see if he can update the package.
But i think you shouldn't allow someone re-using the official framework name like this without specifying if it is a fork or just a way to make it accessible on any platform. In fact we was blaming the official team and it appeared really weird to us because everything was pointing to the official website and github repo.
Thanks a lot for this quick and efficient replies.


TypeMapping: Fix #8010 - Add very simple "type mappings" for non-relational providers

Lifts concept of "mappability" to core.

Removes derived relational conventions that decided mappability via IRelationalTypeMapper - can now be handled by core conventions.
Many code quality fixes.

@lajones Heads up on this one as it will likely require a merge with your work.


fix(tanstack-start): Load router after updating context

Description
This PR brings back the router.load after the context is updated in the middlewareHandler

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

!snapshot

Hey @octoper - the snapshot version command generated the following package versions:

Package
Version

@clerk/astro
1.4.2-snapshot.v5ba8be5

@clerk/backend
1.15.2-snapshot.v5ba8be5

@clerk/chrome-extension
1.3.24-snapshot.v5ba8be5

@clerk/clerk-js
5.30.0-snapshot.v5ba8be5

@clerk/elements
0.17.2-snapshot.v5ba8be5

@clerk/clerk-expo
2.2.30-snapshot.v5ba8be5

@clerk/express
1.3.4-snapshot.v5ba8be5

@clerk/fastify
2.0.6-snapshot.v5ba8be5

@clerk/localizations
3.4.1-snapshot.v5ba8be5

@clerk/nextjs
6.0.3-snapshot.v5ba8be5

@clerk/clerk-react
5.13.2-snapshot.v5ba8be5

@clerk/remix
4.2.42-snapshot.v5ba8be5

@clerk/clerk-sdk-node
5.0.55-snapshot.v5ba8be5

@clerk/shared
2.10.2-snapshot.v5ba8be5

@clerk/tanstack-start
0.4.18-snapshot.v5ba8be5

@clerk/testing
1.3.16-snapshot.v5ba8be5

@clerk/themes
2.1.40-snapshot.v5ba8be5

@clerk/types
4.29.0-snapshot.v5ba8be5

@clerk/ui
0.1.11-snapshot.v5ba8be5

@clerk/upgrade
1.2.0-snapshot.v5ba8be5

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro
npm i<EMAIL_ADDRESS>--save-exact

@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/express
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/tanstack-start
npm i<EMAIL_ADDRESS>--save-exact

@clerk/testing
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

@clerk/ui
npm i<EMAIL_ADDRESS>--save-exact

@clerk/upgrade
npm i<EMAIL_ADDRESS>--save-exact

@octoper What was the reason for reverting this? load() is causing route loaders to run twice, as its already called internally. In my testing removing it doesn't cause any issues and the clerk state is available without it.


Why are dependencies in requirements.yaml packaged in the charts directory?

My apologies if this question has already been asked.  I'm using helm 2.9.0
I have a chart, A, that has dependencies on charts B and C, both of which depend on chart D. All the dependencies are expressed in the requirements.yaml for each chart.  All the charts have been packaged and pushed to a Chartmuseum repo. To test the charts it seems you have to run helm dep up  first, which pulls the dependencies into the charts directory. When you then package the chart the full content of its dependencies get packaged with it.  Therefore the package for Chart A physically contains 2 copies of the D chart (1 each for B and C).   This is a pain during development.  If I make a change to D then I have to not only re-package D, but also repackage everything that depends on D e.g. A, B and C.
Coming from the Java/Maven world I would have expected that the dependencies in the requirements.yaml file would be pulled at install time into a temporary workspace along with all of the transitive dependencies such that when D changed all I need to do is re-package and re-push D in order for installs of A, B and C to pick up the changes.  Am I missing something here?  Seems like a very inefficient way to handle dependencies.
Your response might be that if D needs changing then the D chart should get a new version, followed by changing the dependency version in B and C (which themselves should be versioned) resulting in changes to A as well.  Still have to re-package everything.

Hi @RudyBone
Sorry for the pain but charts are duplicated in the way you described. There is a relative file:// option for dependencies that would allow you to keep them separately if that helps.

Can you point me to an example of how to use the file:// option?  Does it go in the requirements.yaml?

Yes it goes in the requirements.yaml file. Here is some more info.

Closing due to inactivity. Please open a new ticket against Helm 3 if this issue persists. Thanks!


What is the Azure Synapse permission required for an identity to read?

What level of Azure Synapse permission required for an identity such as user or service principal to read the data from Azure Synapse.
The following section only lists the writes permission
https://learn.microsoft.com/en-us/azure/databricks/external-data/synapse-analytics#required-azure-synapse-permissions

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

ID: 358fe757-e92a-30d5-300b-2911e18dfd4c
Version Independent ID: 358fe757-e92a-30d5-300b-2911e18dfd4c
Content: Query data in Azure Synapse Analytics - Azure Databricks
Content Source: databricks/external-data/synapse-analytics.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@subashsivaji
Thanks for your feedback! We will investigate and update as appropriate.

@subashsivaji
To read data from Azure Synapse, an identity such as a user or service principal requires the Synapse Reader role. This role grants read access to Synapse workspaces, SQL pools, and data flows.


Expected signing entity verification

This allows clients to pass in a dictionary with expected signing entities that SwiftPM will check after loading the package graph. This can be used by clients to provide a priori configuration of expected signing by the user or provide a way to verify that information that was previously shown to users matches what was verified during signature verification.
Note that since this operates at the workspace level, we're verifying against the data cached during signature verification, not against the actual data.
rdar://107162424

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci smoke test macos

@swift-ci test windows


Problem with mapper evaluation example?

Following the example verbatim at http://rnftools.readthedocs.io/en/latest/tutorial/03_evaluation.html#basic-example
$ snakemake
Nothing to be done.

Is there an error in the example code?

Oops, disregard.  It was just an issue with code copy+paste from webpage.


Debug-printing geometries segfaults

Something like:
fn main() -> Result<()> {
    let args = std::env::args().collect::<Vec<_>>();
    let point_ds = Dataset::open(&args[1])?;
    let mut layer = point_ds.layer(0)?;
    for feature in layer.features() {
        dbg!(feature);
    }
    Ok(())
}

crashes with:
[src/main.rs:17] feature = Feature {
    _defn: Defn {
        c_defn: 0x0000562e86c81c80,
    },
    c_feature: 0x0000562e86c85d60,
    geometry: [
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/gdal-0.14.0/src/vector/geometry.rs:177:38
stack backtrace:
   0: rust_begin_unwind
             at /rustc/efd27454ae94386e11997b1158f60d3a79deeb7d/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/efd27454ae94386e11997b1158f60d3a79deeb7d/library/core/src/panicking.rs:64:14
   2: core::panicking::panic
             at /rustc/efd27454ae94386e11997b1158f60d3a79deeb7d/library/core/src/panicking.rs:114:5
   3: gdal::vector::geometry::Geometry::wkt
   4: <&T as core::fmt::Debug>::fmt

@lnicola Was going to replicate on MacOS. Can you share the input file?

It happens with any input, like the sample from https://github.com/ngageoint/GeoPackage/blob/master/docs/examples/java/example.gpkg.

Not really the problem, but calling unwrap seems like a bad idea?
https://github.com/georust/gdal/blob/c7f88b56a855cfdff44267009f2ad1730cd03b14/src/vector/geometry.rs#L177

@lnicola I wonder if this (foreign_types) or something like it might be worth considering. I think we need some principled semantics around these GDAL pointers, Rust has all the type machinery we need, we just need to find good examples of how to do this properly or rely on a library that does it for us.

Still haven't looked into it, but I think we handle layers in a better way, that could serve as inspiration.

I have foreign_types prototype here: https://github.com/georust/gdal/compare/master...metasim:gdal:prototype/foreign_types
Personally, once I converted a couple types, I really liked it (except the paucity of documentation), especially since it explicitly distinguishes owned vs. borrowed types. However, there would be several breaking changes.


Adding compat

Adding compatibility from https://github.com/OpenModelica/OMJulia.jl/commits/maintenance/v0.2.0 to register package.
Also remove latest update to version in Project.toml.
Also fixes https://github.com/OpenModelica/OMJulia.jl/issues/69.

The Jenkins CI + Dockerfile with Julia 1.0.3 was failing during the test, because of some strange compatibility issue.
It didn't happen to me when I run the Docker image locally, only when running it on a PR.
@sjoelund What do you think? Should we switch from the Jenkins CI to GitHub Action?
It is more flexible and allows us to test arbitrary Julia versions on Linux, Windows and as soon as we have OpenModelica available on Mac (and setup-openoodelica supports it).
The Windows tests are of course way slower than the Linux tests, because the Windows installer is huge. On the next run it should be a bit faster, because the Windows installer will be cached.

Also @sjoelund would need to change the required tests from Jenkins to Test.yml for this PR to be merged.


New package: CoverageCore v0.1.0

Registering package: CoverageCore
Repository: https://github.com/JuliaCI/CoverageCore.jl
Created by: @DilumAluthge
Version: v0.1.0
Commit: c8e548e629aeea01ec3a5f1d3e5f2127f9be5578
Reviewed by: @DilumAluthge
Reference: https://github.com/JuliaCI/CoverageCore.jl/commit/c8e548e629aeea01ec3a5f1d3e5f2127f9be5578#commitcomment-35516263

Your new package pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request after the mandatory waiting period has elapsed.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

The mandatory waiting period has elapsed.
Your pull request is ready to merge.
I will now merge this pull request.

[noblock]


[Feature][Catalog] Add InMemoryCatalog for test and add new getCatalogTableFromConfig method

Purpose of this pull request

Add new getCatalogTableFromConfig method, so that we can directly get CatalogTable from source config. It will be used when refactor Catalog for move create CatalogTable logic to TableSourceFactory instance.
To prove new method can work fine, add test suite InMemoryCatalog, after this we can test catalog without any third party database.

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Is this not triggering CI?


README: rename DronecodeSDK to MAVSDK, fix badges

Now that DronecodeSDK has been renamed to MAVSDK and has been moved to the mavlink GitHub org, we need to fix the README and badges to reflect this change.

@JonasVautherin I've removed the WIP bot because we now have GitHub draft pull requests.
The rest of the CI integrations should hopefully work again after the name change.


make tslib imports shakable

TypeScript Version:  2.4.1
when I use ts with config like:
{
  "compilerOptions": {
    "experimentalDecorators": true,
    "importHelpers": true,
    "module": "esnext",
    "noEmitHelpers": true,
    "target": "esnext"
  }
}

I notice that it come out with code like this
import * as tslib_1 from "tslib";

It is not good enough for tree-shaking by webpack.
Webpack actually bundle with the entire tslib.es6.js
And it's a bit heavy in my bundle

Expected behavior:
import { __decorate } from "tslib";
// depends on funcitons that actually used with in this file

It should be shakable, as the package.json defines "module": "tslib.es6.js", and uses es6 exports rather than exporting an object. From this perspective, it seems more like a Webpack issue. Have you tried reproducing with Rollup?

@bfricka I think the issue is that import * as tslib_1 from "tslib"; is what is being generated by tsc. Webpack (currently) doesn't know how to shake this. Typescript should emit an import that only includes what that module is actually using.

Totally. I should have read the ticket closer.

That is correct!!! import * is very hard for webpack to try and analyze.
However something like import foo from "tslib/lib/foo" would be far easier to analyze.

Is there anything that would make this unfeasible? It would really be ideal to have only the actually used helpers get bundled by tools like webpack.

@TheLarkInn, just curious, where can users track better tree-shaking for namespace exports in Webpack?

Hi there 👋
We faced this issue this week after using generators with typescript while trying not to blow our size budget.
Below is the workaround I tried.

    // We will need typescript not to inline implementation for __generator
    "noEmitHelpers": true
    // We will need typescript not to import 'tslib' either
    "importHelpers": false,
  }
}

Module using GeneratorFunctions
// import __generator manually
import { __generator as tslib__generator } from 'tslib'
// This is necessary so the above import won't get remove on the compiled version
export const __generator = tslib__generator

export function* helloWorld() {
  yield* "Hello, World!";
}

Output
esm + es2015
import { __generator as tslib__generator } from 'tslib';
export const __generator = tslib__generator;
export function* helloWorld() {
    yield* Array.from('Hello, World!');
}
//# sourceMappingURL=hello_world.js.map

✅ Using any bundler that does support dead code elimination (a.k.a TreeShaking™), it will ignore __generator and tslib since it has not been imported/used.
esm + es5
import { __generator as tslib__generator } from 'tslib';
export var __generator = tslib__generator;
export function helloWorld() {
    return __generator(this, function (_a) {
        switch (_a.label) {
            case 0: return [5, __values(Array.from('Hello, World!'))];
            case 1:
                _a.sent();
                return [2];
        }
    });
}
//# sourceMappingURL=hello_world.js.map

✅ Any bundler will see that __generator is in use and will keep it while ignoring the rest of tslib.
I hope that this will help some of you until we have proper support for tree shaking of importHelpers.

Not sure how tslib could be tree shackable, as long as it does not marked as a sideEffect:false, thus should not be a subject for optimization.

There is a less hacky(in comparison to @fazouane-marouane solution) way to solve the problem

disable importHelpers, let ts inline everything
add runtime-compress-loader loader to your webpack configuration.
it will scan files for ts-helpers signatures, and replace them with corresponding import {helper} from 'tslib', making import tree shakable.

I'd like to clarify some of the requirements for tree-shakable imports:

Which output module kinds should be tree shakable? WebPack seems to only support tree shaking via ES module syntax (import/export), so it seems like this should only be --module es2015 and --module esnext.
Is import { __helper } from "tslib"; enough to be tree shakable, or do there need to be changes made to tslib as well?
The tslib package main export introduces global declarations for each helper to be able to leverage tslib via <script> tags as well as via import. Is that a problem for tree-shakability?

Agreed.
Yes, because tslib has an esm distribution that the bundler will find and use<EMAIL_ADDRESS>No, because the esm distribution doesn't include the global declarations (as far as I can see).

It actually looks like it should be enough to change to the import { __helper } from 'tslib' syntax to start tree shaking the tslib usages. You might have to add a "sideEffects": false but that can be good to do anyway if your esm distribution doesn't cause observable side effects when it is evaluated.

Ditto the above. An tslib build using ESM style imports and exports + "sideEffects": false should be enough for both Webpack 4+ and Rollup.
Webpack:
https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free
Rollup:
https://rollupjs.org/guide/en/#tree-shaking
^ The difference between the two being Rollup will try and determine sideEffects itself while Webpack needs a signal to trigger it's tree-shaking.


Timeout Error

Get this error when creating new project "timeout of 60000ms exceeded". This only happens after updating version to 2.22.

Tracking this in #153


Hardens HTTP integration tests to catch more bugs easier

It was very hard to detect subtle bugs in reactor until I redid the
tests to force us to be conscious of whether a span error is expected or
if we are expecting a remote or local span. Further, this makes sure
these two most difficult to debug things end up with better assertion
failures, including the entire span json. This is super handy when
tests flake due to timing. For example, using a debugger could actually
slow things to the point they pass!

PS I ran these test against armeria and pass all w/o any changes cc @minwoox @kojilin @anuraaga @trustin

ironically the test flake is a good reason why logging span json is helpful. Sometimes things only fail in CI and you'd not know why:
ITTracingAsyncClientHttpRequestInterceptor>ITHttpClient.clientTimestampAndDurationEnclosedByParent:123->ITHttpClient.takeClientSpan:437->ITHttpClient.assertClientSpan:451 Expected span {"traceId":"e7c168c78748af9a","id":"e7c168c78748af9a","name":"test","timestamp":1584667932681036,"duration":12810,"localEndpoint":{"serviceName":"unknown","ipv4":"<IP_ADDRESS>"}} to have kind=CLIENT

latest commit still passes with armeria


UI Refresh: Implement funding rate time period toggle

Description
Allow the user to select from a drop down the time period they wish to view funding rate for


Preview for vertical progress bar broken

Preview of progress bar looks odd as soon as I switch to vertical. The issue can be triggered using any of the samples bundled with skin-composer download.
I'm using recent release 16 on Linux Mint.
I can provide further info and/or a screenshot if required.

I had looked into the folder (e.g. of neutralizer skin) and noticed that there actually are images for vertical scrollbar, so it appeared that the composer failed to apply them. Indeed I overlooked that it keeps displaying "horizontal" postfixed image selection when switched to vertical preview. I assumed that the vertical option was made for that transition, i.e. to tell the composer to apply the image files postfixed "vertical" rather than "horizontal".
Anyway I recommend to do something about it, e.g. have separate fields for vertical image so it can error transparently when vertical option is selected with these fields empty. Or make vertical/horizontal separate classes (not sure right now what the proper way in libgdx-sense is). (I guess this might not only apply to progress bar, but also to scrollbar, maybe slider)
Current behavior can easily look broken, especially to people (like me) who skim through various tools, tying to find a choice.

Unfortunately this is a limitation of LibGDX. Although it makes more sense to me to have the verticle drawables as separate fields, LibGDX doesn't do it that way and thereby Skin Composer has to reflect that. Sorry!


Mount zenml config path as empty dir

Describe changes
To make the helm chart by default compatible with more restrictive cluster security policies that prevent containers from writing to paths that are not mounted as volumes.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

LGTM! for my understanding, is it not good practice to have the container write stuff to ~/.zenconfig within the container and not in a volume? I wasn't aware of this security best-practice, thanks for bringing it forward :)


Bogus glue library

This PR adds a glue library for letting AutoFixture delegating a request to Bogus to create a type.

Gonna add some tests and then merge it in and release it as 2.0 since I dropped supported frameworks like flies


Feature/982 status detail view modal

Style react modal
Style messages

Closing in favour of https://github.com/OpenTechFund/opentech.fund/pull/1056


nixos-install: add --no-local-copy option

Motivation for this change
Fixes #111947
Things done

I tried it in a virtual machine and it seems to work.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Mostly curiosity, no opinions (but maintaining se is hard ...) , Under what scenarios would one see that

installation source is super slow

both internet is much faster than (1), and,

installation target is much faster than (1).

It feels like a very rare case to me and maintaining lines of code, that too of bash is kinda hard ...

Installation source is super slow
The installation source is typically a USB drive, and USB drives are typically quite slow
Internet is much faster than (1)
500+ Mbps broadband is not that uncommon in some places, and often faster than the USB drive
Installation target is much faster than (1)
The installation target is usually an SSD, which is almost guaranteed to be faster than the USB drive.

@jakobrs, wouldn't a reasonable alternative to this be just to launch the installer with the "copy to ram" option? That is typically what I do to avoid sluggishness and accidental usb removal.


Shouldn't the NotOnOrAfter property be based on the NotBefore value?

Given the following SecurityTokenDescriptor I would expect that the default lifespan would ensure that the Time between NotBefore and NotAfter would not exceed 5 minutes, instead it will base the expiration on the current system time unless I set it in the descriptor.
var now = DateTime.Parse('01/01/2011')
new SecurityTokenDescriptor()
            {
                IssuedAt = now,
                NotBefore = now,
                //Expires = now + TimeSpan.FromMinutes(5),
                Issuer = "Test",
                Audience = "testAud",
                Subject = new ClaimsIdentity(),
                SigningCredentials = new SigningCredentials(cert, SignedXml.XmlDsigRSASHA1Url, SignedXml.XmlDsigSHA1Url),
                EncryptingCredentials = new EncryptingCredentials(cert, SecurityAlgorithms.Aes256Encryption,SecurityAlgorithms.Aes256Encryption)
            }

https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/8a6966b0b0d62c1675a557239985b45776ff46de/src/Microsoft.IdentityModel.Tokens.Saml/Saml2/Saml2SecurityTokenHandler.cs#L577

@Tarig0 We think of each of these three values: IssuedAt, NotBefore and Expires as independent. For Saml2, IssuedAt is not used.
A SecurityTokenHandler has these Properties to control behavior:
SetDefaultTimesOnTokenCreation (add times if missing)
TokenLifetimeInMinutes (how long should tokens be valid)
If any of these three are not set on SecurityTokenDescriptor then if SetDefaultTimesOnTokenCreation is true:

Conditions.NotBefore = DateTime.UtcNow
Conditions.NotOnOrAfter = DateTime.UtcNow + TimeSpan.FromMinutes(TokenLifetimeInMinutes)

If you did not set any values in SecurityTokenDescriptor then
NotBefore = UtcNow
NotOnOrAfter = UtcNow + 60 minutes


how to clean jaeger history data in istio

hello,how to clean jaeger history data? i deploy a application in istio,but when i update service,there still some old version history,so i have to delete jaeger pod,:(.
like following, there are same old versions about the same service,but i only want the "eshop" service

so i have to delete pod for jaeger:(
istio-system   istio-tracing-669fd4b9f8-xcbl2            1/1     Running   0          51m

forget the following information
Image:          docker.io/jaegertracing/all-in-one:1.12
istio version:      1.3.3
kubenetes version:     1.14.7

Deleting data is not supported by any Jaeger storage implementations, but many of them do support TTL.


Documentation?

At the risk of stating the obvious, is there documentation on how to use these containers?  I'd have expected something in README.md

https://github.com/ceph/ceph-docker/tree/master/ceph-releases/luminous/ubuntu/16.04/daemon?

That looks pretty reasonable, if I'd had any idea it existed.  I'll file a PR to point noobs to those READMEs

Thanks @dmick


Improve SSLOnlineEvaluator

What does this PR do?
Make SSLOnlineEvaluator supports DDP and checkpoint.

Current SSLOnlineEvaluator does not support DDP. Weights of classification layers are not synced across different processes.
Current SSLOnlineEvaluator will break resume_from_checkpoint functionality of Trainer because SSLOnlineEvaluator add an additional non_linear_evaluator to the main pl_module during on_pretrain_routine_start. This will cause the statedict to mismatch when resume_from_checkpoint.
Both num_classes and dataset arguments can be inferred during runtime. We do not need to pass them in during initialization.
When train the online evaluator, the main pl_module should use eval mode.

This pull request deals with the above mentioned issues.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)

Need to add convert_sync_batchnorm in case a non-linear online evaluator is used.

@zhengyu-yang @ananyahjha93 any progress here? :rabbit:

I have made num_classes  and dataset  optional

@zhengyu-yang @SeanNaren any update here? :rabbit:

@zhengyu-yang @SeanNaren any update here? 🐰
Is there any todo on my side?

Is there any todo on my side?

seems that the GPU tests are failing...

@zhengyu-yang thanks very much for this super helpful change, we need that right now, too!
Just one question around how you designed that: Why are you not loading the state dict of the model/optimizer directly in on_load_checkpoint? Rather, you are saving it in a private member, and only use it in on_pretrain_routine_start. Why is that?


Improve header iconography, color, and layout

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1042
Originally created by @gtsiolis on 2019-09-25 11:48:51

Problem
Currently, the header has a) limited accessibility in terms of color contrast, b) makes it hard to distinguish active menu items, and more.
Proposal
Use better color contrast, iconography, and structure to improve accessibility and usability. The following example uses some of the custom SVG icons from the design system behind GitLab, see gitlab-svgs.

Before
After

View 2 previous comments from the original issue on GitLab

Closing as no longer relevant on account of the removal of the UI for Meltano 3.0


JAV-526 Writing metric data into files

https://servicecomb.atlassian.net/browse/JAV-526

Coverage decreased (-0.3%) to 86.893% when pulling dfdf4e02986598329886e772fda25e67bca75828 on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.2%) to 86.91% when pulling 2c41cbd4ea1b1f5452f179b845737f25d5cd31d0 on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.2%) to 86.933% when pulling e4482cbfdd5f2c7a9934a57d6516f74e7ef74152 on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.3%) to 86.899% when pulling 866a35cfeddc79e0a8d9effc2c4496c89b54c88f on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.2%) to 86.94% when pulling 73038df520e53eee03b9ea9468d1dace23ed95fd on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.2%) to 86.914% when pulling 85dc549e415da056b98ade63b0986d25c4883e1b on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.2%) to 86.927% when pulling 5639977d2c918313b92cdfbfcdde313d5ba007b1 on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

i don't think it's OK
but if we need the metrics output emergency, then merge it. and need to refactor at once.

foundation <- common <- service-registry <- core <-(provider/handler/transport)
this is our dependency order
but now,  foundation depend on core......

Coverage decreased (-0.3%) to 86.902% when pulling 2549eef6095e3161db114ff26f6f53f76acb02ae on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

Coverage decreased (-0.2%) to 86.932% when pulling 25a84212df6059078b497c98ef6bbf46aea8e924 on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

For the dependency issue, foundation <- common <- service-registry <- core <-(provider/handler/transport)
Maybe we introduce an API module to hold the management API that metrics need to use ( I think there could introduce lots of work) , otherwise we just put metrics to the (provider/handler/transport) layer which can have
the dependency of core.

resolved dependency problem of foundation-metrics , current is

io.servicecomb
foundation-common

com.netflix.servo
servo-core

com.netflix.hystrix
hystrix-core

com.netflix.archaius
archaius-core

org.slf4j
slf4j-log4j12
test

Coverage decreased (-0.3%) to 86.892% when pulling 41d75918fb1ba683417180b0fc1bf77b8d599acd on zhengyangyong:JAV-526 into 8eee2a2a4557bd82422205c663d12ca8f118f8eb on ServiceComb:master.

pull latest master from servicecomb and rebase on it

Coverage decreased (-0.2%) to 86.873% when pulling 230bea7efe5e6adf0d9752de196d91e3aff42cb5 on zhengyangyong:JAV-526 into f9bcb13956099df12603c7075b04c5feee3ea874 on ServiceComb:master.

Coverage decreased (-0.1%) to 86.968% when pulling d7695228129b16ffcd478ef4516e684f9d2eff3f on zhengyangyong:JAV-526 into f9bcb13956099df12603c7075b04c5feee3ea874 on ServiceComb:master.

Coverage decreased (-0.02%) to 87.05% when pulling 512aab547ee6184fde48b67d7bce39218a12b153 on zhengyangyong:JAV-526 into f9bcb13956099df12603c7075b04c5feee3ea874 on ServiceComb:master.

Please remember to update the document of how to use it?


"Custom SQL fields cannot contain sub-queries" when using certain SQL keywords in columns

When using the table chart and adding a derived column by using "Custom SQL" and using certain syntax that uses keywords that may be mistaken for a subquery I am unable to use the custom SQL.
How to reproduce the bug

Add any PostgreSQL datasource with a INTERVAL column (duration)
Add a table chart
Add a column with Customer SQL option and the following query:
extract(epoch FROM duration) * 1000
See error:

Expected results
The column should have been calculated since there is no subquery involved.
Actual results
See step 3.
Environment
(please complete the following information):

browser type and version: Firefox 116.0.3
superset version: 2.1.0
python version: 3.8.16
any feature flags active:

FEATURE_FLAGS = {
    "EMBEDDED_SUPERSET": True,
    "DASHBOARD_NATIVE_FILTERS": True,
    "DYNAMIC_PLUGINS": True,
    "DASHBOARD_CROSS_FILTERS": True,
    "THUMBNAILS": False,
    "DRILL_TO_DETAIL": False,
    "VERSIONED_EXPORT": True,
    "ENABLE_TEMPLATE_PROCESSING": True,
    "DASHBOARD_RBAC": True,
    "GENERIC_CHART_AXES": True
}

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
(according to the 2.1.1 changelog this has not been fixed)
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Does the ALLOW_ADHOC_SUBQUERY feature flag resolves your issue?

This is solved issue for me. I was getting this error for druid connection.

Closing this issue as the feature flag seems to resolve it. @fmannhardt feel free to reopen the issue if that's not the case. I authored https://github.com/apache/superset/pull/25161 to include a note in UPDATING.md about the feature flag.


POC snapshot

I don't have write access, had to fork.
This is not meant to be the final PR - for your information only

Implemented in #20


Warn user when using space-separated string with cucumber_opts

Description
Fixes #1614
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds new behaviour)

Please add an entry to the relevant section of CHANGELOG.md as part of this pull request.

Thanks @luke-hill and @valerianb


Demonstrate work-around for singleton pattern.

To test this checkout the singleton-workaround branch and run ./bin/nyc.js node ./singleton-bin.js.  This will output the following:
bin/wrap.js before sw.runMain(): bin/wrap.js
start singleton-bin.js: bin/wrap.js
singleton-bin.js wrote: sub-bin
bin/wrap.js after sw.runMain(): sub-bin
----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |        0 |        0 |        0 |        0 |                   |
----------|----------|----------|----------|----------|-------------------|

This demonstrates the singleton issue by which the value written to singleton-lib.js by nyc is seen by singleton-bin.js at startup, then the new value is seen by nyc after singleton-bin.js exits.
Then run CLEAR_IT=1 ./bin/nyc.js node ./singleton-bin.js to activate the singleton workaround:
bin/wrap.js before sw.runMain(): bin/wrap.js
start singleton-bin.js: undefined
singleton-bin.js wrote: sub-bin
bin/wrap.js after sw.runMain(): bin/wrap.js
----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |        0 |        0 |        0 |        0 |                   |
----------|----------|----------|----------|----------|-------------------|

This shows that when you clear require.cache singleton-bin.js doesn't see the value set by nyc and nyc doesn't see the value set by singleton-bin.js.
In theory spawn-wrap should just completely clear require.cache instead of just removing the script to be run:
https://github.com/tapjs/spawn-wrap/blob/7931ab5ca8732468efb115fc23b89cd7d96c5550/index.js#L445
CC @bcoe

seems reasonable to me, I like the idea of adding a test for this specific category of bug if we do go this route.

Will not be clearing all require.cache as I've found that deleting the main @babel/types source breaks coverage.  Will post a new PR when I'm ready to remove bundling.


no CNA ?

is there any CNA to load ?

I put it in releases. https://github.com/baiyies/ScreenshotBOFPlus/releases/download/build/ScreenshotBOFPlus.zip


[TC-DA-1.4] Script should be updated as per verification Document

From chip-test-scripts created by Rajashreekalmane: CHIP-Specifications/chip-test-scripts#690
Description :
Test Script should be updated as per verification steps.
PFA UI screenshot :

PFA VS screenshot :

@Rajashreekalmane fixed in PR 29727 please verify it and close the ticket.

Issue resolved in latest Image


fix typo leanMore to learnMore

There are several definitions of this name in css that also need to be modified together. E.g: https://github.com/openblockcc/openblock-gui/blob/8fbe8fc77145f2bd3471206ea5cd93041a39b65d/src/components/library-item/library-item.css#L267-L284

I have fixed this problem.


Consider Form Participation?

I know you want to keep this component as lightweight as possible, but it would be nice if it could use the form participation feature of web components. I could then simply place it in a form block, ensure I give it a name, and it would submit it's value when the form is submitted.

I considered this during development, but decided against it.
It can be trivially wrapped in a component that adds form association if you want that. For many people these components will form part of a date picker or some larger component. And usually it's not the calendar you want to submit with the form, but the associated input.
So I'd rather leave the specifics to consumers, who can choose what best suits their needs

Ehhh... I'd argue that form participation isn't trivial - but maybe that was just my experience with it. (I found most of the web component space easy to grok... except for that.) I'm not sure I'd want to add another component to wrap this component though. Anyway, maybe reconsider in the future? :>

Maybe in the future, sure.
I agree form association is complex. Its not complexity I want to take on. You might want to look at the Open WC form participation mixins for an off the shelf integration.
Personally I like the formdata event which is simple to understand, has better browser support, and fits 90% or more of use cases in my experience (I built a whole design system around formdata usage and it worked great).

Cool beans - thanks for the great component - I'm featuring it on my next blog post (that plus 2.99 will get you a cup of coffee.)

Awesome! Please post a link when it's up. Look forward to reading :)

https://www.raymondcamden.com/2024/04/28/links-for-you

I think you can call a web component cute haha. Thanks for the shout out!


Better error message for set_value()

Hi Jonathan
In def set_value(self, obj, new_value), at ../obj_model/obj_model/core.py:3884: ValueError
an example error looks like:
ValueError: Attribute '<wc_lang.core.RateLaw object at 0x7fbb31678a58>' of '<wc_lang.core.RateLawEquation object at 0x7fbb31678b00>' must be None
I think it would be better if the first value was the string value of the attribute and the 2nd was something like the classname, id and name of the Model.
Thanks

More functionally, even a corrected error will not give a user who's not reading obj_model's code much guidance on how to fix the problem.

I can make the error messages a bit more informative, but more is out of
scope.
On Thu, Apr 26, 2018 at 12:38 PM artgoldberg<EMAIL_ADDRESS>wrote:

More functionally, even a corrected error will not give a user who's not
reading obj_model's code much guidance on how to fix the problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KarrLab/obj_model/issues/22#issuecomment-384708146,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACt2KdqRrk1tbdn2qv3uQ5VKzQRhabkgks5tsffqgaJpZM4TlycJ
.

Sure, I realize that. I wrote my comment to document this need for the record.

Implemented in 58a368fe56d00cd05cbcb54914917b49ec38f436


This should show a bit an initial set of CI jobs, makefiles, test example for our charts. Once we're happy with this we can replicate it on all charts (modulo the tests themselves)


cross compile game_of_life example from linux to macos

I would like to use iced for writing utilities which will probably run on MacOS, but I'm on Linux so I'd like to be able to cross compile iced.
Before using iced, I've tried:

https://github.com/fyne-io/fyne
https://github.com/lucor/fyne-cross

which worked pretty well.
Then I would like to find similar things in rust and came across iced. I made a script to cross compile https://github.com/GopherJ/cfg/blob/master/scripts/osxcross.sh, this script worked for some other libraries but I got an error in iced.
   Compiling wgpu-native v0.5.1
error: linking with `x86_64-apple-darwin14-clang` failed: exit code: 1
  |
  = note: "x86_64-apple-darwin14-clang" "-m64" "-L" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.0.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.1.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.10.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.11.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.12.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.13.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.14.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.15.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.2.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.3.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.4.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.5.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.6.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.7.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.8.rcgu.o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.wgpu_native.6kkamhy4-cgu.9.rcgu.o" "-o" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libwgpu_native-259eb0704b182ba7.dylib" "-Wl,-exported_symbols_list,/tmp/rustcJcFFXZ/list" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/wgpu_native-259eb0704b182ba7.2ls74fghvuz96pfl.rcgu.o" "-Wl,-dead_strip" "-dynamiclib" "-Wl,-dylib" "-nodefaultlibs" "-L" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps" "-L" "/home/cheng/Projects/Rust/iced/target/release/deps" "-L" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/build/objc_exception-5b64af16b264bb60/out" "-L" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/build/spirv_cross-2cda498fffa447b0/out" "-L" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libwgpu_core-7a0eb1d2ec16c3e7.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libvec_map-0cdc4d1719aef91b.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libgfx_memory-b0957f5116dad517.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libslab-a8a80358c74b7aaa.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libhibitset-51a8ed710470ef93.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libatom-4e17c0803db55e2a.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libwgpu_types-6b72d275407aeb2c.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libpeek_poke-636dcdf68cfe553c.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libgfx_descriptor-02416bbcba2108f5.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libgfx_backend_metal-fd2d5871df34aa8f.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libstorage_map-8b969022a494c6f5.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libcopyless-11263fcc7f845c81.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libgfx_auxil-40d08a5187d9196d.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libfxhash-401e829a170f5be0.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libbyteorder-ab8d11b47d17436b.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libspirv_cross-60cbb27da3f217dc.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libarrayvec-724353cd69c1d476.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libparking_lot-ddde31b9da9359bf.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libparking_lot_core-bbb77b6192a2bb78.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libsmallvec-b98c81b250f221c1.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/liblock_api-abc2b1410dc340cb.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libscopeguard-2f6bc472ecc1519b.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libmetal-f6a5dc9a853d52f9.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/liblazy_static-e63e0bd2d580c996.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libcocoa-8d9559fa2f0b20c7.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libcore_graphics-c9ef86c602b3f02d.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libforeign_types-484b6ff8f3831cb4.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libforeign_types_shared-07c0f0c2102950eb.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libcore_foundation-34c585b011cd9620.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libcore_foundation_sys-28f40862754da4ca.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libblock-590436d5f0eb89e6.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/librange_alloc-6fdfd7889cb68997.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libobjc-febcccb4db4626d9.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libmalloc_buf-58fbf4f1d52fba23.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libgfx_backend_empty-21e0815140cced69.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/liblog-032b4d7c87d5ce65.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libcfg_if-5d7f3510936b3ebf.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libgfx_hal-ea6185a4ef28cd6b.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libraw_window_handle-aad9bef18864c577.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/liblibc-3507ae351ab28dbd.rlib" "/home/cheng/Projects/Rust/iced/target/x86_64-apple-darwin/release/deps/libbitflags-53d97153ceb1e7b6.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libstd-8b17b186cd972395.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libpanic_unwind-d06c699b1a1b11b4.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libhashbrown-65f6b0602eb03a82.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/librustc_std_workspace_alloc-cbfad1c2e76ceaeb.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libbacktrace-6e499767504f2786.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libbacktrace_sys-767e350fd8547e78.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/librustc_demangle-9ecb8e821171ea10.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libunwind-c11544637ad3758f.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libcfg_if-2e3b92524ee7eda9.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/liblibc-628a35dcde52dad2.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/liballoc-f99de1eca1e6e970.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/librustc_std_workspace_core-ef5998790eeac756.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libcore-3fe78a4d2924ae43.rlib" "/home/cheng/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-apple-darwin/lib/libcompiler_builtins-57149daefc485a08.rlib" "-lc++" "-framework" "Metal" "-lSystem" "-framework" "AppKit" "-framework" "AppKit" "-framework" "Foundation" "-framework" "Foundation" "-framework" "QuartzCore" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreGraphics" "-framework" "CoreFoundation" "-lSystem" "-lobjc" "-lSystem" "-lresolv" "-lc" "-lm"
  = note: ld: framework not found Metal
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

error: aborting due to previous error

error: could not compile `wgpu-native`.

To learn more, run the command again with --verbose.

I'm wondering if there is a solution for this or I must prepare a MacOS environment

I have not successfully cross-compiled a Rust project before. Maybe someone with more experience could chime in. However, you could use GitHub CI to build your macOS binaries!
For instance, the todos example in this repository is compiled for Windows, macOS, and Linux every time a commit is pushed to master and the resulting binaries can be downloaded as build artifacts. Feel free to grab the workflow file as a starting point.

I highly recommend you use cross from the rust-embedded peeps. It has allowed me cross-compile programs directly using the winapi from Linux to Windows (as I mainly develop in WSL)


fix(ci): fix release ci

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


integrate sequencer as repair tool into repairnator

It would be great to have @chenzimin et al's sequencer as repair tool into repairnator. This would really be AI for CI!
References:

http://arxiv.org/pdf/1901.01808
https://github.com/kth/sequencer

closing per #932


Changed Bank Name for ifsc

Merge after build passes.

should i change the release version in package.json??
not being used anywhere?

Not yet. We're planning a release soon, that will get taken care of separately.

Resolved in 1.3.3 release


Add Intel MKL support to Docker container

Today, in our benchmarking we're not using Intel MKL or a CPU-optimized version of TensorFlow inside of our docker container. Updating our container to take advantage of these optimizations should provide significant improvements to our runtimes.
Example of how tensorflow builds an MKL optimized container: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/docker/Dockerfile.mkl

MKL doesn't support int32 or int64 matmul. So not sure this is worth doing. Closing!

thanks for looking into it!


Add Section on Parachain Block Times

Content request
A section should be added discussing a standard config and setup parachains should do for setting block times. Right now this should be 12 seconds. If they set it any lower (something like 6  seconds), they will have authors missing their slots. It's also the case that after a target block time is set, it's very hard to change. If a team solely changes it in their runtime, the next runtime upgrade will brick their chain. There should be an explicit warning about this.
Are you willing to help with this request?
Maybe (please elaborate above)

https://docs.substrate.io/reference/how-to-guides/parachains/prepare-to-launch/#critical-parachain-constraints is not ideal, but it does cover this. You agree? Open to a PR to improve as you see fit for sure :pray:


Out of date commands on Google Groups authorization doc

Page: /setup/security/authorization/google-groups/
Feedback:
The doc says to run:
hal config security roles provider google edit
--admin-username $ADMIN
--credentials-path $CREDENTIALS
--domain $DOMAIN
But the correct command is:
hal config security authz google edit
--admin-username $ADMIN
--credential-path $CREDENTIALS
--domain $DOMAIN

Thank you!


Install and remove build deps in the same RUN

Based on @yosifkit and @tianon recommendations docker-library/official-images#1920

LGTM


elasticOut kinda broken

I made a small demo to see difference between interpolations, you can see output here:

AFAIK, interpolation's purpose is interpolating value from 0 to 1 in a fancy way. I think, it should be a rule that for every a == 0, interpolated value of a will be 0, and for every a == 1, interpolated value of a will be 1. This applies to every interpolation except elasticOut.
How to reproduce:
    System.out.println(Interpolation.elasticOut.apply(0)); //prints 1.0000001

Floating point works this way. I guess we can special case elasticOut.
See InterpolationTest for visuals.


alto2hocr: Hyphenation sign is not handled correctly

Example (the dash is actually normally an em dash):
   ...
   <String WC="0.6233333349" CONTENT="con" HEIGHT="26" WIDTH="79" VPOS="132" HPOS="596" SUBS_TYPE="HypPart1" SUBS_CONTENT="conservation"/>
   <HYP CONTENT="-"/>
</TextLine>
<TextLine HEIGHT="43" WIDTH="679" VPOS="175" HPOS="12">
   <String WC="0.7411110997" CONTENT="servation" HEIGHT="43" WIDTH="194" VPOS="175" HPOS="12" SUBS_TYPE="HypPart2" SUBS_CONTENT="conservation"/>
   ...

will be transformed into
   ...
   con

   servation
   ...

and the dash is missing. For correct presentation (and error computation) it should be part of the first word here. Can this been easily done with the XSLT approach here?

Obviously ALTO uses a <HYP> tag which is currently not handled by the transformation. I did not find a similar tag in the hOCR specification.
http://digi.bib.uni-mannheim.de/~stweil/ocr-praxis/Testseiten/hocr/417576986_0012.hocr is the result of an extended style sheet where I used a quick hack to produce something useful.

Hm.. I see an extra node in your result which results in another space. Our goal is to receive
con-

I think we can try to replace these lines with something like
 <xsl:template match="String">

        <xsl:value-of select="@CONTENT"/>
        <xsl:value-of select="preceding-sibling::HYP/@CONTENT"/>

  </xsl:template>

But this is untested...

Ping @kba . Here are two examples of ALTO files with hyphenations (just search for HYP node):

official example from the ALTO community: http://chroniclingamerica.loc.gov/lccn/sn86069133/1910-10-31/ed-1/seq-1/ocr.xml
one of our examples: http://digi.bib.uni-mannheim.de/fileadmin/digi/417576986/alto/417576986_0078.xml

It looks that CONTENT is empty in our HYP tags, i.e. we may have to do something like an conditional statement.

Here's a small change to the alto2hocr.xsl script that should accomplish this: https://github.com/kba/hOCR-to-ALTO/commit/f447acea8cc90f8085e031d058626968475f4a0a

This https://github.com/kba/hOCR-to-ALTO/commit/f447acea8cc90f8085e031d058626968475f4a0a has been merged - so this issue might be closed...

I wasn't sure anymore if this was already included. Thank you for the confiromation @filak !


When endorsing the order of actions in the log is wrong

The tuck shouldn't happen before deciding to endorse.

Where would you like to see the log message moved to? It's not going to be the easiest to move it.

ok, if its not easy, then maybe it could be clearer that the tucking is paying for the endorsement then?

Anyway, the ordering is strange, but I don't think this is critical.

another thought...the selection interaction could select a card specifically (with the recent array function that was added for echoes) instead of selecting a card to tuck directly.  This would allow the log message to be put in the correct order before the actual transfer occurs.

Where do you want the message to appear? I can find the simplest way to make that happen.

the tuck message should be after the endorsement confirmation message.  that would be in line with the rules.

Before or after the resource icons are printed?

before the "you have 5 crowns" message in the log above since the tucked card can impact the sharing/vulnerability.

as soon as the card is selected, the endorsement has begun so there should be an opportunity to throw that log message?