text:
BUG: Using Concat to Merge Two GroupBy DataFrames

Modin version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest released version of Modin.

[X] I have confirmed this bug exists on the main branch of Modin. (In order to do this you can follow this guide.)

Reproducible Example
import modin.pandas as pd
df1 = pd.DataFrame([['a', 1], ['b', 2], ['b', 4]],
                   columns=['letter', 'number'])
df1_g = df1.groupby('letter', as_index=False)['number'].agg('sum')

df2 = pd.DataFrame([['a', 3], ['a', 4], ['b', 1]],
                   columns=['letter', 'number'])
df2_g = df2.groupby('letter', as_index=False)['number'].agg('sum')

pd.concat([df1_g, df2_g])

Issue Description
I am trying to use 'concat' to combine two DataFrames that have undergone a 'groupby' operation, but I am encountering an error. As a new user of Modin, I'm not entirely sure if it's an issue with my usage or a bug in the software. I appreciate your help with this matter.
Expected Behavior

letter
number

a
1

b
6

a
7

b
1

Error Logs

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[1], [line 10](vscode-notebook-cell:?execution_count=1&line=10)
      [6](vscode-notebook-cell:?execution_count=1&line=6) df2 = pd.DataFrame([['a', 3], ['a', 4], ['b', 1]],
      [7](vscode-notebook-cell:?execution_count=1&line=7)                    columns=['letter', 'number'])
      [8](vscode-notebook-cell:?execution_count=1&line=8) df2_g = df2.groupby('letter', as_index=False)['number'].agg('sum')
---> [10](vscode-notebook-cell:?execution_count=1&line=10) pd.concat([df1_g, df2_g])

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\logging\logger_decorator.py:129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129), in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    [114](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:114) """
    [115](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:115) Compute function with logging if Modin logging is enabled.
    [116](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:116)
   (...)
    [126](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:126) Any
    [127](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:127) """
    [128](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:128) if LogMode.get() == "disable":
--> [129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129)     return obj(*args, **kwargs)
    [131](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:131) logger = get_logger()
    [132](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:132) logger_level = getattr(logger, log_level)

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\pandas\general.py:541](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:541), in concat(objs, axis, join, ignore_index, keys, levels, names, verify_integrity, sort, copy)
    [534](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:534) if len(list_of_objs) == 0:
    [535](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:535)     return DataFrame(
    [536](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:536)         index=input_list_of_objs[0].index.append(
    [537](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:537)             [f.index for f in input_list_of_objs[1:]]
    [538](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:538)         )
    [539](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:539)     )
--> [541](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:541) new_query_compiler = list_of_objs[0].concat(
    [542](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:542)     axis,
    [543](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:543)     list_of_objs[1:],
    [544](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:544)     join=join,
    [545](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:545)     join_axes=None,
    [546](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:546)     ignore_index=ignore_index,
    [547](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:547)     keys=None,
    [548](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:548)     levels=None,
    [549](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:549)     names=None,
    [550](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:550)     verify_integrity=False,
    [551](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:551)     copy=True,
    [552](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:552)     sort=sort,
    [553](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:553) )
    [554](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:554) result_df = DataFrame(query_compiler=new_query_compiler)
    [555](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/pandas/general.py:555) if new_idx is not None:

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\logging\logger_decorator.py:129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129), in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    [114](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:114) """
    [115](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:115) Compute function with logging if Modin logging is enabled.
    [116](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:116)
   (...)
    [126](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:126) Any
    [127](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:127) """
    [128](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:128) if LogMode.get() == "disable":
--> [129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129)     return obj(*args, **kwargs)
    [131](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:131) logger = get_logger()
    [132](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:132) logger_level = getattr(logger, log_level)

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\core\storage_formats\pandas\query_compiler.py:384](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/storage_formats/pandas/query_compiler.py:384), in PandasQueryCompiler.concat(self, axis, other, **kwargs)
    [382](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/storage_formats/pandas/query_compiler.py:382) ignore_index = kwargs.get("ignore_index", False)
    [383](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/storage_formats/pandas/query_compiler.py:383) other_modin_frame = [o._modin_frame for o in other]
--> [384](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/storage_formats/pandas/query_compiler.py:384) new_modin_frame = self._modin_frame.concat(axis, other_modin_frame, join, sort)
    [385](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/storage_formats/pandas/query_compiler.py:385) result = self.__constructor__(new_modin_frame)
    [386](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/storage_formats/pandas/query_compiler.py:386) if ignore_index:

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\logging\logger_decorator.py:129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129), in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    [114](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:114) """
    [115](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:115) Compute function with logging if Modin logging is enabled.
    [116](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:116)
   (...)
    [126](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:126) Any
    [127](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:127) """
    [128](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:128) if LogMode.get() == "disable":
--> [129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129)     return obj(*args, **kwargs)
    [131](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:131) logger = get_logger()
    [132](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:132) logger_level = getattr(logger, log_level)

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\core\dataframe\pandas\dataframe\utils.py:501](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/utils.py:501), in lazy_metadata_decorator.<locals>.decorator.<locals>.run_f_on_minimally_updated_metadata(self, *args, **kwargs)
    [499](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/utils.py:499)     elif apply_axis == "rows":
    [500](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/utils.py:500)         obj._propagate_index_objs(axis=0)
--> [501](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/utils.py:501) result = f(self, *args, **kwargs)
    [502](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/utils.py:502) if apply_axis is None and not transpose:
    [503](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/utils.py:503)     result._deferred_index = self._deferred_index

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\core\dataframe\pandas\dataframe\dataframe.py:3690](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/dataframe.py:3690), in PandasDataframe.concat(self, axis, others, how, sort)
   [3688](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/dataframe.py:3688)                     new_widths = None
   [3689](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/dataframe.py:3689)                     break
-> [3690](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/dataframe.py:3690) return self.__constructor__(
   [3691](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/dataframe.py:3691)     new_partitions, new_index, new_columns, new_lengths, new_widths, new_dtypes
   [3692](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/dataframe/dataframe.py:3692) )

File [h:\miniconda3\envs\modin_env\Lib\site-packages\modin\logging\logger_decorator.py:129](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:129), in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    [114](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:114) """
    [115](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:115) Compute function with logging if Modin logging is enabled.
    [116](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:116)
   (...)
    [126](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:126) Any
    [127](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/logging/logger_decorator.py:127) """
...
--> [182](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/metadata/dtypes.py:182)         self._cols_with_unknown_dtypes.extend(new_cols)
    [183](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/metadata/dtypes.py:183) self._know_all_names = True
    [184](file:///H:/miniconda3/envs/modin_env/Lib/site-packages/modin/core/dataframe/pandas/metadata/dtypes.py:184) return self._columns_order

AttributeError: 'RangeIndex' object has no attribute 'extend'

Installed Versions

INSTALLED VERSIONS
commit              : 47a9a4a294c75cd7b67f0fd7f95f846ed53fbafa
python              : 3.12.0.final.0
python-bits         : 64
OS                  : Windows
OS-release          : 11
Version             : 10.0.22621
machine             : AMD64
processor           : AMD64 Family 23 Model 113 Stepping 0, AuthenticAMD
byteorder           : little
LC_ALL              : None
LANG                : None
LOCALE              : Chinese (Traditional)_Taiwan.950
Modin dependencies
modin               : 0.26.0
ray                 : None
dask                : 2023.12.1
distributed         : 2023.12.1
hdk                 : None
pandas dependencies
pandas              : 2.1.4
numpy               : 1.26.2
pytz                : 2023.3.post1
dateutil            : 2.8.2
setuptools          : 68.2.2
pip                 : 23.3.1
Cython              : None
pytest              : None
hypothesis          : None
sphinx              : None
blosc               : None
feather             : None
xlsxwriter          : None
lxml.etree          : None
html5lib            : None
pymysql             : None
psycopg2            : None
jinja2              : 3.1.2
IPython             : 8.19.0
pandas_datareader   : None
bs4                 : None
bottleneck          : None
dataframe-api-compat: None
fastparquet         : None
fsspec              : 2023.12.2
gcsfs               : None
matplotlib          : None
numba               : None
numexpr             : None
odfpy               : None
openpyxl            : None
pandas_gbq          : None
pyarrow             : None
pyreadstat          : None
pyxlsb              : None
s3fs                : None
scipy               : None
sqlalchemy          : None
tables              : None
tabulate            : None
xarray              : None
xlrd                : None
zstandard           : None
tzdata              : 2023.3
qtpy                : None
pyqt5               : None

accidentally selected

Hi @wsxqaza12, thanks for opening this issue. I can reproduce it on latest master.
@dchigarev, it looks like _cols_with_unknown_dtypes can be a RangeIndex, but we assume it as a list. Can you take this on? https://github.com/modin-project/modin/blob/7ef544f4467ddea18cfbb51ad2a6fcbbb12c0db3/modin/core/dataframe/pandas/metadata/dtypes.py#L182


text:
Quarkus: Collect JfrUnit fields from the complete inheritance path

JfrUnitQuarkusLifecycleCallback#getJfrEvents would not pick up JfrUnit fields declared in a test if Quarkus subclassed the test class with a proxy class.  This patch fixes that.

This LGTM, thanks! Could you only add a test which exposes this particular issue?

This LGTM, thanks! Could you only add a test which exposes this particular issue?

I wasn't able to add a Quarkus test without breaking everything else, so I copied the same change into JfrEventTestExtension and created a test based on that.

Merged; thx, @benkard!

source: gharchive/pull-request

authors: benkard gunnarmorling

repo: moditect/jfrunit

license_type: permissive

license_source: github-api


text:
GH-254: Add bibliography package

This PR resolves GH-254 by adding a bibliography package. The package generates bibliographies, surprise surprise.
I think I am more or less done with this package, but it may have some rough edges, so please come with comments if you have any. There are two new modules intended for use; [cite [note]] <name>  will cite a source from the bibliography by its name, optionally allowing a note such as page numbers, and [bibliography [style] [file]] <database> which imports a BibTeX or Hayagravia Yaml file and uses that to create a bibliography and resolve previous citations. The BibLaTeX (or Yaml) content may be in a file (where the filename is passed as argument), or inserted as the body of the module.
Example document:
## Chapter 1

John MacFarlane [cite "p. 22"] djot released a product
called djot, after releasing Commonmark [cite] Commonmark in 2021.
AsciiDoc by Eclipse Foundation [cite] AsciiDoc is also intersting.

## Bibliography

[bibliography IEEE]<<
@online{djot,
title = {djot and the books that actually works bla bla it is nice. This is nice},
author = {John MacFarlane},
url = {https://djot.net},
urldate = {2023-01-23}
}

@online{AsciiDoc,
author = {{Eclipse Foundation}},
title = {{AsciiDoc}},
url = {http://asciidoc.org/},
urldate = {2023-01-23}
}

@online{Commonmark,
author = {John MacFarlane},
title = {CommonMark Spec},
year = {2021},
month = {6},
url = {https://spec.commonmark.org/0.30/},
urldate = {2023-03-21}
}
>>

Some technical notes:
typst/hayagriva is used for generating the bibliography and citations, allowing different styles such as IEEE, APA CMoS etc. The library allows setting two different styles, BibliographyStyle for the bibliography and CitationStyle for citations. This implementation sets both of them from the bibliography style, but I am not super sure that the CitationStyle is set correctly (but for IEEE and CMoS), the documentation was hard to follow and there didn't exist one CitationStyle for each BibliographyStyle.
To get the bibliography and cites correct, the scheduler are leveraged to compile the document in three stages:

All [cite]s are recorded in order (their content and arguments are stored in a list), but no actual citations are added in the text
[bibliography] runs, knowing all [cite]s and the order they appear in, and it makes a bibliography as well as generates the text for the inline citations
At the previous position of the cites, the appropriate inline citation text is fetched (from the output of [bibliography]) and inserted into the document

The first step is done by pushing JSON objects to the list inline_citations, as well as creating new modules [cite-internal-do-not-use] which is scheduled to run later. The second step is done by reading inline_citations, creating the actual bibliography and citations, and then for each citation in inline_citations, push a string containing that JSON and some JSON to be inserted in the modmark document at the citation place to a set called inline_citation_labels. The third step is done by having [cite-internal-do-not-use] read inline_citation_labels, finding its own label and inserting that JSON there.
For this to be possible, [cite] has to have unknown-content:true while not declaring inline_citations:list/push since that would lead to cyclic dependencies. Additionally, [bibliography] has declared imports:set/push just to facilitate [link] importing hyperref which it needs for LaTeX output.
Note that all of these modules have output format any, since they aren't dependent on the output format. It does, however, require that __text, __italic, __bold, link and newline exist for the target language.

repo: modmark-org/modmark


text:
LikeOrNope in swift

I have implemented MDCSwipeToChoose into a swift project and have the view controller currently swiping, however I am having alot of trouble getting the graphics down and loading the stack as it is done in likeornope.. Is there any chance there is a swift version of likeornope available or will one be coming soon. I think I speak for many new IOS developers by saying this would be extremely useful.
Thanks,
Rich

No response?

I'd love to include an example written in Swift, but I don't have much time to write one myself. @vikmeup? :pray:

I've actually already created a swift version which behaves the same. I'm new to GitHub, how can I submit it for other people to use? @modocache

@modocache that's perfect. I just pulled @takecian changes with Swift example.
https://github.com/modocache/MDCSwipeToChoose/pull/30
I will add Swift project of LikeOrNope this weekend.

@rjburdish feel free to fork https://github.com/modocache/MDCSwipeToChoose repo and send us pull request.
Take a look at https://help.github.com/articles/using-pull-requests/

@modocache @vikmeup
Done. I have pushed and created a pull request for my swift version of LikedOrNope and called it SwiftLikedOrNope. The README has also been updated.
Thanks!

@rjburdish good job! I merged your pull request!

source: gharchive/issue

authors: datomnurdin modocache rjburdish vikmeup

repo: modocache/MDCSwipeToChoose

license: mit

license_source: bigquery


text:
readthedocs points to master

Point to stable version after bug fix update.

Pointing to v0.1.1 now.

authors: gunnarvoet jessecusack

repo: modscripps/mixsea

license: MIT


text:
Type error for userSelect key in styled()

Bug report
Describe the bug
Given
const styles = {
  userSelect: 'none'
}
const Button = styled("button", styles)

this throws a typeerror. as soon as i remove/comment out userSelect: 'none' the typeerror goes away. same error for any other value
To Reproduce
See code above, run in a react app with typescript support
Expected behavior
This should not have any typescript complaints. I can make up any random key and it doesn't complain
Error message
Type error in VSCode
Argument of type '{ userSelect: string; }' is not assignable to parameter of type 'TComponentStylesObject<{ prefix: string; tokens: { colors: { $hyperlink: string; $green: string; $transparentBlack: string; $transparentWhite: string; $grey30: string; $transparentGrey30: string; $white80: string; ... 14 more ...; $linkBlue: string; }; ... 5 more ...; shadows: { ...; }; }; breakpoints: {}; utils: {}...'.
  Type '{ userSelect: string; }' is not assignable to type '{ [pseudo: string]: TFlatCSS<{ prefix: string; tokens: { colors: { $hyperlink: string; $green: string; $transparentBlack: string; $transparentWhite: string; $grey30: string; $transparentGrey30: string; $white80: string; ... 14 more ...; $linkBlue: string; }; ... 5 more ...; shadows: { ...; }; }; breakpoints: {}; uti...'.
    Type '{ userSelect: string; }' is not assignable to type '{ [pseudo: string]: TFlatCSS<{ prefix: string; tokens: { colors: { $hyperlink: string; $green: string; $transparentBlack: string; $transparentWhite: string; $grey30: string; $transparentGrey30: string; $white80: string; ... 14 more ...; $linkBlue: string; }; ... 5 more ...; shadows: { ...; }; }; breakpoints: {}; uti...'.
      Property 'userSelect' is incompatible with index signature.
        Type 'string' is not assignable to type 'TFlatCSS<{ prefix: string; tokens: { colors: { $hyperlink: string; $green: string; $transparentBlack: string; $transparentWhite: string; $grey30: string; $transparentGrey30: string; $white80: string; ... 14 more ...; $linkBlue: string; }; ... 5 more ...; shadows: { ...; }; }; breakpoints: {}; utils: {}; }> | ({ ...;...'.ts(2345)```

## System information

- OS: macOS
- Version of Stitches: 0.0.3-canary-4
- VSCode 1.52.1

your styles object has type { userSelect: string } which stitches doesn't like, inner types can't infer that userSelect is a CSS property and 'none' is a respectful possible value of that property. But you can help yourself and stitches with helpers. I think some type helpers come in the next version of stitches, which will be available soon
For now, you can create those helpers yourself, something similar to
import type { TCss, TCssProperties } from '@stitches/core'

import type { css } from 'stitches.config'

// infer Stitches Config type from your stitches.config I'm sure this part can be done clearer
type GetConfig<S> = S extends TCss<infer T> ? T : never
interface Config extends GetConfig<typeof css> {}

// use this config to create type helpers
type StylesObject = TCssProperties<Config>

const styles: StylesObject = {
  userSelect: 'none',
}

your styles object has type { userSelect: string } which stitches doesn't like, inner types can't infer that userSelect is a CSS property and 'none' is a respectful possible value of that property. But you can help yourself and stitches with helpers. I think some type helpers come in the next version of stitches, which will be available soon
For now, you can create those helpers yourself, something similar to
import type { TCss, TCssProperties } from '@stitches/core'

import type { css } from 'stitches.config'

// infer Stitches Config type from your stitches.config I'm sure this part can be done clearer
type GetConfig<S> = S extends TCss<infer T> ? T : never
interface Config extends GetConfig<typeof css> {}

// use this config to create type helpers
type StylesObject = TCssProperties<Config>

const styles: StylesObject = {
  userSelect: 'none',
}

hmm im not sure i understand why userSelect specifically is not accepted, but something like
{
  poop: "none"
}

is ok. user-select is part of the CSS spec, should it not be accepted?
thanks for the workaround, i managed to work around without too many lines by doing a destructured assignment for user-select: none inside styled()
const styles = {...}
const Button = styled('button', {...styles, userSelect: 'none'})

hmm im not sure i understand why userSelect specifically is not accepted, but something like
{
  poop: "none"
}

is ok. user-select is part of the CSS spec, should it not be accepted?
thanks for the workaround, i managed to work around without too many lines by doing a destructured assignment for user-select: none inside styled()
const styles = {...}
const Button = styled('button', {...styles, userSelect: 'none'})

(im a total typescript noob, sorry!)

(im a total typescript noob, sorry!)

It's because you've abstracted the styles and it doesnt contain the correct type.
This is something we'll fix in the new versions of Stitches by exposing a CSS Type that you can import.
For now, you can type it as any:
const styles: any = {
  userSelect: 'none'
}
const Button = styled("button", styles)

or cast it as any:
const styles = {
  userSelect: 'none'
}
const Button = styled("button", styles as any)

It's because you've abstracted the styles and it doesnt contain the correct type.
This is something we'll fix in the new versions of Stitches by exposing a CSS Type that you can import.
For now, you can type it as any:
const styles: any = {
  userSelect: 'none'
}
const Button = styled("button", styles)

or cast it as any:
const styles = {
  userSelect: 'none'
}
const Button = styled("button", styles as any)

great to hear types will be provided in the future!
i did try any casting first, but bc i have variants in the styles definition as well, it gave a type error when trying to set the attrs like

great to hear types will be provided in the future!
i did try any casting first, but bc i have variants in the styles definition as well, it gave a type error when trying to set the attrs like

You can just mark the userSelect 'none' value as a literal type and not as a generic string
const styles = {
  userSelect: 'none' as 'none'
}
const Button = styled("button", styles)

You can just mark the userSelect 'none' value as a literal type and not as a generic string
const styles = {
  userSelect: 'none' as 'none'
}
const Button = styled("button", styles)

@tarngerine agh, yeah :/ sorry for that. the experience there will be improved very soon. thanks!

@tarngerine agh, yeah :/ sorry for that. the experience there will be improved very soon. thanks!

Closing as its a duplicate of https://github.com/modulz/stitches/issues/304

authors: LexSwed blasterpistol peduarte tarngerine

repo: modulz/stitches


text:
songs/song01_sfx example is broken

I recently loaded the song01_sfx example and the sfx no longer sounds like it should.  It's playing a single tone, rather than following the pattern that is described.
I just pulled from the ATMLib2 branch and discovered this.
commander-keen:ATMlib jgarcia$ git pull origin ATMLib2
From github.com:moduscreate/ATMlib
 * branch            ATMLib2    -> FETCH_HEAD
Already up-to-date.

https://github.com/moduscreate/ATMlib/issues/11

@jaygarcia the SFX in song01_sfx is a single tone. It wasn't at some point but it is now. Feel free to change it to whatever suits the purpose of test SFX.

I am an idiot and totally misread the SFX notation. 🤦♂

authors: dxxb jaygarcia

repo: moduscreate/ATMlib


text:
Dynamically load full inheritance hierarchy

Allows for full use of the OGM module with complex inheritance hierarchies, including interesting edge cases like deriving a vertex class from a non-graph-like base class. Additionally, adds a new strict mode (off by default) where instead of silently dropping unusual inputs (e.g. when setting values to non-property keys), pyorient will raise errors.
Looking forward to hearing your thoughts on this.

Supersedes #166

Thanks!

repo: mogui/pyorient


text:
🛑 Non Attachments Worker is down

In 2d4b665, Non Attachments Worker (https://cw-conn-heartbeat.vercel.app/api/skip-attachments-beat) was down:

HTTP code: 503
Response time: 478 ms

Resolved: Non Attachments Worker is back up in 6c087be.

repo: mohhasbias/cw-conn-status-page


text:
Add VersionedModelReader and VersionedModelWriter constructors

It's quite inconvenient in user code not to have constructors.
Has the version number been increased?

[ ] Yes! (or not but it was intended to not increase it)

Open for 18 days. Any update?

Open for 18 days. Any update?

Sorry, after I opened this draft my Mac died and then I had to setup everything twice again 🙈
This needs tests - I might not be able to add them this week though.

Close it for the moment. Please reopen once it is ready.

repo: moia-dev/teleproto


text:
java GUI not working

Dear bacgtree team,
Thanks for the GUI version. It does not work however after running java -jar ./bcgTree.jar:
Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled.
Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=
CodeCache: size=131072Kb used=7200Kb max_used=7203Kb free=123871Kb
bounds [0x00000001049f8000, 0x0000000105108000, 0x000000010c9f8000]
total_blobs=2639 nmethods=2073 adapters=480
compilation: disabled (not enough contiguous free space left)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at bcgTree.gui.BcgTree.renameProteomes(BcgTree.java:547)
at bcgTree.gui.BcgTree$1.actionPerformed(BcgTree.java:313)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:262)
at java.awt.Component.processMouseEvent(Component.java:6539)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3318)
at java.awt.Component.processEvent(Component.java:6304)
at java.awt.Container.processEvent(Container.java:2239)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2297)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4904)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4535)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4476)
at java.awt.Container.dispatchEventImpl(Container.java:2283)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:84)
at java.awt.EventQueue$4.run(EventQueue.java:733)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:730)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at bcgTree.gui.BcgTree.renameProteomes(BcgTree.java:547)
at bcgTree.gui.BcgTree$1.actionPerformed(BcgTree.java:313)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:262)
at java.awt.Component.processMouseEvent(Component.java:6539)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3318)
at java.awt.Component.processEvent(Component.java:6304)
at java.awt.Container.processEvent(Container.java:2239)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2297)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4904)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4535)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4476)
at java.awt.Container.dispatchEventImpl(Container.java:2283)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:84)
at java.awt.EventQueue$4.run(EventQueue.java:733)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:730)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Any idea? I am using the most recent java and JRE from oracle.
Thanks,
Jianshu

Does this happen right away when you run java -jar ./bcgTree.jar? Or does the GUI open, and you click "Run"? In the latter case, make sure, to provide some proteomes before you start. It looks like you are trying to run bcgTree without providing any input.

I did provide everything and click run. Will share a screenshot soon.
Thanks，
Jianshu

Hello @iimog ,
I attached the screen shot when open the window and also after click run. All denpendencies are there.

Thank you for the screenshots. I'm able to reproduce the error now. It seems to happen when all inputs are genomes and there is no proteome file. Of course, bcgTree should work in this case as well (and it does, it is just the GUI that has problems, but also the GUI should work). I'll fix this problem. But I'm currently on vacation, so I won't be able to fix it this year.
A workaround for now is to translate at least one genome file manually and provide it as proteome. The command that bcgTree uses for the translation is:
prodigal -i final_contigs_AM-654-A11.fasta -o final_contigs_AM-654-A11.fasta.prodigal.genes -a final_contigs_AM-654-A11.fasta.prodigal.faa

And the file final_contigs_AM-654-A11.fasta.prodigal.faa is the proteome that is used further.

Hello @iimog,
Ok no problem, I will use proteome first. Can you also please add fasttree support.  I understand that RAxML is the most accurate one but too slow for more than 30 genomes or so, for a GUI application, most use cases are personal computers like laptops, which will be slow.  fasttree can be 10 times faster while provide almost identical result with RAxML, very useful for quick check of phylogeny of some genomes.
Thanks,
Jianshu

Hello @iimog,
It seems with the newest version of RAXML, v8.2.12, there are alway problems with respect to partition file:
RAxML was called as follows:
raxmlHPC-PTHREADS -f a -m GTRGAMMA -p 740281 -q /Users/jianshuzhao/Github/bcgTree/data/SAR11_SAG_try_bcgtree_full_alignment.concat.partition -s /Users/jianshuzhao/Github/bcgTree/data/SAR11_SAG_try_bcgtree_full_alignment.concat.fa -w /Users/jianshuzhao/Github/bcgTree/data/ -n SAR11_SAG_bcgtree_final -T 4 -x 28840 -N 100
Partition PF00276.16 number 1 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition PF00281.15 number 2 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00297.18 number 3 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition PF00410.15 number 7 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00416.18 number 9 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00466.16 number 10 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF01025.15 number 13 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00001 number 15 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00002 number 16 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00009 number 17 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00012 number 18 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00029 number 20 has a problem, the number of expected states is 20 the number of states that are present is 17.
Please go and fix your data!
Partition TIGR00059 number 22 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00060 number 23 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00061 number 24 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00062 number 25 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00082 number 27 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00115 number 30 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00152 number 32 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00158 number 33 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00165 number 34 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00168 number 36 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00442 number 50 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00663 number 59 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00810 number 61 has a problem, the number of expected states is 20 the number of states that are present is 17.
Please go and fix your data!
Partition TIGR00855 number 62 has a problem, the number of expected states is 20 the number of states that are present is 17.
Please go and fix your data!
Partition TIGR00952 number 64 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00959 number 65 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00964 number 67 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00981 number 69 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01021 number 73 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01024 number 74 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01031 number 76 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR01032 number 77 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01044 number 78 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01049 number 79 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR01050 number 80 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01066 number 82 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01067 number 83 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01079 number 85 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01169 number 87 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01632 number 91 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00276.16 number 1 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition PF00281.15 number 2 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00297.18 number 3 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition PF00410.15 number 7 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00416.18 number 9 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF00466.16 number 10 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition PF01025.15 number 13 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00001 number 15 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00002 number 16 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00009 number 17 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00012 number 18 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00029 number 20 has a problem, the number of expected states is 20 the number of states that are present is 17.
Please go and fix your data!
Partition TIGR00059 number 22 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00060 number 23 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00061 number 24 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00062 number 25 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00082 number 27 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00115 number 30 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00152 number 32 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00158 number 33 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00165 number 34 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00168 number 36 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00442 number 50 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00663 number 59 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00810 number 61 has a problem, the number of expected states is 20 the number of states that are present is 17.
Please go and fix your data!
Partition TIGR00855 number 62 has a problem, the number of expected states is 20 the number of states that are present is 17.
Please go and fix your data!
Partition TIGR00952 number 64 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00959 number 65 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR00964 number 67 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR00981 number 69 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01021 number 73 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01024 number 74 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01031 number 76 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR01032 number 77 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01044 number 78 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01049 number 79 has a problem, the number of expected states is 20 the number of states that are present is 18.
Please go and fix your data!
Partition TIGR01050 number 80 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01066 number 82 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01067 number 83 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01079 number 85 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01169 number 87 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Partition TIGR01632 number 91 has a problem, the number of expected states is 20 the number of states that are present is 19.
Please go and fix your data!
Segmentation fault: 11
I attached the alignment file and partition file from the java GUI:
Archive.zip
Any idea?
Thanks

hello @iimog,
I am new to Java but I have a similar pipeline that I want to put together as bcgtreeGUI. It would be nice if you could share the Java code to make the .jar file.
Thank you,
Jianshu

The GUI issue is fixed in v1.2.1

Thanks for the quick fix and I tested everything. It worked! Again for only 5 genomes, it takes more than 20 minutes with 2 threading. It seems RAxML threading is not so efficient, the same 5 genome for iqtree2, it takes 1 minutes with 2 threads.

repo: molbiodiv/bcgTree


text:
How to set the server's timeout more than the standard 2 minutes?

And in middlevare I tried:
 use: [                 cookieParser(),                 function(req, res, next){                     req.socket.server.setTimeout(600000);                     next();                 }             ]
The code in the hook created()
this.server.setTimeout(600000);
The result was not given
Tell me, please, the more correct method!?

Did you try it in the started()?

Yes, I tried it in started() too...
Logger writes to the console, everything is as expected. The hooks of the router also work out, but something breaks the connection a multiple of 2 minutes.

Feel free to open back if you think the issue is related to moleculer-web.

authors: JeStasG icebob

repo: moleculerjs/moleculer-web


text:
Uncaught League\Container\Exception\NotFoundException: Alias (Mollie\Handler\RetryHandlerInterface)

FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught League\Container\Exception\NotFoundException: Alias (Mollie\Handler\RetryHandlerInterface) is not being managed by the container in /var/www/vhosts/9mmenergy.be/httpdocs/modules/mollie/vendor/league/container/src/Container.php:266
Expected behavior
Get the complet transaction and final page after payment
Actual behavior
Not getting back the paid order
Steps to reproduce the behavior
using a payment method
Environment

PrestaShop version: 1.7.8.10
Mollie module version: latest
PHP version: 7.4

@GigaWeb2023 hey, sorry for a delay.
Could you send us your FTP/SSH and database credentials to support@invertus.eu? The guys will take a look.
Thanks.

@GigaWeb2023 hey, sorry for a delay. Could you send us your FTP/SSH and database credentials to support@invertus.eu? The guys will take a look.
Thanks.

Hi,
we sent to the mail address all the credentials, did you get them ?
Thanks,

Hi @GigaWeb2023,
Yes, we have received the credentials.
As soon as we have analyzed the issue and get more information, I will get back to you with an update.
Best Regards,
Invertus Support team.

Great, thank you,
this is the new url of the shop : https://9mmenergy.be/shop

Hey @GigaWeb2023,
Thanks for waiting!
The issue was fixed by our team and will be included in the upcoming release.
We are currently in the testing phase, so if everything is good, we should release it in the upcoming weeks.
Best Regards,
Invertus Support team.

Thank you for the update,
but actuallly we have this on a real e-shop that is going to be online very soon.
Do you have any idea on when this fix will be available ?
Best regards,

Hi there,
Thanks for waiting!
The issue should be fixed in the new release. You can try it out here - https://github.com/mollie/PrestaShop/releases/tag/v6.0.4-beta
Your feedback is greatly appreciated.
Best Regards,
Invertus Support team.

repo: mollie/PrestaShop


text:
在tableview中电话号码不能点击！

在tableview中电话号码不能点击！

@wasonxie EmojiTableViewCell里- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch是解决方案。

authors: molon wasonxie

repo: molon/MLEmojiLabel


text:
🛑 haccp is down

In 019f505, haccp (https://www.haccp.or.kr) was down:

HTTP code: 400
Response time: 1445 ms

Resolved: haccp is back up in 1ee51c7 after 8 minutes.


text:
Add token to pre-commit autoupdate workflows

Committed via https://github.com/asottile/all-repos

Pull Request Test Coverage Report for Build 1644246511

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

Totals

Change from base Build 1435117580:
0.0%

Covered Lines:
233

Relevant Lines:
240

💛  - Coveralls

Pull Request Test Coverage Report for Build 1644246511

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

Totals

Change from base Build 1435117580:
0.0%

Covered Lines:
233

Relevant Lines:
240

💛  - Coveralls

authors: coveralls mondeja

repo: mondeja/mkdocs-include-markdown-plugin


text:
Проброс звука в TCL телевизорах.

Может разработчик сделать проброс звука, как в другом  известном плеере(авто+) для ТСЛ телевизоров? Фильмы в 4к только в Джаст идут плавно без дëрганья👍, а вот с пробросом звука проблема, не пробрасывает AC-3, только pcm.

I'm afraid this is a device or upstream (ExoPlayer) issue: #285, https://github.com/google/ExoPlayer/issues/9671

Я боюсь, что это проблема устройства или восходящего потока (ExoPlayer): # 285 , google/ExoPlayer # 9671

Да это в ТСЛ что-то намутили, что пробрасывает только в DD +. Но в плеере виму как то смогли обойти эту проблему, но он мне не подходит. Жаль если ничего не поделать.

It's definitely possible to add workarounds but it would require too much back and forth to debug it and add some error prone fixes. One should really intent to fix this issue at its source. Just Player is only a wrapper around ExoPlayer / Media3.

repo: moneytoo/Player

license: Unlicense


text:
Organization

Added:

Organization resource to handle the API calls
Organization test cases

Organization work is on hold for now.

authors: PacoDw themantissa

repo: mongodb/go-client-mongodb-atlas


text:
tets: test mock generation works

Proposed changes
the make gen-mocks command has been broken for a while, fixing it and adding a test to make sure it works
Checklist

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[x] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[x] I have updated e2e/E2E-TESTS.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

example failing test without my fix
https://github.com/mongodb/mongodb-atlas-cli/runs/5481287232?check_suite_focus=true

good job

I had some good inspiration to base this work from :)

repo: mongodb/mongodb-atlas-cli


text:
Issue 789

Changes related to #789  to add optional caching of class names during mapping, which we found increased performance 10-12% in our use case.

Trying to adhere to semantic version, this new feature would have to wait for 1.1 (which hopefully will be the next release anyway)

So I've pulled this and tweaked it slightly.  The commit is above.  Let me know what you think.  The gist of it trying to reuse the DefaultCreator (ObjectFactory actually) from the MappingOptions we get from the Mapper.  At one point during validation, we were creating a new DefaultCreator to validate certain bits.  This change pushes the actual ObjectFactory down in to the validators so we can reuse this cache.
Also, I changed the HashMap to a nonblocking map so as to not incur the locking penalty.  The downside is potentially double writing a String/Class mapping but that's essentially a no-op the second time around.  The plus side is that all the reads don't need to lock what will eventually be a steady state map.
What do you think?

The changes to push the ObjectCreator down into the MappingValidator and the VersionMisuse validation look good to me.
I'm concerned that the change from ConcurrentHashMap to HashMap may cause problems.  According to the API docs for HashMap, the HashMap implementation just isn't safe to use in locations where it might be written by multiple threads, so I'm concerned that the change might blow up under load even in a situation where it's passing in unit tests or working ok under light duty.
My understanding is that ConcurrentHashMap is non-blocking for most reads, and seems to be the fastest of the other available options in the core API, so I guess unless there's another thread-safe option I'd prefer if we leave the map as a ConcurrentHashMap.

That's fair.  I just reread the docs for CHM and it looks like you're right about the reads.  I'll change that back then and merge this PR.  Thanks for the patch and the feedback.

authors: evanchooly rlodge

repo: mongodb/morphia


text:
Poll heartbeat rate

The main motivations for this PR is to tackle two existing issues https://github.com/monix/monix-kafka/issues/94 and https://github.com/monix/monix-kafka/issues/101.
Rebasing existing pending PR: https://github.com/monix/monix-kafka/pull/104, so credits for the author, @voidconductor 🙏

Proper commitAsync implementation that removed callback from methods arguments itself, now completed in this callback, and it was also never used actually used in previous implementations. No api changes.
Polling strategy for keeping the consumer alive and not trigger partition reassignment in slow subscribers, which avoids doing the hack of decreasing poll.max.records. https://github.com/monix/monix-kafka/issues/101.
The polling rate is only configurable internally for performance analysis on benchmarks repos.  Ideally I we would just
This polling is achieved by performing poll(0) from a task running concurrently in the background, which in case of error it the schedule will report it, without stopping the subscription. Although it should never happen since the heartbeat poll is only called if the consumer is paused, and both processes are call synchronized.

@Avasil thank you for all the comments! Will address them and do review again 🧐

@Avasil first of all sorry for the amount of commits, it might make difficult to track the changes review, I assume they will be squashed at the end...
I have written specific new cases in PollHeartbeatTest for the different kafka versions (excluding 0.9.x), and benchmarks covering manual and auto-commit scenarios with different heartbeat interval values.
As part of that I ran the same benchmarks from latest release RC7, to have a base to compare with, and from there I've got two conclusions:

The higher pollHeartBeatInterval is, the slower the consumption becomes (although I am  unsure what this relation is due to). So I ended up setting by default a heartbeat interval of 15ms.
On the other hand, I have noticed that the auto-commit-async has degraded and I am not sure  why (I'm investigating it).

Finally, I was also tempted to move from travis to github actions and splitting the tests by the different kafka versions.

first of all sorry for the amount of commits, it might make difficult to track the changes review, I assume they will be squashed at the end...

No worries, just let me know when you think it's good to re-review - thanks for the hard work!

As part of that I ran the same benchmarks from latest release RC7, to have a base to compare with, and from there I've got two conclusions:

I'll look at the benchmarks later but I feel like they can be unreliable if everything is hosted on one machine so it's hard to draw any conclusions

Finally, I was also tempted to move from travis to github actions and splitting the tests by the different kafka versions.

👍 Yeah, it needs to be done and I could setup sbt ci-release

@Avasil I think it could already be re-reviewed :)

Would be nice to give it a try in a real project though.

That would be ideal, alternatively we may ask it in the main monix gitter channel too, and see if someone is interested in testing it.

authors: Avasil paualarco

repo: monix/monix-kafka


text:
LLVM usage

Brief Description
I have two problems with current use of LLVM inside CppSharp.

The version is from trunk and not a released version
Use of private (not installed) headers such as CodeGen/CodeGenModule.h and others.

These issues prevent getting LLVM from a package manager which in my opinion is a serious downside.
Moreover, the private headers, I believe, can change without notice and break the library.
Do you agree this is problematic and if so do you plan to fix them one day?

Historically we've never used official LLVM releases because we've always depended on trunk for bug fixes (at some point we even had to apply custom patches).

I believe at this point we could switch to a tagged release, but it does limit us in the future in case we need to depend on a recent commit (like we did recently for VS2017 support).
Since this is related to using LLVM from a package manager, another issue related to this is that Clang does not support shared library exports for its API on Windows, so we need to link statically anyway, which would mean we'd only get the benefit from a shared library on non-Windows platform (Linux presumably?).

I think this might could cause issues in the future yes, but it's not been an issue ever since we introduced usage of those APIs. They seem pretty stable at this point in Clang history and unlikely to change. If they do, we'll just update to their equivalents.

I was checking why need them (it's been a while) and it's to get ABI codegen information for return and parameter types. Not using them is not an option since it would mean generating code that crashes at runtime.
Getting the Clang developers to put those APIs under public headers would be an option, but we've been that road before for other APIs and it's a huge waste of our limited time.
We've put a lot of effort and time over the years to make our usage of LLVM as painless as possible to both developers and users, with build scripts for getting, building and packaging pre-compiled LLVM packages for our supported platforms.
If you want to package CppSharp for a package system (which one, by the way?) just do not depend on the package manager's built-in version of LLVM/Clang. All this does really is add a few extra MB of code to the package, and since this is a developer's tool and not a library to be distributed to end-users, I don't think that's an issue to be concerned about.
And it means we can make sure our own version of LLVM is fully-tested and works properly. As we depend on such a heavy set of APIs in Clang, re-using a package manager's version might mean compatibility issues.

Indeed I thought of adding CppSharp to Hunter and I would like to get LLVM from Hunter as well.
The problem with having CppSharp downloading LLVM by itself is described here.

What I recommend doing is just packaging CppSharp by itself, without any dependency on the package manager's LLVM/Clang library. That should work fine. In the end, all of the LLVM/Clang's code will be statically linked in CppSharp.CppParser.dll.
Another issue I forgot to talk about, is that Clang releases (at least on Windows) only provide the C API for linking, while we depend on the C++ API.

Closing, let us know if you have any other issues creating the package.

authors: dvirtz tritao

repo: mono/CppSharp


text:
[objc] Make the processor linker-aware

Processed assemblies and types that are part of the SDK (i.e. not user
code) needs to preserve the types / members that are bound.
This can be done automatically by the processor as those types/members
are being added (before generation). At the end of the process we can
use the collected data to generate a bindings.xml file that the linker
from Xamarin.iOS or Xamarin.Mac can consume.
Notes:

Neither ObjC processing or generating code is unaffected by this;
Unit tests to be included with TimeSpan support (separate PR)

Part 1: this should be merged after PR #292 (decimal support) so it can replace the static linker.xml file.
Part 2: will add System.TimeSpan support and, unlike PR #251 (first attempt), it will work correctly for iOS.

Build and tests passed.

Build failed

PR #325 will fix the (unrelated) failure above.

Build and tests passed.

Build and tests passed.

authors: monojenkins spouliot


text:
Add specs

The specs are based on mocked Sequel dataset and the assertions are run
against SQL the combine should produce.
One of the next steps could be adding an integration test that'd test
specific adapters and eventually raise an error if an unsupported adapter
is being used.
There is also a basic circle.yml file

Brilliant 👌

authors: kubakrzempek wmaciejak

repo: monterail/sequel-combine


text:
Can't seem to turn off SSL

Intention

I'm submitting a bug report
Environment

Operating System:
Windows 10 10586.589
Node Version:
6.8.0
NPM Version:
3.10.8

Description
Current behavior:
I'm behind a proxy, so I've configured my .npmrc to only use http, and npm works fine from the command line. I've also configured Monterey to only use http, and turned off Strict-SSL. However, when I try to create a new project, it hangs while downloading from Git and logs errors indicating a connection failure. The logs indicate that it is still attempting to communicate over port 443, despite other settings to the contrary. I could still be wrong, but that's what it looks like to me.
Expected/desired behavior:
When configured as such, no SSL communications should be attempted.
What is the motivation / use case for changing the behavior?
So I can work from behind the corporate proxy.
Logs

See the attached log file: 2016-10-14.txt

Hi @devingoble your issue is really an issue with GitHub, which specifically enforces the SSL comunications only. I would think that most companies which use GitHub as the source repository have some solution in place for their developers. Here is one hint for such solution if your admin cannot help you:
http://www.lmxm.net/git/2012/05/21/github-behind-isa-proxy.html
As you can see, this solution is specific for a given proxy and I do not believe that there is some universal solution available.

Well the setting you have used is configuring only NPM, and does not change any behavior of Monterey. But this is something we should definitely fix. For example, here we use https:// directly and this is something we could determine based on a settings

this could be useful: https://github.com/monterey-framework/monterey/search?utf8=✓&q=path%3Aapp%2Fsrc+https&type=Code

Unfortunately the GitHub API seems to be only available through https 😢

authors: JeroenVinke adriatic devingoble

repo: monterey-framework/monterey


text:
[WFRP4e System] Enable changing actor sheet configuration

The "Configure Sheet" dialog on Actors have drop-downs for changing configuration, but there are no alternatives except Default and the sheet that matches the Actor Type at creation.
It would be nice to be able to switch sheet between NPC & Creature, so that I can edit in NPC mode (and see all careers) and then switch to Creature mode (for simpler viewing).From: PatrikP#2817wfrp4e: 4.2.1wfrp4e-core: 2.1.2

The author would need to create a hybrid sheet, otherwise, it will mess up with db (not worth).

This is for changing sheet types, not actor types

Could you mean you just want the NPC sheet to have the tab that's on the Creature?

That, or being able to edit talents after dropping a career onto a creature sheet.
But no big deal, it just felt like the sheets could be interchangeable because creatures and npcs handle everyting in the same way, just present them differently.

Maybe show/add the talent tab on creature sheets when it has a talent? Just like spells.... I think that would do it.

Sorry I'm not sure exactly your aim there, an extra tab for that would just be clutter

I prefer the Creature sheet during a play session, because all the important stuff is on the main tab. However, I can't edit or delete talents on Creatures, so it's not very convenient when preparing for play.

You certainly can, you can open the sheet via double right click, and hover + delete key to delete them.

You certainly can, you can open the sheet via double right click (or double click if it's not rollable), and hover + delete key to delete them.

Amazing! 😄

authors: Havoclivekiller Pafvel moo-man


text:
List::last should return Option

https://github.com/moonbitlang/core/blob/85ab5cfbd5e93be37e601ad79d18594383741852/immut/list/list.mbt#L227

This will be changed on the next release.
In the current release I just deprecated it with guidance to migrate

landed on master

authors: Yoorkin bobzhang qazxcdswe123

repo: moonbitlang/core


text:
Add MIP-B05, Gauntlet Base Recommendations

I pre-deployed the new IR contracts using the DeployJRM script:

WETH: https://basescan.org/address/0x6bce15b789e537f3aba3c60cb183f0e8737f05ec
DAI: https://basescan.org/address/0x33DeAc0861FD6a9235b86172AA939E79085c6f52

and their parameters are validated within the proposal tests. I've also added precondition checks for all of the current versions of the parameters we are changing to assist in validating parameter serialization logic/decimal usage etc.
@ndelzingaro88 @reichiang for additional gauntlet review
Targeting on chain delivery date of Tuesday, 09/19

Output of forge script test/proposals/mips/mip-b05/mip-b05.sol:mipb05 --rpc-url base -vv:
[⠒] Compiling...
No files changed, compilation skipped
Script ran successfully.

== Logs ==
  deployerAddress:  0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266
  temporal governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000628ff693426583d9a7fb391e54366292f509d45700000000000000000000000073b06d8d18de422e269645eace15400de7462417000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f5200000000000000000000000000000000000000000000000000000000
  wormhole publish governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c80000000000000000000000000000000000000000000000000000000000000584b19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000628ff693426583d9a7fb391e54366292f509d45700000000000000000000000073b06d8d18de422e269645eace15400de7462417000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f520000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
  artemis governor queue governance calldata
  0xda95691a00000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000018000000000000000000000000000000000000000000000000000000000000007800000000000000000000000000000000000000000000000000000000000000001000000000000000000000000bebdb6c8ddc678ffa9f8748f85c815c556dd8ac600000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000584b19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000628ff693426583d9a7fb391e54366292f509d45700000000000000000000000073b06d8d18de422e269645eace15400de7462417000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f52000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000282e2f746573742f70726f706f73616c732f6d6970732f6d69702d6230352f4d49502d4230352e6d64000000000000000000000000000000000000000000000000

Proposal Description:

./test/proposals/mips/mip-b05/MIP-B05.md

------------------ Proposal Actions ------------------
  1). Set collateral factor for ETH
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
payload
  0xe4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000

  2). Set collateral factor for cbETH
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
payload
  0xe4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000

  3). Set collateral factor for DAI
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
payload
  0xe4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000

  4). Set interest rate model for Moonwell WETH to updated rate model
  target: 0x628ff693426583D9a7FB391E54366292F509D457
payload
  0xf2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec

  5). Set interest rate model for Moonwell DAI to updated rate model
  target: 0x73b06D8d18De422E269645eaCe15400DE7462417
payload
  0xf2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f52

Updated output of forge script test/proposals/mips/mip-b05/mip-b05.sol:mipb05 --rpc-url base -vv:
[⠒] Compiling...
No files changed, compilation skipped
Script ran successfully.

== Logs ==
  deployerAddress:  0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266
  temporal governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000628ff693426583d9a7fb391e54366292f509d45700000000000000000000000073b06d8d18de422e269645eace15400de7462417000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f5200000000000000000000000000000000000000000000000000000000
  wormhole publish governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c80000000000000000000000000000000000000000000000000000000000000584b19a437e0000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000628ff693426583d9a7fb391e54366292f509d45700000000000000000000000073b06d8d18de422e269645eace15400de7462417000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f520000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
  artemis governor queue governance calldata
  [encoded data, 6986 characters]

Proposal Description:

# MIP-B05 Gauntlet Base Risk Recommendations

# Simple Summary

### Risk Parameters

A proposal to adjust 5 risk parameters:

| Risk Parameter          | Current Value | Recommended Value |
| ----------------------- | ------------- | ----------------- |
| ETH Collateral Factor   | 75%           | 78%               |
| cbETH Collateral Factor | 73%           | 75%               |
| DAI Collateral Factors  | 80%           | 82%               |

### IR Parameters

A proposal to adjust 3 IR parameters for 2 assets:

| DAI IR Parameters   | Current | Recommended |
| --------------- | ------- | ----------- |
| BASE            | 0       | 0           |
| Kink            | 0.8     | 0.8         |
| Multiplier      | 0.05    | 0.045       |
| Jump Multiplier | 2.5     | 2.5         |

Gauntlet recommends to increase the kink to 80% and Jump Multiplier to 4.8 for the WETH IR curve to improve capital efficency of WETH:

| WETH IR Parameters   | Current | Recommended |
| --------------- | ------- | ----------- |
| BASE            | 0.01       | 0.01           |
| Kink            | 0.75     | 0.8         |
| Multiplier      | 0.04    | 0.04       |
| Jump Multiplier | 3.8     | 4.8         |

Here is the forum [post](https://forum.moonwell.fi/t/moonwell-base-recommendations-2023-09-11/617) with further analysis and supporting data for our recommendations.

*By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos.*

------------------ Proposal Actions ------------------
  1). Set collateral factor for ETH
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
payload
  0xe4028eee000000000000000000000000628ff693426583d9a7fb391e54366292f509d4570000000000000000000000000000000000000000000000000ad31dde0cce0000

  2). Set collateral factor for cbETH
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
payload
  0xe4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000a688906bd8b0000

  3). Set collateral factor for DAI
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
payload
  0xe4028eee00000000000000000000000073b06d8d18de422e269645eace15400de74624170000000000000000000000000000000000000000000000000b6139a7cbd20000

  4). Set interest rate model for Moonwell WETH to updated rate model
  target: 0x628ff693426583D9a7FB391E54366292F509D457
payload
  0xf2b3abbd0000000000000000000000006bce15b789e537f3aba3c60cb183f0e8737f05ec

  5). Set interest rate model for Moonwell DAI to updated rate model
  target: 0x73b06D8d18De422E269645eaCe15400DE7462417
payload
  0xf2b3abbd00000000000000000000000033deac0861fd6a9235b86172aa939e79085c6f52

Will review first thing tomorrow, looks good!

@reem I don't see the IR model upgrades to USDbC and USDC - is there a reason to withhold those IR model updates and only do DAI for now? Thanks.

Updated with IR updates for USDC and USDbC
Will wait for more commentary on the _setNonce change
Is there something I should be doing for CI to pass? Seems like an existing test is having an issue.

As a sanity check, it would be good to see some integration tests that look at post proposal state, and try to supply and borrow at these new values in these updated markets.

Update to address review comments. I left precondition checks in the build step in order to make things easier to review by hand by visually co-locating the checks, but if y'all feel strongly about moving them am happy to do so.

authors: ElliotFriedman lyoungblood reem


text:
Implement prediction for head tracking?

https://developer.oculus.com/blog/the-latent-power-of-prediction/

Already implemented in the compositor.
https://github.com/ValveSoftware/openvr/wiki/IVRCompositor_Overview#overview


text:
[Bug]: Unavailable Dynamic Sitemap

Describe the bug
안녕하세요. 블로그 잘 사용하던 중에 궁금한 게 있어 이슈 남깁니다.
현재 next site config를 사용해서 배포할 때는 정적으로 sitemap을 생성하는 것을 확인했습니다.
하지만 노션 페이지 추가에 따라 동적으로 sitemap이 변경되지 않는 것 같습니다.
이전 #19 에서 설명하신 /page/sitemap.xml.js가 현재는 main 브랜치에 보이지 않더군요. 포스팅보고 임의로 추가해서 진행도 해보고, 다른 next js 포스팅들 보고도 해봤는데 생성되지 않아서 남깁니다.
제가 아는 동적 sitemap 생성과 의미가 다른건가요? ( notion page 추가 시, 각 페이지 slug 생성에 따라 sitemap에도 추가 생성)
next js에 대해 문외한이라 죄송합니다.
To reproduce

Go to /page folder and create /page/sitemap.xml.js
Make a code according to #19
Push branch and Deploy to Vercel

Browser
mac OS
Validations

[X] Follow our Code of Conduct
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

fix done

@pg56714
OMG...Thanks for your contribution ^^
I will try it on my fork

repo: morethanmin/morethan-log


text:
react-autowhatever dependency installs multiple react instances on npm2.

Hello,
Just a heads up.
Because of react-autowhatever dependency is declared as ^3.1.0 for version react-autosuggest@3.6.0, it installs react-autowhatever@3.2.1 as a dependency. Which has a peerDependency of react ^15.0.1.
On npm 2 peer dependencies auto installed, so if you still use react@0.14.x npm will install multiple instances of react.
As a workaround you can explicitly set react-autowhatever version on your package.json or use shrinkwrap.

@efegurkan Could you please check if it is still an issue in 3.7.3?

@moroshko yep that looks like fixed. Thanks for fast response.

authors: efegurkan moroshko

repo: moroshko/react-autosuggest


text:
How may I mask the search bar underline ?

Hello, folks,
Juste on simple question as title, I wonder whether I could mask the search bar underline by theme props ?
Thx a lot.

What do mean by "search bar underline"?

I meant the underline beneath the input field.

Could you share a screenshot?

Sorry guy, I made a mistake, we used auto suggestion via material ui and in fact we should have configured their TextField ahead. So problem resolved.
I closed this issue, thx all the same :) :)

authors: be-next-hotdog moroshko


text:
Error: Im trying to execute but gives error

While i execute, it gaves me this error :
C:\Users\Usuario\Desktop\TFG\Mapping\ComunidadMadrid\Meteorologicos>python3 -m morph_kgc config.ini
INFO | 2023-05-15 20:30:31,803 | 21 mapping rules retrieved.
INFO | 2023-05-15 20:30:31,881 | Mapping partition with 14 groups generated.
INFO | 2023-05-15 20:30:31,881 | Maximum number of rules within mapping group: 5.
INFO | 2023-05-15 20:30:31,881 | Mappings processed in 4.157 seconds.
multiprocessing.pool.RemoteTraceback:
UnboundLocalError: local variable 'data' referenced before assignment

Please, provide more details, such as the version of morph-kgc nd mappings.

authors: arenas-guerrero-julian titoarrabal

repo: morph-kgc/morph-kgc


text:
Upgrade tensorflow dependency to 1.13.1

Looks like tensorflow 1.13.1 has finally been released. We probably want to update to this version so that we can take full advantage of int64 matrix multiplications and no longer have to support tensorflow 1.12.0 custom builds. This should be fairly straight forward just need to update the tensorflow dependency version in the setup.py, requirements.txt and Makefile.

Closed by https://github.com/mortendahl/tf-encrypted/pull/409

repo: mortendahl/tf-encrypted