camera follow

The camera should follow the player and always view from behind. Since you are playing from a 3rd person perspective it's hard to look 'forward' and see where the player is going to move.

Almost done fixing this issue. Closing for now and adding a new issue for clockwise/counter-clockwise rotation.

Issue for CW/CCW is #2


#if STDEXEC_MSVC() && _MSC_VER >= 1939 should read _MSC_VER < 1939

Just from reading the code and the comment following this line:
https://github.com/NVIDIA/stdexec/blob/main/include/stdexec/coroutine.hpp#L21

Great catch!


Rename a file

This was bugging me doing the FAR work so I had fixed it there, starting the process of reconciling that branch with the dev branch.

Travis failures are unrelated


Requests to /mempool

According to rosetta's docs:

Mempool Endpoints are used to fetch any data stored in the mempool...

The related api call available on Lotus is:
// MpoolPending returns pending mempool messages
MpoolPending(context.Context, types.TipSetKey) ([]*types.SignedMessage, error)

Which needs as input parameter a TipSetKey, which seems to be incompatible with the proper request for this endpoint:
type MempoolRequest struct {
	NetworkIdentifier *NetworkIdentifier `json:"network_identifier"
}

We already discussed this but copying to document it.
It should be possible to do this internally with a combination of Lotus calls, i.e. a) request the latest TipSets, then b) use those to call MpoolPending. This should consider Filecoin's tx execution model.


Added typescript lib interface + Airbnb Eslint addition and fixes

Added Typescript lib interface (index.d.ts)
Added Airbnb Eslint configs and recommendations.
Auto fixed many lint errors
Removed NodeJS v8 testing from Travis
Added instructions for testing
Tests now require a password when running locally (While still the same when running on Travis) I did that because both dbs refused to connect locally without a password
Auto lint both examples
Moved many functions out of the lib's main closure, to make the code more clear and enforce the purity of these functions. Only the Store class is what remains in the closure (Because it requires the session object)
Added knex to main dependencies instead of dev dependencies.

Please squash my commits when merging, because some commits were more or less reverted and will confuse whoever looks back at them.

Also, I think we should create a src folder and split index.js into more than one file because it's a bit confusing with all the functions there. I thought it would be best to wait until you review this already big PR.

@omarryhan well done.

@omarryhan sorry I didn't seen your MR sooner. notifications can get rather cluttered on github :(

It's alright :)

Hey @llambda ,
Sorry to bother you again. Turns out there was a bug in this PR. Someone made a PR with a fix here. I merged it, then pushed a couple of other code organization chores and we're ready for a new release. Just thought I'd notify you with a ping, in case the notification didn't reach you.

Many thanks !!


share manager: update status to error if unable to re-mount volume

Longhorn/longhorn#7183

After rethinking the solution, we can apply the fix.
The network unreachable error is rare, because share-manager resource and pod are on the same node. A network error is usually caused by an unrecoverable gRPC error, so setting the share-manager to error and triggering share-manager restart should be fine.

@Mergify backport v1.4.x v1.5.x


Added  property "slick.isTriggeredAutomatically" in event handlers to…

Hi! This PR refers to my issue https://github.com/kenwheeler/slick/issues/2212
Usage is the same as I described above
$('.my-slider').slick({
    autoplay: true,
    autoplaySpeed: 1000,
    dots: true
}).on('afterChange', function (event, slick, currentSlide) {
    if (!slick.isTriggeredAutomatically) {
        // slider was run by user, do something!
    }
});

Firstly, thanks for the PR; it looks very straightforward and sensible. Detecting autoplay changes seems to be a recurrent use case and it's not easy to do as is.
Typically with PRs we ask that you include some test cases, but in this is low impact enough that it's more a formality. Whipped one up with your fork just the same.
I was apprehensive that this would only work in conjunction with the beforeChange event and not afterChange, thinking that autoPlayClear() would run before afterChange got triggered, but turns out it's subsequent; so all good there.
Basically, it seems good to me, but @simeydotme or @kenwheeler will be the final verdict.
The following is mostly just for reference:
I think this satisfies all the use cases I've heard relating to trigger source identification, but in other issues on the subject people have suggested the possibility of specifically identifying the source. In assembling a list of things that cause slide changes, it occurs to me that the list is both sprawling and the implementation would complicate things a good deal; so I don't actually think it needs to be piggybacked here, but I'll include it at the end for reference purposes.
If this were to be done, my thinking is the new key in the global slick object would be called something like slideChangedBy instead of isTriggeredAutomatically, maybe default to init or something. Have to be careful about properly sequencing in relation to events. Possibly a bit messy.
UI Events:

autoplay
swipe
drag
arrow-left
arrow-right
slide-select
dot-select

Public Methods:

slickNext()
slickPrev()
slickGoTo()
slickAdd()
slickRemove()
slickFliter()
slickUnfliter()

Was thinking about including setOptions() but it struck me as a crazy thing to try to fuss with the overlap it has.


WiX: make swift-inspect required for Windows

We now can always build swift-inspect, remove the option to exclude swift-inspect. Shuffle the tool into the main toolchain installation and remove the additional support that the fragmented swift-inspect handling required.

Tested at https://ci-external.swift.org/job/swift-PR-build-toolchain-windows/5563/


Remove checkbox attachments

Adjust configuration to remove checkbox for "has attachment" filter. Customer will be responsible to alter their data

wrong repo


Disable next and previous buttons

Hello,
just wanted to know if there is a reason why the next and previous buttons are not disabled when first or last page is selected?

No particular reason. The component itself doesn't deal with concerns like this, but if you want you could PR a change to DemoPaginator.
I'll most likely add the check myself later on. Just something like className={!pagination.page && 'disabled'} etc.


Nove 2024 Questions

Adds statewide ballot questions.

@inomyabcs That's good because GitHub desktop is telling me I'm not connected to the internet, so I can't see my updates.

@inomyabcs The rest of the questions are now in. Can you take a look and let me know if it looks good to merge?

Agree. Thanks for doing a better job of reading through those then I did. I was going to miss a lot of little errors.


Improved the readme

@GrahamCampbell the composer install stuff should just be:
composer require vendor/package

I know it could be that, be I don't like that. I prefer to edit composer.json files. That way I can have dependencies order how I want them. :)

We can always change this later if lots of people prefer using the command to require packages.

@GrahamCampbell you are the last one from whom I'd expect personal preference to block best practices ;)

It's not a best practice though? It's just a preference.

It is though. Not only is it more sustainable/future-proof, it also set's the correct version constraint depending on the rest of the composer settings the consuming dev has specified.

Hmmm, I'll think about it, lol.

Come on, @GrahamCampbell, you know I'm right :dancer:

It actually is the recommended way.
Not only does it do auto-mapping to the proper version which is nice and handy. But it also runs a controlled install that will affect less of the other dependencies as possible, since most people simply run composer update or install after editing the composer.json, this can lead to a lot of unexpected updates. So rather than trying to grok all that, composer require will handle everything in a atomic action.
Keeping all dependencies "is alphabetical order" on the other hand is a preference and has not real practical purpose since you can get all that same information using composer show --installed and then remove using composer remove package.. hence touching the json file as little as possible, leading to less syntax errors and such.


Automated model testing update

Planned features

Automated model testing
New file structure
Programmatic API for custom pipeline designing

More about the update
This update aims on bringing automated model testing and the new Odin's programmatic API for custom pipeline scripting. The automated tests for models will generate performance reports with a couple other informations about the inference for further analytical studies on the trained model at staging phase.
Besides the automated testing, this update will also bring the programmatic API for the framework, so the engineers can have more flexibility on Odin's pipelines, since you can't do that on the CLI interface. This will allow a "sandboxy" interaction with the framework, opening up new possibilities.
This update will most likely deploy to PyPI at 1.2.x version.

🛠 Development Updates | v1.2.x
Recently I've run a couple tests on the new Odin API, in the present moment, it can instantiate/create a project, datasets and publish these datasets created via API. The image below shows the following code running:
from odin_vision.api.pipeline import OdinProject

# Tries to load the project, if Odin can't find it and allow_creation=True, then it will create it from scratch
my_project = OdinProject("obd-test", type="detection", allow_creation=True, verbose=True)
# Gives a little report on the project
my_project.see()

# Creates a new dataset or loads it if it already exists
my_new_dataset = my_project.datasets.get(by_name="dataset_test3", allow_creation=True)
my_project.see()

print(my_new_dataset)

# Publishes the dataset
my_new_dataset.publish()

Those are just some of the features planned, the idea is to do everything that Odin CLI can do, but in Python code. Take a look at the details of the features used in the code above:
Starting a project
from odin_vision.api.pipeline import OdinProject

my_project = OdinProject(name="my-project", type="classification").create()

my_project = OdinProject(name="my-project", type="classification", allow_creation=True)

Retrieving an existing project
my_project = OdinProject(name="my-project")

Creating a dataset
my_project.datasets.create("dataset1") # Returns OdinDataset
my_dataset: OdinDataset = my_project.datasets.get(by_name="dataset1", allow_creation=True)

Publishing a dataset
my_dataset.publish()

my_project.datasets.publish(dataset="dataset1")
my_project.datasets.publish(dataset=my_dataset)

As can be observed in those code snippets, the idea is for Odin API to be totally dynamic and responsive, so there's going to be a lot of ways to code in Odin API to achieve the same result. Smart code!


Speed up metrics computation by optimizing segment validation

Before submitting (must do checklist)

[x] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Proposed Changes

Optimize _validate_segment_columns
Remove redundant dataframe selection in metrics computation.

Closing issues
Closes #1336.

Script for testing:
import time
import json

import numpy as np
import pandas as pd
from loguru import logger

from etna.models import NaiveModel
from etna.datasets import TSDataset, generate_ar_df
from etna.metrics import MAE
from etna.pipeline import Pipeline

HORIZON = 14

def make_df(num_segments: int, num_features: int, num_periods: int, random_state: int = 0) -> pd.DataFrame:
    rng = np.random.default_rng(random_state)
    df = generate_ar_df(
        periods=num_periods, start_time="2020-01-01", n_segments=num_segments
    )

    for i in range(num_features):
        # add int column
        df[f"new_int_{i}"] = rng.integers(low=-100, high=100, size=df.shape[0])

    return df

def check_time(num_segments: int, num_features: int, num_periods: int = 365):
    df = make_df(num_segments=num_segments, num_features=num_features, num_periods=num_periods)
    df_wide = TSDataset.to_dataset(df)
    ts = TSDataset(df=df_wide, freq="D")

    model = NaiveModel(lag=1)
    transforms = []
    pipeline = Pipeline(model=model, transforms=transforms, horizon=HORIZON)

    start_time = time.perf_counter()
    metrics, _, _ = pipeline.backtest(ts=ts, metrics=[MAE()], n_folds=3)
    elapsed_time = time.perf_counter() - start_time

    return elapsed_time

def main():
    num_segments = [10, 100, 1000, 10_000]
    num_features = [0, 3, 10]

    results = []
    for cur_num_segments in num_segments:
        for cur_num_features in num_features:
            time_result = check_time(num_segments=cur_num_segments, num_features=cur_num_features)
            record = {"num_segments": cur_num_segments, "num_features": cur_num_features, "time": time_result}
            results.append(record)
            logger.info(json.dumps(record))

    json.dump(results, open("records_2.json", "w"), indent=2)

if __name__ == "__main__":
    main()

Results without changes:
[
  {
    "num_segments": 10,
    "num_features": 0,
    "time": 0.3590500030000001
  },
  {
    "num_segments": 10,
    "num_features": 3,
    "time": 0.4593144890000005
  },
  {
    "num_segments": 10,
    "num_features": 10,
    "time": 0.3713757409999978
  },
  {
    "num_segments": 100,
    "num_features": 0,
    "time": 1.2579138940000014
  },
  {
    "num_segments": 100,
    "num_features": 3,
    "time": 1.4334653250000002
  },
  {
    "num_segments": 100,
    "num_features": 10,
    "time": 1.562795714
  },
  {
    "num_segments": 1000,
    "num_features": 0,
    "time": 9.964996322999998
  },
  {
    "num_segments": 1000,
    "num_features": 3,
    "time": 13.49794635
  },
  {
    "num_segments": 1000,
    "num_features": 10,
    "time": 15.799086332999998
  },
  {
    "num_segments": 10000,
    "num_features": 0,
    "time":<PHONE_NUMBER>17
  },
  {
    "num_segments": 10000,
    "num_features": 3,
    "time":<PHONE_NUMBER>7699998
  },
  {
    "num_segments": 10000,
    "num_features": 10,
    "time":<PHONE_NUMBER>1
  }
]

Results with changes in _validate_segment_columns:
[
  {
    "num_segments": 10,
    "num_features": 0,
    "time": 0.21762080500000014
  },
  {
    "num_segments": 10,
    "num_features": 3,
    "time": 0.25818068400000005
  },
  {
    "num_segments": 10,
    "num_features": 10,
    "time": 0.2985194660000001
  },
  {
    "num_segments": 100,
    "num_features": 0,
    "time": 0.7977682599999998
  },
  {
    "num_segments": 100,
    "num_features": 3,
    "time": 0.8086340990000007
  },
  {
    "num_segments": 100,
    "num_features": 10,
    "time": 0.9596903270000006
  },
  {
    "num_segments": 1000,
    "num_features": 0,
    "time": 6.304263003999999
  },
  {
    "num_segments": 1000,
    "num_features": 3,
    "time": 6.816117811000002
  },
  {
    "num_segments": 1000,
    "num_features": 10,
    "time": 8.042914625000002
  },
  {
    "num_segments": 10000,
    "num_features": 0,
    "time": 62.120309238999994
  },
  {
    "num_segments": 10000,
    "num_features": 3,
    "time": 70.261712954
  },
  {
    "num_segments": 10000,
    "num_features": 10,
    "time": 85.14670703500002
  }
]

Results with removing extra dataframe selection:
[
  {
    "num_segments": 10,
    "num_features": 0,
    "time": 0.21787695200000012
  },
  {
    "num_segments": 10,
    "num_features": 3,
    "time": 0.2454114409999999
  },
  {
    "num_segments": 10,
    "num_features": 10,
    "time": 0.27747879200000014
  },
  {
    "num_segments": 100,
    "num_features": 0,
    "time": 0.6796172610000006
  },
  {
    "num_segments": 100,
    "num_features": 3,
    "time": 0.678246498
  },
  {
    "num_segments": 100,
    "num_features": 10,
    "time": 0.7758322989999993
  },
  {
    "num_segments": 1000,
    "num_features": 0,
    "time": 4.967111137000002
  },
  {
    "num_segments": 1000,
    "num_features": 3,
    "time": 5.283647876000002
  },
  {
    "num_segments": 1000,
    "num_features": 10,
    "time": 6.464345726000001
  },
  {
    "num_segments": 10000,
    "num_features": 0,
    "time": 49.259913931999996
  },
  {
    "num_segments": 10000,
    "num_features": 3,
    "time": 54.42493236100002
  },
  {
    "num_segments": 10000,
    "num_features": 10,
    "time": 66.683967212
  }
]

There was also a profiling using py-spy with a script:
import time
import json

import numpy as np
import pandas as pd
from loguru import logger

from etna.models import NaiveModel
from etna.datasets import TSDataset, generate_ar_df
from etna.metrics import MAE
from etna.pipeline import Pipeline

HORIZON = 14

def make_df(num_segments: int, num_features: int, num_periods: int, random_state: int = 0) -> pd.DataFrame:
    rng = np.random.default_rng(random_state)
    df = generate_ar_df(
        periods=num_periods, start_time="2020-01-01", n_segments=num_segments
    )

    for i in range(num_features):
        # add int column
        df[f"new_int_{i}"] = rng.integers(low=-100, high=100, size=df.shape[0])

    return df

def check_time(num_segments: int, num_features: int, num_periods: int = 365):
    df = make_df(num_segments=num_segments, num_features=num_features, num_periods=num_periods)
    df_wide = TSDataset.to_dataset(df)
    ts = TSDataset(df=df_wide, freq="D")

    model = NaiveModel(lag=1)
    transforms = []
    pipeline = Pipeline(model=model, transforms=transforms, horizon=HORIZON)

    start_time = time.perf_counter()
    metrics, _, _ = pipeline.backtest(ts=ts, metrics=[MAE()], n_folds=3)
    elapsed_time = time.perf_counter() - start_time

    return elapsed_time

def main():
    check_time(num_segments=10_000, num_features=3)

if __name__ == "__main__":
    main()

Results look like this:

Key notions:

Metric computation is still takes a lot of time, about 44%.
TSDataset.describe takes a lot of time, about 25%.

Codecov Report

Merging #1338 (db26e16) into master (aac0fe1) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master    #1338   +/-   ##
=======================================
  Coverage   88.95%   88.95%
=======================================
  Files         204      204
  Lines       12641    12643    +2
=======================================
+ Hits        11245    11247    +2
  Misses       1396     1396

Files Changed
Coverage Δ

etna/metrics/base.py
93.82% <100.00%> (+0.15%)
:arrow_up:

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Results after reworking _validate_timestamp_columns:
[
  {
    "num_segments": 10,
    "num_features": 0,
    "time": 0.2025824759999999
  },
  {
    "num_segments": 10,
    "num_features": 3,
    "time": 0.24138570799999925
  },
  {
    "num_segments": 10,
    "num_features": 10,
    "time": 0.272586608000001
  },
  {
    "num_segments": 100,
    "num_features": 0,
    "time": 0.6173706429999992
  },
  {
    "num_segments": 100,
    "num_features": 3,
    "time": 0.622621066999999
  },
  {
    "num_segments": 100,
    "num_features": 10,
    "time": 0.7178853730000014
  },
  {
    "num_segments": 1000,
    "num_features": 0,
    "time": 4.244795499
  },
  {
    "num_segments": 1000,
    "num_features": 3,
    "time": 4.704148591000001
  },
  {
    "num_segments": 1000,
    "num_features": 10,
    "time": 5.926159300000002
  },
  {
    "num_segments": 10000,
    "num_features": 0,
    "time": 40.73026384199999
  },
  {
    "num_segments": 10000,
    "num_features": 3,
    "time": 46.77938691599999
  },
  {
    "num_segments": 10000,
    "num_features": 10,
    "time": 60.692529713
  }
]

Results after iteration optimization:
[
  {
    "num_segments": 10,
    "num_features": 0,
    "time": 0.22758442000000034
  },
  {
    "num_segments": 10,
    "num_features": 3,
    "time": 0.303228195
  },
  {
    "num_segments": 10,
    "num_features": 10,
    "time": 0.2589208110000003
  },
  {
    "num_segments": 100,
    "num_features": 0,
    "time": 0.5286539329999993
  },
  {
    "num_segments": 100,
    "num_features": 3,
    "time": 0.575157707999999
  },
  {
    "num_segments": 100,
    "num_features": 10,
    "time": 0.6489074320000014
  },
  {
    "num_segments": 1000,
    "num_features": 0,
    "time": 3.4659758200000006
  },
  {
    "num_segments": 1000,
    "num_features": 3,
    "time": 4.007518799999998
  },
  {
    "num_segments": 1000,
    "num_features": 10,
    "time": 5.0106977860000015
  },
  {
    "num_segments": 10000,
    "num_features": 0,
    "time": 33.155186359
  },
  {
    "num_segments": 10000,
    "num_features": 3,
    "time": 39.375860941000006
  },
  {
    "num_segments": 10000,
    "num_features": 10,
    "time": 53.37710269499999
  }
]


verdaccio 4.1.0 shows the unpublished component version in UI

Describe the bug
I've installed verdaccio 4.1.0 ,  and published a package with version 1.0.0 and 1.0.1. I've unpublished version 1.0.1 but still verdaccio displays the package vesion as 1.0.1. But when i try to install the<EMAIL_ADDRESS>it shows package doesn't exists. But the 1.0.1 is there in UI(verdaccio front end).
Expected behavior
The correct version should be there in verdaccio UI.
Screenshots

I can confirm that this indeed happens.
It looks like the top level package.json for the package in the local storage directory still keeps a reference of an unpublished version, yet there's no tarball for such unpublished version available.
Is this by design so that no one can create a version that was unpublished or should it be allowed?

Duplicated https://github.com/verdaccio/verdaccio/issues/1359 👍

Thanks @sathishchandran97 for reporting :-) there is a possible solution in the #1359 perhaps you want go for it 🤓

Is this by design so that no one can create a version that was unpublished or should it be allowed?

@lirantal  it is a bug :-) version unpublish should be removed from the package.json.

Yes indeed! :-)

Okay @juanpicado . Thanks :-)


OrgID is not required in /api/v2/checks and /api/v2/notificationRules

The swagger and the generated swagger docs indicate that the orgID parameter is required for /api/v2/checks and /api/v2/notificationRules
I talked to @desa and @goller and they do expect calls to /api/v2/checks and /api/v2/notificationRules to return all values the user is authorized to see.  I checked on OSS and calls to /api/v2/checks and /api/v2/notificationRules do return all my checks and notificationRules.
I believe this just means our swagger config should take out the required parameter and the docs will be regenerated.

@jademcgough and @desa - No idea who should take care of this as team responsibilities have morphed.  I was about to submit a PR myself to just remove required from the file but I grew concerned it might have unintended consequences for things swagger might automatically trigger.


New Feature Ideas

Can you add soul box doors so you can place as many soul boxs as you like and you can configure how many zombie kills each one needs in order to be full once all the boxes are filled it will open a door for indication on zombies souls being collected you could use a ray of particles going from the zombie to the box I would say a zombie would need to be within a 4 block radius in order for its death to count another idea allow people to change the gun Items and sounds this would allow for a nice texture pack to be made also Super Glad to see you back working on this plugin and sorry for the bad grammer

I'll keep this in mind!

I'll keep this in mind!

Another idea I had was buyable endings so the player needs to get a set amount of points to end the game it would give an extra purpose to the mode the sign setup for a buyable ending could be like this
[Zombies]
Buyable Ending
Cost
40000

Another idea I had was buyable endings so the player needs to get a set amount of points to end the game it would give an extra purpose to the mode the sign setup for a buyable ending could be like this
[Zombies]
Buyable Ending
Cost
40000


GH-735 adjusting check for github to mainly make sure that github app…

…ears in the host name. Will allow many variations of host names as well as username and password.
Closes #735

@allen-servedio Please remind me have you submitted you Apache ICLA?

@mrutkows - yes it was submitted and received by @csantanapr last Friday.

@allen-servedio you were too fast ... i looked it up in the Apache directory and removed my comment )


dunzhang/stella_en_1.5B_v5 Maximum Token Limit Set to 512 Despite Model Capabilities

System Info
docker run --gpus all -p 8081:80 -v $HF_HOME/hub:/data ghcr.io/huggingface/text-embeddings-inference:1.5 --model-id dunzhang/stella_en_1.5B_v5 --auto-truncate
Information

[x] Docker
[ ] The CLI directly

Tasks

[x] An officially supported command
[ ] My own modifications

Reproduction
Issue: Maximum Token Limit Set to 512 Despite Model Capabilities
Steps to Reproduce:
docker run --gpus all -p 8081:80 -v $HF_HOME/hub:/data ghcr.io/huggingface/text-embeddings-inference:1.5 --model-id dunzhang/stella_en_1.5B_v5 --auto-truncate

Observed Behavior:
The output always indicates:
Maximum number of tokens per request: 512

However, according to the MTEB leaderboard, this model should be able to handle up to 131,072 tokens.
Suggested Improvement:
It would be beneficial to add a --max-input-length option to the CLI, allowing users to specify a custom token limit. I checked the current CLI options, and none appear to address the maximum input length.
Additional Details:
Even with the --auto-truncate flag, the following log is generated:
INFO text_embeddings_router: router/src/lib.rs:199: Maximum number of tokens per request: 512

This behavior appears to be controlled by the following line of code: router/src/lib.rs#L199
tracing::info!("Maximum number of tokens per request: {max_input_length}");

Would it be possible to allow users to modify this limit via a CLI option?
Expected behavior
--auto-truncate is expected to auto-handle this instead of raising an error.
--max-input-length is expected to be available in CLI options

The length of the output is 1536 instead of 1024. I did one click deploy. It doesn't match when i load the model for training and for inference. Could you make the model that loads in TEI also use 1024 dims?

System Info
docker run --gpus all -p 8081:80 -v $HF_HOME/hub:/data ghcr.io/huggingface/text-embeddings-inference:1.5 --model-id dunzhang/stella_en_1.5B_v5 --auto-truncate
Information

[x]  Docker
[ ]  The CLI directly

Tasks

[x]  An officially supported command
[ ]  My own modifications

Reproduction
Issue: Maximum Token Limit Set to 512 Despite Model Capabilities
Steps to Reproduce:
docker run --gpus all -p 8081:80 -v $HF_HOME/hub:/data ghcr.io/huggingface/text-embeddings-inference:1.5 --model-id dunzhang/stella_en_1.5B_v5 --auto-truncate

Observed Behavior: The output always indicates:
Maximum number of tokens per request: 512

However, according to the MTEB leaderboard, this model should be able to handle up to 131,072 tokens.
Suggested Improvement: It would be beneficial to add a --max-input-length option to the CLI, allowing users to specify a custom token limit. I checked the current CLI options, and none appear to address the maximum input length.
Additional Details: Even with the --auto-truncate flag, the following log is generated:
INFO text_embeddings_router: router/src/lib.rs:199: Maximum number of tokens per request: 512

This behavior appears to be controlled by the following line of code: router/src/lib.rs#L199
tracing::info!("Maximum number of tokens per request: {max_input_length}");

Would it be possible to allow users to modify this limit via a CLI option?
Expected behavior
--auto-truncate is expected to auto-handle this instead of raising an error. --max-input-length is expected to be available in CLI options

The length of the output is 1536 instead of 1024. I did one click deploy. It doesn't match when i load the model for training and for inference. Could you make the model that loads in TEI also use 1024 dims?


Add more coercions for table/partition mismatch issue in Hive connector

Trying to address https://github.com/prestosql/presto/issues/137
To do:

decimal and double convert.
decimal and float convert.
Currently only support HivePageSource, add support for RecordPageSource.

@hustnn in the description above, I see add support for RecordPageSource, does this mean that this a work in progress?  If so, it it is helpful to the reviewers if you can "edit" the PR title to start with [WIP], so they know it isn't necessary to review yet.

@dain Hi, I found GenericHiveRecordCursorProvider automatically do the coercion without HiveCoercionRecordCursor.

@hustnn, interesting, looks like S3SelectRecordCursorProvider is the only code using the adapter now.  So is this ready to review?

@dain . I will add float and decimal, double and decimal coercion. Then, should be ok for review. For this PR, can we finish the support for hive page source first ?
For the RecordCursor, If also needed, I can open another PR.

@dain Ready for review.

Some super minor comments. This will need review from some that really understands decimal.

Minor comments addressed.

a lot of code has been copied from presto-main. I wonder if it qualifies for a separate module. What do you think @dain @electrum ?

That seems reasonable, but I don't think we should delay this PR for that reorganization.

@sopel39 @dain Comments all fixed.

I'll reorganize the cast code


⚠ Bofrost.lu has degraded performance

In 436362b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 880 ms

Resolved: Bofrost.lu performance has improved in fc52775 after 6 minutes.


Fix GPG error

Pull Request Test Coverage Report for Build 221

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 82.742%

Totals

Change from base Build 220:
0.01%

Covered Lines:
7043

Relevant Lines:
8512

💛  - Coveralls


Nodejs 18 required

I may be wrong but it seems Nodejs 18 is the minimum required version to make this package work correctly!
With Nodejs 16 I got the next error message:
/usr/local/bin/yarn run dev
node:internal/tls/secure-context:65
    context.setCert(cert);
            ^

Error: error:0A00018F:SSL routines::ee key too small
    at node:internal/tls/secure-context:65:13
    at Array.forEach (<anonymous>)
    at setCerts (node:internal/tls/secure-context:63:3)
    at configSecureContext (node:internal/tls/secure-context:152:5)
    at Object.createSecureContext (node:_tls_common:117:3)
    at Server.setSecureContext (node:_tls_wrap:1346:27)
    at Server (node:_tls_wrap:1205:8)
    at new Server (node:https:69:3)
    at Object.createServer (node:https:105:10)
    at startServer (/app/node_modules/next-dev-https/src/server.js:229:18) {
  library: 'SSL routines',
  reason: 'ee key too small',
  code: 'ERR_SSL_EE_KEY_TOO_SMALL'
}

Process finished with exit code 1

You should probably update your package.json to add the minimum version of the engine like:
"engines": {
    "node": ">=18"
}

You could also specify that in the README file.

Thanks for reporting @emulienfou, will look into this when possible.
My initial take is that it's weird that this diffs between node versions. It looks to me that this is a revocation from upstream (OpenSSL prob) from using the cert generated by selfsigned. We should probably change the cert generation params, it should be working on node 16.
Two questions which will speedup debugging:
Which OS(linux, mac, windows) and version is triggering the issue?
Have you validated that this works on the same machine with node 18 but not on 16?

Hi @TobiasMelen,
I was running on Debian 11 with both latest versions of node J's 16 & 18.
Switching from node 16 to 18 resolved the issue.

Hi @emulienfou
I've increased encryption key size to 2048 and switched checksum algorithm to SHA256 which i hopes makes Debian happier to run the cert. Could you try installing this version, running it through node 16 on Debian to see if it's working better?
npm i next-dev-https@sha256

@TobiasMelen for reference purpose it was working fine on Node.js 16.20 but not on 16.15.
After install next-dev-https@sha256 on Nodejs 16.15, it works like a charm now!
Thanks for the fix

Thanks for reporting and testing, seems like selfsigned has quite lax certificate generation defaults, so it was good to bump them a bit. Change released in 2.0.1.


[issue] Slow download speed?

Does it use ffmpeg to download video?
Cuz I know from ytdlp it downloads slow with ffmpeg.
With aria2 mine download will take 2-3 minutes to finish with ffmpeg it would take 12-13 minutes to finish.
Would it not better to use aria2c to bypass download speed limit?

No it downloads the raw streams, decrypts them and adds them to the file.
It should be as fast as possible.

No it downloads the raw streams, decrypts them and adds them to the file. It should be as fast as possible.

I did just download latest word trigger Episode with ytdlp and it took 2 minutes to finish but with anidl.exe it did take 13 minutes?

Can you use ffprobe -i "File" to send me the metadata of the downloaded file?

Can you use ffprobe -i "File" to send me the metadata of the downloaded file?

This one is downloaded with ytdlp and this is downloaded with anidl.exe

Alright, I see your issue. I can tell that you have a good connection speed, so could you try to raise the batch size by doing --partsize number. 10 is default. Try playing with it and test if that fixes anything.

yes that did fix it.
I thank you for your help.
I'm closing it.

Don't mention it. Feel free to open up an issue if you think you found something, so we can improve!


question re: state mgmt architecture

Hey guys!  Thanks for this simple and great project.  Its refreshing to find some sanity and simplicity in this field.  I very much prefer the npm module approach to front end dev and I'm confused why more don't approach things from the bottom up like this instead of reinventing everything from top down and calling it a framework.
I have a question that is less an issue, but more a curiousity regarding the architectural choice for this offering.  I've been looking a lot at state management for virtual dom applications and while I feel like redux is a great refinement of the general flux approach, i am having issues combining it w/ my modular aspirations.  mainly:
1 - if i want to develop in components that are individual npm modules for my app, doesnt the redux approach of having all of your stores, reducers, etc living in centralized separate files make this notion a challenge?  sure i can have them as reducers.js and stores.js files, but then i have to do a lot of work to guarantee they are exporting in exactly the way my app needs them, and its not necessarily friendly for others to consume
2 - im sure youre familar w/ a project in a similar npm style is mercuryjs , which ive been looking heavily at (really wishing there was more community traction and adoption honestly) has a very different approach to state management, where state mutation is still immutable, yet defined locally to each component.  i like this approach, and was curious what you think, and why you would choose redux over this?
sorry if ive gone on too long, but very curious your thoughts, thank you

Hey, thanks for asking this; always happy to think along in terms of architecture. Because this is something philosophical, I can't give you an absolute response, just my thoughts on the matter. I'd be keen to hear what others think about this too!

if i want to develop in components that are individual npm modules for my app, doesnt the redux approach of having all of your stores, reducers, etc living in centralized separate files make this notion a challenge?

In my view virtual-app has a distinction between state modification and side effects. state modification functions, synchronously take an object and return a new object with new values. Side effects use the .on() syntax, and are triggered by an event, don't return anything, but emit a new event with values attach when the async action is done.
All of this doesn't require new files, and can definitely be published to npm. I wouldn't couple these packages too tightly to virtual-app though, as like with all frameworks this one too will eventually become redundant. I think the best candidates to publish to npm are the side effects.

i like this approach, and was curious what you think, and why you would choose redux over this?

So virtual-app doesn't use redux, but something that's a bit less complicated under the hood. I've found mercury's immutable state components to be both large-ish and complicated to use. I'm not sure how they fare in terms of garbage collection, but I think using xtend and message passing is by far easier to reason about, despite not having the same guarantees. It's a bit of a tradeoff, but I think it makes sense for JavaScript as this means we can keep both complexity and code size low.
I hope my take on this makes sense! cheers! :sparkles:

Thank you, definitely so!
I too have concerns about how hard to reason about the mercury model seems to be, but I keep feeling like I'm "almost there" ... The murky docs don't help.  But if I'm having this hard a time it will be a hard sell to the team for sure.
Back to virtual app
The main thing I'm trying to figure, is if you want to keep generic message and state mod definitions local to the component, then when you want to include that component in various virtualapps, do you have a way to say... Namespace the messages to that component to prevent overwrite or, some mechanism to register your component store (living in the package) with the global store of your app?
Trying to think of how it could be possible , at least without adding a lot of messy ETL type code to pull it in

I'd namespace events - treating state like a giant, global thing seems quite alright


Simperium not mapping NSValueTransformer correctly upon logging back in.

@jleandroperez  As a workaround for Simperium not supporting many to many relationships I set up a NSValueTransformer on one of my classes that hold an array of Simperium keys that the object is related to. So, as an example my use case is as follows.
Lineup  has many Players
Players are apart of many Lineups
On my Lineup entity I have a playerIDs  id property that gets transformed into an NSArray
On my Player entity I have a lineupIDs  id property that gets transformed into an NSArray
Everything works fine with Simperium until I log out of the application and re log back in. When that happens, the playerIDs property on my Lineup are no longer there  and the lineupIDs are no longer on my Player are also no longer there.
The Lineup object returns nil for playerIdDs so the object looks like this
What the object looks like after logging back in.
<Lineup: 0x170103f00> (entity: Lineup; id: 0xd000000000040004 <x-coredata://550A4D12-E78C-4D02-9110-EF0CE7BBB8C2/Lineup/p1> ; data: {
ghostData = "{\n  \"key\" : \"c7537de8e1794863b9289ca52eec6743\",\n  \"version\" : \"1\",\n  \"obj\" : {\n    \"playerIDs\" : \"\",\n    \"relationshipTeam\" : \"2e5a3e1d168a4a77ac97aa3914ebaa1a\"\n  }\n}";
playerIDs = nil;
lineupStats =     (
    "0xd000000000080006 <x-coredata://550A4D12-E78C-4D02-9110-EF0CE7BBB8C2/LineupStats/p2>"
);
team = "0xd00000000004000e <x-coredata://550A4D12-E78C-4D02-9110-EF0CE7BBB8C2/Team/p1>";
simperiumKey = c7537de8e1794863b9289ca52eec6743;
})

Everything is saved correctly on Simperium.com. Let me know what more information you need. This is reproducible 10/10.
This works in v0.7.5

Hello @lukegeiger,
This is the setup we use in the WordPress iOS App. The Notification entity has a couple Transformables, that get translated into NSArray.
Incoming questions below!:

Is this entity being sync'ed to other devices? are the transformable attributes being sync'ed there?
By 'saved correctly on simperium' you mean that the ID's do show up on the dashboard, right?.

If possible, please, try the following:

Fresh install + new account
Insert a Lineup with the transformables set.
Make sure that the change goes through (and please, validate on Simperium.com)
Fresh install, again. Log in with verboseLogging enabled.

(Please, grab those logs, it'd be super helpful). Are the Transformables showing up in that initial fresh-install sync?.
Thanks!

@lukegeiger may i ask you if you've been able to retrieve the logs?.
Thank you!

@jleandroperez my fault for late response on this... I haven't been able to get the logs again. It seemed to only be happening to me on that day which is weird. I could have messed up and been on an old pod without realizing it. If I see it again I will get the logs and make sure to re open this.

@lukegeiger no worries at all!. Thanks for the feedback sir, closing for now then. (If needed) please feel free to reopen.
Have a great day!


Installing spaczz with successful RapidFuzz installed

Similar to another post, but it still doesn't install even after successfully installing RapidFuzz separately.
This is what I get:
cl : Command line warning D9025 : overriding '/W3' with '/W4'
cpp_process.cpp
src/cpp_process.cpp(16): fatal error C1083: Cannot open include file: 'Python.h': No such file or directory
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\HostX86\x64\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for rapidfuzz
Failed to build rapidfuzz
ERROR: Could not build wheels for rapidfuzz, which is required to install pyproject.toml-based projects

@lorijwong, spaczz v0.6 is now tested against rapidfuzz v1-3 and Python 3.7-3.11. Please try to install the latest version of spaczz, and please see the latest release notes for some important changes to be aware of.


Contact lookup appears to be failing (maybe just on M+?)

I'm writing an app to perform analytics on SMS history, and I'm unable to load contacts on my device (which is on the P beta, but I don't think that should be relevant to the issue).
When I try to run thread.findContact() it pops up the permission dialog which lets me choose to allow the app to read my contacts. That works fine. However, then it immediately throws.
Here's the stacktrace produced by the java method channel hook:
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): Failed to handle method call
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): java.lang.NegativeArraySizeException: -1
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at com.babariviere.sms.ContactPhotoQueryHandler.queryContactPhoto(ContactPhotoQuery.java:78)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at com.babariviere.sms.ContactPhotoQueryHandler.handle(ContactPhotoQuery.java:46)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at com.babariviere.sms.ContactPhotoQuery.onMethodCall(ContactPhotoQuery.java:133)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:191)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at io.flutter.view.FlutterNativeView.handlePlatformMessage(FlutterNativeView.java:136)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at android.os.MessageQueue.next(MessageQueue.java:326)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at android.os.Looper.loop(Looper.java:160)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at android.app.ActivityThread.main(ActivityThread.java:6642)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at java.lang.reflect.Method.invoke(Native Method)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/MethodChannel#plugins.babariviere.com/queryContactPhoto(25064): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Which can be found here https://github.com/babariviere/flutter_sms/blob/master/android/src/main/java/com/babariviere/sms/ContactPhotoQuery.java#L78
I would try to help fix it but unfortunately I am not very experienced with the Android side of Java.
Is this perhaps my issue?  If you'd like, you can see how I'm setting up the threads here: https://github.com/ArcticZeroo/sms_analytics/blob/master/lib/api/sms_manager.dart#L78

Oh yes, good catch. I will fix this tonight

If you want to fix it, you can check this link to understand the bug: https://stackoverflow.com/questions/44875399/android-java-lang-negativearraysizeexception-1

I've uploaded a new version, can you tell me if this works now?


build: Add semantic release

What is this?
This PR adds automatic releasing with semantic release.
There are a few open TODOs (for @djones or someone who has permissions):

[x] Add GITHUB_TOKEN to CI
[x] Add NPM_TOKEN to CI
[x] Add the semantic release probot to this repo (under org settings)

It would be nice to import those env vars from percy-cypress (or another SDK), but it looks like I don't have permissions:

Access for those tokens should be resolved now. And I've added the semantic pull requests probot to this repo.


socket.setsockopt(zmq.SUBSCRIBE, '') fails when from __future__ import unicode_literals is used

Traceback (most recent call last):
  File "/apps/leds/start.py", line 11, in <module>
    inbound.setsockopt(zmq.SUBSCRIBE, '')
  File "zmq/backend/cython/socket.pyx", line 374, in zmq.backend.cython.socket.Socket.set (zmq/backend/cython/socket.c:4297)
TypeError: unicode not allowed, use setsockopt_string

Correct. unicode_literals means that anywhere you type '', it's actually doing u'', which is unicode, and SUBSCRIBE must be given bytes. To do this, use b'', which will work in both Python 2 and 3.


[BUG] [Genbrugsspand, 240L (2-delt) (1 stk.)] is not defined

Describe the issue
I get this in my error log:
Denne fejl stammer fra en brugerdefineret integration.

Logger: pyaffalddk.api
Kilde: custom_components/affalddk/__init__.py:123
integration: Affaldshåndtering DK (dokumentation, problemer)
Første forekomst: 24. november 2024 kl. 23.40.24 (2 forekomster)
Senest logget: 03.40.24

Material type [Genbrugsspand, 240L (2-delt) (1 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Esbjerg, Address ID: 74775

I assume it's because the bins have been renamed on the api side.
What version of Home Assistant Core has the issue?
2024.11.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
What version of the integration are you using?
2.1.19
Diagnostics information
home-assistant_affalddk_2024-11-25T06-37-58.456Z.log
Anything in the logs that might be useful for us?
2024-11-25 07:37:39.207 WARNING (MainThread) [pyaffalddk.api] Material type [Genbrugsspand, 240L (2-delt) (1 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Esbjerg, Address ID: 74775
2024-11-25 07:37:39.208 DEBUG (MainThread) [custom_components.affalddk] Data fetched 2024-11-25 07:37:39
2024-11-25 07:37:39.208 DEBUG (MainThread) [custom_components.affalddk] Finished fetching affalddk data in 0.201 seconds (success: True)

Additional information
There has been some changes to which bins we have in the last couple of months here in Esbjerg, so this might just be an API endpoint that has been renamed or changed in some other way.

Hejsa,
Jeg skal nok fixe det, men det er lidt svært at se ud fra beskrivelsen hvad der skulle være i den container Genbrugsspand, 240L (2-delt) (1 stk.). Er det mad og restaffald, eller?

Tak. Jeg har fixet det, men arbejder lige nu på en lidt større opdatering, så der går lige nogle dage før næste version kommer ud, men her er det med.

Lækkert, tak for det. :smile:


[windows][macOS][git] Calling flutter pub get fails on CI with multiple projects with same dependency

See: https://github.com/invertase/melos/issues/289
See: https://github.com/dart-lang/pub/issues/3404
Steps to Reproduce

Execute flutter pub cache clean on each of at least two projects with the same (git) dependency, for example this one.
Execute flutter pub get --verbose at around the same time in both projects (e.g. via two terminals)

Expected results:
Not to fail the second command
Actual results:
One command fails with exit code (66; errno = 183)
Firtst terminal:
 flutter pub get
Waiting for another flutter command to release the startup lock...
Running "flutter pub get" in flutter_platform_test_second...       115.6s

Second terminal:
 flutter pub get
Running "flutter pub get" in flutter_tools...                      25.0s
Rename failed, path = 'C:\src\flutter\.pub-cache\_temp\dirb894bfc2' (OS Error: Cannot create a file when that file already exists.
, errno = 183)
Running "flutter pub get" in flutter_platform_test...
pub get failed (66; , errno = 183))

See output of github actions:
https://github.com/Gustl22/flutter_platform_test/runs/6469406757?check_suite_focus=true
See pub_log.txt of second execution

Logs
complete log file here: pub_log.txt
Information about the latest pub run.

If you believe something is not working right, you can go to
https://github.com/dart-lang/pub/issues/new to post a new issue and attach this file.

Before making this file public, make sure to remove any sensitive information!

      ref: HEAD
      resolved-ref: aca373a2d9c64ddb55c54d5c2241e2175effa582
      url: "https://github.com/dart-lang/dartdoc.git"
    s[...]: sdk
    version: "0.0.99"
  source_span:
    dependency: transitive
    description:
      name: source_span
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.8.2"
  stack_trace:
    dependency: transitive
    description:
      name: stack_trace
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.10.0"
  stream_channel:
    dependency: transitive
    description:
      name: stream_channel
      url: "https://pub.dartlang.org"
    source: hosted
    version: "2.1.0"
  string_scanner:
    dependency: transitive
    description:
      name: string_scanner
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.1.0"
  term_glyph:
    dependency: transitive
    description:
      name: term_glyph
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.2.0"
  test_api:
    dependency: transitive
    description:
      name: test_api
      url: "https://pub.dartlang.org"
    source: hosted
    version: "0.4.9"
  typed_data:
    dependency: transitive
    description:
      name: typed_data
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.3.1"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      url: "https://pub.dartlang.org"
    source: hosted
    version: "2.1.2"
  watcher:
    dependency: transitive
    description:
      name: watcher
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.0.1"
  yaml:
    dependency: transitive
    description:
      name: yaml
      url: "https://pub.dartlang.org"
    source: hosted
    version: "3.1.1"
sdks:
  dart: ">=2.17.0-206.0.dev <3.0.0"
  flutter: ">=2.5.0"

---- End pubspec.lock ----
---- Log transcript ----
FINE: Pub 2.17.0
MSG : Resolving dependencies...
SLVR: fact: flutter_platform_test_second is 1.0.0+1
SLVR: derived: flutter_platform_test_second
SLVR: fact: flutter_platform_test_second depends on cupertino_icons ^1.0.2
SLVR: fact: flutter_platform_test_second depends on flutter from sdk
SLVR: fact: flutter_platform_test_second depends on flutter_test from sdk
SLVR: fact: flutter_platform_test_second depends on flutter_lints ^2.0.0
SLVR: fact: flutter_platform_test_second depends on dartdoc from git
SLVR:   selecting flutter_platform_test_second
SLVR:   derived: dartdoc from git
SLVR:   derived: flutter_lints ^2.0.0
SLVR:   derived: flutter_test from sdk
SLVR:   derived: flutter from sdk
SLVR:   derived: cupertino_icons ^1.0.2
IO  : Spawning "cmd /c git --version" in D:\Coding\git\gustl22\flutter_platform_test\packages\flutter_platform_test_second\.
IO  : Finished git. Exit code 0.
    | stdout:
    | | git version 2.34.1.windows.1
    | Nothing output on stderr.
FINE: Determined git command git.
IO  : Spawning "cmd /c git rev-parse --is-inside-git-dir" in C:\src\flutter\.pub-cache\git\cache\dartdoc-41bada436b1841a3d1e0eaff0c4683b7ef2d74e4
IO  : Finished git. Exit code 0.
    | stdout:
    | | true
    | Nothing output on stderr.
IO  : Spawning "cmd /c git rev-list --max-count=1 aca373a2d9c64ddb55c54d5c2241e2175effa582" in C:\src\flutter\.pub-cache\git\cache\dartdoc-41bada436b1841a3d1e0eaff0c4683b7ef2d74e4
IO  : Finished git. Exit code 128.
    | Nothing output on stdout.
    | stderr:
    | | fatal: bad object aca373a2d9c64ddb55c54d5c2241e2175effa582
IO  : Spawning "cmd /c git fetch" in C:\src\flutter\.pub-cache\git\cache\dartdoc-41bada436b1841a3d1e0eaff0c4683b7ef2d74e4
IO  : Finished git. Exit code 0.
    | Nothing output on stdout.
    | stderr:
    | | From https://github.com/dart-lang/dartdoc
    | |  * branch              HEAD       -> FETCH_HEAD
IO  : Spawning "cmd /c git show aca373a2d9c64ddb55c54d5c2241e2175effa582:pubspec.yaml" in C:\src\flutter\.pub-cache\git\cache\dartdoc-41bada436b1841a3d1e0eaff0c4683b7ef2d74e4
IO  : Finished git. Exit code 0.
    | stdout:
    | | name: dartdoc
    | | # Run `dart run grinder build` after updating.
    | | version: 5.1.0
    | | description: A non-interactive HTML documentation generator for Dart source code.
    | | repository: https://github.com/dart-lang/dartdoc
    | |
    | | environment:
    | |   sdk: '>=2.14.0 <3.0.0'
    | |
    | | dependencies:
    | |   analyzer: ^3.4.0
    | |   args: ^2.3.0
    | |   charcode: ^1.3.1
    | |   cli_util: ^0.3.5
    | |   collection: ^1.15.0
    | |   crypto: ^3.0.1
    | |   glob: ^2.0.1
    | |   html: ^0.15.0
    | |   logging: ^1.0.2
    | |   markdown: ">=4.0.0 <6.0.0"
    | |   meta: ^1.7.0
    | |   package_config: ^2.0.2
    | |   path: ^1.8.0
    | |   pub_semver: ^2.1.0
    | |   source_span: ^1.8.1
    | |   yaml: ^3.1.0
    | |
    | | dev_dependencies:
    | |   async: ^2.8.2
    | |   build: ^2.1.0
    | |   build_runner: ^2.1.2
    | |   build_test: ^2.1.3
    | |   build_version: ^2.1.0
    | |   code_builder: ^4.1.0
    | |   coverage: ^1.0.3
    | |   dart_style: ^2.2.0
    | |   grinder: ^0.9.0
    | |   http: ^0.13.3
    | |   lints: ^1.0.1
    | |   test: ^1.19.0
    | |   test_descriptor: ^2.0.0
    | |   test_process: ^2.0.2
    | |
    | | executables:
    | |   dartdoc: null
    | Nothing output on stderr.
SLVR:   fact: dartdoc 5.1.0 from git depends on analyzer ^3.4.0
SLVR:   fact: dartdoc 5.1.0 from git depends on args ^2.3.0
SLVR:   fact: dartdoc 5.1.0 from git depends on charcode ^1.3.1
SLVR:   fact: dartdoc 5.1.0 from git depends on cli_util ^0.3.5
SLVR:   fact: dartdoc 5.1.0 from git depends on collection ^1.15.0
SLVR:   fact: dartdoc 5.1.0 from git depends on crypto ^3.0.1
SLVR:   fact: dartdoc 5.1.0 from git depends on glob ^2.0.1
SLVR:   fact: dartdoc 5.1.0 from git depends on html ^0.15.0
SLVR:   fact: dartdoc 5.1.0 from git depends on logging ^1.0.2
SLVR:   fact: dartdoc 5.1.0 from git depends on markdown >=4.0.0 <6.0.0
SLVR:   fact: dartdoc 5.1.0 from git depends on meta ^1.7.0
SLVR:   fact: dartdoc 5.1.0 from git depends on package_config ^2.0.2
SLVR:   fact: dartdoc 5.1.0 from git depends on path ^1.8.0
SLVR:   fact: dartdoc 5.1.0 from git depends on pub_semver ^2.1.0
SLVR:   fact: dartdoc 5.1.0 from git depends on source_span ^1.8.1
SLVR:   fact: dartdoc 5.1.0 from git depends on yaml ^3.1.0
SLVR:     selecting dartdoc 5.1.0 from git
SLVR:     derived: yaml ^3.1.0
SLVR:     derived: source_span ^1.8.1
SLVR:     derived: pub_semver ^2.1.0
SLVR:     derived: path ^1.8.0
SLVR:     derived: package_config ^2.0.2
SLVR:     derived: meta ^1.7.0
SLVR:     derived: markdown >=4.0.0 <6.0.0
SLVR:     derived: logging ^1.0.2
SLVR:     derived: html ^0.15.0
SLVR:     derived: glob ^2.0.1
SLVR:     derived: crypto ^3.0.1
SLVR:     derived: collection ^1.15.0
SLVR:     derived: cli_util ^0.3.5
SLVR:     derived: charcode ^1.3.1
SLVR:     derived: args ^2.3.0
SLVR:     derived: analyzer ^3.4.0
IO  : Get versions from https://pub.dartlang.org/api/packages/flutter_lints.
IO  : HTTP GET https://pub.dartlang.org/api/packages/flutter_lints
    | Accept: application/vnd.pub.v2+json
    | X-Pub-OS: windows
    | X-Pub-Command: get
    | X-Pub-Session-ID: A7759D1F-1BF0-43A9-9198-3FC56B0D6174
    | X-Pub-Environment: flutter_cli:get
    | X-Pub-Reason: dev
    | user-agent: Dart pub 2.17.0
IO  : HTTP response 200 OK for GET https://pub.dartlang.org/api/packages/flutter_lints
    | took 0:00:00.900314
    | transfer-encoding: chunked
    | date: Tue, 17 May 2022 12:47:23 GMT
    | content-encoding: gzip
    | strict-transport-security: max-age=31536000; preload
    | via: 1.1 google
    | content-type: application/json; charset="utf-8"
    | x-frame-options: SAMEORIGIN
    | x-xss-protection: 1; mode=block
    | x-content-type-options: nosniff
    | server: dart:io with Shelf
IO  : Writing 5170 characters to text file C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\.cache\flutter_lints-versions.json.
FINE: Contents:
    | {"name":"flutter_lints","latest":{"version":"2.0.1","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","repository":"https://github.com/flutter/packages/tree/main/packages/flutter_lints","issue_tracker":"https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+flutter_lints%22","version":"2.0.1","environment":{"sdk":">=2.17.0-0 <3.0.0"},"dependencies":{"lints":"^2.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/2.0.1.tar.gz","published":"2022-04-20T00:02:11.294475Z"},"versions":[{"version":"0.0.0","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins.","version":"0.0.0","homepage":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","environment":{"sdk":">=2.12.0 <3.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/0.0.0.tar.gz","published":"2021-05-05T19:49:34.839383Z"},{"version":"1.0.0-dev.0","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins.","version":"1.0.0-dev.0","homepage":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","environment":{"sdk":">=2.12.0 <3.0.0"},"dependencies":{"lints":"^1.0.0-dev.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/1.0.0-dev.0.tar.gz","published":"2021-05-05T23:57:43.122279Z"},{"version":"1.0.0","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","version":"1.0.0","homepage":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","environment":{"sdk":">=2.12.0 <3.0.0"},"dependencies":{"lints":"^1.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/1.0.0.tar.gz","published":"2021-05-12T17:22:57.364065Z"},{"version":"1.0.1","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","version":"1.0.1","homepage":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","environment":{"sdk":">=2.12.0 <3.0.0"},"dependencies":{"lints":"^1.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/1.0.1.tar.gz","published":"2021-05-13T19:55:08.677550Z"},{"version":"1.0.2","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","version":"1.0.2","homepage":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","environment":{"sdk":">=2.12.0 <3.0.0"},"dependencies":{"lints":"^1.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/1.0.2.tar.gz","published":"2021-05-18T16:25:27.239072Z"},{"version":"1.0.3","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","version":"1.0.3","homepage":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","environment":{"sdk":">=2.12.0 <3.0.0"},"dependencies":{"lints":"^1.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/1.0.3.tar.gz","published":"2021-06-01T22:04:33.837320Z"},{"version":"1.0.4","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","repository":"https://github.com/flutter/packages/tree/master/packages/flutter_lints","issue_tracker":"https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+flutter_lints%22","version":"1.0.4","environment":{"sdk":">=2.12.0 <3.0.0"},"dependencies":{"lints":"^1.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/1.0.4.tar.gz","published":"2021-07-07T18:24:18.658642Z"},{"version":"2.0.0","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","repository":"https://github.com/flutter/packages/tree/main/packages/flutter_lints","issue_tracker":"https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+flutter_lints%22","version":"2.0.0","environment":{"sdk":">=2.17.0-0 <3.0.0"},"dependencies":{"lints":"^2.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/2.0.0.tar.gz","published":"2022-03-18T20:02:01.232637Z"},{"version":"2.0.1","pubspec":{"name":"flutter_lints","description":"Recommended lints for Flutter apps, packages, and plugins to encourage good coding practices.","repository":"https://github.com/flutter/packages/tree/main/packages/flutter_lints","issue_tracker":"https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+flutter_lints%22","version":"2.0.1","environment":{"sdk":">=2.17.0-0 <3.0.0"},"dependencies":{"lints":"^2.0.0"}},"archive_url":"https://pub.dartlang.org/packages/flutter_lints/versions/2.0.1.tar.gz","published":"2022-04-20T00:02:11.294475Z"}],"_fetchedAt":"2022-05-17T14:47:25.232110"}
SLVR:     fact: flutter_lints 2.0.1 depends on lints ^2.0.0
SLVR:       selecting flutter_lints 2.0.1
SLVR:       derived: lints ^2.0.0
IO  : Get versions from https://pub.dartlang.org/api/packages/lints.
IO  : HTTP GET https://pub.dartlang.org/api/packages/lints
    | Accept: application/vnd.pub.v2+json
    | X-Pub-OS: windows
    | X-Pub-Command: get
    | X-Pub-Session-ID: A7759D1F-1BF0-43A9-9198-3FC56B0D6174
    | X-Pub-Environment: flutter_cli:get
    | user-agent: Dart pub 2.17.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on flutter from sdk
SLVR:       fact: flutter_test 0.0.0 from sdk depends on test_api 0.4.9
SLVR:       fact: flutter_test 0.0.0 from sdk depends on path 1.8.1
SLVR:       fact: flutter_test 0.0.0 from sdk depends on fake_async 1.3.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on clock 1.1.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on stack_trace 1.10.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on vector_math 2.1.2
SLVR:       fact: flutter_test 0.0.0 from sdk depends on async 2.8.2
SLVR:       fact: flutter_test 0.0.0 from sdk depends on boolean_selector 2.1.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on characters 1.2.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on charcode 1.3.1
SLVR:       fact: flutter_test 0.0.0 from sdk depends on collection 1.16.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on matcher 0.12.11
SLVR:       fact: flutter_test 0.0.0 from sdk depends on material_color_utilities 0.1.4
SLVR:       fact: flutter_test 0.0.0 from sdk depends on meta 1.7.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on source_span 1.8.2
SLVR:       fact: flutter_test 0.0.0 from sdk depends on stream_channel 2.1.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on string_scanner 1.1.0
SLVR:       fact: flutter_test 0.0.0 from sdk depends on term_glyph 1.2.0
SLVR:         selecting flutter_test 0.0.0 from sdk
SLVR:         derived: term_glyph 1.2.0
SLVR:         derived: string_scanner 1.1.0
SLVR:         derived: stream_channel 2.1.0
SLVR:         derived: source_span 1.8.2
SLVR:         derived: meta 1.7.0
SLVR:         derived: material_color_utilities 0.1.4
SLVR:         derived: matcher 0.12.11
SLVR:         derived: collection 1.16.0
SLVR:         derived: charcode 1.3.1
SLVR:         derived: characters 1.2.0
SLVR:         derived: boolean_selector 2.1.0
SLVR:         derived: async 2.8.2
SLVR:         derived: vector_math 2.1.2
SLVR:         derived: stack_trace 1.10.0
SLVR:         derived: clock 1.1.0
SLVR:         derived: fake_async 1.3.0
SLVR:         derived: path 1.8.1
SLVR:         derived: test_api 0.4.9
SLVR:         fact: flutter 0.0.0 from sdk depends on characters 1.2.0
SLVR:         fact: flutter 0.0.0 from sdk depends on collection 1.16.0
SLVR:         fact: flutter 0.0.0 from sdk depends on material_color_utilities 0.1.4
SLVR:         fact: flutter 0.0.0 from sdk depends on meta 1.7.0
SLVR:         fact: flutter 0.0.0 from sdk depends on vector_math 2.1.2
SLVR:         fact: flutter 0.0.0 from sdk depends on sky_engine from sdk
SLVR:           selecting flutter 0.0.0 from sdk
SLVR:           derived: sky_engine from sdk
IO  : Get versions from https://pub.dartlang.org/api/packages/cupertino_icons.
IO  : HTTP GET https://pub.dartlang.org/api/packages/cupertino_icons
    | Accept: application/vnd.pub.v2+json
    | X-Pub-OS: windows
    | X-Pub-Command: get
    | X-Pub-Session-ID: A7759D1F-1BF0-43A9-9198-3FC56B0D6174
    | X-Pub-Environment: flutter_cli:get
    | X-Pub-Reason: direct
    | user-agent: Dart pub 2.17.0

...
...
...

IO  : Renaming directory C:\src\flutter\.pub-cache\_temp\dirf00913ae to C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\analyzer-3.4.1.
IO  : Deleting directory C:\src\flutter\.pub-cache\_temp\dirf00913ae.
IO  : Deleting directory C:\Users\Gustl\AppData\Local\Temp\pub_401a3871.
ERR : Rename failed, path = 'C:\src\flutter\.pub-cache\_temp\dir9f9b4ec8' (OS Error: Cannot create a file when that file already exists.
    | , errno = 183)
FINE: Exception type: FileSystemException
FINE: dart:io                                                          _Directory.renameSync
    | package:pub/src/io.dart 456:21                                   renameDir.<fn>
    | package:pub/src/io.dart 395:16                                   _attempt
    | package:pub/src/io.dart 454:3                                    renameDir
    | package:pub/src/io.dart 466:5                                    tryRenameDir
    | package:pub/src/source/hosted.dart 882:7                         HostedSource._download.<fn>
    | ===== asynchronous gap ===========================
    | dart:async                                                       Future.catchError
    | package:pub/src/utils.dart 109:52                                captureErrors.wrappedCallback
    | package:stack_trace                                              Chain.capture
    | package:pub/src/utils.dart 122:11                                captureErrors
    | package:pub/src/command.dart 183:13                              PubCommand.run
    | package:args/command_runner.dart 209:27                          CommandRunner.runCommand
    | package:pub/src/command_runner.dart 174:24                       PubCommandRunner.runCommand
    | package:pub/src/command_runner.dart 159:20                       PubCommandRunner.run
    | package:dartdev/dartdev.dart 45:56                               runDartdev
    | C:\b\s\w\ir\cache\builder\sdk\pkg\dartdev\bin\dartdev.dart 11:9  main
---- End log transcript ----

 flutter doctor -v
[√] Flutter (Channel stable, 3.0.0, on Microsoft Windows [Version 10.0.22616.100], locale en-US)
    • Flutter version 3.0.0 at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ee4e09cce0 (8 days ago), 2022-05-09 16:45:18 -0700
    • Engine revision d1b9a6938a
    • Dart version 2.17.0
    • DevTools version 2.12.2

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\src\android\Sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_SDK_ROOT = C:\src\android\Sdk
    • Java binary at: C:\Program Files\Java\jdk-15.0.2\bin\java
    • Java version OpenJDK Runtime Environment (build 15.0.2+7-27)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2022 17.0.6)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools
    • Visual Studio Build Tools 2022 version 17.0.32126.317
    • Windows 10 SDK version 10.0.19041.0

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[√] IntelliJ IDEA Ultimate Edition (version 2022.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2021.2
    • Flutter plugin version 67.1.4
    • Dart plugin version 221.5591.58

[√] VS Code (version 1.66.2)
    • VS Code at C:\Users\Gustl\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension can be installed from:
       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22616.100]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 101.0.4951.67
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 98.0.1108.43

[√] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

This does not happen with dart command executed simultaneously:
dart pub cache clean
dart pub get --verbose

Also note this bug plays a big role in CI via melos when executing melos boostrap, as then flutter pub get is called on every specified subproject in the repository. Therefore some CI workflows break on e.g. windows flutter drive tests.

Thanks @Gustl22 for the detailed report. Would like to know if this only happens on CI or locally too ?
I tried locally per your steps to replicate by cloning the example you shared and then ran the commands for flutter_platform_test and flutter_platform_test_second in two separate terminals for which I observed below:

Ran flutter pub cache clean:

I did get pub 66 exit code but the error seems to be different than you posted.

Ran flutter pub get:

Running dart pub cache clean pretty much gave me similar results, so wondering if this is specific to running concurrently on CI or effects local run too.

Hey @darshankawar, and thank you for testing.
I only could test locally with Windows (11), which could reproduce the error pretty consistent, (but only had one machine to test). Did not test with macOS though. But of course in CI the error occurs more obviously / reliably and on macOS too.
You DO NOT want to execute flutter pub cache clean simultaneously (but this may has the same reason to fail). Otherwise the next step would not fail. The reason for this command is to simulate the clean pub cache, when running in a VM / CI / new project.
You DO want to execute flutter pub get -v simultaneously. (Search for ERR : to get the actual reason)
Also be aware of https://github.com/dart-lang/pub/issues/3404. The error message may vary from time to time as the concurrency may fails at a different spot.

Thanks for the feedback. Although I didn't try to Windows, but performing the same steps based on above input on macOS did run flutter pub get --verbose commands properly simultaneously.

Based on the report and considering the fact that similar issue is open in dart-lang/pub repo, I'll keep this issue open for further insights from the team.

Same issue here, it appears in the messages
Produces the error when the Flutter inspector is launched
Package devtools is currently active at version 2.9.4.
Resolving dependencies...

args 2.3.1
async 2.9.0
browser_launcher 1.1.1
clock 1.1.1
collection 1.16.0
convert 3.0.2
devtools 2.9.4
devtools_server 2.9.4
devtools_shared 2.9.4 (2.14.1 available)
http 0.13.4
http_multi_server 3.2.1
http_parser 4.0.1
intl 0.17.0
logging 1.0.2
meta 1.8.0
mime 1.0.2
path 1.8.2
pedantic 1.11.1
pool 1.5.1
shelf 1.3.1
shelf_proxy 1.0.2
shelf_static 1.1.1
source_span 1.9.1
sse 4.1.0
stack_trace 1.10.0
stream_channel 2.1.0
string_scanner 1.1.1
term_glyph 1.2.1
typed_data 1.3.1
usage 4.1.0
vm_service 8.3.0 (9.3.0 available)
webkit_inspection_protocol 1.1.0
Building package executables...
Built devtools:devtools.

Rename failed, path = 'path\flutter.pub-cache_temp\dir1ceea84b' (OS Error: Cannot create a file when that file already exists.
, errno = 183)
pub finished with exit code 66

FYI: This may be fixed in https://github.com/dart-lang/pub/commit/7ce247439e5d8b04250df2986194f5014d8279a4 (not tested)

FYI: This may be fixed in dart-lang/pub@7ce2474 (not tested)

Sounds good, optimistically closing this as fixed. Feel free to re-open if you verify it is not fixed on the master channel with https://github.com/dart-lang/pub/pull/4120.


Adjusting scales

As of now, the X- and Y-axis are labeled as samples in X and counts in Y axis.
The X-axis should be written in seconds, while the Y-axis should display volts. Currently OmniView is only supporting one type of input device - the AI OmniScope. Each Device comes with a fixed sample rate and two individual calibration-values: offset and scaling. In the near furture @NP199 will make sure, that these informations can be read from the device itself. Until then, we will use one set of fixed values that should be read from the config-file.
{
    "calibration":{
             "samples_per_second": 50000,
             "counts_offset": 45,
             "counts_per_volt": 100
     }
}

Even though these values don't make sense at the moment, they shall be used to scale the X- and Y-axis.

x and y axes ranges are [0, 10], [-10, 200] respectively, with specific values/ticks on Y-axis
Will try to change/enhance it if needed.

As it is implemented in the software and the calibration will be implemented in the next week, this issue will be closed.


Revert "Merge pull request #35137 from DylanDylann/fix/34609"

Details
Reverts https://github.com/Expensify/App/pull/35137 to fix https://github.com/Expensify/App/issues/36175
Fixed Issues
$ https://github.com/Expensify/App/issues/36175
Tests

Created a manual money request
Open the expense
Edit the description and save
Verified the description page is dismissed
Go back
Verified the expense page is dismissed

[ ] Verify that no errors appear in the JS console

Offline tests
None
QA Steps
None

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Typescript check is failing because of this
ERROR: Found new JavaScript files in the project; use TypeScript instead.

which we can ignore since this is just a revert

Please review @marcaaron 🙇

Sorry, didn't see this when I logged on. Has conflicts now !

At this point I'm not sure how to resolve these conflicts. It looks like @DylanDylann and @lindboe were both making changes to IOURequestStepDescription.js and it looks like @lindboe's changes depend on @DylanDylann's. Can either of you help with this?

On my side, when this is re-added, just ensure that policy, policyTags, and policyCategories are passed to all commands that edit requests, so here in updateMoneyRequestDescription.

Hmm maybe we can try to fix it instead of revert... I'll take a quick look to see if it's easy.

Think I figured this one out so gonna close this. Thanks @arosiclair !


Change memcached monitoring to monitor curr_conns

https://github.com/rcbops/rpc-openstack/compare/kilo...bugs/1025-kilo?expand=1Memcached previously monitored total connections, this is does not
tell us useful information, so I changed it to monitor current
connections and also alarm (WARNING) against reaching 90% of the
maximum active connection limit.
memcached_connections is also set globally so that it can be used
in both the memcached role and in the maas role.


[stable/jenkins] helm install failed: Init Crash Loop Back-off

Describe the bug
Unable to install jenkins, got the error Init Crash Loop Back-off
Version of Helm and Kubernetes:
Helm:
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Kubernetes/openshift:
oc version
oc v3.9.60
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth

Server https://master-cnap-00-mp-dev2.bmwgroup.net:8443
openshift v3.9.68
kubernetes v1.9.1+a0ce1bc657

Which chart:
stable/jenkins
What happened:
helm install . --set rbac.create=false --name myjenkins
oc logs myjenkins-748855dbbc-q64ph -p
Error from server (BadRequest): previous terminated container "myjenkins" in pod "myjenkins-748855dbbc-q64ph" not found

oc describe pod myjenkins-748855dbbc-q64ph
Name:           myjenkins-748855dbbc-q64ph
Namespace:      futuremap-ci
Node:           lp00osp09c015/<IP_ADDRESS>
Start Time:     Wed, 05 Jun 2019 09:04:19 +0200
Labels:         app.kubernetes.io/component=jenkins-master
                app.kubernetes.io/instance=myjenkins
                app.kubernetes.io/managed-by=Tiller
                app.kubernetes.io/name=jenkins
                helm.sh/chart=jenkins-1.1.21
                pod-template-hash=3044118667
Annotations:    checksum/config=a254d8e6c6560d248e7e80184dedd30b6a0798bdd94ee6dfbaf88e89ebfa4ba4
                openshift.io/scc=restricted
Status:         Pending
IP:             <IP_ADDRESS>
Controlled By:  ReplicaSet/myjenkins-748855dbbc
Init Containers:
  copy-default-config:
    Container ID:  docker://11e46a3fae9a43730b3c4e4fbc59483ba0fc5440249f81150180eb125f06d73a
    Image:         jenkins/jenkins:lts
    Image ID:      docker-pullable://docker.io/jenkins/jenkins@sha256:08bdd27b066e4ec6bfa1228876551e939df1aeaa9d878e6ddb2b183cd208dc2b
    Port:          <none>
    Command:
      sh
      /var/jenkins_config/apply_config.sh
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 05 Jun 2019 09:07:27 +0200
      Finished:     Wed, 05 Jun 2019 09:08:24 +0200
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 05 Jun 2019 09:05:40 +0200
      Finished:     Wed, 05 Jun 2019 09:06:38 +0200
    Ready:          False
    Restart Count:  1
    Limits:
      cpu:     2
      memory:  4Gi
    Requests:
      cpu:     50m
      memory:  256Mi
    Environment:
      ADMIN_PASSWORD:  <set to the key 'jenkins-admin-password' in secret 'myjenkins'>  Optional: false
      ADMIN_USER:      <set to the key 'jenkins-admin-user' in secret 'myjenkins'>      Optional: false
    Mounts:
      /tmp from tmp (rw)
      /usr/share/jenkins/ref/plugins from plugins (rw)
      /usr/share/jenkins/ref/secrets/ from secrets-dir (rw)
      /var/jenkins_config from jenkins-config (rw)
      /var/jenkins_home from jenkins-home (rw)
      /var/jenkins_plugins from plugin-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from myjenkins-token-6gqv5 (ro)
Containers:
  myjenkins:
    Container ID:
    Image:         jenkins/jenkins:lts
    Image ID:
    Ports:         8080/TCP, 50000/TCP
    Args:
      --argumentsRealm.passwd.$(ADMIN_USER)=$(ADMIN_PASSWORD)
      --argumentsRealm.roles.$(ADMIN_USER)=admin
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     2
      memory:  4Gi
    Requests:
      cpu:      50m
      memory:   256Mi
    Liveness:   http-get http://:http/login delay=90s timeout=5s period=10s #success=1 #failure=5
    Readiness:  http-get http://:http/login delay=60s timeout=5s period=10s #success=1 #failure=3
    Environment:
      JAVA_OPTS:
      JENKINS_OPTS:
      JENKINS_SLAVE_AGENT_PORT:  50000
      ADMIN_PASSWORD:            <set to the key 'jenkins-admin-password' in secret 'myjenkins'>  Optional: false
      ADMIN_USER:                <set to the key 'jenkins-admin-user' in secret 'myjenkins'>      Optional: false
    Mounts:
      /tmp from tmp (rw)
      /usr/share/jenkins/ref/plugins/ from plugin-dir (rw)
      /usr/share/jenkins/ref/secrets/ from secrets-dir (rw)
      /var/jenkins_config from jenkins-config (ro)
      /var/jenkins_home from jenkins-home (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from myjenkins-token-6gqv5 (ro)
Conditions:
  Type           Status
  Initialized    False
  Ready          False
  PodScheduled   True
Volumes:
  plugins:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  tmp:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  jenkins-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      myjenkins
    Optional:  false
  plugin-dir:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  secrets-dir:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  jenkins-home:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  myjenkins
    ReadOnly:   false
  myjenkins-token-6gqv5:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  myjenkins-token-6gqv5
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  region=primary
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
Events:
  Type     Reason                 Age               From                    Message
  ----     ------                 ----              ----                    -------
  Normal   SuccessfulMountVolume  4m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "myjenkins-token-6gqv5"
  Normal   SuccessfulMountVolume  4m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "tmp"
  Normal   SuccessfulMountVolume  4m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "plugin-dir"
  Normal   SuccessfulMountVolume  4m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "secrets-dir"
  Normal   SuccessfulMountVolume  4m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "plugins"
  Normal   SuccessfulMountVolume  4m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "jenkins-config"
  Normal   Scheduled              4m                default-scheduler       Successfully assigned myjenkins-748855dbbc-q64ph to lp00osp09c015
  Normal   SuccessfulMountVolume  3m                kubelet, lp00osp09c015  MountVolume.SetUp succeeded for volume "pvc-2363ada1-8760-11e9-8e1d-fa163ea202e3"
  Normal   Pulling                1m (x2 over 3m)   kubelet, lp00osp09c015  pulling image "jenkins/jenkins:lts"
  Normal   Pulled                 1m (x2 over 2m)   kubelet, lp00osp09c015  Successfully pulled image "jenkins/jenkins:lts"
  Normal   Created                1m (x2 over 2m)   kubelet, lp00osp09c015  Created container
  Normal   Started                59s (x2 over 2m)  kubelet, lp00osp09c015  Started container
  Warning  BackOff                0s                kubelet, lp00osp09c015  Back-off restarting failed container

oc get events
LAST SEEN   FIRST SEEN   COUNT     NAME                                          KIND                    SUBOBJECT                                  TYPE      REASON                       SOURCE                        MESSAGE
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e4e8eabd3   Pod                                                                Normal    Scheduled                    default-scheduler             Successfully assigned myjenkins-748855dbbc-q64ph to lp00osp09c015
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e57c1c103   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "tmp"
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e57c25770   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "plugin-dir"
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e57c556a2   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "secrets-dir"
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e57c5fe51   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "plugins"
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e58d06556   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "jenkins-config"

8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b7e595f8b30   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "myjenkins-token-6gqv5"
8m          8m           1         myjenkins-748855dbbc-q64ph.15a53b827ce28e59   Pod                                                                Normal    SuccessfulMountVolume        kubelet, lp00osp09c015        MountVolume.SetUp succeeded for volume "pvc-2363ada1-8760-11e9-8e1d-fa163ea202e3"
2m          8m           4         myjenkins-748855dbbc-q64ph.15a53b833318b0f1   Pod                     spec.initContainers{copy-default-config}   Normal    Pulling                      kubelet, lp00osp09c015        pulling image "jenkins/jenkins:lts"
2m          7m           4         myjenkins-748855dbbc-q64ph.15a53b90d6257012   Pod                     spec.initContainers{copy-default-config}   Normal    Pulled                       kubelet, lp00osp09c015        Successfully pulled image "jenkins/jenkins:lts"
2m          7m           4         myjenkins-748855dbbc-q64ph.15a53b90f370eab7   Pod                     spec.initContainers{copy-default-config}   Normal    Created                      kubelet, lp00osp09c015        Created container
2m          7m           4         myjenkins-748855dbbc-q64ph.15a53b91080c459e   Pod                     spec.initContainers{copy-default-config}   Normal    Started                      kubelet, lp00osp09c015        Started container
2m          4m           3         myjenkins-748855dbbc-q64ph.15a53bb7b8f85aff   Pod                     spec.initContainers{copy-default-config}   Warning   BackOff                      kubelet, lp00osp09c015        Back-off restarting failed container
1h          16h          154       myjenkins-748855dbbc-zkrzj.15a506cead929bcb   Pod                     spec.initContainers{copy-default-config}   Normal    Pulling                      kubelet, lp00osp09c019        pulling image "jenkins/jenkins:lts"
9m          16h          3581      myjenkins-748855dbbc-zkrzj.15a506e9fe62d6ec   Pod                     spec.initContainers{copy-default-config}   Warning   BackOff                      kubelet, lp00osp09c019        Back-off restarting failed container
8m          8m           1         myjenkins-748855dbbc.15a53b7e4d4c5f7e         ReplicaSet                                                         Normal    SuccessfulCreate             replicaset-controller         Created pod: myjenkins-748855dbbc-q64ph

What you expected to happen:
pod would be started normally
How to reproduce it (as minimally and precisely as possible):
helm install . --set rbac.create=false --name myjenkins
Anything else we need to know:
I changed 2 parameter in values.yaml:

usePodSecurityContext: false
serviceType: NodePort

Thank you!
Best regards
Joao

I am getting a similar error wherein the Jenkins chart won't deploy correctly. However, I am getting the below are the events I am getting:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  34s (x5 over 39s)  default-scheduler  pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
  Warning  FailedScheduling  34s                default-scheduler  AssumePod failed: pod 940c1d9e-880d-11e9-bb74-b2740e7c6771 is in the cache, so can't be assumed

To rollout Jenkins I am using: helm install stable/jenkins --set master.servicetype=NodePort --name jenkins

@orange-ly Have you been able to resolve the error? Did you check the logs of the pod?
One need to figure out why the pod can't start. Is it an error in the init container or another one. Does your pod have internet access? By default it's trying to download and install plugins...

getting a similar issue
in the logs
(curl -sSfL --connect-timeout 20 --retry 3 --retry-delay 0 --retry-max-time 60 https://updates.jenkins.io/download/plugins/credentials-binding-plugin/kubernetes/credentials-binding-plugin.hpi -o /usr/share/jenkins/ref/plugins/credentials-binding-plugin.jpi)

fails with 404 from with GKE but also locally from my laptop

@didil Can you share your values.yaml. I assume there is something wrong with the plugins.
The correct URL for the plugin is http://mirrors.jenkins-ci.org/plugins/credentials-binding/1.19/credentials-binding.hpi
master:
  installPlugins:
    - kubernetes:1.16.0
    - workflow-job:2.32
    - workflow-aggregator:2.6
    - credentials-binding:1.19
    - git:3.10.0

@torstenwalter great thanks I ended up using the values from the readme and they worked. The issue was that I was using an old config from a 0.16 version which had outdated installPlugins values => 404


chore(docs): update Notification Manager Service documentation

chore(docs): update Notification Manager Service documentation

I included the new version in the release note of v13.4.


Hidden temporary file causes upload_photos_by_exif ordering by timestamp to fail

I just uploaded this sequence: http://openstreetview.com/details/27578/0
Notice that the picture order is completely wrong. Since the ordering by EXIF time stamp was added to the upload script I was surprised by this. But it turns out I had a file named .GOPR1874.JPG.DRuZYO in the directory. It was zero bytes in size and looks like something left over from either an interrupted rsync or maybe a batch imagemagick job. But it was enough to cause the exist_timestamp variable on line 359 to be set to false which then disabled EXIF sorting on the whole batch. This caused sorting to fall back to mtime which is completely jumbled up for some reason in this directory.
After I deleted this file, the sequence uploaded in the correct order here: http://openstreetview.com/details/27580/0
I'm thinking the upload script should either ignore hidden files (granted, "hidden" files on a unix system is just a naming convention...) or maybe only upload files with .JPG at the end. Or both?

Thanks for reporting. I will fix this bug as you recommend by upload only .jpg files 👍