When setting config and options causes infinite render loop

When I set config and options, the component is causing an infinite render loop.

Could you please show your code? Thanks!

Of course,
 const { data, update } = useAxiosRequest({     url: 'http://localhost:4000',     params: {       family: '342',     },   },   {     pollInterval: 0,   });
I am setting the pollInterval option because for some reason it is causing the infinite loop, I think the issue is related to that setting.

You create a new object for every render and useAxiosRequest send a new request since it got a new object (config). You have two options:

carry out your config in constant out of a component

const CONFIG = {
    url: 'http://localhost:4000',
    params: {
      family: '342',
    },
  };
const YourComponent = () => {
  const { data, update } = useAxiosRequest(CONFIG);
}

memoize config if it depends on the props

const MyComponent = ({ family }) => {
  const config = React.useMemo(() => ({
      url: 'http://localhost:4000',
      params: {
        family,
      },
    }), [family]);
  const { data, update } = useAxiosRequest(config);
};

It works! Thanks a lot :)


Allow relay.nostr.band to be unsubscribed

It would be nice if relay.nostr.band was hard-coded in "WIP. Add search with NIP-50 #167", forcing the user to connect to a relay they do not want.
Please stop forcing connections to unnecessary relays as some users do not use the search function!
(It is preferable to add it by default but allow the user to deactivate it.)

I need to see how to do this correctly because as we move more into NIP-65 and the Gossip model, the app is supposed to connect with many more relays than what the user declares as being used. To get notifications, for instance, the idea is to connect to as many relays as possible and download information about the author.

OK 👍

Is the gossip model being developed now? Where can we discuss more details on gossip strategies?


Visible underline on tertiary button in inline mode

Bug fix
This PR fixes a bug where the underline of tertiary button is not visible in inline mode.
This fix makes all tertiary buttons align with the sketch file design of tertiary button:
After fix:

Fixes #446.

Coverage remained the same at 80.592% when pulling d60ec72194bcf0792c5befa50c68356f0f82e7b1 on tertiary-button-underline into 784fa13e3c69145efded6ef494480802267f1acd on develop.


:bug: Fix Scrolling is 'tripping' when at top or bottom when no-wrap …

…and itemCount is >= 5

This would be a critical fix for us. Is there a chance that it can be merged anytime soon?

@SmallStoneDD @balazsbanyai Could you provide any videos?

And this issue only can be reproduced by using this PR. 😅

The issue can be reproduced with the latest released version of this library, with disabled wrapping and more than 5 i
tems
The issue is not reproducible using the code built from this PR.
This is how it looks: https://youtu.be/wo2hfMbrY5I

Could you reproduce the issue on sample app? It would be better if you can paste the configs of number picker, such as java code or layout xml.

Could you reproduce the issue on sample app? It would be better if you can paste the configs of number picker, such as java code or layout xml.

Sure thing, this configuration reproduces the issue, here you go:
<com.shawnlin.numberpicker.NumberPicker
        android:id="@+id/horizontal_number_picker"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:layout_marginTop="60dp"
        app:np_orientation="horizontal"
        app:np_wrapSelectorWheel="false"
        app:np_min="16"
        app:np_max="32"
        app:np_maxFlingVelocityCoefficient="3"
        />

Video:
https://youtu.be/14q0ZtirocY

This PR only fixed the tripping in horizontal mode, but unfortunately it made the tripping in vertical mode. And this issue has been fixed at v2.4.11. @SmallStoneDD @balazsbanyai


WIP Preparation for Reader trait

I'm not sure that this PR is ready to merge yet, but I'd like feedback on the direction it is taking. My goal is to define a Reader trait, implement that trait for EndianBuf, and gradually replace all usage of EndianBuf with the Reader trait instead.
This PR takes two steps:

use EndianBuf everywhere, instead of &[u8]. We were already using it in most places, but this extends it to things like parse_u8. There are likely still some places I have missed.
reduce the amount of cloning of EndianBuf. This is achieved by changing parsing functions to take &mut EndianBuf, instead of returning a copy and leaving the input unmodified. The motivation is that while cloning EndianBuf is cheap, this may not be true for other implementations of Reader.

One reason I'm asking for feedback is that I suspect @fitzgen likes the current immutable input for parsing, so this may be a controversial change.

Coverage increased (+0.3%) to 93.373% when pulling 07a6028a0ee99c419f8d882c453336c962f222c7 on philipc:endianbuf into f63bac10c5d0857a96aa2c53c28c1c8d76496fa0 on gimli-rs:master.

Coverage increased (+0.3%) to 93.372% when pulling 8fd8f924fed49ec5e8160b0958a6f0ea5ad44515 on philipc:endianbuf into f63bac10c5d0857a96aa2c53c28c1c8d76496fa0 on gimli-rs:master.

Coverage increased (+0.4%) to 93.394% when pulling c00d91f8403169b182c85f5e1d12900fb0ff0b19 on philipc:endianbuf into f63bac10c5d0857a96aa2c53c28c1c8d76496fa0 on gimli-rs:master.

Sorry I've been putting this off -- I'll try to take a look tomorrow.

Coverage increased (+0.4%) to 93.399% when pulling d8197fbb54c05210af2a8aa423461683d745c6de on philipc:endianbuf into f63bac10c5d0857a96aa2c53c28c1c8d76496fa0 on gimli-rs:master.

I'd like to get your opinion on the immutable input change at least, specifically changing from:
let (rest, val) = parse_xxx(rest)?;
to
let val = parse_xxx(rest)?;
I understand that the former style is great for a backtracking parser, but I'm not aware of any benefit it provides for DWARF parsing, and I think it makes the code more complicated. So I'm not sure if the code is written like this simply as a leftover from using nom, or if you prefer it this way.

In general, I strongly prefer immutability and referential transparency when all else is equal. However, we're moving towards a world where all else is not equal, we will have rampant mutation of the reader while parsing, and trying to paper over that would not be fun.
I also tried thinking of a way to split handles/cursors into the image being read out of the reader itself, and that the reader can be indexed with those handles/cursors or something like that. The idea being that this would allow us to take and return these handles/cursors in a referentially transparent way like we do with slices now. In the end, I think it would be a lot of complexity that wouldn't end up paying for itself, and the mutation is still happening under the covers so if our abstractions leak at all, then it will be blech.
In conclusion, I think the changes in this PR make sense, and this is the road we want to continue down.

Having thought about it more, I'm not sure that the clone cost is going to be important, so don't weight that too heavily in making your decision. Even for the buffered implementation of Reader, the struct it needs to clone should still be small, eg something like { image: &'input Image, offset: usize, len: usize }. I can imagine some consumers wanting to use Rc or Arc.

Yes, my intuition is that these clones shouldn't have any observable overhead compared to parsing each sections contents, but measurement is king.

Thanks again @philipc !


Extension incompatible with Lens 5.4.x

When adding the pre-build release (0.0.1) to the Lens instance (version 5.4.3), it states "Incompatible version".
Is there a dependency that needs to be bumped to get the extension to work with newer versions of Lens?

I've also seen this in lens 6, just wondered if you guys are still maintaining this or if there is something else your recommend?

Hey, thanks for your interest! We're looking actively for maintainers, if you have any chance on fixing this would be really appreciated! 🙏🏻

I found this repo that support v6
https://github.com/the91end/capsule-lens-extension


Oscillation in corridors

Hello,
When following a straight global path in a narrow corridor (wrt the width of the robot), i have oscillations on the trajectory that i can't explain. These oscillations are not present when navigation in wider spaces and i don't think they are due to localization noise.
Any tips or ideas to narrow the search?

I was able to greatly reduce these oscillations by decreasing the inflation_dist parameter (originally 0.5, changed for 0.1). Do you think there is a way to keep the desired behavior of rounding obstacle with a safe margin (the reason for the 0.5 value), without generating trajectory oscillations in a narrow space?
For reference, here are my parameters:
recovery_behavior_enabled: False

TebLocalPlannerROS:

 odom_topic: /encoder/odom
 map_frame: /map

 # Trajectory

 teb_autosize: True
 dt_ref: 0.3
 dt_hysteresis: 0.1
 global_plan_overwrite_orientation: True
 max_global_plan_lookahead_dist: 3.0
 feasibility_check_no_poses: 5

 # Robot

 max_vel_x: 0.42
 max_vel_x_backwards: 0.11
 max_vel_y: 0.0
 max_vel_theta: 0.6
 acc_lim_x: 0.08
 acc_lim_theta: 0.5
 min_turning_radius: 0.0
 footprint_model: # types: "point", "circular", "two_circles", "line", "polygon"
   type: "polygon"
   radius: 0.35 # for type "circular"
   line_start: [-0.3, 0.0] # for type "line"
   line_end: [0.3, 0.0] # for type "line"
   front_offset: 0.2 # for type "two_circles"
   front_radius: 0.2 # for type "two_circles"
   rear_offset: 0.2 # for type "two_circles"
   rear_radius: 0.2 # for type "two_circles"
   vertices: [[-0.27, 0.315], [0.27, 0.315], [0.27, -0.315], [-0.27, -0.315]] # for type "polygon"

 # GoalTolerance

 xy_goal_tolerance: 0.3
 yaw_goal_tolerance: 3.2
 free_goal_vel: False

 # Obstacles

 inflation_dist: 0.1
 min_obstacle_dist: 0.1
 include_costmap_obstacles: True
 costmap_obstacles_behind_robot_dist: 1.0
 obstacle_poses_affected: 30
 costmap_converter_plugin: ""
 costmap_converter_spin_thread: True
 costmap_converter_rate: 5

 # Optimization

 no_inner_iterations: 2
 no_outer_iterations: 2
 optimization_activate: True
 optimization_verbose: False
 penalty_epsilon: 0.05
 weight_max_vel_x: 2
 weight_max_vel_theta: 1
 weight_acc_lim_x: 1
 weight_acc_lim_theta: 1
 weight_kinematics_nh: 1000
 weight_kinematics_forward_drive: 100
 weight_kinematics_turning_radius: 1
 weight_optimaltime: 1
 weight_obstacle: 50
 weight_dynamic_obstacle: 10 # not in use yet
 alternative_time_cost: False # not in use yet

 # Homotopy Class Planner

 enable_homotopy_class_planning: False
 enable_multithreading: True
 simple_exploration: False
 max_number_classes: 1
 selection_cost_hysteresis: 1.0
 selection_obst_cost_scale: 1.0
 selection_alternative_time_cost: False

 roadmap_graph_no_samples: 15
 roadmap_graph_area_width: 5
 h_signature_prescaler: 0.5
 h_signature_threshold: 0.1
 obstacle_keypoint_offset: 0.1
 obstacle_heading_threshold: 0.45
 visualize_hc_graph: False

Lower the angular acceleration rate , max_vel_theta: 0.6 (check with 0.01 to 0.3 ).
increase the max_global_plan_lookahead_dist: 3.0 (check with 6 to 8 range)

The robot is not overshooting in steering when no obstacles is in range. I don't think it has to do with the max_vel_theta value, but I will conduct more tests.

How is it going?


build: fix pyproject.toml

What does this PR do?

Replaces ' with " for consistency in pyproject.toml
Removes setuptools_scm from the [build-backend] section in pyproject.toml
Removes README.md from the dynamic section
Removes setup.py

Fixes #123
Before submitting

[x] Did you read the contributor guideline,
Pull Request section?
[x] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you run all tests locally and make sure they pass. They all fail since I am on macOS and PyTorch complains about not being compiled with CUDA 😢
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

Ciao @dacorvo - sorry if I went on and opened this PR but I wanted to try this out locally.
With this setup, I can build quanto locally. I cannot reproduce the metadata bug you mention in the issue I opened. Can you help me create a setup where I can test that? Thanks!
(Also: would you like swapping black for ruff's native formatter? 🔥)

With this setup, I can build quanto locally. I cannot reproduce the metadata bug you mention in the issue I opened. Can you help me create a setup where I can test that? Thanks!

I will try it also, but I might request you to add some specific tests to verify that the extension is correctly detected and built on all platforms (typically, before adding setuptools_scm the non-python files were not be included in the package).

(Also: would you like swapping black for ruff's native formatter? 🔥)

https://github.com/huggingface/quanto/issues/186

I will try it also, but I might request you to add some specific tests to verify that the extension is correctly detected and built on all platforms

Sure! Would you have some suggestions on how to start and run the tests? e.g. should I use dockerfiles or rely on CI/CD?

(typically, before adding setuptools_scm the non-python files were not be included in the package).

I think this should cover us. Are you referring to the files under quanto/ext?


Auto Refresh refreshes when performing actions

Describe the solution you'd like
When AutoRefresh is on and I select Incidents it sometimes AutoRefreshes and I lose the incidents that I was working with, so If I decided against applying the actions, I will have to reselect the Incident that I was working with.
Describe alternatives you've considered
Incidents should not be auto-refreshed while performing actions on specific data
To Test
Go to Incidents
Select a few Incidents
Click Actions
Wait for the Incidents to AutoRefresh
Click Cancel and notice that no Incidents are selected

@Lodewyk-Git - thanks for sharing your experience.  Let me get this info to one of the PMs to look at.

@Ronmarsiano - Cleaning up stale issues and wondering if the PM team looked into this.


"Basic" ST-Link/v2 support

Implements ST-Link/v2, an ubiquitous and cheap (ca. $10 on Aliexpress) programmer, support for posix platforms.

[x] "basic" .stlinkv2 targets: flash, reset, erase
[x] debugging with gdb
[x] "unitargets": Have stdtargets (like flash) default to stlink if PROGRAMMER = stlinkv2 is set
[x] Add a README section

Also see #19.

@brghena I think I'm more or less done - could you review?


ERROR: Unknown image format/type -> Test run does not seem to work

Describe the bug
I have cloned the repo and tried to run the test case.
I fails with message about unknown image format.
Additional context
pedro@host$ nextflow -v
nextflow version <IP_ADDRESS>60

pedro@host$ singularity --version
2.4.2-dist

pedro@host$ nextflow run main.nf -profile standard,test
N E X T F L O W  ~  version 21.04.3
Launching `main.nf` [golden_elion] - revision: ab68701493
executor >  local (5)
executor >  local (5)
[f0/ff3ece] process > call_snvs1 (1)  [100%] 1 of 1, failed: 1 ✘
[10/b2f904] process > call_snvs2 (1)  [200%] 2 of 1, failed: 2 ✘
[44/9c19f1] process > call_sv_del (1) [100%] 1 of 1, failed: 1 ✘
[ca/e10e4d] process > call_sv_dup (1) [100%] 1 of 1, failed: 1 ✘
[2d/8190ba] process > get_depth (1)   [100%] 1 of 1, failed: 1 ✘
[-        ] process > format_snvs     -
[-        ] process > get_core_var    -
[-        ] process > analyse_1       -
[-        ] process > analyse_2       -
[-        ] process > analyse_3       -
[-        ] process > call_stars      -
Error executing process > 'call_sv_del (1)'

Caused by:
  Process `call_sv_del (1)` terminated with an error exit status (255)

Command executed:

  graphtyper genotype_sv hg38/chr22_hg38.fasta --sam=SIM001.bam --region=chr22:42126000-42137500 --output=SIM001_sv_del cyp_hg38/sv_test.vcf.gz

Command exit status:
  255

Command output:
  (empty)

Command error:
  ERROR  : Unknown image format/type: /home/pedro/projects/stellar-pgx/containers/stellarpgx-dev.sif
  ABORT  : Retval = 255

Work dir:
  /home/pedro/projects/stellar-pgx/work/44/9c19f177e5acfa3fcd5d65fd193b5e

Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`

@pmginacio Thanks for your interest in using StellarPGx. I see you're using Singularity v2.4.2-dist which doesn't seem to support the .sif image partitions.
We ran our StellarPGx development tests using Singularity v 3.6.3-1.osg34.el7. Any chance you could update to v 3.1 or higher?

@twesigomwedavid thank you for your reply and for sharing StellarPGx.
I installed singulatiry from the apt repository and 2.4.2-dist is the version I got.
Since it met the required version stated in the description (>2.3.x), I assumed it should work.
In the mean time, I switched to using docker and it seems to work fine.
Perhaps it would make sense to up the required version for singularity in the README file.


Big refactor: Drop custom VTK, drop docs, plus more

This is an opinionated refactor of the flake that I reckon should make it easier to maintain, open to discussions 🙂. Builds and have been using it for a few weeks, but would like others to test that they are also able to build and use it. Still some more small changes I would like to do and clean up, but I think this is still a good improvement.

We no longer need to use a custom build of VTK as it seems like CQ has
moved to using upstream VTK.
Dropped building of docs as this adds a lot of cruft to the flake
for only a minor gain. The public CQ docs are good enough.
Dropped extra flake targets for building python environments,
etc. Again extra cruft for only minor gain. This flake should provide
the basics: building cadquery and cq-editor along with
deps. Downstream users can then simply add these to their own
environments.
Move fetching of LLVM src into Clang derivation, this way we don't
risk them being out of sync.
Added cq-warehouse package.

Looks nice what you have done. I did many of those things myself (but a lot more ugly), in a local checkout that I wanted to create a PR for as well.
I don't really disagree with anything you have done, and I like that it being kept as KISS as possible. Ie. no docs, no env, no lsp, etc. etc.
It would be really cool, if we could upstream this at some point, to not have to rely on a external repo, and I think others would enjoy that as well.

Build it and tested it , worked perfectly.  Did not test cq-warehouse however. But cq-editor works perfectly fine.

works here as well

We no longer need to use a custom build of VTK as it seems like CQ has moved to using upstream VTK.

CQ should be using conda-forge's VTK, which is here: https://github.com/conda-forge/vtk-feedstock/blob/main/recipe/build-base.sh
I don't know if any of the differences between conda-forge's VTK and nixpkgs' VTK are significant right now, but I do recall fixing several bugs in the past by adding in cmake flags and patches from the conda-forge feedstock.

@vinszent did you mean to abandon this?

Hopefully that's not the case.

Ah no, I deleted my repository so that @marcus7070 can transfer ownership of this one to me. Didn't realise that it would delete the PR, but I guess that makes sense.


Review of Murphy tutorial

For consideration and discussion re the Murphy Diagrams tutorial.

@tennlee I have updated this pull request based on the suggestions from @DerynGriffiths

@nicholasloveday , @tennlee I had another look at this and added one missing space. I think it is good to go.
Same trouble as MAE with the display of the help notes - do we have a solution?
I like the restructure which puts some of the more advanced background material at the end of the notebook.

@nicholasloveday , @tennlee I had another look at this and added one missing space. I think it is good to go.
Same trouble as MAE with the display of the help notes - do we have a solution? I like the restructure which puts some of the more advanced background material at the end of the notebook.

@DerynGriffiths - I have saved the notebook with all cells executed apart from the "help" ones. https://github.com/nci/scores/blob/afe7ae1f9e3d6ad5320995b98a1a4703f535207e/tutorials/Murphy_Diagrams.ipynb


drivers: entropy: adopted TRNG driver for B92

Added entropy driver for B92, unified True Random Number Generator driver for B91 and B92 boards to be common B9x.

@interfer Please fix compliance checks


Automate rolling of SNAPSHOT version in pom

Follow-up to discussion in: https://github.com/datafaker-net/datafaker/issues/1412

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.15%. Comparing base (cd7e58d) to head (df7a4f4).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1438      +/-   ##
============================================
- Coverage     92.18%   92.15%   -0.04%
+ Complexity     3163     3161       -2
============================================
  Files           320      320
  Lines          6182     6182
  Branches        593      593
============================================
- Hits           5699     5697       -2
  Misses          340      340
- Partials        143      145       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@bodiam good to go for now?


Inputs: Add typography customization

Description

Adds Typo.input so you can control the default input typography like you can do with Typo.button, then uses that as the default for the new Typo property in MudBaseInput.
Uses the lh unit which raises browser support level but significantly simplifies the line height. To ease the maintenance burden and set expectations, I added a note to the README about staying up to date so that we aren't tied down to ancient versions. Note: Blazor only supports the latest browser versions.
Resolves #8337
I think the ideal solution might be to scale the entire input up with relative units, but this implementation fits in with our current approach.
How Has This Been Tested?

Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Text Field example:

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[X] I've added relevant tests.

I need to know if this is on the right track and which controls I should apply this to. Check Box, Switch, etc?

@jperson2000 Would love to know what you think

Will the default typography of textfields stay the same as before? In other words, is this visually breaking?

Will the default typography of textfields stay the same as before? In other words, is this visually breaking?

@henon Everything stays the same, the styles are just moved to --mud-typography-input so they can be customized through the theme provider or the new Typo property.

Thanks!

Just wanted to note that this change may have inadvertently changed the font size for MudFields.
It appears that the font size for a MudField control value (when a label is present) has decreased from 16px to 14px. Cache cleared. This occurs on MudFields with labels. See the upper left MudField as an example in the v7 docs (in v6, it was 16px, ).
Simple app.css fix seems to work, but not sure if there are any side effects...
.mud-input { 	font-size: 1rem; }
This was likely caused by "font-size: 1rem" being removed from the .mud-input css class in v7.
I am assuming this was removed as it is supposed to inherit the default font size. I'm guessing something is throwing this off for MudFields, as they are styled as inputs, but are not.

It may be worth noting or keeping in mind for next time that inserting a new enum value in the middle of an already defined list is a bit of a breaking change.
https://github.com/MudBlazor/MudBlazor/commit/72c4cde700306c8b1e411e6d7bf3a5554d35548a#diff-1089e571a136c66006bb1a01911171fea26aba0e559b2e281de79b0b99e77d09R30
We have some internally built razor Nuget packages that reference MudBlazor, use the MudText component, and set the Typo to Typo.caption.
Any project that pulls in our razor Nuget that was built against MudBlazor 7.2, but itself uses a higher version with this change (like 7.3) now displays the text with Typo.button since the enum values got shifted resulting in everything being sized differently and upper-cased.
Subtle breaking change I know, but can we add enum values for the names in the Typo.cs file to make it more obvious to the next  person that they should add something to the end instead, or at least use an unused number if they want to group names?

@sluebbert Very very good point that I shouldn't have missed. Would it help if we moved it to the end now? Are you interested in submitting a PR?

No, it is fine at this point.
I think that last statement summarizes my suggestion at this point. Having the enums assigned to numbers may help the next person who changes it know not to insert, or may remind them that their insert may be a breaking visual change.
I'm not sure what preferences the maintainers have for resolving that suggestion as it is probably applicable to all enums.


After

Issue adding modifier and operation after adjusting vertical resolution.

Would be nice to include a prebuilt .exe in the res.

Hi Hantoo,
There are prebuilt exes at https://github.com/nickmcdonald/ies-generator/releases, and I recommend you use those instead.
There are some issues with the source code at the moment. I was half way through adding more features and i got distracted, and haven't got around to finishing it yet.
thank for your interest


files.{fd,find}_opts is undocumented

These are very useful options (e.g. https://github.com/ibhagwan/fzf-lua/issues/178#issuecomment-939505769) but they are not mentioned in any documentation.
I'll file a PR adding them if I get time.

rg_opts does appear in the README customization under grep.rg_opts, I can add fd_opts in the same manner.
If you wish to PR with a more detailed explanation feel free to do so for the fzf-lua Wiki.

https://github.com/ibhagwan/fzf-lua/commit/cd0cb50717343745b7c5e89c448b372a29521d26
Added fd_opts to README in the above commit.


Deserialize from str

Serde has this functionality:
use std::collections::HashSet;

fn main() {
    let var: HashSet<String> = serde_json::from_str("[\"hello\"]").unwrap();
    dbg!(&var);
}

Do you have something similar in rkyv? I couldn't find it

As far as I know, serialized rkyv data may not be valid UTF8, so it can't be stored as a String / str. So I'm not sure how this suggested from_str function is supposed to work, maybe you could elaborate?

maybe it could work similar to Serde except replacing owned items (e.g. String) with borrowed items (e.g. &str) as you do elsewhere in rkyv. The purpose of this is to be able to completely replace Serde with rkyv rather than having to keep them side-by-side. I'm imagining that rkyv is to Serde what Rust is to C++.

rkyv has to_bytes and from_bytes for this kind of functionality. For the reasons @w-flo mentioned, rkyv can't support to_str and from_str. You can read more about why rkyv's serialized format is different in the book.
rkyv will not aim to support a human-readable text format.


Update Azure Key Vault Configuration Provider in ASP.NET Core page to recommend Azure.Extensions.AspNetCore.Configuration.Secrets rather than Microsoft.Extensions.Configuration.AzureKeyVault

Back story
I was struggling with very slow startup times when using the Microsoft.Extensions.Configuration.AzureKeyVault package, I did a bit of digging and noticed that there was an issue with Microsoft.Azure.Services.AppAuthentication having slow token fetching times. This was fixed in version 1.2.0, but Microsoft.Extensions.Configuration.AzureKeyVault is referencing 1.0.3.
If I add a reference the latest version of Microsoft.Azure.Services.AppAuthentication (1.5.0), everything speeds up nicely.
I was going to make an update to Microsoft.Extensions.Configuration.AzureKeyVault, but it looks like that has been deprecated and replaced with Azure.Extensions.Configuration.Secrets, which has since been replaced with Azure.Extensions.AspNetCore.Configuration.Secrets.
Suggestion
This page currently recommends using the Microsoft.Extensions.Configuration.AzureKeyVault, should this be updated to recommend Azure.Extensions.AspNetCore.Configuration.Secrets?
Or would it be better to add a new page explaining how to to use the new package (as I'm not sure there is 100% feature parity between the two, for example not sure how to authenticate with application id and cerificate)?
Could potentially link to the Azure Key Vault Secrets configuration provider for Microsoft.Extensions.Configuration - Version 1.0.0 page, but it's pretty basic at this point.

Happy to start writing the documentation myself, but this would be my first contribution so want to make sure that there isn't a better process for more significant changes like this 😄.

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

ID: 2cc0b77a-df21-7007-5cec-4399d98c6dc6
Version Independent ID: efe5ae5e-ff64-f1c7-6920-4512fc8f36d1
Content: Azure Key Vault Configuration Provider in ASP.NET Core
Content Source: aspnetcore/security/key-vault-configuration.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@mkArtakMSFT  can you assign someone to review this proposal?


RFC: Refactor proposal! Adding a controllers to napari

The current flow of data in napari is through the use of events emitted. A user can modify a layer through the gui or directly in a jupyter notebook or ipython terminal.
The following  diagram charts the flow of calls when a user modifies the interpolation attribute of an image in the second scenario.

This system works alright but when a user modifies the interpolation attribute through the gui dropdown menu the flow is a bit more complicated, see below:

The current architecture:

makes it hard to debug, and track everything that happens when changes are made
causes repeat calls of methods
forces the qt, vispy connection through qt_viewer

This proposal adds a controllers to the codebase that are the central place to process data updates. A layer's controller has access to all three components (data, qt, and vispy). When changes are made the controller is the only component that receives events, it then updates the layer, qt_controls, and vispy_layer. See modified architecture below:

This simplifies the codebase by:

Only having one method to track down that shows everything that happens on a user change of any kind
Neither the vispy layer or qt  controls will need to connect to events, they will only be responsible for updating themselves.
When something goes wrong the error message will be much easier to parse
There won't be any need to ever suppress events, or risk of causing an endless update loop
eventually qt_viewer will not need to keep track of each layer's vispy mapping and can just call the controllers instead.

The code in this PR is just a small example I made for feedback. I added everything needed for napari to process image interpolation changes from either the layer level or gui level through the new image_controller. The whole refactor would be significant but I think it would be really helpful longterm for readability and debugging. Also from a plugin standpoint we could add hooks to the controller methods and not have to worry about updating anything else.
Looking for all the feedback, likes, dislikes, and concerns!!
NOTE: The tests and build will definitely be broken since this is just a partial refactor meant as an example

After the refactor, if we wanted to swap out vispy / Qt or have multiple rendering options / backends would the we need new controllers for each one? And would we have more duplicate code after the refactor relative to if we tried to do this now.

No, we wouldn't need new controllers. We'd just need to edit the existing ones to modify the new viewers or backends. I actually think this get's easier after this refactor because the changes you'd have to make are all in one place rather then setting up event connections in each new view.

If we wanted to use the model files without any Qt / vispy imports would we still need to import the controller or do something special inside it - i.e. what does a "headless-mode" look like? (I left a more detailed question about that in the model code)

The models shouldn't import the controllers. The controllers import the model. So everything there should work as it does now.

Where do things like mouse functions / keybindings live - say the code in the labels layer around using the paintbrush, including both painting related functions in the model file and the mouse callbacks?

I think this should also live in the controller. So say a mouse event will get emitted from vispy_image.py, the image_controller will be listening to that event and process accordingly.

For the viewer, where does code like add_image and add_labels live and how does it get called? Here I think it is really important that all that code can be run and interacted with without any vispy or Qt imports.

Nothing should get changes in add_image or add_labels. In my mind these are the methods that instatiate the data layer, so they get called, and then the separate methods get called for creating the vispy and qt components (but all three are separate), and then the controller gets created with access to all three. (See changes to qt_viewer)

I'd also love @tlambert03, @jni and particularly @royerloic, who spent a lot of time thinking about our model and view refactor, to take their time to understand the proposed refactor in detail, both for this chunk of code and also how it will propagate to the rest of the code base, and then weigh in.

Yes please give me all the feedback!

How does error handling work in this universe?  One could presume that settings driven by UI may need to be validated against other state, and need to be cancelled if the request is not valid.
The way attributes are set should be consistent between qt_image_layer.py and image.py.  It appears that setting the attribute in image.py updates the attribute and broadcasts the event and then receives yet another set attribute request from the controller.  qt_image_layer.py broadcasts the event, and then receives a set attribute from the controller.  I am fairly sure that the path for qt_image_layer.py is the better one because error handling could plausibly be done by the controller and cancelled.
I like @kne42's comment about the public python object being exposed as another "view".
There is a lot of boiler plate here.  Ideally, we should be codegen'ing a lot of it.

@all we should definitely move this discussion to #1020 as it is imho a superior solution...

Gonna close this out now in favor of the new direction in #1020!


feat(Tabs): Added overflowButton property

Changes

Added class iui-overflow to add styling for overflow tabs

overflow: auto prevents tabs from overflowing the tabs wrapper & allows the function useOverflow to work correctly

Could be more specific - overflow: none?

white-space: nowrap prevents the text in tabs from wrapping (this looks better than allowing it to wrap when using the overflow button)

Added property overflowButton that enables tabs to be truncated and an overflow button to be shown

expects a function that takes the number of items that are visible and returns the 'ReactNode' to render

onTabClick was made into a callback because it's used as a parameter for the memo displayTabs
Added function displayTabs to only show visible tabs when the overflow button is passed in; without an overflow button tabs are displayed as normal

Testing

Added visual test for storybook
** Need to add regular tests
Manually tested:

Made sure that clicking on tabs switches tabs and opens the corresponding content
Made sure that clicking the button opens the dropdown menu
Made sure that clicking an option in the dropdown menu opens the corresponding content and shows that no tabs are selected/open
Made sure that resizing works correctly, both visually and in the dropdown menu content

Docs

Added example to website
Added story to storybook
Added changeset

closes #921

What happens if it's used with vertical tabs?

In Storybook, when I select a tab from the overflow dropdown menu it should have a checkmark showing which menu item is active.

Another thought I'm just thinking outloud, unsure if this is a good idea or not.  From a UX perspective, if I select a tab from the overflow dropdown, I have no visual indicator what tab is active without opening the dropdown menu again.  What if an active tab from the overflow is displayed as the last visible tab?  Mockup below:

Seconding @FlyersPh9 on visibility of the currently selected tab, which would give users' visual feedback of what tab they are on.
Also it looks like for smaller screens like on phone, the entire tab seems to be minimized more than it should, at least compared to the default tab:

I'm just wondering if we want the tab behavior for smaller screens to be consistent across different tab implementations, or if the difference is expected behavior?

Also it looks like for smaller screens like on phone, the entire tab seems to be minimized more than it should, at least compared to the default tab:

It looks like this because I applied maxWidth: 25% to the surrounding div so that the example would be truncated. I didn't just set a width so that users can play with resizing the div.

@LostABike I updated the tabs (and breadcrumbs) overflow stories so that the area won't get too small or too big.

In Storybook, when I select a tab from the overflow dropdown menu it should have a checkmark showing which menu item is active.

Another thought I'm just thinking outloud, unsure if this is a good idea or not. From a UX perspective, if I select a tab from the overflow dropdown, I have no visual indicator what tab is active without opening the dropdown menu again. What if an active tab from the overflow is displayed as the last visible tab? Mockup below:

@FlyersPh9 I added logic to make the last tab the visible tab. I also updated the dropdown menu so that it only shows items that aren't currently visible:

I like how everything works and looks right now so I'm just manually stretch testing things. What is the expected behavior when the tab name is a little longer?

Maybe we want to truncate or phased out words to keep the same tab length? Like how Chrome has it here:

I like how everything works and looks right now so I'm just manually stretch testing things. What is the expected behavior when the tab name is a little longer?

@LostABike
Did you add extra text from Chrome inspect? The useOverflow function can't work correctly in that case because it doesn't have all the information about the tabs (how long they are) before determining how many tabs can be visible, because you're changing that information after it's decided how many tabs can be shown. If the text is longer from the story it would look like this:

But it doesn't work super great when the last tab is replaced with something smaller:

or larger:

Hm, I'll look into fixing that issue.

Maybe we want to truncate or phased out words to keep the same tab length? Like how Chrome has it here:

We don't have any considerations for this on the regular tabs. I feel like we should do it for all types of tabs if we do it. I'm not opposed to the idea, but I'm not sure about it because I feel like that's one of the pros of using an overflow - you can see the entire label even when there's not room for all of them. @FlyersPh9 ?

Maybe we want to truncate or phased out words to keep the same tab length? Like how Chrome has it here:

We don't have any considerations for this on the regular tabs. I feel like we should do it for all types of tabs if we do it. I'm not opposed to the idea, but I'm not sure about it because I feel like that's one of the pros of using an overflow - you can see the entire label even when there's not room for all of them. @FlyersPh9 ?

Let's release without that & see what kind of feedback we get.  Ideally tabs should never be that long & UX team should help guide devs to use shorter labels.

Nice! I think everything works and looks good now 😸

Overflow tabs don't work with keyboard well.

Need to test with disabled tabs.

Why did breadcrumbs images change?

@gretanausedaite Jon requested that the '...' be the large version for tabs, so I went back to breadcrumbs and made it match. It had the small '...' before.

I'm undoing the breadcrumbs changes and putting them in this other PR because I cannot get the tests to work, and it's probably better to be in its own PR anyway; scope and stuff.

😑
I don't know why this is failing. I undid the breadcrumbs changes. Whyyyyyyyyy

Two known issues:

On storybook, clicking on a tab breaks the page. This is specific to storybook and doesn't happen in the doc site example.
The horizontal autoscrolling does not work correctly if you refresh when on the horizontal overflow example in storybook. This occurs because there are passive events running after the initial render that cause the font to change. The calculated distance to scroll happens before the passive events (in a useEffect, which is supposed to happen only after the render) when the font is different. When the font changes, it's larger and pushes the tabs over. Refreshing on a different page and then switching to the horizontal tabs shows how it should act.

I also need to confirm that auto scrolling works when the active tab is to the left of the visible tabs.

Oh! I just thought of another issue. In the doc site, it's hard to scroll horizontal with vertical mouse wheel because the page also scrolls, so your mouse cursor leaves the box and you can no longer scroll.

Added fade to end and scrollbar on hover

Maybe an alternative. Uses clip-path: polygon(10px 0%, 100% 0%, 100% 100%, 10px 100%, 0% 50%); but would need to be adjusted to angle both sides, and probably add a border or a background.

https://stackoverflow.com/questions/72329195/react-component-getting-wrong-ref-dimensions-in-useeffect for my meh fix for intial placement of active tab.

Active tab never sits in fade:
https://user-images.githubusercontent.com/37936169/235053098-2d6e5a15-1221-4f27-9959-401c0b7937fa.mp4

@LostABike I'm just going to make it match what the vertical tabs do without overflow. It just disallows the tabs to be shrunk past the length of the tabs.

Need to update test images

For very long tab content, the wrapper just increased in length instead of staying the same and make content scrollable? That is not the right behavior right?

It have the same behaviour right now in main.

And with vertical tab, content just flows out of the wrapper altogether

overflow: auto added to vertical tabs fixes that, but then it gets two scrollbars. I guess it's better than overflowing content.


390 Add an API to return session chairs and runners

Requires an API key; see the API docs once they've
been updated.

Thanks @dchukhin I've removed those unused imports, and I ran flake8 on the files that were modified in this pull and cleaned up the other things it spotted.

looks good :ok:


JSON3 hangs IE7 with particular json data with long string property values.

I created a jsperf to demonstrate the issue.  Even in IE8 the issue is pronounced (allowing a mere 6 ops/second).  http://jsperf.com/json-parser-perf-ie-largestringproperties
We experienced an issue where json3 was causing the IE7 browser to literally hang.  I've tried running the jsperf in IE7 and it has only hung the browser thus far so there is no data yet.  IE8 took a while but it did finish.
Without IE profiler, I can see if I can generate some metrics from dynatrace to identify which specific function(s) or aspects of the functions might be the culprits.
EDIT: Dynatrace shows only one stand-out function and that is the lex() function when processing the string property value itself.  It took 4779ms to parse that one string.  I'm not sure why sometimes the browser hangs in our real environment (or the jsperf) but it doesn't hang when running the same parse in isolation, other than for the 5 seconds or more it's parsing and the cpu is pegged.
<?xml version="1.0" encoding="utf-8"?><browser_purepath_tree><nodeinfo level="7" function="lex()" arguments="" return="@<div class="columns columns-aligned ...TRUNCATED for brevity" start_ms="7658.334229629743" total_ms="4778.469051234164" exec_ms="4778.46923828125" exec="38.39862" api="json3, JavaScript" agent="Browser"/></browser_purepath_tree>

The main issue is commit cefa14ad99b
-          Source = "" + source;
+          Source = new String(source);

v8 bailsout on charCodeAt as it's an object instead of a string. See code-stubs.h.

The main issue is commit cefa14ad99b
-          Source = "" + source;
+          Source = new String(source);

v8 bailsout on charCodeAt as it's an object instead of a string. See code-stubs.h.

I ran a quick proof-of-concept with simply validating the json with the current recursive descent parser, and then using eval. Speed does improve significantly on newer browsers. Unfortunately IE9 turned out to be a lot slower, and I do not have access to IE7-8, so it requires more research.
http://jsperf.com/json-parser-perf-ie-largestringproperties/18
The JSON3_EVAL is the latest version with the diff https://gist.github.com/oxyc/6d02b15b745638805afd (tests pass)

I ran a quick proof-of-concept with simply validating the json with the current recursive descent parser, and then using eval. Speed does improve significantly on newer browsers. Unfortunately IE9 turned out to be a lot slower, and I do not have access to IE7-8, so it requires more research.
http://jsperf.com/json-parser-perf-ie-largestringproperties/18
The JSON3_EVAL is the latest version with the diff https://gist.github.com/oxyc/6d02b15b745638805afd (tests pass)

@oxyc Thanks for the research, I'll remove the new String usage. Will experiment with the others.

@oxyc Thanks for the research, I'll remove the new String usage. Will experiment with the others.

Here's the latest jsPerf: http://jsperf.com/json-parser-perf-ie-largestringproperties/19.

Here's the latest jsPerf: http://jsperf.com/json-parser-perf-ie-largestringproperties/19.

Also, I'm not too sure, but I feel that one of the main reasons JSON3.parse is slow is due to the number of function calls (get -> lex -> ...). If there was a non-recursive way of parsing, I'm sure that would speed things up.

Also, I'm not too sure, but I feel that one of the main reasons JSON3.parse is slow is due to the number of function calls (get -> lex -> ...). If there was a non-recursive way of parsing, I'm sure that would speed things up.

For reference, I was curious to what it would look like if string literals were validated with a regex instead. This increased the speed in chrome (past nativeJSON for this particular edge case) but decreased in IE9 once again.
I basically replaced the string literal loop in lex() with a naive regex (fails some tests but works well enough for benchmarking)
                var reNeedsEscape = /"([^"\\]*|\\["\\bfnrt\/]|\\u[0-9a-fA-F]{4})*"/;
                var reEscape = RegExp(reNeedsEscape.source, "g");
                var res = reEscape.exec(source.slice(Index));
                if (res) Index += res[0].length;
                else abort();
                return "@"

In case you want to check IE8 here's the jsPerf: http://jsperf.com/json-parser-perf-ie-largestringproperties/20 (includes the eval parsing modification from earlier).

For reference, I was curious to what it would look like if string literals were validated with a regex instead. This increased the speed in chrome (past nativeJSON for this particular edge case) but decreased in IE9 once again.
I basically replaced the string literal loop in lex() with a naive regex (fails some tests but works well enough for benchmarking)
                var reNeedsEscape = /"([^"\\]*|\\["\\bfnrt\/]|\\u[0-9a-fA-F]{4})*"/;
                var reEscape = RegExp(reNeedsEscape.source, "g");
                var res = reEscape.exec(source.slice(Index));
                if (res) Index += res[0].length;
                else abort();
                return "@"

In case you want to check IE8 here's the jsPerf: http://jsperf.com/json-parser-perf-ie-largestringproperties/20 (includes the eval parsing modification from earlier).

I think that it’s not very important to have better performance for modern browsers (Chrome) as they would already have valid JSON.parse implementations. We should instead focus on older browsers (IE 6 - 8, etc.).

Modern browsers could be valid for mobile.

Yep, I’m also experimenting, currently with a non-recursive implementation. Also, if you need access to IE 8, you could use an online service like Sauce Labs.

Here’s my non-recursive implementation: https://github.com/d10/json3/commit/507278b9f9684b608bec3a2f2a626a9d44797a87. I haven’t tested it yet, will try to do so soon.

@d10 Nice! Another approach might be to use a validating parser (here's a very rough, untested port of Go's encoding/json state machine), followed by new Function('return (' + source + )'). That has its own drawbacks, though. I'll run some benchmarks once I have access to my VMs again.

Here’s a jsPerf: http://jsperf.com/json-parser-perf-ie-largestringproperties/23. Seems much slower than current. @oxyc’s regex implementation seems to be the fastest. I will also try to experiment with my non recursive implementation, which currently dies not work.

Cool; RegExp it is. We can tighten it to perform additional validation and measure its impact. Thanks, @oxyc!


Make Spacer extend Expanded

I made Spacer extend Expanded instead of StatelessWidget.
Attempt to fix https://github.com/flutter/flutter/issues/98787
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

What's the rational for this change? I think, overall Flutter prefers composition over inheritance.

Looks like there's another duplicated PR for this: https://github.com/flutter/flutter/pull/98788

After a quick chat with @Hixie , it was decided the issue was not valid and therefore, I'm closing this PR.
Thank you @goderbauer for reviewing it.


Copy scripts to instance catalog

Closes #1014
Pull request acceptance prerequisites:

[x] Signed the CLA (if not already signed)
[x] Rebased/up-to-date with base branch
[x] Tests pass
[ ] Updated CHANGELOG.md with patch notes (if necessary)
[x] Updated CONTRIBUTORS (if attribution is requested)

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Thank you so much for the PR/fix @Jakski - just so you're aware, we're working through some issues with our CLA automation, so even if you signed it, it may not show up here, but we're working on it.
Also, it's likely that your tests will fail, but that's because some of the tests are in a state of disrepair and need to be updated/disabled for the time being - I'm working on that now, and will let you know when you can merge in the latest changes from master that should let the test run/hopefully pass normally.

@Jakski the tests are fixed, so if you could merge in the latest master into your branch we should be able to see legitimate tests :+1:
I'll keep an eye on clearing out the CLA failing check once that's resolved (assuming it's signed).

Thanks @Jakski - I had a branch that makes this parameter customizable instead of statically set to 2, so I've merged your additional changes into my branch and created a new PR, I'll follow up getting those changes in at #1022


Browser integration

Introduction
The current implementation and also the module type do not work with both Karma and webpack.
The main reasons for this are

module type is commonjs, in order to make this work with browsers, we need to use a different module type
di/typedi module name clashes with the import "typedi" and results in recursive require, so we need to refactor this out to a separate package

Originating Issues
This supersedes the following issues

#108
#112
#114

Proposal
In order to solve this problem, I make the following proposal

switch to lerna and make this a monorepo, with the following packages

mocha-typescript
mocha-typescript-di-typedi

by default, these will use the standard CJS (commonjs) module type, but for browser integration
we will have to package this also using webpack. The target will then be dist/ and users wanting to integrate this into their web based projects need to require ("mocha-typescript/dist") instead of just mocha-typescript. Using webpack/karma, this can be aliased to just "mocha-typescript", I believe.
Initial Prototype
An initial prototype for this can be found in the branch https://github.com/pana-cc/mocha-typescript/tree/gh-157

Browser integration now works fine and this is also backed by integration tests on the gh-157 branch.

With #181 in place, we have no confidence whether this will work with karma or similar such solutions. Reopening.

Given the existing seeds for react and angular, which all use karma, this seems to be no longer an issue.


Enhance the Container Runtime Interface

Feature Name

One-line feature description (can be used as a release note): Enhance the Container Runtime Interface (e.g., add container and image filesystem metrics/stats, improve debuggability, etc.)
Primary contact (assignee): @yujuhong
Responsible SIGs: Node
Design proposal link (community repo):
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @dchen1107 @Random-Liu
Approver (likely from SIG/area to which feature belongs): @dchen1107
Feature target (which target equals to which milestone): Alpha 1.7

@yujuhong please, update the feature description with the design proposal.

@yujuhong, were there additional improvements planned for the 1.7 release cycle besides https://github.com/kubernetes/kubernetes/pull/45614? If not I'll go ahead and close this issue and we can open a new issue for 1.8. Thanks!
cc, @dchen1107, @idvoretskyi, @kubernetes/sig-node-feature-requests, @kubernetes/kubernetes-release-managers

@calebamiles UPD. There is no necessity to close the issue - just move it to the "next-milestone" if it's not planned for 1.8 anymore.

Where is the design proposal ? or I should just check kubernetes/kubernetes#45614 ?

Where is the design proposal ? or I should just check kubernetes/kubernetes#45614 ?

There is a doc: https://github.com/kubernetes/community/blob/master/contributors/devel/cri-container-stats.md


docs: Add missing values for persistence in values.yaml

Adds missing values in values.yaml for parameters found in "charts/questdb/templates/statefulset.yaml".

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ramosber seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


False positive: Typosquatting

Hi there, first off all: awesome tools you guys made! :tada:
Second, I encountered the following output when scanning a requirements.txt file:
Found 2 potentially malicious indicators in ruamel-yaml version 0.17.21

typosquatting: This package closely ressembles the following package names, and might be a typosquatting attempt: ruamel-yaml, ruamel-yaml

code-execution: found 1 source code matches
  * setup.py file executing code at ruamel.yaml-0.17.21/setup.py:955
        subprocess.check_output(cmd)

I do get why the second indicator is found, but the first one confuses me:
The package name (also installed on my machine) is ruamel.yaml. There is no package named ruamel-yaml in either my requirements nor on PyPi. Did something went from with the dots in the package name? Or is it because this package is listed in your typosquatting list as ruamel-yaml?
Thanks!

Hi Hugo,
Thanks for reporting! It does sound abnormal, likely a confusion with the - and the . indeed. We'll look into fixing it

same applies to
Found 1 potentially malicious indicators in pdfminer.six version 20221105

typosquatting: This package closely ressembles the following package names, and might be a typosquatting attempt: pdfminer-six, pdfminer-six

Looked a bit into it: the problem arises outside this project. In the used PyPi top list, these false positives are mentioned with a - instead of a . (see ruamel.yaml). You might fix that by making changes to either the original list or by including a separated list of known false positives..

Thanks! I think the easiest way is to normalize the package name passed as an input, and consider that scanning a.b.c is actually going to scan a-b-c. Sounds good to you?

Seems like the easiest way to fix it indeed! However, would that not increase the number of missed typosquats? E.g., with pdfminer.six published on PyPi, a malicious actor can publish pdfminer-six. With your proposed fix, this malicious package will not be detected, right?

Hi! I don't think that should be an issue since PEP 503 states:

This PEP references the concept of a “normalized” project name. As per PEP 426 the only valid characters in a name are the ASCII alphabet, ASCII numbers, ., -, and _. The name should be lowercased with all runs of the characters ., -, or _ replaced with a single - character.

Additionally:

Repositories MAY redirect unnormalized URLs to the canonical normalized URL (e.g. /Foobar/ may redirect to /foobar/), however clients MUST NOT rely on this redirection and MUST request the normalized URL.

You'll notice PyPi does redirect all of these to the same site:

https://pypi.org/project/pdfminer.six/
https://pypi.org/project/pdfminer-six/
https://pypi.org/project/pDfMiNeR.sIx/
https://pypi.org/project/pdfminer.-_-.six/

But more importantly, PIP does not rely on this redirection and gets the normalized URL thanks to pip._internal.utils.packaging. These utilities can be reused by importing packaging and normalizing the name before running the typosquat algorithm.

Will be released shortly, thanks all!

Released as part of v0.1.10 https://github.com/DataDog/guarddog/releases/tag/v0.1.10


KDE Applications 20.08.3

Motivation for this change
Update KDE Applications with a scheduled minor release. Fix the derivation names using the { pname, version } convention.
See: #107570.
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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] 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.

I was trying to build my system today on nixpkgs-unstable but calendarsupport fails to build, do you know if this problem is fixed with the patch for Qt 5.15.2 that you provided in this PR @ttuegel?
I'm getting the following error for reference:
builder for '/nix/store/dxmv0l2icv4kslgnl03hmdr1v8a599dl-calendarsupport.drv' failed with exit code 2; last 10 log lines:
    148 |         printer.setOrientation(QPrinter::Portrait);
        |                 ^~~~~~~~~~~~~~
        |                 Orientation
  /build/calendarsupport-20.08.2/src/printing/calprinter.cpp:151:17: error: 'class QPrinter' has no member named 'setOrientation'; did you mean 'Orientation'?
    151 |         printer.setOrientation(QPrinter::Landscape);
        |                 ^~~~~~~~~~~~~~
        |                 Orientation
  make[2]: *** [src/CMakeFiles/KF5CalendarSupport.dir/build.make:405: src/CMakeFiles/KF5CalendarSupport.dir/printing/calprinter.cpp.o] Error 1
  make[1]: *** [CMakeFiles/Makefile2:284: src/CMakeFiles/KF5CalendarSupport.dir/all] Error 2
  make: *** [Makefile:149: all] Error 2

Seems to be a Qt error so that's why I'm asking this ;)
I saw that this was not merged into master but into staging (and now it's on staging next). Do you know approximately when staging-next might be merged into master @ttuegel? I know that even after this, in can take a while to be available in nixpkgs-unstable but it can give me a rough idea nevertheless ^^

@ttuegel Backporting this one seems to be non-trivial. Do you know of any effort that is being done that could be referenced here?

@ttuegel Backporting this one seems to be non-trivial. Do you know of any effort that is being done that could be referenced here?


Unittest breaking with error for Centos Stream 9/EPEL 9

Describe the bug
Unittest breaking with error with 1.16 and Centos Stream 9/EPEL 9
And worked with 1.15
./unittest
assertion failure testcode/unitverify.c:199
Start of unbound 1.16.0+libevent unit test.
test authzone functions
test negative cache functions
test ub_random functions
test per-view respip config data apply functions
test global respip config data apply functions
test per-view respip config actions apply functions
test global respip config actions apply functions
test signature verify functions
test signature verify:./testdata/test_signatures.1
make: *** [Makefile:345: test] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.ZKuflj (%check)

To reproduce
Steps to reproduce the behavior:

build Unbound 1.16 for any architectures Centos Stream 9/EPEL 9

Expected behavior
Successful finishing of all tests
System:

Unbound version: 1.16
OS: CentOS Stream 9

Additional information
Log with error
https://download.copr.fedorainfracloud.org/results/fcsm/unbound/epel-9-x86_64/04500704-unbound/builder-live.log.gz
Log without error
https://download.copr.fedorainfracloud.org/results/fcsm/unbound/fedora-36-x86_64/04500704-unbound/builder-live.log.gz

This issue seems likely to be caused by the algorithm disable features in those recent distros. The test comes up to test sha1 and this could be disabled. Also other algorithms could be disabled.
You could compile with the feature switches at compile time to turn off those algorithms, and then the test should succeed. It checks if the algorithms are included before testing them.
But for a more automated test, the same type of runtime checks that are performed for fixing the algorithm usage on this type of deployment could also be used to make the test set perform checks on the algorithms.

Thanks


about style of item

how could i change the default width of treeiew. The distance between the node and the node of the next layer is too large，so i want to change

Hello @panliang-rm
This can handled like any other views, you have your xml layout and recycler view so you can control padding and margin
Thank you

sorry, i,don' t know why i can't get the current viewholder
TreeViewHolderFactory factory = (view, i) -> {
addPlanTreeViewHolder = new AddPlanTreeViewHolder(view, context);
return addPlanTreeViewHolder;
};
is null

And how could i get all treenodes, not just invisible

When initializing, I set the isExpanded property for the node; the property is set successfully, but the display is incorrect—it does not expand.


Figure out the API list that need for this tool

We may disable the TiFlash HTTP port inherited from ClickHouse. We need an API list that this tool needs and make them a formal API from the TiFlash server.

how to do authentication?


[IA-2255] add RStudio image to cloud environments dropdown

Changes in this PR:

Remove "Project Specific" option in dropdown (we are now including the RStudio Bioconductor image as an option in the dropdown so we no longer need the project specific option)
Adds new section in cloud environments dropdown called Community-Maintained RStudio Environments (verified partners)
Under the new section added, adds the Rstudio image with label RStudio (R 4.0.0, Bioconductor 3.11.1, Python 2.7.17)

Testing:

Tested with the corresponding changes to this terra-docker PR: https://github.com/DataBiosphere/terra-docker/pull/164
Verified that the new section + option are rendered as expected in the dropdown
Verified that I can choose the new option in the dropdown and the rstudio cloud environment starts up as expected
Verified that existing functionality still works as expected (if I have a runtime Running or Stopped that was built with the RStudio image that the image is selected in the dropdown and the R logo appears in the top right next to the pause button)

I wasn't able to test without the new json file, but the code looks good (pending the comments and lint fixes). Glad to see this simplification!

Since we're adding RStudio to the drop-down and we now have PDs, should we also remove this yellow banner?

@sharmatime

Also to summarize a standup conversation: let's wait for this Leo bug to be merged/released before releasing this UI change, since it's a pretty significant impact to RStudio experience: https://broadworkbench.atlassian.net/browse/IA-2244

Since we're adding RStudio to the drop-down and we now have PDs, should we also remove this yellow banner from the RStudio frame?

@sharmatime

just reached out to Adrian about this. will update accordingly

I wasn't able to test without the new json file, but the code looks good (pending the comments and lint fixes). Glad to see this simplification!

If you replace terra-docker-versions.json in line https://github.com/DataBiosphere/terra-ui/blob/dev/src/components/NewRuntimeModal.js#L469 with gabriela-test-rstudio.json you should be able to test with the new json if you're curious! i pushed that test json file to the google bucket the UI is getting the original file from

@panentheos I pushed all the changes for the PR feedback I received and this PR is now ready for final review


Move neural snow to an extension

The neural snow module is a major source is latency. This PR moves it to an extension, so that we don't pay the cost of loading it if we are not using it.
Closes #559

I think this is fine, my only question is with respect to future snow models, which may need to dispatch off of the depth parameterization type (of which the neural snow model is one type). For example, with the neural snow depth model, we have another prognostic variable, which we can add easily with our existing utilities with dispatch, but it seems like ClimaLand/src would need to know about the neural snow types in that case.

Yes, we will add all those types in ClimaLand, and leave the implementation of the infrastructure in the extension.
You can look at ClimaUtilities to get a sense of how this would look like.

@kmdeck anything else here?


Specify a query to reindex only the documents that belong satisfy a query, in reindex helper function.

It would be great if I were to be able to specify a query when reindexing, so that I can control what documents go into a new index. Instead of just all the documents.
If you don't specify the query it will just reindex all the documents.

Here is the pull request https://github.com/elasticsearch/elasticsearch-py/pull/173

this has been fixed by 87bba04


Node.js Thank you program

As part of the social media program there was some discussion on giving out gift certificates for the Node.js store.
I think a program that applied across all of the Node.js programs would make sense. @Trott already spreads some thanks but it would be great to regularly give out something more tangible as well.

Hello!
I just saw that some open source repositories send a gift card for the stores on the first contribution to the repo.
Maybe it can be done too on the Node.js side, only thinking on code contribution.

Would be helpful if anyone who has seen open source projects implement similar initiatives drops links to those through an issue comment here.
It would be great to see models of how this could work well!

I was wondering, the gift certificates will be for whom? Contributors, collaborators?
How will this work?

This is a great example from Gatsby:/
https://www.gatsbyjs.org/contributing/where-to-participate/
https://www.gatsbyjs.org/contributing/contributor-swag/

For many, a handwritten note saying "thank you" will be the most prized "Thank You". ❤

I've unarchived this repo so I can close all PRs and issues before re-archiving.


Issue with Accepts callback

Hi,
I need to create Action once drop completed... but accept callback fires ,when move starts and passing multiple unwanted updates to server
let options = {
	  accepts: function (el, target, source, sibling) {
		console.log(el, source, target, sibling); // This fires when moving
		return true;
	  }

  };

Mr.Bevacqua  ???
Any Idea ???

@sajumani you should look into the drop event.
Dragula([...])
    .on('drop', (el, target, source, sibling) => {
       // Create Action here
    });


PR for Issue #1002 Initializing Twindle Setup

Explanation of what this PR does:

For setup, interactive user input was required to setup the optional twitter access token, properties for sending the kindle email, setting up the Twindle library path and so on. For this purpose a new npm module called prompt was needed and this can be installed using npm install prompt
A new file called twindle.json will be created in User's Home directory. For windows, the path of the JSON file is C:\Users<user_name>\AppData\Roaming\twndle.json. This can be generated by running node setup/init
Current code which references process.env variables directly was modified to refer to utils/env.js function which checks the json setup file and uses that if present
If json setup file is absent then the current code defaults to the ENV file that we were already using.

Things to do:

If the json setup file is absent,then we must throw an error and the setup/init must be run to finish the setup process
Testing to be done - I tested with 5 to 10 tweets and the changes worked with the JSON file and without the JSON file but more testing needs to be done.

Description
To test the changes in this PR please do the following:
npm install prompt
node setup/init
Attach Screenshot

Note 2 code reviewer approval needed. Approach in twitter group & discord channel.

Great work Mira. This looks good.
I have some improvements in mind here, which we can tackle later.

I don't think we should default to the .env file in the end.
Just create the JSON file, without prompting if necessary. if it doesn't exists, just create it with empty values.

If user is trying to use twitter part, and key isn't configured, ask them for key, and show them articles to refer to if they need help, otherwise it isn't an issue if user is accessing hackernews or github, etc
No need for errors at that point

Node setup/init should be there by default. We shouldn't have to run it separately

Great work Mira. This looks good.
I have some improvements in mind here, which we can tackle later.

I don't think we should default to the .env file in the end.
Just create the JSON file, without prompting if necessary. if it doesn't exists, just create it with empty values.

If user is trying to use twitter part, and key isn't configured, ask them for key, and show them articles to refer to if they need help, otherwise it isn't an issue if user is accessing hackernews or github, etc
No need for errors at that point

Node setup/init should be there by default. We shouldn't have to run it separately

Great work Mira. This looks good.
I have some improvements in mind here, which we can tackle later.
1. I don't think we should default to the .env file in the end.

2. Just create the JSON file, without prompting if necessary. if it doesn't exists, just create it with empty values.

   * If user is trying to use twitter part, and key isn't configured, ask them for key, and show them articles to refer to if they need help, otherwise it isn't an issue if user is accessing hackernews or github, etc
   * No need for errors at that point

3. Node setup/init should be there by default. We shouldn't have to run it separately

This is totally different from how I envisioned this setup and initialized. Thanks for the clarification. Will refactor my code and make another PR

Great work Mira. This looks good.
I have some improvements in mind here, which we can tackle later.
1. I don't think we should default to the .env file in the end.

2. Just create the JSON file, without prompting if necessary. if it doesn't exists, just create it with empty values.

   * If user is trying to use twitter part, and key isn't configured, ask them for key, and show them articles to refer to if they need help, otherwise it isn't an issue if user is accessing hackernews or github, etc
   * No need for errors at that point

3. Node setup/init should be there by default. We shouldn't have to run it separately

This is totally different from how I envisioned this setup and initialized. Thanks for the clarification. Will refactor my code and make another PR


Handle null execution context in threadpool callback

Fixes #5603

I believe that this issue was exposed by CoreFX changes that suppressed execution context flow in various places.


Since video_player 1.0.0 was released, some versions do not build on Android.

Since video_player 1.0.0 was released, 1.0.0, 0.11.1+4, 0.11.1+5 versions do not build on Android.
It only works fine on iOS. So I fixed version to 0.11.1+2.
Is there anything I need to check to use the latest version?
Steps to Reproduce

Update video_player version to 0.11.1+4 or later.
flutter clean and pub get and build on Android/iOS device.

Expected results:
It should be successful on Android/iOS.
Actual results:
Build fails on Android and succeeds on iOS.

Logs

[        ] /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-1.0.0/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java:11: error: cannot find symbol
[   +1 ms] import io.flutter.FlutterInjector;
[        ]                  ^
[        ]   symbol:   class FlutterInjector
[        ]   location: package io.flutter
[        ] /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-1.0.0/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java:77: error: cannot find symbol
[        ]     final FlutterInjector injector = FlutterInjector.instance();
[        ]           ^
[        ]   symbol:   class FlutterInjector
[  +10 ms]   location: class VideoPlayerPlugin
[        ] /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-1.0.0/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java:77: error: cannot find symbol
[        ]     final FlutterInjector injector = FlutterInjector.instance();
[        ]                                      ^
[        ]   symbol:   variable FlutterInjector
[        ]   location: class VideoPlayerPlugin
[        ] 3 errors
[        ] FAILURE: Build failed with an exception.
[        ] * What went wrong:
[        ] Execution failed for task ':video_player:compileDebugJavaWithJavac'.
[        ] > Compilation failed; see the compiler error output for details.
[        ] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 22s
[ +381 ms] Running Gradle task 'assembleDebug'... (completed in 23.6s)
[   +5 ms] Exception: Gradle task assembleDebug failed with exit code 1
[   +2 ms] "flutter run" took 28,625ms.
[   +5 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:591:7)
           <asynchronous suspension>
           #2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:860:18)
           #3      _rootRunUnary (dart:async/zone.dart:1198:47)
           #4      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #5      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #7      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #8      Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #11     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
           #12     _rootRunUnary (dart:async/zone.dart:1198:47)
           #13     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #14     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #16     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #17     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #18     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #19     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #20     AndroidDevice.isLocalEmulator (package:flutter_tools/src/android/android_device.dart)
           #21     _rootRunUnary (dart:async/zone.dart:1198:47)
           #22     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #23     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #24     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #25     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #26     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #27     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
           #28     _rootRun (dart:async/zone.dart:1190:13)
           #29     _CustomZone.run (dart:async/zone.dart:1093:19)
           #30     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
           #31     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
           #32     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #33     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #34     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
           #35     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

[✓] Flutter (Channel stable, 1.20.1, on Mac OS X 10.15.6 19G2021, locale ko-KR)
    • Flutter version 1.20.1 at /Users/user/Documents/flutter
    • Framework revision 2ae34518b8 (3 months ago), 2020-08-05 19:53:19 -0700
    • Engine revision c8e3b94853
    • Dart version 2.9.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/user/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Users/user/Downloads/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C505
    • CocoaPods version 1.9.1

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

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

[✓] Connected device (1 available)
    • Pixel 3a (mobile) • 94FAY0NHHD • android-arm64 • Android 10 (API 29)

• No issues found!

@hyejobs
Tried 0.11.1+4, 0.11.1+5 plugin versions on Android 8.1.0 device using latest stable (1.22.3) and was able to compile and run app without any issues.
I noticed that the latest video_player version ^1.0.0 is just released today (Nov 4) and there are no details in the changelog yet, but I'd wait for couple of days for the team to update if there are any major changes that need to be done before using the plugin (but I don't think that is required). you should be able to run the plugin out of the box.
Also, I'd suggest you to upgrade to latest stable and then then run flutter clean after you upgrade your plugin version.

Hello
I have the same symptoms of failing the build the same.
11:22:06 android build command: flutter build apk lib/main_dev.dart
11:22:06 -----------------------------------------------------------------------------
11:22:06
11:22:07 You are building a fat APK that includes binaries for android-arm, android-arm64, android-x64.
11:22:07 If you are deploying the app to the Play Store, it's recommended to use app bundles or split the APK to reduce the APK size.
11:22:07     To generate an app bundle, run:
11:22:07         flutter build appbundle --target-platform android-arm,android-arm64,android-x64
11:22:07         Learn more on: https://developer.android.com/guide/app-bundle
11:22:07     To split the APKs per ABI, run:
11:22:07         flutter build apk --target-platform android-arm,android-arm64,android-x64 --split-per-abi
11:22:07         Learn more on:  https://developer.android.com/studio/build/configure-apk-splits#configure-abi-split
11:22:07 Running Gradle task 'assembleRelease'...
11:23:55 Note: /Users/jenkins/flutter/.pub-cache/hosted/pub.dartlang.org/appsflyer_sdk-5.4.1+1/android/src/main/java/com/appsflyer/appsflyersdk/AppsflyerSdkPlugin.java uses unchecked or unsafe operations.
11:23:55
11:23:55 Note: Recompile with -Xlint:unchecked for details.
11:23:59
11:23:59 Note: /Users/jenkins/flutter/.pub-cache/hosted/pub.dartlang.org/multi_image_picker-4.7.14/android/src/main/java/com/vitanov/multiimagepicker/FileDirectory.java uses or overrides a deprecated API.
11:23:59
11:23:59 Note: Recompile with -Xlint:deprecation for details.
11:24:01
11:24:01 Note: Some input files use or override a deprecated API.
11:24:01
11:24:01 Note: Recompile with -Xlint:deprecation for details.
11:24:01
11:24:01 Note: Some input files use unchecked or unsafe operations.
11:24:01
11:24:01 Note: Recompile with -Xlint:unchecked for details.
11:24:20
11:24:20 Note: /Users/jenkins/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links-0.4.0/android/src/main/java/name/avioli/unilinks/UniLinksPlugin.java uses or overrides a deprecated API.
11:24:20
11:24:20 Note: Recompile with -Xlint:deprecation for details.
11:24:23
11:24:23 /Users/jenkins/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-0.11.1+5/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java:11: error: cannot find symbol
11:24:23
11:24:23 import io.flutter.FlutterInjector;
11:24:23
11:24:23                  ^
11:24:23
11:24:23   symbol:   class FlutterInjector
11:24:23
11:24:23   location: package io.flutter
11:24:23
11:24:23 /Users/jenkins/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-0.11.1+5/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java:77: error: cannot find symbol
11:24:23
11:24:23     final FlutterInjector injector = FlutterInjector.instance();
11:24:23
11:24:23           ^
11:24:23
11:24:23   symbol:   class FlutterInjector
11:24:23
11:24:23   location: class VideoPlayerPlugin
11:24:23
11:24:23 /Users/jenkins/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-0.11.1+5/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java:77: error: cannot find symbol
11:24:23
11:24:23     final FlutterInjector injector = FlutterInjector.instance();
11:24:23
11:24:23                                      ^
11:24:23
11:24:23   symbol:   variable FlutterInjector
11:24:23
11:24:23   location: class VideoPlayerPlugin
11:24:23
11:24:23 3 errors
11:24:23
11:24:23
11:24:23
11:24:23 FAILURE: Build failed with an exception.
11:24:23
11:24:23
11:24:23
11:24:23 * What went wrong:
11:24:23
11:24:23 Execution failed for task ':video_player:compileReleaseJavaWithJavac'.
11:24:23
11:24:23 > Compilation failed; see the compiler error output for details.

The flutter version I'm using
flutter doctor -v
[✓] Flutter (Channel unknown, 1.20.4, on Mac OS X 10.15.7 19H2, locale ko-KR)
    • Flutter version 1.20.4 at /Users/teamblind_mac/flutter-sdk/flutter
    • Framework revision fba99f6cf9 (7 weeks ago), 2020-09-14 15:32:52 -0700
    • Engine revision d1bc06f032
    • Dart version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/teamblind_mac/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[!] IntelliJ IDEA Ultimate Edition (version 2019.2.4)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    • Dart plugin version 192.7761
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[!] IntelliJ IDEA Community Edition (version 2019.2.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    • Dart plugin version 192.7402
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

Will it only work with the latest version of Flutter?

when update flutter to v1.22.3, error gone!! thanks @darshankawar

When I got this error my flutter version was 1.20.1.
Solved after updating flutter to 1.22.3. thanks!

@hyejobs Glad to know your issue is resolved.
Closing this per your comment above.


⚠ Bofrost.es has degraded performance

In c0b5647, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1322 ms

Resolved: Bofrost.es performance has improved in 5bc4d59 after 17 minutes.


https://atacuki.github.io/fps-game-test/

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
bat game
What part(s) of the article would you like to see updated?
?
Additional information
monkey

https://atacuki.github.io/fps-game-test/
docs-bot @.***>, 17 Haz 2024 Pzt, 14:48 tarihinde şunu
yazdı:

Closed #33535 https://github.com/github/docs/issues/33535 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/33535#event-13184519948, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BC2Z5LP5SH7WZCKB3LDV5ATZH3EIXAVCNFSM6AAAAABJN22CIGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGE4DINJRHE4TIOA
.
You are receiving this because you authored the thread.Message ID:
@.***>


folly: 2<IP_ADDRESS> -> 2<IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/facebook/folly/releases.
meta.description for folly is: "An open-source C++ library developed and used at Facebook"
meta.homepage for folly is: "https://github.com/facebook/folly"
meta.changelog for folly is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2<IP_ADDRESS> with grep in /nix/store/rcidddw9v7br88rl6i3l4vg8sh2racm1-folly-2<IP_ADDRESS>
found 2<IP_ADDRESS> in filename of file in /nix/store/rcidddw9v7br88rl6i3l4vg8sh2racm1-folly-2<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
folly
wdt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rcidddw9v7br88rl6i3l4vg8sh2racm1-folly-2<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A folly https://github.com/r-ryantm/nixpkgs/archive/5199c1593eec9f32a10be3de0773b20c0edc0bf8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rcidddw9v7br88rl6i3l4vg8sh2racm1-folly-2<IP_ADDRESS>
ls -la /nix/store/rcidddw9v7br88rl6i3l4vg8sh2racm1-folly-2<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

folly
wdt

Maintainer pings
cc @abbradar @pierreis for testing.

Package built went fine on NixOS 22.05 Linux x64 using nixpkg-review
2 packages built:
folly wdt

Upstream changes look minor


The microsite is fuX0r3d

Now we are good https://http4s.github.io/http4s-session/

We should get these on subdomains at some point...


Bug in beam_search: memory allocation

If run this code:
model = Qwen2VLForConditionalGeneration.from_pretrained(
    "Qwen/Qwen2-VL-7B-Instruct",
    torch_dtype=torch.bfloat16,
    attn_implementation="flash_attention_2",
    device_map="auto",
    cache_dir="/model/Qwen/"
)
(...)

messages = [
    {
        "role": "user",
        "content": [
            {
                "type": "video",
                "video": "/data/NExTQA/NExTVideo/total/9996338863.mp4",
                # "image": "https://qianwen-res.oss-cn-beijing.aliyuncs.com/Qwen-VL/assets/demo.jpeg",
            },
            {"type": "text", "text": "Describe this video."},
        ],
    }
]
(...)
outputs = model.generate(**inputs, max_new_tokens=10, return_dict_in_generate=True, output_scores=True, do_sample=True, num_beams=2)

Then OutofMemoryError occurs:
torch.OutOfMemoryError: CUDA out of memory. Tried to allocate 538976288.13 GiB. GPU 1 has a total capacity of 47.54 GiB of which 43.55 GiB is free. Process 741857 has 3.97 GiB memory in use. Of the allocated memory 3.19 GiB is allocated by PyTorch, and 478.31 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)

in  6 x A6000 GPUs.
The Tried to allocate 538976288.13 GiB. message in error message is such ridiculous numeric.
p.s. following code works, in  our GPU server(this code works in only 1 Nvidia A6000).
outputs = model.generate(**inputs, max_new_tokens=10, return_dict_in_generate=True, output_scores=True)

Use the Image optimization to do the minimal usage of GPU during inferencing.The code for the image optimization is as follow:
min_pixels = 256 * 28 * 28
max_pixels = 1280 * 28 * 28
processor = AutoProcessor.from_pretrained(
    "Qwen/Qwen2-VL-7B-Instruct", min_pixels=min_pixels, max_pixels=max_pixels
)

@HemanthoDarwin-RabertKennedy-ZS0532 Thanks you for your reply.
However, there's a new error: RuntimeError: probability tensor contains either inf, nan or element < 0.
Traceback (most recent call last):
  File "/home/ywjang/LBA_LAVIS_uncertainty_v2/main_multi_subqa.py", line 840, in <module>
    main()
  File "/home/ywjang/LBA_LAVIS_uncertainty_v2/main_multi_subqa.py", line 214, in main
    text_outputs_base, confidences_base = recomposer(vision, text_inputs)
  File "/home/ywjang/miniconda3/envs/qwen2vl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1553, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/ywjang/miniconda3/envs/qwen2vl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1562, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/ywjang/LBA_LAVIS_uncertainty_v2/models/model.py", line 482, in forward
    outputs = self.model.generate(
  File "/home/ywjang/miniconda3/envs/qwen2vl/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/home/ywjang/miniconda3/envs/qwen2vl/lib/python3.10/site-packages/transformers/generation/utils.py", line 2046, in generate
    result = self._beam_search(
  File "/home/ywjang/miniconda3/envs/qwen2vl/lib/python3.10/site-packages/transformers/generation/utils.py", line 3257, in _beam_search
    next_tokens = torch.multinomial(probs, num_samples=n_tokens_to_keep)
RuntimeError: probability tensor contains either `inf`, `nan` or element < 0

I am getting accuracy loss to set the min and max pixels for this model. If not set i am getting cuda out of memory in A100 80GB machine also.
If i am setting min and max pixels that is given by huggingface, The model takes maximum 24GB worth cuda memory. But i had lots of accuracy loss on this.


Dojo: Increase admin visibility

Motivated from the Discord:

Hi Dr. Kanak, I have a question about the owner/creator of one dojo and the dojo admin. It seems some functionability (e.g., make the dojo official) needs both roles satisfied.
And I encountered a wired issue in making one dojo official: The owner A creates a dojo. He/She can see this dojo in its management webpage and have “Promote to Admin”, but does not have "Make the dojo official". However, the dojo admin cannot access this dojo with admin privilege.
So we need to resort to database modification about this operation

@ConnorNelson it works as expected. For dojo admin, you can go to "Admin Panel" -> "Dojos" -> "Dojo you would like to operate on" -> "Dojo Admin Panel". Then make it official


Remove overlapping BEq instance

I've also removed all the other priority annotations on instances.  Those were unnecessary and just gave a false sense of utility.  Don't use instance priorities unless you absolutely know what you're doing, can clearly explain why they're necessary, have verified that it doesn't work without, and added a comment documenting that fact!

Thanks!


Addition of transport for Modflow 6 not in changelog yet

In GitLab by @JoerivanEngelen on Aug 1, 2022, 15:49
The addition of transport for Modflow 6 is not included yet in the changelog:
https://deltares.gitlab.io/imod/imod-python/api/changelog.html

In GitLab by @JoerivanEngelen on Feb 3, 2023, 09:26
I either missed this or it has been added since, but it's now denoted in this section:
https://deltares.gitlab.io/imod/imod-python/api/changelog.html#id8


New Post UI Created and Responsiveness Added

Hi, Plz have a look on New Mobile and Tablet UI
Issue Number 476

Plz merge my pull request as a GSSOC'23 Contributor

Thanks for your contribution :)

Thank You so much @narayan954 for providing me the opportunity to work on this repository 🤩


Overlap coefficient is not correct

In the implementation of the Overlap coefficient function, the intersection is divided by the minimum of the cardinality of the sets, and not the lengths of the sentences.
For example, "hello" and "world", coefficient = 0.5
>>> textdistance.overlap("hello", "world") 0.4

Textdistance provides the same interface and default parameters for all algorithms. By default, all sequences compares by elements. You can compare them as sets with special argument:
textdistance.Overlap(as_set=True)("hello", "world")

This is because for big enough sentences comparison as sets has no meaning and will produce close values (because alphabet for sentences will be almost the same).

This is your first issue, congrats :)

Thanks for fast answer!
It's work. Thank you! Let's close this