* @return the lease key
         */
        public Smb2LeaseKey getLeaseKey() {
            return leaseKey;
        }

        /**
         * Gets the current lease state flags for this entry
         * @return the current lease state
         */
        public int getLeaseState() {
            return leaseState;
        }

        /**

        SMBUtil.writeInt4(aceCount, buffer, offset + 4); // ACE count
    }

    private void prepareSimpleAce(byte[] buffer, int offset) {
        buffer[offset] = 0x00; // Allow ACE
        buffer[offset + 1] = 0x00; // flags
        SMBUtil.writeInt2(32, buffer, offset + 2); // size
        SMBUtil.writeInt4(0x001200A9, buffer, offset + 4); // access mask

        // Simple SID
        buffer[offset + 8] = 0x01; // revision

- Kubelet now exposes `/debug/flags/v` to allow dynamically setting glog logging level.  For example, to change glog level to 3, you only have to send a PUT request like `curl -X PUT http://127.0.0.1:8080/debug/flags/v -d "3"`. ([#64601](https://github.com/kubernetes/kubernetes/pull/64601), [@hzxuzhonghu](https://github.com/hzxuzhonghu))

### SIG OpenStack

 * provide much stronger guarantees.
 *
 * <h3>Comparison to a map of collections</h3>
 *
 * <p>Multimaps are commonly used in places where a {@code Map<K, Collection<V>>} would otherwise
 * have appeared. The differences include:
 *
 * <ul>
 *   <li>There is no need to populate an empty collection before adding an entry with {@link #put
 *       put}.

                + ",maxParameterCount=" + this.maxParameterCount + ",maxDataCount=" + this.maxDataCount + ",maxSetupCount="
                + (int) this.maxSetupCount + ",flags=0x" + Hexdump.toHexString(this.tflags, 2) + ",timeout=" + this.timeout
                + ",parameterCount=" + this.parameterCount + ",parameterOffset=" + this.parameterOffset + ",parameterDisplacement="

 * which is optimal, and <i>not</i> the size of the internal hashtable, which could be much larger
 * than {@code size()}. Furthermore, this structure places significantly reduced load on the garbage
 * collector by only using a constant number of internal objects.
 *
 * <p>If there are no removals, then iteration order for the {@link #entrySet}, {@link #keySet}, and

or `/etc/sysconfig/kubelet`, depending on the system...

* Adds the same information to an init container as a standard container in a pod when using PodPresets. ([#71479](https://github.com/kubernetes/kubernetes/pull/71479), [@soggiest](https://github.com/soggiest))
* fix the flake in scheduling_queue_test.go ([#74611](https://github.com/kubernetes/kubernetes/pull/74611), [@denkensk](https://github.com/denkensk))

  //    you entered with, and it doesn't actually matter.
  //
  // 2. Since you can enter the monitor without a guard at all, some
  //    places you'll have monitor.enter()/monitor.leave() and other
  //    places you'll have guard.enter()/guard.leave() even though
  //    it's the same lock being acquired underneath. Always using
  //    monitor.enterXXX()/monitor.leave() will make it really clear

        assertTrue(result.contains("version=3"));
        assertTrue(result.contains("size=200")); // updated size
        assertTrue(result.contains("serverType=1"));
        assertTrue(result.contains("flags=0"));
        assertTrue(result.contains("proximity=10"));
        assertTrue(result.contains("ttl=600"));
        // Check that paths and node are present
        assertTrue(result.contains("path="));