proto, pkg, docs: update CSR docstrings

Closes #863.
Signed-off-by: William Woodruff<EMAIL_ADDRESS>cc @haydentherapper

The diff is still failing, for reasons that aren't clear to me...is it possible protoc behaves differently on macOS vs. Linux in terms of comment generation?

@woodruffw Are you using Go 1.19.4? Differences in Go versions can also cause issues

@woodruffw Are you using Go 1.19.4? Differences in Go versions can also cause issues

go version go1.18.2 darwin/amd64 according to go version, so pretty old 😅. I'll update and re-build.


Several examples appear broken following recent changes

The example runs shows several example regressions, per @rparrett on Discord.

[ ] ui_texture_*,
[ ] custom_shader_instancing
[ ] asset_decompression
[ ] volumetric_fog
[ ] transparency_2d (changed, not sure if broken)

Retained rendering world #15320 or various required components changes are both plausible.
This is in addition to #15563.

I think deferred_rendering is broken too
2024-10-01T19:43:15.414646Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 11 Pro", kernel: "22631", cpu: "AMD Ryzen 9 7950X 16-Core Processor", core_count: "16", memory: "63.2 GiB" }
HookApp::findGameWindow, injectWindow:<PHONE_NUMBER>000000
HookApp::findGameWindow, graphicsWindow:<PHONE_NUMBER>000000
OverlayConnector::onMessage,overlay.init
2024-10-01T19:43:16.256784Z  INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce RTX 2080 Ti", vendor: 4318, device: 7687, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "560.94", backend: Vulkan }
2024-10-01T19:43:16.750808Z  INFO bevy_winit::system: Creating new window "App" (0v1#4294967296)
HookApp::deferHook,
HookApp::findGameWindow, injectWindow:<PHONE_NUMBER>000000
HookApp::findGameWindow, graphicsWindow:<PHONE_NUMBER>480DA8
2024-10-01T19:43:16.862308Z  INFO bevy_input::gamepad: Gamepad 44v1#4294967340 connected.
2024-10-01T19:43:17.191075Z  WARN bevy_pbr::render::mesh_view_bindings: Too many textures in mesh pipeline view layout, this might cause us to hit `wgpu::Limits::max_sampled_textures_per_shader_stage` in some environments.
HookApp::deferHook,
2024-10-01T19:43:18.219489Z ERROR wgpu_core::device::global: Device::create_render_pipeline error: Error matching ShaderStages(FRAGMENT) shader requirements against the pipeline
2024-10-01T19:43:18.219683Z ERROR wgpu::backend::wgpu_core: Handling wgpu errors as fatal by default
thread 'Async Compute Task Pool (3)' panicked at C:\Users\chris\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-22.1.0\src\backend\wgpu_core.rs:3411:5:
wgpu error: Validation Error

Caused by:
  In Device::create_render_pipeline, label = 'deferred_lighting_pipeline'
    Error matching ShaderStages(FRAGMENT) shader requirements against the pipeline
      Shader global ResourceBinding { group: 0, binding: 22 } is not available in the pipeline layout
        View dimension D3 (is array: false) doesn't match the binding Sampler(Filtering)

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::render_resource::pipeline_cache::PipelineCache::process_pipeline_queue_system`!
thread '<unnamed>' panicked at C:\Users\chris\tmp\bevy\crates\bevy_render\src\render_resource\pipeline_cache.rs:580:28:
index out of bounds: the len is 0 but the index is 14
Encountered a panic in system `bevy_render::renderer::render_system`!

@ChristopherBiscardi Agreed: https://github.com/bevyengine/bevy/issues/15525

Meshlet example/rendering is also broken :(

3d in wasm/webgpu is also broken since https://github.com/bevyengine/bevy/pull/13497
1 error(s) generated while compiling the shader:
:704:25 error: no matching call to textureSampleLevel(texture_depth_2d_array, sampler, vec2<f32>, i32, f32)

14 candidate functions:
  textureSampleLevel(texture: texture_depth_2d_array, sampler: sampler, coords: vec2<f32>, array_index: A, level: L) -> f32  where: A is i32 or u32, L is i32 or u32
  textureSampleLevel(texture: texture_2d_array<f32>, sampler: sampler, coords: vec2<f32>, array_index: A, level: f32) -> vec4<f32>  where: A is i32 or u32
  textureSampleLevel(texture: texture_depth_2d_array, sampler: sampler, coords: vec2<f32>, array_index: A, level: L, offset: vec2<i32>) -> f32  where: A is i32 or u32, L is i32 or u32
  textureSampleLevel(texture: texture_cube_array<f32>, sampler: sampler, coords: vec3<f32>, array_index: A, level: f32) -> vec4<f32>  where: A is i32 or u32
  textureSampleLevel(texture: texture_depth_2d, sampler: sampler, coords: vec2<f32>, level: L, offset: vec2<i32>) -> f32  where: L is i32 or u32
  textureSampleLevel(texture: texture_depth_cube_array, sampler: sampler, coords: vec3<f32>, array_index: A, level: L) -> f32  where: A is i32 or u32, L is i32 or u32
  textureSampleLevel(texture: texture_2d_array<f32>, sampler: sampler, coords: vec2<f32>, array_index: A, level: f32, offset: vec2<i32>) -> vec4<f32>  where: A is i32 or u32
  textureSampleLevel(texture: texture_depth_2d, sampler: sampler, coords: vec2<f32>, level: L) -> f32  where: L is i32 or u32
  textureSampleLevel(texture: texture_2d<f32>, sampler: sampler, coords: vec2<f32>, level: f32, offset: vec2<i32>) -> vec4<f32>
  textureSampleLevel(texture: texture_2d<f32>, sampler: sampler, coords: vec2<f32>, level: f32) -> vec4<f32>
  textureSampleLevel(texture: texture_depth_cube, sampler: sampler, coords: vec3<f32>, level: L) -> f32  where: L is i32 or u32
  textureSampleLevel(texture: texture_3d<f32>, sampler: sampler, coords: vec3<f32>, level: f32, offset: vec3<i32>) -> vec4<f32>
  textureSampleLevel(texture: texture_3d<f32>, sampler: sampler, coords: vec3<f32>, level: f32) -> vec4<f32>
  textureSampleLevel(texture: texture_cube<f32>, sampler: sampler, coords: vec3<f32>, level: f32) -> vec4<f32>

    let sampled_depth = textureSampleLevel(directional_shadow_texturesX_naga_oil_mod_XMJSXM6K7OBRHEOR2NVSXG2C7OZUWK527MJUW4ZDJNZTXGX, directional_shadow_textures_linear_samplerX_naga_oil_mod_XMJSXM6K7OBRHEOR2NVSXG2C7OZUWK527MJUW4ZDJNZTXGX, light_local_3, array_index_3, 0f);
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

it's also broken in wasm/webgl2 for another reason:
wgpu error: Validation Error

Caused by:
  In Device::create_bind_group, label = 'mesh_view_bind_group'
    Buffer binding 8 range 20480 exceeds `max_*_buffer_binding_size` limit 16384

3d in wasm/webgpu is also broken since #13497
1 error(s) generated while compiling the shader:
:704:25 error: no matching call to textureSampleLevel(texture_depth_2d_array, sampler, vec2<f32>, i32, f32)

14 candidate functions:
  textureSampleLevel(texture: texture_depth_2d_array, sampler: sampler, coords: vec2<f32>, array_index: A, level: L) -> f32  where: A is i32 or u32, L is i32 or u32
  textureSampleLevel(texture: texture_2d_array<f32>, sampler: sampler, coords: vec2<f32>, array_index: A, level: f32) -> vec4<f32>  where: A is i32 or u32
  textureSampleLevel(texture: texture_depth_2d_array, sampler: sampler, coords: vec2<f32>, array_index: A, level: L, offset: vec2<i32>) -> f32  where: A is i32 or u32, L is i32 or u32
  textureSampleLevel(texture: texture_cube_array<f32>, sampler: sampler, coords: vec3<f32>, array_index: A, level: f32) -> vec4<f32>  where: A is i32 or u32
  textureSampleLevel(texture: texture_depth_2d, sampler: sampler, coords: vec2<f32>, level: L, offset: vec2<i32>) -> f32  where: L is i32 or u32
  textureSampleLevel(texture: texture_depth_cube_array, sampler: sampler, coords: vec3<f32>, array_index: A, level: L) -> f32  where: A is i32 or u32, L is i32 or u32
  textureSampleLevel(texture: texture_2d_array<f32>, sampler: sampler, coords: vec2<f32>, array_index: A, level: f32, offset: vec2<i32>) -> vec4<f32>  where: A is i32 or u32
  textureSampleLevel(texture: texture_depth_2d, sampler: sampler, coords: vec2<f32>, level: L) -> f32  where: L is i32 or u32
  textureSampleLevel(texture: texture_2d<f32>, sampler: sampler, coords: vec2<f32>, level: f32, offset: vec2<i32>) -> vec4<f32>
  textureSampleLevel(texture: texture_2d<f32>, sampler: sampler, coords: vec2<f32>, level: f32) -> vec4<f32>
  textureSampleLevel(texture: texture_depth_cube, sampler: sampler, coords: vec3<f32>, level: L) -> f32  where: L is i32 or u32
  textureSampleLevel(texture: texture_3d<f32>, sampler: sampler, coords: vec3<f32>, level: f32, offset: vec3<i32>) -> vec4<f32>
  textureSampleLevel(texture: texture_3d<f32>, sampler: sampler, coords: vec3<f32>, level: f32) -> vec4<f32>
  textureSampleLevel(texture: texture_cube<f32>, sampler: sampler, coords: vec3<f32>, level: f32) -> vec4<f32>

    let sampled_depth = textureSampleLevel(directional_shadow_texturesX_naga_oil_mod_XMJSXM6K7OBRHEOR2NVSXG2C7OZUWK527MJUW4ZDJNZTXGX, directional_shadow_textures_linear_samplerX_naga_oil_mod_XMJSXM6K7OBRHEOR2NVSXG2C7OZUWK527MJUW4ZDJNZTXGX, light_local_3, array_index_3, 0f);
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

it's also broken in wasm/webgl2 for another reason:
wgpu error: Validation Error

Caused by:
  In Device::create_bind_group, label = 'mesh_view_bind_group'
    Buffer binding 8 range 20480 exceeds `max_*_buffer_binding_size` limit 16384

Which example is this? I tried a couple of the 3d examples but they all worked on wasm/webgl2 for me.

Which example is this? I tried a couple of the 3d examples but they all worked on wasm/webgl2 for me.

examples pbr and 3d_scene. after testing on more browsers, it crashes in Safari and Chromium, but works in Firefox after freezing for a few seconds

Which example is this? I tried a couple of the 3d examples but they all worked on wasm/webgl2 for me.

examples pbr and 3d_scene. after testing on more browsers, it crashes in Safari and Chromium, but works in Firefox after freezing for a few seconds

Ah, I was testing in firefox. I didn't expect it to be browser-specific, fun.

Which example is this? I tried a couple of the 3d examples but they all worked on wasm/webgl2 for me.

examples pbr and 3d_scene. after testing on more browsers, it crashes in Safari and Chromium, but works in Firefox after freezing for a few seconds

Both of those work for me with webgl2 on firefox and chromium on Linux. I hope it's not OSX specific =/

from https://docs.rs/wgpu/latest/wgpu/struct.Limits.html#method.downlevel_webgl2_defaults, I guess max_*_buffer_binding_size is max_uniform_buffer_binding_size which should be limited to 16KiB on WebGL2. It's not mandatory for browser to respect it, but it's the standard... and we're requesting more

auto_exposure also seems completely broken. (tested macos, win/4080)

All of the examples in the original message work for me (I just checked them off in the message). I've tested all of the other examples mentioned and they either (1) work for me or (2) have a separate tracking issue.
I'm closing this out. If you identify a case that is still broken, please open a new issue scoped to it.

Opened #15997 and #15998. They may be platform specific if you weren't able to reproduce.


Updated addresses

Some of the addresses were updated when I ran the 'house_contacts.py' script.
First time contributor, feedback welcome!

Looks great, thanks!


remove useless file

there is a useless nuget.exe file in the template, it should be removed

nuget.exe was deleted from template


Fix some spelling

@Ph0tonic please squash your commits, then we can merge.

And please put in a commit message with at least a reasonable subject line (just take the PR title).


add: funders page

fixes #66
Desktop view:

Mobile view:

Looks perfect, thanks a lot @tanya17-05 👏
@git-anurag-hub: please have a quick look and merge if all is fine from your end.
In the meantime, if you like, you can look at another issue, @tanya17-05.


Building Nota in a flake: Error: Cannot find module '.../build.mjs'

I am trying to package Nota in the following flake:
{
  inputs = {
    dream2nix.url = "github:nix-community/dream2nix";
    nota.url =<EMAIL_ADDRESS>    nota.flake = false;
  };

  outputs = {
    self,
    dream2nix,
    nota,
  } @ inp:
    (dream2nix.lib.makeFlakeOutputs {
      systems = ["x86_64-linux"];
      config.projectRoot = ./.;
      source = nota;
      settings = [
        {
          subsystemInfo.noDev = true;
          subsystemInfo.nodejs = 18;
        }
      ];
    })
    // {
      checks = self.packages;
    };
}

After resolving impurities I get this error with nix build
><EMAIL_ADDRESS>build
> node build.mjs
node:internal/modules/cjs/loader:949
  throw err;
  ^
Error: Cannot find module<EMAIL_ADDRESS>    at Module._resolveFilename (node:internal/modules/cjs/loader:946:15)
    at Module._load (node:internal/modules/cjs/loader:787:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

I suspect it has to do with the file extension .mjs as seen here but I'm not sure. Even if overriding something here would fix it, I wouldn't know how to approach it. The output of nix flake show is as expected:
git+file:///home/kento/work
├───checks
│   └───x86_64-linux
│       ├───"@nota-lang/nota": derivation '__at__nota-lang__slash__nota-0.4.12'
│       ├───default: derivation '__at__nota-lang__slash__nota-0.4.12'
│       └───resolveImpure: derivation 'resolve'
├───devShell
│   └───x86_64-linux: development environment 'nix-shell'
├───devShells
│   └───x86_64-linux
│       ├───"@nota-lang/nota": development environment 'nix-shell'
│       └───default: development environment 'nix-shell'
├───packages
│   └───x86_64-linux
│       ├───"@nota-lang/nota": package '__at__nota-lang__slash__nota-0.4.12'
│       ├───default: package '__at__nota-lang__slash__nota-0.4.12'
│       └───resolveImpure: package 'resolve'
└───projectsJson: unknown

Any help is appreciated!

Running ls in the node_modules directory for nota shows that there is no build.mjs, cross referencing this dir with https://github.com/nota-lang/nota/tree/master/packages/nota shows that many files and folders are missing, could be something wrong with the discoverer?
total 36
drwxr-xr-x   4 nixbld1 nixbld  4096 Sep 19 18:20 .
drwxr-xr-x   4 nixbld1 nixbld  4096 Sep 19 18:20 ..
drwxr-xr-x   2 nixbld1 nixbld  4096 Jan  1  1970 dist
-rw-r--r--   1 nixbld1 nixbld  1052 Jan  1  1970 LICENSE
drwxr-xr-x 290 nixbld1 nixbld 12288 Sep 19 18:20 node_modules
-rw-r--r--   1 nixbld1 nixbld  2160 Sep 19 18:20 package.json
-rw-r--r--   1 nixbld1 nixbld  2161 Sep 19 18:20 package.json.bak

nota.url =<EMAIL_ADDRESS>

The problem is, that you are building from a tarball coming from npmjs.org. The releases there are usually pre-built and stripped down. Therefore you cannot build the package again.
Try building from github instead.
Closing, as this is not an issue we can fix. Feel free to open a new issue if there are problems with the github release as well.


The stdlib function env() is deprecated

In the alloy logs the message:
level=warn msg="this stdlib function is deprecated; please refer to the documentation for updated usage and alternatives" controller_path=/ contr │
│ oller_id=pod_logs.feature function=env

shows up quite frequently.  The env() function has been deprecated and is not sys.env() https://grafana.com/docs/alloy/latest/reference/stdlib/sys/#sysenv

Fixed in https://github.com/grafana/k8s-monitoring-helm/pull/1027


Building iOS flutter Error, Cycle inside Runner

I recently upgrade my flutter app to v1.17.5 and getting the below error when trying to run or build the iOS flutter application. I'm not sure whether I should switch the order of some script in the build phase. Any help is appreciated! Thanks

error: Cycle inside Runner; building could produce unreliable results. This usually can be resolved by moving the target's Headers build phase before Compile Sources.
    Cycle details:
    → Target 'Runner': LinkStoryboards
    ○ Target 'Runner' has compile command with input '/Users/ivanchau/AndroidStudioProjects/fella/ios/Runner/Base.lproj/LaunchScreen.storyboard'
    ○ Target 'Runner': Ditto /Users/ivanchau/AndroidStudioProjects/fella/build/ios/Debug-development-iphonesimulator/Runner.swiftmodule/Project/x86_64-apple-ios-simulator.swiftsourceinfo /Users/ivanchau/Library/Developer/Xcode/DerivedData/Runner-gsqfvskdiydqcdftydqhgqbekwhx/Build/Intermediates.noindex/Runner.build/Debug-development-iphonesimulator/Runner.build/Objects-normal/x86_64/Runner.swiftsourceinfo
    ○ Target 'Runner' has compile command for Swift source files
    ○ That command depends on command in Target 'Runner': script phase “Flutter”
    ○ Target 'Runner' has process command with output '/Users/ivanchau/AndroidStudioProjects/fella/build/ios/Debug-development-iphonesimulator/Runner.app/Info.plist'
    ○ Target 'Runner' has compile command with input '/Users/ivanchau/AndroidStudioProjects/fella/ios/Runner/Base.lproj/LaunchScreen.storyboard'
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Constructing build description
    warning: Mapping architecture armv7 to i386. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target 'image_picker' from project 'Pods')
    warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target 'image_picker' from project 'Pods')

Logs
 info • Unused import: 'package:font_awesome_flutter/font_awesome_flutter.dart' • lib/components/RoundTextField.dart:2:8 • unused_import
   info • 'title' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is headline6. This feature was deprecated after v1.13.8. •
          lib/components/backdrop.dart:166:39 • deprecated_member_use
   info • The member 'lerp' can only be used within instance members of subclasses of 'package:flutter/src/animation/tween.dart' • lib/components/backdrop.dart:304:59 •
          invalid_use_of_protected_member
   info • Unused import: 'package:fella/style.dart' • lib/components/button/roundButton.dart:2:8 • unused_import
   info • Unused import: 'package:fella/constants.dart' • lib/components/card/showSurveyCard.dart:2:8 • unused_import
   info • Unused import: 'package:fella/layouts/survey/surveyVote.dart' • lib/components/card/showSurveyCard.dart:4:8 • unused_import
   info • Unused import: 'package:fella/layouts/survey/surveyVote.dart' • lib/components/card/surveyCard.dart:4:8 • unused_import
   info • Unused import: 'package:fella/components/imageBox.dart' • lib/components/card/systemAnnouncementCard.dart:3:8 • unused_import
   info • Unused import: 'package:fella/components/button/roundButton.dart' • lib/components/card/systemAnnouncementCard.dart:4:8 • unused_import
   info • Unused import: 'package:fella/data/viewmodels/groupModel.dart' • lib/components/card/systemAnnouncementCard.dart:6:8 • unused_import
   info • Unused import: 'package:provider/provider.dart' • lib/components/card/systemAnnouncementCard.dart:8:8 • unused_import
   info • Don't import implementation files from another package • lib/components/charts/baseCharts/customCircleSymbolRenderer.dart:11:8 • implementation_imports
   info • Don't import implementation files from another package • lib/components/charts/baseCharts/customCircleSymbolRenderer.dart:12:8 • implementation_imports
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: NumberRow.title, NumberRow.value, NumberRow.min,
          NumberRow.updateVal • lib/components/form/NumberRow.dart:6:7 • must_be_immutable
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LoginTextField.label, LoginTextField.icon,
          LoginTextField.obscure, LoginTextField.textInputType, LoginTextField.controller • lib/components/loginTextField.dart:3:7 • must_be_immutable
   info • 'YearPicker' is deprecated and shouldn't be used. Use CalendarDatePicker instead. This feature was deprecated after v1.15.3. • lib/components/picker.dart:90:21 • deprecated_member_use
   info • 'body1' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText2. This feature was deprecated after v1.13.8. •
          lib/components/picker.dart:183:56 • deprecated_member_use
   info • 'subhead' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is subtitle1. This feature was deprecated after v1.13.8. •
          lib/components/row/titleRow.dart:41:56 • deprecated_member_use
   info • Name non-constant identifiers using lowerCamelCase • lib/constants.dart:95:22 • non_constant_identifier_names
   info • Name non-constant identifiers using lowerCamelCase • lib/constants.dart:104:35 • non_constant_identifier_names
   info • Unused import: 'package:flutter/material.dart' • lib/customClass/userListItem.dart:2:8 • unused_import
   info • The exception variable 'e' isn't used, so the 'catch' clause can be removed • lib/data/calendar.dart:19:33 • unused_catch_clause
   info • Unused import: 'package:fella/data/firebaseObj/survey.dart' • lib/data/services/api.dart:9:8 • unused_import
   info • Unused import: 'dart:collection' • lib/data/services/api/statistics.dart:2:8 • unused_import
   info • Cancel instances of dart.async.StreamSubscription • lib/data/viewmodels/eventModel.dart:17:22 • cancel_subscriptions
   info • Avoid empty statements • lib/data/viewmodels/groupModel.dart:292:5 • empty_statements
   info • Dead code • lib/data/viewmodels/groupModel.dart:292:5 • dead_code
   info • Unused import: 'package:fella/constants.dart' • lib/data/viewmodels/userModel.dart:5:8 • unused_import
   info • Unused import: 'package:firebase_storage/firebase_storage.dart' • lib/data/viewmodels/userModel.dart:13:8 • unused_import
   info • Unused import: 'package:fella/constants.dart' • lib/layoutBase/baseListGroupSelectLayout.dart:2:8 • unused_import
   info • This method overrides a method annotated as '@mustCallSuper' in 'AutomaticKeepAliveClientMixin', but doesn't invoke the overridden method • lib/layouts/dashboard/dashboard.dart:232:10 •
          must_call_super
   info • 'subhead' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is subtitle1. This feature was deprecated after v1.13.8. •
          lib/layouts/dashboard/leaderPage.dart:116:58 • deprecated_member_use
   info • This method overrides a method annotated as '@mustCallSuper' in 'AutomaticKeepAliveClientMixin', but doesn't invoke the overridden method • lib/layouts/dashboard/leaderPage.dart:534:10 •
          must_call_super
   info • Unused import: 'package:fella/style.dart' • lib/layouts/dashboard/submit.dart:25:8 • unused_import
   info • The target expression uses '?.', so its value can be null • lib/layouts/dashboard/tablePage.dart:168:17 • can_be_null_after_null_aware
   info • Unused import: 'package:fella/data/viewmodels/groupModel.dart' • lib/layouts/event/eventMgt.dart:7:8 • unused_import
   info • Unused import: 'package:cached_network_image/cached_network_image.dart' • lib/layouts/event/eventMgt.dart:10:8 • unused_import
   info • Unused import: 'package:fella/layoutBase/baseListLayout.dart' • lib/layouts/event/eventMgt.dart:13:8 • unused_import
   info • Unused import: 'package:transparent_image/transparent_image.dart' • lib/layouts/event/eventMgt.dart:16:8 • unused_import
   info • Unused import: 'package:flutter_linkify/flutter_linkify.dart' • lib/layouts/event/eventPage.dart:24:8 • unused_import
   info • 'subhead' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is subtitle1. This feature was deprecated after v1.13.8. •
          lib/layouts/group/formEdit.dart:62:52 • deprecated_member_use
   info • Unused import: 'package:fella/components/row/customListTile.dart' • lib/layouts/group/groupEdit.dart:7:8 • unused_import
   info • Unused import: 'package:fella/layouts/group/formEdit.dart' • lib/layouts/group/groupEdit.dart:14:8 • unused_import
   info • Unused import: 'package:fella/layouts/group/roleEdit.dart' • lib/layouts/group/groupEdit.dart:15:8 • unused_import
   info • 'subhead' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is subtitle1. This feature was deprecated after v1.13.8. •
          lib/layouts/group/roleEdit.dart:94:56 • deprecated_member_use
   info • This method overrides a method annotated as '@mustCallSuper' in 'AutomaticKeepAliveClientMixin', but doesn't invoke the overridden method • lib/layouts/home/homePage.dart:177:10 •
          must_call_super
   info • Unused import: 'package:firebase_storage/firebase_storage.dart' • lib/layouts/home/infoPage.dart:6:8 • unused_import
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ActivatePage.email, ActivatePage.password •
          lib/layouts/login/activatePage.dart:12:7 • must_be_immutable
   info • This method overrides a method annotated as '@mustCallSuper' in 'AutomaticKeepAliveClientMixin', but doesn't invoke the overridden method • lib/layouts/profile/profile.dart:370:10 •
          must_call_super
   info • Unused import: 'package:fella/layouts/group/roleEdit.dart' • lib/layouts/survey/surveyEdit.dart:15:8 • unused_import
   info • Unused import: 'package:fella/components/statText.dart' • lib/layouts/survey/surveyManagement.dart:7:8 • unused_import
   info • Unused import: 'dart:collection' • lib/layouts/survey/surveyResults.dart:1:8 • unused_import
   info • Unused import: 'dart:math' • lib/layouts/survey/surveyResults.dart:3:8 • unused_import
   info • Unused import: 'package:fella/components/button/roundButton.dart' • lib/layouts/survey/surveyResults.dart:5:8 • unused_import
   info • Unused import: 'package:fella/components/row/userRow.dart' • lib/layouts/survey/surveyResults.dart:9:8 • unused_import
   info • Unused import: 'package:fella/data/firebaseObj/user.dart' • lib/layouts/survey/surveyResults.dart:14:8 • unused_import
   info • Unused import: 'package:fella/data/viewmodels/userModel.dart' • lib/layouts/survey/surveyResults.dart:17:8 • unused_import
   info • Unused import: 'package:fella/util.dart' • lib/layouts/survey/surveyResults.dart:19:8 • unused_import
   info • 'subhead' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is subtitle1. This feature was deprecated after v1.13.8. •
          lib/layouts/userForm/contactComponents.dart:40:50 • deprecated_member_use
   info • This method overrides a method annotated as '@mustCallSuper' in 'AutomaticKeepAliveClientMixin', but doesn't invoke the overridden method • lib/layouts/userForm/userPermission.dart:329:10
          • must_call_super
   info • This method overrides a method annotated as '@mustCallSuper' in 'AutomaticKeepAliveClientMixin', but doesn't invoke the overridden method • lib/layouts/userForm/userStatistics.dart:78:10
          • must_call_super
   info • Unused import: 'dart:math' • lib/layouts/userMgt/adminPage.dart:1:8 • unused_import
   info • Unused import: 'package:fella/style.dart' • lib/layouts/userMgt/adminPage.dart:41:8 • unused_import
   info • Unused import: 'package:fella/data/viewmodels/userModel.dart' • lib/layouts/userMgt/emailSettings.dart:2:8 • unused_import
   info • Unused import: 'dart:io' • lib/layouts/userMgt/newGroup.dart:1:8 • unused_import
   info • Unused import: 'dart:math' • lib/layouts/userMgt/roleManagement.dart:2:8 • unused_import
   info • Unused import: 'dart:io' • lib/layouts/userMgt/selectMembers.dart:1:8 • unused_import
   info • Unused import: 'package:fella/style.dart' • lib/layouts/userMgt/selectMembers.dart:11:8 • unused_import

[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.4 19E287, locale en-CA)
    • Flutter version 1.17.5 at /Users/ivanchau/Documents/flutter
    • Framework revision 8af6b2f038 (2 weeks ago), 2020-06-30 12:53:55 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/ivanchau/Library/Android/sdk
    • Platform android-29, build-tools 28.0.3
    • ANDROID_HOME = /Users/ivanchau/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

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

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)

What is the script the Flutter build phase?  Did you add that?  It's not in a newly created project.  The one in a newly created project doesn't have any input or output dependencies.

That's just the regular "Run Script". I just rename it to Flutter

It's complaining about the Info.plist input, which isn't in a default Flutter create template.  Why did you add that?
Additionally, it means Flutter will never re-compile your dart code unless you touch the Info.plist, or clean your workspace...

That is one of the instruction in the flutter_crashlytics package: https://pub.dev/packages/flutter_crashlytics
I no longer use that package anymore so I just removed and ran flutter clean then flutter run. I'm still getting a similar error message.
error: Cycle inside Runner; building could produce unreliable results.
    Cycle details:
    → Target 'Runner': LinkStoryboards
    ○ Target 'Runner' has compile command with input '/Users/ivanchau/AndroidStudioProjects/fella/ios/Runner/Base.lproj/LaunchScreen.storyboard'
    ○ That command depends on command in Target 'Runner': script phase “Frabic”
    ○ Target 'Runner' has process command with output '/Users/ivanchau/AndroidStudioProjects/fella/build/ios/Debug-production-iphonesimulator/Runner.app/Info.plist'
    ○ Target 'Runner' has compile command with input '/Users/ivanchau/AndroidStudioProjects/fella/ios/Runner/Base.lproj/LaunchScreen.storyboard'
    note: Using new build system
    note: Building targets in parallel
    note: Planning build

The instructions at https://pub.dev/packages/flutter_crashlytics says to add that for fabric, not Flutter.
Okay now it's complaining about your "Frabic" build phase having a LaunchScreen.storyboard input and a Info.plist output.
    ○ Target 'Runner' has process command with output '/Users/ivanchau/AndroidStudioProjects/fella/build/ios/Debug-production-iphonesimulator/Runner.app/Info.plist'
    ○ Target 'Runner' has compile command with input '/Users/ivanchau/AndroidStudioProjects/fella/ios/Runner/Base.lproj/LaunchScreen.storyboard'
    note: Using new build system

You added a bunch of stuff to your Xcode project which it's now unhappy about, this isn't related to Flutter.

But I did not add LaunchScreen as an input in any of the build phase scripts. Does the order of the script matters?

You can upload your ios/Runner.xcodeproj/project.pbxproj and I can take a look.


Yarp.ReverseProxy 2.0.0 has a DOS vulnerability

Yarp.ReverseProxy 2.0.0 has a Denial of Service Vulnerability. This vulnerability is fixed in v2.0.1.
See here: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-33141
I've created PR #27 to fix this.

Thanks, I merged it and published a new version


Update .gitignore

build folder - or maybe explicitly
- CMakeFiles
- cmake_install.cmake
- CMakeCache.txt
- Makefile

Possibly other things.

Found this, may be helpful

gist https://github.com/kigster/cmake-project-template/blob/8c583cafb7d5101098746bcef9a5bcfd3c5cd565/.gitignore
Kitware's own gitignore https://gitlab.kitware.com/cmake/cmake/-/blob/master/.gitignore not sure why they have pyc in there

Also, CMake tip about arbitrarily named build dirs might be useful

https://www.scivision.dev/cmake-auto-gitignore-build-dir/

Fixed by #80


Zm   kill containers

@thieman @paetling
Adding this flag to restart will be a pretty different implementation, so looking at doing that as a second PR.

@thieman @paetling this is updated. I still want to add another integration test for stoping just some services with --rm flag

@thieman updated with additional integration tests


DML review of consumed-odata-service.md

Some review changes.
Important note
Currently it contains the sentence OData version – the OData version: Mendix supports consuming OData 3 and OData 4 and I proposed a change. This is an important change. We don't want to make customers think we have full support for OData V4 yet.

SDM review feedback and updates.


feat: add handler for self-care password expired

Task linked: CU-86958met0 Application does not show the real error message

Another point related to this pull request, for my demo task I need an email, which I often have to retrieve through the getUser method. Maybe we should add the user to the application state to avoid making the same requests frequently.
For example:
`  Future _getAction(String tab) async {
final account = await _webtritApiClient.getUserInfo(_token);
_logger.info('_prepareRequest: $account');
return _webtritApiClient.createDemoData(DemoCredential(
  type: _platformInfo.appType,
  identifier: _appInfo.identifier,
  email: account.email!,
  tenantId: _tenantId,
  action: tab,
));

}`

Another point related to this pull request, for my demo task I need an email, which I often have to retrieve through the getUserInfo method. Maybe we should add the user to the application state to avoid making the same requests frequently.
For example:
  Future<DemoData> _getAction(String tab) async {
    final account = await _webtritApiClient.getUserInfo(_token);
    _logger.info('_prepareRequest: $account');

    return _webtritApiClient.createDemoData(DemoCredential(
      type: _platformInfo.appType,
      identifier: _appInfo.identifier,
      email: account.email!,
      tenantId: _tenantId,
      action: tab,
    ));
  }

or maybe just pull email from login flow   void _onLogined(AppLogined event, Emitter emit) async {

@Freezed(copyWith: false)
class AppLogined with _$AppLogined implements AppEvent {
const factory AppLogined({
required String coreUrl,
required String tenantId,
required String token,
}) = _AppLogined;
}


when more than one page is opened, that resources for each new page are requested more times than they should

<EMAIL_ADDRESS>commented:

Note: This might be related to https://groups.google.com/group/phantomjs/browse_thread/thread/3f7a76c88c4dbca7
but i doubt it.
Which version of PhantomJS are you using?

Version 1.2.0
What steps will reproduce the problem?

Follow my code on http://pastebin.com/3AbWMGZz

uncomment the lines at the top starting with urlList as specified to
test with multiple urls
run the code phantomjs mycode.js

What is the expected output? What do you see instead?
Expected:
Report for http://www.chrischiu.com/testblank1 Load time 118 RequestsTotal : 1
Report for http://www.chrischiu.com/testblank2 Load time 117 RequestsTotal : 1
Result:
Report for http://www.chrischiu.com/testblank1 Load time 118 RequestsTotal : 2
Report for http://www.chrischiu.com/testblank2 Load time 117 RequestsTotal : 1
So to summarise, if you have 1 url. that url gets requested once.
If you have 2 urls, the first one gets requested once, the second one gets requested twice. (it continues on, the third 3 times and so on)
Try this on any page with just a blank html content. if you try this on the same page multiple times you can see this however when printing the address, you won't be able to tell the difference between the page counts
Which operating system are you using?
Tested on :
ubuntu 11.04 phantom 1.2.0
OSX 10.7 (from brew) phantom 1.2.0
Did you use binary PhantomJS or did you compile it from source?
ubuntu:
source via: http://code.google.com/p/phantomjs/wiki/BuildInstructions
sudo apt-get install libqt4-dev libqtwebkit-dev qt4-qmake
git clone git://github.com/ariya/phantomjs.git && cd phantomjs
git checkout 1.2
qmake-qt4 && make
OSX - brew
Please provide any additional information below.

I'm fairly sure this is a problem with phantomjs but it could be a misunderstanding of the code. This is just one example of where something is definitely wrong.
Originally the problem stemmed from trying to access
resource.endReply.status;
after loading has completed by doing a foreach on resources.
resource.endReply was null on some of them which caused the script to stop.
I wrote the example code to try and debug if something odd was happening somewhere.

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #183.
:star2:   6 people had starred this issue at the time of migration.

With phantomjs 2.0 each page is loaded only once.


Added a back to top option

Added a back to top option in the readme file. On clicking it the webpage will scroll to the top.

No thank you.


Image repositories are not disabled by yum anymore

Concreate was chaged in a way, that existing repositories in image
are not disabled during build phase. This enables easy community
images development.

Do not merge, I found a bug I need to fix during community image streams builds.

this should be ready to merge now


Intermittent failures

I mention internal thoughtbot code in this issue, but hey.
The following feature in Trajectory features/users/estimate_stories.feature:56 in the commit 76948caff4fd711324b5e87afc9d2a4c9b80ab61 fails intermittently with the error:
@javascript
Scenario: Estimate multiple stories that affect the number of iterations when the inline story form is visible # features/users/estimate_stories.feature:56
Given today is "August 2, 2010"                                                                              # features/step_definitions/time_steps.rb:1
And I am signed in as a member of the "Snacks" project                                                       # features/step_definitions/user_steps.rb:26
Validation failed: Account can't be blank (ActiveRecord::RecordInvalid)
./features/step_definitions/user_steps.rb:29:in /^I (?:am signed in|sign in) as a member of the "([^"]+)" project$/'       features/users/estimate_stories.feature:58:in And I am signed in as a member of the "Snacks" project'
And the "Snacks" project has a default velocity of 20 points                                                 #

I am not sure if I should open another ticket, but I have experienced intermittent failures too from FactoryGirl when using capybara-webkit. I am getting the following:
Background:                                     # features/books.feature:5
Given I am not authenticated                  # features/step_definitions/devise_steps.rb:5
And I am a new, authenticated user            # features/step_definitions/devise_steps.rb:13
And A donor exists with a name of "Anonymous" # factory_girl-2.2.0/lib/factory_girl/step_definitions.rb:118
And A bin exists with a name of "Top Shelf"   # factory_girl-2.2.0/lib/factory_girl/step_definitions.rb:118
And the following books exists:               # factory_girl-2.2.0/lib/factory_girl/step_definitions.rb:100
  | title   | author  | published | publisher | recommendation | donor           | bin             |
  | Walden  | Thoreau | 1854      | foo       | undecided      | name: Anonymous | name: Top Shelf |
  | AWOCAMR | Thoreau | 1849      | bar       | keep           | name: Anonymous | name: Top Shelf |
  NoMethodError: undefined method `fields' for nil:NilClass:           SELECT DISTINCT(attr.attname)
            FROM pg_attribute attr
            INNER JOIN pg_depend dep ON attr.attrelid = dep.refobjid AND attr.attnum = dep.refobjsubid
            INNER JOIN pg_constraint cons ON attr.attrelid = cons.conrelid AND attr.attnum = cons.conkey[1]
            WHERE cons.contype = 'p'
              AND dep.refobjid = $1::regclass
   (ActiveRecord::StatementInvalid)
  features/books.feature:10:in `And the following books exists:'
And I am on the home page                     # features/step_definitions/web_steps.rb:44
And I follow "Books"                          # features/step_definitions/web_steps.rb:56

When I run it again, all is well.
This same block of code, I've gotten this error for a different step:
Background:                                     # features/books.feature:5
Given I am not authenticated                  # features/step_definitions/devise_steps.rb:5
And I am a new, authenticated user            # features/step_definitions/devise_steps.rb:13
And A donor exists with a name of "Anonymous" # factory_girl-2.2.0/lib/factory_girl/step_definitions.rb:118
And A bin exists with a name of "Top Shelf"   # factory_girl-2.2.0/lib/factory_girl/step_definitions.rb:118
  NoMethodError: undefined method `fields' for nil:NilClass: INSERT INTO "bins" ("active", "created_at", "name", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id" (ActiveRecord::StatementInvalid)
  features/books.feature:9:in `And A bin exists with a name of "Top Shelf"'
And the following books exists:               # factory_girl-2.2.0/lib/factory_girl/step_definitions.rb:100
  | title   | author  | published | publisher | recommendation | donor           | bin             |
  | Walden  | Thoreau | 1854      | foo       | undecided      | name: Anonymous | name: Top Shelf |
  | AWOCAMR | Thoreau | 1849      | bar       | keep           | name: Anonymous | name: Top Shelf |
And I am on the home page                     # features/step_definitions/web_steps.rb:44
And I follow "Books"                          # features/step_definitions/web_steps.rb:56

I also have a test that fails intermittently about 20% of the time. I'm using capybara-webkit in a Test::Unit integration test.
@cpytel, this is a pretty old issue. Has capybara-webkit been working reliably for you guys, or are you still experiencing these kinds of intermittent issues?

We've gotten a lot of the problems fixed but I understand that there may still be intermitted failures.
On Jan 3, 2012, at 10:11 AM, sbleon wrote:

I also have a test that fails intermittently about 20% of the time. I'm using capybara-webkit in a Test::Unit integration test.
@cpytel, this is a pretty old issue. Has capybara-webkit been working reliably for you guys, or are you still experiencing these kinds of intermittent issues?

Reply to this email directly or view it on GitHub:
https://github.com/thoughtbot/capybara-webkit/issues/80#issuecomment-3340966

Chad Pytel, Founder and CEO
thoughtbot, inc.
t:<PHONE_NUMBER> x113
f:<PHONE_NUMBER>
http://www.thoughtbot.com
http://www.twitter.com/thoughtbot


python39Packages.rope: fix tests

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

One test of python39.pkgs.python-languageserver fails.

Result of nixpkgs-review pr 117231 at dd1e228a run on aarch64-linux 1

7 packages failed to build:

spyder (python38Packages.spyder)
python39Packages.pyls-black
python39Packages.pyls-isort
python39Packages.pyls-mypy
python39Packages.pyls-spyder
python39Packages.python-language-server
python39Packages.spyder

12 packages built successfully:

cq-editor
nixpkgs-pytools (python38Packages.nixpkgs-pytools)
python38Packages.pyls-black
python38Packages.pyls-isort
python38Packages.pyls-mypy
python38Packages.pyls-spyder
python38Packages.python-language-server
python38Packages.rope
python38Packages.spyder_3
python39Packages.nixpkgs-pytools
python39Packages.rope
python39Packages.spyder_3

1 suggestion:

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/rope/default.nix:31:5:
   |
31 |     license = licenses.gpl2;
   |     ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

Strange. On macos 10.14, every python39Packages.rope test fails with something along the lines of:
======================================================================
ERROR: test_adding_arguments_for_norm_args_chang_calls_with_kwords (ropetest.refactor.change_signature_test.ChangeSignatureTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/private/tmp/nix-build-python3.9-rope-0.18.0.drv-0/rope-0.18.0/ropetest/refactor/change_signature_test.py", line 15, in setUp
    self.project = testutils.sample_project()
  File "/private/tmp/nix-build-python3.9-rope-0.18.0.drv-0/rope-0.18.0/ropetest/testutils.py", line 34, in sample_project
    remove_recursively(root)
  File "/private/tmp/nix-build-python3.9-rope-0.18.0.drv-0/rope-0.18.0/ropetest/testutils.py", line 61, in remove_recursively
    _remove_recursively(path)
  File "/private/tmp/nix-build-python3.9-rope-0.18.0.drv-0/rope-0.18.0/ropetest/testutils.py", line 70, in _remove_recursively
    shutil.rmtree(path)
  File "/nix/store/895zhsk82r78zc1ayq8nbw3ygq1r55jl-python3-3.9.2/lib/python3.9/shutil.py", line 718, in rmtree
    _rmtree_safe_fd(fd, path, onerror)
  File "/nix/store/895zhsk82r78zc1ayq8nbw3ygq1r55jl-python3-3.9.2/lib/python3.9/shutil.py", line 655, in _rmtree_safe_fd
    _rmtree_safe_fd(dirfd, fullname, onerror)
  File "/nix/store/895zhsk82r78zc1ayq8nbw3ygq1r55jl-python3-3.9.2/lib/python3.9/shutil.py", line 675, in _rmtree_safe_fd
    onerror(os.unlink, fullname, sys.exc_info())
  File "/nix/store/895zhsk82r78zc1ayq8nbw3ygq1r55jl-python3-3.9.2/lib/python3.9/shutil.py", line 673, in _rmtree_safe_fd
    os.unlink(entry.name, dir_fd=topfd)
PermissionError: [Errno 13] Permission denied: 'config.py'
-------------------- >> begin captured logging << --------------------
root: DEBUG: Using /tmp/sample_project as root of the project.
--------------------- >> end captured logging << ---------------------

😕
Can anyone confirm?

Can anyone confirm?

Same for me and already on master. Going to ignore this for now.


Dots - No bottom margin on v1.6.0

The bottom margin is not applied when dots are rendered.
It works fine on v1.5.9

This could be change in css in original slick library


Replace stale with stable and update

The stale mechanism for view queries conflates two independent
concerns:

Whether or not the view results should be returned from a "stable"
set of shards; i.e., mem3:ushards. This semantic is new in 2.0,
having originated in Cloudant code in 20111.

Whether or not the view in question should be updated prior to
responding to the user, i.e., the pre-2.0 semantics.

Both of these concerns represent consistency/availability tradeoffs, but
they're addressing rather different aspects of that continuum. As such,
the "stale" mechanism limits flexibility.
For example, it's quite likely that a user would want to retrieve
"stale" view responses from the fastest available shards - the
"available/available" choice - and this choice is not available with the
existing "stale" mechanism. A similar argument could be made for the
"consistent/consistent" choice.
This patch introduces two new view API keywords - "stable" and "update"

to address concerns #1 and #2, respectively. The semantics of the
"stale" mechanism is implemented in terms of these new keywords.

COUCHDB-3063

This is WIP.

Tests pass along with a fabric change and a couchdb change.


Related Image Schema v2 check should automatically pass on an image that is already certified by Red Hat

Describe the solution you'd like.
This check parses all related images and tries to confirm that their manifest reflects schemaVersion: 2.
If a related image has already been certified (i.e. exists in Red Hat's certified registries), we should assume that the image passes this validation (i.e. we don't need to re-check it).
With this in mind, it might make sense that we check the images that exist in Red Hat registries against the Pyxis API (https://catalog.redhat.com/api/containers/v1/ui/), then we remove the need to provide credentials to Red Hat registries in order to pull and manually validate that image.
Additional context.
This was discussed in the community meeting on 2021-08-26.

This check is no longer in scope, which makes this issue obsolete. Closing!


Release v2.2.6

MACS v2.2.6 (tuned for speed):

Speed up MACS2 with some programming tricks and code cleanup.

The filter_dup function replaces separate_dups. The later one was
implemented for potentially putting back duplicate reads in
certain downstream analysis. However such analysis hasn't been
implemented.

Optimize the speed of writing bedGraph files by using C fprintf correctly.

Optimize BAM and BAMPE parsing with pointer casting instead of python
unpack.

Do not check "track" and "comment" lines in BED file

Bugs fixed

Cutoff-analysis in callpeak command. #341

Other

cmdlinetest script in test/ folder has been updated to: 1. test
cutoff-analysis with callpeak cmd; 2. output the 2 lines before
and after the error or warning message during tests; 3. output
only the first 10 lines if the difference between test result and
standard result can be found; 4. prockreport monitor CPU time and
memory usage in 1 sec interval -- a bit more accurate.

Add unit-testing for PairedEndTrack. Cleaned some unit testing script.

Will hold this release until #340 is solved.

Unittesting and tiny testing SAM file has been added for #347


Run your example TDM main.ipynb exit RuntimeError: applying transform <monai.transforms.io.dictionary.LoadImaged object at 0x73c8370c57c0>

My environment is as follows:
numpy==1.22.0
monai==0.9.1
nibabel ==3.2.1
I've modified it according to what you said yesterday and still get the above error.

I hope you can help me with this, thanks！

Sorry for the late response. Do you still have problem now? It seems to me that Monai still not able to detect the "reader libraries". Could you double check whether you install it or not? If already installed, maybe restart the whole environment would be helpful.


Removed CentOS 5 from dockers.  Fixed #1295.

Looks good to me, if you pull in the latest changes from master, I'd be happy to merge 👍


Forward constants in local.tee translation with constant value inputs

Before this change the translator forwarded the assigned local variable instead of C. However, it is possible in this particular case to forward the constant value instead of the local variable which improves code generation of following instructions due to improved optimization opportunities.

Note: The clippy CI issue seems to be a bug in clippy since I cannot see how the flagged code can be unconditionally recursive.


findOneOrCreate not working with "useX" query

When filtering by columns of a related model, an issued findOneOrCreate will fail due to unknown columns in result for the model to create.
<?php

class ObjectIdentityQuery extends BaseObjectIdentityQuery
{
    public function filterByAclObjectIdentity(ObjectIdentityInterface $objectIdentity)
    {
        $this
            ->useAclClassQuery()
                ->filterByType($objectIdentity->getType())
            ->endUse()
            ->filterByIdentifier($objectIdentity->getIdentifier())
        ;

        return $this;
    }
}

A valid work-around:
<?php
class ObjectIdentityQuery extends BaseObjectIdentityQuery
{
    public function filterByAclObjectIdentity(ObjectIdentityInterface $objectIdentity)
    {
        $aclClass = AclClass::fromAclObjectIdentity($objectIdentity);
        $this
            ->filterByClassId($aclClass->getId())
            ->filterByIdentifier($objectIdentity->getIdentifier())
        ;

        return $this;
    }
}

I think the only thnig that Propel can do is to throw and exception when findOneOrCreate() is used in conjunction with join(), since there is nothing Propel can do to transform joins into subqueries just for this case.

Ah, I see there is already an exception, but it's not clear. I'll rewrite it.

Well, imho it should work. In case the object could not be found, it should be created, even if a join() is used. However I didn't take a deeper look into it by now, but planning to do. Please don't close this issue with the #287 as a solution.

That means leaving aside the foreign keys, which is a bug IMHO:
$book = BookQuery::create()
  ->filterByPrice(125)
  ->useAuthorQuery()
    ->filterByFirstName('Leo')
  ->endUse()
  ->findOneOrCreate();

If not found, the newly created Book object should be set 125 as price, AND the pk of the author named "Leo" as author_id.

Yep, correct.

I have to correct my third step, just to be sure, save is not issued by findOneOrCreate() so it stays by returning an object as mentioned which will yield isNew to be true. (That's the way it currently works.)

No, it should not be buggy :-) Let me give it a try, the worst thing: I will fail at some point, but better than never tried.

Ok, give it a try :)

havvg/Propel@413a077cf33c7244caf0563d8b3cf0d65770165b
Well, I don't have the propel testsuite set up right now, but with manually testing, this works.
I will add unit tests for this as soon as I got the testsuite up again.
What do you think about it so far? @fzaninotto

VERY hackish, very preliminary.
What would you do for a left join?
What would you do for custom conditions on related tables?
What would you do for two-steps joins?
What would you do for joins with multiple conditions?

Good questions, showing the need of tests, definitely!
Didn't thought about relation graphs, very good point.
Multiple conditions should work already, the others would probably fail right now.
Thanks for the feedback, opened many test cases!


pin ubuntu version

aiming to fix #7867

fyi if we do this, we also need to downgrade snapcraft's base on electron-builder config. Downgrading that brought it's own set of problems (see https://github.com/Kong/insomnia/pull/5555)
side-note, for taking the other route (prepping for ubuntu 24), some things that need to be fixed first on electron-builder side:

allow for core24 https://snapcraft.io/core24
allow for different gnome plug https://github.com/electron-userland/electron-builder/blob/15ce5b4164378f7398ff84cabe8ee97eef5cfd1b/packages/app-builder-lib/templates/snap/snapcraft.yaml#L133C1-L136C38


FEATURE REQUEST: It's hard to understand what is happening in a migration file

Hi
I was looking into this migration file, to understand what kind of things I changed...
/// <reference path="../pb_data/types.d.ts" />
migrate((db) => {
  const dao = new Dao(db)
  const collection = dao.findCollectionByNameOrId("bf6zd9b9bsb1zo5")

  collection.listRule = null
  collection.viewRule = null
  collection.createRule = null
  collection.updateRule = null
  collection.deleteRule = null

  return dao.saveCollection(collection)
}, (db) => {
  const dao = new Dao(db)
  const collection = dao.findCollectionByNameOrId("bf6zd9b9bsb1zo5")

  collection.listRule = ""
  collection.viewRule = ""
  collection.createRule = ""
  collection.updateRule = ""
  collection.deleteRule = ""

  return dao.saveCollection(collection)
})

I can see that some things are happening to a collection, but I don't know what collection these things are happening to.
Proposed solution:
I think simply adding a comment like this could solve the issue.
// Collection Name: `users`
const collection = dao.findCollectionByNameOrId("bf6zd9b9bsb1zo5")

We can also do the same to explain the difference between the first and the second functions used inside the migrate function.
That's all.
thanks.

I don't think this is necessary as the collection name should be already part of the autogenerated migration file.

I don't think this is necessary as the collection name should be already part of the autogenerated migration file.

I just noticed that 👍


useless variable (refactoring)

In https://github.com/ImagicTheCat/vRP/blob/master/vrp/client/basic_garage.lua at line 18 :
  local i = 0
    while not HasModelLoaded(mhash) and i < 10000 do
      RequestModel(mhash)
      Citizen.Wait(10)
    end

variable i is never edited therefore the second condition is always true it might be refactored by
    while not HasModelLoaded(mhash) do
      RequestModel(mhash)
      Citizen.Wait(10)
    end

Thanks, the variable is used to prevent infinite request loop in case of invalid model (max 100 seconds).
Fixed.

Ok that's what I was thinking too


[Redesign]: Dependency groups aren't spaced correctly

In the versions tab of the display package page redesign, the dependency groups are too close to each other:

@dannyjdev You can verify this by looking at the "Dependencies" tab that supports multiple target frameworks. The TFM headings shouldn't be too close to each other.


update kubetest2 release repo

Signed-off-by: cwen0<EMAIL_ADDRESS>What problem does this PR solve?

fix e2e:
14:41:22  info: downloading kubetest2 v0.1.0
14:41:22    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
14:41:22                                   Dload  Upload   Total   Spent    Left  Speed
14:41:23
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     9  100     9    0     0      7      0  0:00:01  0:00:01 --:--:--     7
14:41:23
14:41:23  gzip: stdin: not in gzip format

What is changed and how does it work?
Check List

Tests

Unit test
E2E test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has Go code change
Has CI related scripts change
Has Terraform scripts change

Side effects

Breaking backward compatibility

Related changes

Need to update the documentation

Does this PR introduce a user-facing change?

NONE

Codecov Report

Merging #701 into master will decrease coverage by 1.29%.
The diff coverage is 36.12%.

@@            Coverage Diff             @@
##           master     #701      +/-   ##
==========================================
- Coverage   55.78%   54.49%   -1.30%
==========================================
  Files          68       69       +1
  Lines        4383     4652     +269
==========================================
+ Hits         2445     2535      +90
- Misses       1768     1927     +159
- Partials      170      190      +20

Impacted Files
Coverage Δ

api/v1alpha1/networkchaos_types.go
22.98% <ø> (ø)

api/v1alpha1/podchaos_types.go
37.14% <ø> (ø)

controllers/networkchaos/netem/utils.go
0.00% <0.00%> (ø)

pkg/chaosdaemon/netlink_linux.go
0.00% <0.00%> (ø)

pkg/chaosdaemon/stress_server_linux.go
0.00% <0.00%> (ø)

pkg/chaosdaemon/tc_linux.go
42.85% <0.00%> (ø)

pkg/utils/chaosdaemon.go
51.21% <0.00%> (ø)

pkg/utils/grpc.go
0.00% <0.00%> (ø)

pkg/webhook/inject/inject.go
73.49% <0.00%> (-0.68%)
:arrow_down:

pkg/chaosdaemon/util.go
72.48% <9.09%> (-10.60%)
:arrow_down:

... and 16 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 9ace035...d063652. Read the comment docs.

/run-e2e-test


Column of the date and time of the test

Good afternoon!
Is it possible to add a column of the date and time of the test on the left/right, as was the case with the version from henrywhitaker3?

"Created" is when the test was run, all the way to the right

Thanks a lot!


False detection of changes

Hi,
I would like use bump-cli to track changes in specification. However I notice that there is a noise changes detected.
$ npm list  | grep 'bump-cli'
└──<EMAIL_ADDRESS>$ curl "https://api.production.selectstar.com/swagger/?format=openapi" | jq '.' > ./remote-openapi.json
...
$ ./node_modules/.bin/bump diff remote-openapi.json remote-openapi.json
* Comparing the two given definition files... done
[Breaking] Modified: PATCH /tags/{guid}/
  [Breaking] Body modified
    Attributes added: guid, name, description, richtext_description, icon, color, parent, ordinal, updated_on, owner, breadcrumbs, visible
    [Breaking] Attribute removed: items
  [Breaking] Response modified: 200
    Attributes added: guid, name, description, richtext_description, icon, color, parent, ordinal, updated_on, owner, breadcrumbs, visible
    [Breaking] Attribute removed: items

I would expect that the specification compared with itself is not able to generate any differences, but it is different, so the comparison has some bugs.
Could we make avoid that noise to make comparisons & changelog more reliable?
Kind regards

Hello @ad-m-ss,
Thanks for your bug report. I took a close look to the specification file you have shared (https://api.production.selectstar.com/swagger/?format=openapi) and noticed there's an issue in the operationId values used. Indeed, by the openapi specification, the “Operation object” has a possible operationId field which is defined by:

Unique string used to identify the operation. The id MUST be unique among all operations described in the API.

However you have two operations (PATCH /tags/{guid}/ and PATCH /tags/) which have the same operation id value of tags_partial_update. This leads our diff computation to compare those two operations (incorrectly, yes).
I would suggest to try to fix the operation Ids from your API definition and we will try to make some changes on our side to avoid this kind of incorrect difference (We will probably ignore any operations which has a duplicate operationId).
Let me know if this helps and if you have any further questions.
Good day to you :slightly_smiling_face:

Thanks for your analysis. I will fix that & keep you informed.

It helps! Thanks!

I am not sure that ignoring any operations is a good idea. I would prefer to have an error & refused that changes to be merged that silently ignore.

I am not sure that ignoring any operations is a good idea. I would prefer to have an error & refused that changes to be merged that silently ignore.

Thanks for the feedback, that definitely sounds like a better idea. :slightly_smiling_face:


Fix broken link in Scalability-checklist.md

Fixing issue #45 .

This document has been relocated to https://github.com/Azure/azure-content/blob/master/articles/best-practices-scalability-checklist.md


Not showing icon

Describe the bug
When user type one character in search bar it is showing not found however there is present icons from that character.
Expected behaviour
When user type one character in search bar it should show all present icons from that character.
Screenshots

Additional context
No response
Code of Conduct

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

Hi,
I would like to work on this issue. Can this be assigned to me under GSSOC'23 label please. Thank you

@pavitrachavda97 assigning this to you


build errors fix - clean dist folders before start

There are currently intermittent errors when running Perses on our main branch, this PR ensures all previous dist folders are cleaned before npm run start -w app is run.
Related to this discussion in #perses-dev.
Install errors Karan ran into: main_branch_npm_errors_ex.txt

Not sure if we really want to always be doing this before start since it basically eliminates all the benefits we get from Typescript's project cache.

Maybe we just update the README or other dev instructions to let folks know they can do this (along with removing node_modules and running npm install) to reset their environments if they have issues?

Was thinking more and since this happens occasionally in CI too, it’d be good to have some non-manual way to address this—what if we moved ‘npm run clean’ to run after all modules are installed (maybe in postinstall? @LukeTillman)
That wouldn’t affect local dev as much since we don’t reinstall that often and I think this comes about because of weird peerDependency issues


Add Helm section, update labs to use Helm

Currently the workshop is using kustomize for installing the demo app. Kustomize works well for examples and getting started but is not scalable for production. One concern here is that because the workshop is using kustomize, customer might assume it is best practice and adopt the pattern for production.
Change the workshop sample application installations to use helm.
Add a section explain what helm is, and different pattern of usage, here are some ideas:

dependency charts, making one chart dependent on the other. Use case, you are using network policies and most off the shelf charts don't support them, you can create an in-house helm chart and make the off the shelf one dependent on it.
how and when to use helm and kustomize together, i.e. post-render kustomize for helm charts you don't own:
https://github.com/thomastaylor312/advanced-helm-demos/tree/master/post-render
https://helm.sh/docs/topics/advanced/#post-rendering

Kustomize is suitable for production. We choose to use Kustomize for a number of reasons, primarily due to clarity in the YAML (for example, seeing which lines have changed when updating a deployment). That being said, I would be happy to introduce a section focusing on Helm. Can we open a [feat] request issue?


cargo check error: failed to run custom build command for afl v0.6.0

Question
cargo check failed
git tag: v4.0.0-rc
os: macos 10.15.4
cargo version: cargo 1.41.0-nightly (626f0f40e 2019-12-03)
rustc version: rustc 1.42.0-nightly (0de96d37f 2019-12-19)
log:
>> cargo check --all
    Checking libfuzzer-sys v0.3.1
    Checking hyper v0.13.3
    Checking libtitan_sys v0.0.1 (https://github.com/tikv/rust-rocksdb.git?branch=tikv-4.x#193485b1)
   Compiling afl v0.6.0
   Compiling grpcio-sys v0.5.0
   Compiling librocksdb_sys v0.1.0 (https://github.com/tikv/rust-rocksdb.git?branch=tikv-4.x#193485b1)
    Checking tidb_query_datatype v0.0.1 (/Users/xiaochen/project/tikv/components/tidb_query_datatype)
    Checking fuzz v0.0.1 (/Users/xiaochen/project/tikv/fuzz)
    Checking memoffset v0.5.1
    Checking parking_lot_core v0.6.2
    Checking raw-cpuid v7.0.3
   Compiling pprof v0.3.15
    Checking tipb_helper v0.0.1 (/Users/xiaochen/project/tikv/components/tipb_helper)
    Checking crossbeam-epoch v0.7.2
    Checking parking_lot v0.9.0
    Checking hyper-tls v0.4.1
    Checking rusoto_credential v0.43.0
error: failed to run custom build command for `afl v0.6.0`

Caused by:
  process didn't exit successfully: `/Users/xiaochen/project/tikv/target/debug/build/afl-5e0b1c47186415ee/build-script-build` (exit code: 101)
--- stdout
rm -f afl-gcc afl-fuzz afl-showmap afl-tmin afl-gotcpu afl-analyze afl-as as afl-g++ afl-clang afl-clang++ *.o *~ a.out core core.[1-9][0-9]* *.stackdump test .test test-instr .test-instr0 .test-instr1 qemu_mode/qemu-2.10.0.tar.bz2 afl-qemu-trace
rm -rf out_dir qemu_mode/qemu-2.10.0
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C llvm_mode clean
rm -f *.o *.so *~ a.out core core.[1-9][0-9]* test-instr .test-instr0 .test-instr1
rm -f ../afl-clang-fast ../afl-llvm-rt.o ../afl-llvm-rt-32.o ../afl-llvm-rt-64.o ../afl-clang-fast++
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C libdislocator clean
rm -f *.o *.so *~ a.out core core.[1-9][0-9]*
rm -f libdislocator.so
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C libtokencap clean
rm -f *.o *.so *~ a.out core core.[1-9][0-9]*
rm -f libtokencap.so
[*] Checking for the ability to compile x86 code...
[+] Everything seems to be working, ready to compile.
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-gcc.c -o afl-gcc
set -e; for i in afl-g++ afl-clang afl-clang++; do ln -sf afl-gcc $i; done
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-fuzz.c -o afl-fuzz
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-showmap.c -o afl-showmap
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-tmin.c -o afl-tmin
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-gotcpu.c -o afl-gotcpu
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-analyze.c -o afl-analyze
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" afl-as.c -o afl-as
ln -sf afl-as as
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN; AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/lib/afl\" -DDOC_PATH=\"/share/doc/afl\" -DBIN_PATH=\"/bin\" test-instr.c -o test-instr
echo 0 | ./afl-showmap -m none -q -o .test-instr0 ./test-instr
echo 1 | ./afl-showmap -m none -q -o .test-instr1 ./test-instr

Oops, the instrumentation does not seem to be behaving correctly!

Please ping<EMAIL_ADDRESS>to troubleshoot the issue.

--- stderr
make: *** [test_build] Error 1
thread 'main' panicked at 'assertion failed: status.success()', /Users/xiaochen/.cargo/registry/src/github.com-1ecc6299db9ec823/afl-0.6.0/build.rs:33:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed

I tried to build google afl, but the AFL_PATH is not same with cargo output:
♪  AFL git:(master) make
[*] Checking for the ability to compile x86 code...
[+] Everything seems to be working, ready to compile.
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-gcc.c -o afl-gcc
set -e; for i in afl-g++ afl-clang afl-clang++; do ln -sf afl-gcc $i; done
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-fuzz.c -o afl-fuzz
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-showmap.c -o afl-showmap
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-tmin.c -o afl-tmin
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-gotcpu.c -o afl-gotcpu
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-analyze.c -o afl-analyze
cc -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL
_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN
_PATH=\"/usr/local/bin\" afl-as.c -o afl-as
ln -sf afl-as as
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN; AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=.
 ./afl-clang -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN_PATH=\"/usr/local/bin\" test-instr.c -o test-instr
./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
echo 1 | ./afl-showmap -m none -q -o .test-instr1 ./test-instr
[+] All right, the instrumentation seems to be working!
[+] LLVM users: see llvm_mode/README.llvm for a faster alternative to afl-gcc.
[+] All done! Be sure to review README - it's pretty short and useful.

WARNING: Fuzzing on MacOS X is slow because of the unusually high overhead of
fork() on this OS. Consider using Linux or *BSD. You can also use VirtualBox
(virtualbox.org) to put AFL inside a Linux or *BSD VM.

NOTE: If you can read this, your terminal probably uses white background.
This will make the UI hard to read. See docs/status_screen.txt for advice.
♪  AFL git:(master) ✗ make install
[*] Checking for the ability to compile x86 code...
[+] Everything seems to be working, ready to compile.
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN; AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O3 -funroll-loops -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/local/lib/afl\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -DBIN_PATH=\"/usr/local/bin\" test-instr.c -o test-instr
./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
echo 1 | ./afl-showmap -m none -q -o .test-instr1 ./test-instr
[+] All right, the instrumentation seems to be working!
[+] LLVM users: see llvm_mode/README.llvm for a faster alternative to afl-gcc.
[+] All done! Be sure to review README - it's pretty short and useful.

WARNING: Fuzzing on MacOS X is slow because of the unusually high overhead of
fork() on this OS. Consider using Linux or *BSD. You can also use VirtualBox
(virtualbox.org) to put AFL inside a Linux or *BSD VM.

NOTE: If you can read this, your terminal probably uses white background.
This will make the UI hard to read. See docs/status_screen.txt for advice.
mkdir -p -m 755 ${DESTDIR}/usr/local/bin ${DESTDIR}/usr/local/lib/afl ${DESTDIR}/usr/local/share/doc/afl ${DESTDIR}/usr/local/share/afl
rm -f ${DESTDIR}/usr/local/bin/afl-plot.sh
install -m 755 afl-gcc afl-fuzz afl-showmap afl-tmin afl-gotcpu afl-analyze afl-plot afl-cmin afl-whatsup ${DESTDIR}/usr/local/bin
rm -f ${DESTDIR}/usr/local/bin/afl-as
if [ -f afl-qemu-trace ]; then install -m 755 afl-qemu-trace ${DESTDIR}/usr/local/bin; fi
if [ -f afl-clang-fast -a -f afl-llvm-pass.so -a -f afl-llvm-rt.o ]; then set -e; install -m 755 afl-clang-fast ${DESTDIR}/usr/local/bin; ln -sf afl-clang-fast ${DESTDIR}/usr/local/bin/afl-clang-fast++; install -m 755 afl-llvm-pass.so afl-llvm-rt.o ${DESTDIR}/usr/local/lib/afl; fi
if [ -f afl-llvm-rt-32.o ]; then set -e; install -m 755 afl-llvm-rt-32.o ${DESTDIR}/usr/local/lib/afl; fi
if [ -f afl-llvm-rt-64.o ]; then set -e; install -m 755 afl-llvm-rt-64.o ${DESTDIR}/usr/local/lib/afl; fi
set -e; for i in afl-g++ afl-clang afl-clang++; do ln -sf afl-gcc ${DESTDIR}/usr/local/bin/$i; done
install -m 755 afl-as ${DESTDIR}/usr/local/lib/afl
ln -sf afl-as ${DESTDIR}/usr/local/lib/afl/as
install -m 644 docs/README docs/ChangeLog docs/*.txt ${DESTDIR}/usr/local/share/doc/afl
cp -r testcases/ ${DESTDIR}/usr/local/share/afl
cp -r dictionaries/ ${DESTDIR}/usr/local/share/afl

And I also tried to install afl.rs, but it doesn't help:
♪  tikv git:(issue-7220) cargo install afl
    Updating crates.io index
  Downloaded afl v0.8.0
  Downloaded 1 crate (2.7 MB) in 4.20s
  Installing afl v0.8.0
  Downloaded atty v0.2.14
  Downloaded unicode-width v0.1.7
   Compiling semver-parser v0.7.0
   Compiling libc v0.2.69
   Compiling bitflags v1.2.1
   Compiling xdg v2.2.0
   Compiling unicode-width v0.1.7
   Compiling vec_map v0.8.1
   Compiling ansi_term v0.11.0
   Compiling strsim v0.8.0
   Compiling cc v1.0.52
   Compiling semver v0.9.0
   Compiling textwrap v0.11.0
   Compiling rustc_version v0.2.3
   Compiling afl v0.8.0
   Compiling atty v0.2.14
   Compiling clap v2.33.0
    Finished release [optimized] target(s) in 37.70s
  Installing /Users/xiaochen/.cargo/bin/cargo-afl
   Installed package `afl v0.8.0` (executable `cargo-afl`)

Btw, the slack invite link of tikv-wg is outdated

Btw, the slack invite link of tikv-wg is outdated

I have joined it

@breeswish PTAL

I found afl.rs v0.8.0 could be build successfully on my mac, and v0.6.0 not.
And tikv use v0.6 currently, should we upgrade dependency of afl to 0.8?

can repro.

I have the same problem, build on mac(OSX version: 10.15.3), got error:
error: failed to run custom build command for afl v0.6.0

how did you solve it?

@iosmanthus Could you help resolve this issue?

In TiKV, fuzz tests are organized as workspace members, not as dependences,  so it is hard to compile them conditionally. However, if you are facing afl compiling problem, I suggest that you run cargo check with --exclude flag to ignore checking the fuzz. (maybe a little bit verbose)
cargo check --exclude fuzz --exclude fuzzer-afl --exclude fuzzer-libfuzzer --exclude fuzzer-honggfuzz --workspace

@XiaochenCui For now, please consider not to check the fuzz/fuzzer-* workspace members.
cargo check \
	--exclude fuzzer-afl \
	--exclude fuzzer-libfuzzer \
	--exclude fuzzer-honggfuzz \
	--workspace

Maybe we can add this flags to our Makefile.

@iosmanthus

I believe this issue is resolved via https://github.com/tikv/tikv/pull/8011 by excluding fuzzers explicitly. Feel free to comment if you are still meeting this issue. Thanks!


fix: Upgrade spring boot version

Please first merge PR# https://github.com/eclipse-tractusx/managed-service-orchestrator/pull/39
Veracode issue fix by upgrading spring boot version

postgres is still restricted, pls rerun dash

@Siegfriedk , We have re-run it in morning but request still under review. https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/9159

@Siegfriedk  - This can be merged.

@Siegfriedk Latest DEPENDENCIES file push with remove all restricted library use


[tarantool] Update to new releases (2.10 and 1.10)

Thanks for the PR, meanwhile the automation already took care of the update, see https://github.com/endoflife-date/endoflife.date/commit/beea04e64a50d5c25ce2b9a0eca1346641c1d48e
For tarantool we only have to add new release cycles.


build: update dependencies to remove vulnerabilities

npm audit was showing lots of vulnerabilities, yikes! This resolves every single one of them ✅
cc @christo4ferris

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: update the status of geo-replication destination connection

Fixes #118
Master Issue: #
Motivation
The status of the  pulsarconnection  which is used for geo-replication destination connection is not updated.
Modifications

Update the status of the pulsar connection which is used for indicating the geo-replication destination connection after the PulsarGeoReplication is created successfully.

Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation
Check the box below.
Need to update docs?

[ ] doc-required
(If you need help on updating docs, create a doc issue)

[x] no-need-doc
(Please explain why)

[ ] doc
(If this PR contains doc changes)

@FushuWang We can merge this.


Fix: Output Appending Issue for Each Scan on a Single Project

Description:
This PR addresses issue #79, where the output of multiple scans on a single project was appended to the same JSON file. The changes introduced in this PR ensure that a unique file is created for each scan, preventing the output of different scans from being appended to the same file.
Key Changes:

[x] Added a new generate_unique_filename function that generates a unique file name within the output directory by appending a counter to the base name if a file with the same name already exists. This function is essential in preventing the overwriting or appending of previous scan results, as it ensures that each new scan will be saved in a separate file with a unique name.

[x] Updated the crawl_loop function in src/gcp_scanner/scanner.py to use the generate_unique_filename function when saving the output of the scan. This ensures that a new, unique file is created for each scan, rather than appending the output to an existing file.

By implementing these changes, the output of each scan is now saved in a separate file, eliminating the issue of appending scan results to the same file. This makes it easier for users to analyze the output of individual scans and prevents the unintentional merging of scan results. The generate_unique_filename function plays a crucial role in ensuring that each scan's output is saved in a distinct file, which ultimately enhances the usability and reliability of the GCP resource scanner.
Related Issues
fixes #79

we have #84 already addressing this problem.
Thank you for pointing this out. I understand that there is already an ongoing PR (#84) that addresses the same issue. My approach offers an alternative solution to the problem, and I'm aware that the existing PR might be outdated and result in conflicts.

Considering the lack of response from the author of the old PR, I would like to propose my solution for your review. If you find it beneficial or more suitable for the project, I am willing to work on integrating the changes. If you think this PR should be closed, that is fine as well.
Please let me know your thoughts and how you would like to proceed with this matter.

we have #84 already addressing this problem.

Thank you for pointing this out. I understand that there is already an ongoing PR (#84) that addresses the same issue. My approach offers an alternative solution to the problem, and I'm aware that the existing PR might be outdated and result in conflicts.
Considering the lack of response from the author of the old PR, I would like to propose my solution for your review. If you find it beneficial or more suitable for the project, I am willing to work on integrating the changes. If you think this PR should be closed, that is fine as well.
Please let me know your thoughts and how you would like to proceed with this matter.

There is #84 that's almost ready for merge. I'd close this PR.

#84 has been merged. Closing this one.


fix(names-in-underlying-database): Make client call more readable

Hi @do4gr can you take a look at this and see if the syntax is solid, etc? There's a comment about the syntax, you can see the comment when you click on "Resolve conflict."
Thanks for your help with resolving, and hopefully merging, this PR!

Before/After:


"how to write custom service listeners" missing on Doc

The doc [1] explains it will also explain how to write custom service listeners. But the content is not providing that information at all. It needs to be added.
[1] https://ballerina.io/learn/how-to-extend-ballerina/

Assigning this to @jeradrutnam to have a look at getting the Java syntax coloring done.


2.x

review the gora

@TerminusSatani please close and delete this pull request. If you have a pull request for the 2.x branch then it needs to be made against that branch. Thank you

@TerminusSatani please close this Pull Request


Console cleanup

#1017

@Velua Can we remove all console.timer?
Can you look at things thrown from console.warn and see if we can repair warnings we throw,
You can just remove some of them if they are irreverent to track.
Since the console is more clean now I will look into some of the deprecation warnings we get.

Yeah kill the console.times as well.


Fix send race

This solves a similar problem as #1758: in some cases, currently emitting a metric or yielding an output can result in an EAGAIN error, and we believe Done events are sometimes dropped. In async land, we shouldn't need a lock; multiple writers should be able to write to a StreamWriter safely. We also keep a sync Lock when the predictor is not async.
However, I'm still not sure if StreamRedirector is safe. After some research, StreamWriter.write calls self._transport.write and when StreamWriter is wrapping a unix socket and using the default selector, the _transport is a _SelectorSocketTransport, which calls self._buffer.extend, and self._buffer is a bytearray. However, on 3.12, append is called instead of extend.
After more soul-searching, I think write should be basically thread-safe: the two critical calls, socket.send() and bytearray.append/extend should be represented as a single bytecode instruction and some native code which works on python objects and does not release the GIL. As far as I understand, python threads are switched "between bytecodes". Even though the individual calls are thread-safe, the overall write method is not quite thread safe: a relevant thread switch could occur between the if not self._buffer, _sock.send, and _buffer.extend lines. However, in that case the race condition would result data could being sent out of order or incorrectly delayed/sent early, but it I think it shouldn't be corrupted, and we don't really care about the ordering of log lines vs outputs.
I can see two solutions:

Ideally, we would probably add an alternate implementation of StreamWriter that uses the main event loop and wraps stderr/stdout in StreamReaders, start a separate task for each stream, and use await wrapped_stream.read() so that threads are not necessary. there's a tricky moment where we need to use the threaded StreamRedirector to capture logs while the predictor is being imported, since we don't know if we're going to be async or not.
Alternatively, we could try to use a queue or deque to communicate between threads, so instead of calling stream_write_hook StreamRedirector would do queue.put, the main event loop would do queue.get and not worry about thread safety for the pipe. The problem with this is that asyncio.Queue is not thread-safe and queue.Queue could block the event loop. You could use a busy wait or similar and get_nowait, but that has other downsides.

https://replicatehq.slack.com/archives/C0617RF4HHP/p1719896679090459?thread_ts=1719867269.654439&cid=C0617RF4HHP

Closing in favor of #1831


Update our release rc config so that a breaking change commit will only bump the minor version and not the major version

Previously, I made a breaking change commit because we removed the caching of the config file and we decided to go to 1.0.0.  However, we have now decided that since we are still before 1.0.0, then that is okay to have breaking changes at any release.  Therefore, we want to update our release rc config so that when it detects the breaking change commit syntax that will do a minor version bump.
We can use the 'dry run' option to test the workflow and verify that it is working correctly.
Also, update the README to inform about the breaking change coming in v0.32.0.
Here is a code snippet provided to assist in the work:
Iliya Savov:
Good Morning! Hope you had wonderful Holidays!
I'm circling back regarding the semantic-releases issue we discussed previously. I've investigated it and it seems that we can reclassify the release types when there's breaking changes detected without the need to patch the upstream repos.
We have to create a .releaserc file and set the setting in there
Here's an example I've tested
{
  "plugins": [
    [
      "@semantic-release/commit-analyzer",
      {
        "preset": "conventionalcommits",
        "releaseRules": [
          { "type": "docs", "scope": "README", "release": "patch" },
          { "type": "refactor", "release": "patch" },
          { "type": "style", "release": "patch" },
          { "breaking": "true", "release": "minor"}
        ],
        "parserOpts": {
          "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES"]
        }
      }
    ],
    "@semantic-release/release-notes-generator"
  ]
}

the key part here is { "breaking": "true", "release": "minor"}
which can then be tested  with semantic-release --branches develop --debug -r . after installing  semantic-release  and conventional-changelog-conventionalcommits

:tada: This issue has been resolved in version 0.32.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix styling for runways mapped as areas

Only the linear centerline should get the dashed stroke:

That particular runway in the screenshot needed an area=yes, but there were issues with how areas were being styled at low zoom and I fixed those + a few other things.


Nan::Callback returns early from javascript execution

We're trying to provide "crypto hooks" in our project by calling back into javascript for all methods that require encryption (in order to get around having to statically link openssl to our addon). When I make a Nan::Call on the stored crypto callback (a Nan::Callback), I'm getting a return value before the function in javascript completes execution. This would seem to imply the crypto code is actually async, but the docs seem to imply it should work synchronously. Here's an example of the javascript code:
(key, iv, input, output) => {
  const result = crypto
     .createCipheriv('aes-256-cbc', key, iv)
     .update(input)
     .final();

   result.copy(output);
   return result.length;
}

Is there any way to ensure we're waiting for the function to complete, or is this actually an async call that needs to be handled with a worker?

Turns out an error was being thrown, similar to #605


Suggestion: Player List

Hiii ^^
Are you planning to make a list of players?

There is already a player list in admin functions...

Yes already here... close issue pls

Yes but for all players, and with a more beautiful style

Once again, the cosmetic part is not the objective of this framework. Please stop flood this git, and let ImagicTheCat do the most importants parts of this framework. We don't care about cosmetic, we can do it easily.

Ok, u can talk with me gently pls im not a dog..

And anyone its just a suggestion not a obligation

Stop flood this git for nothing. Not less not more.

Pfff.

Wait the fivem forum release for that questions. Imagic says that many many times...

YES I KNOW BUT "ANYONE" IT JUST A "SUGGESTION", SUGGESTION DUDE A IDEA NOT A HELP

I thank people who help me by answering on typical issues, but please don't start a fight. If someone is flooding, I will take care of it.


Zombie is gonna break those cuffs!

fixes #30396
fixes #26060
About the PR

Zombies uncuff when they zombify. The alternative is letting them use the uncuff action again, but, I don't really see a compelling reason for that instead of just uncuffing them.

Technical details

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

fix: Zombies will no longer remain cuffed when they turn.

Isn't this already handled? https://github.com/space-wizards/space-station-14/pull/30321

Isn't this already handled? (just hasn't made it to the servers yet) #30321

uh, maybe! I didn't check publish, I just saw a new issue said it still didn't work. #30396

Yeah, I just tested on master, and it looks like it is working. I'm guessing it just wasn't published yet.

this is kinda an imperfect solution considering you shouldn't have to manually handle removing cuffs off of handless entities. since its already fixed i think this PR isn't really needed.


Support sharing definitions between repos with different languages/package managers

Background
#36 introduced support for sharing definitions between repositories, but it relies on leveraging an existing sharing mechanism between those repositories - package distribution (e.g. go get, npm, nuget, etc.).
There are also use cases where there are no existing packages shared between repositories, and yet they both relate to the same bounded context.  A typical example is a split between a front-end (e.g. in JavaScript/TypeScript) and a backend (e.g. in go, NodeJs, Ruby, .NET, JVM, etc.).
There is a case to be made that splitting such repos is an antipattern from the perspective of keeping all code associated with a bounded context in a more cohesive manner (e.g. a single repo), since functional changes are likely to affect all code that is a manifestation of that bounded context.  However, current CI/CD tooling is far more attuned to aligning repositories with deployable components rather than logical components, so for the time being, this is definitely a scenario that Contextive needs to handle.
Options:
Considered approaches for sharing with pros & cons:
Raw URL from hosted source control
Common hosted source control platforms (e.g. github, bitbucket, gitlab) offer a raw URL to retrieve a file from a repo.

Pros:

Simple mechanism to retrieve the file

Cons:

Have to poll the URL to retrieve updates
Have to authenticate the URL, which likely means storing auth credentials (added security burden) or prompting for credentials (user friction)
Only works if the repo has such a RAW url

Clone repo into tmp folder
Could clone a nominated repo into it's own tmp folder and identify the file in that repo

Pros:

Able to retrieve the file, even if no RAW url available

Cons:

Have to poll the repo (fetch/update) to retrieve updates
Have to authenticate to clone.  Might work seamlessly if the user has stored credentials (e.g. ssh key), but would be painful if not
Have to clone the whole repo - no way to get a single file (e.g. github explicitly blocks the git archive mechanism)

Self-published/hosted
Much like how many teams publish a swagger/json file alongside their API, a contextive definitions file could be included in a build process as an artifact, and thus made available at a URL in a preproduction (or even production) environment

Pros:

Potential to access the file at a simple URL with no authentication

Cons:

More effort for teams to publish the definitions file
Teams may not like the file being publicly available (may have auth, vpn, or source IP restrictions)

Thanks for this, they are interesting options and I agree with the pros and cons assessments.
I really like the idea of self published or hosted like a swagger file as it could be a way to share the content with stake holders / domain experts who don't have access to the source code repository. Although I definitely agree with both of those cons, especially that there may be sensible objections to publicly exposing the details of your core domains.
Raw URL or cloning the repo both seem like sensible options and seem fairly equivalent usability. I would prefer whichever has the least friction. My current workplace at least all use SSH keys for Bitbucket connectivity as this is required for private Go packages so that shouldn't be painful for us.

I am doing this self published for my integration events. The page describes both the external events the service subscribes to as well as the outgoing events.

Thanks for the info @bluecitylights - can you share a few more details on how/where you are publishing the files? And are you pulling them down into other repositories so contextive can work in those repositories?
Would you like contextive to offer more native/built in support for that pattern, or is it leveraging other things you're doing outside contextive (in which case it might make sense for contextive to be ignorant/agnostic as to how you're doing it...)


Can't seem to install the add-on

(This is the first time I'm reporting an issue and a 2 days user to HA so please bear with me)
Can't seem to be able to configure the integration and login properly.
To Reproduce
Steps to reproduce the behavior:

I've updated to the latest version
I've added debug: True after my credentials in configuration.yaml
I've restarted HASS.IO twice
I go to 'notifications' and start UI configuration of the add-on
I get a pop-up with Captcha challenge
I re-enter my Amazon's password and enter the captcha and click submit
I get to the Alexa Media Player - Verification Method enter 'sms' and submit
I get a weird empty pop up and then I'm stuck

Expected behavior
I was expected for the login to work
Screenshots

System details

Home-assistant 0.108.2
Hassio Yes
alexa_media  2.5.13
alexapy - sorry, I couldn't understand that, in HACS I also see it as 2.5.13

Logs
Please provide logs. We'll be most likely asking for them anyway.
Additional context
I've managed to get to the configuration screen when I entered '0' or '1' in the verification screen but just got the captcha again and couldn't complete the process.
I didn't manage to get any OPT messages ((email nor SMS).
Thanks!! :)

See work arounds in #568.  You may have to delete  Ami's 5th Android Device to get past this at this point or setup 2FA on your app.

Oh and welcome to HA and the component.

Thank you so much Alan for the quick response and the warm welcome!! :)
What do you mean by  'delete Ami's 5th Android Device'?
Delete it from where? How can I do it?
I don't even understand what device is it referring?
could it be the Alexa app installed on my android smartphone?
Since I live in Israel I think I had to do a workaround in order to install Alex (maybe I downloaded an APK file. can't really remember)

It's described in the thread I linked. You can delete it from the website but again check the thread.

Thank you so much Alan.
I've managed to do it with the 2FA.
What will happen if I now disable 2FA from amazon website. Will the add-on continue to work?

Yes. It may ask you again to relog in after a couple of months.

Thanks Alan.
Since I had one echo dot which I gave as a gift registered on me I had to remove the add-on and re-install it. Now I have relevant only devices (I think).
The thing is that they look like this:

Is it OK? did I've managed to break it?

No it's fine. Those will become available if relevant information is available.