bundle : displacement of circle label

Hi,
I think it's a small issue/question that I propose, I am using the bundle visualization. as label, I use "-" and I changed the css style as such:
.node {
  font: 300 11px "Helvetica Neue", Helvetica, Arial, sans-serif;
  fill: #bbb;

  font-size: 36px;
  font-weight: bold;
  line-height: 26.4px;
}

mainly to have a nice and big "-"
but I observe a little displacement of the circle label, like the diameter of the label circle position and angle is not exactly define the same way on each side of the wheel.
So I see that half way, the label are reversed but I don't see how this could produce this artifact. May be someone encounter the issue already
see figure https://1drv.ms/f/s!ApPwUjpLIL5sioEkiYbnMcUjASQ1kg
especially at the bottom it's visible
hope you have a clue about that :)
Roselyne

Please use Stack Overflow tag d3.js to ask for help. Although I make an effort to assist everyone that asks, I am not always available to provide help promptly or directly. Stack Overflow provides a better collaborative forum for self-help: tens of thousands of D3-related questions have already been asked there, and some answered questions may be relevant to you.
When asking for help, please include a link to a live example that demonstrates the issue, preferably on bl.ocks.org. It is often impossible to debug from code snippets alone. Isolate the issue and reduce your code as much as possible before asking for help. The less code you post, the easier it is for someone to debug, and the more likely you are to get a helpful response.
If you have a question about D3’s behavior and want to discuss it with other users, also consider the d3-js Google Group or joining the d3-js Slack.
Thank you! 🤗


Missing process to report a problem for build tools-only installation

The instructions all rely on having VS installed. I only have the build tools installed as I use JetBrains Rider as my primary IDE.
(I'm having the same reboot issue as https://developercommunity.visualstudio.com/content/problem/30007/visual-studio-installer-always-asking-for-reboot.html with install version 2.4.1080.1113. The PowerShell script solution proposed there did not work either.)

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

ID: 2386e67e-a67b-de55-db57-e29a83dcb410
Version Independent ID: 6247fba9-4255-9a59-c206-0e8547e12335
Content: How to report a problem with Visual Studio - Visual Studio
Content Source: docs/ide/how-to-report-a-problem-with-visual-studio.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @seaniyer
Microsoft Alias: seiyer

@mattr Thanks for your input. We'll review the docs for improvement. You can file an issue on build tools online at Developer Community site here.
https://developercommunity.visualstudio.com/content/problem/post.html?space=62
It is simply filling out the form on that page. VS IDE is not needed.  I hope that helps.

Sean


Change [IU]256 conversion host functions to take Val

What
Follow up on https://github.com/stellar/rs-soroban-env/pull/889.
Changes the [IU]256 conversion functions from Object to Val.
Fixes some broken calibration tests.
Why
https://github.com/stellar/rs-soroban-env/pull/889#issue-1772336785 explains the reasons for exposing Val instead of Object in the arithmetic host functions for the SDK.  It also added helper functions to allow constructing from u32.
The reasons same apply for the conversion functions, which allows the guest to construct a general [IU]256 from 256 bits (either via a bytes objects or four [IU]64), and also taking advantage of the small-number optimization from the host side.
Known limitations
[TODO or N/A]

Discussed with @graydon , not a totally necessary change. Closing.


Interactive tests shows nothing [WSL2 Ubuntu 20.04]

I'm using

WSL2 Windows 11
Anaconda 3

I've installed both habitat-lab and habitat-sim (conda install) following the README up until the tests. The non-interactive tests in the habitat-lab are working fine. But the Interactive tests of both habitat-lab (interactive_play) and habitat-sim (habitat_viewer) show black. I've read that habitat doesn't support Windows or WSL (don't know how it is for VMWare) but it installed fine.

Any insight is welcome

Looks like 0ns GPU duration means either nothing to render, or no rendering happening. Console logs would be necessary to know more.

It somehow runs correctly, very very rarely. I don't see any apparent difference between failing and successful logs.
It automatically uses my intel graphic as the renderer even after i change it to nvidia through MESA (though i'm not an expert myself so i might have missed something), but i doubt this is the reason.
This is the console log of the habitat viewer.
Platform: can't get Xft.dpi property for virtual DPI scaling, falling back to physical DPI
Renderer: D3D12 (Intel(R) UHD Graphics 770) by Microsoft Corporation
OpenGL version: 4.1 (Core Profile) Mesa 22.2.0 - kisak-mesa PPA
Using optional features:
    GL_ARB_vertex_array_object
    GL_ARB_ES2_compatibility
    GL_ARB_separate_shader_objects
    GL_ARB_robustness
    GL_ARB_texture_storage
    GL_ARB_invalidate_subdata
    GL_ARB_texture_storage_multisample
    GL_ARB_multi_bind
    GL_ARB_direct_state_access
    GL_ARB_get_texture_sub_image
    GL_ARB_texture_filter_anisotropic
    GL_KHR_debug
Using driver workarounds:
    no-layout-qualifiers-on-old-glsl
    mesa-dsa-createquery-except-pipeline-stats
    mesa-forward-compatible-line-width-range
[04:32:38:779433]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Dataset>: Proposing JSON name : default.scene_dataset_config.json from original name : default| This file does not exist.
[04:32:38:779497]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (capsule3DSolid:capsule3DSolid_hemiRings_4_cylRings_1_segments_12_halfLen_0.75_useTexCoords_false_useTangents_false) created and registered.
[04:32:38:779530]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (capsule3DWireframe:capsule3DWireframe_hemiRings_8_cylRings_1_segments_16_halfLen_1) created and registered.
[04:32:38:779554]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (coneSolid:coneSolid_segments_12_halfLen_1.25_rings_1_useTexCoords_false_useTangents_false_capEnd_true) created and registered.
[04:32:38:779575]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (coneWireframe:coneWireframe_segments_32_halfLen_1.25) created and registered.
[04:32:38:779594]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cubeSolid:cubeSolid) created and registered.
[04:32:38:779612]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cubeWireframe:cubeWireframe) created and registered.
[04:32:38:779633]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cylinderSolid:cylinderSolid_rings_1_segments_12_halfLen_1_useTexCoords_false_useTangents_false_capEnds_true) created and registered.
[04:32:38:779654]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cylinderWireframe:cylinderWireframe_rings_1_segments_32_halfLen_1) created and registered.
[04:32:38:779675]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (icosphereSolid:icosphereSolid_subdivs_1) created and registered.
[04:32:38:779694]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (icosphereWireframe:icosphereWireframe_subdivs_1) created and registered.
[04:32:38:779714]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (uvSphereSolid:uvSphereSolid_rings_8_segments_16_useTexCoords_false_useTangents_false) created and registered.
[04:32:38:779733]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (uvSphereWireframe:uvSphereWireframe_rings_16_segments_32) created and registered.
[04:32:38:779753]:[Metadata] AssetAttributesManager.cpp(110)::AssetAttributesManager : Built default primitive asset templates : 12
[04:32:38:779873]:[Metadata] SceneDatasetAttributesManager.cpp(35)::createObject : File (default) not found, so new default dataset attributes created  and registered.
[04:32:38:779886]:[Metadata] MetadataMediator.cpp(120)::createSceneDataset : Dataset default successfully created.
[04:32:38:779903]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Physics Manager>: Proposing JSON name : ./data/default.physics_config.json from original name : ./data/default.physics_config.json| This file does not exist.
[04:32:38:779925]:[Metadata] PhysicsAttributesManager.cpp(26)::createObject : File (./data/default.physics_config.json) not found, so new default physics manager attributes created and registered.
[04:32:38:779939]:[Metadata] MetadataMediator.cpp(203)::setActiveSceneDatasetName : Previous active dataset  changed to default successfully.
[04:32:38:779952]:[Metadata] MetadataMediator.cpp(175)::setCurrPhysicsAttributesHandle : Old physics manager attributes  changed to ./data/default.physics_config.json successfully.
[04:32:38:779957]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage :  and dataset : default which is currently active dataset.
[04:32:38:785609]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and dataset : default which is currently active dataset.
[04:32:38:785651]:[Metadata] AttributesManagerBase.h(321)::loadAllTemplatesFromPathAndExt : <Object Template> : ParsingObject Template: Cannot find data/objects/example_objects as directory or data/objects/example_objects.object_config.json as config file. Aborting parse.
[04:32:38:785680]:[Default] viewer.cpp(979)::Viewer : Scene Dataset Configuration file location : default | Loading Scene : Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:785687]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and dataset : default which is currently active dataset.
[04:32:38:801151]:[Metadata] MetadataMediator.cpp(297)::getSceneInstanceAttributesByName : Dataset : default has no preloaded SceneInstanceAttributes or StageAttributes named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb so loading/creating a new StageAttributes with this name, and then creating a SceneInstanceAttributes with the same name that references this stage.
[04:32:38:801203]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Stage Template>: Proposing JSON name : Download/scene_datasets/habitat-test-scenes/apartment_1.stage_config.json from original name : Download/scene_datasets/habitat-test-scenes/apartment_1.glb| This file does not exist.
[04:32:38:801258]:[Metadata] AbstractObjectAttributesManagerBase.h(184)::createObject : File (Download/scene_datasets/habitat-test-scenes/apartment_1.glb) exists but is not a recognized config filename extension, so new default Stage Template attributes created and registered.
[04:32:38:801295]:[Metadata] SceneDatasetAttributes.cpp(47)::addNewSceneInstanceToDataset : Dataset : 'default' : Stage Attributes 'Download/scene_datasets/habitat-test-scenes/apartment_1.glb' specified in Scene Attributes exists in dataset library.
[04:32:38:801310]:[Metadata] SceneDatasetAttributes.cpp(84)::addNewSceneInstanceToDataset : Dataset : 'default' : Lighting Layout Attributes 'no_lights' specified in Scene Attributes but does not exist in dataset, so creating.
[04:32:38:801317]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Lighting Layout>: Proposing JSON name : no_lights.lighting_config.json from original name : no_lights| This file does not exist.
[04:32:38:801336]:[Metadata] LightLayoutAttributesManager.cpp(36)::createObject : File (no_lights) not found, so new default light layout attributes created and registered.
[04:32:38:801352]:[Sim] Simulator.cpp(237)::createSceneInstance : Navmesh file location in scene instance : Download/scene_datasets/habitat-test-scenes/apartment_1.navmesh
[04:32:38:801438]:[Sim] Simulator.cpp(242)::createSceneInstance : Loading navmesh from Download/scene_datasets/habitat-test-scenes/apartment_1.navmesh
[04:32:38:801484]:[Nav] PathFinder.cpp(852)::loadNavMesh : NavMeshSettings aren't present, guessing that they are the default
[04:32:38:801552]:[Sim] Simulator.cpp(244)::createSceneInstance : Navmesh Loaded.
[04:32:38:801576]:[Scene] SceneGraph.h(85)::createDrawableGroup : Created DrawableGroup:
[04:32:38:801587]:[Assets] ResourceManager.cpp(297)::loadSemanticSceneDescriptor : SceneInstance : Download/scene_datasets/habitat-test-scenes/apartment_1.glb proposed Semantic Scene Descriptor filename : Download/scene_datasets/habitat-test-scenes/apartment_1.scn
[04:32:38:801605]:[Assets] ResourceManager.cpp(344)::loadSemanticSceneDescriptor : SSD File Naming Issue! Neither SceneInstanceAttributes-provided name : Download/scene_datasets/habitat-test-scenes/apartment_1.scn  nor constructed filename : Download/scene_datasets/habitat-test-scenes/info_semantic.json exist on disk.
[04:32:38:801644]:[Assets] ResourceManager.cpp(1641)::ConfigureImporterManagerGLExtensions : Importing Basis files as ASTC 4x4.
[04:32:38:802857]:[Sim] Simulator.cpp(302)::createSceneInstance : Using scene instance-specified Light key : - no_lights -
[04:32:38:802886]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and dataset : default which is currently active dataset.
[04:32:38:802955]:[Sim] Simulator.cpp(412)::instanceStageForSceneAttributes : Start to load stage named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb with render asset : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and collision asset : Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:803003]:[Assets] ResourceManager.cpp(691)::createStageAssetInfosFromAttributes : Frame :{"up":[0,0,1],"front":[0,1,0],"origin":[0,0,0]} for render mesh named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb|{"up":[0,0,1],"front":[0,1,0],"origin":[0,0,0]} for semantic mesh named :  with type specified as semantic|Semantic Txtrs : False
[04:32:38:803031]:[Assets] ResourceManager.cpp(507)::loadStage : Start load render asset Download/scene_datasets/habitat-test-scenes/apartment_1.glb .
[04:32:38:803047]:[Assets] ResourceManager.cpp(973)::loadStageInternal : Attempting to load stage Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:803064]:[Assets] ResourceManager.cpp(855)::loadRenderAsset : Loading general asset named: Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:803080]:[Assets] ResourceManager.cpp(1641)::ConfigureImporterManagerGLExtensions : Importing Basis files as ASTC 4x4.
[04:32:39:581159]:[Assets] ResourceManager.cpp(2089)::loadMaterials : Building 1 materials for asset named 'apartment_1.glb' :
[04:32:39:581258]:[Assets] ResourceManager.cpp(2194)::loadMaterials : Idx 00:Flat.
[04:32:39:678477]:[Sim] Simulator.cpp(439)::instanceStageForSceneAttributes : Successfully loaded stage named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:39:678543]:[Sim] Simulator.cpp(471)::instanceStageForSceneAttributes :
---
The active scene does not contain semantic annotations : activeSemanticSceneID_ = 0
---
[04:32:39:678577]:[Sim] Simulator.cpp(205)::reconfigure : CreateSceneInstance success == true for active scene name : Download/scene_datasets/habitat-test-scenes/apartment_1.glb  with renderer.
[04:32:39:691651]:[Default] viewer.cpp(432)::printHelpText :
==================================================
Welcome to the Habitat-sim C++ Viewer application!
==================================================
Mouse Functions ('m' to toggle mode):
----------------
In LOOK mode (default):
  LEFT:
    Click and drag to rotate the agent and look up/down.
  RIGHT:
    (physics) Click a surface to instance a random primitive object at that location.
  SHIFT-LEFT:
    Read Semantic ID and tag of clicked object (Currently only HM3D);
  SHIFT-RIGHT:
    Click a mesh to highlight it.
  CTRL-RIGHT:
    (physics) Click on an object to voxelize it and display the voxelization.
  WHEEL:
    Modify orthographic camera zoom/perspective camera FOV (+SHIFT for fine grained control)
In GRAB mode (with 'enable-physics'):
  LEFT:
    Click and drag to pickup and move an object with a point-to-point constraint (e.g. ball joint).
  RIGHT:
    Click and drag to pickup and move an object with a fixed frame constraint.
  WHEEL (with picked object):
    Pull gripped object closer or push it away.
    + ALT: rotate object fixed constraint frame (yaw)
    + CTRL: rotate object fixed constraint frame (pitch)
    + ALT+CTRL: rotate object fixed constraint frame (roll)

Key Commands:
-------------
  esc: Exit the application.
  'H': Display this help message.
  'm': Toggle mouse mode (LOOK | GRAB).
  TAB/Shift-TAB : Cycle to next/previous scene in scene dataset.
  ALT+TAB: Reload the current scene.

  Agent Controls:
  'wasd': Move the agent's body forward/backward, left/right.
  'zx': Move the agent's body up/down.
  arrow keys: Turn the agent's body left/right and camera look up/down.
  '9': Randomly place agent on NavMesh (if loaded).
  'q': Query the agent's state and print to terminal.
  '[': Save agent position/orientation to "./saved_transformations/camera.year_month_day_hour-minute-second.txt".
  ']': Load agent position/orientation from file system, or else from last save in current instance.

  Camera Settings
  '4': Cycle through camera modes (Camera, Fisheye, Equirectangular)
  '5': Switch ortho/perspective camera.
  '6': Reset ortho camera zoom/perspective camera FOV.
  '7': Cycle through rendering modes (RGB, depth, semantic)

  Visualization Utilities:
  'l': Override the default lighting setup with configured settings in `default_light_override.lighting_config.json`.
  'e': Enable/disable frustum culling.
  'c': Show/hide UI overlay.
  'n': Show/hide NavMesh wireframe.
  'i': Save a screenshot to "./screenshots/year_month_day_hour-minute-second/#.png".
  ',': Render a Bullet collision shape debug wireframe overlay (white=active, green=sleeping, blue=wants sleeping, red=can't sleep)

  Object Interactions:
  SPACE: Toggle physics simulation on/off
  '.': Take a single simulation step if not simulating continuously.
  '8': Instance a random primitive object in front of the agent.
  'o': Instance a random file-based object in front of the agent.
  'u': Remove most recently instanced rigid object.
  't': Instance an ArticulatedObject in front of the camera from a URDF file by entering the filepath when prompted.
    +ALT: Import the object with a fixed base.
    +SHIFT Quick-reload the previously specified URDF.
  'b': Toggle display of object bounding boxes.
  'p': Save current simulation state to SceneInstanceAttributes JSON file (with non-colliding filename).
  'v': (physics) Invert gravity.
  'g': (physics) Display a stage's signed distance gradient vector field.
  'k': (physics) Iterate through different ranges of the stage's voxelized signed distance field.

  Additional Utilities:
  'r': Write a replay of the recent simulated frames to a file specified by --gfx-replay-record-filepath.
  '/': Write the current scene's metadata information to console.

  Nav Trajectory Visualization:
  '1': Toggle recording locations for trajectory visualization.
  '2': Build and display trajectory visualization.
  '3': Toggle single color/multi-color trajectory.
  '+': Increase trajectory diameter.
  '-': Decrease trajectory diameter.

  'F': (audio) Add audio source in front of the agent
  '0': (audio) Run audio simulation
  ==================================================

[04:32:50:512734]:[Sim] Simulator.cpp(66)::~Simulator : Deconstructing Simulator
[04:32:50:512806]:[Agent] Agent.cpp(30)::~Agent : Deconstructing Agent
[04:32:50:512827]:[Physics] PhysicsManager.cpp(50)::~PhysicsManager : Deconstructing PhysicsManager
[04:32:50:512851]:[Scene] SceneManager.h(25)::~SceneManager : Deconstructing SceneManager
[04:32:50:512864]:[Scene] SceneGraph.h(25)::~SceneGraph : Deconstructing SceneGraph
[04:32:50:512892]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:512992]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:513168]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:513827]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:514005]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:514874]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:516273]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:516939]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:518751]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:518807]:[Scene] SemanticScene.h(47)::~SemanticScene : Deconstructing SemanticScene
[04:32:50:519684]:[Gfx] Renderer.cpp(72)::~Impl : Deconstructing Renderer
```Platform: can't get Xft.dpi property for virtual DPI scaling, falling back to physical DPI
Renderer: D3D12 (Intel(R) UHD Graphics 770) by Microsoft Corporation
OpenGL version: 4.1 (Core Profile) Mesa 22.2.0 - kisak-mesa PPA
Using optional features:
    GL_ARB_vertex_array_object
    GL_ARB_ES2_compatibility
    GL_ARB_separate_shader_objects
    GL_ARB_robustness
    GL_ARB_texture_storage
    GL_ARB_invalidate_subdata
    GL_ARB_texture_storage_multisample
    GL_ARB_multi_bind
    GL_ARB_direct_state_access
    GL_ARB_get_texture_sub_image
    GL_ARB_texture_filter_anisotropic
    GL_KHR_debug
Using driver workarounds:
    no-layout-qualifiers-on-old-glsl
    mesa-dsa-createquery-except-pipeline-stats
    mesa-forward-compatible-line-width-range
[04:32:38:779433]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Dataset>: Proposing JSON name : default.scene_dataset_config.json from original name : default| This file does not exist.
[04:32:38:779497]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (capsule3DSolid:capsule3DSolid_hemiRings_4_cylRings_1_segments_12_halfLen_0.75_useTexCoords_false_useTangents_false) created and registered.
[04:32:38:779530]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (capsule3DWireframe:capsule3DWireframe_hemiRings_8_cylRings_1_segments_16_halfLen_1) created and registered.
[04:32:38:779554]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (coneSolid:coneSolid_segments_12_halfLen_1.25_rings_1_useTexCoords_false_useTangents_false_capEnd_true) created and registered.
[04:32:38:779575]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (coneWireframe:coneWireframe_segments_32_halfLen_1.25) created and registered.
[04:32:38:779594]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cubeSolid:cubeSolid) created and registered.
[04:32:38:779612]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cubeWireframe:cubeWireframe) created and registered.
[04:32:38:779633]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cylinderSolid:cylinderSolid_rings_1_segments_12_halfLen_1_useTexCoords_false_useTangents_false_capEnds_true) created and registered.
[04:32:38:779654]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (cylinderWireframe:cylinderWireframe_rings_1_segments_32_halfLen_1) created and registered.
[04:32:38:779675]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (icosphereSolid:icosphereSolid_subdivs_1) created and registered.
[04:32:38:779694]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (icosphereWireframe:icosphereWireframe_subdivs_1) created and registered.
[04:32:38:779714]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (uvSphereSolid:uvSphereSolid_rings_8_segments_16_useTexCoords_false_useTangents_false) created and registered.
[04:32:38:779733]:[Metadata] AssetAttributesManager.cpp(121)::createObject : Asset attributes (uvSphereWireframe:uvSphereWireframe_rings_16_segments_32) created and registered.
[04:32:38:779753]:[Metadata] AssetAttributesManager.cpp(110)::AssetAttributesManager : Built default primitive asset templates : 12
[04:32:38:779873]:[Metadata] SceneDatasetAttributesManager.cpp(35)::createObject : File (default) not found, so new default dataset attributes created  and registered.
[04:32:38:779886]:[Metadata] MetadataMediator.cpp(120)::createSceneDataset : Dataset default successfully created.
[04:32:38:779903]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Physics Manager>: Proposing JSON name : ./data/default.physics_config.json from original name : ./data/default.physics_config.json| This file does not exist.
[04:32:38:779925]:[Metadata] PhysicsAttributesManager.cpp(26)::createObject : File (./data/default.physics_config.json) not found, so new default physics manager attributes created and registered.
[04:32:38:779939]:[Metadata] MetadataMediator.cpp(203)::setActiveSceneDatasetName : Previous active dataset  changed to default successfully.
[04:32:38:779952]:[Metadata] MetadataMediator.cpp(175)::setCurrPhysicsAttributesHandle : Old physics manager attributes  changed to ./data/default.physics_config.json successfully.
[04:32:38:779957]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage :  and dataset : default which is currently active dataset.
[04:32:38:785609]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and dataset : default which is currently active dataset.
[04:32:38:785651]:[Metadata] AttributesManagerBase.h(321)::loadAllTemplatesFromPathAndExt : <Object Template> : ParsingObject Template: Cannot find data/objects/example_objects as directory or data/objects/example_objects.object_config.json as config file. Aborting parse.
[04:32:38:785680]:[Default] viewer.cpp(979)::Viewer : Scene Dataset Configuration file location : default | Loading Scene : Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:785687]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and dataset : default which is currently active dataset.
[04:32:38:801151]:[Metadata] MetadataMediator.cpp(297)::getSceneInstanceAttributesByName : Dataset : default has no preloaded SceneInstanceAttributes or StageAttributes named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb so loading/creating a new StageAttributes with this name, and then creating a SceneInstanceAttributes with the same name that references this stage.
[04:32:38:801203]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Stage Template>: Proposing JSON name : Download/scene_datasets/habitat-test-scenes/apartment_1.stage_config.json from original name : Download/scene_datasets/habitat-test-scenes/apartment_1.glb| This file does not exist.
[04:32:38:801258]:[Metadata] AbstractObjectAttributesManagerBase.h(184)::createObject : File (Download/scene_datasets/habitat-test-scenes/apartment_1.glb) exists but is not a recognized config filename extension, so new default Stage Template attributes created and registered.
[04:32:38:801295]:[Metadata] SceneDatasetAttributes.cpp(47)::addNewSceneInstanceToDataset : Dataset : 'default' : Stage Attributes 'Download/scene_datasets/habitat-test-scenes/apartment_1.glb' specified in Scene Attributes exists in dataset library.
[04:32:38:801310]:[Metadata] SceneDatasetAttributes.cpp(84)::addNewSceneInstanceToDataset : Dataset : 'default' : Lighting Layout Attributes 'no_lights' specified in Scene Attributes but does not exist in dataset, so creating.
[04:32:38:801317]:[Metadata] AttributesManagerBase.h(380)::createFromJsonOrDefaultInternal : <Lighting Layout>: Proposing JSON name : no_lights.lighting_config.json from original name : no_lights| This file does not exist.
[04:32:38:801336]:[Metadata] LightLayoutAttributesManager.cpp(36)::createObject : File (no_lights) not found, so new default light layout attributes created and registered.
[04:32:38:801352]:[Sim] Simulator.cpp(237)::createSceneInstance : Navmesh file location in scene instance : Download/scene_datasets/habitat-test-scenes/apartment_1.navmesh
[04:32:38:801438]:[Sim] Simulator.cpp(242)::createSceneInstance : Loading navmesh from Download/scene_datasets/habitat-test-scenes/apartment_1.navmesh
[04:32:38:801484]:[Nav] PathFinder.cpp(852)::loadNavMesh : NavMeshSettings aren't present, guessing that they are the default
[04:32:38:801552]:[Sim] Simulator.cpp(244)::createSceneInstance : Navmesh Loaded.
[04:32:38:801576]:[Scene] SceneGraph.h(85)::createDrawableGroup : Created DrawableGroup:
[04:32:38:801587]:[Assets] ResourceManager.cpp(297)::loadSemanticSceneDescriptor : SceneInstance : Download/scene_datasets/habitat-test-scenes/apartment_1.glb proposed Semantic Scene Descriptor filename : Download/scene_datasets/habitat-test-scenes/apartment_1.scn
[04:32:38:801605]:[Assets] ResourceManager.cpp(344)::loadSemanticSceneDescriptor : SSD File Naming Issue! Neither SceneInstanceAttributes-provided name : Download/scene_datasets/habitat-test-scenes/apartment_1.scn  nor constructed filename : Download/scene_datasets/habitat-test-scenes/info_semantic.json exist on disk.
[04:32:38:801644]:[Assets] ResourceManager.cpp(1641)::ConfigureImporterManagerGLExtensions : Importing Basis files as ASTC 4x4.
[04:32:38:802857]:[Sim] Simulator.cpp(302)::createSceneInstance : Using scene instance-specified Light key : - no_lights -
[04:32:38:802886]:[Metadata] MetadataMediator.cpp(66)::setSimulatorConfiguration : Set new simulator config for scene/stage : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and dataset : default which is currently active dataset.
[04:32:38:802955]:[Sim] Simulator.cpp(412)::instanceStageForSceneAttributes : Start to load stage named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb with render asset : Download/scene_datasets/habitat-test-scenes/apartment_1.glb and collision asset : Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:803003]:[Assets] ResourceManager.cpp(691)::createStageAssetInfosFromAttributes : Frame :{"up":[0,0,1],"front":[0,1,0],"origin":[0,0,0]} for render mesh named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb|{"up":[0,0,1],"front":[0,1,0],"origin":[0,0,0]} for semantic mesh named :  with type specified as semantic|Semantic Txtrs : False
[04:32:38:803031]:[Assets] ResourceManager.cpp(507)::loadStage : Start load render asset Download/scene_datasets/habitat-test-scenes/apartment_1.glb .
[04:32:38:803047]:[Assets] ResourceManager.cpp(973)::loadStageInternal : Attempting to load stage Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:803064]:[Assets] ResourceManager.cpp(855)::loadRenderAsset : Loading general asset named: Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:38:803080]:[Assets] ResourceManager.cpp(1641)::ConfigureImporterManagerGLExtensions : Importing Basis files as ASTC 4x4.
[04:32:39:581159]:[Assets] ResourceManager.cpp(2089)::loadMaterials : Building 1 materials for asset named 'apartment_1.glb' :
[04:32:39:581258]:[Assets] ResourceManager.cpp(2194)::loadMaterials : Idx 00:Flat.
[04:32:39:678477]:[Sim] Simulator.cpp(439)::instanceStageForSceneAttributes : Successfully loaded stage named : Download/scene_datasets/habitat-test-scenes/apartment_1.glb
[04:32:39:678543]:[Sim] Simulator.cpp(471)::instanceStageForSceneAttributes :
---
The active scene does not contain semantic annotations : activeSemanticSceneID_ = 0
---
[04:32:39:678577]:[Sim] Simulator.cpp(205)::reconfigure : CreateSceneInstance success == true for active scene name : Download/scene_datasets/habitat-test-scenes/apartment_1.glb  with renderer.
[04:32:39:691651]:[Default] viewer.cpp(432)::printHelpText :
==================================================
Welcome to the Habitat-sim C++ Viewer application!
==================================================
Mouse Functions ('m' to toggle mode):
----------------
In LOOK mode (default):
  LEFT:
    Click and drag to rotate the agent and look up/down.
  RIGHT:
    (physics) Click a surface to instance a random primitive object at that location.
  SHIFT-LEFT:
    Read Semantic ID and tag of clicked object (Currently only HM3D);
  SHIFT-RIGHT:
    Click a mesh to highlight it.
  CTRL-RIGHT:
    (physics) Click on an object to voxelize it and display the voxelization.
  WHEEL:
    Modify orthographic camera zoom/perspective camera FOV (+SHIFT for fine grained control)
In GRAB mode (with 'enable-physics'):
  LEFT:
    Click and drag to pickup and move an object with a point-to-point constraint (e.g. ball joint).
  RIGHT:
    Click and drag to pickup and move an object with a fixed frame constraint.
  WHEEL (with picked object):
    Pull gripped object closer or push it away.
    + ALT: rotate object fixed constraint frame (yaw)
    + CTRL: rotate object fixed constraint frame (pitch)
    + ALT+CTRL: rotate object fixed constraint frame (roll)

Key Commands:
-------------
  esc: Exit the application.
  'H': Display this help message.
  'm': Toggle mouse mode (LOOK | GRAB).
  TAB/Shift-TAB : Cycle to next/previous scene in scene dataset.
  ALT+TAB: Reload the current scene.

  Agent Controls:
  'wasd': Move the agent's body forward/backward, left/right.
  'zx': Move the agent's body up/down.
  arrow keys: Turn the agent's body left/right and camera look up/down.
  '9': Randomly place agent on NavMesh (if loaded).
  'q': Query the agent's state and print to terminal.
  '[': Save agent position/orientation to "./saved_transformations/camera.year_month_day_hour-minute-second.txt".
  ']': Load agent position/orientation from file system, or else from last save in current instance.

  Camera Settings
  '4': Cycle through camera modes (Camera, Fisheye, Equirectangular)
  '5': Switch ortho/perspective camera.
  '6': Reset ortho camera zoom/perspective camera FOV.
  '7': Cycle through rendering modes (RGB, depth, semantic)

  Visualization Utilities:
  'l': Override the default lighting setup with configured settings in `default_light_override.lighting_config.json`.
  'e': Enable/disable frustum culling.
  'c': Show/hide UI overlay.
  'n': Show/hide NavMesh wireframe.
  'i': Save a screenshot to "./screenshots/year_month_day_hour-minute-second/#.png".
  ',': Render a Bullet collision shape debug wireframe overlay (white=active, green=sleeping, blue=wants sleeping, red=can't sleep)

  Object Interactions:
  SPACE: Toggle physics simulation on/off
  '.': Take a single simulation step if not simulating continuously.
  '8': Instance a random primitive object in front of the agent.
  'o': Instance a random file-based object in front of the agent.
  'u': Remove most recently instanced rigid object.
  't': Instance an ArticulatedObject in front of the camera from a URDF file by entering the filepath when prompted.
    +ALT: Import the object with a fixed base.
    +SHIFT Quick-reload the previously specified URDF.
  'b': Toggle display of object bounding boxes.
  'p': Save current simulation state to SceneInstanceAttributes JSON file (with non-colliding filename).
  'v': (physics) Invert gravity.
  'g': (physics) Display a stage's signed distance gradient vector field.
  'k': (physics) Iterate through different ranges of the stage's voxelized signed distance field.

  Additional Utilities:
  'r': Write a replay of the recent simulated frames to a file specified by --gfx-replay-record-filepath.
  '/': Write the current scene's metadata information to console.

  Nav Trajectory Visualization:
  '1': Toggle recording locations for trajectory visualization.
  '2': Build and display trajectory visualization.
  '3': Toggle single color/multi-color trajectory.
  '+': Increase trajectory diameter.
  '-': Decrease trajectory diameter.

  'F': (audio) Add audio source in front of the agent
  '0': (audio) Run audio simulation
  ==================================================

[04:32:50:512734]:[Sim] Simulator.cpp(66)::~Simulator : Deconstructing Simulator
[04:32:50:512806]:[Agent] Agent.cpp(30)::~Agent : Deconstructing Agent
[04:32:50:512827]:[Physics] PhysicsManager.cpp(50)::~PhysicsManager : Deconstructing PhysicsManager
[04:32:50:512851]:[Scene] SceneManager.h(25)::~SceneManager : Deconstructing SceneManager
[04:32:50:512864]:[Scene] SceneGraph.h(25)::~SceneGraph : Deconstructing SceneGraph
[04:32:50:512892]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:512992]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:513168]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:513827]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:514005]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:514874]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:516273]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:516939]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:518751]:[Sensor] Sensor.cpp(69)::~Sensor : Deconstructing Sensor
[04:32:50:518807]:[Scene] SemanticScene.h(47)::~SemanticScene : Deconstructing SemanticScene
[04:32:50:519684]:[Gfx] Renderer.cpp(72)::~Impl : Deconstructing Renderer

Are you looking around when it doesn't work? The mesh isn't just behind the camera?
Not sure if I know how to debug this issue if it isn't happening consistently.

Indeed, I moved when it successfully ran, the mesh is correct I suppose. I'm also not sure what caused this, since it's not like the program failed to run, but it just outputs weird things. I'll see what I can do and try


option-b---creating-a-package-without-the-installer

This step references a .zip file that we need to unzip locally before running the packager.py script (package-without-binary.zip).
where is this .zip file located?  I can't locate it in the repo - do we create it manually?
https://github.com/CrowdStrike/Cloud-AWS/blob/main/systems-manager/documentation/AWS-Systems-Manager-Intro.md#option-b---creating-a-package-without-the-installer

IT appears these zi

Two zip files are included in the Packaging-utilities/zip-files folder that contain example files for creating a
208 | CrowdStrike package for AWS Systems Manager.

p files were removed?

Thank you!

Hi @RuBiCK!
We have an example that contains the contents of this legacy archive located here: https://github.com/CrowdStrike/Cloud-AWS/tree/main/state-manager/ssm-distributor
This solution also contains an enhancement that demonstrates downloading the sensor from the API, bundling it into the distributor package, and then deploying it to S3. (e.g. The sensor is downloaded at package creation, not during sensor deployment.)
Let us know if there are any questions.

Thanks for the information @jshcodes!
I'm facing different errors and following the documentation. In S3 bucket it sucessfully create and upload files to falcon/ but doesn't appear the files in the root folder like layer.zip, createSsmParams.zip, lamda_ssm_setup.zip and Local-CrowdStrike-Automation-Doc.yml
I'm going to upload them manually and keep with the installation instructions

Uploading them to the bucket should work.  You don't need to upload the YAML file. (CrowdStrike-Automation-Doc.yml)


FRI connection fails for ros noetic

Hello,
First of all thank you for this repo, it looks really interesting and exciting!
We have gone through the setup, using the noetic branch, but unfortunately encountered a few issues. We have a LBR iiwa 14, to which we have added the FRI package and the LBRserver java file in the src folder. The install and sync went well.
We then connected our client PC which runs on ubuntu 20.04 and with ros Noetic to the controller through the two possibilities:

the X66 port and using <IP_ADDRESS> as IP, rate of 10ms
the KONI port and using <IP_ADDRESS> as IP, rate of 10ms

In both cases, we are able to ping the controller but unable to create a connection.
We first start the LBRserver application on the SmartPad (rate 10ms, Position Control) and then we run on the client PC the moveit_planning_execution.launch, but the LBRserver stops pretty quickly after not getting any response from the client PC with a "timout before FRI connection was good or excellent" error.
We used wireshark to have a look at the UDP communication, and we can clearly see that the controller is sending packages but our client PC is not responding.

The outcome is the same for both ports/IPs.
Are we missing something? We are not a part of your university, so we do not have access to your sharepoint.

happy to chat in person if that is the case. We stopped development of the noetic branch, however, it should still work.
When you launch roslaunch lbr_moveit moveit_planning_execution.launch model:=med7 sim:=false, did you set sim:=false?

I'm sorry to hear about that, we hope this is not too much trouble then.
Yes we did indeed change the sim argument to false.

can you find any errors in the terminal, ie ... | grep ERROR for a quick check

the most common issue are missing dependencies

The only error I get the launch file terminal is the following:
[ERROR] [1679319207.644945605]: Could not find the planner configuration 'None' on the param server

thanks for the feedback. Is this related to #68 ?

this repository is built using FRI 1.15, maybe there might be an issue

That might explain it indeed. Any idea if KUKA will let us update it? It's quite old and not supported anymore I believe

But even if the FRI version is too old, shouldn't I see in Wireshark some udp msg from my PC towards the robot controller?
I looks like the problem is on the client PC end no?

it could be that from fri 1.14 -> 1.15 there is a new message field, I am trying to look this up right now

May I ask for your help? I can't access the cpp source code for the FRI 1.14. You can extract it through

You should see the source code here

In the .zip file, check there is a license stating
Redistribution and use of the software in source and binary forms, with or
without modification, are permitted

If you could send me that zip file to<EMAIL_ADDRESS>I am happy to investigate. If this too much of a burden for you, no problem

Absolutely no problem, I'll gladly help out! Give me a minute, have to change OS

okay so on the client source side there are absolutely no differences

Shoot ... so something with my setup on the PC or something with the connection is not right. Might also be the iiwa itself ... this repo only uses the FRI package?

you can check whether the fri runs stand alone. E.g. build and install it
https://github.com/KCL-BMEIS/fri/tree/fri-1.14#cross-platform-build-and-installation
run one of the example applications
https://github.com/KCL-BMEIS/fri/tree/fri-1.14#client-side---laptop

the LBRJointSineOverlay sample application, by default (you'd have to check in Sunrise), sets the ip to <IP_ADDRESS>

I'm about to test it.

Unfortunately, even now with the right IP, it does not work

I'll redo the sunrise project setup from scratch following https://github.com/KCL-BMEIS/fri/tree/fri-1.14#server-side---kuka-controller to be sure

sorry to hear that. The instructions might differ a little bit for your robot

Yes, we have a different media flange

Still not working unfortunately

Really sorry to hear that and no idea what the issue could be.
Maybe it makes sense to try and get the fri running standalone first.
There is also the iiwa_stack, which you could try.

I'll take this feedback seriously and will try to improve the unit testing. This particular issue has probably to do with the fri or some network settings

thank you! I'll forward you some FRI documentation

I think I figured it out:
Just tried only KUKA's FRI and the connection worked as soon as I disabled my firewall!
Still have to setup my firewall correctly and try this repo again, but looks promising!

To setup the firewall on ubuntu 20.04:
sudo ufw allow proto udp from <IP_ADDRESS> to <IP_ADDRESS> port 30200

It all works fine now, thank you for your help !


API should return "job title"

User Story
job title available to the UI

T-shirt size: SML

User Story
Several of the UI mockups show people's full name, email address and job title.  It turns out that while job title is in AD, we haven't been storing it anywhere useful and aren't making it available to the UI.

Description

Acceptance Criteria/Tests
Correct job titles should be shown in the UI wherever the UI team has decided to include them (org chart, requestor lists, role owner, etc)

User's table is the right place to put this?

migrated to new tmobile/sawtooth-next-directory repo


Difference pytorch 0.4.1 vs 1.1

Hi,
This may not be the correct place to ask this, but I thought it's worth a shot. First off, thanks for releasing this code, it has been very helpful and I learned a lot. I am evaluating this model for semantic segmentation of large scale laser scan data and I have so far used the older pytorch 0.4 build with CUDA 8. For several reasons, I recently tried out the newest release with pytorch 1.1 + CUDA 10 + CUdnn 7.3.1.
I am noticing a significantly worse convergence behaviour(depending on the model setup and training data, anywhere from 2 to 8% worse accuracy when no longer any gains are made) and visibly worse segmentation results on test data on the newer build, when using the same model parameters, same hyperparameters, same Data-Loading, hardware, same everything.
Also when loading the same model checkpoint and evaluating with model.eval() on the exact same data, there are some minor differences even after the first SA layer, although I am not sure this is the reason for the worse training performance.
I came across some tidbits here and there about different behaviour of log_softmax in the newer version of nn.CrossEntropyLoss(), or maybe the fact I had to compile pytorch 1.1 myself vs installing a pre-compiled version of 0.4 is the reason. For building pyTorch 1.1 and your extensions I used gcc 7.3 with nvcc 10. Everything is in anaconda3 on a ubuntu box.
If you have any ideas, I'd be very happy to hear them!
Cheers,
Johannes

I don't have a build of pytorch master anywhere so I can't easily try things on master.  I tried pytorch 1.0.1 + CUDA 10 + cudnn 7.4 and I am seeing results I would expect for the example semantic segmentation script, so I don't believe I introduced any bugs when upgrading this repo to pytorch >= 1.0 (there definitely could still be as deep learning is really good at managing to do something sensible even with horrible bugs however).
Could you try pytorch 1.0.1?

Hello,
thank you for the suggestion. I compiled pytorch 1.0.1 with cuda 10 and cudnn 7.3.1. The discrepancies in loss and accuracy look the same as with pytorch 1.1. I'm using a moderately large custom dataset, could be it only shows up with my data, i haven't tested yet on indoor3d or modelnet. Might do that next.
Cheers,
Johannes


Feature Request: Export the LangFlow to a LangChain code implementation

Hey Langflow -
My team and I are working on building a tool and we wanted to use LangFlow to figure out how we would configure our LangChain agent. It would be helpful if instead of only having the option to export/generate python code which calls and implements the flow.json designed in LangFlow, would it be possible to add in a feature to generate an equivalent LangChain code which would implement all the components present in the LangFlow document.
Is there already a way to do this - or could this be implemented?
Thanks

Hey there! Have you ever given custom components a shot? I've got a feeling they might be a great fit for your situation

+1 this would be very useful

+1 agreed. This would be extremely useful.

+1. This would be extremely useful.


Get all instances in each reservation, not just the first

The previous list comprehension was slicing off only the first instance in each reservation. Now all instances in each reservation are included. If you had an autoscale group and had the MaxBatchSize greater than one, ssh2ec2 would only find the first instance in the reservation.
@mikery

Thanks Micah!

Noooo problem


Docs search preview cuts off words

Looks like it may show just a max number of characters. See if we can control this and be smarter about the text that gets displayed.

@louh - is there a possible fix for this (being as you self-assigned it)?
Else, I'll close and archive.

I don't believe this is something we can tackle on our end. It would
involve digging into the guts of MkDocs or seeing if they have fixed /
enabled fixing it in an upgrade. I think we could archive, since this is
likely to return in future work.
On Wed, Feb 17, 2016, 4:50 PM Rhonda Glennon<EMAIL_ADDRESS>wrote:

@louh https://github.com/louh - is there a possible fix for this (being
as you self-assigned it)?
Else, I'll close and archive.
—
Reply to this email directly or view it on GitHub
https://github.com/mapzen/mapzen-docs-generator/issues/34#issuecomment-185482081
.

Thanks for the analysis.


[WIP, CI] RL pipeline

Description
Adds a simple torchrl pipeline to capture bc-breaking changes from our main dep

Codecov Report
Patch and project coverage have no change.

Comparison is base (a25f5d7) 87.68% compared to head (a0c1dc7) 87.68%.

:exclamation: Current head a0c1dc7 differs from pull request most recent head a7d1206. Consider uploading reports for the commit a7d1206 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #319   +/-   ##
=======================================
  Coverage   87.68%   87.68%
=======================================
  Files          30       30
  Lines       10958    10958
=======================================
  Hits         9609     9609
  Misses       1349     1349

Flag
Coverage Δ

linux-cpu
85.91% <ø> (ø)

linux-gpu
87.65% <ø> (ø)

linux-macos-cpu
85.93% <ø> (ø)

linux-stable-cpu
85.91% <ø> (ø)

linux-stable-gpu
87.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Timestamp does not reflect correct time

Describe the bug
When using the Timestamp component, it does not update accordingly unless there is a state change in the page.
To Reproduce
Steps to reproduce the behavior:

Render the Timestamp component where the timestamp is new. (e. new Date()). Timestamp will be shown with 0 seconds ago and not update as the seconds pass.
Trigger a state change on the page to allow the timestamp to update.

OR

Go to the "Time Ago" Timestamp story page. Timestamp will show as 0 seconds ago and not change.
Click on the "Not This Year" page in the sidebar, then go back by clicking the "Time Ago" page. The timestamp will update once and not change again.

Expected behavior
The timestamp should should reflect time ago accurately. We can also update this component to simply show a date and time.
Please complete the following information:

Version of the library: 0.0.19

Resolved in PR #254.


Error: Could not find source directory

I get the following error while trying to run ffjson for a file
Error: error=Could not find source directory: GOPATH=["/home/sztanpet/go/gocode"] REL="/home/sztanpet/go/destinyggchat" path="":

must REL be a relative path or something?

Is your code inside your GOPATH?  From the error message it looks like destinyggchat is outside the GOPATH?
Because of how ffjson works, your code must be inside your GOPATH, so that it can compile your project to export the structure.

indeed it is not

symlinked it into the GOPATH but it still says
Error: error=Could not find source directory: GOPATH=["/home/sztanpet/go/gocode"] REL="/home/sztanpet/go/gocode/destinyggchat" path="":

It needs to be in a correct part of the GOPATH, under the src directory:
https://golang.org/doc/code.html#Workspaces
So if your project is called destinyggchat, your source code goes in $GOPATH/src/github.com/destinygg/chat

Thank you, works perfectly now
May I ask for this information to be made more clear in the docs?

Yeah, not sure how to best document this -- ffjson just depends on import paths and $GOPATH being setup the 'standard' way....


Update to syntex 0.32

Apparently Racer doesn't use any APIs that changed, so this is purely a
version bump. Tests passed on my machine.

This change is

Thanks @jwilm


Add mechanism to count copies for all rendering paths / document formats

There is currently no high level facility that counts copies, only impressions. Lacking this makes implementing features such as "Job Proof and Suspend" (IPP Enterprise Printing Extensions v2.0) difficult because the logic gets pushed down to lower levels and individual document rendering pipelines, which can lead to inconsistent behavior.
Describe the solution you'd like
Add "copies" and "copies_completed" to _pappl_job_s. Streaming document formats (PWG Raster) complicate because the copies are usually just resent as additional pages. Implementing support for the "job-pages-per-set" Job Template attribute (5100.1) for streaming formats will help with this and the logic for counting the copies  if it isn't supported already.
It might also be good to have a "rstartcopy_cb" and/or "rendcopy_cb" callbacks for drivers.
Describe alternatives you've considered
I tried writing driver code but whether my callbacks get called depends on the document format and some document formats don't hit my driver. Counting impressions doesn't work if the driver doesn't know the total number of pages in the document(s), which requires the driver to be able to parse the document format, which is not always otherwise needed.
Additional context
n/a

While we can't extend the driver callbacks in a 1.x series, I think we can expose this in a way that allows the driver to pause processing and resume later as needed.

[master 109207d] Add papplJobGetCopies/Completed and papplJobSetCopiesCompleted APIs (Issue #265)

[master d7d8e02] Update raster path to count copies properly (Issue #265)


LinearProgressIndicator and CircularProgressIndicator Documentation.

LinearProgressIndicator and CircularProgressIndicator documentation does not specify that value parameter should be between 0 and 1.
Steps to Reproduce
Documentation issue.

it is similar for CircularProgressIndicator.

Logs

❯ flutter doctor -v
[✓] Flutter (Channel master, 2.5.0-2.0.pre.128, on macOS 11.5.1 20G80
    darwin-arm, locale en-IN)
    • Flutter version 2.5.0-2.0.pre.128 at /Users/sushantchandla/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 08320a8dc4 (6 days ago), 2021-08-03 01:05:02 -0400
    • Engine revision eb1d87d805
    • Dart version 2.14.0 (build 2.14.0-372.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/sushantchandla/Library/Android/Sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/sushantchandla/Library/Android/Sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.59.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.25.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 11.5.1 20G80 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 92.0.4515.131

• No issues found!

I would like to make a pr fixing this : )

For LinearProgressIndicator, it does seem to mention the value, as below:

https://api.flutter.dev/flutter/material/LinearProgressIndicator-class.html
For CircularProgressIndicator, it does seem not to have mentioned the range though.
Labeling it as applicable.

This link is for the constructor. Here's a class doc link, which does mention that https://api.flutter.dev/flutter/material/CircularProgressIndicator-class.html

The https://api.flutter.dev/flutter/material/RefreshProgressIndicator-class.html doc comment though would probably benefit from having the same section

I will open a PR to fix this in a bit 👍

@SushantChandla I have started - I figured you would not be on it since it has been 16 days.

Okay, no problem : )

So it turns out, I only found a single place missing the doc (i.e. the abstract class ProgressIndicator docs) → so that was an easy fix.
I thought about adding an assertion for the value to be between 0.0 and 1.0, however, that would be a breaking change. Instead, I checked the code and it turns out the value is always clamped using num.clamp. That is why I added that to the value docs :)
The PR is #88800 🚀


Adds Eagles Landing Christian Academy

Eagles Landing Christian Academy

@xxShadowRingxx Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

I cant find an IT-related long-term course, and how could I prove that the school uses the domain I provided
Other than that I can give you the rest
elcaonline.org
2400 Highway 42 N, McDonough, GA 30253

@xxShadowRingxx Thank you for the clarification. Yes, the school is eligible for being added to the trusted list.
Please provide us with a proof, which shows that the school recognizes the domain elcachargers.org that you are submitting, as an official email domain for the students.
You can provide us with any of the following:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

Would this work, I can’t find any proof, only email domain I have found on the website are Faculty domains.

You still there @philipto

@xxShadowRingxx  Thank you for the clarifications. Pull request merged.
FTR: another proof of the domain ownership is at https://www.instantcheckmate.com/people/ruby-calhoun/


add forwarded header

Experimented a bit with a COW-like interface for the forwarded header. Let me know if you'd prefer to switch to just the Owned version. Alternatively, if y'all like this pattern, we might want to use it for other headers

I think using a Cow under the hood might make sense, but we probably shouldn't surface it to the end-user. So far I've been trying to make enums expose HTTP terminology only, and caring a bit less about internal optimizations.
Also for fn new: would it make sense to use a TryInto<URL> bound? We may need to ensure we correctly serialize it, but to me that seems like a fairly natural fit?

@yoshuawuyts How do you think x-forwarded-for, x-forwarded-proto, and x-forwarded-host should interact with the forwarded header? It would be nice for there to be a "meta header" that pulled from whatever was available

I guess the question is how 1:1 the headers types should be with a single header

It's my understanding that those are no longer used much, and mostly exist for backwards compat purposes? Afaik they haven't been specced either.
Perhaps let's not care about it now, and if we ever want to do something there we can add some higher-level "proxy" submodule (perhaps in Tide?) that is aware of how to handle this?

Unfortunately, I think the standardization of forwarded isn't yet complete, and the x- variants are still common in the wild. A quick search turned up references like https://devcenter.heroku.com/articles/http-routing#heroku-headers, and there are "de facto" specs:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Host
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For

Forwarded is part of RFC 7239, dated 2014. The iana HTTP header overview lists it as an accepted standard (experimental headers are highlighted).
Given how long it's been around it would be surprising if it this wasn't supported by modern servers. Perhaps a compromise we can make here is that we try and detect X-Forwarded-For as a fallback in from_headers, but never serialize it ourselves in value. That way we can detect it if we must, but don't propagate it ourselves. Wdyt?

Exactly what I suggested in the edit to https://github.com/http-rs/http-types/pull/221#issuecomment-670797969, which I might have made at the same time as you posted this :thumbsup:
Also switching to making each field an Option<Cow<'_, str>>, making the parser a bit more lax (I thought all four were required but it turns out they're not), replacing the new(a,b,c,d) with chainable setters, and making apply fallible because it's basically a builder finalizer. phew there was a bunch wrong with the first version of this pr.

and making apply fallible because it's basically a builder finalizer

Ah interesting; none of the other headers has a fallibly apply. They all assume that once they contain a value it's valid; this makes it easy to reason about the inner state for both parsing and encoding.
What would the error be that surfaces for apply? Is there a way we could surface it sooner?

@yoshuawuyts @Fishrock123 This is now ready for review. Although I do hope that this is fairly readable as far as hand-rolled nearly-zero-copy parsers go, I think the most valuable way to review this would be to take a look at the spec and the test cases before looking at the implementation.
The general approach to parsing in this pr is for parsers to return (Option<&str>, &str) or (Option<Cow<'_, str>>, &str), depending on whether the parser might need to sometimes allocate. The first value is the thing if it can be parsed, and the second str is the rest of the input string, split at the end of the consumed bytes.

(Note: I did not review the spec)

I've removed the with_… chainable methods from this, should be good to go, cc @yoshuawuyts


Get validation workflow running with DROID

The script should be included in the Makefile. Running this script should fetch & pull the sheets from Google Sheets then run validation. The validation should be applied to the sheets.
@jamesaoverton can this be a bash script or would you rather have validate.py updated to do all the tasks?

Following up, I figured this would just be a button in DROID that runs in the console, rather than a CGI script. Is that correct?

Hey @beckyjackson I am currently finishing up step 3 in #77
The interface looks something like:

I think it does not really matter how you implement the validation, but I run my part (3) it something like this:
Makefile:
automated_mapping:
	make cogs_pull
	make mapping_suggest_cogs
	cogs push

@beckyjackson Yes, a task in the Makefile would be fine. Then this needs to link to the task:
https://github.com/IHCC-cohorts/data-harmonization/blob/master/Makefile#L13
Assume that COGS has already shared the Google Sheet with the submitter. COGS is working with files in build/metadata.tsv and build/terminology.tsv. Please add validation for the metadata sheet to your script.

If you do metadata and terminology separately, that would be good - I already need metadata.tsv in step 3, so we could validate that one as part of the mapping process

I think this is done now.


stacked group is not rendered correctly when stack group is not adjacent

when stacked group is set for non adjacent datasets, it seems the group index returned is not correct.
Please see the codepen here:
https://codepen.io/adamshe/pen/bYGRBP
Looking forward to a quick fix. thanks.

The following patch fixes the problem. fix_4897_stacked_group_is_not_rendered_correctly_when_stack_group_is_not_adjacent.patch.txt

@jcopperfield could you create a PR with that patch?

I confirmed that this patch works, but all the yaxis id needs to be y-axis-n format


DocComments and Cleanup

Enabling DocComments for OpenAPI.
Clearing up all warnings in OpenAPI project.
Implementing some of the feedback from the original PR.

Codecov Report

Merging #97 into master will not change coverage.
The diff coverage is 89.79%.

@@           Coverage Diff           @@
##           master      #97   +/-   ##
=======================================
  Coverage   74.43%   74.43%
=======================================
  Files         126      129    +3
  Lines        5469     5469
=======================================
  Hits         4071     4071
  Misses       1398     1398

Impacted Files
Coverage Δ

...ourceCode.Clay.OpenApi/Builders/DocumentBuilder.cs
94.44% <ø> (ø)
:arrow_up:

.../SourceCode.Clay.OpenApi/Builders/ServerBuilder.cs
94.44% <ø> (ø)
:arrow_up:

...Code.Clay.OpenApi/Builders/ParameterBodyBuilder.cs
93.1% <ø> (ø)
:arrow_up:

...urceCode.Clay.OpenApi/Builders/MediaTypeBuilder.cs
94.73% <ø> (ø)
:arrow_up:

src/SourceCode.Clay.OpenApi/Reference.cs
72.22% <ø> (ø)
:arrow_up:

...Api/Builders/OpenIdConnectSecuritySchemeBuilder.cs
78.57% <ø> (ø)
:arrow_up:

...rceCode.Clay.OpenApi/Builders/ComponentsBuilder.cs
97.72% <ø> (ø)
:arrow_up:

...de.Clay.OpenApi/Serialization/OpenApiSerializer.cs
66.66% <ø> (-22.91%)
:arrow_down:

...ay.OpenApi/Builders/ApiKeySecuritySchemeBuilder.cs
82.35% <ø> (ø)
:arrow_up:

src/SourceCode.Clay.OpenApi/Server.cs
100% <ø> (ø)
:arrow_up:

... and 55 more

Continue to review full report at Codecov.

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

Merging this as there are no logic changes.


[LIVY-603]Upgrade spark 2.4 from 2.4.0 to 2.4.3

What changes were proposed in this pull request?
update spark 2.4 config from 2.4.0 to 2.4.3, config with current pom.xml will fail because 2.4.0 spark is removed from http://mirrors.advancedhosters.com/apache/spark/
https://issues.apache.org/jira/browse/LIVY-603
How was this patch tested?
Existing unit tests.
Please review https://livy.incubator.apache.org/community/ before opening a pull request.

Hi
The travis build is still broken. You may need to change the other 2.4.0 in the pom related section
      <properties>
        <spark.scala-2.11.version>2.4.0</spark.scala-2.11.version>
        <spark.version>${spark.scala-2.11.version}</spark.version>
        <netty.spark-2.11.version>4.1.17.Final</netty.spark-2.11.version>
        <java.version>1.8</java.version>
        <py4j.version>0.10.7</py4j.version>
        <spark.bin.download.url>
          http://mirrors.advancedhosters.com/apache/spark/spark-2.4.0/spark-2.4.0-bin-hadoop2.7.tgz
        </spark.bin.download.url>
        <spark.bin.name>spark-2.4.0-bin-hadoop2.7</spark.bin.name>
      </properties>

@yantzu would you please address the comment like @yiheng mentioned, thanks!

since there is another pr has fixed the issue, I will just close this one

Thanks @yantzu for you patch!


Removed whitespace when there are 2 panes in default Project view

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #16863
Description

The default project views i.e. when there are only two panes on the workspace viz. Map and main, the view is divided in the ratio 1:1(map and main occupy equal width). e.g. Implement the Serialization of a Passport User or any project view.
With this fix it makes the map 33% width & rest 67% is kept for the main view.

@rajatkantinandi Thanks for your contribution. This is an elegant way to handle this, and it looks and works great!
Also, congratulations on your first open source contribution to the core freeCodeCamp repo!


@supabase/ssr NextJs 14 middleware broke in 0.0.8

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
NextJs middleware (14.0.1) no longer works after upgrading from @supabase/ssr from 0.0.7 to 0.0.8
Specifically,  the cookie.get method ends up being called with undefined instead of name. I believe this may be related to the deletion of cookieOptions.name in the latest patch?
unhandledRejection: TypeError: Cannot read properties of undefined (reading 'name')
    at RequestCookies.get

Code for middleware was taken directly from the docs. Downgrading to 0.0.7 fixes the issue.
// middleware.ts
import { type CookieOptions, createServerClient } from '@supabase/ssr'
import { type NextRequest, NextResponse } from 'next/server'

export async function middleware(request: NextRequest) {
  let response = NextResponse.next({
    request: {
      headers: request.headers,
    },
  })

  const supabase = createServerClient<Database>(
    process.env.NEXT_PUBLIC_SUPABASE_URL!,
    process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
    {
      cookies: {
        get(name: string) {
          return request.cookies.get(name)?.value
        },
        remove(name: string, options: CookieOptions) {
          request.cookies.set({
            name,
            value: '',
            ...options,
          })
          response = NextResponse.next({
            request: {
              headers: request.headers,
            },
          })
          response.cookies.set({
            name,
            value: '',
            ...options,
          })
        },
        set(name: string, value: string, options: CookieOptions) {
          request.cookies.set({
            name,
            value,
            ...options,
          })
          response = NextResponse.next({
            request: {
              headers: request.headers,
            },
          })
          response.cookies.set({
            name,
            value,
            ...options,
          })
        },
      },
    },
  )

  await supabase.auth.getSession()

  return response
}

System information

OS: Windows
Version of supabase-js: 2.38.4
Version of Node.js: 18.16.0

+1 I'm having the same issue. Everything is updated. Strangely, the supabase example project works just fine... I'm confused as to why we have to do all the middleware cookie stuff ourselves... that only complicates things further.
Previously I could just refresh the user session by doing
const {
    data: { session },
  } = await supabase.auth.getSession();

But now the middleware client needs cookies and returns a response. Isn't that just plain out superfluous since the auth.getSession() automatically updates cookies?
I'm just confused, the ssr package seems a step backwards that just adds more complexity and potential breaking points...

The same issue while trying to exchange code for the session.
Interesting thing is cookies set but with name like undefined.0

I found some workaround here.
We have to provide the name of the cookies.
Server client
export const createClient = (cookieStore: ReturnType<typeof cookies>) => {
  return createServerClient<Database>(
    process.env.NEXT_PUBLIC_SUPABASE_URL!,
    process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
    {
      cookieOptions: {
        name: 'sb:token',
      },
      cookies: {
        get(name: string) {
          return cookieStore.get(name)?.value
        },
        set(name: string, value: string, options: CookieOptions) {
          try {
            cookieStore.set({name, value, ...options})
          } catch (error) {}
        },
        remove(name: string, options: CookieOptions) {
          try {
            cookieStore.set({name, value: '', ...options})
          } catch (error) {}
        },
      },
    },
  )
}

Browser client
export const createClient = () =>
  createBrowserClient<Database>(
    process.env.NEXT_PUBLIC_SUPABASE_URL!,
    process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
    {
      cookies: {},
      cookieOptions: {
        name: 'sb:token',
      },
    },
  )

That's the only way I found to make it work at the moment.

+1
[TypeError: Cannot read properties of undefined (reading 'name')]
TypeError: Cannot read properties of undefined (reading 'name')
    at RequestCookies.get (webpack-internal:///(middleware)/./node_modules/next/dist/compiled/@edge-runtime/cookies/index.js:205:70)
    at Object.get (webpack-internal:///(middleware)/./utils/supabase/middleware.ts:19:40)
    at eval (webpack-internal:///(middleware)/./node_modules/@supabase/ssr/dist/index.mjs:235:50)
    at combineChunks (webpack-internal:///(middleware)/./node_modules/@supabase/ssr/dist/index.mjs:59:25)
    at Object.getItem (webpack-internal:///(middleware)/./node_modules/@supabase/ssr/dist/index.mjs:233:49)
    at getItemAsync (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/lib/helpers.js:107:33)
    at SupabaseAuthClient.__loadSession (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:881:98)
    at SupabaseAuthClient._useSession (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:864:39)
    at SupabaseAuthClient._emitInitialSession (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:1362:27)
    at eval (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:1352:22)

+1 ssr is a downgrade 🥲

I found some workaround here.
We have to provide the name of the cookies.
Server client

export const createClient = (cookieStore: ReturnType<typeof cookies>) => {

  return createServerClient<Database>(

    process.env.NEXT_PUBLIC_SUPABASE_URL!,

    process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,

    {

      cookieOptions: {

        name: 'sb:token',

      },

      cookies: {

        get(name: string) {

          return cookieStore.get(name)?.value

        },

        set(name: string, value: string, options: CookieOptions) {

          try {

            cookieStore.set({name, value, ...options})

          } catch (error) {}

        },

        remove(name: string, options: CookieOptions) {

          try {

            cookieStore.set({name, value: '', ...options})

          } catch (error) {}

        },

      },

    },

  )

}

Another thing that I think isn't needed is getting the cookieStore straight from the import (without passing it as a prop every time). It was like this with the auth helpers...

+1 in the npx create-next-app -e with-supabase template

[TypeError: Cannot read properties of undefined (reading 'name')]

TypeError: Cannot read properties of undefined (reading 'name')

    at RequestCookies.get (webpack-internal:///(middleware)/./node_modules/next/dist/compiled/@edge-runtime/cookies/index.js:205:70)

    at Object.get (webpack-internal:///(middleware)/./utils/supabase/middleware.ts:19:40)

    at eval (webpack-internal:///(middleware)/./node_modules/@supabase/ssr/dist/index.mjs:235:50)

    at combineChunks (webpack-internal:///(middleware)/./node_modules/@supabase/ssr/dist/index.mjs:59:25)

    at Object.getItem (webpack-internal:///(middleware)/./node_modules/@supabase/ssr/dist/index.mjs:233:49)

    at getItemAsync (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/lib/helpers.js:107:33)

    at SupabaseAuthClient.__loadSession (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:881:98)

    at SupabaseAuthClient._useSession (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:864:39)

    at SupabaseAuthClient._emitInitialSession (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:1362:27)

    at eval (webpack-internal:///(middleware)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:1352:22)

Strange... with me the example works just fine lol

@thisislvca try deploying it to Vercel edge?

We've reverted the version with the broken code. We were trying to fix another issue relating to cookie name not setting and this created a break in the 0.0.8 release.

@silentworks with 0.0.9  do we need to change or remove something in de server.ts for the example to work?
 cookies: {         get(name: string) {           return cookieStore.get(name)?.value         },

@RobinGiel I don't understand what you are asking here. The steps to use tha ssr package are in the docs here https://supabase.com/docs/guides/auth/server-side/creating-a-client

I have also encountered the same issue.
I set up using the following commands:
npx supabase init
npx npx create-next-app@latest --typescript -e with-supabase
npx supabase start

However, I received the following error:
Error: Cannot read properties of undefined (reading 'name')
return cookieStore.get(name)?.value

@RobinGiel I don't understand what you are asking here. The steps to use the ssr package are in the docs here https://supabase.com/docs/guides/auth/server-side/creating-a-client

Yes following the docs and the example but I'm also getting errors the same as @DevRyuki is getting

As pointed out in other issue, downgrading @supabase/ssr to 0.0.6 is a temporary fix
Upgrading to 0.0.9 get rid of Cannot read properties of undefined (reading 'name') issue but data is saved in an 'undefined' cookie key making it unaccessible to the authorization flow

As pointed out in the other issue, downgrading @supabase/ssr to 0.0.6 is a temporary fix.
Upgrading to 0.0.9 get rid of Cannot read properties of undefined (reading 'name') issue but data is saved in an 'undefined' cookie key making it inaccessible to the authorization flow.

I just downgrade to 0.0.6 and indeed no more issue. And after I updated back to 0.0.9 and had again no issues. Maybe it's an issue with the local node_modules

As pointed out in the other issue, downgrading @supabase/ssr to 0.0.6 is a temporary fix.
Upgrading to 0.0.9 get rid of Cannot read properties of undefined (reading 'name') issue but data is saved in an 'undefined' cookie key making it inaccessible to the authorization flow.

As pointed out in the other issue, downgrading @supabase/ssr to 0.0.6 is a temporary fix.
Upgrading to 0.0.9 get rid of Cannot read properties of undefined (reading 'name') issue but data is saved in an 'undefined' cookie key making it inaccessible to the authorization flow.

I just downgrade to 0.0.6 and indeed no more issue. And after I updated back to 0.0.9 and had again no issues. Maybe it's an issue with the local node_modules

Changing "@supabase/ssr": "latest" to "@supabase/ssr": "0.0.6" and running it did not cause any issues.
Afterwards, changing the version to "@supabase/ssr": "0.0.9" and running it also did not cause any issues.
Furthermore, changing it back to "@supabase/ssr": "latest" did not result in any problems.
SignIn and SignUp were both successful without any issues.

Tested again and 0.0.9 worked fine, sorry for the confusion

I think we can close the issue 💪

I still get this issue, even when I downgrade to 0.0.6...anyone else?

Thank you everyone for reporting back on the 0.0.9 release. I'm going to close this issue out as it seems to have been resolved in 0.0.9.

Same issue is there in latest
 "@supabase/ssr": "^0.1.0",
 "@supabase/supabase-js": "^2.39.3",

Error: Cannot find module '@supabase/ssr'

That doesn't sound like a supabase error, but more like a package manager error. Try to uninstall and reinstall the package :)

@gokulkrishh as @thisislvca mentioned this is likely a package manager issue. You can see 0.1.0 was published to npm by the supabase team 2 days ago https://www.npmjs.com/package/@supabase/ssr.

@silentworks Yes, its an issue with the pkg manager. I found out the bug thats causing this issue. Link to bug i opened in NextJS.


Allow custom hostname in upgrade role

Related issue: #2088
kube_node_hostname should be managed by the user if required (e.g mapping in inventory file etc).

@bradbeam @chadswen any thoughts on this?

I'm ok with the idea.
Have you checked that inventory_hostname isn't used anywhere else?
Could you also provide a documentation or add it the inventory sample?

/assign me
/lgtm

I think it's going to cause issue with how kubeadm is configured, please re-open an issue to discuss the feature.


net-mgmt:snmp - process crashes with MibII enabled

I am running OPNsense 17.7.8-amd64 in a VM on VMware ESXi 6.0 and recently I have started having issues with bsnmpd crashing.  I have had some issues with this in the past where a reboot of OPNsense has resolved the issue, but this is not the case this time.
I have found that bsnmpd stops crashing when I disable MibII, but MibII is what I would like to use.
I am unsure where the logs are kept, but nothing appears to be written to /var/log/system.log
Any assistance to fault find this problem would be great and thanks in advance.

@fichtner this can be closed as old os-snmp is EoL


REPL file loading

[x] Allow using :l (and :load) to load a file into the REPL.
[x] Add :r to reload already loaded files.

I'd like to add support for reloading files before finishing this off, but there's a coupel of questions worth resolving:

Should using :load reset the environment. This is useful, as there won't be artifacts from previous :loads.
If we do reset the environment, how does one load multiple files? One possibility would be to specify multiple files to :load. Obviously the whole module resolution thing is a whole 'nother discussion, but...
How should :reload handle file order (if we don't have variadic load)?

I really need to clean up the REPL code at some point. Well, anything which needs to convert "plain text" into core.


Add node_confirms default bucket props

This is an upstream PR of two PRs already merged/tested on the nhs-fork.
The original PRs are:

https://github.com/nhs-riak/riak_core/pull/1
https://github.com/nhs-riak/riak_core/pull/8

See https://github.com/basho/riak_kv/pull/1663 for full details. This PR supports that KV feature.

I'm getting quickcheck errors on this branch - output attached
out.riak_core.rdb-upstream-pr-node-confirms.txt

But those errors are fixed on develop-2.2, right?

Are you asking that I rebase on basho/develop-2.2 and re-push? Or fix the issue again? I kind of assumed you'd merge to develop-2.2 locally and run the tests (since that is what the end result would be after the merge.)

Ah - let me try the rebase/merge and see if I can get it to work - yep the errors were familiar.

Rebase and pass 👍
out.riak_core.rdb-upstream-pr-node-confirms-after-rebase.txt
For the record - rebar.config needed merging - after the rebase the rebar.config looked like the following (forgive the formatting) :
{erl_first_files, ["src/gen_nb_server.erl", "src/riak_core_gen_server.erl",
		   "src/riak_core_stat_xform"]}.
{cover_enabled, true}.
{erl_opts, [warnings_as_errors, {parse_transform, lager_transform},
            debug_info, {platform_define, "^[0-9]+", namespaced_types},
            {platform_define, "^R15", "old_hash"}]}.
{edoc_opts, [{preprocess, true}]}.
{eunit_opts, [verbose]}.
{xref_checks, []}.
{xref_queries, [{"(XC - UC) || (XU - X - B - \"(cluster_info|dtrace)\" : Mod)", []}]}.

{deps, [
  {basho_stats   , ".*" , {git , "git://github.com/basho/basho_stats.git"      , {branch , "master"}}}        ,
  {clique        , ".*" , {git , "https://github.com/basho/clique.git"         , {branch , "develop-2.2"}}}   ,
  {eleveldb      , ".*" , {git , "git://github.com/basho/eleveldb.git"         , {branch , "2.0"}}}           ,
  {exometer_core , ".*" , {git , "git://github.com/basho/exometer_core.git"    , {branch , "master"}}}        ,
  {lager         , ".*" , {git , "git://github.com/basho/lager.git"            , {tag    , "3.2.4"}}}         ,
  {pbkdf2        , ".*" , {git , "git://github.com/basho/erlang-pbkdf2.git"    , {branch , "master"}}}        ,
  {poolboy       , ".*" , {git , "git://github.com/basho/poolboy.git"          , {branch , "develop-2.2.5"}}} ,
  {riak_ensemble , ".*" , {git , "https://github.com/basho/riak_ensemble"      , {branch , "develop-2.2"}}}   ,
  {riak_sysmon   , ".*" , {git , "https://github.com/basho/riak_sysmon.git"    , {tag    , "2.1.5"}}}
]}.

cheers @bryanhuntesl, I'll sort out the rebar.config. Forks and rebar.config are hard.


Add Dockerfile for x86 architecture

I was not able to run your image on the following docker env:
Client:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.7.1
 Git commit:   bb80604
 Built:        Sun Oct 16 07:57:31 UTC 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 17:00:50 2016
 OS/Arch:      linux/amd64

For this reason I've created an ubuntu based docker image that works on my x86 env. It is available on docker hub: dsantoro/pocket2kindle.

Hi @acca,
I am happy to accept the MR, but the docker images are in other repo:
https://github.com/alvaroreig/docker
If you ask for the MR and rename the folder to pocket2kindle-amd64 (as the current one is called pocket2kindle-arm) I will accept it and modify the Readme of pocket2kindle to provide the details of the images.
Regards,

Why not keep Dokerfiles inside the same repository ? This let you manage development and distribution/deployment from the same codebase, moreover it is more easier to receive help from contributors.
Anyway, as you prefer, here is the new PR: https://github.com/alvaroreig/docker/pull/1


[TED] extractor rewrite

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
TED has restructured their site and a rewrite for TED extractor is required (#2343).
changes:

rewrite talks and playlist handling
added series handling
removed handling /watch/ urls (was very old code and new watch pages no longer contains a single video as the old extractor expects)

I have used quite a bit of the old parsing code as some of them still matches the new json structure. There are parts of code which I am not sure if they are still necessary with their new player (e.g. audio_download and rtmp source), but since they are not fatal I chose to leave them as is.

Add some tests for playlist, series and #season

I was trying to use series_id instead of id, it works with the binary but the test is complaining that the id key is not present.
Is there a way around this or shall I just leave it to use id?

This was a partial review.
Remove useless/obvious comments and add or <empty object> after every try_get and .get used to get iterables.

Thanks for the review, I have committed the suggested changes.
by the way, for this issue I mentioned above, it may not be directly related to this PR but I want some insights from the reviewers.

I was trying to use series_id instead of id, it works with the binary but the test is complaining that the id key is not present. Is there a way around this or shall I just leave it to use id?
Traceback (most recent call last):
  File "P:\BT\software\yt-dlp\test\test_download.py", line 191, in test_template
    expect_info_dict(self, res_dict, test_case.get('info_dict', {}))
  File "P:\BT\software\yt-dlp\test\helper.py", line 257, in expect_info_dict
    test_info_dict = sanitize_got_info_dict(got_dict)
  File "P:\BT\software\yt-dlp\test\helper.py", line 238, in sanitize_got_info_dict
    if test_info_dict.get('display_id') == test_info_dict['id']:
KeyError: 'id'

common.py states that playlist 'can' have 'id' which means it is not compulsory.
https://github.com/yt-dlp/yt-dlp/blob/32b95bb6436fd17ee21cd55217f16361d4e7494a/yt_dlp/extractor/common.py#L385-L395
But the test helper seems to be treating 'id' as compulsory and therefore using test_info_dict['id'] and not test_info_dict.get('id')?
https://github.com/yt-dlp/yt-dlp/blob/32b95bb6436fd17ee21cd55217f16361d4e7494a/test/helper.py#L237-L239
Which should be the correct behavior?

Probably an oversight. I'll look into it. Playlist Id is optional


Rotate global workqueue database and recreate views

Production global workqueue database is reasonably sized, however it's views have grown beyond the limits and they are almost 50x bigger than the database itself. From CMSWEB's report:
TOTAL SIZE(MB)       HOST                   DB NAME    DB SIZE(MB)    VIEWS SIZE(MB)         DOCS      DELETED
-------------------------------------------------------------------------------------------------------
      61814.10  vocms0740                 workqueue        1448.26          60365.84        29618       863516

besides that, most of the documents are now deleted.
For further reference, we need to save the permanent docs (non-deleted) into a new database and swap them during the intervetion. I have started this investigation a couple of weeks ago, but I faced several couch crashes and instabilities.
I'll create a wiki page with all the instructions and then we can discuss the final bits, @ticoann

Production workqueue database was rotated today. It had around 1400 valid docs, 930k deleted docs and it was taking 1.4GB of disk space. Views were contributing to 70GB!!!
New database with the valid docs only has ~20MB and views are around 15MB.
Closing

Wonderful, Thanks Alan, Lina. @amaltaro, @h4d4


Optional exponential backoff

Amazon recommends using exponential backoff on 5xx errors and on ProvisionedThroughputExceededException responses.  I haven't tested this code yet, but wanted to see if there is interest in including it in the project.  If so I'll clean it up and get some documentation written.

@jlafon @danielhochman curious on your thoughts

@joshowen What about using botocore's implementation?

My opinion:
I'm a fan of handling retries at the application layer. As an example, botocore's retry logic is not well understood. When this kind of handling is on by default, it's sure to behave unexpectedly during an outage or throttling, and can mask real issues with the application in the case that it does recover operations. Some may also want more granular retry logic (e.g. per operation), in which case you have to rewrite it yourself anyways.
If we do ship something like this I would vote for it to be off by default.

I actually didn't know botocore had an implementation included.  This PR has retrying disabled by default, and I'm currently using it in production without any issues.  Is there any interest in including it in the project?

@jlafon any thoughts on including this functionality in the project?  Happy to rewrite to use BotoCore's implementation if you want it included.

@joshowen Using botocore's sounds like a good idea.

superseded by #135


[HOP-3704] remove poi dependency from jsoninput

https://issues.apache.org/jira/browse/HOP-3704
Following this checklist to help us incorporate your contribution quickly and easily:

[X] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[X] Each commit in the pull request should have a meaningful subject line and body.
[X] Format the pull request title like [HOP-XXX] - Fixes bug in SessionManager,
where you replace HOP-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the commit message.
[X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[X] Run mvn clean install apache-rat:check to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[X] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using git rebase -i.

Trivial changes like typos do not require a JIRA issue (javadoc, comments...).
In this case, just format the pull request title like (DOC) - Add javadoc in SessionManager.
If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[X] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
[ ] In any other case, please file an Apache Individual Contributor License Agreement.

The POI dependency is only there for an IOUtils.closeQuietly call.
The module already has its own closeQuietly method anyway.
The recent POI 5.2.0 build is causing build failures - eg https://ci-builds.apache.org/job/Hop/job/Hop-integration-tests/513/
POI 5.2.0 uses log4j-api and has a number of other dependencies.

Tested the integration test and they work again, thanks @pjfanning!


Added HelioHost

Added PHP 5.4, 5.5, 5.6, 7.0, and 7.1 from heliohost.org to hosts.yml

Thanks for persisting with this!


python sandbox not working properly

I was recently trying python builder sandbox and it produced an empty folder.

Related to: https://github.com/threefoldtech/jumpscaleX/issues/612

refactored @ branch: development_builder @ commit: https://github.com/threefoldtech/jumpscaleX/commit/5ef815b2922ce0f29f461270db710582f3aedb28
sample generated flist: https://hub.grid.tf/hammam/python3.flist.md for v3.6.8

Branch: development, Commit: 688ba59a635e50ed30551fe7ff37bdeecf84ffbd


No UI for imported/preexisting intent

Is your feature request related to a problem? Please describe.
I'm importing intents from predefined .LU files (e.g. General LU with cancel, help, etc). This works well, and I think will help as we deliver templates and samples that use LU to customers, but there is no UI support in the main window for using these intents.
Describe the solution you'd like
There are two things that I think would be helpful in the UI for this scenario:

When I create a new intent trigger for the dialog, I would like to be able to select from any intents that are already present or imported into the .lu file for the recognizer, rather than always having to type in the existing intent name and skip the utterances input.

In the settings for the trigger, I would like to see some indication that it is using an imported intent or a link to the intent. Right now, I see an empty "Trigger Phrases" box and have to open the LU tab manually to find the imported intent. If I could see the utterances there it would help me know its already configured.

(Added tag of "Type: Bug" since with the new templates many users will encounter this)

(@vivekkshankar tagging you as fyi. you might have already considered this case in your trigger redesign explorations.)