ISSUE-263 Improve the commit process

introduce merge script which is based on Spark merge script and borrow some block from Kafka

removed unnecessary parts regarding porting back, handling JIRA issues including marking versions

This closes #263 but need to remove CHANGELOG.md separately since including removal of CHANGELOG.md will incur merge conflict.
Please play with merge script to determine how it works and how it configures commit title and commit message of squashed commit.
The script is not that complicated if you are familiar with git command so you may want to also read the script.
Please note that PR's body is picked for squashed commit message instead of accumulation of commit messages in PR's commits. This is based on the decision that Spark / Kafka / etc projects define the template of pull request which guarantees the PR's body to be valuable to get into commit message.
What merge script is doing:

It checks the title of PR to verify it conforms to the rule: the title of PR should be started with ‘ISSUE-‘.

It also means that pull requests should be based on corresponding issues.
If the PR doesn’t respect the rule, merger can stop merging, force use the title, fix the title manually.

It checks out target branch and PR’s branch, and squash commits in PR into one.

If there’re multiple authors in PR, it just stops merging instead of enumerating authors and letting merge pick primary author.

This was a blocker for Storm introducing similar merge script.
For now, we can rely on merger to handle the case manually instead of making script much complicated.

Commit title will be the title of PR.
Commit message will contain below things:

The body of PR
The information of author(s)
The information of merger if merger resolves merge conflict manually
The origin commits on PR if necessary (optional)
Auto close message for Github PR

Push the squashed commit to the remote (HWX gerrit repository).

@satishd
Unlike Streamline project, there're no DEVELOPER.md so I couldn't add the explanation of merge process. Please let me know when you think we may be better to also adopt DEVELOPER.md from Streamline.

@satishd
Please clarify committer details.
Did you mean reviewer list? According to Kafka merge script, merger needs to put it manually which makes me feel the thing to avoid.
https://github.com/apache/kafka/blob/c22c1775a550dbefe6bd4cdcf8820404351257a8/kafka-merge-pr.py#L154-L155
If you mean it and you would like to add, I'll add it too.
Did you mean authors in commits? The merge script will not work with multiple authors in a PR. In that case, squashing commits into one only preserves authorship for only one author.

@satishd Please clarify committer details.

@HeartSaVioR I meant that as reviewers details. Is not there a way to pick up reviewers list from a PR? It is good to have that information as part of commit message.

@satishd
We need to decide how to determine reviewers from PR then. Maybe from comments, Reviewers in github PR, and so on. For former how we determine reviewers from comments? Finding +1 or LGTM?
Also need to decide who can become reviewer: only committers, including contributors.

And we could leave github ID without any other information but if we want to leave name and email like Kafka, we need to maintain matching table.

github id from Reviewers in PR should be fine, who can be committers or contributors. We will always ask reviewers to use review option in PR by not just putting a comment.

@satishd
Then we could leverage below API:
https://api.github.com/repos/hortonworks/registry/pulls/256/reviews
Each comment has state which is one of APPROVED, CHANGES_REQUESTED, COMMENTED.
Only APPROVED and CHANGES_REQUESTED affects overall review state for specific user.
Do we want to only select reviewers who 'finally' approve the change? Or include all reviewers for all kinds of overall review state?

Do we want to only select reviewers who 'finally' approve the change? Or include all reviewers for all kinds of overall review state?

@HeartSaVioR We should include whoever reviewed with or without final approval of the proposed change.

@satishd
Done. I just left reviewers' github ID because retrieving their name as well as email needs separate API call per each reviewer. There's quota for calling Github API and unless we set OAuth it might be very limited.

@satishd Done and squashed the commits.


Update logging message for config loading

Be more specific about what happens when we don't find the configuration file, instead of making it look like an error. An exception will still be thrown if required params aren't configured in either place.
By the way, VM options override configuration file settings, which may warrant a note in the readme. :book:

:+1: for better words


GH-43060: [C++] Limit buffer size in BufferedInputStream::SetBufferSize with raw_read_bound

Rationale for this change

See https://github.com/apache/arrow/issues/43060 . This patch optimize memory-usage for buffering
What changes are included in this PR?

Limit the buffer_size_ used by SetBufferSize
Are these changes tested?
Yes

Are there any user-facing changes?
No

GitHub Issue: #43060

@ursabot please benchmark

Will merge in 1day if CI passes and no negative comments

                    Traceback (most recent call last):
  File "/opt/homebrew/var/buildkite-agent/builds/test-mac-arm/apache-arrow/arrow-bci-benchmark-on-test-mac-arm/benchmarks/benchmarks/_benchmark.py", line 323, in r_benchmark
    result, output = self._get_benchmark_result(command)
  File "/opt/homebrew/var/buildkite-agent/builds/test-mac-arm/apache-arrow/arrow-bci-benchmark-on-test-mac-arm/benchmarks/benchmarks/_benchmark.py", line 366, in _get_benchmark_result
    output, error = self.conbench.execute_r_command(command, quiet=False)
  File "/Users/voltrondata/miniconda3/envs/arrow-commit/lib/python3.8/site-packages/conbenchlegacy/runner.py", line 228, in execute_r_command
    raise Exception(error)
Exception: Error in library(arrowbench) : there is no package called ‘arrowbench’
Execution halted

Emm


Added platform type

Closes #68

Would you like to add yourself to the contributors table? Feel free to open another PR :smile:


Collection of toys for sam to interact with

Collection of toy like objects for any situation for sam to interact with.

skateboard DONE
sportsballs (bowling ball, golf ball, tennis ball, football, rugby ball) DONE
shed (or other light structure for sam to crash through)
Other sam-like entities (childen, dancers, etc)
hanging punching bags DONE
standing punching bags

Added balls, though there should be flags for density and texture. Might make these a different issue soon though.

Added rectangles. With rectangles map designers can now make structures.
Closing this task as several toys have been made - plenty for us to play around with ideas. If new objects are desided to be needed they will have their own tasks.


support custom fields for TimeEntry

There is no support for custom fields when creating a TimeEntry.

I don't see any volunteers to implement this and I have never used custom fields in time entries. I don't have any sample use-cases for them and I don't want to make up requirements. closing as won't fix.


feat(invoice): support 0 amount invoices

Description:
Add support for zero amount invoices by allowing the user to set the amount to pay manually in the case that the invoice amount is zero.
Motivation and Context:
Support sero amount invoices like those created by tippin.me
How Has This Been Tested?
Try to pay a zero amount invoice (use https://tippin.me/ for example)
Types of changes:
New feature
Checklist:

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

Please try again @JimmyMow - I think these issues should be resolved now.

Tested ACK c5ecfa7 🎊


Docs: Improve "Getting Started" docs

Description

Copies over content from https://flowfuse.com/blog/2024/03/dashboard-getting-started/ to improve the underlying documentation with the latest workflow

Okay, it doesn't copy the whole article, just two of the sections. I can re-write if required.

Comment from @Paul-Reed:

Shouldn't all the documentation really be in one place instead of users having to follow links to other sites...


debug

This change is

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Update feed-stac-api Lambda to use pystac-client

Replace sat-search with pystac-client: https://github.com/stac-utils/pystac-client

Nevermind I see this addressed in issue #34

Per @matthewhanson closed as OBE, refer to #34 and #41


Implement vulnerability scanning components [unstable]

It is implemented based on current design, might have some changes later.

Coverage increased (+0.04%) to 57.182% when pulling 7a0a423cc8271deb5d46f484b66fb62336e9dacb on steven-zou:master into 79e80aad6760fa29c231e3cb5d0038f574e911be on vmware:master.


Standardise docker setup

Remove ssl enforcing from the app, because it's now handled on nginx level
Use moj base docker container for Ruby 2.2.2
Upgrade Ruby to 2.2.2

CircleCI is down, but I have run the tests and they pass.


Update to latest LUIS SDK model using endpoint instead of region.

Pull Request Test Coverage Report for Build 1165

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 68.627%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-config/src/botConfigurationBase.ts
2
79.17%

Totals

Change from base Build 1162:
-0.07%

Covered Lines:
2168

Relevant Lines:
2978

💛  - Coveralls


ES6 Arrow Functions Breaks Middleware Factory

Expected behaviour
Karma should allow ES6 arrow functions for a middleware factory. It should behave the same as if a traditional function was passed.
Actual behaviour
Karma throws "Cannot read property '1' of null", because it is trying to reflect the functions parameters as a string and is assuming "function" will be present.
Environment Details
Karma version: 1.7.0
Relevant part of your karma.config.js file:
{
  beforeMiddleware: ['jinja'],
  plugins: [
      'karma-*',
      {'middleware:jinja': ['factory', () => renderJinjaTemplate]},
  ]
}

Steps to reproduce the behaviour

Add a custom middleware plugin
Add a factory plugin for the middleware
Pass an arrow function as the middleware's factory

I tracked down the issue to the vojtajina/node-di dependency. Unfortunately that project has was depreciated in favor of a project that was unreleased and got abandoned in favor of coupling it to the angular core...
Would you be open to a fork of di?

@deckar01 another alternative is to migration to the DI implementation in @angular/core or it's extraction at injection-js.


Release docker image for arm64.

The following file has been modified:
Modified .github/workflows/tests.yml file to build and push the image for both amd64 and arm64 platforms.
Signed-off-by: odidev<EMAIL_ADDRESS>

Great to get a arm64 build.
But the PR changes other things that should not change (when to push) and also needs to change the step docker_tagged, so that release versions (tagged latest and x.y.z, by git tag) are also built for ARM.

Also, in order to release on arm64 I think we need to run at least some basic tests on that platform as well.

@odidev ?

@cyberw , I have added changes as per your suggestions and pushed the commit and am now checking into adding tests for arm64.

@odidev Did you find a way to run the tests on arm? I can merge this without the tests, but it would be nice to have them...

I want to try adding 3.10 support, so merging this first makes sense, even without tests...


Pre-compiled module is missing<EMAIL_ADDRESS>

WARN Pre-compiled module is missing<EMAIL_ADDRESS>WARN Please an file issue at https://github.com/tessel/t2-cli/issues/new with this warning.
WARN
WARN This warning might be caused by one of the following:
WARN
WARN 1. A pre-compiled binary has not yet been built for this module.
WARN 2. The binary didn't compile correctly for the platform that you're developing on.
WARN    Binaries that are Linux-only or even OpenWRT-specific may cause this issue.
WARN    Try to npm install --force the affected module, then rerun your deployment command.
WARN 3. The binary may be platform specific and impossible to compile for OpenWRT.

Hi, trying to import the node midi package into an otherwise empty project.  This happens when trying to t2 run index.js.
Thanks.

@crstffr It looks like we have the pre-compiled module for<EMAIL_ADDRESS>in our storage, so I'll try this out on my local tonight. Otherwise, I'll try to recompile the package and upload it to our storage.

@HipsterBrown thanks for taking a look.  How would I go about accessing the package from your storage?

t2-cli does that for you. What version of Node (node -v) and t2-cli (t2 version) are you using?

Local node: v6.9.2
INFO Tessel Environment Versions:
INFO t2-cli: 0.1.4
INFO t2-firmware: 0.0.16
INFO Node.js: 4.5.0

Sounds good, thanks.

I've just pre-compiled<EMAIL_ADDRESS>and pushed it the pre-compiled module server

I've just pre-compiled<EMAIL_ADDRESS>and pushed it the pre-compiled module server

I've got this same issue with running the t2 led.js experiment.


Refactor popup filters options

Refactor popup_filters options to allow a literal object or a boolean. Basically going from a flat prefix based structure to a more structured one.
Enforce semi eslint rule

Codecov Report

Merging #462 into master will decrease coverage by 0.06%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master     #462      +/-   ##
==========================================
- Coverage   87.29%   87.22%   -0.07%
==========================================
  Files          37       37
  Lines        4383     4383
  Branches      354      358       +4
==========================================
- Hits         3826     3823       -3
- Misses        534      537       +3
  Partials       23       23

Impacted Files
Coverage Δ

src/dom.js
84.61% <ø> (ø)
:arrow_up:

src/number.js
87.5% <ø> (ø)
:arrow_up:

src/array.js
100% <ø> (ø)
:arrow_up:

src/string.js
96.42% <ø> (ø)
:arrow_up:

src/sort.js
76.92% <0%> (ø)
:arrow_up:

src/modules/dateType.js
92.85% <100%> (ø)
:arrow_up:

src/tablefilter.js
91.83% <100%> (ø)
:arrow_up:

src/modules/popupFilter.js
87.56% <100%> (-1.63%)
:arrow_down:

Continue to review full report at Codecov.

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


[Benchmark] Upgrade self-managed benchmark datastore cluster to 2.12.0 version

The current benchmark datastore serving https://opensearch.org/benchmarks is using OpenSearch-2.7.0 version. Since the release of OS-2.7.0 version there have been many significant changes, updates and bug-fixes have gone into OpenSearch Dashboards.
This issue is to track the upgrade of benchmark datastore cluster from OS-2.7.0 to OS-2.12.0.

[Triaged] @rishabh6788 Are we able to close this issue? Seems like the migration is completed.

Version upgrade was completed successfully.


The toy-data link http://www.cse.yorku.ca/~mridataset/ is invalid. Would you please kindly update it?

Dear chuan1093,
the dataset is the same as the one that can be found here.
http://jtl.lassonde.yorku.ca/software/datasets/
However, the corresponding download link on this website also seems not to work. Maybe it's a temporary problem?
Best regards,
Andreas

Dear chuan1093,
I just checked again the website after a while and it still does not seem to be working. Maybe the best thing is to directly contact the guys from the lab.
Best,
Andreas

Dear chuan1093,
the link for the cardiac dataset should be working again.
Best regards,
Andreas


changing/applying new font family using formatInline - does not remove old class, it just adds a new one

Hi,
As per Pulges suggestion (thanks!) I am using formatInline to apply different font families over portions of selected text.
In order to do this I created several classes, one for each family.
If you only apply a font family class over a portion of text, it works great. If you try to apply different font families over the same selection the result is not great:
< span class=" verdana impact roboto " >...
I tried naming all the fonts using a scheme - ftfa[A-Z]{4} - and using this as a regex. My hope was that the WYSIWYG will only apply 1 font family and upon calling the formatInline again it will replace the existing font family - if any - with the new one.
But this does not happend. The result is exactly as above but with other class names:
< span class=" ftfaVDNA ftfaIMPA ftfaRBTO " >...
Is there any way to archive the behavior I expect?
And/or how can I read the currently applied font family?
Thanks,
Cristian

I'm having the same issue. I think the way to resolve is for the functions that call formatInline.exec() to call formatInline.remove() first. This may not be appropriate for all functions that use formatInline, but it is for font name, size, color, bgcolor etc.
I've been using the original xing version of wysihtml5 in my app Clibu and am in the process of switching to this version, so I am a bit new to it.

Also see my issue: https://github.com/Voog/wysihtml/issues/247


Add a color-based redshift cut to grid degrader

grid_degrader currently selects too many high redshift galaxies to be truly realistic. Want to add a color-based redshift cut off in each pixel to reduce the high redshift tail.

closed by #203


wrapping SafeAreaView in the children node

Environment
System:
OS: macOS 10.15.3
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 66.25 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 13.6.0 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.13.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 23, 27, 28, 29
Build Tools: 28.0.3, 29.0.2
System Images: android-19 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>10548
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-create-library: 3.1.2
Platforms
iOS: iPhone 5s 10.3.1 and iPhones 7 Plus 10.3.1
Android: No problem
Versions

iOS:
react-native-modal: 11.5.3
react-native: 0.61.5
react: 16.9.0

Description
The modal did not show the child content
Reproducible Demo
    <RNModal
      isVisible={this.state.isVisible}
    >
      <SafeAreaView style={{ flex: 1 }}>
        <View style={{ backgroundColor: "white", flex: 1 }}>
          <Text>
            { "abcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabc"
            }
          </Text>
        </View>
      </SafeAreaView>
    </RNModal>

Same problem here, except on the first time it works. On subsequent tries it doesn't. ios 13.3, iphone 11.

Tried locally, found no problems. It's probably related to the native modal directly.

Hey @yeong0809 ! I think I have something that can help. The possible issue is that you are not passing a size to the <Modal /> component neither to your <SafeAreaView /> component.
I suggest using Dimensions from React Native lib or reading this section at Readme about size of things inside the modal.
Try this:
<RNModal
  isVisible={true}
  deviceWidth={deviceWidth} {/* here */}
  deviceHeight={deviceHeight} {/* and here */}
  style={{ margin: 0, flex: 1 }}>
  <SafeAreaView style={{ flex: 1 }}> {/* here you can pass backgroundColor: "white" too, if you want */}
    <View style={{ backgroundColor: "white", flex: 1 }}>
      <Text>{"Test Text"}</Text>
    </View>
  </SafeAreaView>
</RNModal>

Another possible solution is defining your zIndex from your modal as 2 or 3. You should hardly avoid using zIndex property at Styles but for this case is ok because it's supposed to show the content in front of other content.

Hi everyone, I have encountered the same problem as @yeong0809 met, and I found a solution for this!
Situation

This issue only happens on iOS 10.3.1 or below regardless of iPhone type
If using <View/> to replace <SafeAreaView/>, the layout will be fine
If changing animationIn from slideInUp to any other animation that not includes Y-axis change will also be fine

My thought
It should be a native bug and fixed on iOS 11.0.0.
I have tested that this bug is also happening on other <SafeAreaView />'s animation that moving Y-axis from bottom,
no matter using translateY or bottom style.
📢 　  Until Apple officially announces not supporting iOS 10 or below,　　　　　📢
📢 　please help to spread this message to other projects that are also affected. 📢
Screenshots

My Codes
IOSModal/index.js
Click to expand
import React, { PureComponent } from 'react';
import { SafeAreaView, TouchableOpacity, View, Text } from 'react-native';
import Modal from 'react-native-modal';
import PropTypes from 'prop-types';

import { I18n } from '@Helpers';
import { COLORS } from '@Styles';

import { styles } from './styles';

class IOSModal extends PureComponent {
state = { visible: false };

show = () => {
  this.props.onShow && this.props.onShow();
  this.setState({ visible: true });
};

hide = () => { this.setState({ visible: false }); };

submit = () => {
  this.props.onSubmit && this.props.onSubmit();
  this.hide();
};

render() {
  return (
    <Modal style={styles.modal} testID="modal" isVisible={this.state.visible} onRequestClose={this.hide} onBackdropPress={this.hide} transparent>
      <SafeAreaView style={styles.modalBox}>
        <View style={styles.header}>
          <TouchableOpacity style={styles.button} onPress={this.hide}>
            <Text style={styles.cancel}>{I18n.t('cancel')}</Text>
          </TouchableOpacity>
          <TouchableOpacity style={styles.button} onPress={this.submit}>
            <Text style={styles.submit}>{I18n.t('submit')}</Text>
          </TouchableOpacity>
        </View>

        <View style={styles.content}>
          {this.props.children && this.props.children}
        </View>
      </SafeAreaView>
    </Modal>
  );
}
}

IOSModal.propTypes = {
  children: PropTypes.element.isRequired,
  onShow: PropTypes.func,
  onSubmit: PropTypes.func
};

export default IOSModal;

IOSModal/styles.js
Click to expand
import { StyleSheet } from 'react-native';

import { COLORS } from '@Styles';

export const styles = StyleSheet.create({
  modal: {
    margin: 0,
    justifyContent: 'flex-end'
  },
  modalBox: {
    borderTopLeftRadius: 15,
    borderTopRightRadius: 15,
    width: '100%',
    backgroundColor: COLORS.IOS_MODAL.BACKGROUND
  },
  header: {
    borderBottomWidth: 0.3,
    borderBottomColor: COLORS.INPUT.BORDER,
    paddingHorizontal: 15,
    paddingVertical: 8,
    flexDirection: 'row',
    justifyContent: 'space-between',
    alignItems: 'center'
  },
  button: {
    paddingVertical: 9,
    paddingHorizontal: 15
  },
  cancel: {
    fontSize: 17,
    color: COLORS.TEXT
  },
  submit: {
    fontSize: 17,
    color: COLORS.THEME.PRIMARY
  },
  content: {
    justifyContent: 'center'
  }
});

Solutions
1. Create this custom slideInUp animation:
const newSlideInUp = {
  0: {
    opacity: 0,
    translateY: 0
  },
  0.5: {
    opacity: 0,
    translateY: 100,
  },
  1: {
    opacity: 1,
    translateY: 0,
  }
};

2. Use it in your modal component's animationIn:
<Modal animationIn={newSlideInUp} style={styles.modal} isVisible={this.state.visible}>
  {/*...*/}
</Modal>

3. Or you can add it to modal's defaultProps if your modal mostly use default animationIn:
 import Modal from 'react-native-modal';

 Modal.defaultProps = Modal.defaultProps || {};
 Modal.defaultProps.animationIn = newSlideUp;

Closing, thank you @jagwingchoy !

None of these solutions worked for me. I've tried wrapping every single component in safearea view, I've tried using device height and device width. I am still having to use paddingBottom to get my buttons up above the safe are inset. Does anyone have another way of doing this?
Thank you!


Disable HRQ e2e tests

HRQ isn't on in the default manifests so we shouldn't try to test it.
Tested: verified that the right number tests are "pending" when I run
make test-e2e. Didn't wait to verify exactly which ones they were.

/assign @erikgb
/assign @rjbez17
May I get a quick lgtm for this? The nightly e2e tests are broken because of it. Thanks!

/lgtm
Thanks!


device error functional

Add a function, which takes a percent and digit to create a functional for a quickndirty calculation of measurement uncertainty from the device.
(something like, 1.5% 2d for a amperemeter or something like that)

CalculateMeasurement/HU already includes this functionality to some extend.


Add Athena::PreparedStatement per 2021-08-05 changes

Add when resource spec includes this new resource:
The following resource was added: AWS::Athena::PreparedStatementAWS::Athena::PreparedStatement
Use the AWS::Athena::PreparedStatement resource to specify a prepared statement for use with SQL queries in Athena. Use prepared statements for repeated execution of the same query with different query parameters. A prepared statement contains parameter placeholders whose values are supplied at execution time.

Fixed via ffdcf2c2d04f3ac6db4588160aaf70949f75d905


[BUG]: AnythingLLM Appimage not working on Kubuntu 24.04 after upgrade

How are you running AnythingLLM?
Docker (local)
What happened?
When I run the appimage this the error that I get:
./AnythingLLMDesktop.AppImage
[5392:0522/123545.151532:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_Anythipva25Z/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
Are there known steps to reproduce?
Just running the appimage.

This is not a bug with AnythingLLM and is a client-side config issue on your OS + Electron (what the app uses)
https://github.com/electron/electron/issues/17972
Also, since you are trying to run the AppImage, you should be aware of https://github.com/Mintplex-Labs/anything-llm/issues/898 which effects all Linux distros


OpenEBS operator 1.3.0

Added csv 1.3.0 for openebs operator

Signed-off-by: ChandanSagar<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Has you operator nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@ChandanSagar, please check following error:
ERROR: metadata.annotations.alm-examples contains invalid json string [1.3.0/openebsoperator.v1.3.0.clusterserviceversion.yaml]
Expecting ',' delimiter: line 123 column 9 (char 3314)

@J0zi Please take a look, thanks.

@ChandanSagar, looks good. To merge it, PR should be signed by @ksatchit as an original contributor.

@ChandanSagar, looks good. To merge it, PR should be signed by @ksatchit as an original contributor.

@J0zi , is there any specific procedure for this (sorry about my ignorance!)

@ksatchit, instructions are ^^ or here https://github.com/operator-framework/community-operators/blob/master/docs/contributing.md#sign-your-work

@J0zi Can you please take a look now, thanks?


How to specify a custom pallete name?

I want to declare a custom pallete named excel, which I will use on for example a button to show it green. So, I tried that on code sandbox and I was unsuccessful. Here is the link to sandbox: https://codesandbox.io/s/13rzn53xx7
I don't know that if this is a feature or not? If its a feature then that should be a bug. Else can you please suggest me a workaround.
Expected Behavior

As per my sandbox code, color of secondary button should look green.
Current Behavior

Color of secondary button looks gray

Tech
Version

Material-UI
next

React
> 16

browser
chrome

@Vishal1419 You can't. The color property has static supported values. You need to write a wrapping component that implements this behavior.
I want to work on this story in the future. I was thinking of introducing a Color component for this use case.

@oliviertassinari  Thanks for the quick reply. Can you please give an example of wrapping component or any link to it?

Ok, I got the idea, I will try to implement it and let you know the results.

@Vishal1419 Any success?

how can I access muiThemeable in material-ui-next?
I have tried to import it like:
import muiThemeable from 'material-ui/styles/muiThemeable
But it gives me an error.
I have also tried this:
import { muiThemeable } from 'material-ui/styles';
But it gives me undefined.
I really want a way to get the currentTheme and then I want to access pallete out of that.

Also, when changing backgroundColor of button, I loose ripple effect as well as hover effect.

@oliviertassinari  Thanks for giving me the idea, I have created the wrapping component and it works.
@gustavopch Yes, I implemented it. Take a look at the code below:
import React, { Component } from 'react';
import { withTheme } from 'material-ui/styles'
import PropTypes from 'prop-types';

class Color extends Component {
    constructor(props) {
        super(props);
        this.state = {
            hover: false,
        }
        this.toggleHover = this.toggleHover.bind(this);
    }

    toggleHover() {
        this.setState({
            hover: !this.state.hover,
        });
    }

    render() {
        const { theme, color, children } = this.props;
        return (
            React.cloneElement(children, {
                style: {
                    ...children.props.style,
                    color: !children.props.disabled &&
                           theme.palette[color].contrastText,
                    background: !children.props.disabled &&
                                (this.state.hover
                                ? theme.palette[color].dark
                                : theme.palette[color].main),
                },
                onMouseEnter: this.toggleHover,
                onMouseLeave: this.toggleHover,
            })
        );
    }
}

Color.propTypes = {
    color: PropTypes.string.isRequired,
    children: PropTypes.element.isRequired,
    theme: PropTypes.object.isRequired,
}

export default withTheme()(Color);

You can use it as follows:
<Color color="excel">
    <Button
        color="primary"
        variant="raised"
        style={{ margin: 10, marginTop: 6 }}
        disabled={props.selectedContacts.length <= 0}
        onClick={props.deleteSelectedContacts}
    >
        <DeleteIcon style={{ marginRight: 10 }} />
        Export To Excel
    </Button>
</Color>

In theme I am doing this:
import { createMuiTheme } from 'material-ui/styles';

const theme = createMuiTheme({
  palette: {
    primary: {
      light: '#e3f2fd',
      main: '#2196f3',
      dark: '#1976d2',
      contrastText: '#fff',
    },
    secondary: {
      light: '#fbbcd0',
      main: '#f50057',
      dark: '#c51162',
      contrastText: '#fff',
    },
    excel: {
      light: '#E8F5E9',
      main: '#4CAF50',
      dark: '#2E7D32',
      contrastText: '#fff',
    }
  },
});

export default theme;

And in App.js, I wrap parent div inside MuiThemeProvider as follows:
      <div className="App">
        <Provider store={store}>
          <MuiThemeProvider theme={LightTheme}>
            <Contacts />
          </MuiThemeProvider>
        </Provider>
      </div>

@oliviertassinari Any in-built support for this in newer versions?

I'm closing as a duplicate of #14185. #13875 covers the same problem.


Does redux-eggs work with ReduxToolkit v2?

It appears that redux-eggs is bound to the v1.9 series of ReduxToolkit.
Has anybody had success with ReduxToolkit v2?

Hello @visualjeff!
I'm currently actively exploring the possibility of using this library with the latest major versions of Redux Toolkit. Please stay tuned for updates.

Thank you.   V2 of the RTK address import issues related to nodejs and ESM.  How soon do you think you'll be able to confirm compatibility?
Once again, Thank you!

Hey fostyfost,
Just thought I'd circle back around to see if there were any updates to redux-eggs as it pertains to V2 of RTK?
Jeff

Also looking to update to RTK 2.x and all its new ecosystem (react-redux 9.x, redux-thunk 3.x, etc)


colloid-gtk-theme: 2023-08-12 -> 2023-10-28

Description of changes

Update to version 2023-10-28
Remove update script

Closes https://github.com/NixOS/nixpkgs/pull/259682
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
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.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2852


🪪 Allow custom licenses outside SPDX

Currently license values in MyST frontmatter are strict. They must be from the SPDX license list, referenced by ID, with no extra, custom information. This is probably how licenses should be used - just pick a good, existing one and stick with that, don't try to embellish it or make up your own. However, in reality, this is not the case. Publishers, authors, etc often have their own license notes, urls for their license policies, or entirely new licenses.
This PR updates license validation in MyST to enable more flexibility when defining license.
First, you may define a license as an SPDX ID, as before. The behavior for this is unchanged: it will be automatically expanded to contain all the relevant license metadata, including name, url, OSI status, etc:
license: CC-BY-4.0

And, as before, you may still separate content and code licenses - again, no changes to this.
license:
  content: CC-BY-4.0
  code: MIT

However, you may now add your own note - in this case, other metadata will still be populated as before, alongside your note:
license:
  id: CC-BY-4.0
  note: When attributing this content, please indicate the Source was MyST Documentation.

You may also override metadata fields - in this case, the new url will be used, but other metadata will be populated as before:
license:
  id: CC-BY-4.0
  url: https://example.com/licenses/how-our-journal-uses-cc-by

Finally, you may define your own totally new license:
license:
  id: im-not-a-lawyer
  name: I'm Not A Lawyer License
  url: https://example.com/licenses/these-wont-stand-up-in-court

Note, in cases all where you (1) do not use an SPDX license or (2) override default SPDX fields, MyST will raise a warning.

Went through this with Franklin! Looking good, and opens up a lot more possibilities to support real-world use cases for capturing license information.


How to mount other storage (not replace my cli stroage)

How can I mount other storage like
$acctKey = ConvertTo-SecureString -String "dummydummy" -AsPlainText -Force
$credential = New-Object System.Management.Automation.PSCredential -ArgumentList "Azure\dummydummy", $acctKey
New-PSDrive -Name Z -PSProvider FileSystem -Root "\\dummydummy.file.core.windows.net\someFolder" -Credential $credential -Persist

or bash
sudo mount -t cifs //dummydummy.file.core.windows.net/fncontainers /TSmount -o vers=3.0,username=dummydummy,password=dummydummy,dir_mode=0777,file_mode=0777,sec=ntlmssp

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

ID: ecd5d368-8d1c-f984-4922-ab4c7ae14db5
Version Independent ID: dbb6bc4c-87f4-18a0-f6e9-f9f48be1f289
Content: Persist files for Bash in Azure Cloud Shell
Content Source: articles/cloud-shell/persisting-shell-storage.md
Service: azure
GitHub Login: @jluk
Microsoft Alias: juluk

@TiloGit Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

any update on this?

Thanks for reaching out!
Mounting storage requires root access in Linux.  Cloud Shell does not provide root access in the container, so this is not a supported scenario.
Please add this as a feature request on https://aka.ms/cloudshell/feedback so we can evaluate it in the future.

#please-close

#label:"cloud-shell/svc"


install-cni container in istio-cni-node daemonset is not ready after install istio through rancher marketplace

I installed a K3s cluster through K3sup and I register my cluster in rancher.
1- rancher version 2.5.7
2- k3s cluster version  v1.20.5+k3s1. but version 19 has same problem too
3- fresh install
4- cluster type: on prem ( 3 VMs CentOS Linux release 7.9.2009)
5- HA cluster all 3 nodes are master node and embeded databse is used
6- istio version 1.8.3
after I register my cluster and everything seems working, I deployed istio. if I deploy istio without cni enabled everything is up and running but if I install istio cni then  all pods is up and running except  istio-cni-node. in this pod repair-cni container is up and running but install-cni container is not ready. following is istio-cni logs
2021-04-22T09:18:19.404192Z	info	Copied istio-cni to /host/opt/cni/bin.
2021-04-22T09:18:19.470837Z	info	Copied istio-cni-repair to /host/opt/cni/bin.
2021-04-22T09:18:19.566199Z	info	Copied istio-cni-taint to /host/opt/cni/bin.
2021-04-22T09:18:19.617904Z	info	Copied istio-iptables to /host/opt/cni/bin.
2021-04-22T09:18:19.617993Z	info	Directory /host/secondary-bin-dir is not writable, skipping.
2021-04-22T09:18:19.619461Z	info	Using CNI config template from CNI_NETWORK_CONFIG environment variable.
2021-04-22T09:18:19.619488Z	info	CNI config: {
"cniVersion": "0.3.1",
"name": "istio-cni",
"type": "istio-cni",
"log_level": "info",
"kubernetes": {
  "kubeconfig": "/etc/cni/net.d/ZZZ-istio-cni-kubeconfig",

  "cni_bin_dir": "/opt/cni/bin",

  "exclude_namespaces": [ "istio-system", "kube-system" ]

}
}

Unfortunately  no, but I will put my time weekend to investigate more

@jesuspabloalfaro just I guess it can be related to PSP


How to Specify SecureRandom in SslContext?

Expected behavior
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
4.1.42.Final
JVM version (e.g. java -version)
openjdk version "11.0.4" 2019-07-16 LTS
OS version (e.g. uname -a)
Windows 10 Pro x64
I'm looking for way to integrate custom SecureRandom in SslContext of Netty but unable to find anyway. Can anyone help?

AFAIK, providing your own SecureRandom would only make sense for JDK based SslContext implementation and not for OpenSSL based one.
Currently, SslContextBuilder is very generic and doesn't take parameters that are specific to a given implementation.
The only way would be to build your own java.net.ssl.SSLContext and pass your SecureRandom to init and then wrap into Netty's JdkSslContext.

AFAIK, providing your own SecureRandom would only make sense for JDK based SslContext implementation and not for OpenSSL based one.
Currently, SslContextBuilder is very generic and doesn't take parameters that are specific to a given implementation.
The only way would be to build your own java.net.ssl.SSLContext and pass your SecureRandom to init and then wrap into Netty's JdkSslContext.

If I warp SSLContext to Netty JdkSslContext then I will lose OpenSSL Performance Benefits. Is my understanding correct?

I think @normanmaurer would agree this can be closed and such questions are better asked on StackOverFlow than on this bug tracker.

As @slandelle said... Closing

TBH, Support is really rude here. Never mind.


Need a splunkforwarder_input defined resource type

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 2016.4.0
Ruby: ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux]
Distribution: OEL 6/7
Module version: ce5b15ad5993cae6b72739d9f05f656ebfc5347c

What are you seeing
There are defined resource types for all of the other splunkforwarder_* configurations. However, we need one that handles limits and is placed in /opt/splunkforwarder/etc/system/local/limits.conf. It appears this one has just been missed.
What behaviour did you expect instead
It should behave exactly the same as all of the other splunkforwarder_* defined resource types.
Any additional information you'd like to impart
The other defined resource types work great.

This actually is implemented now.
https://github.com/voxpupuli/puppet-splunk/blob/master/lib/puppet/type/splunk_limits.rb
https://github.com/voxpupuli/puppet-splunk/blob/master/lib/puppet/type/splunkforwarder_limits.rb


Tweaks for islands off Vite

Just a working branch of trying to get islands off vite, corresponding marimo-quarto branch is here
I haven't had time to solidly work on this, but hope that I can address/ fix-up some of the issues tonight:
todos:

[ ] isIsland
[ ] clean-up

Bugs:

[ ] Islands with multiple outputs currently do not work
[ ] json outputs still a little weird
[ ] Dedent breaks functions
example:

def fn(x):
    pass

Could handle quarto side with easy hack of prepending "#\n", but asking render not to dedent is probably a good idea too
Beyond my control:

[ ] the island cdn is wishful thinking? https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>
Things I would like to see:

[ ] intermediate flags (cache / pickle definitions for use in non-intermediate cells)
[ ] Quarto side, implement execution-options: https://quarto.org/docs/computations/execution-options.html

Relevant quarto-marimo branch: https://github.com/dmadisetti/quarto-marimo/pull/3/files

Just little changes to get things working from an external app.
There was 1 issue I wasn't able to track down, which is that multiple outputs seem broken during hydration (the worker sends down the right response)- but I'll open an issue for that

@dmadisetti what do you mean by:

the island cdn is wishful thinking

If it was to publish it, I've done that task to this PR: https://github.com/marimo-team/marimo/pull/1230

and for:

Islands with multiple outputs currently do not work

Is this the global matplotlib issue or something else?
Btw this PR looks good to me, feel free to merge when you are done with it

@dmadisetti what do you mean by:

the island cdn is wishful thinking

If it was to publish it, I've done that task to this PR: #1230

Wishful thinking in that the source currently points to a broken link. Cool! I'll try to publish the sample site once something is hosted

For the multiple outputs bug see #1232
I don't have permissions to merge, but I think this is a good start!

thanks @dmadisetti, I will look into #1232 today


zsh-powerlevel10k does not provide the p10k executable

Describe the bug
In the instructions for powerlevel10k, it says to use p10k configure to configure the prompt after installing. The package zsh-powerlevel10k doesn't provide this executable.
To Reproduce
Steps to reproduce the behavior:

nix-shell -p zsh-powerlevel10k
zsh
p10k configure <- errors

Expected behavior
p10k configure should provide the setup for the prompt, but it isn't found even if the package is installed.
Additional context
I've tried this on 20.09 and unstable, and neither have worked. I might be doing something wrong, but I can't figure out what.
Notify maintainers

Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.32, NixOS, 21.05pre287596.ae1c8ede09b (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(root): `"nixos-21.05pre287596.ae1c8ede09b"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

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

For the p10k script to be available you need to source the theme like this:
nix-build -A zsh-powerlevel10k
source result/share/zsh-powerlevel10k/powerlevel10k.zsh-theme

Ah, I knew I was missing something. Thanks!


Fixing performance issues after #804

Fixes #886
I've finally been investigating more in-depth the regression I've seen on our KMeans after #804
The issue lies somewhere in a complicated kernel and I didn't manage to have a minimal reproducer yet,
but at least I've found a hack that is not too complicated that makes it work again, see this PR.
The bug was not a performance bug but a caching bug. Sorry for misleading you into thinking that might be related to performance. The way it surfaced on the benchmarks was with a general slowdown on GPU because rather than segfaulting it rather returns corrupted results that was triggering a slower code branch in the KMeans (cluster relocation). On CPU it gave segfaults, meaning the wrong code was executed, so I could have thought sooner about caching issues.
Basically in sklearn_numba_dpex we factor some code using dpex.func kernel functions that are defined as closures and re-instantiated with different parameters every time it's needed. See https://github.com/soda-inria/sklearn-numba-dpex/blob/main/sklearn_numba_dpex/kmeans/kernels/_base_kmeans_kernel_funcs.py . This is the best solution for factoring redundant code that I've thought of (and it only works as long as there are no local memory allocation or barriers in the factored code) ).
So there we can have dpex.func functions with same code, same __name__, same __qualname__,  but that have different globals and id. Globals can include yet other dpex.func functions that have the same characteristics.
It seems that the cache key does not include all the cases we fall into. Adding id(func) solve definitely the issue.
I've said this fix is a "hack" but in fact I don't think it's a bad behavior. It means that every time a kernel or a func are re-instantiated their cache is reset. That could be a feature.

For the record:

this code used to work without requiring any hacks around caching with numba < 0.19.0.

after the bump to numba == 0.19.0 it broke and I added a similar hack using monkey patching from sklearn_numba_dpex, see https://github.com/soda-inria/sklearn-numba-dpex/blob/main/sklearn_numba_dpex/patches/load_numba_dpex.py#L45

after #804 this hack is not necessary anymore , but is must be replaced by the diff shown in this PR

[X] Have you provided a meaningful PR description?

[ ] Have you added a test, reproducer or referred to an issue with a reproducer?

[ ] Have you tested your changes locally for CPU and GPU devices?

[ ] Have you made sure that new changes do not introduce compiler warnings?

[ ] If this PR is a work in progress, are you filing the PR as a draft?

edit: it does not actually fix the issue. But it does seem to be a caching issue on dpex.func functions. Continuing investigation...

In fact this does not solve the issue.


client verify server based on peer's micro service name since ip addr…

client verify server based on peer's micro service name since ip address is uncertain in docker

Coverage increased (+0.03%) to 66.327% when pulling c97bbfd3bace6547b4f6d922227cf645f7b5b437 on dengguojie:master into 2b2e97f28783eee77867431fb7d1a4495526504d on go-chassis:master.


More integration tests for Model + some fixes in the framework

Fix for #487

LGTM

LGTM. Thanks @mwielgus !


compile support for newer linux

thanks
www.zpool.ca

VPS, Ubuntu 16.04
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.

On Wed, Oct 3, 2018 at 3:11 PM cryptomaxsun<EMAIL_ADDRESS>wrote:

VPS, Ubuntu 16.04
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cryptodev35/icash/pull/3#issuecomment-426739837, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGAv4tcIu3ejCMR_fQKKgOfqgjjUEPuMks5uhP2-gaJpZM4PcYBu
.

1 cpu 3.3 Ghz, 1 gb RAM, 1Gb SWAP.


[Feature] Add fd cache for segment files and remove the file cache in BlockManager

Compared with the FileCache used in FileBlockManager, the entry of FdCache
will be erased before deleting the corresponding file, i.e, fd will be closed, so the
disk space can be released earlier.
What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] others

run starrocks_be_unittest

run starrocks_be_unittest


Recommend more popular projects

Hi folks,
I have tools called kubectx/kubens that do this job: https://github.com/ahmetb/kubectx
Also https://github.com/ahmetb/kubectl-aliases seem to be doing some of the functionality that's listed here.
Also https://github.com/jonmosco/kube-ps1 provides the PS1 functionality in a more elegant way.
I wanted to leave these here, in case if you'd like to redirect visitors to more actively maintained projects.

Thanks @ahmetb. Looks like these projects represent 3 separate features that are rolled up into one in this project. The goal of this project is to be a one stop shop and also do it in the simplest terms possible for easy customization.


xcrun instruments -s devices doesn't return a list of simulators

In the directions it states to use:
xcrun instruments -s devices
but on my Mac this doesn't return a list of simulators instead I get:
❯ xcrun instruments -s devices
xcrun: error: sh -c '/Applications/Xcode-13.2.0.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode-13.2.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find instruments 2> /dev/null' failed with exit code 17664: (null) (errno=Invalid argument)
xcrun: error: unable to find utility "instruments", not a developer tool or in PATH
If I run this, however, I do get a list of simulators:
xcrun simctl list
I believe the documentation needs to be updated.
Thanks,
Aaron

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

ID: 192e3c97-ef59-1232-dfb0-65f77a8f960c
Version Independent ID: 1794e724-d580-1d90-188d-6d2885bedc2f
Content: Local testing with iOS Simulators - Visual Studio App Center
Content Source: docs/test-cloud/frameworks/uitest/ios/simulator.md
Service: vs-appcenter
Sub-service: app-center-test
GitHub Login: @lucen-ms
Microsoft Alias: lucen

Thanks for letting us know
Fixed now


Trying to implement ParallelIterator for a custom struct

I am trying to implement the ParallelIterator trait for my own custom type, and this is how it should look in case of the standard Iterator:
struct CustomIterator {
    number: i32
}

impl Iterator for CustomIterator {
    type Item = i32;

    fn next(&mut self) -> Option<Self::Item> {
        self.number += 5;
        Some(self.number)
    }
}

The main question is "How I should implement ParallelIterator for CustomIterator?"

It's definitely not as simple as a normal Iterator!
The first question to ask is how you will split your iterator for parallel processing. The CustomIterator you've shown here won't work because it is unbounded, just as we don't implement ParallelIterator for RangeFrom. If you had an endpoint, you could split your iterator in half, which gives you the means to implement an internal Producer.
If you can implement your iterator in terms of existing iterators, this is easiest, perhaps like:
use rayon::iter::plumbing::*;
use rayon::prelude::*;

pub struct StepBy5 {
    start: i32,
    end: i32,
}

impl ParallelIterator for StepBy5 {
    type Item = i32;

    fn drive_unindexed<C>(self, consumer: C) -> C::Result
    where
        C: UnindexedConsumer<Self::Item>,
    {
        let StepBy5 { start, end } = self;

        // Start with a simple range, then map it to increment by 5
        (0..(end - start + 4) / 5)
            .into_par_iter()
            .map(|i| start + i * 5)
            .drive_unindexed(consumer)
    }
}

Otherwise, I would use an existing implementation as a reference, and read plumbing/README.md. You could also consider using one of the wrappers like split() or par_bridge().

Thank you very much, now I think I understand it.


Not working with Obsidian Publish

I've copied CSS styling from /src/assets/main.css into my publish.css, reset my browser cache and tried making some changes in CSS but I'm not able to get it to work in my webpage.
It would be really great if this plugin can work with Publish feature as well !!

Hi, at the moment the plugin won't work for publish. It has to take the code block and render some HTML before the CSS can do anything and plugins cannot be enabled on publish at the moment.