Add Longest_Alternating_Subsequence

Kindly merge this, for hacktoberfest

ATTENTION 🚨🚨🚨
Don’t Forget To Follow Me On Github , and Add Your Name In _contributor name.txt_ if not found your name in _contributor name.txt_ it should be Labelled as SPAM.
STAR 🌟 this REPO for future HacktoberFest.

ATTENTION 🚨🚨🚨
Don’t Forget To Follow Me On Github , and Add Your Name In _contributor name.txt_ if not found your name in _contributor name.txt_ it should be Labelled as SPAM. STAR 🌟 this REPO for future HacktoberFest.

Hi @Romi904 I am not able to update my name in the Contributors. It says permission to your repo is denied!

Okay,let our team to check the issue.
On Wed, 5 Oct, 2022, 2:05 am aryangupta899, @.***>
wrote:

ATTENTION 🚨🚨🚨
Don’t Forget To Follow Me On Github , and Add Your Name In contributor
name.txt if not found your name in contributor name.txt it should be
Labelled as SPAM. STAR 🌟 this REPO for future HacktoberFest.
Hi @Romi904 https://github.com/Romi904 I am not able to update my name
in the Contributors. It says permission to your repo is denied!
—
Reply to this email directly, view it on GitHub
https://github.com/Romi904/Durmello/pull/108#issuecomment-1267547199,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXJU74JS4CBFC6KUBA7RED3WBSIJJANCNFSM6AAAAAAQ4XCVCA
.


Suggestions for KASPA ROI Calculator

Would it be possible to add a feature to calculate the date when the Miner value is zero, past the ROI date?
Also, might have found a error with values, see the file i uploaded.
Appreciate your development efforts!!!

@tejas-iot if I understood correctly, you're asking about the scenario where you can actually ROI with the device and would just want to see when it would eventually yield 0 net profit after that. That's doable, I'll put it in my todo list.
The Daily Change column showing some big drops in change looks like they happen when Kaspa does its monthly halving.

Correct. I’d like to know when a miner crosses to negative cash flow.
Got it on the halving. Thx.
Get Outlook for iOShttps://aka.ms/o0ukef

From: coderofstuff @.>
Sent: Sunday, September 17, 2023 11:10:21 AM
To: coderofstuff/kas-breakeven-calc @.>
Cc: Robert Johnson @.>; Mention @.>
Subject: Re: [coderofstuff/kas-breakeven-calc] Suggestions for KASPA ROI Calculator (Issue #1)
@tejas-iothttps://github.com/tejas-iot if I understood correctly, you're asking about the scenario where you can actually ROI with the device and would just want to see when it would eventually yield 0 net profit after that. That's doable, I'll put it in my todo list.
The Daily Change column showing some big drops in change looks like they happen when Kaspa does its monthly halving.
—
Reply to this email directly, view it on GitHubhttps://github.com/coderofstuff/kas-breakeven-calc/issues/1#issuecomment-1722509702, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATASBT7ETU7TDUKDZJUFFSLX24OG3ANCNFSM6AAAAAA43VLG5I.
You are receiving this because you were mentioned.Message ID: @.***>

Hello @coderofstuff
Thanks a lot for your really good tool
some ideas i have ;

actually there is an increment for KAS price that we enter ( Daily Price Increase ) ; it would be nice to be able as well to indicate the KAS price at multiple dates ( not increment )
Get the KAS price prediction by day from https://coindataflow.com/fr/prédiction/kaspa
choose units ( TH/S for hashrate -  PH/s daily increase - )
get automatically the PH/s increase (average year increase ) from https://2miners.com/fr/kas-network-hashrate for example if they have an API
add an option to choose not to sell each days but in the biggest KAS price days ( colored in the table )
add pool fees percentage
add selling platform fees KAS to FIAT
add USD to EUR fees after KAS to FIAT
add maintenance fees
increase session stored for the tool ( sometimes it reloads and lose the variables )
be able to download excel, pdf or txt file of the results

Thanks

Hello @coderofstuff Thanks a lot for your really good tool
some ideas i have ;
* actually there is an increment for KAS price that we enter ( Daily Price Increase ) ; it would be nice to be able as well to indicate the KAS price at multiple dates ( not increment )

* Get the KAS price prediction by day from https://coindataflow.com/fr/pr%C3%A9diction/kaspa

* choose units ( TH/S for hashrate -  PH/s daily increase - )

* get automatically the PH/s increase (average year increase ) from https://2miners.com/fr/kas-network-hashrate for example if they have an API

* add an option to choose not to sell each days but in the biggest KAS price days ( colored in the table )

* add pool fees percentage

* add selling platform fees KAS to FIAT

* add USD to EUR fees after KAS to FIAT

* add maintenance fees

* increase session duration stored for the tool ( sometimes it reloads and lose the variables )

* be able to download excel, pdf or txt file of the results

Thanks

Maybe later ;
Add photovoltaic possibility ( price of the solar installation - duration in years - battery capacity in KWH )
-> verify if the consumption of the asics are below battery capacity
-> calculate price per kwh ( total price / nb years of the life durability of the installation / nb of days / nb kwh of battery capacity )
Other idea ; get a json list of known asics + their manufacturer price in the market and select them in a table  ; like 5 ks0 ultra ; another line 5 ks5L ; 5 antminer ks5 pro ....etc etc
it would add the price and the hashrate automatically.
The results would be added together or you could separe them clicking on the + button( like detail by line in the table ).


Sensor becoming unavailable when adding RT updates

Describe the bug
Finally got it working with an SQLite issue. My issue here now is that any RT info that I would like to enter into the system will update the sensor for it to become available. It may be the links I am using but these are provided by the developers.

URL Trip Data: https://gtfs.adelaidemetro.com.au/v1/realtime/trip_updates
URL Veh Pos: https://gtfs.adelaidemetro.com.au/v1/realtime/vehicle_positions
URL Alerts: https://gtfs.adelaidemetro.com.au/v1/realtime/service_alerts
Steps/data to reproduce the behavior, e.g.

Removed configured entry
Readded entry
Readded RT links (as above)

Release used
Main and latest Home Assistant
Additional
Logger: custom_components.gtfs2.coordinator
Source: helpers/update_coordinator.py:315
integration: GTFS 2 (General Transit Feed Specification) (documentation, issues)
First occurred: 11:50:00 AM (1 occurrences)
Last logged: 11:50:00 AM
Unexpected error fetching 9d58c5a1802150e1ee33b170a5673874 data: name 'err' is not defined
Traceback (most recent call last):
File "/config/custom_components/gtfs2/coordinator.py", line 159, in _async_update_data
self._get_rt_alerts = await self.hass.async_add_executor_job(get_rt_alerts, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/gtfs2/gtfs_rt_helper.py", line 309, in get_rt_alerts
if entity.HasField("alert"):
^^^^^^^^^^^^^^^
AttributeError: 'dict' object has no attribute 'HasField'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 315, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/gtfs2/coordinator.py", line 166, in _async_update_data
raise UpdateFailed(f"Error in getting start/end stop data: {err}")
^^^
NameError: name 'err' is not defined
other log below
Logger: custom_components.gtfs2.coordinator
Source: custom_components/gtfs2/coordinator.py:165
integration: GTFS 2 (General Transit Feed Specification) (documentation, issues)
First occurred: 11:50:00 AM (1 occurrences)
Last logged: 11:50:00 AM
Error getting gtfs realtime data, for origin: **redacted for privacy ** with error: 'dict' object has no attribute 'HasField'

If it helps, There is also a curl link to each of these
curl -X GET "https://gtfs.adelaidemetro.com.au/v1/realtime/vehicle_positions" -H "accept: application/x-google-protobuf"

Update - Just adding trip updates is giving real time info, I'm specifically aiming for vehicle locations.
Cheers!

Fixed in <IP_ADDRESS> ... please note that for Alerts I have only been able to do very basic testing as it is quite a job to first find one and then tie it to a stop-in-use....


Import circularity involving a multitest causes syntax errors.

253ffeed4a7e27a4085f63aa6d60e8c19f3454d5 introduced a new multitest "deferred_type_dependency_test.dart", which imports two other files ("deferred_type_dependency_lib{1,2}.dart"), and those files in turn import "deferred_type_dependency_test.dart".  This leads to syntax errors because the multitest infrastructure works by transforming the multitest into brand new files (with different names).  This means that the files "deferred_type_dependency_lib{1,2}.dart" are still pointing to the untransformed multitest, so when the code is run through analyzer, it sees the untransformed multitest code, leading to syntax errors.
The reason this isn't breaking in the VM is because the VM generates parse errors lazily; since the untransformed main() method is never called, the VM never tries to parse it.  But the analyzer parses all code reachable through the transitive closure of imports, so it sees the parse errors.
I believe the correct way to fix this is to move the code needed by "deferred_type_dependency_lib{1,2}.dart" out of the multitest file and into a fourth ".dart" file that can be imported by the others, so that there is no import circularity.

Duplicate of #23894


KOGITO-4475 Upgrade Spring Boot to 2.3.4

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

tried merging #1128 to see if it works /cc @radtriste @r00ta @danielezonca

The Linux check has failed. Please check the logs.

had to kill the build
jenkins please retest this

The Linux check has failed. Please check the logs.

The Linux check is successful.

blocked by https://github.com/kiegroup/kogito-runtimes/pull/1128

The Linux check has failed. Please check the logs.

superseded by https://github.com/kiegroup/kogito-runtimes/pull/1169


test allocations: restore small number of work items in case of reduction

@kpet This is related to https://github.com/KhronosGroup/OpenCL-CTS/pull/1852
We use reduction argument on simulation then too high number of work items makes test very long and we see timeouts. Would be nice have previous value set. I agree there is a need to implement function which will calculate this number accordingly

Merging this PR would result in failures for the implementations listed in #1852. Is the issue you're seeing on a final device or development environment? If the latter, maybe we could introduce command line options to help.

Merging this PR would result in failures for the implementations listed in #1852. Is the issue you're seeing on a final device or development environment? If the latter, maybe we could introduce command line options to help.

By default value is set as in #1852  Only when someone use reduction factor (percentage in command line) Do you use it ?
if (g_reduction_percentage != 100)

@gwawiork Apologies I'd missed that when quickly skimming through it. I've now approved the PR. Should be fine.

Discussed in the April 16th teleconference.  We'll give this one more week for review, but are hoping to merge shortly.

Merging as discussed in the May 21st teleconference.


Enhancement: Hide email contact details in issue reports

Contact Details
Redacted
What features would you like to see added?
Please consider hiding, or not collecting, the contact details when someone adds an issue.
More details
It's unusual to collect this info, but if you need it, it would be great to hide that from view except for the maintainers. I get enough spam as it is so I don't like to have my email on scrapeable websites.
Update: I just noticed it's optional so I just won't supply it. Still, I think it would be better not to ask or obscure it.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I do agree with you that it's not needed. We do not even collect the info. It was already included in the template we used and we never removed it. I'll do something about that soon.
Just to be clear, that field is not required to submit an issue, it's completly optional and you can leave it empty. I'll still remove it.

@fuegovic What do you think about removing the checkbox for the code of conduct? It already says, "By submitting this issue, you agree to follow our Code of Conduct" so the checkbox is superfluous.


Move common testing infrastructure as Gradle test fixtures

Because we often need to setup a common GraphQL infrastructure for tests, we should share this more broadly in the codebase.
For that, we're going to use Gradle test fixtures.

We've moved everything we needed; GraphQlResponse was another likely candidate, but it seems to be enough for now.


MSID: 92459 Version: 1 DOI: 10.1101/2<IP_ADDRESS>4224

MSID: 92459
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>4224
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92459
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4224

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/92459v1
Update ticket with any problems (add blocked label)
Add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>4224
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/92459/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 6: Add PDF url to manuscripts.json
Pull request created to enhanced-preprint-client

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

waiting for peer review content to load, references incorrectly formatted: 21, 27 and 38, otherwise fine to QC.


Failed to build jupyter-scipy-notebook-ee image.

While attempting to build jupyter-scipy-notebook-ee image, I encountered the following error which prevented me from building the image properly.
I am using Windows 10 Home and Docker Toolbox, with Virtualization enabled.
failed
ERROR conda.core.link:_execute(502): An error occurred while installing package 'conda-forge::ipywebrtc-0.4.0-py36_1'.
LinkError: post-link script failed for package conda-forge::ipywebrtc-0.4.0-py36_1
running your command again with `-v` will provide additional information
location of failed script: /opt/conda/bin/.ipywebrtc-post-link.sh
==> script messages <==
<None>

Attempting to roll back.

Rolling back transaction: ...working... done

LinkError: post-link script failed for package conda-forge::ipywebrtc-0.4.0-py36_1
running your command again with `-v` will provide additional information
location of failed script: /opt/conda/bin/.ipywebrtc-post-link.sh
==> script messages <==
<None>

I have an identical problem, though the issue seems related to the bqplot package. Failed to build on a Linux Mint 19.2 machine, with Docker version 18.09.7
ERROR conda.core.link:_execute(502): An error occurred while installing package 'conda-forge::bqplot-0.11.2-py36_1000'. LinkError: post-link script failed for package conda-forge::bqplot-0.11.2-py36_1000 running your command again with-v` will provide additional information
location of failed script: /opt/conda/bin/.bqplot-post-link.sh
==> script messages <==
Traceback (most recent call last):
File "/opt/conda/bin/jupyter-nbextension", line 11, in
sys.exit(main())
File "/opt/conda/lib/python3.6/site-packages/jupyter_core/application.py", line 266, in launch_instance
return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/traitlets/config/application.py", line 658, in launch_instance
app.start()
File "/opt/conda/lib/python3.6/site-packages/notebook/nbextensions.py", line 988, in start
super(NBExtensionApp, self).start()
File "/opt/conda/lib/python3.6/site-packages/jupyter_core/application.py", line 255, in start
self.subapp.start()
File "/opt/conda/lib/python3.6/site-packages/notebook/nbextensions.py", line 896, in start
self.toggle_nbextension_python(self.extra_args[0])
File "/opt/conda/lib/python3.6/site-packages/notebook/nbextensions.py", line 872, in toggle_nbextension_python
logger=self.log)
File "/opt/conda/lib/python3.6/site-packages/notebook/nbextensions.py", line 483, in enable_nbextension_python
logger=logger)
File "/opt/conda/lib/python3.6/site-packages/notebook/nbextensions.py", line 380, in _set_nbextension_state_python
m, nbexts = _get_nbextension_metadata(module)
File "/opt/conda/lib/python3.6/site-packages/notebook/nbextensions.py", line 1122, in _get_nbextension_metadata
m = import_item(module)
File "/opt/conda/lib/python3.6/site-packages/traitlets/utils/importstring.py", line 42, in import_item
return import(parts[0])
File "/opt/conda/lib/python3.6/site-packages/bqplot/init.py", line 64, in
from .figure import *
File "/opt/conda/lib/python3.6/site-packages/bqplot/figure.py", line 36, in
from .scales import Scale, LinearScale
File "/opt/conda/lib/python3.6/site-packages/bqplot/scales.py", line 45, in
from .traits import Date
File "/opt/conda/lib/python3.6/site-packages/bqplot/traits.py", line 33, in
import pandas as pd
File "/opt/conda/lib/python3.6/site-packages/pandas/init.py", line 23, in
from pandas.compat.numpy import *
File "/opt/conda/lib/python3.6/site-packages/pandas/compat/numpy/init.py", line 10, in
_np_version = np.version
AttributeError: module 'numpy' has no attribute 'version'
Attempting to roll back.
`

For those of you who come across this post, I've have found a workaround by updating the jupyter scipy notebook docker that serves as the base to build the jupyter-scipy-notebook-ee, as well as updating the package versions for the different packages that are subsequently installed. Here is the Dockerfile I have modified to achieve a succesful build, but keep in mind I got here by trial and error, not a deep understanding of Docker builds:
FROM jupyter/scipy-notebook:2ce7c06a61a1
LABEL base-image="jupyter/scipy-notebook:2ce7c06a61a1 10/08/2019"
LABEL maintainer="Tyler Erickson<EMAIL_ADDRESS>
# Altair - Declarative visualization in Python
#     docs: https://altair-viz.github.io
#   source: https://github.com/altair-viz/altair
#     pkgs: conda search -c conda-forge altair
ARG ALTAIR_VERSION=3.2.0

# bqplot - Grammar of Graphics-based interactive plotting framework for the Jupyter notebook
#     docs: https://bqplot.readthedocs.io
#   source: https://github.com/bloomberg/bqplot
#     pkgs: conda search -c conda-forge bqplot
#           npm search bqplot
ARG BQPLOT_VERSION=0.11.4
ARG BQPLOT_NPM_VERSION=0.4.7

# Earth Engine Python API
#     home: https://earthengine.google.com
#     docs: https://developers.google.com/earth-engine
#   source: https://github.com/google/earthengine-api
#     pkgs: conda search -c conda-forge earthengine-api
ARG EARTHENGINE_API_VERSION=0.1.192

# Google API Python Client
#     home: http://google.github.io/google-api-python-client/
#     docs: https://developers.google.com/api-client-library/python/apis/
#   source: https://github.com/google/google-api-python-client/
#     pkgs: conda search -c conda-forge google-api-python-client
ARG GOOGLE_API_PYTHON_VERSION=1.7.11

# ipyleaflet - Leaflet-based interactiving mapping widget
#     docs: https://ipyleaflet.readthedocs.io
#   source: https://github.com/jupyter-widgets/ipyleaflet
#     pkgs: conda search -c conda-forge ipyleaflet
ARG IPYLEAFLET_VERSION=0.11.1

# ipyvolume - 3d plotting in the Jupyter notebook
#     docs: https://ipyvolume.readthedocs.io/
#   source: https://github.com/maartenbreddels/ipyvolume
#     pkgs: conda search -c conda-forge ipyvolume
#           npm search jupyter-threejs
ARG IPYVOLUME_VERSION=0.5.2
ARG THREEJS_VERSION=2.1.1

# jupyterlab-manager
#   source: https://github.com/jupyter-widgets/ipywidgets/tree/master/packages/jupyterlab-manager
#     pkgs: npm search @jupyter-widgets/jupyterlab-manager
ARG WIDGETS_JUPYTERLAB_MANAGER_VERSION=1.0.2

# nbdime - Notebook Diff & Merge tool
#     docs: https://nbdime.readthedocs.io
#   source: https://github.com/jupyter/nbdime
#     pkgs: conda search -c conda-forge nbdime
ARG NBDIME_VERSION=1.1.0

# Palettable - color maps
#     docs: https://jiffyclub.github.io/palettable
#   source: https://github.com/jiffyclub/palettable
#     pkgs: conda search -c conda-forge palettable
ARG PALETTABLE_VERSION=3.2.0

# PyDrive - Simplifies many Google Drive API tasks
#     home: https://pypi.org/project/PyDrive
#     docs: https://pythonhosted.org/PyDrive
#   source: https://github.com/gsuitedevs/PyDrive
#     pkgs: conda search -c conda-forge pydrive
ARG PYDRIVE_VERSION=1.3.1

# TensorFlow - Computation using data flow graphs for scalable machine learning
#     home: https://www.tensorflow.org
#     docs: https://www.tensorflow.org/api_docs
#   source: https://github.com/tensorflow/tensorflow
#     pkgs: conda search -c conda-forge tensorflow
ARG TENSORFLOW_VERSION=1.13.1

# Vega Datasets - Collection of datasets used in Vega and Vega-Lite examples
#     docs: http://vega.github.io/vega-datasets
#   source: https://github.com/vega/vega-datasets
#     pkgs: conda search -c conda-forge vega_datasets
ARG VEGA_DATASETS_VERSION=0.7.0

#### Other packages
#
# jupyterlab/toc - Table of Contents extension for JupyterLab
#   source: https://github.com/ian-r-rose/jupyterlab-toc
#
# nbgitpuller - Notebook Git Puller
#   source: https://github.com/data-8/nbgitpuller
#
# Sidecar - A sidecar output widget for JupyterLab
#   source: https://github.com/jupyter-widgets/jupyterlab-sidecar
#
# ipythonblocks - colored grids
#   home: http://www.ipythonblocks.org/

RUN conda update -n base conda &&\
    conda install --quiet --yes \
        altair=${ALTAIR_VERSION} \
        bqplot=${BQPLOT_VERSION} \
        earthengine-api=${EARTHENGINE_API_VERSION} \
        google-api-python-client=${GOOGLE_API_PYTHON_VERSION} \
        ipyleaflet=${IPYLEAFLET_VERSION} \
        ipyvolume=${IPYVOLUME_VERSION} \
        nbdime=${NBDIME_VERSION} \
        palettable=${PALETTABLE_VERSION} \
        pydrive=${PYDRIVE_VERSION} \
        tensorflow=${TENSORFLOW_VERSION} \
        vega_datasets=${VEGA_DATASETS_VERSION} \
      && \
    conda upgrade --all && \
    conda build purge-all && \
    jupyter nbextension enable --py widgetsnbextension --sys-prefix && \
    # JupyterLab Extensions
    pip install sidecar && \
    jupyter labextension install --no-build jupyter-leaflet@${IPYLEAFLET_VERSION} && \
    jupyter labextension install --no-build ipyvolume@${IPYVOLUME_VERSION} && \
    jupyter labextension install --no-build jupyter-threejs@${THREEJS_VERSION} && \
    jupyter labextension install --no-build bqplot@${BQPLOT_NPM_VERSION} && \
    jupyter labextension install --no-build @jupyterlab/toc && \
    pip install git+https://github.com/data-8/nbgitpuller \
      && jupyter serverextension enable --py nbgitpuller --sys-prefix && \
    pip install ipythonblocks && \
    export NODE_OPTIONS=--max-old-space-size=16000 && \
    jupyter lab build && \
    # Clean up
    npm cache clean --force && \
    rm -rf $CONDA_DIR/share/jupyter/lab/staging && \
    rm -rf /home/$NB_USER/.cache/yarn && \
    rm -rf /home/$NB_USER/.node-gyp && \
    fix-permissions $CONDA_DIR && \
    fix-permissions /home/$NB_USER

Thanks for working on updating the Dockerfile, which as you discovered is using quite a few old versions. Feel free to submit a Pull Request for review with the changes you found to work.


[pretend-youre-xyzzy] add chart for pretend you're xyzzy

Signed-off-by: Dennis Zhang<EMAIL_ADDRESS>
Description of the change
new chart for pretend you're xyzzy, a cards against humanity clone

Benefits
new chart for pretend you're xyzzy, a cards against humanity clone

Possible drawbacks

Applicable issues

fixes #

Additional information

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

I will rebase master when I get a chance later today.


Shrink sidebar on small windows sizes similar to the settings page

Settings has different icons for different sections, while sidebar will have same icons for many items. Hence shrinking like settings isn't going to be a good solution. In this case, sidebar should expand as an overlay when the pointer enters.

@Jaiganeshkumaran v0.20 has support for resizing the sidebar.


bower.json

It would be nice to have a bower.json file for this library.

I agree. Originally I was sort of against integrating package mangers and the like, but Bower has definitely proven its staying power and I'm changing my mind.

I forgot someone had already gone ahead and set that up for me a while back! You could've been using "bower install konami-js" this whole time as it turns out, but I've added the bower.json file to the repo now as well as instructions on the examples page.
Thanks.


Featured Post Icon Does not change after activation

I tested this issue in all templates, same on each one

it's only in light icons mode, just because all icons are light!


LinearCombination block encoding may be leaving resource register dirty, affecting ChebyshevPolynomial

Evidence for this was encountered when debugging ChebyshevPolynomial. We are currently unable to correctly construct polynomials of complex linear combinations, which seems to be because reflecting on the ancilla register is not enough.
One theory I have so far is that the problem lies in the Select oracle, which may be somehow modifying its selection register in such a way that the Prepare oracle is not correctly uncomputing its junk.
Related: #1233

@anurudhp points out that this may be an inherent limitation of alias sampling. From the paper:

Select itsel necessarily introduces entanglement between its target register |ψ> and the index register |l> (plus associated junk register). So Prepare† will not exactly restore |l> or the junk register. Although we only specify the action of Prepare on the |0> state, Prepare will be applied to other states due to this imperfect uncomputation effect.

So we are faced with a tradeoff of either 1) using alias sampling and treating dirty resource qubits as ancilla, or 2) switching to e.g. state preparation by rotation. Either way, ancilla count goes up.


Interface merging

While converting to TypeScript (#789) It is becoming annoying that some System interfaces have generic and non-generic versions, and the members are needed to be redirected from one to other.
For example the hack at https://github.com/intellifactory/websharper/blob/master/src/stdlib/WebSharper.Main.Proxies/Enumerable.fs#L29 translates badly to TS as it is not defining a GetEnumerator0 member that would be used on calls through System.Collections.IEnumerable.
A way to simplify TS output and interoperability would be to merge the translated form of some interfaces with special logic. Fox example only one real implementation of GetEnumerable could be given, and both generic and non-generic versions would just translate to a TS class member named GetEnumerable.
Other similarly merged interfaces: IEnumerator, IComparable, IComparer, IEquatable, IEqualityComparer, and later collection interfaces (#576) when those are added to the proxies.

Previously Inline attribute was not allowed on interface implementation methods. This led to some duplicated instance members, one implementation redirecting to the other, for example in the case of the proxy for System.Collections.Generic.List.Enumerator<T> which defines MoveNext as a non-implementation member, and also twice as implementations for System.Collections.IEnumerator and System.Collections.Generic.IEnumerator<T>.
Now allowing Inline so that these instance members can be merged in the output, but this can also lead to incorrect behavior when the inline is not correct (redirecting to another instance member with the same name). Later a check can be added so that this is forced.

If an interface extends both IEnumerable and IEnumerable<T>, the non-generic version must be dropped because now they conflict in TS. Probably the same is needed with other merged interfaces, will test.


Fix dependabot behaviour for es-restclient and vertx.

This PR attempts to correct the behaviour of dependabot in regards to #2826 and #2827.
For vertx we want dependabot PRs only for non-major updates, for the ES-client prevent all updates except for the 7_x plugin.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-10-05T14:41:24.482+0000

Duration: 59 min 50 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
3163

Skipped
35

Total
3198

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


how to install in k8s

Proposal: [Description of the feature]
Current behavior: [What currently happens]
Desired behavior: [What you would like to happen]
Use case: [Why is this important (helps with prioritizing requests)]
Requests may be closed if we're not actively planning to work on them.

helm install influxdb-cluster ./influxdb-cluster


NullPointerException

java.lang.NullPointerException:
Attempt to invoke virtual method 'int java.lang.String.indexOf(java.lang.String, int)' on a null object reference
at java.util.regex.Pattern.quote(Pattern.java:439)
at com.klinker.android.link_builder.LinkBuilder.on(Unknown Source)
setText
setContext
addLinks
build
addLinkToSpan
addLinkToSpan
applyLink

private void addLinkToSpan(Spannable s, Link link) {
// get the current text
maybe this line
Pattern pattern = Pattern.compile(Pattern.quote(link.getText()));
maybe this line
Matcher matcher = pattern.matcher(text);
    // find one or more links inside the text
    while (matcher.find()) {

        // find the start and end point of the linked text within the TextView
        int start = matcher.start();

        //int start = text.indexOf(link.getText());
        if (start >= 0) {
            int end = start + link.getText().length();

            // add link to the spannable text
            applyLink(link, new Range(start, end), s);
        }

        // if we are only looking for the first occurrence of this pattern,
        // then quit now and don't look any further
        if (findOnlyFirstMatch) {
            break;
        }
    }
}

For this, it would be very helpful if you could provide an example that will throw the exception.

Closing for no followup or method to reproduce it


Update OxyPlot.Core to 2.2.0

This updates OxyPlot.Core (and OxyPlot.ExampleLibrary) to the latest version 2.2.0. oxyplot-maui still builds well without any further changes, and also the samples look mostly fine (when skimming through them).
I also quickly looked through the release notes at https://github.com/oxyplot/oxyplot/releases/tag/v2.2.0, and it seems to me there aren't any breaking changes in this release. Is that right, @VisualMelon, or is there anything we should be aware of?

Nothing that should affect the satellite assemblies

Alright, thanks for the confirmation. Then I'll just merge this ...


fix(form-item): left label style

close #3593，这样效果可以么

Codecov Report

Merging #3604 (976cf75) into main (9255495) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3604   +/-   ##
=======================================
  Coverage   62.98%   62.98%
=======================================
  Files        1056     1056
  Lines       21965    21965
  Branches     5731     5731
=======================================
  Hits        13834    13834
  Misses       6638     6638
  Partials     1493     1493

Impacted Files
Coverage Δ

src/form/src/styles/form-item.cssr.ts
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

星号最好还是能在右上角


Introduce two models to track Dependencies.toml and Ballerina.toml

Description:
Currently, we are encapsulating both these config files in one model PackageManifest.
Need to introduce another model to track Dependencies.toml separately.
Describe your problem(s)
Describe your solution(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Duplicated with https://github.com/ballerina-platform/ballerina-lang/issues/32065


Modified fields on table extension not included in VS Code symbols

Open a table extension al file which modifies some fields in the base table. Those fields are not included in the symbols listed by VS Code (Ctrl+Shift+O)

Hi, we really appreciate your idea but currently, this issue is beyond the scope of the AL language and development tools. We will consider it internally but please go ahead and post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. We're constantly monitoring top Ideas and will consider them for a future release.


Update README.md

조금더 향상된 번역본 입니다.
확인 부탁드립니다.

Thank you for your contribution. I am afraid that I should reject this commit because you removed english doc. You can't just replace it. I suggest you to place your translation on the tail.


Porting to Linux

From https://github.com/Microsoft/vcpkg/issues/1435#issuecomment-314929968:

I have been thinking about helping port vcpkg to Linux. However there are currently many dependencies on Windows. The one thing that is frustrating is the wstring/string issue. Since most of the functions on Windows work with wchars which is not the same with the Linux counter parts.  What are yout thoughts on defaulting to wstring on windows then string on Linux. Something like
#ifdef _WIN32
#define CustomString std::wstring
#define Char wchar_t
#elif __linux__
#define CustomString std::string
#define Char char
#endif

This is what we did in cpprestsdk and I believe it was a mistake; it makes it extremely easy to accidentally use std::string or std::wstring instead of CustomString, which will compile fine on your current platform but break everything else.
I think there are two possible alternatives that alleviate this:

Fully wrap the custom string type in a struct so the typesystem prevents you from accidentally dropping down to std::string. I think this could be the right answer for some tightly-controlled codebases.
UTF-8/std::string everywhere with conversions only at the IO/syscall boundaries.

For Vcpkg, we'd prefer to go with option 2 due to the significantly simpler implementation impact. I'd be happy to merge changes to the code in this direction and we already have vcpkg::Strings::to_utf16 and vcpkg::Strings::to_utf8 helpers.

@ras0219-msft Thanks for creating the issue. Another question what is the project structure going to look like.  Are all system depended functions going to remain in  vcpkg_system.cpp or we would have to separate them like support/windows/vcpkg_system.cpp and support/linux/vcpkg_system.cpp like what they do with https://github.com/llvm-mirror/llvm/tree/master/lib/Support.

How about using the same technique as boost::nowide? It may help with option 2...

Yeah, boost::nowide is exactly along the lines of option 2.
@atkawa7 I would prefer to keep both implementations side-by-side in a single file for now. The reason I would see to add platform specific files is if we need to add APIs used across the codebase that aren't available everywhere, though this would need serious justification.
Example:

On Windows, we can leverage the system threadpool and we want to wrap it in some layers that are still threadpool-specific. On Linux, not only do we not have the threadpool, we (in this hypothetical example) don't even have a way to implement a similar API surface and need #ifdefs at every usage location to do some locally custom workaround.
Thus, we might have a Windows-specific file for those threadpool APIs which are entirely unused and unavailable on other platforms.

I can't think of any situation currently where it wouldn't make sense to have the API available on all platforms, thus we shouldn't need platform-specific files.

A note on porting to Linux: are you sure this makes sense? Instead of heaving some sort of compromise, why not having something which works perfectly on Windows? I suggest instead to investigate support for cross-compilation scenarios on Windows for other target platforms. As far as I can tell this would be a unique feature for a "brewing" package manager and extremely useful.

@paul-michalik I think it does make a lot of sense. See #57.

#57 is not a justification... It's just an opinion which may be subject to discussion. Still, I believe that a brewing package manager capable of serving various target platforms from Windows would be very valuable.

@ras0219-msft Just wondering. How do you deal with __interface. It seems when I replace it with class + public: or struct I get so many errors  method with override specifier 'override' did not override any base class in vcpkg_dependencies.cpp related to class AdjacencyProvider

@paul-michalik Sorry, I think I wasn't clear in naming this issue.
This is not representing official support from Vcpkg for running on Linux. This issue is intended to represent that we're willing to work with anyone who wants to attempt it -- which @atkawa7 has indicated he'd like to :).
I firmly believe that making the codebase more cross-platform (and therefore accessible to more compilers and static analysis tools) will improve the overall code quality and have benefits even for Windows.
As for cross-compiling from Windows to other platforms, I would personally love to have that! However, there are obstacles that need ironing out:

Every additional supported platform introduces a large burden onto maintainers, who often only care about the one or two platforms they primarily target.
Is cross-compiling the right answer, or would it be better to just wrap a native Linux distribution instead (i.e. maybe we just wrap Gentoo/pacman/apt-get)? Wrapping should result in higher quality packages, but it would also cause version skew across platforms.

Exactly as you expressed above, every additional supported configuration is a compromise, so we are instead currently focused on making the Windows-on-Windows experience as perfect as we can!
@atkawa7 You'll need to mark all the functions as virtual void foo() = 0. See https://docs.microsoft.com/en-us/cpp/cpp/interface for more details.

@ras0219-msft Another question. Just wondering with these lines in vcpkg_system.cpp why  vcpkg uses environment to get architecture? And not using macros such as those defined here Architectures.
Optional<CPUArchitecture> to_cpu_architecture(CStringView arch)
    {
        if (Strings::case_insensitive_ascii_compare(arch, "x86") == 0) return CPUArchitecture::X86;
        if (Strings::case_insensitive_ascii_compare(arch, "x64") == 0) return CPUArchitecture::X64;
        if (Strings::case_insensitive_ascii_compare(arch, "amd64") == 0) return CPUArchitecture::X64;
        if (Strings::case_insensitive_ascii_compare(arch, "arm") == 0) return CPUArchitecture::ARM;
        if (Strings::case_insensitive_ascii_compare(arch, "arm64") == 0) return CPUArchitecture::ARM64;
        return nullopt;
    }

    CPUArchitecture get_host_processor()
    {
        auto w6432 = get_environment_variable(L"PROCESSOR_ARCHITEW6432");
        if (auto p = w6432.get()) return to_cpu_architecture(Strings::to_utf8(*p)).value_or_exit(VCPKG_LINE_INFO);

        auto procarch = get_environment_variable(L"PROCESSOR_ARCHITECTURE").value_or_exit(VCPKG_LINE_INFO);
        return to_cpu_architecture(Strings::to_utf8(procarch)).value_or_exit(VCPKG_LINE_INFO);
    }

See https://github.com/Microsoft/vcpkg/blob/master/toolsrc/src/vcpkg_System.cpp#L26-L43

The host that vcpkg was built for doesn't necessarily map to the true host architecture. Bootstrap always builds for x86, for example.

Thanks @ras0219-msft

So would you recommend using something like on linux
#include <sys/utsname.h>

CPUArchitecture get_host_processor()
    {
        struct utsname info;

        if (uname(&info) == -1)
        {
            return to_cpu_architecture(std::string()).value_or_exit(VCPKG_LINE_INFO);
        }
        return to_cpu_architecture(info.machine).value_or_exit()
    }

I think you are just after the string "x86" or x64" here?

The codebase now builds on Linux! Thank you very much @atkawa7 for starting this :)
See #1528 for details on how to try it out.

@ras0219-msft Awesome !!!

@ras0219-msft Do you have a example on how we could build it?

In https://github.com/Microsoft/vcpkg/pull/1528#issuecomment-346975155 I (very concisely) lay out the gist of how to build it. There's a toolsrc\CMakeLists.txt, but it requires a recent g++ -- I've listed out the exact command lines that work in WSL inside that comment.


any breaking changes from 0.6 to 0.7 ?

Are there any breaking changes or syntax changes coming from 0.6 to 0.7.0 ?
List views seem to be affected.

Yes, there are some needed breaking changes. Read the release notes (always).
https://github.com/rstoenescu/quasar-framework/releases/tag/v0.7.0

Thanks, I couldn't find the release notes , but I know now where to look for future releases.
Love this framework!


async/await using tokio

This builds on top of the work from #15 porting it to std::future and streams.

ping @dylanmckay


Update scala-collection-compat to 2.4.2

Updates org.scala-lang.modules:scala-collection-compat from 2.3.2 to 2.4.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang.modules", artifactId = "scala-collection-compat" } ]

labels: library-update, semver-minor

Superseded by #105.


Link does not work anymore in the README.

Hi all,
It looks like the link does not work anymore in this tutorial.
Thanks.

Fixed by https://github.com/efabless/caravel_user_project/pull/41


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26005

TagBot fix

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26045

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27584

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27584

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/45624

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86607

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87392

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/91710

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


fix: allow combined prefix and suffix children for TextField component

This PR is meant as a proposal for allowing TextField and Combobox components to have combined Affix child components. This would help in use cases where both a prefix and a suffix is needed (eg. a label prefix and a button suffix).
It would also widen the types to accept conditional rendering of Affix children, like this:
const hasAffix = true;
<TextField>
    {hasAffix && <Affix />}
</TextField>

Pros:

Allows combined prefix and suffix
Types accept conditional rendering of Affix child components

Cons:

Since the TS types will accept multiple Affix child components, no compile-time guarantee is given for correct usage. However, it's already possible to render multiple prefix and suffix children, even though the result is not necessarily correct.

I would like to hear your opinion before moving forward with this proposal.

Great! This was missing.


Can' t compile at rustc 1.24.0-nightly (7eb64b86c 2017-12-20)

My environments
$ rustup run nightly rustc --version
rustc 1.24.0-nightly (7eb64b86c 2017-12-20)
$ uname -rvm
4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64
$ lsb_release -sd
Ubuntu 16.04.3 LTS

Actual Output
$ rustup run nightly cargo build
   Compiling modbus_server v0.1.0 (file:///home/kubo39/dev/rust/modbus/tokio-modbus)
warning: unused imports: `BoxFuture`, `Sink`
  --> src/bin/main.rs:19:31
   |
19 | use futures::{future, Future, BoxFuture,Stream,Sink};
   |                               ^^^^^^^^^        ^^^^
   |
   = note: #[warn(unused_imports)] on by default
warning: unused import: `std::thread`
  --> src/bin/main.rs:20:5
   |
20 | use std::thread;
   |     ^^^^^^^^^^^

warning: unused import: `std::sync::mpsc::channel`
  --> src/bin/main.rs:21:5
   |
21 | use std::sync::mpsc::channel;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^

warning: unused imports: `ErrorKind`, `Read`, `Write`
  --> src/bin/main.rs:23:21
   |
23 | use std::io::{self, ErrorKind, Write,Read};
   |                     ^^^^^^^^^  ^^^^^ ^^^^

warning: use of deprecated item 'futures::BoxFuture': removed without replacement, recommended to use a local extension trait or function if needed, more details in https://github.com/alexcrichton/futures-rs/issues/228
  --> src/bin/main.rs:19:5
   |
19 | use futures::{future, Future, BoxFuture,Stream,Sink};
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: #[warn(deprecated)] on by default

error[E0599]: no method named `decode` found for type `docopt::Docopt` in the current scope
  --> src/bin/main.rs:79:25
   |
79 |         .and_then(|d| d.decode())
   |                         ^^^^^^

error: aborting due to previous error

error: Could not compile `modbus_server`.

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

FYI I am very new to rust and trying to use this package. I ran into the same problem. I am working off the default branch (commit 4999aafb9d17e0675350df5a3661e42202d69340)
$ ~/.cargo/bin/cargo version
cargo 1.53.0-nightly (0ed318d18 2021-04-23)

Output of ~/.cargo/bin/cargo build --verbose
error[E0599]: no method named `decode` found for struct `Docopt` in the current scope
  --> src\bin\main.rs:79:25
   |
79 |         .and_then(|d| d.decode())
   |                         ^^^^^^ method not found in `Docopt`

warning: unused import: `Future`
  --> src\bin\main.rs:19:23
   |
19 | use futures::{future, Future, BoxFuture,Stream,Sink};
   |                       ^^^^^^

warning: unused import: `Stream`
  --> src\bin\main.rs:19:41
   |
19 | use futures::{future, Future, BoxFuture,Stream,Sink};
   |                                         ^^^^^^

error: aborting due to previous error; 8 warnings emitted

For more information about this error, try `rustc --explain E0599`.
error: could not compile `modbus_server`

I edited Cargo.toml so that tokio-core = "=0.1.7" (guessing from ages shown on crates.io), but that didn't seem to help (nor did trying other versions). Eventually, I noticed that there was a dependency related to the error message: docopt = "*", so instead I changed that to docopt = "0.7" and then was able to build without error.


Execution play with rework

This is a first very rough version of the execution play feature. We are merging it especially in the context of the release 0.0.1. More validation still needs to be done and an overall better management of the executions, but this still provides users with the possibility to run executions on their own machine (not in a container).

Pull Request Test Coverage Report for Build 193

191 of 289 (66.09%) changed or added relevant lines in 24 files are covered.
6 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-4.007%) to 90.274%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server/resources/pipeline_boutiquesdescriptor.py
15
16
93.75%

server/resources/executions.py
0
1
0.0%

server/resources/decorators/init.py
1
3
33.33%

server/resources/helpers/path.py
1
3
33.33%

server/logging/setup.py
0
3
0.0%

server/startup_validation.py
1
5
20.0%

server/resources/helpers/register.py
12
17
70.59%

server/resources/helpers/pipelines.py
37
47
78.72%

server/resources/execution_play.py
13
35
37.14%

server/resources/helpers/execution.py
17
41
41.46%

Files with Coverage Reduction
New Missed Lines
%

server/resources/execution_play.py
1
37.84%

server/resources/decorators/init.py
1
92.19%

server/resources/helpers/register.py
2
72.97%

server/resources/register.py
2
85.71%

Totals

Change from base Build 157:
-4.007%

Covered Lines:
1847

Relevant Lines:
2046

💛  - Coveralls

Pull Request Test Coverage Report for Build 193

191 of 289 (66.09%) changed or added relevant lines in 24 files are covered.
6 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-4.007%) to 90.274%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server/resources/pipeline_boutiquesdescriptor.py
15
16
93.75%

server/resources/executions.py
0
1
0.0%

server/resources/decorators/init.py
1
3
33.33%

server/resources/helpers/path.py
1
3
33.33%

server/logging/setup.py
0
3
0.0%

server/startup_validation.py
1
5
20.0%

server/resources/helpers/register.py
12
17
70.59%

server/resources/helpers/pipelines.py
37
47
78.72%

server/resources/execution_play.py
13
35
37.14%

server/resources/helpers/execution.py
17
41
41.46%

Files with Coverage Reduction
New Missed Lines
%

server/resources/execution_play.py
1
37.84%

server/resources/decorators/init.py
1
92.19%

server/resources/helpers/register.py
2
72.97%

server/resources/register.py
2
85.71%

Totals

Change from base Build 157:
-4.007%

Covered Lines:
1847

Relevant Lines:
2046

💛  - Coveralls


Getting error while running Configure.ps1 script

Logs:
Creating the AAD application (ProfileAPI)
Done creating the service application (ProfileAPI)
Getting access from 'service' to 'Microsoft Graph'
Set-AzureADApplication : Error occurred while executing SetApplication
Code: Request_BadRequest
Message: Invalid value specified for property 'resourceAppId' of resource 'RequiredResourceAccess'.
RequestId: 96a0308b-f89a-4cdd-a37e-63d6448c875c
DateTimeStamp: Sat, 13 Jun 2020 02:16:04 GMT
Details: PropertyName  - resourceAppId, PropertyErrorCode  - InvalidValue
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
At C:\Users\v-alfila\ms-identity-javascript-react-spa-dotnetcore-webapi-obo\AppCreationScripts\Configure.ps1:336 char:4
+    Set-AzureADApplication -ObjectId $serviceAadApplication.ObjectId - ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-AzureADApplication], ApiException
    + FullyQualifiedErrorId : Microsoft.Open.AzureAD16.Client.ApiException,Microsoft.Open.AzureAD16.PowerShell.SetApplication

@greybax sorry for the delay -looks like there was some issue with connecting to Azure AD.  Can you verify that Azure Portal is accessible while you're running the script?

Closing this due to inactivity. Let us know if your issue persists.


User added to site access after upgrade is lost after rollback

Rancher versions:
rancher/server: v1.6.7 to v1.6.9-rc5
Docker version: (docker version,docker info preferred)
**Operating system and kernel: (cat /etc/os-release, uname -r preferred)**Ubuntu
**Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)**GCE/DO
**Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)**Single node
**Environment Template: (Cattle/Kubernetes/Swarm/Mesos)**Cattle
Steps to Reproduce:

Create a setup in v1.6.7 with AD enabled and provide site access to two users
Upgrade to v1.6.9-rc5.
After upgrade, add another user "testnewuser" to site access and verify that the user has access to the setup
Rollback to v1.6.7.

After rollback, 'testnewuser' is not listed in the site access page and does not have access to the setup.

Ping @mrajashree @prachidamle. Should this be documented as a known issue? I recall us discussing that if you were to rollback from new-AD to old-AD, you would get the old AD's config because we started saving the config differently. But it looks like we did not add that as a release note.
CC @deniseschannon

I did note it as an issue, but in the rollback section. I don't believe we'll be able to fix this for rollback due to how we handle settings.

Note on Rollback: If you are rolling back and have authentication enabled using Active Directory, any new users/groups added to site access on the Access Control page after the upgrade will not be retained upon rolling back. Any users added before the upgrade will continue to remain. [#9850]


Composite rule group with different set of facts for each rule

I have a requirement to execute composite rule in a manner that
each rule have a set of facts. The engine should execute each rule with its associated facts and find out the whole rule.
I think the UnitRuleGroup is an implementation of AND like condition. is there any rule implementation available for OR condition.
Please suggest

ActivationRuleGroup can do it well

ActivationRuleGroup is XOR logic, not OR logic.
https://github.com/j-easy/easy-rules/blob/ab75210854e06dff39469bd0a42b8c45ebf826ed/easy-rules-support/src/main/java/org/jeasy/rules/support/composite/ActivationRuleGroup.java#L32-L33


Fix spelling error in inspecting-the-json-structure.md

Change
FROM:
Inspecing the structure of nasa.json
TO:
Inspecting the structure of nasa.json

Added helpful jq hint to "Get the first ten documents in a json list."
Ran dos2unix to fix extraneous ^M.
Commit d60643a addresses this issue.


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or another core contributor signed this repository up for Open Collective. This pull request adds financial contributors from your Open Collective https://opencollective.com/criticalmaps-android ❤
What it does:

adds a badge to show the latest number of financial contributors
adds a banner displaying contributors to the project on GitHub
adds a banner displaying all individuals contributing financially on Open Collective
adds a section displaying all organizations contributing financially on Open Collective, with their logo and a link to their website

P.S: As with any pull request, feel free to comment or suggest changes.
Thank you for your great contribution to the Open Source community. You are awesome! 🙌
And welcome to the Open Collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other Open Source sustainers!

@mltbnz maybe worth adding for ios as well...?

Think so too


Updated Fly.prototype.watch in docs

Updated to add options and made it clear that the tasks, and options that are passed are the same as Fly.prototype.start.

@tjbenton Thanks!! :+1:

@bucaran You're welcome!


Caching feature

This PR re-introduces repository caching as official/default mbed CLI feature:

caching is enabled by default and uses the system/user default temp dir
a user can override the cache location via the CACHE config setting
a user can disable caching by setting up the CACHE_DISABLED config variable
improved handling of mbed library builds (.bld/mbed 2.0)

Also fixes how cached repositories are handling across different protocols (e.g. cached ssh repo is cloned as https repo)
Reviewers:

[ ] @sg-
[ ] @theotherjimmy

Also cc @bridadan as this might have implications with the CI

LGTM 👍
Looks to be enabled by default, is there a flag or global setting to disable caching?

@sg- Nice suggestion! Now implemented via the cache_disabled config option.

LGTM 👍

@screamerbg Can't wait to see this guy in CI :smile:


Ignore modules with pom packaging

Having maven multi module builds the parent module is normally of packaging type pom, so there are no source folders. But the kslint maven Plugin is passing the default source folders to ktlint which results in 3 warnings.
Kind regards
Michael

@reitzmichnicht, thanks for reporting this issue. There are reasons why you may have Kotlin files in a module with pom packaging (e.g. projects that have Maven and Gradle build scripts), so skipping ktlint entirely isn't an option. But for modules with pom packaging I've reduced the logging for missing directories from WARN to DEBUG. You can find this change in #209. This change is in the 0.9.24 release of this plugin.

Thank you for the quick fix, works now as expected


Cross compilation

Hello,
Is it possible to do cross-compilation with node-gyp? I want to compile native addon for linux while running node-gyp build on Windows machine.
I am able to build addon on each of the platforms, but I would like to do cross compilation.
Thank You,
Peter

It's not explicitly supported at the moment and there are a few places in node-gyp where it assumes that the host arch/os == the target arch/os although you can probably work around that without too much effort.
More importantly, add-ons need to be compatible with cross-compiling.  Add-ons with simple binding.gyp files probably are but more complex ones need not be.

@bnoordhuis, i have a similar question.  I've been toying with electron-rebuild.  as you may be aware, my node version !== electron's node version, so electron-rebuild has to recompile some modules against it's version.  I see the rebuild module doing something like npm rebuild --target=TARGET_VERSION --arch=ARCH_VERSION.  That doesn't seem to reliably product builds to my expectation.  e.g. node v0.12.7 has process.versions.modules == 14, while my electron's === 44.  the above command still seems to build against 14, vs 44 like I expect.
Do you have any tips on how I can best use npm to recompile against a target version?  Assume that I have the target header files already downloaded.  I need to use npm vs explicit node-gyp as there may be other lifecycle hooks that must be run for a module at install.
I will gladly add to the README with pertinent docs if you can assist!

@cdaringe You probably need to specify --nodedir /path/to/sources, otherwise it's assumed you're targeting the same binary that is used to execute node-gyp.

@bnoordhuis, thanks, I'll check it out.  I did trace my original problem to the fact that some npm lifecycle scripts were conditionally rebuilding based on process.xzy, where the process was the sys process vs. the electron node process.  I updated my stuff to rebuild using electron's node by appending env: ATOM_SHELL_INTERNAL_RUN_AS_NODE.  yahtzee!

+1

Has any progress been made on this? Also is changing the OS inside node-gyp enough to make it cross compile?

Well, I need to cross compile, so I'll be messing around with node-gyp or alternatively using raw gyp. I'll let you know how it goes.

Any update on this @tyduptyler13 ?

I have yet to prove this but I am pretty sure you can pull it off if you compile node itself from the platform you are compiling on as well. The reason being, it needs the same mangling scheme as your addon. I will get around to doing this soon. I am currently moving and starting a new job so I'm a bit busy lately.
It would be nice if there is a way to create a translation layer between windows and linux compiled code so that you can still do the dynamic linking at runtime (how node calls your stuff)

@tyduptyler13 So uh.. webassembly?

@tyduptyler13 So uh.. webassembly?

That's would be cool :-P

Web assembly is a target of mine, it usually has the same mangling scheme as clang as it sort of emulates the behavior of a compiled C/C++ application.
Another point I can make is that if your addon only exposes C style anythings, you can totally get away with cross platform compiles because C doesn't get its names mangled. Hence the "extern C" stuff in lots of the old school addons.
I was exploring to see if node-gyp could just do some of this mangling management, but I haven't gotten deep enough to say yet. Either its loader could handle these weird schemes internally when selecting the C++ name OR it could try cheating and use ASM flags to manually set the name. The ASM would probably be easier, but could have issues if you don't handle all of the weirdness with namespaces, class names, templates, inheritance, etc.

Also, side note: tempted to create a node driven build platform that sort of follows Gulp but would be more flexible in what it can compile. The goal is to allow node to compile c/c++/etc. That way I can remove gyp entirely and simplify the build process. Effectively it would be among gyp, make, cmake, and autotools type tools. This would definitely increase cross platform support. Would any of you be interested in using such a thing?

This would definitely increase cross platform support. Would any of you be interested in using such a thing?

Probably me, to port all my NodeOS custom build bash scripts :-) I was thinking also to do it myself, since I got them to have a somewhat similar structure and checkings (download sources, configure, make, make install), just only I don't have time, but would be a matter of porting them. You can take a look at them to know how they are organized and we could chat about moving it forward :-D

Hi, my electron application has node ref and ffi modules for dll linking and it works perfectly fine on windows with electron-rebuild and after electron-builder but when I clone the source code on Ubuntu 18 and run the electron-rebuild the created exe file says %1 is not win32 application.
Could anybody please help me out in this? I'm struggling a lot to get it worked.
Thanks in advance.

@mjangir You need to recompile your dll to .so for Linux and electron app will be work fine.
It maybe be better to create dinamic linking library for all support platforms, then create a nodejs addon with your export functions. Then you can compile the addon for the node or the Electron App.
If you have a question about creating add-ons, you can ask them

I'm going to close this because I think a pull request by someone who wants this is going to be the only way forward here. Otherwise this issue is just going to stay open perpetually with occasional drop-ins. This will require external help to get it moving anywhere if it's still needed.

@rvagg I was able to successfully rebuild native modules, even with electron-forge & electron-rebuild that utilize node-gyp under the hood (see https://github.com/electron/electron-rebuild/issues/378).
Cross-compilation from other host architectures seems to be easily achievable by prepending CC=arm-linux-gnueabihf-gcc CXX=arm-linux-gnueabihf-g++ CC_host="gcc -m32" CXX_host="g++ -m32" env variables before invoking node-gyp and requires minimal system configuration, only the installation of the target toolchain. How about merging this approach to the tool, so that it automatically sets the proper variables?

@artus9033 with what you're suggesting how would that work for building on Linux to support Windows platforms?

@rvagg wrote:

a pull request by someone who wants this is going to be the only way forward here.

@artus9033 wrote:

Cross-compilation from other host architectures seems to be easily achievable

Is there a pull request as @rvagg requested?

@artus9033 with what you're suggesting how would that work for building on Linux to support Windows platforms?

I haven't tested it yet, but when I find time, I will give x86_64-w64-mingw32-gxx a shot, set up analogically to the approach I described above.

@rvagg wrote:

a pull request by someone who wants this is going to be the only way forward

@artus9033 wrote:

Cross-compilation from other host architectures seems to be easily achievable

Is there a pull request as @rvagg requested?

@cclauss I will try to prepare one and reach out then, for now I just wanted to share this approach, as at the moment I don't have enough time to try to implement this as part of node-gyp.

Did anybody got any updates? I want to know where/how to get the shared libraries to link to the N-API functions while cross-compiling.

Did anybody got any updates? I want to know where/how to get the shared libraries to link to the N-API functions while cross-compiling.

I've writing an N-API extension on Node.js 14.16.0
Works well under Linux, compiled with GNU-gcc 8.3.0 but requires VisualStudio 2019 to address Windows server 2016.
When cross compiling from Linux to target Windows with mingw x64, Node says : the extension does not self register.
Why the same code base (very near of the samples in official documentation) compiled or cross-compiled acts differently?
If necessary, I can push a minimalist reproducible code.


fix unbound variable error on release test envs

quick fix unbound variable error on release test env since -u is set

Adding this for posterity (TIL about default values in bash) https://stackoverflow.com/questions/15143863/bash-colon-operator-in-variable-substitution


Merge from Main to ludo-java21

@ludoch can you refresh your branch from main and only submit changes for review for the changes you are initiating? This looks like you might have been working from a stale branch.