genisoimage: Error / mkisofs / Joliet tree sort failed. -joliet-long switch may help you.

Hi, thank you for this great product.
Basically, I try to make dotnet wasm.
 The -joliet-long switch may help you.
------
container2wasm3626668171:402
--------------------
 400 |     COPY --link --from=tini-amd64-dev /out/tini /rootfs/sbin/tini
 401 |     RUN mkdir -p /rootfs/proc /rootfs/sys /rootfs/mnt /rootfs/run /rootfs/tmp /rootfs/dev /rootfs/var /rootfs/etc && mknod /rootfs/dev/null c 1 3 && chmod 666 /rootfs/dev/null
 402 | >>> RUN mkdir /out/ && mkisofs -l -J -R -o /out/rootfs.bin /rootfs/
 403 |     # RUN isoinfo -i /out/rootfs.bin -l
 404 |
--------------------
ERROR: failed to solve: process "/bin/sh -c mkdir /out/ && mkisofs -l -J -R -o /out/rootfs.bin /rootfs/" did not complete successfully: exit code: 1
exit status 1

As the error says:
/rootfs/oci/rootfs/root/.dotnet/sdk/8.0.201/Sdks/Microsoft.NET.Sdk.BlazorWebAssembly/targets/Microsoft.NET.Sdk.BlazorWebAssembly.ServiceWorkerAssetsManifest.5_0.targets
and
/rootfs/oci/rootfs/root/.dotnet/sdk/8.0.201/Sdks/Microsoft.NET.Sdk.BlazorWebAssembly/targets/Microsoft.NET.Sdk.BlazorWebAssembly.ServiceWorkerAssetsManifest.targets
have the same Joliet name, and Joliet tree sort failed.
The -joliet-long switch of mkisofs /  genisoimage may help.

Before I use my own Dockerfile, I've tried the official dotnet container images:
https://github.com/devcontainers/images/tree/main/src/dotnet
and hit the same error, therefore this error seems inevitable.
Is there any possible work-around?
Thank you.

https://github.com/ktock/container2wasm/blob/main/Dockerfile
402 | >>> RUN mkdir /out/ && mkisofs -l -J -R -o /out/rootfs.bin /rootfs/
Actually, I modified this line to add -joliet-long option, then re-make the c2w and the build process finished without the error.
I think it may be good to add the -joliet-long option to c2w  also.

Thanks for reporting this issue and the workaround.

I think it may be good to add the -joliet-long option to c2w also.

SGTM

Hello, I have the same issue when converting an image.
However, my error is:
container2wasm1342668950:431
--------------------
 429 |     COPY --link --from=tini-amd64-dev /out/tini /rootfs/sbin/tini
 430 |     RUN mkdir -p /rootfs/proc /rootfs/sys /rootfs/mnt /rootfs/run /rootfs/tmp /rootfs/dev /rootfs/var /rootfs/etc && mknod /rootfs/dev/null c 1 3 && chmod 666 /rootfs/dev/null
 431 | >>> RUN mkdir /out/ && mkisofs -l -J -R -o /out/rootfs.bin /rootfs/
 432 |     # RUN isoinfo -i /out/rootfs.bin -l
 433 |

Where should I fix? I am using the latest release (v0.6.5).
Also I read the Dockerfile of the main branch, but there were two lines of mkisofs -l -J -R -o /out/rootfs.bin /rootfs/.
Should I append -joliet-long option to the both lines?


Support for "ImageSharp"

For cross-platform applications (i.e. .Net Core 2.0) I'd suggest to add the support for ImageSharp as graphics interface.
I've been able to make it working, but that was because someone else made it work before me!
The current mine is somewhat meant as temporary until a better implementation will be available. Let me know if you're interested in my attempt.

There's now a .Net Core 2 replacement for System.Drawing by Microsoft:
https://www.nuget.org/packages/System.Drawing.Common/

@flensrocker That is only supported on Windows from my understanding as it is still based on GDI

Looking at [1] there is no "Windows Only" marker for System.Drawing.Common.
[1] https://blogs.msdn.microsoft.com/dotnet/2017/11/16/announcing-the-windows-compatibility-pack-for-net-core/

Afaik the best available libs to support are ImageSharp vs System.Drawing.Common vs SkiaSharp.
Maybe it should be possible to implement an interface which can be implemented for different platforms and implement one of the three as a default?

@groege I'm not the software architect of this project and I do not decide what will be implemented. But there surely are several ways to implement different types of image handling for different platforms or different configurations.

Looks like they're switching to a commercial license: https://sixlabors.com/blog/beta-six-labors/.

ImageSharp's license is AGPLv3. Is it compatible with PDFSharp's which is MIT?

According to this comment you need to install libgdiplus in linux / macOS for System.Drawing to work on these platforms.
SkiaSharp & Magick.NET also seems to have runtime dependencies for different OS platforms.

FYI: Currently, ImageSharp's license is Apache-2.0
https://github.com/SixLabors/ImageSharp/blob/master/LICENSE

It does seem that they back tracked a bit and their v1.0.x nuget packages are still Apache-2.0 licensed: https://www.nuget.org/packages/SixLabors.ImageSharp/1.0.3.
Building on a package that we know is likely to change to an incompatible license maybe isn't the best idea, but the ImageSharp betas were all quite solid. I expect the v1.0 branch to remain good enough for most uses, even if subsequent versions are not licensed as compatibly. So if their v1 covers the uses needed, maybe that's good enough.

PDFsharp 6.0.0 uses a different approach. Feel free to use ImageSharp in your port of PDFsharp.


Proposal: Translation of UI

Hi; Can we offer you translations of the user interface?
(In my case, in French)
I am aware that Accrescent is still at an early stage, and that many additions will be necessary before the first public publication, this is only a base that I will keep updated as additions are made (if it fits)
I can do this via pull request, or by simply providing you the strings.xml file.
Thanks.

Hi and thanks for the offer! Yes, I'm willing to accept translations provided at least one other person reviews them. Like you pointed out, Accrescent is still in development, so I'm going to take a best-effort approach to translation maintenance for now.
Go ahead and make a PR.
Linking https://github.com/accrescent/meta/issues/5 for tracking purposes.
@Wonderfall would you be interested in reviewing this?

Yeah, no problem.

@lberrymage: It's a great idea, I completely understand your point of view.
@Wonderfall: the simplest, I'll give you access to my fork, you can check and modify the files at your leisure :-)


Subtask 6 : Add a updated Start Button to the layout and style it accordingly.

Defined a styled button with the text "START WORKOUT"
The button is crafted to align visually with the app's overarching design, displaying a dark background tint and utilizing a monospace font. Its behavior, including the actions triggered upon clicking the button, is determined by its associated functionality.
The link to the pull request is: #198
The link to the commit: Commit link

Added the above-mentioned Subtask Title, subtask description and Links to the pull request and the commit made


No call events for newly created lines

Hi, This issue was originally submitted on Codeplex, but I see it is still an issue in the latest version on GitHub. This issue had me scratching my head for a while back in 2016. The suggested change below is now part of my standard ATAPI build and running live with a number of different phone systems - although we have only found it to be a major issue on Cisco CUCM (tested with CUCM 9.x, 10.x and 11.x) with extension mobility.
Original Codeplex Issue Text below:-
Lines added after the initial ATAPI initialisation do not fire any call events, although the lines are controllable.
The fix for this issue is a code change to register the TapiManager event handlers immediately following creation of the new TAPILine in TapiManager.ProcessTapiMessage.
This is tested against CUCM 9.1 where lines are removed and added when mobility users log-out and log-in to handsets.
TapiManager.cs:
case TapiEvent.LINE_CREATE:
{
	var newLine = new TapiLine(this, msg.dwParam1.ToInt32());

	// Change to add event handler registration
	newLine.NewCall += HandleNewCall;
	newLine.CallStateChanged += HandleCallStateChanged;
	newLine.CallInfoChanged += HandleCallInfoChanged;
	newLine.AddressChanged += HandleAddressChanged;
	newLine.Changed += HandleLineChanged;
	newLine.Ringing += HandleLineRinging;
	// End of change

	lock (_lineArray)
	{
	_lineArray.Add(newLine);
	}
	if (LineAdded != null)
	LineAdded(this, new LineAddedEventArgs(newLine));
}
break;

Great! Can you submit a pull request? We can integrate it pretty easily that way

Not being a previous git user, I'm trying to do this all on the Github website. Forking was ok, but the minor edit to the cs file looks to have replaced all the line breaks in the file.  I've got as far as pressing the create pull request button for the fork - but that just gives me a page with an enormous textbox that I cannot type into.
Creating a push request on GitHub is becoming more of a challenge than identifying the atapi event handler issue. I'll have another go in the morning.  :-)

Fixed with PR #12.


Unresponsive with Windows Subsystem for Linux

The Scala REPL, SBT and Activator are all unresponsive when run in the bash shell provided by the Windows 10 Subsystem for Linux (released today). After I type 'sbt' and press Enter, the terminal window becomes unresponsive. No input, no output.

Do you know if JLine 2 in general works on Windows Subsystem for Linux?
You might have to pass in -Djline.terminal=jline.UnixTerminal. See http://www.scala-sbt.org/0.13/docs/Manual-Installation.html

I have no idea what this thing supports. -Djline.terminal=jline.UnixTerminal does not help :(

a thread dump might help with troubleshooting. where's it getting stuck?

See also Microsoft/BashOnWindows#541, Microsoft/BashOnWindows#196, and Microsoft/BashOnWindows#253

I'm marking this Invalid for now since it's likely an environmental issue with the subsystem aka Bash on Windows.

I'll update this issue after M$ releases a WSL update

Microsoft just released a new version of Windows Subsystem for Linux. I'll look at it later in the week. Here is it in case anyone else is interested.

Same issue here, goes unresponsive after a disk write.   Seems to complete the disk write but the shell becomes unresponsive.  Can't execute it in another window either, it's just totally dead.  I have system managed pagefiles, Windows Defender and bitlocker enabled on C:.    Windows 10 Build 1607.


NiceTohave: layouts

We need to find how we can align all layouts (a component or something, propably there is something from next(?), ...)

Default (Index, Profile, ...) [Header, main Container]
SplitScreen (login, Register) [SliptScreen gleich wie in Storybook]

done and merged


fix an issue on reapir run dying out

problem was not to reschedule runner when no segments were started

@mmatalka @rzvoncek @Yarin78

I'm not the best person to know if this is correct or not, but it looks like it makes sense to me.
:+1:


World Racing 2 - Black screen upon launching the game

Describe the bug

Upon launching the game, the game window is completely black and there are not even RTX Remix related pop-ups visible (Welcome to RTX Remix [...]). Stable versions before 0.3.0 are giving "Could not create Direct 3D device!" error, but back a while ago I was able to run the game fine with the latest unstable dxvk/bridge as of April 15th. Upon running though i can "hear" that the game runs and reacts to inputs, as there is music and various sfx playing in the background.
remix-0.3.0-release
RTX 3090
546.31
World Racing 2 - Champion Edition (https://store.steampowered.com/app/1301010/World_Racing_2__Champion_Edition/)

Attach files!

NvRemixBridge.log
d3d9.log
WR2_PC_d3d9.log

To Reproduce
Steps to reproduce the behavior:

Launch the game in 32-bit mode

Thank you for filling the report. Are you using a DirectX8 to 9 wrapper?

I have tried using a DX8 to 9 wrapper but it doesnt make any difference because it seems the Champion Edition of the game runs at DX9 already

Closing this one as the game appears to be probably not compatible with Remix

Closing this one as the game appears to be probably not compatible with Remix


Updates to improve docker support

Lyra's dockerfile was a bit out of date. It now builds
and installs. It's pushed up to docker hub so you can:
docker pull lyraproj/lyra:latest
docker run -it lyraproj/lyra:latest /bin/bash
Then inside the container
lyra apply foobernetes
This also adds a make docker target to the Makefile.

ヽ(•‿•)ノ

Maybe add the pull/run to the getting started bit of the README? It's a hell of a lot faster than building everything from scratch.


Localize without XAML

Dear developers,
I have to localize some strings direct in Code without XAML in different languages.
Could you suggest me a possible solution?
Thank you in advance.

The goal of this library is to use RESX in XAML, but you can use RESX in .NET languages (C#, ....) without any problem, see https://docs.microsoft.com/cs-cz/dotnet/framework/resources/working-with-resx-files-programmatically

Thank you very much!

@maks-ua even if it is closed. You could also write your own TranslationProvider that delivers the data from classes / attributes,..

@konne of course, I'm sorry for the late answer
`
public class LocalizationProvider
{
    public static String GetLocalizedValue(string key)
    {
        CultureInfo ci = new CultureInfo(language); //language should be passed here

        Assembly ass = Assembly.Load("ProjectName");

        ResourceManager rm = new ResourceManager("ProjectName.Folder.Strings", ass);

        return rm.GetString(key, ci);
    }
}

`
This works perfectly with different language resx files.
Im currently try to implement an append function in case if the key doesnt exist in the Strings.resx
I use ResourceWriter.AddResource() but cannot get correct path of the file: it is looking for the file on my Desctop...
If someone has ideas, please share them.
Best regards,
Maks

The solution is pretty simple:
 if (rm.GetString(key, ci) == null)
            {
                string root = Path.GetDirectoryName(Assembly.GetCallingAssembly().Location);
                string file = "TODOStrings";
                string path =<EMAIL_ADDRESS>root, file, ci);

                if (!File.Exists(path))
                {
                    using (StreamWriter sw = File.CreateText(path))
                    {
                        sw.WriteLine(key);
                    }
                }
                else
                {
                    string[] readText = File.ReadAllLines(path);
                    foreach (string s in readText)
                    {
                        if (s == key) break;
                        else
                        {
                            using (StreamWriter sw = File.AppendText(path))
                            {
                                sw.WriteLine(key);
                                break;
                            }
                        }
                    }
                }
            return $"Key: {key}";
            }
            else return rm.GetString(key, ci);


Use higher tag level

Coverage increased (+0.1%) to 98.413% when pulling 92e2e23137e460f771b04b22028391cbaffe06d2 on kanongil:tag-levels-fix into 4d67abf7bfc69d301d86d3725f0ed58892610da5 on pinojs:master.

Thanks! This is good!


Updates from code repo

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Profile/Connect-PowerBIServiceAccount.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Profile/Disconnect-PowerBIServiceAccount.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Profile/MicrosoftPowerBIMgmt.Profile.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Reports/Get-PowerBIReport.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Reports/MicrosoftPowerBIMgmt.Reports.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Workspaces/Add-PowerBIWorkspaceUser.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Workspaces/Get-PowerBIWorkspace.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Workspaces/MicrosoftPowerBIMgmt.Workspaces.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Workspaces/Remove-PowerBIWorkspaceUser.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Workspaces/Restore-PowerBIWorkspace.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

powerbi-ps-1.0.193/MicrosoftPowerBIMgmt.Workspaces/Set-PowerBIWorkspace.md
:white_check_mark:Succeeded
View (powerbi-ps-1.0.193)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


When installing alluxio through helm, UnknownHostException appeared

Alluxio Version:
alluxio:2.3.0
Describe the bug
Following the guide https://docs.alluxio.io/os/user/stable/en/deploy/Running-Alluxio-On-Kubernetes.html to install alluxio.Error s occurd. I had set multi master3.
Pod status is :
[root@k8s-master01 ~]# kubectl -n spark get pods
NAME                                        READY   STATUS             RESTARTS   AGE
alluxio-fuse-j8rrm                          1/1     Running            0          10s
alluxio-fuse-rrcrn                          1/1     Running            0          10s
alluxio-fuse-wfrkr                          1/1     Running            0          10s
alluxio-master-0                            0/2     Running            0          10s
alluxio-worker-4kmbq                        0/2     CrashLoopBackOff   1          10s
alluxio-worker-5ng5f                        0/2     CrashLoopBackOff   1          10s
alluxio-worker-8rvbz                        0/2     CrashLoopBackOff   1          10s

Then i got endpoints:
[root@k8s-master01 ~]# kubectl -n spark describe  endpoints alluxio-master-0
Name:         alluxio-master-0
Namespace:    spark
Labels:       app=alluxio
              chart=alluxio-0.6.5
              heritage=Helm
              release=alluxio-1597374253
              role=alluxio-master
              service.kubernetes.io/headless=
Annotations:  endpoints.kubernetes.io/last-change-trigger-time: 2020-08-14T03:04:36Z
Subsets:
  Addresses:          <IP_ADDRESS>
  NotReadyAddresses:  <none>
  Ports:
    Name          Port   Protocol
    ----          ----   --------
    embedded      19200  TCP
    rpc           19998  TCP
    job-rpc       20001  TCP
    web           19999  TCP
    job-web       20002  TCP
    job-embedded  20003  TCP

Events:  <none>

Logs for master :
[root@k8s-master01 ~]# kubectl -n spark logs alluxio-master-0 -c alluxio-master
2020-08-14 03:04:20,037 INFO  BlockMasterFactory - Creating alluxio.master.block.BlockMaster
2020-08-14 03:04:20,037 INFO  FileSystemMasterFactory - Creating alluxio.master.file.FileSystemMaster
2020-08-14 03:04:20,037 INFO  MetricsMasterFactory - Creating alluxio.master.metrics.MetricsMaster
2020-08-14 03:04:20,037 INFO  MetaMasterFactory - Creating alluxio.master.meta.MetaMaster
2020-08-14 03:04:20,037 INFO  TableMasterFactory - Creating alluxio.master.table.TableMaster
2020-08-14 03:04:20,113 INFO  TieredIdentityFactory - Initialized tiered identity TieredIdentity(node=alluxio-master-0, rack=null)
2020-08-14 03:04:20,114 INFO  UnderDatabaseRegistry - Loading udb jars from /opt/alluxio-2.3.0/lib
2020-08-14 03:04:20,137 INFO  UnderDatabaseRegistry - Registered UDBs: hive,glue
2020-08-14 03:04:20,139 INFO  LayoutRegistry - Registered Table Layouts: hive
2020-08-14 03:04:20,146 INFO  ExtensionFactoryRegistry - Loading core jars from /opt/alluxio-2.3.0/lib
2020-08-14 03:04:20,174 INFO  ExtensionFactoryRegistry - Loading extension jars from /opt/alluxio-2.3.0/extensions
2020-08-14 03:04:20,942 INFO  ProcessUtils - Starting Alluxio master @alluxio-master-0:19998.
2020-08-14 03:04:20,943 INFO  RaftJournalSystem - Initializing Raft Journal System
2020-08-14 03:04:20,951 INFO  JournalStateMachine - Initialized new journal state machine
2020-08-14 03:04:21,062 INFO  AbstractPrimarySelector - Primary selector transitioning to SECONDARY
2020-08-14 03:04:21,063 INFO  RaftJournalSystem - Starting Raft journal system. Cluster addresses: [alluxio-master-0:19200, alluxio-master-1:19200, alluxio-master-2:19200]. Local address: alluxio-master-0:19200
2020-08-14 03:04:21,288 INFO  GrpcMessagingServer - Successfully started messaging server at: alluxio-master-0:19200
2020-08-14 03:04:21,299 INFO  ServerContext - alluxio-master-0:19200 - Transitioning to FOLLOWER
2020-08-14 03:04:21,307 INFO  AbstractPrimarySelector - Primary selector transitioning to SECONDARY
2020-08-14 03:04:21,333 INFO  NettyUtils - EPOLL_MODE is available
Aug 14, 2020 3:04:21 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<4>: (alluxio-master-2:19200)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-2, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-2: Name does not resolve
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-2: Name does not resolve
	at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
	at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
	at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}
Aug 14, 2020 3:04:21 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<6>: (alluxio-master-1:19200)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-1, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-1: Name does not resolve
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-1: Name does not resolve
	at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
	at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
	at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}
2020-08-14 03:04:31,458 INFO  FollowerState - alluxio-master-0:19200 - Polling members [ServerMember[type=ACTIVE, status=AVAILABLE, serverAddress=alluxio-master-2:19200, clientAddress=null], ServerMember[type=ACTIVE, status=AVAILABLE, serverAddress=alluxio-master-1:19200, clientAddress=null]]
Aug 14, 2020 3:04:31 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<10>: (alluxio-master-1:19200)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-1, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-1
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-1
	at java.net.InetAddress.getAllByName0(InetAddress.java:1281)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}

logs for worker:
[root@k8s-master01 ~]# kubectl -n spark logs alluxio-worker-55n5h  -c alluxio-worker
2020-08-14 05:18:17,159 INFO  NettyUtils - EPOLL_MODE is available
Aug 14, 2020 5:18:22 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<1>: (alluxio-master-0:19998)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-0, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-0: Try again
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-0: Try again
	at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
	at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
	at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}
2020-08-14 05:18:22,395 WARN  RetryUtils - Failed to load cluster default configuration with master (attempt 1): alluxio.exception.status.UnavailableException: Failed to handshake with master alluxio-master-0:19998 to load cluster default configuration values: UNAVAILABLE: Unable to resolve host alluxio-master-0
Aug 14, 2020 5:18:22 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<3>: (alluxio-master-0:19998)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-0, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-0
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-0
	at java.net.InetAddress.getAllByName0(InetAddress.java:1281)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}

Logs for fuse:
[root@k8s-master01 ~]# kubectl -n spark logs alluxio-fuse-pmr58
umount: /mnt/alluxio-fuse: not mounted
Starting alluxio-fuse on local host.
2020-08-14 05:18:17,532 INFO  TieredIdentityFactory - Initialized tiered identity TieredIdentity(node=<IP_ADDRESS>, rack=null)
2020-08-14 05:19:13,220 INFO  NettyUtils - EPOLL_MODE is available
Aug 14, 2020 5:19:33 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<1>: (alluxio-master-0:19998)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-0, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-0: Temporary failure in name resolution
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-0: Temporary failure in name resolution
	at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
	at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
	at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}
Aug 14, 2020 5:19:33 AM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext
WARNING: [Channel<3>: (alluxio-master-0:19998)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host alluxio-master-0, cause=java.lang.RuntimeException: java.net.UnknownHostException: alluxio-master-0
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: alluxio-master-0
	at java.net.InetAddress.getAllByName0(InetAddress.java:1281)
	at java.net.InetAddress.getAllByName(InetAddress.java:1193)
	at java.net.InetAddress.getAllByName(InetAddress.java:1127)
	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
	... 5 more
}

To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Expected behavior
A clear and concise description of what you expected to happen.
Urgency
Describe the impact and urgency of the bug.
Additional context
Add any other context about the problem here.

And my Configuration file is :
#
# The Alluxio Open Foundation licenses this work under the Apache License, version 2.0
# (the "License"). You may not use this work except in compliance with the License, which is
# available at www.apache.org/licenses/LICENSE-2.0
#
# This software is distributed on an "AS IS" basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
# either express or implied, as more fully set forth in the License.
#
# See the NOTICE file distributed with this work for information regarding copyright ownership.
#

# This should not be modified in the usual case.
fullnameOverride: alluxio

## Common ##

# Docker Image
image: alluxio/alluxio
imageTag: 2.3.0
imagePullPolicy: IfNotPresent

# Security Context
user: 1000
group: 1000
fsGroup: 1000

# Site properties for all the components
properties:
  # alluxio.user.metrics.collection.enabled: 'true'
#  alluxio.security.stale.channel.purge.interval: 365d
  alluxio.master.mount.table.root.ufs: "s3://xxxx"
  alluxio.master.mount.table.root.option.aws.accessKeyId: "xxx"
  alluxio.master.mount.table.root.option.aws.secretKey: "xxx"
  alluxio.master.mount.table.root.option.alluxio.underfs.s3.endpoint: "xxx"
  # worker props
  alluxio.worker.data.server.domain.socket.address: /opt/domain
  alluxio.worker.data.server.domain.socket.as.uuid: true
  # master props
  alluxio.master.metastore.dir: "/mnt/data/alluxio-k8s/metastore"

# Recommended JVM Heap options for running in Docker
# Ref: https://developers.redhat.com/blog/2017/03/14/java-inside-docker/
# These JVM options are common to all Alluxio services
# jvmOptions:
#   - "-XX:+UnlockExperimentalVMOptions"
#   - "-XX:+UseCGroupMemoryLimitForHeap"
#   - "-XX:MaxRAMFraction=2"

# Mount Persistent Volumes to all components
# mounts:
# - name: <persistentVolume claimName>
#   path: <mountPath>

# Use labels to run Alluxio on a subset of the K8s nodes
nodeSelector: {"alluxio": "true"}

## Master ##

master:
  count: 3 # Controls the number of StatefulSets. For multiMaster mode increase this to >1.
  replicas: 1 # Controls #replicas in a StatefulSet and should not be modified in the usual case.
  args: # Arguments to Docker entrypoint
    - master-only
    - --no-format
  # Properties for the master component
  properties:
    # Example: use ROCKS DB instead of Heap
    # alluxio.master.metastore: ROCKS
    # alluxio.master.metastore.dir: /metastore
  resources:
    # The default xmx is 8G
    limits:
      cpu: "4"
      memory: "8G"
    requests:
      cpu: "1"
      memory: "1G"
  ports:
    embedded: 19200
    rpc: 19998
    web: 19999
  hostPID: false
  hostNetwork: false
  # dnsPolicy will be ClusterFirstWithHostNet if hostNetwork: true
  # and ClusterFirst if hostNetwork: false
  # You can specify dnsPolicy here to override this inference
  # dnsPolicy: ClusterFirst
  # JVM options specific to the master container
  jvmOptions:
  nodeSelector: {}

jobMaster:
  args:
    - job-master
  # Properties for the jobMaster component
  properties:
  resources:
    limits:
      cpu: "4"
      memory: "8G"
    requests:
      cpu: "1"
      memory: "1G"
  ports:
    embedded: 20003
    rpc: 20001
    web: 20002
  # JVM options specific to the jobMaster container
  jvmOptions:

# Alluxio supports journal type of UFS and EMBEDDED
# UFS journal with HDFS example
# journal:
#   type: "UFS"
#   folder: "hdfs://{$hostname}:{$hostport}/journal"
# EMBEDDED journal to /journal example
# journal:
#   type: "EMBEDDED"
#   folder: "/journal"
journal:
  type: "EMBEDDED" # "UFS" or "EMBEDDED"
  ufsType: "local" # Ignored if type is "EMBEDDED". "local" or "HDFS"
  folder: "/journal" # Master journal folder
  # volumeType controls the type of journal volume.
  # It can be "persistentVolumeClaim" or "emptyDir"
  volumeType: emptyDir
  size: 1Gi
  # Attributes to use when the journal is persistentVolumeClaim
  storageClass: "standard"
  accessModes:
    - ReadWriteOnce
  # Attributes to use when the journal is emptyDir
  medium: ""
  # Configuration for journal formatting job
  format:
    runFormat: true # Change to true to format journal

# You can enable metastore to use ROCKS DB instead of Heap
# metastore:
#   volumeType: persistentVolumeClaim # Options: "persistentVolumeClaim" or "emptyDir"
#   size: 1Gi
#   mountPath: /metastore
# # Attributes to use when the metastore is persistentVolumeClaim
#   storageClass: "standard"
#   accessModes:
#    - ReadWriteOnce
# # Attributes to use when the metastore is emptyDir
#   medium: ""

## Worker ##

worker:
  args:
    - worker-only
    - --no-format
  # Properties for the worker component
  properties:
  resources:
    limits:
      cpu: "4"
      memory: "4G"
    requests:
      cpu: "1"
      memory: "2G"
  ports:
    rpc: 29999
    web: 30000
  # hostPID requires escalated privileges
  hostPID: false
  hostNetwork: true
  # dnsPolicy will be ClusterFirstWithHostNet if hostNetwork: true
  # and ClusterFirst if hostNetwork: false
  # You can specify dnsPolicy here to override this inference
  dnsPolicy: ClusterFirstWithHostNet
  # JVM options specific to the worker container
  jvmOptions:
  nodeSelector: {}

jobWorker:
  args:
    - job-worker
  # Properties for the jobWorker component
  properties:
  resources:
    limits:
      cpu: "4"
      memory: "4G"
    requests:
      cpu: "1"
      memory: "1G"
  ports:
    rpc: 30001
    data: 30002
    web: 30003
  # JVM options specific to the jobWorker container
  jvmOptions:

# Tiered Storage
# emptyDir example
#  - level: 0
#    alias: MEM
#    mediumtype: MEM
#    path: /dev/shm
#    type: emptyDir
#    quota: 1G
#
# hostPath example
#  - level: 0
#    alias: MEM
#    mediumtype: MEM
#    path: /dev/shm
#    type: hostPath
#    quota: 1G
#
# persistentVolumeClaim example
#  - level: 1
#    alias: SSD
#    mediumtype: SSD
#    type: persistentVolumeClaim
#    name: alluxio-ssd
#    path: /dev/ssd
#    quota: 10G
#
# multi-part mediumtype example
#  - level: 1
#    alias: SSD,HDD
#    mediumtype: SSD,HDD
#    type: persistentVolumeClaim
#    name: alluxio-ssd,alluxio-hdd
#    path: /dev/ssd,/dev/hdd
#    quota: 10G,10G
tieredstore:
  levels:
    - level: 0
      mediumtype: MEM
      path: /mnt/data/alluxio-k8s/ramdisk
      type: hostPath
      quota: 10G
      high: 0.9
      low: 0.7
    - level: 1
      mediumtype: HDD
      path: /mnt/data/alluxio-k8s/hdd-disk1
      type: hostPath
      quota: 100G
      high: 0.9
      low: 0.7

# Short circuit related properties
shortCircuit:
  enabled: true
  # The policy for short circuit can be "local" or "uuid",
  # local means the cache directory is in the same mount namespace,
  # uuid means interact with domain socket
  policy: uuid
  # volumeType controls the type of shortCircuit volume.
  # It can be "persistentVolumeClaim" or "hostPath"
  volumeType: hostPath
  size: 1Mi
  # Attributes to use if the domain socket volume is PVC
  pvcName: alluxio-worker-domain-socket
  accessModes:
    - ReadWriteOnce
  storageClass: standard
  # Attributes to use if the domain socket volume is hostPath
  hostPath: "/tmp/alluxio-domain" # The hostPath directory to use

## FUSE ##

fuse:
  image: alluxio/alluxio-fuse
  imageTag: 2.3.0
  imagePullPolicy: IfNotPresent
  # Change both to true to deploy FUSE
  enabled: true
  clientEnabled: false
  # Properties for the jobWorker component
  properties:
  # Customize the MaxDirectMemorySize
  # These options are specific to the FUSE daemon
  jvmOptions:
    - "-XX:MaxDirectMemorySize=2g"
  hostNetwork: true
  # hostPID requires escalated privileges
  hostPID: true
  dnsPolicy: ClusterFirstWithHostNet
  user: 0
  group: 0
  fsGroup: 0
  args:
    - fuse
    - --fuse-opts=allow_other
  # Mount path in the host
  mountPath: /mnt/alluxio-fuse
  resources:
    requests:
      cpu: "0.5"
      memory: "1G"
    limits:
      cpu: "1"
      memory: "1G"

##  Secrets ##

# Format: (<name>:<mount path under /secrets/>):
# secrets:
#   master: # Shared by master and jobMaster containers
#     alluxio-hdfs-config: hdfsConfig
#   worker: # Shared by worker and jobWorker containers
#     alluxio-hdfs-config: hdfsConfig

When i reset the num of master to 1,master seems to be  alright but workers and fuses still go wrong.And the  error is the same.

Do you use the Alluxio helm repo or extract the helm package yourself from the 2.3.0 tarball?
Alluxio master pods are deployed using StatefulSet, meaning it is created one by one. Once alluxio-master-0 is Running and is Ready 2/2, alluxio-master-1 is started. You see alluxio-master-2 is not resolvable because the pod is not started yet. Normally alluxio-master-0 will start first and pass the readiness probe, although it will not find the peers for the quorum, it's gonna retry for a while and not crash. In this period alluxio-master-1 and 2 will start the same way and they will finally create the quorum.
I think the error you see in the master log is just the symptom, not the root cause. Can you please do a kubectl get pods --watch after you do helm install and add what you see here? I'd like to see if the master pods ever pass the readiness check and alluxio-master-1 gets created. You should also do kubectl describe pod alluxio-master-<index> do look for anormalies.

Thanks for your replay.I extract the helm package by using the commands
!/bin/sh
id=$(docker create alluxio/alluxio:2.3.0)
docker cp $id:/opt/alluxio/integration/kubernetes/ - > ./kubernetes.tar
docker rm -v $id 1>/dev/null

Logs for the command ''' kubectl -n spark get pods --watch```
[root@k8s-master01 ~]# kubectl -n spark get pods --watch
NAME                                        READY   STATUS    RESTARTS   AGE
sparkoperator-1596693252-6fc5457db9-5zgqp   1/1     Running   4          12d
alluxio-fuse-client-2gx7v                   0/1     Pending   0          0s
alluxio-worker-4s6kw                        0/2     Pending   0          0s
alluxio-master-0                            0/2     Pending   0          0s
alluxio-fuse-client-qv77h                   0/1     Pending   0          0s
alluxio-fuse-client-wmw7z                   0/1     Pending   0          0s
alluxio-fuse-client-2gx7v                   0/1     Pending   0          0s
alluxio-worker-4s6kw                        0/2     Pending   0          0s
alluxio-master-0                            0/2     Pending   0          0s
alluxio-worker-hzppj                        0/2     Pending   0          0s
alluxio-fuse-client-qv77h                   0/1     Pending   0          0s
alluxio-worker-kvmnf                        0/2     Pending   0          0s
alluxio-fuse-client-wmw7z                   0/1     Pending   0          0s
alluxio-fuse-client-kg5m6                   0/1     Pending   0          0s
alluxio-fuse-client-tm7dx                   0/1     Pending   0          0s
alluxio-worker-hzppj                        0/2     Pending   0          0s
alluxio-fuse-client-2gx7v                   0/1     ContainerCreating   0          0s
alluxio-fuse-client-kg5m6                   0/1     Pending             0          0s
alluxio-worker-kvmnf                        0/2     Pending             0          0s
alluxio-worker-4s6kw                        0/2     ContainerCreating   0          0s
alluxio-fuse-client-tm7dx                   0/1     Pending             0          0s
alluxio-fuse-client-wmw7z                   0/1     ContainerCreating   0          0s
alluxio-master-0                            0/2     Init:0/1            0          0s
alluxio-fuse-6hhx6                          0/1     Pending             0          0s
alluxio-worker-kvmnf                        0/2     ContainerCreating   0          0s
alluxio-fuse-client-qv77h                   0/1     ContainerCreating   0          0s
alluxio-fuse-client-tm7dx                   0/1     ContainerCreating   0          0s
alluxio-fuse-6hhx6                          0/1     Pending             0          0s
alluxio-fuse-jzqtw                          0/1     Pending             0          0s
alluxio-fuse-8phv4                          0/1     Pending             0          0s
alluxio-fuse-jzqtw                          0/1     Pending             0          0s
alluxio-fuse-client-kg5m6                   0/1     ContainerCreating   0          0s
alluxio-fuse-8phv4                          0/1     Pending             0          0s
alluxio-worker-hzppj                        0/2     ContainerCreating   0          0s
alluxio-fuse-6hhx6                          0/1     ContainerCreating   0          0s
alluxio-fuse-8phv4                          0/1     ContainerCreating   0          0s
alluxio-fuse-jzqtw                          0/1     ContainerCreating   0          1s
alluxio-worker-hzppj                        0/2     Running             0          1s
alluxio-worker-4s6kw                        0/2     Running             0          2s
alluxio-fuse-6hhx6                          1/1     Running             0          2s
alluxio-worker-kvmnf                        0/2     Running             0          2s
alluxio-fuse-8phv4                          1/1     Running             0          2s
alluxio-master-0                            0/2     Init:0/1            0          2s
alluxio-fuse-jzqtw                          1/1     Running             0          3s
alluxio-fuse-client-tm7dx                   1/1     Running             0          3s
alluxio-master-0                            0/2     PodInitializing     0          3s
alluxio-fuse-client-2gx7v                   1/1     Running             0          4s
alluxio-master-0                            0/2     Running             0          4s
alluxio-fuse-client-qv77h                   1/1     Running             0          5s
alluxio-master-0                            1/2     Running             0          18s
alluxio-master-0                            2/2     Running             0          21s
alluxio-master-1                            0/2     Pending             0          0s
alluxio-master-1                            0/2     Pending             0          0s
alluxio-master-1                            0/2     Init:0/1            0          0s
alluxio-master-1                            0/2     PodInitializing     0          1s
alluxio-master-1                            0/2     Running             0          2s
alluxio-master-1                            1/2     Running             0          12s
alluxio-master-1                            2/2     Running             0          19s
alluxio-master-2                            0/2     Pending             0          0s
alluxio-master-2                            0/2     Pending             0          0s
alluxio-master-2                            0/2     Init:0/1            0          1s
alluxio-master-2                            0/2     Init:0/1            0          1s
alluxio-master-2                            0/2     PodInitializing     0          2s
alluxio-master-2                            0/2     Running             0          3s
alluxio-master-2                            1/2     Running             0          14s
alluxio-master-2                            2/2     Running             0          18s
alluxio-fuse-client-kg5m6                   1/1     Running             0          103s
alluxio-fuse-client-wmw7z                   1/1     Running             0          108s
alluxio-worker-kvmnf                        0/2     Running             1          2m21s
alluxio-worker-kvmnf                        0/2     Running             2          2m23s
alluxio-worker-hzppj                        0/2     Running             1          2m32s
alluxio-worker-4s6kw                        0/2     Running             1          2m36s
alluxio-worker-hzppj                        0/2     Running             2          2m36s
alluxio-worker-4s6kw                        0/2     Running             2          2m39s
alluxio-worker-kvmnf                        0/2     Running             3          4m51s
alluxio-worker-kvmnf                        0/2     Running             4          4m53s
alluxio-worker-hzppj                        0/2     Running             3          5m1s
alluxio-worker-4s6kw                        0/2     Running             3          5m6s
alluxio-worker-hzppj                        0/2     Running             4          5m6s
alluxio-worker-4s6kw                        0/2     Running             4          5m9s
alluxio-worker-kvmnf                        0/2     Running             5          7m21s
alluxio-worker-kvmnf                        0/2     Running             6          7m23s
alluxio-worker-hzppj                        0/2     Running             5          7m31s
alluxio-worker-4s6kw                        0/2     Running             5          7m36s
alluxio-worker-hzppj                        0/2     Running             6          7m36s
alluxio-worker-4s6kw                        0/2     Running             6          7m39s

And logs for the command  kubectl -n spark describe pod alluxio-master-0:
[root@k8s-master01 ~]# kubectl -n spark describe pod alluxio-master-0
Name:         alluxio-master-0
Namespace:    spark
Priority:     0
Node:         k8s-bignode03/<IP_ADDRESS>
Start Time:   Mon, 24 Aug 2020 09:10:18 +0800
Labels:       app=alluxio
              chart=alluxio-0.6.5
              controller-revision-hash=alluxio-master-96c6758c
              heritage=Helm
              name=alluxio-master
              release=alluxio-1598231414
              role=alluxio-master
              statefulset.kubernetes.io/pod-name=alluxio-master-0
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  StatefulSet/alluxio-master
Init Containers:
  journal-format:
    Container ID:  docker://6e2ae4d6de07e7d763f419d92f6d34c94d54f28940b5d982acd8b29de6d28c34
    Image:         alluxio/alluxio:2.3.0
    Image ID:      docker-pullable://alluxio/alluxio@sha256:caf1f0aaa8529082d7562e8b9e4bcd2d845e376a9261b44cf96799e88f4bea3a
    Port:          <none>
    Host Port:     <none>
    Command:
      alluxio
      formatJournal
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 24 Aug 2020 09:10:19 +0800
      Finished:     Mon, 24 Aug 2020 09:10:20 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /journal from alluxio-journal (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2lqr6 (ro)
Containers:
  alluxio-master:
    Container ID:  docker://157548c56fb8a611e7c2844e53319e5ec9e11c8fcfec304c6494eb5322bb91bd
    Image:         alluxio/alluxio:2.3.0
    Image ID:      docker-pullable://alluxio/alluxio@sha256:caf1f0aaa8529082d7562e8b9e4bcd2d845e376a9261b44cf96799e88f4bea3a
    Ports:         19998/TCP, 19999/TCP, 19200/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Command:
      /entrypoint.sh
    Args:
      master-only
      --no-format
    State:          Running
      Started:      Mon, 24 Aug 2020 09:10:21 +0800
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     4
      memory:  8G
    Requests:
      cpu:      1
      memory:   1G
    Liveness:   exec [alluxio-monitor.sh master] delay=15s timeout=5s period=30s #success=1 #failure=2
    Readiness:  exec [alluxio-monitor.sh master] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment Variables from:
      alluxio-config  ConfigMap  Optional: false
    Environment:
      ALLUXIO_MASTER_HOSTNAME:  alluxio-master-0 (v1:metadata.name)
    Mounts:
      /journal from alluxio-journal (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2lqr6 (ro)
  alluxio-job-master:
    Container ID:  docker://f575b264dd75f5ec8d7a24630dbdcdc69667655f7140d4959334b68e742572f8
    Image:         alluxio/alluxio:2.3.0
    Image ID:      docker-pullable://alluxio/alluxio@sha256:caf1f0aaa8529082d7562e8b9e4bcd2d845e376a9261b44cf96799e88f4bea3a
    Ports:         20001/TCP, 20002/TCP, 20003/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Command:
      /entrypoint.sh
    Args:
      job-master
    State:          Running
      Started:      Mon, 24 Aug 2020 09:10:21 +0800
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     4
      memory:  8G
    Requests:
      cpu:      1
      memory:   1G
    Liveness:   exec [alluxio-monitor.sh job_master] delay=15s timeout=5s period=30s #success=1 #failure=2
    Readiness:  exec [alluxio-monitor.sh job_master] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment Variables from:
      alluxio-config  ConfigMap  Optional: false
    Environment:
      ALLUXIO_MASTER_HOSTNAME:  alluxio-master-0 (v1:metadata.name)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2lqr6 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  alluxio-journal:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  1Gi
  default-token-2lqr6:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-2lqr6
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  alluxio=true
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age        From                    Message
  ----    ------     ----       ----                    -------
  Normal  Scheduled  <unknown>  default-scheduler       Successfully assigned spark/alluxio-master-0 to k8s-bignode03
  Normal  Pulled     11m        kubelet, k8s-bignode03  Container image "alluxio/alluxio:2.3.0" already present on machine
  Normal  Created    11m        kubelet, k8s-bignode03  Created container journal-format
  Normal  Started    11m        kubelet, k8s-bignode03  Started container journal-format
  Normal  Pulled     11m        kubelet, k8s-bignode03  Container image "alluxio/alluxio:2.3.0" already present on machine
  Normal  Created    11m        kubelet, k8s-bignode03  Created container alluxio-master
  Normal  Started    11m        kubelet, k8s-bignode03  Started container alluxio-master
  Normal  Pulled     11m        kubelet, k8s-bignode03  Container image "alluxio/alluxio:2.3.0" already present on machine
  Normal  Created    11m        kubelet, k8s-bignode03  Created container alluxio-job-master
  Normal  Started    11m        kubelet, k8s-bignode03  Started container alluxio-job-master

The master pods seem to be started,but logs for the master are the same.Can you reproduce the issue in your env?

When i use single master to deploy alluxio,everything seems to be  alright.
And my values.yaml :
#
# The Alluxio Open Foundation licenses this work under the Apache License, version 2.0
# (the "License"). You may not use this work except in compliance with the License, which is
# available at www.apache.org/licenses/LICENSE-2.0
#
# This software is distributed on an "AS IS" basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
# either express or implied, as more fully set forth in the License.
#
# See the NOTICE file distributed with this work for information regarding copyright ownership.
#

# This should not be modified in the usual case.
fullnameOverride: alluxio

## Common ##

# Docker Image
image: alluxio/alluxio
imageTag: 2.3.0
imagePullPolicy: IfNotPresent

# Security Context
user: 0
group: 0
fsGroup: 0

# Site properties for all the components
properties:
  # alluxio.user.metrics.collection.enabled: 'true'
#  alluxio.security.stale.channel.purge.interval: 365d
  alluxio.master.mount.table.root.ufs: "s3://spark-k8s/alluxio_k8s/"
  alluxio.master.mount.table.root.option.aws.accessKeyId: "AZ0MJYCXF0EBSSDB7QZQ"
  alluxio.master.mount.table.root.option.aws.secretKey: "QgDR2m9U3BUISA8B443Axmgtlox0YJBufzhyIkoY"
  alluxio.master.mount.table.root.option.alluxio.underfs.s3.endpoint: "http://<IP_ADDRESS>:8000"
  # worker props
  #alluxio.worker.data.server.domain.socket.address: /opt/domain
  #alluxio.worker.data.server.domain.socket.as.uuid: true
  # master props
  alluxio.master.metastore.dir: "/mnt/data/alluxio-k8s/metastore"

# Recommended JVM Heap options for running in Docker
# Ref: https://developers.redhat.com/blog/2017/03/14/java-inside-docker/
# These JVM options are common to all Alluxio services
# jvmOptions:
#   - "-XX:+UnlockExperimentalVMOptions"
#   - "-XX:+UseCGroupMemoryLimitForHeap"
#   - "-XX:MaxRAMFraction=2"

# Mount Persistent Volumes to all components
# mounts:
# - name: <persistentVolume claimName>
#   path: <mountPath>

# Use labels to run Alluxio on a subset of the K8s nodes
nodeSelector: {"alluxio": "true"}

## Master ##

master:
  count: 1 # Controls the number of StatefulSets. For multiMaster mode increase this to >1.
  replicas: 1 # Controls #replicas in a StatefulSet and should not be modified in the usual case.
  args: # Arguments to Docker entrypoint
    - master-only
    - --no-format
  # Properties for the master component
  properties:
    # Example: use ROCKS DB instead of Heap
    # alluxio.master.metastore: ROCKS
    # alluxio.master.metastore.dir: /metastore
  resources:
    # The default xmx is 8G
    limits:
      cpu: "4"
      memory: "8G"
    requests:
      cpu: "1"
      memory: "1G"
  ports:
    embedded: 19200
    rpc: 19998
    web: 19999
  hostPID: false
  hostNetwork: false
  # dnsPolicy will be ClusterFirstWithHostNet if hostNetwork: true
  # and ClusterFirst if hostNetwork: false
  # You can specify dnsPolicy here to override this inference
  # dnsPolicy: ClusterFirst
  # JVM options specific to the master container
  jvmOptions:
  nodeSelector: {}

jobMaster:
  args:
    - job-master
  # Properties for the jobMaster component
  properties:
  resources:
    limits:
      cpu: "4"
      memory: "8G"
    requests:
      cpu: "1"
      memory: "1G"
  ports:
    embedded: 20003
    rpc: 20001
    web: 20002
  # JVM options specific to the jobMaster container
  jvmOptions:

# Alluxio supports journal type of UFS and EMBEDDED
# UFS journal with HDFS example
# journal:
#   type: "UFS"
#   folder: "hdfs://{$hostname}:{$hostport}/journal"
# EMBEDDED journal to /journal example
# journal:
#   type: "EMBEDDED"
#   folder: "/journal"
journal:
  type: "UFS" # "UFS" or "EMBEDDED"
  ufsType: "local" # Ignored if type is "EMBEDDED". "local" or "HDFS"
  folder: "/journal" # Master journal folder
  # volumeType controls the type of journal volume.
  # It can be "persistentVolumeClaim" or "emptyDir"
  volumeType: emptyDir
  size: 1Gi
  # Attributes to use when the journal is persistentVolumeClaim
  storageClass: "standard"
  accessModes:
    - ReadWriteOnce
  # Attributes to use when the journal is emptyDir
  medium: ""
  # Configuration for journal formatting job
  format:
    runFormat: true # Change to true to format journal

# You can enable metastore to use ROCKS DB instead of Heap
# metastore:
#   volumeType: persistentVolumeClaim # Options: "persistentVolumeClaim" or "emptyDir"
#   size: 1Gi
#   mountPath: /metastore
# # Attributes to use when the metastore is persistentVolumeClaim
#   storageClass: "standard"
#   accessModes:
#    - ReadWriteOnce
# # Attributes to use when the metastore is emptyDir
#   medium: ""

## Worker ##

worker:
  args:
    - worker-only
    - --no-format
  # Properties for the worker component
  properties:
  resources:
    limits:
      cpu: "4"
      memory: "4G"
    requests:
      cpu: "1"
      memory: "2G"
  ports:
    rpc: 29999
    web: 30000
  # hostPID requires escalated privileges
  hostPID: false
  hostNetwork: false
  # dnsPolicy will be ClusterFirstWithHostNet if hostNetwork: true
  # and ClusterFirst if hostNetwork: false
  # You can specify dnsPolicy here to override this inference
  #dnsPolicy: ClusterFirstWithHostNet
  # JVM options specific to the worker container
  jvmOptions:
  nodeSelector: {}

jobWorker:
  args:
    - job-worker
  # Properties for the jobWorker component
  properties:
  resources:
    limits:
      cpu: "4"
      memory: "4G"
    requests:
      cpu: "1"
      memory: "1G"
  ports:
    rpc: 30001
    data: 30002
    web: 30003
  # JVM options specific to the jobWorker container
  jvmOptions:

# Tiered Storage
# emptyDir example
#  - level: 0
#    alias: MEM
#    mediumtype: MEM
#    path: /dev/shm
#    type: emptyDir
#    quota: 1G
#
# hostPath example
#  - level: 0
#    alias: MEM
#    mediumtype: MEM
#    path: /dev/shm
#    type: hostPath
#    quota: 1G
#
# persistentVolumeClaim example
#  - level: 1
#    alias: SSD
#    mediumtype: SSD
#    type: persistentVolumeClaim
#    name: alluxio-ssd
#    path: /dev/ssd
#    quota: 10G
#
# multi-part mediumtype example
#  - level: 1
#    alias: SSD,HDD
#    mediumtype: SSD,HDD
#    type: persistentVolumeClaim
#    name: alluxio-ssd,alluxio-hdd
#    path: /dev/ssd,/dev/hdd
#    quota: 10G,10G
tieredstore:
  levels:
    - level: 0
      alias: MEM
      mediumtype: MEM
      path: /mnt/data/alluxio-k8s/ramdisk
      type: hostPath
      quota: 10G
      high: 0.9
      low: 0.7
    - level: 1
      alias: HDD
      mediumtype: HDD
      path: /mnt/data/alluxio-k8s/hdd-disk1
      type: hostPath
      quota: 100G
      high: 0.9
      low: 0.7

# Short circuit related properties
shortCircuit:
  enabled: true
  # The policy for short circuit can be "local" or "uuid",
  # local means the cache directory is in the same mount namespace,
  # uuid means interact with domain socket
  policy: uuid
  # volumeType controls the type of shortCircuit volume.
  # It can be "persistentVolumeClaim" or "hostPath"
  volumeType: hostPath
  size: 1Mi
  # Attributes to use if the domain socket volume is PVC
  pvcName: alluxio-worker-domain-socket
  accessModes:
    - ReadWriteOnce
  storageClass: standard
  # Attributes to use if the domain socket volume is hostPath
  hostPath: "/tmp/alluxio-domain" # The hostPath directory to use

## FUSE ##

fuse:
  image: alluxio/alluxio-fuse
  imageTag: 2.3.0
  imagePullPolicy: IfNotPresent
  # Change both to true to deploy FUSE
  enabled: true
  clientEnabled: false
  # Properties for the jobWorker component
  properties:
  # Customize the MaxDirectMemorySize
  # These options are specific to the FUSE daemon
  jvmOptions:
    - "-XX:MaxDirectMemorySize=2g"
  hostNetwork: true
  # hostPID requires escalated privileges
  hostPID: true
  dnsPolicy: ClusterFirstWithHostNet
  user: 0
  group: 0
  fsGroup: 0
  args:
    - fuse
    - --fuse-opts=allow_other
  # Mount path in the host
  mountPath: /mnt/alluxio-fuse
  resources:
    requests:
      cpu: "0.5"
      memory: "1G"
    limits:
      cpu: "1"
      memory: "1G"

##  Secrets ##

# Format: (<name>:<mount path under /secrets/>):
# secrets:
#   master: # Shared by master and jobMaster containers
#     alluxio-hdfs-config: hdfsConfig
#   worker: # Shared by worker and jobWorker containers
#     alluxio-hdfs-config: hdfsConfig

When i set hostNetwork to false,everything seems to be alright.But while alluxio works with spark in k8s,i will set hostNetwork to true,which can ensure data locality.Is there something wrong with my use?Please take a look at your convenience.

Do you use the Alluxio helm repo or extract the helm package yourself from the 2.3.0 tarball?
Alluxio master pods are deployed using StatefulSet, meaning it is created one by one. Once alluxio-master-0 is Running and is Ready 2/2, alluxio-master-1 is started. You see alluxio-master-2 is not resolvable because the pod is not started yet. Normally alluxio-master-0 will start first and pass the readiness probe, although it will not find the peers for the quorum, it's gonna retry for a while and not crash. In this period alluxio-master-1 and 2 will start the same way and they will finally create the quorum.
I think the error you see in the master log is just the symptom, not the root cause. Can you please do a kubectl get pods --watch after you do helm install and add what you see here? I'd like to see if the master pods ever pass the readiness check and alluxio-master-1 gets created. You should also do kubectl describe pod alluxio-master-<index> do look for anormalies.

I have added some info here.Please take a look at your convenience.

I use the command helm install alluxio -f ./config.yaml alluxio-charts/alluxio -n spark  to install alluxio,errors are the same.I find that if i set hostNetwork to true in worker props,alluxio can not work,but when i set it to false ,allxuio can deploy success.
And in both cases, alluxio does not work properly when i test with spark which read data from alluxio.

Thanks for the additional information!
A quick test to run is to try 2.4.0-SNAPSHOT solves your problem, there has been a few improvements related to fuse.
From your information, it seems your workers are never READY for serving. I would check if you can ping or curl to the master service names (alluxio-master-0) from the master/worker pods. If that does not work, check what is wrong with the services by kubectl describe svc alluxio-master-x.
I will try to reproduce your case and let you know too.

Thanks for your replay!
When i set hostNetwork to true in worker props ,i can ping to the master service names (alluxio-master-0) from the master pods,but can not ping to alluxio-master-0 from worker pods . And i use the command  kubectl -n spark describe svc alluxio-master-o to get infos :
[root@k8s-master01 ~]# kubectl -n spark describe svc  alluxio-master-0
Name:              alluxio-master-0
Namespace:         spark
Labels:            app=alluxio
                   chart=alluxio-0.6.11
                   heritage=Helm
                   release=alluxio-1598952492
                   role=alluxio-master
Annotations:       <none>
Selector:          app=alluxio,release=alluxio-1598952492,role=alluxio-master,statefulset.kubernetes.io/pod-name=alluxio-master-0
Type:              ClusterIP
IP:                None
Port:              rpc  19998/TCP
TargetPort:        19998/TCP
Endpoints:         <IP_ADDRESS>:19998
Port:              web  19999/TCP
TargetPort:        19999/TCP
Endpoints:         <IP_ADDRESS>:19999
Port:              job-rpc  20001/TCP
TargetPort:        20001/TCP
Endpoints:         <IP_ADDRESS>:20001
Port:              job-web  20002/TCP
TargetPort:        20002/TCP
Endpoints:         <IP_ADDRESS>:20002
Port:              embedded  19200/TCP
TargetPort:        19200/TCP
Endpoints:         <IP_ADDRESS>:19200
Port:              job-embedded  20003/TCP
TargetPort:        20003/TCP
Endpoints:         <IP_ADDRESS>:20003
Session Affinity:  None
Events:            <none>

When i change the version of alluxio to 2.4.0-SNAPSHOT,errors are same.Any suggestions would be appreciate!

@marrycheck I tried both https://alluxio-charts.storage.googleapis.com/openSource/2.3.0 and https://alluxio-charts.storage.googleapis.com/openSource/2.4.0-SNAPSHOT but did not reproduce your issue. I'm installing with your config (almost the same, changed a few properties like aws key). I'm running with master not using hostNetwork and workers using hostNetwork.
NAME                   READY   STATUS    RESTARTS   AGE     IP              NODE            NOMINATED NODE   READINESS GATES
alluxio-fuse-29crc     1/1     Running   0          4m21s   172.x.x.x   172.x.x.x   <none>           <none>
alluxio-fuse-mp8r8     1/1     Running   0          4m21s   172.x.x.x   172.x.x.x   <none>           <none>
alluxio-master-0       2/2     Running   0          4m21s   <IP_ADDRESS>       172.x.x.x   <none>           <none>
alluxio-master-1       2/2     Running   0          4m3s    <IP_ADDRESS>       172.x.x.x   <none>           <none>
alluxio-master-2       2/2     Running   0          3m44s   <IP_ADDRESS>       172.x.x.x   <none>           <none>
alluxio-worker-cm9wt   2/2     Running   0          4m21s   172.x.x.x   172.x.x.x   <none>           <none>
alluxio-worker-jdnl7   2/2     Running   0          4m21s   172.x.x.x   172.x.x.x   <none>           <none>

Unfortunately the checks on the easy perspectives do not solve your issue. Based on the information i cannot think of a root cause for you issue, but I would suggest maybe checking the following. They should at least give us a bit direction on what to look next:

What if your k8s network setup? For example, iptables or ipvs? Do you have any specific setting in your environment like PodSecurityConext?
What CNI implementation do you use? For example, in our test environment we are using weave. Are there logs in the CNI provider pods that you can check?

Some other tests that I can think of:

Create pods that are not relevant to alluxio, for example nginx in your environment. Try if you can make it ping alluxio-master-x services successfully with and without host network. And can the ngnix pods ping IPs of alluxio worker/master pods? Note that if your masters are using HA, only the primary master will respond to your curl requests.
What other services are using host network in your environment, and how are they set up?

Thanks for your suggestions.
i use ipvs`` and weave, neither have no any settings for  PodSecurityConext```.
I test with nginx by using hostNetwork,and can not ping alluio-master-x.Then i change to another k8s env,alluxio seems to be ok.Em,,,i do not know why.Thanks again!

Shutdown flannel checksum  by using ethtool -K flannel.1 tx-checksum-ip-generic off seem to solve this issue.

same issue with you.

Shutdown flannel checksum by using ethtool -K flannel.1 tx-checksum-ip-generic off seem to solve this issue.

Flannel checksum is there for a reason. How is this a remedy even let alone a solution? At ebst its a temp hack and its been 2 years Alluxio should have fixed this ...

And of course ethtool -K flannel.1 tx-checksum-ip-generic off did not fix the issue for me even

/reopen

Same Issue here. Helm version = 0.6.54  Alluxio version =  2.9.3


Roll engine a71609f0695c..56d8634c51ff (2 commits)

https://github.com/flutter/engine/compare/a71609f0695c...56d8634c51ff
git log a71609f0695c2977ac96b7a79e67e24767abfda2..56d8634c51ff50534b1853b71205eff861131dcf --no-merges --oneline
56d8634c5 Improve shadow doc in PhysicalShapeLayer (flutter/engine#8114)
bd0f9085e Adds a platfromViewId to SemanticsNode (flutter/engine#8055)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (mklim@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Tooltips font loading Times New Roman locally

Tooltips on growth charts should have Montserrat font, like in the live demo, but when running locally the font loads in as Times New Roman

To add context - this behaviour only seems to occur when using Storybook, so there is a good chance it's related to that. The live demo on rcpch.ac.uk works perfectly

Fixed and merged in v7.0.0. Documentation updated


FFXIV_ACT_Plugin_Korean.dll is not needed

There is no need to find FFXIV_ACT_Plugin_Korean.dll anymore.

Does nobody use this anymore? Or everybody renames it?

If you see latest Korean release, here, it's original name does not contain "Korean".
It had been renamed by "해루봇" which is ACT maintainer for Korean users, but it's not renaming anymore.

Thanks for the explanation!


inputFormat to 24-hour leaves picker with AM/PM

I'm setting the inputFormat to 24-hour, as below:
<DateTimeField
 label="test"
 inputFormat="DD/MM/YYYY HHmm" />

This works fine for the value that's displayed in the field, but the time picker dialog still only lets you select from 12 hours with AM/PM symbols.
This makes no sense.  The inputFormat parameter needs to change the picker to 24-hours too.  Or there needs to be another parameter to set that.

I am facing the same problem. Did you found any solution for this?


Step 4 added how to open project

Added information on how to open chat triggers in IntelliJ.

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


Compliance Report D | Allow more than two decimals and negative values in schedule D output table |2|

In the output table, we want to allow more than 2 decimals and negative values. Note: this should only be allowed for the output table in Schedule D, and not for the rest of the compliance report fields.
https://trello.com/c/z4bgBib0/1737-compliance-report-d-allow-more-than-two-decimals-and-negative-values-in-schedule-d-output-table-2

resolved in sprint tunguska


ptv3-semseg training problem

When I was training ptv3-semseg on s3dis, I encountered the "ValueError: Trainer: num_samples should be a positive integer value, but got num_samples=0 ", the workaround I found on the network told me to set shuffle in dataloader to False, However, I still encounter the above error after making the change. How can I solve it?

Hi, pleaase check whether the processed data is correctly linked to the default data path (Pointcept/data/s3dis)


Connect / Link to Lake datatabases Virtual Tables data

Dear Guys,
can you confirm that it will NOT be possible to:

Connect to Virtual Table data using Power BI Dataverse connector;
Include Virtual Tables in the Azure Synapse Link;

Thanks!
JP

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

ID: a5b64c8d-3c3d-4e4d-afb1-5e0a54c84046
Version Independent ID: 8180bdbe-ec98-642e-b7ee-1f57954ee502
Content: Create virtual tables using virtual connectors (Microsoft Dataverse) - Power Apps
Content Source: powerapps-docs/developer/data-platform/virtual-entities/create-virtual-tables-using-connectors.md
Service: powerapps
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

@gpitzalis Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Add Installation Steps

@christinakayastha I have removed the duplicate dependencies, should be able to merge now.


The training is easy to collapse

Thanks for your sharing. I have one question, after I have made some changes for running on my environment (Python 3.6, Pytorch 4.1), the training is easy to collapse （ loss be NAN), have you encountered it ?
Best,

Thanks for your sharing. I have one question, after I have made some changes for running on my environment (Python 3.6, Pytorch 4.1), the training is easy to collapse （ loss be NAN), have you encountered it ?
Best,

Thanks for your sharing. I have one question, after I have made some changes for running on my environment (Python 3.6, Pytorch 4.1), the training is easy to collapse （ loss be NAN), have you encountered it ?
Best,

I got the same problem as you,have you figure it out?


Branch: Quicklogic : Yosys optimizes the design completely when no IO's/ PADs defined in the design

Steps to reproduce the issue

Synthesize any design without IO pads using yosys

IP designs on S3 devices can be used for processing data within S3, without external IO defined in the IP design. S3 has ASSP block (M4) which interfaces with the FPGA block, so there could be design where M4 sends data to FPGA, FPGA IP (like FFT) process the data and sends it back to M4. No external IO, in the FPGA IP, need to be defined in these scenario.
But Yosys, completely optimizes the design when it does not see any IO defined in the FPGA design.
Test_Design2.zip

I updated https://github.com/antmicro/yosys/tree/quicklogic fork, where the support for QuickLogic devices currently resides. Now the qlal4s3b_cell_macro module has attribute keep that will preserve this cell, and communication with it.

The issue is fixed. So closing the issue.
Thanks & Best Regards,
Rakesh


Fallback to NATs if staging over http isn't there

Thanks for contributing to the cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:
When staging over http isn't supported on the DEA, fallback to NATs

An explanation of the use cases your change solves
Rolling upgrade when CC supports staging and the DEAs don't yet.

[x] I have viewed signed and have submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[x] I have run all the unit tests using bundle exec rake

[x] I have run CF Acceptance Tests on bosh lite

[#118970125]

Looks like this pull request was merged already, but not closed.


Generating same access token for all users with Client Credential Grant Type

The application receives the same access token for the user for the grant type Client_Credentials.
An unauthenticated user launch the application
apiGateway: https://sandbox-test.com:8243/token
grant_type=client_credentials
Steps To reproduce the issue.
User 1  in  Machine 1
{"access_token":"65f2f8a9-f45b-3d08-a8c4-f40eef3fe471", "scope":"am_application_scope default","token_type":"Bearer","expires_in":1989}
User 2  in  Machine 2
{"access_token":"65f2f8a9-f45b-3d08-a8c4-f40eef3fe471","scope":"am_application_scope default","token_type":"Bearer","expires_in":1962}
User 3  in  Machine 3
{"access_token":"65f2f8a9-f45b-3d08-a8c4-f40eef3fe471","scope":"am_application_scope default","token_type":"Bearer","expires_in":1778}
Note :- access token is same for all user with different expiry times.
Here is my concern: -
Why we are getting same access toke for all user, is there any way to refresh?
Is there any approach to get the new access toke for each user request?
Is there any way to update the expiry time for each new request?
Please help me to resolve the issue.

The issue is with Unauthenticated user
Two unauthenticated launches the application from and we are using the same client key, client secret for the request. We are getting same access token for the 2 unauthenticated users.
grant_type=client_credentials
Here is the response for the 2 Unauthenticated users
Unauthenticated User 1
{"access_token":"65f2f8a9-f45b-3d08-a8c4-f40eef3fe471", "scope":"am_application_scope default","token_type":"Bearer","expires_in":1989}
Unauthenticated User 2
{"access_token":"65f2f8a9-f45b-3d08-a8c4-f40eef3fe471","scope":"am_application_scope default","token_type":"Bearer","expires_in":1962}
Here is the Requirement: -
Is there any approach to get different access token and the expiry time with Client credential grant for all the unauthenticated users?
Is there any approach to get different token by using Client credential grant?
Expected Result
User1
{"access_token":"123456", "scope":"am_application_scope default","token_type":"Bearer","expires_in":3600}
User2
{"access_token":"987654", "scope":"am_application_scopedefault","token_type":"Bearer","expires_in":3600}
Is there any approach to get the same fixed expiry time for each unauthenticated user?
Expected Result
User1
{"access_token":"123456", "scope":"am_application_scope default","token_type":"Bearer","expires_in":3600}
User2
{"access_token":"123456", "scope":"am_application_scope default","token_type":"Bearer","expires_in":3600}
Please help me to resolve the issue.

Can we use 'authorization code' grant for anonymous user(a user without login and credentials)?

Can we use 'authorization code' grant for anonymous user(a user without login and credentials)?

Unfortunately, this is not the intended usage of the Authorization code grant defined by RFC6749 . According to the specification, mentioned grant must interact with the resource owner (simply user).

The authorization code grant type is used to obtain both access tokens and refresh tokens and is optimized for confidential clients. Since this is a redirection-based flow, the client must be capable of interacting with the resource owner's user-agent (typically a web browser) and capable of receiving incoming requests (via redirection) from the authorization server.

If your use case involves an anonymous user, then I see two approaches you can try.

Allow user to register and obtain credentials

This is supported by WSO2 IS. More can be read from this link.

Obtain access token for anonymous users through client credential grant

Given that there is no user login, your application can obtain tokens that are granted on client credentials. From your backend, you can expose APIs which allow access on top of access tokens obtain through client credential grant. How to do the separation ? For this you can use WSO2 token introspection  and verify for scope and username values.

For the above suggestion, we observe a peculiar behavior. When we have user 1 and user 2 accessing application simultaneously with client credential grant and getting distinct token, It is observed that within sometime the token for both users get revoked somehow.

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 new connection by connection string with username and password

I'd like to have a fast way to add a connection by using a connection strings (including username and password).
For example -<EMAIL_ADDRESS>I saw that I can add from JDBC URL but it doesn't parse the username and password, and it also uses the Old Postgres driver instead of New Postgres driver, which gives me less features (no Lock Manager).

Thanks for the idea


Vega links don't appear to behave as default, when embedded in scala JS?

Solved with the new embedding facades


Ignore unknown items when selling junk

Some servers (e.g. Turtle WoW) have custom grey items, that are not present in SellValueDB.
To be on the safe side, skip over these items when selling junk. (Before this change, we would throw a lua error and sell nothing.)

Thanks for your contribution, but I prefer to not have it abort everything just because a value is unknown.
I decided to just assume 0-value on unknown items. So the end-result displaying the value might be off, but at least everything got sold without any errors:
https://github.com/shagu/ShaguTweaks/commit/c3e5cebc29cae4d5bf8980771e4da6a7ddaf2ed9


Symbolize keys in options hash

https://bugzilla.redhat.com/show_bug.cgi?id=1542661
Symbolize the first level keys in the options hash.
Symbols are only supported in Ruby, when a options hash (dictionary) is sent from other languages via the REST API, they send the keys as strings.
This PR saves the options keys as symbols.

@Fryguy @gtanzillo @gmcculloug
Please review

@mkanoor Please review test failures

Symbols are only supported in Ruby, when a options hash (dictionary) is sent from other languages via the REST API, they send the keys as strings.

When the options hash is sent from any language via the REST API, they send the keys as strings. That's how JSON works.
Why convert to symbols? Maybe callers should use HashWithIndifferentAccess or...
Why isn't this treated as an API concern as it's the API's problem? The API should know that all inputs need to be handled appropriately to the backend, be it HWIA or 'just always use strings' or 'just always use symbols' It is the thing taking in input, afterall. Is this a problem elsewhere? I bet it is.
Why are only the first level keys symbolized? Do we now have hashes where some keys are symbols and others (further in the nesting) are strings? That sounds pretty confusing.

I don't disagree since a hash containing symbols is converted to a string before it is sent out by the REST API.
So it might make sense to convert it at the API layer on the way in.
Changing it to HWIA for the blocker bug is risky we can do it in the next release.

I would propose that go with this PR for Gaprindasvili only since it's a blocker and holding up the release. We can address this on the API side on master. @Fryguy @chrisarcand @mkanoor what do you think?

I think this PR alone is likely to break many user implementations since the options can be updated from automate scripts and we have not enforced symbols or strings there in the past.  There is likely many user scripts that expect to set/get strings and this change would break all get calls using keys as strings.
There is less exposure on the API side and going forward I think it makes sense to look into using HashWithIndifferentAccess.

@imtayadeway Can you work on making the suggested change on the API side?

@mkanoor I'm struggling to understand what is going on here. For requests, we already deserialize options by symbolizing all the keys. There is however a special case for creating provision requests: https://github.com/ManageIQ/manageiq-api/blob/01aff85924673fbadfdd65cdada8289fad885e15/app/controllers/api/provision_requests_controller.rb#L5-L19. As you can see, we don't do any handling of the options directly there, all that data must get munged by the provision workflow, and it's not clear to me what ends up in the options field.

@mkanoor where is that options hash coming from? Because it's not sent in the request as "options": { "foo": "etc"}

@imtayadeway its coming from Ansible which is trying to update the options hash with provisioning information. It uses the REST API to edit the resource.

@mkanoor have you managed to reproduce the issue? Because we should already be deserializing options hashes properly

@imtayadeway Its in the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1542661
and we have also been able to reproduce it locally

@mkanoor would you mind sharing which API requests were used to recreate it?

@imtayadeway
We have a request_task which has the options, for the requests I do see that we symbolize the keys
https://github.com/ManageIQ/manageiq-api/blob/master/lib/services/api/request_parser.rb#L13
Can we check if the request_task also tries to symbolize the keys like requests does?

@imtayadeway
https://github.com/ManageIQ/manageiq-api/blob/f257e71ea7c78063659efe2d5bc77c8cc14f659f/app/controllers/api/subcollections/request_tasks.rb#L12

Closed in favor of https://github.com/ManageIQ/manageiq-api/pull/317


Add createdBy name to test result query and results table

Related Issue or Background Info

#514

Changes Proposed

Adds ApiUser type to graphql schema
Maps in frontend
Updates associated FE snapshot

Looks like #513 leaked in here a bit. I can remove the frontend changes if it bothers anyone

What other properties of the user might we expose? If it's just a single string, should we just unwrap that into the parent?
Though on the flip side, returning the name as a single string puts name formatting into the API instead of the front end, which seems iffy...

@benwarfield-usds Good point re: doing this formatting on the FE. We in fact already have functions to do so, so I'll move it there instead.
With respect to what other properties to expose, I'm not sure. My approach was going to be to keep it as minimal as possibly, but that might not be graphql-y?


nyc not working with project type module (esm)

Expected Behavior
to extract a code coverage report in text and html format for my node project working as a module (with esm)
Observed Behavior
NOT WORKING!
=============================== Coverage summary ===============================
Statements   : Unknown% ( 0/0 )
Branches     : Unknown% ( 0/0 )
Functions    : Unknown% ( 0/0 )
Lines        : Unknown% ( 0/0 )
================================================================================

Troubleshooting steps

[ YES] still occurring when I put cache: false in my nyc config

Environment Information
  System:
    OS: macOS 14.1.1
    CPU: (8) arm64 Apple M2
    Memory: 40.91 MB / 16.00 GB
  Binaries:
    Node: 21.6.0 - /usr/local/bin/node
    npm: 10.2.4 - /usr/local/bin/npm
    pnpm: 8.10.5 - /usr/local/bin/pnpm
  npmPackages:
    nyc: ^15.1.0 => 15.1.0

Experiencing the same issue in Node: v20.11.0 when running ESM code.
Tested with, or without --require esm

Duplicate of https://github.com/istanbuljs/nyc/issues/1530 I think

finally c8 worked for me, instead of nyc (which is still failing):
c8 --experimental-monocart --reporter=html --reporter=text mocha logic/*.spec.js


v1.1.23

Bug fixes

#572 - fix for qualifier option for new dates

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.212%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7893

Relevant Lines:
7966

💛  - Coveralls


Add NUSD token

Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists

[x] logo dimensions: 120*120 px
[x] logo background: Transparent
[x] At least one transaction on the token contract
[x] For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
[x] Same document name for both .json and .png (Including capitalization)

Project background:
Official announcement: https://neutralproject.com/token-profile.html
Project team background: Our team has deep industry experience spanning blockchain development, distributed systems, investments, and trading knowledge to usher in the next ecosystem of financial instruments. We blend this expertise along with renown thought leadership from academia to deliver high-quality, innovative products that will help both institutions and retail investors alike invest in emerging crypto assets.
Project basic information: The Neutral Dollar is built as a metastable basket, fully collateralized by and inter-exchangeable with constituent stablecoins. The result is a superior digital dollar by being a lower volatility token with a more subdued risk profile. The construction is designed to be liquidity- and exchange- neutral, enabling us to have merits and applications that no individual stablecoin project alone can exhibit. It is a better instrument to result in a greater pool of liquidity, stable medium of exchange, and unit of account.
Media publications:

https://finance.yahoo.com/news/kucoin-among-first-exchanges-support-100036117.html
https://medium.com/@neutralproject/earn-6-5-interest-on-nusd-with-nexo-guaranteed-by-crypto-insurance-2d5603b1010a
https://www.crowdfundinsider.com/2019/04/146336-neutral-dollar-stablecoin-launched-by-sequoia-funded-neutral/
https://medium.com/ddex/neutral-dollar-nusd-a-diversified-basket-of-stablecoins-announces-ddex-exchange-listing-33c3134bf1da

Tradeable exchanges: DDEX, KuCoin
Recommended Gas Limit (For ERC-20 project teams) for transaction: (Default is 60,000) --

Hey @calebsevern as mentioned in the chat:

I believe that's due to the GCC_OLD definition. That token definition has a case mismatch which is causing all other PRs to fail with the same message.
There's an existing PR that claims to fix this: https://github.com/consenlabs/token-profile/pull/4159, I can rebase as soon as it's merged in.

hi, we've fixed the issue. And you need to re-pr so that will be ok. This one should be closed.


Fix pin mode for STM32F1 target.

Failed for pin_index 0 (PA_0, PB_0,PC_0).
Usecase:
DigitalIn pa0(PA_0, PullUp);
//or
gpio_t gpio;
gpio_init(&gpio, C9);
gpio_dir(&gpio, PIN_INPUT);
gpio_mode(&gpio, PullDown);

in both cases GPIO registers are corrupted.

cc @bcostm @adustm ,please review

LGTM

@anpilog Can you have a look at : https://developer.mbed.org/users/mbed_official/code/mbed-src/issues/14 ? That was the previous bugfix that this patch reverts, as @bcostm highlighted above

This PR does not revert the previous code. It fixes an issue when the pin number is equal to 0.

Thanks, I missed that as github aligned lines, I spotted only first constant to be changed, not that -1 removal


Always add var.security_groups to launch template

what

If var.security_groups is present, add any passed in security groups to the default cluster security group.

why

var.security_groups is only added to the launch template if var.remote_access_enabled is true. Additional security groups should not be dependent on SSH access being enabled to be used.
Specifically, ran into an issue when using a x-account shared VPC where the default security group for the VPC was not available to accounts the VPC was shared with. After encountering this error, when attempting to specify a security group for the launch template using var.security_groups, realized this var isn't active unless var.remote_access_enabled is also set. See below for output:

Error: error creating EKS Node Group (my-eks-node-group): InvalidRequestException: You do not have access to a default security group in VPC vpc-123456. Specify a security group, 310. Specify a security group, and try again.
│ {
│   RespMetadata: {
│     StatusCode: 400,
│     RequestID: "4a670b03-66e0-4ec2-8f42-4254c32588a4"
│   },
│   Message_: "You do not have access to a default security group in VPC vpc-123456. Specify a security group, and try again."
│ }

This seems to be mostly a workaround for launch templates as EKS managed nodegroups should be auto-assigned to the default cluster security group, even if the launch template has no security groups attached to it.
Issue was present in v0.19.0 only when using var.kubernetes_taints, but in >=v0.20.0 this issue applied to all nodegroups created with this module.
references

Using AWS provider v3.50.0

My only comment re: tests is you could add another test. As shown in another of their modules here: https://github.com/cloudposse/terraform-aws-ecs-web-app/tree/master/examples, you can make another folder for your remote_access_enabled = false test which won't modify their core test at all.


adding binary files to a release

Is it possible to add binary files using this particular action when creating a release?

Was this closed because it is implemented? If so can the README be updated? this is what I am looking to use but can't see in the docs how to go about it.

@jamlen this functionality is handled by a separate official GitHub Action: https://github.com/actions/upload-release-asset

@jamlen this functionality is handled by a separate official GitHub Action: https://github.com/actions/upload-release-asset