SettingWithCopy dependence on reference count

As a follow-up to my question, I believe the current approach is that pandas assumes that the programmer intends assignment to a child DF/S to be propagated to the parent DF/S as long as the parent has a non-zero reference count.
The problems like the ones I described would be avoided if child DataFrame always warned on assignment regardless of the reference count of the parent object - UNLESS a copy() method or DataFrame constructor was explicitly applied to the slice.  (If desired query and/or filter can be documented as copy methods as well.)
(Making ref count incremented when the child is a view is not enough because the code that works normally might one day stop working - with SettingWithCopyWarning that but might be ignored if it appear on the client site - simply due to the change in the input data.)
If this approach is followed, the documentation can also be clarified as follows:

When applying indexing, filter (???) and some other operations (???) to a parent DF/S pandas may create a view or copy of the parent depending on conditions that are too complicated to describe. This creates a possibility of a subtle bug in the code when assigning to the child DF/S. To help catch such potential bugs, pandas assumes that the programmer intends assignment to a child DF/S to be propagated to the parent DF/S unless it is explicitly copied (using .copy(), .query(), DataFrame constructor, etc??? ); when pandas cannot guarantee such behavior, it generates SettingWithCopyWarning. Note that this happens regardless of whether the parent DF/S is reachable in the current context or even whether it still exists as an object.

pls show an explicit example

Examples (more context in my SO question):
import pandas as pd
data = pd.DataFrame({'a': [1, 2, 3], 'b': ['a', 'b', 'c']})
new_data = data[['a', 'b']]
data = data['a']
new_data.loc[0, 'a'] = 100 # no warning, doesn't propagate to data
assert data[0] == 1

data = pd.DataFrame({'a': [1, 2, 3], 'b': ['a', 'b', 'c']})
new_data = data['a']
data = data['a']
new_data.loc[0] = 100 # no warning, propagates to data
assert data[0] == 100

data = pd.DataFrame({'a': [1, 2, 3], 'b': ['a', 'b', 'c']})
data = data.groupby('a')
new_data = data.filter(lambda g: len(g)==1)
new_data.loc[0, 'a'] = 100 # no warning, does not propagate to data
assert data.filter(lambda g: True).loc[0, 'a'] == 1

Edit to my original post: I think it would also be useful to have a method, say unlink(), that explicitly breaks the link between a DataFrame slice and its parent DataFrame. It's not the same as copy() because copy() always copies, while unlink() would be a no-op if the slice happens to already lose its link to the parent (e.g., due to the dtypes combination, in-memory arrangement, etc., or because it or or copy() was already called earlier).

you can just set:
is_copy = None
object dtypes always copy and are never views
this while earning bizness is a mess because we don't have copy-on-write
I don't think this is likely to be addressed in current pandas and will have to wait for pandas 2.0
that said if you want to whip up some tests that mimic current behavior we can put them in a special area so as to note behavior that should change

Of course, I understand that CopyOnWrite is the only proper resolution. But pandas 2.0 is probably 3-6 years away. I'm not sure about the amount of effort to make the warning more comprehensive (e.g., as I suggested or otherwise); if it's not that big maybe worth it? After all, in the meantime this is the only protection from these bugs.

you are misunderstanding
we are freezing for pandas 1.0 by the end of the year
2.0 is slated for next year - so it's not 3-6 years (where did that come from?)
but more like 1-1.5

you are certainly welcome to PR a fix for this - but it requires s non trivial effort

Oh sorry, I didn't realize pandas 2.0 is not that far. I naively assumed 1.0-2.0 is going to take comparable time to 0-1.0. In that case, fixing SettingWithCopyWarning is not a high priority.

yeah 1.x will be long term supported with very few
API changes

@pkch FYI, I made some progress on setting up a PR for keeping track of children of DataFrames (#12036) -- something you may have seen it looks like, but worth flagging. I set it aside since there were aspirations of CopyonWrite getting implemented in 1.0 (#11970), though now appears that it's been pushed to 2.0 (https://github.com/pandas-dev/pandas2/issues/10). You may find some of the components useful if you decide to try and get something in before 2.0.


binder page

Adds a page with information about the Binder project.
Currently, this doesn't change the navbar because there isn't much room there for a new item. For now, we can just link directly to this page when people have questions about
the Binder project.

I've been pondering who will read this page, what they already know and what they will be looking for. Once we know this we can write text for them.
Here is my guess: either familiar with Jupyter-the-notebook or just heard of Jupyter but unfamiliar. Not super informed about what Project Jupyter is and the different options and sub-communities that exist. Not because they don't care but keeping up with open-source politics isn't what they do day to day. They are just using "Jupyter". They are wondering what else Jupyter does out of interest or because they have a concrete problem that they would like to solve and wondering if Jupyter "already has something for this".
As a result I think we should describe what problems Project Binder solves in a way that people who have this problem can recognise themselves. We can't make an exhaustive list because that list is super long. My feeling is that the three most frequent uses of mybinder.org are:

workshops and tutorials (Scipy and Pycon workshops. "do you also love spending the first half of your workshop sorting out how to install stuff?")
documentation and examples (spacy, bokeh, scikit-learn, etc)
education (lecture courses and books)

I would lead with these (or other) three examples of when you want to use Binder. It is important to include the badge in each example or other link that is "try it now". Binder is all about making trying stuff easy and low risk so we need to use that in our page :)
Then a blurb about what Project Binder (PB) is (we already have that in the current diff).
Then a list of the things PB does, with their GitHub repo descriptions as description (maybe we need to update them a bit), link to the docs, link to "how to get started", link to the repo

BinderHub
repo2docker
mybinder.org
binder example gallery(?)

(Put like that it seems like we don't do that much...)
Then a short block on "where to find out more, come chat to us, ask on the forum, get involved with contributing to the individual repositories. Thanks to GKE and OVH for sponsoring mybinder.org"

What do you think  about that as a rough plan? (Also how did it take till now for me to realise that Project Binder + Jupyter can be shortened to PB+J that mos awesome of sandwich toppings?)

Finally looping back on this one too :-)
Thanks @betatim for the comments - I updated the content and pushed a new commit w/ some extra info, what do you think?
https://5d8e72bd1755f90008c7b093--dazzling-gates-2d8e39.netlify.com/binder
One thing to note in terms of "who will land on this page?". Right now, it isn't linked from anywhere in the Jupyter documentation. The link just "exists" and we could link to it externally. So I doubt (in its current form) this page would just be stumbled upon by curious Jupyter people, but I might for example include a link to this page when I give talks about Binder etc.

Not linking it from the navbar means the pressure is lower to get it right first time. I like the idea of linking it from other places and the fact that it is on jupyter.org will give it some credibility.
How do we move forward getting this merged? Do we ping someone? Mark it as ready for review?

good question - @tgeorgeux could you take a look and merge if all looks OK? This PR doesn't change the front page of jupyter.org, it only makes this page available if somebody directly links to it (which I'd like to do occasionally in talks etc)

Also of note, I don't have merge rights on this repo. :)

Thanks for the comments @tgeorgeux - I think should should be able to merge, since GitHub blocks a merge until someone with merge rights approves the PR, and your approval has unlocked the ability to merge for me, so I assume you have merge rights?
If not, perhaps I can merge this away and then link to it from the docs.mybinder.org page?

My permissions are at a weird stage where I am an 'approving reviewer' but still can't merge unless somebody ELSE who is an approver approves. Regardless I don't really see any reason not to merge if you've got the button!

okie dokie - I'll merge this since it's not changing the front page / nav bar etc at all, thanks for the review and improvements!


Are the gene-trait pairs all cross-tissue?

Hi, I am quite interested in the PhenomeXcan method. I was wondering what is the biological meaning of 'regional colocalization probability' (RCP)?  Is it something like aggregating the effects in each tissue made by a given gene?
Also, has fastENLOC got a tissue-specific method to give the RCP values in each tissue? or weights to show how much a gene-tissue pair contribute to the trait? Thanks!

Hi @chilampoon, thank you for your interest.
RCP gives you the probability that the GWAS signal (for a trait) is colocalized with the eQTL signal (for a gene-tissue pair). Note that this works per tissue, and for the paper we have taken the maximum RCP across all tissues for a given gene-trait pair.
If you want to access the tissue-specific results, follow the instructions in the main page to access a Google Spreadsheet with the individual results for fastENLOC.

I see. I just didn't notice the Google Spreadsheet. Thank you!


Renaming device after setting it as active results in wrong name during interactions

After setting the device as the active device, any of the commands under "Get active device" use the name as it was set when I set it as the active device instead of the new name.

This is a good one! I'll modify the logic to verify that the saved device is still "available" (which would catch both offline and renamed devices) and handle accordingly.


in clause parsing and interpretation issue

Describe the Bug
if you try to run
3 in [1,2] or true
in feelin playground. It results in false.
Steps to Reproduce
1.visit link
https://nikku.github.io/feel-playground/?e=3+in+[1%2C2]+or+true&c=~3YCAkIC%2BgICAgICAgIC9AgCXnLILCNLEWVvD4A7RTE6e5VQHnL67RAf8ffGpOTFExGjxp2lIHt%2Fmy8diAzMQSsxIFwmdegBxI7oRrX98i6CA&t=expression&st=true
Expected Behavior
I think this is due to the parser not able to determine the proper ending of an unary test when "in" is involved in a comparison.
The disjunction in the above case should involve 3 in [1,2] and true
not [1,2] and true
Environment

Host (Browser/Node version), if applicable: [e.g. MS Edge 18, Chrome 69, Node 10 LTS]
OS: Windows 10
Library version: latest

@spearsandshields The specification backs up your claim. disjunction has higher precendence, than comparison, hence your expression should evaluate as follows: (3 in [1,2]) or (true).

Relevant excerpts from the specification:

Cf. feelin playground and feel scala playground.
The two implementations handle the example structurally similar, with different interpretation around null conversion. As we're also not directly comparing disjunction and comparison here, but nesting I suspect that such a statement will be (1) generally parsed this way (also we parse left to right) and (2) you're better off to disambiguate anyway.

As always, happy to take any reasonable arguments and contribution to move this forward, i.e. a dmn-tck test case could ensure we end up in the right interpretation.
It won't be worth my time though, hence I'm closing this issue as won't fix.

Sounds reasonable as per your priority, thanks for the investigation


Add jedi-language-server (a Python LSP)

I've been using this for a while, works fine.

Actually, this has some issues.
jedi_language_server expects the current project's dependencies to be installed in its same environment. Because those are not inside the container, completion and other features work rather poorly.

Hey, I think the Go language server works like this aswell. I already created a PR in lspcontainers/lspcontainers.nvim#33 to make it work in Go. For this language server you cold probably make it work in a similar way.

Smart. I don't think the same approach can work with Python though. For a few reasons:

There's no single place where all dependencies get downloaded.
It's hard to figure out how to find the virtualenv with the dependencies. The project might be using poetry flit or pipenv or mkvirtualenv to handle dependencies, and it's non-trivial to find out which.

Regarding (2), I'm working on a wrapper that figures that out for other dev tools, so it might be usable here somehow. The problem is this needs to run in the host, since the tool being used indicates where the virtualenv is located.

Maybe a potential workaround for this is to create a custom image with the requirements is installed in a project specific LSP container? This breaks the independence of the language server and the project, but helps with also supporting cases where someone is developing in a container too. I suppose this is a larger solution than for just this PR but putting it out there.

Actually, this has some issues.
jedi_language_server expects the current project's dependencies to be installed in its same environment. Because those are not inside the container, completion and other features work rather poorly.

Sorry for my delayed reply - been working and moving which has consumed a lot of my time. This is indeed how gopls currently works due to how packages are resolved in the container and mounting the host packages into the container is a possible option.

Smart. I don't think the same approach can work with Python though. For a few reasons:
1. There's no single place where all dependencies get downloaded.

2. It's hard to figure out _how_ to find the virtualenv with the dependencies. The project might be using `poetry` `flit` or `pipenv` or `mkvirtualenv` to handle dependencies, and it's non-trivial to find out which.

Regarding (2), I'm working on a wrapper that figures that out for other dev tools, so it might be usable here somehow. The problem is this needs to run in the host, since the tool being used indicates where the virtualenv is located.

I'm thinking the problem here is essentially the approach to package management with something like virtalenv over npm. For example, virtualenv hijacks the shell itself to work properly where as something like npm is just a file path. Because virtualenv is dependent on a shell - it may be a requirement (though I don't know the solution) in order to resolve the packages.
If I think about this a bit more - it seems you'd need some way to essentially reproduce the steps taken to create a virtual environment in the container and then run some kind of automation script to install everything on start...
OR
Don't use virtualenv at all and find a different approach for this.
If you think about it - virtualenv is doing the exact same thing that our container is doing so in a way it's just an added layer. Might find it easier to avoid any of it and just install the packages to the system somehow.

For example, virtualenv hijacks the shell itself to work properly where as something like npm is just a file path.

Raw-virtualenv just alters your $PATH and adds /path/to/virtualenv/bin to it.
However, virtualenv is rarely used directly, it's usually used by a higher level tool, like mkvirtualenv, poetry or pipenv. Each of these tools store the generated virtualenv in a different location too.
And that's where the tricky part comes...

Might find it easier to avoid any of it and just install the packages to the system somehow.

If the project uses poetry, then dependencies are defined in pyproject.toml with one format. If the project uses pipenv,then it's a different file. Finally, the project might be using neither, at which point you have to guess if it's in setup.py or requirements.txt.
Until the Python ecosystem as a whole has converged into "one way to defined dependencies" a bit more, I don't think there's much that can be done here.
It would be possible to write a script to determine the right thing, and build a container on-the-fly, but this is rather tricky:

When does the images get rebuilt? E.g.: How do we pick up dependency changes?
Do we pile up a new container for each python project that's opened?
Is the user responsible for cleaning up stale images?

I'm starting to think that this particular LSP is ill-suited to be containerised; mostly due to bigger inconsistencies in python-land itself.

Smart. I don't think the same approach can work with Python though. For a few reasons:
1. There's no single place where all dependencies get downloaded.

2. It's hard to figure out _how_ to find the virtualenv with the dependencies. The project might be using `poetry` `flit` or `pipenv` or `mkvirtualenv` to handle dependencies, and it's non-trivial to find out which.

Regarding (2), I'm working on a wrapper that figures that out for other dev tools, so it might be usable here somehow. The problem is this needs to run in the host, since the tool being used indicates where the virtualenv is located.

Could it be an option to off-load this to the lspcontainers config? Maybe we could add an option there to specify a path where the dependencies are located and then mount that path into the container. I get that this is not a very pretty option either because if you may need to have different configs for different projects, but this way we at least could avoid building extra tools for finding dependencies.

Maybe we could add an option there to specify a path where the dependencies are located and then mount that path into the container.

Poetry uses {cache-dir}/virtualenvs, or $POETRY_VIRTUALENVS_PATH.
Pipenv uses $WORKON_HOME.
mkvirtualenv uses $WORKON_HOME.
There are other tools (e.g.: flit), so this list is non-exhaustive.

We'd need some logic on the host to determine which of these is used, and mount the right thing.
As an alternative, we can simply mount all of the above as read-only volumes, and let the tools inside the container figure out which one they need.
This however, only covers the "find the right virtualenv location" part, and not actually running the tools inside them.

I'm currently working on a small python script to help with something very related. mypy is a type-checking tool for Python, that has to run inside the virtualenv (since it needs to access all the project dependencies).
I run this via a non-containerised LSP, but an issue I have is that I need to activate the virtualenv before I run vim (so that the mypy inside the virtualenv is run, and not the mypy in /usr/bin. The wrapper script I'm working on detects which of the above (poetry/pipenv/mkvirtualenv) a project uses, and runs the mypy inside of that virtualenv.
I feel that this might be a useful piece in the puzzle we're trying to build here, but containerising on top of it is an extra step.

Maybe we could add an option there to specify a path where the dependencies are located and then mount that path into the container.

Poetry uses {cache-dir}/virtualenvs, or $POETRY_VIRTUALENVS_PATH.
Pipenv uses $WORKON_HOME.
mkvirtualenv uses $WORKON_HOME.
There are other tools (e.g.: flit), so this list is non-exhaustive.

We'd need some logic on the host to determine which of these is used, and mount the right thing.
As an alternative, we can simply mount all of the above as read-only volumes, and let the tools inside the container figure out which one they need.
This however, only covers the "find the right virtualenv location" part, and not actually running the tools inside them.

I'm currently working on a small python script to help with something very related. mypy is a type-checking tool for Python, that has to run inside the virtualenv (since it needs to access all the project dependencies).
I run this via a non-containerised LSP, but an issue I have is that I need to activate the virtualenv before I run vim (so that the mypy inside the virtualenv is run, and not the mypy in /usr/bin. The wrapper script I'm working on detects which of the above (poetry/pipenv/mkvirtualenv) a project uses, and runs the mypy inside of that virtualenv.
I feel that this might be a useful piece in the puzzle we're trying to build here, but containerising on top of it is an extra step.

As a temporal solution, I'm using the project image as a base for the Jedi LSP image.  This way, I don't have to worry about how the project handles dependencies.
https://github.com/marticols/nvim_lsp_dockerfiles/blob/8180bb89ff0cc890c1554a047ce321901c290cc9/jedi/Dockerfile#L1-L7
In case my project has an image called to_do_app, I generate the project LSP image with:
make build/jedi tag=to_do_lsp base=to_do_app
Then I configure lspconfig to use the project LSP image if I'm working on the project directory.
https://github.com/marticols/dotfiles/blob/9d3dc5df84c962318339689bc360e44464bc377d/nvim/lua/setup/lsp.lua#L15-L40
I also have a fallback jedi lsp image in case I haven't configured the project:
make build/jedi tag=jedi_lsp base=python:slim-buster
Maybe giving the option to change the base image and building it before running the image could be a nice solution for this PR.

This might actually be the only real way this can be solved in a Docker focused approach. Normally - we add our dependencies to the Dockerfile itself during build so this isn't an issue. When trying to add packages at a more global level with Docker post-build is always an issue. This is something we may need to think about "how" we would implement this.

Another note (though I'd rather not have to do this) would be to accept that this type of language server that requires global packages different from the workspace might not fit the design of lspcontainers. I'm not saying that's the case at the moment - I'm just putting it out there as a possibility of limitation due to the design.

As a temporal solution, I'm using the project image as a base for the Jedi LSP image. This way, I don't have to worry about how the project handles dependencies.

Most python projects (I'd say over 90%) don't have an accompanying Dockerfile or docker image. This does serve as a workaround for the few large projects that do, but doesn't really scale beyond those few.
An alternative would be to try and install the project using PEP517 tooling (this should at least bring in all runtime dependencies), but that won't work for projects that aren't python libraries (e.g.: desktop applications that ship via meson).

I'm not using this language server any more. If someone else is interested, feel free to pick it up.


Opening Subpage in Browser throws 404 error

Hello!
I'm facing an issue where the app routing works fine when I use in app navigation (i.e. clicking pages and tabs), but doesn't work when I open the url in browser:
open https://theremapp.com - works
open https://theremapp.com/transparency - doesn't work
Refreshes also do not work, once I was navigated to this new page.
Interestingly enough, this is not an issue when I run the app on my local host, but is an issue when I deploy. Thank you.

Hi @michaeldwu - thanks for opening the issue :)
Unfortunately, we will not be able to solve the issue in this repo. I am also not sure why it happens.
The path strategy functionality is implemented in the framework itself. This means you would need to open an issue at https://github.com/flutter/flutter/issues to report the bug (about "path URL strategy in Flutter web").

is there any other soluction?

Hey @michaeldwu, did you find any solution?

@sathish-xe Hi, this is most likely because your SPA is not configured properly. I have elaborated on it in my StackOverflow answer here:
https://stackoverflow.com/a/65709246/6509751
(See the notes section)


Wasm support

Hi,
Would you consider integrating WASM support based or not based on this repo (which based on this one)?

This does look interesting for sure. It seems all changes can be localized to a different platform enlightenment provider to tweak scheduling behavior via a custom CAL? Is there anything else needed besides this to get it working?
Given we have enlightenments and custom CALs as an extensibility point, and this shows their usefulness, we should at the very least make sure that they cover everything that's needed to light up an environment like WASM such that the core of Rx remains the same across all plaforms, and just a tiny module needs to be installed to make it work in different environments. So, if there's anything missing, or something that looked particularly hard, we should address this first.
Beyond this, we can consider if we want to support WASM out of the box as part of Rx releases.

Hey @bartdesmet and thanks for your detailed reply.
First of all, the way of extensibility I've found, is as you can see in the code, by explicitly setting the obsolete PlatformEnlightenmentProvider.Current with our custom IPlatformEnlightenmentProvider. Would be happy of better ways.
Apart from that, as @jeromelaban pointed out, there is a simple way to 'port to wasm', which is if we get an exception when trying to create a new Thread. It would definitely be nice if the functionality is baked in Rx itself. Otherwise, we're looking for nicer ways to plug in custom enlightenment providers.
P.S. I'm not sure what you're referring to by CAL.

Hey @bartdesmet, aside from the custom enlightenment provider, there are no other changes that are needed at this point, aside from the temporary lack of threads for wasm. I can tell you that it works pretty well, we've been using @nventive a similar set of changes for a while now, and it works pretty well. It's obviously running all single-threaded so not all operators are functional (blocking ones, specifically), but the rest is behaving as it would on any .NET runtime that supports Rx.
The only particularity is the fact that the Wasm scheduler (when no threads are available) requires the reset of a System.Threading.Timer instance (which maps to a JavaScript setTimout, and can be somehow costly. For the CoreDispatcher in Uno, we've had to use a special JS mixin that uses of the non-standard setImmediate function, which is a lot less costly, but requires the addition of a non-trivial piece of Javascript, something that mono does not provide an easy way to package, and that dependents such as Rx may not want as well.
Threads support in mono-wasm will fix a lot of those temporary platform issues.
I'm glad that you kept the extensibility mechanisms you put in place for supporting PCLs (way back now !), as it allows for this kind of new platforms support without having to alter Rx published packages, and their dependents. I'd be a good idea not to deprecate them :)

Thanks for the prompt replies.
First, sorry for the jargon. CAL stands for "Concurrency Abstraction Layer" and is the bottom-most layer of scheduler infrastructure, which seems was replaced for WASM. This is indeed a supported scenario, so I don't think there's much to do in Rx itself at this point.
I'll make sure the support for enlightenment providers doesn't get dropped. A similar extensibility point to intercept query operators (for purposes of e.g. building debuggers) was being questioned in https://github.com/dotnet/reactive/issues/540, so it'd good to see real-world use cases of these Rx 2.x facilities being pointed out here in the issue tracker.

It seems to me such platform support can live outside dotnet/reactive, as demonstrated by the example provided given that we don't remove the various hooks and override possibilities (very unlikely to happen now). Also I presume there would be quirks to be worked around quickly due to platform bugs discovered or version changes which are much better handled via the dedicated external library.


Testing process

Testing and Validation:

Conduct thorough testing to ensure the reliability and correctness of your RTOS simulation.
Validate the simulation results against expected outcomes.
Address any issues or bugs that may arise during testing.

Performance Analysis:

If applicable, perform a performance analysis of your RTOS simulation.
Measure and analyze factors such as task execution times, context switch overhead, and system responsiveness.

DoD: Creating a Test script to test RTOS functions

commit:
https://github.com/youssef456/RTOS_Embedded_Linux/commit/290c9ac0fecfe038dd561256e0339d397bb525c8


Is there a method on how to restrict the output size?

Hey
I would want to restrict the output size by words/characters. Are there any methods?
I looked at max_length & max_tgt_len however they seem to not be working.
I set
recall_eval as False
max_length as 20
max_tgt_len as 20
min_length as 10
However the output remained of the constant size
Note: Using the below inference command ( Pre Trained CNN DM model Extractive )
python src/train.py  -task ext -mode test -test_from ./models/bertext.pt -batch_size 3000 -test_batch_size 500 -bert_data_path ./bert_path/ -log_file ./logs/val_abs_bert_cnndm  -sep_optimtrue -use_interval true -visible_gpus -1 -max_pos 512 -max_length 20 -max_tgt_len 20 -alpha 0.95 -min_length 10 -result_path ./results/ -report_rouge false -recall_eval False

These hyperparameters are used to control abstractive summarization.
For extractive summarization, please refer to https://github.com/nlpyang/PreSumm/issues/31 for setting the number of selected sentences.


Run InstCombine tests in CI

Run tests for the library InstCombine which is build on the CI to check
that the mutations applied don't affect functionality.
Fixes #40.

It turned out to be impractical to run the InstCombine tests in the CI. This has instead been replaced by #83.


Ability to relocate session space

Playing around with teleportation and had to move the world underneath the user.
Should be an OpenXR way to update the session's reference space, making that unecessary / just locating the player within the world.

Nope, correct way is to move the world, and not mess with the openxr spaces.


"Invalid configuration file" when creating linked clones

Hi,
getting this message every time labbuildr is creating a linked clone:
 ==> Creating Linked Clone E2013N1 from E:\labbuildr\2012R2FallUpdate\2012R2FallUpdate.vmx, VMsize is XL
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.

But everything works as it should.
Marcel

the isuuse comes wgen creating the scsi disks. for anothe closed issue i had to uncomment warnings ( https://github.com/bottkars/vmxtoolkit/issues/5 ) iknow the iwarnings are nnoying, and have never been fixed by vmware, as they only appear on some systems. i will pipe the garbage t the errro pipe, so you will no longer see them. closed and moved to vmxtoolkit


Alerts are repeatedly opened and closed by unrelated commits.

Here is an example alert. https://github.com/mesonbuild/meson/pull/11218/checks?check_run_id=10309314938

Fixed alerts

Unused local variable (unittests/baseplatformtests.py:219)

This points to the following code: https://github.com/mesonbuild/meson/blob/891b4ffe3372c840322f5586430dcba34acf6d53/unittests/baseplatformtests.py#L219-L219
... but the commit in question doesn't modify that code, and it certainly doesn't fix that.
Now, if I go look at the history of this alert....

First detected in commit
Nov 25, 2022
@ eli-schwartz
Merge https://github.com/mesonbuild/meson/commit/f52936a8c5be498446e6f0ee98296b28ea8c7968 into https://github.com/mesonbuild/meson/commit/11fe8f11579d46870ed340dca8234ea35edf769c
86a6b42
unittests/baseplatformtests.py:219 on branch refs/pull/11108/merge
Appeared in branch refs/pull/11108/merge
Nov 25, 2022
CodeQL #8: Commit 86a6b42b
Fixed in branch refs/pull/11108/merge
Nov 25, 2022
@ eli-schwartz
Merge https://github.com/mesonbuild/meson/commit/f52936a8c5be498446e6f0ee98296b28ea8c7968 into https://github.com/mesonbuild/meson/commit/11fe8f11579d46870ed340dca8234ea35edf769c
86a6b42
Reappeared in branch refs/pull/11108/merge
Nov 25, 2022
@ eli-schwartz
Merge https://github.com/mesonbuild/meson/commit/b1f41107d76701efecc8cdde3ba798e992a2f0a0 into https://github.com/mesonbuild/meson/commit/11fe8f11579d46870ed340dca8234ea35edf769c
977e61e
unittests/baseplatformtests.py:219 on branch refs/pull/11108/merge
Appeared in branch master
Nov 25, 2022
Commit f64e5cee
Fixed in branch master
Nov 25, 2022
@ jpakkane
Prepare release 0.61.0.
9e1f207
Reappeared in branch master
Nov 25, 2022
@ jpakkane
Prepare the 0.62.0 release.
fb67adf
unittests/baseplatformtests.py:208 on branch master
Fixed in branch master
Nov 25, 2022
@ jpakkane
Finalize the release.
9c6dab2
Reappeared in branch master
Nov 28, 2022
@ eli-schwartz
@ dcbaker
Add github's CodeQL scanner to CI.
5022fd3
unittests/baseplatformtests.py:219 on branch master
Fixed in branch master
Nov 28, 2022
@ jpakkane
Don't ignore documentation-related flags for D compilers
23fcea1
Reappeared in branch master
Nov 28, 2022
@ smallwood-d
@ duckflyer
@ jpakkane
Fix crash when toolchain is missing
d32ee58
unittests/baseplatformtests.py:219 on branch master
Appeared in branch refs/pull/11115/merge
Nov 28, 2022
CodeQL #19: Commit 38594dcd
Fixed in branch refs/pull/11115/merge
Nov 29, 2022
@ obilaniu
Merge https://github.com/mesonbuild/meson/commit/68da84fba3fd3ac0742352605d54b985c70c23c7 into https://github.com/mesonbuild/meson/commit/1a6a014494785e107023b25c157b30c3a4838b99
87ec9c6
Fixed in branch master
Nov 29, 2022
@ obilaniu
@ eli-schwartz
CUDA: Update minimum driver version table to include CUDA 11.8
6190b64
Appeared in branch refs/pull/9865/merge
Nov 29, 2022
CodeQL #29: Commit f12cd573
Fixed in branch refs/pull/11117/merge
Nov 30, 2022
@ eli-schwartz
Merge https://github.com/mesonbuild/meson/commit/67da2ad0fb3a0e45bd878d21aa1c5d956214c483 into https://github.com/mesonbuild/meson/commit/e8727fc8571bc8b9dc23255c267b52478d12e66f
ae66d91
Fixed in branch refs/pull/11119/merge
Nov 30, 2022
@ fooishbar
Merge https://github.com/mesonbuild/meson/commit/3393c818812317a0338755aa965ad2b03837e25d into https://github.com/mesonbuild/meson/commit/e8727fc8571bc8b9dc23255c267b52478d12e66f
3fb025b
Reappeared in branch refs/pull/11119/merge
Nov 30, 2022
@ fooishbar
Merge https://github.com/mesonbuild/meson/commit/1b98549c706aa11d4281105616c020903725a965 into https://github.com/mesonbuild/meson/commit/e8727fc8571bc8b9dc23255c267b52478d12e66f
237b096
unittests/baseplatformtests.py:219 on branch refs/pull/11119/merge
Reappeared in branch master
Nov 30, 2022
@ dcbaker
@ eli-schwartz
pylint: enable simplifiable-if-statement
67da2ad
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/11119/merge
Nov 30, 2022
@ fooishbar
Merge https://github.com/mesonbuild/meson/commit/aaebb1f45f7b12d31578b44624481f3cc395a4d7 into https://github.com/mesonbuild/meson/commit/67da2ad0fb3a0e45bd878d21aa1c5d956214c483
7f38298
Fixed in branch master
Nov 30, 2022
@ fooishbar
@ dcbaker
tests: Write out LD_LIBRARY_PATH for built shared libraries
a0514a7
Reappeared in branch master
Nov 30, 2022
@ eli-schwartz
docs: clarify that prog.full_path has potentially valid uses
dcc50b9
unittests/baseplatformtests.py:219 on branch master
Fixed in branch master
Nov 30, 2022
@ eli-schwartz
docs: clarify prog.full_path even more
fae24d8
Reappeared in branch master
Nov 30, 2022
@ sashashura
@ eli-schwartz
build: harden workflow permissions
9074ad9
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/11126/merge
Dec 1, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/617c3f6e64728712390071deb6d9be3c6a3af46c into https://github.com/mesonbuild/meson/commit/9074ad93c6675cdb603b85d85a8090100058f81b
a96c6ef
Reappeared in branch refs/pull/11126/merge
Dec 1, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/62dceecffc87812d3d76b7994bf852d92ea91a68 into https://github.com/mesonbuild/meson/commit/9074ad93c6675cdb603b85d85a8090100058f81b
3d33ea9
unittests/baseplatformtests.py:219 on branch refs/pull/11126/merge
Fixed in branch refs/pull/11127/merge
Dec 1, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/d804624a9c6ffe468174162d2395af3f04cc9cad into https://github.com/mesonbuild/meson/commit/9074ad93c6675cdb603b85d85a8090100058f81b
89a806e
Fixed in branch master
Dec 5, 2022
@ mchampanis
@ eli-schwartz
dependencies: only print not_found_message once
f194413
Reappeared in branch master
Dec 5, 2022
@ fanf2
@ eli-schwartz
docs: change old SourceForge link to GitHub
8a72558
unittests/baseplatformtests.py:219 on branch master
Fixed in branch master
Dec 5, 2022
@ wally-mageia
@ eli-schwartz
Use meson setup [options] in meson RPM macro
99dfc98
Reappeared in branch master
Dec 5, 2022
@ dcbaker
@ eli-schwartz
modules/rust: Add support for string include_directories
bb87528
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/10714/merge
Dec 5, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/12c91afd4f85980d41250192e05e6c1810820c36 into https://github.com/mesonbuild/meson/commit/bb875280b695b8d0435833c192f99233e74a522a
633906f
Reappeared in branch refs/pull/11127/merge
Dec 6, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/bb2a68a4c1285c8de19c70118d4fa745ec9e78af into https://github.com/mesonbuild/meson/commit/d0054f2c3c3497e22069d1efb5b1d985d75fe5ca
93ecaac
unittests/baseplatformtests.py:219 on branch refs/pull/11127/merge
Fixed in branch refs/pull/11127/merge
Dec 6, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/ef11b6c676d5789e168f09dc154ada510ef1a1d3 into https://github.com/mesonbuild/meson/commit/d0054f2c3c3497e22069d1efb5b1d985d75fe5ca
df25978
Fixed in branch master
Dec 6, 2022
@ szanni
@ xclaesse
docs: Add missing import to the windows module example.
cee7ecd
Fixed in branch refs/pull/11125/merge
Dec 6, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/9e36923c72eec7100dd7d7c7314cabadf18dd7b6 into https://github.com/mesonbuild/meson/commit/bcd50e71d51eac2fa8e1afbb30cb7d5260e0f42a
4a7a122
Reappeared in branch refs/pull/11125/merge
Dec 6, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/4d361287a06cfe3c7ba6eb09751d36c640f8ab9a into https://github.com/mesonbuild/meson/commit/bcd50e71d51eac2fa8e1afbb30cb7d5260e0f42a
4b95d05
unittests/baseplatformtests.py:219 on branch refs/pull/11125/merge
Reappeared in branch refs/pull/10714/merge
Dec 6, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/7c0053594359f347eab9b0384c354ce60fbd0b72 into https://github.com/mesonbuild/meson/commit/bcd50e71d51eac2fa8e1afbb30cb7d5260e0f42a
ac70545
unittests/baseplatformtests.py:219 on branch refs/pull/10714/merge
Fixed in branch refs/pull/10714/merge
Dec 6, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/d0a5eaa1ee94d4a678fd11166b7b577e5e2aa0e6 into https://github.com/mesonbuild/meson/commit/bcd50e71d51eac2fa8e1afbb30cb7d5260e0f42a
94fde44
Appeared in branch refs/pull/10990/merge
Dec 7, 2022
CodeQL #107: Commit b4efe3e5
Reappeared in branch refs/pull/10714/merge
Dec 7, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/3a56afdcacaf4fe5f0cca26b9e98230e602edb10 into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
6968b65
unittests/baseplatformtests.py:219 on branch refs/pull/10714/merge
Reappeared in branch refs/pull/11127/merge
Dec 7, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/068d5e1905fedf4752644fe64d9ed80a2a70e59d into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
df48ed4
unittests/baseplatformtests.py:219 on branch refs/pull/11127/merge
Fixed in branch refs/pull/11127/merge
Dec 7, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/dd7c9e234f66cdb87719a947febe415756433f29 into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
5230edf
Reappeared in branch refs/pull/11127/merge
Dec 7, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/24197c5869f8e40e25c2bea0d9b4d67612a1d21a into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
f81e38a
unittests/baseplatformtests.py:220 on branch refs/pull/11127/merge
Fixed in branch refs/pull/11127/merge
Dec 7, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/ce277753f92c8302db3f4b646bf5243a66764ab2 into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
22eb334
Fixed in branch refs/pull/11147/merge
Dec 8, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/f427aefb330c4d64f79a7c08bedbf11c80f60ec2 into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
2a937f8
Reappeared in branch refs/pull/11127/merge
Dec 9, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/14857472398efe3ec477225a7ea5f956885e0866 into https://github.com/mesonbuild/meson/commit/d490636328e78984af0b80c70a8217c4f9cf9c52
b8d265b
unittests/baseplatformtests.py:220 on branch refs/pull/11127/merge
Reappeared in branch master
Dec 9, 2022
@ eli-schwartz
@ jpakkane
python module: don't overwrite and destroy the .pc dependency name
7b2c47e
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/11150/merge
Dec 9, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/d63c0ba6e612012b97a83ef3e2cf17030297680b into https://github.com/mesonbuild/meson/commit/2ec3fe7a4af5bd4d8a83947d675f9233805f3dfd
05f2eca
Fixed in branch master
Dec 9, 2022
@ xclaesse
@ jpakkane
doc: Add date in release notes
17c0a7f
Appeared in branch refs/pull/11071/merge
Dec 9, 2022
CodeQL #139: Commit 20f15461
Fixed in branch refs/pull/11127/merge
Dec 10, 2022
@ amyspark
Merge https://github.com/mesonbuild/meson/commit/5de6a09428d4620b26d759cabc3e088264107fe1 into https://github.com/mesonbuild/meson/commit/17c0a7f76a3168cd568c33fbad2824da2d702764
bd07c59
Fixed in branch refs/pull/11071/merge
Dec 10, 2022
@ tristan957
Merge https://github.com/mesonbuild/meson/commit/679721e75659cef68b6582c54b63d54df64a75ff into https://github.com/mesonbuild/meson/commit/17c0a7f76a3168cd568c33fbad2824da2d702764
b3e39cb
Reappeared in branch master
Dec 10, 2022
@ jpakkane
Merge pull request https://github.com/mesonbuild/meson/pull/11024 from dcbaker/submit/bindgen-dependencies
dbb33aa
unittests/baseplatformtests.py:219 on branch master
Fixed in branch master
Dec 10, 2022
@ obilaniu
@ jpakkane
CUDA: Update compute-capability limits logic for CUDA 12.
255f335
Fixed in branch refs/pull/11144/merge
Dec 11, 2022
@ philj56
Merge https://github.com/mesonbuild/meson/commit/53fa268368bd19f094928c78a835990117735c77 into https://github.com/mesonbuild/meson/commit/255f335d8e305d4cad261484d5d3e0f80b82d886
8b5814e
Reappeared in branch refs/pull/11071/merge
Dec 11, 2022
@ tristan957
Merge https://github.com/mesonbuild/meson/commit/dfea023ced8b48b318826738f54328ea24ef63b3 into https://github.com/mesonbuild/meson/commit/5bea2ca198041fa044222dc5b8b63b155e525d5c
6cac840
unittests/baseplatformtests.py:219 on branch refs/pull/11071/merge
Appeared in branch refs/pull/11159/merge
Dec 11, 2022
CodeQL #158: Commit 30b9ec0b
Reappeared in branch refs/pull/11147/merge
Dec 12, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/69dafc0204b327a9ef9d4a2a94d27912528bab9e into https://github.com/mesonbuild/meson/commit/b249470a4c1de39a0a56d9237f767fe04d6efa05
79018af
unittests/baseplatformtests.py:219 on branch refs/pull/11147/merge
Fixed in branch refs/pull/11151/merge
Dec 13, 2022
@ brad0
Merge https://github.com/mesonbuild/meson/commit/7d452aa46c6bcd47966df75b98a5a7f7d849fcb2 into https://github.com/mesonbuild/meson/commit/b249470a4c1de39a0a56d9237f767fe04d6efa05
6696531
Appeared in branch refs/pull/11135/merge
Dec 14, 2022
CodeQL #174: Commit 5c4fa472
Appeared in branch refs/pull/11174/merge
Dec 14, 2022
CodeQL #176: Commit 8ad6105e
Fixed in branch refs/pull/11135/merge
Dec 14, 2022
@ bonktree
Merge https://github.com/mesonbuild/meson/commit/96f0ecac69459ae44a8b6b030ab7ac275c1700b7 into https://github.com/mesonbuild/meson/commit/dd25b88f009ee47579b33dfbd167a9434cc8f2be
6b93707
Fixed in branch refs/pull/11179/merge
Dec 14, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/66b6671852eca089832d4b4c3637a0fe7ce1536a into https://github.com/mesonbuild/meson/commit/dd25b88f009ee47579b33dfbd167a9434cc8f2be
55511a0
Reappeared in branch refs/pull/11179/merge
Dec 14, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/a4a38da4b427bb581379238875a5780a76ebb0b1 into https://github.com/mesonbuild/meson/commit/dd25b88f009ee47579b33dfbd167a9434cc8f2be
c0dbedb
unittests/baseplatformtests.py:219 on branch refs/pull/11179/merge
Fixed in branch refs/pull/11174/merge
Dec 14, 2022
@ bgilbert
Merge https://github.com/mesonbuild/meson/commit/35e230e48ca42f4ccb872d1d01f9280f8015b417 into https://github.com/mesonbuild/meson/commit/dd25b88f009ee47579b33dfbd167a9434cc8f2be
8740802
Appeared in branch refs/pull/10582/merge
Dec 14, 2022
CodeQL #185: Commit b60712a2
Fixed in branch refs/pull/10582/merge
Dec 14, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/0ff70e7b5f11796704258767da2c6ad876e56b98 into https://github.com/mesonbuild/meson/commit/dd25b88f009ee47579b33dfbd167a9434cc8f2be
b894bd8
Reappeared in branch master
Dec 14, 2022
@ eli-schwartz
docs: clarify the semantics of the required: kwarg everywhere
57f91bb
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/11175/merge
Dec 14, 2022
@ Akaricchi
Merge https://github.com/mesonbuild/meson/commit/4814a392963065abf02e9daf2af3a8aa3ba3fdc2 into https://github.com/mesonbuild/meson/commit/57f91bb593b9eebf772a16a5519de58996d27c3a
93a22c4
Reappeared in branch refs/pull/10582/merge
Dec 15, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/445fa1b6a2c347eca1aeb1756f88673aa6bc6224 into https://github.com/mesonbuild/meson/commit/57f91bb593b9eebf772a16a5519de58996d27c3a
2a1aed0
unittests/baseplatformtests.py:219 on branch refs/pull/10582/merge
Fixed in branch refs/pull/10582/merge
Dec 15, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/2922f8949b042b1ebf579e12c2bb3ce0cdee8445 into https://github.com/mesonbuild/meson/commit/57f91bb593b9eebf772a16a5519de58996d27c3a
f1c9a65
Fixed in branch refs/pull/11179/merge
Dec 15, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/58340a76a70aee98b9b73348ec6e8fb9ccd9f130 into https://github.com/mesonbuild/meson/commit/57f91bb593b9eebf772a16a5519de58996d27c3a
3f1bde8
Appeared in branch refs/pull/11181/merge
Dec 15, 2022
CodeQL #195: Commit a6aacab9
Fixed in branch refs/pull/11181/merge
Dec 15, 2022
@ tristan957
Merge https://github.com/mesonbuild/meson/commit/6ed5c8cd6d4aafbd4dda416f43294f13781d98ca into https://github.com/mesonbuild/meson/commit/57f91bb593b9eebf772a16a5519de58996d27c3a
2ae5f2d
Fixed in branch master
Dec 15, 2022
@ eli-schwartz
delay importing ctypes unless it is actually used
2ef94a7
Reappeared in branch refs/pull/11181/merge
Dec 15, 2022
@ tristan957
Merge https://github.com/mesonbuild/meson/commit/fb6fda385391ac5d030b4e642fc426ada5d80488 into https://github.com/mesonbuild/meson/commit/2ef94a71f8072567e39f22bfed7bcae0ca2038c2
9d120a5
unittests/baseplatformtests.py:219 on branch refs/pull/11181/merge
Fixed in branch refs/pull/11181/merge
Dec 15, 2022
@ tristan957
Merge https://github.com/mesonbuild/meson/commit/71cddebf2c6093fe52de01329847926801f87f35 into https://github.com/mesonbuild/meson/commit/2ef94a71f8072567e39f22bfed7bcae0ca2038c2
0d604df
Reappeared in branch master
Dec 16, 2022
@ jpakkane
Merge pull request https://github.com/mesonbuild/meson/pull/11174 from bgilbert/jar-manifest
27bd499
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/10714/merge
Dec 16, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/1b2216c500a9f18436d427ed74888e7740b62b55 into https://github.com/mesonbuild/meson/commit/27bd499772483c620bc0eca219edf2707de3dee6
25aeed2
Reappeared in branch refs/pull/10714/merge
Dec 16, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/1725e62fb4faa2a75b48aa4979efaa41baf5d8e8 into https://github.com/mesonbuild/meson/commit/27bd499772483c620bc0eca219edf2707de3dee6
68d9795
unittests/baseplatformtests.py:219 on branch refs/pull/10714/merge
Appeared in branch refs/pull/11188/merge
Dec 18, 2022
CodeQL #217: Commit 536499f1
Fixed in branch refs/pull/11188/merge
Dec 18, 2022
@ nirbheek
Merge https://github.com/mesonbuild/meson/commit/9fc425c4e3acb5766f9d2d138d0c725aff5dfa5e into https://github.com/mesonbuild/meson/commit/9c1b6a95b06db3d2a167251488a496465221300e
cfd48d6
Fixed in branch refs/pull/11197/merge
Dec 19, 2022
@ bonzini
Merge https://github.com/mesonbuild/meson/commit/34286929336b167fb0c6ab02497a345be7277347 into https://github.com/mesonbuild/meson/commit/9c1b6a95b06db3d2a167251488a496465221300e
14d36c1
Appeared in branch refs/pull/11198/merge
Dec 19, 2022
CodeQL #226: Commit 3bb01a78
Fixed in branch refs/pull/11198/merge
Dec 19, 2022
@ bonzini
Merge https://github.com/mesonbuild/meson/commit/d43d9c4a83cbd0cd313999492da9f0421f4dc4e9 into https://github.com/mesonbuild/meson/commit/9c1b6a95b06db3d2a167251488a496465221300e
8d3dfb0
Fixed in branch master
Dec 19, 2022
@ amitdo
@ eli-schwartz
Users.md: Add PostgreSQL
2e54f77
Appeared in branch refs/pull/11201/merge
Dec 21, 2022
CodeQL #235: Commit 99cbc837
Fixed in branch refs/pull/11203/merge
Dec 21, 2022
@ xclaesse
Merge https://github.com/mesonbuild/meson/commit/8f935e9673bcf6f58dd9c644c672da843d44298e into https://github.com/mesonbuild/meson/commit/2e54f772d396daf79c817aea6848fbb324aa0f59
d746d6d
Reappeared in branch master
Dec 21, 2022
@ xclaesse
@ eli-schwartz
doc: Add missing include_directories kwarg to compiler.preprocess()
a0b37a7
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/11207/merge
Dec 21, 2022
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/5ceed3f99e21a8498163ec1c740c83442397ecb9 into https://github.com/mesonbuild/meson/commit/99713ae257cae6f86b3b34ddf474a8cff247ea29
8108f68
Fixed in branch master
Dec 21, 2022
@ bonzini
@ dcbaker
add more testcases for prebuilt objects
b38bf09
Reappeared in branch master
Dec 23, 2022
@ jpakkane
Bump version number for new development.
8e2355e
unittests/baseplatformtests.py:219 on branch master
Fixed in branch master
Dec 24, 2022
@ dcbaker
interpreter: use static_lib's already calculated pic value
2fd5bd9
Fixed in branch refs/pull/11213/merge
Dec 25, 2022
@ bluca
Merge https://github.com/mesonbuild/meson/commit/b3ee443c2fc710cd51bc8cd697b1881eec9e8f9e into https://github.com/mesonbuild/meson/commit/2fd5bd934e0e6dd26ad8c326a156a710f912b335
0cd3b90
Reappeared in branch refs/pull/11213/merge
Dec 25, 2022
@ bluca
Merge https://github.com/mesonbuild/meson/commit/3385accc59fa67be4e8aa4fb2c3cc69cea5b05f3 into https://github.com/mesonbuild/meson/commit/2fd5bd934e0e6dd26ad8c326a156a710f912b335
16465e7
unittests/baseplatformtests.py:219 on branch refs/pull/11213/merge
Fixed in branch refs/pull/11213/merge
Dec 26, 2022
@ bluca
Merge https://github.com/mesonbuild/meson/commit/f0f17012120d3fda0bfb71ef72986668a182c1c0 into https://github.com/mesonbuild/meson/commit/2fd5bd934e0e6dd26ad8c326a156a710f912b335
6563bdc
Reappeared in branch master
Dec 26, 2022
@ eli-schwartz
dependencies: better logging of pkg-config call outputs
891b4ff
unittests/baseplatformtests.py:219 on branch master
Appeared in branch refs/pull/11164/merge
Dec 26, 2022
CodeQL #267: Commit 42758023

Thanks for the detailed report, and for your patience -- we have limited support coverage during this holiday period, and I'm just catching up with this particular issue.
I had a brief look at the data from recent code scanning runs on your repo. I suspect the problem you observed occurred during the rollout of CodeQL 2.11.4 in the tool cache in the default Actions runner image. Some runs on this repo obtained CodeQL 2.11.3, and some runs obtained CodeQL 2.11.4, which in turn can lead to the spurious opening and closing of alerts due to differences in analysis between those versions.
We are aware of this problem in general, and it is a high-priority item for us to fix at the start of the new year, ensuring that your alerts are stable even when a new CodeQL version is being rolled out. Until then please accept my apologies for the inconvenience -- we know how disruptive it can be to have your alerts close and reopen in this way.
As a temporary workaround, you can set tools: latest in the with: section of the codeql-action/init@v2 step in your workflow, which will bypass the cache and always download the latest version of CodeQL. This will give you more consistency in the CodeQL version being used across workflow runs, at the cost of an extra ~1min in each run. (If it is inconvenient to modify the workflow, we can temporarily enable the same behaviour for you on the GitHub server side. Let us know if you prefer that.)
Please let us know in case you are still observing the problem with the above workaround. I'll leave this issue open until we have completed and rolled out the fix I mentioned so that you can avoid the workaround.

Thanks for the advice. I've just deployed this change in https://github.com/mesonbuild/meson/commit/334d2137e9b224a655007b0b7c328e1c95320027 and I'll report back.

I still see this issue, see for example https://github.com/mesonbuild/meson/runs/10493109542
The matching analyze job: https://github.com/mesonbuild/meson/actions/runs/3859141415/jobs/6578397228#step:3:12
Fixed in branch master
Jan 4, 2023
@ andy5995
@ eli-schwartz
Users.md: add slapt-get
25e73b6
Reappeared in branch master
Jan 8, 2023
@ eli-schwartz
@ xclaesse
avoid detecting masm as a MSVC-like compiler for detecting showincludes
b9b27d3
unittests/baseplatformtests.py:219 on branch master
Fixed in branch refs/pull/11243/merge
Jan 9, 2023
@ jackwil1
Merge https://github.com/mesonbuild/meson/commit/e787f9e180f8fffd86e5e716e1fd6a50eaab8c55 into https://github.com/mesonbuild/meson/commit/cb20486f37c0dfce60e541e512d2ceaa6e0b701e
7ec4236
Appeared in branch refs/pull/11268/merge
Jan 9, 2023
CodeQL #348: Commit 31cf1102
Fixed in branch refs/pull/11268/merge
Jan 9, 2023
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/e966d48653c6c145c0238577e9e3dbce6d92b76d into https://github.com/mesonbuild/meson/commit/ded57707c8196eda2fcf7ea507e7e2b38f9a7d19
b5ff4f8
Reappeared in branch refs/pull/11268/merge
Jan 9, 2023
@ dcbaker
Merge https://github.com/mesonbuild/meson/commit/e04c3a0232219b2f2efa67f515ebd4fbcb1c2fa3 into https://github.com/mesonbuild/meson/commit/ded57707c8196eda2fcf7ea507e7e2b38f9a7d19
d73cdfb
unittests/baseplatformtests.py:219 on branch refs/pull/11268/merge
Fixed in branch master
Jan 10, 2023
@ dcbaker
modules: fully type the Qt* modules
6ed6c8c
Reappeared in branch master
Jan 10, 2023
@ dcbaker
@ eli-schwartz
docs: Add ld64.lld to linker reference table
8655287
unittests/baseplatformtests.py:219 on branch master
Appeared in branch refs/pull/11273/merge
Jan 10, 2023
CodeQL #360: Commit cad75877


Update signPetition() action to submit signatures to API

Note: API for this doesn't yet exist, but let's assume for now it's a POST request to petitions/${petitionSlug}/signatures

This commit POSTs to the current api 4430a875
(not the api path in the issue (petitions/:slug/signatures), which I don't think we should do, since we need an independent route which can go directly to the SQS queue (rather than elegantly be part of a predictable RESTful api -- but I think it's worth it)


Maximum number of concurrent chat discussions

Duo Money is looking to have hundreds of concurrent encrypted chat discussions with buyers. How many concurrent encrypted chat discussions can the client handle?

Do you mean in a performance type of way?

I mean from a feasibility point of view. Can a single node realistically handle hundreds of concurrent discussions within the reference client? I expect large eBay stores have many concurrent discussions with their buyers, and wondered if OpenBazaar is designing the encrypted chat UI for these large sellers.
Things that from the top of my head could break when there are hundreds of chats:

Bad performance
Hardcoded maximum number of chat discussions
The chats become unwieldy to navigate when there are too many, because they need to be manually scrolled through

We can probably test that fairly easily.

From purely an interface point of view, I've designed Chat so that you can safely manage about 10 concurrent conversations at a given time. Anything beyond 10 active conversations typically is unmanageable by a single person anyways and will require a team of customer service reps to distribute the load to.
There are limitations within the reference client. We simply cannot build one app to solve every problem for every user, but this creates amazing opportunities for 3rd party tools to emerge to make managing customer service easier for mid to large size stores. intercom.io for example does exactly this for traditional eCommerce stores and they employe 200+ people to solve these types of problems.

At some point a dedicated view for chat conversations will probably be necessary and we have discussed this before.

Agreed, it could be useful. However, having a dedicated Chat view doesn't solve the distribution problems for mid to large size businesses though. If you have hundreds of inbound messages coming in every few minutes, you need many people to distribute the load to, a single person can't keep up with it. Simply adding a dedicated view doesn't solve any of the underlying problems for big businesses. They'll need user roles, ticketing, volume distribution, reporting, etc. It's not trivial.

@JustinDrake This should be answered.


nix-darwin uninstalls nix-homebrew taps

Even when I used autoMigrate = true in nix-homebrew, brew bundle (with the Brewfile generated by nix-darwin's homebrew module) kept trying to uninstall my immutable taps. This obviously failed:
Homebrew Bundle complete! 46 Brewfile dependencies now installed.
Untapping homebrew/cask...
Error: Permission denied @ apply2files - /opt/homebrew/Library/Taps/homebrew/homebrew-cask

To fix this in my config, I added
homebrew.taps = map (key: builtins.replaceStrings ["homebrew-"] [""] key) (builtins.attrNames config.nix-homebrew.taps)

to get a list of taps that I provided to nix-homebrew and make sure nix-darwin keeps them installed. Could nix-darwin set this automatically?

Someone had the same issue with a similar fix here: https://github.com/zhaofengli/nix-homebrew/issues/5#issuecomment-1878798641.


Design Data Input and Processing Modules

Designs based on values calculated from OpenCV and MediaPipe objects and functions.
Projected Objects Documentation:

OpenCV VideoCapture
MediaPipe : TBD

Designs may change over time.

Merging on Wednesday, Nov 15 pending any outstanding conversations.


Add partitioned tables in the schema cache

WIP

[x] Changelog
[x] Embedding documentation

@laurenceisla http://www.egull.co keeps failing linkcheck, maybe just comment the line for now.


preview: QtPreview: Copy source to a temporary line buffer for speed

This simple change reduces viewfinder CPU-per-frame by a factor of at least 2 (tested on both ARM32 and ARM64).
Though where preview rate was limited by CPU it might not actually reduce total cycles (but might improve frame rate).
This reduces the benefit of the previous "U,V sharing" optimization, but the latter has been retained, to reduce code churn.
Further optimizations such as vectorizing the YUV->RGB conversion in signed 16-bit (rather than float) would yield diminishing returns and are not planned. If we really wanted further speedup we should arrange for a correctly-sized RGB888 source image!

@naushir was looking at whether using allocations from the /dev/dma_heap/linux,cma dma heap gave the benefits desired (namely CPU cached memory) without jumping through the hoops of copying the data manually.
He'd made comment that it was relatively straightforward, but I know little more (we already jump through hoops allocating the buffers with REQ_BUFS, export them all, REQBUFS(0), and then switch to DMABUF import mode).

Yes. The benefit may depend on how the pixels are accessed. If visited few times per inner loop it might be better to keep it out of the cache (to avoid evicting other stuff) -- unless ARM can detect that it's being "streamed" and magically confine it to a small part of the cache?
x264 (for example) seems to do a global copy of each incoming frame. I'm not sure if that's essential (due to stride/padding requirements?) or if it can be bypassed; in the latter case a cacheable buffer would make a lot of sense.
A H/W codec that didn't overwrite its source buffers would presumably not care if the buffers were cacheable, provided they were never dirty -- we might want to specify writethrough?

I think this is worth putting in now until we get the dma heap framebuffer allocations work in.


Use Dagger 2 in one module

Is your feature request related to a problem? Please describe.
We can add Dagger 2 to one module to show how other developers how you can use it especially in a multi module application.
Describe the solution you'd like
Implement Dagger 2 in one module.
Additional context
Dagger Basics Tutorial
Dagger Codelab
Benchmarks Comparing the different DI solutions available

You are the master here

Also lets have one module without DI, for those who simply want to see the architecture and modules without DI.


[DOCFIX]Update docs/cn/Running-Hive-with-Alluxio.md

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17451/
Test PASSed.


Browser Tab does not work

Known issue--it hasn't been implemented. We are working on it here: https://github.com/OpenDevin/OpenDevin/pull/547
Existing issue: https://github.com/OpenDevin/OpenDevin/issues/138


Inconsistent output between ListArray.flatten() and ChunkedArray.flatten() with struct type

Summary
ListArray.flatten and FixedSizeListArray.flatten return an array of its values, sliced with offsets of the parent array.
When the same array is wrapped into a ChunkedArray, and the array type is StructArray the output is a chunked array of the parent array. In other words, ChunkedArray.flatten returns the array itself, instead of its values
Environment
Observed on Windows 10
python=3.11.2
pyarrow=11.0.0
Details
import pyarrow as pa

array = pa.array([
    [{'a': 5}, {'a': 6}],
    [{'a': 7}]
])

# same array wrapped in a ChunkedArray
array_chunked = pa.chunked_array([array])

Now let's flatten each of these two arrays.
Output of array.flatten()
<pyarrow.lib.StructArray object at 0x000001DAA018D8A0>
-- is_valid: all not null
-- child 0 type: int64
  [
    5,
    6,
    7
  ]

Output of array_chunked.flatten()
[<pyarrow.lib.ChunkedArray object at 0x000001DAAE852A20>
 [
   [
     -- is_valid: all not null
     -- child 0 type: int64
       [
         5,
         6
       ],
     -- is_valid: all not null
     -- child 0 type: int64
       [
         7
       ]
   ]
 ]]

In other words, the first chunk of the flattened chunked array is equal to the original array, which should not happen
assert not array.equals(array_chunked.flatten()[0].chunk(0))  # AssertionError

This issue is observed with FixedSizeListArray as well
array = pa.array([[{'a': 5}], [{'a': 7}]],
                 type=pa.list_(pa.struct([('a', pa.int32())]), list_size=1))
array_chunked = pa.chunked_array([array])
assert not arr.equals(carr.flatten()[0].chunk(0))  # AssertionError

Expected behavior:
Flattened chunked array is expected to be a chunked array wrapping values of the original array, which is a StructArray
Component(s)
Python

This is actually expected behavior - although your assumption here isn't unwarranted since there's some unfortunate naming at play.
Basically, flatten has two different meanings depending on whether we're dealing with a ListArray or StructArray... For the former, the list values get concatenated into a single array like you mentioned. For the latter, "flattening" a struct means returning each of its child fields as a separate array. ChunkedArray's flatten method strictly mirrors the StructArray version - so, since the underlying type isn't a struct, it will just return the ListArray chunks as-is.
Note that the original array's list types should be irrelevant here - e.g. flattening a chunked array of list<int64> should also yield a single chunked array of list<int64> (just like with list<struct<a: int64>>).
If you're suggesting that we modify ChunkedArray::flatten to handle lists differently than structs then I don't disagree in principle, although I suspect adding an independent method that does what you've described would be more appropriate.


Use "GitHub" over "Github"

It seems the automation checks text content identical, and I found my typo fixing on the generated "release.yml" cause pipeline to fail:
https://github.com/korandoru/hawkeye/actions/runs/8460335170/job/23178340096?pr=133
Hopefully it should be fixed in a template file in this repo. But I don't know which one is the template. I'm willing to send a patch to fix it if it's desired.

Thanks for offering to fix it! The template is here: https://github.com/axodotdev/cargo-dist/blob/main/cargo-dist/templates/ci/github_ci.yml.j2

Patch sent - https://github.com/axodotdev/cargo-dist/pull/886
BTW, I found the skipped job has an unresolved name, is it possible to improve?

Actually, I don't check carefully the generated workflow but give it a fire to see first 🤣


pip check support in pip

Hello,
This PR adds pip check support in PipPackage module.

Verify installed packages have compatible dependencies.

Best

The error is test_ssh_service on py36 / alpine, seems not related to this PR.

Merged, thanks!


security: update dependencies mkdirp, yargs and yargs-parser

Description of the Change

mkdirp: prototype pollution by minimist => update to<EMAIL_ADDRESS>yargs-parser: prototype pollution => update to<EMAIL_ADDRESS>yargs: update to<EMAIL_ADDRESS>

Coverage remained the same at 92.804% when pulling 69ea2b0de10ad304be0cef87d9097ef6466fae3f on juergba/security into 2f264784d22277efa99244a8615ce2a1830b2d3c on master.


chore(localizations): Update Turkish localization according to the latest en-US

Description
I translated all of the remaining English values into Turkish and improved some of the existing translations.

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[X] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Thank you for contributing! 🙏


Mod doesn't work in server instances.

What's the issue?
Server instances with Camerapture installed crash on startup.
I'm using fabric-server-mc.1.20.1-loader.0.16.9-launcher.1.0.1.jar with no extra arguments (other than -Xmx), and openjdk-17-jre.
latest.log
(no crash report generated)
What loader are you using?
Fabric
What is your Minecraft version?
1.20.1
What is Camerapture's version?
Camerapture 1.7.1

Oops, small oversight by me! Should be fixed in the next version!


Remove @nft/templates library

Project organization

Dependant on https://github.com/liteflow-labs/liteflow-js/pull/90

Description
Remove the templates library as this is being merged into the https://github.com/liteflow-labs/marketplace-template/pull/45
How to test
Build the libraries and link them to the template then check that all pages are working as expected
Note that the failed deployment is normal as the storybook has been removed for templates
Checklist

[x] Update related changelogs
[x] Update docs if necessary

seems ok to me. are we going to help out the customers to move the templates to their apps?


WhatsApp does not load in 5.5.0-gm

Describe the bug
WhatsApp service only blinks "WhatsApp works only with Google Chrome 49+" in endless loop. With 5.4.3 there is no such issue.
To Reproduce

Steps to reproduce the behavior:

Install 5.5.0-gm on MacOS
Run Ferdi
Open WhatsApp service

Expected behavior
WhatsApp loads properly like in 5.4.3.
Screenshots

https://youtu.be/LdUtIxV9i_I
Desktop:

OS: MacOS 10.15.4
Ferdi Version 5.5.0-gm

Server Used: https://api.getferdi.com

Debug information: https://debug.getferdi.com/35dd02af-1e79-4c25-b2ac-a8d0277aecea

Seems to be (again) a user agent problem.
find .../Ferdi/recipes/whatsapp/index.js and replace like this:
`
"use strict";
module.exports = Franz => class Messenger extends Franz {
overrideUserAgent() {
//return window.navigator.userAgent.replace(/(Franz|Electron)([^\s]+\s)/g, '');
return "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.113 Safari/537.36";
}
};
`
not a perfect fix but hotfixed it for me.
restart ferdi to see effect

Confirm that. After simple upgrade from previous version both Whatsapp services stopped working.

@mokipedia We have identified the issue, working on it (see https://github.com/getferdi/ferdi/issues/536#issuecomment-616093384)! 🙏
Thank you for your patience.


Fixed formatting of panic data to suport strings

This change is

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-0.4.0-rc6@78352fb). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##             release-0.4.0-rc6    #1064   +/-   ##
====================================================
  Coverage                     ?   79.25%
====================================================
  Files                        ?       35
  Lines                        ?     5327
  Branches                     ?     5327
====================================================
  Hits                         ?     4222
  Misses                       ?      734
  Partials                     ?      371

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Ruller position is +1 from my expectation

#3233
Multiple rulers work great and look great.
However, when I configure a set of rulers e.g. [20,40,90,140] I expected the ruler to land on that column not the one after that.  This could be by design but I found it a little confusing as I wanted to know that once I reached the ruler I had hit column 20 vs 21.

Seems to behave the same as Atom's default wrap-editor as well as the community-based multi-wrap-editor.

@seanmcbreen
I think a ruler at 20 should help me keep my lines <=20 characters, therefore its positioning after the specified column.


there can be use of express js on your website

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

not for now. thank you


cannot compile "cp: cannot stat 'build/rose': No such file or directory"

OS: artixlinux with runit
error message:
$ sudo GTK=4 BUILDTYPE=RELEASE make install
cp -f build/rose /mcc
cp: cannot stat 'build/rose': No such file or directory
make: *** [makefile:32: install] Error 1

I am still having this problem with the latest commit.  Also is the project still being maintained? The AUR packaged is old and orphaned. Love the project, a star from me!


Fixing Microprofile test suites (temporary adding javax.servlet dependency and downgrading to Jetty 9)

Fixing Microprofile test suites (temporary adding javax.servlet dependency and downgrading to Jetty 9), @jimma it may help you with https://issues.apache.org/jira/browse/CXF-8781

@reta From the CI result, there are still some test failures under  cxf-systests-microprofile-async and cxf-systests-microprofile-nocdi caused by  java.lang.ClassNotFoundException: javax.json.JsonException
The wiremock or wiremock-standalone dependency should both work for test scope ,  but it seems it needs to add more javax dependencies for wiremock dependency.
For cxf-systests-microprofile-weld, I did the similar change in weld module to get more tests passed yesterday , but there are still some failures I still need to have a look: https://github.com/apache/cxf/pull/1018/commits/94ce0543f4167d75dc2c9352b124e8358aec72be.
And the latest CI shows there are 23 failures(in my branch) to fix : https://ci-builds.apache.org/job/CXF/job/CXF-JDK17-PR/110/. Do you have an idea what I need to have a look ?

Thanks @jimma

The wiremock or wiremock-standalone dependency should both work for test scope , but it seems it needs to add more javax dependencies for wiremock dependency.

I tried to fix that but went into rabbit hole of dependency mess, probably we need to wait for wiremock to catch up ...

Do you have an idea what I need to have a look ?

I haven't yet into the failures yet, but I will help you out on https://github.com/apache/cxf/pull/1018

Thanks @jimma

The wiremock or wiremock-standalone dependency should both work for test scope , but it seems it needs to add more javax dependencies for wiremock dependency.

I tried to fix that but went into rabbit hole of dependency mess, probably we need to wait for wiremock to catch up ...

+1, now adding wiremock-standalone seems a bit easier and it doesn't need to add much other dependencies.  This will make it easier too when we replace the wiremock-standalone with the new wiremock release.

Do you have an idea what I need to have a look ?

I haven't yet into the failures yet, but I will help you out on #1018

Thanks @reta.  Let's discuss there.


Blank 'name' field from Restaurant search

@bubsinthemountains
The name field comes through as blank sometimes. Seems like it is happening when I pick a restaurant with a name that starts with digits, but that could be a coincidence.  The issue can be reproduced by searching with the zip code 80516 and selecting 24 Carrot Bistro as the restaurant.

fixed!


spec.subnetIDs empty after adoption of CacheSubnetGroup

Describe the bug
Similar to https://github.com/aws-controllers-k8s/community/issues/1389, the spec.subnetIDs: Required value error is encountered when an existing resource of type CacheSubnetGroup is adopted.
Steps to reproduce

Create a basic CacheSubnetGroup configured with some dummy subnet ids.
Adopt the resource via the AdoptedResource resource.
The following error pops up in the status of the AdoptedResource:

Status:
  Conditions:
    Message:  CacheSubnetGroup.elasticache.services.k8s.aws "{AWS_RESOURCE_NAME}" is invalid: spec.subnetIDs: Required value
    Status:   False
    Type:     ACK.Adopted

Expected outcome
Following the error CacheSubnetGroup resource is not created by the AdoptedResource. I expect the respective CacheSubnetGroup to be created and that the adoption is executed with success.
Environment

Kubernetes version 1.23
Using EKS (yes/no), if so version? yes
AWS service targeted (S3, RDS, etc.) elasticache

Hi @mustafasencer did the fixes you sent work for both the normal creation path and the adoption path? if yes we could make a new release for elasticache :)

@A-Hilaly Yeah, both normal and adoption paths are working. That is a great news 🚀

That's awesome news! Thank you @mustafasencer.
Sending a release PR soon

/close


Ethereum private key incorrect

Continuing from https://github.com/iancoleman/bip39/issues/395#issuecomment-578420534

I get the expected ETH address in standalone (without any Chrome or Brave issues) from my 12 word seed but it's giving me an incorrect private key

My manual tests (abandon abandon ability m/44'/60'/0'/0/0) give
0.3.11
Address 0xe5815d
Public Key 0x03e723e
Private Key 0x8f253078
0.4.0
Address 0xe5815d
Public Key 0x03e723e
Private Key 0xL21y1q
Private key is not matching.
To do:

Find reason for change in private key and fix
Change network tests to check all table values, not just address

It's using the bitcoin privkey WIF string instead of the ethereum hex encoded privkey.
Need to change
https://github.com/iancoleman/bip39/blob/927450e169e15e31b8f402c78a016cac47fc582d/src/js/index.js#L1137
to
privkey = libs.ethUtil.bufferToHex(keyPair.d.toBuffer())
I'll add this change and release asap (once the tests are all updated, a lot of extra test data to add so will take some time).
Thanks for bringing this to my attention @pieman64 and @PaulUD

Cheers @iancoleman

See https://github.com/iancoleman/bip39/commit/dd496c82c10ddd9612c80c70b4a21e05f2720624
Fix released in 0.4.2

Thank you. As of my understanding, anyone who would have generated a seed within 0.3.11 could have used it without any problems on Ledger / Trezor, but if he tried exporting private keys through the tool, he would have freaked out because of the messed up private key?
BR.

@spyhandler almost. 0.3.14 was fine.


Update BCR benchmark to Catalyst and MT

I had to move the BCR benchmark to a new project environment (and hence made a new folder) as I wasn't able to get the Project.toml updated to use Catalyst (I was encountering dependency misery, with incompatible errors that I couldn't decipher). I suspect the errors were related to the geometric integrators package, perhaps due to it restricting the available polynomials.jl versions.
I haven't managed to run the benchmark to completion locally yet; just building the sparse and dense Jacobians with MT takes on the order of 30-60 minutes each. Hopefully it can go through on the server ok.

FWIW I let the generated script from the benchmark Weave file run overnight and got the following timings (this may not include compilation time for everything as some commands had previously run I think). This seems to work ok, so assuming everything will be re-run / generated on the benchmark server this should be ok to merge.
 ────────────────────────────────────────────────────────────────────────────
                                     Time                   Allocations
                             ──────────────────────   ───────────────────────
      Tot / % measured:           6111s / 98.7%           2214GiB / 100%

 Section             ncalls     time   %tot     avg     alloc   %tot      avg
 ────────────────────────────────────────────────────────────────────────────
 ODEProb DenseJac         1    3572s  59.2%   3572s   1246GiB  56.4%  1246GiB
 ODEProb SparseJac        1    2264s  37.6%   2264s    941GiB  42.6%   941GiB
 SparseJac Eval1          1    58.1s  0.96%   58.1s   3.61GiB  0.16%  3.61GiB
 DenseJac Eval1           1    58.1s  0.96%   58.1s   3.61GiB  0.16%  3.61GiB
 ODERHS Eval1             1    39.5s  0.66%   39.5s   3.52GiB  0.16%  3.52GiB
 ODEProb No Jac           1    33.9s  0.56%   33.9s   9.78GiB  0.44%  9.78GiB
 Parse Network            1    3.17s  0.05%   3.17s    436MiB  0.02%   436MiB
 Create ODESys            1    323ms  0.01%   323ms   44.6MiB  0.00%  44.6MiB
 DenseJac Eval2           1    888μs  0.00%   888μs      224B  0.00%     224B
 SparseJac Eval2          1    805μs  0.00%   805μs      256B  0.00%     256B
 ODERHS Eval2             1   88.3μs  0.00%  88.3μs      192B  0.00%     192B
 ────────────────────────────────────────────────────────────────────────────

FWIW I let the generated script from the benchmark Weave file run overnight and got the following timings (this may not include compilation time for everything as some commands had previously run I think). This seems to work ok, so assuming everything will be re-run / generated on the benchmark server this should be ok to merge.
 ────────────────────────────────────────────────────────────────────────────
                                     Time                   Allocations
                             ──────────────────────   ───────────────────────
      Tot / % measured:           6111s / 98.7%           2214GiB / 100%

 Section             ncalls     time   %tot     avg     alloc   %tot      avg
 ────────────────────────────────────────────────────────────────────────────
 ODEProb DenseJac         1    3572s  59.2%   3572s   1246GiB  56.4%  1246GiB
 ODEProb SparseJac        1    2264s  37.6%   2264s    941GiB  42.6%   941GiB
 SparseJac Eval1          1    58.1s  0.96%   58.1s   3.61GiB  0.16%  3.61GiB
 DenseJac Eval1           1    58.1s  0.96%   58.1s   3.61GiB  0.16%  3.61GiB
 ODERHS Eval1             1    39.5s  0.66%   39.5s   3.52GiB  0.16%  3.52GiB
 ODEProb No Jac           1    33.9s  0.56%   33.9s   9.78GiB  0.44%  9.78GiB
 Parse Network            1    3.17s  0.05%   3.17s    436MiB  0.02%   436MiB
 Create ODESys            1    323ms  0.01%   323ms   44.6MiB  0.00%  44.6MiB
 DenseJac Eval2           1    888μs  0.00%   888μs      224B  0.00%     224B
 SparseJac Eval2          1    805μs  0.00%   805μs      256B  0.00%     256B
 ODERHS Eval2             1   88.3μs  0.00%  88.3μs      192B  0.00%     192B
 ────────────────────────────────────────────────────────────────────────────

Sparse convergence plot:

Sparse convergence plot:

@shashi This is probably the BCR script to use for testing going forward. Just activate the project.toml for the Bio folder and should be good to go.

@shashi This is probably the BCR script to use for testing going forward. Just activate the project.toml for the Bio folder and should be good to go.

Cool! Btw what's the link to the page with the results, the one in the README is now broken.

Cool! Btw what's the link to the page with the results, the one in the README is now broken.

The benchmark needs to be run on the benchmarking server to generate the new html page and such. Then I’ll update the readme with the new link.

The benchmark needs to be run on the benchmarking server to generate the new html page and such. Then I’ll update the readme with the new link.


Xcode 11.1. Undefined symbols for architecture x86_64

What did you do?
running unit tests
What did you expect to happen?
host app compiles fine, so the same is expected for unit tests target
What actually happened instead?
I got error
Undefined symbols for architecture x86_64:   "SwiftyJSON.JSON.init(Any) -> SwiftyJSON.JSON", referenced from:       MainTests.GroupTests.testFunc() -> () in Tests.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
Environment
List the software versions you're using:

SwiftyJSON (5.0.0)
Xcode Version: 11.1
Swift Version: Xcode Default

Please also mention which package manager you used and its version. Delete the
other package managers in this list:

Cocoapods: 1.7.5

Did you find the answer?


Running in Jupyter notebook / lab / other

The purpose of this issue is to get an idea of what's needed for Flexx to run inside environments like the notebook, JupyterLab, and other. What special measures does Flexx need to take, and what does Flexx need to know. Some things are already in place, but there are some loose ends.
Flexx needs to be made aware of certain aspects of the environment that it runs in. Sometimes its ok if the user provides this information (e.g. via app.init_notebook()), but the more we can automate, the better. If the server is aware of something, its easy to make the client aware too. The reverse is less true (the server might need the information before a connection is made).
I split this up aspects related to notebooks and Phosphor.
General
Since Flexx is embedded as part of an existing web page/app, there is no concept of a "Flexx app", and therefore must make use of the default session. E.g. app.init_notebook() takes care of this.
Notebooks
Notebooks can run in:

The Jupyer notebook (which does not have Phosphor loaded).
The notebook widget in JLab (Phosphor is loaded).
Something else?
In all cases, its a notebook that can be exported to HTML. For this reason, Flexx must always embed its own phosphor-all.js and phosphor-all.css for the exported notebook to work.

What Flexx needs to be able to detect:

Server and client need to know whether its running in a notebook. This is set by app.init_notebook().
Client needs to know whether its running in an exported notebook. We now try to detect this by looking for the presence of window.IPython.foo.bar and window.jupyter.lab. This seems fragile though.

Phosphor
If Flexx is loaded in an environment that already uses Phosphor, Flexx should probably use that version. This is a problem we're now facing with integrating Flexx with JLab, but could be an issue in general, especially if Phosphor gets more widely adopted.
For the JavaScript, Flexx ships its own phosphor-all.js in an AMD module. In one way or another, we can make Flexx make use of the available library instead of its own. For the CSS, Flexx ships its own phosphor-al.js (i.e. phosphor/styles/base.css). Fortunately, we can set this style DOM element to disabled if we know that Phosphor is already loaded.
How to determine if Phosphor is already loaded:

Check the presence of window.jupyter.lab. Works in JLab, but is not a generic solution.
Phosphor could set a global (and also report its version), e.g. window.phosphor_version.

How to let Flexx reach the Phosphor lib:

JLab (the Flexx-plugin) can provide hooks.
A more generic solution?

Versioning: if the version of the available Phosphor is incompatible with the version that Flexx is using, things will break. We can:

Do nothing: hope that the versions are compatible enough.
Warn if versions mismatch, but just try on a mismatch.
Error if versions mismatch.
Let Flexx use its own version version (on a version mismatch).

Multiple Flexx "instances"
In JLab you can run multiple notebooks at the same time. Also, eventually we might have some plugins in JLab based on Flexx, while a user can use Flexx in a notebook. As it is now, things will break hard when this happens. Module names, class definitions, and instance id's...

You could mirror the matplotlib approach? By default matplotlib just opens in new windows, even from an notebook, unless you apply the %matplotlib notebook magic to a notebook cell.

Yeah, I guess that's equivalent to calling app.init_notebook(). But from that point on, there are still plenty of difficulties :)

Client needs to know whether its running in an exported notebook. We now try to detect this by looking for the presence of window.IPython.foo.bar and window.jupyter.lab. This seems fragile though.

You could create an endpoint on the server to test if it's available. The client can then try to connect to it, assuming that it's in an exported notebook, if the connection fails and app.init_notebook() was called.

Found a solution for detecting whether the notebook is exported by setting a flag that does not end up in the exported html.

Industry best practices recommend feature detection; just try to make use of [Phosphor], and if you can't, assume it's not loaded.

But how? Phosphor might be packaged with WebPack, an AMD module, a global ...  and if its in WebPack, there is no way to load it unless there is a hook.

Multiple Flexx "instances"

Make flexx.app instance-based rather than a global. :) That could tie in with #238

Flexx can already severe multiple apps and sessions from the same process. What I mean here is one client that is connected to multiple Flexx servers. The problem is the global window.flexx.

But how? Phosphor might be packaged with WebPack, an AMD module, a global ... and if its in WebPack, there is no way to load it unless there is a hook.

Touché, I am still more used to the old school world of script tags on a .html file...

Flexx can already severe multiple apps and sessions from the same process. What I mean here is one client that is connected to multiple Flexx servers. The problem is the global window.flexx.

Right, so the client needs to be aware of multiple servers... that'll get hairy very quickly.


Win7 32 bit python3.5.4 how to install pyrealsense2?

Does it have to be python3.6？

Hi chaojizhangdaxin,
Have you tried python3.5.4, any issues? Or if it would be an option for you to upgrade to 3.6?
Thanks!

@chaojizhangdaxin Any update about this ticket? Looking forward to your reply. Thanks!

@chaojizhangdaxin Could you please update? Thanks!


Include QString

Adds #include <QString> to all files which use QString.
Addresses @clalancette's comment here. The linter's "include what you use" rule does not work on this header. Probably other QT headers as well, but this is the most common.

Pulls: ros2/rviz#1298
Gist: https://gist.githubusercontent.com/ahcorde/1453a997533c1caec0186b8c578031a6/raw/88b5b66f9df531bcbe781bc48d285e773327c393/ros2.repos
BUILD args:   --packages-above-and-dependencies rviz_common rviz_default_plugins rviz_visual_testing_framework rviz_rendering --packages-above-and-dependencies rviz_common rviz_default_plugins rviz_visual_testing_framework rviz_rendering
TEST args:  --packages-above rviz_common rviz_default_plugins rviz_visual_testing_framework rviz_rendering --packages-above rviz_common rviz_default_plugins rviz_visual_testing_framework rviz_rendering
ROS Distro: rolling
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/14812

Linux
Linux-aarch64
Linux-rhel
Windows


Virtio-Net driver is not respecting VIRTIO_NET_F_MRG_RXBUF

If a Virtio-Net PCI function (Device) does not advertise the VIRTIO_NET_F_MRG_RXBUF then the driver must supply a single descriptor RX buffer large enough to contain the virtio_net_hdr and the RX packet contents.
The Windows driver does not do this, it supplies a two descriptor buffer, one for the virtio_net_hdr and another for the packet contents, this behavior is explicitly prohibited by the specification.

Related:

https://github.com/virtio-win/kvm-guest-drivers-windows/pull/1089
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/1078

I think this is an unfortunate remnant of the support for the pre-1.0 virtio spec.

Probably was broken long time ago. Probably the driver should fail to start if this feature is not present until this is fixed. Thank you for pointing this out.

@ddaney-fungible Out of curiosity - do you experience issues with the non-compliant driver on HW or other than QEMU\KVM hypervisor?

@ddaney-fungible Out of curiosity - do you experience issues with the non-compliant driver on HW or other than QEMU\KVM hypervisor?

Yes. The failure was seen in a virtio-net function that is not part of Qemu. On the system in question EDK2 and Linux drivers seem to work well, but it was observed that this Windows driver was supplying buffers in two chunks, one of size 12 for the header and the second for the packet payload.

@ddaney-fungible Can you please share with us the host features as suggested during feature negotiation? (better in hex)
Thanks.

@ddaney-fungible Can you please share with us the host features as suggested during feature negotiation? (better in hex) Thanks.

device_feature[0] = 0x00010029
defice_feature[1] = 0x00000057
Driver is responding with:
driver_feature[0] = 0x00010029
driver_feature[1] = 0x00000007

I think there is a misunderstanding of how to interpret those values.
device_feature[0] = VIRTIO_NET_F_CSUM |
VIRTIO_NET_F_MTU |
VIRTIO_NET_F_MAC |
VIRTIO_NET_F_STATUS
device_feature[1] = VIRTIO_F_VERSION_1 |
VIRTIO_F_NOTIFICATION_DATA |
VIRTIO_F_ACCESS_PLATFORM |
VIRTIO_F_ORDER_PLATFORM |
VIRTIO_F_RING_PACKED

@ddaney-fungible Sorry, by mistake I swapped them when read

The virtio  spec says:
<IP_ADDRESS>.1 Driver Requirements: Setting Up Receive Buffers
• If VIRTIO_NET_F_MRG_RXBUF is not negotiated:
– If VIRTIO_NET_F_GUEST_TSO4, VIRTIO_NET_F_GUEST_TSO6 or VIRTIO_NET_F_GUEST_-
UFO are negotiated, the driver SHOULD populate the receive queue(s) with buffers of at least
65562 bytes.
– Otherwise, the driver SHOULD populate the receive queue(s) with buffers of at least 1526 bytes.
• If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer MUST be at least the size of the struct
virtio_net_hdr.
Note: Obviously each buffer can be split across multiple descriptor elements.
If VIRTIO_NET_F_MQ is negotiated, each of receiveq1.. .receiveqN that will be used SHOULD be populated
with receive buffers.
<IP_ADDRESS>.2 Device Requirements: Setting Up Receive Buffers
The device MUST set num_buffers to the number of descriptors used to hold the incoming packet.
The device MUST use only a single descriptor if VIRTIO_NET_F_MRG_RXBUF was not negotiated.
Note: This means that num_buffers will always be 1 if VIRTIO_NET_F_MRG_RXBUF is not negotiated.
In the terminology of the spec the "descriptor" is one or more "descriptor elements", combined together using VIRTQ_DESC_F_NEXT, see "2.8.6 Next Flag: Descriptor Chaining" (in the indirect area, if supported, or several consecutive elements in the descriptor queue)
The point of VIRTIO_NET_F_MRG_RXBUF is that this virtio-net specific feature allows to place a network packet over several consecutive descriptors (not chained together with VIRTQ_DESC_F_NEXT).
Chaining the "descriptor elements" into one "descriptor" is virtio transport feature, common for all the virtio devices.
Probably this is a good idea to reduce number of descriptor elements and we'll evaluate the possibility to do so, but I think there is no violation of the spec. We can request the comment from virtio-comment or virtio-dev mail lists if needed.

@ddaney-fungible I am wondering if you support RSS in your HW and if you aware of the virtio spec parts related to RSS.
Also, it will be interesting to hear about the offload support.


Converting normal map values to vectors; numerical errors

Perturbed normals are encoded in normal map pixels as RGB vectors. To obtain a perturbed normal conversion from RGB to unit vector is required. The problem appears when one (or more) of RGB channel has a value of 128 which should exactly be 0 in converted vector. But in this case, converted vector not 0 but close to 0, more specifically: 0.003921 or -0.003921.
Below is the normal map baked in Blender which has this specific cases:

For example, pixel value of (128, 128, 255) should be converted to (0,0,1) but it it has values of (0.003921, -0.003921, 0.999985).

I wanna work on to this project can you assign it to me.


Syntax error on DDL for H2 DBMS

In the file tables_h2.sql there is a SQL syntax error at line 95 (extra comma).
This error cannot permit the execution of creation script on H2 DBMS.

It should already been fixed by #513, this issue can be closed.

@jhouserizer another one already fixed that can be closed


Remove Axios as the default driver

Now Axios driver is used as the default, but because of this it is always bundled even if not used. This adds an unnecessary weight to the package

Closed by #12


Build 'virtualbox-iso' errored: Error removing floppy controller

On Windows 7 x64, When I execute:
packer build -only=virtualbox-iso -var-file=ubuntu1604.json ubuntu.json
I get this error after cleanup.sh successfully terminates:
==> virtualbox-iso: Gracefully halting virtual machine...
        virtualbox-iso: Removing floppy drive...
==> virtualbox-iso: Error removing floppy controller: VBoxManage error: VBoxManage.exe: error: The machine 'ubuntu1604' is already locked for a session (or being unlocked)
==> virtualbox-iso: VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
==> virtualbox-iso: VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 1038 of file VBoxManageStorageController.cpp
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
...
==> Builds finished but no artifacts were created.
Is this something related to packer, to VBoxManage or to how your scripts are using these utils?
VBox version = 5.1.10 (latest)

Which version of Packer do you have? There has been a fix for this in (at
least) the latest version.
On Nov 30, 2016 8:47 AM, "Christian P. Lerch"<EMAIL_ADDRESS>wrote:

On Windows 7 x64, When I execute:
packer build -only=virtualbox-iso -var-file=ubuntu1604.json ubuntu.json
I get this error after cleanup.sh successfully terminates:
==> virtualbox-iso: Gracefully halting virtual machine...
virtualbox-iso: Removing floppy drive...
==> virtualbox-iso: Error removing floppy controller: VBoxManage error:
VBoxManage.exe: error: The machine 'ubuntu1604' is already locked for a
session (or being unlocked)
==> virtualbox-iso: VBoxManage.exe: error: Details: code
VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface
IMachine, callee IUnknown
==> virtualbox-iso: VBoxManage.exe: error: Context:
"LockMachine(a->session, LockType_Write)" at line 1038 of file
VBoxManageStorageController.cpp
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
...
==> Builds finished but no artifacts were created.
Is this something related to packer, to VBoxManage or to how your scripts
are using these utils?
VBox version = 5.1.10 (latest)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/boxcutter/ubuntu/issues/89, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiCg8mRXhy-vOxTZP0cJnYiTxtLhnHUks5rDSoagaJpZM4K_5aI
.

>packer -version
0.12.0
>vboxmanage -version
5.1.10r112026

Try to adjust post_shutdown_delay

Will try. Can you please give me a short hint where exactly to put this parameter

      "output_directory": "output-{{ user `vm_name` }}-virtualbox-iso",
      "shutdown_command": "echo '{{ user `ssh_password` }}'|sudo -S shutdown -P now",
      "post_shutdown_delay": "5m",
      "ssh_password": "{{ user `ssh_password` }}",
      "ssh_username": "{{ user `ssh_username` }}",
      "ssh_wait_timeout": "10000s",
      "type": "virtualbox-iso",

Thank you very much!
It worked now with just a 1m delay.

https://github.com/boxcutter/ubuntu/commit/05ff63e51ec51ba3521d181318dc91a33e27f528


Invalid monitor display error

I keep getting the same error that my resolution is unsupported no matter what size I pick. So what resolutions ARE allowed?

All 16:9 and 16:10 resolutions are accepted. If all of those resolutions are saying they're not supported then we will need some more information about your setup.

Never mind, the issue was resolved once I switched to a different monitor.


Refactor Code and readable issues

Currently the code is all over the place and in one single file. Refactor the code by moving it to a more organised structure.

Hello @boidushya
Please assign this issue to me.
Thank You

Sure @radioactive11 , if you need any further help, please let me know


Nuget Package out of date

Hey Rico, you need to update your nuget package, because .NET developers are people too.

@evereq maintains according to #97