feat(tap): set position to tapped location

Now the slider will move to the tapped location.
This adds another way to adjust the slider other than dragging the thumb circle.
Also adds .idea to .gitignore so the whole folder is ignored

Codeowners: I wanted to get your thoughts on this. For my own project, I wanted to add tap capabilities but I'm not sure if it is desired by you. Feel free to close this if this behavior is not desired. Let me know if you'd like a video demonstrating the change.

@conkur Thanks for using this lib and creating PR with enhancement. will definitely look into this.

@akashmi Thanks! Great library, very clean. If I end up finishing my project which is currently using this library I will share my work

@conkur we have included your changes along with a few more enhancements in this PR https://github.com/Mindinventory/AndroidCircularSlider/pull/5
and released the new version 0.0.2. thanks for your contribution.


Fix session ID deadlockwhen opening a VoiceConnection

Closes https://github.com/bwmarrin/discordgo/issues/829
When checking the Voice Session ID in VoiceConnection.open(), the sessionID is populated asynchronously when websocket messages come in, see wsapi.go.
However, open() still holds the lock on the session, so the ID can never be populated, and we loop and accomplish nothing until releasing the lock upon exiting the function.
This PR addresses this deadlock bug by momentarily releasing the lock anytime the process sleeps, allowing other processes to populate the sessionID appropriately - while not sacrificing concurrency safety by releasing the lock entirely.

Thanks for the contribution!

I did the edits myself, to not hold it off for longer. Hope you understand and sorry for the wait.


Run two instances of Hyperion ?

Hi,
I would like to have to led system in my room: one doing Ambilight on my TV, and the other to control the light from my android phone.
I bought one 5m led strip to do this. Is it possible to control only a part of the led strip as Ambilight and let the other as ambilight, or is it possible to run two instances of Hyperion to control the differents led strip ?
Thks

Is there an accepted way to add hue and lightpack-multi together in one instance?

@Blabla51 works now with the forwarder, could you close this? thanks

Please refer to the new Json/Proto forwarder from rePanther.
Closed
Thank you


Very slow fill on 1.12

Hello,
We have to pre-render custom map with OTG and fill command. Problem is that we use last spigot, otg for 1.12 and it's clear install on server with 32 cpu's every to 3,7GhZ, 64gb ddr4, 500GB SSD with very fast access. So hardware and software is i think fine.
After changing server 2 times and trying many combinations with /wb fill 100-10000 0 false we got usually that.

As you see it's almost impossible to render map that have only 16k x 16k. We are doing it from 3 days with that result at this moment. I never had that problem with fill by years.

Yeah, strange. Clearly you have plenty of memory, which would have been one of the two things I'd think most likely to cause the sort of problem. The other thing would be setting too high of a frequency on the Fill command. Since you mention trying 100-10000 for the frequency, you might try the default frequency of 20 to see if that helps. As powerful as your server is, I kind of doubt it in your case, but overly high frequencies can actually un-intuitively cause that sort of slowdown instead of improving the speed.
One other thought, you are using version 1.8.7 of the plugin since you're on 1.12, right?

Cpu's can have 3,7 on HT normally from start from 2,5. Yea that's right i'm on 1.8.7 with final build of spigot for last 1.12. I tried to use Paper as well.

Do you have any other plugins running which make changes to world generation? Those could cause the process to take longer. Or do you have a mapping plugin like DynMap running? If so, you might consider disabling map updates temporarily for it until the process is complete, and do a fullrender after the world is generated.
One other thing I can think of which you might try would be to set a higher value (or possibly 0) for the fillautosave option to see if that helps.
/wb fillautosave [seconds] - set the interval for automatic saving of the world during the Fill process. Default 30 seconds, set to 0 to disable automatic world saving (not recommended).
Permission: worldborder.fillautosave

Dynmap was tested to but for now i disabled it at all and tried fillauto. With 0 it's helps a little bit, but still i have to restart server time to time.

Maybe setting the max memory to a lower value might help. If max memory is very high, many chunks can be kept loaded which can slow down the server.

In my experience WB has started eating RAM very aggressively. It dosnt matter how much mem I allocate - always getting
Available memory is very low, task is pausing. A cleanup will be attempted now, and the task will automatically continue if/when sufficient memory is freed up. Alternatively, if you restart the server, this task will automatically continue once the server is back up.
Also, thank you for hint with chunksPerRun value - I reduced it to 1 and the process became faster.

Hi - I'm having this issue on Paper build 167 for Minecraft 1.14.4, using WB 1.9.10 beta. I was getting issues running out of memory, but disabling dynmap while I generate chunks seems to fix that. But it is going very slowly:

@DmitryRendov what is the chunksPerRun value you mention?


docs: Add inspectIT Ocelot Documentation site to showcase page

Motivation
We would like to add the documentation of our Open Source project inspectIT Ocelot as we have used docusaurus for a long time now and enjoy using it eversince!
If you have any questions, feel free to reach out to me!
Greetings
Marius

Sorry, this website is using Docusaurus v1, but our showcase is for v2 sites.


Recipe: nfs::_idmap outputs Failed to start nfs-idmapd.service on Ubuntu 16.04.

I have a machine, which is running Ubuntu 16.04 Desktop, 64-bit version, that I want to set up as an NFS client.
The recipe doing this setup starts with:
include_recipe 'nfs'
include_recipe 'nfs::client4'

When cooking the machine, I get the following output:
Recipe: nfs::_common
  * apt_package[nfs-common] action install (up to date)
  * apt_package[rpcbind] action install (up to date)
  * directory[/etc/default] action create (skipped due to only_if)
  * template[/etc/default/nfs-common] action create (up to date)
  * template[/etc/modprobe.d/lockd.conf] action create (up to date)
  * service[portmap] action start (up to date)
  * service[portmap] action enable (up to date)
  * service[lock] action start (up to date)
  * service[lock] action enable (up to date)
  * service[nfs-config.service] action start (up to date)
  * service[nfs-config.service] action enable (up to date)
Recipe: nfs::_idmap
  * template[/etc/idmapd.conf] action create (up to date)
  * service[idmap] action start

    ================================================================================
    Error executing action `start` on resource 'service[idmap]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '5'
    ---- Begin output of /bin/systemctl --system start nfs-idmapd ----
    STDOUT:
    STDERR: Failed to start nfs-idmapd.service: Unit nfs-server.service not found.
    ---- End output of /bin/systemctl --system start nfs-idmapd ----
    Ran /bin/systemctl --system start nfs-idmapd returned 5

    Cookbook Trace:
    ---------------
    /home/janne/chef-solo/local-mode-cache/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
    /home/janne/chef-solo/local-mode-cache/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
    /home/janne/chef-solo/local-mode-cache/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
    /home/janne/chef-solo/local-mode-cache/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
    /home/janne/chef-solo/local-mode-cache/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'

    Resource Declaration:
    ---------------------
    # In /home/janne/chef-solo/local-mode-cache/cache/cookbooks/nfs/recipes/_idmap.rb

     29: service 'idmap' do
     30:   service_name node['nfs']['service']['idmap']
     31:   action [:start, :enable]
     32:   supports :status => true
     33: end

    Compiled Resource:
    ------------------
    # Declared in /home/janne/chef-solo/local-mode-cache/cache/cookbooks/nfs/recipes/_idmap.rb:29:in `from_file'

    service("idmap") do
      action [:start, :enable]
      supports {:status=>true}
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      service_name "nfs-idmapd"
      pattern "idmap"
      declared_type :service
      cookbook_name "nfs"
      recipe_name "_idmap"
    end

    Platform:
    ---------
    x86_64-linux

The nfs-idmap service is marked as being static. I don't know the exact meaning of static:
root@asus:~# systemctl list-unit-files | grep nfs-idmap
nfs-idmapd.service                         static
root@asus:~#

I think the name mapping works on the machine despite the failed cooking.
This make me believe that the mapping service should not be started by the nfs::_idmap recipe in this case, though I'm far from sure.

@janskarvall I had the recipe install nfs-kernel-server package, since nfs-idmapd unit file depends on nfs-server. Not sure if this is correct, because perhaps the nfs-idmapd unit file is for nfs4 server services, but then I would think it should depend nfs-kernel-server.service and not nfs-server.service?
If you, or someone else, discovers more information on this as far as providing nfs4 client services on Ubuntu 16.04 then please shoot me an update.

I think it is wrong to solve this issue by installing (and running) the nfs-kernel-server on the client. The nfs client should work without it, i.e. by only installing the nfs-common package. This is in line with the  Ubuntu 16.04 NFS documentation.
As I wrote above, I do not think that the nfs-idmapd.service shall be started on an nfs client. (Maybe it is a bug that the nfs-common package installs the nfs-idmapd.service unit file.)
I am able to cook and run my nfs client machine after having changed the _idmap.rb file to not try to start the nfs-idmapd.service. I believe that /usr/sbin/rpc.idmapd, which is running, make id mapping work.
I have tried to find information that describes this, but failed to do so. I also do not know if this behaviour is common for all systemd based distributions.
I do not have a suggestion on how to fix the _idmap.rb recipe. I could not find a way that the recipe would know if it runs on a pure nfs client or if the machine (maybe also) runs as an nfs server.

Thank you for the quick reply.  I am going to re-open this issue, and revert that change before releasing.  Will alter the recipe to skip starting the nfs-idmapd.service on Ubuntu 16.04

OK. To clarify, I think nfs-idmapd.service needs to be started whenever the nfs-kernel-server is installed. Skipping is only for a "pure" client, i.e. a host that only has nfs-common installed.

Understood

I'm getting the same also using only server recipe
include_recipe "nfs::server4"

Output is:
11:30:07      ubuntu1604: Recipe: nfs::_common
11:30:11      ubuntu1604:   * apt_package[nfs-common] action install
11:30:11      ubuntu1604:     - install version 1:1.2.8-9ubuntu12.2 of package nfs-common
11:30:11      ubuntu1604:   * apt_package[rpcbind] action install (up to date)
11:30:11      ubuntu1604:   * directory[/etc/default] action create (skipped due to only_if)
11:30:11      ubuntu1604:   * template[/etc/default/nfs-common] action create
11:30:11      ubuntu1604:     - update content in file /etc/default/nfs-common from 978a91 to 7f08ea
11:30:11      ubuntu1604:     --- /etc/default/nfs-common	2019-04-29 12:36:46.000000000 +0000
11:30:11      ubuntu1604:     +++ /etc/default/.chef-nfs-common20190905-1488-bm0xzd	2019-09-05 09:30:10.749923607 +0000
11:30:11      ubuntu1604:     @@ -1,15 +1,3 @@
11:30:11      ubuntu1604:     -# If you do not set values for the NEED_ options, they will be attempted
11:30:11      ubuntu1604:     -# autodetected; this should be sufficient for most people. Valid alternatives
11:30:11      ubuntu1604:     -# for the NEED_ options are "yes" and "no".
11:30:11      ubuntu1604:     -
11:30:11      ubuntu1604:     -
11:30:11      ubuntu1604:     -# Options for rpc.statd.
11:30:11      ubuntu1604:     -#   Should rpc.statd listen on a specific port? This is especially useful
11:30:11      ubuntu1604:     -#   when you have a port-based firewall. To use a fixed port, set this
11:30:11      ubuntu1604:     -#   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
11:30:11      ubuntu1604:     -#   For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
11:30:11      ubuntu1604:     -STATDOPTS=
11:30:11      ubuntu1604:     -
11:30:11      ubuntu1604:     -# Do you want to start the gssd daemon? It is required for Kerberos mounts.
11:30:11      ubuntu1604:     -NEED_GSSD=
11:30:11      ubuntu1604:     +# Generated by Chef for ip-172-30-2-14.ec2.internal# Local modifications will be overwritten.
11:30:11      ubuntu1604:     +STATDOPTS="--port 32765 --outgoing-port 32766"
11:30:11      ubuntu1604:   * service[portmap] action restart
11:30:11      ubuntu1604:     - restart service service[portmap]
11:30:11      ubuntu1604:   * service[lock] action restart
11:30:11      ubuntu1604:     - restart service service[lock]
11:30:11      ubuntu1604:   * service[nfs-config.service] action restart
11:30:11      ubuntu1604:     - restart service service[nfs-config.service]
11:30:11      ubuntu1604:   * template[/etc/modprobe.d/lockd.conf] action create
11:30:11      ubuntu1604:     - create new file /etc/modprobe.d/lockd.conf
11:30:11      ubuntu1604:     - update content in file /etc/modprobe.d/lockd.conf from none to b06a17
11:30:11      ubuntu1604:     --- /etc/modprobe.d/lockd.conf	2019-09-05 09:30:11.061923361 +0000
11:30:11      ubuntu1604:     +++ /etc/modprobe.d/.chef-lockd20190905-1488-5oyutu.conf	2019-09-05 09:30:11.061923361 +0000
11:30:11      ubuntu1604:     @@ -1 +1,4 @@
11:30:11      ubuntu1604:     +# Generated by Chef for ip-172-30-2-14.ec2.internal
11:30:11      ubuntu1604:     +# Local modifications will be overwritten.
11:30:11      ubuntu1604:     +options lockd nlm_udpport=32768 nlm_tcpport=32768
11:30:11      ubuntu1604:     - change mode from '' to '0644'
11:30:11      ubuntu1604:   * service[portmap] action restart
11:30:11      ubuntu1604:     - restart service service[portmap]
11:30:11      ubuntu1604:   * service[lock] action restart
11:30:11      ubuntu1604:     - restart service service[lock]
11:30:11      ubuntu1604:   * service[nfs-config.service] action restart
11:30:11      ubuntu1604:     - restart service service[nfs-config.service]
11:30:11      ubuntu1604:   * service[portmap] action start (up to date)
11:30:11      ubuntu1604:   * service[portmap] action enable (up to date)
11:30:11      ubuntu1604:   * service[lock] action start (up to date)
11:30:11      ubuntu1604:   * service[lock] action enable
11:30:11      ubuntu1604:     - enable service service[lock]
11:30:11      ubuntu1604:   * service[nfs-config.service] action start (up to date)
11:30:11      ubuntu1604:   * service[nfs-config.service] action enable (up to date)
11:30:11      ubuntu1604: Recipe: nfs::_idmap
11:30:11      ubuntu1604:   * template[/etc/idmapd.conf] action create
11:30:11      ubuntu1604:     - update content in file /etc/idmapd.conf from 44726c to ca812b
11:30:11      ubuntu1604:     --- /etc/idmapd.conf	2019-04-29 12:36:46.000000000 +0000
11:30:11      ubuntu1604:     +++ /etc/.chef-idmapd20190905-1488-vswu0f.conf	2019-09-05 09:30:11.753922948 +0000
11:30:11      ubuntu1604:     @@ -2,11 +2,35 @@
11:30:11      ubuntu1604:
11:30:11      ubuntu1604:      Verbosity = 0
11:30:11      ubuntu1604:      Pipefs-Directory = /run/rpc_pipefs
11:30:11      ubuntu1604:     -# set your own domain here, if id differs from FQDN minus hostname
11:30:11      ubuntu1604:     -# Domain = localdomain
11:30:11      ubuntu1604:
11:30:11      ubuntu1604:     +# The following should be set to the local NFSv4 domain name
11:30:11      ubuntu1604:     +# The default is the host's DNS domain name.
11:30:11      ubuntu1604:     +Domain = ec2.internal
11:30:11      ubuntu1604:     +
11:30:11      ubuntu1604:     +# The following is a comma-separated list of Kerberos realm
11:30:11      ubuntu1604:     +# names that should be considered to be equivalent to the
11:30:11      ubuntu1604:     +# local realm, such that<EMAIL_ADDRESS>can be assumed to
11:30:11      ubuntu1604:     +# be the same user as<EMAIL_ADDRESS>11:30:11      ubuntu1604:     +# If not specified, the default local realm is the domain name,
11:30:11      ubuntu1604:     +# which defaults to the host's DNS domain name,
11:30:11      ubuntu1604:     +# translated to upper-case.
11:30:11      ubuntu1604:     +# Note that if this value is specified, the local realm name
11:30:11      ubuntu1604:     +# must be included in the list!
11:30:11      ubuntu1604:     +#Local-Realms =
11:30:11      ubuntu1604:     +
11:30:11      ubuntu1604:      [Mapping]
11:30:11      ubuntu1604:
11:30:11      ubuntu1604:      Nobody-User = nobody
11:30:11      ubuntu1604:      Nobody-Group = nogroup
11:30:11      ubuntu1604:     +
11:30:11      ubuntu1604:     +[Translation]
11:30:11      ubuntu1604:     +
11:30:11      ubuntu1604:     +# Translation Method is an comma-separated, ordered list of
11:30:11      ubuntu1604:     +# translation methods that can be used.  Distributed methods
11:30:11      ubuntu1604:     +# include "nsswitch", "umich_ldap", and "static".  Each method
11:30:11      ubuntu1604:     +# is a dynamically loadable plugin library.
11:30:11      ubuntu1604:     +# New methods may be defined and inserted in the list.
11:30:11      ubuntu1604:     +# The default is "nsswitch".
11:30:11      ubuntu1604:     +Method = nsswitch
11:30:11      ubuntu1604:     +
11:30:11      ubuntu1604:   * service[idmap] action restart
11:30:11      ubuntu1604:
11:30:11      ubuntu1604:     ================================================================================
11:30:11      ubuntu1604:     Error executing action `restart` on resource 'service[idmap]'
11:30:11      ubuntu1604:     ================================================================================
11:30:11      ubuntu1604:
11:30:11      ubuntu1604:     Mixlib::ShellOut::ShellCommandFailed
11:30:11      ubuntu1604:     ------------------------------------
11:30:11      ubuntu1604:     Expected process to exit with [0], but received '5'
11:30:11      ubuntu1604:     ---- Begin output of /bin/systemctl --system restart nfs-idmapd ----
11:30:11      ubuntu1604:     STDOUT:
11:30:11      ubuntu1604:     STDERR: Failed to restart nfs-idmapd.service: Unit nfs-server.service not found.
11:30:11      ubuntu1604:     ---- End output of /bin/systemctl --system restart nfs-idmapd ----
11:30:11      ubuntu1604:     Ran /bin/systemctl --system restart nfs-idmapd returned 5
11:30:11      ubuntu1604:
11:30:11      ubuntu1604:     Resource Declaration:
11:30:12      ubuntu1604:     ---------------------
11:30:12      ubuntu1604:     # In /tmp/packer-chef-solo/local-mode-cache/cache/cookbooks/nfs/recipes/_idmap.rb
11:30:12      ubuntu1604:
11:30:12      ubuntu1604:      29: service 'idmap' do
11:30:12      ubuntu1604:      30:   service_name node['nfs']['service']['idmap']
11:30:12      ubuntu1604:      31:   action [:start, :enable]
11:30:12      ubuntu1604:      32:   supports status: true
11:30:12      ubuntu1604:      33: end
11:30:12      ubuntu1604:
11:30:12      ubuntu1604:     Compiled Resource:
11:30:12      ubuntu1604:     ------------------
11:30:12      ubuntu1604:     # Declared in /tmp/packer-chef-solo/local-mode-cache/cache/cookbooks/nfs/recipes/_idmap.rb:29:in `from_file'
11:30:12      ubuntu1604:
11:30:12      ubuntu1604:     service("idmap") do
11:30:12      ubuntu1604:       action [:start, :enable]
11:30:12      ubuntu1604:       default_guard_interpreter :default
11:30:12      ubuntu1604:       service_name "nfs-idmapd"
11:30:12      ubuntu1604:       enabled nil
11:30:12      ubuntu1604:       running nil
11:30:12      ubuntu1604:       masked nil
11:30:12      ubuntu1604:       pattern "idmap"
11:30:12      ubuntu1604:       declared_type :service
11:30:12      ubuntu1604:       cookbook_name "nfs"
11:30:12      ubuntu1604:       recipe_name "_idmap"
11:30:12      ubuntu1604:       supports {:status=>true}
11:30:12      ubuntu1604:     end
11:30:12      ubuntu1604:
11:30:12      ubuntu1604:     System Info:
11:30:12      ubuntu1604:     ------------
11:30:12      ubuntu1604:     chef_version=14.2.0
11:30:12      ubuntu1604:     platform=ubuntu
11:30:12      ubuntu1604:     platform_version=16.04
11:30:12      ubuntu1604:     ruby=ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
11:30:12      ubuntu1604:     program_name=/usr/bin/chef-client
11:30:12      ubuntu1604:     executable=/opt/chef/bin/chef-client

Same recipe works in ubuntu1404
11:29:18      ubuntu1404: Recipe: nfs::_common
11:29:20      ubuntu1404:   * apt_package[nfs-common] action install
11:29:20      ubuntu1404:     - install version 1:1.2.8-6ubuntu1.2 of package nfs-common
11:29:20      ubuntu1404:   * apt_package[rpcbind] action install (up to date)
11:29:20      ubuntu1404:   * directory[/etc/default] action create (skipped due to only_if)
11:29:20      ubuntu1404:   * template[/etc/default/nfs-common] action create
11:29:20      ubuntu1404:     - update content in file /etc/default/nfs-common from 887a49 to 105a1f
11:29:20      ubuntu1404:     --- /etc/default/nfs-common	2012-10-10 16:15:43.000000000 +0000
11:29:20      ubuntu1404:     +++ /etc/default/.chef-nfs-common20190905-1254-4yp9uq	2019-09-05 09:29:20.027838000 +0000
11:29:20      ubuntu1404:     @@ -1,17 +1,3 @@
11:29:20      ubuntu1404:     -# If you do not set values for the NEED_ options, they will be attempted
11:29:20      ubuntu1404:     -# autodetected; this should be sufficient for most people. Valid alternatives
11:29:20      ubuntu1404:     -# for the NEED_ options are "yes" and "no".
11:29:20      ubuntu1404:     -
11:29:20      ubuntu1404:     -# Do you want to start the statd daemon? It is not needed for NFSv4.
11:29:20      ubuntu1404:     -NEED_STATD=
11:29:20      ubuntu1404:     -
11:29:20      ubuntu1404:     -# Options for rpc.statd.
11:29:20      ubuntu1404:     -#   Should rpc.statd listen on a specific port? This is especially useful
11:29:20      ubuntu1404:     -#   when you have a port-based firewall. To use a fixed port, set this
11:29:20      ubuntu1404:     -#   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
11:29:20      ubuntu1404:     -#   For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
11:29:20      ubuntu1404:     -STATDOPTS=
11:29:20      ubuntu1404:     -
11:29:20      ubuntu1404:     -# Do you want to start the gssd daemon? It is required for Kerberos mounts.
11:29:20      ubuntu1404:     -NEED_GSSD=
11:29:20      ubuntu1404:     +# Generated by Chef for ip-172-30-2-21.ec2.internal# Local modifications will be overwritten.
11:29:20      ubuntu1404:     +STATDOPTS="--port 32765 --outgoing-port 32766"
11:29:21      ubuntu1404:   * service[portmap] action restart
11:29:21      ubuntu1404:     - restart service service[portmap]
11:29:22      ubuntu1404:   * service[lock] action restart
11:29:22      ubuntu1404:     - restart service service[lock]
11:29:22      ubuntu1404:   * template[/etc/modprobe.d/lockd.conf] action create
11:29:22      ubuntu1404:     - create new file /etc/modprobe.d/lockd.conf
11:29:22      ubuntu1404:     - update content in file /etc/modprobe.d/lockd.conf from none to dda0ca
11:29:22      ubuntu1404:     --- /etc/modprobe.d/lockd.conf	2019-09-05 09:29:22.164906059 +0000
11:29:22      ubuntu1404:     +++ /etc/modprobe.d/.chef-lockd20190905-1254-1c2s5z1.conf	2019-09-05 09:29:22.160904095 +0000
11:29:22      ubuntu1404:     @@ -1 +1,4 @@
11:29:22      ubuntu1404:     +# Generated by Chef for ip-172-30-2-21.ec2.internal
11:29:22      ubuntu1404:     +# Local modifications will be overwritten.
11:29:22      ubuntu1404:     +options lockd nlm_udpport=32768 nlm_tcpport=32768
11:29:22      ubuntu1404:     - change mode from '' to '0644'
11:29:23      ubuntu1404:   * service[portmap] action restart
11:29:23      ubuntu1404:     - restart service service[portmap]
11:29:24      ubuntu1404:   * service[lock] action restart
11:29:24      ubuntu1404:     - restart service service[lock]
11:29:24      ubuntu1404:   * service[portmap] action start (up to date)
11:29:24      ubuntu1404:   * service[portmap] action enable (up to date)
11:29:24      ubuntu1404:   * service[lock] action start (up to date)
11:29:24      ubuntu1404:   * service[lock] action enable (up to date)
11:29:24      ubuntu1404: Recipe: nfs::_idmap
11:29:24      ubuntu1404:   * template[/etc/idmapd.conf] action create
11:29:24      ubuntu1404:     - update content in file /etc/idmapd.conf from 44726c to ca812b
11:29:24      ubuntu1404:     --- /etc/idmapd.conf	2012-10-10 16:15:43.000000000 +0000
11:29:24      ubuntu1404:     +++ /etc/.chef-idmapd20190905-1254-18pee69.conf	2019-09-05 09:29:24.349998000 +0000
11:29:24      ubuntu1404:     @@ -2,11 +2,35 @@
11:29:24      ubuntu1404:
11:29:24      ubuntu1404:      Verbosity = 0
11:29:24      ubuntu1404:      Pipefs-Directory = /run/rpc_pipefs
11:29:24      ubuntu1404:     -# set your own domain here, if id differs from FQDN minus hostname
11:29:24      ubuntu1404:     -# Domain = localdomain
11:29:24      ubuntu1404:
11:29:24      ubuntu1404:     +# The following should be set to the local NFSv4 domain name
11:29:24      ubuntu1404:     +# The default is the host's DNS domain name.
11:29:24      ubuntu1404:     +Domain = ec2.internal
11:29:24      ubuntu1404:     +
11:29:24      ubuntu1404:     +# The following is a comma-separated list of Kerberos realm
11:29:24      ubuntu1404:     +# names that should be considered to be equivalent to the
11:29:24      ubuntu1404:     +# local realm, such that<EMAIL_ADDRESS>can be assumed to
11:29:24      ubuntu1404:     +# be the same user as<EMAIL_ADDRESS>11:29:24      ubuntu1404:     +# If not specified, the default local realm is the domain name,
11:29:24      ubuntu1404:     +# which defaults to the host's DNS domain name,
11:29:24      ubuntu1404:     +# translated to upper-case.
11:29:24      ubuntu1404:     +# Note that if this value is specified, the local realm name
11:29:24      ubuntu1404:     +# must be included in the list!
11:29:24      ubuntu1404:     +#Local-Realms =
11:29:24      ubuntu1404:     +
11:29:24      ubuntu1404:      [Mapping]
11:29:24      ubuntu1404:
11:29:24      ubuntu1404:      Nobody-User = nobody
11:29:24      ubuntu1404:      Nobody-Group = nogroup
11:29:24      ubuntu1404:     +
11:29:24      ubuntu1404:     +[Translation]
11:29:24      ubuntu1404:     +
11:29:24      ubuntu1404:     +# Translation Method is an comma-separated, ordered list of
11:29:24      ubuntu1404:     +# translation methods that can be used.  Distributed methods
11:29:24      ubuntu1404:     +# include "nsswitch", "umich_ldap", and "static".  Each method
11:29:24      ubuntu1404:     +# is a dynamically loadable plugin library.
11:29:24      ubuntu1404:     +# New methods may be defined and inserted in the list.
11:29:24      ubuntu1404:     +# The default is "nsswitch".
11:29:24      ubuntu1404:     +Method = nsswitch
11:29:24      ubuntu1404:     +
11:29:25      ubuntu1404:   * service[idmap] action restart
11:29:25      ubuntu1404:     - restart service service[idmap]
11:29:25      ubuntu1404:   * service[idmap] action start (up to date)
11:29:25      ubuntu1404:   * service[idmap] action enable (up to date)
11:29:25      ubuntu1404: Recipe: nfs::server
11:29:27      ubuntu1404:   * apt_package[nfs-kernel-server] action install
11:29:27      ubuntu1404:     - install version 1:1.2.8-6ubuntu1.2 of package nfs-kernel-server
11:29:27      ubuntu1404:   * template[/etc/default/nfs-kernel-server] action create
11:29:27      ubuntu1404:     - update content in file /etc/default/nfs-kernel-server from a0dc37 to ecf3ce
11:29:27      ubuntu1404:     --- /etc/default/nfs-kernel-server	2014-02-25 16:43:39.000000000 +0000
11:29:27      ubuntu1404:     +++ /etc/default/.chef-nfs-kernel-server20190905-1254-ohpz9a	2019-09-05 09:29:26.871258000 +0000
11:29:27      ubuntu1404:     @@ -1,23 +1,5 @@
11:29:27      ubuntu1404:     -# Number of servers to start up
11:29:27      ubuntu1404:     -RPCNFSDCOUNT=8
11:29:27      ubuntu1404:     -
11:29:27      ubuntu1404:     -# Runtime priority of server (see nice(1))
11:29:27      ubuntu1404:     -RPCNFSDPRIORITY=0
11:29:27      ubuntu1404:     -
11:29:27      ubuntu1404:     -# Options for rpc.mountd.
11:29:27      ubuntu1404:     -# If you have a port-based firewall, you might want to set up
11:29:27      ubuntu1404:     -# a fixed port here using the --port option. For more information,
11:29:27      ubuntu1404:     -# see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS
11:29:27      ubuntu1404:     -# To disable NFSv4 on the server, specify '--no-nfs-version 4' here
11:29:27      ubuntu1404:     -RPCMOUNTDOPTS="--manage-gids"
11:29:27      ubuntu1404:     -
11:29:27      ubuntu1404:     -# Do you want to start the svcgssd daemon? It is only required for Kerberos
11:29:27      ubuntu1404:     -# exports. Valid alternatives are "yes" and "no"; the default is "no".
11:29:27      ubuntu1404:     -NEED_SVCGSSD=""
11:29:27      ubuntu1404:     -
11:29:27      ubuntu1404:     -# Options for rpc.svcgssd.
11:29:27      ubuntu1404:     -RPCSVCGSSDOPTS=""
11:29:27      ubuntu1404:     -
11:29:27      ubuntu1404:     -# Options for rpc.nfsd.
11:29:27      ubuntu1404:     -RPCNFSDOPTS=""
11:29:27      ubuntu1404:     +# Generated by Chef for ip-172-30-2-21.ec2.internal# Local modifications will be overwritten.
11:29:27      ubuntu1404:     +# Rendered Debian/Ubuntu template variant
11:29:27      ubuntu1404:     +RPCMOUNTDOPTS="-p 32767"
11:29:27      ubuntu1404:     +RPCNFSDCOUNT="8"
11:29:27      ubuntu1404: Recipe: nfs::_sysctl
11:29:27      ubuntu1404:   * sysctl[fs.nfs.nlm_tcpport] action apply (skipped due to only_if)
11:29:27      ubuntu1404:   * sysctl[fs.nfs.nlm_udpport] action apply (skipped due to only_if)
11:29:27      ubuntu1404:   * service[rpcbind] action start (up to date)
11:29:27      ubuntu1404:   * service[rpcbind] action enable (up to date)
11:29:27      ubuntu1404: Recipe: nfs::server
11:29:27      ubuntu1404:   * service[nfs-kernel-server] action start
11:29:27      ubuntu1404:     - start service service[nfs-kernel-server]
11:29:27      ubuntu1404:   * service[nfs-kernel-server] action enable (up to date)

Hello, any update on this?
Issue is still present on 'nfs', '~> 5.0.0' in both Ubuntu 18 and Ubuntu 2004
include_recipe "nfs::server4"

Output is:
2022-09-22 07:39:15.030000	Stdout:   * apt_package[nfs-common] action install[2022-09-22T07:39:09+00:00] INFO: Processing apt_package[nfs-common] action install (nfs::_common line 22)
2022-09-22 07:39:15.030000	Stdout: [2022-09-22T07:39:14+00:00] INFO: apt_package[nfs-common] installed nfs-common at 1:1.3.4-2.1ubuntu5.5
2022-09-22 07:39:15.030000	Stdout:
2022-09-22 07:39:15.030000	Stdout:     - install version 1:1.3.4-2.1ubuntu5.5 of package nfs-common
2022-09-22 07:39:15.030000	Stdout:   * apt_package[rpcbind] action install[2022-09-22T07:39:14+00:00] INFO: Processing apt_package[rpcbind] action install (nfs::_common line 22)
2022-09-22 07:39:15.030000	Stdout:  (up to date)
2022-09-22 07:39:15.030000	Stdout:   * directory[/etc/default] action create[2022-09-22T07:39:15+00:00] INFO: Processing directory[/etc/default] action create (nfs::_common line 26)
2022-09-22 07:39:15.030000	Stdout:  (skipped due to only_if)
2022-09-22 07:39:15.030000	Stdout:   * template[/etc/default/nfs-common] action create[2022-09-22T07:39:15+00:00] INFO: Processing template[/etc/default/nfs-common] action create (nfs::_common line 36)
2022-09-22 07:39:15.030000	Stdout: [2022-09-22T07:39:15+00:00] INFO: template[/etc/default/nfs-common] backed up to /etc/chef/local-mode-cache/backup/etc/default/nfs-common.chef-20220922073915.027862
2022-09-22 07:39:15.030000	Stdout: [2022-09-22T07:39:15+00:00] INFO: template[/etc/default/nfs-common] updated file contents /etc/default/nfs-common
2022-09-22 07:39:15.030000	Stdout:
2022-09-22 07:39:15.030000	Stdout:     - update content in file /etc/default/nfs-common from 978a91 to 0e3769
2022-09-22 07:39:15.030000	Stdout:     --- /etc/default/nfs-common	2021-05-13 13:27:22.000000000 +0000
2022-09-22 07:39:15.030000	Stdout:     +++ /etc/default/.chef-nfs-common20220922-7963-ohsorx	2022-09-22 07:39:15.021003527 +0000
2022-09-22 07:39:15.030000	Stdout:     @@ -1,15 +1,3 @@
2022-09-22 07:39:15.030000	Stdout:     -# If you do not set values for the NEED_ options, they will be attempted
2022-09-22 07:39:15.030000	Stdout:     -# autodetected; this should be sufficient for most people. Valid alternatives
2022-09-22 07:39:15.030000	Stdout:     -# for the NEED_ options are "yes" and "no".
2022-09-22 07:39:15.030000	Stdout:     -
2022-09-22 07:39:15.030000	Stdout:     -
2022-09-22 07:39:15.030000	Stdout:     -# Options for rpc.statd.
2022-09-22 07:39:15.030000	Stdout:     -#   Should rpc.statd listen on a specific port? This is especially useful
2022-09-22 07:39:15.030000	Stdout:     -#   when you have a port-based firewall. To use a fixed port, set this
2022-09-22 07:39:15.030000	Stdout:     -#   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
2022-09-22 07:39:15.030000	Stdout:     -#   For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS
2022-09-22 07:39:15.030000	Stdout:     -STATDOPTS=
2022-09-22 07:39:15.030000	Stdout:     -
2022-09-22 07:39:15.030000	Stdout:     -# Do you want to start the gssd daemon? It is required for Kerberos mounts.
2022-09-22 07:39:15.845000	Stdout:     -NEED_GSSD=
2022-09-22 07:39:15.845000	Stdout:     +# Generated by Chef for ip-172-31-0-35.ec2.internal# Local modifications will be overwritten.
2022-09-22 07:39:15.845000	Stdout:     +STATDOPTS="--port 32765 --outgoing-port 32766"
2022-09-22 07:39:15.845000	Stdout:   * kernel_module[lockd] action install[2022-09-22T07:39:15+00:00] INFO: Processing kernel_module[lockd] action install (nfs::_common line 44)
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:     * file[/etc/modprobe.d/options_lockd.conf] action create[2022-09-22T07:39:15+00:00] INFO: Processing file[/etc/modprobe.d/options_lockd.conf] action create (/opt/cinc/embedded/lib/ruby/gems/3.0.0/gems/chef-17.2.29/lib/chef/resource/kernel_module.rb line 106)
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: file[/etc/modprobe.d/options_lockd.conf] created file /etc/modprobe.d/options_lockd.conf
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:       - create new file /etc/modprobe.d/options_lockd.conf[2022-09-22T07:39:15+00:00] INFO: file[/etc/modprobe.d/options_lockd.conf] updated file contents /etc/modprobe.d/options_lockd.conf
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:       - update content in file /etc/modprobe.d/options_lockd.conf from none to 747b48
2022-09-22 07:39:15.845000	Stdout:       --- /etc/modprobe.d/options_lockd.conf	2022-09-22 07:39:15.101003922 +0000
2022-09-22 07:39:15.845000	Stdout:       +++ /etc/modprobe.d/.chef-options_lockd20220922-7963-2womad.conf	2022-09-22 07:39:15.101003922 +0000
2022-09-22 07:39:15.845000	Stdout:       @@ -1 +1,2 @@
2022-09-22 07:39:15.845000	Stdout:       +options lockd nlm_udpport=32768 nlm_tcpport=32768
2022-09-22 07:39:15.845000	Stdout:     - load kernel module lockd
2022-09-22 07:39:15.845000	Stdout:     * directory[/etc/modules-load.d] action create[2022-09-22T07:39:15+00:00] INFO: Processing directory[/etc/modules-load.d] action create (/opt/cinc/embedded/lib/ruby/gems/3.0.0/gems/chef-17.2.29/lib/chef/resource/kernel_module.rb line 114)
2022-09-22 07:39:15.845000	Stdout:  (up to date)
2022-09-22 07:39:15.845000	Stdout:     * file[/etc/modules-load.d/lockd.conf] action create[2022-09-22T07:39:15+00:00] INFO: Processing file[/etc/modules-load.d/lockd.conf] action create (/opt/cinc/embedded/lib/ruby/gems/3.0.0/gems/chef-17.2.29/lib/chef/resource/kernel_module.rb line 118)
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: file[/etc/modules-load.d/lockd.conf] created file /etc/modules-load.d/lockd.conf
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:       - create new file /etc/modules-load.d/lockd.conf[2022-09-22T07:39:15+00:00] INFO: file[/etc/modules-load.d/lockd.conf] updated file contents /etc/modules-load.d/lockd.conf
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:       - update content in file /etc/modules-load.d/lockd.conf from none to 8bb64b
2022-09-22 07:39:15.845000	Stdout:       --- /etc/modules-load.d/lockd.conf	2022-09-22 07:39:15.461005698 +0000
2022-09-22 07:39:15.845000	Stdout:       +++ /etc/modules-load.d/.chef-lockd20220922-7963-qx23ae.conf	2022-09-22 07:39:15.461005698 +0000
2022-09-22 07:39:15.845000	Stdout:       @@ -1 +1,2 @@
2022-09-22 07:39:15.845000	Stdout:       +lockd
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: kernel_module[lockd] not queuing delayed action restart on service[portmap] (delayed), as it's already been queued
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: kernel_module[lockd] not queuing delayed action restart on service[statd] (delayed), as it's already been queued
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: kernel_module[lockd] not queuing delayed action restart on service[lock] (delayed), as it's already been queued
2022-09-22 07:39:15.845000	Stdout:   * execute[update initramfs] action nothing[2022-09-22T07:39:15+00:00] INFO: Processing execute[update initramfs] action nothing (/opt/cinc/embedded/lib/ruby/gems/3.0.0/gems/chef-17.2.29/lib/chef/dsl/declare_resource.rb line 233)
2022-09-22 07:39:15.845000	Stdout:  (skipped due to action :nothing)
2022-09-22 07:39:15.845000	Stdout:   * service[portmap] action start[2022-09-22T07:39:15+00:00] INFO: Processing service[portmap] action start (nfs::_common line 56)
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: service[portmap] started
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:     - start service service[portmap]
2022-09-22 07:39:15.845000	Stdout:   * service[portmap] action enable[2022-09-22T07:39:15+00:00] INFO: Processing service[portmap] action enable (nfs::_common line 56)
2022-09-22 07:39:15.845000	Stdout:  (up to date)
2022-09-22 07:39:15.845000	Stdout:   * service[statd] action start[2022-09-22T07:39:15+00:00] INFO: Processing service[statd] action start (nfs::_common line 56)
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: service[statd] started
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.845000	Stdout:     - start service service[statd]
2022-09-22 07:39:15.845000	Stdout:   * service[statd] action enable[2022-09-22T07:39:15+00:00] INFO: Processing service[statd] action enable (nfs::_common line 56)
2022-09-22 07:39:15.845000	Stdout: [2022-09-22T07:39:15+00:00] INFO: service[statd] enabled
2022-09-22 07:39:15.845000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     - enable service service[statd]
2022-09-22 07:39:15.846000	Stdout:   * service[lock] action start[2022-09-22T07:39:15+00:00] INFO: Processing service[lock] action start (nfs::_common line 56)
2022-09-22 07:39:15.846000	Stdout:  (up to date)
2022-09-22 07:39:15.846000	Stdout:   * service[lock] action enable[2022-09-22T07:39:15+00:00] INFO: Processing service[lock] action enable (nfs::_common line 56)
2022-09-22 07:39:15.846000	Stdout:  (up to date)
2022-09-22 07:39:15.846000	Stdout: Recipe: nfs::_idmap
2022-09-22 07:39:15.846000	Stdout:   * template[/etc/idmapd.conf] action create[2022-09-22T07:39:15+00:00] INFO: Processing template[/etc/idmapd.conf] action create (nfs::_idmap line 23)
2022-09-22 07:39:15.846000	Stdout: [2022-09-22T07:39:15+00:00] INFO: template[/etc/idmapd.conf] backed up to /etc/chef/local-mode-cache/backup/etc/idmapd.conf.chef-20220922073915.802300
2022-09-22 07:39:15.846000	Stdout: [2022-09-22T07:39:15+00:00] INFO: template[/etc/idmapd.conf] updated file contents /etc/idmapd.conf
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     - update content in file /etc/idmapd.conf from b0488e to ca812b
2022-09-22 07:39:15.846000	Stdout:     --- /etc/idmapd.conf	2021-05-12 19:30:06.000000000 +0000
2022-09-22 07:39:15.846000	Stdout:     +++ /etc/.chef-idmapd20220922-7963-vpilc.conf	2022-09-22 07:39:15.797007355 +0000
2022-09-22 07:39:15.846000	Stdout:     @@ -2,11 +2,35 @@
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:      Verbosity = 0
2022-09-22 07:39:15.846000	Stdout:      Pipefs-Directory = /run/rpc_pipefs
2022-09-22 07:39:15.846000	Stdout:     -# set your own domain here, if it differs from FQDN minus hostname
2022-09-22 07:39:15.846000	Stdout:     -# Domain = localdomain
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     +# The following should be set to the local NFSv4 domain name
2022-09-22 07:39:15.846000	Stdout:     +# The default is the host's DNS domain name.
2022-09-22 07:39:15.846000	Stdout:     +Domain = ec2.internal
2022-09-22 07:39:15.846000	Stdout:     +
2022-09-22 07:39:15.846000	Stdout:     +# The following is a comma-separated list of Kerberos realm
2022-09-22 07:39:15.846000	Stdout:     +# names that should be considered to be equivalent to the
2022-09-22 07:39:15.846000	Stdout:     +# local realm, such that<EMAIL_ADDRESS>can be assumed to
2022-09-22 07:39:15.846000	Stdout:     +# be the same user as<EMAIL_ADDRESS>2022-09-22 07:39:15.846000	Stdout:     +# If not specified, the default local realm is the domain name,
2022-09-22 07:39:15.846000	Stdout:     +# which defaults to the host's DNS domain name,
2022-09-22 07:39:15.846000	Stdout:     +# translated to upper-case.
2022-09-22 07:39:15.846000	Stdout:     +# Note that if this value is specified, the local realm name
2022-09-22 07:39:15.846000	Stdout:     +# must be included in the list!
2022-09-22 07:39:15.846000	Stdout:     +#Local-Realms =
2022-09-22 07:39:15.846000	Stdout:     +
2022-09-22 07:39:15.846000	Stdout:      [Mapping]
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:      Nobody-User = nobody
2022-09-22 07:39:15.846000	Stdout:      Nobody-Group = nogroup
2022-09-22 07:39:15.846000	Stdout:     +
2022-09-22 07:39:15.846000	Stdout:     +[Translation]
2022-09-22 07:39:15.846000	Stdout:     +
2022-09-22 07:39:15.846000	Stdout:     +# Translation Method is an comma-separated, ordered list of
2022-09-22 07:39:15.846000	Stdout:     +# translation methods that can be used.  Distributed methods
2022-09-22 07:39:15.846000	Stdout:     +# include "nsswitch", "umich_ldap", and "static".  Each method
2022-09-22 07:39:15.846000	Stdout:     +# is a dynamically loadable plugin library.
2022-09-22 07:39:15.846000	Stdout:     +# New methods may be defined and inserted in the list.
2022-09-22 07:39:15.846000	Stdout:     +# The default is "nsswitch".
2022-09-22 07:39:15.846000	Stdout:     +Method = nsswitch
2022-09-22 07:39:15.846000	Stdout:     +
2022-09-22 07:39:15.846000	Stdout: [2022-09-22T07:39:15+00:00] INFO: template[/etc/idmapd.conf] sending restart action to service[idmap] (immediate)
2022-09-22 07:39:15.846000	Stdout:   * service[idmap] action restart[2022-09-22T07:39:15+00:00] INFO: Processing service[idmap] action restart (nfs::_idmap line 29)
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     ================================================================================
2022-09-22 07:39:15.846000	Stdout:     Error executing action `restart` on resource 'service[idmap]'
2022-09-22 07:39:15.846000	Stdout:     ================================================================================
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     Mixlib::ShellOut::ShellCommandFailed
2022-09-22 07:39:15.846000	Stdout:     ------------------------------------
2022-09-22 07:39:15.846000	Stdout:     Expected process to exit with [0], but received '5'
2022-09-22 07:39:15.846000	Stdout:     ---- Begin output of ["/bin/systemctl", "--system", "restart", "nfs-idmapd"] ----
2022-09-22 07:39:15.846000	Stdout:     STDOUT:
2022-09-22 07:39:15.846000	Stdout:     STDERR: Failed to restart nfs-idmapd.service: Unit nfs-server.service not found.
2022-09-22 07:39:15.846000	Stdout:     ---- End output of ["/bin/systemctl", "--system", "restart", "nfs-idmapd"] ----
2022-09-22 07:39:15.846000	Stdout:     Ran ["/bin/systemctl", "--system", "restart", "nfs-idmapd"] returned 5
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     Resource Declaration:
2022-09-22 07:39:15.846000	Stdout:     ---------------------
2022-09-22 07:39:15.846000	Stdout:     # In /etc/chef/local-mode-cache/cache/cookbooks/nfs/recipes/_idmap.rb
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:      29: service 'idmap' do
2022-09-22 07:39:15.846000	Stdout:      30:   service_name node['nfs']['service']['idmap']
2022-09-22 07:39:15.846000	Stdout:      31:   action [:start, :enable]
2022-09-22 07:39:15.846000	Stdout:      32:   supports status: true
2022-09-22 07:39:15.846000	Stdout:      33: end
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     Compiled Resource:
2022-09-22 07:39:15.846000	Stdout:     ------------------
2022-09-22 07:39:15.846000	Stdout:     # Declared in /etc/chef/local-mode-cache/cache/cookbooks/nfs/recipes/_idmap.rb:29:in `from_file'
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     service("idmap") do
2022-09-22 07:39:15.846000	Stdout:       action [:start, :enable]
2022-09-22 07:39:15.846000	Stdout:       default_guard_interpreter :default
2022-09-22 07:39:15.846000	Stdout:       declared_type :service
2022-09-22 07:39:15.846000	Stdout:       cookbook_name "nfs"
2022-09-22 07:39:15.846000	Stdout:       recipe_name "_idmap"
2022-09-22 07:39:15.846000	Stdout:       service_name "nfs-idmapd"
2022-09-22 07:39:15.846000	Stdout:       supports {:status=>true}
2022-09-22 07:39:15.846000	Stdout:     end
2022-09-22 07:39:15.846000	Stdout:
2022-09-22 07:39:15.846000	Stdout:     System Info:
2022-09-22 07:39:15.846000	Stdout:     ------------
2022-09-22 07:39:15.846000	Stdout:     chef_version=17.2.29
2022-09-22 07:39:15.846000	Stdout:     platform=ubuntu
2022-09-22 07:39:15.846000	Stdout:     platform_version=18.04
2022-09-22 07:39:15.846000	Stdout:     ruby=ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux]
2022-09-22 07:39:15.846000	Stdout:     program_name=/opt/cinc/bin/cinc-client
2022-09-22 07:39:15.846000	Stdout:     executable=/opt/cinc/bin/cinc-client


Bug: in mobile view after click on hamburger 4 option only icon is showing

What happened?
I think after click on hamburger icons on the 4 option profile show also come as text only icon showing

Add screenshots
No response
What browsers are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue

Hello @Sanchitbajaj02 please assign this issue to me under gssoc 24

Hello @Sanchitbajaj02 please assign this issue to me under gssoc 24

Hi @kapilG0 sorry to tell you but this issue is being addressed and PR is under review process. You can raise or solve another issue


Branchlist-behind-ahead-apicall

Solved undefined issues for getting data from useCalculateCommitDivergenceMutation
Used the index in branch list for getting the data of useCalculateCommitDivergenceMutation, instead of splitting props in BranchList components
Add default setting for the default branch in the first row of the branch list

Add default setting for the default branch in the first row of the branch list


[1pt] PR: nws_lid creation (Dev-nws-lid-creation)

This PR addresses #368
Creates the nws_lid layer with attributes that denote whether a site is a headwater and whether it is co-located (on the same nwm_feature_id) with another site.
This is created by retrieving all NWS_LID sites:

all sites attributed with rfc_forecast_point = True
all evaluated sites not included in (1)
all sites in HI/PR/VI

It then sorts through the WRDS metadata for all these sites and compiles the feature_id associated with the site as well as the most downstream feature_id immediately upstream of the ocean. This information is compiled into a dictionary.
Reads in the nwm_flows.gpkg layer used in FIM run to obtain the NWM river network. It then loops through all the sites based on the downstream feature_id to group sites that would flow into each other. For example, all sites associated with the Mississippi River would be selected at once. The network is then traversed and headwater sites are identified.
It then does a check to see if sites are co-located, based on having the same feature_id assignment.
It then creates a spatial GeoDataFrame of all nws_lid points and then the headwater/co-located attributes are joined.  The spatial data is then written out to file.
Additions

Creation of nws_lid geopackage layer with attributes denoting whether a site is a headwater site or is co-located with another site (at least referencing same nwm feature_id).

Testing
1.Example run is:
python3 foss_fim/tools/generate_nws_lid.py -w /path/to/workspace
Screenshots
nws_lid points are attributed with a "is_headwater" column that indicates whether it is a headwater lid location or not.
Headwater points are in black

Headwater points also denoted as co-located (assigned same nwm feature_id from WRDS)

Another example of Headwater points also co-located

@TrevorGrout-NOAA I can merge this in once it's approved. It looks like it has conflicts with the base branch, though.


brew tap version

Can you make this amazing application distributed to the brew network? I would really appreciate it!

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


Randomly allocate from the pool resources, not always from the front

This PR implements this #10
Not sure if I want to push this upstream yet. It is a little invasive and there is a performance hit to doing this and I don't want to add to the api to make this selectable.


Levels of project

1. Please describe why this term needs to be added
What this term is about? (briefly)
The Cloud Native Computing Foundation (CNCF) hosts a number of different projects, which are categorized into different levels based on their maturity and adoption.
The lowest level is sandbox projects
These projects are cool concepts that have real value to the cloud native ecosystem and they are able to come in cncf in an easy manner , easy proceedings, the committee looks at application all together there's a quick quote yay or nay and projects either in or not and those projects then gets this neutral ip zone within cncf have to collaborate attract more people to contribute and build the buzz to ultimately go up level .
Next project is incubating projects
These projects that are starting to demonstrate that they have adoption by end users  they are starting to demonstrate that more  than one  company is contributing to them .showing that they have good governance model , thinking about security of projects etc.
The top level that is graduated projects
These projects are most stress tested , most reliable , where users feel free to use this in their production system. These projects go through security audits regularly they have a guaranteed vendor neutral governance. They have a diverse community, they are mature Operations  kubernetes is obviously one of them . There are even others like fluently is other graduated project , envoy proxy is other one .
Why this term needs to be added? (briefly)

Describing the different levels of projects in the CNCF is important for a few reasons:
Helps users and adopters understand the maturity and stability of a project: By categorizing projects into different levels, the CNCF is providing a way for users and adopters to understand the maturity and stability of a project. A project that has graduated, for example, has demonstrated a high level of adoption, maturity, and stability, which can give users and adopters confidence in the project.
Provides a framework for project development and governance: The different levels provide a framework for project development and governance. Projects that are in the Sandbox level, for example, are typically in the early stages of development and may not yet have a fully formed community. Projects that are in the Graduated level, on the other hand, have proven their ability to operate at scale and have a sustainable community. This framework can help guide the development and governance of projects as they progress through the different levels.
Encourages participation in the CNCF community: By providing a path for projects to progress from the Sandbox level to the Graduated level, the CNCF is encouraging participation in its community. Developers and organizations can contribute to projects at any level, and by doing so, they can help these projects grow and mature. As projects progress through the different levels, they become more established and stable, which can make them more attractive to users and adopters.
Overall, describing the different levels of projects in the CNCF is important for providing users and adopters with a way to understand the maturity and stability of a project, for guiding project development and governance, and for encouraging participation in the CNCF community.
2. Checklist

[X] The suggested term fits the cloud native definition or is essential to understanding cloud native terms. (We hope to avoid adding general or broad terminologies)
[X] There is no existing issue yet. (shift+click to check existing issues)
[ ] The term has not already been declined in the past. (shift+click to check)
[X] The term does not already exist in the glossary.
[X] I understand that maintainers will assess if the term should be part of the Glossary. (Please be patient)
[X] I want to work on this term and confirm that I meet the criteria as outlined in "who can contribute". (If not checked, maintainers will assign another volunteer)

(Note)
Maintainers will assign a label after assessment procedure.
(from triage/awaiting to triage/accepted or triage/not accepted)
A contributor can be assigned to this issue after the issue get the triage/accepted label.
The assignee needs to check Style Guide.

Hi @NIKITA-M-VERMA
The term has not already been declined in the past. (shift+click to check)
is a mandatory checklist. So, you need to actually check duplication and check the box.
Levels of project is too general term and does not require additional definition as a term.
As a maintainer, let me change the triage to triage/not accepted
Thanks for the suggestion.


Can't run testing extensions in .net framework

For some reason, the runner fails with an exception stating that the implementation of IHttpClientFactory isn't implementing the Create method.

Wondering if it might have to do with different implementations of HttpClient; netstandard and net461.
Multi-target is hard... 0_0

This was a mix of the broken System.Net.Http package and a missing package (Microsoft.Owin.Host.HttpListener).
Fixed in 22c72fc2c7df7f34a77395361cc070c54a2fc708


Add Chung-Ang univ domain

https://www.cau.ac.kr/
Add Chung-Ang univ domain

@ByeonghwiJeong I am sorry, the domain cau.ac.kr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


PDF Download doesn't display content

Describe the bug
Downloading PDFs from SAS Content doesn't work correctly via the Explorer pane in the extension. The PDF will have no content, where as when downloading it directly from SAS Drive or SAS Studio the PDF is displayed correctly after download.
Steps to reproduce
Steps to reproduce the behavior:
Run the following SAS code (Change the USERNAME to your user name on the SAS Viya environment)
ods html close;  /* Not needed if using SAS Studio */

title "Create a Table of Contents";
options nodate;

filename outpdf filesrvc folderPath='/Users/USERNAME/My Folder' filename='test.pdf';

title "Create a Table of Contents";
options nodate;

ods pdf file=outpdf contents=yes bookmarklist=hide;

proc freq data=sashelp.cars;
   tables origin*type;
run;

proc print data=sashelp.cars;
run;

ods pdf close;    /* Not needed if using SAS Studio */
ods html;
```

- Then navigate to My Folder in the Explorer pane in SAS Studio
- Right click and select download from the context menu
- Open up the file and it won't display content
- Go to SAS Drive or SAS Studio and download it from there and it will display.

**Expected behavior**
Downloading the pdf file via VS Code should work in the same way as with directly from SAS Content.

**Screenshots**

**Environment (please complete the following information):**
Client OS: Windows 11
Extension version: v1.7.1]
SAS version: SAS Viya 2024.01

**Additional context**
Add any other context about the problem here.

Thanks @Criptic/@brunomueller for bringing this to our attention. This is resolved by https://github.com/sassoftware/vscode-sas-extension/pull/875 and should be released with 1.8.0


Use npm v7 with workspaces for local development and testing

This PR uses npm v7 (with its support of workspaces) for local development and testing. This should only affect local development, and not the generated output from create-react-app. So if I made changes that do affect the output, it is likely a mistake. 😄
Lerna
lerna is still being used for changelog generation and publishing. These two tasks could be replaced with individual tools/scripts, now that npm is responsible for installing and linking dependencies.

I was running into the same issue as #11306, so I included a similar commit (01f855771d67e193bbd2c1ddc01f685aa7e44950) in order to get tests passing further.

Could you elaborate on why this change is necessary? What is gained from this migration compared to what's already in place?

Also if you're using node 14 in a CI environment, you'll need to manually install npm 7 like I did here: https://github.com/facebook/create-react-app/pull/11304/files#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721R14-R15

@dan-kez Are you using npm@7? The workspaces support used by this repo is only available in npm 7. I added a note to the contributing docs about this, but a better check with a clearer error message would help in this case.

It looks like this was the issue. nicolo-ribaudo fixed this in https://github.com/babel/babel/pull/13724
Thanks for the prompt response and apologies for posting before digging into it further!

This PR uses npm v7 (with its support of workspaces) for local development and testing. This should only affect local development, and not the generated output from create-react-app. So if I made changes that do affect the output, it is likely a mistake. 😄
Lerna
lerna is still being used for changelog generation and publishing. These two tasks could be replaced with individual tools/scripts, now that npm is responsible for installing and linking dependencies.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!


Add QCOW 3 support

Adds support for latest version of qcow spec to vm parsing code. Confirmed a qcow3 disk fails parsing before patch and succeeds after. Does not add any additional parsing logic for new qcow3 features (compatibilty bits and such) which can be added at a later date.

:+1: @roliveri Please review

So, there's no need to change the way we read/decode the header between qcow 2 and 3?

No (as far as I can tell). Generated a qcow2 disk with some partitions, confirmed fleecing succeeded. Then converted it to qcow3 and confirmed fleecing failed. Then made the changes above and reran the fleece which ran successfully.
Again with this patch we're not extracting any off the additional fields qcow3 defines, such as the feature bitmasks and header extensions, but since qcow3 is backwards compatible w/ 2 this should suffice until those are needed.

My concern is that someday we'll encounter a qcow3 file with features we don't support, and it will fail in some non-obvious way - making it more difficult to debug. Are there ways to check for said incompatibilities now, avoiding non-obvious failures in the future?
For example: fail if any bits in incompatible_features are set.

Ya we should be able to extract the new info in the same manner as we are other header fields. New extended structures will need to be defined and populated, will look at expanding this going forward

Looking good @movitto.  Is this WIP?  Wasn't sure because I just really see the parsing, but don't see the code bailing on incompatible features, unless I'm missing something.

@Fryguy as far as full qcow3 support yes its a WIP though could be merged at any point as I've verified that it successfully parses the new data from a qcow 3 image. Will incorporate the feedback / continue to expand upon functionality w/ this PR though.

@Fryguy updated to incorporate style feedback and to fail on detecting unknown incompat bits. Also added support for qcow preallocated clusters (all 0's). Couldn't find reference to a 'bitSet?' helper so left those lines as is though can update if need be

@roliveri Please re-review

@Fryguy @roliveri rebased and updated

@movitto Nice job on getting QCOW3 support in.  PR is looking better with every iteration!

@Fryguy @roliveri any chance of a review?

It looks good to me.
@Fryguy if you have no other comments, I'll merge it.


chocolateyversion - bad parsing (to_s) for versioning

https://github.com/puppetlabs/puppetlabs-chocolatey/blob/3.0.0/lib/facter/chocolateyversion.rb
needs a to_s or something that would avoid:
chocolateyversion: !ruby/string:Puppet::Util::Execution::ProcessOutput 0.10.8
which is the output that is received via:
puppet facts --render-as yaml
puppet facts --render-as json
side note anything with facter -p (-y|-j) seems to work fine

@tek0011 Are you opening this in addition to one for puppetlabs/chocolatey?

oh.  nope, but i sure will now!  sorry, wrong project.

@ferventcoder Do you want that in puppetlabs issue tracker, you mean?  puppetlabs/chocolatey has no option to open issues.  I think thats why I lead myself here.

https://tickets.puppetlabs.com/browse/MODULES-5788


Saving with javascript ajax(fetch) doesn't work?

How do you save with javascript ajax?
I have noticed the textarea that this is set does not update, there's some eventlistener to send it or something (not sure how that works)
anyway my code I have to click the save button twice for it to actually POST the new data, the POST request it sends the first time does not have the new data, but the second time it does have the data. It is easyMDE that causes this.
All I want to do is be able to click a save button and not have it refresh the entire page to save, so whatever method there is to do that I will use.. as I said my current one works but I gotta click save 2 times. (no jquery please)
method="POST" onsubmit="event.preventDefault(); saveNotesForm(event,this);">
function saveNotesForm(e,form) { 	var formData = new FormData(form); 	fetch(form.action,{ 		method:'POST', 		body: formData, 	}); 	console.log('sent msg'); }

I also use fetch to save the data and I manually append the value of the of the editor to the form data like this: formData.append('content', mde.value());

Oh ok I did not know that is how you can get the form's value with easyMDE.value()
It looks like I can work with that pretty well, thank you


Prevent exception when legacy accounts have >50k contacts

I have several legacy accounts with huge numbers of contacts.  When users try to delete those contacts using CON_DeleteContactOverride, they get an exception in the form:

npsp:Too many query rows: 50001
Error is in expression '{!processDelete}' in component apex:page in page npsp:con_deletecontactoverride: (npsp)

This patch aggregates the results instead of querying the 50k+ contacts that will never be used.
It's likely that && contactsInHousehold[0].get('ct') == 1 is redundant.
Critical Changes
Fixes bug that can be duplicated as follows:
Reproduce

Create an Account
Create 60k contacts all in that account.
Click delete on one of those contacts.

Expected result:
Contact is deleted.
Actual result:

npsp:Too many query rows: 50001
Error is in expression '{!processDelete}' in component apex:page in page npsp:con_deletecontactoverride: (npsp)

Changes
Issues Closed
#2425: Cannot delete Contact in Account with >50k Contacts

@ckoppelman thanks for the pull request.  my understanding is that aggregate queries still count the number of rows they have to process over.  So even though your change is only returning one row, the fact that the underlying data has over 50k records will still be a problem.  I could be wrong, but that's my recollection.  Were you able to test your new query/code in your large org using either anonymous apex or the query editor in the dev console?

I have not yet deployed this to production (in process), but I ran it as anon Apex (well, technically, I ran the below) and was able to reproduce the error with a known mega-Account.  First I tried the simple GROUP BY which didn't help.  Adding the HAVING clause fixed it.
Separately (not addressed here), it might also be useful to ensure that the user may delete that Account on a permissions level.

@davidhabib Update - It is now deployed to production on my system and working just fine.

An even better solution is to only make that second SOQL query if queryContact.Account.npe01__SYSTEMIsIndividual__c.  That way you save a SOQL call.  I can modify my patch to do that if you'd like.

thanks for testing and verifying it solved the problem in your org.  yes,
if you could update your pull request that would be great.  I'll then make
sure we get it assigned for further review and testing in our next sprint
(which will start in Jan), so we can release it thereafter.  thanks.
David Habib | Lead Member of Technical Staff | salesforce.org
On Wed, Dec 21, 2016 at 1:31 PM, Charles Koppelman<EMAIL_ADDRESS>
wrote:

An even better solution is to only make that second SOQL query if
queryContact.Account.npe01__SYSTEMIsIndividual__c. That way you save a
SOQL call. I can modify my patch to do that if you'd like.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/pull/2426#issuecomment-268645653,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3bVyDxAkz4pS6YpHK9VioX9Zsybua1ks5rKZqngaJpZM4LTEAo
.

@davidhabib done. I look forward to deleting my patch.

I've cloned your pull request to a feature branch in our repository so it can run thru our build process.  I'll tag you on the new request.  thanks!


Should returns boolean when handling URL.

This allow us to inform the application accurately about whether we have handled the URL, rather than always returning YES regardless of the result.

Currently, there's no way I could forward the result of calling -[DPLDeepLinkRouter handleURL:withCompletion:] back to -[UIApplicationDelegate application:openURL:sourceApplication:annotation:] without synchronizing the block calls, or chaining the blocks call.
This is inconvenience in a number of ways:

It makes it hard to integrate with other APIs or Frameworks that need to handle URL as well. We will have to call this last in this case because we wouldn't know the result in the current run loop frame.
We will have to always return YES even if there's no route handler to handle the URL.

This looks good. Thanks @lxcid.

Hey @lxcid Thanks - great change!
Ahead of merging the PR can you sign our CLA?
https://docs.google.com/a/usebutton.com/forms/d/1WHFWnzz5OL8c9o49KgpgyERzQUQajX5p8_80YLCghds/viewform

Cool! Done. Thanks!


fix UPGMA algorithm

Merging clusters should be done by taking the weighted average using the cluster sizes as weights.
Original issue by @bmesuere on Sat Jun 14 2014 at 17:20.
Closed by @bmesuere on Sat Jun 14 2014 at 20:06.

The difference seems to be minimal. You can check by comparing the results from scruffy with the ones from unipept.ugent.be
Original comment by @bmesuere on Sat Jun 14 2014 at 20:12.

It is expected that the difference would be small, but it's better to use the correct implementation of the UPGMA algorithm, if we claim we use that algorithm
Original comment by @pdawyndt on Sun Jun 15 2014 at 10:52.


Adds built-in Selenium support for Javascript website scraping

Adds built-in Selenium support for Javascript website scraping.
No more "The website encountered an error and could not provide the requested data.", issue anymore while the bot is crawling sites like Quora.

Before:

After:

This is a great addition. However, I think it would be best if it takes advantage of the OnlineAgent's ability to receive a custom website reader rather than making it a parameter on the OnlineAgent.
Basically, the Selenium website reader you wrote should be a stand alone website reader in core.py that the user can import and use with the OnlineAgent.
Example use case with this new approach:
from llm_axe import selenium_reader
agent = OnlineAgent(llm, custom_site_reader=selenium_reader)

Let me know what your thoughts are. Thanks again!

Hello, I agree that making it a built-in reader function is a better option.
However, my original thoughts were only use selenium when JavaScript website is detected, if I made a custom selenium_reader and uses it every time, we will get significant longer response time.
Or maybe I have to make two functions,selenium_reader and selenium_and_soap_reader?
Let me know what you think, thanks!

Oh okay. I see what you are saying.
In that case, I think your suggestion of making two functions seems like the best approach. It gives more options to the user which is always great.
Maybe we can call the second one selenium_hybrid_reader?

Oh okay. I see what you are saying.
In that case, I think your suggestion of making two functions seems like the best approach. It gives more options to the user which is always great.
Maybe we can call the second one selenium_hybrid_reader?

That's probably a better name, Thanks👍


feat: Add pip_tmp_dir to allow setting the location of the pip temporary directory

…rectory
Signed-off-by: Aidan Jensen<EMAIL_ADDRESS>Description

Add the ability to set the location of the temporary directory for pip installs
Motivation and Context

When building in remote docker, you may need to set a shared location for the pip install directory
Breaking Changes

No it does not
How Has This Been Tested?

[X] I have tested and validated these changes using one or more of the provided examples/* projects

I added a test that uses a temp dir in the cwd, and watched that directory while it was used.

@antonbabenko any thoughts on this?

@pdecat Could you please review this one (especially the Python part)?

Hi, most changes relative to the addition of pip_tmp_dir look correct to me, left a few remarks.
However, I'm still wondering about a concrete need for that.
@artificial-aidan, you mention "Can be useful for Docker in Docker builds.". Can you expand a bit why? In your actual use case, do you specify a special path that can be cached or something?
Also, wouldn't setting TMPDIR, TEMP or TMP environment variable achieve the same?

When using a remote Docker container for docker builds, the tmp directory might not be mounted on the remote host. In my case there is a shared directory mounted between the caller and the remote docker container. By setting the temp dir to this, the docker builder can access the files created.
In theory those environment variables might work, (and would have saved me a lot of time probably) but now that I wrote it it seems like there could be a case where you didn't want all of the python temporary dirs to go to wherever you are setting your pip_temp_dir to be.

Just minor comments. Leave terraform-docs as the last step (I will fix).

Wrapped up the minor comments and fixed a merge conflict.

This PR is included in version 2.28.0 :tada:


Added preliminary support for Tez

This is preliminary version of tez support.. The following changes are required to have full support.
Here is the summary:
Done:
Added basic support for tez jobs. Added couple of heuristics to make sure they appear in the UI.Current implementation is just having the same code as MR heuristics.
To Be Done:
The main problem with Tez support is one Yarn application can have multiple dags (or jobs). The current implementation assumes that for each Yarn application, there is one MR job. So some design changes need to be done.
Some UI support as well to show multiple dags under one Yarn application.
We need to come up with some class structure for heuristics as some heuristics will be exactly same for Tez and MR . So class hierarchy will help us not to write redundant code.

Support sparksrteaming monitoring job?


[Explicit Module Builds] Do not add the .modulemap file to the build command arguments

As these files are already specified in the relevant dependency scanner JSON output field.

@swift-ci please test


Handle servers that give 500 errors better

If I do a GetCapabilities request on a server and it replies with http status 500, because something is fundamentally wrong with the server, then this PR means owslib will not raise an HTTP exception.
Previously this only occurred for 40x statuses.
I currently am trying to talk to this GeoNetwork CSW:
http://geonet.allerdale.gov.uk/geonetwork/srv/en/csw?version=2.0.2&request=GetCapabilities&service=CSW
which returns a 500 error and an HTML page, but no doubt they will fix it soon, otherwise I'd submit a doctest.
Without this PR we get some random exception trying to parse the HTML response:

from owslib.csw import CatalogueServiceWeb
c=CatalogueServiceWeb('http://geonet.allerdale.gov.uk/geonetwork/srv/en/csw')
Exception raised:
Traceback (most recent call last):
File "/usr/lib/python2.7/doctest.py", line 1289, in __run
compileflags, 1) in test.globs
File "<doctest csw_error.txt[1]>", line 1, in
c=CatalogueServiceWeb('http://geonet.allerdale.gov.uk/geonetwork/srv/en/csw')
File "owslib/csw.py", line 88, in init
self._invoke()
File "owslib/csw.py", line 668, in _invoke
self._exml = etree.parse(BytesIO(self.response))
File "lxml.etree.pyx", line 3198, in lxml.etree.parse (src/lxml/lxml.etree.c:65048)
File "parser.pxi", line 1588, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:93355)
File "parser.pxi", line 1617, in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:93649)
File "parser.pxi", line 1495, in lxml.etree._parseDoc (src/lxml/lxml.etree.c:92453)
File "parser.pxi", line 1011, in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:89097)
File "parser.pxi", line 577, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:84804)
File "parser.pxi", line 676, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:85904)
File "parser.pxi", line 616, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:85228)
XMLSyntaxError: Opening and ending tag mismatch: link line 7 and head, line 8, column 11

and with this PR we get a much nicer HTTPException that tells us the URL with all the params that we are trying (which I can tell the user so he/she can debug the server):
Exception raised:
Traceback (most recent call last):
File "/usr/lib/python2.7/doctest.py", line 1289, in __run
compileflags, 1) in test.globs
File "<doctest csw_error.txt[1]>", line 1, in
c=CatalogueServiceWeb('http://geonet.allerdale.gov.uk/geonetwork/srv/en/csw')
File "owslib/csw.py", line 88, in init
self._invoke()
File "owslib/csw.py", line 650, in _invoke
self.response = openURL(self.request, None, 'Get', username=self.username, password=self.password, timeout=self.timeout).read()
File "owslib/util.py", line 203, in openURL
req.raise_for_status()
File "/home/co/ckan/local/lib/python2.7/site-packages/requests/models.py", line 851, in raise_for_status
raise HTTPError(http_error_msg, response=self)
HTTPError: 500 Server Error: Internal Server Error
I included the 50x codes that I felt are pretty certain to be "server not happy", and missed off "501 Not Implemented" which sort of implied the request was not supported now but may be in the future, but the server did know what it was doing. Anyway, I'm open to changing this list to all the 5xx ones if preferred.

Thanks @davidread!


fix translation errors

Thanks for taking the time to contribute this localization pull request. However, we are not able to accept contributions to this historical reference repository at this time.


Create hSECURITY.md

honestly, I think this PR is not from a person. There is no ticket description whatsoever. So I'm going to close this. If this is really a serious attempt, file a proper PR with description and reasoning


[5.4] Fixed broken dependency between sf/debug and sf/console

Due to this commit in symfony/console, pointing at symfony/debug:3.2.* is not compatible with symfony/console:3.2.*.
This fixes the compatibility. Will probably have to revert once sf straightens their deps.

Looks like a mistake in symfony.

Nobody should be using Laravel 5.4 at this time.

@GrahamCampbell so we wait?
I had to do this manually at master to be able to composer install the framework... others may hesitate to do so.

This is definitely a mistake in Symfony.

I had to do this manually at master to be able to composer install the framework... others may hesitate to do so.

No way that should ever be required in order to use laravel.

I've sent a PR to symfony: https://github.com/symfony/symfony/pull/19932.

Awesome! That was probably the most sensitive way to go.


[CAP 35] Update documentation

Update documentation at https://github.com/stellar/new-docs

Add new operations
Add new effects
Add new operation details for pre-existing operations (if needed)
Add new Account flag (if needed)
Add new Trustline flag (if needed)
Add new Claimable Balance flag (if needed)

Also covered by stellar/new-docs#355. There's value in keeping it here for tracking purposes, but are there more docs requirements within the monorepo itself (docstrings, etc.)?

I believe this was closed when stellar/new-docs#355 closed.


Disable codecov comments on PRs, they are very verbose

Codecov Report

Merging #31 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   74.18%   74.18%
=======================================
  Files           8        8
  Lines        1623     1623
=======================================
  Hits         1204     1204
  Misses        419      419

Continue to review full report at Codecov.

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

Hey @raphlinus have you seen this and the other open PR? :)


What's the difference between 'chi_sim.traineddata' and 'chi_sim_vert.traineddata'?

In tesseract-ocr/tessdata_best folder,there are two models related to Simplified Chinese, called 'chi_sim.traineddata' and 'chi_sim_vert.traineddata'.
I wonder what's the difference between them, thanks!

Please see
https://github.com/tesseract-ocr/tessdata_fast/blob/master/README.md
Read the last section re jpn_vert
Same applies for chi_sim_vert
On Mon 5 Mar, 2018, 12:03 PM None<EMAIL_ADDRESS>wrote:

In tesseract-ocr/tessdata_best folder,there are two models related to
Simplified Chinese, called 'chi_sim.traineddata' and
'chi_sim_vert.traineddata'.
I wonder what's the difference between them, thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tessdata_best/issues/20, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AE2_o7XLdHPNb8uDrZb2iONGjC_jfgQFks5tbNwigaJpZM4Sbylb
.

Thank you for your answer!
I'll close this issue.


move registry refresh out of the observer loop

This resolves the $O(n^2)$ problem in the observer and vastly boosts the initialization performance.
I have noticed no drawbacks yet.

Thanks @wfjsw :)


Why Not Use Lora Config modules_to_save?

In the docs modules_to_save is defined as:
modules_to_save: List of modules apart from LoRA layers to be set as trainable and saved in the final checkpoint. These typically include model’s custom head that is randomly initialized for the fine-tuning task.
https://huggingface.co/docs/peft/conceptual_guides/lora
If I am understanding right, according to your work, for llama 2 the modules should be:
modules_to_save = ["embed_tokens","input_layernorm","post_attention_layernorm","norm"]
When adding a new token, such as a padding token(which you do) we should also save "lm_head" right?
This will then save the weights in the adapter.bin file.
I do not see how you are saving both adapter.bin and the trainable_params.bin with the current code.  I would think only adapter.bin would be saved.
Thanks!

I do not get a pytorch_model.bin file when I finetune.  That is probably because have taken your work(full finetuning of some modules, custom flast attention forward) and used it with a trl-based finetuning solution, so I guess it's my own fault.
Regardless, assuming that I understand what modules_to_save does, the adapter.bin I am getting should have the same updates that your solution does.
Could you please confirm that the modules to save would be the following without adding tokens:
"embed_tokens","input_layernorm","post_attention_layernorm","norm"
and with adding new tokens:
"embed_tokens","input_layernorm","post_attention_layernorm","norm", "lm_head"
Thanks so much for your research!

Hi,
To get pytorch_model.bin, you need to run python3 zero_to_fp32.py . pytorch_model.bin in the checkpoint directory.
Yes. These are the learnable parameters, and the lora weights.
Regards,
Yukang Chen

Thanks!


Toggle able from the calendar view

It would be nice to be able to toggle the calendars on and off from the calendar view, and toggle which calendars can be toggled from the events settings.
(Thanks for this plugin! It was exactly what I was looking for!)

Possible duplicate of https://github.com/davish/obsidian-full-calendar/issues/86

This is in fact a duplicate. Thanks for flagging @0-ft!


Remove dyes from trading with the wandering trader

When playing with the acacia tree, the wondering trader becomes essential to obtain oak saplings and other important natural items. The problem is that the wondering trader takes more than 5 hours to generate and has only 6 trades, from which random items are selected, including 16 different types of dyes. This high number of dyes ends up taking up space for possible important items, while having no use for the player, since they can be obtained in other ways.
If you're unlucky, for example, you'll have to spend weeks afk with your computer on. This makes the Skyblock experience exhausting. I suggest removing the Wondering Trader dyes so that it speeds up the process of obtaining natural items

While I think this would be a neat optional datapack, I don't believe this should be in the default datapack. I believe that the main version should make the least amount of changes to the game possible, just enough to make everything obtainable and renewable.


Add GDI as supported file extension for conversion

chdman supports the conversion of GDI files, a format used by Sega Dreamcast emulators.  Adding it to the list of supported ISO file extensions is enough to enable conversion of GDI files to CHD.

Thanks for the note. I noticed this too a few hours back (script isn't that old anyway) and even used chdman in the past to convert GDI files I think. Not sure how this slipped through and I will add it.

Yes, I think GDIs (and probably CUEs as well) should take priority over any ISO files since I think there are games in GDI format out there that have tracks that use the .iso file extension instead of .bin.

Actually, here's an example of a GDI file with some of the tracks using the .iso file extension: https://hiddenpalace.org/Hydro_Thunder_(Jun_16,_1999_prototype)


Update Flow to 0.33

Current coverage is 87.92% (diff: 100%)

Merging #2692 into master will increase coverage by <.01%

@@             master      #2692   diff @@
==========================================
  Files           243        243
  Lines         18226      18226
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          16024      16025     +1
+ Misses         1939       1938     -1
  Partials        263        263

Diff Coverage
File Path

•••••••••• 100%
js/noms/src/put-cache.js

Powered by Codecov. Last update c9c1bb9...eef3652


add RPM module (Closes #49)

It's basic implementation of things which I described in #49

@jpakkane what do you think?

Looks pretty nice. There are few niggles, though.

the spec file is generated into the dir where Meson was invoked from, it should go in the build directory
the function generate_spec should be called generate_spec_template to make it clear it may need hand editing
some projects have a directory called build already, it should be something more unique such as rpmbuilddir
presumably RPM passes the compiler flags to use with CFLAGS et al? If yes, then the Meson command should have --buildtype=plain, if no it should have --buildtype=debugoptimized
trunk changed in the mean time to get a subdirectory 4, change the number in this one to 5
this spec file does not run tests, it should call 'ninja-build test' at some point

[X] the spec file is generated into the dir where Meson was invoked from, it should go in the build directory
[X] the function generate_spec should be called generate_spec_template to make it clear it may need hand editing

[X] some projects have a directory called build already, it should be something more unique such as rpmbuilddir
[X] presumably RPM passes the compiler flags to use with CFLAGS et al? If yes, then the Meson command should have --buildtype=plain, if no it should have --buildtype=debugoptimized
[] trunk changed in the mean time to get a subdirectory 4, change the number in this one to 5
don't understand this.
[X] this spec file does not run tests, it should call 'ninja-build test' at some point

trunk changed in the mean time to get a subdirectory 4, change the number in this one to 5
don't understand this.

@jpakkane I've also added support for auto-generating build requires for non-default compilers (fortran, vala, objc, objc++)

What I meant is that you should rename your directory from "4 rpm" to "5 rpm".

@jpakkane done

Thanks for fixing. One last question. What is the configure file you generate for? If it is needed by the rpm machinery please print a comment in the resulting rpm template explaining why it needs to be there.

@jpakkane, it's because only way to apply ALL compiler/linker flags (CFLAGS, CXXFLAGS, FFLAGS, FCFLAGS, LDFLAGS) is using %configure macros from RPM.
On my system it is:
$ rpm --eval %configure

  CFLAGS="${CFLAGS:--O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic}" ; export CFLAGS ;
  CXXFLAGS="${CXXFLAGS:--O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic}" ; export CXXFLAGS ;
  FFLAGS="${FFLAGS:--O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -I/usr/lib64/gfortran/modules}" ; export FFLAGS ;
  FCFLAGS="${FCFLAGS:--O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -I/usr/lib64/gfortran/modules}" ; export FCFLAGS ;
  LDFLAGS="${LDFLAGS:--Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld}"; export LDFLAGS;
  [ "1" = 1 ] && for i in $(find . -name config.guess -o -name config.sub) ; do
      [ -f /usr/lib/rpm/redhat/$(basename $i) ] && /usr/bin/rm -f $i && /usr/bin/cp -fv /usr/lib/rpm/redhat/$(basename $i) $i ;
  done ;
  [ "1" = 1 ] && [ x != "x-specs=/usr/lib/rpm/redhat/redhat-hardened-ld" ] &&
      for i in $(find . -name ltmain.sh) ; do
        /usr/bin/sed -i.backup -e 's~compiler_flags=$~compiler_flags="-specs=/usr/lib/rpm/redhat/redhat-hardened-ld"~' $i
      done ;
  ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu \
	--program-prefix= \
	--disable-dependency-tracking \
	--prefix=/usr \
	--exec-prefix=/usr \
	--bindir=/usr/bin \
	--sbindir=/usr/sbin \
	--sysconfdir=/etc \
	--datadir=/usr/share \
	--includedir=/usr/include \
	--libdir=/usr/lib64 \
	--libexecdir=/usr/libexec \
	--localstatedir=/var \
	--sharedstatedir=/var/lib \
	--mandir=/usr/share/man \
	--infodir=/usr/share/info

and if we want to use proper flags we need to execute that macros, but it's executing ./configure and in our case we should use blank executable file (for example, one package in Fedora: http://pkgs.fedoraproject.org/cgit/gmqcc.git/tree/gmqcc.spec#n37)

@jpakkane now I think it's ready for merge.

I looked through RPM docs and it seems that the flags in question will be set in the RPM_OPT_FLAGS environment variable. We should also set the install prefix when configuring Meson (default is /usr/local, which is wrong for package bulding).
Combining these two, it would seem that the way to do this is to not have the configure bits but instead set up Meson with this:
CFLAGS="${RPM_OPT_FLAGS}" meson .. --prefix=%{_prefix} --buildtype=plain

Does this seem correct to you?

That still leaves out global ldflags. And the documentation I can found does not say where RPM sets those up...

This is weird. On my fedora test machine, rpm --eval %configure or %cmake does not set ldflags at all. However if it did, then the (hopefully final) correct stanza would be this:
CPPFLAGS="%{__global_cflags}" LDFLAGS="%{__global_ldflags}" meson .. --prefix=%{prefix} --buildtype=plain

@jpakkane done.

@jpakkane done with properly solution from RPM side (added %meson macros. See #55)
Any issues?

@jpakkane Probably there should be a bit more better thing to detect install or not-install RPM macros, but I don't know. If no other issues - please merge with commit with fix of choosing install or not install rpm macros.

Looks fine. Let's get this in now.


Docs explain multiple invocations of callback passed to Mina.transaction

Should this be moved to the docs repo? Could we clarify the title--not sure what's it's requesting.


[2021-12-06] drop support of php7.3

on 2021-12-06 the support for php7.3 ended. see https://www.php.net/supported-versions.php
lets take this for a change to switch the min-version of this lib to 7.4 .
see https://www.php.net/manual/en/migration74.new-features.php
so to use the new language features, a breaking change will happen:

[x] drop php7.3 from CI
[x] drop php7.3 from composer manifest (php: ^7.4)
[x] migrate to php74 via php-cs-fixer
[x] make class properties type-save
[x] bump ergebnis/composer-normalize to a later version that does not need php7.3 - #46
[x] review the proposals below

PROPOSAL: remove getters and setters, if a property can be made type safe and converted to public.
PRO

less methods to maintain

CON

no setters = cannot use chained setters ala $instance->setA(1)->setB(2);

code changes
from
class C {
  /** @var bool */
  private $prop = true;

  /** @return $this */
  public function setProp(bool $prop): self
  {
     $this->prop = $prop;
     return $this;
  }
}

to
class C {
  public bool $prop = true;
}

proposed change to remove getters/setters was dropped.
removing setters wouod remove the feature to of chaining, which comes in handy in downstream implementations.
removing the getter might be appealing, but can be re-thought later.


When using a web camera to track my eyes, I can't always get the gaze vector, why?

Nice job! But I met a few problems when running your eye-tracker.
I used a web camera (WIN2 USB2.0 PC Camera) to test the eye tracker. However, the result showed that I can't always obtain the gaze (normal) vector of my eye ball. Is there any solutions for this? I want the gaze vector could be obtained stably.
Should I change another camera or update the camera calibration information in the "cameraintrinsics_eye.txt" file? Or I have to keep the positions of the camera and my head in a more stable status?
Another problem is that is there any paper or document that describe your eye tracking algorithm？ because I'd like to learn more details about your work.
Many thanks!

Hi Crissallan,
Our algorithm is designed to work with near-eye infrared cameras, so it may not work with standard webcameras. The initial implementation of the tracker is described in the following publication:
Itoh, Y., & Klinker, G. (2014, March). Interaction-free calibration for optical see-through head-mounted displays based on 3d eye localization. In 2014 IEEE symposium on 3d user interfaces (3dui) (pp. 75-82). IEEE.
Unfortunately the updated drift correction model is not yet published, but the above publication should get you started.
Best,
Jason

Hi Crissallan,
Our algorithm is designed to work with near-eye infrared cameras, so it may not work with standard webcameras. The initial implementation of the tracker is described in the following publication:
Itoh, Y., & Klinker, G. (2014, March). Interaction-free calibration for optical see-through head-mounted displays based on 3d eye localization. In 2014 IEEE symposium on 3d user interfaces (3dui) (pp. 75-82). IEEE.
Unfortunately the updated drift correction model is not yet published, but the above publication should get you started.
Best,
Jason

Thank you so much!


Fix Process.find_executable once and for all

Make it work on Windows.
Make it actually check that the found path is an executable file.
Fix a lot of edge cases.
Add specs and also verify that these expectations exactly match what Process.new would do.

Could you add a comment to the manual spec that describes how it differens from the regular one?

(I agree with the comments but I haven't made the suggested changes yet.)

Once and for all until we decide to implement PATHEXT on windows :P

Well if you did that, it'd be wrong as long as we want to match the behavior of Process.run (what it will run or won't), and the specs would not pass.
PATHEXT is a thing just in CMD shell.

ping

ping


WIP | Just testing CI

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Patch and project coverage have no change.

Comparison is base (7036fcf) 82.04% compared to head (e76f917) 82.04%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1027   +/-   ##
=======================================
  Coverage   82.04%   82.04%
=======================================
  Files          52       52
  Lines        5653     5653
=======================================
  Hits         4638     4638
  Misses       1015     1015

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


JPEG recreated at each start

Even when defining a data dir, thumbnails are always recreated.
Steps to reproduce :

start program with the --tempdir data/ flag
all books are indexed / thumbnails are created
stop the program, the log 2017/12/30 21:17:50 Not removing temp dir because dir already existed at start is dumped (quite expected)
data/ folder still contains all *.jpg
start the program again with the same command line / same --tempdir
everything is indexed again (maybe expected) but every single thumbnail is then also recreated (which takes quite some time with a lot of *.epub)

(a test like "if the corresponding cover and thumbbail jpeg are already available in the current tempdir, then don't recreate them" is probably missing)
With BookServer 3.0.4

Thanks for reporting these issues!
As for caching, I forgot to add the check. Good catch.

I have fixed this, and it will be included in the next release. As for performance, there is not much difference unless you have a large number of books.


Cannot create a database with the same name as a deleted one

Login to Arachne Data Node
Go to Administration → Databases
Create a database with valid parameters (e.g. copy an existing one) and a unique name
Delete the database
Create another database with the same name as on the step # 3

Expected result: creating is possible since the previous database has been deleted
Actual result: a new database is not created because it has the same name as the database from the step # 3 which has already been deleted

I still observe this issue on our Ody stand

As discussed:

Connection check should not be a part of adding datasource action
We want to have a separate button on UI to check connection
Connection check should be done though Execution Engine

I was able to create a data source with the same name as a deleted one


Add RFB protocol version negotiation

Before, if the client did not support the by the server
advertised RFB protocol version, the program would hang. The
correct behavior is to select the next lower supported version.
Like before, we really only support version 3.3.

sorry its took me so long to look at this, if you could fix the spelling error and merge master so we can get the tests passing I'd be happy to merge it.

Hi, completely forgot about this change. I fixed the typo and rebased. Thanx.

thanks from rainy Vancouver and be careful the plug doesn't get wet :)