fix(ui/blocks): fixing overlapping blocks for undefined poolArrays

It appears that poolArray[0][0] can return undefined, resulting in an error when trying to read .thanos.
I haven't dug deeper into why it's undefined, so there is a root cause that should be fixed instead?

[x] I added CHANGELOG entry for this change.

Fixes #7216
Changes
Using ?. to catch undefined poolArrays.
Verification
If have only tested this with my Thanos deployment, which hasn't any overlapping blocks - can someone check if this works also when there are overlapping blocks present?

An E2E test is failing:
15:27:12 toolsBucketWeb-1: ts=2024-03-28T15:27:12.979772333Z caller=runutil.go:117 level=error name=toolsBucketWeb-1 msg="function failed. Retrying in next tick" err="BaseFetcher: iter bucket: Get \"https://<IP_ADDRESS>:32790/toolsBucketWeb-test/?location=\": dial tcp <IP_ADDRESS>:32790: connect: connection refused"
15:27:21 toolsBucketWeb-1: ts=2024-03-28T15:27:21.698806328Z caller=runutil.go:117 level=error name=toolsBucketWeb-1 msg="function failed. Retrying in next tick" err="BaseFetcher: iter bucket: Get \"https://<IP_ADDRESS>:32805/toolsBucketWeb-test/?location=\": dial tcp <IP_ADDRESS>:32805: connect: connection refused"
panic: test timed out after 10m0s

Don't see why my change would cause a connection refused, but toolsBucketWeb at least looks like it could be related - or is this a flake?

I believe it is a flake. Just re ran the test

Hey @outofrange, are you still planning to continue this PR? I think once we resolve conflicts it might be good to go and we can see if the issue is fixed


dart build should create data assets under asset-id name not under original filename

A package could emit two assets under two different ids but with the same from-source location. This works in dart run because the data assets aren't copied, but with dart build it fails because it copies based on the original file name, which can have a clash, as opposed to a unique name based on asset-id.
output.addAsset(DataAsset(id1, 'foo.txt'));
output.addAsset(DataAsset(id2, 'foo.txt'));

We should have a guarantee that all assets have unique assetId but not necessarily unique filename.

@mkustermann Did you mean NativeCodeAssets? DataAssets support hasn't landed yet.


breaks after pnpm update

steps to reproduce:

clone yourself a fresh main branch of fuwari
use either system pnpm or one installed with npm
pnpm update
pnpm dev
see a lot of red in terminal caused by several things

are you not supposed to update your local repo ever? :P

The latest release of cheerio broke astro-icon 1.1.0.
Modify the package.json by changing "astro-icon": "1.1.0" to "astro-icon": "^1.1.0". Then run pnpm update again, and it should work.

The latest release of cheerio broke astro-icon 1.1.0.
Modify the package.json by changing "astro-icon": "1.1.0" to "astro-icon": "^1.1.0". Then run pnpm update again, and it should work.

worked, thank you. shouldn't it be changed upstream?

The latest release of cheerio broke astro-icon 1.1.0.
Modify the package.json by changing "astro-icon": "1.1.0" to "astro-icon": "^1.1.0". Then run pnpm update again, and it should work.

worked, thank you. shouldn't it be changed upstream?

I’m not quite sure what you mean by upstream. The issue has already been fixed in astro-icon 1.1.1. The "^1.1.0" above allows pnpm to update astro-icon to 1.1.1. I’ll update the package.json in this project as well.

The latest release of cheerio broke astro-icon 1.1.0.
Modify the package.json by changing "astro-icon": "1.1.0" to "astro-icon": "^1.1.0". Then run pnpm update again, and it should work.

worked, thank you. shouldn't it be changed upstream?

I’m not quite sure what you mean by upstream. The issue has already been fixed in astro-icon 1.1.1. The "^1.1.0" above allows pnpm to update astro-icon to 1.1.1. I’ll update the package.json in this project as well.

oops sorry i meant "upstream" as in this repo. thank you


TCPSocket not seeing docker network?

This is a tricky one to report and I'm not sure what all details will help track down the root of the issue, so let me know what I can do to help.
Running the following code against the latest Docker for Mac beta (which may, in itself be part of the problem):
require "http/client"

HTTP::Client.new("docker.local", 8001, ssl: false) do |client|
  puts client.host, client.port, client.ssl?

  res = client.get("/")
  puts res.body
end

Returns the following
> cr test.cr
docker.local
8001
false
getaddrinfo: nodename nor servname provided, or not known (Socket::Error)
[4411973602] *CallStack::unwind:Array(Pointer(Void)) +82
[4411973505] *CallStack#initialize<CallStack>:Array(Pointer(Void)) +17
[4411973464] *CallStack::new:CallStack +40
[4412147673] *Socket::Error@Exception#initialize<Socket::Error, String, Nil>:CallStack +41
[4412147604] *Socket::Error::new<String>:Socket::Error +100
[4412141451] *TCPSocket#initialize<TCPSocket, String, Int32, Float64?, Float64?>:Nil +1835
[4412139581] *TCPSocket::new<String, Int32, Float64?, Float64?>:TCPSocket +221
[4412131582] *HTTP::Client#socket<HTTP::Client>:(OpenSSL::SSL::Socket | TCPSocket+) +110
[4412131035] *HTTP::Client#exec_internal<HTTP::Client, HTTP::Request>:HTTP::Client::Response +43
[4412130962] *HTTP::Client#exec<HTTP::Client, HTTP::Request>:HTTP::Client::Response +34
[4412130445] *HTTP::Client#exec<HTTP::Client, String, String, Nil, Nil>:HTTP::Client::Response +29
[4412130407] *HTTP::Client#get<HTTP::Client, String>:HTTP::Client::Response +39
[4411933302] __crystal_main +37926
[4411943976] main +40

However, using Ruby (which I believe to be based off of the same C socket library, performs correctly:
require 'net/http'

Net::HTTP.get 'docker.local', "/", 8001

Which prints out the request body of the API as I expect (this was run in the REPL).
If I swap the docker.local hostname for the IP the hostname resolves to, it works properly. However I would expect this not to be an issue. Anything I can give you to help chase this down?

If I remember correctly, based on what @waj told me (but I might be wrong), we are using libevent for network-related stuff and libevent doesn't see these addresses, but the C functions that come with mac do.

So basically that's the reason: Ruby uses the C library, we are not (but we should). But that means we need to replicate all of what libevent does. I guess this will come in the future but not right now.

I can confirm: DNS resolution are blocking calls, and as such can potentially block the event loop for a long time, which is bad, obviously. We thus rely on libevent's async DNS, which is evented, but uses its own custom resolver that reimplements getaddrinfo instead of C syscalls: http://www.wangafu.net/~nickm/libevent-book/Ref9_dns.html

That being said, how does docker resolver works? Does it set anything into the /etc/resolv.conf file? Maybe initializing the dns base manually with evdns_base_resolv_conf_parse and DNS_OPTIONS_ALL would help?

Docker for Mac beta does not set anything in the /etc/resolv.conf file. It probably routes it through the internal network stack?
https://beta.docker.com/docs/mac/experiment/#user-space-networking-vpn-hostnet

That link may require a docker login.

Hosts in the .local domain are not resolved through DNS. Instead multicast DNS (mDNS) is used, and it's implemented by Bonjour in OSX. Libevent doesn't use these services and that's why Crystal is currently unable to connect with .local hosts.
I was recently playing around the idea of stop using the name resolution from libevent, and use native services provided on each platform instead. For example, in Linux there is getaddrinfo_a which does exactly what we need. In OSX, there are some Core Foundation APIs that we can use to use the same name resolution services that every app uses. It requires spawning another thread to execute the CF run loop, but that shouldn't be an issue.

Hit this trying to connecto to postgres inside a docker network. It's not quite the same network because it's not a .local address, but the resolve fails regardless. Here is what I did to work around:
conninfo = PQ::ConnInfo.from_conninfo_string(ENV["DATABASE_URL"])
host = `getent hosts #{conninfo.host} | awk '{ printf $1 }'`
conninfo = PQ::ConnInfo.new(host, conninfo.database, conninfo.user, conninfo.password, conninfo.port, conninfo.sslmode)
PG.connect(conninfo)

Turns out shelling out was the easiest solution...

I want to just poke at the idea of possibly re-evaluating abstraction-and-events framework when the concurrency discussions phase starts. I'm still not to sure about libevent personally, there are many options.

I looked around to see what node/libuv and go do to avoid the problem:

libuv uses a pool of threads that will run getaddrinfo so it won't block the event loop. If many requests are done in parallel it may block (?). See https://nodejs.org/api/all.html#all_dns and http://docs.libuv.org/en/latest/threadpool.html

go uses a custom DNS client on UNIX by default, except for some cases like the domain ends with .local or the platform doesn't allow direct DNS requests (OS X), etc. It then fallbacks to getaddrinfo but limits the number of parallel calls to avoid blocking all threads. See https://golang.org/src/net/net.go and https://golang.org/src/net/dnsclient_unix.go

Closing in favor of #2660


iOS integration fluuter moduel set up the generate_multiple_pod_projects

Steps to Reproduce

...
...
...

Pods for flutter_test
use_frameworks!
install_all_flutter_pods(flutter_application_path)
target 'flutter_testTests' do
inherit! :search_paths
# Pods for testing
end
target 'flutter_testUITests' do
# Pods for testing
end
end
post_install do |installer|
flutter_post_install(installer) if defined?(flutter_post_install)
end

compile:
#ifndef GeneratedPluginRegistrant_h
#define GeneratedPluginRegistrant_h
#import <Flutter/Flutter.h> // 'Flutter/Flutter.h' file not found      because Flutter.framework and GeneratedPluginRegistrant.framework not install
NS_ASSUME_NONNULL_BEGIN
@interface GeneratedPluginRegistrant : NSObject

(void)registerWithRegistry:(NSObject*)registry;
@end

NS_ASSUME_NONNULL_END
#endif /* GeneratedPluginRegistrant_h */


Port to Java 11 and updated deps

Move to Java 11 and use latest dependencies

Closed by https://github.com/idsec-solutions/signservice-integration/pull/45


NuGet.Server: Adding support for SQL Server (and other database backends)

One of the things we really want at Stack Overflow is a simple internet NuGet feed without external dependencies. This has a few legs to it, we want to:

Use our existing SQL Server high availability (not add a new thing we need to failover)
Have HA on the NuGet feed inside a single data center (not skew based on when timers hit like NuGet.Server today)
Read-through caching so a build server never goes to the internet (this will be a separate issue - just including here)

Example: on a miss it goes to nuget.org, grabs the package, caching it locally on the way back. The next fetch is local.

Publish our own internal-only packages to the feed

NuGet.Server
NuGet.Server is the simplicity and minimal setup and dependencies we want, but is still ultimately file based and therefore has inherent limitations:

Skew between servers (or DFS shares)
Overall speed, as reading full packages from disk is expensive to rebuild indexes and such
Scale, because of the above

NuGetGallery
The obvious question: why not just use Gallery?

The gallery has the same file store dependencies as server, but for Lucene searching.
The gallery is updated a lot, for internal deployment this ins't a win because all we need is a very simple v2 feed. Of all the changes to NuGetGallery, how many of those actually impact the v3 feed (or any feed at all)? A relatively small portion. Since the gallery has lots of UI and other concerns, the amount of churn, updates, code to certify, etc. is a huge ratio to relevant changes just to host a feed.
Setup is quite a bit more complex, even locally - this is a one time cost but it illustrates the weight of Gallery vs. what's actually needed.
I want to be clear: Gallery is great, it's just not a great fit.

So: SQL Server. I played with what's needed to make this happen and it's not all that much. I have a working version of this on a branch here: NickCraver/NuGet.Server (craver/sql-server branch) with most of the relevant pieces in this commit: https://github.com/NickCraver/NuGet.Server/commit/96953922c5a645f24548345388797dfe44b0056a
Here's a view on the current state of things:

Note: the Packages table has PackageData directly in it (again - just a first pass), this returns too much data for most things. It's quite easy to make this another table and I'll do that next.
It's a first pass with a few pitfalls, but all of them are straightforward to remedy. This is just the rest of a few nights getting a feed up. It's already fully functional, but needs a few global changes to be workable:

.NET 4.6 -> .NET 4.6.1 min version, to support netstandard2.0 EF Core is built on.
DI needs request scope (the current DI is very simple, but a data context really should be request scope - it's currently long lived because of this limitation). This is bad because in a multi-server scenario not checking the DB per request (looking at the materialized context instead) would by desynced and error-prone. Pretty much any DI swap would support this.
Some generally useful helpers should moved around.

Overall note: While this issue and current code supports SQL Server, if we can figure out the dependency issue EF Core can very easily be swapped out for MySQL, SQLite, Postgres, etc. - anything that EF Core supports as the usage is very basic. Perhaps making the provider itself a plugin somehow would make things like NuGet.Server.MySQL an option. I'm not sure how that would work...so I'm starting the discussion here with SQL Server.
cc @joelverhagen

I love everything here and would like to replace our NuGet server with less disk-based feed - SQL Server is already natural backup target. The transparent mirror is great too.
As a current user I'd like to see easy migration path. We have a folder full of package names with subfolders for versions...

@lahma That reminds me! Currently the file system watcher where you can drop files into the \Packages folder resides in the ServerPackageRepository (and therefore is only active when the backend file store is in use), but IMO, is a distinct piece of functionaity.
There's no reason to tie the folder drop functionality to the ultimate backend store. If we moved this (and had some event handlers on the thing perhaps), it'd just pickup files and drop them into whatever backend store is in use. The leads me to migration: while not a one-click solution "just copy your packages here and we'll suck them in" is still pretty appealing as an easy-to-do option serving multiple use cases.
@joelverhagen thoughts here? I could tackle moving it into a shared place as part of this proposal if welcomed.

thoughts here? I could tackle moving it into a shared place as part of this proposal if welcomed.

Love the idea. This would also facilitate improved test coverage of that component... It's a bit fiddly right now. I tried this in the past but ran into pain. Definitely worth another stab.
Thus far it seems like upstream and decouple file system watcher belong in the main packages: NuGet.Server or one of I two dependencies.
And the EF integration belongs in NuGet.Server.Database or some such name.

In case others are looking for a hosted option that already does a lot of this, you can check out VSTS NuGet which gives you geo-redundancy private feeds with the read-through caching you mention.
Funny enough, our project started out with doing exactly what you are proposing - I remember hitting the same DI scoping issue you're talking about.  However, we ended up going in different direction.  Unfortunately, we doing it on an internal SQL framework that makes the code we wrote not particularly helpful to your pursuit.


HDDS-5490. Remove an OM node from HA ring

What changes were proposed in this pull request?
Adds support to remove an OM node from an HA cluster.
To remove an OM, we need to follow the below steps:

Update ozone-site.xml of each OM node by adding the to be decommissioned nodeId to the config ozone.om.decommissioned.nodes.<om-service-id>.
Run the following command:
ozone admin om decommission -id=<om-service-id> -nodeid=<decommissioned-node-id> -hostname=<decommissioned-node-hostname [(optional) force]

The DecommssionOM subcommand will verify that all the existing OMs configs have been updated with the decommissioned node. If the verification is successful, it will send a decommission request via OMAdmin protocol to the leader OM. The Leader OM will submit a SetConfiguration request to Ratis to remove the decommissioned peer from Raft conf and OM state.
If the force option is used in the decommission command,  the check that all OMs have the updated config will be bypassed and the decommission request will be sent to the OM leader.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5490
How was this patch tested?
Will update unit tests

Thank You @hanishakoneru for the PR.
I have one general question.
With this approach, looks like we need the config to be updated before on all nodes not only OM right. As the decomission sub command also verifies few checks and also in general RpcClient also needs when building failOverProxy list.

Thanks for the review @bharatviswa504. I have addressed your comments.

With this approach, looks like we need the config to be updated before on all nodes not only OM right. As the decomission sub command also verifies few checks and also in general RpcClient also needs when building failOverProxy list.

Yes, its good to have the config updated on all nodes for failovers. But the requirement is only OMs and the node from which the admin command is run. RpcClient would still work with old configs (there would be a unnecessary failover to the decommissioned OM though).

Thanks for the review Bharat.

Do we want to allow only operation at a time on this operation? And throw exception to other invokes on this API from client Like Already remove is ongoing something like this.
Coming from the perspective of one cli remove om1, and another cli remove om2. If we know inprogress thing, we can ask for 2nd invocation retry once after first is completed. Do we need any such semantics here?

Missed this earlier. Yes, it would be good to have this. But since the SetConfiguration will be synchronized from Ratis side, it is not critical that we control it from Ozone side as well.
A simple way to handle this would be to fail the request on getting ReconfigurationInProgressException. This way we can throw the error upto the cli and ask to retry. What do you think?

Thanks for the review Bharat.

Do we want to allow only operation at a time on this operation? And throw exception to other invokes on this API from client Like Already remove is ongoing something like this.
Coming from the perspective of one cli remove om1, and another cli remove om2. If we know inprogress thing, we can ask for 2nd invocation retry once after first is completed. Do we need any such semantics here?

Missed this earlier. Yes, it would be good to have this. But since the SetConfiguration will be synchronized from Ratis side, it is not critical that we control it from Ozone side as well. A simple way to handle this would be to fail the request on getting ReconfigurationInProgressException. This way we can throw the error upto the cli and ask to retry. What do you think?

Yes good idea, i think this can also be taken as part of HDDS-5847, as we need changes in failOverProxyProvider for that to fail when ReconfigurationInProgressException is received.

Thanks @bharatviswa504 for the reviews and the +1. I have updated HDDS-5847 to include policy for ReconfigurationInProgressException.
I will merge this shortly.


install Problem

hi, i think i'm to dump to install your Modul mmm-growatt.
it only show "undefinedW"
can you please help me?
follow steps i have done:
npm install growatt
and then i follow the MM install instuctions and fill the growatt login data an PlantID and so on. But it dont work. :-(
thank you verry much for your help and best greetings from germany
herbiro

Hi. You need to go into the /MagicMirror/modules folder first and then run git clone https://github.com/mumblebaj/MMM-Growatt.git. When that is finished you need to go into the MMM-Growatt folder and run npm install.  When that is done you update the config/config.js file.
    {
            module: "MMM-Growatt",
            position: "middle_center",
            disabled: true,
            //        header: "My Plant Data",
            config: {
                    username: "yourusername",
                    password: "yourpassword",
                    plantId: yourplantid,
                    deviceSerial: "yourdeviceserial",
                    updateInterval: 1000*60*30
            }
    },

if you have done all the above steps correctly then it should work.

This means i dont need to "npm install growatt" ?

There is no such step. These are the only steps to get the module installed: Nowhere in those steps does it say npm install growatt.


sun.rmi.transport.ObjectTable was unintentionally initialized at build time

The build of a very simple example was failing with this error:
Error: Classes that should be initialized at run time got initialized during image building:
 sun.rmi.transport.ObjectTable was unintentionally initialized at build time. To see why sun.rmi.transport.ObjectTable got initialized use --trace-class-initialization=sun.rmi.transport.ObjectTable

What was puzzling is that the same project had already built once with success. It took me a while to figure out this was caused by jvisualvm running on my machine and probably causing the native image build to fail (maybe because it auto discovers Java processes and was causing them to load RMI classes).
This is a not issue (please close it) but I thought creating it could help other people stumbling on this problem.

Thanks for raising that, that could be potentially a bug on GraalVM native image side, I will ask to the GraalVM team and provide you a feedback.

Could you please create an issue on GraalVM side where you will provide the output you see with --trace-class-initialization=sun.rmi.transport.ObjectTable and share a repro project link?
Please share the link to this issue here in order to allow me to bring to it the the attention of the GraalVM team.

FYI: As a quick fix, you can run native-image with -J-XX:+DisableAttachMechanism to disable JMX and Attach API. Attach API is used to enable local JMX connection.


[posm]: Optimization: Store a hash of the poolkey, tickLower, and tickUpper per tokenId

Component
Position Manager
Describe the suggested feature and problem it solves.
Instead of storing the full PoolKey, and the tickLower and tickUpper for the position we can just store a hash of those fields per tokenId.
This PR should include a rename for relevant mapping and view function names.
Describe the desired implementation.
No response
Describe alternatives.
No response
Additional context.
No response

Will be closed by https://github.com/Uniswap/v4-periphery/pull/196


Ta bb

Dear colleague. I haven't found any implementation that uses EMA for Bollinger Bands to test against, so this implementation is kind of intuitive. The same with tests, which are compared with my spread sheet. I haven't implemented partial equality for f64 or used any library as I do think this is not a good idea to create more dependencies on this level, or any if not necessary.
Partial Equality for f64 on reddit discussed:  https://www.reddit.com/r/rust/comments/664vo0/partialeq_and_f64/
That's why some bands output numbers are so explicitly long in assert!() macros. But from your implementation of MAX and MIN i see that this problem Was greatly recognized. I am leaving it as it is to let You comment on it at this point if necessary.
Thx.

Thanks! It looks good.
I'll merge and do some tweaks.
I'll replace EMA with SMA, since I think it is correct way to calculate standard deviation (something I overlooked on the design proposal stage).

Just for note: https://www.mathsisfun.com/data/standard-deviation-calculator.html

Thanks!
I did some updates, and released a new version with BB: https://docs.rs/ta/0.1.2/ta/indicators/struct.BollingerBands.html

Thanks, looks great.


chore: bdd-spring-1585801410 to 0.0.1

chore: Promote bdd-spring-1585801410 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Tensorflow installation issue

Hi Team,
I have anaconda with python 2.7 in my windows 7 machine, i tried to install tensorflow with the below command.

c:> conda create -n tensorflow python=2.7
it has installed successfully.
activate tensorflow
it changed the prompt to
(tensorflow) C:>
I have visual studio 2015, and selected the environment as python 2.7 and ran a sample program, it is giving the below error, please suggest.
from keras.models import Sequential

File "D:\Anaconda2\Lib\site-packages\keras_init_.py", line 3, in
from . import utils
File "D:\Anaconda2\Lib\site-packages\keras\utils_init_.py", line 6, in
from . import conv_utils
File "D:\Anaconda2\Lib\site-packages\keras\utils\conv_utils.py", line 3, in
from .. import backend as K
File "D:\Anaconda2\Lib\site-packages\keras\backend_init_.py", line 83, in <
module>
from .tensorflow_backend import *
File "D:\Anaconda2\Lib\site-packages\keras\backend\tensorflow_backend.py", lin
e 1, in
import tensorflow as tf
ImportError: No module named tensorflow
Press any key to continue . . .

Warning: As this doesn't appear to be a bug with Tensorflow, the devs may ask for this to be moved to Stack Overflow.
Please note that from the Installation Page for Windows, Tensorflow is NOT supported on Python 2.7 but only 3.5 (or 3.6 in the latest release). Please try again on a newer version of Python.

Hello
After activating tensor flow u have to install tensor flow inside it using pip or conda.
Please refer to the following link and proceed.
https://www.tensorflow.org/versions/r0.12/get_started/os_setup#pip_installation_on_windows

@shreyneil You should avoid linking users to old versions of the installation instructions. The latest installation page for Windows on the Tensroflow website is available here:  Installation Page for Windows
Please see my above comment on Python versions and let me know how you get on. For further installation issues you may find @mrry 's installation troubleshooter helper here: https://gist.github.com/mrry/ee5dbcfdd045fa48a27d56664411d41c

As @jubjamie has stated:
Please note that from the Installation Page for Windows, Tensorflow is NOT supported on Python 2.7 but only 3.5 (or 3.6 in the latest release). Please try again on a newer version of Python.

Closing issue.

Hey guys, I am trying to install tensorflow but found this message:
Collecting tensorflow
Could not find a version that satisfies the requirement tensorflow (from versions: )
No matching distribution found for tensorflow
any suggestion?

Best off re-filing on Stack Overflow. Chances are you are trying to install an invalid binary or aren't suing a supported configuration.
If you decide to move this issue to Stack Overflow, please post the link here so that myself (or others that stumble upon this issue) can find the S/O thread.


protobuf_generate_grpc_cpp step in cmake doesn't build protobuf file

What version of gRPC and what language are you using?
1.25.0
What operating system (Linux, Windows,...) and version?
MacOS Catalina
What runtime / compiler are you using (e.g. python version or version of gcc)
Clang 11.0.3
What did you do?
I use protobuf_generate_grpc_cpp in my CMakeList.txt file to trigger generating the protobuf file. But it does nothing.
What did you expect to see?
For my file to be built into .cc files
What did you see instead?
This is what I get when generating my makefile
-- Failed to find LLVM FileCheck
-- git Version: v1.5.0
-- Version: 1.5.0
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_STD_REGEX -- success
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX -- success
-- Performing Test HAVE_STEADY_CLOCK -- success
--
-- <IP_ADDRESS>
CMake Warning (dev) at _deps/grpc-src/third_party/protobuf/cmake/install.cmake:60 (message):
  The file
  "/Users/jamescampbell/Documents/Workspace/ThingOS/runtime/_deps/grpc-src/third_party/protobuf/src/google/protobuf/stubs/io_win32.h"
  is listed in
  "/Users/jamescampbell/Documents/Workspace/ThingOS/runtime/_deps/grpc-src/third_party/protobuf/cmake/cmake/extract_includes.bat.in"
  but there not exists.  The file will not be installed.
Call Stack (most recent call first):
  _deps/grpc-src/third_party/protobuf/cmake/CMakeLists.txt:231 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
CMake Warning (dev):
  Policy CMP0042 is not set: MACOSX_RPATH is enabled by default.  Run "cmake
  --help-policy CMP0042" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

  MACOSX_RPATH is not specified for the following targets:

   zlib

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done
-- Build files have been written to: /Users/jamescampbell/Documents/Workspace/ThingOS/runtime

Otherwise I don't get any output when building the makefile relating to the protobuf.
Anything else we should know about your project / environment?
Some information for cmake users how they should be generating the protobufs would be great :)

This is still an issue

@jcampbell05  Do you solve it? I have the same problem.


Put the recommended platform installers on the download page

I use Linux, so the current download instructions on http://www.scala-sbt.org/download.html are fine for me, but I think the other recommended platform installers should be front and center on this page as well.  They should be above the fold when browsing the page on a common desktop resolution.
I realize the links are available as part of the docs (http://www.scala-sbt.org/0.13/docs/Setup.html), but linking directly to the Windows, OSX, and Linux install instructions would make for a better UX (a few less clicks and scrolling).

Note that the download page changes contents depending on the platform you browse.
For me (using Mac) it says:
Homebrew (Third-party package)
$ brew install sbt

Ah, of course.  My mistake.  I was attempting to find setup instructions for another platform for another individual.  I didn't consider there would be a user agent switch.
I'll close the ticket.


Retrieve query name as macro variable

Is your feature request related to a problem? Please describe.
Currently I have my grafana dashboards as code. I would like to paramtertize the query parameters as much as possbile in order to not have things hardcoded in the query string.
For instance:
{
  "database": ":database_name",
  "datasource": {
    "type": "grafana-timestream-datasource",
    "uid": ":datasource_id"
  },
  "hide": true,
  "measure": "sensor_1",
  "rawQuery": "SELECT \r\n  time,\r\n  measure_value::double AS 'First Sensor'\r\n FROM $__database.$__table	\r\nWHERE $__timeFilter\r\n AND measure_name = $__measure \r\n \r\nORDER BY time ASC",
  "refId": "First Sensor",
  "table": ":table_name"
}

I would like to have the query name, this is the refId parameter, as a variable in the rawQuery.
Describe the solution you'd like
An additional macro called $__refId. To be able to do the following query:
SELECT
  time,
  measure_value::double AS $__refId
FROM $__database.$__table
WHERE $__timeFilter
AND measure_name = $__measure
ORDER BY time ASC

Describe alternatives you've considered
NA
Additional context
Link to a petition in the grafana forum:

https://community.grafana.com/t/how-do-i-reference-a-query-name-as-a-variable-for-the-display-name/82358

Hi @victormico ! Thanks for the feature request, I'll move this to our backlog to be considered.

Hi @iwysiu any update on this? Thanks!

Hi @victormico ! This is still in our backlog, but we haven't prioritized this work


Fail on decode big file with blockIndependence=false

Descriptor

  blockIndependence: false,
  blockChecksum: false,
  blockMaxSize: 4194304,
  streamSize: true,
  streamChecksum: false,
  dict: false,
  dictId: 0

LZ4 Frame mode
Uncompressed file size > 20 MB

Node LZ4 lib fail to decompress content, compressed by 3rd party libs. With blockIndependence: true everything is ok. Looks like uncompress_DataBlock don't rely on context from previous block and always fail on further blocks decoding.

I cannot decompress data compressed by Python lz4 lib with blockIndependence: false as well

I cannot decompress data compressed by Python lz4 lib with blockIndependence: false as well


[Blog] September community gems

Tentative publish date: 9/30/2021
Community gems for the month

@julieg18 any idea why DVC download link check failed here? (also, I'm constantly getting notified about these failures for some reason).

@julieg18 any idea why DVC download link check failed here? (also, I'm constantly getting notified about these failures for some reason).

There was a bug in our link check that we fixed a while ago. Updating this branch with the lastest version of master should fix the issue. As for notifications, Github seems to send out emails anytime a check fails.

@dberenbaum @shcheklein Could one of you merge this please?


Can't run inference with Colab (dalle-pytorch version / state dict keys mismatch)

Thanks for sharing model! It seems like the dalle-pytorch pip version needs to be fixed in the colab example.
dalle-pytorch==1.14.3-> dalle-pytorch==0.14.3

Thank you! the colab inferencing has been actually fixed now-- needed to change the versions.

It seems the 0.14.3.zip is downloaded in the wrong path (/content/dalle-pytorch-pretrained/ instead of /content/) so that DALLE-pytorch directory is not created via !unzip /content/0.14.3.zip -d /content/dalle-pytorch-pretrained
You have to add -O /content/ at the end of wget command as follows:
!wget "https://github.com/lucidrains/DALLE-pytorch/archive/refs/tags/0.14.3.zip" -O /content/

thank you! actually fixed now

It seems the 0.14.3.zip is downloaded in the wrong path (/content/dalle-pytorch-pretrained/ instead of /content/) so that DALLE-pytorch directory is not created via !unzip /content/0.14.3.zip -d /content/dalle-pytorch-pretrained
You have to add -O /content/ at the end of wget command as follows:
!wget "https://github.com/lucidrains/DALLE-pytorch/archive/refs/tags/0.14.3.zip" -O /content/


Feature request: enforce one annotation per click

Hi Joe,
When plotting/viewing really dense data and making a cursor in the 'multiple' display mode, I'll sometimes end up in a situation where a single click generates many annotations. Could you add the feature that sets a one annotation per click policy? Annotating the closest object to the click would be a bonus, but not necessary for my needs.

Out of curiosity, which backend are you using?
There's already code in-place to prevent this, but it relies on single-shot timers, which don't work properly on all backends.  I've been meaning to round up a list of every backend + OS where single-shot timers aren't working and send PR's upstream.
At any rate, I'm beginning to think I should re-architect things and avoid pick events entirely.  The big advantage is that it would avoid a reliance on timers altogether.

I’m using Qt4Agg, (packaged with an “Anaconda2” distribution for Python 2.7/Windows 8.1 64-bit).
Thanks,
Joe
From: Joe Kington<EMAIL_ADDRESS>Sent: Saturday, February 20, 2016 10:24 PM
To: joferkington/mpldatacursor<EMAIL_ADDRESS>Cc: Chapman, Joe<EMAIL_ADDRESS>Subject: Re: [mpldatacursor] Feature request: enforce one annotation per click (#52)
Out of curiosity, which backend are you using?
There's already code in-place to prevent this, but it relies on single-shot timers, which don't work properly on all backends. I've been meaning to round up a list of every backend + OS where single-shot timers aren't working and send PR's upstream.
At any rate, I'm beginning to think I should re-architect things and avoid pick events entirely. The big advantage is that it would avoid a reliance on timers altogether.
—
Reply to this email directly or view it on GitHubhttps://github.com/joferkington/mpldatacursor/issues/52#issuecomment-186730008.

I think this happens in DataCursor._select, namely:
        for artist in self.artists:
            fixed_event = event_axes_data(event, artist.axes)
            inside, info = contains(artist, fixed_event)
            if inside:
                fig = artist.figure
                new_event = PickEvent('pick_event', fig.canvas, fixed_event,
                                     artist, **info)
                self(new_event)

Enforcing a single annotation per click can be trivially enforced by adding break at the end of the if clause.  Getting the closest line is a bit harder, you basically need to propagate the info back to that point for sorting purposes.

Fixed as @anntzer suggested. I'm going to leave the "closest artist" part out for the moment, as it adds a fair amount of complexity for relatively little gain.


Update deployment process to use sitemaps from platform-output-support

Given the new sitemaps generated in https://github.com/opentargets/platform/issues/1485, platform-output-support will be responsible for the generation of sitemaps (https://github.com/opentargets/platform/issues/1505) and the deployment step will be responsible for taking the front-end codebase and injecting the new sitemaps (https://github.com/opentargets/platform/issues/1545).
Can we please adjust the deployment process to use the sitemaps generated by platform-output-support?

I'll have a look at this, thanks @andrewhercules

ot-sitemaps is being integrated with Travis (https://github.com/opentargets/ot-sitemap-cli/pull/3) for automated assembly of the jar file that will be run by the provisioner, currently being tested at this terraform provisioner branch

Ticket closed as sitemaps generated and indexed by Google and Bing


How to make select all and delete work in forms

Was not showing the entire list when select all and delete was used within a form so I added this to keyup function...
if (e.keyCode == 46 && this.value == ""){

          $list.children($this.opts.ignore.trim() ? ":not(" + $this.opts.ignore + ")" : '').removeClass('selected').each(function() {

            var data = (
                        $this.opts.attribute != 'text'
                          ? ($(this).attr($this.opts.attribute) || '')
                          : $(this).text()
                        ).toLowerCase();

            var treaty = data.removeAccents($this.opts.ignore_accents).indexOf(q) == -1 || q === ($this.opts.hidden_mode ? '' : false)

              $this.opts.highlight ? $(this).removeHighlight().highlight(q).show() : $(this).show();

              $this.trigger('_after_each');

          });

}

@vdw This doesn't seem like a question, but more of a shortcoming/bug. The search is not cleared/recalculated if I select the text and press "delete" on the keyboard.

Making delete worked for me with this change instead:
-if ( [38, 40, 13].indexOf(e.keyCode) == -1 && ( e.keyCode != 8 ? $this.val().length >= $this.opts.min_chars : true ) ) {
+if ( [38, 40, 13].indexOf(e.keyCode) == -1 && ( ( e.keyCode != 46 && e.keyCode != 8 ) ? $this.val().length >= $this.opts.min_chars : true ) ) {

It removes the length check if either delete or backspace have been pressed. Before it was only triggering on backspace.


[RFE] social card for github

The Social image is used on social so it shows a nice headlamp-specific-image rather than the github one.
Because more prettier, and more better engagement. So there is a headlamp specific preview image.
For inspo, see examples of social cards at https://github.com/explore The Social image docs has more info like pixel size of the image.

Please try these graphics. If needed, we can add a tagline below the logo.

@tsompura Thanks! Can you add "The extensible UI for Kubernetes" as a tagline?

@joaquimrocha Updated with tagline.

The most recent green one is cool.

Thanks @tsompura . I have applied the one Chris picked. Great job.


Mutating webhook and discovery helm sub-charts

This commit adds the Helm subchart for the Mutating webhook

/rebase

/hold

/rebase


【Tezos】How do I specify Burn when creating a transaction?

Is your feature request related to a problem? Please describe.
I used TrustWallet to sign the transaction and broadcast it successfully, but I could not find the transaction, I suspect that because I did not specify a Burn, no miners would package the transaction for it. How do I specify Burn when creating a transaction?
Describe the solution you'd like
I want to have a parameter "burn"
val json =         {             "operationList": {                 "branch": "BL8euoCWqNCny9AR3AKjnpi38haYMxjei1ZqNHuXMn19JSQnoWp",                 "operations": [{                  {                     "burn": 10000                     "source": "tz1XVJ8bZUXs7r5NV8dHvuiBhzECvLRLR3jW",                     "fee": 1272,                     "counter": 30739,                     "gasLimit": 10100,                     "storageLimit": 257,                     "kind": 108,                     "transactionOperationData": {                         "destination": "tz1XVJ8bZUXs7r5NV8dHvuiBhzECvLRLR3jW",                         "amount": 1                     }                 }]             }         }

Having any issues with your trust wallet?
Contact our trust wallet support team
To help resolve your issue
Customer service


Item of schema type 'media' are not returning through api

./src/extensions/menus/strapi-server.js contains schema:
const customAttrs = {
menuItemIcon: {
type: 'media',
allowedTypes: [ 'images' ],
multiple: false,
},
menuItemThumbnail: {
type: 'media',
allowedTypes: [ 'images' ],
multiple: false,
},
menuItemFeatureImage: {
type: 'media',
allowedTypes: [ 'images' ],
multiple: false,
},
};
_http://localhost:1337/api/menus/3?populate=*_   returns:
"items": [
{
"id": 17,
"order": 0,
"title": "Profiles",
"url": "/products",
"target": null,
"createdAt": "2022-12-28T22:01:41.002Z",
"updatedAt": "2022-12-29T22:42:09.712Z"
},
Changing type to string allows the custom item to appear in the api as a null.

I had the same problem. Solved it by using this plugin: https://github.com/Barelydead/strapi-plugin-populate-deep
In my case with a menu in three levels, I used /menus/1?nested=true&populate=deep,3


A functioning client

Concrete classes under src/{Parser/Parser,Entity/Entity,Serialiser/Serialiser}/ were generated using bin/classGenerator, so no need to pay too much attention to those.
Tests to come, but probably gonna generate most of those too.

👍 Only a rough review, looks really good!

Does it pass our Code Sniffer?

@wpillar, yep, now it does. Give it a make test if you don't believe me.

@brendankay, since you last looked at this, the majority of changes have been adding tests and formatting the classGenerator to meet our standards.
The only big change is some improvements to AbstractParser, which means the handling of arrays is not so hacky.
Could you cast a quick eye over this? There's no rush.


Force project pathname to be directory

Several times I've used quickproject to create a temporary project, usually in the current working directory. When I've tried to do this I have invariably tried something like this:
(quickproject:make-project "testprj" :depends-on '(:cl :cl-who))
or something like it. I know it is expecting a directory pathname, such as "testprj/". What would be cool is if it does "the right thing" either way. In other words, implements something like this:
(quickproject:make-project (cl-fad:pathname-as-directory "testproj") :defpends-on '(:cl :cl-who))
I can't think of a case where something as simple as making sure the string "testprj" is terminated with a "/" for unix filesystems wouldn't be the right thing for it to do.

Agreed.  I just got bit by this as well.

The next update will have something to avoid the problem.

On Wed, 30 Nov 2011 16:37:47 -0800, Zach Beane
<EMAIL_ADDRESS>wrote:

The next update will have something to avoid the problem.

Reply to this email directly or view it on GitHub:
https://github.com/xach/quickproject/issues/3#issuecomment-2969083

Great! I love it. I just used it ten minutes ago.
Jeff

This has been committed and released.


Consider removing Community Portal from docs

The Community Portal lists a couple dozen extensions written by the community. We should consider removing it because it hasn't been updated recently (last addition July 2020) and it has largely been replaced by https://exchange.tableau.com.
These are the places which require change:

modify nav head (_includes/header.html)
remove layout (_layouts/community.html)
remove community section (community/)
modify home page (index.html)

Are there actions we could take to juice up the community portal?

Well if we implemented the change suggested here, it would die right away because we'd be removing it. I'm just suggesting the idea but happy to hear reasons why we should keep it.

Further conversations with the team clarified: these extensions still have a place as "community" level contributions as opposed to the more formal/vetted extensions in Tableau Exchange. It's still true it hasn't been updated in quite a while, but there's no urgency to remove it.


Order of operations fix in Expression

Fix so that the style below equals 15 instead of 7.
{
    "defines" : {
        "value" : "1.0 + 2.0",
    },
    "pointSize" : "5.0 * ${value}"
}

Unit test?

Added test.


GitHub release or another way to reproducibly get binary

Hey guys,
I am working with TensorFlow, and just noticed, that Windows build fails due to file hash mismatch.
Apparently, it downloads cub from https://github.com/NVlabs/cub/archive/1.6.4.zip , and this file seems to be changing over time.
Is there a url for unchanging binary? Like a GitHub release, or maybe something internal, which TF build could use.

+1 this makes it hard for TensorFlow to include CUB releases.  Can you keep the release files immutable?

@lostmsu if you're still experiencing this bug please cross-post to tensorflow issues and we'll update the hash.

Yep, as mentioned in https://github.com/NVlabs/cub/issues/77, we'll be using GIT tags moving forward to demarcate immutable releases (as well as keeping the last major.minor.last branches for customer hotfixes).  The breaking of hashes was a one-time necessity to address https://github.com/NVlabs/cub/issues/94 (purge orphan bloat from the repository because of unreasonable git history size.)


refactor: simplify json-rpc proxy logic

What was wrong?
We proxy the JSON rpc requests to the corresponding network. This required some duplicated logic for each subnetwork (and it wasn't consistent).
How was it fixed?
Introduced new type using generics and managed to create one functions that can proxy requests to each subnetwork.
While this is an improvement, I'm not completely satisfied with the current state because I believe that we still have some unnecessary json serialization / deserializaion. But that will be left for some potential future improvements.
To-Do

[x] Run hive tests locally and make sure there is no regression.
[ ] Clean up commit history and use conventional commits.

I run hive tests locally and I didn't notice any regression. Some tests are failing, but they are failing with latest docker image as well (I think hive is very flaky on my local machine, and it also takes a long time to run).
I'm not even sure whether hive tests (and which ones) even use JSON-RPC.

I'm not even sure whether hive tests (and which ones) even use JSON-RPC.
All hive tests use the JSON-RPC

I run hive tests locally and I didn't notice any regression. Some tests are failing, but they are failing with latest docker image as well (I think hive is very flaky on my local machine, and it also takes a long time to run).

I don't think this is enough information for a 3rd party to come to a conclusion

I run only trin client (running all clients takes a lot of time, but I might run it tonight).
There are some failing tests beacon suite, but they are the same one as the one that are failing here: https://portal-hive-experimental.ethdevops.io/, so I will ignore them.
The only other failing tests are in history-interop:

OFFER Epoch Accumulator:  trin --> trin (x2)
GOSSIP blocks from A:trin --> B:trin

The only error visible in the logs is that "Content not found in local storage"
Because they fail with latest trin docker image, and because other OFFER tests pass, I don't think it has anything to do with this PR, and I'm guessing it has something to do with the size of the payload and my machine.
What further steps do you propose me to take in order to figure out what is happening here?


Cleanup HTML

There was a lot of random spacing in the HTML – this cleans it up to use some more standard styling. Tell me if you'd like me to change anything!

Thanks, that spacing was totally unacceptable


Smaller button image for use in lists

Lists of deployable apps look better with a smaller button, but to resize the image on GitHub requires leaving markdown for HTML. Add a smaller image that can be referenced to keep it simple.
This is what I'm currently experimenting with:
<img src="https://storage.googleapis.com/cloudrun/button.svg" alt="Run on Google Cloud" height="20">

I am thinking we should probably scale down the original svg so that people don’t resort to html.

Agreed

I tried height=40 (by saving this to github gists + save as .md), and it seems to render better. height=20 is a bit too small.
Currently it's 50px, so shrink by 20% would be good enough.


Extended test BoardView GPIO. Added test for analog read and write.

Codecov Report

Merging #27 (77a6c3a) into development (fa35f5c) will increase coverage by 0.14%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development      #27      +/-   ##
===============================================
+ Coverage        49.83%   49.98%   +0.14%
===============================================
  Files               76       76
  Lines             2791     2791
===============================================
+ Hits              1391     1395       +4
+ Misses            1400     1396       -4

Impacted Files
Coverage Δ

src/SMCE/BoardView.cpp
60.81% <0.00%> (+1.63%)
:arrow_up:

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 fa35f5c...77a6c3a. Read the comment docs.


Getting more done in GitHub with ZenHub

Hola! @gld1982ltd has created a ZenHub account for the SkeletonFramework organization. ZenHub is the leading team collaboration and project management solution built for GitHub.

How do I use ZenHub?
To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.
What can ZenHub do?
ZenHub adds a series of enhancements directly inside the GitHub UI:

Real-time, customizable task boards for GitHub issues;
Burndown charts, estimates, and velocity tracking based on GitHub Milestones;
Personal to-do lists and task prioritization;
“+1” button for GitHub issues and comments;
Drag-and-drop file sharing;
Time-saving shortcuts like a quick repo switcher.

Add ZenHub to GitHub
Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @gld1982ltd.

"Built specifically for fast-moving teams"
Someday! We'll get there! I believe! ヽ（゜ロ゜；）ノ

Yeah, just basically testing this out.


Create npm package

Using npm link is only a good solution during development. I would like to include this as a dev dependency in my package.json so everybody in the team uses the lint by default.
It would be nice to add the project to a CI and configure it to do automatic deployments when a new tag is added.

@angelozerr let me know if you need help with this stuff.

let me know if you need help with this stuff.

Yes please, I don't know this feature -(


Doesent work on Termux

Checkboxes

[✔ ] Updated fsociety
[✔ ] Issue does not already exist
[ ✔] fsociety issue, not a tool issue

Expected Result
doesent launch
Running it on Termux without root privledges.

what do?

Actual Result
$ fsociety
File "/data/data/com.termux/files/usr/usr/share/doc/fsociety/fsociety.py", line 1194
print "-------------------------"
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("-------------------------")?

btw whats youre discord?
i cant find it

You can DM me on discord with this issue ID (102)
My discord is Alison but Hacker, please join the server: https://discord.gg/BaBpuPn

Found the issue... Termux launches all 'python' commands as python3. On most Linux distros like Kali it is python2, to fix:
cd ../use/bin nano fsociety
Inside you will see something like
python /data/data/com.termux/files/usr/usr/share/doc/fsociety/fsociety.py
Simply change it to
python2 /data/data/com.termux/files/usr/usr/share/doc/fsociety/fsociety.py
Now as far as needing root it is a good idea to have but not needed I was able to launch with no problem.

Oh damn check that out - thanks man!


Trying To Install On 32 Bit Chromebook

I Just Want To Know How To Install On A 32 Bit Chromebook Because When I Ran sudo edit-chroot -all
And It Said I Was Using amd64 I'm On A 32 Bit Device But I Cant Load In
Any Tips

I don't think you can edit all chroots at the same time.
Try using -a i386


Initial support for the rival 700s

This PR only contains support for cdpi / polling rate.

Merged, I just updated the family name and added tests :D


[TextField] Handle Chrome autofill

There is a display issue in the TextField outlined variant when chrome pre-fills the text box on initial page load. The auto filled text overwrites the label. See below screenshot.

Also notice the yellow background for auto filled text, can it be overridden?
MUI version 3.9.2

This need to fix this problem! #14453 might provide some ways to address the problem.
@garygrubb I'm wondering, are you able to create a reproduction example that we can consistently use to solve the problem? Thank you! This looks very close to the Google main login form:

Sorry for the delayed response. I will try and create a small reproduction when time permits later this week. In the mean time I have a temporary fix in place - setting autoFocus on any one of the Textfields solves the issue.
                            <TextField                                 required                                 **autoFocus**                                 variant="outlined"                                 id="username"                                 label="mobile number"                                 defaultValue=""                                 margin="normal"                                 name="username"                                 type="tel"                                 onChange={this.handleChange}                                 error={!this.state.validMobile}                                 autoComplete="tel-national username"                             />

setting autoFocus on any one of the Textfields solves the issue.

Doesn't seem to work for me.

Also notice the yellow background for auto filled text, can it be overridden?

@garygrubb I did this via a theme override:
const theme = createMuiTheme({
  overrides: {
    MuiInputBase: {
      input: {
        '&:-webkit-autofill': {
          transitionDelay: '9999s',
          transitionProperty: 'background-color, color',
        },
      },
    },
  },
});

The alternative is to use a box-shadow to fill the input: https://stackoverflow.com/questions/2781549/removing-input-background-colour-for-chrome-autocomplete

@oliviertassinari This might do the trick: https://stackoverflow.com/a/41530164/396889

Also, FYI: https://github.com/facebook/react/issues/1159

@MarkMurphy Any idea how I could reproduce the problem?

@MarkMurphy Any idea how I could reproduce the problem?

For me, I created a simple username and password form allowed Chrome to remember my credentials.
Using Chrome 72.0.3626.119 on MacOS High Sierra 10.13.6
@material-ui/core version "3.8.1"
@material-ui/styles version "3.0.0-alpha.6"

@MarkMurphy I could reproduce it with https://material-ui.com/getting-started/page-layout-examples/sign-in/:

This is with the text field standard variant. So, we can notice two issues:

The focus active state isn't detected, we have a fix for it in #14132, just waiting for someone to lead the effort.
The fill state is only detected when moving the focus to the page.

Let's try with the outlined variant now. We can use this page: https://deploy-preview-14499--material-ui.netlify.com/getting-started/page-layout-examples/sign-in-side/

It seems like its a chrome autofill problem. If we were provided with ways to detect chrome's autofill it'd be an easy fix... but Im not aware of any solution. Only solution was to turn off autocomplete/autofill for all textfields.

@ymoon715 there’s at least one other workable solution which I posted a link to above.

Workaround documentation:

Disabling autocomplete: https://stackoverflow.com/a/30976223/882337

Overriding styles: http://webagility.com/posts/the-ultimate-list-of-hacks-for-chromes-forced-yellow-background-on-autocompleted-inputs

Disabling autofill styles (snippet from the second link above):

input:-webkit-autofill,
.my-class:-webkit-autofill {
    -webkit-transition-delay: 9999999s;
}

Thanks @cezarderevlean , I got rid of the yellow background, Now just need to figure out how to remove the greyed out helper text.

If you don't want to "disable" autofill as described in the first link I've put above, keep in mind that after autofill, it will appear like in your screenshot only when page refreshed by a code change in
development (as far as I've tested). A normal browser load/refresh will be fine, it will make the placeholder shrink.
Also, if what I've said above proves untrue, one workaround you can implement is always keep the placeholder shrinked with this prop on TextField:
InputLabelProps={{
    shrink: true,
}}

@cezarderevlean thanks. You are right. A normal browser refresh works fine.

I don't know how I missed it but @MarkMurphy had a similar solution way back & it uses material theme override which is a bit cleaner for use case. Thanks Mark.

If you don't want to "disable" autofill as described in the first link I've put above, keep in mind that after autofill, it will appear like in your screenshot only when page refreshed by a code change in
development (as far as I've tested). A normal browser load/refresh will be fine, it will make the placeholder shrink.
Also, if what I've said above proves untrue, one workaround you can implement is always keep the placeholder shrinked with this prop on TextField:
InputLabelProps={{
    shrink: true,
}}

Thanks, this worked for me.

Setting autoFocus on the username field and autoComplete='new-password' on the password field also did the trick for me.

For folks wanting to get the actual values of the input, instead of just detecting the presence of the values (see https://github.com/mui-org/material-ui/issues/14427#issuecomment-466054906), I've come up with a solution detailed in this SO article: https://stackoverflow.com/questions/35049555/chrome-autofill-autocomplete-no-value-for-password/56157489#56157489. The link has a good history of this overall issue that affects Chrome in general.
  componentDidMount() {
    var evt = new MouseEvent("click", {
      view: window,
      clientX: 0
    });
    window.dispatchEvent(evt);
    let iterations = 0;

    const interval = setInterval(() => {
      const value = this.inputs.email.value;
      // plain js alternative:
      // const value = document.getElementById("email").value;
      if (!!value || iterations > 20) {
        console.log(value);
        return clearInterval(interval);
      }

      iterations++;
      console.log("not found -> repeat");
    }, 100);
  }

Basically, I force a mouse click on the input so Chrome sets the value on the input. Then at a later point when the value is ready, I grab the value. It's definitely hacky, but Chrome leaves us with no options... (see details of Chrome's stance in the SO article).

TL;DR: This is a browser issue. They do not consistently fire input events when autofilling forms.
This is an issue at the browser level. If I click inside the page and then reload it correctly dispatches input events. If I click on the page, click in the navbar it only stops working on the second enter. If I land on the page by copying the link to the page and entering it in the navbar it also works.
I'm not even sure we can fix this for all browsers since when polled the input value is still empty even if autofilled. There's a neat trick for chrome only. Will investigate if only chrome has these issues.

@eps1lon Have you opened a bug in Chromium if this is Chromium related?

@scatteredlife
https://github.com/mui-org/material-ui/issues/718#issuecomment-529064043
This does not work for me.
This does work: InputLabelProps={{ shrink: true }}, although it always stays shrinked

The following diff seems to solve the issue:
diff --git a/packages/material-ui/src/InputBase/InputBase.js b/packages/material-ui/src/InputBase/InputBase.js
index d258e5b71d..a7aebb1288 100644
--- a/packages/material-ui/src/InputBase/InputBase.js
+++ b/packages/material-ui/src/InputBase/InputBase.js
@@ -311,6 +311,10 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     }
   };

+  // Check the input state on mount, in case it was auto filled by the browser during hydration.
+  React.useEffect(() => {
+    checkDirty(inputRef.current);
+  }, [checkDirty]);
+
   const handleClick = event => {
     if (inputRef.current && event.currentTarget === event.target) {
       inputRef.current.focus();

Can anyone confirm the quality of the fix?

@oliviertassinari Having "workaround fix" in material ui is needed, but if this is probably a Chromium bug as someone mentioned above, this workaround fix should be only temporarily, and the issue should be fixed within Chromium. Is it related to something like this: chromium search result, or is it a mui bug?

I don't think that it's an issue with Chrome at this point. I think that it's an issue with React and server-side rendering. If a user writes content in an input, before React hydrate, we are never notified about it.

@oliviertassinari But the server side rendering is not happening in create-react-app development server?

react bug report: https://github.com/facebook/react/issues/1159
iOS specific bug: https://bugs.chromium.org/p/chromium/issues/detail?id=895898

The issue is most likely that any onInput or onChange handlers need to be set via javascript. If this happens after chrome autofills these events are lost. The more javascript the more likely you loose the events. React started an effort to reduce  the time events are fired without react catching those. This will help hydrated UIs.
The other issue is that sometimes input.value isn't set although the value is autofilled. Only after focusing/blurring the input which likely has unintended side-effects (e.g. form validation).
It's very hard to properly research this issue since almost no reports have a reproducible example. We should not apply any fix until we have identified the issue properly though theoretically the fix from @oliviertassinari https://github.com/mui-org/material-ui/issues/14427#issuecomment-530145849 looks like it should at least cover dropped events.

I believe that the "event triggered before hydration" problem also affects us in https://github.com/mui-org/material-ui/issues/14132#issuecomment-453657016.

@oliviertassinari CRA is irrelevant here, but just add the following code in CRA app: https://codesandbox.io/s/textinput-bug-hsv9m
If you open this codesandbox, open the sandbox app preview in new window. The issue does not appear consistently after refresh, but double clicking on F5 it is reproduced in 90% of times.
Also I found something similar shown in this image:

On the codesandbox app preview fill the form
Reload the app preview. The form won't be autofilled automatically.
Click on username. Chrome will offer you to pick a user.
Hover the user.

@eps1lon Says the issue can be that Chrome fires autofill related event(s) before handlers are set up.
But how can Chrome even autofill before the input fileds are created in the DOM, and how can they be created in the DOM before javascript has run enough to set up event handlers. This seems fishy to me.
This can maybe happen with SSR (although I don't know how that works), but CRA development server does not use SSR.

@eps1lon Says the issue can be that Chrome fires autofill related event(s) before handlers are set up.

This only applies to static html which is hydrated by react and was only theoretically constructed because we didn't have a reproduction at the moment. Now that we have we can investigate actual issues.

I can't reproduce the issue on Chrome v76.0.3809.132, macOS v10.14.6.

I can reproduce the issue on Chrome v76.0.3809.87, Windows 10.

I can reproduce the issue on Chrome v76.0.3809.132, macOS v10.14.6.

my solution:
import { isChrome, osName} from "react-device-detect";
.....
.....

  const isChromeOSX = osName === 'Mac OS' && isChrome

  const [shrink, setShrink] = useState(isChromeOSX ? true : undefined)

  useEffect(() => {
    if(isChromeOSX) {
      const listen = () => {
        setShrink(undefined)
        window.removeEventListener('click',listen)
      }
      window.addEventListener('click', listen);
      return () => {
        window.removeEventListener('click',listen)
      };
    }
  }, [])

  return  <TextField
          .....
          variant="outlined"
          InputLabelProps={{ shrink }}
        />

The following diff solves the occurrences of the problem I can reproduce, can somebody confirm it?
diff --git a/packages/material-ui/src/FormControl/FormControl.js b/packages/material-ui/src/FormControl/FormControl.js
index 0ede7ca404..c7cb22aeb9 100644
--- a/packages/material-ui/src/FormControl/FormControl.js
+++ b/packages/material-ui/src/FormControl/FormControl.js
@@ -145,6 +145,14 @@ const FormControl = React.forwardRef(function FormControl(props, ref) {
     };
   }

+  const onFilled = React.useCallback(() => {
+    setFilled(true);
+  }, []);
+
+  const onEmpty = React.useCallback(() => {
+    setFilled(false);
+  }, []);
+
   const childContext = {
     adornedStart,
     disabled,
@@ -156,16 +164,8 @@ const FormControl = React.forwardRef(function FormControl(props, ref) {
     onBlur: () => {
       setFocused(false);
     },
-    onEmpty: () => {
-      if (filled) {
-        setFilled(false);
-      }
-    },
-    onFilled: () => {
-      if (!filled) {
-        setFilled(true);
-      }
-    },
+    onEmpty,
+    onFilled,
     onFocus: () => {
       setFocused(true);
     },
diff --git a/packages/material-ui/src/InputBase/InputBase.js b/packages/material-ui/src/InputBase/InputBase.js
index d258e5b71d..9cb6c94f43 100644
--- a/packages/material-ui/src/InputBase/InputBase.js
+++ b/packages/material-ui/src/InputBase/InputBase.js
@@ -116,6 +116,13 @@ export const styles = theme => {
       '&$disabled': {
         opacity: 1, // Reset iOS opacity
       },
+      '&:-webkit-autofill': {
+        animationDuration: '5000s',
+        animationName: '$auto-fill',
+      },
+    },
+    '@keyframes auto-fill': {
+      from: {},
     },
     /* Styles applied to the `input` element if `margin="dense"`. */
     inputMarginDense: {
@@ -239,17 +246,20 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     }
   }, [muiFormControl, disabled, focused, onBlur]);

+  const onFilled = muiFormControl && muiFormControl.onFilled;
+  const onEmpty = muiFormControl && muiFormControl.onEmpty;
+
   const checkDirty = React.useCallback(
     obj => {
       if (isFilled(obj)) {
-        if (muiFormControl && muiFormControl.onFilled) {
+      },
+    },
+    '@keyframes auto-fill': {
+      from: {},
     },
     /* Styles applied to the `input` element if `margin="dense"`. */
     inputMarginDense: {
@@ -239,17 +246,20 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     }
   }, [muiFormControl, disabled, focused, onBlur]);

+  const onFilled = muiFormControl && muiFormControl.onFilled;
+  const onEmpty = muiFormControl && muiFormControl.onEmpty;
+
   const checkDirty = React.useCallback(
     obj => {
       if (isFilled(obj)) {
-        if (muiFormControl && muiFormControl.onFilled) {
-          muiFormControl.onFilled();
+        if (onFilled) {
+          onFilled();
         }
-      } else if (muiFormControl && muiFormControl.onEmpty) {
-        muiFormControl.onEmpty();
+      } else if (onEmpty) {
+        onEmpty();
       }
     },
-    [muiFormControl],
+    [onFilled, onEmpty],
   );

   useEnhancedEffect(() => {
@@ -311,6 +321,12 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     }
   };

+  // Check the input state on mount, in case it was filled by the user
+  // or auto filled by the browser before the hydration (for SSR).
+  React.useEffect(() => {
+    checkDirty(inputRef.current);
+  }, []); // eslint-disable-line react-hooks/exhaustive-deps
+
   const handleClick = event => {
     if (inputRef.current && event.currentTarget === event.target) {
       inputRef.current.focus();
@@ -354,6 +370,10 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     };
   }

+  const handleAutoFill = () => {
+    // Provide a fake value as Chrome might not let you access it for security reasons.
+    checkDirty({ value: 'x' });
+  };
+
   return (
     <div
       className={clsx(
@@ -399,6 +419,7 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
           defaultValue={defaultValue}
           disabled={fcs.disabled}
           id={id}
+          onAnimationStart={handleAutoFill}
           name={name}
           onBlur={handleBlur}
           onChange={handleChange}

I tested this fix locally with material-ui sandbox (the docs page) and cannot reproduce the issue.
With this fix I can neither reproduce the similar issue mentioned in https://github.com/mui-org/material-ui/issues/14427#issuecomment-530503051 (part B)

@oliviertassinari @eps1lon I tested v4.4.3 in my business application and I didn't see the error. So it seems the patch (although maybe not the most elegant) solved the issue.

@oliviertassinari @eps1lon
I do have a minor new issue now unfortunately. When playing with autofill. Select user, then delete password, then try to select again (or something like that) the labels stay rised, even though the fields are empty :/

@oliviertassinari @eps1lon @croraf I've also tested it in my application ans the issue is no longer present. Thanks for your help.

@garygrubb But try to reproduce the subtle error I'm mentioning in the above post.

@coraf Yes I was able to reproduce the same issue on desktop Chrome Version 76.0.3809.132 (Official Build) (64-bit). The mobile version and firefox seem ok.
If you open a new issue for this, please tag me so I can follow along.

Would the following help?
diff --git a/packages/material-ui/src/InputBase/InputBase.js b/packages/material-ui/src/InputBase/InputBase.js
index 439e8afa7..f0ab8bb66 100644
--- a/packages/material-ui/src/InputBase/InputBase.js
+++ b/packages/material-ui/src/InputBase/InputBase.js
@@ -373,6 +373,12 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
   }

   const handleAutoFill = () => {
+    // The change event is correcty triggered when the input is focused.
+    // There is no need to detect autofill.
+    if (fcs.focused) {
+      return;
+    }
+
     // Provide a fake value as Chrome might not let you access it for security reasons.
     checkDirty({ value: 'x' });
   };

@oliviertassinari Your additional fix seems to solve the remaining issue I described.
But I have found another flavor of the issue :D

This will give you the following resultant issue at the end

@croraf Oh boy, I haven't seen this one coming! Yeah, it makes sense.
diff --git a/packages/material-ui/src/InputBase/InputBase.js b/packages/material-ui/src/InputBase/InputBase.js
index 763ab105c..9dce66f9d 100644
--- a/packages/material-ui/src/InputBase/InputBase.js
+++ b/packages/material-ui/src/InputBase/InputBase.js
@@ -86,6 +86,7 @@ export const styles = theme => {
       // Make the flex item shrink with Firefox
       minWidth: 0,
       width: '100%', // Fix IE 11 width issue
+      animationName: '$auto-fill-cancel',
       '&::-webkit-input-placeholder': placeholder,
       '&::-moz-placeholder': placeholder, // Firefox 19+
       '&:-ms-input-placeholder': placeholder, // IE 11
@@ -123,6 +124,9 @@ export const styles = theme => {
     '@keyframes auto-fill': {
       from: {},
     },
+    '@keyframes auto-fill-cancel': {
+      from: {},
+    },
     /* Styles applied to the `input` element if `margin="dense"`. */
     inputMarginDense: {
       paddingTop: 4 - 1,
@@ -380,9 +384,11 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     };
   }

-  const handleAutoFill = () => {
+  const handleAutoFill = event => {
     // Provide a fake value as Chrome might not let you access it for security reasons.
-    checkDirty({ value: 'x' });
+    checkDirty(
+      event.animationName.indexOf('auto-fill-cancel') !== -1 ? inputRef.current : { value: 'x' },
+    );
   };

   return (

From:

https://github.com/klarna/ui/blob/v4.10.0/Field/index.jsx#L105-L113
https://codedaily.io/tutorials/69/Animated-Input-Label-with-Chrome-Autofill-Detection-in-React

4.4.2

4.4.3

proposed patch

@oliviertassinari , @croraf - Tested in production and it works as expected. Thanks.
Please tag me in any other bug fixes you would like me to test in poduction. I'd be happy to help.

Happy to hear it.

Doesn't support dark theme?

@MAkerboom We could consider changing the color to be a darker blue. Is this someting you would like to experiment with?

@oliviertassinari as long as the outline is showing and it still has enough contrast with the text is seems fine by me

@MAkerboom The best approach I can come up with is:
diff --git a/packages/material-ui/src/FilledInput/FilledInput.js b/packages/material-ui/src/FilledInput/FilledInput.js
index 71d0bcc94..4b681cba1 100644
--- a/packages/material-ui/src/FilledInput/FilledInput.js
+++ b/packages/material-ui/src/FilledInput/FilledInput.js
@@ -106,6 +106,12 @@ export const styles = theme => {
     /* Styles applied to the `input` element. */
     input: {
       padding: '27px 12px 10px',
+      '&:-webkit-autofill': {
+        WebkitBoxShadow: theme.palette.type === 'dark' ? '0 0 0 100px #266798 inset' : null,
+        WebkitTextFillColor: theme.palette.type === 'dark' ? 'white' : null,
+        borderTopLeftRadius: 'inherit',
+        borderTopRightRadius: 'inherit',
+      },
     },
     /* Styles applied to the `input` element if `margin="dense"`. */
     inputMarginDense: {
diff --git a/packages/material-ui/src/OutlinedInput/OutlinedInput.js b/packages/material-ui/src/OutlinedInput/OutlinedInput.js
index f60c4e5d5..376e37ba8 100644
--- a/packages/material-ui/src/OutlinedInput/OutlinedInput.js
+++ b/packages/material-ui/src/OutlinedInput/OutlinedInput.js
@@ -65,6 +65,11 @@ export const styles = theme => {
     /* Styles applied to the `input` element. */
     input: {
       padding: '18.5px 14px',
+      '&:-webkit-autofill': {
+        WebkitBoxShadow: theme.palette.type === 'dark' ? '0 0 0 100px #266798 inset' : null,
+        WebkitTextFillColor: theme.palette.type === 'dark' ? 'white' : null,
+        borderRadius: theme.shape.borderRadius,
+      },
     },
     /* Styles applied to the `input` element if `margin="dense"`. */
     inputMarginDense: {

Is that OK with you? Do you want to submit a pull request? :)

Much better! thx. will try to make a PR

I saw this bug while using <AutoComplete/>.  The text field would not "shrink" its label when focusing on it. I saw this in Firefox and Chrome (did not test other browsers).  Upgrading from v4.5.0 to v4.5.2 fixed the issue.  I believe the PRs linked to this issue are responsible, so thank you!

FWIW here is a theme override to prevent chrome from displaying custom colors on autofilled inputs :

        MuiInputBase: {
            root: {
                fontFamily: '"Lato", serif',
                "& input": {
                    "&:-webkit-autofill": {
                        transition:
                            "background-color 50000s ease-in-out 0s, color 50000s ease-in-out 0s",
                    },
                    "&:-webkit-autofill:focus": {
                        transition:
                            "background-color 50000s ease-in-out 0s, color 50000s ease-in-out 0s",
                    },
                    "&:-webkit-autofill:hover": {
                        transition:
                            "background-color 50000s ease-in-out 0s, color 50000s ease-in-out 0s",
                    },
                },
            },
        },

@armellarcier I would be careful with removing the custom colors, I think that it's meant to help users. It can also be interesting from a security standpoint, do know that you are on the right domain name, not being fished (otherwise autofill doesn't work)

I had to run around looking for answers, couldn't find one that I liked. I finally had an idea to combine some of the ideas suggested over this issue. Here is how I solved it for me:
using formik-material-ui
using 'touched' from Formik to check if it is an initial user interaction or not
on the Field do this:
InputLabelProps={{ shrink: !touched.password ? true : values.password }}
the entire TextField looks like this:
`<Field component={TextField}
type={showPassword ? "text" : "password"}
label="Password"
name="password"
variant="outlined"
InputLabelProps={{ shrink: !touched.password ? true : values.password }}
InputProps={{
endAdornment: (

{showPassword ?  : }

),
}}
/>

For v5:
    MuiInputBase: {
      styleOverrides: {
        input: {
          "&:-webkit-autofill": {
            transitionDelay: "9999s",
            transitionProperty: "background-color, color",
          },
        },
      },
    },

For v5:
    MuiInputBase: {
      styleOverrides: {
        input: {
          "&:-webkit-autofill": {
            transitionDelay: "9999s",
            transitionProperty: "background-color, color",
          },
        },
      },
    },

it also requires to override styles for MuiFilledInput and MuiOutlinedInput to have the same behaviour with dark mode
// dark theme only
...
components: {
  MuiFilledInput: {
    styleOverrides: {
      input: {
        '&:-webkit-autofill': {
          WebkitBoxShadow: 'inherit',
          WebkitTextFillColor: 'inherit',
          caretColor: 'inherit',
        },
      }
    },
  },
  MuiOutlinedInput: {
    styleOverrides: {
      input: {
        '&:-webkit-autofill': {
          WebkitBoxShadow: 'inherit',
          WebkitTextFillColor: 'inherit',
          caretColor: 'inherit',
        },
      }
    },
  },
}
...

Is it somehow possible to derive the color used for the dark mode autofill background from the theme? When using a blue primary color it doesn't work so well out of the box with the hardcoded color #266798:

Thanks to @killmenot and @pyzenberg
Solution for v4:
createTheme({
  overrides: {
    MuiInputBase: {
      input: {
        '&:-webkit-autofill': {
          transitionDelay: '9999s',
          transitionProperty: 'background-color, color',
        },
      },
    },
    MuiFilledInput: {
        styleOverrides: {
          input: {
            '&:-webkit-autofill': {
              WebkitBoxShadow: 'inherit',
              WebkitTextFillColor: 'inherit',
              caretColor: 'inherit',
            },
          }
        },
      },
    MuiOutlinedInput: {
      input: {
        '&:-webkit-autofill': {
          WebkitBoxShadow: 'inherit',
          WebkitTextFillColor: 'inherit',
          caretColor: 'inherit',
        },
      },
    },
  },
});

I still see it in v5 why is this issue closed?

HI there,
I got same issue<EMAIL_ADDRESS>with react@18 and chrome 107. It did not happen with react@17.

Not the best solution but it's the only one that working right now:
  components: {
    MuiCssBaseline: {
      styleOverrides: `
        input:-webkit-autofill,
        input:-webkit-autofill:hover,
        input:-webkit-autofill:focus,
        input:-webkit-autofill:active  {
          -webkit-box-shadow: 0 0 0 100px #111111 inset !important;
        }
      `
    }
  }

Change #111111 to your background color. I don't like this solution but it's the only one that working right now (V5).

My hero.

I still see it in v5 why is this issue closed?

I'm to!

Any updates?

This issue is still relevant.

Try using the   -internal-autofill-previewed selector on css, e.g. input:-internal-autofill-previewed.

I have a simple solution for that,  return null for a value.
Here's the example:
          <TextField
              label={errors.email || "Email"}
              name={'adminEmail'}
              error={!!errors.email}
              onChange={handleChange}
              value={values.email || null}
              variant="outlined"
              className={`mb-8 `}
              autoComplete="new-password"
          />

I have a simple solution for that, return null for a value.
Here's the example:
          <TextField
              label={errors.email || "Email"}
              name={'adminEmail'}
              error={!!errors.email}
              onChange={handleChange}
              value={values.email || null}
              variant="outlined"
              className={`mb-8 `}
              autoComplete="new-password"
          />

Great timing! Had to fix a bug regarding this today and setting initial values to null is the only thing that worked, so thank you!
We had it inconsistently overlapping on some version of the form but not others. Bizarre.

Don't use React or JS to solve this. It can be easily captured by CSS selectors. Try using the  -internal-autofill-previewed selector on css, e.g. input:-internal-autofill-previewed to e.g; hide your placeholder text.

I have a simple solution for that, return null for a value.
Here's the example:
          <TextField
              label={errors.email || "Email"}
              name={'adminEmail'}
              error={!!errors.email}
              onChange={handleChange}
              value={values.email || null}
              variant="outlined"
              className={`mb-8 `}
              autoComplete="new-password"
          />

Thanks a lot! This worked for me 👍

The problem is present in last verison, any fix?

I found another workaround if you want to keep the autofill styles but hide the placeholder until the user focuses the input. It's not very clean but it works at least:
(You will need to play with top, left, width, height and padding props so the autofill adjusts well to your input.)
styleOverrides: {
    input: {
      position: 'relative',
      '&:-webkit-autofill': {
        position: 'absolute',
        left: '5px',
        top: '5px',
        zIndex: 9999,
        width: '87%',
        height: '35%',
        paddingLeft: '10px',
      },
    },
    ```

Do not JS or React solutions.js solutions, simply use these CSS selectors internal-autofill-previewed selector, as described at https://bugs.chromium.org/p/chromium/issues/detail?id=1405170

What if we make it in another way making interactive InputLabelProps(shrink):
InputLabelProps={{ shrink: true/false }}
const [hasFilledEmail, setHasFilledEmail] = useState(false);
<TextField
            InputLabelProps={{ shrink: hasFilledEmail }}
            InputProps={{
                onAnimationStart: (e) => {
                    e.animationName === 'mui-auto-fill' && setHasFilledEmail(true);
                },
                onFocus: () => setHasFilledEmail(true),
                onBlur: () => {
                    if (!!emailValue) {
                        setHasFilledEmail(true);
                    } else if (emailValue !== undefined) {
                        setHasFilledEmail(false);
                    }
                },
            }}
        />

What you need, is to don't overlap your data by input label.
The solution for changing styles for input is knowing, but this solution can help you with overlaying. Wdyt?
@oliviertassinari

@misharosa

What if we make it in another way making controlled labels by InputLabelProps(shrink): InputLabelProps={{ shrink: true/false }}
const emailValue = useWatch({ control, name: 'email' });
const [hasFilledEmail, setHasFilledEmail] = useState(false);
<TextField
          variant="outlined"
          name="email"
          label="Email"
          fullWidth={true}
          InputLabelProps={{ shrink: hasFilledEmail }}
          InputProps={{
              onAnimationStart: (e) => {
                  e.animationName === 'mui-auto-fill' && setHasFilledEmail(true);
              },
              onFocus: () => setHasFilledEmail(true),
              onBlur: () => {
                  if (!!emailValue) {
                      setHasFilledEmail(true);
                  } else if (emailValue !== undefined) {
                      setHasFilledEmail(false);
                  }
              },
          }}
      />

In this case, I working with react-hook-form
@oliviertassinari Wdyt?

Thanks! @sanzhardanybayev 's solution also worked but I got an error

value prop on input should not be null

This can be partially fixed if you are using react-hook-form and provide defaultValues as undefined.
The only downside, is that shadowDOM font-size will probably be different to font-size of your input field.
Other than that it worked for me. It's better that shrink: true.
Example:
const form = useForm<AuthUserDto>({
    resolver: yupResolver(schema),
    defaultValues: {
      email: undefined,
      password: undefined,
    },
    reValidateMode: 'onChange',
    mode: 'onChange',
  });

This is how I fixed the overlap of autofill and label, ugly, but worked for me. I added this to theme. I used a specific selectors for outlined textfields, change the class for the other variants. If you wish to remove the background color also, there are working solutions above.
MuiTextField: {
	styleOverrides: {
		root: {
			// Puts the label into notched position
			'.MuiInputLabel-outlined:has(+ .MuiOutlinedInput-root > .MuiOutlinedInput-input:-webkit-autofill)': {
				transform: 'translate(14px, -9px) scale(0.75)',
			},
			// Creates a hole around the text inside the border
			'.MuiOutlinedInput-input:-webkit-autofill ~ .MuiOutlinedInput-notchedOutline > legend': {
				maxWidth: '100%',
			},
		},
	},
},
```

Any updates on this issue?


V10 compatibility - inline links

V10 changed the class name for inline links, so I adjusted the CSS accordingly. I also added a background to the links so they stand out a bit, and you don't get a line going through the bottom when they're used in headers.
I also adjusted module.json to the new V10 format. Make sure to mark 1.6.3's maximum version as V9 on the admin page so Foundry doesn't update people to 1.7.0. (As well as 1.7.0 as only compatible with V10, obviously)

Also some issues with new journals, will fix, so hold off on merging till then

V10 journals are all working, plus I Prettier'd everything


feat: Adding tags variable to the aws_iam_openid_connect_provider resource

As we create resources is always a good practice to keep tags for them. This PR adds the tags argument to the aws_iam_openid_connect_provider resource which reads its value from the tags variables.
Tested using Terraform and Terragrunt without any issues.

@npalm  it looks like the change I proposed was actually added as part of https://github.com/philips-labs/terraform-aws-github-oidc/releases/tag/v0.8.1, so for now I will just add some modifications to the main README.md. Please let me know if this is ok.

@npalm it looks like the change I proposed was actually added as part of https://github.com/philips-labs/terraform-aws-github-oidc/releases/tag/v0.8.1, so for now I will just add some modifications to the main README.md. Please let me know if this is ok.

Actually I just realized the aws_iam_role  doesn't have the tags argument so I'm proposing the addition of this argument on this PR, I updated the docs as well and changed the title and description of the PR.


Solid sends WS messages on private resources without authentication

E.g. https://inbox1.inrupt.net/inbox/ is not accessible without authentication (GET returns 401). But anybody can subscribe to it without any authentication/authorization:
var socket = new WebSocket('wss://inbox1.inrupt.net/inbox/', ['solid-0.1']);
This way I get notifications for e.g. new messages in that inbox.
(observed on https://inrupt.net/ - server version Solid 5.6.4)
Is that intentional? I can see this as potentially insecure, if e.g. someone subscribes to some more specific resource to watch if it was updated or not.
I don't see any spec regarding auth at https://github.com/solid/solid-spec/blob/master/api-websockets.md.

AFAIK, the inbox is, has,  by default APPEND permissions.   APPEND allows you to use POST and PATCH, but not READ.  WRITE perms imply READ, APPEND perms do not.  This makes sense if you think about it - we want anyone to be able to write a message to us (append it), but only we ourselves should be able to read it.

Thanks for the quick reply. I'm not sure we're talking about the same stuff - permissions for CRUD operations on inbox are alright, AFAIK.
I am talking about the WebSockets API. Anybody, without any auth, can subscribe to anyone's inbox or any other resource: https://github.com/solid/solid-spec/blob/master/api-websockets.md#subscription.
I haven't tested it on other resources, but if it works the same way, I could maliciously subscribe to someone's (imaginatory) resources like /medical/myCancerRecords or /bank/records and get notifications when there's CRUD on those resources.
But if you say sending the WS events depend on APPEND permissions, then it is ok I guess. That should be in the WS spec I believe.

Yes, I think my point may be a red herring for your question.   You can't tell if someone has APPEND perms just from a 401 on a GET, but on the other hand someone without READ perms should not be getting notifications.


Implement Series.item

This PR proposes Series.item
>>> kser = ks.Series([10])
>>> kser.item()
10

Codecov Report

Merging #1502 into master will decrease coverage by 2.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1502      +/-   ##
==========================================
- Coverage   93.93%   91.78%   -2.16%
==========================================
  Files          36       36
  Lines        8445     8448       +3
==========================================
- Hits         7933     7754     -179
- Misses        512      694     +182

Impacted Files
Coverage Δ

databricks/koalas/missing/series.py
100.00% <ø> (ø)

databricks/koalas/series.py
96.98% <100.00%> (+0.01%)
:arrow_up:

databricks/koalas/usage_logging/__init__.py
24.32% <0.00%> (-70.28%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50.00% <0.00%> (-50.00%)
:arrow_down:

databricks/koalas/__init__.py
73.07% <0.00%> (-19.24%)
:arrow_down:

databricks/conftest.py
88.67% <0.00%> (-7.55%)
:arrow_down:

databricks/koalas/frame.py
92.56% <0.00%> (-3.02%)
:arrow_down:

databricks/koalas/utils.py
94.25% <0.00%> (-2.40%)
:arrow_down:

databricks/koalas/namespace.py
84.49% <0.00%> (-1.61%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0.00%> (-0.96%)
:arrow_down:

... and 1 more

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 6fbe6d0...800edad. Read the comment docs.


Configurable Password Expiry time when importing bulk users (eg : CSV import)

Is your suggestion related to an experience ? Please describe.
Currently, If we import users using CSV, the password will be valid only for 24hr

Describe the improvement

it needs to set the password-active-time at the user creation. Default can be 24 hours, while import tool(and SCIM) can set it to different value.
The code at JDBCUserStoreManager need to be moved to AbstractUserStore manager, and handle the time duration from the request, if not then at the user store config, if not then handle with server config, and at last the hard-coded default (24h)
Additional context

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Add missing pkg to dev docker

What this PR does / why we need it:
This adds psmisc docker-compose packages to dev docker images as they
are needed to to run the demo.
Signed-off-by: bur<EMAIL_ADDRESS>Which issue(s) this PR fixes:

This fixes #312
Special notes for your reviewer:
Does this PR introduce a user-facing changes and/or breaks backward compatability?:

Ouch! This is already addressed by #339. Closed


Blurry screen during character creation randomly

This occurs about 25% of the time when starting a new character. Unsure what's causing this, will need to do some diag and find the culprit. It's some type of light blast effect that occasionally happens before the initial racemenu is opened. Sometimes it takes long enough to occur that it does show in the race menu. Tis being looked into
For now, you can select the race you want to use, then exit the race menu. Then use the  showracemenu console command after MCM configuration has completed.

I've narrowed this down to what seems to be a soft incompatibility between Alternate Perspective and Depths of the Reach, or Darkstorm.esp.
For reasons I do not know, this is the mod initiates some sort of effect right on a new game. In vanilla, this is not really a problem due to the intro sequence. When using an alternate start mod, it seems this effect is very noticeable.
I have tested this on a vanilla game. only using SKSE,
SkyUI, Alternate Perspective, Depths of the Reach, and it's requirements.
Working on seeing if I can find a way to fix this, but in the meantime it will be a long term bug until it is fixed or patched.

The recent version of Alternate Perspective - Voiced Addon has added a tweak to delay the racemenu from appearing for a moment. This seems to have stopped this from happening


Alphabetised the schema

Closes #254
Very simple change to make current schema properties alphabetically ordered, to facilitate easier comparison for the review of #235

Thank you @evalott100 !


Fix TypeError: Arguments to path.join must be strings

Doing gulp build resulted in an error described at the following link:
http://stackoverflow.com/questions/28140012/gulp-typeerror-arguments-to-path-join-must-be-strings

Hi @andreisebastianc thanks for your PR. In the new application, released yesterday I don't use gulp anymore – so your change does not apply here (sorry for the big change).