where is data/scene_observations

when i installed soundspaces0.1.2 with habitat-0.1.7, after downloading dataset, I tryed to start to train the model, but a problem occured：
speaks that I lose file 'data/scene_observation/replica/apartment_0.pkl'
where can i get these files?
and when i tryed to just to run the pretrained models as instruction 4 'Generate demo video with audio', problem also occured that raise an EOF error.
here is my console output:
(habitat_cuda) fyw@7049GP-TRT:/data1/fyw/soundspaces/sound-spaces-0.1.2$ python ss_baselines/av_nav/run.py --exp-config
ss_baselines/av_nav/config/audionav/replica/train_telephone/audiogoal_depth.yaml --model-dir data/models/replica/audiogoal_depth
2022-12-19 22:56:16.318318: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-19 22:56:16.475771: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2022-12-19 22:56:17.063157: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:17.063246: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:17.063257: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
data/models/replica/audiogoal_depth/tb exists
data/models/replica/audiogoal_depth/data exists
Output directory already exists! Overwrite the folder? (y/n)y
2022-12-19 22:56:20,932 config: BASE_TASK_CONFIG_PATH: configs/audionav/av_nav/replica/audiogoal.yaml
CHECKPOINT_FOLDER: data/models/replica/audiogoal_depth/data
CHECKPOINT_INTERVAL: 50
CMD_TRAILING_OPTS: []
DEBUG: False
DISPLAY_RESOLUTION: 128
ENV_NAME: AudioNavRLEnv
EVAL:
SPLIT: val
USE_CKPT_CONFIG: True
EVAL_CKPT_PATH_DIR: data/models/replica/audiogoal_depth/data
EXTRA_RGB: False
LOG_FILE: data/models/replica/audiogoal_depth/train.log
LOG_INTERVAL: 10
NUM_PROCESSES: 5
NUM_UPDATES: 40000
RL:
DISTANCE_REWARD_SCALE: 1.0
PPO:
clip_param: 0.1
entropy_coef: 0.2
eps: 1e-05
gamma: 0.99
hidden_size: 512
lr: 0.00025
max_grad_norm: 0.5
num_mini_batch: 1
num_steps: 150
ppo_epoch: 4
reward_window_size: 50
tau: 0.95
use_gae: True
use_linear_clip_decay: True
use_linear_lr_decay: True
value_loss_coef: 0.5
SLACK_REWARD: -0.01
SUCCESS_REWARD: 10.0
TIME_DIFF: False
WITH_DISTANCE_REWARD: True
WITH_TIME_PENALTY: True
SEED: 0
SENSORS: ['DEPTH_SENSOR']
SIMULATOR_GPU_ID: 0
TASK_CONFIG:
DATASET:
CONTENT_SCENES: ['*']
DATA_PATH: data/datasets/audionav/replica/{version}/{split}/{split}.json.gz
SCENES_DIR: data/scene_datasets/replica
SPLIT: train_telephone
TYPE: AudioNav
VERSION: v1
ENVIRONMENT:
ITERATOR_OPTIONS:
CYCLE: True
GROUP_BY_SCENE: True
MAX_SCENE_REPEAT_EPISODES: -1
MAX_SCENE_REPEAT_STEPS: 10000
NUM_EPISODE_SAMPLE: -1
SHUFFLE: True
STEP_REPETITION_RANGE: 0.2
MAX_EPISODE_SECONDS: 10000000
MAX_EPISODE_STEPS: 500
PYROBOT:
BASE_CONTROLLER: proportional
BASE_PLANNER: none
BUMP_SENSOR:
TYPE: PyRobotBumpSensor
DEPTH_SENSOR:
CENTER_CROP: False
HEIGHT: 480
MAX_DEPTH: 5.0
MIN_DEPTH: 0.0
NORMALIZE_DEPTH: True
TYPE: PyRobotDepthSensor
WIDTH: 640
LOCOBOT:
ACTIONS: ['BASE_ACTIONS', 'CAMERA_ACTIONS']
BASE_ACTIONS: ['go_to_relative', 'go_to_absolute']
CAMERA_ACTIONS: ['set_pan', 'set_tilt', 'set_pan_tilt']
RGB_SENSOR:
CENTER_CROP: False
HEIGHT: 480
TYPE: PyRobotRGBSensor
WIDTH: 640
ROBOT: locobot
ROBOTS: ['locobot']
SENSORS: ['RGB_SENSOR', 'DEPTH_SENSOR', 'BUMP_SENSOR']
SEED: 100
SIMULATOR:
ACTION_SPACE_CONFIG: v0
AGENTS: ['AGENT_0']
AGENT_0:
ANGULAR_ACCELERATION: 12.56
ANGULAR_FRICTION: 1.0
COEFFICIENT_OF_RESTITUTION: 0.0
HEIGHT: 1.5
IS_SET_START_STATE: False
LINEAR_ACCELERATION: 20.0
LINEAR_FRICTION: 0.5
MASS: 32.0
RADIUS: 0.1
SENSORS: ['RGB_SENSOR']
START_POSITION: [0, 0, 0]
START_ROTATION: [0, 0, 0, 1]
AUDIO:
BINAURAL_RIR_DIR: data/binaural_rirs
EVERLASTING: True
GRAPH_FILE: graph.pkl
HAS_DISTRACTOR_SOUND: False
METADATA_DIR: data/metadata
POINTS_FILE: points.txt
RIR_SAMPLING_RATE: 44100
SCENE:
SOURCE_SOUND_DIR: data/sounds/1s_all
CONTINUOUS_VIEW_CHANGE: False
DEFAULT_AGENT_ID: 0
DEPTH_SENSOR:
HEIGHT: 128
HFOV: 90
MAX_DEPTH: 10.0
MIN_DEPTH: 0.0
NORMALIZE_DEPTH: True
ORIENTATION: [0.0, 0.0, 0.0]
POSITION: [0, 1.25, 0]
TYPE: HabitatSimDepthSensor
WIDTH: 128
FORWARD_STEP_SIZE: 0.5
GRID_SIZE: 0.5
HABITAT_SIM_V0:
ALLOW_SLIDING: True
ENABLE_PHYSICS: False
GPU_DEVICE_ID: 0
GPU_GPU: False
PHYSICS_CONFIG_FILE: ./data/default.physics_config.json
RGB_SENSOR:
HEIGHT: 128
HFOV: 90
ORIENTATION: [0.0, 0.0, 0.0]
POSITION: [0, 1.25, 0]
TYPE: HabitatSimRGBSensor
WIDTH: 128
SCENE: data/scene_datasets/habitat-test-scenes/van-gogh-room.glb
SCENE_DATASET: replica
SCENE_OBSERVATION_DIR: data/scene_observations
SEED: 100
SEMANTIC_SENSOR:
HEIGHT: 480
HFOV: 90
ORIENTATION: [0.0, 0.0, 0.0]
POSITION: [0, 1.25, 0]
TYPE: HabitatSimSemanticSensor
WIDTH: 640
TILT_ANGLE: 15
TURN_ANGLE: 10
TYPE: SoundSpacesSim
USE_RENDERED_OBSERVATIONS: True
USE_SYNC_VECENV: False
VIEW_CHANGE_FPS: 10
TASK:
ACTIONS:
ANSWER:
TYPE: AnswerAction
LOOK_DOWN:
TYPE: LookDownAction
LOOK_UP:
TYPE: LookUpAction
MOVE_FORWARD:
TYPE: MoveForwardAction
STOP:
TYPE: StopAction
TELEPORT:
TYPE: TeleportAction
TURN_LEFT:
TYPE: TurnLeftAction
TURN_RIGHT:
TYPE: TurnRightAction
ANSWER_ACCURACY:
TYPE: AnswerAccuracy
AUDIOGOAL_SENSOR:
TYPE: AudioGoalSensor
COLLISIONS:
TYPE: Collisions
COMPASS_SENSOR:
TYPE: CompassSensor
CORRECT_ANSWER:
TYPE: CorrectAnswer
DISTANCE_TO_GOAL:
DISTANCE_TO: POINT
TYPE: DistanceToGoal
EPISODE_INFO:
TYPE: EpisodeInfo
GOAL_SENSOR_UUID: spectrogram
GPS_SENSOR:
DIMENSIONALITY: 2
TYPE: GPSSensor
HEADING_SENSOR:
TYPE: HeadingSensor
IMAGEGOAL_SENSOR:
TYPE: ImageGoalSensor
INSTRUCTION_SENSOR:
TYPE: InstructionSensor
INSTRUCTION_SENSOR_UUID: instruction
MEASUREMENTS: ['DISTANCE_TO_GOAL', 'NORMALIZED_DISTANCE_TO_GOAL', 'SUCCESS', 'SPL', 'SOFT_SPL', 'NUM_ACTION', 'SUCCESS_WEIGHTED_BY_NUM_ACTION']
NORMALIZED_DISTANCE_TO_GOAL:
TYPE: NormalizedDistanceToGoal
NUM_ACTION:
TYPE: NA
OBJECTGOAL_SENSOR:
GOAL_SPEC: TASK_CATEGORY_ID
GOAL_SPEC_MAX_VAL: 50
TYPE: ObjectGoalSensor
POINTGOAL_SENSOR:
DIMENSIONALITY: 2
GOAL_FORMAT: POLAR
TYPE: PointGoalSensor
POINTGOAL_WITH_GPS_COMPASS_SENSOR:
DIMENSIONALITY: 2
GOAL_FORMAT: POLAR
TYPE: PointGoalWithGPSCompassSensor
POSSIBLE_ACTIONS: ['STOP', 'MOVE_FORWARD', 'TURN_LEFT', 'TURN_RIGHT']
PROXIMITY_SENSOR:
MAX_DETECTION_RADIUS: 2.0
TYPE: ProximitySensor
QUESTION_SENSOR:
TYPE: QuestionSensor
SENSORS: ['SPECTROGRAM_SENSOR']
SOFT_SPL:
TYPE: SoftSPL
SPECTROGRAM_SENSOR:
TYPE: SpectrogramSensor
SPL:
SUCCESS_DISTANCE: 0.2
TYPE: SPL
SUCCESS:
SUCCESS_DISTANCE: 0.2
TYPE: Success
SUCCESS_DISTANCE: 0.2
SUCCESS_WEIGHTED_BY_NUM_ACTION:
TYPE: SNA
TOP_DOWN_MAP:
DRAW_BORDER: True
DRAW_GOAL_AABBS: True
DRAW_GOAL_POSITIONS: True
DRAW_SHORTEST_PATH: True
DRAW_SOURCE: True
DRAW_SOURCE_AND_TARGET: True
DRAW_VIEW_POINTS: True
FOG_OF_WAR:
DRAW: True
FOV: 90
VISIBILITY_DIST: 5.0
MAP_PADDING: 3
MAP_RESOLUTION: 10000
MAX_EPISODE_STEPS: 1000
TYPE: TopDownMap
TYPE: AudioNav
TENSORBOARD_DIR: data/models/replica/audiogoal_depth/tb
TEST_EPISODE_COUNT: 2
TORCH_GPU_ID: 0
TRAINER_NAME: AVNavTrainer
USE_LAST_CKPT: False
USE_SYNC_VECENV: False
USE_VECENV: True
VIDEO_DIR: data/models/replica/audiogoal_depth/video_dir
VIDEO_OPTION: []
VISUALIZATION_OPTION: []
2022-12-19 22:56:20,933 Initializing dataset AudioNav
2022-12-19 22:56:20, INFO: Using VectorEnv
2022-12-19 22:56:23.734928: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-19 22:56:23.741468: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-19 22:56:23.780980: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-19 22:56:23.817418: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-19 22:56:23.875324: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-19 22:56:23.898933: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2022-12-19 22:56:23.902790: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2022-12-19 22:56:23.917278: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2022-12-19 22:56:23.970617: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2022-12-19 22:56:24.035279: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2022-12-19 22:56:24.643324: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.643448: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.643460: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2022-12-19 22:56:24.651956: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.652052: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.652065: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2022-12-19 22:56:24.652287: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.652382: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.652394: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2022-12-19 22:56:24.729861: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.729981: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.729994: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2022-12-19 22:56:24.792559: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.792655: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/site-packages/cv2/../../lib64:
2022-12-19 22:56:24.792667: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2022-12-19 22:56:25,091 Initializing dataset AudioNav
2022-12-19 22:56:25,092 Initializing dataset AudioNav
2022-12-19 22:56:25,105 Initializing dataset AudioNav
2022-12-19 22:56:25,170 Initializing dataset AudioNav
2022-12-19 22:56:25,233 Initializing dataset AudioNav
2022-12-19 22:56:25, INFO: Sampled 13132 from frl_apartment_2
2022-12-19 22:56:25, INFO: Sampled 1892 from room_0
2022-12-19 22:56:25,442 initializing sim SoundSpacesSim
Process ForkServerProcess-4:
Traceback (most recent call last):
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/contextlib.py", line 74, in inner
return func(*args, **kwds)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 233, in _worker_env
env = env_fn(*env_fn_args)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/env_utils.py", line 131, in make_env_fn
env = env_class(config=config, dataset=dataset)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/environments.py", line 46, in init
super().init(self._core_env_config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 336, in init
self._env = Env(config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 110, in init
id_sim=self._config.SIMULATOR.TYPE, config=self._config.SIMULATOR
File "/data1/fyw/soundspaces/habitat-lab/habitat/sims/registration.py", line 19, in make_sim
return _sim(**kwargs)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/soundspaces/simulator.py", line 164, in init
with open(self.current_scene_observation_file, 'rb') as fo:
FileNotFoundError: [Errno 2] No such file or directory: 'data/scene_observations/replica/frl_apartment_2.pkl'
2022-12-19 22:56:25, INFO: Sampled 13882 from frl_apartment_1
2022-12-19 22:56:25, INFO: Sampled 1526 from hotel_0
2022-12-19 22:56:25, INFO: Sampled 13670 from frl_apartment_0
2022-12-19 22:56:25,496 initializing sim SoundSpacesSim
Process ForkServerProcess-3:
Traceback (most recent call last):
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/contextlib.py", line 74, in inner
return func(*args, **kwds)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 233, in _worker_env
env = env_fn(*env_fn_args)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/env_utils.py", line 131, in make_env_fn
env = env_class(config=config, dataset=dataset)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/environments.py", line 46, in init
super().init(self._core_env_config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 336, in init
self._env = Env(config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 110, in init
id_sim=self._config.SIMULATOR.TYPE, config=self._config.SIMULATOR
File "/data1/fyw/soundspaces/habitat-lab/habitat/sims/registration.py", line 19, in make_sim
return _sim(**kwargs)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/soundspaces/simulator.py", line 164, in init
with open(self.current_scene_observation_file, 'rb') as fo:
FileNotFoundError: [Errno 2] No such file or directory: 'data/scene_observations/replica/hotel_0.pkl'
2022-12-19 22:56:25, INFO: Sampled 17220 from frl_apartment_3
2022-12-19 22:56:25,659 initializing sim SoundSpacesSim
Process ForkServerProcess-5:
Traceback (most recent call last):
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/contextlib.py", line 74, in inner
return func(*args, **kwds)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 233, in _worker_env
env = env_fn(*env_fn_args)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/env_utils.py", line 131, in make_env_fn
env = env_class(config=config, dataset=dataset)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/environments.py", line 46, in init
super().init(self._core_env_config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 336, in init
self._env = Env(config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 110, in init
id_sim=self._config.SIMULATOR.TYPE, config=self._config.SIMULATOR
File "/data1/fyw/soundspaces/habitat-lab/habitat/sims/registration.py", line 19, in make_sim
return _sim(**kwargs)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/soundspaces/simulator.py", line 164, in init
with open(self.current_scene_observation_file, 'rb') as fo:
FileNotFoundError: [Errno 2] No such file or directory: 'data/scene_observations/replica/frl_apartment_3.pkl'
2022-12-19 22:56:25, INFO: Sampled 4360 from office_4
2022-12-19 22:56:25,737 initializing sim SoundSpacesSim
Process ForkServerProcess-2:
Traceback (most recent call last):
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/contextlib.py", line 74, in inner
return func(*args, **kwds)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 233, in _worker_env
env = env_fn(*env_fn_args)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/env_utils.py", line 131, in make_env_fn
env = env_class(config=config, dataset=dataset)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/environments.py", line 46, in init
super().init(self._core_env_config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 336, in init
self._env = Env(config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 110, in init
id_sim=self._config.SIMULATOR.TYPE, config=self._config.SIMULATOR
File "/data1/fyw/soundspaces/habitat-lab/habitat/sims/registration.py", line 19, in make_sim
return _sim(**kwargs)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/soundspaces/simulator.py", line 164, in init
with open(self.current_scene_observation_file, 'rb') as fo:
FileNotFoundError: [Errno 2] No such file or directory: 'data/scene_observations/replica/office_4.pkl'
2022-12-19 22:56:26, INFO: Sampled 40748 from apartment_0
2022-12-19 22:56:26, INFO: Sampled 388 from office_0
2022-12-19 22:56:26,288 initializing sim SoundSpacesSim
Process ForkServerProcess-1:
Traceback (most recent call last):
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/contextlib.py", line 74, in inner
return func(*args, **kwds)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 233, in _worker_env
env = env_fn(*env_fn_args)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/env_utils.py", line 131, in make_env_fn
env = env_class(config=config, dataset=dataset)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/environments.py", line 46, in init
super().init(self._core_env_config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 336, in init
self._env = Env(config, dataset)
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/env.py", line 110, in init
id_sim=self._config.SIMULATOR.TYPE, config=self._config.SIMULATOR
File "/data1/fyw/soundspaces/habitat-lab/habitat/sims/registration.py", line 19, in make_sim
return _sim(**kwargs)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/soundspaces/simulator.py", line 164, in init
with open(self.current_scene_observation_file, 'rb') as fo:
FileNotFoundError: [Errno 2] No such file or directory: 'data/scene_observations/replica/apartment_0.pkl'
Traceback (most recent call last):
File "ss_baselines/av_nav/run.py", line 101, in
main()
File "ss_baselines/av_nav/run.py", line 95, in main
trainer.train()
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/av_nav/ppo/ppo_trainer.py", line 234, in train
self.config, get_env_class(self.config.ENV_NAME)
File "/data1/fyw/soundspaces/sound-spaces-0.1.2/ss_baselines/common/env_utils.py", line 102, in construct_envs
auto_reset_done=auto_reset_done
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 194, in init
read_fn() for read_fn in self._connection_read_fns
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 194, in
read_fn() for read_fn in self._connection_read_fns
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 97, in call
res = self.read_fn()
File "/data1/fyw/soundspaces/habitat-lab/habitat/utils/pickle5_multiprocessing.py", line 68, in recv
buf = self.recv_bytes()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/connection.py", line 216, in recv_bytes
buf = self._recv_bytes(maxlength)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/connection.py", line 407, in _recv_bytes
buf = self._recv(4)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/connection.py", line 379, in _recv
chunk = read(handle, remaining)
ConnectionResetError: [Errno 104] Connection reset by peer
Exception ignored in: <function VectorEnv.del at 0x7fc15fa98950>
Traceback (most recent call last):
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 588, in del
self.close()
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 456, in close
read_fn()
File "/data1/fyw/soundspaces/habitat-lab/habitat/core/vector_env.py", line 97, in call
res = self.read_fn()
File "/data1/fyw/soundspaces/habitat-lab/habitat/utils/pickle5_multiprocessing.py", line 68, in recv
buf = self.recv_bytes()
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/connection.py", line 216, in recv_bytes
buf = self._recv_bytes(maxlength)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/connection.py", line 407, in _recv_bytes
buf = self._recv(4)
File "/home/fyw/anaconda3/envs/habitat_cuda/lib/python3.7/multiprocessing/connection.py", line 383, in _recv
raise EOFError

I am a little confused about when I run this script, the bug comes out saying HabitatSimRGBSensor object has no attribute _getdefault_spec, I used habitat-0.1.7,too


Cilium 1.14.5+ can break Kubernetes pod connectivity due to the reserved:init label never being removed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Starting with Cilium 1.14.5, we are occasionally seeing pods in newly provisioned (DigitalOcean managed) Kubernetes clusters completely fail to ingress or egress traffic any traffic. The built-in cilium monitor shows that packets are dropped / being rejected on their way into and out of such pods.
We did not notice that the affected pods all have the reserved:init label set on the Cilium endpoint in addition to the regular pod labels. Also, the policies for both ingress and egress are marked enabled for such pods according to cilium endpoint get/list even though the policy enforcement policy is set to default and no network policies are installed at all -- output from cilium endpoint list for an affected CoreDNS instance:
ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                   IPv6   IPv4          STATUS
           ENFORCEMENT        ENFORCEMENT
2354       Enabled            Enabled           26544      k8s:doks.digitalocean.com/managed=true                                               <IP_ADDRESS>   ready
                                                           k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system
                                                           k8s:io.cilium.k8s.policy.cluster=default
                                                           k8s:io.cilium.k8s.policy.serviceaccount=coredns
                                                           k8s:io.kubernetes.pod.namespace=kube-system
                                                           k8s:k8s-app=kube-dns
                                                           reserved:init

I am assuming that the policy enforcement is a consequence of the reserved:init label being set. What is not clear to me is why that special label has not been removed despite all other pod labels having been discovered successfully.
According to the documentation for the reserved:init label, it may be assigned when one of three described conditions hold. We do not use Docker on the Kubernetes nodes and we also don't run in etcd mode, so only a (brief) unavailability of the Kubernetes API server remains as possible explanation why the label was added in the first place. FWIW, in none of the cases I have looked at more closely, I was able to spot a clear error message in the Cilium agent logs indicating that an API server request may have failed. (If the failures manifest as API watch events not being propagated to the agent in time or with a delay, however, then I imagine it could be conceivable that no error logs may be produced.)
So far we have only spotted the problem during the initial provisioning of a cluster. Once a cluster manages to finish bootstrapping without the reserved:init label being assigned, the issue does not seem to occur anymore during the remaining runtime of a cluster (or we haven't spotted it yet). I've been speculating whether the API server not being totally stable and settled in during the provisioning process may be a contributing factor.
The issue also happens on 1.14.6 but does not seem to manifest in 1.14.4.
I've been trying to reproduce the problem by attempting to surgically disallow access from the Cilium agent to the API server just as far as label discovery is concerned. This turned out to be somewhat tricky since pods won't even come up if access is prohibited too broadly. The closest I have gotten this to is by modifying the RBAC permissions of the agent to strip off the get and watch permissions from the pods resource, essentially splitting the (default) RBAC API group
- apiGroups:
  - ""
  resources:
  - namespaces
  - services
  - pods
  - endpoints
  - nodes
  verbs:
  - get
  - list
  - watch

into two separate groups, like this:
- apiGroups:
  - ""
  resources:
  - namespaces
  - services
  - endpoints
  - nodes
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - list

After restarting the Cilium agent, newly launched pods received the reserved:init label. Even when I re-enable all permissions for the pods resource, the label sticks around.
I have to say that I am not super certain if the above is the perfect or even right way to reproduce the bug: I would have expected the CiliumEndpoint objects of deliberately broken pods not not have any regular pod labels at all but only the reserved:init label while the RBAC permission is modified. However, when I watch for new CiliumEndpoint objects, I always see both the regular labels and the reserved:init label being associated right from the beginning. Chances are though I am missing some details on how the label is handled exactly, so happy to hear feedback on this and apply any repro suggestions folks may have.
One large(r) scale reproduction case that does work fairly reliable is to launch 50-60 new clusters in our environment. I'd then usually hit 1-2 broken clusters that show the described symptoms.
We're now downgrading to 1.14.4 again as a workaround, but obviously would want to see the bug addressed so that we can roll forward again. I've been peaking around the code a bit but haven't been able to identify any particular area that would need to be worked on for a fix. Once the root cause is identified and the approach to fixing it becomes apparent, I'm open to trying to submit a PR myself. Appreciate your support on this case.
 subsys=daemon
2024-01-26T00:04:41.736524723Z level=info msg="Reusing previous DNS proxy port: 46327" subsys=daemon
2024-01-26T00:04:41.736577715Z level=info msg="Waiting until all Cilium CRDs are available" subsys=k8s
2024-01-26T00:04:42.737076426Z level=info msg="All Cilium CRDs have been found and are available" subsys=k8s
2024-01-26T00:04:42.737255001Z level=info msg="Creating or updating CiliumNode resource" node=pool-o7caf subsys=nodediscovery
2024-01-26T00:04:42.737383326Z level=info msg="Creating or updating CiliumNode resource" node=pool-o7caf subsys=nodediscovery
2024-01-26T00:04:42.753990106Z level=warning msg="Unable to update CiliumNode resource, will retry" error="Operation cannot be fulfilled on ciliumnodes.cilium.io \"pool-o7caf\": the object has been modified; please apply your changes to the latest version and try again" subsys=nodediscovery
2024-01-26T00:04:42.758977918Z level=info msg="Retrieved node information from cilium node" nodeName=pool-o7caf subsys=k8s
2024-01-26T00:04:42.759006576Z level=info msg="Received own node information from API server" ipAddr.ipv4=<IP_ADDRESS> ipAddr.ipv6="<nil>" k8sNodeIP=<IP_ADDRESS> labels="map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:s-2vcpu-4gb beta.kubernetes.io/os:linux doks.digitalocean.com/managed:true doks.digitalocean.com/node-id:2684529e-fb0e-4062-8414-beda244612e9 doks.digitalocean.com/node-pool:pool doks.digitalocean.com/node-pool-id:4fda5043-42f3-4379-85a1-caf2b1eacb29 doks.digitalocean.com/version:1.29.0-do.0 failure-domain.beta.kubernetes.io/region:nyc1 kubernetes.io/arch:amd64 kubernetes.io/hostname:pool-o7caf kubernetes.io/os:linux node.kubernetes.io/instance-type:s-2vcpu-4gb topology.kubernetes.io/region:nyc1]" nodeName=pool-o7caf subsys=k8s v4Prefix=<IP_ADDRESS>/25 v6Prefix="<nil>"
2024-01-26T00:04:42.759011260Z level=info msg="k8s mode: Allowing localhost to reach local endpoints" subsys=daemon
2024-01-26T00:04:42.759103839Z level=info msg="Detected devices" devices="[]" subsys=linux-datapath
2024-01-26T00:04:42.759179373Z level=info msg="Enabling k8s event listener" subsys=k8s-watcher
2024-01-26T00:04:42.760241864Z level=info msg="Removing stale endpoint interfaces" subsys=daemon
2024-01-26T00:04:42.760478879Z level=info msg="Skipping kvstore configuration" subsys=daemon
2024-01-26T00:04:42.760961750Z level=info msg="Restored router address from node_config" file=/var/run/cilium/state/globals/node_config.h ipv4=<IP_ADDRESS> ipv6="<nil>" subsys=node
2024-01-26T00:04:42.761448424Z level=info msg="Initializing node addressing" subsys=daemon
2024-01-26T00:04:42.761460281Z level=info msg="Initializing cluster-pool IPAM" subsys=ipam v4Prefix=<IP_ADDRESS>/25 v6Prefix="<nil>"
2024-01-26T00:04:42.761640076Z level=info msg="Restoring endpoints..."  Scheduling regeneration" endpointID=2354 subsys=daemon
2024-01-26T00:04:43.899239049Z level=info msg="Successfully restored endpoint. Scheduling regeneration" endpointID=3484 subsys=daemon
2024-01-26T00:04:43.899244666Z level=info msg="Successfully restored endpoint. Scheduling regeneration" endpointID=716 subsys=daemon
2024-01-26T00:04:43.899614239Z level=info msg="Successfully restored endpoint. Scheduling regeneration" endpointID=1013 subsys=daemon
2024-01-26T00:04:43.899630563Z level=info msg="Successfully restored endpoint. Scheduling regeneration" endpointID=1375 subsys=daemon
2024-01-26T00:04:43.899662538Z level=info msg="Successfully restored endpoint. Scheduling regeneration" endpointID=188 subsys=daemon
2024-01-26T00:04:43.899831711Z level=info msg="Reusing existing global key" key="k8s:doks.digitalocean.com/managed=true;reserved:init=;k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=default;k8s:io.cilium.k8s.policy.serviceaccount=coredns;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=kube-dns;" subsys=allocator
2024-01-26T00:04:43.899913299Z level=info msg="Reusing existing global key" key="k8s:doks.digitalocean.com/managed=true;reserved:init=;k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=default;k8s:io.cilium.k8s.policy.serviceaccount=konnectivity-agent;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=konnectivity-agent;" subsys=allocator
2024-01-26T00:04:43.900073394Z level=info msg="Reusing existing global key" key="k8s:doks.digitalocean.com/managed=true;k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=default;k8s:io.cilium.k8s.policy.serviceaccount=coredns;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=kube-dns;" subsys=allocator
2024-01-26T00:04:43.900353241Z level=info msg="Reusing existing global key" key="k8s:app.kubernetes.io/name=hubble-ui;k8s:app.kubernetes.io/part-of=cilium;k8s:doks.digitalocean.com/managed=true;reserved:init=;k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=default;k8s:io.cilium.k8s.policy.serviceaccount=hubble-ui;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=hubble-ui;" subsys=allocator
2024-01-26T00:04:43.900466662Z level=info msg="Reusing existing global key" key="k8s:app.kubernetes.io/name=hubble-relay;k8s:app.kubernetes.io/part-of=cilium;k8s:doks.digitalocean.com/managed=true;k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=default;k8s:io.cilium.k8s.policy.serviceaccount=hubble-relay;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=hubble-relay;" subsys=allocator
2024-01-26T00:04:43.903343744Z level=info msg="Removed endpoint" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3392 identity=4 ipv4=<IP_ADDRESS> ipv6= k8sPodName=/ subsys=endpoint
2024-01-26T00:04:43.903635602Z level=info msg="Service has stale backends: triggering refresh" l3n4Addr="{AddrCluster:<IP_ADDRESS> L4Addr:{Protocol:NONE Port:443} Scope:0}" orphanBackends=1 serviceID=3 serviceName=kube-system/hubble-peer subsys=service
2024-01-26T00:04:43.903849263Z level=info msg="Deleted orphan backends" orphanBackends=0 subsys=service
2024-01-26T00:04:43.909894169Z level=info msg="Launching Cilium health daemon" subsys=daemon
2024-01-26T00:04:43.915782854Z level=info msg="Launching Cilium health endpoint" subsys=daemon
2024-01-26T00:04:43.916025190Z level=info msg="Started healthz status API server" address="<IP_ADDRESS>:9879" subsys=daemon
2024-01-26T00:04:43.916074342Z level=info msg="Processing queued endpoint deletion requests from /var/run/cilium/deleteQueue" subsys=daemon
2024-01-26T00:04:43.916189367Z level=info msg="processing 0 queued deletion requests" subsys=daemon
2024-01-26T00:04:43.916200581Z level=info msg="Initializing Cilium API" subsys=daemon
2024-01-26T00:04:44.008081737Z level=info msg="Daemon initialization completed" bootstrapTime=3.075300848s subsys=daemon
2024-01-26T00:04:44.009645573Z level=info msg="Serving cilium API at unix:///var/run/cilium/cilium.sock" subsys=daemon
2024-01-26T00:04:44.009862278Z level=info msg="Configuring Hubble server" eventQueueSize=2048 maxFlows=4095 subsys=hubble
2024-01-26T00:04:44.010125005Z level=info msg="Starting local Hubble server" address="unix:///var/run/cilium/hubble.sock" subsys=hubble
2024-01-26T00:04:44.019216650Z level=info msg="Beginning to read perf buffer" startTime="2024-01-26 00:04:44.019011616 +0000 UTC m=+3.164582993" subsys=monitor-agent
2024-01-26T00:04:44.026700452Z level=info msg="Starting Hubble server" address=":4244" subsys=hubble
2024-01-26T00:04:44.423351037Z level=info msg="Compiled new BPF template" BPFCompilationTime=517.96385ms file-path=/var/run/cilium/state/templates/ee45e889ba1ebc46ccd364277ee0a6dcfd1fdf536c1a3c96824acb8e9e59a485/bpf_host.o subsys=datapath-loader
2024-01-26T00:04:44.427521331Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_hostns_01013 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_hostns_01013 subsys=bpf
2024-01-26T00:04:44.432339008Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_hostns_01013 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_hostns_01013:pending" subsys=bpf
2024-01-26T00:04:44.436300519Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_netdev_00006 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_netdev_00006 subsys=bpf
2024-01-26T00:04:44.440506589Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_netdev_00006 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_netdev_00006:pending" subsys=bpf
2024-01-26T00:04:44.440594962Z level=info msg="Rewrote endpoint BPF program" containerID= datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=1013 identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint
2024-01-26T00:04:44.441248004Z level=info msg="Restored endpoint" endpointID=1013 ipAddr="[ ]" subsys=endpoint
2024-01-26T00:04:44.548550782Z level=info msg="regenerating all endpoints" reason="one or more identities created or deleted" subsys=endpoint-manager
2024-01-26T00:04:45.032551571Z level=info msg="New endpoint" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2510 ipv4=<IP_ADDRESS> ipv6= k8sPodName=/ subsys=endpoint
2024-01-26T00:04:45.032770312Z level=info msg="Resolving identity labels (blocking)" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2510 identityLabels="reserved:health" ipv4=<IP_ADDRESS> ipv6= k8sPodName=/ subsys=endpoint
2024-01-26T00:04:45.032893383Z level=info msg="Identity of endpoint changed" containerID= datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=2510 identity=4 identityLabels="reserved:health" ipv4=<IP_ADDRESS> ipv6= k8sPodName=/ oldIdentity="no identity" subsys=endpoint
2024-01-26T00:04:45.403891964Z level=info msg="Compiled new BPF template" BPFCompilationTime=1.501767707s file-path=/var/run/cilium/state/templates/0a76c06fbd3a7ff6a468a86e716d7c632a9f2067f6d96caaa28c5628ba641692/bpf_lxc.o subsys=datapath-loader
2024-01-26T00:04:45.410653039Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_03484 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_03484 subsys=bpf
2024-01-26T00:04:45.415997033Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_02354 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_02354 subsys=bpf
2024-01-26T00:04:45.469463405Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_03484 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_03484:pending" subsys=bpf
2024-01-26T00:04:45.469506208Z level=info msg="Rewrote endpoint BPF program" containerID=bb1c6e4107 datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=3484 identity=10529 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-2v8kj subsys=endpoint
2024-01-26T00:04:45.478110959Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_01375 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_01375 subsys=bpf
2024-01-26T00:04:45.479430692Z level=info msg="Restored endpoint" endpointID=3484 ipAddr="[<IP_ADDRESS> ]" subsys=endpoint
2024-01-26T00:04:45.519716495Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_02354 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_02354:pending" subsys=bpf
2024-01-26T00:04:45.519773211Z level=info msg="Rewrote endpoint BPF program" containerID=e1ca34e31b datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=2354 identity=26544 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/coredns-6857f5494d-9fq8l subsys=endpoint
2024-01-26T00:04:45.532402052Z level=info msg="Restored endpoint" endpointID=2354 ipAddr="[<IP_ADDRESS> ]" subsys=endpoint
2024-01-26T00:04:45.535879006Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_00188 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_00188 subsys=bpf
2024-01-26T00:04:45.550138716Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_01375 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_01375:pending" subsys=bpf
2024-01-26T00:04:45.550242261Z level=info msg="Rewrote endpoint BPF program" containerID=da67bbf6ea datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=1375 identity=2782 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/hubble-ui-dd784fb98-vlh74 subsys=endpoint
2024-01-26T00:04:45.563264304Z level=info msg="Restored endpoint" endpointID=1375 ipAddr="[<IP_ADDRESS> ]" subsys=endpoint
2024-01-26T00:04:45.593125470Z level=info msg="Re-pinning map with ':pending' suffix" bpfMapName=cilium_calls_00716 bpfMapPath=/sys/fs/bpf/tc/globals/cilium_calls_00716 subsys=bpf
2024-01-26T00:04:45.642603138Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_00188 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_00188:pending" subsys=bpf
2024-01-26T00:04:45.642835490Z level=info msg="Rewrote endpoint BPF program" containerID=77ffdb95b8 datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=188 identity=26484 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/hubble-relay-568f96b49b-vrssn subsys=endpoint
2024-01-26T00:04:45.644256652Z level=info msg="Restored endpoint" endpointID=188 ipAddr="[<IP_ADDRESS> ]" subsys=endpoint
2024-01-26T00:04:45.705821201Z level=info msg="Unpinning map after successful recreation" bpfMapName=cilium_calls_00716 bpfMapPath="/sys/fs/bpf/tc/globals/cilium_calls_00716:pending" subsys=bpf
2024-01-26T00:04:45.705908265Z level=info msg="Rewrote endpoint BPF program" containerID=27a24173b5 datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=716 identity=21226 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/coredns-6857f5494d-vwfh6 subsys=endpoint
2024-01-26T00:04:45.706987230Z level=info msg="Restored endpoint" endpointID=716 ipAddr="[<IP_ADDRESS> ]" subsys=endpoint
2024-01-26T00:04:45.707135247Z level=info msg="Finished regenerating restored endpoints" regenerated=6 subsys=daemon total=6
2024-01-26T00:04:45.707835652Z level=info msg="Removed stale bpf map" file-path=/sys/fs/bpf/tc/globals/cilium_lb4_source_range subsys=daemon
2024-01-26T00:04:45.734345427Z level=info msg="Rewrote endpoint BPF program" containerID= datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=2510 identity=4 ipv4=<IP_ADDRESS> ipv6= k8sPodName=/ subsys=endpoint
2024-01-26T00:04:45.936505162Z level=info msg="Serving cilium health API at unix:///var/run/cilium/health.sock" subsys=health-server
2024-01-26T00:05:56.985744848Z level=info msg="Delete endpoint request" containerID=bb1c6e4107 endpointID=3484 k8sNamespace=kube-system k8sPodName=konnectivity-agent-2v8kj subsys=daemon
2024-01-26T00:05:56.986100153Z level=info msg="Releasing key" key="[k8s:doks.digitalocean.com/managed=true reserved:init k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system k8s:io.cilium.k8s.policy.cluster=default k8s:io.cilium.k8s.policy.serviceaccount=konnectivity-agent k8s:io.kubernetes.pod.namespace=kube-system k8s:k8s-app=konnectivity-agent]" subsys=allocator
2024-01-26T00:05:56.988354365Z level=info msg="Removed endpoint" containerID=bb1c6e4107 datapathPolicyRevision=1 desiredPolicyRevision=1 endpointID=3484 identity=10529 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-2v8kj subsys=endpoint
2024-01-26T00:05:57.444237785Z level=info msg="Create endpoint request" addressing="&{<IP_ADDRESS> 91fd74df-3b1f-435b-b8ef-031008c03cab default   }" containerID=93558b36a83bd32e510d1d4feb10f8aea0f44d7724ca155609ce5ecb1abfd52e datapathConfiguration="&{false false false false false <nil>}" interface=lxc78519e01f29f k8sPodName=kube-system/konnectivity-agent-xjfkb labels="[]" subsys=daemon sync-build=true
2024-01-26T00:05:57.444275019Z level=info msg="New endpoint" containerID=93558b36a8 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3761 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb subsys=endpoint
2024-01-26T00:05:57.444283551Z level=info msg="Resolving identity labels (blocking)" containerID=93558b36a8 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3761 identityLabels="k8s:doks.digitalocean.com/managed=true,k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system,k8s:io.cilium.k8s.policy.cluster=default,k8s:io.cilium.k8s.policy.serviceaccount=konnectivity-agent,k8s:io.kubernetes.pod.namespace=kube-system,k8s:k8s-app=konnectivity-agent" ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb subsys=endpoint
2024-01-26T00:05:57.444377904Z level=info msg="Skipped non-kubernetes labels when labelling ciliumidentity. All labels will still be used in identity determination" labels="map[k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name:kube-system]" subsys=crd-allocator
2024-01-26T00:05:57.462595124Z level=info msg="regenerating all endpoints" reason="one or more identities created or deleted" subsys=endpoint-manager
2024-01-26T00:05:57.462629809Z level=info msg="Invalid state transition skipped" containerID=93558b36a8 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3761 endpointState.from=waiting-for-identity endpointState.to=waiting-to-regenerate file=/go/src/github.com/cilium/cilium/pkg/endpoint/policy.go ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb line=611 subsys=endpoint
2024-01-26T00:05:57.462866690Z level=info msg="Allocated new global key" key="k8s:doks.digitalocean.com/managed=true;k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=default;k8s:io.cilium.k8s.policy.serviceaccount=konnectivity-agent;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=konnectivity-agent;" subsys=allocator
2024-01-26T00:05:57.462877879Z level=info msg="Identity of endpoint changed" containerID=93558b36a8 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3761 identity=46597 identityLabels="k8s:doks.digitalocean.com/managed=true,k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system,k8s:io.cilium.k8s.policy.cluster=default,k8s:io.cilium.k8s.policy.serviceaccount=konnectivity-agent,k8s:io.kubernetes.pod.namespace=kube-system,k8s:k8s-app=konnectivity-agent" ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb oldIdentity="no identity" subsys=endpoint
2024-01-26T00:05:57.462883264Z level=info msg="Waiting for endpoint to be generated" containerID=93558b36a8 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3761 identity=46597 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb subsys=endpoint
2024-01-26T00:05:57.550155103Z level=info msg="Rewrote endpoint BPF program" containerID=93558b36a8 datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=3761 identity=46597 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb subsys=endpoint
2024-01-26T00:05:57.550475668Z level=info msg="Successful endpoint creation" containerID=93558b36a8 datapathPolicyRevision=1 desiredPolicyRevision=1 endpointID=3761 identity=46597 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/konnectivity-agent-xjfkb subsys=daemon
2024-01-26T00:05:58.460132845Z level=info msg="regenerating all endpoints" reason="one or more identities created or deleted" subsys=endpoint-manager

Anything else?
This was initially discussed on Slack: https://cilium.slack.com/archives/C53TG4J4R/p1706254144830909
My best bet as to which change may have introduced a bug into Cilium is #29248 by @aanm. He also mentioned that there's another, currently still open PR #30170 (authored by @oblazek) that is related to the his PR I referenced earlier. Mentioning it here as well for the sake of completeness.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

ta Timo, nice catch! One suggestion would be to bisect between v1.14.4 and v1.14.5, and see if you truly end up in https://github.com/cilium/cilium/pull/29248. But the repro doesn't sound like a 5-minute exercise :).

he @julianwiedmann, thanks for the suggestion. You're right, it might involve some work.
I think I'll try to patch out the culprit change first from 1.14.5 and see if I'm lucky with that. If not, I'll start bisecting.
Will let you know once I know more.

So I went ahead and patched out #29251 (or, rather, its commits) from 1.14.5, which is the 1.14 back port variant from upstream #29248 that I suspected to be the culprit. I pushed the resulting branch to my fork (the top commit has the reverting patch).
I then built the Cilium agent as well as operator images to test in a custom cluster. In that setup, the RBAC-based reproduction does not work anymore, meaning I could not trigger the bug (similar to how I wasn't able to do that in v1.14.4).
I then created 500 clusters and checked for pods having the reserved:init label: I could not find a single one, i.e., all clusters came up good.
Just to be safe, I did the counter example and created several clusters on 1.14.5 (unpatched). Out of 100 cluster creates, I ran into two broken instances right away again.
Overall, I believe this confirms that the PR in question is the problematic one.
Worth highlighting that the back-porting PR #29251 has an additional commit (endpoint: fix panic in RunMetadataResolver due to send on closed channel) that the original upstream PR did not have. I had planned to run another test where I reverted all commits from #29251 except for that specific one to further distinguish which commit(s) would truly be responsible; unfortunately, the revert does not cleanly apply in that combination. I did no further attempts to address any conflicts since I felt I was really stepping out of my territory, potentially making things even worse.
Regardless, I think the above demonstrated that #29251 is related to the reported bug.
I can try to dig further into what the change in question did to hopefully understand where the essence of the problems lies, but I might need some pointers/guidance from folks more familiar with the code (possibly @aanm).

FWIW, here's the output of cilium endpoint log for an endpoint that suffers from the dangling reserved:init label:
Timestamp              Status    State                   Message
2024-02-12T09:43:01Z   OK        ready                   Successfully regenerated endpoint program (Reason: one or more identities created or deleted)
2024-02-12T09:43:01Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:43:01Z   OK        regenerating            Regenerating endpoint: one or more identities created or deleted
2024-02-12T09:43:01Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to one or more identities created or deleted
2024-02-12T09:43:00Z   OK        ready                   Successfully regenerated endpoint program (Reason: one or more identities created or deleted)
2024-02-12T09:43:00Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:43:00Z   OK        regenerating            Regenerating endpoint: one or more identities created or deleted
2024-02-12T09:43:00Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to one or more identities created or deleted
2024-02-12T09:25:52Z   OK        ready                   Successfully regenerated endpoint program (Reason: )
2024-02-12T09:25:52Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:52Z   OK        regenerating            Regenerating endpoint:
2024-02-12T09:25:52Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to
2024-02-12T09:25:51Z   OK        ready                   Successfully regenerated endpoint program (Reason: one or more identities created or deleted)
2024-02-12T09:25:51Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:51Z   OK        regenerating            Regenerating endpoint: one or more identities created or deleted
2024-02-12T09:25:51Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to one or more identities created or deleted
2024-02-12T09:25:50Z   OK        ready                   Successfully regenerated endpoint program (Reason: one or more identities created or deleted)
2024-02-12T09:25:50Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:50Z   OK        regenerating            Regenerating endpoint: one or more identities created or deleted
2024-02-12T09:25:50Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to one or more identities created or deleted
2024-02-12T09:25:50Z   OK        ready                   Successfully regenerated endpoint program (Reason: updated security labels)
2024-02-12T09:25:50Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:50Z   OK        regenerating            Regenerating endpoint: updated security labels
2024-02-12T09:25:50Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to updated security labels
2024-02-12T09:25:49Z   OK        ready                   Successfully regenerated endpoint program (Reason: one or more identities created or deleted)
2024-02-12T09:25:49Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:49Z   OK        regenerating            Regenerating endpoint: one or more identities created or deleted
2024-02-12T09:25:49Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to one or more identities created or deleted
2024-02-12T09:25:30Z   OK        ready                   Successfully regenerated endpoint program (Reason: retrying regeneration)
2024-02-12T09:25:30Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:30Z   OK        regenerating            Regenerating endpoint: retrying regeneration
2024-02-12T09:25:30Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to retrying regeneration
2024-02-12T09:25:30Z   Failure   ready                   Error regenerating endpoint: context canceled
2024-02-12T09:25:30Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2024-02-12T09:25:30Z   OK        regenerating            Regenerating endpoint: Initial build on endpoint creation
2024-02-12T09:25:30Z   OK        waiting-to-regenerate   Successfully regenerated endpoint program (Reason: updated security labels)
2024-02-12T09:25:30Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to Initial build on endpoint creation
2024-02-12T09:25:30Z   OK        regenerating            Regenerating endpoint: updated security labels
2024-02-12T09:25:30Z   OK        waiting-to-regenerate   Triggering endpoint regeneration due to updated security labels
2024-02-12T09:25:30Z   OK        ready                   Set identity for this endpoint
2024-02-12T09:25:30Z   OK        waiting-for-identity    Endpoint creation

Note the line
2024-02-12T09:25:30Z   Failure   ready                   Error regenerating endpoint: context canceled

where presumably, the API server wasn't immediately ready yet.
I thought the final waiting-for-identity sounded suspicious, but I see the same in the output in a good cluster where I patched out the suspected commits.


refactor(transformer): simplify TS export assignment transform

#3762  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Add Electron Output

This pull request wraps the kiwiirc output with electron.
Things left to do:

prevent opening of developer tools (https://github.com/kiwiirc/kiwiirc-desktop/blob/master/src/index.js#L147)
desktop item and icons

This is excellent. Didn't know you could produce electron so simply... You've blown my mind.
Can you remove the formatting changes, or add them in a separate commit?

Forced pushed the PR with auto formatting removed.

Is it possible to inline the patch into the flake rather than to include it as a separate file? I'm unsure if this is actually possible, but it would be much neater!

Yes, that's possible. I've updated the PR.


Textures/Models breaking when re logging

Hi, I have installed the plugin today and I have found that when a mob is spawn whilst a bedrock player is online the player can see the mob models and textures fine. If the player then logs out and rejoins the server the models and textures disappear and just a lone flying bat is placed where the mob should be. The models and Textures still show fine on Java clients when this happens so I think it is something on the Geyser side of things at fault. Grateful for any help you are able to provide.

latest version?

latest version?

It was the latest at the time of writing the original message. I have noticed you have released an update which I have downloaded and installed for all .jar and the issue seems to be improved in the sense that when a Bedrock player logs in now they appear as the base animal used for the mob so in this case it is a pig. Subsequent logging out and back in leaves ghost mobs (pigs) around the map where the original has wondered off. You can still see the mob walking around as the pig minus the model engine skin as well as the static ghost mobs.


create-react-app freezes at extracting "rxjs"

#ITS NOW SHOWING TWO LOADERS CAN U PLEASE HELP ME WITH IT ????

Please help ...

Hi @NamanKhurana,
Does this issue still happen, or can we close this?
If it's still happening, would you mind to provide more details such as:

steps to replicate
version of Create React App
OS version
node version
npm version

Thanks ☺
fyi @iansu


Pin karma, karma-mocha dev dependencies

Hi @Peripheral1994, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
For more information, see README.md.


What is the proper way to let ObjectType resolveField function know the upper query name

For example , below schema:
type Book {
  img: String!
  title: String!
  author: String!
  price: Int!
}

type Query{
  featured_book():[Book]
  best_seller_book():[Book]
}

query {
  featured_book {
    img
    title
    author
    price
  }
  best_seller_book {
    img
    title
    author
    price
  }
}

for featured_book query, I want the img field return big image, for best_seller_book query, I want the img field return normal image, I don't know how to let the Book object type know which upper query is calling it, so it can return different size image.I think use arguments might be an option, is there any other way besides that ?
Thank you!

Sounds a bit magical to me. When querying the same book, I'd expect the same result.
Why don't you simply create two fields, one for big and one for normal image? Or pass arguments to img field of type enum ImageSize?

@simPod , I'm trying to find a way that don't need to change the schema , or change it as little as possible.

All I'm saying that IMO it's wrong to return different results for the same query.

I don't see a problem for frontend guy to change few lines and modify his queries ;)

I don't think you can easily traverse the tree "up".
But in the featured_book and best_seller_book queries you can e.g. use the $context to set a state which is also available when the children are resolved.
But I don't know if the order is guaranteed, e.g. children nodes of featured_book evaluated direct after the query was resolved but before children of node best_seller_book are being processed.
Or when you resolve the individual book types form a query, you add some internal meta data to your own values/models itself to figure out how the should behave when the specific field is resolved.
Definitely magic/dirty.

Agree that this is a hack. Don't do it like this.  This is against "GraphQL way".
As they said, the schema/query must be changed to make it work as needed. Changing schema doesn't mean breaking it. You could add arguments to field img which will be totally backward-compatible.
In general, I don't see any reason why frontend guys would be against this in favor of dirty hacks. Maybe there is a lack of communication. If it is the case - invite them here to discuss as it doesn't make any sense for me.

Thank you guys. Will try to communicate with frontend guy about this.


Publish container service 2019-10-01 api version

Latest improvements:
Included in 2019-10-01 api version:

added private FQDN (PR #7430 )
updating sdk tags (PR #7550 )

Both PRs have been approved. This PR is to merge from dev branch to master branch.
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[x] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

Looks good to me, please wait for the ARM team's review


TLS Version issue

building the box doesn't work anymore.
after running packer fix and continuing with a new file one find that there's a TLS issue during download.
Seems to be described in saltstack issue 56276
this is what you'd see happening:
    virtualbox-iso: C:\Users\vagrant>powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))"  0<NUL
==> virtualbox-iso: Exception calling "DownloadString" with "1" argument(s): "The request was aborted: Could not create SSL/TLS secure
==> virtualbox-iso: channel."
==> virtualbox-iso: At line:1 char:1
==> virtualbox-iso: + iex ((new-object net.webclient).DownloadString('https://chocolatey.or ...
==> virtualbox-iso: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> virtualbox-iso:     + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
==> virtualbox-iso:     + FullyQualifiedErrorId : WebException
==> virtualbox-iso:
==> virtualbox-iso: Provisioning step had errors: Running the cleanup provisioner, if present...
==> virtualbox-iso: Cleaning up floppy disk...
==> virtualbox-iso: Deregistering and deleting VM...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored after 9 minutes 20 seconds: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]

I tried their workaround with the extra parameter to -Command.
The relevant string is [Net.ServicePointManager]::SecurityProtocol=[Net.SecurityProtocolType]::Tls12;
This needs to be added to the download calls in chocolatey.bat and vm-guest-tools.bat.
I don't know (yet) if it would also be possible to inject the registry keys as in their other suggestion.
That would set the TLS default to 1.2 which breaks the standard Win2016 behaviour but otherwise seems a very good thing[tm].

Also tried with the windows update provisioner, that is a nice solution, but you would probably need a proxy if you use that more often.
"provisioners": [

 {

 "type": "windows-shell",

{

   "type": "windows-update"

},
{
"execute_command": "{{ .Vars }} cmd /c "{{ .Path }}"",
"scripts": [
"scripts/vm-guest-tools.bat",
"scripts/chocolatey.bat",
"scripts/chocopacks.bat"

 ]

 ],

 "type": "windows-shell"

},
{

 "type": "windows-shell",
 "execute_command": "{{ .Vars }} cmd /c \"{{ .Path }}\"",
 "scripts": [
   "scripts/pin-powershell.bat",
   "scripts/set-winrm-automatic.bat"

 ]

 ],

 "type": "windows-shell"

},
{

 "type": "powershell",
 "scripts": [
   "scripts/disable-screensaver.ps1",
   "scripts/set-powerplan.ps1",
   "scripts/postInstall.ps1",
   "scripts/postSetup.ps1"

 ]

 ],

 "type": "powershell"

},
{
"type": "windows-restart"
}
],


Warning: The app gradle file must have a dependency on com.google.firebase:firebase-core for Firebase services to work as intended.

Hello!
I love this plugin, however I see the following warning when I build for android:
Warning: The app gradle file must have a dependency on com.google.firebase:firebase-core for Firebase services to work as intended.
And for IOS:
ld: library not found for -lFirebaseCore
clang: error: linker command failed with exit code 1 (use -v to see invocation)
** BUILD FAILED **
Thanks!

This is just a warning. According to official docs the core dependency can be absent (
https://firebase.google.com/docs/cloud-messaging/android/client)

fyi: the official docs also state this:

Firebase now requires the app gradle file to explicitly list com.google.firebase:firebase-core as a dependency for Firebase services to work as expected.
https://developers.google.com/android/guides/releases#may_23_2018

so, is there a solution ?

so, is there a solution ?

I added a line implementation 'com.google.firebase:firebase-core:16.0.5' which fixed the warning

That fixed it!

Version 1.2 now has explicit dependency on firebase-core

But when use 16.1.0 then this warning is occuring also...and 16.1.0 is the lastest one.

someone help me?

implementation 'com.google.firebase:firebase-core:16.0.5

thanks, this fixed the warning

so, is there a solution ?

I added a line implementation 'com.google.firebase:firebase-core:16.0.5' which fixed the warning

where i must to add this line? sorry am a newbie

so, is there a solution ?

I added a line implementation 'com.google.firebase:firebase-core:16.0.5' which fixed the warning

where i must to add this line? sorry am a newbie

add it in your app level build.gradle file in dependencies.

so, is there a solution ?

I added a line implementation 'com.google.firebase:firebase-core:16.0.5' which fixed the warning

where i must to add this line? sorry am a newbie

add it in your app level build.gradle file in dependencies.

which line dependencies?
I've been in the last line but failed

OMG !!! when I added this  "implementation 'com.google.firebase:firebase-core:16.0.5' ",in a new line,my error got automatically solved,Thans a lot.

Hey users  this is just a warning .you don't need to worry about it But, if you want to resolve the warning then just add this line      implementation 'com.google.firebase:firebase-core:16.0.7'
Or you can Use the latest version for your dependencies
such as :
implementation 'com.google.firebase:firebase-auth:16.1.0'
implementation 'com.google.firebase:firebase-database:16.1.0'
implementation 'com.google.firebase:firebase-storage:16.1.0'
Hope your problem get solved by this

so, is there a solution ?

I added a line implementation 'com.google.firebase:firebase-core:16.0.5' which fixed the warning

where i must to add this line? sorry am a newbie

in build.gradle(app)
dependencies
{
//HERE
implementation 'com.google.firebase:firebase-core:16.0.5
}

Somehow unfortunately I didn't get my solution using only "implementation 'com.google.firebase:firebase-core:16.0.5' "
after searching a lot I finally got my solution following this Please Change your Firebase and Google Library to same version
If you use your Assistant tool of Android Studio for automatically implement dependencies , Its possible to mismatch the version number. So in that case just make sure you use the same version of google play services and firebase.

Use the latest version from the developer docs as at the time of writing the latest versions were
implementation 'com.google.firebase:firebase-database:16.1.0'
implementation 'com.google.firebase:firebase-core:16.0.8'
https://firebase.google.com/support/release-notes/android

someone help me?
Edit
I found a solution, I added the plugin cordova-plugin-firebase-core and solved it.

Hey,
I have the same Problem. How can i add this plugin?


Added retry behavior to seshat registration.

Codecov Report

Merging #94 into master will decrease coverage by 0.6%.
The diff coverage is 46.15%.

@@            Coverage Diff             @@
##           master      #94      +/-   ##
==========================================
- Coverage   90.71%   90.11%   -0.61%
==========================================
  Files          35       35
  Lines        2661     2681      +20
  Branches      164      167       +3
==========================================
+ Hits         2414     2416       +2
- Misses         87      104      +17
- Partials      160      161       +1

Impacted Files
Coverage Δ

src/config.c
79.81% <33.33%> (-1.32%)
:arrow_down:

src/conn_interface.c
75.36% <47.82%> (-7.33%)
:arrow_down:

tests/test_client_list.c
90.76% <0%> (-6.16%)
:arrow_down:

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 ef52fb7...b029551. Read the comment docs.


Enhancementbuild hash table with new thread, as non-vec…

info
in HashJoinNode, build hash table with new thread, so that child(0) can open() async. in this way,  hash table from different HashJoinNode in the plan tree can build at same time.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (No Need)
Has document been added or modified: (No Need)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

2 issues:

I think you forget to handle runtime filter in vectorized hash join
We should bring some performance test to see if this do improve the performance.


Ipbanlist fixes

Fixes some concurrency issues in the IPBanList class:

It calls HashSet#contains() from outside a synchronized block: it might not be able to catch a change made by a different thread
The bannedIps field is not volatile even though multiple threads can set it to a new instance from loadBannedIps(): other threads might not see the updated instance

There are also some minor code improvements suggested by IntelliJ

looks good, some remarks:

volatile could be removed again if the Set is made final (and cleared + reused in loadBannedIps())
loadBannedIpsIfNeeded is only called with forceLoad set to false -> opportunity to be simplified.

sidenote:
I noticed that the IPBanList is indirectly polling the modification time of the file via isBanned(). Maybe it could be polled only once per second? I don't know the exact requirements for this feature however. Maybe @snoopdave could help.

Hello Michael, thanks for the review :)

volatile could be removed again if the Set is made final (and cleared + reused in loadBannedIps())

In order to reuse the Set that way, I think we need to clear and populate it somehow atomically, which I'm not sure how, because otherwise it will introduce a time window where isBanned() gets called while the Set is empty which sounds like some kind of vulnerability. Based on that, I guess using volatile this way is kind of reasonable

loadBannedIpsIfNeeded is only called with forceLoad set to false -> opportunity to be simplified.

Agreed. Removed at a5417a5

In order to reuse the Set that way, I think we need to clear and populate it somehow atomically, which I'm not sure how, because otherwise it will introduce a time window where isBanned() gets called while the Set is empty which sounds like some kind of vulnerability. Based on that, I guess using volatile this way is kind of reasonable

you are right. This would require a temporary map and iterating through the concurrent map which causes also issues.
My initial thought was to keep volatile but make the map immutable (swap on write), since its rarely updated but read in every request.  But I don't know how the file is used in practice - so lets keep your solution.

loadBannedIpsIfNeeded is only called with forceLoad set to false -> opportunity to be simplified.

Agreed. Removed at a5417a5

awesome
another thing:
are the new test dependencies needed? The test seems simple enough to do fine with the standard junit asserts. I would try to avoid adding new dependencies unless its worth it.

looks good, some remarks:

volatile could be removed again if the Set is made final (and cleared + reused in loadBannedIps())
loadBannedIpsIfNeeded is only called with forceLoad set to false -> opportunity to be simplified.

sidenote:
I noticed that the IPBanList is indirectly polling the modification time of the file via isBanned(). Maybe it could be polled only once per second? I don't know the exact requirements for this feature however. Maybe @snoopdave could help.

Even once per second seems a bit excessive.

are the new test dependencies needed? The test seems simple enough to do fine with the standard junit asserts. I would try to avoid adding new dependencies unless its worth it.

Removed Mockito from pom.xml at 15bf473 , I thought I would need it but it turned out I didn't for now.
As for AssertJ, I'd like to keep it as it's much better than standard ones.

@nuzayats thanks!
I do like fluent interfaces too, just that i don't feel that it adds enough benefits in this particular case, to justify a new test dependency (just for one small junit test).

LGTM

i don't feel that it adds enough benefits in this particular case, to justify a new test dependency (just for one small junit test).

For this one at least it adds some benefit I think for example:
assertThat(readIpBanList()).containsOnly("<IP_ADDRESS>");
The standard assertion APIs don't provide such a collection verification if I'm not mistaken. Also to me having a new test dependency is not such a big deal but is there something which concerns you about it?

i don't feel that it adds enough benefits in this particular case, to justify a new test dependency (just for one small junit test).

For this one at least it adds some benefit I think for example:
assertThat(readIpBanList()).containsOnly("<IP_ADDRESS>");
The standard assertion APIs don't provide such a collection verification if I'm not mistaken.

assertTrue(list.contains("<IP_ADDRESS>"));
assertTrue(list.size() == 1);

or if you prefer one line
assertEquals(List.of("<IP_ADDRESS>"), list);

Also to me having a new test dependency is not such a big deal but is there something concerning about it?

Its far less problematic than a runtime dependency - i agree. Still, it has to pull its weight. Old projects tend to accumulate dependencies and removing them is always a little bit more difficult than adding new ones. More dependencies mean more maintenance time spent to keep them updated and detect abandoned projects to migrate away from.
The red flags here are that this library is only used by a single (small) test, and it is also not convincing to me that it is really necessary for that test.
However the impact is little (and it has no transitive dependencies), so if you really want it, I am ok to merge your changes. (thanks again for the contribution btw, esp also for adding a test case)

Removed AssertJ at 9dca2da .
But it sounds like I will have to stick with the basic or outdated assertion APIs in Roller development unless there is a chance to write substantial amount of new code and tests even though there is a much better assertion library available already today. The points you raised are valid but writing unit tests with fundamental assertTrue() and assertEquals() for collection verifications in 2021 is kind of sad :(

thanks for understanding. I am not opposed to AssertJ, if we have extensive collection based tests in future we can still add it so we get some proper use out of it. But maybe not for two lines delta :)


Prevent Deadlocks

        public virtual bool Post(SlackMessage slackMessage)
        {
            var result = PostAsync(slackMessage);
            return result.Result;
        }

Although one would wonder why the synchronous method above would be called from an async task, if where called it could result in a deadlock.
https://blog.stephencleary.com/2012/07/dont-block-on-async-code.html
Consider rewriting it like this:
        public virtual bool Post(SlackMessage slackMessage)
        {
            var result = PostAsync(slackMessage);
            return result.GetAwaiter().GetResult();
        }
        // Or a one liner :)
        public virtual bool Post(SlackMessage slackMessage)
          => PostAsync(slackMessage).GetAwaiter().GetResult();

https://blog.stephencleary.com/2014/12/a-tour-of-task-part-6-results.html

Having said that your probably okay just using the .ConfigureAwait(false) in the Post method.

Hi @bronumski thanks for the info, i like your original approach since it is clearer what is going on, will consider updating it soon :+1:


If i play with old version i cant look up or down but in latest version it is not detecting my controllers

What controller are you using?

That's  pc controllers
Dx Usb joysticks

What controller are you using?

That's pc controllers
Dx USB joysticks

You can't use a joystick, only gamepads.

You can't use a joystick, only gamepads.

Same issue with gamepad either
Plz help If you want i can send you screen shots

Which gamepad are you using?

Which gamepad are you using?

thats pc controllers
Wired Vibration Gamepad PC USB Controller Gampad  (White)

Which gamepad are you using?

Double Shock pc Controllers
That;s pc controllers
and on old version i can play easily but cant look up or down

Which gamepad are you using?

Help me plz


Replace almost all uses of 'syscall' with 'unix' pkg.

golang.org/x/sys/unix package is replacement for syscall which has
been deprecated since Go 1.4.

Deprecated: this package is locked down. Callers should use the corresponding package in the golang.org/x/sys repository instead. That is also where updates required by new systems or versions should be applied. See https://golang.org/s/go1.4-syscall for more information.

While the changes do touch a lot of files, all of the modifications are
simply replacing imports of the syscall package, with x/sys/unix
implementations. No functionality changes, so no new tests added.
There is one case of syscall remaining in the cilium dnsproxy. There
is currently no good replacement listening for UDP traffic.
Fixes: https://github.com/cilium/cilium/issues/10116
Signed-off-by: Joshua Roppo<EMAIL_ADDRESS>

This change is

Coverage decreased (-0.01%) to 44.529% when pulling adeeb58ba5eaa6a7749c4a820aea697d03ef5abd on Ropes:kind/cleanup/ropes/replace/syscall/w/unix/pkgs into bdb6d71aed2e52f44b57a850ef773918a5a57f63 on cilium:master.

test-me-please

Alright, I've been able to verify the test failure locally. Also checked the prior commit to make sure that there wasn't some upstream instability which sneaked through.
Very curious what has actually been uncovered here. I'll start investigating syscall vs unix package constants, perhaps there is a difference between values with the same name? Seems very peculiar if that were the case, but the change surface is rather small.

@Ropes As far as I can tell, there's only one failure which looks like the known CI flake #9869 :
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/17085/testReport/junit/Suite-k8s-1/17/K8sPolicyTest_Basic_Test_TLS_policy/
So if the rest of the build (including the full testsuite with the k8s-1.11+net-next+kubeproxy-free) passes then this should be good enough from a testing perspective. Just need reviews from the codeowners.

Since there aren't really any logic changes in this PR, it'll be easier to refactor post #10058 & #10117 get merged. When they merge I'll have a second pass and get it ready again. #10117 is similar to what this changeset.. just didn't pick up using unix package.

Just force pushed a fix for a code conflict with master.

test-me-please


Mutation

Mutate a randomly generated decision tree.

Implemented in:

0810faacceb4348336d8f25d9a9e54b960b2e05f (change class of leaf node)
102210fedc68ae1a5291605e37a797aac7327cf2 (exchange class for tree)
b508f99f09981e0631d1ecf0bdf83c8a89036e8b (change attribute of mid-tree node)
ff6d60d39dbecef897197fd272b4fc1a092b7ae1 (change attribute value)
ed039548a2087c21e88b9b06b9767d3aaff2c579 (exchange tree for class)
490bed246a19d07aeec1cffeda87735e9dcab91f (exchange tree for tree)


import GUPImage fails !

Hi
I am using latest Xcode 9 beta 4.
Importing GPUImage files - even in the example project for simple video filter
Please help!

Could it be some kind of naming issue with the framework??

Is this after actually building your project? The Swift compiler reports that before the module has been built, which is a bit of a false positive. Try building the project, which should get rid of this error.

Tried re-building of course but didn't work.
Tried clearing, erasing Xcode cache but nothing. It refuses to recognize it

Try with one of the projects in the examples directory. Last I checked, those all built just fine under Xcode 9 beta 3, but I haven't had the time to check everything under beta 4.
Make sure that you've set GPUImage as a build dependency for the application to make sure it is built before the application is.
One thing that I see in your screenshot above is GPUImage at the same level as your application, which doesn't seem right. If you have GPUImage open in another workspace or project, that could be preventing it from building in your current project. You can only have a framework open in one Xcode project at a time.

Hello there, I just wanna add there might be a problem when you have different configurations on the project. GPUImage2 counts with the fact that there is debug and release configuration. So it copies itself in the derivate data folder named debug/release. I have configurations named develop, testing and production so i had to add them in GPUImage too so the .framework stuff is copied in the correct folders.


Roll Flutter Engine from 8ffc705a55d5 to f975f20290e0 (3 revisions)

https://github.com/flutter/engine/compare/8ffc705a55d5...f975f20290e0
2023-11-01<EMAIL_ADDRESS>Roll Skia from f1983b5af2ef to b7ac9da3e5ac (1 revision) (flutter/engine#47548)
2023-11-01<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from x2NzYMNhyodIwDl0I... to Lrg_lElxg0BmYp97-... (flutter/engine#47547)
2023-11-01<EMAIL_ADDRESS>Roll Skia from 83d6345dd3c2 to f1983b5af2ef (2 revisions) (flutter/engine#47541)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from x2NzYMNhyodI to Lrg_lElxg0Bm
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


beginListActiveSessionsAndWait() does not return Sessions even though the api called by the sdk does return Sessions

Package Name: @azure/arm-network
Package Version: 30.2.0
Operating system: Windows
[x] nodejs

version: 16.15.0

[x] browser

name/version: Chrome/112.0.5615.138

[x] typescript

version: 4.9.5

Is the bug related to documentation in

[ ] README.md
[x] source code documentation
[x] SDK API docs on https://docs.microsoft.com

Describe the bug
When using "beginListActiveSessionsAndWait" of the networkclient as described in Microsoft Docs or azure-sdk-for-js sample file i do not get back any sessions as a result, even though in the networking tab the sessions do appear.

-> I have also tried it when more than one session was active at the bastion - still the function of the sdk returned an empty array
Also in the Azure portal the sessions are displayed:

To Reproduce
Steps to reproduce the behavior:

implement returnsAListOfCurrentlyActiveSessionsOnTheBastion() function as described in the docs
create a bastion
create vm
connect to vm via bastion
run the implemented returnsAListOfCurrentlyActiveSessionsOnTheBastion()

Expected behavior
The SDK function should return the same result as the API returns
Screenshots

Additional context
Add any other context about the problem here.

Thank you @MichaMican for such a nicely detailed issue description.

I can reproduce the result of your issue and am looking for the cause

Hi @kazrael2119 - were you able to find the root cause? This issue is currently a blocker for us and we need to decide if we try to implement the pagination & session acquiring on our own or if this is beeing fixed in the foreseeable future

beginListActiveSessionsAndWait

In swagger https://github.com/Azure/azure-rest-api-specs/blob/efd49b89cbc6b44f81056affc40cb7b96b520474/specification/network/resource-manager/Microsoft.Network/stable/2022-11-01/bastionHost.json#L874 the resonse should contains "value" and "nextlink" ,
and in "value", it contains your expected behavior:https://github.com/Azure/azure-rest-api-specs/blob/efd49b89cbc6b44f81056affc40cb7b96b520474/specification/network/resource-manager/Microsoft.Network/stable/2022-11-01/bastionHost.json#L806
see the example response in swagge:https://github.com/Azure/azure-rest-api-specs/blob/efd49b89cbc6b44f81056affc40cb7b96b520474/specification/network/resource-manager/Microsoft.Network/stable/2022-11-01/examples/BastionSessionsList.json#L10
but actually, the response body doesn't follow this chema which doesn't have nextlink parameter, I think this bug is causeb by this

@qiaozha @kazrael2119 Any updates on this?

Service backend needs to fix this mismatch. I have been trying to contact service team, there's not much we can do in the SDK side. If you like, you may open a support ticket.

Hi @qiaozha i am a bit confused why this should be a backed issue? As shown in the screenshots the backend returns the correct values, and the azure portal frontend also can deal with it correctly - So I would be very suprised if this is not fixable within the SDK

This operation response violates the fifth requirement here.
https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#202-accepted-and-location-headers
portal must have some sort of fallback logic to the original-uri, but the guideline has specifically asked the service backend to return exact the same response if the operation had been executed synchronously in the polling request when the operation is complete.

@MichaMican, The raw response is unicode encoded. And the response mey be not match with the response defined in swagger.That's why we got unexpected  value: [].

Thanks for the clarification - Can you move that forward to the respective team internally?

“service attention” label is added, we only can wait for service feedback

Any update on this?

Any update on this? (@qiaozha )

I will ping service team again, but no promises here. Sorry. You probably should open a support ticket https://azure.microsoft.com/en-us/support/create-ticket which might get your issue resolved sooner.

@MichaMican Since the final state is set via 'location', have you tried implementing a LRO poll on location? Using REST client, that returns the appropriate results and should unblock you temporarily while we investigate and make a permanent fix

@abhi7860 Will take a look into it thanks for the heads up.
However a library native approach is preferred for obvious reasons - so keep me posted on the status of the fix.

@MichaMican Did this ever work for you before and recently stopped working? Perhaps, because of a package upgrade?

Hi @abhi7860 - No unfortunately not to my knowledge - I just installed the package for the first time and it did not work so I opened this issue.

https://github.com/Azure/azure-sdk-for-js/blob/main/documentation/MIGRATION-guide-for-next-generation-management-libraries.md#long-running-operations
I see that because of some recent changes devs need to implement LRO poller. I wonder if the SDK is not responding because of that

We should already eliminate the possible cause from the SDK side before reporting to service side @abhi7860 https://github.com/Azure/azure-sdk-for-js/issues/25671#issuecomment-1556645637 this is the root cause based on our investigation, I think it should be clear for you, feel free to let us know if it isn't.

Any updates on this? @kazrael2119 @qiaozha @abhi7860  - The problem is still persistent and in my opinion there is no simple workarround for this - i basically would have to implement the calling of the api completely on my own, hence i'd have to ditch the library alltogether


Add my graph please?

I had write simple graphShower for https://narodmon.ru data
Can you add my code to youre firmware, please?
FoxGraph.zip

Added.
For more contributions, you can start a pull request with your mods to be added to firmware.
You can also add your name on your app.


word-spacing doesn't get adjusted properly in Safari

I get fine results for all browsers except Safari (mobile and desktop). I know it doesn't have subpixel font-scaling, but the adjustement via word-spacing could be much more accurate. Mostly it's left untouched. I see many cases of inaccurate adjusted lines, where manual word-spacing leads to much better results.

I fixed it. I'll create a pull request later.


Design kit access request

Thanks for your interest in the IBM.com Design kits!
We are in a closed adoption phase at the moment. Please answer the following questions to help us better understand your interest. Someone from Carbon for IBM.com will reach out to you soon regarding your request for access.

Which team are you on?
iX Studio Duesseldorf / Germany

What experience are you designing for?
ix Dach webpage

What platform is your experience on? (ie. Drupal, Wordpress, etc)
Drupal

Please list a point of contact for:
Offering manager Markus Dietrich
Design lead Alexander de Babtistis
Development lead Michael Wolfram

Any additional information you'd like to share about your project

Hi @bypeter-ecxio would you mind sharing your IBM email so I can add you to the design kit folder?
Thank you!


slices disappears if when i do a get for missing data

so basically i have something like
type A struct{
 a []int
 AA []int
}

someA := &A{}
someA.a = make([]int,10)
someA.AA = make([]int, 10)
cur, _ := r.table('sometable').get(1).run(session)
cur.One(someA)

doing this gives the following result
len(someA.a) == 0
len(someA.AA) == 10

Is this intended? or am i doing something wrong?

GoRethink will zero any fields when decoding the result into a struct. The reason for this is that if you were reusing the same variable for each iteration of Next you wouldnt want data from a previous iteration to still be there in future iterations.

OK got it!


stackimpact python agent is causing threading issues

archlinux python 3.6 x64
self._socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
self._socket.connect((address, port))
self._socket.setblocking(1)
..... etc etc
all works fine
as soon as i add right at the top of the script
agent = stackimpact.start(
agent_key = '...............................',
app_name = 'abc.connect')
my app tries to send stuff before it finished receiving and so on and it all goes south.
when my app is supposed to have a serial behavior, send receive send more receive send receive.. no parallel stuff and definitely not send before it finished receiving.
is there any way to run stackimpact in an app that uses socket lib ?

My assumption is that signals that profilers rely on interfere with blocking operations. Are you handling errors from blocking calls, such as EINTR? To test if that's the case, you can try to start the agent with disabled profilers by setting the flags cpu_profiler_disabled, allocation_profiler_disabled, block_profiler_disabled to False.


⚠ Bofrost.fr has degraded performance

In 7171aef, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1408 ms

Resolved: Bofrost.fr performance has improved in 62b5ed3 after 8 minutes.


Can you provide more demos

I want to learn more examples

I want to learn more examples
I think current repo provides sufficient ESP8266 examples.  Do you mean ESP32 examples? if you want to see maore ESP32 examples, you could refer to my repository (although I used another homekit library from younghyunjo, you could still find useful examples from my repo).
You can find my esp32-homekit here.

I want to know more types of cases, such as air conditioners, windows, thermostats

@CHNleing download the HomeKit Specification and indulge yourself.

@maximkulkin Thank you very much, I found Homekit Accessory Protocol Specification from Apple official website.
I am trying to read it.