ImportError: Numba could not be imported.

Am trying to set uo and environment for machine learning with pycaret
from pycaret.classification import * exp1 = setup(diabetes, target = 'Class variable')
and i am getting an error below

ImportError                               Traceback (most recent call last)
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typeconv\typeconv.py in
3     # Numba, if it fails to import, provide some feedback
----> 4     from numba.core.typeconv import _typeconv
5 except ImportError as e:
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
ImportError                               Traceback (most recent call last)
 in
1 from pycaret.classification import *
----> 2 exp1 = setup(diabetes, target = 'Class variable')
~\AppData\Roaming\Python\Python37\site-packages\pycaret\classification.py in setup(data, target, train_size, sampling, sample_estimator, categorical_features, categorical_imputation, ordinal_features, high_cardinality_features, high_cardinality_method, numeric_features, numeric_imputation, date_features, ignore_features, normalize, normalize_method, transformation, transformation_method, handle_unknown_categorical, unknown_categorical_method, pca, pca_method, pca_components, ignore_low_variance, combine_rare_levels, rare_level_threshold, bin_numeric_features, remove_outliers, outliers_threshold, remove_multicollinearity, multicollinearity_threshold, create_clusters, cluster_iter, polynomial_features, polynomial_degree, trigonometry_features, polynomial_threshold, group_features, group_names, feature_selection, feature_selection_threshold, feature_interaction, feature_ratio, interaction_threshold, session_id, silent, profile)
878
879     #import library
--> 880     from pycaret import preprocess
881
882     data = preprocess.Preprocess_Path_One(train_data = data,
~\AppData\Roaming\Python\Python37\site-packages\pycaret\preprocess.py in
24 from sklearn.decomposition import IncrementalPCA
25 from sklearn.preprocessing import KBinsDiscretizer
---> 26 from pyod.models.knn import KNN
27 from pyod.models.iforest import IForest
28 from pyod.models.pca import PCA as PCA_od
~\AppData\Roaming\Python\Python37\site-packages\pyod_init_.py in
2
3 from . import models
----> 4 from . import utils
5 # TODO: add version information here
6
~\AppData\Roaming\Python\Python37\site-packages\pyod\utils_init_.py in
9 from .data import generate_data
10 from .data import evaluate_print
---> 11 from .stat_models import pairwise_distances_no_broadcast
12 from .stat_models import wpearsonr
13 from .stat_models import pearsonr_mat
~\AppData\Roaming\Python\Python37\site-packages\pyod\utils\stat_models.py in
9
10 import numpy as np
---> 11 from numba import njit
12 from scipy.stats import pearsonr
13 from sklearn.utils.validation import check_array
~\AppData\Roaming\Python\Python37\site-packages\numba_init_.py in
18
19 # Re-export typeof
---> 20 from numba.misc.special import (
21     typeof, prange, pndindex, gdb, gdb_breakpoint, gdb_init,
22     literally, literal_unroll
~\AppData\Roaming\Python\Python37\site-packages\numba\misc\special.py in
1 import numpy as np
2
----> 3 from numba.core.typing.typeof import typeof
4
5
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typing_init_.py in
----> 1 from .context import BaseContext, Context
2 from .templates import (signature, make_concrete_template, Signature,
3                         fold_arguments)
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typing\context.py in
9 import numba
10 from numba.core import types, errors
---> 11 from numba.core.typeconv import Conversion, rules
12 from numba.core.typing import templates
13 from .typeof import typeof, Purpose
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typeconv\rules.py in
1 import itertools
----> 2 from .typeconv import TypeManager, TypeCastingRules
3 from numba.core import types
4
5
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typeconv\typeconv.py in
15            "possible please include the following in your error report:\n\n"
16            "sys.executable: %s\n")
---> 17     raise ImportError(msg % (url, reportme, str(e), sys.executable))
18
19 from numba.core.typeconv import castgraph, Conversion
ImportError: Numba could not be imported.

Kindly assist with a diagnosis and solution

This is likely a duplicate of #5600.  There is a workaround in the issue discussion that should help until we get a patch release out next week.

@mbtallbert thank you for raising this issue with the Numba issue tracker. @seibert I concur with that assessment, will label and close the issue. @mbtallbert in case this is a mistake, please feel free to re-open the issue with additional information, thanks!


wrong code for Context example

https://reactjs.org/docs/context.html

This theme should contain in a lambda, but seems the lambda disappeared.

This example has been updated. @gaearon Close this issue


graphics: Current restoring logic is wrong?

Now stale images are resolved BEFORE the game main logic, but this should be done AFTER that. The image becomes 'stale' e.g. if the image is both source and destination of drawing. I haven't checked this behavior with tests, so I'll check this.

Note: Another condition for stale is when the image drawing commands history is too big. This can happen easily (e.g. examples/sprites) but restoring (reading pixels from GPU) didn't happen since 'volatile' images like a screen don't need to be restored and in all examples, only the screen has such many drawing history.

The first issue regarding restoring timing is hard to test, but I think it's fixed...

Oops, https://github.com/hajimehoshi/ebiten/commit/7d236950c2e027f82b1775441a132e4d5f6f0e62 fixed #375, not #357


State of the art analysis (issue #142 related)

The aim is to find and summarize 20-30 articles considering the following fields:

[x] #307

[x] #308

[x] #309

[x] #310

It should be added to Mendeley which enables to generate a .bib file.

The issue will not be closed until all references are linked to sota.


Jedi <= 0.17.2 requires parso < 0.8.0

Issue:
As of today, if you have a fresh environment and install ipython (7.17 is current) then you get an incompatible version of parso and jedi.  This makes the tab-complete not work (which is bad).  I've tracked this down to the fact that the latest version of parso=0.8.0 (which is in conda-forge) requires jedi>0.17.2 (which is not in conda-forge, and in fact 0.17.2 is the latest tagged version of jedi).  The problem is that earlier versions of jedi did not explicitly put the restriction that they require parso<0.8.0 (which 0.17.1 and 0.17.2 do).  Therefore, the solver goes and grabs parso=0.8.0 and then finds that jedi=0.15.2 is compatible (according to the requirements), but it actually is not.
The solution, I believe, is to patch things so that jedi<=0.17.2 explicitly require parso<0.8.0.

Environment (conda list):

$ conda list
# packages in environment at /u1/ki/erykoff/lsst-rh10_20200810/conda/miniconda3-py37_4.8.2/envs/ipy717-3:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       1_gnu    conda-forge
backcall                  0.2.0              pyh9f0ad1d_0    conda-forge
backports                 1.0                        py_2    conda-forge
backports.functools_lru_cache 1.6.1                      py_0    conda-forge
ca-certificates           2020.6.20            hecda079_0    conda-forge
certifi                   2020.6.20        py38h32f6830_0    conda-forge
decorator                 4.4.2                      py_0    conda-forge
ipython                   7.17.0           py38h1cdfbd6_0    conda-forge
ipython_genutils          0.2.0                      py_1    conda-forge
jedi                      0.15.2                   py38_0    conda-forge
ld_impl_linux-64          2.34                 hc38a660_9    conda-forge
libblas                   3.8.0               17_openblas    conda-forge
libcblas                  3.8.0               17_openblas    conda-forge
libffi                    3.2.1             he1b5a44_1007    conda-forge
libgcc-ng                 9.3.0               h24d8f2e_14    conda-forge
libgfortran-ng            7.5.0               hdf63c60_14    conda-forge
libgomp                   9.3.0               h24d8f2e_14    conda-forge
liblapack                 3.8.0               17_openblas    conda-forge
libopenblas               0.3.10          pthreads_hb3c22a3_4    conda-forge
libstdcxx-ng              9.3.0               hdf63c60_14    conda-forge
ncurses                   6.2                  he1b5a44_1    conda-forge
numpy                     1.19.1           py38h8854b6b_0    conda-forge
openssl                   1.1.1g               h516909a_1    conda-forge
parso                     0.8.0              pyh9f0ad1d_0    conda-forge
pexpect                   4.8.0            py38h32f6830_1    conda-forge
pickleshare               0.7.5           py38h32f6830_1001    conda-forge
pip                       20.2.2                     py_0    conda-forge
prompt-toolkit            3.0.6                      py_0    conda-forge
ptyprocess                0.6.0                   py_1001    conda-forge
pygments                  2.6.1                      py_0    conda-forge
python                    3.8.5           h4d41432_2_cpython    conda-forge
python_abi                3.8                      1_cp38    conda-forge
readline                  8.0                  he28a2e2_2    conda-forge
setuptools                49.6.0           py38h32f6830_0    conda-forge
six                       1.15.0             pyh9f0ad1d_0    conda-forge
sqlite                    3.32.3               h4cf870e_1    conda-forge
tk                        8.6.10               hed695b0_0    conda-forge
traitlets                 4.3.3            py38h32f6830_1    conda-forge
wcwidth                   0.2.5              pyh9f0ad1d_1    conda-forge
wheel                     0.34.2                     py_1    conda-forge
xz                        5.2.5                h516909a_1    conda-forge
zlib                      1.2.11            h516909a_1007    conda-forge

Details about  conda and system ( conda info ):

$ conda info
     active environment : ipy717-3
    active env location : /u1/ki/erykoff/lsst-rh10_20200810/conda/miniconda3-py37_4.8.2/envs/ipy717-3
            shell level : 2
       user config file : /afs/slac.stanford.edu/u/ki/erykoff/.condarc
 populated config files : /afs/slac.stanford.edu/u/ki/erykoff/.condarc
          conda version : 4.8.2
    conda-build version : not installed
         python version : 3.7.6.final.0
       virtual packages : __cuda=8.0
                          __glibc=2.12
       base environment : /u1/ki/erykoff/lsst-rh10_20200810/conda/miniconda3-py37_4.8.2  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /u1/ki/erykoff/lsst-rh10_20200810/conda/miniconda3-py37_4.8.2/pkgs
                          /afs/slac.stanford.edu/u/ki/erykoff/.conda/pkgs
       envs directories : /u1/ki/erykoff/lsst-rh10_20200810/conda/miniconda3-py37_4.8.2/envs
                          /afs/slac.stanford.edu/u/ki/erykoff/.conda/envs
               platform : linux-64
             user-agent : conda/4.8.2 requests/2.22.0 CPython/3.7.6 Linux/2.6.32-754.27.1.el6.x86_64 rhel/6.10 glibc/2.12
                UID:GID : 10646:1092
             netrc file : /afs/slac.stanford.edu/u/ki/erykoff/.netrc
           offline mode : False

PRs welcome!

@conda-forge/jedi @conda-forge/parso Can you all comment on this?

I redirected OP to this repo. Original request was at https://github.com/conda-forge/jedi-feedstock/issues/34

mmk - is the requested change in the dependencies correct?

I have verified that this is indeed an issue and all old versions of jedi with loose dependency on parso are affected by it. This has also been reported upstream at https://github.com/davidhalter/jedi/issues/1654
Unfortunately, parso makes breaking changes in minor releases.
We can wait for parso-0.8.0 compatible jedi 0.18.0 to be released. But then the problem will occur again with the next minor of parso. So I think OP is right and we should hotfix old versions of jedi with loose dep on parso to the corresponding next minors.

OK. Can the devs of @conda-forge/jedi @conda-forge/parso please send a PR here to patch the data then?

You might need information from @davidhalter on which parso versions should be pinned for older jedi versions.

From https://github.com/davidhalter/parso/issues/148#issuecomment-673977148 I can infer that each version of jedi that specifies a minimum parso version should also specify a max that is less than the next minor version of parso?

Unfortunately, parso makes breaking changes in minor releases.

This is not a minor release. This is a pre-1.0 release and according to semantic versioning it's totally fine to break the API at that point. The API is not yet considered stable.
https://semver.org/

We can wait for parso-0.8.0 compatible jedi 0.18.0 to be released. But then the problem will occur again with the next minor of parso. So I think OP is right and we should hotfix old versions of jedi with loose dep on parso to the corresponding next minors.

I don't think that is the actual issue. The dependency resolver for conda does the wrong thing: It picks an older Jedi version when there is no reason to do that. That should be fixed and that is most likely an issue with conda. This does not happen with pip.

You might need information from @davidhalter on which parso versions should be pinned for older jedi versions.

I have unfortunately no idea which versions are compatible. I wanted to pin the parso versions a long time ago, but some people were unhappy, because back then the pip dependency resolver was even worse. I only started pinning recently.

P.S.: I also don't think there's any reason to use an older Jedi version, they are just worse and buggier.

I just want to point out that this is not really a fix of the actual problem.
It's probably also an incorrect assumption that Jedi 0.15.2 should be used with parso < 0.7.x.

This issue is still occurring when resolving an environment for Python 2. Jedi 0.17.x is not built for Python 2, so conda picks Jedi 0.16.0, and because that version does not pin Parso, and versions of Parso 0.8.0 were published that did not require Python >=3.6, conda picks Parso 0.8.0. Opened an issue here: https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/issues/81

Jedi 0.17.x is not built for Python 2, so conda picks Jedi 0.16.0

This is not true. 0.17.x works fine with Python 2.

Yes, the issue is not with Jedi, but with conda-forge. Jedi on conda-forge has different tarballs for each minor version of Python. Prior to today, there was not a tarball for Jedi 0.17.x - python 2.7 - the most recent was 0.16.0, which didn't pin parso <0.8.0, causing an issue for my python 2 conda environments.
However, this was just resolved here: https://github.com/conda-forge/jedi-feedstock/issues/36

Well I think the important thing that is not getting surfaced in this discussion is Python 2 was intentionally dropped by conda-forge earlier this year ( https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/491 ). This is aligned with larger community efforts where Python 2 has been dropped ( https://www.python.org/doc/sunset-python-2/ ) ( https://python3statement.org ).
While it's certainly great that the issue in this case was resolvable. It's important to be aware that there is no maintenance effort in conda-forge going towards Python 2. So one can reasonably expect environments on Python 2 to lag both in terms of package versions and fixes.
cc @conda-forge/core (for vis)


training weights

May I ask if you can send the link for training weights? Thank you very much for your work

The model weights have always been available under Releases:
https://github.com/Qualcomm-AI-research/FFNet/releases/tag/models


.from have to be implemented

implement this:
x = 'some/xpath//with[@atr="ss"]
jin = Jini.new
    .from(x)
    .remove_node(xpath)
    .to_s
puts jin # some//with[@atr="ss"]

closed as completed


Ensure all logs from PANW are included in Sentinel dashboard

Describe the bug
Logs from Cortex Data Lake are not showing up in the Sentinel dashboard. Palo Alto Networks/Microsoft mutual customer uses the CDL / Sentinel workbook integration for graphs, charts, etc. The queries are only pulling data from firewalls that are forwarding directly to Sentinel as opposed to logs from CDL (which receives logs from FWs and forwards them to Sentinel).
In that workbook, the logic “where DeviceProduct has ‘PAN-OS’” is used to leverage logs from PANW firewalls. However, it seems that logs coming from CDL have a different DeviceProduct value: ‘LF.” As a result, logs from CDL are not showing up in the workbook.
To Reproduce
Steps to reproduce the behavior:

Navigate to Sentinel dashboard (GitHub Repo: https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/PaloAlto-PAN-OS)
See that the charts do not pull CDL data

Expected behavior
The data visualized should be from both CDL and firewall data.

Hi @arshvishen123, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 20-02-2024. Thanks!

Hi @arshvishen123 Could you please share more details with detailed replication steps ,if needed will have teams meeting on this issue

+Pralay Roy @.***>
Hi Pralay, can you please work with this Murali (a representative from
Microsoft) on the Sentinel issue?
Arsh
On Wed, Feb 21, 2024 at 7:53 PM Murali Krishna Dev Uppugunduri <
@.***> wrote:

Hi @arshvishen123
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_arshvishen123&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=Itfd4o7ztq3J9gQqolOA6XhtPBOLUA0UIcWoD63gZNDipxW8Y5mX9PVt8v6ISOVz&s=OkvZtUtMVInIcu4fI1jaTgFgwHerbjgkI56e9FVATL8&e=
Could you please share more details with detailed replication steps ,if
needed will have teams meeting on this issue
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Azure_Azure-2DSentinel_issues_9958-23issuecomment-2D1958608381&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=Itfd4o7ztq3J9gQqolOA6XhtPBOLUA0UIcWoD63gZNDipxW8Y5mX9PVt8v6ISOVz&s=Y1mEjcdW_SuGmQEqwjm3rA4ASvC7Yy2BVwZ5siDZdiE&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BGFJSBMJ7D65O3TSIMORFGTYU26KNAVCNFSM6AAAAABDJKOQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYGYYDQMZYGE&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=Itfd4o7ztq3J9gQqolOA6XhtPBOLUA0UIcWoD63gZNDipxW8Y5mX9PVt8v6ISOVz&s=Hdkj4VW05o3qxyK9zI3b6-xEduoOJKnHnvdwtwj2L3M&e=
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @arshvishen123 / Pralay,Could you please share convenient time slots for teams meeting to v-muuppugund@microsoft.com,so we can do further trouble shooting on this issue

Hi @arshvishen123, Could you please check on above comment. Thanks!

Pralay and Manoj, can you please work with the MSFT team here. This ticket
has been open for a while now.
On Thu, Feb 29, 2024 at 12:34 AM v-sudkharat @.***>
wrote:

Hi @arshvishen123
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_arshvishen123&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=98qkv-qMDmaUnNrhYOA4q6hXcCoa_dxGttw7cyqf_Nw&e=,
Could you please check on above comment. Thanks!
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Azure_Azure-2DSentinel_issues_9958-23issuecomment-2D1970653243&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=T5kUFtPkNE8KJ4nJ1aCTSz3IYG2HQxBX_C9vzqUEEbY&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BGFJSBMNLUZN2K5DARM7JFLYV3TZPAVCNFSM6AAAAABDJKOQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TGMRUGM&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=pFUKRoc-TfPtlzGJOMLLoymrutZ4lZw-T4_fbP14eNY&e=
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Arsh

Hi Rajiv,
Please schedule a call on Monday IST to fix this issue.
Thanks & Regards
Pralat
On Thu, Feb 29, 2024 at 10:27 PM Arsh Vishen @.***>
wrote:

Pralay and Manoj, can you please work with the MSFT team here. This ticket
has been open for a while now.
On Thu, Feb 29, 2024 at 12:34 AM v-sudkharat @.***>
wrote:

Hi @arshvishen123
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_arshvishen123&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=98qkv-qMDmaUnNrhYOA4q6hXcCoa_dxGttw7cyqf_Nw&e=,
Could you please check on above comment. Thanks!
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Azure_Azure-2DSentinel_issues_9958-23issuecomment-2D1970653243&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=T5kUFtPkNE8KJ4nJ1aCTSz3IYG2HQxBX_C9vzqUEEbY&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BGFJSBMNLUZN2K5DARM7JFLYV3TZPAVCNFSM6AAAAABDJKOQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TGMRUGM&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=pFUKRoc-TfPtlzGJOMLLoymrutZ4lZw-T4_fbP14eNY&e=
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Arsh

Sounds good.
Microsoft Team, could we connect March 11th Monday at 9:30 AM IST / 11 PM
EST? I can send a Zoom invite.
Thanks,
Rajiv Kandiah |  Systems Engineer
Palo Alto Networks  |  Canada
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property of
Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.
https://register.paloaltonetworks.com/igniteontourtoronto
On Fri, Mar 8, 2024 at 10:55 AM Pralay Roy @.***>
wrote:

Hi Rajiv,
Please schedule a call on Monday IST to fix this issue.
Thanks & Regards
Pralat
On Thu, Feb 29, 2024 at 10:27 PM Arsh Vishen @.***>
wrote:

Pralay and Manoj, can you please work with the MSFT team here. This
ticket has been open for a while now.
On Thu, Feb 29, 2024 at 12:34 AM v-sudkharat @.***>
wrote:

Hi @arshvishen123
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_arshvishen123&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=98qkv-qMDmaUnNrhYOA4q6hXcCoa_dxGttw7cyqf_Nw&e=,
Could you please check on above comment. Thanks!
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Azure_Azure-2DSentinel_issues_9958-23issuecomment-2D1970653243&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=T5kUFtPkNE8KJ4nJ1aCTSz3IYG2HQxBX_C9vzqUEEbY&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BGFJSBMNLUZN2K5DARM7JFLYV3TZPAVCNFSM6AAAAABDJKOQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TGMRUGM&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=pFUKRoc-TfPtlzGJOMLLoymrutZ4lZw-T4_fbP14eNY&e=
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Arsh

+Michael Ong @.***>
Arsh
On Fri, Mar 8, 2024 at 8:03 AM Rajiv Kandiah @.***>
wrote:

Sounds good.
Microsoft Team, could we connect March 11th Monday at 9:30 AM IST / 11 PM
EST? I can send a Zoom invite.
Thanks,
Rajiv Kandiah |  Systems Engineer
Palo Alto Networks  |  Canada
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property
of Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.
https://register.paloaltonetworks.com/igniteontourtoronto
On Fri, Mar 8, 2024 at 10:55 AM Pralay Roy @.***>
wrote:

Hi Rajiv,
Please schedule a call on Monday IST to fix this issue.
Thanks & Regards
Pralat
On Thu, Feb 29, 2024 at 10:27 PM Arsh Vishen <
@.***> wrote:

Pralay and Manoj, can you please work with the MSFT team here. This
ticket has been open for a while now.
On Thu, Feb 29, 2024 at 12:34 AM v-sudkharat @.***>
wrote:

Hi @arshvishen123
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_arshvishen123&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=98qkv-qMDmaUnNrhYOA4q6hXcCoa_dxGttw7cyqf_Nw&e=,
Could you please check on above comment. Thanks!
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Azure_Azure-2DSentinel_issues_9958-23issuecomment-2D1970653243&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=T5kUFtPkNE8KJ4nJ1aCTSz3IYG2HQxBX_C9vzqUEEbY&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BGFJSBMNLUZN2K5DARM7JFLYV3TZPAVCNFSM6AAAAABDJKOQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TGMRUGM&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=pFUKRoc-TfPtlzGJOMLLoymrutZ4lZw-T4_fbP14eNY&e=
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Arsh

Hi team, was this closed?
Arsh
On Thu, Mar 21, 2024 at 9:39 AM Arsh Vishen @.***>
wrote:

+Michael Ong @.***>
Arsh
On Fri, Mar 8, 2024 at 8:03 AM Rajiv Kandiah <
@.***> wrote:

Sounds good.
Microsoft Team, could we connect March 11th Monday at 9:30 AM IST / 11 PM
EST? I can send a Zoom invite.
Thanks,
Rajiv Kandiah |  Systems Engineer
Palo Alto Networks  |  Canada
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property
of Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.
https://register.paloaltonetworks.com/igniteontourtoronto
On Fri, Mar 8, 2024 at 10:55 AM Pralay Roy @.***>
wrote:

Hi Rajiv,
Please schedule a call on Monday IST to fix this issue.
Thanks & Regards
Pralat
On Thu, Feb 29, 2024 at 10:27 PM Arsh Vishen <
@.***> wrote:

Pralay and Manoj, can you please work with the MSFT team here. This
ticket has been open for a while now.
On Thu, Feb 29, 2024 at 12:34 AM v-sudkharat @.***>
wrote:

Hi @arshvishen123
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_arshvishen123&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=98qkv-qMDmaUnNrhYOA4q6hXcCoa_dxGttw7cyqf_Nw&e=,
Could you please check on above comment. Thanks!
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Azure_Azure-2DSentinel_issues_9958-23issuecomment-2D1970653243&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=T5kUFtPkNE8KJ4nJ1aCTSz3IYG2HQxBX_C9vzqUEEbY&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BGFJSBMNLUZN2K5DARM7JFLYV3TZPAVCNFSM6AAAAABDJKOQHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TGMRUGM&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=TaMK1c37nC6elB3AYiepetqiFSs_nnrSAGs42zjzreg&m=5HFPGk6nJiKHjaWQRTQbVytyc9kCH-N0GFJtiC4_K6HbLZkH1Wr82MBuXIbq0vPn&s=pFUKRoc-TfPtlzGJOMLLoymrutZ4lZw-T4_fbP14eNY&e=
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Arsh

Hey @arshvishen123, Any update for us? Please let us know if anything required for our side. Thanks!

Hey @arshvishen123, Any update for us? Please let us know if anything required for our side. Thanks!
Hi @arshvishen123 ,Apologies for delay,PR has been raised ,will update you once pushed

Hi @arshvishen123 , we are closing your issue (https://github.com/Azure/Azure-Sentinel/issues/9958) as PR is raised ,as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation!


OpenJS Foundation Sustainability Collaboration Space Meeting 2024-09-30

Time
UTC Mon 30-Sep-2024 16:30 (04:30 PM):

Timezone
Date/Time

US / Pacific
Mon 30-Sep-2024 09:30 (09:30 AM)

US / Mountain
Mon 30-Sep-2024 10:30 (10:30 AM)

US / Central
Mon 30-Sep-2024 11:30 (11:30 AM)

US / Eastern
Mon 30-Sep-2024 12:30 (12:30 PM)

EU / Western
Mon 30-Sep-2024 17:30 (05:30 PM)

EU / Central
Mon 30-Sep-2024 18:30 (06:30 PM)

EU / Eastern
Mon 30-Sep-2024 19:30 (07:30 PM)

Moscow
Mon 30-Sep-2024 19:30 (07:30 PM)

Chennai
Mon 30-Sep-2024 22:00 (10:00 PM)

Hangzhou
Tue 01-Oct-2024 00:30 (12:30 AM)

Tokyo
Tue 01-Oct-2024 01:30 (01:30 AM)

Sydney
Tue 01-Oct-2024 02:30 (02:30 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Sustainability Collaboration Space+Meeting+2024-09-30&iso=20240930T1630
or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Sep+30%2C+2024+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1p2CTQDL49GZj6h-cq064_1Y4xQWQhUKhSN9UhAZXVvI/edit

Agenda
Extracted from sustainability-agenda labelled issues and pull requests from the openjs-foundation org prior to the meeting.
openjs-foundation/sustainability-collab-space

OpenJS + Open Source Pledge #12
Guide on Resource Allocation for JS Ecosystem Projects Post-Funding #9
Identify and Analyze Current Financial Status of OpenJS Projects #7
Invite projects to share their experiences with us #6
Document Sponsorship Platforms and Strategies for Maintainers #5
Create a blog post to announce the collab space  #3

Invited

Ecosystem Report Collab Space Members: @openjs-foundation/sustainability-collaboration-space

Observers/Guests
Notes
The agenda comes from issues labelled with sustainability-agenda across all of the repositories in the openjs-foundation org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
link for participants: https://zoom-lfx.platform.linuxfoundation.org/meeting/97342926119?password=39c25254-e7a3-4830-be8e-d54d63234bfb

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

Glad to see that the integration is working and we have an agenda and notes. Thanks for the support @mhdawson :heart:


[issue #275] fix waiting for consumers to be ready

Following the issue #275 already closed, I believe that it is better to throw an exception when the timeout is reached instead of logging a warning.
I got an issue after the time out is reached but the test is launched. After the test execution when calling stop-all it throws an exception because the time out was a warning telling us that something was not correctly set up.
15:56:08  13:56:08.822 [main] INFO - Pub rate    15.1 msg/s /  7.5 MB/s | Cons rate     9.9 msg/s /  5.0 MB/s | Backlog:  4.7 K | Pub Latency (ms) avg: 20.1 - 50%: 14.8 - 99%: 89.2 - 99.9%: 122.4 - Max: 122.4 | Pub Delay Latency (us) avg: 134.7 - 50%: 132.0 - 99%: 200.0 - 99.9%: 209.0 - Max: 209.0
15:56:21  13:56:19.002 [main] INFO - Pub rate    14.9 msg/s /  7.5 MB/s | Cons rate    10.3 msg/s /  5.2 MB/s | Backlog:  4.8 K | Pub Latency (ms) avg: 25.2 - 50%: 14.9 - 99%: 102.0 - 99.9%: 139.9 - Max: 139.9 | Pub Delay Latency (us) avg: 132.0 - 50%: 130.0 - 99%: 205.0 - 99.9%: 215.0 - Max: 215.0
15:56:31  13:56:29.182 [main] INFO - Pub rate    15.0 msg/s /  7.5 MB/s | Cons rate    10.4 msg/s /  5.2 MB/s | Backlog:  4.8 K | Pub Latency (ms) avg: 20.5 - 50%: 14.3 - 99%: 93.2 - 99.9%: 93.8 - Max: 93.8 | Pub Delay Latency (us) avg: 134.1 - 50%: 131.0 - 99%: 209.0 - 99.9%: 251.0 - Max: 251.0
15:56:31  13:56:29.372 [main] INFO - ----- Aggregated Pub Latency (ms) avg: 22.3 - 50%: 14.7 - 95%: 67.0 - 99%: 116.5 - 99.9%: 237.0 - 99.99%: 500.5 - Max: 743.4 | Pub Delay (us)  avg: 152.2 - 50%: 133.0 - 95%: 176.0 - 99%: 216.0 - 99.9%: 518.0 - 99.99%: 58451.0 - Max: 91599.0
15:56:31  13:56:29.696 [AsyncHttpClient-3-3] ERROR - Failed to do HTTP post request to http://<IP_ADDRESS>:8080/stop-all -- code: 500
15:56:31  13:56:29.697 [main] ERROR - Failed to run the workload '1 producer(s) / 1 consumers on 1 topic(s)' for driver 'driver-kafka/kafka.yaml'
15:56:31  java.util.concurrent.CompletionException: java.lang.IllegalArgumentException
15:56:31  	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) ~[?:?]
15:56:31  	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319) ~[?:?]
15:56:31  	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645) ~[?:?]
15:56:31  	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) ~[?:?]
15:56:31  	at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073) ~[?:?]

@merlimat could you take a look at it? Thank you!!


How to remove tooltip

Describe the bug
I added a tooltip using Tooltip.SetTip, but to remove it I tried two things, neither of which worked.

"" a weird empty tooltip
null well the previous tooltip is stuck on my screen till I stop the app :(

Workaround
ToolTip.SetTip(x, null);
ToolTip.SetIsOpen(x, false);

Workaround
ToolTip.SetTip(x, null);
ToolTip.SetIsOpen(x, false);

I don't see how this is a workaround and not a solution. In fact the second "workaround" is exactly how the ToolTip disappears on MouseLeave.
https://github.com/AvaloniaUI/Avalonia/blob/a2652f7c2a5f3f39b4320acc3cde7420f9c7e55b/src/Avalonia.Controls/ToolTipService.cs#L131

I don't see how this is a workaround and not a solution. In fact the second "workaround" is exactly how the ToolTip disappears on MouseLeave.
https://github.com/AvaloniaUI/Avalonia/blob/a2652f7c2a5f3f39b4320acc3cde7420f9c7e55b/src/Avalonia.Controls/ToolTipService.cs#L131

Well, i called it a workaround, as it felt "hacky", but perhaps it is a
solution.
On Wed, 13 Jan 2021 at 16:47, jhofinger<EMAIL_ADDRESS>wrote:

I don't see how this is a workaround and not a solution. In fact the
second "workaround" is exactly how the ToolTip disappears on MouseLeave.
https://github.com/AvaloniaUI/Avalonia/blob/a2652f7c2a5f3f39b4320acc3cde7420f9c7e55b/src/Avalonia.Controls/ToolTipService.cs#L131
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AvaloniaUI/Avalonia/issues/5287#issuecomment-759382789,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQZA72OXUO2YVWQLTM5C43SZV6N7ANCNFSM4WAOUSUA
.

--
Thanks
Dweep

Well, i called it a workaround, as it felt "hacky", but perhaps it is a
solution.
On Wed, 13 Jan 2021 at 16:47, jhofinger<EMAIL_ADDRESS>wrote:

I don't see how this is a workaround and not a solution. In fact the
second "workaround" is exactly how the ToolTip disappears on MouseLeave.
https://github.com/AvaloniaUI/Avalonia/blob/a2652f7c2a5f3f39b4320acc3cde7420f9c7e55b/src/Avalonia.Controls/ToolTipService.cs#L131
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AvaloniaUI/Avalonia/issues/5287#issuecomment-759382789,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQZA72OXUO2YVWQLTM5C43SZV6N7ANCNFSM4WAOUSUA
.

--
Thanks
Dweep

@djthegr8 usually you need to use Unset value to reset property, because "null" and "string.Empty" are valid values.  In case of tooltip it looks like this:
ToolTip.SetTip(this, AvaloniaProperty.UnsetValue);

// Or
this.ClearValue(ToolTip.TipProperty);

But in my opinion the real issue is with null value for tooltip, as you mentioned:
null well the previous tooltip is stuck on my screen till I stop the app :(

But in my opinion the real issue is with null value for tooltip, as you mentioned:
null well the previous tooltip is stuck on my screen till I stop the app :(

Quite precisely. Setting it to null should intuitively do the same thing as
UnsetValue. I just started out in Avalonia, and wasn't too aware regarding
this, so somebody like me would intuitively use null....
On Thu, 14 Jan 2021, 03:18 Max Katz<EMAIL_ADDRESS>wrote:

But in my opinion the real issue is with null value for tooltip, as you
mentioned:
null well the previous tooltip is stuck on my screen till I stop the app :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AvaloniaUI/Avalonia/issues/5287#issuecomment-759759514,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQZA75XGGX5JWWY7TKDK2LSZYIJ7ANCNFSM4WAOUSUA
.

Quite precisely. Setting it to null should intuitively do the same thing as
UnsetValue. I just started out in Avalonia, and wasn't too aware regarding
this, so somebody like me would intuitively use null....
On Thu, 14 Jan 2021, 03:18 Max Katz<EMAIL_ADDRESS>wrote:

But in my opinion the real issue is with null value for tooltip, as you
mentioned:
null well the previous tooltip is stuck on my screen till I stop the app :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AvaloniaUI/Avalonia/issues/5287#issuecomment-759759514,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQZA75XGGX5JWWY7TKDK2LSZYIJ7ANCNFSM4WAOUSUA
.

I agree with @djthegr8 , a null value should hide the tooltip.  Using code behind for this task is very problematic as my View Models are programed in a .Net Core DLL that does not link with front end libraries like WPF or Avalonia.


Add option to skip validation

Reasons for doing this will probably be related to performance. I'm inclined to say that skipping validation should result in a loud warning so that users do not get into the habit of doing this all the time.

Keep in mind that when skipping validation, we still probably want to preserve the validation pass that populates default values, so this goal might be in conflict with #570.


Forbid super in static class methods with server function directives

Static class methods that are annotated with "use cache" or "use server" must not call super.

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).


WebSub build hangs in the Ubuntu build

Description:
WebSub builds are hanging when starting to run the tests. This is only happening in Ubuntu. Hence disabled the tests from the snapshot publish.
Need to re-enable it.

This is fixed now.


Bug: documenting forked state while I work on a cleaner repro

Describe the bug
My Android Pixel and iPad are both logged in latest Converse (249) to cvoell.eth associated inbox Id and are in the group chat XMTP Eng 3.
Currently they are not receiving messages from other participants in the chat, but they do both see messages that I send from cvoell.eth on either account.
This is messy to diagnose because I was also testing earlier with groups that included accounts that did not have all their old installation keys removed, and with a bot that was on an old version of libxmtp.
So it is possible that this state where two installations keys from the same inbox id are in some forked state from the rest of the group, is a result of some invalid state from starting groups with accounts on older versions, etc.
Before I try and repro with new accounts, I just wanted to capture logs and screen shots here of the current state.
cameron-android-libxmtp-logs.log
cvoell.ios-libxmtp.logs.txt

Pixel cvoell.eth
iPad cvoell.eth
screenshot from slack

Expected behavior
No response
Steps to reproduce the bug
No response

Note right now, my devices are getting updates from each other, but no other updates in the XMTP Eng 3 groups, other groups are updating for both devices.


initialize project structure

Motivation:
It is important to establish a structure that all can work  with.
Specifically this helps to:

have one commonly established directory structure for godot
store images that are being worked on / yet to be established
space for documentation and concepts

Implementation Idea:
I would propose the following structure.
It would be great to get some feedback so that we can iterate on it further:
├── Arch-enemies --> Godot-Project
│   ├── icon.svg
│   ├── icon.svg.import
│   └── project.godot
├── docs --> Documentation and concepts !
│   ├── coding_conventions.md
│   ├── game_design
│   │   └── meeting_notes
│   │       └── 1_broad_concepts.md
│   ├── meeting_notes.md
│   └── README.md
├── FrontEnd-Space --> Images/Bitmaps and more
│   ├── final-assets
│   ├── README.md
│   └── wip-assets
├── LICENSE
└── README.md

my updated filestructure would look like that:
.
├── Arch-enemies
│   ├── assets
│   │   └── sprites
│   │       ├── bridgepuzzle
│   │       ├── combat
│   │       └── overworld
│   ├── icon.svg
│   ├── icon.svg.import
│   ├── project.godot
│   ├── scenes
│   │   ├── _debug
│   │   ├── game_scense
│   │   ├── main.tscn
│   │   └── menu
│   └── src
├── docs
│   ├── coding_conventions.md
│   ├── game_design
│   │   └── meeting_notes
│   │       └── 1_broad_concepts.md
│   ├── meeting_notes.md
│   └── README.md
├── FrontEnd-Space
│   ├── final-assets
│   ├── README.md
│   └── wip-assets
├── LICENSE
└── README.md

Looks really good, i assume the godot part is automatically generated by godot?
How are we gonna structure the code itself? Is that also automatically generated (if so then ignore this)

godot part is automatically generated by godot?

nope, at least no the folders and all.
I tried to find a structure that introduces some sort of separation of different aspects ( overworld, combat, puzzling, menu ... ) and thought that this structure might make sense.
Well and regarding the code:
I think we will position it within the specified sections or create a new structure in /src/ that will somewhat "mirror" the separation-idea.

ah very nice, that makes a lot of sense and i like the idea of mirroring the aspects in src.
The article has some really good advice, nice! thanks for linking it and coming up with the structure.

I would maybe add a section for common sprites, in case we have some that are used in multiple parts of the game.

Maybe in the docs we should make clear from when and where the notes are, like the meeting_notes.md are the notes from our first general meeting.
So adding folders for general, coding, game-design, assets and numbering the notes by their chronology?

So, like this? Is everyone okay with that?
.
├── Arch-enemies
│   ├── assets
│   │   └── sprites
│   │       ├── bridgepuzzle
│   │       ├── combat
│   │       └── overworld
│   ├── icon.svg
│   ├── icon.svg.import
│   ├── project.godot
│   ├── scenes
│   │   ├── _debug
│   │   ├── game_scense
│   │   ├── main.tscn
│   │   └── menu
│   └── src
├── docs
│   ├── coding_conventions.md
│   ├── meeting_notes
│   │   └── game_design_meetings
│   │       └── meeting_notes
│   │           └── 1_broad_concepts.md
│   │   └── general_meetings
│   │       └── meeting_notes.md
│   │   └── coding_meetings
│   │   └── ui_asset_meetings
│   └── README.md
├── FrontEnd-Space
│   ├── final-assets
│   ├── README.md
│   └── wip-assets
├── LICENSE
└── README.md

Looks good I think.

I do agree and would use this structure
your opinions on it ? @DerSimi @Raining-Cloud @trashsolid123 ?

Should be good, and if not we still can change it slightly later on

I think everyone agrees this is a good structure for now.


Added the lit Braziers in Wintertodt as a light source

Working code that implements the feature I proposed in https://github.com/RS117/RLHD/issues/308#issue-1244055520!
With/Without

"Flicker" effect

Added the Lit Brazier to lights.json
  {
    "description": "WINTERTODT_LIT_BRAZIER",
    "height": 300,
    "alignment": "CENTER",
    "radius": 600,
    "strength": 15,
    "color": [
        165,
        255,
        56
    ],
    "type": "FLICKER",
    "duration": 0,
    "range": 15,
    "objectIds": [
        "BURNING_BRAZIER_29314",
        "BURNING_BRAZIER_31926"
    ]
  },

https://github.com/Ben10164/RLHD/blob/9cb635344aa8b423caefeb6bef441d70684727f7/src/main/resources/rs117/hd/scene/lighting/lights.json#L29331-L29349
As well as moving the Doors of Dihn down to follow the Lit Brazier
  {
    "description": "WINTERTODT_DOOR",
    "height": 500,
    "alignment": "SOUTH",
    "radius": 1500,
    "strength": 15,
    "color": [
        165,
        255,
        56
    ],
    "type": "STATIC",
    "duration": 0,
    "range": 0,
    "objectIds": [
        "DOORS_OF_DINH"
    ]
  }

https://github.com/Ben10164/RLHD/blob/9cb635344aa8b423caefeb6bef441d70684727f7/src/main/resources/rs117/hd/scene/lighting/lights.json#L29350-L29367

I'l take a look at this ingame, some quick thoughts for now:
I expect that trading some strength for radius (e.g. 600 radius, 15 str) would look better - it's a good rule to make radius at least around twice of the height, so that the light hits the floor properly and you don't have to overstrengthen it.
Is the light only on when the Brazier is lit?
Hop in the dev channel on discord sometime (:

I expect that trading some strength for radius (e.g. 600 radius, 15 str) would look better - it's a good rule to make radius at least around twice of the height, so that the light hits the floor properly and you don't have to overstrengthen it.

I'll get started on a new commit! I was confused on how to find a proper value for height.

Is the light only on when the Brazier is lit?

Yes it is! It's only for the IDs of the lot Brazier. I should've added a gif showing that!

Good to see more people around, hop in the dev channel on discord sometime (:

I was there earlier getting some help compiling, but I'll be more active!

Nice work!


Set upper bound for numpy 1.20.0

pandas version under 1.0.5 is not compatible with numpy version 1.20.0, so I set an upper bound on numpy requirement.
See also numpy issue #18355 and pandas issue #39520

Hi @Seonu-Lim,
Thanks for the PR! This is a big miss on my test, and a consequence of me not having a proper CI system in place at the moment.
PR lgtm, thanks!


[WIP] Add installation instructions for CentOS

Preview here

Daria, this looks good. But a couple of questions:

anyone else been able to follow the instructions with success?
You have WIP in title, and in-progress label.... are you pending anything before final review for potentially merging?

@andrewdavidmackenzie
Yes, I am pending that somebody else follows the instructions with success :)
Also,

was looking for approval from somebody from engineering, which I guess can be considered done
during the initial installation I had an issue with DNS resolution, which I couldn't reproduce later. There was some recent change related to it, I believe, so it would be good to test the whole process again on the latest revision of v2

You'll need to recruit a CentOS tester @mayorova ...

Sometimes the installation documentation is called INSTALL.md.
There are few documents that are in the root like GETTING_STARTED.md, CONTRIBUTING.md.
Usually the development instructions. Imo it could make sense to follow that and put rest in the docs folder .

I think best you just propose the actual docs to use and their names Michal - other wise each of the rest of us might have different opinions and different projects we use as references - and we do around and around. The main contribution of the PR is the doc content and I'd avoid getting stuck on exact file naming. You just chose.

Yep. Definitely not a blocker for merging. It just might cause some confusion on clear things up like in https://github.com/3scale/apicast/pull/159.

The instructions work on a clean CentOS 7 installation, given that the locales are correctly set. Otherwise, this bug might be hit and prevent the downloaded configuration from being applied correctly.


How to set num_classes?

Hi, thank you very much for sharing this code - I wanted to ask for some guidance on how to set the num_classes parameter.
I have a case where each bag has a label class X or class Y. When I set num_classes=2 some bags are predicted as [1, 1] or [0, 0] - these labels do not exist in my dataset (a bag cannot be both class X and Y or neither). So I think num_classes should be set to 1 such that predictions are either 0 or 1 - is that correct?
I am confused because the TCGA dataset is the same task - a bag is either LUAD or LUSC (it cannot be both or neither), yet in the code num_classes is set to 2? Why is this?
Thank you!

https://github.com/binli123/dsmil-wsi#feature-vector-csv-files-explanation
If you have a binary classification (true and false), it is regarded as 1 class. If you have two classes, and an optional negative class, it is regarded as 2 classes. TCGA has two classes + a negative class (benign region) that might exist in slides of both classes. In this case, if the prediction is [0, 0], it is counted as a benign sample and you potentially have a false negative for both classes.

Thank you very much for this answer :) I think I understand your explanation - so in the TCGA example is your thinking that, while there are no benign samples in the dataset, when presented with external data the model will be able to predict benign, whereas if 1 class is used the model will only ever be able to predict LUAD or LUSC?
Also, since there are no [0,0] [1,1] labels in the dataset does this have a negative effect on reported performance?

I think there is a viewpoint to help understand. The critical instances are class-specific, so that each class has a corresponding critical instance. In dsmil.py, the author applys 'torch.sort' operator along dimension 0, which sort the output score for each class. Then the MIL aggregator of DSMIL (Figure 3 in paper) is done for each class by matrix multiplication without loop.

So now I have a classification task with 4 instances, should I set num_class to 4?

So now I have a classification task with 4 instances, should I set num_class to 4?

it did.


Updates to support Start Group and End Groups

export Message.Data and Index attributes
add information about start/end groups to readme, and example

See the readme updates below and examples for more information.

https://github.com/paulmach/protoscan/issues/2


[UNTESTED] Added ripper for comicextra.com

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[ ] a bug fix (Fix #...)
[x] a new Ripper https://github.com/RipMeApp/ripme/issues/38#issuecomment-459969747
[ ] a refactoring
[ ] a style change/fix
[ ] a new feature

Description

Added new ripper for comicextra.com
Supports ripping of whole comic( all chapters) or individual chapter of a comic.
Each chapter is saved in a subdirectory, named as chapter-1, chapter-full etc.
Each image is named as page as the original file names are very long ( and garbled).
ex: 001_page.jpeg, 027_page.jpeg etc.

Testing
Required verification:

[ ] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[ ] I've verified that this change works as intended.

[ ] Downloads all relevant content.
[ ] Downloads content from multiple pages (as necessary or appropriate).
[ ] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[x] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[x] I've added a unit test to cover my change.

I've test this and confirmed it works


Wrong instruction for Amazon EKS Workshop > Helm > Deploy Example Microservices Using Helm > Customize Defaults

https://eksworkshop.com/helm_root/helm_micro/customize/
replicas: {{ .Values.replica }} should be replicas: {{ .Values.replicas }} as that is in values.yaml!

This has been corrected


Fix: filter branch HEAD

for-each-ref may list HEAD as one of the branches.
Before

After

the failures of os builds are irrelevant, they are fixed in #881


Uncaught SyntaxError: Invalid regular expression

[Enter steps to reproduce below:]

Start atom
Type in /*** and then the character @

This problem appears on my PC with Windows 7 64-bit, but this doesn't occur on my linux laptop. I have a german keyboard layout.
Atom Version: 0.199.0
System: lukas-PC
Thrown From: autoflow package, v0.23.0
Stack Trace
Uncaught SyntaxError: Invalid regular expression: /^/*** /: Nothing to repeat
At C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\autoflow\lib\autoflow.js:42

SyntaxError: Invalid regular expression: /^/\*** /: Nothing to repeat
  at new RegExp (native)
  at C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\autoflow\lib\autoflow.js:42:47
  at Object.module.exports.reflow (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\autoflow\lib\autoflow.js:45:13)
  at Object.module.exports.reflowSelection (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\autoflow\lib\autoflow.js:24:27)
  at atom-text-editor.atom.commands.add.autoflow:reflow-selection (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\autoflow\lib\autoflow.js:7:26)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\src\command-registry.js:238:29)
  at C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\src\command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:519:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:354:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (C:\Users\lukas\AppData\Local\atom\app-0.199.0\resources\app.asar\src\window-event-handler.js:178:20)

Commands
  4x -0:23.7.0 editor:newline (atom-text-editor.editor.is-focused)
  2x -0:23.2.0 core:move-up (atom-text-editor.editor.is-focused)
     -0:17.3.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:15.5.0 autoflow:reflow-selection (atom-text-editor.editor.is-focused)
  2x -0:14.3.0 editor:delete-to-beginning-of-word (atom-text-editor.editor.is-focused)
     -0:13.6.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:11.6.0 autoflow:reflow-selection (atom-text-editor.editor.is-focused)

Config
{}

Installed Packages
# User
language-powershell, v2.0.1

# Dev
No dev packages

Are you using a US English keyboard layout? Or some other one?

Sorry, a german keyboard layout.

Okay, in this case I think the issue can be closed, or? Ty very much, I was confused why that problem only occurs on windows.

Well, I think this is still a valid bug ... let me just try to reproduce it.

I can reproduce it using Atom v0.200.0-1a8ebd5 on Mac OS X 10.10.3 with the following repro steps:

Open Atom
Open a new file with Cmd+N
Type /*** into the editor
Execute the autoflow:reflow-selection command with Cmd+Alt+Q

Expected: Nothing to happen (no reflow needs to occur)
Actual: Error notification appears

Thanks so much for reporting this, it will be fixed in the next Atom release, 0.201.0


Don't reload znc.pem on every client connection

Need some way to poke ZNC to reload it instead.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29395815-don-t-reload-znc-pem-on-every-client-connection?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

One option is to use inotify

Just add an command like znc reloadcert or similar.
It will work for most purposes. Anyone who is using Letsencrypt (or any other CA) most likely already uses cron jobs to update the certificate and concatenate the cert files into znc.pem, so adding another cron job that reloads the cert after updating it shouldn't be an issue.

@muffeeee such command would require user to connect to ZNC via IRC protocol (and authenticate as some admin) from crontab.

No, I'm not talking about an IRC command - I'm talking about a UNIX command that can also be run manually from a terminal session.
znc reloadcert
Either that, or make service znc reload also reload cert, or make something like service znc reloadcert

@muffeeee The second part only works when ZNC is set up as a service which is NOT the default configuration.  The first operates on the principle that there's a way to pass a command to the running ZNC from the command like, which I don't think is possible as it currently exists.

Either way, my znc doesn't reload the cert on every connection anyway for some reason, so I'm still stuck with a soon-to-expire cert unless I restart znc.

No permissions to read the file?
ZNC does NOT cache cert in memory yet. This bug is exactly about this.
2016-01-17 14:50 GMT+00:00 muffe<EMAIL_ADDRESS>
Either way, my znc doesn't reload the cert on every connection anyway for
some reason, so I'm still stuck with a soon-to-expire cert unless I restart
znc.
—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/issues/1215#issuecomment-172331576.

You could make ZNC reload all config files including znc.pem on SIGHUP, SIGUSR1, or SIGRTMIN.

Is this bug about a performance improvement? Is there a significant impact? When I first read that znc reloaded it on every connection it seemed like a great idea to me.

It's about LetsEncrypt, no one cared before it came.

Yeah but the current behavior makes it easier to use it with letsencrypt (no need to do anything to reload certs), while this ticket is about not reloading it every time and possibly adding an extra manual reload step (which is how it works everywhere else, but still)
So I assume it's for performance reasons. Just wondering how big of a deal that is. I don't know znc's scalability requirements, either.

From what I have understood the longer term aim is to

Start ZNC as root
ZNC reads certs from /etc/letsencrypt/whatever
3.ZNC becomes the normal user and continues normally.

Or at least that has been wished without having to manually copy LE certs around the system and lose automatic renewals.

Start ZNC as root

Certainly no, see #1233

which is how it works everywhere else

That's the reason

If it's not done for performance benefit there is no reason to fix this. I consider it a feature.
And frankly the performance penalty of the file read is negligible. It's not a web server with thousands of connections requesting it constantly.
Otherwise triggering the reload of the certificate via handling SIGHUP is the best option.
Restarting znc to reload the certificate should not be considered.


Set back the ViewBackend to the previous bridge references

Falling back to the previous bridge Id because the current Surface is gone. This action prevents inconsistencies by keeping the ViewBackend i a consistent state pointing to a still valid bridge reference.
An example of a scenario that could generate this kind of inconsistency is a failed load request due to content filter policies. In that case, the client gone situation is reached because
Co-authored-by: Adrian Perez de Castro<EMAIL_ADDRESS>Acked-by: Adrian Perez de Castro<EMAIL_ADDRESS>Signed-off-by: Pablo Saavedra<EMAIL_ADDRESS>

@psaavedra Great find! I have incorporated a modified version of this patch as a commit in #158, so all the related changes can be reviewed together—this PR is not needed anymore.


Week 22 Review

2.7/3
Feature
Endpoint
Code
Plan

Score: 2.8/3
Requriments

[x] .1 Frontend UI demo.   UI takes inputs and passes them to an API and returns data from the backend to frontend.

Frontend is fetching data from backend on local host and displays on frontend

[x] .1  Postman API Demo.  JSON Raw/Body formatted API passes inputs to backend and updates persistent table.

Postman Demo worked and adds it to a list / updates the backend

[x] .1 - Java Demo - Object Creation.  Tester method that shows creation of Objects and outputs to Terminal, illustrate printing objects (hopefully using toString().

Extra

[x] .1 - Java Demo with Postman or UI - All CRUD methods.   Above was focused on Create and Read, this is focused on Update and Delete.

Delete function working to delete the objects


Inconsistence diagnostics result

We are having memory problems with the build of our project, and we have started to debug with diagnostic tool to see from where this problems come out.
So the approach we have followed is to try a git bisect approach to navigate to different points of the git history and execute the diagnostic tool to see the results:
go to a SHA point --> ./node_modules/.bin/tsc --diagnostics --> see results

In some of that points diagnostic tool output the problem with the memory:
./node_modules/.bin/tsc --diagnostics

<--- Last few GCs --->

[8419:0x102801600]   241827 ms: Mark-sweep 1407.0 (1507.6) -> 1406.9 (1478.1) MB, 1554.8 / 0.0 ms  (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1555 ms) last resort
[8419:0x102801600]   243178 ms: Mark-sweep 1406.9 (1478.1) -> 1406.9 (1478.1) MB, 1349.2 / 0.0 ms  last resort

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x3192c811bbd9 <JS Object>
    2: createTypeNodeFromObjectType [/Users/dave/projects/work/audiense/audiense/nebula/node_modules/ts-jest/node_modules/typescript/lib/tsc.js:23775] [pc=0x1fc0b05777eb](this=0xb2d5cb8a1e1 <JS Global Object>,type=0x96be025b41 <a Type with map 0x2f8e9d10e859>)
    3: createAnonymousTypeNode [/Users/dave/projects/work/audiense/audiense/nebula/node_modules/ts-jest/node_modules/typescript/lib/tsc....

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/local/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 4: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
 5: v8::internal::LCodeGenBase::PopulateDeoptimizationData(v8::internal::Handle<v8::internal::Code>) [/usr/local/bin/node]
 6: v8::internal::LChunk::Codegen() [/usr/local/bin/node]
 7: v8::internal::HCompilationJob::FinalizeJobImpl() [/usr/local/bin/node]
 8: v8::internal::(anonymous namespace)::GetOptimizedCode(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Compiler::ConcurrencyMode, v8::internal::BailoutId, v8::internal::JavaScriptFrame*) [/usr/local/bin/node]
 9: v8::internal::Compiler::Compile(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Compiler::ClearExceptionFlag) [/usr/local/bin/node]
10: v8::internal::Runtime_CompileLazy(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
11: 0x1fc0af9840bd
zsh: abort      ./node_modules/.bin/tsc --diagnostics

But then, we navigate to a know status of the project, were diagnostic tool worked well the last time, and we also obtain the memory problem output. So the problem is we are not obtaining a confidence and consistence result between executions
Are diagnostic tool generating some tmp files between executions that we should delete to obtain a consistence result? Any clue why is this happening?

    ]
  },
  "exclude": [
    "node_modules",
    "storybook"
  ]
}

Expected behavior:
Diagnostic should always return the same result between executions
Actual behavior:
After outputs a memory problem, diagnostic tool will always returns a memory problem in a point when it returned a success result before

Closing, because I wasn't cleaning the outDir between execution 😅


Linked File Submissions UI Updated

#980 #981 #982 #983
Updated the layout in Credit Transaction details so it shows the linked file submissions in the same way as the one in File Submission
Changelog:

Updated Credit Transaction Detail page
Replaced Last updated to Submitted on in File Submission List
Added timestamp besides status in File Submission detail

 SFS | Display submission date in the UI |2|

 SFS | Expose the date that the status changed in the UI |1|

 SFS | Hide remove link button for BCeID users for Linked Credit Transactions |2|

 SFS | Hide Linked Credit Transactions under certain statuses for BCeID users |3|


Some STM32 series require CONFIG_PM_DEVICE if CONFIG_PM=y

Describe the bug
Some STM32 series (g0, l0, l4, l5, wb, wl) require CONFIG_PM_DEVICE if CONFIG_PM=y. However, one should be able to have system PM enabled (CONFIG_PM=y) without the need of CONFIG_PM_DEVICE. It turns out that the device PM hooks are used in some cases, e.g. UART, to block system suspension until the peripheral is done. For more context, see https://github.com/zephyrproject-rtos/zephyr/pull/38383#discussion_r705402367. https://github.com/zephyrproject-rtos/zephyr/pull/38432 proposes an alternative solution that should allow disabling CONFIG_PM_DEVICE even when CONFIG_PM=y.
Note that no STM32 drivers implement actual device PM as of today.
To Reproduce
Look at:
soc/arm/st_stm32/stm32g0/Kconfig.defconfig.series
soc/arm/st_stm32/stm32l0/Kconfig.defconfig.series
soc/arm/st_stm32/stm32l4/Kconfig.defconfig.series
soc/arm/st_stm32/stm32l5/Kconfig.defconfig.series
soc/arm/st_stm32/stm32wb/Kconfig.defconfig.series
soc/arm/st_stm32/stm32wl/Kconfig.defconfig.series

Expected behavior
CONFIG_PM_DEVICE should not be a requirement to enable CONFIG_PM.
Impact

Firmware is required to be compiled with more resources than needed.
Device PM infrastructure is not being used to implement low power modes

Logs and console output
N/A
Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK 0.13.0
Commit SHA or Version used 9886d18c5c8c511e1ace9ff7afc40682d9d40e77

Additional context
https://github.com/zephyrproject-rtos/zephyr/issues/38382
https://github.com/zephyrproject-rtos/zephyr/pull/38383
https://github.com/zephyrproject-rtos/zephyr/pull/38432

Note that no STM32 drivers implement actual device PM as of today.

Well, gpio driver does...

Note that no STM32 drivers implement actual device PM as of today.

~Well, gpio driver does...~ That's PM_DEVICE_RUNTIME actually.
But I agree on the point. We should be able to enable only PM w/o PM_DEVICE

You're right, I missed that one.

Note that no STM32 drivers implement actual device PM as of today.

~Well, gpio driver does...~ That's PM_DEVICE_RUNTIME actually.
But I agree on the point. We should be able to enable only PM w/o PM_DEVICE

Actually, the code will not do PM when doing system PM (because low power is used for the PM state STM32 handles) but will do PM when using the runtime API. I think this illustrates quite well the problem of having LOW_POWER and SUSPEND. @ceolin

It is clear a problem these drivers need to enable CONFIG_DEVICE_PM to workaround the system PM. These options can be selected independently if needed.
Regarding the low power, I don't see a problem it as a major problem, from the subsystem perspective it is a hint to the device to save energy. It is up to the device decide what to do with it. That is something that will always be device specific, even if we had only SUSPEND  devices would still may interpret it in different manners (they may have multiple saving states).
The subsystem uses LOW_POWER when the sleep state is shallow and it needs to wake up fast, drivers can use it to set their equivalent state collaborating with the overall system.
This discussion is not particular to this issue, but  I see pros/cons in have multiple device states. The policy manager for devices can solve this problem. The proposed solution (https://github.com/zephyrproject-rtos/zephyr/pull/37823) is just replicating the current behavior, but we can device power states information per device in DT and make the policy consume it.

The problem of having both LOW_POWER and SUSPEND and treating them independently can cause problems. For example, a device can decide to just implement LOW_POWER, SUSPEND or both. Let's take a system with N devices, each implementing a random combination of the previous list. Now the system goes to a low power state where SUSPEND is used to put devices into a low power state. There will be a subset of devices, those implementing LOW_POWER only, that will just be left ON even though they can be put into a state that would save some power. The same would happen if LOW_POWER is used. The policy proposal in #37823 doesn't help to solve such cases. If there are multiple low power states, as there are now, the PM subsystem must be smart enough to take advantage of all cases. We can't move this problem to devices forcing to handle all cases, since then there's virtually no difference between LOW_POWER and SUSPEND states.

The problem of having both LOW_POWER and SUSPEND and treating them independently can cause problems. For example, a device can decide to just implement LOW_POWER, SUSPEND or both. Let's take a system with N devices, each implementing a random combination of the previous list. Now the system goes to a low power state where SUSPEND is used to put devices into a low power state. There will be a subset of devices, those implementing LOW_POWER only, that will just be left ON even though they can be put into a state that would save some power. The same would happen if LOW_POWER is used.

Note that the system power states documentation says what is more or less expected from a device when the system goes to state.
	/**
	 * @brief Runtime idle state
	 *
	 * Runtime idle is a system sleep state in which all of the cores
	 * enter deepest possible idle state and wait for interrupts, no
	 * requirements for the devices, leaving them at the states where
	 * they are.
	 *
	 * @note This state is correlated with ACPI S0ix state
	 */
	PM_STATE_RUNTIME_IDLE,
	/**
	 * @brief Suspend to idle state
	 *
	 * The system goes through a normal platform suspend where it puts
	 * all of the cores in deepest possible idle state and *may* puts peripherals
	 * into low-power states. No operating state is lost (ie. the cpu core
	 * does not lose execution context), so the system can go back to where
	 * it left off easily enough.
	 *
	 * @note This state is correlated with ACPI S1 state
	 */
	PM_STATE_SUSPEND_TO_IDLE,

The policy proposal in #37823 doesn't help to solve such cases. If there are multiple low power states, as there are now, the PM

It does not solve the problem as I stated there, but it is one step further, if the the information about which states a device implements were available the policy could be smarter.

subsystem must be smart enough to take advantage of all cases. We can't move this problem to devices forcing to handle all

How exactly the subsystem must be smart ? Removing LOW_POWER the only thing that the subsystem will be able to do is suspend or not suspend. All the hard work will still needed to be implemented by the device.

cases, since then there's virtually no difference between LOW_POWER and SUSPEND states.

What you mean here ? That devices are only active or suspended ? Or that most drivers were handling both states are the same ?

The problem of having both LOW_POWER and SUSPEND and treating them independently can cause problems. For example, a device can decide to just implement LOW_POWER, SUSPEND or both. Let's take a system with N devices, each implementing a random combination of the previous list. Now the system goes to a low power state where SUSPEND is used to put devices into a low power state. There will be a subset of devices, those implementing LOW_POWER only, that will just be left ON even though they can be put into a state that would save some power. The same would happen if LOW_POWER is used.

Note that the system power states documentation says what is more or less expected from a device when the system goes to state.
	/**
	 * @brief Runtime idle state
	 *
	 * Runtime idle is a system sleep state in which all of the cores
	 * enter deepest possible idle state and wait for interrupts, no
	 * requirements for the devices, leaving them at the states where
	 * they are.
	 *
	 * @note This state is correlated with ACPI S0ix state
	 */
	PM_STATE_RUNTIME_IDLE,
	/**
	 * @brief Suspend to idle state
	 *
	 * The system goes through a normal platform suspend where it puts
	 * all of the cores in deepest possible idle state and *may* puts peripherals
	 * into low-power states. No operating state is lost (ie. the cpu core
	 * does not lose execution context), so the system can go back to where
	 * it left off easily enough.
	 *
	 * @note This state is correlated with ACPI S1 state
	 */
	PM_STATE_SUSPEND_TO_IDLE,

The system PM code doesn't seem to follow these specs:

PM_STATE_RUNTIME_IDLE:  "no requirements for the devices, leaving them at the states where they are.". Now: they are all called to set LOW_POWER state.

There is also some lack of clarity:

PM_STATE_SUSPEND_TO_IDLE : "...into low-power states". Which states?. Now: LOW_POWER.

The policy proposal in #37823 doesn't help to solve such cases. If there are multiple low power states, as there are now, the PM

It does not solve the problem as I stated there, but it is one step further, if the the information about which states a device implements were available the policy could be smarter.

subsystem must be smart enough to take advantage of all cases. We can't move this problem to devices forcing to handle all

How exactly the subsystem must be smart ? Removing LOW_POWER the only thing that the subsystem will be able to do is suspend or not suspend. All the hard work will still needed to be implemented by the device.

 Or use LOW_POWER if SUSPEND is not implemented, etc. As of today, this is effectively deferred to the drivers, which led to "handle all just in case" pattern. This has many associated problems, e.g.:

we can't set any behavior expectations (I don't know if TURN_OFF will turn off or suspend really). I could be turning off a sensor, but I actually see it just drawing a bit less milliwatts. However, the API states that device is disconnected.
Take a device that handles all "low power states" the same way. After SUSPEND, it should not be called again, since it doesn't know what else to do, really. If I call TURN_OFF, 1. no power configuration can change, 2. it could fail (maybe comms need to be resumed some special way?)

cases, since then there's virtually no difference between LOW_POWER and SUSPEND states.

What you mean here ? That devices are only active or suspended ? Or that most drivers were handling both states are the same ?

A driver that just supports one of the actions, LOW_POWER or SUSPEND is basically forced to handle both the same way in practice. For example, STM32 only makes use of PM_STATE_SUSPEND_TO_IDLE, which in turn only uses PM_DEVICE_ACTION_LOW_POWER. This means that all devices that want to have a chance of entering low power mode in such system, need to handle LOW_POWER. Things just get worse if we consider the runtime API, where only SUSPEND is considered.
So to summarize, I'd prefer a system that just has SUSPEND handled properly than a system that in theory offers one more level, but that in practice, it is not handled consistently.


update stage callback interface

See https://github.com/SciML/OrdinaryDiffEq.jl/pull/1445 and https://github.com/SciML/DiffEqDocs.jl/pull/480
CC @Cczernik

This is convenient - I was going to ask for the same interface change! Is the old interface deprecated?

No, it was just removed. I guess Chris thinks we are the only ones using such a crazy stuff :sweat_smile:

That seems surprising to me, but I guess we'll hear complaints if there are others using it...

(see the issue linked in my PR)

I guess the argument f was mostly useless for people nowadays. It was kind of necessary in the old days when DiffEq didn't accept parameters p explicitly, that we use for our semidiscratization semi. Back in the old days, we wrapped parameters in callable structs, so it was good to pass f. Since that's not the case anymore, it's just convenient to pass the parameters and the integrator explicitly.

I'll merge this now since the only failing tests are caused by upstream issues.


Add support for older shading devices

For the older CJAU-01/03 shading device position is not supported and I think that is why I get this error in home assistant:
2023-08-11 11:00:06.719 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Entity.async_write_ha_state()
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 746, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 810, in _async_write_ha_state
    attr.update(self.state_attributes or {})
                ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/cover/__init__.py", line 284, in state_attributes
    if (current := self.current_cover_position) is not None:
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/xcomfort_bridge/cover.py", line 149, in current_cover_position
    return 100 - self._state.position
           ~~~~^~~~~~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'int' and 'NoneType'

Would be good if this device is reported differently.
Let me know if this is difficult without the actual device and I will have a look at it when time permits...

No more errors now, thanks!!


(Elementary) shortest path problem with resource constraints

Why this Mod?

Shortest path problem from given source node to target node minimizing total arc and/or node costs, subject to knapsack constraints for the whole path on further resources like distance/time/load on arcs and/or nodes.
Costs are allowed to be negative potentially leading to loops along the path (even infinite loops if resource constraints are not restricting). If asking for "elementary" paths, loops are forbidden.
Classical NP-hard combinatorial problem, often arising as subproblem of more complicated problems, e.g., in the pricing problem of route-based formulations for vehicle routing problems.
State-of-the-art algorithms are labeling algorithms similar to dynamic programming that can be difficult to implement correctly and efficiently. For inefficient implementations, MILP might have comparable performance.

What will the API be?

Graph-based input seems more appropriate instead of multiple matrices/arrays that may be inconsistent. Pandas dataframes are a good option.
Resource "cost" is mandatory and serves as resource to minimize. All further resources with arbitrary names are optional for nodes and arcs.
Node and arc values with the same resource name are accumulated along the path.

node_data = pd.DataFrame([
    {"node": 0, "cost": -3, "time": 4, "distance": 3},
    {"node": 1, "cost": 5, "time": 3, "distance": 7},
    {"node": 2, "cost": 6, "time": 1, "distance": 2},
    {"node": 3, "cost": -4, "time": 5, "distance": 3}
])

arc_data = pd.DataFrame([
    {"source": 0, "target": 1, "cost": 16, "distance": 1},
    {"source": 0, "target": 2, "cost": -13, "distance": 3},
    {"source": 1, "target": 2, "cost": 10, "distance": 2},
    {"source": 2, "target": 1, "cost": -4, "distance": 6},
    {"source": 1, "target": 3, "cost": 12, "distance": 3},
    {"source": 3, "target": 2, "cost": -9, "distance": 2}
])

limits = {
  "time": 10,
  "distance": 18
}

path, objective = solve_espprc(node_data=node_data, arc_data=arc_data, source=0, target=3, limits=limits, elementary=True)

Additional context

I guess the public/private issue also made the rcsp fork unusable? This is no issue at all, I can just start with a new fork.

Yeah, new fork required I'm afraid, sorry about that.

@ruthmair Are you still working on this? Simon has given us the OK on writing a VRP mod! 😈

I still need to start working on this, but it is on my list.
Would you do a VRP mod based on column generation?

Yeah, why not? Would you say the formulation is better? We could have mod based on the formulation(s), or even better formulation(s) + heuristic to insert solutions via callback


Persisting Data with Volumes

HI Everyone
I'm on mac, docker versions are
Server: Docker Engine - Community
Engine:
Version:          18.09.2
Client: Docker Engine - Community
Version:           18.09.2
I've tried what seems to be every conceivable way of persisting data, using -v, or --mount, but nothing seems to be working.  I think I must be getting the path to where the data exists inside the container wrong or something.
Is persisting data possible with my versions above and this image?  I've got a saved image prior to the image being pulled from docker hub, which was very sad btw, not your fault I know. :-(
Thanks for any tips or suggestions.

Bit more information
Whenever I try to use --mount, when I exec into the container I can't access the database, constantly says it's starting up
Here's the alert log
Enter user-name: root@d1956113a860:/# cat /u01/app/oracle/diag/rdbms/xe/XE/trace/alert_XE.log
/u01/app/oracle/diag/rdbms/xe/XE/trace/alert_XE.log: line 1: Tue: command not found
/u01/app/oracle/diag/rdbms/xe/XE/trace/alert_XE.log: line 2: syntax error near unexpected token (' /u01/app/oracle/diag/rdbms/xe/XE/trace/alert_XE.log: line 2: Starting ORACLE instance (normal)'
Whenever I try to use the -v option, it will work first time, so I import some data, stop and remove the container, run it again mapping to the volume, and then I see similar errors, and the database always either shutting down or starting up making it unusable.

I've now tried this within a docker-compose context
version: '2'
services:
  oracle-db:
    build:
      context: .
      dockerfile: oracle.Dockerfile
    container_name: oracle-db
    environment:
      - ORACLE_ALLOW_REMOTE=true
    volumes:
      - oracle:/u01/app/oracle/oradata/XE/
    ports:
      - 49161:1521
volumes:
  oracle:

docker-compose up works beautifully, and I docker exec into the container, and import some data with imp.
Then I run docker-compose down, and docker-compose up again, and this error pops up in the output from the compose command
oracle-db    | Starting Oracle Net Listener.
oracle-db    | Starting Oracle Database 11g Express Edition instance.
oracle-db    |
oracle-db    | ERROR:
oracle-db    | ORA-01033: ORACLE initialization or shutdown in progress
oracle-db    | Process ID: 0
oracle-db    | Session ID: 0 Serial number: 0
oracle-db    |
oracle-db    |
oracle-db    | SP2-0306: Invalid option.
oracle-db    | Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]]
oracle-db    | where <logon> ::= <username>[/<password>][@<connect_identifier>]
oracle-db    |       <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]
oracle-db    | /usr/sbin/startup.sh: ignoring /docker-entrypoint-initdb.d/*

I've run into the same problem - adding a mounted volume over the oradata directory works first time but then after a restart Oracle won't start properly - any ideas @wnameless ?

Hi everyone i found a fix for this problem.
Instead of setting the volume path to /u01/app/oracle/XE/oradata set it to /u01/app/oracle and will work.
That solutions works for me.

Hi everyone i found a fix for this problem.
Instead of setting the volume path to /u01/app/oracle/XE/oradata set it to /u01/app/oracle and will work.
That solutions works for me.

It workes for me as well. Thanks!!

Hi everyone i found a fix for this problem.
Instead of setting the volume path to /u01/app/oracle/XE/oradata set it to /u01/app/oracle and will work.
That solutions works for me.

It works for me as well. Thanks!!

HI Everyone
I have also encountered this problem, but it is still not working properly, so I have to find another way to solve it.
You can map out a host directory with -v, create a new table space, and store database files on the host
step 1.
docker run -d -p 49161:1521 -p 28080:8080 -e ORACLE_ALLOW_REMOTE=true  --restart=always -v /home/db/:/home/oradata/ wnameless/oracle-xe-11g-r2
step 2.
sqlplus system/oracle@xe;
step 3.
create tablespace newspace datafile '/home/db/newspace.dbf' size 32m autoextend on;
step 4.
create user user1 identified by xxxx default tablespace newspace temporary tablespace temp;

how did you get this to work exactly? Im struggling. would rather data not stored in the container.

how did you get this to work exactly? Im struggling. would rather data not stored in the container.

Hi, This is the command I wrote:
docker run -d -p 1521:1521 -e ORACLE_ALLOW_REMOTE=true -v oracle:/u01/app/oracle  wnameless/oracle-xe-11g-r2

Hi, This is the command I wrote:
docker run -d -p 1521:1521 -e ORACLE_ALLOW_REMOTE=true -v oracle:/u01/app/oracle  wnameless/oracle-xe-11g-r2

Hi, is there anyone fix this issue? I'd just like to share a work around using k8s environment:

create a pvc and define a mount point for a temporary folder (e.g. /tmp/app) in the yaml at the first running
apply the yaml and finish your setups, for example creating DB, tables and account, etc.
execute inside the pod to copy the entire directory of /u01/app/oracle to /tmp/app/oracle with archive mode: cp -a /u01/app/oracle /tmp/app
delete the pod using kubectl delete -f file.yaml
modify the yaml to change the mount point back to /u01/app, and apply it again

okay, now will be the tricky part:

check the logs of the server pod to find the line 'Starting Oracle Net Listener' straight after a Stopping, ignore all the ERRORs
if not found, then delete the pod directly using 'kubectl delete pod' command (not via -f file.yaml), and check the log again. (note: the pod name may varied if the pod is handled by a deployment)

repeat these two steps till to find the Starting line exists

I know this is not a proper way to solve this issue, just a work around as I mentioned. I really keen to hear a final solution from you guys!


[opentelemetry-cpp] update version to 1.4.1

Describe the pull request

What does your PR fix?
Update opentelemetry-cpp port to the latest version v1.4.1.

Which triplets are supported/not supported?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

I'm not sure why, but the dependent package azure-core-tracing-opentelemetry-cpp is failing with the message
No transport adapter was selected, using libcurl as the default option for POSIX.
CMake Error at /Users/joao/Projects/vcpkg/scripts/buildsystems/vcpkg.cmake:824 (_find_package):
  Could not find a configuration file for package "opentelemetry-cpp" that is
  compatible with requested version "1.3.0".

  The following configuration files were considered but not accepted:

    /Users/joao/Projects/vcpkg/installed/x64-osx/share/opentelemetry-cpp/opentelemetry-cpp-config.cmake, version: 1.4.1

Call Stack (most recent call first):
  CMakeLists.txt:39 (find_package)

Seems like it should work, as the version is greater than 1.3.0, but it doesn't.

I'm not sure why, but the dependent package azure-core-tracing-opentelemetry-cpp is failing with the message
No transport adapter was selected, using libcurl as the default option for POSIX.
CMake Error at /Users/joao/Projects/vcpkg/scripts/buildsystems/vcpkg.cmake:824 (_find_package):
  Could not find a configuration file for package "opentelemetry-cpp" that is
  compatible with requested version "1.3.0".

  The following configuration files were considered but not accepted:

    /Users/joao/Projects/vcpkg/installed/x64-osx/share/opentelemetry-cpp/opentelemetry-cpp-config.cmake, version: 1.4.1

Call Stack (most recent call first):
  CMakeLists.txt:39 (find_package)

Seems like it should work, as the version is greater than 1.3.0, but it doesn't.

@joaosoares, This error is because azure-core-tracing-opentelemetry-cpp set https://github.com/Azure/azure-sdk-for-cpp/blob/584f83c7bd0399a5c473508c459d3e11fcf2c764/sdk/core/azure-core-tracing-opentelemetry/CMakeLists.txt#L39
find_package(opentelemetry-cpp "1.3.0" CONFIG REQUIRED)

so when you update opentelemetry-cpp from "1.3.0" to "1.4.1" made
  Could not find a configuration file for package "opentelemetry-cpp" that is
  compatible with requested version "1.3.0".

The soultion:
Port: azure-core-tracing-opentelemetry-cpp
vcpkg.json file:
    {
      "name": "opentelemetry-cpp",
      "version>=": "1.3.0"
    },

->
    {
      "name": "opentelemetry-cpp",
      "version>=": "1.4.1"
    },

Make a patch file:
file: https://github.com/Azure/azure-sdk-for-cpp/blob/584f83c7bd0399a5c473508c459d3e11fcf2c764/sdk/core/azure-core-tracing-opentelemetry/CMakeLists.txt#L39
find_package(opentelemetry-cpp "1.3.0" CONFIG REQUIRED)

->
find_package(opentelemetry-cpp "1.4.1" CONFIG REQUIRED)

I'm not sure why, but the dependent package azure-core-tracing-opentelemetry-cpp is failing with the message
No transport adapter was selected, using libcurl as the default option for POSIX.
CMake Error at /Users/joao/Projects/vcpkg/scripts/buildsystems/vcpkg.cmake:824 (_find_package):
  Could not find a configuration file for package "opentelemetry-cpp" that is
  compatible with requested version "1.3.0".

  The following configuration files were considered but not accepted:

    /Users/joao/Projects/vcpkg/installed/x64-osx/share/opentelemetry-cpp/opentelemetry-cpp-config.cmake, version: 1.4.1

Call Stack (most recent call first):
  CMakeLists.txt:39 (find_package)

Seems like it should work, as the version is greater than 1.3.0, but it doesn't.

@joaosoares, This error is because azure-core-tracing-opentelemetry-cpp set https://github.com/Azure/azure-sdk-for-cpp/blob/584f83c7bd0399a5c473508c459d3e11fcf2c764/sdk/core/azure-core-tracing-opentelemetry/CMakeLists.txt#L39
find_package(opentelemetry-cpp "1.3.0" CONFIG REQUIRED)

so when you update opentelemetry-cpp from "1.3.0" to "1.4.1" made
  Could not find a configuration file for package "opentelemetry-cpp" that is
  compatible with requested version "1.3.0".

The soultion: Port: azure-core-tracing-opentelemetry-cpp vcpkg.json file:
    {
      "name": "opentelemetry-cpp",
      "version>=": "1.3.0"
    },

->
    {
      "name": "opentelemetry-cpp",
      "version>=": "1.4.1"
    },

Make a patch file: file: https://github.com/Azure/azure-sdk-for-cpp/blob/584f83c7bd0399a5c473508c459d3e11fcf2c764/sdk/core/azure-core-tracing-opentelemetry/CMakeLists.txt#L39
find_package(opentelemetry-cpp "1.3.0" CONFIG REQUIRED)

->
find_package(opentelemetry-cpp "1.4.1" CONFIG REQUIRED)

@LarryOsterman,Could you please look this plan feasible?

@JonLiu1993 patch added, all checks are passing now

All features are tested successfully in the following triplet:

x64-linux

I asked Azure folks to comment on the patch to their bits.

Thank you, will implement these changes

Thanks for the update!


perf: Move react, react-dom to peer deps

[x] Explain the motivation for making this change.

react and react-dom shouldn't be pinned so i dont need to install multiple versions of react to use this package

[x] Provide a solid test plan for your changes.

tests ran, just make sure it's still loading as you expect.

[x]  Link to the issue - if any #24

this doesn't close that issue, it's just a small part of it.

That was dev dependencies, you need it there because the tests depend on react being present.

You are correct. But if we keep it as dev dep it is included in the final bundle:

A sample nextjs app would I am testing this in still has 2 copies of react:

Maybe there is something wrong with our build process 🤔

I checked again and it looks like I was not installing it correctly. Your PR looks good as is, I removed my commit.
Lets merge it!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Sorry for the confusion. The change was released and works as expected. Thank you for the PR!


Borrowing/returning

Implemented borrowing and returning. Changed the borrower's page to tabs layout with first tab being the borrowed books(TODO) and the second tab being the requests.

Is this O.K to merge @AY-Chen  @ishchow ?

@ishchow can you check this again?

Just tested it and it works!


Roll Flutter Engine from 347f506a341f to 64df738fdba0 (11 revisions)

https://github.com/flutter/engine/compare/347f506a341f...64df738fdba0
2023-12-06<EMAIL_ADDRESS>Roll Skia from 326bdc97ac40 to 570103e08087 (1 revision) (flutter/engine#48746)
2023-12-06<EMAIL_ADDRESS>Roll Dart SDK from 6eb13603c212 to dbfe4e3f867e (1 revision) (flutter/engine#48745)
2023-12-06<EMAIL_ADDRESS>[Impeller] Store Buffer/Texture bindings in vector instead of map. (flutter/engine#48719)
2023-12-06<EMAIL_ADDRESS>Roll Skia from 33cba437bf70 to 326bdc97ac40 (2 revisions) (flutter/engine#48743)
2023-12-06<EMAIL_ADDRESS>[Impeller] Provide the clear color to an advanced blend if it was optimized out (flutter/engine#48646)
2023-12-06<EMAIL_ADDRESS>[Windows] Set swap interval on raster thread after startup (flutter/engine#47787)
2023-12-06<EMAIL_ADDRESS>Roll Skia from 384d14063dc1 to 33cba437bf70 (3 revisions) (flutter/engine#48740)
2023-12-06<EMAIL_ADDRESS>[Windows] Refactor the GLES proc table (flutter/engine#48688)
2023-12-06<EMAIL_ADDRESS>Replace use of Fontmgr::RefDefault with explicit creation calls (flutter/engine#48571)
2023-12-06<EMAIL_ADDRESS>[Impeller] disable entity culling by default. (flutter/engine#48717)
2023-12-06<EMAIL_ADDRESS>Roll Skia from 23e1cb20a6b5 to 384d14063dc1 (1 revision) (flutter/engine#48738)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


corrections and suggestions

A few typos, grammar errors, and just simple readability improvement suggestions...

nicely done! by the way you did the improvements i can easily tell that you tried the steps too. thanks for trying to replicate the tutorial.


Add support for maven multimodule project

What do you think about reading and parsing modules into a multimodule project?

That would be a great functionality !
Do you want to manage the PR?

sure, i'll do it

Thank you! Your help is greatly appreciated 😄

Hello @agalbenus,
I was truly needing this functionality and decided to implement it.
Cheers!


Compiling master fails with missing file Reporting/Problem

Trying to build current master (commit 51e20357) fails with the following error message:
Resolving dependencies...
Configuring elm-0.19.1...
Preprocessing executable 'elm' for elm-0.19.1..
cabal: can't find source for Reporting/Problem in compiler/src, builder/src,
terminal/src, dist/build/elm/autogen, dist/build/global-autogen

This is using cabal <IP_ADDRESS> on a Debian buster amd64 installation.

I recommend compiling based on the 0.19.0 tag. There is ongoing work in master, so it is not always in a compiling state. If I do work on a separate branch, I get other comments saying that people cannot figure out where the work is happening. Whatever choice is made, it does not work well for everyone.

I see, thanks for the explanation. I find it strange, though, that people cannot figure out where work is happening, as git log --graph quite nicely orders most recent commits at the top, IIRC.