Try to fix artifact storage & retrieval for release

No idea why this changed, must be a conda infrastructure thing (?)

I suppose it's because I switched to using MSYS2 on Windows.
In any case, keeping this for now for the artifact identifier used for up-/downloading on our CI system, while dropping the suffix from our produced artifact filenames

keeping this for now for the artifact identifier used for up-/downloading on our CI system

Can we change this, too? It would be nice not to have to remember or see this weird extra name anywhere other than our standard name-mangling location tools/extract_version.sh

keeping this for now for the artifact identifier used for up-/downloading on our CI system

Can we change this, too? It would be nice not to have to remember or see this weird extra name anywhere other than our standard name-mangling location tools/extract_version.sh

No idea, I have to admit I can barely figure out anymore what's going on and where; things have gotten too complex for to handle for my limited shell skills :(

@larsoner One difficulty is that the architecture during downloading artifacts for the release is different from the arch during uploading, as we do the release on Ubuntu for all artifacts.

:+1:

@larsoner Artifacts for testing should appear at https://github.com/mne-tools/mne-installers/releases/tag/untagged-206c90cf42605d7206d3 any minute now.


[Experimental] Coalesce/parse nested inline tags

The compiler should now handle things like:
<time><span>**Foo**</span></time>

Current coverage is 94.87% (diff: 100%)

Merging #80 into master will increase coverage by 0.03%

@@             master        #80   diff @@
==========================================
  Files             1          1
  Lines           155        156     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            147        148     +1
  Misses            8          8
  Partials          0          0

Powered by Codecov. Last update 5645a27...3187066


Consider striping and omitting DWARF in Go packages

When building go packages, we might want to make it an option to pass -ldflags="-s -w".
Per the Go docs:
-s
    Omit the symbol table and debug information.
-w
    Omit the DWARF symbol table.

See the following for more details:

https://golang.org/cmd/link/
https://blog.filippo.io/shrink-your-go-binaries-with-this-one-weird-trick/
https://news.ycombinator.com/item?id=11515612

Regarding -w, that should just strip the debugging symbols, leaving enough for readable panic info. Also, we shouldn't forget to do this when building go itself (e.g. go build -ldflags="-s -w" cmd/go), which supposedly can drop the size down to ~9.0MB from ~12.5MB.

The normal strip utility is already run in fixupPhase, so they're partially stripped already, but maybe the Go tools can strip it more. It would be nice to have numbers on some Go packages.

triage: fixed?


IE11 appears to default to a mobile view for admin login

Despite requesting a desktop version of the site.

Chrome and Firefox are the only supported browsers. See
https://github.com/HubPress/hubpress.io/blob/master/README.adoc#browser-compatibility
On Mon, Apr 25, 2016, 12:51 Rory Hayes<EMAIL_ADDRESS>wrote:

Despite requesting a desktop version of the site.
[image: image]
https://cloud.githubusercontent.com/assets/908662/14772667/dad9f568-0a55-11e6-9787-e67c9cecc7d4.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/HubPress/hubpress.io/issues/376

--
Sent from Mobile.


Error while implementing NBi testing framework for database

Hi,
I am trying to implement NBI testing for one of the databases. I've created .nbits fie in which I've given connection string and valid username and password. But when I execute the test I get an error 'Login failed for user ...'
Can you please help me resolve this error?

It just means that your connection string is not valid, your user have no access to this database.

I'm using the connection string exactly same way its mentioned in the examples in NBI documentation. Also, the user has access to the database. The user can connect to the database without any issue while connecting through SSMS, but get an error 'Login failed' in NBI.
Please advise.

if you want some help you need to provide some information. Nobody could help you with the few information you've distilled. If you just copy/paste most of the connection strings found in the documentation they won't work because they are just fake.
Could you, at least, post your connection string and previously check that you don't use a connection string with SQL Server authentication information when your server is configured to use Windows authentication.

Our server is configured to Windows authentication; what should be the syntax of connection string in such case?

Connection strings can look differently. Let me google it for you: https://www.connectionstrings.com/sql-server/
As soon as you can connect with the same user from another client (e.g. Excel) with this connection string, it will work with NBi. "Login failed" suggests that the actual user who tries to connect does not have a login on the server. Debug this first, NBi requires working connections.
Try to build a connection with Excel and take out the information out of the connection properties and put it into the required connection string. Does that help?
Perhaps an admin can help you setting up connections to a database, too :)
Cheers

We are using following connection string:
<query connectionString="Data Source=SMSPPRODM01;Initial Catalog=CAReporting_Dev;User Id=REDMOND\smsprpt;password=***********">
Our SQL server is configured with Windows authentication.
User that is executing code i.e. 'REDMOND\smsprpt' has access to SMSPPRODM01 server.
Even then we are getting login failed error. Screenshot below

Connection string is borrowed from an Excel connection with same data source.

Guys,
If your server is configured for Windows Authentication then you don't need to provide the user and password in your connection string.

We have tried that approach too but in that case test case fails stating an error 'Login is failed for user ' '

connectionString="Data Source=Server_Name;Initial Catalog=Database_Name;Integrated Security=true"

It worked. Thanks for your help.


Locust performance on windows pretty bad

Prerequisites

[X] I am using the latest version of Locust
[X] I am reporting a bug, not asking a question

Description
I have written some tests. They work fine when run as a single user. However when run in bulk to stress test, my computer spits out the CPU warning very early with not that many users. In addition if I consult the CPU chart on my machine, its showing almost no activity (<10%). Finally the response times shown on the stats page are heavily inflated indicating that the test is lagging out.
What my test does is effectively take a json dictionary, compress it and send it as a post request. Not much else. Here is relevant samples of how I am doing that:
jsonDict = {
    "Lang":"en",
    "Shard":1,
    "Adid":"Tester",
    "Platform":"ios",
    "Device":"Locust"
}
result = self.sendWebRequest("Create",jsonDict,validate_create_response)

def sendWebRequest(self, requestName, jsonDict, validator):
    json_string = json.dumps(jsonDict, indent=4)  # 'indent' is optional but makes the output more readable

    gzipped_data = gzip.compress(json_string.encode())
    headers = {
        'Content-Type': 'application/octet-stream'
    }
    url = "/"+requestName+"Request"
    with self.client.post(url=url, data=gzipped_data,headers=headers,catch_response=True) as response:

My CPU is an AMD Ryzen 9 5900x 12 core with 32 gigs of ram.
The reporting data shows average of 7000ms when the true average is probably around 200ms
Even if I run a tiny test it gets the cpu warning:
[2024-01-17 14:02:16,852] DESKTOP-NVIJ1JN/INFO/locust.runners: All users spawned: {"MyUser": 20} (20 total users)
[2024-01-17 14:02:17,362] DESKTOP-NVIJ1JN/WARNING/root: CPU usage above 90%! This may constrain your throughput and may even give inconsistent response time measurements! See https://docs.locust.io/en/stable/running-distributed.html for how to distribute the load over multiple CPU cores or machines
Command line
locust
Locustfile contents
Many files, relevant sections are described in the post.

Python version
3.12.1
Locust version
2.20.1
Operating system
Windows 10

[LocustTester.zip](https://github.com/locustio/locust/files/13969407/LocustTester.zip
Source if needed.

I ran this same test on linux and the problem did not occur FYI

You’re not really meant to call .stop() on users. Perhaps that is the issue? Your use case is a little too complex for me to investigate. You’ll need to narrow it down, preferably with a minimum reproducible example https://stackoverflow.com/help/minimal-reproducible-example

I called stop because I need the user to die and a fresh one be created as the sequence of the test cannot be repeated with the same user id

I was able to improve this by optimizing out a lot of json deserialization. Its still not acceptable but I don't know that its related to windows so closing this.


Add Lithuanian holidays

https://keliauk.urm.lt/kita-informacija/lietuvos-respublikos-valstybines-sventes

PR looks good! I'll keep this upon so others can verify the results in the snapshot are correct.


CDAP-15246. Fix macros checks, remove deprecated API usage, some minor fixes

Fix Streaming plugin validation failure when macros are present in credentials.
When building Salesforce project, there is warning since the deprecated API is used.
.../salesforce-plugins/src/main/java/co/cask/hydrator/salesforce/plugin/source/streaming/SalesforcePushTopicListener.java uses or overrides a deprecated API.
Rewrote the code to avoid using deprecated method org.cometd.bayeux.Message#getJson
For generating json from message in new API jackson or jetty has to be used. Using jackson in our case.
PushTopicNotifyCreate, pushTopicNotifyUpdate, pushTopicNotifyDelete are marked as nullable but based on widget configuration, they can not be null.
Rename constants "PUSHTOPIC" -> "PUSH_TOPIC"

  protected static final String PROPERTY_PUSHTOPIC_NAME = "pushTopicName";
  protected static final String PROPERTY_PUSHTOPIC_QUERY = "pushTopicQuery";

Add final:
private static Pattern isValidFieldNamePattern = Pattern.compile("[a-zA-Z0-9.-_]+");

@albertshau PR is ready to be merged.


How to keep the rq worker active when there's job waiting to process

Dear Jezdez,
I have a flask web app and I am trying to use your flask-rq2 to manage the async queue.
Due to the nature of async, I've written a separate worker. (I've tried to start the worker inside my web app but without success.). The code the worker is simple.
import os
from app import rq, create_app

app = create_app(os.getenv('FLASK_CONFIG') or 'default')
with app.app_context():
    worker = rq.get_worker("high")
    worker.work(burst=True)

when I run my web app, I start the worker simply using:  python worker.py.
It worked to listen to the queue and process the job inside the queue. However, when the jobs are done, it quit automatically.
Is there a way to keep this worker active all the time. or how it can start automatically when there's job enter the queue?
I'm new to the queue management with rq. any best practice advice to use your package would be very appreciated.
Thanks a lot,

Oh, sure, just remove the burst=True option when calling worker.work above. This will basically keep the worker running and wait for new queued jobs.
It's strongly recommeded to use the flask rq worker command line tool in the upcoming version instead of writing an own worker going forward. Hope this helps.


Fix all_permissions function path

The partial all_permissions is pointing to ('modules/permission/lib/queries/permission/get_all') is missing. Changing the path to 'modules/permission/get_permissions' seems to fix it. Although I think it may be better to instead add queries, commands, and hook folders in the permission module, and keep the original path as is.

Thanks for your contribution, but it's already fixed in https://github.com/Platform-OS/pos-module-permission/pull/2


Feature Request: Option to specify time range for downloads

I’ve been using SW-DLT for a week or so and it's amazing. Thank you for this tool! I do have a feature request that would make it even more useful for specific needs—
It would be great if the shortcut could leverage yt-dlp's ability to trim a download to a specific time range. I often need to save only specific parts of longer videos. Being able to specify a start and end time for the download would save me from having to manually trim down a much longer download after the fact.
For instance, I often need only a 30-second clip from a 2-hour news broadcast.
I am intermediately savvy with shortcuts but not quite enough to do a pull request or fork and add this feature myself. Any assistance, input, or consideration for this feature would be greatly appreciated.
Thank you for your hard work and the amazing tool!

That sounds useful, I'm going to add it into the list of features, however I'm working on these as time allows


Add flutter support + improve language-specific aspects

Improvements:

Better buttons
Hide tabs for other languages (all tabs can be enabled for debugging)
Add generic header
Add WARN if guide is incomplete for the language
Remove missing SEP-10 feature for TS

Preview is available here:http://developers-pr179.previews.kube001.services.stellar-ops.com


OUTPUT TEXT FILES INCLUDES INSUFFICIENT DATA

The script collects the various threading processes used in scanning implementation. We will work on rectifying that issue.

Still working on implementing new features


ghost players in offline mode

What is the current behavior?
When a player leaves and joins an offline server quickly, a clone of the player is created
What is the expected behavior?
That the previous player entity leaves before the next one joins
What steps will reproduce the problem?
leave and join a server with mojang auth enabled in quick succession
What operating system and java version is being used?
windows 10 java 11
Additional information / Possible thoughts on why this bug is happening
Probably due to a netty channel not being terminated correctly

leave and join a server with mojang auth enabled in quick succession
I think you mean disabled

I had this happen to me during testing with a group.  He did not disconnect, rather he joined the world, then was quickly kicked.  He never told me the message, but a version of him floated at the spawn point.  He then rejoined, yet the floating "player" was still there.

Fixed in the current in-progress branch.


fix multisig

reference: https://dashtalk.org/threads/dash-electrum-v0-2-4-1-support.6498/page-3#post-85137

ACK
Odd, the multisig version is correct elsewhere. We must have missed it.

Fixed with #22


/train destroyall -command kills vanilla minecarts

Info

BkCommonLib:  1.16.4-v2-SNAPSHOT Build: 790
TrainCarts:  1.16.4-v3-SNAPSHOT Build: 972
Server Type: Paper-1.16.4 Build: 323

Bug
/train destroyall -command kills vanilla minecarts
Description
Maybe this is intended behaivior, but i personally rate it as a bug.
If i use /train destroyall or /train removeall it removes all vanilla minecarts in every loaded chunk,
instead of just only destroying all known trains.
Expected behaviour
Destroy trains only.

Actual behaviour
Vanilla minecarts are destroyed too.
Steps to reproduce
Spawn some vanilla minecarts (e.g. with /summon) and use /train destroyall while you're looking at the recently spawned minecarts and watch your minecarts disappearing.
Video: https://craft-together.de/~irgendsoeintyp/2020-12-12_13-34-46.mp4
Additional Information
This Bug is not new.
But it is very hard to maintain a survival-server with a big railway-network if you just can't destroy all trains with a command because you have to fear players are loosing their (vanilla-)minecarts.
Sorry for my english.. Still learning :)

Would be nice to have sub-commands to choose an action.
Like:
/train
destroyall
all
trains
minecarts

This can be closed because it is now possible with the new command-flags

Thank you!

This can be closed because it is now possible with the new command-flags

Thank you!


tools: add dsq

Motivation: as an alternative to octosql and experiments with the idea sql for everything.
Source: https://github.com/multiprocessio/dsq.

https://github.com/kamilsk/dotfiles/commit/78dce2efebeb64d3c3b5b21b3541b5054da33701


Alert on unsupported client

Followup - when we have our wrapper, we'll need to update the cop to disallow using Net::HTTP directly in favor of it.

Let's have our wrapper published before we merge this.


Fix handling g_variant_iter_next

Arguments passed to g_variant_iter_next should be freed
in every iteration:
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-iter-next

Nice change, LGTM.


support for Lambert conformal conic grid mapping in NetCDF files

adaption of fc_rules_cf.krb for loading NetCDF-files with a LCC projection.
compare-operator for LambertConformal projection.
elif branch for saving LCC grid_mapping.
test for loading such a file (pull request for iris-test-data has been sent)

Thanks @mir06 :+1: This is a very useful fix & extension, which I'd love to merge ... it's very close to being ready. It won't take much to fix the secant_latitudes issue (I'm happy to help if you'd like), and please could you update the copyright period at the start of the file to extend to 2016.
Would you mind signing the CLA as linked from CONTRIBUTING.md? (Sorry for the admin - you only need to do this once!)

I'll sign and send the CLA right now.

I'll sign and send the CLA right now.

Thanks :smile: I'm off for day so I won't be able to deal with it until Fri. @marqh would you mind helping? (Or ask someone else in the office?)

Thanks :smile: I'm off for day so I won't be able to deal with it until Fri. @marqh would you mind helping? (Or ask someone else in the office?)

@mir06  recieved and processed, many thanks;
welcome to SciTools

The only remaining blocker to merging this in its current form is getting the test data merged.

@rhattersley and all developers
I'm glad to contribute a bit to your great project. Many many :+1:

@rhattersley i pushed the corrected test-data some weeks ago. Are there any other obstacles for merging?

Are there any other obstacles for merging?

Thanks for the nudge. I've merged the test data, so now you just need to update IRIS_TEST_DATA_REF in .travis.yml so that it points to the latest commit:
  - export IRIS_TEST_DATA_REF="c1ac751ef41a2d0032f597e247bb962406b31cfa"

Hopefully all the tests will pass on Travis-CI at that point.

The test-data ref here needs to be changed to the one on master, which is now to a later revision. Also, a rebase to remove the extra merge and other commits wouldn't be unwarranted.

This is awesome. Thanks @mir06!
A few things I would love to see:

[ ] - a what's new entry
[ ] - a test for saving LambertConformal data

In order to prevent the death by a thousand cuts, I'd be happy to merge this as it is and have those in a subsequent PR (happy to help).
Otherwise, I think this is good to go. @rhattersley - your call on the todo list above.

@pelson I'll do those two new PR as soon as possible

I'll do those two new PR as soon as possible

@mir06 - I've sent you a PR which should sort this out already (I must have started it just before you posted - sorry).

(BTW. In sending you that PR I realised you'd been working on your "master" branch. I would recommend working in a branch in the future.)

@rhattersley are there still obstacles for merging? please let me know.

Thank you @mir06. This was a super contribution and I think it will make a real difference to anybody wanting to use Lambert Conformal.
:+1: :tada:


I get an error when updating

Try uninstall inference-cli and reinstall inference-cli[yolo-world]

Okay, I'll try it now.

Find the lines inference-cli[yolo-world]>=0.13.0,  inference-gpu[yolo-world]>=0.13.0 in the requirements.txt, comment them out with "#",  and manually install these two dependency packages

Enter in this command in Python environment directory of ComfyUi:
python.exe -m pip install "inference-cli[yolo-world]>=0.13.0" "inference-gpu[yolo-world]>=0.13.0"


timeseries tabular predictions result in "['unique_id'] not found in axis" error

Bug Report Checklist

[X] I provided code that demonstrates a minimal reproducible example.
[ ] I confirmed bug exists on the latest mainline of AutoGluon via source install.
[X] I confirmed bug exists on the latest stable version of AutoGluon.

Describe the bug
Thanks for your work here. Unfortunately, I am unable to run tabular predictions using the AutoGluon Timeseries quickstart minimal example and the latest release version (1.0.0) or the latest dev version (1.0.1b20240301). I have the same error with other datasets, column naming conventions, and configurations.
The error messages are different but possibly related to issue 3862.
Expected behavior
Minimal example should work with all model types and tabular forecasts should work in general.
To Reproduce
%pip install autogluon.timeseries==1.0

import pandas as pd
from autogluon.timeseries import TimeSeriesDataFrame, TimeSeriesPredictor

df = pd.read_csv("https://autogluon.s3.amazonaws.com/datasets/timeseries/m4_hourly_subset/train.csv")
train_data = TimeSeriesDataFrame.from_data_frame(
    df,
    id_column="item_id",
    timestamp_column="timestamp"
)

predictor = TimeSeriesPredictor(
    prediction_length=48,
    path="autogluon-m4-hourly",
    target="target",
    eval_metric="MASE",
)

predictor.fit(
    train_data,
    time_limit=600,
    hyperparameters={
        "RecursiveTabular":{},
        "DirectTabular":{},
    },
    verbosity=4,
)

Screenshots / Logs
Beginning AutoGluon training... Time limit = 600s
AutoGluon will save models to '/autogluon-m4-hourly'
=================== System Info ===================
AutoGluon Version:  1.0.0
Python Version:     3.10.12
Operating System:   Linux
Platform Machine:   x86_64
Platform Version:   #58~20.04.1-Ubuntu SMP Mon Jan 22 17:15:01 UTC 2024
CPU Count:          16
GPU Count:          0
Memory Avail:       104.32 GB / 119.47 GB (87.3%)
Disk Space Avail:   126.07 GB / 146.59 GB (86.0%)
===================================================

Fitting with arguments:
{'enable_ensemble': True,
 'eval_metric': MASE,
 'hyperparameters': {'DirectTabular': {}, 'RecursiveTabular': {}},
 'known_covariates_names': [],
 'num_val_windows': 1,
 'prediction_length': 48,
 'quantile_levels': [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9],
 'random_seed': 123,
 'refit_every_n_windows': 1,
 'refit_full': False,
 'target': 'target',
 'time_limit': 600,
 'verbosity': 2}

Inferred time series frequency: 'H'
Provided train_data has 148060 rows, 200 time series. Median time series length is 700 (min=700, max=960).

Provided dataset contains following columns:
	target:           'target'

AutoGluon will gauge predictive performance using evaluation metric: 'MASE'
	This metric's sign has been flipped to adhere to being higher_is_better. The metric score can be multiplied by -1 to get the metric value.
===================================================

Starting training. Start time is 2024-03-01 22:21:22
Models that will be trained: ['RecursiveTabular', 'DirectTabular']
Training timeseries model RecursiveTabular. Training for up to 200.0s of the 599.9s of remaining time.
	Warning: Exception caused RecursiveTabular to fail during training... Skipping this model.
	"['unique_id'] not found in axis"
Training timeseries model DirectTabular. Training for up to 299.8s of the 599.6s of remaining time.
	Warning: Exception caused DirectTabular to fail during training... Skipping this model.
	"['unique_id'] not found in axis"
Not fitting ensemble as no models were successfully trained.

 It was an issue with the package install locations in the remote environment I was using (Databricks) causing pip to report package versions that weren't actually being used.


Corrected Typo

Corrected "Phone Nember" to "Phone Number"

Corrected Typo in "Phone Nember" to "Phone Number"


Scheduling not used for systemd timers

The role offers schedule_* variables for each backup task to define the time to run the backup. However, those variables are only respected for cron jobs. Systemd timers are always set up to run once per night between 2 and 5.
https://github.com/roles-ansible/ansible_role_restic/blob/c5126af60b8fd09b159dec8a4c12acf85749accb/templates/restic.timer.j2#L4-L6
Multiple backup tasks might run at quite different times, increasing the chance of an inconsistent backup. It also forces you to run application-level backups before 2 o'clock.
(I wasn't sure if this is covered by #9, because it does not mention specifics.)

We now support some variables for systemd timers

So, how to change the oncalendar value for systemd? It's still doesn't seem to be supported...


actions/notify - add support for message attribtues in sns transport

resolves: https://github.com/capitalone/cloud-custodian/issues/2649

@kapilt agreed, did some testing locally but wanted to formally inspect the message in a test. Didn't think to do the SNS -> SQS flow but that makes sense.

Just curious. Was this PR included in the latest (<IP_ADDRESS>) release? I don't see it in the release notes, but it was merged before the release was published.
Thanks!


EmailJS logs interfere with app logs. Should be at Trace level

Email Js log are console.log strings and are of not json structure. This screws up the app's json logs being accumulated in logstash and utilized in elastic search.
E.g. Elevate portal deployed in aws, use emailJS, but logs created by Emailjs are a problem.

Is the issue still open? Can I work on it?


Create url pattern for question_detail view ie put , patch , delete , update

Hey it's modelviewset, we don't need to add additional URL patterns in urls.py. They will work already just by providing  in the end. Did I understand something wrong based on issue title?

is it up for claims or what ?

i think question view_set route is not yet used in the urls only answer_viewset is present as router
am i wrong? is there any work around for question viewset
i am new to model viewset so it would be helpful

is it up for claims or what ?
please wait , i will inform in a bit
i am closing it for now

feel free to comment here on question_viewset router , i think you can do that in a closed issue

makes sense 👍 . PR is merged


Invalid props in ResponsiveProvider

Issue Report
There are some problems related to proptypes.
Expected Behavior

breakpoints should not trigger a warning.
mediaQueries and breakpointsMax should have clear shapes.

Actual Behavior

breakpoints is giving an invalid prop warning.
mediaQueries and breakpointsMax have PropTypes.any.

Steps to Reproduce the Issue
You can test this with yarn test

:tada: This issue has been resolved in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[docs] Updated README

Coverage remained the same at 73.529% when pulling 27e0554b7b56f1779e60615a8e70c11d944b9c9a on feature/readme-fixes into 904c960fa98063dab8bef014b1289344bc0b169f on develop.


No checking for taking address of a bit-field

struct S {
    int a:1;
};

void foo() {
    struct S s;
    int *p = &s.a;
}

I am always aware of this but left it.

Haha, it's a feature!


Add legrandinone platform to communicate with Legrand PLC devices

Description:
New platform to communicate with legrand in one PLC devices using an USB to PLC gateway.
Code based on RFLink platform.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#7232
Example entry for configuration.yaml (if applicable):

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hello @boblegal31,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

8e3fd191e240c38a526933fcd60245964200bfb4 - This commit has something that looks like an email address (boblegal31@github.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:


⚠ Guya.moe Proxied has degraded performance

In 1f125dd, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 12948 ms

Resolved: Guya.moe Proxied performance has improved in eecd441 after 25 minutes.


BigQuery Time Values May Be Incorrect

On the _datetime_from_json function, @arterrey commented that

I'm getting values out of BigQuery in seconds. So * 1000.0 is not enough - it needs to be * 1000000.0 to work. However, I'm not sure if that is a bug in the BigQuery API or a bug in this client library.

This contradicts the note in the code that

Field value will be in milliseconds.

@arterrey Can you elaborate where you are "getting values out of BigQuery in seconds"? Like an example use of this library and how the output differs from what you expect?

The field value from the web interface is "2012-06-12 08:05:14 UTC". From the pdb session below you can see that the value returns a dattime in the 1970 rather then 2012.
(Pdb) list 762
757     def _bool_from_json(value, field):
758         if _not_null(value, field):
759             return value.lower() in ['t', 'true', '1']
760
761
762     def _datetime_from_json(value, field):
763         if _not_null(value, field):
764             import pdb; pdb.set_trace()
765             # Field value will be in milliseconds.
766  ->         return _datetime_from_microseconds(1000.0 * float(value))
767
(Pdb) value
u'1.33948831400937E9'
(Pdb) float(value)
1339488314.00937
(Pdb) _datetime_from_microseconds(1000.0 * float(value))
datetime.datetime(1970, 1, 16, 12, 4, 48, 314009, tzinfo=<UTC>)
(Pdb) _datetime_from_microseconds(1000000.0 * float(value))
datetime.datetime(2012, 6, 12, 8, 5, 14, 9370, tzinfo=<UTC>)
(Pdb)

That's really great info! Thanks for showing the pdb stack.
It looks like
value == 1339.488314009370

Which request did you make to retrieve this data? Can you provide a code snippet?

I think you mean
    value ==<PHONE_NUMBER>.00937

just using fetch_data...
    def fetch_table(data_set, table_name):

        table = data_set.table(table_name)
        assert table.exists()
        table.reload()

        next_page = None

        while (True):
            rows, total_count, next_page = table.fetch_data(page_token=next_page)
            for row in rows:

                # use schema to convert tuple into dict
                row_dict = {}
                for i in range(len(table.schema)):
                    field = table.schema[i]
                    row_dict[field.name] = row[i]

                yield PathableDict(row_dict)

            if next_page is None:
                break

Sorry I overlooked the actual value:
(Pdb) value
u'1.33948831400937E9'

It seems that instead of
datetime.timedelta(microseconds=1000.0 * float(value))

we should just be using
datetime.timedelta(seconds=float(value))

Like you said, the value is seconds, not milliseconds.
I couldn't find any evidence of "seconds" in the discovery doc:
https://www.googleapis.com/discovery/v1/apis/bigquery/v2/rest
FWIW the bigquery.tabledata.list returns a TableDataList, and the schema for that type has TableDataList.rows a list of TableRow, which in turn has TableRow.f a list of TableCell which then is an any type (which is kind of a black hole).
I'm off to bed for now but will try to throw in some test data (from our system tests) and inspect the output on the APIs explorer:
https://developers.google.com/apis-explorer/#p/bigquery/v2/bigquery.tabledata.list
Also FWIW our link in our docstring:
https://cloud.google.com/bigquery/reference/rest/v2/tabledata/list
is broken. It should be:
https://cloud.google.com/bigquery/docs/reference/v2/tabledata/list

Really just
rows, total_count, next_page = table.fetch_data(page_token=next_page)

was what I was looking for. Thanks!

I just created a table with the following schema:
[
   {
    "name": "Timestamp",
    "type": "TIMESTAMP",
    "mode": "REQUIRED"
   },
   {
    "name": "Description",
    "type": "STRING",
    "mode": "REQUIRED"
   },
   {
    "name": "Quantity",
    "type": "INTEGER",
    "mode": "REQUIRED"
   },
   {
    "name": "Unit_Price",
    "type": "FLOAT",
    "mode": "REQUIRED"
   }
]

and uploaded the following data:
$ cat /tmp/with_timestamp.csv
2015-09-09T17:59:22Z,Testing,1,2.5

In the developer console, the data looks like:
Row  Timestamp                Description  Quantity Unit_Price
1    2015-09-09 17:59:22 UTC  Testing      1        2.5

In the API explorer, tabledata.list returns:
{
 "kind": "bigquery#tableDataList",
 "etag": "\"m-9bZ2XqlR7n8jGvqgVmLOTsm1s/xddlFZR3Ob1xPfHtKV-u3wV2TLU\"",
 "totalRows": "1",
 "rows": [
  {
   "f": [
    {
     "v": "1.441821562E9"
    },
    {
     "v": "Testing"
    },
    {
     "v": "1"
    },
    {
     "v": "2.5"
    }
   ]
  }
 ]
}

The Preparing data for bigquery docs don't specify how timestamps are returned, only the formats which can be used to load the data.  It does say,

BigQuery stores TIMESTAMP data internally as a UNIX timestamp with microsecond precision.

So what shall we do? Also, how does 2015-09-09T17:59:22Z,Testing,1,2.5 make it through our pipeline?

Given that the values are always returned as scientific-formatted floats of seconds (unlike datastore timestamps, which are stored as microseconds), we should be using float(value).

How does 2015-09-09T17:59:22Z,Testing,1,2.5 make it through our pipeline?

ISO-8660 strings are one of the supported formats for loading TIMESTAMP data.

I mean what is the codepath.

Client.load_table_from_storage could trigger that path.

I see. So the CSV goes directly through GCS, so our code doesn't actually handle the timestamp string?

Yup.  Table.insert_data expects clients to pass in real Python datetime.datetime instances for TIMESTAMP fields.


installation fails with nodejs version 16

Hello,
the official ioBroker docker image uses nodejs version 16, since they recommend using that version.
Unfortunately the latest version of homebridge-nb does require version 18.13.0 at minimum resulting in following error output:
2023-01-25 19:50:08.618  - info: ham.0 (1734) npm install homebridge-nb --production  --loglevel error (System call)
2023-01-25 19:50:09.536  - info: ham.0 (1734) npm
2023-01-25 19:50:09.536  - info: ham.0 (1734)  ERR! code EBADENGINE

2023-01-25 19:50:09.537  - info: ham.0 (1734) npm ERR!
2023-01-25 19:50:09.538  - info: ham.0 (1734)  engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Required: {"homebridge":"^1.6.0","node":"^18.13.0"}
npm ERR! notsup Actual:   {"npm":"8.19.3","node":"v16.19.0"}

2023-01-25 19:50:09.539  - info: ham.0 (1734)

2023-01-25 19:50:09.540  - info: ham.0 (1734) npm ERR! A complete log of this run can be found in:
npm ERR!     /opt/iobroker/.npm/_logs/2023-01-25T18_50_08_842Z-debug-0.log

2023-01-25 19:50:09.546  - error: ham.0 (1734) Error: Library homebridge-nb not installed after 3 attempts

Is there any chance to require a lower node version <=16.15.0 ?
Thanks in advance
Dean

I develop and test my plugins against the latest LTS version of NodeJS.  That’s the version listed in package.json.  They might or might not run on other versions; I simply don’t have the bandwidth to test nor support these.

Thanks so much for your time and consideration.
If anyone else falls into my scenario, running the official ioBroker docker container, therefore being stuck on Version 16 of node, you can give it an unsupported shot by manually installing the plugin.
Simply move the git repository into the "node_modules" directory, which might be /opt/iobroker/node_modules/iobroker.ham/noide_modules.
Afterwards add to the homebridge adapters package.json (which might be at /opt/iobroker/node_modules/iobroker.ham/package.json) the dependency like that:
  "dependencies": {
    [...]
    "homebridge-nb": "^1.3.1",
    [...]
  },

Restart and good luck.
As pointed out by @ebaauw, that might or might not work. At least in my setup with node 16.15.0 it works flawlessly.


Publish image to DockerHub

Building the docker image takes quite long (> 30mins) so this should really be made available to people to download.

Publishing an image to DockerHub under an organisational account requires a paid for subscription. We therefore publish to ghcr.io instead and that workflow is working so closing this issue.


ITVR - Console utility to update DL#

New utility in Console to change the DL# if an applicant enters it wrong
Description:
Build a new component where an IDIR user can update the DL#. This could be done so that a record of the original DL# is retained, but only as a record, so that the DL# could be released in case it belongs to someone else.
Need to consider keeping a record of the changes made so that gov users can trace back any changes made to DL#'s
Wireframe: Al to add something?
Purpose and benefit to user:
This has been a reoccurring issue that so far has been made as a direct data fix in the DB by a developer. This will allow the ITVR Business Admin the capability to update a DL# directly in the console.
Acceptance Criteria:

[ ] Given I am a ITVR Business Admin, When I am logged into the ITVR console, then I can search for a rebate by DL# or application ID # and update and save the DL#

Development Checklist:

[ ] Create history table for storing old drivers licences
[ ] Add function that will save old drivers license to new history table when updating the record
[ ] Add that functionality to the console with an editable text box, so idir users can change the drivers license number and then save it. Do it the same way that Cancel Application is done but make sure that it adds to the history table.

Notes:

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @emi-hi @jig-patel @JulianForeman @tim738745 @vibhiquartech

Two comments:

It would have been good to allow letters to be used when editing the DL# (e.g. for the person with no license)
It would be better if you could access the history of changes tot he DL# form the main application. Or they were linked in some more intuitive way.


Heroku Deploy failed

Hi,
When i copy the repo on Heroku, it built good but:

When i tried to enter with URL, Heroku shows an error:

And there are no errors in the log.

Hello @danjimgar ,
If there is no logs, could you contact Heroku for more info, theirs Support team is open and respond quickly.
And what deploy/installation method?

Hello @danjimgar ,
Is this issue solved?

Closed due to silence at issue owner end.
Feel free to reopen it in case if the issue still persists on your end.


Using Own VPS instead

Project is awesome , I wonder if I could use my own vps instead of using data . If there is any way please guide me.
Regards

yes you can use uvicorn and gunicorn

can you please explain a bit ? I would appriciate if you can guide to deploy it on my local machine / vps with out using deta.


remove needless recursive call on message unfinished in guacd and listener socket

https://github.com/m-expunged/guacamole-sharp/blob/cdd27ad409e0014d878aee1f23ea188524755748/GuacamoleSharp.Server/GSListener.cs#L291

nvm recursive call is correct here and is needed for unfinished messages...


Can't compile - spread operator

Hello,
I am trying to use this module in a Laravel app and using WebPack, and I can't seem to get it to work. I'm getting the following error:
ERROR in ./node_modules/vue-mdc-adapter/components/util/link.js
Module parse failed: Unexpected token (19:35)
You may need an appropriate loader to handle this file type.
|       // router-link case
|       element = this.$root.$options.components['router-link']
|       data.props = {tag: this.tag, ...this.link}
|     } else {
|       // element fallback
 @ ./node_modules/vue-mdc-adapter/components/util/index.js 5:0-25
 @ ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}],"es2015","stage-3"],"plugins":["transform-object-rest-spread","transform-es2015-destructuring","transform-object-rest-spread","syntax-object-rest-spread","transform-object-assign","transform-es2015-parameters"]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0&bustCache!./node_modules/vue-mdc-adapter/components/button/mdc-button.vue
 @ ./node_modules/vue-mdc-adapter/components/button/mdc-button.vue
 @ ./node_modules/vue-mdc-adapter/components/button/index.js
 @ ./node_modules/vue-mdc-adapter/components/index.js
 @ ./resources/assets/js/app.js
 @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss

After much research and googling I've realized the problem is the spread operator is the problem and I've tried about everything I can as far as babel plugins to fix it. However, I've been completely unsuccessful. At the moment I've got a .babelrc that has all sorts of stuff I likely don't need in an effort to get this to work:
{
  "presets" : [
    "es2015", "stage-3"
  ],
  "plugins": [
	"transform-es2015-destructuring",
	"transform-object-rest-spread",
	"syntax-object-rest-spread",
	"transform-object-assign",
	"transform-es2015-parameters"
  ]
}

Any help or suggestions would be most welcome.

Have you tried using babel-preset-env? It's recommended by Babel.

I just tried it and it has the same result unfortunately. I've tried
many different plugins trying to get this project to work because I
really want to use it but I've been stuck on this issue for quite a
while now. Any other ideas? I assume you use webpack / babel so
certainly you must have something different in your config than mine.

griest024<EMAIL_ADDRESS>November 30, 2017 at 4:10 PM
Have you tried using |babel-preset-env|? It's recommended by Babel.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stasson/vue-mdc-adapter/issues/138#issuecomment-348321876,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxvL-4-T-4GjAqigNbBQ_p9pvsvj3oOks5s7xnjgaJpZM4QxMUb.

Try importing vue-mdc-adapter/dist

That did it! But why?

griest024<EMAIL_ADDRESS>November 30, 2017 at 4:41 PM
Try importing |vue-mdc-adapter/dist|
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stasson/vue-mdc-adapter/issues/138#issuecomment-348329961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxvL7z46cNE1ogFXIfdy5Ss4N0EkLR9ks5s7yEWgaJpZM4QxMUb.

The dist folder holds the precompiled versions of the components. I'm not sure why Babel couldn't compile it for you but that's something funky with your own environment, not this library.

Thanks for the help!

griest024<EMAIL_ADDRESS>November 30, 2017 at 4:46 PM
The |dist| folder holds the precompiled versions of the components.
I'm not sure why Babel couldn't compile it for you but that's
something funky with your own environment, not this library.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stasson/vue-mdc-adapter/issues/138#issuecomment-348331043,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxvL5OeyIp5X4ZktCRBtk_a5oFbGqNUks5s7yIXgaJpZM4QxMUb.

@coogle
Your babel config looks good. Although preset es2015 is a obsolete and it's probably better to use preset env with latest babel:

This is the minimal config i'd use for webpack + vue + vue-router + vue-mdc-adapter

{
   ["env", { "modules": false }]
  "plugins": [
    "transform-object-rest-spread",
    "syntax-dynamic-import"
  ],
  "presets": [
  ],
}

The problem is most probably that code in node_modules do not get transpiled in your webpack config: vue-mdc-adapter and @material source distribution is es6 and need to be transpiled in order to build from source. It's missing from the doc

// babel loader config
  {
    test: /\.js$/,
    loader: 'babel-loader',
    include: [
      path.resolve(__dirname, 'node_modules/@material')
      path.resolve(__dirname, 'node_modules/vue-mdc-adapter')
    ]
  }

Note you do that only if you want to build for source.
As @griest024  said, You can build using the pre-built distribution.  This is probably the easiest.
I fix the doc...

in next release, new ESM distribution will be transpiled so it should work seemlessly with webpack ...


feat(privatek8s): add Jenkins controller

This PR add the Jenkins controller intended for infra.ci.jenkins.io, without the corresponding jobs definitions (for another PR)
Follow-up of https://github.com/jenkins-infra/kubernetes-management/pull/3247
Remaining changes of https://github.com/jenkins-infra/kubernetes-management/pull/3194
Ref: https://github.com/jenkins-infra/helpdesk/issues/2844

LGTM


dashboard - when a list of skills is returned, display the employees associated

list all employees in a references section on the dashboard
when a individual skill is selected, highlight which employees have those skills

this looks to have been addressed in a recent commit in which drilling down into a skill profile page displays the list of employees associated with it


Reconfigure Header Fields

I setup httpManager like this
extension AppDelegate: HTTPManagerConfigurable {
    func configure(httpManager: HTTPManager) {
        httpManager.environment = APIConfig.staging
            ? HTTPManager.Environment.Staging
            : HTTPManager.Environment.Production

        let config = URLSessionConfiguration.default
        config.timeoutIntervalForRequest = 10
        httpManager.sessionConfiguration = config

        if let token = AuthManager.JWTToken {
            httpManager.defaultHeaderFields.addValue("Bearer \(token)", forHeaderField: "Authorization")
        }

        httpManager.defaultRetryBehavior = HTTPManagerRetryBehavior
            .retryNetworkFailureOrServiceUnavailable(withStrategy: .retryTwiceWithDefaultDelay)
    }
}

Then I have a case when user log out and log in again.
The header fields token is not refreshed.
I have to close the app then open it again to make it work.
How do I handle this case and Is there a way to reset header fields?

You can modify the defaultHeaderFields property at any time, not just within this function. Modifications to that property won't affect any requests that have already been created, but it will affect requests created after the modification.
That said, you may want to investigate the defaultAuth property instead, which is the preferred way of dealing with the "Authorization" header. That property is designed to support multiple different auth mechanisms, including allowing the auth object to handle a 401 Unauthorized, refresh its credentials, and automatically retry the request (e.g. for implementing OAuth token refresh). I don't know the details of your auth scheme, so I don't know if you can make use of the flexibility of this object. If you really just have a string value that you want to provide, then this property may not get you anything.

I just try defaultAuth and it seems to work properly now.
Thank you very much.


Doesn't download, just finishes without downloading anything.

As the title suggests, running node index.js doesn't download any photos. The command just exits.

The same for me. I cannot download unsplash photos anymore.

Same for me :(

I already made a pull request that fixes this bug, which is due to the unsplash website removing pagination and having a page that loads as it scrolls. The fork with the fixed code is in my repository.


add back suppression of CA1811 on new Bypass method

@yizhong-ms,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[spark] Support scala 2.13

Purpose
Prepare for #3940

Support scala 2.13

Ensure that the same code can be compiled in Scala 2.12 and Scala 2.13, the most noteworthy thing is that: we can not use scala.jdk.CollectionConverters (for compatibility with Scala 2.12), we can only use scala.collection.JavaConverters, and need to manually specify the output type (for compatibility with Scala 2.13) such as JList.asScala.toSeq
new profile -Pscala-2.13 to change to Scala2.13, default is still Scala2.12

Introduce utitcase-spark and utitcase-spark-scala2.13 CI

Tests

API and Format

Documentation

LGTM. @JingsongLi please take a look.


Create an SQL database for future features

Potential features that will require a database:

Peak elo tracker (throughout all seasons)
Elo history (throughout all seasons)
Character mains icon if we decide to add specific character mains next to leaderboard names

clan leaderboard history

main purpose is to retrieve most recently saved retrieved data in case of reaching API limit request on / leaderboard command


feat: upgrade to PHP 8.2RC6 and use the official PHP builds

Upgrade to PHP 8.2RC6 and don't compile our own PHP now that https://github.com/docker-library/php/pull/1342 and https://github.com/docker-library/php/pull/1331 are merged.

This won't work, at least for alpine images because it doesn't build libphp.so and they don't seem to want to add it because it adds too much to the image size.

This breaks seamless PECL support on Alpine, fyi:
RUN pecl install xdebug
pecl/xdebug requires PHP (version >= 7.2.0, version <= 8.1.99), installed version is 8.2.0RC6

@jamogriff it's broken everywhere, even using install-php-extensions xdebug won't work. It isn't compatible so it can't be installed.


Update asv links in contributing guide

asv is on PyPI, so install from there instead of the git repo
Update some links that are out of date

Thanks, @dstansby !


[DataGrid] Columns to have a fluid width

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
As the data-grid document says, By default, the columns have a width of 100 pixels. We can override it by using the width property available in ColDef.
Is there an option for columns to have a fluid width so that columns will get a proportion of the width of the container?

Examples 🌈
<div style={{ width: "100%"}}>
<DataGrid
  columns={[
    { field: 'id' },
    { field: 'username' },
    { field: 'age' },
  ]}
  rows={rows}
/>
</div>

If my window width is 900px. The column with for 'id', 'username' and 'age' should be 300px each.
Columns should resize automatically when window width changes.

Motivation 🔦
In most of the table components, I have worked with, this is the default behavior. Is there a way to accomplish this using column props?? or should this be a new feature??

@amiranga Why did you close the issue?

I also need this behavior
A workaround would be to use the following style overrides:
         {
            colCell: {
              flex: 1,
              minWidth: "1px !important",
              maxWidth: "none !important"
            },
            viewport: {
              "& .rendering-zone": {
                width: "initial !important",
                maxWidth: "initial !important"
              }
            },
            row: {
              width: "100% !important"
            },
            colCellWrapper: {
              display: "flex"
            },
            cell: {
              flex: 1,
              minWidth: "1px !important",
              maxWidth: "none !important",
              "&:last-of-type": {
                minWidth: "0 !important",
                flex: 0
              }
            }
         }

Do not provide width for the columns in the ColDef[] array


[#1895] Make extended metadata url clickable

I implemented this as a reusable class. It can be used to make occurrences of URLs inside some element clickable.
Example:
To initialize on page load add the class "url-clickable" to your item:
Some text and a URL https://github.com/hydroshare/hydroshare/issues/898
To initialize dynamically call the urlClickable method:
$("#mySelector").urlClickable();

@hyi, I made the changes you've suggested and adjusted some of the style in these tabs for consistency.
I also found and fixed a bug causing errors when typing in the same URL multiple times in one entry.

@mauriel133 +1 from me.


Implement stdev and variance for all distributions

Fixes #530.

Codecov Report

Merging #1596 (829a8b1) into develop (14e7d44) will decrease coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head 829a8b1 differs from pull request most recent head c02e660. Consider uploading reports for the commit c02e660 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##           develop    #1596      +/-   ##
===========================================
- Coverage    73.12%   73.09%   -0.03%
===========================================
  Files           93       93
  Lines         5030     5069      +39
  Branches       846      847       +1
===========================================
+ Hits          3678     3705      +27
- Misses        1327     1338      +11
- Partials        25       26       +1

see 9 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Build Mac wheels in CI

Hi @scotts
Looks like problem with the build
pip install TorchCodec-0.0.4.dev0-cp39-cp39-macosx_11_0_arm64.whl
pip install --pre torchvision --index-url https://download.pytorch.org/whl/nightly/cpu
conda install "ffmpeg=4.4.2" -c conda-forge

and then executing smoke tests:
python test/decoders/manual_smoke_test.py
zsh: segmentation fault  python test/decoders/manual_smoke_test.py


feat: add username and password to es client

thank you so much for contribution.
could you add these fields to README.md?


Fix disabled color not being customizable for LinkButton

Fixes #83748
The property for changing the LinkButton's disabled color was there, but it was not being shown in the editor. It should be visible now.

This is actually a part of a larger issue: #82402
Adding a theme property will change the default appearance of LinkButton, so it's probably too late to do it for 4.2.

Oh that makes sense, so should I close this in favour of fixing the larger issue instead?

Adding a theme property will change the default appearance of LinkButton, so it's probably too late to do it for 4.2.

Can we add a default theme that looks like the current appearance (i.e. black text) for 4.2, then change it later to something that looks better for 4.3?

The issue I linked has 4.2 milestone (not sure if it's still planned for that version though), so adding black color as an ad-hoc fix is not necessary. If anything this PR could be repurposed as style enhancement.

I'm happy to change it either way! If we do not use black, is the control_font_disabled_color ok?

I think at this point we'll probably go with the proper solution for the issue. That said, adding a style for disabled linked button, as KoBeWi mentions, is still an appropriate thing to do. But in 4.3.
In the mean time, dould you please squash your commits into one? Make sure that the final commit has a short but descriptive message (the title of this PR is a good option). See this documentation, if you need help with squashing.

I think at this point we'll probably go with the proper solution for the issue.

Absolutely, that makes a lot of sense.

In the mean time, dould you please squash your commits into one?

It should be done now. Thank you for the pointer!


Fix partition handling by always using string values

Always use string representation of the value to compute the partition so that the value from query can always match the value from the segment.
Fix the wrong handling of BYTES and BIG_DECIMAL type as partition column

Codecov Report
Attention: 36 lines in your changes are missing coverage. Please review.

Comparison is base (e207844) 61.64% compared to head (04f71c5) 46.47%.
Report is 2 commits behind head on master.

Files
Patch %
Lines

...ot/common/request/context/RequestContextUtils.java
33.33%
8 Missing and 2 partials :warning:

...local/indexsegment/mutable/MutableSegmentImpl.java
0.00%
6 Missing :warning:

...processing/partitioner/TableConfigPartitioner.java
33.33%
2 Missing and 2 partials :warning:

.../impl/stats/AbstractColumnStatisticsCollector.java
0.00%
2 Missing :warning:

.../stats/BigDecimalColumnPreIndexStatsCollector.java
0.00%
2 Missing :warning:

...impl/stats/BytesColumnPredIndexStatsCollector.java
0.00%
2 Missing :warning:

...impl/stats/DoubleColumnPreIndexStatsCollector.java
0.00%
2 Missing :warning:

.../impl/stats/FloatColumnPreIndexStatsCollector.java
0.00%
2 Missing :warning:

...or/impl/stats/IntColumnPreIndexStatsCollector.java
0.00%
2 Missing :warning:

...r/impl/stats/LongColumnPreIndexStatsCollector.java
0.00%
2 Missing :warning:

... and 1 more

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #12115       +/-   ##
=============================================
- Coverage     61.64%   46.47%   -15.18%
+ Complexity     1153      945      -208
=============================================
  Files          2406     1808      -598
  Lines        130851    95077    -35774
  Branches      20218    15343     -4875
=============================================
- Hits          80665    44188    -36477
- Misses        44287    47737     +3450
+ Partials       5899     3152     -2747

Flag
Coverage Δ

custom-integration1
?

integration
?

integration1
?

integration2
?

java-11
?

java-21
46.47% <48.57%> (-15.04%)
:arrow_down:

skip-bytebuffers-false
46.47% <48.57%> (-15.14%)
:arrow_down:

skip-bytebuffers-true
?

temurin
46.47% <48.57%> (-15.18%)
:arrow_down:

unittests
46.47% <48.57%> (-15.17%)
:arrow_down:

unittests1
46.47% <48.57%> (-0.23%)
:arrow_down:

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hi @Jackie-Jiang @snleee @swaminathanmanish , thanks for making the code changes in this PR! We really appreciate the contribution here. While we do have some concerns on making the backward incompatible changes not just for this PR (i.e. changing the signature of a public API) but for all the future PRs, as any incompatible changes could easily impact the existing running Pinot use cases and requires admins to verify, not just for 1 cluster in 1 company but for all the Pinot clusters run in different places/companies.
If possible, can we do the following if the backward incompatibility is inevitable in the future PR:

tag the PR with incompatible label, and at least ask for more reviewers from different companies (like StarTree, LinkedIn, Uber, etc).
add the migration plan/action items to the PR if it's marked as backward incompatible, so that same steps can be followed by different companies to avoid anything unexpected.

By following this steps we can at least have someone to keep an eye on the incompatible changes from multiple stakeholders and have consensus promptly instead of merging it silently. Again, we really appreciate the contribution here and look forward to building the great milestones to come together! Thanks!

@jackjlli Thanks for the suggestion! Going forward, will add a section to list all the public API changes in the PR description.
The backward incompatible changes (non API changes) are more critical because it might be hard to catch. We should always handle backward compatibility for consecutive releases, and use multiple releases to maintain backward compatibility.


HomeKit crashes trying to load battery sensor

Home Assistant release with the issue:
0.101.3
Last working Home Assistant release (if known):
~0.99 (I think...maybe 0.98)
Operating environment (Hass.io/Docker/Windows/etc.):
Docker running on Ubuntu
Integration:
HomeKit
Description of problem:
As of (I think) 0.100, my HomeKit config doesn't load. I get the stack trace below indicating that self.hass.states.get(self.linked_battery_sensor).state is returning NoneType for the .get() call.
The only device I have in my HomeKit config that would have a battery AFAIK is a Schlage Z-Wave door lock.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
homekit:
  auto_start: false
  entity_config:
    climate.downstairs:
      name: Downstairs
    climate.upstairs:
      name: Upstairs
    light.back_outdoor_flood_lights_level:
      name: Back Flood Lights
    light.front_outdoor_flood_lights_level:
      name: Front Flood Lights
    light.stairs_light_level:
      name: Stairs Light
    lock.kitchen_door_lock:
      name: Kitchen Door Lock
      linked_battery_sensor: sensor.kitchen_door_lock_battery
    media_player.spotify:
      feature_list:
        - feature: play_pause
        - feature: play_stop
    sensor.dark_sky_daytime_high_temperature:
      name: Daytime High
    sensor.dark_sky_overnight_low_temperature:
      name: Night Low
    sensor.dark_sky_temperature:
      name: Current
    sensor.downstairs_thermostat_humidity:
      name: Humidity
    sensor.upstairs_thermostat_humidity:
      name: Humidity
    switch.office_heated_blanket_switch:
      name: Heated Blanket
  filter:
    include_domains:
      - climate
      - fan
      - light
      - lock
      - media_player
      - sensor
      - switch
    exclude_entities:
      # Exclude the individual light strips. The light strip group will be included.
      - light.light_strip_bar_1
      - light.light_strip_bar_2
      - light.light_strip_bar_3
      - light.light_strip_kitchen_1
      - light.light_strip_kitchen_2
      - light.light_strip_kitchen_3
      # Hide the on/off switch for the plugs we don't ever want to toggle
      - switch.bar_coffee_maker
      - switch.bar_dishwasher
      - switch.kitchen_dishwasher
      - switch.washer
      - switch.washer_pedestal
      # Others we don't care about in HomeKit
      - sensor.dark_sky_temperature_0d
      - sensor.downstairs_thermostat_target
      - sensor.downstairs_thermostat_temperature
      - sensor.laundry_room_multisensor_temperature
      - sensor.upstairs_thermostat_target
      - sensor.upstairs_thermostat_temperature
      - switch.kitchen_island_lights_secondary_switch
      - switch.master_bed_light_left_switch
      - switch.master_bed_light_right_switch
      - switch.pi_hole_ad_blocking_enabled

automation:
  # Start HomeKit after a bit, which gives Z-Wave and other components time to start up.
  - alias: 'Start HomeKit'
    initial_state: true
    trigger:
      - platform: homeassistant
        event: start
    action:
      - delay: 00:05
      - service: homekit.start

Traceback (if applicable):
11/10/2019 4:47:04 PM2019-11-10 16:47:04 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
11/10/2019 4:47:04 PMTraceback (most recent call last):
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 190, in async_run
11/10/2019 4:47:04 PM    await self._handle_action(action, variables, context)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 274, in _handle_action
11/10/2019 4:47:04 PM    await self._actions[_determine_action(action)](action, variables, context)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 357, in _async_call_service
11/10/2019 4:47:04 PM    context=context,
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 97, in async_call_from_config
11/10/2019 4:47:04 PM    domain, service_name, service_data, blocking=blocking, context=context
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/core.py", line 1236, in async_call
11/10/2019 4:47:04 PM    await asyncio.shield(self._execute_service(handler, service_call))
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/core.py", line 1263, in _execute_service
11/10/2019 4:47:04 PM    await self._hass.async_add_executor_job(handler.func, service_call)
11/10/2019 4:47:04 PM  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
11/10/2019 4:47:04 PM    result = self.fn(*self.args, **self.kwargs)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/components/homekit/__init__.py", line 168, in handle_homekit_service_start
11/10/2019 4:47:04 PM    homekit.start()
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/components/homekit/__init__.py", line 379, in start
11/10/2019 4:47:04 PM    self.add_bridge_accessory(state)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/components/homekit/__init__.py", line 348, in add_bridge_accessory
11/10/2019 4:47:04 PM    acc = get_accessory(self.hass, self.driver, state, aid, conf)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/components/homekit/__init__.py", line 265, in get_accessory
11/10/2019 4:47:04 PM    return TYPES[a_type](hass, driver, name, state.entity_id, aid, config)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/components/homekit/type_locks.py", line 36, in __init__
11/10/2019 4:47:04 PM    super().__init__(*args, category=CATEGORY_DOOR_LOCK)
11/10/2019 4:47:04 PM  File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 109, in __init__
11/10/2019 4:47:04 PM    battery_found = self.hass.states.get(self.linked_battery_sensor).state
11/10/2019 4:47:04 PMAttributeError: 'NoneType' object has no attribute 'state'

Additional information:

I've confirmed that removing the lock domain from the homekit integration fixes the issue.


mega slow Complete writing plot

it makes me wonder why renaming/moving plot on same device takes over 60s latest Beta CUDA plotter
/c-tmp/plot-k32-c07-....plot.tmp -> /c-tmp/plot-k32-c07-....plot Completed writing plot in 74.57 seconds
/c-tmp is SSD/NVMe with XFS...after forced trim, it is now 71s.
such a file operation usually takes <1s
Is it a bug?

I'm also seeing this behavior.

Guys from chiaforum said it is normal - explained by Harold himself in Chia Discord.

I believe he's making a fix for this.

Guys from chiaforum said it is normal - explained by Harold himself in Chia Discord.

Completed Plot 1 in 162.94 seconds ( 2.72 minutes )
Completed writing plot in 7.03 seconds

This is currently fixed in a testing branch, and should make its way to dev soon.

Completed Plot 1 in 151.47 seconds ( 2.52 minutes )

/ramdisk/plot-k32-c07-......plot.tmp -> /ramdisk/plot-k32-c07....plot
Completed writing plot in 18.71 seconds
```

using `ramdisk` as [suggested](https://github.com/Chia-Network/bladebit/issues/375) by harold

Note that to use tmpfs as a ram output directory on Linux you need to build your own bladebit with this change applied:
--- a/src/plotting/GlobalPlotConfig.h
+++ b/src/plotting/GlobalPlotConfig.h
@@ -33,1 +33,1 @@
-    bool            disableOutputDirectIO  = false;            // Do not use direct I/O when writing the plot files
+    bool            disableOutputDirectIO  = true;             // Do not use direct I/O when writing the plot files

As Linux tmpfs does not support O_DIRECT. It'd be ideal to have that as a command line option, or for PlotWriter() to fall back automatically to non-direct-io when open returns EINVAL.
bladebit can "write" the plot to tmpfs in a seconds this way and you can have a separate process monitoring that to offload it to ssd while bladebit is already working on the next plot.
Also: run ./embed-version.sh before you build if you don't want to see the placeholder 0.0.0-dev version.

Or use block based ramdisk brd


OpenAIGym Environment does not support Dict/nested spaces

I built a gym environment for a problem I'm working on. My action space looks like:
import gym
from gym import spaces

class MultipleMoverGridWorld(gym.Env):
    ...
    def __init__(self):
        self.action_space = spaces.Dict({
        "mover{}".format(i): spaces.Discrete(5) \
                for i in range(self.n_movers)
        })

with each mover in my grid world having 5 possible actions (up/down/left/right/null). My environment allows multiple movers to change position each time step. I get the following error when trying to get the tensorforce actions:
---------------------------------------------------------------------------
TensorForceError                          Traceback (most recent call last)
<ipython-input-515-20ed75416bda> in <module>()
----> 1 OpenAIGym.action_from_space(space=env.action_space)

~\AppData\Local\ESRI\conda\envs\cpd\lib\site-packages\tensorforce\contrib\openai_gym.py in action_from_space(space)
    150             return actions
    151         else:
--> 152             raise TensorForceError('Unknown Gym space.')

TensorForceError: Unknown Gym space.

Near as I can tell, I should be able to implement the functionality in tensorforce as:
actions = {
    "mover{}".format(i): dict(type='int', num_actions=5) \
            for i in range(self.n_movers)
}

I can definitely work on a PR for this if there's interest, but definitely want to check if there's a workaround first. I have my environment implemented as an OpenAI gym and would prefer not to reimplement as a tensorforce environment if I have the option. :)
EDIT: I should also add that this is only a minimal example of this: my action space will be a little more complex in the future.

Hey, this is just due to a missing conversion of gym.spaces.Dict (maybe a more recent feature, because I think we implemented all existing space types back then). Hence I would suggest modifying/extending the tensorforce.contrib.openai_gym.py file accordingly in a PR (here and here), instead of implementing your own TensorForce environment. The conversion should be straightforward, since we are using only dicts.

Yes, sure, that would be welcome! Similar to how the branch for gym.spaces.Tuple does already flatten arbitrary nesting, I would expect that concatenating the dict key strings with '-' or so could work. We never actually experimented with nested spaces, I think, so you might also need some 'unpacking' in the execute method, which doesn't at all exist yet.

Ah, I see what you mean! I hadn't noticed the recursion in the case for gym.spaces.Tuple. I'll implement the same functionality for gym.spaces.Dict and think about where the unpacking needs to occur.


libmediainfo: 18.03.1 -> 18.05

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libmediainfo/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 18.05 with grep in /nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05
directory tree listing: https://gist.github.com/74cf8ceacead58990e67775b627a172a
du listing: https://gist.github.com/a515ce2cc6f6d9f886c1948aa1d3e561

meta.description for libmediainfo is: '"Shared library for mediainfo"'.
cc @devhell for testing.

Success on x86_64-linux (full log)
Attempted: libmediainfo
Partial log (click to expand)
removed '/nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05/lib/pkgconfig/libmediainfo.pc'
'libmediainfo.pc' -> '/nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05/lib/pkgconfig/libmediainfo.pc'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05
shrinking /nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05/lib/libmediainfo.so.0.0.0
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05/lib
patching script interpreter paths in /nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05
checking for references to /build in /nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05...
/nix/store/5qyyi56b38pqwkrz245xv8skn3bsflzg-libmediainfo-18.05

Success on x86_64-darwin (full log)
Attempted: libmediainfo
Partial log (click to expand)
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/private/tmp/nix-build-libmediainfo-18.05.drv-0/MediaInfoLib/Project/GNU/Library/test'
make[1]: Leaving directory '/private/tmp/nix-build-libmediainfo-18.05.drv-0/MediaInfoLib/Project/GNU/Library/test'
removed '/nix/store/a0iwrnkj0dhvz356s9zwzpibh41cwcam-libmediainfo-18.05/lib/pkgconfig/libmediainfo.pc'
'libmediainfo.pc' -> '/nix/store/a0iwrnkj0dhvz356s9zwzpibh41cwcam-libmediainfo-18.05/lib/pkgconfig/libmediainfo.pc'
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/a0iwrnkj0dhvz356s9zwzpibh41cwcam-libmediainfo-18.05/lib
patching script interpreter paths in /nix/store/a0iwrnkj0dhvz356s9zwzpibh41cwcam-libmediainfo-18.05
/nix/store/a0iwrnkj0dhvz356s9zwzpibh41cwcam-libmediainfo-18.05

Success on aarch64-linux (full log)
Attempted: libmediainfo
Partial log (click to expand)
removed '/nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05/lib/pkgconfig/libmediainfo.pc'
'libmediainfo.pc' -> '/nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05/lib/pkgconfig/libmediainfo.pc'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05
shrinking /nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05/lib/libmediainfo.so.0.0.0
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05/lib
patching script interpreter paths in /nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05
checking for references to /build in /nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05...
/nix/store/q81a0yvdmf53cag1nmn6my86p8xxb3x4-libmediainfo-18.05


default static route test

static route test with the following steps

Test case steps:

Configures DUT interfaces port1 and port2 with VRF name VRF1
Configure DUT Interface with IPv4 and IPv6 Address
Configures OTG interfaces and creates
Create Traffic flow with Src address of OTG port 1 interface and dst address of 203.0.113.x
Configure default static route under VRF VRF1
Verify traffic flow has no loss

Pull Request Functional Test Report for #2588 / 13ba9bbe10af948fa2ea920083c6db74d7e6e283
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-1.25: Management network-instance default static route

Cisco 8000E

RT-1.25: Management network-instance default static route

Cisco XRd

RT-1.25: Management network-instance default static route

Juniper cPTX

RT-1.25: Management network-instance default static route

Juniper ncPTX

RT-1.25: Management network-instance default static route

Nokia SR Linux

RT-1.25: Management network-instance default static route

Openconfig Lemming

RT-1.25: Management network-instance default static route

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-1.25: Management network-instance default static route

Cisco 8808

RT-1.25: Management network-instance default static route

Juniper PTX10008

RT-1.25: Management network-instance default static route

Nokia 7250 IXR-10e

RT-1.25: Management network-instance default static route

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1729

Relevant Lines:
3256

💛  - Coveralls

Hi @mihirpitale-googler / @nraghavendran / @AmrNJ
If there are no pending change request can we kindly merge this its been sitting for some time.


Update podman

Currently CI is broken
docker pull quay.io/containers/podman:v4.7.2@sha256:f3671cf897e2a8745c926ff2720a990fb350815a85d5b6fd58f4d5cb58ef458d
Error response from daemon: manifest for quay.io/containers/podman@sha256:f3671cf897e2a8745c926ff2720a990fb350815a85d5b6fd58f4d5cb58ef458d not found: manifest unknown: manifest unknown

Not sure yet why it got out of sync

the podman team sadly removes "old" container images as soon as a new one is pushed, it's actually very annoying

Triggered an update but didn't get the latest hash. Unfortunately, I think there's something broken in the update process because we had different hashes for podman

Ugh
Error response from daemon: manifest for quay.io/containers/podman@sha256:f3671cf897e2a8745c926ff2720a990fb350815a85d5b6fd58f4d5cb58ef458d not found: manifest unknown: manifest unknown

Nvm I just had forgotten to add both changes... 😓

This happens frequently, exactly as @brancz described.

My recommendation is too simply remove the digest (parca-dev/.github#27), that was done in the Parca repo.
Renovate caches results from the registries, that's likely why it was not aware of the latest yet


v0.2.1

Codecov Report

Merging #29 (c2f28d7) into main (dc57568) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head c2f28d7 differs from pull request most recent head 72f656b. Consider uploading reports for the commit 72f656b to get more accurate results

@@            Coverage Diff            @@
##              main       #29   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          230       230
=========================================
  Hits           230       230

Impacted Files
Coverage Δ

src/fastapi_redis_cache/redis.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dc57568...72f656b. Read the comment docs.


Context menus wrong position on multiple displays with mixed DPI

Tested on Terminator and Firefox, the same bug occurs in Gnome so I don't know where it happens, I heard that it's libgtk bug but probably not. I use Wayland build of Firefox of course, and scale 1.75 or 2 of my secondary 4K monitor.
If there is similar issue - sorry for posting it.

Also, in sway opening context menu near border causes bug where border is at higher index than context window, and that causes graphical defect.
See here:
https://imgur.com/a/pPg0vQA

Just a tip, on most wlroots-based compositors (including Sway) you can use https://github.com/emersion/grim to create screenshots.

Just a tip, on most wlroots-based compositors (including Sway) you can use https://github.com/emersion/grim to create screenshots.

Yes I know but I had not hotkey attached and doing it via terminal was causing context menu dissapear so I though it will be faster to do with phone.

Tested on Terminator and Firefox, the same bug occurs in Gnome so I don't know where it happens, I heard that it's libgtk bug but probably not. I use Wayland build of Firefox of course, and scale 1.75 or 2 of my secondary 4K monitor.

I'm pretty sure this is related to https://github.com/swaywm/sway/issues/3135#issuecomment-448794177.
For Firefox, see https://bugzilla.mozilla.org/show_bug.cgi?id=1423598. It looks like that was fixed within the past week and should be included in the recent nightly builds.
I'm not sure what the status is for Terminator.

Also, in sway opening context menu near border causes bug where border is at higher index than context window, and that causes graphical defect.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1528021, which was closed as a duplicate of the issue above and thus should also be resolved in recent nightly builds.


Add --cluster_advertise <host/ip> option which would be used for auto-discovery

Feature Request
Use Case:
Related to issue #438.
Right now, with auto-discovery, a server will propagate to the routed servers and possibly clients, the host/IP specified in listen and/or cluster parameter.
It can be a problem if this address is not accessible or should not be from outside of the box.
The listen address should only be used for the bind (could be <IP_ADDRESS> on a container, or a special interface in a bare-metal cluster with private networking). The advertised host/ip should be the only ip known by both other members of the mesh and clients, keeping the backend hidden.
Such configuration permit to use VIP addresses in front of potential dying containers (works for both swarm and kubernetes for example without the use of headless services).
Proposed Change:
Adding a new parameter, say --cluster_advertise <host/ip>, would allow the server to use this address instead of trying to resolve the listen address (if <IP_ADDRESS> is specified), or the result of RemoteAddr() for routes.
Other servers and clients would be made aware of the advertised address instead of the address used by the server to create the tcp listener.
Who Benefits From The Change(s)?
People running NATS Server in containers or in the cloud when some addresses are not visible from the outside. Also, would help for situations when a node is restarted and assigned a new IP address, which with auto-discovery would be added to the list as a new entry. With use of cluster_advertise, the address being the same, it would not change the list of server.
Alternative Approaches
If host/ip is used for listen and cluster parameters, that address is currently advertised to clients, but not other servers. Still, as mentioned above, there are cases where the binding address of the NATS Server is not the address one would want to make public.

Hey guys, we are also interested in this functionality in order to circumvent the problem of connecting via reverse proxy (amazon elb). Is there any update on this idea or a branch we might be able to play with?
@luma

@stamf This is not implemented yet. Asking @ColinSullivan1 and/or @petemiron to see if this is in the roadmap.

IMO this sounds like a good enhancement to me.  We're evaluating outstanding issues and will be publishing a roadmap soon.

I have the same issue, as described in #542, when using NATS cluster inside docker, the connect_urls returns the docker internal IP addresses, which cannot be accessed to the Client.
Another case is when the servers have multiple network interface, and one for communication between NATS servers in the cluster, and another for the communication with clients, in this case, the connect_urls are most likely return the IP addresses are not accessible to the client either.
Having a -advertise argument will help the issue, we can specify which address we expect the client will connect to:
$ gnatsd -p 4223 \
    -cluster  nats://<IP_ADDRESS>:5222 \
    -routes nats://nats_a:5222 \
    -advertise <IP_ADDRESS>:4223

I would be interested in paying someone to do this work or making a donation to the project if we could get it done. Would someone be able to contact me about this if interested please<EMAIL_ADDRESS>

Thank you for the offer @chrissharkey, we'd happily accept a PR submission for this feature. I'll email you separately to see if you'd like to be invited to our slack channel and for any support questions.

For those interested in this issue, could you please have a look at the comment I made on the PR regarding "route" advertise (not client, which I think is fine). Would love some feedback on your use case. Link to comment is here


Retraction in go.mod should be allowed to retract versions of subdirectory go.mod files in the same git repo

What version of Go are you using (go version)?

$ go version
go version go1.17.2 linux/amd64

Does this issue reproduce with the latest release?
This is the latest release
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/fishy/.cache/go-build"
GOENV="/home/fishy/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/fishy/.gopath/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/fishy/.gopath"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/nix/store/vydvhfg076dfchm93hn96li2k1jqh04n-go-1.17.2/share/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/nix/store/vydvhfg076dfchm93hn96li2k1jqh04n-go-1.17.2/share/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.2"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/fishy/work/test-go-mod-retract/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3897776340=/tmp/go-build -gno-record-gcc-switches"

What did you do?
This is forked from the discussion of https://github.com/golang/go/issues/34055 and is an issue currently affecting Apache Thrift.
I made a minimal reproducible example at https://github.com/fishy/test-go-mod-retract to demonstrate the issue, but the high level summary is:

The project made a mistake by adding go.mod to a subdirectory, without realizing the consequences of that.
The project realized that's a mistake, removed the go.mod in the subdirectory and added go.mod to the root directory instead.
The action in 2 doesn't fix the issue totally. the version with go.mod under the subdirectory will be recognized by go toolchain (and pkg.go.dev site) as the "latest" version, over whatever git semver tag you tagged at the project later (for example, if you go to<EMAIL_ADDRESS>it will tell you that it's not the "latest" version).
Even if you try to retract that version from root go.mod file, it won't work (as I demonstrated in the test-go-mod-retract repo).

What did you expect to see?
Either:

We are able to retract a version from a previous, subdirectory go.mod file, from the root go.mod file

or

Provide a way to retract the whole go.mod file (e.g. we can add the subdirectory go.mod saying "every previous version coming out of this go.mod file are retracted and this go.mod file should be ignored")

What did you see instead?
The consequences of the mistake of adding subdirectory go.mod file lasts forever with no way to fix completely.

1 seems infeasible, the module system doesn't operate on the concept of repos, and individual modules are independent.
2 is already possible possible by publishing a higher version which retracts all the versions before, up to and including the current version

Sorry @seankhliao I didn't explain myself well in my proposal 2.
My understanding is (please correct me if I'm wrong) that the current thing we have in 2, is that yes we can retract all previous versions of this module in the subdirectory/go.mod file, but by doing so we are adding subdirectory/go.mod again, making the current version available, and we are going back to dealing with all the consequences of having a subdirectory/go.mod again, which totally defeats the purpose (the purpose is to retract all versions under subdirectory/go.mod and make it to always use root go.mod going forward).
Thus, my proposal is to add something like (any of the following or some better names, I'm bad at names):

retract *
retract all
retract module
retract-module
retract_module
etc.

With the semantic of "retract all previous versions of this module, and also ignore the current version of this module and lookup the parent directory for go module instead".
Does that make sense?

Thankns, @seankhliao! That worked.


Update CI

I believe of all of our projects, intake-esm is the most "up-to-date" with regards to CI testing.  I think that mpirical should match its CI testing framework.  This means:

Updating the CircleCI tests to implement an upstream-dev job, adding tests for Python 3.7 and 3.8, adding nightly builds, etc.
Add a Branch Protection Rule (in the GitHub repo settings) to enforce non-upstream-dev tests pass for PRs and that merging directly into master is not allowed.
Add GitHub Actions for code style enforcement (black, flake8, and isort).

Should contact @andersy005 for help, if necessary.

Is someone planning on working on this? I've got some time this afternoon just in case :)

In case some of the steps used in intake-esm's CI setup are not clear, please let me know. I am happy to help out.

@andersy005 I will definitely reach out if we can't make sense of the intake-esm testing framework.

Sounds good :+1:

I'm starting to sort through intake-esm's CI in preparation for our pair-programming session on Thursday.


Ammend Bootstrap dependency

@grahamgilchrist
please review.

There are breaking changes between bootstrap 1.1.0-1.2.0, but it doesn't look like they affect the modal. We may even be able to support =>1.0.0 - <1.3 as the 1.0-1.1 breaking changes only affect tabs and not the modal


fix, output option, and tests for sandbox/readstats.py

@mr-c, what do you think - could this be moved to scripts/?

[ ] Is it mergable?
[ ] Did it pass the tests?
[ ] If it introduces new functionality in scripts/ is it tested?
Check for code coverage.
[ ] Is it well formatted? Look at make pep8, make diff_pylint_report,
make cppcheck, and make doc output. Use make format and manual
fixing as needed.
[ ] Did it change the command-line interface? Only additions are allowed
without a major version increment. Changing file formats also requires a
major version number increment.
[ ] Is it documented in the ChangeLog?
[ ] Was a spellchecker run on the source code and documentation after
changes were made?

Jenkins, retest this please

jenkins, test this please

Ready for review @mr-c

Fix those 5 nits and we're good.

@mr-c, ready for review. Looks to me like pylint picked up a few new problems because readstats was moved into scripts, and hence the CI failed; I don't think the problems are worth fixing, though. Please advise!

We don't currently fail jobs for pylint. You can always review the log in Jenkins to see the cause of the failure.

Interpreting the log is always challenging; I couldn't see any clear reason why this build failed.

Jenkins now knows how to recognize this failure mode

Jenkins, please test this.

Jenkins, retest this please.

Well, aren't you exposing all sort of undocumented bits :-) Jenkin's Failure Cause Management has been updated to explain this one as well

Naturally obstreporous, that's me :)

OK, ready for review (& merge?) @mr-c

Enjoy :-)

thanks!


URL not working: Microsoft Business Profile

The link to Microsoft Business Profile doesn't work
It can be found in this part of the website:
Microsoft, on the other side, has its approach known as "brand cards," which does much the same thing as BIMI without utilizing DNS. Businesses can instead get started by signing up for the Microsoft Business Profile program. Office Web Apps (OWA) in Office 365 and Outlook.com use the verified icon that businesses provide to Microsoft when they join up. Some brand cards are created for well-known companies because the application uses Bing.

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

ID: 416478f7-78f0-f193-e548-d8731935335e
Version Independent ID: 416478f7-78f0-f193-e548-d8731935335e
Content: BIMI support
Content Source: ce/marketing/bimi-support.md
Service: dynamics-365-marketing
GitHub Login: @alfergus
Microsoft Alias: alfergus

Thanks for your comment, @ErLWinner. This issue has been assigned to the doc author for review.


Mica in the SUI BG doesn't work on Win10

This build appears to have resolved it for me in initial testing, with a completely unrelated side effect of the dark mode for settings having the light mode color background rendering it completely unreadable (but it at least appears to resolve this actual issue from what I can see so far)

Originally posted by @spootle in https://github.com/microsoft/terminal/issues/13388#issuecomment-1379527904

Pretty obviously, I set a transparent BG when we want mica, but there is no mica so it's just W H I T E


DacpacTool invocation fails on Windows if the maximum command length is exceeded

Apparently there's a limit to the length of a command sent at the Windows command line (8191 characters, possibly up to 32767 in some situations). Because DacpacTool is called via the command line, and each included file is sent as a separate argument, projects with either (a) a lot of objects or (b) very long paths to each object will eventually exceed this limit and fail.
I ran into this limitation and was able to work around it by creating a symbolic link to shorten my paths, but that's a workaround at best and projects with a large number of objects won't be able to do that.
One possible solution to the problem would be to pass the list of included objects in a temporary file, rather than via the CLI.

As mentioned, I've been able to work around this, so it's a low-priority issue for me personally, but I wanted to make sure it got logged so it could be dealt with at some point.

I guess we could write a list of files that are part of the project to a temporary file in the obj folder and then read that file from the DacpacTool. Shouldn't be too hard to do with the MSBuild built-in WriteLinesToFile task. If anyone's willing to sent a PR for this that would be great!

I'll take care of this at some point. This isn't a really high priority for me, but as you mentioned, it shouldn't be too difficult, so I'll try to get a PR in for it this week or next.

That would be awesome! Really appreciate all the work you've been putting into this.

Version 1.6.1 that contains the fix for this is now up on NuGet.org.


Objects in scene cause performance degradation

Stress tested with this:
for _ in 0...1000 {
  let ship: SCNNode = (scene.rootNode.childNode(withName: "ship", recursively: true)?.clone())!

  let x = Float(arc4random_uniform(1000)) / 100.0 - 5
  let y = Float(arc4random_uniform(1000)) / 100.0 - 5
  let z = -Float(arc4random_uniform(1000)) / 100.0
  print(x,y,z)
  ship.position = SCNVector3(x, y, z)
  sceneView.scene.rootNode.addChildNode(ship)
  sceneView.antialiasingMode = .multisampling4X
}

There seems to be no problem


DingTalk Plugin stores credentials in plain text

Describe the bug
A clear and concise description of what the bug is.
https://jenkins.io/security/advisory/2019-10-01/#SECURITY-1423
Screenshots
If applicable, add screenshots to help explain your problem.
Jenkins Info(please complete the following information):

Version [e.g. 22]

DingTalk Plugin Info(please complete the following information):

Version [e.g. 22]

Additional context
Add any other context about the problem here.

2.0 之前的版本导致的安全警告，现在已经修复了。