Introduce BeliefUpdater type

I think it would be very useful to define a BeliefUpdater type. Here are the main benefits, as I see them:

Allows use of different belief update methods for the same belief type. For instance, for a particle-based belief, one may chose an exact belief updater for a small problem and a particle-filtering updater for a larger problem.

Similarly to the Solver type, allows for a clean way of providing configuration parameters for belief updaters and preallocation/storage of their frequently used variables (thus possibly improving performance). An alternative to this would be to store such parameters and variables in either the belief structure or the POMDP structure, neither of which would be ideal, in my opinion.

We'd need to modify 'belief' function as follows:
belief(bu::BeliefUpdater, pomdp::POMDP, belief_old::Belief, action::Any, obs::Any, belief_new::Belief=create_belief(pomdp))

I'm good with this if there is consensus.

I'll reply later today
On Sat, Sep 26, 2015 at 3:58 PM Mykel Kochenderfer<EMAIL_ADDRESS>wrote:

I'm good with this if there is consensus.
—
Reply to this email directly or view it on GitHub
https://github.com/sisl/POMDPs.jl/issues/32#issuecomment-143502952.

After thinking about this for a while, I am strongly against introducing this type. First, I will talk some about how the functionality of a BeliefUpdater can be implemented (elegantly) in the current interface, and then I will talk about the reasons that I think it should not be included.
A) BeliefUpdater functionality can be implemented using the current framework
First, it should be noted that any belief update behavior that could be specified by a BeliefUpdater could be specified by including the BeliefUpdater object in the Belief object. Thus, there is not a strict need for BeliefUpdater for the sake of being able to represent all possible belief update behaviors.
If I understand correctly, the argument for introducing BeliefUpdater is that it would be more convenient in some cases to reuse code by defining several BeliefUpdaters for one Belief type, and more julian to use multiple dispatch to determine behavior rather than examining the contents of the Belief object. Fortunately, julia's parametric type system allows us to easily do this without using two objects. I believe the examples that @ebalaban used involved particle filters, but I think Gaussian filters for nonlinear systems might offer a shorter example. Suppose that we have a single Gaussian belief representation, but we want to have an Unscented Kalman Filter (UKF) update and an Extended Kalman Filter (EKF) update. This can be implemented in the following way:
abstract Belief

abstract GaussianBeliefUpdater

type EKFUpdater <: GaussianBeliefUpdater
end

type UKFUpdater <: GaussianBeliefUpdater
end

type GaussianBelief{T<:GaussianBeliefUpdater}
end

function belief(b::GaussianBelief{EKFUpdater})
    println("EKF update")
end

function belief(b::GaussianBelief{UKFUpdater})
    println("UKF update")
end

ekf_belief = GaussianBelief{EKFUpdater}()
ukf_belief = GaussianBelief{UKFUpdater}()

belief(ekf_belief)
belief(ukf_belief)

The belief function here represents the belief function in POMDPs.jl. Both GaussianBelief{EKFUpdater} and GaussianBelief{UKFUpdater} are subtypes of Belief, but they behave differently when belief is called. The first time belief is called, an ekf update occurs, the second time a ukf update occurs.
If there are any other cases that cannot be addressed by this method or something similar, please post a comment, and I think we can come up with a way to do it elegantly without requiring BeliefUpdater.
B) BeliefUpdater will make developing and using POMDPs.jl more difficult and less likely to be widely adopted
I think BeliefUpdater will make life more difficult for us primarily for the following 4 reasons:
1. There is one more concept to understand
When someone is deciding whether to use POMDPs.jl, they will look at the interface and, the quicker they understand it, the more likely they will be to adopt it. BeliefUpdater is likely to distract from the more fundamental concepts we are trying to communicate.
2. The list of objects that define a problem will be larger
Every time someone writes a new problem (POMDP subtype), they will have to define a BeliefUpdater. Moreover, there will be many places where types will need to have an extra belief updater field, or functions will need to have belief updater arguments. This is unnecessary for simple problems, and will raise the barrier to entry.
3. create_belief and specialize_belief will be much more complicated
If we want to automatically determine the belief type based on the pomdp as we do when we call create_belief, we will also need to define a function to determine the BeliefUpdater for that Belief. Furthermore, if we adopt the specialize_belief function in #32, the specialized belief will also have an associated BeliefUpdater that will need to be determined.
4. Belief and BeliefUpdater types will tend to be highly coupled
One of the main reasons that I see for introducing a new abstract type in POMDPs.jl is that it defines a new component that can be reused with a wide range of other components, i.e. most POMDPs should be able to be used with most Solvers, which should be able to be used with most Simulators. This will probably not be the case with BeliefUpdaters. It seems to me that each BeliefUpdater would only be able to be used with one, or at most a few Belief types. Since there is such a strong coupling here, I think a better way to organize this is with parametric types or another similar approach.
I hope this all makes sense, I really want this interface to be as good as possible :)

Thanks, guys, for taking the time to really figure this out. Zach, would it be possible to discuss at 11:30am on Monday?

@zsunberg, thank you for the detailed response on this. I certainly share your desire to make this API as good as possible :-) I think where we diverge on this is that I consider belief update to be an operation in roughly the same category of importance as solving the POMDP in the first place and you, perhaps, see it being in more of a supporting capacity to the solver (please correct me if I am wrong).
We could, of course, as you suggest, encapsulate belief updater parameters in Belief structures, create wrappers for beliefs that make them look different (even though, deep inside, they are all the same) and dispatch the appropriate belief() methods based on that. So, why not do the same for solvers too then? We'd create different wrappers for our input POMDP (e.g. POMCP_POMDP, DESPOT_POMDP, MCVI_POMDP, etc). We'd then hide configuration parameters for the solver inside the POMDP structure and then call solve(). I have to confess that before really understanding the general philosophy that POMDPs.jl was aiming for, this is kind of what I implemented in the first cut of DESPOT. I do, however, now like that we keep the POMDP structure as clean and generic as possible. In the same manner, I would also like to keep Belief implementations as clean as possible and only containing the distribution itself. As you may have deduced from our previous discussions, my preference is to resort to type wrapping only in the most dire circumstances. I think type wrapping makes it harder to understand what is going on, rather than easier.
Ideally, belief updating would be independent of the problem type and of the solver type. Thus any problem can be used with any solver and with any belief updater that supports the belief representation type that we want to use in the solver. You are right that a belief updater will be tied to one (or, at most, few) belief types - but this is what I think we want! In the near term, belief updaters will probably be supplied by solver writers to work with their preferred belief representations. In the future, however, I'd like to see a library of them that can work on the popular belief representation types using a variety of methods (e.g., UKF and EKF for Gaussian belief, as you mentioned).
So, I remain convinced that endowing belief updaters with the same rights and responsibilities as solvers is the right way to go :-) Perhaps others will chime in and help us break our stalemate :-)

I think I'm being persuaded by Edward. Very fundamental to POMDPs is the notion of belief updating. There are probably more algorithms for belief updating (e.g., in the fields of state estimation, tracking, and filtering) than there are for doing the actual planning. Of course, we want to stay focused on the planning aspect and not try to be a comprehensive state estimation package.

Just out of curiosity, will introducing a separate BeliefUpdater type help you solve the problem of DESPOT being tied to a specific belief representation/update method? I don't believe it can help with POMCP since the update simulations are carried out as part of the decision-making process. I am beginning to think the POMCP and DESPOT situations are not as similar as I thought.

I think the strongest argument for this is that separation of state and dynamics information is good. I.e. in the <POMDP, State> domain, the POMDP contains the dynamics information and the State contains the state information, in the <Policy, PolicyState> domain, the policy contains the dynamics information and the PolicyState contains the state informations, so, if we want beliefs to be analogous, as @ebalaban has said, we should have <BeliefUpdater, Belief> instead of just Belief.
I will feel a lot less uneasy about this if we adopt the changes suggested in #34 because then it would be clear that the Policy should carry a BeliefUpdater (or the Policy will handle the belief updates itself if that makes sense for the policy). Before #34 it wasn't clear to me where exactly the BeliefUpdater would live in the simulation and who would be responsible for it.
We may want to consider breaking the belief updates interface out into a separate package though to keep POMDPs more concise

I'm okay with belief update stuff either being in POMDPs.jl or in a separate package.
The Policy would keep track of the BeliefUpdater.

OK - what about this:
Either
abstract BeliefUpdater
abstract POMDP <: BeliefUpdater
abstract Policy <: BeliefUpdater

function update(::BeliefUpdater, ::Belief, ::Action, ::Observation)

or, if we can't stomach something that radical, simply
function update(::Union(BeliefUpdater, Policy, POMDP), ::Belief, ::Action, ::Observation)

(with the extra preallocation arguments of course).
This reflects the fact that a Policy may provide the belief update if the belief is a policy-specific structure, and a POMDP may provide exact belief updates or domain-specific approximate belief updates.
I think this solves all of our problems:

@ebalaban can define BeliefUpdaters that are not Policys or POMDPs to his heart's content
@zsunberg doesn't have to carry around an extra BeliefUpdater wherever beliefs are used
This provides a way for problem designers to specify exact belief updates

I think that in the outer loop simulate function, the policy should always be the first argument to update for consistency's sake. That policy may contain a BeliefUpdater for internal use if the solver-writer wants to provide that flexibility.

Okay. I'd rather have four separate functions instead of one with a Union. I really want to avoid using Unions.

@mykelk, is there a reason you said "four" instead of "three"? I only see three being created. Am I missing something?
Also, is there a "Union considered harmful" somewhere out there for me to read? To me using a union seems like a more concise way of doing exactly the same thing as declaring the three functions (this is of miniscule importance - not worth arguing - I'm just curious).

@ebalaban should we close this and move further discussion to #35

Sounds good.


Do not find cupti header files

like this
[ 14%] Building CUDA object CMakeFiles/ios_runtime.dir/src/ios/profile.cu.o
/workdir/ios/ios/src/ios/profile.cu:5:10: fatal error: cupti_events.h: No such file or directory
 #include <cupti_events.h>
          ^~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/ios_runtime.dir/src/ios/profile.cu.o] Error 1
make[1]: *** [CMakeFiles/ios_runtime.dir/all] Error 2
make: *** [all] Error 2

but, I install in /usr/local/cuda/extras/CUPTI/include/ already.

Hi tonyw,
I have added the cuda/extras/CUPTI/include to the include path in CMakeLists.txt file explicitly in the master branch. Can you give another try?
Do not hesitate to reach out if there is still any problem or question.

good job


hello，cooperation！

Hello! I am also recently trying to replicate Block-NeRF and have built the most basic network architecture, including merging Mip-NeRF with NeRF-Wild, and got good results, if interested I hope to share my code to see if it helps your progress, here is my email<EMAIL_ADDRESS>if interested you can email me and I will share my code and my current progress

Sure, thank you very much. I have emailed you.


Add option to no-extraneous-dependencies to check shrinkwrap

Just thinking of this : If a package has a npm-shrinkwrap.json file, any (production) dependencies should also appear in the shrinkwrap.
I'm proposing to add a new option (checkShrinkwrap: bool?) to add an additional check for dependencies (that we know are production dependencies), to verify that they also appear at the top level of the shrinkwrap.
What do you think?
PS: Yup. This rule has a lot of options...

My new barometer for rule creation/mutation is "will I immediately be glad I can use this?"
If no: not right now.
It would be cool to validate that shrinkwrap matches dependencies, but that feels more like a script to call during posttest/prepublish than a lint rule.
But again: if you'll use it and be glad you have it, do it. 😄

My new barometer for rule creation/mutation is "will I immediately be glad I can use this?"

Sounds like a good rule of thumb :+1:
I need to talk about it to colleagues, but I think we'd definitely use it at work. It happens sometimes (too often at least) that dependencies are added to the projects without the shrinkwrap being updated. I agree that a separate tool could be used for this (there probably exists some, don't know any, but I haven't looked for any either), but I think that this would be a nice addition here. It would be one less think to set up in a project, as ESLint configs are shareable, but build processes are not.
Now that I think of it, this could get a bit harder when there are multiple shrinkwraps in a project (as we've seen with the multiple package.json issues), though I don't know if (and thus how...) that is used somehow.


make Error on personal Suppression File to not fatal

Fixes Issue
if one personal suppression file fails to load, analyzer stops after prepare step and base suppression File Rules are not processed
Description of Change
I change to make not fatal Error, if personal suppression file fails to load
Have test cases been added to cover the new functionality?
?

Can one of the admins verify this patch?

thanks!

@jeremylong, when do you plan to make the next release?

My plan is next weekend. I want to go through the FP and likely add the ability to suppress NSP findings.


Better job jar assignment using 0.9.0 method of HadoopTask

This continues to help prevent spurious library collisions by only loading the kinds of jars that Hadoop tasks should load.
Hadoop tasks use io.druid.indexer.JobHelper#setupClasspath to replicate their jars. The jars are put in some universally accessable location and each job addresses them.
Spark has internal mechanisms for shipping its jars around, making an external blob storage (like HDFS or S3) not required for jar distribution.
In general they both "make list of jars... distribute via XXX... make that list available on all the workers" but how they accomplish the XXX part is different.

LGTM, wondering if there is a way to verify that it fixes the initialization race ?

@xvrl updated master comment with more information.

@drcrallen can we put it in the code? that would be the best place for posterity and debugging differences between hadoop / spark in the future.

@xvrl fixed


Update documentation according to major version 1.0.0

Signed-off-by: Maxime Belanger<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

Thanks!
/lgtm


add client-test scm info

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Adress 2

hello,
As no developer, i am trying to put my site together.  How can i change the is at least one charachter is required?

You can modify the rules here:
https://github.com/tastyigniter/ti-ext-cart/blob/048acecb53bad81b990b37f2e9ae9bfd6d71ede9/components/Checkout.php#L302


Transaction creation failed.

Just trying the out of the box transaction an error:
Phantom - RPC Error: Transaction creation failed. {code: -32003, message: 'Transaction creation failed.'}

Same issue on my end

Faced the same issue and increased the lamport value(i tried with 1 Billion Lamport) to higher value and ot worked.
Note: 1 Sol = 1 Billion Lamport and so transaction of 1 Lamport is failing i guess.


Swagger spec incorrect casing for complex type parameters

I'm using camel-casing for my route parameters, sometimes I use complex types as parameter which works fine. However, no matter what casing I use for the names of the properties, they are all in lower case in the generated Swagger spec.
In the XML the member looks as follows:
       <member name="NavigationFlagParameters.IncludeChildNodes">
           <summary>
           Indicates whether or not child nodes should be included.
           </summary>
       </member>

This will be converted into the following in the spec:
{
    "name": "includechildnodes",
    "in": "query",
    "description": "Indicates whether or not child nodes should be included.",
    "required": false,
    "type": "boolean"
},

Am I missing something or is this a bug?

Yep this looks like a bug. Thanks for reporting it - I'll aim to get a fix out with the next release.

Should be resolved in latest release - 5.2.0

It seems like all my request parameters are FORCED to camelCase. This looks wierd when I have things like DOB or SSN which become sSN and dOB


Documentation for Odo integration with Operator Hub

What type of PR is this?
/kind documentation
[skip ci]
What does does this PR do / why we need it:
Adds documentation explaining how to use Odo and Operator Hub
Which issue(s) this PR fixes:
Fixes #2779
How to test changes / Special notes to the reviewer:

/approve

The docs are very nice and thorough, the one thing that worries me is that it exposes alot of words like pods, CRDs etc which we want to hide from the user as thats one of the principals of odo I suppose.
I understand that, the docs isn't the only place where this needs to be taken care of. or maybe we cannot solve this problem for the operator hub feature due to the limitations of the metadata accessible to odo. something to think about I guess.

The docs are very nice and thorough, the one thing that worries me is that it exposes alot of words like pods, CRDs etc which we want to hide from the user as thats one of the principals of odo I suppose.
I understand that, the docs isn't the only place where this needs to be taken care of. or maybe we cannot solve this problem for the operator hub feature due to the limitations of the metadata accessible to odo. something to think about I guess.

I wouldn't be afraid of using terms like Pods or CRDs in the documentation. This is a great place to explain what odo is doing under the hood, for those that are interested,  and reveal some of the "odo magic".

Hey @dharmit thank you so much for detailing how to use odo with Operator Hub.
My question is, is there any way you can format it similar to how we do some of the OpenShift tutorials? For example:
* Showing how to create a project first

* Using the numeric formatting (1. 2. 3. etc) of the steps

Similar to this example: https://odo.dev/docs/creating-a-multicomponent-application-with-odo/
The source being here: https://github.com/openshift/openshift-docs/blob/master/cli_reference/openshift_developer_cli/creating-a-multicomponent-application-with-odo.adoc
If not, no worries. at the moment, the site and the synchronization to the current docs is a bit messed up.
I know this is a lot to ask. But I can re-organize it if you'd like. I wouldn't be removing any of your notes, but simply putting it in a similar format as our current documentation.

Sure, I can make the changes that should help this piece use directly on odo website. That would be cool!

The docs are very nice and thorough, the one thing that worries me is that it exposes alot of words like pods, CRDs etc which we want to hide from the user as thats one of the principals of odo I suppose.

I agree with your thought process but I think we've used the corresponding words used in odo terminology all over the place. For example, if we're talking about CSV, we make sure that the word Operator shows up right besides it or at least in the same sentence. Same for CR/CRD and service.
As for pods, it's showing up near the end of the doc where we explain the user that default configuration will bring up three pods of EtcdCluster. I don't see a way to use something else in its place. Three instances of EtcdCluster doesn't seem like entirely right to me. :disappointed:

I understand that, the docs isn't the only place where this needs to be taken care of. or maybe we cannot solve this problem for the operator hub feature due to the limitations of the metadata accessible to odo. something to think about I guess.

I think we should always keep in mind to use the words in odo terminology more liberally than those from k8s terminology. So, if it seems like k8s terminology is used more than odo terminology, it's wrong on our part (here, my part) and we must fix it!
That said, I believe that documentation is a place where we could use words from k8s world so that interested users can know what's happening under the hood.

@cdrage to make changes to this PR to structure the docs like you've suggested, I think I could do below:

break the sections in the .adoc file into modules.
have a modules directory at a level above docs/user/operator-hub.adoc, so that would be docs/modules

Is there anything else I'd be required to do?

@dharmit Nope, no need for the modules. What I was suggesting is adding perhaps a "Creating a project" and following a similar format as: https://odo.dev/docs/creating-a-single-component-application-with-odo/
For example, we start with listing pre-requisites and follow a simple step-by-step structure. Have a look at a few of the other examples such as:
https://odo.dev/docs/creating-a-multicomponent-application-with-odo/
and https://odo.dev/docs/creating-an-application-with-a-database/ and notice how similar they are.

@cdrage I've made the changes. Hope they align with your recommendations. Let me know if you'd like me to make any changes. I've kept a separate "Prerequisites" section but let me know if it doesn't make sense to keep it.
Other than that, the docs on https://odo.dev need to change from Log in to an OpenShift cluster: to Login to the Kubernetes/OpenShift cluster:, IMO.

/lgtm

@cdrage need your input on this comment https://github.com/openshift/odo/pull/3029#issuecomment-624461469. If it looks good, could you please LGTM?
/hold

Can you change this so it's in the
/docs/public folder? Then we can refactor after / LGTM :)

/lgtm


Sources identification

Resolve next:

each source should have an alias. "n/d" in outout means bug or error
should be a way to define a special style for different sources (in main output and search output)
column "sources" should have to modes: text and icons.

Solved 0.14.0


Option -NewTitle DOESN'T WORK

When using the option -NewTitle, one gets an error:
Start-SPOSiteRename : A parameter cannot be found that matches parameter name 'NewSiteTitle'.
At line:4 char:60

... teRename -Identity $url -NewSiteUrl $NewSiteUrl -NewSiteTitle $newTit ...

                                                ~~~~~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Start-SPOSiteRename], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Online.SharePoint.PowerShell.StartSPOSiteRename

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1d1b44e3-4af5-1458-d931-72a0f698732b
Version Independent ID: 1751767f-1d8a-7750-35b9-725b5a3ad705
Content: Start-SPOSiteRename (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteRename.md
Service: sharepoint-powershell
GitHub Login: @trent-green
Microsoft Alias: trgreen

@officedocsbot assign @yogkumgit

Hello @mvanders Marc 👍
How are you?
Please be sure of running the latest available stable version of the SharePoint Powershell module.
Try to reproduce to see if we had to change something in the documentation but could not repro.
Thank you

@get-itips  Thank you very much for the contribution and sharing this explanation. @mvanders
Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Update the game over message

Update the game over message so people know how to play again!

wfwqefwefqwfwqef


Close all/other tabs should close all saved tabs when some tabs are unsaved

Say I have two tabs:

tab A shows a saved file
tab B shows a file with unsaved changes

In VS code, if I "Close All" tabs, the editor will first ask me whether I want to save changes in tab B. If I cancel the dialog, no tabs are closed.
In Sublime Text, if I "Close All" tabs, the editor will close tab A, then ask me what to do with tab B.
This is extremely helpful for cleaning up the work space of the editor, when I have tens of tabs open, but I want to keep the unsaved ones around for whatever reason.
The work around is to go and manually close tabs one by one, which is slow and annoying.

While I agree this should be an option, I prefer the current behavior, so this should probably be a setting.
Also, if this change is made I think we should also have a way of reopening the closed tabs with a single command, and not have to reopen one by one until we find the correct set of tabs that were open.


How to save the model?

I want to save models during training as the state_dict() function in pytorch. How can?

you can look at each ML or DL model as a set of parameters, if you completely know the model which you are working with, you can manually save those parameters, if not, a simple way to save ML models is using joblib library:
import joblib
joblib.dump(model, 'model.pkl')

and simply load it:
model = joblib.load('model.pkl')

Hi, when I try to use 'joblib' to save the trained model in the 'convolutional_neural_network.py' program, I encounter the following error. How can I resolve this?"
"TypeError: cannot pickle '_io.TextIOWrapper' object"

您好，我是黄绮恒，我已经收到了您的来信，非常感谢您能抽出宝贵时间给我发Email，我会尽快回复。祝您生活愉快！Hello, I am Huang Qiheng. I have received your letter. Thank you very much for taking the time to email me. I will reply as soon as possible.


Problem: Hollywood syntax highlighting is outdated.

Solution: Update syntax highlighting to Hollywood version 10.

I'll include it, thanks.


BUG: cannot install scipy/meson.build ERROR: Dependency "OpenBLAS" not found, tried pkgconfig, framework and cmake

Describe your issue.
I am trying to install scipy on my Mac M1, macOS Monterey version 12.6.
I keep getting this message, despite having OpenBLAS specified:
../../scipy/meson.build:131:0: ERROR: Dependency "OpenBLAS" not found, tried pkgconfig, framework and cmake

Inspired by https://github.com/scipy/scipy/issues/13409#issuecomment-1021057368.
Reproducing Code Example
> pip list
Package        Version
-------------- --------
attrs          22.1.0
beniget        0.4.1
Cython         0.29.32
exceptiongroup 1.0.0
gast           0.5.3
iniconfig      1.1.1
meson          0.63.3
ninja          <IP_ADDRESS>
numpy          1.23.4
packaging      21.3
pip            22.3
pluggy         1.0.0
ply            3.11
pybind11       2.10.1
pyparsing      3.0.9
pytest         7.2.0
pythran        0.12.0
setuptools     56.0.0
tomli          2.0.1

> brew install openblas
> export OPENBLAS=$(/opt/homebrew/bin/brew --prefix openblas)
> export CFLAGS="-falign-functions=8 ${CFLAGS}"
> pip install scipy

Error message
Looking in indexes: https://pypi.org/simple
Collecting scipy
  Using cached scipy-1.9.3.tar.gz (42.1 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [68 lines of output]
      ld: warning: directory not found for option '-L/opt/homebrew/opt/lapack/lib'
      The Meson build system
      Version: 0.63.3
      Source dir: /private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6
      Build dir: /private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6/.mesonpy-5zpf6fue/build
      Build type: native build
      Project name: SciPy
      Project version: 1.9.3
      C compiler for the host machine: cc (clang 14.0.0 "Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)")
      C linker for the host machine: cc ld64 819.6
      C++ compiler for the host machine: c++ (clang 14.0.0 "Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)")
      C++ linker for the host machine: c++ ld64 819.6
      Host machine cpu family: aarch64
      Host machine cpu: arm64
      Compiler for C supports arguments -Wno-unused-but-set-variable: YES
      Compiler for C supports arguments -Wno-unused-but-set-variable: YES (cached)
      Compiler for C supports arguments -Wno-unused-function: YES
      Compiler for C supports arguments -Wno-conversion: YES
      Compiler for C supports arguments -Wno-misleading-indentation: YES
      Compiler for C supports arguments -Wno-incompatible-pointer-types: YES
      Library m found: YES
      Fortran compiler for the host machine: gfortran (gcc 12.2.0 "GNU Fortran (Homebrew GCC 12.2.0) 12.2.0")
      Fortran linker for the host machine: gfortran ld64 819.6
      Compiler for Fortran supports arguments -Wno-conversion: YES
      Program cython found: YES (/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/bin/cython)
      Program pythran found: YES (/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/bin/pythran)
      Program cp found: YES (/bin/cp)
      Program python found: YES (/Users/james.braza/code/stingray/venv/bin/python)
      Found pkg-config: /opt/homebrew/bin/pkg-config (0.29.2)
      Run-time dependency threads found: YES
      Library npymath found: YES
      Library npyrandom found: YES
      Found CMake: /opt/homebrew/bin/cmake (3.24.2)
      Run-time dependency openblas found: NO (tried pkgconfig, framework and cmake)
      Run-time dependency openblas found: NO (tried pkgconfig, framework and cmake)

      ../../scipy/meson.build:131:0: ERROR: Dependency "OpenBLAS" not found, tried pkgconfig, framework and cmake

      A full log can be found at /private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6/.mesonpy-5zpf6fue/build/meson-logs/meson-log.txt
      + meson setup --native-file=/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6/.mesonpy-native-file.ini -Ddebug=false -Doptimization=2 --prefix=/Users/james.braza/.pyenv/versions/3.8.14 /private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6 /private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6/.mesonpy-5zpf6fue/build
      Traceback (most recent call last):
        File "/Users/james.braza/code/stingray/venv/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 351, in <module>
          main()
        File "/Users/james.braza/code/stingray/venv/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 333, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/james.braza/code/stingray/venv/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 969, in get_requires_for_build_wheel
          with _project(config_settings) as project:
        File "/Users/james.braza/.pyenv/versions/3.8.14/lib/python3.8/contextlib.py", line 113, in __enter__
          return next(self.gen)
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 948, in _project
          with Project.with_temp_working_dir(
        File "/Users/james.braza/.pyenv/versions/3.8.14/lib/python3.8/contextlib.py", line 113, in __enter__
          return next(self.gen)
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 777, in with_temp_working_dir
          yield cls(source_dir, tmpdir, build_dir)
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 682, in __init__
          self._configure(reconfigure=bool(build_dir) and not native_file_mismatch)
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 713, in _configure
          self._meson(
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 696, in _meson
          return self._proc('meson', *args)
        File "/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-build-env-y04279an/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 691, in _proc
          subprocess.check_call(list(args))
        File "/Users/james.braza/.pyenv/versions/3.8.14/lib/python3.8/subprocess.py", line 364, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['meson', 'setup', '--native-file=/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6/.mesonpy-native-file.ini', '-Ddebug=false', '-Doptimization=2', '--prefix=/Users/james.braza/.pyenv/versions/3.8.14', '/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6', '/private/var/folders/78/lm6p91s90fx99cshsxqz_19w0000gn/T/pip-install-5u70s5ho/scipy_e3eb27a162664e6297ee8511faef33d6/.mesonpy-5zpf6fue/build']' returned non-zero exit status 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

SciPy/NumPy/Python version information
n/a, 1.23.4, 3.8.14

I'm not sure why pip doesn't install the wheel that's on PyPI, scipy-1.9.3-cp38-cp38-macosx_12_0_arm64.whl. If I create a Python 3.8 environment then try and pip install scipy it collects the correct wheel. What happens if you try:
pip install scipy==1.9.3 --only-binary=:all:

Yeah I am also not sure why pip install is not playing nice with the macOS binaries. 🥲
Adding either --only-binary=:all: or --prefer-binary enabled the installation to work, by installing a macOS binary.
Thank you so much @andyfaff !  Please feel free to close this ticket if you see no further action necessary.

Check your Python version. I was able to install this in Python 3.11.4 (in Anaconda).

I found the solution by running
brew info openblas
and then setting the variables added shown there:
...
==> Caveats
openblas is keg-only, which means it was not symlinked into /opt/homebrew,
because macOS provides BLAS in Accelerate.framework.
For compilers to find openblas you may need to set:
export LDFLAGS="-L/opt/homebrew/opt/openblas/lib"
export CPPFLAGS="-I/opt/homebrew/opt/openblas/include"
For pkg-config to find openblas you may need to set:
export PKG_CONFIG_PATH="/opt/homebrew/opt/openblas/lib/pkgconfig"

Yep, the pkg-config part is now included in the macOS section of our building docs: https://scipy.github.io/devdocs/building/index.html#system-level-dependencies


I Was Sleeping But I'm Married to The Malware

Worker.kt implements CoroutineScope
rename executeWorker to execute
wrap doWork in Worker.launch
move provideCoroutineScope to globalscope

I love the way that sounds. I came earlier though before I got out of bed. That must be why I conquered! haha


various tox improvements

pass proxy environment variables to docs (as these are needed to fetch correctly intersphinx files behind proxies)
better indentation for commands to see where boundaries between commands are
do not start all definitions on new line, this makes the file more compact and readable
use references instead of repeating dependencies, and version qualify dependency
replace echo with Python for not relying on OS packages
also ignore intermediate coverage files

@agjohnson which ones do you mean? and what do you consider arbitrary?

Anyone? :+1:

@gaborbernat We'll get to this when we can. This is an open source project, and our priority list sometimes means there is a delay in response. Don't worry; we know this PR is here, and we'll review it again when we can.

Sounds like we have different views on what should go in tox.ini. Thanks for the PR, but I'm going to close this as I don't think it's likely to get updated/merged. Feel free to reopen with changes if so -- sorry!


Not reconnecting to gateway

Describe the bug
We're experiencing a problem with disgo staying connected to the gateway for long durations (many weeks). We have gateway.WithAutoReconnect(true), but still occasionally log in to discord and see the bot offline, even though the process is still running ok, and other parts of the process are working fine. I'm not exactly certain at which point it goes offline, but looking at the logs for the night, these errors were logged:
Error
The error which gets logged if there is any:
time="2023-09-06T00:52:13Z" level=info msg="Received event" Duration="301.324µs" Event="On Member Joined Voice" Guild=...
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown
2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown

To Reproduce
Steps to reproduce the behavior:
Run the bot for a very long time
Expected behavior
Not disconnect from gateway
Screenshots
If applicable, add screenshots to help explain your problem.
Disgo Version(please complete the following information):

Version v0.16.7

Additional context
Add any other context about the problem here.

2023/09/06 00:52:13 ERROR error while parsing voice gateway event. error: json: cannot unmarshal object into Go value of type voice.GatewayMessageDataUnknown

this has been fixed in https://github.com/disgoorg/disgo/releases/tag/v0.16.8
please try updating to v0.16.9
gateway.WithAutoReconnect(true) is not needed since that is set to true by default
can you enable debug logs? that should help identify the issue with disconnecting

closing this since there is no response

@ImVexed ^


Add build for linux-aarch64

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerende

The aarch64 build fails with:
Encountered problems while solving:
  - nothing provides requested tensorflow *,2.17.* cpu*

See https://github.com/conda-forge/tensorflow-feedstock/issues/136


Tap on url bar no longer selects the entire url

Describe the bug
On newer versions of the app, tapping the url bar only places the cursor into the url, instead of selecting the entire thing. So if you were wanting to copy the url, or clear the addess bar to make another search or type a different address, you'd have to do a long press to select all before being able to do so.
This might be intended behavior for duckduckgo search pages, because in that scenario it's very useful to be able to just tap once on the url bar and be able to add more search terms right away or move the cursor around, but when on other web pages, when a user taps on the url bar, chances are they're trying to either copy the address, or clear it to type a search term/another site's address.
It's a bit annoying to use this way, when you're used to it working the other way. And even though one may get used to this behavior eventually, it's a bit unfriendly to use.
How to Reproduce
Steps to reproduce the behavior:

Go to any web page
Tap on the url bar
Cursor gets placed where you tapped, instead of selecting the entire address bar

Expected behavior
Tapping the address bar should default to selecting the entire address bar for sites other than duckduckgo search pages (don't know if it's possible to have different behavior between sites though.)
Smartphone (please complete the following information):

DDG App Version: 5.76.1
Device: Nexus 5
OS: Android 7.1.2

On 5.75.1 it was fine, so it's either 5.76.0 or 5.76.1 that changed the behavior.

Thanks, we have a task in our internal backlog to address this issue: https://app.asana.com/0/414730916066338/1199931182139250/f

8f46aa7
Confirmed fixed in 5.77.0


[qbittorrent] qbittorrent failling to start with error

qBittorrent

Addon name : qBittorrent
Addon version : <IP_ADDRESS>202110311443-7435-01519b5e7ubuntu20.04.1-ls166-8

Describe the bug
Hi there, I've just installed the addon and haven't really changed the default configuration. From the logs I can see it's getting up to the 91-qbittorrent_configuration.sh script and curl throws an error and the container stops. I had a look at the script and I can see that the curl is to fetch the frontend code. I've been able to get a shell to an image of the stopped container, and I ran the curl command manually and it's able to fetch the frontend successfully. I've tried to debug this on my own, but I think I'm stuck now!
Thanks in advance for any help.
To Reproduce

Start the qbittorrent addon

Full addon log
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-aaa_dockerfile_backup.sh: executing...
[cont-init.d] 00-aaa_dockerfile_backup.sh: exited 0.
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
 Add-on: Qbittorrent
 qBittorrent is a bittorrent client
-----------------------------------------------------------
 Add-on version: <IP_ADDRESS>202110311443-7435-01519b5e7ubuntu20.04.1-ls166-8
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 11 (bullseye)  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.2.9
 Home Assistant Supervisor: 2022.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
 https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 10-adduser: executing...
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    1000
User gid:    1000
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 30-nginx.sh: executing...
[cont-init.d] 30-nginx.sh: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 90-dns_set.sh: executing...
[23:59:24] INFO: DNS SERVERS set to <IP_ADDRESS>
[cont-init.d] 90-dns_set.sh: exited 0.
[cont-init.d] 91-qbittorrent_configuration.sh: executing...
[23:59:25] INFO: Downloads can be found in /share/qBittorrent
[23:59:25] INFO: Whitelisted subsets will not require a password : localhost,<IP_ADDRESS>,<IP_ADDRESS>/16,<IP_ADDRESS>/16
[23:59:26] INFO: WEBUI username set to admin
[23:59:26] INFO: Alternate UI enabled : qb-web. If webui don't work, disable this option
curl: (3) URL using bad/illegal format or missing URL
[cont-init.d] 91-qbittorrent_configuration.sh: exited 3.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Full addon config
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
whitelist: localhost,<IP_ADDRESS>,<IP_ADDRESS>/16,<IP_ADDRESS>/16
customUI: vuetorrent
SavePath: /share/qBittorrent
Username: admin
DNS_server: <IP_ADDRESS>,<IP_ADDRESS>
PUID: '0'
PGID: '0'

System

Supervisor version: supervisor-2022.01.1
Host system version: Home Assistant 2022.2.9

I just tested setting customUI: '' in the yaml configuration and it started! So it's definitely an issue fetching the UI.

Okay, the plot thickens... Now that I could grab a shell on the actual running, 'hassio launched' container, I can see that DNS resolution isn't working on the container (and thus qbittorrent doesn't actually work).
root@db21ed7f-qbittorrent:/# curl google.com
curl: (6) Could not resolve host: google.com

So finally, just in case anyone has the same issue. I was able to disable the custom DNS server with DNS_server: '' (the default setting is <IP_ADDRESS>,<IP_ADDRESS>)
I was also then able to set the customUI option as well and everything else worked.

Hello, thanks for the great troubleshooting! I've tried to improve my code lately to have a 100% success on lints, and this surely has caused this issue. I'll investigate and push a new version to restore custom DNS setting. Thanks!

You were spot on. I've checked I had the same issue, corrected the dns code, and checked that it works. The new version just pushed will work with custom DNS! Once again, thanks A LOT for your great analysis!

BTW new version today, with the latest qbittorrent version. It includes the dns fix

The new version corrupted my qbittorent btw. Its not holding the config file at beginning and changed everything to /config/downloads. When changing it from the GUI it holds but after reboot its config again. Very strange.
As it now messed up my storage as i always save everything at /mnt/NAS/Downloads and not local disk.

@alexbelgium: No worries! Glad I could help :)
@deku-m: it might a good idea to make a new issue for your problem. I was planning on closing this ticket at the original issue is fixed. Plus it'll give you an opportunity to fill in the issue template with additional info.

And... That's why I had avoided updating to 4.4.0, but it seems 4.4.1 have s the same bug... I'll check but it's a probable reverse upcoming

Download folder bug fixed in new release


Extend to another type of cnc controller

Thanks @PatrickRitchie for this guide to make Haas Machine data available on MTConnect Agent using MTConnect.NET library.
In the regards of same, can I refer it as a guide to route Mitsubishi cnc data to MTConnect Agent.  I will make use of Mitsubishi communication dll libraries. Will I be able to extend this method to x number of Mitsubishi cnc machines ?

Yes you are welcome to use it as a guide for a Mitsubishi CNC and yes you can extend it as needed. Please let me know if you have any other questions.


Logical issue with expired items remainder

The feature of expiry remainder is not working properly.

This issue has been covered in #23 PR.


Logging events

Description
When using the built sendMail function, it outputs logs for different events such as errors and responses from the configured transport.
Problem
My main concern is that I'm no longer in control over which logs gets sent to and how they are transformed as the standard output is console. Many server applications uses a centralised source for handling of info/error logs and apply a standardised format, which then gets sent through different configured log transports (such as files, AWS or other).
This could also for example result in poorly managed environments unintentionally sharing PII with a third party.
Possible solutions
It should probably be up to users of this library to listen to these events and deal with it

Let users attach a custom message/error handler for events.
Place all logs behind DEBUG environment variable (this essentially disables possibilities for mailing logs in production environments)
Leave event handling to be configured on transport only

I'd love to hear what you think.

Great idea @johanolandero. I'm all for scrubbing personally identifying info from logs and letting you configure logging on the nodemailer transport (if you want).
Here's one place I see us potentially logging too much: https://github.com/sofn-xyz/mailing/blob/main/packages/core/src/index.ts#L120
Do you have examples of the logs you'd want to scrub? A screenshot with the message would be useful. I want to make sure we're considering them all.

The code you referenced was definitely the culprit in my case. Seems like the potential error logs is related to preview-stuff which is disabled in production anyway. Thanks @psugihara

awesome, thanks for filing!


Update trigger for LEAPM 6.0

Drop testing of install DVD which is no longer part of distro Instead of Install DVD we only have PackagesDVD

I think the failure comes from the deletion of xml/obs/openSUSE:Leap:Micro.xml. This file is needed IIRC.

I'll look into this this morning (after meeting marathon). Thank you folks!

The images seem to be there:
sudo -u geekotest rsync --password-file rsync.secret -4 --list-only obspublish::openqa/openSUSE:Leap:Micro:6.0:ToTest/images/x86_64/*/ | grep -E "raw$|xz$|qcow2$|vmdk$|vmx$"
-rw-r--r--    871,516,704 2024/04/10 22:50:06 openSUSE-Leap-Micro.x86_64-6.0-Base-Build7.1.raw.xz
-rw-r--r--    876,171,084 2024/04/10 22:52:57 openSUSE-Leap-Micro.x86_64-6.0-Base-SelfInstall-Build7.1.raw.xz
-rw-r--r--    884,167,888 2024/04/10 22:50:07 openSUSE-Leap-Micro.x86_64-6.0-Base-VMware-Build7.1.vmdk.xz
-rw-r--r--            513 2024/04/10 22:50:07 openSUSE-Leap-Micro.x86_64-6.0-Base-VMware-Build7.1.vmx
-rw-r--r--  4,294,967,296 2024/04/10 22:49:48 openSUSE-Leap-Micro.x86_64-6.0-Base-encrypted-Build7.1.raw
-rw-r--r--  1,041,956,864 2024/04/10 22:49:21 openSUSE-Leap-Micro.x86_64-6.0-Base-qcow-Build7.1.qcow2
-rw-r--r--  1,028,542,084 2024/04/10 22:52:06 openSUSE-Leap-Micro.x86_64-6.0-Default-Build7.1.raw.xz
-rw-r--r--  1,028,725,284 2024/04/10 22:56:03 openSUSE-Leap-Micro.x86_64-6.0-Default-SelfInstall-Build7.1.raw.xz
-rw-r--r--  1,033,338,972 2024/04/10 22:52:35 openSUSE-Leap-Micro.x86_64-6.0-Default-VMware-Build7.1.vmdk.xz
-rw-r--r--            513 2024/04/10 22:52:35 openSUSE-Leap-Micro.x86_64-6.0-Default-VMware-Build7.1.vmx
-rw-r--r--  4,294,967,296 2024/04/10 22:50:46 openSUSE-Leap-Micro.x86_64-6.0-Default-encrypted-Build7.1.raw
-rw-r--r--  1,300,365,312 2024/04/10 22:51:07 openSUSE-Leap-Micro.x86_64-6.0-Default-qcow-Build7.1.qcow2

I don't see RT  images being built
There is a new flavor Default-encrypted that needs to be added
There is a new flavor Default-qcow to be added
The old MicroOS-Image flavor should be replaced by Default
There are 2 types of images, do we want to sync also the Base flavors or just Default?

I'm not sure about content of t/obs ... I simply took 5.5 Images and bumped 5.5.0 -> 6.0, 5.5 -> 6.0 and referenced last published build 13.1

There was a mistake. RT images are only available in base flavor.
Follow-up: https://github.com/os-autoinst/openqa-trigger-from-obs/pull/247


Set TChannel port to Ringpop labels

What changed?
Membership will return enhanced Hostinfo data. Using Ringpop labels to propagate supported transport ports across hashring members.

Why?
Additional port data in Hostinfo will open easier RPC transport migrations.

How did you test it?
Unit tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build f1bac43d-69bc-41d2-89e7-2cbea19a9f10

21 of 99 (21.21%)  changed or added relevant lines in 4 files are covered.
55 unchanged lines in 12 files lost coverage.
Overall coverage increased (+0.006%) to 56.955%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/membership/hashring.go
7
10
70.0%

common/membership/hostinfo.go
12
33
36.36%

common/peerprovider/ringpopprovider/provider.go
0
54
0.0%

Files with Coverage Reduction
New Missed Lines
%

common/membership/hashring.go
1
78.08%

client/history/client.go
2
39.33%

client/history/metricClient.go
2
46.37%

common/task/fifoTaskScheduler.go
2
87.63%

common/task/weightedRoundRobinTaskScheduler.go
2
89.64%

service/history/handler.go
2
48.56%

service/matching/matcher.go
2
91.46%

service/history/task/fetcher.go
3
86.67%

service/frontend/workflowHandler.go
4
59.4%

common/persistence/nosql/nosqlExecutionStore.go
9
60.46%

Totals

Change from base Build 44b36639-36d5-40b3-9df5-aa902204e7ff:
0.006%

Covered Lines:
82973

Relevant Lines:
145682

💛  - Coveralls


ubuntu running error

@chrismattmann  I tried to run it on ubuntu, but it seems some syntax error on  bad fd number.
It probably happens because of ">&" symbol.
Try to figure out.

Ahh it's the shell my guess is you are using bash and not csh

@chrismattmann  It is not csh. It's dash....

Yeah >& only works for csh we need something that works across shells

Oh got it!!! Learned from you!!!

:+1: @dongnizh - so we should figure out a cross platform solution here.

@dongnizh check this out: http://stackoverflow.com/questions/3908063/python-subprocess-with-shell-true-redirections-and-platform-independent-subproc maybe we should use subprocess and/or popen2?

@dongnizh did you check my link out?

@chrismattmann I would like to try to change the os cmd to subprocess and see what it is going on.

+1 try that

ok @dongnizh can you confirm that #41 fixed this?

@chrismattmann What do you mean? You mean the new PR?

This is closed due to #41 .

yay thanks @dongnizh !


stop test when RCU stalls happen

I was hoping that https://github.com/cilium/tetragon/commit/88128417dd1abbea900d2fed9994f906ba570ea5 would cause a panic when an RCU stall happens, which would result in the vm being stopped since we are setting panic=-1 in the VM's kernel args: https://github.com/cilium/tetragon/blob/b8ad0ac9636c9259407f738beab99f43041aefda/cmd/tetragon-vmtests-run/qemu.go#L45
to reboot immediately. see https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt:

panic=		[KNL] Kernel behaviour on panic: delay
timeout > 0: seconds before rebooting
timeout = 0: wait forever
timeout < 0: reboot immediately
Format:

However, it does not seem to work. Run https://github.com/cilium/tetragon/runs/7868377256?check_suite_focus=true, had RCU stalls but the machine did not reboot.
kernel log:

Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
[    0.000000] Linux version 5.4.209 (root@eecd43a3ba4d) (gcc version 12.1.0 (Debian 12.1.0-7)) #1 SMP Thu Aug 4 16:31:52 UTC 2022
[    0.000000] Command line: root=/dev/sda console=ttyS0 earlyprintk=ttyS0 panic=-1
[    0.000000] x86/fpu: x87 FPU will use FXSAVE
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffdffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000013fffffff] usable
[    0.000000] printk: bootconsole [earlyser0] enabled
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.8 present.
[    0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 2095.062 MHz processor
[    0.004524] last_pfn = 0x140000 max_arch_pfn = 0x400000000
[    0.005869] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
Memory KASLR using RDTSC...
[    0.006886] last_pfn = 0xbffe0 max_arch_pfn = 0x400000000
[    0.021041] found SMP MP-table at [mem 0x000f5c80-0x000f5c8f]
[    0.023197] check: Scanning 1 areas for low memory corruption
[    0.028920] ACPI: Early table checksum verification disabled
[    0.029535] ACPI: RSDP 0x00000000000F5A50 000014 (v00 BOCHS )
[    0.029949] ACPI: RSDT 0x00000000BFFE15A2 000030 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
[    0.030912] ACPI: FACP 0x00000000BFFE1476 000074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)
[    0.031724] ACPI: DSDT 0x00000000BFFE0040 001436 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
[    0.032027] ACPI: FACS 0x00000000BFFE0000 000040
[    0.032200] ACPI: APIC 0x00000000BFFE14EA 000080 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
[    0.032407] ACPI: HPET 0x00000000BFFE156A 000038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)
[    0.032716] ACPI: Reserving FACP table memory at [mem 0xbffe1476-0xbffe14e9]
[    0.032938] ACPI: Reserving DSDT table memory at [mem 0xbffe0040-0xbffe1475]
[    0.033095] ACPI: Reserving FACS table memory at [mem 0xbffe0000-0xbffe003f]
[    0.033248] ACPI: Reserving APIC table memory at [mem 0xbffe14ea-0xbffe1569]
[    0.033400] ACPI: Reserving HPET table memory at [mem 0xbffe156a-0xbffe15a1]
[    0.036371] No NUMA configuration found
[    0.036501] Faking a node at [mem 0x0000000000000000-0x000000013fffffff]
[    0.037510] NODE_DATA(0) allocated [mem 0x13fff9000-0x13fffcfff]
[    0.041020] Zone ranges:
[    0.041175]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.041403]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.041556]   Normal   [mem 0x0000000100000000-0x000000013fffffff]
[    0.041721] Movable zone start for each node
[    0.041867] Early memory node ranges
[    0.041984]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.042258]   node   0: [mem 0x0000000000100000-0x00000000bffdffff]
[    0.042429]   node   0: [mem 0x0000000100000000-0x000000013fffffff]
[    0.044055] Zeroed struct page in unavailable ranges: 130 pages
[    0.044265] Initmem setup node 0 [mem 0x0000000000001000-0x000000013fffffff]
[    0.194375] ACPI: PM-Timer IO Port: 0x608
[    0.195162] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[    0.195786] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[    0.196095] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.196564] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[    0.196764] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.197024] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[    0.197176] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[    0.197546] Using ACPI (MADT) for SMP configuration information
[    0.197729] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.198238] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[    0.199398] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.199611] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[    0.199777] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
[    0.199918] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
[    0.200064] PM: Registered nosave memory: [mem 0xbffe0000-0xbfffffff]
[    0.200205] PM: Registered nosave memory: [mem 0xc0000000-0xfffbffff]
[    0.200345] PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
[    0.200615] [mem 0xc0000000-0xfffbffff] available for PCI devices
[    0.201266] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>391419 ns
[    0.870566] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
[    0.881357] percpu: Embedded 56 pages/cpu s190552 r8192 d30632 u1048576
[    0.885069] Built 1 zonelists, mobility grouping on.  Total pages: 1032041
[    0.885265] Policy zone: Normal
[    0.885580] Kernel command line: root=/dev/sda console=ttyS0 earlyprintk=ttyS0 panic=-1
[    0.902561] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.910582] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.912927] mem auto-init: stack:off, heap alloc:off, heap free:off
[    1.246979] Memory: 4026852K/4193784K available (12291K kernel code, 1312K rwdata, 6036K rodata, 1272K init, 2092K bss, 166932K reserved, 0K cma-reserved)
[    1.253885] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    1.265343] rcu: Hierarchical RCU implementation.
[    1.265499] rcu: 	RCU event tracing is enabled.
[    1.265641] rcu: 	RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2.
[    1.266018] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    1.266227] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    1.292085] NR_IRQS: 4352, nr_irqs: 440, preallocated irqs: 16
[    1.303950] Console: colour *CGA 80x25
[    1.305876] printk: console [ttyS0] enabled
[    1.305876] printk: console [ttyS0] enabled
[    1.331125] printk: bootconsole [earlyser0] disabled
[    1.331125] printk: bootconsole [earlyser0] disabled
[    1.332384] ACPI: Core revision 20190816
[    1.338428] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>7 ns
[    1.344281] APIC: Switch to symmetric I/O mode setup
[    1.349496] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    1.355190] tsc: Marking TSC unstable due to TSCs unsynchronized
[    1.355728] Calibrating delay loop (skipped), value calculated using timer frequency.. 4190.12 BogoMIPS (lpj=2095062)
[    1.356894] pid_max: default: 32768 minimum: 301
[    1.357962] LSM: Security Framework initializing
[    1.359068] SELinux:  Initializing.
[    1.360197] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    1.360491] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
Poking KASLR using RDTSC...
[    1.384884] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    1.385071] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    1.385527] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    1.385826] Spectre V2 : Mitigation: Retpolines
[    1.385950] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    1.386202] Speculative Store Bypass: Vulnerable
[    1.393236] Freeing SMP alternatives memory: 36K
[    1.511458] smpboot: CPU0: AMD QEMU Virtual CPU version 2.5+ (family: 0x6, model: 0x6, stepping: 0x3)
[    1.519234] Performance Events: PMU not available due to virtualization, using software events only.
[    1.521656] rcu: Hierarchical SRCU implementation.
[    1.525060] Huh? What family is it: 0x6?!
[    1.527094] smp: Bringing up secondary CPUs ...
[    1.530647] x86: Booting SMP configuration:
[    1.530831] .... node  #0, CPUs:      #1
[    1.607651] smp: Brought up 1 node, 2 CPUs
[    1.607955] smpboot: Max logical packages: 2
[    1.608132] smpboot: Total of 2 processors activated (8380.92 BogoMIPS)
[    1.626557] devtmpfs: initialized
[    1.637003] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>275000 ns
[    1.637438] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    1.641458] PM: RTC time: 22:46:03, date: 2022-08-16
[    1.648145] NET: Registered protocol family 16
[    1.651120] audit: initializing netlink subsys (disabled)
[    1.653058] audit: type=2000 audit(1660689963.309:1): state=initialized audit_enabled=0 res=1
[    1.660128] cpuidle: using governor menu
[    1.661768] ACPI: bus type PCI registered
[    1.664306] PCI: Using configuration type 1 for base access
[    1.667834] mtrr: your CPUs had inconsistent fixed MTRR settings
[    1.668253] mtrr: your CPUs had inconsistent variable MTRR settings
[    1.668513] mtrr: your CPUs had inconsistent MTRRdefType settings
[    1.668782] mtrr: probably your BIOS does not setup all CPUs.
[    1.669015] mtrr: corrected configuration.
[    1.688118] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    1.693411] cryptomgr_test (26) used greatest stack depth: 15520 bytes left
[    1.694755] cryptomgr_test (28) used greatest stack depth: 15216 bytes left
[    1.706128] ACPI: Added _OSI(Module Device)
[    1.706518] ACPI: Added _OSI(Processor Device)
[    1.706641] ACPI: Added _OSI(3.0 _SCP Extensions)
[    1.706776] ACPI: Added _OSI(Processor Aggregator Device)
[    1.707114] ACPI: Added _OSI(Linux-Dell-Video)
[    1.707233] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    1.707480] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    1.724336] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    1.742197] ACPI: Interpreter enabled
[    1.743305] ACPI: (supports S0 S3 S4 S5)
[    1.743495] ACPI: Using IOAPIC for interrupt routing
[    1.744110] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    1.746117] ACPI: Enabled 2 GPEs in block 00 to 0F
[    1.785458] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    1.786271] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3]
[    1.787565] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
[    1.790349] PCI host bridge to bus 0000:00
[    1.790658] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    1.790870] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    1.791081] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    1.791251] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
[    1.791428] pci_bus 0000:00: root bus resource [mem 0x140000000-0x1bfffffff window]
[    1.791458] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.792028] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
[    1.797398] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
[    1.798726] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
[    1.803096] pci 0000:00:01.1: reg 0x20: [io  0xc080-0xc08f]
[    1.804969] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
[    1.805544] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
[    1.805963] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
[    1.806505] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
[    1.808007] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
[    1.809206] pci 0000:00:01.3: quirk: [io  0x0600-0x063f] claimed by PIIX4 ACPI
[    1.809545] pci 0000:00:01.3: quirk: [io  0x0700-0x070f] claimed by PIIX4 SMB
[    1.811906] pci 0000:00:02.0: [1af4:1003] type 00 class 0x078000
[    1.813039] pci 0000:00:02.0: reg 0x10: [io  0xc000-0xc03f]
[    1.814519] pci 0000:00:02.0: reg 0x14: [mem 0xfebfe000-0xfebfefff]
[    1.820458] pci 0000:00:02.0: reg 0x20: [mem 0xfebf4000-0xfebf7fff 64bit pref]
[    1.823667] pci 0000:00:03.0: [1af4:1009] type 00 class 0x000200
[    1.825113] pci 0000:00:03.0: reg 0x10: [io  0xc040-0xc07f]
[    1.827114] pci 0000:00:03.0: reg 0x14: [mem 0xfebff000-0xfebfffff]
[    1.832512] pci 0000:00:03.0: reg 0x20: [mem 0xfebf8000-0xfebfbfff 64bit pref]
[    1.841799] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[    1.842889] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[    1.843664] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[    1.844363] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[    1.844458] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
[    1.847623] iommu: Default domain type: Translated
[    1.852238] vgaarb: loaded
[    1.854492] SCSI subsystem initialized
[    1.857110] pps_core: LinuxPPS API ver. 1 registered
[    1.857277] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    1.857504] PTP clock support registered
[    1.858707] EDAC MC: Ver: 3.0.0
[    1.862008] PCI: Using ACPI for IRQ routing
[    1.871320] NetLabel: Initializing
[    1.871491] NetLabel:  domain hash size = 128
[    1.871615] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    1.873394] NetLabel:  unlabeled traffic allowed by default
[    1.873892] hpet: 3 channels of 0 reserved for per-cpu timers
[    1.874531] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    1.874732] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[    1.879053] clocksource: Switched to clocksource hpet
[    2.362741] VFS: Disk quotas dquot_6.6.0
[    2.363155] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    2.366396] pnp: PnP ACPI init
[    2.372577] pnp: PnP ACPI: found 5 devices
[    2.399005] thermal_sys: Registered thermal governor 'step_wise'
[    2.399124] thermal_sys: Registered thermal governor 'user_space'
[    2.404190] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns:<PHONE_NUMBER> ns
[    2.405451] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    2.405640] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    2.405793] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    2.405925] pci_bus 0000:00: resource 7 [mem 0xc0000000-0xfebfffff window]
[    2.405925] pci_bus 0000:00: resource 8 [mem 0x140000000-0x1bfffffff window]
[    2.407555] NET: Registered protocol family 2
[    2.409401] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    2.416761] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    2.417266] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    2.418156] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
[    2.420332] TCP: Hash tables configured (established 32768 bind 32768)
[    2.421963] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    2.422467] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    2.424405] NET: Registered protocol family 1
[    2.428307] RPC: Registered named UNIX socket transport module.
[    2.428498] RPC: Registered udp transport module.
[    2.428498] RPC: Registered tcp transport module.
[    2.428498] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.428498] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[    2.428498] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[    2.428498] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[    2.428498] PCI: CLS 0 bytes, default 64
[    2.435083] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    2.435344] software IO TLB: mapped [mem 0xbbfe0000-0xbffe0000] (64MB)
[    2.442439] check: Scanning for low memory corruption every 60 seconds
[    2.446989] Initialise system trusted keyrings
[    2.449113] workingset: timestamp_bits=56 max_order=20 bucket_order=0
[    2.466969] NFS: Registering the id_resolver key type
[    2.467488] Key type id_resolver registered
[    2.467507] Key type id_legacy registered
[    2.468727] 9p: Installing v9fs 9p2000 file system support
[    2.489442] Key type asymmetric registered
[    2.489756] Asymmetric key parser 'x509' registered
[    2.490129] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    2.490449] io scheduler mq-deadline registered
[    2.490629] io scheduler kyber registered
[    2.496009] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[    2.500183] ACPI: Power Button [PWRF]
[    2.681640] PCI Interrupt Link [LNKB] enabled at IRQ 10
[    2.858684] PCI Interrupt Link [LNKC] enabled at IRQ 11
[    2.861703] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    2.885329] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    2.891386] Non-volatile memory driver v1.3
[    2.919654] loop: module loaded
[    2.930417] scsi host0: ata_piix
[    2.933292] scsi host1: ata_piix
[    2.934384] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc080 irq 14
[    2.934634] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc088 irq 15
[    2.936280] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    2.939430] e100: Copyright(c) 1999-2006 Intel Corporation
[    2.940372] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    2.940372] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    2.940372] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    2.940372] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    2.940372] sky2: driver version 1.30
[    2.947367] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[    2.951798] serio: i8042 KBD port at 0x60,0x64 irq 1
[    2.952383] serio: i8042 AUX port at 0x60,0x64 irq 12
[    2.956977] rtc_cmos 00:00: RTC can wake from S4
[    2.960877] rtc_cmos 00:00: registered as rtc0
[    2.961915] rtc_cmos 00:00: alarms up to one day, y3k, 114 bytes nvram, hpet irqs
[    2.963600] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised<EMAIL_ADDRESS>[    2.974671] Initializing XFRM netlink socket
[    2.976387] NET: Registered protocol family 10
[    2.984968] Segment Routing with IPv6
[    2.988651] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.992276] NET: Registered protocol family 17
[    2.994448] 9pnet: Installing 9P2000 support
[    3.001046] Key type dns_resolver registered
[    3.003336] IPI shorthand broadcast: enabled
[    3.004810] registered taskstats version 1
[    3.004958] Loading compiled-in X.509 certificates
[    3.010127] PM:   Magic number: 2:785:805
[    3.010896] printk: console [netcon0] enabled
[    3.011094] netconsole: network logging started
[    3.014331] Unstable clock detected, switching default tracing clock to "global"
[    3.014331] If you want to keep using the local clock, then add:
[    3.014331]   "trace_clock=local"
[    3.014331] on the kernel command line
[    4.409171] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[   22.853587] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   22.854256] rcu: 	1-...!: (0 ticks this GP) idle=ca4/0/0x0 softirq=20/20 fqs=0
[   22.854496] 	(detected by 0, t=21002 jiffies, g=-1139, q=39)
[   22.854496] Sending NMI from CPU 0 to CPUs 1:
[   22.859421] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[   22.859546] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.120 msecs
[   22.854496] rcu: rcu_sched kthread starved for 21002 jiffies! g-1139 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[   22.854496] rcu: RCU grace-period kthread stack dump:
[   22.854496] rcu_sched       I15016    11      2 0x80004000
[   22.854496] Call Trace:
[   22.854496]  __schedule+0x288/0x600
[   22.854496]  ? __mod_timer+0x1a6/0x3c0
[   22.854496]  schedule+0x34/0xa0
[   22.854496]  schedule_timeout+0x84/0x140
[   22.854496]  ? __next_timer_interrupt+0xc0/0xc0
[   22.854496]  rcu_gp_kthread+0x4f6/0xd40
[   22.854496]  ? kfree_call_rcu+0x10/0x10
[   22.854496]  kthread+0x107/0x120
[   22.854496]  ? __kthread_bind_mask+0x60/0x60
[   22.854496]  ret_from_fork+0x35/0x40
[   43.855505] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   43.855976] rcu: 	1-...!: (0 ticks this GP) idle=cc0/0/0x0 softirq=20/20 fqs=0
[   43.856153] 	(detected by 0, t=21002 jiffies, g=-1135, q=37)
[   43.856314] Sending NMI from CPU 0 to CPUs 1:
[   43.856538] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[   43.856486] rcu: rcu_sched kthread starved for 21002 jiffies! g-1135 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[   43.856486] rcu: RCU grace-period kthread stack dump:
[   43.856486] rcu_sched       I15016    11      2 0x80004000
[   43.856486] Call Trace:
[   43.856486]  __schedule+0x288/0x600
[   43.856486]  ? __mod_timer+0x1a6/0x3c0
[   43.856486]  schedule+0x34/0xa0
[   43.856486]  schedule_timeout+0x84/0x140
[   43.856486]  ? __next_timer_interrupt+0xc0/0xc0
[   43.856486]  rcu_gp_kthread+0x4f6/0xd40
[   43.856486]  ? kfree_call_rcu+0x10/0x10
[   43.856486]  kthread+0x107/0x120
[   43.856486]  ? __kthread_bind_mask+0x60/0x60
[   43.856486]  ret_from_fork+0x35/0x40
[   64.857512] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   64.857740] rcu: 	1-...!: (0 ticks this GP) idle=cdc/0/0x0 softirq=20/20 fqs=0
[   64.857913] 	(detected by 0, t=21002 jiffies, g=-1131, q=37)
[   64.858070] Sending NMI from CPU 0 to CPUs 1:
[   64.858282] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[   64.858488] rcu: rcu_sched kthread starved for 21002 jiffies! g-1131 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[   64.858488] rcu: RCU grace-period kthread stack dump:
[   64.858488] rcu_sched       I15016    11      2 0x80004000
[   64.858488] Call Trace:
[   64.858488]  __schedule+0x288/0x600
[   64.858488]  ? __mod_timer+0x1a6/0x3c0
[   64.858488]  schedule+0x34/0xa0
[   64.858488]  schedule_timeout+0x84/0x140
[   64.858488]  ? __next_timer_interrupt+0xc0/0xc0
[   64.858488]  rcu_gp_kthread+0x4f6/0xd40
[   64.858488]  ? kfree_call_rcu+0x10/0x10
[   64.858488]  kthread+0x107/0x120
[   64.858488]  ? __kthread_bind_mask+0x60/0x60
[   64.858488]  ret_from_fork+0x35/0x40
[  103.087243] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  103.087558] rcu: 	1-...!: (0 ticks this GP) idle=cf8/0/0x0 softirq=20/20 fqs=0
[  103.087821] 	(detected by 0, t=38227 jiffies, g=-1127, q=10)
[  103.088024] Sending NMI from CPU 0 to CPUs 1:
[  103.088684] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  103.088153] rcu: rcu_sched kthread starved for 38227 jiffies! g-1127 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  103.088153] rcu: RCU grace-period kthread stack dump:
[  103.088153] rcu_sched       I15016    11      2 0x80004000
[  103.088153] Call Trace:
[  103.088153]  __schedule+0x288/0x600
[  103.088153]  ? __mod_timer+0x1a6/0x3c0
[  103.088153]  schedule+0x34/0xa0
[  103.088153]  schedule_timeout+0x84/0x140
[  103.088153]  ? __next_timer_interrupt+0xc0/0xc0
[  103.088153]  rcu_gp_kthread+0x4f6/0xd40
[  103.088153]  ? kfree_call_rcu+0x10/0x10
[  103.088153]  kthread+0x107/0x120
[  103.088153]  ? __kthread_bind_mask+0x60/0x60
[  103.088153]  ret_from_fork+0x35/0x40
[  182.556239] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  182.556604] rcu: 	1-...!: (0 ticks this GP) idle=d0c/0/0x0 softirq=20/20 fqs=1
[  182.556906] 	(detected by 0, t=117696 jiffies, g=-1127, q=10)
[  182.557153] Sending NMI from CPU 0 to CPUs 1:
[  182.559019] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  182.557153] rcu: rcu_sched kthread starved for 79461 jiffies! g-1127 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  182.557153] rcu: RCU grace-period kthread stack dump:
[  182.557153] rcu_sched       I15016    11      2 0x80004000
[  182.557153] Call Trace:
[  182.557153]  __schedule+0x288/0x600
[  182.557153]  ? __mod_timer+0x1a6/0x3c0
[  182.557153]  schedule+0x34/0xa0
[  182.557153]  schedule_timeout+0x84/0x140
[  182.557153]  ? __next_timer_interrupt+0xc0/0xc0
[  182.557153]  rcu_gp_kthread+0x4f6/0xd40
[  182.557153]  ? kfree_call_rcu+0x10/0x10
[  182.557153]  kthread+0x107/0x120
[  182.557153]  ? __kthread_bind_mask+0x60/0x60
[  182.557153]  ret_from_fork+0x35/0x40
[  334.112602] kworker/dying (5) used greatest stack depth: 15208 bytes left
[  355.114517] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  355.114827] rcu: 	1-...!: (0 ticks this GP) idle=d28/0/0x0 softirq=20/20 fqs=0
[  355.114999] 	(detected by 0, t=21002 jiffies, g=-1123, q=12)
[  355.115193] Sending NMI from CPU 0 to CPUs 1:
[  355.115430] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  355.115489] rcu: rcu_sched kthread starved for 21002 jiffies! g-1123 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  355.115489] rcu: RCU grace-period kthread stack dump:
[  355.115489] rcu_sched       I15016    11      2 0x80004000
[  355.115489] Call Trace:
[  355.115489]  __schedule+0x288/0x600
[  355.115489]  ? __mod_timer+0x1a6/0x3c0
[  355.115489]  schedule+0x34/0xa0
[  355.115489]  schedule_timeout+0x84/0x140
[  355.115489]  ? __next_timer_interrupt+0xc0/0xc0
[  355.115489]  rcu_gp_kthread+0x4f6/0xd40
[  355.115489]  ? kfree_call_rcu+0x10/0x10
[  355.115489]  kthread+0x107/0x120
[  355.115489]  ? __kthread_bind_mask+0x60/0x60
[  355.115489]  ret_from_fork+0x35/0x40
[  376.116517] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  376.117044] rcu: 	1-...!: (0 ticks this GP) idle=d48/0/0x0 softirq=20/20 fqs=0
[  376.117250] 	(detected by 0, t=21002 jiffies, g=-1119, q=11)
[  376.117432] Sending NMI from CPU 0 to CPUs 1:
[  376.117645] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  376.117497] rcu: rcu_sched kthread starved for 21002 jiffies! g-1119 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  376.117497] rcu: RCU grace-period kthread stack dump:
[  376.117497] rcu_sched       I15016    11      2 0x80004000
[  376.117497] Call Trace:
[  376.117497]  __schedule+0x288/0x600
[  376.117497]  ? __mod_timer+0x1a6/0x3c0
[  376.117497]  schedule+0x34/0xa0
[  376.117497]  schedule_timeout+0x84/0x140
[  376.117497]  ? __next_timer_interrupt+0xc0/0xc0
[  376.117497]  rcu_gp_kthread+0x4f6/0xd40
[  376.117497]  ? kfree_call_rcu+0x10/0x10
[  376.117497]  kthread+0x107/0x120
[  376.117497]  ? __kthread_bind_mask+0x60/0x60
[  376.117497]  ret_from_fork+0x35/0x40
[  397.118507] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  397.118932] rcu: 	1-...!: (0 ticks this GP) idle=d64/0/0x0 softirq=20/20 fqs=0
[  397.119124] 	(detected by 0, t=21002 jiffies, g=-1115, q=11)
[  397.119285] Sending NMI from CPU 0 to CPUs 1:
[  397.119499] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  397.119488] rcu: rcu_sched kthread starved for 21002 jiffies! g-1115 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  397.119488] rcu: RCU grace-period kthread stack dump:
[  397.119488] rcu_sched       I15016    11      2 0x80004000
[  397.119488] Call Trace:
[  397.119488]  __schedule+0x288/0x600
[  397.119488]  ? __mod_timer+0x1a6/0x3c0
[  397.119488]  schedule+0x34/0xa0
[  397.119488]  schedule_timeout+0x84/0x140
[  397.119488]  ? __next_timer_interrupt+0xc0/0xc0
[  397.119488]  rcu_gp_kthread+0x4f6/0xd40
[  397.119488]  ? kfree_call_rcu+0x10/0x10
[  397.119488]  kthread+0x107/0x120
[  397.119488]  ? __kthread_bind_mask+0x60/0x60
[  397.119488]  ret_from_fork+0x35/0x40
[  418.120507] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  418.120740] rcu: 	1-...!: (0 ticks this GP) idle=d80/0/0x0 softirq=20/20 fqs=0
[  418.120912] 	(detected by 0, t=21002 jiffies, g=-1111, q=11)
[  418.121066] Sending NMI from CPU 0 to CPUs 1:
[  418.121399] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  418.121486] rcu: rcu_sched kthread starved for 21002 jiffies! g-1111 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  418.121486] rcu: RCU grace-period kthread stack dump:
[  418.121486] rcu_sched       I15016    11      2 0x80004000
[  418.121486] Call Trace:
[  418.121486]  __schedule+0x288/0x600
[  418.121486]  ? __mod_timer+0x1a6/0x3c0
[  418.121486]  schedule+0x34/0xa0
[  418.121486]  schedule_timeout+0x84/0x140
[  418.121486]  ? __next_timer_interrupt+0xc0/0xc0
[  418.121486]  rcu_gp_kthread+0x4f6/0xd40
[  418.121486]  ? kfree_call_rcu+0x10/0x10
[  418.121486]  kthread+0x107/0x120
[  418.121486]  ? __kthread_bind_mask+0x60/0x60
[  418.121486]  ret_from_fork+0x35/0x40
[  451.528232] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  451.528613] rcu: 	1-...!: (0 ticks this GP) idle=d9c/0/0x0 softirq=20/20 fqs=0
[  451.528922] 	(detected by 0, t=33407 jiffies, g=-1107, q=10)
[  451.529147] Sending NMI from CPU 0 to CPUs 1:
[  451.532987] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  451.529147] rcu: rcu_sched kthread starved for 33407 jiffies! g-1107 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  451.529147] rcu: RCU grace-period kthread stack dump:
[  451.529147] rcu_sched       I15016    11      2 0x80004000
[  451.529147] Call Trace:
[  451.529147]  __schedule+0x288/0x600
[  451.529147]  ? __mod_timer+0x1a6/0x3c0
[  451.529147]  schedule+0x34/0xa0
[  451.529147]  schedule_timeout+0x84/0x140
[  451.529147]  ? __next_timer_interrupt+0xc0/0xc0
[  451.529147]  rcu_gp_kthread+0x4f6/0xd40
[  451.529147]  ? kfree_call_rcu+0x10/0x10
[  451.529147]  kthread+0x107/0x120
[  451.529147]  ? __kthread_bind_mask+0x60/0x60
[  451.529147]  ret_from_fork+0x35/0x40
[  532.081249] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  532.081510] rcu: 	1-...!: (0 ticks this GP) idle=db0/0/0x0 softirq=20/20 fqs=1
[  532.081735] 	(detected by 0, t=113960 jiffies, g=-1107, q=10)
[  532.081927] Sending NMI from CPU 0 to CPUs 1:
[  532.082983] NMI backtrace for cpu 1 skipped: idling at default_idle+0x1e/0x130
[  532.082138] rcu: rcu_sched kthread starved for 80545 jiffies! g-1107 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[  532.082138] rcu: RCU grace-period kthread stack dump:
[  532.082138] rcu_sched       I15016    11      2 0x80004000
[  532.082138] Call Trace:
[  532.082138]  __schedule+0x288/0x600
[  532.082138]  ? __mod_timer+0x1a6/0x3c0
[  532.082138]  schedule+0x34/0xa0
[  532.082138]  schedule_timeout+0x84/0x140
[  532.082138]  ? __next_timer_interrupt+0xc0/0xc0
[  532.082138]  rcu_gp_kthread+0x4f6/0xd40
[  532.082138]  ? kfree_call_rcu+0x10/0x10
[  532.082138]  kthread+0x107/0x120
[  532.082138]  ? __kthread_bind_mask+0x60/0x60
[  532.082138]  ret_from_fork+0x35/0x40

Switching to heaver machines, eliminated this issue. Closing.


[rexster/gremlin] Can not query any vertices after addVertex()

The original question can be found in this thread:
https://groups.google.com/forum/#!topic/orient-database/6s2Rr5u3uiQ

Environment
OrientDB: 1.7.3
Rexster: 2.5.0

Description
Using gremlin through Rexster console (i.e. Rexpro protocol),

Add one new vertex using "graph.addVertex()".
Then, query the other existing (not-changed) vertex than the new one, but null is returned.

Example

rexster[groovy]> g = rexster.getGraph('m_test0')
==>orientgraph[remote:localhost/m_test0]

## Successful query (User.uid == 1)
rexster[groovy]> user_1 = g.query().labels('User').has('uid', 1).vertices().toList()[0]
==>v(User)[#142:0]

## Add one vertex (User.uid == 3)
rexster[groovy]> new_user = g.addVertex('class:User', 'uid', 3, 'nickname', 'mago')
==>v(User)[#140:-2]

## Can not query the other vertex (User.uid == 1) than the new one. What's wrong ?
rexster[groovy]> user_1_again = g.query().labels('User').has('uid', 1).vertices().toList()[0]
==>null

## Also, can not query the other existing vertex (User.uid == 2).
rexster[groovy]> user_2 = g.query().labels('User').has('uid', 2).vertices().toList()[0]
==>null

rexster[groovy]> g.commit()
==>null

## Even after commit(), all query fails.
rexster[groovy]> user_1_again = g.query().labels('User').has('uid', 1).vertices().toList()[0]
==>null

rexster[groovy]> user_3 = g.query().labels('User').has('uid', 1).vertices().toList()[0]
==>null

Even if I use "g.V('@class', 'User').has('uid', 1)" instead of "g.query().labels('User')", same result.

The issue has been closed because no response has been received after a while. In case the issue is still valid, please reopen it or write a comment that explains why it's still valid and a way to reproduce it. Thank you.


Transition Component does not end transition on from-to-class when setting class properties

Vue version
3.2.45
Link to minimal reproduction
https://sfc.vuejs.org/#eNp9Ul1P3DAQ/CuWpYpWInFKy0saEP0PffRLLtlwpv6SvQmcTvffWdu5cIDEm3dmPONd75H/9b5eZuAt7+IQlEcWAWd/L60y3gVkRxZgYic2BWfYFUmvpJV2cDaSdO+e2V0SfMcwww9pO1Fc6D4VCMbrHoEqxrp/oCFboruTfOfGg+QrE3obFSpnWe899IGBRQhVyqwG3cdIF1Ih+cr0A6oFNq6UG4tuY9CtIRQzqoUtlZoSTM8l+Vk1OGOcJeB+D1q7TpC0PE28ve1sI86NENCJix6pjHjQ6VgXR3ZMd7wrBi2b1AuMfxKmYcKWNfkc1ON+K0YVye9AWg0vGXmaI6rpUNHMkfpr2ZC7JO5EQflfcszOITrTsupn03xbWXTvuduNKSMrLG49tqzXOqe+YdU4h76QN03TmFgc6Ktzs/yal1WpTO/rp+gsLVO2lSsRJW9LUMJohVIt+R7Rx1aI2fr/j2lg4oE4EWaLykA1OvPwq76pf9/Sb0S8xGuIptoF9xwhUKLk1xfmgsCFliCAHSFA+DLsg/Zd4AfuU2jKpDmc+OkVZ2gjKg==
Steps to reproduce
on load transition does not end on from-to-class
What is expected?
transition stops mid screen
What is actually happening?
to class removed on transition end
System Info
using SFC playground
chrome macos

Any additional comments?
No response

please refer to https://vuejs.org/guide/built-ins/transition.html#css-based-transitions
modify minimal reproduction:
https://sfc.vuejs.org/#eNp9Ustu2zAQ/BWCQJEWiEQ1bS6qEqT/0CMvtLSKmfIFcqXEMPzvWZK24yRAbpyZ3RkuuXv+N4R2XYD3fEhj1AFZAlzCvXTaBh+R7VmEmR3YHL1lV1R6JZ10o3eJSrf+md3lgu8YF/gh3SCqC/UTQLDBKARCjA3/wECxRH8n+cZPO8mLkrWoXNKovWMqBFCRgUOITU5tRqNSopYMJD8qakS9wlmr8GxIlpNe2dromcR8OWo81Y7eWu+IuN+CMX4QVHq6iHi7SaWIOd6b8CAuRiKYcGfysa2WbJ9bgq/9PZv1C0x/Mmdgxp515Rz14/YMJp3Ib0e1Bl4K87Qk1POuoSdGGrVnYxm4aBuP6G3PbrtvhA8UXL6lxJ605md3Ukmv71Ir8Dxaz5QxxfGNa6YlqiredF1nU/WgHy1D8mteN6KxKrRPyTvamWIrj0KSvK9BmaNNyVjyLWJIvRCLC/8f80OJB9JEXBxqC83k7cOv9qb9fUvfkPCSbyHZZhP9c4JIiZJfX5gLIlfagwhuggjxy7APte8CP2ifQnMmvcOBH14BE2gZKg==

i still dont think its working. It only happens to work due to the css ordering. Actually both classes are applied. if i take your example and move the .from class above the .common class it doesnt work again. Thats important because you might not have control over the ordering of css eg tailwind
https://sfc.vuejs.org/#eNp9Uttu2zAM/RVCwNANqC/r1hfPLbp/2KNeHJtu1OkGiXYbBPn3UlKSpi1Q+MXkOTyHpLgXf72v1wVFJ/o4BuUJItLi76VVxrtAsIeAMxxgDs7AFVOvpJV2dDYydeue4S4RvlNY8Ie0fVNUuJ4DQuP1QMgRQP8PNWZJcndSbNy0kyIjCQuDjYqUszB4j0MAtIShSq7VqIcYuSQFUhyRYSS14hkr4VmQJSe1wlqpmcHUHBeeuKMzxllO3G9Ra9c3TD010rx1UlKcOfbNcd9cjMRhpJ0u09V5P/v0u3FEznRQ/Wzbb3+kPUhbF8uCe1f0O5jVC07MANA4Uwdt/g/qcXsOJhXZb8dcjS8587REUvOu4icgXkUHY15Ixk7Wtyfj9NVlN8WczuN1MGidq95y1bSEoYA3bduaWFT4VfOg4lqUq6jM4Oun6CzfTZaVRyBK0RWjlONrSbEUWyIfu6ZZrP//mJbRPDDWhMWSMlhNzjz8qm/q37f8FJEu8zVGU22Ce44Y2FGK6wvxhpMr30JAO2HA8KXZB+47ww/YJ9PkyXs4iMMrfeQaNA==

enter-to-class is  not applied continuously, only for a tick at the end. the proposed solution is correct. If you have CSS order issues, make the from class of higher specificity. And yes, with tailwind that means you would have to create a class with @apply in this specific case. In others, whe the transitioned value is inherited/default (i.e. opacity: 1, you would not have to do that.

Okay. Thanks for your explanation. Feels like it needs one more css class for after like
from-class, from-to-class, "from-to-after". Im not sure the point of from-to-class removing on transition end but yeah relying on css specificity for Transition component is not ideal.
The actual use case is a slide up menu from the bottom of the screen in mobile view


Groll diff

Should be very helpful. It should print the diff between the prev state.

I usually prefer to use the GitHub application to inspect larger changes, but hey, PRs are welcome ;-)

Closing, because no more activity.


Added textAppearance property for TextView

Really? About which branch are you talking about? I've checked out master, and it doesn't seem to have one: https://github.com/Kotlin/anko/blob/master/anko/library/generated/sdk23/src/Properties.kt
Btw, what's the purpose of these packages ending with sdk number?

I've founded it here: https://github.com/Kotlin/anko/blob/8f8a6c7485fab9c8492f2ccfd5cecb97e3ce7f30/anko/library/static/platform/src/CustomViewProperties.kt
but still I have no clue why you added to sdk25, not to sdk23/src/Properties.kt... You're checking if there is M or higher Android version, right?

Well yes, your are absolutely correct, I should've added it in sdk-23. Actually, I shouldn't have added it since it is already in master, it is just not released in new version yet.


[Hold for payment 2022-12-20] Priority Mode options is not changing to selected language

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to Settings - Preference - Change language to Spanish/English
Observe Priority Mode Value

Expected Result:
Priority Mode Value should be changed to selected language
Actual Result:
Priority Mode Value is not changing to selected language
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.2.36-1
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/205735622-153a1a21-052c-4633-b29a-74cbcfe9280e.mov

Expensify/Expensify Issue URL:
Issue reported by: @varshamb
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1670258478133289
View all open jobs on GitHub

I'll work on this one

Introduced here, moving the logic to the constructor prevents the component from updating. I'll work on a fix tomorrow morning.

@slafortune I believe the only thing left here is the reporting bonus payment to @varshamb. Could you please help with that?

Created regression test issue here. Only missing payment now.

Bump for payment

Shoot!  Sorry for missing this - on it now!

Apologies @aimane-chnaif , needed to add Internal label to get get job created (this is an edge case and shouldn't continue to happen)
@varshamb can you please accept the job and reply here once you have?
https://www.upwork.com/jobs/~01a252bf33ccff5da7

Apologies @aimane-chnaif , needed to add Internal label to get get job created (this is an edge case and shouldn't continue to happen)
@varshamb can you please accept the job and reply here once you have? https://www.upwork.com/jobs/~01a252bf33ccff5da7

@varshamb can you please accept the job and reply here once you have?

Accepted!

Thanks @varshamb ! Paid!


Merge google -> main

79962b89 Merge pull request #2650 from rsuderman:main-to-google
36b257bc Synchronize submodules
39e93284 Integrate TF at tensorflow/tensorflow@63b8670dae81
8ce0251a Synchronize submodules
79ececc1 Integrate LLVM at llvm/llvm-project@f7ffb122d08e
4f5117eb Synchronize submodules
4bc8f2cf Integrate LLVM at llvm/llvm-project@9d2da6759b4d

LGTM. I think the integration failure is a known issue.

Yup, checked with Geoffrey :P


add checks for args

Idk why u didn't add them in the first place...
I added for these commands -

pyre i/install
pyre uninstall

added checks for the rest of the commands

Cool! Thanks a lot for the PR