Add "Is Referenced By" to "Relations" drop down on resource edit page

Also see #2763 which provides some better semantics for how the relations terms should be displayed on the page once a relationship is created. I modified that issue to include this new term.

And - just a minor semantic wiggle - we have the term "Cites". Do we want this term to be "IsCitedBy" instead of "IsReferencedBy?"

Sure - it can. I just thought since we already had "Cites" as a term, it made more sense to have the converse "IsCitedBy" as a new term rather than introducing something that might be a little semantically different. I'm not sure it really matters. "IsReferencedBy" could be considered a little broader in that a "reference" may or may not be a formal citation.

IsReferencedBy is pure dublin core, if we care. Happy to make it say whatever

@aphelionz - yep, Dublin Core in its dcterms namespace has both "References" and "IsReferencedBy". The other terms we are using came from a cito namespace and add the ability to have relation types that are maybe a bit more expressive. I would be fine with "IsReferencedBy" - let's just make sure it gets associated with the right namespace when it gets written to the metadata.

So superset is:

References
IsReferencedBy
Cites
IsCitedBy

@horsburgh I was referred by @martinseul to this ticket and then realized this might have been superseded by the new changes you proposed a couple of weeks ago on Wed call. Can we close this ticket? Thanks

@zhiyuli - yes, see the discussion in #3261. There's a link to a Google doc there where I lay out the changes that will need to be made to related resources, including addition of new relationship type terms. There are Dublin Core relationship types for "references" and "isReferencedBy" that can be used to create more generic pointers from and to external references. Also, they are Dublin Core and so more consistent with our overall metadata model. I think we can close this ticket, knowing that the terms will be reconciled with work on #3261.


Can it be implemented on TOOD?

it can be implemented on TOOD?The name of your method in the code is BboxDistanceMetric?

我也想知道，希望作者能回复一下


Portworx Backup - ROKS 4.17 qualification and signoff

Portworx Backup - ROKS 4.17 Qualification and Signoff

Environment:
ROKS version: 4.17.1
OS version: RHEL 8.10(Ootpa)
Kernel version: 4.18.0-553.22.1.el8_10.x86_64
Container version: cri-o://1.30.6-3.rhaos4.17.git49b5172.el8
PX Enterprise version: <IP_ADDRESS>-4ad9804
PX backup version: 2.8.0-dev
Covered below scenarios as part of this qualification

PX Backup Installation
Backup operations

Manual
Schedule
Single NS & Multiple NS
Custom Resource

Restore operations

Default restore
In-place restore
Custom restore
Replace restore

Px Backup Un installation


StructMatcher procedural macro

This is something I've dreamed of having in the C++ googletest library. The difference is in Rust this seems possible!
#[googletest::StructMatcher]
struct MyType {
  field_1: i32,
  field_2: String,
  ...
}

This attribute macro would generate something akin to:
#[cfg(test)]
struct MyTypeStructMatcher {
  field_1: Option<Box<dyn Matcher<ActualT = i32>>>,
  field_2: Option<Box<dyn Matcher<ActualT = String>>>,
  ...
}

#[cfg(test)]
impl googletest::matcher::Matcher for MyTypeStructMatcher {
  type ActualT = MyType;

  fn matches(&self, actual: &Self::ActualT) -> MatcherResult {
    if let Some(field_1) = &self.field_1 {
      if field_1.matches(&actual.field_1).is_no_match() {
        return MatcherResult::NoMatch;
      }
    }
    ...
  }
}

(A supporting enum in googletest code to make it easier to construct the field matcher)
pub enum StructFieldMatcher<ActualT> {
  None,
  Matcher(Box<dyn Matcher<ActualT = ActualT>>)
}

impl<M: Matcher + 'static> From<M> for StructFieldMatcher<<M as Matcher>::ActualT> {
  fn from(value: M) -> Self {
    Self::Matcher(Box::new(value))
  }
}

This enables usage similar to the following:
#[googletest::test]
fn my_test() {
  let value = MyType {
      field_1: 3,
      field_2: "helloworld".into(),
      ...
    };
  expect_that!(value, MyTypeStructMatcher{
      field_1: lt(3).into(),
      field_2: contains_substring("llow").into(),
    });
}

Disadvantages
We need to make googletest (or some related crate) a public dependency of crates. Thankfully the #[cfg(test)] attribute should prune the code gen for the entire implementation, but we do still pay the cost of the procedural macro.

There is some support for this with matches_pattern! macro. But I like this approach as well, since it is more obvious what code is generated. However, currently, matches_pattern! is more powerful, as it handles methods as well.
To avoid the disadvantages, we could use cfg_attr, which should avoid adding the macro to the public dependencies.
Nice trick with .into(). I was pondering an option with generic field, but with other trade-offs. Adding them here for completeness.
Declaration
#[cfg(test)]
struct MyTypeStructMatcher<M1, M2, ...> {
  field_1: M1,
  field_2: M2,
  ...
}

impl<M1: Matcher<i32>, M2: Matcher<String>, ...> Matcher<MyType> for MyTypeStructMatcher<M1, M2, ...> {
  ...
}

But it is not possible to implement a Default implementation, hence all the field must be set.
Wait for https://github.com/rust-lang/rust/issues/86555
https://github.com/rust-lang/rust/issues/86555 will allow to implement:
impl MyTypeStructMatcher<Anything, Anything, ...> {
  fn is_anything() -> Self {
    ...
  }
 }

which can be passed as default:
MyTypeStructMatcher{
 field_1: eq(31),
  ..MyTypeStructMatcher::is_anything()
}

Use a builder pattern
We can easily implement a generic builder to set fields like:
impl MyTypestructMatcher<Anything, Anything, ...> {
  fn new() -> Self {...}
}

// Maybe lock M1 to Anything, to disallow overwrite
impl<M1, M2, ...> MyTypeStructMatcher<M1, M2, ...> {
  fn field_1<N: Matcher<i32>>(field_1_matcher: N) -> MyTypeStructMatcher<N, M2, ...> {
    ...
  }
}

but this is less elegant than using a constructor directly.

I completely missed the matches_pattern tbh, so thank you! That does solve 90% of my pain. One thing it's missing is that it's not exhaustive. Part of the reason I want something like this is to ensure we catch every field. I've been bitten before by my tests checking some but not all fields.
The "declaration" idea was my first thought (not fully formed of course). Its main advantage being omitting .into() entirely. Perhaps this is the way to go? If you only want to specify some fields, users can just use matches_pattern. This struct's main advantage is that it's exhaustive.
I definitely don't like the builder pattern, especially for nesting these. I can only imagine what horrors rustfmt would come up with. It is an important alternative though.

In the matcher-generator approach, there's a further nuance of nested structs and figuring out how to do the right thing there if the nested struct has a corresponding matcher struct generated vs not.
So given that matches_pattern seems to meet most of the needs, is the only thing left to be solved the ability to ensure that all fields have been checked? Or is there additional functionality being sought here?
(Looking to possibly take this on.)

@marcianx, nested structs should be handled like any other field. So for a struct like:
#[googletest::StructMatcher]
struct MyType {
  field_1: MyNestedStruct,
  field_2: String,
}

struct MyNestedStruct {
  a: i32,
  b: u32,
}

It should generate something like:
#[cfg(test)]
struct MyTypeStructMatcher {
  field_1: Option<Box<dyn Matcher<ActualT = MyNestedStruct>>>,
  field_2: Option<Box<dyn Matcher<ActualT = String>>>,
}

Whether a matcher exists that you can put there is up to the caller. For example, they can use a matches_pattern there, or any or whatever else.

As for matches_pattern replacing this, if there's a way to make it exhaustive, that would be great, but I don't think there is? matches_pattern doesn't get the definition of the struct, so it has no idea how many fields exist. Not to mention, matches_pattern also supports properties, which makes it a little confusing in terms of being exhaustive. Like can you still also test properties if the matcher is meant to be exhaustive? Unclear what the right behavior is there.

Ah, you're right about nested structs -- your representation is quite generic.
It would be a pity to make a second strongly overlapping way to do the same thing that matches_pattern! already does just to additionally support the specific use-case of exhaustiveness. But it might be possible to use a complementary approach that avoids duplication of functionality, like defining a derive macro that implements a custom trait, say:
trait ReflectFields {
  fn field_names() -> Vec<String>;
}

If we can incorporate this into matches_pattern! and have matches_pattern! fail if not all fields are checked unless the pattern passed into it explicitly has a ..} suffix.

Tracking which fields are checked would require some careful thinking.
We'd also have to use specialization hacks (like inherent-method/auto-ref specialization) to support values that don't implement ReflectFields.

I've not tested the feasibility of this approach yet, though it would likely require converting matches_pattern! to a proc_macro first.
The disadvantage of this approach is that lack of exhaustiveness would be caught at runtime instead of compile time.
WDYT?

Per chat with @bjacotg:

matches_pattern! doesn't work well with autocomplete and you can't use it if fields are not public.
matches_pattern! doesn't use valid rust syntax, so that rustfmt doesn't work on it.

I'll investigate a solution similar to the original post. Please LMK @bjacotg if you'd like me to attempt a different direction.

I was experimenting and chatting with @bjacotg, and this is where we landed so far
Tool behavior
To understand the constraints imposed by rust-analyzer autocomplete and rustfmt, I ran a few tests with both vim + coc.vim and with vscode with the rust-analyzer plugin.

rustfmt requires valid rust syntax. The presence of Foo { a: ref 1 } within a macro prevents rustfmt from formatting the macro.
rust-analyzer auto-complete happens to work even when within a macro that matches against ($($tt:tt)*) (which is as untyped as a macro gets). It suggests autocompletions from ambient symbols, but when it matches some struct-like syntax, it will offer precise types if the struct name is defined, even in the presence of invalid syntax like the use of ref in Foo { a: ref 1 }:

I get this full-signature autocomplete only after the first struct field and the following comma have been entered.

To get more proactive autocomplete, I need to have no macros: e.g. it would have to be outside verify_pred!(...). @bjacotg noted that a verify_that!(foo).eq(matcher) might work, but it wouldn't report the right file+line location on error.

So maybe using a macro-based solution, even with nested macros, wouldn't hurt auto-complete too badly as noted above and maybe we could reduce the scope to just focus on making field matching exhaustive in the absence of an explicit ..} suffix in the pattern.
Field exhaustiveness
It occurred to me that we don't really need the full-powered StructMatcher in order to support field exhaustiveness. We could just generate a zero-sized struct with all the fields and One that just occurred to me is to create a dummy zero-sized struct with all the same fields. We construct the dummy struct constructor syntax as we parse fields. Then we embed the construction of the dummy struct in a noop way as long as the pattern match doesn't end in ..}. The disadvantage is that we still require an annotation on the original Struct.
@bjacotg then had the brilliant idea of modifying the strategy to generate a match or matches! instead! And that doesn't even require an annotation on the original struct! So to elaborate:
Given:
verify_that!(
    actual,
    matches_pattern!(
      Foo {
        a: eq(1),
        b: eq("foo"),
        method(): starts_with!("3"),
      }
    ),
)

matches_pattern! would generate:
{
  fn __matches_pattern_ensure_exhastive_match(val: Foo) {
    let _ = match val {
      Foo { a: _, b: _ } => "ensure exhaustive matches_pattern!",
    };
  }
  // ... actual matching logic ...
}

which would result in a compilation error when a new field (say, c) is added to Foo:
error[E0027]: pattern does not mention field `c`
 --> src/main.rs:9:7
  |
9 |       Foo { a: _, b: _ } => "ensure exhaustive matches_pattern!",
  |       ^^^^^^^^^^^^^^^^^^ missing field `c`
  |
help: include the missing field in the pattern
  |
9 |       Foo { a: _, b: _, c } => "ensure exhaustive matches_pattern!",
  |                       ~~~~~
help: if you don't care about this missing field, you can explicitly ignore it
  |
9 |       Foo { a: _, b: _, .. } => "ensure exhaustive matches_pattern!",
  |

The compilation error isn't the most direct, but hopefuly the inline string makes it obvious.

Woah, the field exhaustiveness idea is so clever!!! The cost of a bad error message is sad, but for the simplicity of not needing a struct attribute, it might be worth it!
I wonder if the error message would get better or worse by forcing newlines into the generated code (if that's even allowed in declarative macros). I would imagine seeing the struct definition on multiple lines might make it more readable.
Thanks for proving me wrong about making the macro exhaustive hahaha.

Ugh, one of the issues I ran into after implementing (thanks to exhaustive tests!): if Foo above is an enum variant instead of a struct, then fn __matches_pattern_ensure_exhastive_match(val: Foo) doesn't compile since Foo isn't a type. So I need to use Foo strictly in a match pattern context and infer the type.
To do this, I have to match against a value with inferred type. But then I also have to somehow declare andthis value without the inferred type being available. Since I can't pass the value into the function without specifying its type, I also need to produce an instance of the value. PhantomData comes to mind, or per dtolnay's "Unit struct with type parameters" trick, I can do this with a 0-sized array.
quote! {
    fn __matches_pattern_ensure_exhastive_match(i: usize) {
        let val: [_; 0] = [];
        let _ = match val[i] {
            #struct_name { #(#field_names: _),* } => "ensure exhaustive matches_pattern!",
        };
    }
}

Seems to work for enums!

Actually, the method above doesn't infer generic parameters of the struct properly. The workaround is to match against the actual value by putting this match within predicate matcher:
googletest::matchers::predicate(|actual| {
    // The match must be in an inferred matcher so that generic arguments of
    // `#struct_name` can be deduced based on the actual type.
    match actual {
        #struct_name { #(#field_names: _),* } => {},
        // The pattern below is unreachable if the type is a struct (as opposed to an
        // enum). Since the macro can't know which it is, we always include it and just
        // tell the compiler not to complain.
        #[allow(unreachable_patterns)]
        _ => {},
    }
    true
}),

Ah, haha! Oh man. After lots of debugging, I realized that I needed a ref-only predicate matcher to avoid the additional inference issues and then went into matches_pattern::internal to implement it, and then realized that it already exists as PatternOnlyMatcher. :)


Unintuitive default split when logging three images

Describe the annoyance
When logging exactly three images to separate entity paths, the first image will be in its own pane, with the remaining two sharing an extra grid pane. It's a bit annoying to rearrange into a view where all images have the same size. This seems to only happen when logging exactly three images.
To Reproduce
import rerun as rr
import numpy as np

rr.init("test", spawn=True)

rr.log("image1", rr.Image(np.random.rand(100,100,3)))
rr.log("image2", rr.Image(np.random.rand(100,100,3)))
rr.log("image3", rr.Image(np.random.rand(100,100,3)))
# rr.log("image4", rr.Image(np.random.rand(100,100,3)))

Expected behavior
All images should appear in a consistent way in the viewer (i.e., all taking the same amount of space).
Additional context
rerun_py 0.10.0-alpha.7+dev [rustc 1.72.1 (d5c2e9c34 2023-09-13), LLVM 16.0.5] x86_64-unknown-linux-gnu main 47414c8, built 2023-10-24T12:00:38Z

@emilk something we want to consider fixing in the default tiling or close as won't fix with explicit user blueprint as the future solution?

I think the problem here is that we have a heuristic for the default arrangement that will never be perfect.
The current heuristic is not smart enough to know that some of the space-views have a fixed aspect ratios (as 2D space-view have, but 3D space-views do not). Adding this support is possible, but challenging.
The real solution is to make it easier for users to change the default from code and in the UI:

https://github.com/rerun-io/rerun/issues/2276
https://github.com/rerun-io/rerun/issues/2652


This repo is not being updated

I've been watching this repo hoping the author would pop back in and merge some necessary pull requests, and even emailed him to see if he would allow someone else to, but I've gotten no response and it's been quite a while since his last comment. So does anyone have an updated fork that the current users could migrate to? This seems like a project that a few too many people use to be abandoned.

What about yours @ansballard? Or maybe @Boyyce?

Back to it... will take care of the issues and push a variable-width version of the picker asap.


Support for Canon 60D cameras

I've started some work on Canon support, but it probably should be a lot cleaner than what's currently in place. I found that all the information for the which focus points are selected, which are in focus, and the exact coordinates are all in the EXIF on my Canon 60D. Since that's not exactly the most modern Canon at this point, I would venture the same or better information can be found in newer ones.
I documented what the EXIF data looks like and created a map file for the Canon 60D coordinates in a branch, if someone is interested in using it to add broader Canon support based on this. It should be easy to generate maps of any Canon camera that has similar AF data to mine automatically.
See my branch at https://github.com/neilschelly/Focus-Points/tree/canon-60d
I'd be happy to answer any questions or supply any sample images if it would be helpful to someone motivated to continue this work.

Hi, Thanks a bunch for this. I may have some good/bad news for you. I think you're camera is already supported. Can you please download the latest from the master repo and try it?

I just bumped to your latest master, removed and reinstalled the plugin, and I don't see any focus points come up when I click "Show Focus Point" in the plugin extras menu. I just see the image itself in the window. If I do Show Metadata, it comes up as a blank/empty window.
I can try to troubleshoot a bit more later, or I can send you the images I'm looking at if that would help you. I don't have a lot of time to contribute unfortunately. I had the best of intentions when I forked this, but it's going to be awhile before I can really contribute too much more coding time.

great. I'll add your mapping file then. thanks for checking that. 1 final thing if you dont mind. can you PR some sample images into here for me
https://github.com/musselwhizzle/Focus-Points-Sample-Images

Done.

Using supplied sample images, current canon 60D is off. Adjust or used supplied point map (See Screenshot)

I can't reproduce this - all the 60D sample images show correct focus points with the latest master branch on my system.
e.g.

weird, I dont get that at all. None of the 60D images work for me. Both the 40D and 80D work great.

@rderimay - could you try and see what you get?

PS: attached is my metadata file. Is this the same as you're getting?
IMG_8568-metadata.txt

Your metadata matches what I see. What does a full log look like?

log attached:
libraryLogger.txt

It's related to the dialog size which is a result of your screen size. Change the dialog to something small here:
local contentWidth = appWidth * .9
  local contentHeight = appHeight * .9

and it will completely break (or fix it in my case)

it has to do with the piecing together of the focus box. If there's not enough space to draw all 4 corners, the script completely fails.

Look how close the first image is. When I make the dialog box just a hair smaller, the focus box goes away. We fix this issue, and it should be resolved @rderimay

Yes, this line causes the small boxes to be ignored:
if dist > 25 then

I agree. It looks like a bug when they dont show up. The first image I posted isn't useable. I'll let @rderimay chime in before we change the code.

@neilschelly let's see if we can get yours working. First off are you mac or PC.

If I do Show Metadata, it comes up as a blank/empty window
That's not a good sign. It wont work with that blank.

Set your logging to debug (as shown in the screenshot), and then attach your log file here please.

Your log file is located under ~/Documents/libraryLogger.log. Rename it to libraryLogger.txt so this webpage will let you upload it.

Good Morning :-)
This is intended behavior. I will PR an improvement by displaying them in all cases but limiting their proximity so that it still looks like an af point.

Le 13 janv. 2017 à 07:27, Joshua Musselwhite<EMAIL_ADDRESS>a écrit :
I agree. It looks like a bug when they dont show up. The first image I posted isn't useable. I'll let @rderimay chime in before we change the code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Fixed in PR #98

Yes, the current master resolves my issue. Still need to figure out why @neilschelly metadata is completely blank, then we'll be all set!

When do you write blank metadata, is it something that is not working on my code or in the metadata dialog code ?
Don't understand if I need to test something or not actually.
On 13 janvier 2017 at 19:39:06, Joshua Musselwhite<EMAIL_ADDRESS>wrote:
Yes, the current master resolves my issue. Still need to figure out why @neilschelly metadata is completely blank, then we'll be all set!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I need a response from Neil. You're off the hook for now :)

Ok !
On 13 janvier 2017 at 20:21:40, Joshua Musselwhite<EMAIL_ADDRESS>wrote:
I need a response from Neil. You're off the hook for now :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry folks, my day job has nothing to do with this. The Mac I use for photography is at home. I hope to be able to get the test data you need later tonight.

I just upgraded the plugin to the latest/greatest. Focus points show up and the metadata page is no longer empty. I'm all good now! Thanks a ton for the effort.


pdo_firebird

Hey Folks!
I'm trying to use the fork of this repo:
https://github.com/Ambacia-consulting/doctrine-firebird-driver
I'm using symfony 5.4 with php8.1 (or later if I'm able to upgrade any further...).
Problem is that I'm alway getting an error and parameter injection for some reason does not work.
So we have switch to pdo_firebase as interbase / ibase must be installed on our own - which is not feasible in lookout for our hosting...
Error
Too few arguments to function IST\DoctrineFirebirdDriver\Driver\AbstractFirebirdInterbaseDriver::__construct(), 0 passed in /var/www/html/vendor/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php on line 291 and exactly 1 expected
services.yaml
IST\DoctrineFirebirdDriver\Driver\AbstractFirebirdInterbaseDriver:
    arguments:
        $configuration<EMAIL_ADDRESS>
App\Service\FirebirdService:
    arguments:
        $db<EMAIL_ADDRESS>
Anyone a quick guess?
Best,
Bent

I just saw that even though the author claimed having shifted to pdo_firebird... it's using ibase_connect and similar functions.
This shouldn't be the case - right?
I'm somewhat confuse :upside_down_face:

hint for the next one :see_no_evil:
-> dev-master branch
composer.json

  "repositories": [
    {
      "url": "https://github.com/Ambacia-consulting/doctrine-firebird-driver/tree/master",
      "type": "git"
    }
  ],

...

    "kafoso/doctrine-firebird-driver": "dev-master",


Linux Support on pip

Description
pip missing support for pipelineDP on Linux
How to Reproduce
[root@iZbp1flguy1vkvhcyxmq60Z PipelineDP]# pip3 install pipeline-dp
WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3 install --user` instead.
Collecting pipeline-dp
  Could not find a version that satisfies the requirement pipeline-dp (from versions: )
No matching distribution found for pipeline-dp

You have Python 3.6. There are pip packages for Python of versions >=3.7 (according to wiki page Python 3.6 is no longer officially supported).
You can install a newer version of Python and everything should work.

Still the same error after updating
wenhui.zhang@n231-227-105:~$ python3 --version
Python 3.10.2
wenhui.zhang@n231-227-105:~$  pip3 install pipeline-dp
Defaulting to user installation because normal site-packages is not writeable
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't c
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't c
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't c
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't c
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't c
Could not fetch URL https://pypi.org/simple/pipeline-dp/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(hos
ERROR: Could not find a version that satisfies the requirement pipeline-dp (from versions: none)
ERROR: No matching distribution found for pipeline-dp


Inllisense not working in existing modules in Visual Studio 2015 community

I have everything well configured with the _references.js file, and I get intellisense for other libraries, like jQUERY, but I can't get it to work properly for AngularJS.
For example. in the bellow picture I'm creating a new module and adding a directive and I get intellisense for the $http angular object, which is fine.

But in the bellow picture the module is already created and so I don't put the empty array in the module declaration. If I did, it would overwrite any previous declared module, rendering my app useless. Even though everything works fine with the code, intellisense is gone:

I've been searching for more than a month. Any ideas?

This has to be a _references.js issue. If the Intellisense engine can't find the module declaration in a file referenced there then it won't be able to spin up AngularjS.
If you post a sample project that demonstrates the issue I will take a look.

jmbledsoe, thank you!
I ziped everything but the packages and .vs folder. Hope it's enough.
WebApplication1.zip

Move angular.js and angular-mocks.js ahead of your application files in _references.js. Files in _references.js need to be in the same order as they are in your index.html for Intellisense to know what to do with them.

Again, thank you very much. This fixed it.
I didn't find this information anywhere. I imagine this happens to 99% of users, because the "update javascript references" command  that auto add every JS file in the _references.js doesn't care about the order, nor does it gives any warning nor any of the documentation do. not that I could find.

Yeah the docs need updated. Feel free to create a PR!

I want to give back to the community. I'm planning to do a complete guide about VS Intellisense, including AngularJS. I never did a pull request. It's gonna be my pleasure doing it for the first time. :smile:

Awesome! Thanks!


Bump the dot version of haproxy for our test env

What does this PR do?
Bumps our version for e2e testing from 2.1.2 to 2.1.4 to match the latest dot release currently available.
Motivation
While this is a minor version update, we received a bug report (https://github.com/DataDog/integrations-core/issues/6568) for something observed in 2.1.4 which hadn't been seen in our test environment.

FWIW I don't think the bug is due to versioning, but configuration. If you remove stick-table from our conf you should see the issue.

FWIW I don't think the bug is due to versioning, but configuration. If you remove stick-table from our conf you should see the issue.

Agree - it just seemed like a minor change that would keep us up-to-date.


Failed to create over sized thick provisioning image

Currently For thick provisioning cephcsi creates an image and it writes zeros to the images until the image is full. If the ceph cluster gets full 9occupied more than 85%) during this operation the cephcsi client opened to write zeros hangs and all the subsequent requests for the same volume returns with an error when a user deletes the PVC this will leave a stale rbd image in the cluster.
The above problem can be fixed by #2115  by setting the SetPoolFullTry flag (which allows the delete of rbd images even if the cluster is full and also it returns an error when we are writing zeros when the ceph is full). Even with this fix, we end up Creating/Deleting the image multiple times until the ceph is freed up.  Once the ceph cluster is 85% the cluster becomes read-only and also affects the already mapping client read/write performance. With the help of #2125  we do check for the free space before creating the rbd image and we don't create/delete images frequent for a single PVC request. this will help to avoid the to an extent and will reduces the read/write overread of the already mapped rbd image.

Currently For thick provisioning cephcsi creates an image and it writes zeros to the images until the image is full. If the ceph cluster gets full 9occupied more than 85%)

Note that the 85% is configurable.

during this operation the cephcsi client opened to write zeros hangs

This is expected to be addressed with #2115.

and all the subsequent requests for the same volume returns with an error when a user deletes the PVC this will leave a stale rbd image in the cluster.

Kubernetes will retry. Maybe there is a CSI status return code for 'provisioning in progress'? If that gets returned to Kubernetes, it should also request to abort/delete the volume that is being provisioned. This status notification exists for snapshots, maybe for volumes too?

The above problem can be fixed by #2115 by setting the SetPoolFullTry flag (which allows the delete of rbd images even if the cluster is full and also it returns an error when we are writing zeros when the ceph is full).

Ok!

Even with this fix, we end up Creating/Deleting the image multiple times until the ceph is freed up.

Yes, that is how Kubernetes is designed to work.

Once the ceph cluster is 85% the cluster becomes read-only and also affects the already mapping client read/write performance.

Does this affect performance more than an application workload once the volume is provisioned? There is also a request to provide an optimized way for allocations in Ceph (RHBZ#1924129).

With the help of #2125 we do check for the free space before creating the rbd image and we don't create/delete images frequent for a single PVC request. this will help to avoid the to an extent and will reduces the read/write overread of the already mapped rbd image.

A solution to prevent thick-provisioning from causing a full cluster should ideally take the following into account:

understand is the reason to use thick-provisioning, it is a workaround for accounting issues, and makes it impossible to have the benefits of the (standard, well tested) thin-provisioning
likeliness of running out of space (how many clusters are seized too small?)
the 85% watermark in Ceph is configurable, anything Ceph-CSI does needs to adjust to that too
...

Some more questions that would help in judging to see if we need to (can?) fix this in Ceph-CSI

Can we have a single sentence for the problem that needs addressing?
Why is running out of space with thick-provisioning different from running out of space with workloads on thin-provisioned volumes?
What cases are not addressed with #2125, and what is the plan to address those?
Are there other workarounds that can prevent this issue from happening?


Downloader: Configure preferred source code origin

Add new downloader parameter --source-code-origin to set the preferred download location:
Either vcs or artifact.
Defaults to the current standard vcs.
See: https://github.com/oss-review-toolkit/ort/issues/2848

PR is ready to review.
One thing is currently missing, though:
The Postgres storage might contain results from one source that is not the prioritized one.
This will be adressed and I'll open a separate PR for this.

Merging this despite the failing tests which have been verified to pass locally.


Improve Search Modal performance

Right now the search components renders three sub components all at once resulting in unnecessary rendering that contributes to slower responses. Use branching logic as appropriate and render the three sub components as needed.
Acceptance Criteria

[ ]  Search component only renders one of SearchInputModal or LocationInputModal or the Search screen component

Steps for QA:

Open the Search screen
Click on one of the search input modal, the modal should open faster than before.

We tried a fix to this problem, which improved the speed of the app but broke the functionality. Putting it back in triage for now.

closing as we have an updated design #918


fixed Rosette installation in FrontendDockerfile

As suggested I created a pull request.
I tested the changes with the test_in_docker.sh file, they work correctly.
With the old file, failures occured.
A full explanation of the changes is found in #68
Please review and merge. Tell me your thoughts!

It appears that the travis-CI failed.
Would you mind taking a look? If not, I can take a look later this week.

Of course I will have a look :)
The problem is that the dockerimage for Cosette-Frontend is pulled from shumo/cosette-frontend (dockerhub). However this image is build with the exact wrong dockerfile, that I propose to fix in this PR.
We could solve this by merge this PR and update the dockerfile in shumo/cosette-frontend (see here) to the version that I created here :)

Thanks @primeapple . I have merged your PR manually on my local repo and it passed the regression tests.

I see. That's the circular dependency issue (that file in docker hub actually linked here as well).

Restart CI test after new docker image is up. Now the CI test passes. Thanks @primeapple !


Spike: Revisit Answer Attestation

The DTR IG is currently being updated, and the way that attestation works is being revisited. We need to verify that our implementation is compliant with the latest IG that will be balloted in May.
DTR IG:
https://build.fhir.org/ig/HL7/davinci-dtr/specification.html
Acceptance Criteria:

The IG is reviewed and any stories we need to work to be compliant are in the backlog.

We will now return only the questionnaireresponse-author extension on items that are populated by CQL.  All other extensions are handled by the DTR app.


The dinghy ssh-config does not exist

After a fresh installation of dinghy, the ssh-config command does not exist any more. It don't know if it's a feature or a bug.

  $ dinghy ssh-config
  > Could not find command "ssh-config".
  $ dinghy version
  > Dinghy 4.2.0

Yeah see the changelog (https://github.com/codekitchen/dinghy/blob/master/CHANGELOG.md#420---2016-01-22). Dinghy doesn't handle ssh itself anymore, it just calls out to docker-machine ssh now, so the ssh infrastructure code was removed. Depending on your use case, you can still get the information from docker-machine inspect dinghy, or just call dinghy ssh directly.
Sorry for breaking the semver contract on that, I should've waited for a major version bump to remove the command.


ReactiveStreams API Adapter for S3 ByteStream

Describe the feature
Currently, the S3Client upload and get support ByteStream, when using it in a Reactive application,  it is not so easy to convert a reactive streams type to ByteStream.
Is your Feature Request related to a problem?
No
Proposed Solution
I would like use the ReactiveStreams compatible Publisher<ByteBuffer>, esp, in Spring WebFlux/Reactor, use the specific Flux and DataBuffer aka Flux<DataBuffer>, also consider RxJava3/SmallRye Munity
Describe alternative solutions or features you've considered

The existing ByteStream to implements Publisher
Kotlin Couroutines, support Flow as data type.

Acknowledge

[ ] I may be able to implement this feature request

AWS Kotlin SDK version used
0.15.2-beta
Platform (JVM/JS/Native)
JVM
Operating System and version
Windows 10

@hantsy Thanks for the feature request.
NOTE: There is a rather large limitation from S3 though that requires a known Content-Length. This would require that you know the total size that will be produced by a Flow/Publisher at the time of making the request. This may or may not be an issue for you depending on your use case.

Indeed today you would need to create your own adapter from Flow/Publisher -> ByteStream. I've produced a working sample using Flow<ByteArray> you can hopefully extrapolate from below that does this (assuming the limitation called out above is workable for your use case).
The key to marrying the two together is to collect the producer in a coroutine and write the individual buffers to an SdkByteChannel and use that channel as a ByteStream.OneShotStream.
/**
 * Dummy producer
 */
fun producer(content: ByteArray, cnt: Int): Flow<ByteArray> = flow {
    repeat(cnt) {
        println("emitting buffer $it")
        emit(content)
        delay(1.seconds)
    }
}

/**
 * Collect the [producer] flow and emit it as a [ByteStream.OneShotStream]
 *
 * @param producer the publisher
 * @param contentLength the total content length that producer will emit
 * @return a [ByteStream] that can be used for S3 operations
 */
fun CoroutineScope.byteStreamFlow(
    producer: Flow<ByteArray>,
    contentLength: Long
): ByteStream {
    val chan = SdkByteChannel()
    launch {
        producer
            .onCompletion { cause -> chan.close(cause)    }
            .collect {
                println("writing buffer")
                chan.writeFully(it)
            }
    }

    return object : ByteStream.OneShotStream() {
        override val contentLength: Long? = contentLength
        override fun readFrom(): SdkByteReadChannel = chan
    }
}

fun main(): Unit = runBlocking {
    val bucketName = "<YOUR-BUCKET-NAME>"
    val keyName = "<YOUR-KEY-NAME>"

    val dummyContent = "Reactive ByteStream example".encodeToByteArray()
    val cnt = 10
    val contentLength = (dummyContent.size * cnt).toLong()

    S3Client.fromEnvironment{
        sdkLogMode = SdkLogMode.LogRequest + SdkLogMode.LogResponse
    }.use { s3 ->

        // S3 requires Content-Length header for PutObject or UploadPart
        val bodyStream = byteStreamFlow(producer(dummyContent, cnt), contentLength)

        val resp = s3.putObject {
            bucket = bucketName
            key = keyName
            body = bodyStream
        }

        println(resp)
    }
}

Currently, I am using Spring WebFlux multipart feature to upload a file to S3, the uploaded file  FilePart include a content method (return a Flux<DataBuffer>) to retrieve the file content.
I convert Flux<DataBuffer> into ByteArray, and use S3Client ByteStream.readFrom to read it it. On my testing environment (LocalStack docker and a text file), it works well.
I will try your solution to use Flow in the whole progress, thanks.

The Spring reactive Part(Upload files)  does not include a method/field to get the content length.

Currently I am using the following codes to get files from s3 service and write to http response in a Spring Webflux/Kotlin Coroutines appalication.
val request = GetObjectRequest {
    bucket = bucketName
    key = objectKey
}

// read the object into byte array.
client.getObject(request) { it.body?.toByteArray()

...

// in spring controller.

val buffer = DataBufferUtils.read(
    ByteArrayResource(bytes), // the byte array retrieved from S3
    DefaultDataBufferFactory(),
    1024
).log()

// write to HTTP response
return exchange.response.writeWith(buffer).awaitSingleOrNull()

I assume you're storing the result of getting the byte array into a value called bytes?
val bytes = s3client.getObject(request) { it.body?.toByteArray() }

If so, that looks like the correct way to read the entire object into memory. What exception or problem are you seeing?

This works with a LocalStack Docker and I tested it with a text file. But on the AWS, it is deployed by the CI and Devops, I have no enough permission to view all aws logs.
For my experience, maybe I have to set content type to my HttpResponse.

I know reading the object into a byte array is a bad idea. But there is no simple way to convert between Flux<DataBuffer> and S3 ByteStream.

It should be possible to adapt a ByteStream into a Flow. For example:
const val bufferSize = 4096

suspend fun main() {
    val s3 = S3Client.fromEnvironment { }

    val req = GetObjectRequest {
        bucket = "some-bucket"
        key = "some-key"
    }

    s3.getObject(req) { resp ->
        val stream = resp.body as ByteStream.OneShotStream
        val flow = produceFlow(stream.readFrom())
        consumeFlow(flow)
    }

    println("Complete!")
}

fun produceFlow(reader: SdkByteReadChannel): Flow<ByteArray> {
    val buffer = ByteArray(bufferSize)
    return flow {
        var bytes = reader.readAvailable(buffer)
        while (bytes != -1) {
            if (bytes > 0) {
                emit(buffer.copyOfRange(0, bytes))
            }
            bytes = reader.readAvailable(buffer)
        }
    }
}

suspend fun consumeFlow(chunks: Flow<ByteArray>) {
    var total = 0
    RandomAccessFile("/tmp/chunk-download.zip", "rw").use { file ->
        chunks.collect { chunk ->
            println("Received a ${chunk.size} byte chunk, writing to file (written $total bytes so far)")
            file.write(chunk)
            total += chunk.size
        }
        println("Finished writing file, wrote $total bytes")
    }
}

This code sample emits individually-allocated buffer chunks into a Flow in produceFlow. It then writes those chunks to a RandomAccessFile in consumeFlow. Note that the consuming code needs to execute in the context of the getObject response lambda (otherwise, the stream will be freed and the bytes will no longer be available).

I tried to apply the Flow<ByteArray>.toByteStream, and ByteStream.toFlow(), failed, check the branch of the example project: https://github.com/hantsy/aws-sdk-kotlin-spring-example/pull/6


Docker: Jobs not running with vanilla Docker image

As the title says, doing a docker run -it -p 5000:5000 cantino/huginn gets a Huginn image up and running, but background jobs will not run. They just sit in the list.

Hey @TFenby, thanks for reporting this. There isn't really anyone working on the Docker deployment right now.  Do you know it well enough to debug?  Also, @ianblenke might have ideas.

Sounds like we need to spin up some background workers. For that, we'll need a process manager like supervisord. Let me take a quick stab at it.

It looks like [ -z DO_NOT_RUN_JOBS ] is the culprit. Changing that to "-n" fixes it.
I'm refactoring the init script a bit here to exec supervisord and have it spawn children processes to ensure proper signal delivery. Will generate a PR shortly.

Awesome @ianblenke, thanks!

@TFenby Did #681 fix this for you?

https://github.com/cantino/huginn/pull/681#issuecomment-69746193
:)

Ah!  Awesome :smile:


Added hex transparency

Added hex transparency to the back of hex codes
closes #16

Hi @lars-vc , thank you very much for submitting the PR.
I tried it out and things are looking good.
One small issue is that the Transparent HEX value should be at the beginning instead of at the end? According to:
https://stackoverflow.com/a/23201304/19205063
https://gist.github.com/lopspower/03fb1cc0ac9f32ef38f4
But there are information like this
https://webtools.fineaty.com/ColorInfo/FFFFFF00/en/Information-about-the-FFFFFF00-color.html
I'm unfamiliar with Transparent HEX colors so I can't tell :smile:. What do you think about putting Transparent HEX information at the beginning or at the end? Thank you :)

Also I forgot about when you open the Color Picker when your cursor is on a color, the Color Picker should pick up the color under your cursor. Maybe we can add the feature for Transparent HEX colors in the future?

Hi @lars-vc , thank you very much for submitting the PR. I tried it out and things are looking good.
One small question I have is that the Transparent HEX value should be at the beginning instead of at the end? According to: https://stackoverflow.com/a/23201304/19205063 https://gist.github.com/lopspower/03fb1cc0ac9f32ef38f4
But there are information like this https://webtools.fineaty.com/ColorInfo/FFFFFF00/en/Information-about-the-FFFFFF00-color.html
I'm unfamiliar with Transparent HEX colors so I can't tell 😄. What do you think about putting Transparent HEX information at the beginning or at the end? Thank you :)

It is a bit of a toss up, but CSS uses at the back (https://stackoverflow.com/questions/1751263/hex-colors-numeric-representation-for-transparent). So that's why I picked at the back.

Also I forgot about when you open the Color Picker when your cursor is on a color, the Color Picker should pick up the color under your cursor. Maybe we can add the feature for Transparent HEX colors in the future?

Ah I forgot about this, Ill fix it tmrw!

Ah I forgot about this, Ill fix it tmrw!
Thank you very much. I'm sorry in advance because that part of the code base is a bit amateurish :smile:

Added!

Thank you very much @lars-vc for the amazing PR :smile:


Blur: inital fundamentals commit

:pushpin: References
🎄 Asset Checklist

[x] Added to databases.csv or already exists

🧮 Metric Checklist

[x] Added new fact tables if necessary
[x] Pulled fact table into ez_asset_metrics.sql table
[x] Compiles in Github
[x] Show Changed Models in Github matches expectations for what metric value should be

Looks great! Just be sure to execute out the compiled SQL + execute locally in Dagster before shipping

Ran daily_blur_job which includes all relevant extract code + SQL transformations and all looks good 👍


ProviderContainer weirdly catches and handles unintended errors

Describe the bug
I made a mistake on my codebase. Dang, that happens. Specifically, I gave two routes the same name.
I'm using GoRouter as a dependency; rightfully, my router will complain about this with a specific runtime exception.
The thing is, ProviderContainer kicks in, eats this exception and returns something I'm unable to understand.
I had to do a scavenge the stack trace to understand where such exception came from.
Here's what I get on my terminal:

some incomprehensible logs

══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown building UncontrolledProviderScope:
Got a stack frame from package:stack_trace, where a vm or web frame was expected. This can happen if
FlutterError.demangleStackTrace was not set in an environment that propagates non-standard stack
traces to the framework, such as during tests.
'package:flutter/src/foundation/stack_frame.dart':
Failed assertion: line 192 pos 7: 'line != '===== asynchronous gap ===========================''

The relevant error-causing widget was:
  UncontrolledProviderScope
  UncontrolledProviderScope:file:///home/venir/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_riverpod-2.1.1/lib/src/framework.dart:250:12

When the exception was thrown, this was the stack:
#2      StackFrame.fromStackTraceLine (package:flutter/src/foundation/stack_frame.dart:192:7)
#3      MappedIterator.moveNext (dart:_internal/iterable.dart:391:20)
#4      WhereTypeIterator.moveNext (dart:_internal/iterable.dart:869:20)
#5      new _GrowableList._ofOther (dart:core-patch/growable_array.dart:202:26)
#6      new _GrowableList.of (dart:core-patch/growable_array.dart:152:26)
#7      new List.of (dart:core-patch/array_patch.dart:51:28)
#8      Iterable.toList (dart:core/iterable.dart:470:12)
#9      StackFrame.fromStackString (package:flutter/src/foundation/stack_frame.dart:93:10)
#10     StackFrame.fromStackTrace (package:flutter/src/foundation/stack_frame.dart:78:12)
#11     FlutterErrorDetails.debugFillProperties (package:flutter/src/foundation/assertions.dart:712:57)
#12     DiagnosticableNode.builder.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:2940:17)
#13     DiagnosticableNode.builder (package:flutter/src/foundation/diagnostics.dart:2943:8)
#14     _FlutterErrorDetailsNode.builder (package:flutter/src/foundation/assertions.dart:1289:56)
#15     DiagnosticableNode.emptyBodyDescription (package:flutter/src/foundation/diagnostics.dart:2954:77)
#16     DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1632:13)
#17     DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#18     WidgetInspectorService._nodeToJson (package:flutter/src/widgets/widget_inspector.dart:1606:18)
#19     WidgetInspectorService._reportStructuredError (package:flutter/src/widgets/widget_inspector.dart:937:44)
#20     FlutterError.reportError (package:flutter/src/foundation/assertions.dart:1184:14)
#21     _debugReportException (package:flutter/src/widgets/framework.dart:6493:16)
#22     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4887:9)
#23     StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5050:11)
#24     Element.rebuild (package:flutter/src/widgets/framework.dart:4604:5)
#25     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4859:5)
#26     StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5041:11)
#27     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4853:5)
...     Normal element mounting (7 frames)
#34     _UncontrolledProviderScopeElement.mount (package:flutter_riverpod/src/framework.dart:309:11)
...     Normal element mounting (9 frames)
#43     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3863:16)
#44     Element.updateChild (package:flutter/src/widgets/framework.dart:3592:18)
#45     RenderObjectToWidgetElement._rebuild (package:flutter/src/widgets/binding.dart:1195:16)
#46     RenderObjectToWidgetElement.mount (package:flutter/src/widgets/binding.dart:1164:5)
#47     RenderObjectToWidgetAdapter.attachToRenderTree.<anonymous closure> (package:flutter/src/widgets/binding.dart:1111:18)
#48     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2605:19)
#49     RenderObjectToWidgetAdapter.attachToRenderTree (package:flutter/src/widgets/binding.dart:1110:13)
#50     WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:945:7)
#51     WidgetsBinding.scheduleAttachRootWidget.<anonymous closure> (package:flutter/src/widgets/binding.dart:925:7)
(elided 6 frames from class _AssertionError, class _RawReceivePortImpl, class _Timer, and dart:async-patch)

════════════════════════════════════════════════════════════════════════════════════════════════════

Another exception was thrown: 'package:flutter/src/widgets/framework.dart': Failed assertion: line 4606 pos 14: 'owner!._debugCurrentBuildTarget == this': is not true.

Another exception was thrown: 'package:flutter/src/widgets/framework.dart': Failed assertion: line 4606 pos 14: 'owner!._debugCurrentBuildTarget == this': is not true.
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: 'package:flutter/src/widgets/framework.dart': Failed assertion: line 2609 pos 20: '_debugCurrentBuildTarget == context': is not true.
     _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
     _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
     BuildOwner.buildScope.<anonymous closure> (package:flutter/src/widgets/framework.dart:2609:20)
     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2613:12)
     RenderObjectToWidgetAdapter.attachToRenderTree (package:flutter/src/widgets/binding.dart:1110:13)
     WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:945:7)
     WidgetsBinding.scheduleAttachRootWidget.<anonymous closure> (package:flutter/src/widgets/binding.dart:925:7)
     Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:18:15)
     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:398:19)
     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:429:5)
     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192:12)

Versus what I should get on my terminal if I hadn't used ProviderScope:

some useful logs

══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown building Myapp(dirty):
duplication fullpaths for name "home":/home, /home
'package:go_router/src/configuration.dart':
Failed assertion: line 188 pos 15: '!_nameToPath.containsKey(name)'

The relevant error-causing widget was:
  Myapp Myapp:file:///home/venir/Documents/Riverpod/riverpod_bug_repro/lib/main2.dart:6:16

When the exception was thrown, this was the stack:
#2      RouteConfiguration._cacheNameToPath (package:go_router/src/configuration.dart:188:15)
#3      new RouteConfiguration (package:go_router/src/configuration.dart:24:5)
#4      new GoRouter (package:go_router/src/router.dart:65:27)
#5      globalRouter (package:riverpod_bug_repro/router/router.dart:17:22)
#6      globalRouter (package:riverpod_bug_repro/router/router.dart)
#7      Myapp.build (package:riverpod_bug_repro/main2.dart:17:21)
#8      StatelessElement.build (package:flutter/src/widgets/framework.dart:4949:49)
#9      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4878:15)
#10     Element.rebuild (package:flutter/src/widgets/framework.dart:4604:5)
#11     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4859:5)
#12     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4853:5)
#13     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3863:16)
#14     Element.updateChild (package:flutter/src/widgets/framework.dart:3592:18)
#15     RenderObjectToWidgetElement._rebuild (package:flutter/src/widgets/binding.dart:1195:16)
#16     RenderObjectToWidgetElement.mount (package:flutter/src/widgets/binding.dart:1164:5)
#17     RenderObjectToWidgetAdapter.attachToRenderTree.<anonymous closure> (package:flutter/src/widgets/binding.dart:1111:18)
#18     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2605:19)
#19     RenderObjectToWidgetAdapter.attachToRenderTree (package:flutter/src/widgets/binding.dart:1110:13)
#20     WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:945:7)
#21     WidgetsBinding.scheduleAttachRootWidget.<anonymous closure> (package:flutter/src/widgets/binding.dart:925:7)
(elided 6 frames from class _AssertionError, class _RawReceivePortImpl, class _Timer, and dart:async-patch)

════════════════════════════════════════════════════════════════════════════════════════════════════

To Reproduce
I made it! You can reproduce this behavior on this repo. To reproduce, do the following:

Run the application using Riverpod via flutter run -t lib/main.dart: you'll get weird errors
Run the exact same application, without using Riverpod: flutter run -t lib/main2.dart: you'll get useful errors

Expected behavior
main.dart and main2.dart should show the same exception, i.e. the readable GoRouter one, as ProviderScope shouldn't absorb nor modify the nature of this exception, I guess.
EDIT. I forgot to push my commits onto the repro, sorry. Now it's updated.

I have actually run into this issue before and I thought I was doing something very wrong. Debugging was very painful without seeing the actual error message. I've used this snippet to get readable error message though stacktrace is still messed up.
FlutterError.demangleStackTrace = (StackTrace stack) {
  if (stack is Trace) return stack.vmTrace;
  if (stack is Chain) return stack.toTrace().vmTrace;
  return stack;
};

Ah yes, my bad, should've been more specific :)

I'm seeing this stack trace in my project. This issue only occurs when I use a nested route in GoRoute, for eg:
GoRoute(
  path: '/home',
  builder: (context, state) => const HomePage(),
  routes: [
    GoRoute(
      path: 'recent_contacts',
      builder: (context, state) => const RecentContactsPage(),
    ),
  ],
),

Not sure if OP also has the same route structure since his repo sample is not found now. If I remove mRecentContacts route here, the issue will not occur.
Adding demangleStackTrace as mentioned above can work around this, but hope there is another better solution.


declare with force

When running "metacat declare" in a recovery or repair situation, the user might find that the file record 1) does not exist, 2) exists, but is retired or 3) exists unretired.   Please consider two switches

--force which would "unretire" and "update -r" if the record was found in a retired state
--overwrite which would include the --force feature and in addition would "update -r" if the record existed.

Providing this on the server side simply removes the logic and several server calls that it takes to implement these patterns in user code.

@rlcee Would perhaps: --overwrite=retired vs --overwrite=any be more descriptive?
I am tempted to change this entirely as an error handlier on the API client side,
in a 4.0.1 client release(?)...

Just thinking about it a little, what feels natural to me is "--if-needed=unretire  --if-needed=overwrite".  But I don't feel strongly, so please proceed.  Please include this option in the python API.  As for coding it as a error handler in the client, does that imply making several calls to the server?  Would it be more efficient to handle it on the server side?  I'm not sure how much a connection costs in time.  But I wouldn't really expect this option to be activated frequently, since it is imagined for helping in cleanup of a non-optimal situation.  Thanks

Yes, the client would be making several calls to the server, if the file exists,  but it  keeps the server simpler, and thus a smaller change overall.

Okay, I googled for similar phrases, and I've come up with --unretire-as-required  and --overwrite-as-required.   I think that flows better.

Okay, so I ended up with --as-required=overwrite or --as=required=unretire.

Thanks very much!


removeFromActionEvents: true does not work

1 - Describe the bug
removeFromActionEvents: true in AwesomeNotifications().getInitialNotificationAction(removeFromActionEvents: true) does not do anything.
I will keep it short as I see that this already got resolved in master but not in the version from pub dev. So next version it will probably get fixed and I open the issue is just to keep track of that.
This line is missing in the version from pub.dev, so the value of removeFromActionEvents does not being transferred to AwesomeNotificationsPlatform.instance.getInitialNotificationAction()
https://github.com/rafaelsetragni/awesome_notifications/blob/5e9e2b6b5cc31b463cdda709bc2ef17cb44559b9/lib/awesome_notifications.dart#L194
This issue seems to be fixed in the master branch so it is only open to keep track until it arrives to pub.dev
package version -  awesome_notifications: ^0.7.4+1

Hi @guyluz11, i just uploaded the new release versions of 0.7.5-dev.2+1 versions of awesome_notifications and awesome_notifications_fcm to fix this issue. Please, check it out to see if this issue is solved on these new versions.
Also, don't forget to join in your Discord Beta team to request fixes and new updates.

Thanks


Add addtional seetings in config.yaml

Without setting this option, Google would refuse indexing the web page because Google would complain No: 'noindex' detected in 'robots' meta tag

Hi @BDHU , maybe using HUGO_ENV environment variables is a better way?
HUGO_ENV=production hugo


Webpack related warnings and error after upgrading v4.0.3 to v5.0.0

Describe the bug
Getting warnings and ultimately an error after upgrading from v4.0.3 to v5
Starting the development server...

(node:62864) [DEP_WEBPACK_COMPILATION_CACHE] DeprecationWarning: Compilation.cache was removed in favor of Compilation.getCache()
(node:62864) [DEP_WEBPACK_TEMPLATE_PATH_PLUGIN_REPLACE_PATH_VARIABLES_HASH] DeprecationWarning: [hash] is now [fullhash] (also consider using [chunkhash] or [contenthash], see documentation for details)
(node:62864) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET_INDEXER] DeprecationWarning: chunk.files was changed from Array to Set (indexing Array is deprecated)
(node:62864) [DEP_WEBPACK_CHUNK_ENTRY_MODULE] DeprecationWarning: Chunk.entryModule: Use new ChunkGraph API

And then this (the error is at the end of the output)
Compiled successfully!

You can now view company-web-app in the browser.

  Local:            http://localhost:3000
  On Your Network:  http://<IP_ADDRESS>:3000

Note that the development build is not optimized.
To create a production build, use npm run build.

assets by path static/media/*.svg 4.97 MiB
  assets by info 4.63 MiB [immutable] 537 assets
  + 15 assets
assets by path static/media/*.woff 207 KiB
  asset static/media/roboto-v20-latin-900italic.c20d916c1a1b094c1cec.woff 21.8 KiB [emitted] [immutable] [from<EMAIL_ADDRESS>(auxiliary name: main)
  + 9 assets
assets by path static/media/*.woff2 162 KiB
  asset static/media/roboto-v20-latin-900italic.cb5ad999740e9d8a8bd1.woff2 17.1 KiB [emitted] [immutable] [from<EMAIL_ADDRESS>(auxiliary name: main)
  + 9 assets
assets by path static/js/*.js 31.4 MiB
  asset static/js/bundle.js 30.8 MiB [emitted] (name: main) 1 related asset
  + 2 assets
+ 4 assets
orphan modules 4.28 MiB [orphan] 6340 modules
runtime modules 33 KiB 19 modules
built modules 21.6 MiB (javascript) 5.14 MiB (asset) [built]
  modules by path ./node_modules/ 14.1 MiB (javascript) 4.93 MiB (asset)
    javascript modules 14 MiB 2737 modules
    asset modules 22.3 KiB (javascript) 4.93 MiB (asset) 544 modules
    json modules 30.2 KiB 5 modules
  modules by path ./src/ 7.55 MiB (javascript) 220 KiB (asset)
    javascript modules 6.81 MiB 1274 modules
    asset modules 25.3 KiB (javascript) 220 KiB (asset) 18 modules
    json modules 727 KiB
      ./src/locales/sv.json 238 KiB [built] [code generated]
      + 2 modules
  ./util.inspect (ignored) 15 bytes [built] [code generated]
1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack 5.69.1 compiled with 1 error in 52352 ms
No issues found.

And finally, when trying to run the app I get this in my Chrome console
Uncaught Error: Module parse failed: Cannot read properties of undefined (reading 'resource')
File was processed with these loaders:
 * ./node_modules/workerize-loader/dist/rpc-worker-loader.js
 * ./node_modules/babel-loader/lib/index.js
 * ./node_modules/source-map-loader/dist/cjs.js
You may need an additional loader to handle the result of these loaders.
TypeError: Cannot read properties of undefined (reading 'resource')

Did you try recovering your dependencies?

Yes, I've tried deleting node_modules/ and package-lock.json
$ npm --version
8.1.4

Which terms did you search for in User Guide?

Mostly searched for "1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)"
Environment

Environment Info:

  current version of create-react-app: 4.0.3
  running from /Users/tobbe/.config/yarn/global/node_modules/create-react-app

  System:
    OS: macOS 12.2
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 16.14.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.1.4 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 98.0.4758.109
    Edge: 98.0.1108.62
    Firefox: 94.0.1
    Safari: 15.3
  npmPackages:
    react: ^17.0.1 => 17.0.2
    react-dom: ^17.0.1 => 17.0.2
    react-scripts: ^5.0.0 => 5.0.0
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce
Unfortunately not able to reproduce outside of our (closed source) code. A fresh cra5 project works fine.
Expected behavior

I expected the upgrade to go smoothly
Actual behavior

Reproducible demo

Sorry, no demo to share 🙁

Here are dependencies and a few more things from our package.json
  "dependencies": {
    "@formatjs/cli": "^1.1.22",
    "@formatjs/intl-getcanonicallocales": "^1.5.3",
    "@formatjs/intl-locale": "^2.4.13",
    "@formatjs/intl-numberformat": "^4.2.11",
    "@formatjs/intl-pluralrules": "^4.0.5",
    "@formatjs/intl-relativetimeformat": "^5.2.11",
    "@companyab/boundary-pages": "^1.2.1",
    "@companyab/docs": "^3.2.1",
    "@companyab/company-nets": "^0.6.1",
    "@companyab/company-onfido": "^15.0.0",
    "@companyab/company-pep": "^6.0.1",
    "@companyab/translation-runner": "^1.3.0",
    "@companyab/ui-2": "^37.0.1",
    "@material-ui/core": "^4.11.0",
    "@material-ui/icons": "^4.9.1",
    "@sentry/react": "^5.27.1",
    "@testing-library/jest-dom": "^5.11.6",
    "@testing-library/react": "^11.2.0",
    "@testing-library/user-event": "^12.2.2",
    "@types/body-scroll-lock": "^3.1.0",
    "@types/classnames": "^2.2.11",
    "@types/d3": "^6.3.0",
    "@types/d3-interpolate-path": "^2.0.0",
    "@types/d3-scale": "^2.2.0",
<EMAIL_ADDRESS>"^0.0.41",
    "@types/jest": "^26.0.15",
    "@types/js-cookie": "^2.2.6",
    "@types/jspdf": "^1.3.3",
    "@types/luxon": "^1.26.2",
    "@types/node": "^16.7.8",
<EMAIL_ADDRESS>"^1.0.1",
    "@types/react": "^16.9.56",
    "@types/react-datepicker": "^3.1.7",
    "@types/react-dom": "^16.9.9",
    "@types/react-flag-icon-css": "^1.0.4",
    "@types/react-helmet": "^6.1.0",
    "@types/react-intl": "^3.0.0",
    "@types/react-linkify": "^1.0.0",
    "@types/react-modal": "^3.12.0",
    "@types/react-router-dom": "^5.1.7",
    "@types/ua-parser-js": "^0.7.35",
    "body-scroll-lock": "^4.0.0-beta.0",
    "core-js": "^3.6.5",
    "d3-interpolate-path": "^2.1.2",
    "elevio": "^1.0.2",
    "fireworks-js": "^1.3.5",
    "framer-motion": "^2.7.2",
    "intersection-observer": "^0.11.0",
    "js-cookie": "^2.2.1",
    "jspdf": "^2.3.0",
    "luxon": "^1.23.0",
    "qrcode.react": "^1.0.1",
    "query-string": "^6.13.1",
    "react": "^17.0.1",
    "react-animate-height": "^2.0.21",
    "react-dom": "^17.0.1",
    "react-flag-icon-css": "^1.0.25",
    "react-helmet": "^6.1.0",
    "react-intersection-observer": "^8.26.2",
    "react-intl": "^5.20.2",
    "react-intl-translations-manager": "^5.0.3",
    "react-linkify": "^1.0.0-alpha",
    "react-modal": "^3.12.1",
    "react-router": "^5.2.0",
    "react-router-dom": "^5.2.0",
    "react-to-print": "^2.10.0",
    "sass": "^1.49.9",
    "typescript": "^4.4.2",
    "ua-parser-js": "^0.7.24"
  },
  "scripts": {
    "// preinstall needed for": "https://github.com/facebook/create-react-app/issues/11773",
    "preinstall": "npx npm-force-resolutions",
    "modify-files": "node ./modify_files.js",
    "analyze": "source-map-explorer 'build/static/js/*.js'",
    "start": "node write_env.js development && react-scripts start",
    "build": "node write_env.js production && react-scripts build && npm run modify-files",
    "test": "react-scripts test",
    "translations": "translation-runner",
    "translations:print-all": "translation-runner --print-all"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "devDependencies": {
    "@types/classnames": "^2.2.11",
    "husky": "^3.0.8",
    "lint-staged": "^11.1.2",
    "npm-force-resolutions": "^0.0.10",
    "prettier": "^2.3.2",
    "react-scripts": "^5.0.0",
    "source-map-explorer": "^2.4.2",
    "workerize-loader": "^1.2.0",
    "ws": "^7.2.0"
  },


Oyun oynamak vee video öğretici gelsin bence

Clear and concise description of the problem
Gelsin
Suggested solution
Gelsin
Alternative
Gelsin
Additional context
Gelsin
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

:)

@İbax


Add unmet peer dependency<EMAIL_ADDRESS>

warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>

… @jelteliekens these are warnings that you need to add these dependencies to your own package.json

Ok, thanks. After some research I figured it out as well.


The translation of SQL editions and supported features is unacceptable

The translation of SQL editions and supported features is unacceptable
some description is  totally opposite after translation.
for an example
The original info of Always on AG feature is not supported at standard edition, you can find it from this URL:
https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2017#RDBMSHA
but it says yes at chinese version, here is the url:
https://docs.microsoft.com/zh-cn/sql/sql-server/editions-and-components-of-sql-server-2017#RDBMSHA
It will really confuse customer.

@SonjaSaltzman Please take a look at this localization issue.

@ishasahni1 for follow-up

@SonjaSaltzman @Powerhelmsman @lichaozhao Thank you so much for your valuable feedback. We are looking into this issue and checking with our translation team on the same. Will keep you posted once the issue is fixed on the translation side.


Feature Request: URL preview

Fantastic app.  Thanks for your work on it.
I have a feature request that I think would be valuable for a broad audience.  It'd be really nice to include URL previews if a message contains a link. Currently links sent from Mudslide are just the raw text:

However if you paste a link in the native WhatsApp client, it'll generate a preview:

I believe Baileys has the capability to include the preview.
Is this something that can be included?

Thanks very much, @robvanderleek!  I will test in the coming couple of days.

Thanks again for your work on including this functionality, @robvanderleek .  I've now had a chance to test and have some feedback.  I'm ignoring the imdb issue as it seems like it's the only URL that isn't working for me, so I'm assuming it's site-specific.
It seems that the preview parses the site heading, but does not include the image rendering.  For example, the following shows the same link sent from the native WA client, and then from Mudslide:

The above is the same for other sites too:

versus

I've seen a ticket talking about image sizing for the preview so understand that an image should be generated.
Do you see the same?

Hi @ThisIsTheOnlyUsernameAvailable
I've added some extra code from the issue you mentioned, can you try again?
For me, on iOS WA client, the images do render (both with and without the extra code mentioned above):

What platform is your client running on?

I'm using Android and am not seeing the previews.  However it looks like this is a known bug: https://github.com/WhiskeySockets/Baileys/issues/347
Thanks for your implementation of the feature; I really appreciate it.  I'll see if I can get it fixed upstream.


Implement MVP data model

See the boxes labelled MVP in the following document:
Domain-Model-MVP.pdf

Fixed in #82


Fix the Podfile entry mentioned in Readme

Needed to be pod 'LHSKeyboardAdjusting', '~> 0.0'

@cazares don't know why I ever missed this! updated for 2.0. :)

Awesome! Thanks @dlo :D


Revert "Resolve mouse lag issue in Android VM."

This reverts commit 9e1a2caf7ba33f9be500564597b946bcd91bdc47.
Tracked-On: OAM-122237

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

FAILURE: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.


boards: Add MG100

Add Laird Connectivity MG100

zephyr/tests/net/bridge needs an exclusion added


Objective-C support

Objective-C support, so the framework can be included in objc projects.
Mostly just converting structs to classes, tagging with @objc as needed, and fixing up some stuff that straight up doesn't existing objc (typealias, OptionSet for the BorderMask class).  Several of the protocols had to be turned into classes - which may not be totally needed, but was the best as I could figure out to make it work.
I'm by no means experienced or even intermediary with swift, so I'm open to suggestions and happy to help test/work through issues with the pull request.
But it does work for me now in objc programs, via cocoapods, then just add
#import "KPCTabsControl/KPCTabsControl-Swift.h"
to headers or code files to get the classes

Hi. Thanks for your work. First, I am surprised you cannot use the framework as it is in an Obj-C project. For the Swift3 release I just made, maybe not, as it breaks compatibility with several things. But I thought the Swift2 release would work. I can see your PR is made from my old Swift3 branch, maybe you could try with the Swift2 branch first? I am reluctant to made all those changes back to just to be compatible with Obj-C (especially the change of protocols into classes).

Xcode8 refuses to load the swift 2 code without converting it, so I don't really know if it is objc compatible or not, but can try to investigate a bit further.

I, too, think the current Swift 3 code should compile with Xcode 8 as a framework and then work from Objective-C using @import KPCTabsControl; out of the box.

The styles/themes - because they're structs, aren't exposed at all in the objc code.  Then converting them to classes leads down the rabbit hole that the entire diff is

Official doc says it all: https://developer.apple.com/library/prerelease/content/documentation/Swift/Conceptual/BuildingCocoaApps/InteractingWithObjective-CAPIs.html#//apple_ref/doc/uid/TP40014216-CH4-ID35
While we could easily fix enums, changing struct and tuples is a pain. I'd rather make an obj-c branch.

Ya up to y'all.  I'm happy to maintain it separate here in my repo if youd prefer - I'm more comfortable with objc than swift, and the safari tabs style was exactly what I'm looking for for my project, so did the porting work.  I'll keep using my work either way, and master changes periodically.


If not header, first paragraph must be selected from above and to its left

When I'm using the Ursine theme (either Polar or Umbra) and the first paragraph is not a header, trying to select it fails. Instead, its selection box (or whatever it's called) is immediately above the text and to its left, so if I click there, it will select the text.
Again, this only occurs on the first paragraph, and it does not occur if the text is a header. I've tried this with other themes, so I know it's an Ursine issue.

Huh, that's interesting. Turns out that little hacky thing I did for the splashscreen does affect that paragraph line (I essentially messed with a couple of properties of the first "line" of text, as well as a couple of other key elements). I got an idea to work around that, but it'll probably have to wait a bit since I'm stuck on finals right now.
I'll reply here once more when I put a release up with that fix, as well as a couple of other details

Release is up! Sorry it took a while; I wasn't able to do this earlier due to college work overload


Updates to the holidays of Croatia, starting from the year 2020

Starting from the year 2020, there are some changes to the national holidays of Croatia. Some holidays have changed names, some have been disbanded and a new holiday was added.
The holiday list which is valid from the year 2020 can be found at the "Narodne novine" https://narodne-novine.nn.hr/clanci/sluzbeni/2019_11_110_2212.html
(English: The People's Newspaper), the official gazette of the Republic of Croatia which publishes laws, regulations, appointments and official decisions and releases them in the public domain
Edit: The full list of changes

Statehood day is now celebrated at a new date. The old date is still remembered (called "Spomendan", but is not an official holiday) as Independence Day (Dan neovisnosti).
Homeland Thanksgiving Day has been given a different name to include Victory Day and Day of Croatian Defenders (full name: Dan pobjede i domovinske zahvalnosti i Dan hrvatskih branitelja/Victory and Homeland Thanksgiving Day and the Day of Croatian Defenders).
Independence Day is no longer an official holiday. (It is still remembered as a "Spomendan" called Croatian Parliament Day, this PR only removes the official holiday - does not add the "Spomendan").
A new official holiday is created called "Remembrance Day for Homeland War Victims and Remembrance Day for the Victims of Vukovar and Skabrnja"

Hey @stelgenhof, I briefly updated the changelog and updated the PR description to include full list of changes.


[AIRFLOW-1221] Fix templating bug with DatabricksSubmitRunOperator

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

In our implementation of DatabricksSubmitRunOperator we mistakenly
switched the order of the tuples returned by enumerate. The bug
is fixed in this commit and an additional unit test is added to
verify that this bug is fixed.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Changes LGTM. Could you update the description?

LGTM, indeed please update commit message per guidelines (jira issue in subject).

@bolkedebruin good catch. I've fixed this now.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2308   +/-   ##
=======================================
  Coverage   69.23%   69.23%
=======================================
  Files         144      144
  Lines       11024    11024
=======================================
  Hits         7633     7633
  Misses       3391     3391

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 a379cc1...74b6983. Read the comment docs.

@bolkedebruin could we get this merged? Thanks :)


Compilation errors in ESPHome

Hi mate,
I'm trying to test your integration in Home Assistant but I can't get it to compile.
My configuration in ESPHome:
midea-ac.txt
And the error logs while compiling:

logs_midea-ac_upload.txt
Do you know what's happening? Maybe it's something related with I'm using NodeMCU ESP8266 rather than ESP32?
Thank you for your work

It was definitely an error caused for trying to flash an ESP8266... I'm working on a port of your code for the ESP8266 boards and will let you know when it's done. Of course will give you credits.
Kind Regards

Hello,
Just got your message.
Never tried it on ESP8266 and glad to hear somebody will port it.
I can give some advice. For ESP8266 try using just Serial or Serial1 instead of Serial2 and change the parameters for begin.

If interested you can read more at:
http://arduino.esp8266.com/Arduino/versions/2.3.0/doc/reference.html (I hope is up to date)


Export animated gltf

Hello,
Firstly, I would like to express my gratitude for releasing such wonderful code. I am someone who attempted to extract animated gltf from your previous project, the BANMo project(#58). At that time, you mentioned that there was a plan to release code for extracting animated gltf in lab4d. I am curious to know when this feature might be updated?

Hi @LyndzP, thanks for getting in touch. This feature was not on top of the to-do list, as there were other ways for 4D visualization (e.g., viser). I can put it to higher priority if more people need it.
It would also be great if you have time to contribute, as you seem to be able to export banmo result to gltf!


Can this project become an organization?

Is your feature request related to a problem? Please describe.
according to the owner of this repo it's difficult for him (that was the conclusion i made) to continue to create new features. also it appears he also need some hand to make hotfixes like https://github.com/SpacingBat3/WebCord/issues/328 (the owner can say that. this is just an assumption about this last phrase).
Describe the solution you'd like
so i wonder (and i hope breaking the line here)  and if the owner is agree in create an organization like happened with  invidious.
Because this app is awesome. I'm super happy using wayland and share my screen to coworkers! Really love it.

That's unlikely to happen, given I don't see much interest of external developers. I have some plans to grant people access to a separate branch through (and in general make it a bit less restrictive to master), although I think I should follow some criteria and possibly only add these people which will actively contribute to it via PRs.
As of the features, I will probably work on low-effort ones, mostly following the last project I've opened.

Good to know. I'll close this issue because of the clarification provided by the author.
Good work!


Update install_k9s

What this PR does / why we need it:
With k9s release v0.24.10 the asset name now contains the version, hence the install script has to be updated
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Fixed `install_k9s` script

/invite @gardener/ops-toolbelt-maintainers

@petersutter just one question - is there any chance that we would need the older versions? Then we would have to support both download link formats.

@plkokanov usually there is no need to get an older version, except maybe there is a bug in the latest released version in which case you might want to have the previous version. v0.24.10 is already out some time and seems to be stable, so I would vote for keeping it simple and leave it as is and not support the versions older than v0.24.10


bump release runner fanout to 4c runners

we're seeing:
  Warning  Evicted    3m28s  kubelet            The node had condition: [DiskPressure].

now on some legs of the build.
this bumps us up (slightly) to 4c runners, which also have significantly larger disks
ref: https://docs.github.com/en/actions/using-github-hosted-runners/about-larger-runners#machine-sizes-for-larger-runners

There isn't a 4 core runner pool, so everything has been wedged since this landed.  I'm puzzled that we aren't seeing this in the private rebuilds?

We applied this change downstream, but not here: https://github.com/chainguard-images/images/pull/1571


Wildcard expansion not supported in Windows Powershell?

Hello.  First, I would like to say that I really appreciate you writing this version of the panorama eoi fix for Samsung jpgs.  I just tried running the sampan exe in Windows 11 using Powershell and although Powershell is supposed to support wilcard expansion, it does not work.  I get the following error:
PS C:\temp> .\sampan pans*.jpg -i
thread 'main' panicked at 'Cannot open file pans*.jpg: Os { code: 123, kind: Other, message: "The filename, directory name, or volume label syntax is incorrect." }', src/main.rs:124:38
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
I am, however, able to get wildcard expansion to work using git bash.  Thanks!

Hi @mipoon,
Thanks for trying the program out! The problem is that Powershell does not expand wildcards like all normal shells, but passes the * character to the program.
Could you try running:
sampan (get-item pans*.jpg) -i

Yes, that works!  That's fantastic.  Thank you so much for the quick solution.
I have another question/issue but will open a separate ticket for that so it is not confused.

@mipoon I updated the README with instructions. Thanks for testing!


How could  I use a general CSV file?

Hi,
I would like to know whether your architecture would suit a general classification problem? Means, any CSV file or tabular data?

Yes it would you can use the model however you like


Aliases for enum variants are not working with flattened enums

I have an enum with some aliases for the variants. The enum is placed as field inside a struct. If I add the flatten tag to the field, the deserialization fails with the error no variant of enum MyEnum found in flattened data. If I don't use the flatten tag, everything works as expected.
Not working example (with flatten tag):
#[derive(Deserialize, Debug, PartialEq)]
pub enum MyEnum {
    #[serde(alias = "ValueStringAlias")]
    #[serde(rename = "ValueString")]
    String(String),

    #[serde(alias = "ValueBooleanAlias")]
    #[serde(rename = "ValueBoolean")]
    Boolean(bool),
}

#[derive(Deserialize, Debug, PartialEq)]
#[serde(rename_all = "PascalCase")]
struct Test {
    number: u32,

    #[serde(flatten)]
    my_enum: MyEnum,
};

const TEST_XML: &'static str = r##"
    <Test>
        <Number>123</Number>
        <ValueBooleanAlias>true</ValueBooleanAlias>
    </Test>
"##;

Working example (without flatten tag):
#[derive(Deserialize, Debug, PartialEq)]
pub enum MyEnum {
    #[serde(alias = "ValueStringAlias")]
    #[serde(rename = "ValueString")]
    String(String),

    #[serde(alias = "ValueBooleanAlias")]
    #[serde(rename = "ValueBoolean")]
    Boolean(bool),
}

#[derive(Deserialize, Debug, PartialEq)]
#[serde(rename_all = "PascalCase")]
struct Test {
    number: u32,
    my_enum: MyEnum,
};

const TEST_XML: &'static str = r##"
    <Test>
        <Number>123</Number>
        <MyEnum>
            <ValueBooleanAlias>true</ValueBooleanAlias>
        </MyEnum>
    </Test>
"##;

I've used quick-xml as deserializer here, but it semse to be a bug of serde.

Closing as a duplicate of #1504.

While the duplicate issue, #1504, is closed, the issue in the original comment here is still a problem. Using the same code from the original comment, I have put together an example using serde_json (so I could have it run on the playground) to show the problem: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=088644732feb07e0e7d1a97f423838ad
It seems that the solution to #1504 fixed the problem for field aliases, but not variant aliases.
Can we reopen this issue? Or is there another issue tracking enum variant aliases?

Probably, #2566 will fix that, the relevant lines seems to the here:
https://github.com/serde-rs/serde/pull/2566/files#diff-2a062279ae10fa8cfea059371a1320afc87b998e7153017941e31ff7450ca64aR1218-R1221

@Anders429 You have a nice repro for the outstanding problem with enum variants. I would open a separate issue for better tracking.

Seems like the outstanding problem with enum+alias+flattened is also reported here https://github.com/serde-rs/serde/issues/2188

#2566 does completely resolve this issue. This can be verified by rerunning the playground I linked above.


DragonbornSpeaksNaturally.exe cannot exit after game exited

Biirman 29 March 2019, 2:23AM

I have encountered an issue that is quite annoying. Whenever I close the game, the dragonbornspeaknaturally.exe does not, resulting in a couple things. If I launch the game without closing, there are two instances open. Also, steam thinks the game is still running. Is there some way to make the program close when Skyrim closes, so I don't have to open up task manager?

Fixed at https://github.com/YihaoPeng/DragonbornSpeaksNaturally/commit/b040af7e356cb92f7a42277c3116dae9a617999a


Feature/setting plugin

Transform our Project plugin (applied to project) into a Settings plugin (applied to settings), as a prerequisite to control new gradle dependencies restrictions at settings.
Two missing tasks will be developed in following PRs:

Reenable pandora plugin
Allow configuration from settings

LGTM, great job!


Transition from document.execCommand to navigator.clipboard

💥 Proposal
Is your feature request related to a problem? Please describe
document.execCommand is being deprecated. navigator.clipboard.readText and writeText are already supported in all browsers so we should be able to just replace the implementation.
Describe the solution you'd like
Replace document.execCommand with navigator.clipboard.readText/writeText
Describe alternatives you've considered
None
Are you able to assist to bring the feature to reality?
I can try
Additional context
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard
Have you read the Contributing Guidelines on issues?
Yes

Thanks for bringing this to our attention @vincentdo. I’ll plan next days in order to check my availability and work effort to support the new API considering the library context and usage. In the meaning time, feel free to propose any change or additional feedback that you believe you can do 😋


AccountSession receives and stores clientId after successful auth

ClientId was constant null previously.

Hi @adamsipos, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;


Day 12: Hill Climbing Algorithm

Codecov Report

Merging #21 (0efbe49) into main (3a43d3f) will decrease coverage by 0.04%.
The diff coverage is 97.89%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   98.35%   98.31%   -0.05%
==========================================
  Files          34       38       +4
  Lines        2487     2723     +236
==========================================
+ Hits         2446     2677     +231
- Misses         41       46       +5

Impacted Files
Coverage Δ

lib/aoc/src/lib.rs
96.55% <ø> (ø)

lib/solution/src/lib.rs
100.00% <ø> (ø)

lib/solution/src/day12/state.rs
92.85% <92.85%> (ø)

lib/solution/src/day12/grid.rs
96.25% <96.25%> (ø)

lib/solution/src/day12/mod.rs
98.57% <98.57%> (ø)

bin/aoc2022/src/main.rs
94.02% <100.00%> (ø)

lib/aoc/src/math.rs
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Tooltip text underlined twice with yellow color

Steps to Reproduce
This seems to affect every Tooltip, but can most easily be seen by creating a new flutter project, running it, and long-pressing the floating action button:
flutter create test_tooltip
cd test_tooltip
flutter run

The tooltip shown after long-pressing the fab shown looks like this:

As far as I can tell, this has been introduced in the latest alpha update, but also occures on master.
Flutter Doctor
[✓] Flutter (on Linux, locale de_DE.UTF-8, channel alpha)
    • Flutter at /home/simon/bin/flutter
    • Framework revision 4424892c79 (vor 4 Tagen), 2017-10-10 16:45:11 -0700
    • Engine revision 2a84f18c79
    • Tools Dart version 1.25.0-dev.11.0

[✓] Android toolchain - develop for Android devices (Android SDK 26.0.1)
    • Android SDK at /home/simon/Android/Sdk
    • Platform android-26, build-tools 26.0.1
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] Android Studio (version 2.3)
    • Android Studio at /opt/android-studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.2)
    • Flutter plugin version 18.1
    • Dart plugin version 172.4155.35

[✓] Connected devices
    • GT I9300 • 32305bd8f5c48001 • android-arm • Android 7.1.2 (API 25)

cc @gspencergoog @yjbanov who both worked on relevant parts of the codebase recently


Go to Symbol in Workspace

Type: Bug
I have moved to a new HP All in One PC.  When we search with the above option, system lists the information of  few symbols only from my markdown (.md) files.  Majority of the symbols are not visibile or recognized.
In my laptop, everything is working fine
Please look into this
Thank you
VS Code version: Code 1.73.0 (8fa188b2b301d36553cbc9ce1b0a146ccb93351f, 2022-11-01T15:34:06.111Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-10500T CPU @ 2.30GHz (12 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.78GB (1.48GB free)

Process Argv
--crash-reporter-id 31b6b8c1-20b9-41ee-8513-6cba1293401a

Screen Reader
no

VM
0%

Extensions (52)

Extension
Author (truncated)
Version

add-to-snippet
50P
0.2.1

monokai-charcoal-high-contrast
74t
3.4.0

vscode-m3u
af4
1.0.0

Bookmarks
ale
13.3.1

project-manager
ale
12.7.0

code-sum-up
art
0.1.0

insertnumbers
Asu
0.9.1

All-Autocomplete
Ati
0.0.23

file-properties-viewer
bru
1.0.0

dbclient-jdbc
cwe
1.2.1

vscode-autohotkey-plus
cwe
2.7.1

vscode-mysql-client2
cwe
5.9.1

dart-code
Dar
3.52.1

githistory
don
0.6.19

python-environment-manager
don
1.0.4

python-extension-pack
don
1.7.0

xml
Dot
2.5.1

gitlens
eam
13.1.0

remotehub
Git
0.46.0

vbnet
gor
1.0.2

ftp-simple
hum
0.7.6

MagicPython
mag
1.1.0

compare-folders
mos
0.22.3

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.12

remote-containers
ms-
0.262.3

remote-ssh
ms-
0.92.0

remote-ssh-edit
ms-
0.84.0

remote-wsl
ms-
0.72.0

vscode-remote-extensionpack
ms-
0.23.0

remote-explorer
ms-
0.0.2

remote-repositories
ms-
0.24.0

vsliveshare
ms-
1.0.5776

vscode-paste-image
mus
1.0.4

color-highlight
nau
2.5.0

autodocstring
njp
0.6.1

emoji
Per
1.0.1

material-icon-theme
PKi
4.22.0

calc
rai
2.3.1

java
red
1.12.0

LiveServer
rit
5.7.9

vscode-fileutils
sle
3.5.0

vscode-autohotkey
sle
0.2.2

numbermonger
sof
0.5.0

python
tht
0.2.3

pdf
tom
1.2.0

search
use
0.0.1

vscode-java-debug
vsc
0.46.0

vscode-java-pack
vsc
0.25.6

vscode-maven
vsc
0.39.2

vscode-icons
vsc
12.0.1

local-history
xyz
1.8.1

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848cf:30577861
nodejswelcome1:30587005
fc301958:30595537
282f8724:30602487
gswce1:30612156
iaj6b796:30613358
dbltrim-noruby:30604474
f6dab269:30613381

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I am using the latest version

Please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions

Start Extension Bisect

I have done that.  Still the issue exists

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

Will share the screen recording

https://user-images.githubusercontent.com/8948123/203499778-54b764a4-c4f6-4730-ad90-086f7b55c9c9.mp4
Enclosed a video explaining the issue

In the above video, I have mentioned that the Visual studio is opened as administrator.  The issue exists if the visual studio is opened in normal mode also

I have further investigated this issue.  System is displays all symbols in the listing but the same is not getting displayed during search.  Following video explains this
https://user-images.githubusercontent.com/8948123/203737283-d27aedf9-6e3e-48a6-b171-b1b58c8858a8.mp4

Your attention to this problem is highly appreciated.

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

Let me check

I installed latest VS Code Insiders build.  There it is working correctly

In the latest stable version, the issue exists

I checked with installing different versions - Till September update 1.72.2 it is working fine.

Thanks for testing. If it works in insiders, then the issue has likely already been fixed (or one of the extensions / settings you had in the stable version was causing this)
The current insiders will go out to stable sometime this week