Custom header logo linking to default port 80 instead of actual instance port

If your Kanboard instance is accessible via different port number from the default 80, the header logo links to localhost/dashboard instead of localhost:[port_number]/dashboard.
See screenshots for my installation on port 8077

i dont know anything about how customizer would interact with "WeKanboard", so something to think about.
However, go to Apllication settings, and make sure you put in your Application URL with the Port.

See if that fixes your issue.

Hi Craig
Issue solved after setting my Application URL with the port number. the
value was previously blank.
Thank you for your quick answer!
On Sat, Feb 25, 2023 at 12:20 PM Craig Crosby @.***>
wrote:

i dont know anything about how customizer would interact with
"WeKanboard", so something to think about.
However, go to Apllication settings, and make sure you put in your
Application URL with the Port.
[image: image]
https://user-images.githubusercontent.com/26339368/221377871-feb09377-c85a-4f13-ab36-3a754f228646.png
See if that fixes your issue.
—
Reply to this email directly, view it on GitHub
https://github.com/creecros/Customizer/issues/143#issuecomment-1445196026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARJLRNRY5UKETAHTWCR3ZX3WZJSQFANCNFSM6AAAAAAVIAA5QE
.
You are receiving this because you authored the thread.Message ID:
@.***>


[FLINK-16983][python] Support RowType in vectorized Python UDF

What is the purpose of the change
This pull request add support of RowType in vectorized Python UDF.
Brief change log

Introduce row column vector in blink
Introduce ArrowRowColumnVector, RowWriter, etc to support RowType in vectorized Python UDF

Verifying this change
This change added tests and can be verified as follows:

Java test cases ArrowUtilsTest, BaseRowArrowReaderWriterTest and RowArrowReaderWriterTest
Python test case test_pandas_udf.py

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @hequn8128 and also @JingsongLi for the changes of blink planner.

@hequn8128 Thanks a lot for the review. Updated the PR.

@jark Could you help to take a look at the changes about blink planner? Thanks in advance.

@Jark Could you help to take a look at the changes about blink planner? Thanks in advance.

I think you tagged the wrong person here, did you mean @wuchong ?

@Jark  Oh, you're right. Sorry about the interrupt!

cc @wuchong

Nice to meet you @Jark  :)

@dianfu no worries!
@wuchong nice to meet you as well :)

@wuchong  @JingsongLi Any comments? The changes related to the blink planner has been split into a separate commit and the changes is very small and should be easy to review.

Thanks @dianfu , the RowColumnVector.java changs looks good to me.

@wuchong Thanks a lot for the review.


Expectation_X0

Thx for the amazing work!
When you calculating the Expectation_X0 and Tr_Cov_d for Analytic-Init, did you assume the pixel value for X0 follow a normal distribution?

Hi @ryancll,
Actually,we apply a normal distribution $N(\mu_T,\sigma_T^2I)$ as the prior. As stated in the paper,to minimize the KL Divergence between the actual distribution $P(X_T)$ and $N(\mu_T,\sigma_T^2I)$,we propose an analytic expression for $\mu_T$ and $\sigma_T$.

Hi @ryancll ,
We make no assumptions about the distribution of the true data X_0. We assumed that the prior distribution in the generation process is a normal distribution, but not a standard Gaussian. To minimize the KL divergence between this prior distribution and the true distribution, we derive the analytical form of its mean and variance.

Hi @ryancll ,thank you for your suggestions.Mathematically,we may have a more complex analytic form of the prior,and the more complex it is,the smaller minimal KL divergence will be. However,the more complex the prior distribution is, the greater the computational time complexity, and the lower the computational efficiency.For example,if we adpot a normal distribution $N(\mu,\Sigma)$,where $\Sigma$ isn't a scalar matrix,it could be tough to sample from this prior distribution.


WinError 2 error

Program can't read the text unfortunately. I get a [WinError 2] error. Anyone know what to do??

are you able to share what you did to fix this? I've been playing with it for hours now , any help would be appreciated. Thanks!

bro  help me
i am also getting error  in this one


Reading custom fields not working

API v1.3.0
Hi, i added custom fields to a bill object, just like in your tests:
        record.customFields = [
            [ "customfield1", "customvalue1" ],
        ];

When i try to query the recently created bill object,
            queryFields: [
                "RECORDNO",
                "VENDORID",
                "WHENCREATED",
                "WHENDUE",
                "CURRENCY",
                "APBILLITEMS",
                "DESCRIPTION",
                "RECORDID",
                "DOCNUMBER",
               "CUSTOMFIELD1",
               "CUSTOMFIELDS"
            ],

Every other property is returned correctly, but  both "CUSTOMFIELD1" and "CUSTOMFIELDS" is empty, i didn't find a way to retrieve the data i inserted.
Is there any example or tests i can look into on how to retrieve them ?

Hi Marius,
I tried this out by modifying query.js in examples project and now I am able to fetch custom field in the Bill Object. Please find the code below.  I hope this helps !!
` const client = bootstrap.client(logger);
    let filter = new IA.Functions.Common.NewQuery.QueryFilter.OrOperator();
    filter.addFilter(new IA.Functions.Common.NewQuery.QueryFilter.Filter("CUSTOMFIELD2").like("1099 Int"));
    filter.addFilter(new IA.Functions.Common.NewQuery.QueryFilter.Filter("CUSTOMFIELD2").like("customFieldValue2"));

    let orderBuilder = new IA.Functions.Common.NewQuery.QueryOrderBy.OrderBuilder();
    orderBuilder.addDescending("VENDORNAME");
    const orders = orderBuilder.orders;

    let selectBuilder = new IA.Functions.Common.NewQuery.QuerySelect.SelectBuilder();
    selectBuilder.addFields(["VENDORNAME", "CUSTOMFIELD2"])
       ;
    const selects = selectBuilder.selects;

    let query = new IA.Functions.Common.NewQuery.Query();
    query.selectFields = selects;
    query.fromObject = "APBILL";
    query.filter = filter; // Comment out this line to see all invoices without any filtering
    query.caseInsensitive = true;
    query.pageSize = 100;
    query.orderBy = orders;

    logger.info("Executing query to Intacct API");

    const response = await client.execute(query);
    const result = response.getResult();

    logger.debug("Query successful", {
        "Company ID": response.authentication.companyId,
        "User ID": response.authentication.userId,
        "Request control ID": response.control.controlId,
        "Function control ID": result.controlId,
        "Data": result.data,
    });

    let json_data = result.data;

    if (json_data && Array.isArray(json_data) && json_data.length >= 1) {
        console.log(`Success! Total number of results: ${ result.totalCount.toString() }\n`);
        console.log(`First ARINVOICE result found: ${ JSON.stringify(json_data[0]) }`);
        console.log("See the log file (logs/intacct.html) for the complete list of results.\n");
    }  else {
        console.log("The query executed, but no ARINVOICE objects met the query criteria.\n");
        console.log("Either modify the filter or comment it out from the query.\n");
        console.log("See the log file (logs/intacct.html) for the XML request.\n");
    }`


fix 0.3.0-rc.0 version reporting

Fixes https://github.com/mitogen-hq/mitogen/issues/777

/AzurePipelines run

/AzurePipelines run

In setup.py __version__ is has eval() called on it. I don't think it's a problem, but perhaps note worthy.
https://github.com/mitogen-hq/mitogen/blob/6e0a01f8a04b227c918b31fe3c29720357661bc2/setup.py#L38-L40

In setup.py __version__ is has eval() called on it. I don't think it's a problem, but perhaps note worthy.
https://github.com/mitogen-hq/mitogen/blob/6e0a01f8a04b227c918b31fe3c29720357661bc2/setup.py#L38-L40

How do a sample of projects do their version, wrt to alphas/betas and int vs string?

Mitogen: all previous releases have used a 3-tuple of integers. There haven't been any alphas or betas.
Based git log -G __version__ -p mitogen/__init__.py, and https://pypi.org/project/mitogen/#history

Python
>>> sys.version_info
sys.version_info(major=3, minor=10, micro=0, releaselevel='alpha', serial=4)
>>> sys.version
'3.10.0a4 (default, Jan  5 2021, 00:08:30) \n[GCC 9.3.0]'
>>> print(sys.version)
3.10.0a4 (default, Jan  5 2021, 00:08:30)
[GCC 9.3.0]

Ansible (now ansible-base, as a string in ansible/release/__init.py)
>>> ansible.__version__
'2.10.0b1'

Hypothesis: has always used 3-tuple of integers.
Based on git log -P -G ^__version_info__ -p, and https://pypi.org/project/hypothesis/#history

How do a sample of projects do their version, wrt to alphas/betas and int vs string?

Mitogen: all previous releases have used a 3-tuple of integers. There haven't been any alphas or betas.
Based git log -G __version__ -p mitogen/__init__.py, and https://pypi.org/project/mitogen/#history

Python
>>> sys.version_info
sys.version_info(major=3, minor=10, micro=0, releaselevel='alpha', serial=4)
>>> sys.version
'3.10.0a4 (default, Jan  5 2021, 00:08:30) \n[GCC 9.3.0]'
>>> print(sys.version)
3.10.0a4 (default, Jan  5 2021, 00:08:30)
[GCC 9.3.0]

Ansible (now ansible-base, as a string in ansible/release/__init.py)
>>> ansible.__version__
'2.10.0b1'

Hypothesis: has always used 3-tuple of integers.
Based on git log -P -G ^__version_info__ -p, and https://pypi.org/project/hypothesis/#history

In setup.py __version__ is has eval() called on it. I don't think it's a problem, but perhaps note worthy.
https://github.com/mitogen-hq/mitogen/blob/6e0a01f8a04b227c918b31fe3c29720357661bc2/setup.py#L38-L40

I'm in favor of removing the way Mitogen does versioning in place of versioneer. I've used it before in other projects and it automatically detects version based on things like git tag. I see that it says it supports python3 only at the moment; if we still want to support python2 then we can use https://github.com/python-versioneer/python-versioneer/tree/0.18 which supports back to python2.6. If we migrated to versioneer then there'd be no need for either the custom version function in setup.py or having to maintain a tuple ourselves :D

In setup.py __version__ is has eval() called on it. I don't think it's a problem, but perhaps note worthy.
https://github.com/mitogen-hq/mitogen/blob/6e0a01f8a04b227c918b31fe3c29720357661bc2/setup.py#L38-L40

I'm in favor of removing the way Mitogen does versioning in place of versioneer. I've used it before in other projects and it automatically detects version based on things like git tag. I see that it says it supports python3 only at the moment; if we still want to support python2 then we can use https://github.com/python-versioneer/python-versioneer/tree/0.18 which supports back to python2.6. If we migrated to versioneer then there'd be no need for either the custom version function in setup.py or having to maintain a tuple ourselves :D

Notes to self

The git tag v0.3.0-rc.0 already exists
__version__ = (0, 3, "0-rc.0") results in package mitogen-0.3.0rc0 (no dash before "rc0")
Versioneer

uses git tags, or version embedded in parent directory name (typical for unpacked sdist), e.g.

mitogen-0.3.0rc0+20.gdb354df3.dirty
mitogen-0.3.0rc0+21.gac720689
mitogen-0.3.0rc1 (after git tag -a v0.3.0rc1, note the v`, tag now deleted)

has no dependencies of it's own
doesn't introduce runtime, or CI dependencies (90% confidence)
generates

versioneer.py (imported by setup.py, checked in file and sdist bundled file are identical)
mitogen/_verison.py (imported in mitogen/__init__.py, checked in file introspects environment, sdist bundled file de-serializes embedded json)

works with string versions, not tuple style versions
relies on executing code at import time to populate mitogen.__version__
would need some remedial work in the minifier, and test suite======================================================================
ERROR: test_minify_all (minify_test.MitogenCoreTest)
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/alex/src/mitogen/tests/minify_test.py", line 112, in test_minify_all
   self._test_syntax_valid(minified, name)
 File "/home/alex/src/mitogen/tests/minify_test.py", line 71, in _test_syntax_valid
   compile(minified, name, 'exec')
 File "mitogen/_version.py", line 37
   def get_config():
     ^
IndentationError: expected an indented block

======================================================================
FAIL: test_simple (module_finder_test.FindRelatedTest)
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/alex/src/mitogen/tests/module_finder_test.py", line 295, in test_simple
   self.assertEquals(set(related), self.SIMPLE_EXPECT)
AssertionError: Items in the first set but not the second:
u'mitogen._version'

======================================================================
FAIL: test_stats (responder_test.ForwardTest)
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/alex/src/mitogen/tests/responder_test.py", line 194, in test_stats
   self.assertEquals(2+os_fork, self.router.responder.good_load_module_count)
AssertionError: 2 != 3

has the meme-tastic long_description=LONG in its setup.py :smile:

Notes to self

The git tag v0.3.0-rc.0 already exists
__version__ = (0, 3, "0-rc.0") results in package mitogen-0.3.0rc0 (no dash before "rc0")
Versioneer

uses git tags, or version embedded in parent directory name (typical for unpacked sdist), e.g.

mitogen-0.3.0rc0+20.gdb354df3.dirty
mitogen-0.3.0rc0+21.gac720689
mitogen-0.3.0rc1 (after git tag -a v0.3.0rc1, note the v`, tag now deleted)

has no dependencies of it's own
doesn't introduce runtime, or CI dependencies (90% confidence)
generates

versioneer.py (imported by setup.py, checked in file and sdist bundled file are identical)
mitogen/_verison.py (imported in mitogen/__init__.py, checked in file introspects environment, sdist bundled file de-serializes embedded json)

works with string versions, not tuple style versions
relies on executing code at import time to populate mitogen.__version__
would need some remedial work in the minifier, and test suite======================================================================
ERROR: test_minify_all (minify_test.MitogenCoreTest)
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/alex/src/mitogen/tests/minify_test.py", line 112, in test_minify_all
   self._test_syntax_valid(minified, name)
 File "/home/alex/src/mitogen/tests/minify_test.py", line 71, in _test_syntax_valid
   compile(minified, name, 'exec')
 File "mitogen/_version.py", line 37
   def get_config():
     ^
IndentationError: expected an indented block

======================================================================
FAIL: test_simple (module_finder_test.FindRelatedTest)
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/alex/src/mitogen/tests/module_finder_test.py", line 295, in test_simple
   self.assertEquals(set(related), self.SIMPLE_EXPECT)
AssertionError: Items in the first set but not the second:
u'mitogen._version'

======================================================================
FAIL: test_stats (responder_test.ForwardTest)
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/alex/src/mitogen/tests/responder_test.py", line 194, in test_stats
   self.assertEquals(2+os_fork, self.router.responder.good_load_module_count)
AssertionError: 2 != 3

has the meme-tastic long_description=LONG in its setup.py :smile:

This sounds fine as a built-time requirement (loving it's a single module) assuming that the tar.gz releases it produces do not require Git to be installed on the target machine (I think this is the case?)
On the compatibility front, while the core library treats Python 2 essentially as a stable near-universal network protocol for manipulating remote infrastructure, the terms /could/ be a little looser for the host machine, where it's much simpler to ensure a modern Python build is available (even in crusty weird old environments). I'm wary of taking little sips of the Python 3 kool-aid though, as it could lead to painting the project into an unforeseen corner. The idea of Python 2 disappearing any time in the coming years is some adorable meme that in no way reflects the real world lifecycle of enterprise infrastructure.

This sounds fine as a built-time requirement (loving it's a single module) assuming that the tar.gz releases it produces do not require Git to be installed on the target machine (I think this is the case?)
On the compatibility front, while the core library treats Python 2 essentially as a stable near-universal network protocol for manipulating remote infrastructure, the terms /could/ be a little looser for the host machine, where it's much simpler to ensure a modern Python build is available (even in crusty weird old environments). I'm wary of taking little sips of the Python 3 kool-aid though, as it could lead to painting the project into an unforeseen corner. The idea of Python 2 disappearing any time in the coming years is some adorable meme that in no way reflects the real world lifecycle of enterprise infrastructure.

assuming that the tar.gz releases it produces do not require Git to be installed

Correct

I'm wary of taking little sips of the Python 3 kool-aid though, as it could lead to painting the project into an unforeseen corner

Versioneer 0.18 would require Python 2.6+ on the Mitogen initiator (maybe also child nodes), I think we can do without the 0.19 features.

assuming that the tar.gz releases it produces do not require Git to be installed

Correct

I'm wary of taking little sips of the Python 3 kool-aid though, as it could lead to painting the project into an unforeseen corner

Versioneer 0.18 would require Python 2.6+ on the Mitogen initiator (maybe also child nodes), I think we can do without the 0.19 features.

I'm preparing a 0.3.0rc1 and 0.2.10rc1 as PRs. Propose to make a decision on versioneer in 0.3.0rc2.

I'm preparing a 0.3.0rc1 and 0.2.10rc1 as PRs. Propose to make a decision on versioneer in 0.3.0rc2.

I'm preparing a 0.3.0rc1 and 0.2.10rc1 as PRs. Propose to make a decision on versioneer in 0.3.0rc2.

Sounds good 👍

This sounds fine as a built-time requirement (loving it's a single module) assuming that the tar.gz releases it produces do not require Git to be installed on the target machine (I think this is the case?)

Correct, iirc nothing needs to be installed on the target machine (at least I haven't needed to on the versions I've used for my own projects).

I'm preparing a 0.3.0rc1 and 0.2.10rc1 as PRs. Propose to make a decision on versioneer in 0.3.0rc2.

Sounds good 👍

This sounds fine as a built-time requirement (loving it's a single module) assuming that the tar.gz releases it produces do not require Git to be installed on the target machine (I think this is the case?)

Correct, iirc nothing needs to be installed on the target machine (at least I haven't needed to on the versions I've used for my own projects).


Publication API

The main purpose of this API is to manage a single repository on the department's research publications.

The API will be used by the ESCAL web
Can integrate with the other websites/pages in the department such as Computer Vision, Cyber Security, etc...
Can add the publication details into the Staff and People profile pages

TODO

[ ] Identify the parameters need to collect
[ ] Identify the way we can collect the publication information
[ ] Design the data repository (Git Repo / Google Sheet / Google Form)
[ ] Design the procedures for long term sustainability
[ ] Implement the APIs
[ ] Write the API documentation

Discussion Summary (2021-12-19):

Identify the required fields for the publications
Add "affiliation" as a parameter, and only show the papers with CE Affiliation in the frontend web
Will add a Mentor from E15 to guide the development team about the publications
Prepare a Google Form to collect publication data
Design a data structure to keep them
Will appoint a maintainer(s) to collect the publication data and update in the repo based on the Form responses

It was decided to implement the Publication information collection from a well-designed Google Form at this time and directly process the details in api.ce.pdn.ac.lk. Later will be moving this into a separate repository

Commit 765908d implemented the basic setup + workflow (daily updates)
Information can be provided from the Google Form, https://forms.gle/vAPghP9c96a19bNY9

There is a suggestion to have a public Discord Channel and update every new publication information there. ( automated by the Google Actions )

@gihanjayatilaka

Publication API documentation is now available from https://api.ce.pdn.ac.lk/docs/publications/#/


Remove pointer events on the icon containing element.

Closes #1797

I thought the bug was that we want to be able to click the icon to activate the tab. Wouldn't setting pointer events to none do the opposite?
What am I missing?

Setting the pointer events to none made the event target the link that wrapped the icon.
But it was good to look more closely at the issue, the better fix was adding .closest to the event handler so it didn't use the icon as the event target.


Simple coverage checker

Depends on https://github.com/Kindelia/Wikind/pull/60

Type families info and additional information for the coverage checker now is compiled with the rest of the code needed to checker.hvm.
Changed name of axioms.
Added [axiom] flag to make coverage checker not get a foreign function that is filled outside of the checked code as data constructor (ONLY USEFUL INSIDE THE TYPE CHECKER)

Closed to split this PR into multiples with simple fixes.


add example for sending a file via NamedFile/NamedFileBuilder

Examples include using static DirHandler but it would be good to have an example for NamedFile. I had to dig in the source code to see how it was used.
#[handler]
async fn get_file(req: &mut Request, res: &mut Response) -> anyhow::Result<()> {
  let path = "./file.txt";
  let file = NamedFile::open(path).await?;
  file.send(req.headers(), res).await;
  Ok(())
}

Also might be worth adding docs so can see an example without looking at the source code at https://docs.rs/axum/0.2.3/axum/response/struct.Redirect.html#.

I appreciate if you can give a PR :)
Doc repository: https://github.com/salvo-rs/website

Added fn send_file to Response.


RENDER Problem in Tree

when try to render a tree with thousands of nodes , it slows down and takes a lot of time to render, sometimes shows time out.

The file that you send is broken. The json is not formatted correcty. You can go to the end of the file in order to see that. Everything works fine with fixed json. You can see my fix for your file in the attachment.
json-repaired.txt


Incorrect article being opened

This afternoon I've noticed that the extension doesn't seem to be opening the correct article, as far as I can tell the article that is at the top of the current folder is opened not the current article.

Same problem for me using 0.7 version

+1

+1. Can I go back to 0.6 in my browser?...

And this evening it seems to have started working as expected again...

Thanks for the update.  I just released 0.8 with a fix.  Sorry about that friends!  Thanks for your patience.


Add check for Size field

Closes #89
Tested with Size field and without Size field.

Merged, thank you so much! I did some refactoring to make those checks easier to test locally with a personal access token. With them, doing #45 should be very strightforward. Would you be interested in that?


Weird stuff with doing Dimensional Boosts Challenge late in the game

If you do Dimensional Boosts Challenge with enough eternities:

Due to not taking account of bulk correctly in Dimensional Boosts Challenge, the Dimensional Shift button breaks (the game enters an infinite loop due to trying to reset infinitely many times).
Due to not taking account of Dimensional Boosts Challenge at all, max buying galaxies breaks (it doesn't buy any since there are no eighth dimensions to buy them with).
if the above two issues were fixed, you could get tons of galaxies if you were in EC7 with some first ID, since first ID will produce lots of seventh dimensions which will produce lots of sixth dimensions. It's as if there were a ninth dimension.

(Should I sign up for the discord and post these there? The issues section looks rather empty, and I don't want to create a lot of noise.)

Using github to report bugs is totally fine, however if it's a serious gameplay affecting issue like the C8 one, I would recommend PMing me or Hevipelle on discord so we can see it right away.

A PR has been made with fixes to these issues. Also, EC7 will no longer do anything in C10 because it produces 7th dims, and C10 states there and only 6 dimensions.


BUG: pandas std broken, erratic behavior

I seem to have encountered a bug while using
DataFrame.apply(np.std) or DF.groupby.agg(np.std)
tested on:

debian 7.9 (wheezy), pandas version: 0.16.2.dev
ubuntu 15.10, pandas version:  0.15.0

more version details for the tested snippets below

test code:
import numpy as np
import pandas as pd
print("pandas version: ", pd.__version__)

# why is there a difference ?
s = pd.Series([1.11] * 10)
print(np.std(s))
# 1.88486436615e-08
print(np.std(s.values))
# 2.22044604925e-16

# why is it significantly != 0 ?
# why is there a difference ?
print(np.std(pd.Series([53426.7756333882,] * 50)))
# 0.0011048543456
print(np.std(pd.Series([53426.7756333882,] * 123)))
# 0.000704429402084

# doing that with data frames
df = pd.DataFrame([538512.198638,] * 123)
print(df.apply(np.std))
# 0    0.030867
# dtype: float64
print(np.std(df))
# 0    0.030867
# dtype: float64
print(np.std(df.values))
# 2.32830643654e-10

using the following data set even NaNs appear as result for std
funnily this happens if you add enough digits after the comma
import numpy as np
import pandas as pd
print("pandas version: ", pd.__version__)

df = pd.DataFrame([538512.1986379109,]*126)
df['uid']=15
df.set_index('uid', inplace=True)

# why do I occasionally even get NaN for identical values?
# NaN appears if there are enough decimal places after the comma
print(df.groupby(level=0).agg([np.mean, np.std]))
#                 0
#              mean std
#uid
#15<PHONE_NUMBER>38 NaN
df['bla'] = 911.
print(df.groupby(level=0).agg([np.mean, np.std]))
#                 0      bla
#              mean std mean std
#uid
#15<PHONE_NUMBER>38 NaN  911   0
df['bla'] =<PHONE_NUMBER>1571542312243214
print(df.groupby(level=0).agg([np.mean, np.std]))
#                 0      bla
#              mean std mean std
#uid
#15<PHONE_NUMBER>38 NaN  911 NaN

bug hypotheses:
this looks like a detail-problem regarding the way pandas applies functions
is the size of the mapped-on container calculated wrong? (e.g. not the single column series length is used, but the overall container's number of elements)
version details: (ubuntu 15.10)
INSTALLED VERSIONS
commit: None
python: 2.7.10.final.0
python-bits: 64
OS: Linux
OS-release: 3.13.0-43-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: de_AT.UTF-8
pandas: 0.15.0
nose: 1.3.6
Cython: 0.23.3
numpy: 1.8.2
scipy: 0.14.1
statsmodels: 0.5.0
IPython: 2.3.0
sphinx: 1.2.3
patsy: 0.4.0
dateutil: 2.2
pytz: 2014.10
bottleneck: None
tables: 3.2.2
numexpr: 2.4.3
matplotlib: 1.4.2
openpyxl: 2.3.0-b1
xlrd: 0.9.4
xlwt: 0.7.5
xlsxwriter: None
lxml: 3.4.4
bs4: 4.3.2
html5lib: 0.999
httplib2: 0.9
apiclient: None
rpy2: 2.6.2
sqlalchemy: 1.0.8
pymysql: 0.6.2.None
psycopg2: 2.6.1 (dt dec mx pq3 ext lo64)

suggesting labels
#BUG, #Prio-high, #Numeric, #Internals

dupe of #10242 was fixed in 0.17.0


Switch to conventionally named version tables

Turns out the default behavior of the gem is to name the columns like "location_versions", which is what i believe we want.
We've been overriding the default to make them "locations_versions".
This PR removes the overrides and migrates to the default table names.
~I think this will break old migrations. I'll need to update them (?!)~

FWIW, I couldn't find any other places that need to change.

FWIW, I couldn't find any other places that need to change.
Oh, and we don't need to change old migrations, because if you rewind it will also change the names of the tables back so they will work.  They would only break if you tried to cherry pick one old migration and run that out of order on the modern state of the database.  But you would never do that.

Check the test results here. The old migrations do not work on CI on this branch...
When I change the models to NOT override the default table name, it seems to immediately change the schema at the point of model instantiation, and the database doesn't find the old table names.
It is very strange!

in other words, I think maybe this plug-in generates the tables without a migration, so there's no initial migration that the earlier migrations, modify those tables can refer to

But you need to write a migration!  Otherwise when you deploy this we will strand all of the old versions tables!

right that's what's confusing. If I write the migration which I have a migration here it doesn't find the old tables.
Maybe i need two quick PRs.
Because if I change the set up of 'act_as_versioned' for say the Name model, to not use the custom table name, 'names_versions', but to use the default name, 'name_versions' it immediately sets up that table without a migration!

How did schema.rb change?
On Sat, Mar 2, 2024 at 10:00 PM andrew nimmo @.***>
wrote:

right that's what's confusing. If I write the migration which I have a
migration here it doesn't find the old tables.
Maybe i need two quick PRs.
Because if I change the set up of 'act_as_versioned' for say the Name
model, to not use the custom table name, 'names_versions', but to use the
default name, 'name_versions' it immediately sets up that table without a
migration!
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1990#issuecomment-1975002260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNJI666ZX6EKPPAA6WTYWKG6HAVCNFSM6AAAAABEDSD2BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGAYDEMRWGA
.
You are receiving this because you commented.Message ID:
@.***>

That's what i'm saying. That is the mystery.
The gem seems to have changed the schema directly. I started writing a migration but I never ran it, because I noticed Schema had already changed.

That doesn't make a lick of sense.  How could it possibly know the name of
the old tables????
Okay, when exactly did... oh nevermind, I'll pull the PR myself and pay
close attention to when the tables miraculously get renamed.
On Sat, Mar 2, 2024 at 10:11 PM andrew nimmo @.***>
wrote:

That's what i'm saying. That is the mystery.
The gem seems to have changed the schema directly. I started writing a
migration but I never ran it, because I noticed Schema had already changed.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1990#issuecomment-1975003939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNMKJVXJQTUV6ZZOGDLYWKIFXAVCNFSM6AAAAABEDSD2BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGAYDGOJTHE
.
You are receiving this because you commented.Message ID:
@.***>

I'm curious why we're doing this.
Would it make any sense to declare acts_as_versioned bankruptcy and switch to a maintained versioning gem.
I'm pretty sure we'd have to abandon all the old versions and start from scratch. The last time I looked a this there wasn't a path from acts_as_versioned to a newer gem.
(I also wonder if acts_as_versioned is thread safe.)

You're right, Joe.  The reason we kept acts_as_versioned alive was because
it was so much work to migrate the old tables to the new ones.  Surely
that's important, right?  We aren't actually considering removing all
editing changes ever made on the site?
On Sat, Mar 2, 2024 at 10:41 PM Joseph D. Cohen @.***>
wrote:

I'm curious why we're doing this.
Would it make any sense to declare acts_as_versioned bankruptcy and
switch to a maintained versioning gem.
I'm pretty sure we'd have to abandon all the old versions and start
from scratch. The last time I looked a this there wasn't a path from
acts_as_versioned to a newer gem.
(I also wonder if acts_as_versioned is thread safe.)

—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1990#issuecomment-1975008951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNOS4U4TB5ISC7UWOVTYWKLWXAVCNFSM6AAAAABEDSD2BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGAYDQOJVGE
.
You are receiving this because you commented.Message ID:
@.***>

coverage: 94.421%. remained the same
when pulling 36f4f16688a8a807adad7b8bd06eef74d23e56bc on nimmo-version-tables
into 26dcd4066454e31e1706135f8156e60e3a1d14e7 on main.


Switch MarshalTo from append to write

This is a lot more consistent with the stdlib when dealing with lower
level byte slices. The idea is that the code will error if the buffer is
too small, rather than silently append. The MarshalSize method allows
you to know the exact size required so there's no reason why you can't
allocate the right amount of memory.

And yeah, this is me back-tracking from the original code review where I wanted to append while you guys wanted to write. The big difference is that we check the bounds and never append.


'Find out more' link is broken.

Describe the bug
Link: https://docs.opencollective.com/help/hosts
Does not work:
"Page not found
Sorry, but the page you were looking for could not be found."
To Reproduce
Steps to reproduce the behavior:

Go to 'https://opencollective.com/become-a-fiscal-host'
Click on 'Find out more'
See error

Expected behavior
Docs
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@contraexemplo can you have a look?

Fixed on the docs side as well (https://github.com/opencollective/documentation/commit/387ca1d8f3ed567e1c765204d596e3df2777a1f4).


[fix] Container sass placeholder has incorrect variable for spacing

This placeholder in the pfe-sass/extends/_extends.scss file has the padding property using the container-spacer var, and it should use container-padding.
/// Set up a container element
%container {
  position: relative;
  display: block;
  width: 100%;
  padding: pfe-var(container-spacer);
}

Lettuce: Green Thumb Made 👍


Build and publish container images for easy integration

PR summary
Builds and publishes container images in CI. PR builds ensure the image continues working
for a simple case, and main/tagged builds publish new images.

Based on Matthias' initial PR: https://github.com/IBM/openapi-validator/pull/601/files
Run test-docker with a valid IBM ruleset extension in CI
Spruce up docs for container image use on README
Add deploy step to push images

Thoughts on where these images should be pushed?
I selected ibmcom/... since it looks like there's already images out there for IBM. The GitHub registry might also be worth considering.
I thought the Containerfile idea Matthias introduced was pretty cool, but I don't think that has caught on as a standard yet and I don't want to confuse folks new to it. I changed it to Dockerfile for that reason.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:
N/A

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Blaimi:x: JohnStarichYou have signed the CLA already but the status is still pending? Let us recheck it.

Hey all! I think this is ready for review. Before we merge, we should set up some way to log in to the appropriate registry before the docker push. I don't know which registry is preferred, so it'd be great to sort that out first.

Ok, all updated and the test deploy was successful:

:tada: This PR is included in version 1.6.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Link the Fontsource docs for Preloading Fonts in the Fonts page

Description (required)
Adds a link in the Using Fontsource section of the Fonts page referencing the Fontsource docs' Preloading Fonts guide.
Related issues & labels (optional)

Closes #7451

Excited to share my first contribution to Astro Docs  🎉 My Astro Discord username is _vivitt

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/fonts.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Hello @sarah11918,
Thanks for your quick feedback!
Your suggestions make a lot of sense. I’ve just added one more commit including both changes. Let me know what you think and if you see anything else that can be improved.


Reduce Elm closure

It's around 1400MB atm: http://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.elmPackages.elm-compiler.x86_64-linux#tabs-charts

I suspect most of it is Haskell https://github.com/NixOS/nixpkgs/issues/4504.

I tried setting enableSharedExecutables = false; on each elm package, but that didn't yield much result.

I guess it needs to compile haskell during runtime.

Don't think so, npm has binary compiled elm in 80M:
$ du -sh node_modules/elm/Elm-Platform/0.17.0/.cabal-sandbox/bin/
78M     node_modules/elm/Elm-Platform/0.17.0/.cabal-sandbox/bin/

All statically compiled

OK, sounds convincing. If it doesn't assume ghc on $PATH or something.

@domenkozar, enableSharedExecutables = false; helps only for packages that have no library components. Once a package provides a library, it invariable depends on the transitive closure of its dependencies -- which includes GHC. If the libraries aren't neeed by end-users, then it might make sense to remove them to mitigate this problem.

@peti indeed.
I can get it down from 1.7G to 50MB using following patch:
diff --git a/pkgs/development/compilers/elm/packages/elm-compiler.nix b/pkgs/development/compilers/elm/packages/elm-compiler.nix
index f6a92b6..d1c0171 100644
--- a/pkgs/development/compilers/elm/packages/elm-compiler.nix
+++ b/pkgs/development/compilers/elm/packages/elm-compiler.nix
@@ -13,8 +13,10 @@ mkDerivation {
     sha256 = "17y0jlii81mnjywknblcv1nfja51slmwrhz9x8w144b0sblcj0if";
     rev = "e44deafaf9cbf3749484070f267f03a368711adb";
   };
-  isLibrary = true;
+  isLibrary = false;
   isExecutable = true;
+  enableSharedLibraries = false;
+  enableSharedExecutables = false;
   libraryHaskellDepends = [
     aeson aeson-pretty_0_7_2 ansi-terminal ansi-wl-pprint base binary
     bytestring containers directory edit-distance filepath indents

But elm-make and others can't be compiled then since elm-compiler library doesn't exist. Does that mean we have to build elm-compiler twice?

If the elm library is required to compile elm programs, then it seems like elm compilation implies Haskell compilation, which in turn requires GHC and friends. I don't see what we could do about that, really (except for some multiple outputs magic).

@peti it's not required to compile Elm programs, but to compile all of Elm executables (elm-make, elm, etc).

Hmm, in that case you would probably need a full version of elm for compiling the toolchain, and the toolchain itself would then be linked statically so that nothing refers to GHC. I am sorry for being vague, but I know nothing about elm and its internal structure, so I have really no clue what I am talking about here. :smile:

There is now upstream discussion to join all projects under Elm: https://groups.google.com/forum/#!topic/elm-dev/-qGgYTKyAS8
Until this is decided I don't think it's worth pursuing reducing closure size, but let's keep the issue open as a reminder to myself to check this in a few months.

I'm going to close this, Elm 0.19 ships a single executable so it will be easy to use static haskell dependencies for compiling it with small closure-size.

Elm 0.19 should have been released a long time ago.
Once https://github.com/NixOS/nixpkgs/issues/32082 is done, we can really just do enableSharedExecutables = false; as I intended a year and a half ago.

Fixed by https://github.com/NixOS/nixpkgs/pull/32629/commits/f73e5245e0f0a671d4132ac33a9be9145fe30845 once https://github.com/NixOS/nixpkgs/pull/32629 is going to be merged.

Elm 0.19 has just been released!


Prototype EspNow peer to peer video

Why
As discussed in issue #8, we would like to reduce the video latency between the rover and the gamepad in order to make FPV mode more usable.  One potential latency is the protocol between the rover and the web application.  The Open.HD project has addressed this issue in part by writing code to create a custom peer to peer connection between RaspberryPi endpoints using usb wifi adapters' radios.  Espressif had created a similar peer to peer protocol between Esp32 endpoints called EspNow.
What
Implement a peer to peer video protocol from an Esp32Cam to an Esp32 with a TFT display using EspNow.  Measure the latency of transmitting a frame from the Esp32Cam to the endpoint.  Compare the peer to peer latency with the web app's websocket latency.

EspNow will not work for video; it has a a maximum message length of just 250 bytes.  So let's keep the Why part of this ticket, but change the What.  I'm going to close this issue.
I've created a new issue to try a different approach
First, let's measure the latency in our current setup where the Esp32Cam in configured as a station and then connects to some local access point.  So in this setup, the client also connects to that access point and can then load the web application using the rover's ip address.  So the web socket packets must pass through the access point in this configuration.
Then let's implement a scheme where we make the Esp32Cam an access point and connect directly to that access point to load the web application.  That scheme eliminates the router as the middle man.  This may also simply connecting to the rover if we can choose it's ip address on the network; then we can know a priori what that is; no messing with router ip-allocation.  Once we implement that scheme, then measure the latency; hopefully eliminating the router will speed things up.

The analysis process is useful.


Update Resources/doc/index.rst

Added Codesnippets  on missing installation steps.

Thanks for the contribution. Closing in favour of #79.


Revising Imaging Level 1, 3 and 4 components

This PR combines proposed changes to Imaging level 1, Imaging Level 3 and Imaging level 4.
Imaging Level 1
Fixes #42. Replaces #34
Imaging Level 3
Fixes #43, Replaces PR #50

[x] Add mask component
[x] Add images component
[x] Add channels component
[x] Add mask attributes
[x] Add images attributes
[x] Add channels attributes
[x] Add a regex for Channel Metadata Filename to ensure is csv
[x] Tidy up parents
[x] Assign reviewers

Imaging Level 4
Fixes #49

@elv-sb Once approved can you leave for me to do the merge... I will do a squash-and-merge and tidy up the resulting commit message - otherwise there is quite a long and messy chain of commits.


Code for Responsive Safety in RL by PID Lagrangian Methods

The paper mentions https://github.com/astooke/safe-rlpyt (404)
This repo mentions the code in the commits but i don't find anything in the head.
Where can i find an official implementation?

Hi, I found it: https://github.com/astooke/rlpyt/tree/master/rlpyt/projects/safe


Start-AzsReadinessChecker failed because Import-Module "Microsoft.AzureStack.ReadinessChecker" failed.

Repro:

Execute script with the following command:
Start-AzsReadinessChecker -RegistrationAccount $registrationCredential -AzureEnvironment AzureCloud -RegistrationSubscriptionID $subscriptionID

Expected result: Execution successed

Actual result: got the following error
Start-AzsReadinessChecker : The 'Start-AzsReadinessChecker' command was found in the module 'Microsoft.AzureStack.ReadinessChecker', but the module could not be loaded. For more information,

run 'Import-Module Microsoft.AzureStack.ReadinessChecker'.
At line:1 char:1
Start-AzsReadinessChecker -RegistrationAccount $registrationCredentia ...
CategoryInfo          : ObjectNotFound: (Start-AzsReadinessChecker:String) [], CommandNotFoundException
FullyQualifiedErrorId : CouldNotAutoloadMatchingModule
and I run "Import-Module" command and the got the error following

PS C:\Users\xxx.xxxx> Import-Module Microsoft.AzureStack.ReadinessChecker -Force
Import-Module : The following error occurred while loading the extended type data file: Error in TypeData
"Microsoft.Azure.Commands.Common.Authentication.Abstractions.IAzureContextContainer": The TypeConverter was ignored because it already occurs.
Error in TypeData "Microsoft.Azure.Commands.Common.Authentication.Abstractions.IAzureContextContainer": The member SerializationDepth is already present.
Error in TypeData "Microsoft.Azure.Commands.Common.Authentication.ProtectedFileTokenCache": The member PropertySerializationSet is already present.
Error in TypeData "Microsoft.Azure.Commands.Common.Authentication.ProtectedFileTokenCache": The member SerializationMethod is already present.
Error in TypeData "Microsoft.Azure.Commands.Common.Authentication.AuthenticationStoreTokenCache": The member PropertySerializationSet is already present.
Error in TypeData "Microsoft.Azure.Commands.Common.Authentication.AuthenticationStoreTokenCache": The member SerializationMethod is already present.
Error in TypeData "Microsoft.Azure.Commands.Profile.Models.PSAzureContext": The member SerializationDepth is already present.
Error in TypeData "Microsoft.Azure.Commands.Profile.Models.PSAzureProfile": The member SerializationDepth is already present.
At line:1 char:1
Import-Module Microsoft.AzureStack.ReadinessChecker -Force
CategoryInfo          : InvalidOperation: (:) [Import-Module], RuntimeException
FullyQualifiedErrorId : FormatXmlUpdateException,Microsoft.PowerShell.Commands.ImportModuleCommand

@kariyukisusumu please provide us with the documentation you are referring to so we an better assist

@kariyukisusumu I apologize for the delay on this issue. Do you still need assistance with running Start-AzSReadinessChecker?

@kariyukisusumu I apologize for the delay on this issue. Do you still need assistance with running Start-AzSReadinessChecker?

We resolved this issue.
We re-run in other WS2016 machine(NOT Azure VM) and we succeed the Start-AzsRedinessChecker.
I guess that this issue happened because of  the Powershell Module version mismatch.
Thanks


feat(textarea): higher by default on mobile

pushed another thing after some clarifying design chat, unrelated, just to save time, will try to not squash when merging