Replace length(min,max) with range operator

The range operator .. should be the syntax used by garde to perform HasLength validation. This would also provide more information to HasLength implementations, making them more performant.
Example
struct People {
  #[garde(length(2..))]
  linked_list : LinkedList<Person>
}

Using would make the HasLength impl return faster, as it wouldn't be necessary to compute the whole length of the linked list (related to https://github.com/jprochazk/garde/issues/5)
Range operator is a well know Rust feature

This would also provide more information to HasLength implementations, making them more performant

Can you expand on this? What information does x..=y have that min=x, max=y doesn't?

Using would make the HasLength impl return faster, as it wouldn't be necessary to compute the whole length of the linked list

LinkedList::len computes in O(1), because it keeps track of its length.
As for the syntax, I politely disagree. I don't think ranges are a good match here! Ranges are primarily used for slicing, which is a kind of indexing operation. length does not index into your collection, it only checks its length against some bounds. I copied the syntax from validator, and I don't think we should try to fix what isn't broken.

Can you expand on this? What information does x..=y have that min=x, max=y doesn't?

Because it's a type, it contains more information than just the values. This could be passed to the HasLength impl to improve performance (see below)

LinkedList::len computes in O(1), because it keeps track of its length.

I didn't know LinkedList keeps track of the current length :). Nonetheless, it was just an example where the length operation might be O(n). Other data structures will behave differently

Ranges are primarily used for slicing, which is a kind of indexing operation

Ranges are much more powerful than that. They can be used to specify any kind of range, not only "indexes"

Character ranges ('A'..'Z').contains('B')
String ranges ("hello".."world").contains(&"a");
Time periods ...
...

Anything that has either a start or end (or even none of them!) can be represented using ranges. And of course, as expected by the Rust compiler team, Ranges are heavily optimised for performance

I copied the syntax from validator

Validator wasn't designed with a composable design, and it shows on things like this. For instance, see https://github.com/Keats/validator/issues/205

it seems like the derive macro filters what types you can use manually.

Rust has a rich type system we could leverage to our advantage to perform validation. We just need to use it

Anything that has either a start or end (or even none of them!) can be represented using ranges. And of course, as expected by the Rust compiler team, Ranges are heavily optimised for performance

My understanding is that the .contains calls ultimately compile down to comparison ops. We're just using those comparison ops directly instead. But we don't have to guess, godbolt confirms this.
That being said, maybe there's some type system magic niche somewhere that I'm not aware of which could improve performance for length checks in garde. If that's the case, I encourage you to make the change and benchmark it! It shouldn't require any changes to the syntax, though.

Validator wasn't designed with a composable design, and it shows on things like this

I don't think changing the syntax makes any difference in terms of composability here. Do you have any concrete examples?

Rust has a rich type system we could leverage to our advantage to perform validation. We just need to use it

Yep, I agree, which is why the validation rules in garde are based on traits instead of plain functions.

My understanding is that the .contains calls ultimately compile down to comparison ops

I had something else on my mind while writing that comment. To my knowledge, there are no performance benefits intrinsic to the Range type. Apologises for the misunderstanding

I don't think changing the syntax makes any difference in terms of composability here. Do you have any concrete examples?

As you noted, the macro could emit ranges and delegate the bound checks to the specific impl. Syntax could be left as it is.

As you noted, the macro could emit ranges and delegate the bound checks to the specific impl. Syntax could be left as it is.

I see, I think I also misunderstood what you were suggesting. Correct me if I'm wrong, but you're saying that this code:
https://github.com/jprochazk/garde/blob/62292a11a4446c16d9ec3118b8ebde1dd797adee/garde/src/rules/range.rs#L19
Should accept some R: RangeBounds<T> instead of (min, max) values, and then delegate the bounds checking to R::contains? If that is the case, then I agree it would be a significant improvement.

delegate the bounds checking to R::contains

Rather delegate the bounds checking to the particular HasLength impl, something like
// Allows
pub trait HasLength<RangeType> {
    fn check(&self, range: RangeType) -> Result<(),Error>;
}

// Most collections will do this
impl HasLength<T, RangeType: RangeBounds> for Vec<T>{
    fn check(&self, range: RangeType) -> Result<(),Error> {
        if range.contains(self.len()) { Ok(()) } else { Err(...) }
    }
}

// Other collections, where `len()` is O(N) would choose any other impl

I see, but in case of length and byte_length, you can already do this by implementing the Length/ByteLength trait directly. HasLength/HasByteLength is only meant for types which compute length in constant time. Seems like this is more of a problem with lacking documentation!
I still think the range rule could be generalized to support any RangeBounds type, which would allow something like:
struct Foo {
  value: char,

}

but that's a separate issue.

I still think the range rule could be generalized to support any RangeBounds type,

Yea thats a good one
To be honest, i think everything could be generalised even further into traits. Something like this:
pub trait Validator<T> {
   type Context;
   fn validate(&self, ctx: &Context, value: T) -> garde::Result {
      todo!()
   }
}

impl <T: AsRef<str>> Validator<T> for Email {
   type Context = ();
   fn validate(&self, ctx: &Context, value: T) -> garde::Result {
      todo!()
   }
}
// ...

use garde::validators::Email;
use garde::validators::Regex;

#[derive(Validate)]
pub struct Person {
  #[validate(Email)]
  name: String,
  // Range impls Validate<Vec<T>>, Validate<LinkedList<T>>,...
  #[validate(18..=20)]
  age: NonZeroUsize,
  // impl AsRef<str>, so it could support `Regex`
  #[validate(Regex(r"[\w/]{1,20}")]
  foo: camino::Path,
}

But now Email is a struct, so you couldn't implement that rule for something that isn't AsRef<str>.
You could solve it by having an Email struct (which you pass to validate), and some ValidateEmail trait that would have a blanket impl for AsRef<str>... And now you've got basically the same design as this library, only worse, because you don't get the opportunity to have nice error messages for "obviously wrong" usage (like duplicate rules).

But anyway, seeing as the use case:

it wouldn't be necessary to compute the whole length of the linked list

Is addressed by implementing Length/ByteLength directly, I'm going to close this issue.

But now Email is a struct, so you couldn't implement that rule for something that isn't AsRef.

Given that emails are expected to be valid strings, I don't see how this is an issue. Specially when using AsRef<str> unlocks a lot of types. I can name a few:

Box<str>
Arc<str>
String
camino::Path # External crate, for free!
camino::PathBuf # External crate, for free!
Cow
SmallStr # External crate, for free!

Also, the docs list AsRef<str> as one of the implementors of the email rule (https://docs.rs/garde/latest/garde/rules/email/trait.Email.html#impl-Email-for-T)

you couldn't store any state in the validator anyway

See the another_one field on the example. The validator would be configurable and also can receive state (context API). But yes, the validator must be stateless

the context API could be improved to support passing any kind of state to custom validators

https://docs.rs/axum/latest/axum/#sharing-state-with-handlers
Check axum::extract::State, and axum::extract::FromRef

In a nutshell: What the API I described earlier offers is to ditch the macro based design in favour of a trait based one

Given that emails are expected to be valid strings, I don't see how this is an issue.

This example is a bit contrived, but say you want to validate an email stored as a ropey::Rope. It isn't contiguous, so you can't get a &str from it directly without allocating an extra string.
The current email rule is already implemented over any AsRef<str>, but with your design, you couldn't implement it for anything else. As a consequence, the design you propose is strictly a subset of the current design, so as far as I can tell, it wouldn't unlock any new use cases. I encourage you to try using the types you listed in validated fields, because those are already supported!

What the API I described earlier offers is to ditch the macro based design in favour of a trait based one

The rules being deeply integrated into the macro is a feature, one which I don't want to ditch, because a good macro can significantly improve the user experience.
To give a more concrete example, the pattern rule actually attempts compiles the regex during macro expansion, and outputs out the resulting error (if there is one), so you know right away if the regex is invalid. You couldn't do this with your design, because the Regex validator may be renamed to anything by the user, so the macro would have no way of knowing that it's being given a regex that it should check. Good error messages are really important!

Check axum::extract::State, and axum::extract::FromRef

I know about this approach, but it's based on storing the state as dyn Any, which is problematic, because you don't discover incorrect usage until you try to extract the state, and it panics. Ideally a better context API would be strongly typed.

This example is a bit contrived, but say you want to validate an email stored as a ropey::Rope. It isn't contiguous, so you can't get a &str from it directly without allocating an extra string.

The regex crate wouldn't work either, and pretty much anything (that works with strings) expects an str. By convention, we expect str. It's a safe bet that covers most usecases. Nonetheless, keep reading :)

you couldn't implement it for anything else

You wouldn't be implementing an email rule, but a validator for ropey::Rope (Validator<ropey::Rope>)
pub struct RopeyValidator;

impl Validator<ropey::Rope> for RopeyValidator {
  type Context = RopeyRegex; // Or something like that

   fn validate(&self, ctx: &Context, value: ropey::Rope) -> garde::Result {
      if ctx.matches(value) { Ok(()) } else { Err(...) }
   }
}

This API ditches the idea of hardcoded rules in favour of generic Validators (implementors of the trait Validator<T> for some T). And every field with the #[garde] attribute is checked against all the defined set of validators. Nothing more, nothing less

a good macro can significantly improve the user experience.

It can also increase significantly complexity and compile times. Thats one of the main reasons most people ran away from heavy macro frameworks like Rocket. They generate too much code and makes rustc compile too slow!!

To give a more concrete example, the pattern rule actually attempts to compile the regex during macro expansion,

Thats worrisome. I don't see that documented on the docs. And it's definitely a behaviour I would like to disable. I don't need to benchmark it to know it increases compilation times on medium sized projects. Moreover, there are already existing solutions to this problem (https://docs.rs/lazy-regex/latest/lazy_regex/). Why would your implementation be better? I would consider regex compilation out of scope for this crate

You couldn't do this with your design, because the Regex validator may be renamed to anything by the user, so the macro would have no way of knowing that it's being given a regex that it should check

Right! That example is incomplete. Because regex::Regex and regex::bytes::Regex aren't constructed that way.
// Either this or the `lazy_regex` crate I linked earlier.
// 1. User is able to opt in into regex validation
// 2. Regex can be called elsewhere.
// 3. No more macro magic behind the curtains
lazy_static::lazy_static! {
   static ref RE: Regex = Regex::new("...").unwrap();
}

#[derive(Validate)]
pub struct Person {
  // Use RE directly, as it impls `Validate<T> where T: AsRef<str>`
  #[validate(RE]
  foo: String,
}

I know about this approach, but it's based on storing the state as dyn Any

Nope, that was axum::extract::Extension. Since the 0.6.0 release, sh*t got serious. State is type safe

I created a POC of the API. I included an example example/person.rs that showcases the API. It doesn't include a macro, but rather an aproximation of what the macro should produce
https://github.com/Altair-Bueno/garde-poc-validator
Note: For the sake of simplicity, i'm using ranges, but it can be anything else

You wouldn't be implementing an email rule, but a validator for ropey::Rope

As far as I can tell, that would require you to create N*M validators, where N is the number of types, and M is the number of rules. I think a less contrived example would be any string type which does not deref to &str.

It can also increase significantly complexity and compile times. Thats one of the main reasons most people ran away from heavy macro frameworks like Rocket.

A lot of people actually love Rocket's approach, but they "ran away" from it because it was unmaintained. I know at least I did.

Thats worrisome. I don't see that documented on the docs. And it's definitely a behaviour I would like to disable

You aren't disabling compile time validation of your regular expressions, you're just moving that work to a different macro. I plan to replace full regex with just regex_syntax, as I wasn't previously aware of its existence. But it doesn't make sense to allow disabling this feature, as otherwise you would get a panic when the regex is constructed at runtime.

Nope, that was axum::extract::Extension. Since the 0.6.0 release, sh*t got serious. State is type safe

Only for State, but you can't always use it, for the rest there's Extension which is not type safe.
To reiterate, the macro being deeply integrated with rules is a feature, and I have no plans to ditch it. Feel free to build out your POC into a more complete library and then use that instead! :)

But it doesn't make sense to allow disabling this feature, as otherwise you would get a panic when the regex is constructed at runtime.

Compile times. The more work the macro does, the slower it will compile. Its the same deal with sqlx and other macros that do too much

Only for State, but you can't always use it,

Yes you can, or at least I haven't found any problems whatsoever with FromRef
#[derive(FromContext)
pub ValidatorContext {
  context1: (),
  context2: FooContext,
  // ...
}

To reiterate, the macro being deeply integrated with rules is a feature, and I have no plans to ditch it.

Roger. Thanks for your time :)


Clear the internal package of unused/deprecated things

This removes some of the things mentioned in #7031.
I could also replace hashLower with scala.util.hashing.MurmurHash3 in the whole repo as suggested in the comment. Would that be a good idea or is there more do be done for replacing hashLower?

private[http4s] def compareField[A, B: Order] is only used in Uri. Could be moved there and made private. Opinions on that?

This could be done by using CIString for class TransferCoding and class Scheme which would be correct according to RFC, but breaking.

That sounds right, maybe deserves its own dedicated PR?

private[http4s] def compareField[A, B: Order] is only used in Uri. Could be moved there and made private. Opinions on that?

Sounds good to me 👍 then we can merge this one.

This could be done by using CIString for class TransferCoding and class Scheme which would be correct according to RFC, but breaking.

That sounds right, maybe deserves its own dedicated PR?

Yeah, that sounds right.

private[http4s] def compareField[A, B: Order] is only used in Uri. Could be moved there and made private. Opinions on that?

Sounds good to me +1 then we can merge this one.

After having another look at compareField: it is not even used in they way advertised in the javadoc. I simply replaced by Order.by[A, B](f).compare(a, b) and deleted compareField.  Updating Pull request when lint is happy.

I had some arguments with git while rebasing and in the process pushed a wrong commit. I fixed that but accidentally brought mergify to add module:laws module:ember-core module:circe labels. This PR does not involve these modules. Sorry...


Stepping back from Thanos maintainers

I'm stepping back from Thanos maintainers. Unfortunately I don't have time to follow Thanos dev and community, and I think it's just unfair keep wearing this hat.
Let me just say I ❤  Thanos community and project! Vibrant, active, nice people. I learned a lot from all of you, thanks!

Do you want to add yourself to the Previous Maintainers list?

Yep, done!

Nooo, it's unfortunate to see that you're leaving. Thanks for everything you have done!


Full Scottish Gaelic translation.

Translated and proofed by Stòrlann Nàiseanta na Gàidhlig.
References
None
Description
Translations into Scottish Gaelic have been made by staff at Stòrlann as part of their migration from DSpace 5.x to DSpace 7.x. They are offered to the community in hopes they will be useful.
Instructions for Reviewers
All strings have been translated and then checked by a second reviewer. However, there may still be typos, and there may be instances where the translation is incorrect (sometimes the context in which the original phrase was used could not be determined, and this may affect, for example, whether it is used as a command or as a title.)
For testing, note that the language code for Scottish Gaelic is "gd" and the language label should be "Gàidhlig".
Checklist
File has been run against the yarn json5 validator and passes. If there is anything else required, happy to look at it.

Thanks @donaldi and Stòrlann Nàiseanta na Gàidhlig!  I'll give this a quick review (not for accuracy of translations, but rather for completeness, etc) and see if we can fit this into 7.2 (due out next week). We might be able to squeeze it in, but if it misses that release, we'll definitely get it into 7.3.


Chatting Stats

Is it possible to gather some statistics about the usage?
Like sum of messages written.
Most active user.
Most tagged user.
etc.
I know it's possible to count the number of messages via the database. So it shouldn't be that difficult, is it?

:+1:


Enhance conversation ui

adjust  conversation ui
support hot key on recipients input

Coverage decreased (-0.01%) to 1.242% when pulling c3d38a97ad3d2f9248f300e4e07240f326d4a3c4 on embbnux:enhance-conversation-ui into 2fdbf3193c8bc1daa02d24f18684bba58a8f64a2 on ringcentral:master.


Fix: Support entering named colors into the input control.

Fixes the bug that reverts to black when you enter a named color.

thanks @krk could you run the grunt tasks for generate and reflect these changes on dist files too? thx


REST HTTP Crud booster

similar to https://github.com/wildfly-swarm-openshiftio-boosters/wfswarm-rest-http-crud

started here with basic functionality  https://github.com/bucharest-gold/nodejs-rest-http-crud


chore: update RELEASE procedures

@MaxTru Thanks to your feedback I was able to get rid of one section. Please have another look.


OCI nix-variant of the image spec

https://github.com/opencontainers/image-spec/blob/main/manifest.md
Notably, we could gather to submit proposal for a different mediaType:

application/vnd.nix.image.layer.v1.nar

application/vnd.oci.image.layer.v1.tar

application/vnd.oci.image.layer.v1.tar+gzip

application/vnd.oci.image.layer.nondistributable.v1.tar

application/vnd.oci.image.layer.nondistributable.v1.tar+gzip

/cc @manveru

I don't know exactly what you have in mind, but having a layer per nar is not possible since the number of layer is generally limited to 128 (kernel limitation i guess).
OCI layers are self contained while the JSON layer as used by nix2container relies on files which are in the Nix store (outside of the layer itself). So, i'm not sure it could fit the OCI layer model...

The idea would be that really a layer is a nix store path and that OCI compliant runtimes would know how to fetch layers from nix stores.
But you are absolutely right with the 128 layer limitation. I haven't thought about this.
Maybe this can serve nevertheless as an inspiration on how we can better integrate the nix distribution story with OCI distribution story.
Technically the 128 limit would require some synthetic predictably less-volatile base-layer of the kind that nix2container is precisely trying to avoid.

Connecting the breadcrumbs: https://github.com/opencontainers/image-spec/issues/922

@blaggacao would it be possible to add an option for a OCI layer that said it was non-colliding, and then the runtime could bind mount it instead of using overlayfs? It seems that would make the change to OCI a bit more general and potentially get around the 128 layers issue

Another option I'm wondering about is zstd:chunked https://www.redhat.com/sysadmin/faster-container-image-pulls


Jupyter Notebook Move Cell and Insert Cell Above not functioning

Issue Type: Bug
For Inserting Cell Above:

Create New Blank Jupyter Notebook
Enter and run something in the cell so it has output
Press 'esc' then 'a'
Expected: inserts cell above. Actual: moves input to above cell and leaves output in below cell.

For Moving Cell:

Create two cells and run something different in each so they each have different output
Move one cell past the other.
Expected: cells switch places, including both input and output. Actual: outputs switch but inputs stay where they are.

I think this may be a larger output handling problem, because I'm pretty sure I've seen running one cell change the output on a different cell too.
Extension version: 2019.10.44104
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (7.09GB free)

Process Argv

Screen Reader
no

VM
0%

This should be fixed in our insider's build


[Feature Request]: Metadata filter doesn't support array as filter value and IN operator for filter searching

Feature Description
I wanted to use a array as a value to my metadata filer for one of my projects. Locally I could run it by commenting couple of validations.
llama_index/core/vector_stores/types.py
def legacy_filters(self) -> List[MetadataFilter]:
"""Convert MetadataFilters to legacy ExactMatchFilters."""
filters = []
for filter in self.filters:
# if filter.operator != FilterOperator.EQ:
#     raise ValueError(
#         "Vector Store only supports exact match filters. "
#         "Please use ExactMatchFilter or FilterOperator.EQ instead."
#     )
filters.append(MetadataFilter(key=filter.key, value=filter.value))
return filters
llama_index/core/vector_stores/utils.py
def _validate_is_flat_dict(metadata_dict: dict) -> None:
"""
Validate that metadata dict is flat,
and key is str, and value is one of (str, int, float, None).
"""
for key, val in metadata_dict.items():
if not isinstance(key, str):
raise ValueError("Metadata key must be str!")
# if not isinstance(val, (str, int, float, type(None))):
#     raise ValueError(
#         f"Value for metadata {key} must be one of (str, int, float, None)"
#     )
is there any way I can use array as filter value or could you please provide this functionality so that I can use llama_index and mongodb vectorsearch for my project.
Reason
No response
Value of Feature
No response

I'm not sure why you had to comment out the legacy filters, the latest version of the package is not using legacy filters at all
https://github.com/run-llama/llama_index/blob/0ea7eec644d130b4a48389ea6fe47340b50bc094/llama-index-integrations/vector_stores/llama-index-vector-stores-mongodb/llama_index/vector_stores/mongodb/pipelines.py#L57
The only change needed in the framework would be to set flat_metadata=False on the class attribute of the vector store

Hi @logan-markewich, thanks you for your clarification. Is there any chance that we can have something like: self.flat_metadata = flat_metadata in this
https://github.com/run-llama/llama_index/blob/0ea7eec644d130b4a48389ea6fe47340b50bc094/llama-index-integrations/vector_stores/llama-index-vector-stores-mongodb/llama_index/vector_stores/mongodb/base.py#L92


LV522 Extra Ports

About the PR

Ports missing LV522 Tiles needed for mapping. (Corsat Tiles, Platebots, White_Cyan1)
Why / Balance

Needed for LV522
Technical details

None
Media

Requirements

[ X ] I have read and am following the Pull Request and Changelog Guidelines.
[ X ] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

None
Changelog

None

no clue about the errors


How it works with iTerm2?

How can I download the font and work with iTerm2?

These have long since been added to Nerd Fonts. Please see https://www.nerdfonts.com/font-downloads for font downloads. Should work out of the box for iTerm2.


Remove unreachable code

Codecov Report

Merging #40 (d0e5615) into master (ca539cf) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #40      +/-   ##
==========================================
+ Coverage   32.10%   32.11%   +0.01%
==========================================
  Files          67       67
  Lines        4177     4175       -2
==========================================
  Hits         1341     1341
+ Misses       2836     2834       -2

Impacted Files
Coverage Δ

lona/app.py
29.41% <ø> (+0.67%)
:arrow_up:

Continue to review full report at Codecov.

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

Great! Thanks! :)


release: v1.1.0

Description:
Commit Message
release: v1.1.0

see the guidelines for commit messages.
Changelog Entry
version: <log entry>

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have documented my code in accordance with the documentation guidelines
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have run the unit tests
[ ] I only have one commit (if not, squash them into one commit).
[ ] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Temporary patch for version 1.0.0 . Not required anymore.


[Environment] Melitngpot

Depends on https://github.com/pytorch/rl/pull/2054
Figuring out: https://github.com/pytorch/rl/issues/2065
cc @ezhang7423

Will test on my end and report back!


refac: made it to a real jquery plugin

some small changes, to make it to a real jquery plugin

@JohnnyTheTank thanks a lot for contributing. Actually I already had many changes during your PR so it would be a little harder to merge your code. For now I just took your ideas and reimplemented them on my own, so this should be pretty much the same as your recommended.
Really bad that I used the param.x = params.x ? params.x : null; instead of params.x = params.x || null.
Usually I'm the one who tells people to not code that way :angry: :angry: but thanks for your input. :angel:
I didn't put your change in place with the global variable. Currently I want to keep it because only that way the user can decide to call the gallery without having his code inside of the document on load or having it inside that function wich might be a better experience for people using the gallery the first time and don't get stock with such bugs. I'll try to figure out a better solution later but for now I want to keep it.
I still have many things I want to change in the code structure, but for now everything is working and I had no performance issues wich was my goal.

well, I'm fine :+1:
thanks for your detailed answer


Multiple ghost instances interfere with each other's authentication (v0.7.4)

My company runs two separate instances of ghost, served under the same domain by nginx. After upgrading to v0.7.4 from v0.6, we noticed a strange behavior where if you open both blogs, each in a separate tab but in the same browser, it's impossible to log in to both. You stay logged in for a second, but then get immediately logged out.
After taking a look, we were able to find that ghost remembers authentication by adding an entry into local storage. In v0.6, the key of this entry includes the url ghost is served at, for example:

Url of instance
Local storage key

www.spanishdict.com/blog
ghost-blog

www.spanishdict.com/blog/traductor
ghost-blog-traductor

However, in v0.7, this key becomes just ghost. The effect is that if both blogs are open at once, they override each other's auth entry, having the effect of always giving that entry the default value {"authenticated":{}}.
If it's helpful in figuring out how to fix/recreate this, I can provide access to our test environment with v0.7.4 deployed.
Thanks for maintaining this project!
cc/ @carsonbanov @sandinmyjoints

Hola Juan,
thanks for the detailed bug report. I'll take a look at fixing this.

Awesome, gracias @halfdan!

This is a regression, introduced in https://github.com/TryGhost/Ghost/commit/87e54c0d54696af6361b8704de1049298f2ff935#diff-647be943e1d5223ba4d913e869b2ef12L14


Store used URL to verify objects

OFLauncher-rei supports specifying a server to download the files from, which can have different revisions than the official toast.openfortress.fun.
If a user, for whatever reason, decides to change the URL after installing this can lead to files being left in the incorrect state.
To fix this I propose adding a .remote (or similar #18) that lets the program verify what remote was used last and if we need to verify the files from the first revision onwards

This doesn't solve the problem. All it would do is basically just replay from revision zero, which in turn is effectively a reinstall with checks for the current overlapping files. I think a better solution is to include a unique name for the thing that is installed. This would prevent disasterous situations, but also gives us an opportunity to warn the user. Think something like a file called .product with the contents "openfortress/openfortress",

This doesn't solve the problem. All it would do is basically just replay from revision zero, which in turn is effectively a reinstall with checks for the current overlapping files.

That is the point.
There is no simple way, without storing things client side, of ensuring that the new server and old server provide the same info without sending a bunch of queries to both.
With the current architecture its easier to simply fetch all file changes from 0 to LATEST and verify if they are locally present.

I think a better solution is to include a unique name for the thing that is installed. This would prevent disasterous situations, but also gives us an opportunity to warn the user. Think something like a file called .product with the contents "openfortress/openfortress",

a simple name would hold no authority over the state of the revisions, any repo could copy an existing product name while being incompatible.
One way to establish authority would be having each revision contain a hash of all files combined together from rev 0 to the CURRENT REVISON, allowing a client to verify that the revision we are on is indeed the same one as on the server without having to do a bunch of checking.
But since the current data the revision endpoint returns is an array of file metadata, we can't simply add this kind of revision information without breaking backwards compatibility, thus the only kind of authority we can derive, without being backwards incompatible and while holding as much authority as we can, is by checking if we changed servers or not

There is no simple way, without storing things client side, of ensuring that the new server and old server provide the same info without sending a bunch of queries to both.
a simple name would hold no authority over the state of the revisions, any repo could copy an existing product name while being incompatible.

TVN was designed to work with a trusted host. This is why we use MD5, it's only for incidential damage. What I'm proposing is also for incidential damage. It's meant for users accidentially choosing some other game.

There is no simple way, without storing things client side, of ensuring that the new server and old server provide the same info without sending a bunch of queries to both.
a simple name would hold no authority over the state of the revisions, any repo could copy an existing product name while being incompatible.

TVN was designed to work with a trusted host. This is why we use MD5, it's only for incidential damage. What I'm proposing is also for incidential damage. It's meant for users accidentially choosing some other game.

How can you trust that the server that says its openfortress is truly openfortress?
That is why I suggest using the host, or rather just the full domain + path so that changes between http and https won't break things since that is the authorative name that we use to connect to what we presume to be a known good server in regards to our local state.

How can you trust that the server that says its openfortress is truly openfortress?
HTTPS.

How can you trust that the server that says its openfortress is truly openfortress?

HTTPS.

that is not an answer
HTTPS ensures that the traffic is secure, not that tis server is in the same state as another.
toast.openfortress.fun can say its openfortress, but so can mirror.blab.ru

As I've mentioned TVS was designed such that you are supposed to be able to trust the server you're downloading from. If there's nothing else to add I'll be closing this issue.

As I've mentioned TVS was designed such that you are supposed to be able to trust the server you're downloading from. If there's nothing else to add I'll be closing this issue. If we need to change our threat model that's for another issue.

Yes and that is fine
but one thing you really should not trust a server on is if it matches another servers revision state.
Lets give an example for this:
of-fix.mirror.ex points to a custom tvn repo with a modified client libary that adds some nice features a few people had asked for otherwise its 1:1 the same as toast.openfortress.fun.
If a user went and changed the URL in oflauncher-rei it would check if .revisions is lower and if so update to that newest version.
Otherwise it goes and does nothing.
Now, if the user does while they are on the latest version they do not receive the changed files and are required to manually intervene by deleting .revision and thus forcing the launcher to recheck every file.

The user and client trust both servers just fine but there is no way of migrating to a new server without having to manually intervene


Clarify MSRV policy

Latest 0.4.1 release broke support for older Rust versions compared to 0.4.0, for example, accessing enum variants via Self were not available for Rust 1.36.0:
https://github.com/KokaKiwi/rust-hex/blob/78359a859c356a6c756cccad16977fdedc4824c5/src/error.rs#L26-L30
In my case this version of hex were used as a dependency in the Cargo.toml,
[dependencies]
hex = "0.4.0"

and after the new release, cargo automatically started using 0.4.1 as they are assumed to be compatible.
Generally it seems unexpected to update MSRV (Minimal Supported Rust Version) in the patch versions, so it would be nice to clarify your policy on the compiler versions support.
Usual options are either to test specific Rust version in the CI workflow or to put a note in the README file that this project is compatible only with the latest stable Rust version.
EDIT: this discussion might be interesting too.

Oh shoot indeed, i should've been more careful releasing the 0.4.1 as i didn't think about the used Rust's version (only thought about the API stability as per semver requirements, which is okay but not always enough indeed) :x
As the breaking stuff seems to be easily fixable, i think i'll release a non-breaking corrective version (0.4.2) and yank the 0.4.1 version (to avoid other broken stuff), and stating in the README.md a MSRV for at least an old enough Rust version (maybe 1.36.0 actually) as this lib should be mostly simple and thus wouldn't require an "edging" Rust version
Along this statement i'll add the MSRV to the Rust's version matrix in the CI so it'd be checked from now on to avoid any future breaking version like this...
PS: also if it's okay for you, i'll gladly do with some feedback about this plan of doing as i never dealt with yank[ed/ing] stuff before, so any tip or comment on this would be greatly valuable for me ^-^

Yeah, unfortunately there is no builtin way to force MSRV right now (yet), so at least you can utilize matrix builds to check both for stable and some MSRV version.
Also I'm in no position to ask about some specific Rust version, but considering the amount of the dependant crates and repositories, there is be a chance that sticking with Rust 1.36 will break compatibility to someone.
Naive and dirty way to determine the minimal version would be a bunch of rustup target install {version} && cargo +{version} build commands issued on 0.4.0 tag and going back to some extremely old Rust version, and I fail to find better option for now :(
Crates yanking is pretty easy, the following command should do the thing:
cargo yank --vers 0.4.1 hex

Note that yank subcommand also has the --undo flag, so in case of any typos it will be easy to rollback it back to the "un-yanked" state.

I just wanted to follow up on this issue. I checked your package using this library https://github.com/foresterre/cargo-msrv
Here are the results for your package. To get each result, I ran git checkout <tag>, and then cargo msrv --bisect

For Hex v0.4.3, the msrv is 1.46.0
For Hex v0.4.2, the msrv is 1.31.1
For Hex v0.4.1, the msrv is 1.37.0
For Hex v0.4.0, the msrv is 1.31.1
For Hex v0.3.2 and all lower, the msrv is 1.17.0


Bump all deps to 0.4

Bumped from -alpha.
Needed this because I was getting weird errors like "Bls12_381 doesn't impl PairingEngine". This was because my Bls12_381 was 0.4 and the groth16 PairingEngine was 0.3.

Thanks!


[SPARK-46473][SQL] Reuse getPartitionedFile method

What changes were proposed in this pull request?
Reuse getPartitionedFile method to reduce redundant code.
Why are the changes needed?
Reduce redundant code.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No

Looks OK, but re-run tests

The tests passed, please review it, thank you @srowen

Merged to master


Question: Pkg for implementing 'osm namespace add' in golang

Hi! I am currently working on a project that uses the OSM's TrafficSplit capabilities. I am wondering if it is possible for me to implement osm namespace add <namespace> in a golang file, instead of using the cli (Main goal is to achieve everything without installing cli)? I have looked into OSM's packages and I was unable to find a function/package that achieves this.

Hey @ruokun-niu, osm namespace add adds the openservicemesh.io/monitored-by=<mesh-name> label and the openservicemesh.io/sidecar-injection=enabled annotation on the namespace, by default. It provides flags that override the default behavior.
Depending on your use case, you could simply do the same in your Go code using k8s API. Since most of the CLI code is defined under cmd/cli, to make this exportable, you could also consider moving the relevant code to pkg/cli.


Backport #6075 to 2.2 - NullReferenceException in IISHttpContext

We've had some requests to backport the fix for https://github.com/aspnet/AspNetCore/issues/6075 to 2.2.x. This issue is tracking a possible backport (will need to be approved by shiproom).

Closing this because we think there are a few more cases. We want to solve this in 3.0 before backporting. Filed https://github.com/aspnet/AspNetCore/issues/9873.

@anurse : Any idea when a fix will be available for 2.2 ?
Can we check link these issues to a realease notes site ?

No word yet, but we'll be doing some looking at it soon. I'll re-open this to track that :).

Putting this in a 3.0 milestone to keep it on our radar. Right now we have some higher priority 3.0 work to get this in. Also, this is fixed in the coming 3.0 release (in September) and 2.2 goes end-of-life in December, so we'll be using that to evaluate the prioritization here.

Given that the fix is coming in 3.0 which ships in September and the next 2.2 patch is targeting September, backporting doesn't feel valuable here. Plus, 2.2 will be end-of-life in December of this year.


Google Maps 3.32+ won't render

Describe the issue / bug.
#
Google retired the 3.31 version of Google Maps today and I have been unable to get 3.32, 3.33, or 3.34 to display in my application. I spent about eight hours on this today trying to fix it and researching, but no one else seems to have this particular problem. I was able to determine that it relates to webpack and this template's configuration, somehow.
The mapping script is retrieved successfully (I have tried with numerous methods and they all have the same outcome). You can see that the Google Maps canvas is there, with the hand cursor as well, but no map images are loaded.
Side note: In my main project (not the one above), I am able to get the map to display if the corresponding div is smaller than 800x480, which I find really bizarre.
How can I reproduce this problem?
#
I was able to replicate the problem with a fresh electron-vue project and replacing the LandingView page with a page displaying a map.
It's at https://github.com/zxc23/electron-vue-google-maps-problem
Happens in both dev and prod. In MapPage.vue, you can put a Google Maps API key, but even if you leave it blank it would display a map in the background if it were working correctly.
If visual, provide a screenshot.
#
https://i.imgur.com/8o4BlhI.png
Tell me about your development environment.

Node version: ~8.9.1
NPM version: ~6.1.0
Operating System: Windows 10 x64

Happens on both my PCs.

Managed to fix this replication by adding the initial center coordinate to the map initialisation:
let map = new google.maps.Map(document.getElementById('map'), { center: {lat: -34.397, lng: 150.644}, zoom: 11 })
However, the problem still persists in my main app. I may be getting close to the heart of the issue.

OK, after another several hours, I've fixed this.
Process was to first update packages in package.json to match those of the current template. Then I updated some other bits and pieces of the webpack config. Finally, I deleted the node_modules folder and ran npm install again.


Use "modern client" and add path to "router base", and use nuxt generate, the JS can't be loaded.

Version
v2.4.5
Reproduction link
Github
GH page
Steps to reproduce
git clone git@github.com:ycs77/nuxt-test-gen.git
cd nuxt-test-gen
yarn install
yarn generate

Use server start site in the "dist" directory
Open browser DevTools > Network
You can look the JS is not loaded

What is expected ?
The site JS loaded successfully.
What is actually happening?
nuxt.config.js
module.exports = {
  modern: 'client',
  router: {
    base: process.env.DEPLOY_ENV === 'gh_pages' ? '/nuxt-test-gen/' : ''
  },
  ...
}

If use one of a "modern client" or "router base", nothing will happen.
But if you use it as above, the site JS will not loaded.

This bug report is available on Nuxt community (#c8801)

@ycs77 Thanks for reporting this bug.
This issue should be fixed in #5202 , but one thing need to be noticed is:
router.base needs to be same value between generate and start, so please add cross-env DEPLOY_ENV=gh_pages  in start and then access http://localhost:3000/nuxt-test-gen/

Thank you for your reminder


Move Scalars to Hotchocolate Types namespace

Move scalars from Hotchocolate.Types.Scalars to Hotchocolate.Types
Addresses #3317

/AzurePipelines run


First login error

Bug description
Fresh install the version <IP_ADDRESS> and use wsl -d NixOS. The log should show it.
To Reproduce
Please see logs
Expected behavior

Logs
PS G:\nixos-wsl\23.05> wsl --import NixOS .\NixOS\ nixos-wsl.tar.gz --version 2
Import in progress, this may take a few minutes.
操作順利完成。
PS G:\nixos-wsl\23.05> wsl -d NixOS
<3>WSL (74) ERROR: CreateProcessEntryCommon:577: execvpe /run/current-system/sw/bin/bash failed 2
<3>WSL (74) ERROR: CreateProcessEntryCommon:586: Create process not expected to return

What does wsl.exe --version show for you?

WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.3448
nzbr @.***> 於 2023年10月7日 週六 上午4:58寫道：

What does wsl.exe --version show for you?
—
Reply to this email directly, view it on GitHub
https://github.com/nix-community/NixOS-WSL/issues/305#issuecomment-1751395833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANDZ3AJZ5M4KZNDVBQORYZ3X6BWGRAVCNFSM6AAAAAA5UGMTDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGM4TKOBTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

The latest WSL version is <IP_ADDRESS>. Try installing the update through the Microsoft Store and see if that fixes it

I installed again and the version is same

I can't see a version number in the screenshots and I don't think any of us knows that asian language.

Sorry the store can't change the language. My WSL version is <IP_ADDRESS>, and the store doesn't have any upgrade.

Sorry the store can't change the language. My WSL version is <IP_ADDRESS>, and the store doesn't have any upgrade.

There is an official guide by Microsoft on how to upgrade from WSL 1  to WSL 2.
https://learn.microsoft.com/en-us/windows/wsl/install#:~:text=Upgrade version from WSL 1 to WSL 2

@KSaiAkshit The guide is about upgrading from WSL 1 (emulated kernel, basically reverse-WINE) to WSL 2 (actual Hyper-V VM). That has, however, nothing to do with the version number from wsl --version.
I really don't know who at Microsoft thought it was a good idea to start numbering WSL 2 releases at 0... and later 1..., but I absolutely see how this is confusing

Ahh, my bad my bad. Yeah just realized, it is quite confusing,

The 2.0.4 release (now 2.0.6) is a pre-release. The advice on the README and here about wsl from the store seems to be outdated. 1.2.5 is the latest official release, and the only one you can get from the store. To upgrade to the latest in pre-release, run this on cli (pwsh or cmd):
wsl --update --pre-release

I guess I had a similar problem. This is a (recording screen](https://drive.google.com/file/d/17xiO3NyRQPbo_nWQwU36zgGt85KwsBx9/view?usp=drive_link).
Basically, I can't open the system via wsl -d after successfully installing NixOS-WSL, and I don't see any error messages

I have use store to update the version of wsl, and also try for wsl update, but seems --pre-release not work for me
I have try multiable verison of tarball, two of the latest release and a nixos tarball export from the system before reinstall (same computer)
My default wsl version is 2

@jackyliu16
What does wsl --version report for you?
Have you tried the whole process in a non-admin console? (Not sure if that changes anything, but it might be worth a shot)
If that doesn't help, please use the working debian install to get the output of sudo dmesg after you try starting NixOS

This is because of native systemd.
Change in /etc/nixos/configuration.nix:
From:
wsl.nativeSystemd = true;
To:
wsl.nativeSystemd = false;
Please let me know if this fixes the issue

I was in mind I did already report this bug and told the workaround here, but searching through the issues I didn't find it

This is very likely because of native systemd (Was my issue).
Change in /etc/nixos/configuration.nix:
From:
wsl.nativeSystemd = true;
To:
wsl.nativeSystemd = false;
Please let me know if this fixes the issue

@KSaiAkshit @jackyliu16

@KSaiAkshit @jackyliu16 @aikooo7
Please keep in mind, that syschdemd is no longer supported and only left as an option for compatibiliy purposes. It will probably be removed entirely at some point in the future

@KSaiAkshit @jackyliu16 @aikooo7
Please keep in mind, that syschdemd is no longer supported and only left as an option for compatibiliy purposes. It will probably be removed entirely at some point in the future

Thanks for the heads up, still is a good workaround until we can find why this happens.

Closing since WSL 1 support is only left for backwards compatibility and if problems can be fixed by upgrading to 2.0, then that is the solution.


make 'main' the default (protected) branch?

these days you don't need to maintain a gh-pages branch in order to wire up GitHub Pages.
if @springmeyer feels like giving me admin keys to this repo i'd be interested in making main the default branch and setting up branch protection rules to disable -f pushing, etc.

Happy to give you admin access. But it appears that, given this repo is in my personal account (rather than an org), I'm not able to give you admin.

So perhaps share the steps you'd recommend and I can run it out?

this repo is in my personal account (rather than an org)

i forgot about that little snag 😄
Settings > Branches

the ✏ lets you rename the default branch
Add Rule lets you define what is allowed for main or any other branch.

there are lots of options to enforce security. at a minimum i find it helpful to disable force pushing and ensure that the commit history for the repo can't be overwritten.

Settings > Pages
I think this one will update automatically when you rename the default branch, but it'd be worthwhile to doublecheck.

thanks for humoring me. none of this is mission critical.

Thanks, all done!


{BOT} Feature

Thanks for the contribution @wangzelin007!

Me too

Auto reply to avoid issue/pr response SLA.
Auto assign milestone based on issue/PR creation date.
-- If the pr creation time is less than 7 days, put into the next milestone and notify the user.
-- If the pr creation time is more than 7 days, put into the current milestone.
-- If the issue creation time is less than 21 days, put into the next milestone and notify the user.
-- If the issue creation time is more than 21 days, put into the current milestone.

TODO: The default comment was replaced by bot comment.

Auto reply to avoid issue/pr response SLA.
Auto assign milestone based on issue/PR creation date.
-- If the pr creation time is less than 7 days, put into the next milestone and notify the user.
-- If the pr creation time is more than 7 days, put into the current milestone.
-- If the issue creation time is less than 21 days, put into the next milestone and notify the user.
-- If the issue creation time is more than 21 days, put into the current milestone.


Fix wring usage of podman instead of docker, fix jdb usage

Some tweaks. Tests should be  more reliable now (e.g., running them after previously failed run, they will clean the hanging containers at first, and the jdb part now works properly).

Can one of the admins verify this patch? If it is not dangerous to our systems, juts tell me to "run_tests".  ( without the underscore and quotes :smiley: )


Regression in a nested query

Given the following document:
[
  {
    "name": "a",
    "groups": [{
      "type": "phase",
      "name": "alpha"
    }, {
      "type": "not_phase",
      "name": "beta"
    }]
  }, {
    "name": "b",
    "groups": [{
      "type": "phase",
      "name": "beta"
    }, {
      "type": "not_phase",
      "name": "alpha"
    }]
  }
]

and the following JSON path query:
$[<EMAIL_ADDRESS>== 'phase' && @.name == 'alpha')] empty false)]

0.22 and 0.23 yield different results:
// 0.22 (selects 'a'):
[
  {
    "name": "a",
    "groups": [{
      "type": "phase",
      "name": "alpha"
    }, {
      "type": "not_phase",
      "name": "beta"
    }]
  }
]
// 0.23 (selects none):
[]

I can't reproduce the issue. I get the same result with 2.2.0 and 2.3.0. Can you share some more details?

That's weird. Let me dig further and get back to you.

Could you try this?

It seems to be related to the Jackson backend:
 String json = "[" + "  {" + "    \"name\": \"a\"," + "    \"groups\": [{" + "      \"type\": \"phase\","
        + "      \"name\": \"alpha\"" + "    }, {" + "      \"type\": \"not_phase\"," + "      \"name\": \"beta\""
        + "    }]" + "  }, {" + "    \"name\": \"b\"," + "    \"groups\": [{" + "      \"type\": \"phase\","
        + "      \"name\": \"beta\"" + "    }, {" + "      \"type\": \"not_phase\"," + "      \"name\": \"alpha\""
        + "    }]" + "  }" + "]";

    // Should not print '[]'
    System.err.println(JsonPath.parse(json)
        .read(JsonPath.compile("$[<EMAIL_ADDRESS>== 'phase' && @.name == 'alpha')] empty false)]")));

yields the same result with 2.2.0 and 2.3.0.

6cf30fd1a0be42aa0e8385b1ff8ca99e7fbd74be broke it

Thanks a lot for a super quick fix! Any chance of cutting a new release?


device_tracker.bluetooth_le_tracker not working with HASS.IO since introduction...?

The ble tracker was introduced in about version 5.? but I haven't been able to get it working at all.
My logs look like this:
2017-10-27 22:59:01 ERROR (SyncWorker_11) [homeassistant.util.package] Unable to install package gattlib==0.20150805: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-2hdf7tbx/gattlib/
2017-10-27 22:59:01 ERROR (MainThread) [homeassistant.setup] Not initializing device_tracker.bluetooth_le_tracker because could not install dependency gattlib==0.20150805
2017-10-27 22:59:01 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform device_tracker.bluetooth_le_tracker: Could not install all requirements.

I have tried with a fresh hass.io install about 2 weeks ago but I still get the same errors in the logs.
I have Bluetooth BCM43xx (version 0.7) installed and it shows the following in the logs:
starting version 3.2.1
bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set Controller UART speed to 115200 bit/s
Device setup complete

I have tried it with & without this add-on. I am running on a Raspberry Pi 3.
Others are also reporting the same problem here:
https://community.home-assistant.io/t/hassio-list-bluetooth-le-devices/22798/17

You need add https://github.com/home-assistant/hassio-build/blob/master/homeassistant/generic/Dockerfile
But there no one was able to make it working. But if you have hardware for test it, feel free to make it working and make a PR 👍

is pip install gattlib even working? This might be an upstream issue.
the compilation of gattlib throws an error when I try to install it on my laptop using python 3.6 and gcc 7.2

Do we miss any dependencies for gattlib?

No but that person they have test it, was the meaning, that he don't work. Maybe while Alpine not run on glibc and need musl.

https://github.com/home-assistant/home-assistant/issues/9048

It didn't work for him because he wasn't able to install gatttool which we have fixed now. Mi Flora now works, but the Bluetooth LE Tracker component needs gattlib which the guy succesfully installed.

If you want you can give a try

Yeah, I'll give it a try, I'm just not sure how to test if it's working in the end

Just an update after updating to 0.57.2 - still got the same problem. Log files says:
2017-11-07 19:48:12 ERROR (SyncWorker_5) [homeassistant.util.package] Unable to install package gattlib==0.20150805: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-jcs9g68n/gattlib/
2017-11-07 19:48:12 ERROR (MainThread) [homeassistant.setup] Not initializing device_tracker.bluetooth_le_tracker because could not install dependency gattlib==0.20150805
2017-11-07 19:48:12 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform device_tracker.bluetooth_le_tracker: Could not install all requirements.

I haven't had time to implement this

any news on this?

sorry, but I need to finish my PHD thesis, therefore I lack time. Maybe someone else can jump in on this.

I see, that is a pity.
So, for my understanding, in principle, the fix implemented in Mi Flora platform could also be implemented to the tracker platform?
Would not be better be implemented it in hassio it self to make the fix available to any other platform suffering the same problem? (probably my understanding of the different "levels" between hassio and the platforms is not the best) Just asking :)

There is no fix for Mi Flora anymore, the component was completely rewritten so the answer to your first question is no.

It's would be fixable, you need only build the python module with correct library. It is not very difficult (Need only a bit knowledge about musl and glibc envs) but I have no time and to many task for do it self.

 Would so love this to work so I could use my beacons for something.

since this seems to be a big issue I am thinking about taking a different route, just FYI @braddo99 https://github.com/mertenats/Open-Home-Automation/tree/master/ha_mqtt_binary_sensor_ble_scanner

so just looking at this and it looks like firstly boost is needed but as per this thread:
https://bitbucket.org/OscarAcena/pygattlib/issues/41/ld-cannot-find-lboost_python-py34
lboost_python-py35 is there but the system looks for 34 - will report back

Any progress?

Any progress on this issue?

Have same problem.
Hostname	hassio
System	Resin OS 2.3.0+rev1
Hass.io supervisor
Version	103.3

Any up?

@ahmadalsaady When I see that error try:
sudo hciconfig hci0 reset    ... or whatever your device may be. I have never figured out why the device becomes unavailable to HA periodically but I did have two bluetooth devices, in built and dongle and when I took the dongle out, the issue presented much less frequently. Works pretty well for me now for BLE, still don't see bluetooth (nonLE) devices though.


Add condition to check if ruby version is < 2.7

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Fixes #6952

Thanks so much for your contribution!  You rock, @emreerhan!

Thank you for your first contribution to Homebrew/brew, Emre! 🥇


Listener "onSpotlightSequenceEnd"

Is there any way to know (or trigger some codes) when a spotlight sequence ends?

@saqibsoftwares , Added a sequence end listener. You'll get it in next update.

Still this method is not available

When the update be available? I'm waiting for this.

I'm also waiting for this, I've just asked another question on the top related to this, did a search and afterwards here I am, when can we expect a listener?


feat: Yarn version update

Feature Suggestion
I suggest updating version of the Yarn package installed in the project to the latest version. Last update was made 7 months ago. Outdated version of Yarn cause warning in console. Fix is simple and I believe new minor versions of yarn would not break anything so it should be not that hard to implement.

Possible Implementation
Updating yarn version inside project is quite easy. Simple command will do the job:
yarn set version latest
Then two files will be generated:

.yarnrc
yarn-1.22.5.js

that should be committed into repository.

Context
While we use yarn commands on console we got warning like this one:

so upgrading yarn version would remove this warning.

We've avoided bumping the yarn version to not grow the repo size too much. There haven't (last time I checked) been any worthwhile updates, and the size on disk is ~6MB. A specific fix we've been waiting for is for yarn postpack scripts to be called, but afaik that's not released yet.
I don't think there's any compelling reason to upgrade to v1.22.5, no security fixes, and yarn pack fix in .5 shouldn't affect us much either. Would be nice to disable the warning though 😅


Last version not compatible con xcode 6.0.1 (6A317)

Hello, I compile the last versión of the repository, without any errors, it appears in may plugin directory correctly,  but I can't run code pilot, it not appears in my xcode menu. Any suggestion? Exist a new version of the code?

New XCode versions support has been added recently. Closing this issue.


No f08 tool

This issue was originally created at: 2015-01-06 09:57:03.
This issue was reported by: russel.
russel said at 2015-01-06 09:57:03

There is no f08 tool to match all the tools associated with other Fortran (and
FORTRAN :-) standards.

There's an SCons/Tool/f08py and matching SCons/Tool/f08.xml - is this actually an active issue?

Closing.
Reopen if still an issue.


Added missing mocha dep

Missing dependency used by the custom reporter

I'll close this one and put both together


Rate limited

Anyone else getting rate limited error after playing a few tracks? I think it was working before... I have tried experimenting with sendTrackEvent and sendTrackProgress with no success.

Pledged 5$ on bountysource since I still experience problems.
{ [TrackError: Network error]
domain: 12,
code: 0,
description: '',
data: null,
name: 'TrackError',
message: 'Network error' }


Layer upload (GeoTIFF and zipped SHP)

This suggest to add a button to upload a local dataset (GeoTIFF or zipped shapfile) to the GeoServer and creating a new coverage/feature type based on it.
https://user-images.githubusercontent.com/9415123/200905043-9f2d60ab-637e-4c77-9510-a8e7e8df5ac4.mp4
Please review @terrestris/devs.

Thanks for the review!


[Frontend][PaddlePaddle] Add topk op and Fix bug, when the output is a dimension, it …

There are some operation in PaddlePaddle that output a tensor which shape is [1], meanwhile, the slice op have decrease_axis attr, but it should not be squeezed.
@heliqi
@jiangjiajun
cc @junrushao

Would you like to fix the CI so we could get it in?

Would you like to fix the CI so we could get it in?

I think

h

Would you like to fix the CI so we could get it in?
E       File "/workspace/tests/python/frontend/paddlepaddle/test_forward.py", line 1356, in slice5 (* user code *) [2023-01-05T11:12:37.644Z] E   	b, c, h, w = paddle.shape(inputs)  # add decrease_axis
I think this error may be related to the version of the paddlepaddle

Would you like to fix the CI so we could get it in?
E       File "/workspace/tests/python/frontend/paddlepaddle/test_forward.py", line 1356, in slice5 (* user code *) [2023-01-05T11:12:37.644Z] E   	b, c, h, w = paddle.shape(inputs)  # add decrease_axis
I think this error may be related to the version of the paddlepaddle

The paddlepaddle version we matched before was 2.1.3.
If you want to upgrade and match the latest paddlepaddle version, you can pull request and modify the Paddle version in the code  and the code.

Would you like to fix the CI so we could get it in?
E       File "/workspace/tests/python/frontend/paddlepaddle/test_forward.py", line 1356, in slice5 (* user code *) [2023-01-05T11:12:37.644Z] E   	b, c, h, w = paddle.shape(inputs)  # add decrease_axis
I think this error may be related to the version of the paddlepaddle
@woobinw
The paddlepaddle version we matched before was 2.1.3.
If you want to upgrade and match the latest paddlepaddle version 2.4, you can pull request and modify the Paddle version in the code  and the code.

`[2023-01-09T07:38:22.462Z] tests/python/frontend/paddlepaddle/test_forward.py:81: in verify_model
[2023-01-09T07:38:22.462Z]     baseline_outputs = baseline_model(*[input[:] for input in input_data])
[2023-01-09T07:38:22.462Z] /venv/apache-tvm-py3.7/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py:902: in call
[2023-01-09T07:38:22.462Z]     outputs = self.forward(*inputs, **kwargs)
[2023-01-09T07:38:22.462Z] /venv/apache-tvm-py3.7/lib/python3.7/site-packages/paddle/fluid/dygraph/io.py:1191: in i_m_p_l
[2023-01-09T07:38:22.462Z]     return _run_dygraph(self, input, program_holder)
[2023-01-09T07:38:22.462Z] /venv/apache-tvm-py3.7/lib/python3.7/site-packages/paddle/fluid/dygraph/io.py:754: in _run_dygraph`

@junrushao
The ethosu test seems to have nothing to do with PaddlePaddle frontend.

Thank you for pinging me @woobinw! Indeed the failure is not relevant to the change you brought in, and I'm not sure if it's flaky or consistently reproducible error. Retriggered the test just now, and let's see if it could work this timw

@tvm-bot rerun

Could you rebase to latest HEAD? I’m sure it’s going to pass this time

Could you rebase to latest HEAD? I’m sure it’s going to pass this time

Yes, It has been rebased to latest HEAD.

Thanks for the contribution! It’s merged!


Update go1.4 to build machine

maybe it's time to using go1.4

@s7v7nislands - this is a duplicate of #1264

Closing due to duplication.


feat(Workspaces) : create database workspace

Create a database, role when creating a workspace. The created database and role use the workspace slug name as identifier.
The created role has CONNECT and CREATE privileges granted on the created database.
Changes

Add create_database function in api.py on database module
Add create_database api on workspace model
Replace and use the workspace slug name when querying for workspace database objects

How/what to test
1 - Configure env variables that hold the pg_server credentials
2 - Call the create workspace mutation
3 - Check that a database and a role with the workspace slug name are created

Nice work +1 I will try to test it asap.
Could you already try to "disconnect" workspace databases from the Postgres connector? It is not necessary to use the Database model anymore.

Okay, on it.

@pvanliefland If we remove the Database model, do we need to generate a password with the created role ? For now the created role cannot connect without a password.

@pvanliefland If we remove the Database model, do we need to generate a password with the created role ? For now the created role cannot connect without a password.

Yes, you need to generate a password and store it on the workspace model using an EncryptedTextField field.

@qgerome should be good now


Inconsistency in the structure of param_dict

The param_dict argument of TemplateModel.set_parameters(...) has type dict[str, float] while params_dict of mira.modeling.amr.ops.add_transition(...) has type dict[str, dict[str, Any]].
It's just a minor mismatch in interface that tripped me up.

I see, those are different by design but I suppose it could be changed. The thinking is as follows:

for set_parameters, you just provide the value for each input parameter
for add_transition you have the option to provide an entirely new parameter definition if it appears in the new transition

Do you think set_parameters should allow creating new parameters rather than just allow updating parameter values?

In this case, I needed to add 6 new parameters and assign values to them. If set_parameters allows creating new parameters, then I could avoid making 6 add_parameter and 1 set_parameters calls. So yes please!


Top background colour should merge with header

So that when the page is dragged down, the blue does not show through

Closed in #80


Add Hashable concept

In alignment with existing concepts, such as Serializable, Printable, Parseable, we should port the crude util::hash functionality into a concept: Hashable. The implementation should follow syntax and semantics of N3980 (Types Don't Know #).

Available as of e3fdff7a2ff6894964fb02feeec9e7a758caf0b1.


add Locked trait

Adds a new trait to moments called Locked, which is an important field that platforms need to use to filter out moments that can't be used in listings/can't be sent anywhere
I ran the following for tests but I'm not sure if this is sufficient so please let me know if there's anything else I need to do
# from repo root
cd lib/go/contracts
make generate
make test

➜  contracts git:(is-locked-trait) ✗ make test
go test ./...
ok  	github.com/dapperlabs/nba-smart-contracts/lib/go/contracts	0.122s
?   	github.com/dapperlabs/nba-smart-contracts/lib/go/contracts/internal/assets	[no test files]

Hello, thanks for contributing!
There are tests in the root directory of the project which can be executed by running make test (They were broken, I just fixed them here https://github.com/dapperlabs/nba-smart-contracts/commit/9dd6390c3496ff4da08a84a01798c4e8082146d3)
Let me know when you've had a chance to update your branch and verify the tests and I will be happy to get this deployed for you.

Hello, thanks for contributing!
There are tests in the root directory of the project which can be executed by running make test (They were broken, I just fixed them here 9dd6390)
Let me know when you've had a chance to update your branch and verify the tests and I will be happy to get this deployed for you.

Thanks for taking a look! I've gone ahead and verified tests pass (had to do two small updates to get them working), and I also had to commit a change to assets.go which seemed pretty similar to the flow-nft repo. If anything else is needed give me a shout!
Here's the output from running make ci
➜  nba-smart-contracts git:(is-locked-trait) go clean -testcache
➜  nba-smart-contracts git:(is-locked-trait) make ci
/Applications/Xcode.app/Contents/Developer/usr/bin/make ci -C lib/go
/Applications/Xcode.app/Contents/Developer/usr/bin/make ci -C contracts
go generate
go mod tidy
git diff --exit-code
go test ./...
ok  	github.com/dapperlabs/nba-smart-contracts/lib/go/contracts	0.117s
?   	github.com/dapperlabs/nba-smart-contracts/lib/go/contracts/internal/assets	[no test files]
/Applications/Xcode.app/Contents/Developer/usr/bin/make ci -C templates
go generate
go mod tidy
git diff --exit-code
go test ./...
?   	github.com/dapperlabs/nba-smart-contracts/lib/go/templates	[no test files]
?   	github.com/dapperlabs/nba-smart-contracts/lib/go/templates/data	[no test files]
?   	github.com/dapperlabs/nba-smart-contracts/lib/go/templates/internal/assets	[no test files]
/Applications/Xcode.app/Contents/Developer/usr/bin/make ci -C test
go generate
go mod tidy
git diff --exit-code
go test ./...
ok  	github.com/dapperlabs/nba-smart-contracts/lib/go/test	14.872s

hey @tpetrychyn checking in, any chance I can get some eyes on this this week?

@austinkline it appears the build step got stuck during the github webhook outage yesterday. Could you please send an empty commit to restart the PR checks?
gc --allow-empty -m "retry checks"

@austinkline it appears the build step got stuck during the github webhook outage yesterday. Could you please send an empty commit to restart the PR checks?
gc --allow-empty -m "retry checks"

Done!


feat (authz): [API] add canonical identity sample for Minimal Apis in ASP.NET Core 6

closes: #506092
WHY
we wanted to create our first canonical sample that protects a web API written in ASP.NET Core 6 with Minimal Api.
WHAT Changed?

create minimal web API
protect api using ASP.NET Core Identity
clean up scaffold sample just a bit more: removal of comments, files, etc.
add README (not deployable but necessary assets to make it work)

HOW to test?
follow the steps in the README.md

requested folder/files changes:
minimal-api-... -> protect-api
MinimalWebApi.csproj -> Api.csproj

requested folder/files changes:
minimal-api-... -> protect-api MinimalWebApi.csproj -> Api.csproj

done | addressed from 5931


Increase coverage for cutscene files

Description
Task: Increase coverage for cutscene files.
Feature: Create Cutscenes for each start of the day
The current coverage for the cutscene folder is 45%

This ticket aims to increase this score to about 80%.
Dependencies
N/A
Milestones
List of steps that need to be completed for this task.

[ ] Create Test for Day2Cutscene.java (Oct. 03)
[ ] Create Test for BackgroundRenderComponent.java (Oct. 03)
[ ] Create Test for CutsceneFactory.java (Oct. 03)

Completion Deadline: Oct. 03
Documentation

Sonar Cloud Stats

Member

Caleb Murphy (@Caleb-J-Murphy)

Not completed in the sprint. Will be done by another team.


feat!: rework IconButton

Description

closes https://github.com/traefik/faency/issues/347
closes https://github.com/traefik/faency/issues/174

Preview

https://user-images.githubusercontent.com/3367393/163997758-dacce9dc-6d51-4d07-8635-e28621cd2962.mp4
Breaking changes

IconButton api changed and UI changed
Good PR checkboxes

[x] Change has been tested
[ ] Added/Updated tests
[x] Added/Updated stories
[x] PR follows conventions
[x] Labels are set
[x] Project is linked

Good Review checkboxes

 ℹ  Copy the snippet and paste in the review field to fill it
- [ ] I've tested the changes
- [ ] I've agreed on the unit tests (soon to come)
- [ ] I've checked the stories
- [ ] I've read the code and understood it
- [ ] I don't have any more questions
- [ ] I've described any optional improvements
- [ ] I checked PR follows [conventions](https://github.com/traefik/faency#how-to-contribute)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Crash with the mt-multiserver-chatcommands plugin

Append then I run the send command with telnet.

Thanks! It works


[AVM Question/Feedback]: Add examples to the readme

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
I'd like to have examples for parameters and UDTs to the generated readme. The contribution guide already mentions this feature here, but the examples are not added to the readme.
Here are some examples on how I add examples:
@metadata({
  example: '''
  -<EMAIL_ADDRESS>  - ['john<EMAIL_ADDRESS>  '''
})
@description('Optional. The email recipient value to receive alerts.')
param additionalRecipients array = []

@metadata({
  example: '''
  {
      "key1": "value1",
      "key2": "value2"
  }
  '''
})
@description('Optional. Tags of the resource.')
param tags object?

type replicaSetType = {
  @description('Required. Virtual network location.')
  location: string

  @metadata({
    example: '/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/<resourceGroup>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/<subnetName>'
  })
  @description('Required. The id of the subnet that Domain Services will be deployed on. The subnet has some requirements, which are outlined in the [notes section](#Network-Security-Group-NSG-requirements-for-AADDS) of the documentation.')
  subnetId: string
}[]?

The challenge I see with this approach (as opposed to leverage the UDTs documentation itself and or the usage examples) is that this introduces untested code, that 'can' run stale. We used to actually have a lot of examples called 'Parameter Usage xzy' in CARML, but soon found out that 90% were outdated within a year without anybody noticing but users that encountered issues.
I'm not saying the idea is bad - it just comes at quite a cost that I'm not sure how to avoid.

I understand the challenges. This is a must have feature which distinguishes AVM from the usual MS docs and offers real benefits in adoption and usage.
Looking up what the parameter is expecting can be a frustrating and time-consuming task. I want to offer guidance to users.

@ReneHezser - I feel this is addressed with the max tests as we test the largest parameter set possible. Although we do not limit contributors and owners from adding this information to the main.bicep files, it would be at the contributors/owners discretion to enforce this for complex objects that cannot be tested within the max test. We do import the tests into the readme to give the users real world examples of the parameter structure.
Any additional items to this should be opened as a issue on the target module

@ChrisSidebotham, I think @ReneHezser is aware that the tests are imported. I've seen for several parameters, that metadata was added which is just not imported into the module readme at this point.
I guess it would make sense to bring this up in the team if we want to just support adding examples and relying on the module owners to maintain them at all times, are restrict examples to everything which is validated across a module's tests cases instead. What do you think?

@AlexanderSehr - Today we had a discussion about BCPNFR1 which I feel also addresses this. CARML Migrated moduleshad been exempt from the MUST use UDT's for complex objects and arrays until the Migration was complete. Now the expectation is that we will drive tis into the "migrated" modules. In which the usage becomes alot simpler with autocomplete functionality - lets mark this for discussion in the next team call

@AlexanderSehr - Today we had a discussion about BCPNFR1 which I feel also addresses this. CARML Migrated moduleshad been exempt from the MUST use UDT's for complex objects and arrays until the Migration was complete. Now the expectation is that we will drive tis into the "migrated" modules. In which the usage becomes alot simpler with autocomplete functionality - lets mark this for discussion in the next team call

UDTs would certainly help and cover most of the effort. But they're not 1:1 the same as an example. E.g. the UDT would say 'this property is a resource Id' in the property's name or description and if you know how a resourceId needs to look like great. If somebody does not, an example would maybe help.
I'd think that this is where this could/should land - on the UDT properties. This would make it also a whole lot easier to maintain as @ReneHezser in this case would not need to descripte the entire object in an example (which could run stale if the structure changes), but the individua properties of the object (which are very likely only to change in the way that they're removed / replaced).
If I'm not making any sense, I can add an example later 😄

I added another example to the initial post showing different usage scenarios of parameter combinations. Some of this can be done with the Condition in the description, but I still see enormous value in the whole example.


Add non-numeric transformations

@drkane: I don't expect this PR to be merged (given it breaks all the tests), however I'd like your thoughts on adding non-numeric transformations to the library.
From the Arelle library, I've taken an edited version of the FunctionIxt.py file which contains regexes (regeces?) of all the transformations per namespace (slightly edited) which should allow dates to be parsed back to ISO format and at the same time gives another level of validation of the (i)XBRL wrt permitted transformations for a given namespace (e.g. your account_3.html test file in this repository does not parse because it uses an invalid transformation).
In order to do this, I've added a boolean numeric identifier to the format to avoid parsing numeric values (though the transformations for these exist in the functionixt.py file) and had to pass through the ixt namespace too to identify the correct set of transformations.

This is fantastic - thanks very much for putting it together. I'd definitely like to include the full range of transformations in the library.
In terms of merging the PR, I think there's a few things we would need to be in place before it could merge:

[ ] get tests passing, and (more tricky) add tests for all the new functions. I wonder if something like doctest strings would be a good way to go.
[ ] check the licence situation for lifting the code from Arelle - my initial assessment is that this is within their licensing terms but we'd probably need more acknowledgements & links to their licence in the new functionsixt.py
[ ] (minor point but it would be good to match the code styles up a bit - first step would be running black & isort over the code)
[ ] I think the addition of new fields to ixbrlNonNumeric class, and the changes more generally, would constitute a breaking change, and so would need a bigger version bump reflecting this. The test for account 3 failing is an example of this.

Presumably the test failing for test account 3 is because I've edited the account in a way that means the account itself is no longer compliant with the spec, rather than the original account being non-compliant. Either way, one suggestion is that we add a "strict" mode, where it fails in a case where the ixt doesn't match the format. If strict mode is off then it would just look for a matching format without checking the ixt version - although we would need to decide which version of the function to use, so maybe that's a bad idea.
I'll add some more specific comments in the code - but thanks again, this is great and would be a fantastic addition.

Hi @wcollinscw - not sure if this is something you're still looking at. I've now added plugin functionality which allows you to create a plugin to handle formats that aren't in the core library.
I think this might be the best way to meet your needs - it should be possible to create a plugin which contains any missing formats, and install it with this library, and then they will be parsed in your data as well. Let me know if this is a helpful way to do it.

@drkane thanks for the message - sorry I got completely distracted with another project, but will definitely revisit this using the plugins feature - looks great. I'll close this PR for now. Cheers

Thanks @wcollinscw - let me know if there's anything I can do to help with a plugin, the plugin system hasn't been tested against a real-world example so keen to see if it actually works!


Not working in Android 13

Describe the bug
Images is not visible and print snack bar The permission to access Files is not granted, please go to settings to grant it
Screenshots

Smartphone (please complete the following information):

Device: OnePlus Nord CE 3 Lite
OS: Oxigene

Still, this same issue is there. I cannot able to open Gallery due to this. Please reply once fixed this.


WireGuard DNS support for destination address

Right now the destination IP will get resolved using the host's DNS. However, if a --dns options is provided, onetun should resolve the destination IP using the given peer IP(s) instead. This is a feature in WireGuard configurations.
For example:
onetun <IP_ADDRESS>:8080 pc.intranet:8080  \
    --dns <IP_ADDRESS>                   \
    --endpoint-addr <IP_ADDRESS>:51820  \
    [...options...]

... Should resolve pc.intranet by querying <IP_ADDRESS> (through WireGuard) instead of the locally configured DNS. It's the equivalent of setting DNS = <IP_ADDRESS> in a peer's wg0.conf.
Should support multiple DNS servers (prioritizing using the supplied order). Only peer IPs can be given, since onetun has no way of knowing which nameservers should be tunnelled and which shouldn't. The endpoint must have the given DNS server as an AllowedIP.
If --dns is provided and the resolution fails, onetun should fall back to the local DNS, unless --dns-strict is also passed. In that case, onetun will exclusively use the nameservers passed using --dns. If resolution fails entirely, onetun exits.

This is unblocked now; will open a branch to integrate this


Fully transparent color looks weird

Bug Description
If you have a fully transparent solid color anywhere (text color, border color, text background color, shape color), the result is really weird in the preview. See screenshots below
Expected Behaviour

The preview should somehow reflect the transparent color

Steps to Reproduce

Add a shape
Change the color opacity to 0%
Observe weird behavior

Screenshots

Additional Context

Plugin Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Show the non-transparent color in color preview
Write the actual hex in the editable text field
Show the opacity input with 0% as the value

It should work similarly to a fully-transparent gradient:

Hi team, are we looking for something like this?

@barklund
I saw that in the code comment, you put down comment: 'If opacity is 0, no extra styling needed'. Is there any caveat we need to consider about?

Verified in QA

Closing. @samitron7 @ivayloklissarov @aaecheverria


Make it clear that Docker needs to be running for serverpod to run

serverpod create fails without an error if Docker isn't running. There should be a check for that. Also documentation should be added to clarify that Docker needs to be running for serverpod to work in its default configuration.

Fixed


Add TUYATEC-v3uxbuxy

Add TUYATEC-v3uxbuxy as temphumidsensor.

Hi @danielgajdos, thanks for the request. I have added the new manufacturerName to the next release of the app.


CFE-882: add few test cases for external-certificate

Follow up : https://github.com/openshift/library-go/pull/1625

/assign @alebedev87 @Miciah

/unhold


Add Edit and Delete buttons to Avatar component

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

Summary
Currently we have avatar component which does the great job but implementing an edit & delete button along with it would be better.
Example screenshot:

Context
Most of the times people add profile avatars while editing their user's profile, so we can extend the use of this component further to provide edit & delete icons with buttons so that user can trigger their method accordingly.

@Gauravdarkslayer do you mind to point where in standard flowbite library this component is present?

Sure @rluders , here it is
General version:
https://flowbite.com/docs/components/avatar/
React version: https://www.flowbite-react.com/docs/components/avatar

I would say that this is a no. The standard library doesn't support the requested behavior by default, you can use the Avatar component to build a second component that fits your needs.


SharedState of operators are not reinitialized when the physical plan is executed repeatedly

We don't init the sharedState of each operator in the physical plan when we execute a physical plan. This will cause a bug when we execute a physical plan twice.

This is known issue that we keep state in physical operator. I'm convinced reinitialize is the right approach. Most likely we want to have an OperatorState class.


CME changes domain\ suffix to None\

Describe the bug
CME changes domain suffix to None\ when used with winrm
if used with smb it works perfect
To Reproduce
Steps to reproduce the behavior:
crackmapexec winrm  -u user -p password
Expected behavior
automatically find the domain name and append it to the user
Screenshots
root@kali:~/Desktop/CTF# crackmapexec winrm targets -u user.txt -p "P@ssw0rd"
WINRM       <IP_ADDRESS>   5985   NONE             [-] None\testuser:P@ssw0rd "('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))"

Crackmapexec info

OS: kali
Version of CME 5.0.0dev
Installed from apt

Hello @sxplitfirex does your target is linked to a domain ?

Closing since no update

Closing since no update

Sorry for not seeing this earlier.
Yes, the target is domain joined, and the issue only happens with WINRM, the other protocols work fine.


[sdl2] update to 2.0.22

Fix #24654
Update sdl2 to the latest version 2.0.22
All features are tested successfully in the following triplet:

x64-windows
x64-windows-static

/azp run

/azp run

Thanks for the update!


Command line too long when doing EAS local build on Windows

Build/Submit details page URL
https://forums.expo.dev/t/command-line-too-long-when-doing-eas-local-build-on-windows/69457/1
Summary
local build is being passed a JWT using the command line which breaks on Windows if the number of characters exceed 8191-characters
Managed or bare?
managed
Environment

eas-cli/3.5.2 win32-x64 node-v16.18.1

expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22621
Binaries:
Node: 16.18.1 - ~.nvm\versions\node\v16.18.1\bin\node.EXE
Yarn: 1.22.19 - ~.nvm\versions\node\v16.18.1\bin\yarn.CMD
npm: 8.19.2 - ~.nvm\versions\node\v16.18.1\bin\npm.CMD
Watchman: 20230108.221750.0 - C:\Users\trajano\scoop\shims\watchman.EXE
IDEs:
Android Studio: AI-213.7172.25.2113.9123335
npmPackages:
babel-preset-expo: ~9.2.1 => 9.2.2
expo: ^47.0.12 => 47.0.13
react: 18.1.0 => 18.1.0
react-dom: 18.1.0 => 18.1.0
react-native: 0.70.5 => 0.70.5
react-native-web: ~0.18.7 => 0.18.10
Expo Workflow: managed
Error output
I tried to debug this using
DEBUG=* eas build --platform android --profile preview  --local

The command that fails in the end is The command line is too long.
I hacked the code a bit to show the command it is sending.
{
  command: 'npx',
  args: [
    '-y',
<EMAIL_ADDRESS>    'eyJq... this is a very long JWT that contains my keystore...'
  ]
}

Reproducible demo or steps to reproduce from a blank project
This can be done using a private key that is 8192 byte length.
I wrote up the details on the forum as well
https://forums.expo.dev/t/command-line-too-long-when-doing-eas-local-build-on-windows/69457/1
My suggestion to fix this would be to change the local build plugin code so that it accepts the JWT from STDIN (avoid using a file because it contains private keys)

eas-cli/3.5.2 win32-x64 node-v16.18.1

It looks like you are not running that under WSL, even if we would fix that issue you would get an error "Android builds are supported only on Linux and macOS" or "iOS builds can only be run on macOS." (We will probably need to move that platform validation a bit earlier)
https://github.com/expo/eas-build/blob/main/packages/local-build-plugin/src/checkRuntime.ts#L21
Is the same happen when running a build on WSL? We do not officially support local builds for windows even under WSL, but if the same limit on command length applies there we might look into changing that.

Ok closing for now then I didn't realize that Windows is not supported.
No I don't run in WSL.


Improve counting of message arguments when msg is provided as a keyword

Closes https://github.com/astral-sh/ruff/issues/6454.

This was a regression in v0.0.283.


Snat list Creation

Hello,
Until the recent AS3 3.21, looks like there is still no schema to create a snat list. We only see snatpool shcema. Snat list is created in LTM, if we want to map a snatpool to a vlan. This can be done via BIGIP GUI or tmsh but not available via AS3. Will it be available in future releases?
Thanks
Prabhat

Please resubmit this issue using one of our issue templates: https://github.com/F5Networks/f5-appsvcs-extension/issues/new/choose


User resource usage endpoint

@DaoWen I merged from master and resolved a conflict at the end of test_basic.py due to a test that I had added at the end colliding with your new tests here. Sorry for the close and re-open, it's the only way I know of to make GitHub realize that the conflict has been resolved when resolving through their UI.

Can we add documentation to the API doc for this endpoint?

Can we add documentation to the API doc for this endpoint?

I think we should scrap our current API document in favor of an auto-generated document from our swagger annotations—but that would require beefing up all of our swagger annotations, which is going to take some work. I'll update the asciidoc file for now.

Sample basic output:
{
  "total_usage": {
    "cpus": 10,
    "mem": 2560,
    "gpus": 0,
    "jobs": 10
  }
}

Sample breakdown output:
{
  "total_usage": {
    "cpus": 2,
    "mem": 512,
    "gpus": 0,
    "jobs": 2
  },
  "grouped": [
    {
      "group": {
        "uuid": "d250d3ed-f397-47b6-9a71-173871e81c63",
        "name": "cookgroup",
        "running_jobs": [
          "ba9b69a7-5fce-4047-a484-167290134322"
        ]
      },
      "usage": {
        "cpus": 1,
        "mem": 256,
        "gpus": 0,
        "jobs": 1
      }
    }
  ],
  "ungrouped": {
    "running_jobs": [
      "81a23761-25c8-4714-a72f-3e0057ecbab6"
    ],
    "usage": {
      "cpus": 1,
      "mem": 256,
      "gpus": 0,
      "jobs": 1
    }
  }
}

@dposada - I added some basic documentation to the current REST API adoc file: https://github.com/DaoWen/Cook/blob/d9811198054638c3760551c824c968175f982904/scheduler/docs/scheduler-rest-api.adoc#user-resource-usage
Several of the other endpoint descriptions in that file are either out of date or otherwise inaccurate. I want to revisit the swagger annotations sometime soon—but we'll see if I have time. :persevere:

@pschorf - If you approve, I think this is ready to merge.

@pschorf - It's green again.


Add more configuration arguments to lakeFS file system

The three additional arguments added here are:

verify_ssl, to toggle whether or not to verify SSL certificates in HTTPS connections
ssl_ca_cert, pointing to a PEM file for cert verification
proxy, for giving a proxy server address.

Closes #31.

LGTM


Cannot find module '@schematics/angular/utility/workspace'

I'm submitting a...

[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

- Node version: XX
- Platform:

Others:

⚠ Closing now as didn't filled the issue template with relevant information for us.
Please edit this issue with the info in order to reopen this.


Isse while importing PineconeVectorStore

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
import os
import pinecone
import streamlit as st
from dotenv import load_dotenv, find_dotenv
from langchain.chains import RetrievalQA
from langchain_openai import ChatOpenAI
from langchain_openai import OpenAIEmbeddings
from langchain_community.document_loaders import PyPDFLoader, Docx2txtLoader, TextLoader
from langchain_core.vectorstores import VectorStore
from langchain_community.vectorstores import Pinecone
from langchain_pinecone import PineconeVectorStore
from langchain.text_splitter import RecursiveCharacterTextSplitter
Error Message and Stack Trace (if applicable)
cannot import name 'PineconeVectorStore' from 'langchain_pinecone'
Description
So while import all of the libraries i provided Unfortunatelly i get an error. Can't tell why. I am using import that has been set in the code libs/partners/pinecone/langchain_pinecone/vectorstores.py. The example says directly to use this import. If anyone had this issue, i would be glad to hear the solution.
System Info
System Information

OS:  Linux
OS Version:  #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb  7 11:40:03 UTC 2
Python Version:  3.11.5 (main, Sep 11 2023, 13:54:46) [GCC 11.2.0]

Package Information

langchain_core: 0.1.22
langchain: 0.1.6
langchain_community: 0.0.19
langsmith: 0.0.87
langchain_openai: 0.0.5
langchain_pinecone: 0.0.2

Packages not installed (Not Necessarily a Problem)
The following packages were not found:

langgraph
langserve

The solution is to install directly from github.
pip install git+https://github.com/langchain-ai/langchain.git


Automatic PR from RestAPI-PR1185

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1185

Codecov Report

Merging #1141 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1141   +/-   ##
=======================================
  Coverage   55.14%   55.14%
=======================================
  Files        2162     2162
  Lines       60328    60328
=======================================
  Hits        33269    33269
  Misses      27059    27059

Impacted Files
Coverage Δ

...ons/operations/appliance_definitions_operations.py
7.97% <ø> (ø)
:arrow_up:

.../managedapplications/managed_application_client.py
34.37% <ø> (ø)
:arrow_up:

...edapplications/operations/appliances_operations.py
6.98% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


cmd/link: select DWARF 4 when using external linker

When a user requests external linkage, the Go linker seems to be invoking the external linker with the "-gdwarf-2" flag (asking for DWARF version 2). Example:
$ go build -x -ldflags "-v -linkmode external -extld gcc" himom.go 1> transcript.txt 2>&1
$ fgrep 'host link' transcript.txt
0.07 host link: "gcc" "-m64" "-gdwarf-2" "-o" "/tmp/go-build530006148/b001/exe/a.out" ...
$

Given that the DWARF produced by the Go compiler is now DWARF 4, I don't think it makes sense to continue to use this flag.   When I look at the dwarf from the himom.go build above, it appears that all compilation units in the .debug_info are showing version 4 except for this one:
  Compilation Unit @ offset 0x5b7c5:
   Length:        0x4f (32-bit)
   Version:       2
   Abbrev Offset: 0x1141
   Pointer Size:  8
 <0><5b7d0>: Abbrev Number: 1 (DW_TAG_compile_unit)
    <5b7d1>   DW_AT_stmt_list   : 0x110fa
    <5b7d5>   DW_AT_low_pc      : 0x488867
    <5b7dd>   DW_AT_high_pc     : 0x48887e
    <5b7e5>   DW_AT_name        : gcc_amd64.S
    <5b7f1>   DW_AT_comp_dir    : /x/go/src/runtime/cgo
    <5b80a>   DW_AT_producer    : GNU AS 2.24
    <5b816>   DW_AT_language    : 32769	(MIPS assembler)

Not sure what the original thinking was for doing this, but it doesn't seem useful now.

For the record, we started passing -gdwarf-2 in https://golang.org/cl/7891044.  But I don't really understand why we are passing a -g option here at all, as we are only passing object files, and the linker just ignores the -g option anyhow.  So I think your CL is right.