xml comment regex

I tried to create an XML comment regex. It works correctly with JS, for example, but fails with logos.
There are two problems, and I feel they are connected.

I had to add --[^->]|-{3,}[^->] instead of just |-{2,}[^->] as it did not work this way.
It has -{2,}> in the end but only accepts --> as the end, but not ---> or ---->.

use logos::Logos;

#[derive(Logos, Debug, PartialEq)]
#[logos(skip r"\s*")] // Ignore this regex pattern between tokens
enum Token {
    /*
       <!-{2,} - match start of the comment with any number of hyphens
       (
           [^-] - match anything that is not a hyphen
           |-[^-] - single hyphen
           |--[^->] - two hyphens
           |-{3,}[^->] - three or more hyphens
       )* - match anything that is not a comment end
       -{2,}> - match end of the comment with any number of hyphens (this does not work)
    */
    #[regex(r"<!-{2,}([^-]|-[^-]|--[^->]|-{3,}[^->])*-{2,}>")]
    XmlComment,
}

fn main() {
    let mut lex = Token::lexer(
        r#"
			<!--- this is a comment, it contains - -- --- ---- and -> and it is ok -->
			<!--- this is a comment and it failes as it has more than two hypens in the end --->
		"#,
    );

    dbg!(lex.next());
    dbg!(lex.next());
    dbg!(lex.next());
}

Hello @romamik! I think your issue is generally related to the fact that Logos doesn't like "greedy patterns". I.e., you should usually use negation instead to find the next of a comment. However, you could also probably used callbacks and bumps. Here is some pseudocode:

fn callback(lex: &'source mut Lexer<Token>) -> Result<&'source str, MyError> {
    let slice = lex.slice(); // e.g., '<----'
    let pattern = format!("{}>", slice[1..]); // e.g., '---->'
    lex.remainder()
        .find(pattern)
        .map(|index| {
            lex.bump(index + pattern.len());
            lex.slice()
        })
        .ok_or(MyError::UnterminatedComment)
}

#[derive(Logos, Debug, PartialEq)]
#[logos(skip r"[ \t\n\f]+")]
enum Token<'source> {
    #[regex("<!-{2,}", callback)]
    Comment(&'source str),
    ...
}

I wish I knew about bump earlier. It is useful not only in this context, but in other situations as well.

I am happy it solved your issue :-)
@romamik, can you include a minimal code snippet with your solution? So other people coming across this issue will know how you managed it :D

use logos::{Lexer, Logos};

#[derive(Logos, Debug, PartialEq)]
#[logos(skip r"\s*")] // Ignore this regex pattern between tokens
enum Token<'src> {
    #[regex("<!-{2,}", |lex| skip_comment(lex))]
    XmlComment(&'src str),
}

fn skip_comment<'src>(lex: &mut Lexer<'src, Token<'src>>) -> Result<&'src str, ()> {
    let mut open_count = 1;
    loop {
        let rem = lex.remainder();
        let close_pos = rem.find("-->").ok_or(())?;
        let open_pos = rem.find("<!--");
        if let Some(open_pos) = open_pos {
            if open_pos < close_pos {
                open_count += 1;
                lex.bump(open_pos + 4);
                continue;
            }
        }
        lex.bump(close_pos + 3);
        open_count -= 1;
        if open_count == 0 {
            break;
        }
    }
    Ok(lex.slice())
}

fn main() {
    let mut lex = Token::lexer(
        r#"
			<!--- this is a comment, it contains - -- --- ---- and -> and it is ok -->
			<!--- this is a comment and it failes as it has more than two hypens in the end --->
			<!-- <!-- nested comment --> -->
		"#,
    );

    dbg!(lex.next());
    dbg!(lex.next());
    dbg!(lex.next());
    dbg!(lex.next());
}

Thanks @romamik! Can you include the terminal output to show the debug prints?

I've edited the message to include debug prints.

Thank you! Closing now :-)

I just discovered, that it is possible to skip comments in Lexer instead of ignoring them in code later. It is stated in the documentation, but I missed is somehow.
use logos::{Lexer, Logos, Skip, Span};

#[derive(Logos, Debug, PartialEq)]
#[logos(skip r"\s*")] // Ignore this regex pattern between tokens
enum Token<'src> {
    #[token("<!--", |lex| skip_comment(lex))]
    XmlComment,

    #[regex("<[a-zA-Z0-9-]+", |lex| &lex.slice()[1..])]
    TagOpen(&'src str),

    #[token("/>")]
    TagClose,
}

fn skip_comment<'src>(lex: &mut Lexer<'src, Token<'src>>) -> Skip {
    let mut open_count = 1;
    loop {
        let rem = lex.remainder();
        let close_pos = rem.find("-->").expect("unterminated comment");
        let open_pos = rem[..close_pos].find("<!--");
        if let Some(open_pos) = open_pos {
            open_count += 1;
            lex.bump(open_pos + 4);
            continue;
        }
        lex.bump(close_pos + 3);
        open_count -= 1;
        if open_count == 0 {
            break;
        }
    }
    Skip
}

fn main() {
    let mut lex = Token::lexer(
        r#"
			<!--- this is a comment -->
        <tag-name
			<!--- this is a comment inside tag (that's weird, but why not?) --->
        />
		"#,
    );

    assert_eq!(lex.next(), Some(Ok(Token::TagOpen("tag-name"))));
    assert_eq!(lex.next(), Some(Ok(Token::TagClose)));
    assert_eq!(lex.next(), None);
}


Fix redefinition of the html_context in the docs/conf.py

fixes look of the "tabs", html_context was redefined in #4583, so here's a little fix 😀
(GH-4634)
This pr can be just merged as it contains only one commit
I checked, banner remains, so we're ready to go

Thanks


Basic editor GUI

Added

ImGui (Submodule)
EditorGUI (Static class)

I will make more widgets in EditorGUI, just put this up so people can see. When docking and viewports come to imgui-beef I will make sure to support that too.

Dependencies should be added to the Workspace and Editor project.

I will look into the other JSON library so that may fix the style serialization issue


Improve Envoy crash logging

While core dumps are often better for in-depth debugging we've found that a high percentage of bugs can be debugged a bit more quickly with a combination of stack trace and information about the stream which caused the crash.
To start with I'd love to replicate what we have for L7 debugging in-house, where we track and dump active session.   Essentially each active stream in each worker thread registers itself with a scoped thread-local object on all dispatcher entry points, and the crash signal handler logs a bunch of information about active stream on segfault.  This is super useful for debug but for consistent state dumping, every alarm and IO entry point has to create a scoped tracker for traces (worse case you just miss out on debug info)
It'd be a bunch of code churn but I don't think it's terrible to have an Printable interface with dumpState() function which various  stream / hcm / connection interfaces can implement, and have L7 alarms and IO entry points (interested folks could implement for L4 as well, if inclined, we'd likely not need that for some time) which latch a thread-local-storage Printable interface for the stream.   the dumpState functions can also be quite helpful in debug/error logging, especially for ASSERTs/RELEASE_ASSERT as they generally have enough information about state to help assess what went wrong.
Checking in with @envoyproxy/maintainers before I go off code spelunking, both for if we're up for the extra APIage and plumbing, and if you all have lower hanging fruit which might make sense to tackle first.

@alyssawilk at a high level this sounds interesting and useful to me. My only concern would potentially be around perf but I think we can make it light weight enough or potentially make it opt-in with a null implementation or something like that.
Also, I think we should sync up with @htuch before you start doing significant coding. I have been discussing with him some ways we might due per-tenant accounting in the future, and there is some overlap I think on the plumbing required. It would be good to make sure we cover both cases so we don't have to do it twice...

I think the base implementation is setting and clearing a pointer on alarm entry, so should be fine from a perf perspective.  I agree once we have scoped "entering a session" objects we can also use them for attribution and that'd be more perf heavy.  I'll start on sessing logging utils and printable APIs which shouldn't overlap, and try to save the scoped entry points for when htuch@ is back online.

Chatting with @yanavlasov today, he had the idea that GDB scripts to crawl the core would provide both the information of interesting ^^ and also provide a form of documentation on "how Envoy works", i.e. the key relationship between data structures. I think what @alyssawilk is working on is generally interesting, but just thought I'd point out the potential confluence between these.

Envoy specific GDB scripts would be amazing!

+1 - if we could "auto" generate debug info from crashes that'd be awesome.  Bonus points for flags to redact obvious PII.


Don't explicitly call _onUnregistered in unregisterApp()

The distributor is supposed to invoke this callback when the instance has been successfully unregistered.

That makes sens, thanks


Allow JHipster sample to compile to native

As discussed with @sdeleuze on Twitter, I created a sample JHipster project and configured it using Spring Native.
-> here's the ticket will all information on the JHipster side: https://github.com/jhipster/generator-jhipster/issues/13733
The 2 first problems are:

The logback file makes startup fail (you can go past this by removing the file)
There is an error concerning the HttpStatus class. As we're using Undertow, I tried to migrate to Tomcat, but that didn't help.

Thanks Julien, let's try to see if we can make it in time for 0.9.1 otherwise we will move it to 0.9.2.

FYI We are working on solving various issues you encountered via other issues:

Logback #625
HttpStatus #612
Make sure AOT compilation is invoked : #623 and #593

I had a deeper look to your JHipster sample app.
After removing logback-spring.xml due to #625, and @EnableJpaAuditing(auditorAwareRef = "springSecurityAuditorAware") because not supported yet, I faced this error Binding to target [Bindable@cc33e78 type = tech.jhipster.config.JHipsterProperties] failed.
Spring Native is supposed to recognize @EnableConfigurationProperties usages and register reflection entries properly but here, I am not sure how JHipsterProperties is registered. I see this in jhipster-framework spring.factories:

Could you share more context about how JHipsterProperties is registered and why?

@EnableJpaAuditing(auditorAwareRef = "springSecurityAuditorAware") should be removed anyway, this comes from my very early code and I now believe this was a bad idea.
For JHipsterProperties, I believe this is also my fault -> shouldn't it be listed here, in the spring.factories? I thought it was the correct way to register some custom properties (and it works!), but I haven't studied that at all

For JHipsterProperties, the recommended way to do it is probably to specify @EnableConfigurationProperties(JHipsterProperties.class) on a configuration classes imported by a spring.factories.
I am moving this issue to 0.9.2 since that's mostly a tracking issue for other more fine grained issues in order to have your basic sample working and since that will require update on your side for JHipsterProperties. Please let me know when I can test again.

Oh sorry, this is probably what I did - and so listing it in spring.factories should be a mistake. I'll have a look.

Let's continue the work and discussion on https://github.com/jhipster/generator-jhipster/issues/13733 to avoid duplication.


Skip failing book tests

Skip these two book tests for now.
Tracking it here: https://github.com/microsoft/azuredatastudio/issues/20589

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.03%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
28007

Relevant Lines:
62039

💛  - Coveralls


Update hyper.rb

The hyperterm directory used for extensions &c. was marked as ~/.hyper_modules, when it's actually ~/.hyper_plugins.
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for your contribution.


FancyZones - Per zone hot key sequences

Individual Hot Key to target snapping of a selected window to a specific zone
As a user, I would like the ability to create customized, individual hot key sequences to snap a selected window to a specific zone in FancyZones.
As an example, imagine if I laid out my zones in a 3x3 grid. This is similar to a keyboard number pad. As a result, I would like the ability to create individual hot keys so that I could say type 'Ctrl + Alt +1' to snap a selected window to the lower left zone in my 3x3 zone arrangement. I could also type 'Ctrl + Alt + 9' to snap a different selected window to the top right zone in my 3x3 zone arrangement.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Duplicate of #1411


Code 500 error

{"code":500,"error":"Block-scoped declarations (let, const, function, class) not yet supported outside strict mode"}
How can I fixed this? its about NodeJs version?

You should be using Node 4.0 > 0


How can I edit the name of all columns?

In Tidyverse I could do this to remove all "/" symbols in column names:
rename_with(~ str_replace_all(., "/", ""))
Is there a way to do this in a Tidier chain?

rename_with isn't implemented yet. There is a way to do this within a chain using existing Julia syntax. Will share in a bit, but either way will leave this issue open until we implement rename_with.

below is a very preliminary rename_with macro that can be used with str_replace_all in a Tidier Chain to accomplish your goal.
using DataFrames: rename

df = DataFrame("A/B" => [1, 2])
macro rename_with(df, func)
    return quote
        cols = names($(esc(df)))
        new_cols = map(c -> $(esc(func))(string(c)), cols)
        rename_map = Dict(zip(cols, new_cols))
        rename($(esc(df)), rename_map)
    end
end

@chain df begin
    @rename_with( str -> str_replace_all(str, "/", ""))
end

@rename_with(df, str -> str_replace_all(str, "/", ""))

Of note, plz use the most recent TidierStrings version (not yet released because there are a few other changes I am planning before releasing still, so u will have to first update via ] add TidierStrings#main )

@rename_with() has been added to v0.13.0 and is now merged.


add-enable-pandas-copy-on-write-mode-checker

Copy-on-Write was first introduced in version 1.5.0. Starting from version 2.0 most of the optimizations that become possible through CoW are implemented and supported. All possible optimizations are supported starting from pandas 2.1.
CoW will be enabled by default in version 3.0.
References
https://pandas.pydata.org/pandas-docs/stable/user_guide/copy_on_write.html#copy-on-write-cow

https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#indexing-view-versus-copy


Add support for xtend_tuya

This PR adds support for Tuya IPC camera using xtend_tuya as a WHEP gateway.
Please don't hesitate to refactor anything that you feel is badly written, I'm not at all a GO developer but I tried my best to keep the code as clean as I could :).
If you want to test this yourself, don't hesitate to contact me at<EMAIL_ADDRESS>This should fix the issue #1345 and is related to issue #315 and PR #1379
Don't hesitate to make any comment.
Have a nice day,
Azerty

My opinion:
go2rtc supports importing WebRTC cameras from Home Assistant through the hass source ([here](https://github.com/AlexxIT/go2rtc#source-hass:~:text=Hub-G3-AB12-,WebRTC Cameras,-(from v1.6.0).
It would be nice if xtend_tuya added this WebRTC support through Home Assistant's standards, hoping that maybe go2rtc's hass source would pick it up without needing an extra source.
Code-wise I know nothing about this, so maybe this comment is completely irrelevant.
In case it is relevant: Home Assistant is overhauling their WebRTC implementation, going away from rtsp_to_webrtc in favor of having go2rtc bundled and even enabled by default in 2024.11.0. Maybe it's better to wait for it before start implementing this.


DialogPreference's dialog disappears on orientation change

When a DialogPreference's dialog, e.g. an EditTextPreference's dialog, is shown and the orientation of the device changes, the dialog will become invisible.

Fixed in version 2.0.5.


Copy Data Between Users Across Dev & Prod

Summary
This PR creates a TypeScript script for the command line to copy a user's data from one user to another, optionally across dev and prod Firebases. Firebase makes it very difficult to copy data between documents in their web interface since there's no way to easily download documents, and it's nearly impossible to upload data using the web interface. The only practical way to move data on Firebase is to use a program with a service account that can get the data for a document and set the contents of another document.
To further investigate #672, we need to make changes to the data for a user with a broken account on prod. However, we cannot and should not change data on prod, so this script is needed to transfer the data to dev where we can safely experiment with it. Only the TPM should use this with prod. However, this script will also allow us to make copies of documents on dev for developers to experiment with.
Test Plan
Run the script from the command line with various arguments in preview mode (EXECUTE=FALSE) and actually copy between documents on dev (e.g. copy from your account on dev to another google account that you have). You don't actually have to copy to another user if you want; the "user" only refers to the name of a document, so you can name your documents what you want. However, you'll need an email that corresponds to the document name to actually use the data. I recommend only having the dev service account in your repo at first until you have thoroughly read through the code and are confident that it will behave as it is supposed to once a prod service account credentials are in the repo.
Again, it is very important to read through the code because a prod service account grants the ability to mess with our data on prod if the script has an error that I didn't notice.

If we're going to be parsing command line arguments, I think it would be better to use a CLI library. That way, we can have named arguments for the source and destination, as well as switches for boolean arguments.

@zachary0kent

If we're going to be parsing command line arguments, I think it would be better to use a CLI library. That way, we can have named arguments for the source and destination, as well as switches for boolean arguments.

That sounds good! I've only ever manually handled command line arguments, let alone done anything with the command line in TypeScript. What do you suggest?

@zachary0kent

If we're going to be parsing command line arguments, I think it would be better to use a CLI library. That way, we can have named arguments for the source and destination, as well as switches for boolean arguments.

That sounds good! I've only ever manually handled command line arguments, let alone done anything with the command line in TypeScript. What do you suggest?

I think the minimist package would be good here. yargs is fun and pirate-themed, but also likely a little overkill.

@zachary0kent

If we're going to be parsing command line arguments, I think it would be better to use a CLI library. That way, we can have named arguments for the source and destination, as well as switches for boolean arguments.

That sounds good! I've only ever manually handled command line arguments, let alone done anything with the command line in TypeScript. What do you suggest?

I think the minimist package would be good here. yargs is fun and pirate-themed, but also likely a little overkill.

Would that work fine with how we run typescript using npm run ts-node which then calls ts-node -T -P tsconfig.node.json?

@zachary0kent

If we're going to be parsing command line arguments, I think it would be better to use a CLI library. That way, we can have named arguments for the source and destination, as well as switches for boolean arguments.

That sounds good! I've only ever manually handled command line arguments, let alone done anything with the command line in TypeScript. What do you suggest?

I think the minimist package would be good here. yargs is fun and pirate-themed, but also likely a little overkill.

Would that work fine with how we run typescript using npm run ts-node which then calls ts-node -T -P tsconfig.node.json?

Yeah I think it should be fine.

Wow PR #711. Go team!
Just wanted to say hi this is Han I was a former PM at CoursePlan

minimist can be a dev dependency. Also, I think fromUser and toUser should be separate arguments, instead of being bundled into the argument for the source/destination environment.

I think it's nice to have them in one argument because it refers to a pseudo path to the user's data. Also, the command gets very long with 5 separate arguments.

minimist can be a dev dependency. Also, I think fromUser and toUser should be separate arguments, instead of being bundled into the argument for the source/destination environment.

I think it's nice to have them in one argument because it refers to a pseudo path to the user's data. Also, the command gets very long with 5 separate arguments.

That's true--I think what I mainly take issue with is how easy it is to enter arguments in an incorrect format. How would you feel about having the from and to environment arguments being switches instead (i.e. --fromDev or --fromDev=true)? I also think we should print an error if any arguments (like the user) are invalid.

There is currently no way to roll back changes, eg. if the script fails halfway through (db atomicity). Should there be? Maybe we want a way to back up data 😱
Yes, this is dangerous. I could catch all the errors, store the data I'm overwriting, and then write that data back to the doc. It's an interesting problem because there's many things that could fail… even just writing the data back to the doc could cause issues.

We should keep in mind that dev and prod could have different schemas. Maybe we should keep a log of database copies between environments just in case something breaks
I was thinking that maybe we could run through the data we're replacing to "understand" if our new data will match the schema, but honestly that wouldn't be too useful especially if we're trying to copy to dev to understand a broken doc. Writing to prod is a lot more dangerous and it would be good to have an invariant checker to ensure that the data we write is okay, but honestly we should never write to prod from this. So, I think we can maybe get away with blindly copying data to dev because there's no harm in breaking our own dev users. Can you explain what you're thinking with the log? Are you talking about a way to revert back?

I'll read more later. Thanks for the review Ben!!!

Yes, this is dangerous. I could catch all the errors, store the data I'm overwriting, and then write that data back to the doc. It's an interesting problem because there's many things that could fail… even just writing the data back to the doc could cause issues.

We can probably just accept that we can't guarantee atomicity and rerun the script if it failed midway.

Writing to prod is a lot more dangerous and it would be good to have an invariant checker to ensure that the data we write is okay, but honestly we should never write to prod from this. So, I think we can maybe get away with blindly copying data to dev because there's no harm in breaking our own dev users.

This is a good point. I agree

How would you feel about having the from and to environment arguments being switches instead (i.e. --fromDev or --fromDev=true)?

I like this approach better, except it should be for dev by default and there should be a switch to run it in prod. Similarly, for execute=true, it should be false by default (our previous scripts used a --dry-run switch but I think it should be a dry run by default).

Could you incorporate this? Let me know if you need some clarification

@noschiff looking good! Can you

change ts-node to npm run ts-node in the pr description
change the example command in the script documentation to not include --execute
pretty print the output json so it's not on a single line


[fix][ci]duplicate modernizer-maven-plugin config in pulsar-metadata

duplicate modernizer-maven-plugin config in pulsar-metadata
maven warn:
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-metadata:jar:2.11.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.gaul:modernizer-maven-plugin @ line 166, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

@MarvinCai

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@youzipi you can try to merge the nightly master by click the "Update Branch" button and rerun the test.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

"OWASP Dependency Check" is unrelated to this patch.

@hangc0276 @codelipenghui


Unable to configure custom domain

Please provide us with the following information:

This issue is a: (mark with an x)

[ ] bug report -> please search issues before submitting
[x] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
After I import my domain certificate, it is not available to be selected in the dropdown menu when adding a custom domain.
Steps to reproduce

Add new domain and validate the domain
Create new certificate
Certificate is not available to be selected from the dropdown

Expected behavior [What you expected to happen.]
Certificate to be available to be linked with the domain
Actual behavior [What actually happened.]
Certificate is not available
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Ex. Did this issue occur in the CLI or the Portal?

Having same issue, certificate were ordered via portal.

We removed a validation in the portal that was only looking at CN and ignoring SAN. This fix has been rolled out (early this week). Can you try again?


On removed tumblr iframe just 404, not false positive bug to STDOUT

You might want to also do this for other sites, because it's filling my output with bugs that aren't bugs just 404s. That first '''WARNING''' message before the first '''ERROR''' and then process stop would have sufficed.
youtube-dl --verbose http://taintedkayla.tumblr.com/posts/1133366857
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'http://taintedkayla.tumblr.com/posts/1133366857']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.06.15
[debug] Python version 2.7.9 - Linux-3.19.0-20-generic-x86_64-with-Ubuntu-15.04-vivid
[debug] exe versions: avconv 11.2-6, avprobe 11.2-6, rtmpdump 2.4
[debug] Proxy map: {}
[generic]<PHONE_NUMBER>: Requesting header
WARNING: Could not send HEAD request to http://taintedkayla.tumblr.com/posts/1133366857: HTTP Error 404: Not Found
[generic]<PHONE_NUMBER>: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 312, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 1730, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

IE this isn't a youtube-dl problem but a site problem and shouldn't generate a bug report.

Some websites responds a 404 for wrong input parameters. In such cases it's really youtube-dl's problem, for example #4281. There's no simple way to determine whether 404 is simply NOT FOUND or something different. As a result, keeping reporting 404 is reasonable.
I'm closing this ticket as I think there's nothing need to be changed in youtube-dl.


Tracking/leading naming consistency

I was wondering if you'd be open to renaming the larger variants of the tracking/leading utilities to match. It's caught me up a couple of times where I had expected tracking-loose to work and had to end up reaching for the docs.

I think loose would be preferable to wide for two reasons:

It works better as a description in both horizontal and vertical directions.
It sounds more like the opposite of tight.

You can change this in your config file if you like 👍 Going to keep them as-is in the default configuration at the moment though, as "wide letter-spacing" and "tight letter-spacing" is the generally accepted language in typography.
Can see examples on Wikipedia here:
https://en.wikipedia.org/wiki/Letter-spacing


my_config.vim didn't work?

Hi, i'm "working" with vim for many years, but never the way it's meant to be. I used it more than a Text-gui-editor.
Nevertheless, i wan't to increase my skills now and teaching me by viewing some yt-vids and reading (yes i do this) and so i stumbeld over vim_runtime. I try to use this on my maschines i logged into.
I try to use a own-config and create the my_config.vim file and set there some options.
So and thats the issue: how do i know that my_config would be used? I set this option:
set relativenumber
but this isn't be stored and every time i start vim, i have to set it manualy. So how could i check tha my_config.vim would be used?
Thanks.

I'm having trouble with my_configs.vim as well.
I'm trying to override the colorscheme in ~/.vim_runtime/my_configs.vim but it doesn't get applied.

Try to ensure that your ~/.vimrc looks like this:
set runtimepath+=~/.vim_runtime

source ~/.vim_runtime/vimrcs/basic.vim
source ~/.vim_runtime/vimrcs/filetypes.vim
source ~/.vim_runtime/vimrcs/plugins_config.vim
source ~/.vim_runtime/vimrcs/extended.vim
source ~/.vim_runtime/my_configs.vim

You likely have an error in your my_configs.vim file 👍


run-android stuck on starting: intent

After installing and importing react-native-easy-grid 0.1.17 running:
react-native run-android
is now stuck at
Starting: Intent { cmp=com.awesomeproject/.MainActivity }

@Thomasin500 Looks like this is an issue with adb.  See this StackOverflow question

That fixed the 'adb' problem so thank you, but I think I'm still missing some. Firing up the example from the readme does not show the grid as expected.

@Thomasin500 just give some background color for <Col/>.
Screenshot

Sample code
import React, { Component } from 'react';
import { Col, Row, Grid } from 'react-native-easy-grid';
export default class App extends Component {
  render() {
    return (
      <Grid>
      <Col style={{backgroundColor:"red"}}></Col>
      <Col style={{backgroundColor:"blue"}}></Col>
  </Grid>
    );
  }
}

got it! thanks!


🐛 Task :react-native-vision-camera:compileDebugKotlin FAILED on React Native 0.71.3 Android Platform

What's happening?
When installing react-native-vision-camera in a React Native 0.71.3 project, the compilation for Android fails with the error: Task :react-native-vision-camera:compileDebugKotlin FAILED. This issue occurs with both the latest versions of v3 and v4 of the react-native-vision-camera module.
I even tried changing the kotlinVersion to "1.7.0" but it still didn't work
Reproduceable Code
Running command `npx react-native run-android` in the terminal

Relevant log output
Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':react-native-vision-camera:compileDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

Camera Device
NA

Device
Android Pixel Simulator
VisionCamera Version
4.6.3
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Same here
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/FpsSampleCollector.kt: (28, 30): Overload resolution ambiguity:
public final operator fun minus(other: Byte): Long defined in kotlin.Long
public final operator fun minus(other: Double): Double defined in kotlin.Long
public final operator fun minus(other: Float): Float defined in kotlin.Long
public final operator fun minus(other: Int): Long defined in kotlin.Long
public final operator fun minus(other: Long): Long defined in kotlin.Long
public final operator fun minus(other: Short): Long defined in kotlin.Long
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/FpsSampleCollector.kt: (41, 21): Overload resolution ambiguity:
public final operator fun div(other: Byte): Double defined in kotlin.Double
public final operator fun div(other: Double): Double defined in kotlin.Double
public final operator fun div(other: Float): Double defined in kotlin.Double
public final operator fun div(other: Int): Double defined in kotlin.Double
public final operator fun div(other: Long): Double defined in kotlin.Double
public final operator fun div(other: Short): Double defined in kotlin.Double
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/extensions/List+toJSValue.kt: (9, 8): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/extensions/List+toJSValue.kt: (9, 28): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/extensions/ViewGroup+installHierarchyFitter.kt: (9, 3): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/extensions/ViewGroup+installHierarchyFitter.kt: (10, 68): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/extensions/ViewGroup+installHierarchyFitter.kt: (12, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/extensions/ViewGroup+installHierarchyFitter.kt: (16, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (9, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (10, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (10, 41): Unresolved reference: stackTraceToString
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (12, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (19, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (20, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (21, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/CallbackPromise.kt: (22, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/withPromise.kt: (8, 3): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/withPromise.kt: (10, 13): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/withPromise.kt: (12, 7): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class
e: /Users/duduneto/Dev/foxbox/VersapayMobile/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/react/utils/withPromise.kt: (14, 13): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/duduneto/.gradle/caches/transforms-3/a4392289346230b43647c03e09a39d82/transformed/jetified-kotlin-stdlib-1.9.21.jar!/kotlin/Unit.class

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':react-native-vision-camera:compileDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 5m 13s

React Native:
0.71.2
VisionCamera Version:
4.6.3
kotlinVersion=1.7.0


Remix ASTWalker ts

Extract AST walker as a separate module.
Typescript
Eventemitter with callback support

together with this PR should we mark the astwalker code in remix-lib as deprecated?

We can mark remix-lib astWalker code as deprecated. I will try to use remix-astwalker in remix-lib and see if the tests passes.

@yann300 I was trying the deprecation process locally. We need to make small changes in remix-lib to make the new AstWalker module work. We need to change var AstWalker = require('./astWalker') to var AstWalker = require('remix-astwalker').AstWalker to make the new module work. We can make these changes once we have released first version of remix-astwalker. Also I have checked that remix-ib passes tests with new remix-astwalker module. :+1:

We can find some references about AST on following links:

https://github.com/ethereum/solidity/blob/develop/libsolidity/ast/AST.h

i think it just need a little rebasing ;)

how is it possible that the diff contains some commits already merged?

I did
git checkout remix-lib-ts
git rebase master
git pull
git push origin master

If I remember correctly this happened earlier as well. What am I doing wrong ? @yann300

perhaps check that your master is actually up to date
git fetch origin/master
git rebase origin/master

Yes master is updated with origin. :confused:

I think we could just restart from another branch and put the code under the folder remix-astwalker in a single commit in order to get rid of all these already-in commits.

PR moved to #1156


Paket.Init should place Paket binaries in CWD

I'm really enjoying using F# with Paket in Atom. But I think the Paket.Init command should not only create the paket.dependencies etc. in the current working dir (where my current file resides) but also create the .paket folder and place the paket.bootstrapper and paket.exe there so one does not have to copy them there manually every time.
A nice bonus would be to add paket.exe to the .gitignore so only the bootstrapper gets commited.

I think this should implemented in Paket.Core. Would love to see a pull request.

How should that be implemented? Maybe add a function that takes a path and adds Paket there if it does not exist? Or modify the existing Init?

I think we should modify the original init function and create the
structure we usually assume.
2015-06-01 10:36 GMT+02:00 Stefan Reichel<EMAIL_ADDRESS>
How should that be implemented? Maybe add a function that takes a path and
adds Paket there if it does not exist? Or modify the existing Init?
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket.Atom/issues/14#issuecomment-107364115
.

There's also the auto-restore command which already downloads the bootstraper into .paket dir. It does a few things apart from that however

So this can be put into it's own function and be called from init and auto-restore?

yeah I think so

OK, my implementation is almost ready. Need to check if the files already exist (the skip download) but the refactoring is done. I hope I have enough time tonight to finish it. If not, it will be ready tomorrow.


Use git name-rev as a fallback for branch name

This would replace the current usage of git show-ref, which displays
commit hash when in detached HEAD, and bring it in line with how the Zsh
version displays branches.
When .git/HEAD is a hash and not a ref (e.g. when you git checkout HEAD~#
where # is some number of commits behind HEAD), it shows only
the hash.
One oddity to this approach is, if you have many branches or refs
containing common commits, the branch can show as stash~2,
pullreqs/3071~1, or fix-colored-yes-perf~1, for example. Because
this method is more descriptive, I consider this acceptable and better than
the current behavior of only showing the commit hash when in detached
HEAD.

I tend to agree with this behavior👍
@cole-h Are you willing to add a test for this? If not that’s okay, I can look into it in the coming days☺

The test passes on my end, so I have no idea why it's failing on Travis.
I used sudo make build-pure-on FISH_VERSION=2.7.0 && sudo docker run --name test-pure-on-2.7.0 --rm --interactive --tty pure-on-fish-2.7.0 (and 3.0.0).

@cole-h thank you kindly!☺


Add nodeadm PR checks

Description of changes:
Adds the build, test, and test-e2e make targets for nodeadm to the PR workflow.
Also adds a check to ensure any generated code is up-to-date.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I'll rebase once #1566 is in.


Error trying to locate the pr template file when exists

On trying to run the k8s-promoter manually, I'm getting the following error:
 FATA[0000] manifest.New: descriptionBuilder: ManifestRepository is missing PR template. A template is expected at .github/PULL_REQUEST_TEMPLATE/master.md

This is despite the file, with the path above, being in both the main (gitops) repository and the config repo.

Hey @johnfoxcloudreach
Thanks for reporting!
Do you mind sharing a bit more information to help us diagnose this problem?

How is k8s-promoter started? Full command would be useful.
Are your main (gitops) repository and config repository two separate git repositories?
Would you be able to share the directory layout of git repositories that you use with k8s-promoter? The output of tree should be enough.

Here's the command trying to use
./bin/k8s-promoter \
  --owner johnfoxcloudreach \. # github user
  --repository k8s-gitops-flux-config \ # my flux gitops repo
  --target test \ # name of the environment from clusters.yml
  --commit-range<PHONE_NUMBER>58f8c660b6e144c4567bb198ddb46c...aad529cce66f760068a3261a83113ddbf5d4a60c \ # commits with app going into dev
  --config-repository k8s-promoter-config \ # my config with clusters.yml detailing name and paths to environments
  --committer-name "Promotion Bot" \
  --committer-email<EMAIL_ADDRESS>\
  --gpg-key-path private.pem # created a gpg key with the above name and trying to use this

Here's the gitops repo that's running flux
├── clusters
│   ├── dev
│   │   ├── flux-system
│   │   │   ├── gotk-components.yaml
│   │   │   ├── gotk-sync.yaml
│   │   │   └── kustomization.yaml
│   │   ├── podinfo-kustomization.yaml
│   │   └── podinfo-source.yaml
│   └── test
│       └── flux-system
│           ├── gotk-components.yaml
│           ├── gotk-sync.yaml
│           └── kustomization.yaml
└── README.md

the k8s-promoter structure:
├── README.md
└── cluster.yaml

Thanks


Error: endorsement failure during invoke. response: status:500 message:"error in simulation: failed to execute transaction 7e04a449d757e86b2b4a1dc0fc752f5670d15f00c28fe20efefef6facb7b641e: invalid invocation: chaincode 'myccc' has not been initialized for this version, must call as init first"

I have installed minifabric. Followed the command mention in the github readme. I am able to query with existing channel.
I created a channel coolchannel.
Then, I copied the simple chaincode and created another one with name myccc. I ran the following command.

./minifab install -n myccc -l go -p '"init","a","200","b","100"'
./minifab approve
./minifab commit
./minifab discover
It was successful. Logs below:
`xxxx@WKMZTAA2E459 mywork % ./minifab discover
Using spec file: /Users/swasaha/mywork/spec.yaml
Minifab Execution Context:
FABRIC_RELEASE=2.3.0
CHANNEL_NAME=coolchannel
PEER_DATABASE_TYPE=golevel
CHAINCODE_LANGUAGE=go
CHAINCODE_NAME=myccc
CHAINCODE_VERSION=1.0
CHAINCODE_INIT_REQUIRED=true
CHAINCODE_PARAMETERS="init","a","200","b","100"
CHAINCODE_PRIVATE=false
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=newest
EXPOSE_ENDPOINTS=false
CURRENT_ORG=org0.example.com
HOST_ADDRESSES=<IP_ADDRESS>,<IP_ADDRESS>
WORKING_DIRECTORY: /Users/swasaha/mywork
.......

Preparing for the following operations: *********************
verify options, discover
.......
Running operation: ******************************************
verify options
.
Running operation: ******************************************
discover
........................
Discover endorsers results **********************************
Chaincode endorsers file: ./vars/discover/coolchannel/myccc_endorsers.json
Discover orderers results ***********************************
Channel orderers file: ./vars/discover/coolchannel/ordererendpoints.json
STATS *******************************************************
minifab: ok=47	failed=0
real	0m15.246s
user	0m12.448s
sys	0m3.402s
xxxx@WKMZTAA2E459 mywork %`

./minifab invoke -p '"query","a"'
Log message:
`xxxx@WKMZTAA2E459 mywork % ./minifab invoke -p '"query","a"'
Using spec file: /Users/swasaha/mywork/spec.yaml
Minifab Execution Context:
FABRIC_RELEASE=2.3.0
CHANNEL_NAME=coolchannel
PEER_DATABASE_TYPE=golevel
CHAINCODE_LANGUAGE=go
CHAINCODE_NAME=myccc
CHAINCODE_VERSION=1.0
CHAINCODE_INIT_REQUIRED=true
CHAINCODE_PARAMETERS="query","a"
CHAINCODE_PRIVATE=false
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=newest
EXPOSE_ENDPOINTS=false
CURRENT_ORG=org0.example.com
HOST_ADDRESSES=<IP_ADDRESS>,<IP_ADDRESS>
WORKING_DIRECTORY: /Users/swasaha/mywork
.......

Preparing for the following operations: *********************
verify options, cc invoke
.......
Running operation: ******************************************
verify options
.
Running operation: ******************************************
cc invoke
..............
Run the chaincode invoke script on cli container ************
non-zero return code
Error: endorsement failure during invoke. response: status:500 message:"error in simulation: failed to execute transaction 9321b5bc6124267326ace94c4f944b23f51134bdb4a768ae63dfec108a5c7ccd: invalid invocation: chaincode 'myccc' has not been initialized for this version, must call as init first"
STATS *******************************************************
minifab: ok=33	failed=1
real	0m8.327s
user	0m6.924s
sys	0m1.510s
xxxx@WKMZTAA2E459 mywork % `
I thought I need to invoke init first, so I tried the following
6. xxxx@WKMZTAA2E459 mywork % ./minifab invoke -p '"init","a","200","b","100"'
But no success, it is also giving me the same error.
`# Run the chaincode invoke script on cli container ************
non-zero return code
Error: endorsement failure during invoke. response: status:500 message:"error in simulation: failed to execute transaction 7e04a449d757e86b2b4a1dc0fc752f5670d15f00c28fe20efefef6facb7b641e: invalid invocation: chaincode 'myccc' has not been initialized for this version, must call as init first"
STATS *******************************************************
minifab: ok=33	failed=1
`
I am stuck. @litong01  can you please help me what I am doing wrong?
Note: I am a beginner. Hence in need of help.

You need to initialize the chaincode as the error said. So try minifab initialize command before you call invoke.

Thanks @litong01  . Closing this issue :)
./minifab initialize -p '"init","a","200","b","100"' solves the issue.


Trouble with Statsample::Bivariate#correlation_matrix

(Original: clbustos/statsample#17)
Hi, I'm in trouble with statsample to do PCA analysis for large data. Does anyone have any good idea?
I want to do PCA alanysis with very large data. (3000 variables, 50 samples)
Then, I wrote this code.
data_raw = IO.readlines('data1.txt').map{|v| v.split }[1..-1]

hash_tmp = {}

data_raw[1..3000].each do |ary|
  hash_tmp[ary[0]] = ary[1..-1].map(&:to_i).to_scale
end

ds = hash_tmp.to_dataset

puts "Input data done!"

cor_matrix=Statsample::Bivariate.correlation_matrix(ds)

puts "cor_matrix was prepared."

pca=Statsample::Factor::PCA.new(cor_matrix)

binding.pry

But the ruby on my mac doesn't return "Cor_matrix was prepared.".
I wrote another code to investigate a cause of this.
# Opening Class to investigate where is bottleneck
module Statsample
  module Bivariate
    class << self
      def covariance_matrix_optimized(ds)
        x=ds.to_gsl
        n=x.row_size
        m=x.column_size
        puts "calculating means..."
        means=((1/n.to_f)*GSL::Matrix.ones(1,n)*x).row(0)
        puts "centering matrix..."
        centered=x-(GSL::Matrix.ones(n,m)*GSL::Matrix.diag(means))
        puts "calculating covariance matrix..."
        ss=centered.transpose*centered
        puts "calculating n..."
        s=((1/(n-1).to_f))*ss
        puts "done!"              #<= This line has executed
        s
      end

      def correlation_matrix(ds)
        vars,cases=ds.fields.size,ds.cases
        if !ds.has_missing_data? and Statsample.has_gsl? and prediction_optimized(vars,cases) < prediction_pairwise(vars,cases)
          binding.pry
          cm=correlation_matrix_optimized(ds)
          binding.pry             #<= This line hasn't executed. :(
        else
          cm=correlation_matrix_pairwise(ds)
        end
        binding.pry
        cm.extend(Statsample::CovariateMatrix)
        binding.pry
        cm.fields=ds.fields
        binding.pry
        cm
      end
    end
  end
end

Then the Ruby return until "done!" and doesn't return from Statsample::Bivariate#covariance_matrix_optimized method.
I haven't seen a Ruby method which doesn't return.
If someone knows a way to solve this problem or investigate cause deeply, please tell me.

has this been solved in the latest release? could you check?


Flexible format and DailyOffsetPartition Parser

Made Timestamped MessageParser to have flexible prefix and partition format for date, hour and minute, also added daily offset partitioning message parser  to support following format to have partiotions backup up per day with hour and minute granularity
/mnt/secor_data/message_logs/backup/28248_12/Log/20161021/02/of fset=0/1_0_00000000000000025658.gz

i have updated the access modifier on the fields , there is no need to override these as they are config settings that are already defined and in essence shouldn't be overridden during execution once defined., please review

Thanks for the contribution


[BUG] Error and never sending MQTT message when face gets matched - "TypeError: MQTT: recognize error: Cannot read properties of undefined"

Thanks a lot for your great work and taking up the ball :)
Describe the bug
After uploading a known face, it gets matched correctly. However after that, an error message is created and the MQTT message never seems to get sent:
Getting error:
error: TypeError: MQTT: recognize error: Cannot read properties of undefined (reading 'DEVICE_TRACKER_TIMEOUT')
Also the MQTT Topic does not get generated, alas this is expected, as it does not ever seem to send the MQTT message.
23-11-13 20:24:48 info: processing manual: a3f9755a-844d-4829-989a-a29e4a71f268
23-11-13 20:24:48 info: Access granted to IP address: ::ffff:<IP_ADDRESS>
23-11-13 20:24:48 info: Access granted to IP address: ::ffff:<IP_ADDRESS>
23-11-13 20:24:48 info: done processing manual: a3f9755a-844d-4829-989a-a29e4a71f268 in 0.23 sec
23-11-13 20:24:48 info: {
  id: 'a3f9755a-844d-4829-989a-a29e4a71f268',
  duration: 0.23,
  timestamp: '2023-11-13T19:24:48.445Z',
  attempts: 1,
  camera: 'manual',
  zones: [],
  counts: { person: 1, match: 1, miss: 0, unknown: 0 },
  matches: [
    {
      name: 'ufo',
      confidence: 100,
      match: true,
      box: [Object],
      type: 'manual',
      duration: 0.2,
      detector: 'aiserver',
      filename: 'ccaf237e-1df6-4a42-a299-1e1503ce402a.jpg'
    }
  ],
  misses: [],
  unknowns: []
}
23-11-13 20:24:48 error: TypeError: MQTT: recognize error: Cannot read properties of undefined (reading 'DEVICE_TRACKER_TIMEOUT')
    at /double-take/api/src/util/mqtt.util.js:280:29
    at Array.forEach (<anonymous>)
    at module.exports.recognize (/double-take/api/src/util/mqtt.util.js:239:13)
    at module.exports.start (/double-take/api/src/controllers/recognize.controller.js:185:10)
23-11-13 20:24:48 info: undefined
23-11-13 20:24:49 info: Access granted to IP address: ::ffff:<IP_ADDRESS>

Version of Double Take
v<IP_ADDRESS>.1 from 12th of november 2023
Expected behavior
After manually uploading a trained picture / known face via the UI, in case it gets recognised, an MQTT message is sent to the MQTT broker (and in this case a sensor in HA is created).
Screenshots
N/A
Hardware

Architecture or platform: [amd64]
OS: [Home Assistant OS - Linux]

Additional context
Detection is working well so far when manually uploading trained faces. Training is working well.
Please see config (took out comments here for clarity only):
# Double Take
mqtt:
  host: <IP_ADDRESS>
  username: !secret mqtt_username
  password: !secret mqtt_password
  port: 1883
  client_id: double-take

  topics:
    homeassistant: homeassistant
    matches: double-take/matches
    cameras: double-take/cameras

detectors:
  aiserver:
    url: http://<IP_ADDRESS>:32168
    timeout: 15
    opencv_face_required: false

detect:
  match:
    save: true
    base64: false
    confidence: 60
    purge: 168
    min_area: 1000

  unknown:
    save: true
    base64: false
    confidence: 40
    purge: 8
    min_area: 0

Also, there is an old issue with the original double-take, but I found nothing there that would help me: https://github.com/jakowenko/double-take/issues/169

try to add
frigate:
  device_tracker_timeout: 30

into config

Thanks a lot for the hint, that helped. Now the usecase of manually uploading is working so far :)
Without the frigate url set (I am not using frigate but BlueIris), the double-take icon stays red - is that a problem?
Do you have any plans to support additional NVRs like BlueIris? I would be happy to test. It can communicate via MQTT as well (and indeed does here).

OK, understood. Is there a planned way to use it without frigate? It would be great to have it automatically process images, when they are put into a directory - maybe I missed that, sorry, if so.
Regarding BlueIris, I just want to say that it is very, very, very reasonable priced and there is nothing else out there which is as good for small / medium home use, IMO. When I started with this, I tried several solutions (including frigate, but I had the wrong hardware, back then) and I am using it since many years. I am very glad that Ken is keeping it up.
Thanks again for your work and your help!

I will make it possible to use Double-Take without Frigate in the next release.

It's because you use it without Frigate
As a workaround, you can add to the configuration
frigate:
  device_tracker_timeout: 30

The problem has already been fixed in the beta version, the fix will be included in release <IP_ADDRESS>


Feature/issue154

Add delimiter support in config

Hi @dbardi,
Thanks for this. Looks good. I'll merge it in and asap 👍
Just a heads up: After the merge I'll probably move the config node to a CsvExport parent node or something similar, to make its usage more obvious.


infiniteScrollUpDistance is not working

I am getting this error when I include it as in the example.
Template parse errors:
Can't bind to 'infiniteScrollUpDistance' since it isn't a known native property
The (scrolledUp) event is not triggering either with or without including the infiniteScrollUpDistance attribute.
I can get the default (scolled) event to work as expected, just not the scroll up.

What version are you using?

0.1.2
I tried to upgrade to 0.1.3 and I got the typings duplicate warnings (added as another issue) and a dep not found error, so had to switch back to 0.1.2.

0.1.3 is the one with the scroll up stuff, but there is a bug right now with that version I think.

Just upgraded to the 0.1.4 and all is working well now!  Thanks

thanks for cofirming that
fix is on #35


<2.9> Convert test_wl_deployment test to go

Migrated test_wl_deployment test to TestWorkloadDeployment

Backports
v2.9 rancher/rancher#46387
v2.7 rancher/rancher#46393
v2.8 rancher/rancher#46392


Unable install on mac

Bug Description
Starting a fresh install, i cant install via "pip install langflow", in the package  "gotrue*" returns this error => "  WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))': /packages/b8/89/4b1dffdf9cef64f6253875983a8aed1a6e3f6c405cc958f9f315c9846e64/gotrue-2.9.3-py3-none-any.whl.metadata"
Trying to reinstall in same directory, receive different error =>
langflow/venv/lib/python3.12/site-packages/pip/_vendor/resolvelib/resolvers.py", line 457, in resolve
raise ResolutionTooDeep(max_rounds)
pip._vendor.resolvelib.resolvers.ResolutionTooDeep: 200000
Then the installation fails, i'm using macos sonoma 14.7
Reproduction
only "pip install langflow" in your virtualenv
Expected behavior
just i wanna install the new version
Who can help?
No response
Operating System
MacOsx 14.7
Langflow Version
v1.1.1
Python Version
3.12
Screenshot

Flow File
No response

Hi @osoluche
We are aware of the delay with installation via pip install, and we will have a new release with the fix soon.
In the meantime, we recommend installation via uv.
Below is the documentation:
https://docs.langflow.org/get-started-installation


AppFW denyURL pattern breaks strings

The standard line below breaks string formatting:
bind appfw profile  -denyURL q{([ /=]|\t|\n)(ls|rm|cat)([ ;'"&].*)?$} -comment "Command injection attack" -state DISABLED

I think this is addressed with #14


Add DayZ

Implement DayZ, but it doesn't work yet because of a mising part of the configuration file.
I have been working on this for a while now, and I took some inspiration from https://github.com/Greelan/AMPTemplates/tree/dayz to finish the module. The issue that Greelan was facing with BattlEye not starting could be traced back to two startup parameters which, if set, prevent BattlEye to work normal.
-bepath=./battleye

The module is still not working as of now, because the approach mentioned in #development does not work. Providing the startup option -config twice, will result in the game engine taking the last provided option and disregard any other configuration file. Because of that we still lack a solution for this part of the server cfg file:
class Missions
{
    class DayZ
    {
        template="dayzOffline.chernarusplus"; // Mission to load on server startup. <MissionName>.<TerrainName>
					      // Vanilla mission: dayzOffline.chernarusplus
					      // DLC mission: dayzOffline.enoch
    };
};

This part is essential to be able to run a DayZ dedicated server.
Lastly I would like to thank @Greelan for their awesome work and @IceOfWraith for their provided help in #development

Support for config templates is in Nightly.

What's the current blocker on this now that #584 has been resolved?

Time. Lol I think it will work now. I ran into issues with the config.json not wanting to merge with the current version but otherwise just need to test RCON.

Battleye RCON - in particular the 45s timeout and it's flakiness when the server isn't shutdown properly - will likely still be the main issue

This is ready for full testing now. It does not support RCON due to the feature request mentioned above.
For Windows, it defaults to the Original server which is Windows only, but can be changed under SteamCMD and Updates. For Linux it is locked to the Experimental server since it is the only one supporting Linux.
In my testing, the query port does not function on the experimental server, even with my work around to supply the client ID using a variable.
This template took a lot of reworking due to how old it was when first started,. Plus, I don't play DayZ or know how the modding works, so feedback is definitely welcome!

I should note too, since this uses template merging, Veloren was used as an example for the template file. Thanks Greelan!

https://github.com/CubeCoders/AMP/issues/725 is also related for RCon support

Can you double check the docker thing? I have it running fine on my end in the standard ampbase image.

I've made some additional tweaks to the settings, for consistency/clarity etc.
The most substantive change is for the "reverse" settings, such as Disable Crosshair. The previous approach does not work for the initial setting state: although set to True (on) as the default, the setting shows as off. An AMP issue that was discovered long ago.

 Now who reviews it? We've got a conundrum.

BTW, I still get this docker error when attempting to run in Linux on the latest Nightly:
/AMP/dayz/server/DayZServer: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory

Well shit. Now who reviews it? We've got a conundrum.

No? You check my changes, confirm if you agree, I can then still review.
But the docker issues need resolution anyway.

Lol I was kidding.

BTW, I still get this docker error when attempting to run in Linux on the latest Nightly:
/AMP/dayz/server/DayZServer: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory

This is really bizarre. You're running it with default settings? Sure you've grabbed the latest Docker images?

Just did a manual docker pull, has resolved it

Only other point to add is I see Recv-Q in netstat when using 2305, but not when using a much higher port like 2402. I remember on Arma that RCON behaved better when there was separation between ports

You wrote that you removed a redundant rcon port setting, but you removed the RCon password setting

You wrote that you removed a redundant rcon port setting, but you removed the RCon password setting

Typo. Setting still redundant

Just tried out your changes and it seems to work as expected. I was able to connect to the server fine.

So TIL about console and RCON getting the Arma 3 template into shape, which may be relevant to DayZ:
Linux

Has full console output
RegexMatch works (eg on "connected to Steam servers" message)
RCONConnected partly works - the server start is registered so that the Restart/Stop buttons appear, but the server starting notification does not go away
OS_CLOSE does a proper server shutdown so is an alternative to String

Windows

No console output until RCON is connected
RegexMatch is only therefore capable of working on the "Rcon connected" message that appears (more precisely, that appears if RCON is functioning correctly)
RCONConnected partly works, the same as Linux
Immediate suppresses the "Rcon connected" message and seemingly other console output
OS_CLOSE does not do a proper server shutdown (which means RCON does not shut down properly and won't work on the next start, because the BattlEye active file is not removed)
Server stop/restart stops RCON working on the next start (even if the BattlEye active file is not the issue) - the AMP bug still seems present

Upshot of the above

Windows forces the lowest common denominator
Functional RCON is essential to proper server stop and RCON functionality
RegexMatch and String need to be used
The RCON timeout issue needs to be addressed

That's some good sleuthing. Some of it was known already, but it's good to confirm and figure out the rest. In the case of DayZ I'll have to double check but I'm pretty sure the game state was saved with OS_CLOSE in Windows as I was able to leave and come back to the same position in game. I didn't mess with RCON though since... doesn't work anyways in AMP.

Yeah, I was referring to "proper server shutdown" from the perspective of BattlEye viewing it as such and removing the active file.

Of course! I was mainly noting it to verify since I'm not 100% sure on save state. If it doesn't save with an OS_CLOSE then we're dead in the water. If RCON just doesn't work, I'm not concerned really. We can release as-is with the intention that RCON isn't an option for now and will be added later.

That may be an option for DayZ given the server isn't currently on AMP, but I'm a little reluctant to go down that path with Arma as it would remove functionality that is currently there.

Completely agree. Arma is in a good working stat (AFAIK) in AMP right now. Whereas, DayZ has been constantly requested. Getting it out without RCON for now is best in my opinion. But of others disagree, I won't argue.

Completely agree. Arma is in a good working stat (AFAIK) in AMP right now. Whereas, DayZ has been constantly requested. Getting it out without RCON for now is best in my opinion. But of others disagree, I won't argue.

The issue I see is the unclean BattleEye shutdown. BattleEye is not only the servers RCon but also the AntiCheat system. If BE wasnt shutdown properly the server is unable to start a new instance at the next start, thus loosing battleye completely. ( I think this is how it was, but I may misremember since it was a long while ago )

Definitely something to verify. I don't know that the BattlEye RCON and anti-cheat are the same thing though. Even though both are called BattlEye.

I think that needs to be tested, as I think RCON not working might not impact anti-cheat, particularly as they use different ports

Definitely something to verify. I don't know that the BattlEye RCON and anti-cheat are the same thing though. Even though both are called BattlEye.

It's the same server but it is doing two different things

Looks to me on a quick test that the BattlEye server is still initialised even if RCON can't connect in AMP.
In fact, the RCON server still operates when the old active file is retained (the port is opened and I can connect with another client) - it is just that AMP can't connect to it because of the rotating RCON password.

Ahh right... I knew that actually. That's why at one point I had put the $RemoteAdminPassword as a static one. But then Mike shut down that possibility.

https://github.com/CubeCoders/AMP/issues/725
Seems to have been implemented, so re-visiting rcon should now be an option XD

See? All we have to do is complain enough. ;)

Hi @IceOfWraith. Thank you very much for putting the work in to get this done. I have been waiting to be able to move away from other hosting providers for DayZ for a while. Could I just check on what we are waiting for to get this merged back in? I'm hoping to build a few servers on Linux this weekend. Also, if you need help, I'd be happy to pitch in.

Well, unfortunately the new RCON keep alive changes didn't work. So we're waiting on Mike to implement that so we can put it to use here.

They do work. But there is the server restart bug

Lol yupp, just caught up on all the messages. Are you able to enter messages through the console then? Or is that still an issue?

When RCON is working I can. But when the server is restarted, no

What's the state of this right now? Has it been tested since the Packet index issue was fixed?

Given AMP’s BattlEyeRCON is still an issue with Arma 3, I suspect the same is the case for DayZ.

Is possible to host a DayZ server with AMP yet?

Various amendments made to update the template files, including for more recent functionality.


[Android] Accessibility talkback order on meeting screen reordered

Purpose

Reorder talkback focus and announcement on the meeting screen for teams meeting
Reorder talkback focus and announcement on the meeting screen for group meeting
Reorder talkback focus and announcement on the meeting screen for no participant meeting

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Click on join call button and turn on talkback
swipe right left to verify

What to Check
Verify that the following are valid

first join call do not focus on switch camera directly but to the banner and screen first

Other Information

Tested


Check the main page for broken links

Description: You must check on the main page for broken links.
Precondition: The website is up and running

Step 1: Check on the main page for broken links.

Expected result: All links from the main page should work.

Step 2: Check on the main page for broken links on your mobile.

Expected result: All links from the main page should work on your mobile.


Changes to Vagrantfile

Hello,
I would recommend updating the Vagrantfile with

XX.XX.XX.XX and have the user add their address before doing vagrant up.
vapor location now changed. update code
sudo wget toolbox.qutheory.io -O vapor

I just put it together here instead of creating a new PR
Vagrantfile.zip

@paulatwilson +1
Currently the build is failing with the old wget url. Would be great to see the above added


Print container logs in CI

Which issue does this PR close?

Part of #5283
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

This only impacts CI and is non-controversial so merging


Feat/frontend mbr gbr foolproof mechanism

Add friendly alert for MBR should be greater than GBR(both subscription and profile).

Hi @Alonza0314 ,
I am unfamiliar with the zod package, but I think there is a way to add the validation in the type schema instead of creating another validation code.
Maybe you can try zod refine in Google search(? ( I'm not sure XD)

I've checked the DTO schema which all of them are written via zod. I think we can feat this function first and make the validation in another PR for the whole DTO schemas(profile and subscriber) if needed(?

Hi @Alonza0314 ,
I am unfamiliar with the zod package, but I think there is a way to add the validation in the type schema instead of creating another validation code.
Maybe you can try zod refine in Google search(? ( I'm not sure XD)

Hi, @andy89923,
I discussed this with Ian yesterday. For now, we can proceed like this and add the valid part later in the backend.


[WIP] Implement read jobType to simulate load with GET requests

Type of change
Attempt to address https://github.com/kube-burner/kube-burner/issues/575

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[x] Documentation Update

Description
Adds new jobType: read which can be used to simulate load of GET requests
Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

@rsevilla87 I was thinking about problem with high amount of objects spawning many goroutines, limiting amount of concurrent goroutines to QPS probably is not very good idea because based on my use cases I have not that many objects defined in my job while in some jobs I am tempting to set quite high QPS to produce significant load which I think is not unique use case for kube-burner.
I am not very concerned with creating goroutines for every object as I can't imagine sane use-case with hundreds of objects being involved, while setting up QPS to hundreds or even thousands makes alot of sense to me.

@rsevilla87 I was thinking about problem with high amount of objects spawning many goroutines, limiting amount of concurrent goroutines to QPS probably is not very good idea because based on my use cases I have not that many objects defined in my job while in some jobs I am tempting to set quite high QPS to produce significant load which I think is not unique use case for kube-burner. I am not very concerned with creating goroutines for every object as I can't imagine sane use-case with hundreds of objects being involved, while setting up QPS to hundreds or even thousands makes alot of sense to me.

ok, makes sense, let's give it a try, we can always update and improve it in the future. Can you add a simple test case to https://github.com/kube-burner/kube-burner/blob/main/test/test-k8s.bats
Thanks!

@riuvshyn I've added simple read test case seems it is passing on CI, I was unable to run it locally because I don't have required local infra.

@rsevilla87 I've added simple read test case seems it is passing on CI, I was unable to run it locally because I don't have required local infra.

Great!, thank you very much!


Decode OpticalInset cf #1511

fixes #1511

Thanks for spending the time researching this. As I finish up Android O stuff any day now, I'll jump into your two related fixes here. I will write a test to prevent regression and try and tackle any TODOs you have left.

Have some research to do with these Optical Bounds. Don't quite understand them yet enough to rebuild unit-tests about them.
https://plus.google.com/+RomanNurik/posts/RpqbQBzGmGv
https://developer.android.com/about/versions/android-4.3.html#OpticalBounds
https://developer.android.com/about/versions/android-4.3.html#UI

Sorry for the delay on this. It has been merged + a test added to prevent regression.


Register ProximalMethods.jl

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/72306
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 5646c7db7a31d07b6610a1c5ae35a223d38ef58a
git push origin v0.1.0


Add specific error(s) for missing imports

Feature
I'd like a specific error for missing imports on e.g. instantiate_pre.
Benefit
A specific error would give access to the missing import information without parsing the (presumably unstable) message string, and provide access to the missing import's type which is currently inaccessible.
Example code that would benefit from this: https://github.com/fermyon/spin/pull/959/files#diff-3df137e08da293bebdb5cbe1b81fcae6af75992a24c583f47e8040baecbf123aR259
Implementation
Copy the ImportType details into a new error struct:
pub struct UnknownImport {
  module: String,
  name: String,
  ty: ExternType,
}

Expose this info from a method e.g. import(&self) -> &ImportType or just AsRef<ImportType>.
Alternatives

New error type(s) could be returned from relevant methods rather than wrapping in anyhow::Error. This has been discussed in https://github.com/bytecodealliance/wasmtime/issues/3928.

Add some mechanism for returning a list of missing imports, e.g. Linker::missing_imports(&self, module: &Module) -> impl Iterator<Item = &ImportType>. I actually quite like this but it would add additional API surface area.

Sounds reasonable to me to add! Adding this would be adding a new public error type and then documenting on the error and relevant methods where it can show up, and if you'd like to take a stab at implementing that'd be much appreciated!


Session creation is failing with 'Too Many Requests'

We are trying to use Selenoid with GGR, and set up one cluster with 50 nodes per selenoid instance.
VM configuration:
Selenoid: Latest
GGR: Latest
CPU: 32 core
RAM: 32 GB
Suddenly we are seeing many requests are in pending state. Out of 50, 18to 20 are consumed and rest are always pending state.
top command shows, high consumption of IO.  We are also enabling VNC, not sure if it contributes to the network IO.

@dibyaranjan-pg this could be too many parallel sessions for 32 cores.

@dibyaranjan-pg I mean you could try lowering -limit parameter value.

@vania-pooh sure, am trying that now.. I see pending numbers decreased when I bring down the  -limit to 30.  1 core for 1 container looks too low for me, will try to increase it further cautiously and check. Do you have any suggestion to follow here? What should an ideal number of container 1 core cpu can hold?

@dibyaranjan-pg this depends mainly on tested application. So -limit can vary from 1 to 1.5-2 browsers per CPU.


Input/Output

What is needed for this issue to be resolved?

What is needed for this issue to be resolved?

Well, documentation of the haxe.io package and how to use it. Output, Input, FileInput, StringInput, BytesInput... that kind of stuff.

Like this? https://api.haxe.org/haxe/io/index.html

Bytes is important seems that name is not familiar with people mastering POSIX/C terminology and there is considerable implementation there and no description. Also *Data types that seems to represent native objects - and for those the API should be very explicit even listing which native type is used on each platform since users micro optimizing at some point will have to cast them
Use a language in terms of POSIX or C  since that is the common language on most platforms.
haxe.io types are poorly documented. None of them has a description and only few members are documented. This is huge blocker for new people since:

Some types, like Bytes* have names that are unknown in POSIX and in general developers form other platforms are lost
IO types needs to be clearly understood in order to optimally implement IO which is critical
the only workaround is to read the haxe.io package source code it self in order to figure out, more or less, what these types do or optimal performance implementations when

I strongly recommend to mention posix names if there is a straight forward relation ship and other language types and not just mention "words like " native" or "array"  or "int", for example, "BytesData represents a native array of bytes which in general are stored as 8 bit unsigned integers, (integers in 0-255). Each target uses the optimal and minimal implementation, and if supported an ArrayBuffer view to avoid referencing the whole array. for example in C++ an unsigned short[] , in JavaScript an ArrayBuffer in python python.ArrayBuffer, "
Although this might seems exposing  private code, users need to clearly understand exactly what the type represents, at least in terms of POSIX or C in order to implement optimal solutions need
My point, don't be high level here. (this is a feedback for the API not for the manual which it should by more high level, but since it seems the initiative is happening here...) thanks

Well, documentation of the haxe.io package and how to use it. Output, Input, FileInput, StringInput, BytesInput... that kind of stuff.

This section also includes the sys.io functions right? I can write some sections about command line input/process spawn etc


Support HTML embed

This can work using oEmbed as well as pasting HTML
The embed would have a default size that can be overridden either by the embed code or by manually inputing a new field
For this content type will also be able to include a custom SVG icon

Reference: https://iframely.com/try/


Remove stale comment from Thermostat XML.

The relevant fields are nullable in both XML and spec, and the spec issue is long-resolved.

Fast-tracking comment-only change with domain expert approval.


chore: settings.json for Ruff extension in VSCode

I have added the following config to the settings.json file so we can use the Ruff Extension for VSCode for code autoformatting:
    "[python]": {
        "editor.formatOnSave": true, // Enable auto format on save
        "editor.codeActionsOnSave": {
          "source.fixAll": "explicit",
          "source.organizeImports": "explicit" // This lets ruff reorganize the imports
        },
        "editor.defaultFormatter": "charliermarsh.ruff"
    }

By default, it reads the config from pyproject.tomlfile.
I just want to let you know three main key points here that we should take into consideration before merging with dev:

I have enabled formatOnSave option, for me is useful but do you consider that we should enable this for all contributors?
I wanted the Ruff formatter to reorganize the import section of each *.py file. For me it also makes clearer this section, but we can omit it if you feel so.
I have also added exclude = ['tests/*',] in the pyproject.toml file, so ruff does not raise warnings on some double-quoted strings in the tests folder.

Waiting for your response on these 3 keypoints!

Thanks for a nice contribution, @DanielGMorenaFhecor! I have accepted the changes, and even removed the excluded test folder and updated all the code so that it passes all tests 😃


docker container ls  - Provide list of available --filters options

File: engine/reference/commandline/container_ls.md
Currently, it's totally unclear which filters are supported by this command.
Trial and error and googling, led me to find out that the following options work:

-f name=xyz: will filter all matching names
-f name=xyz*: will filter all names that starts with xyz

On the other hand, the following commands are not working:

-f name=xyz*db: you cannot filter names that starts and ends with specific prefix and suffix. Just results nothing without error.
-f image=postgres: does not work and gives this error message: Invalid filter 'image'

I'm not asking for a new feature, I'm just asking to clarify what are the supported filters as part of the documentations, please.
For example, the search command has a perfect Filtering section with example of each one.
Thank you so much

Closing duplicate of https://github.com/docker/docker.github.io/issues/14868


DL directive broken?

i've tried configure UART1 via OS and there was required save speed as LONG value:
  ld IX, uart_config
; ...
uart_config:
    dl 115200
    db 8
; other fields are byte lenght and worked fine

I've got "Invalid mnemonic" error.

The documentation was a little ahead this time. The DL command was in, but with a 'DW24' mnemonic.
Fixed in the last commit, also in /binaries


feat: stop sigprof while calling native

Backgroud

When go received a SIGPROF signal while it is running on sonic's native functions, it will crash duet to missing stack information. At present, sonic doesn't support add stack map for native functions (on plan), thus a work-around way is to set  runtime.prof.hz = 0, thus sigprof() handler won't call gentraceback() which cause crash. After we support make stackmap in future, this behavior will be removed

Benchmark

Get

name                      old time/op    new time/op    delta
GetOne_Parallel_Sonic-16    3.54µs ±39%    4.85µs ±27%  +36.92%  (p=0.004 n=10+9)
GetOne_Sonic-16             14.9µs ±20%    12.7µs ±14%  -14.79%  (p=0.001 n=10+9)

name                      old speed      new speed      delta
GetOne_Parallel_Sonic-16  3.84GB/s ±43%  2.76GB/s ±34%  -28.22%  (p=0.004 n=10+9)
GetOne_Sonic-16            879MB/s ±18%  1009MB/s ±16%  +14.71%  (p=0.004 n=10+10)

name                      old alloc/op   new alloc/op   delta
GetOne_Sonic-16              24.0B ± 0%     24.0B ± 0%     ~     (all equal)
GetOne_Parallel_Sonic-16     24.6B ± 2%     24.6B ± 2%     ~     (p=1.000 n=10+10)

name                      old allocs/op  new allocs/op  delta
GetOne_Sonic-16               1.00 ± 0%      1.00 ± 0%     ~     (all equal)
GetOne_Parallel_Sonic-16      1.00 ± 0%      1.00 ± 0%     ~     (all equal)

flame graph before this PR

flame graph after this PR

fix #310


Consider changing ServerBootstrap configuration interface

I think ServerBootstrap  public interface for EventLoop configuration is somewhat verbose/vague.
The method named 'group' by itself  does not convey much about the passed in EventLoops relationships (group for what purpose?, how?) and it would be very difficult to capture their intrinsic interaction with a short verb. I suggest keeping the “explanation” separate from the configuration interface.
I suggest a more “declarative” interface:
// a short version for the common scenario:
ServerBootstrap b = new ServerBootstrap();
b.eventLoops(NioEventLoop.class)
.channel(NioServerSocketChannel.class);
// an alternate one-liner for advanced configurations
ServerBootstrap b = new ServerBootstrap();
b.eventLoops(NioEventLoop.class, NioEventLoop.class)
.channel(NioServerSocketChannel.class);
//  also having an expressive version would be helpful for newcomers.
ServerBootstrap b = new ServerBootstrap();
b.disptachEventLoop(NioEventLoop.class)
b.channelEventLoop(NioEventLoop.class)
.channel(NioServerSocketChannel.class);
where eventLoops signature:
eventLoops(Class<? extends EventLoop> dispatcherEventLoopClass (or acceptor), Class<? extends EventLoop> channelEventLoopClass)
‘boss’ seems a bit weird...

additional control for manually overriding default instance allocations

eventLoops(NioEventLoop.class, 2, NioEventLoop.class, 2)  // for instanceCount (2 dispatcher / 2 workers).
I think "thread counts"  should be omitted as they are an implementation detail of a higher level abstraction.

No apparent interest.


Every Instance of Multiselect Dropdown calls onClose

I have a several multiselect dropdowns I'm using to filter results in a table.
I want to use the (onClose) event to start the filter method.
It calls the onClose event as many times as I have multiselect dropdowns.
In addition, when inserting into the dom (using *ngif expression), the (onClose) event also fires for every instance

Same is happening with me. Just saw this and I have a feeling its not going to be resolved soon. onClose fires wherever I click on the component.

Also having this issue (v2.10.2). It's inside a NgbDropdown and even opening the dropdown fires the event.

@CuppaLabs I have same issue. The closeDropdown method is being called whenever you click outside the dropdown. If the dropdown is already closed, this is causing the onClose to still get fired.
Angular: 6.2.2
Multiselect: 4.1.1
I have made a change that works on my local. I do not have access to make changes/branches for this repository so please make this change. https://github.com/dadreano/angular2-multiselect-dropdown/commit/78014fa4569ad8c679b45b061c1d5fbf1bc72436

Basing on @dadreano solution, i fixed this problem by overriding the component prototype method with this :
AngularMultiSelect.prototype.closeDropdown = function() {
      if (this.searchInput && this.settings.lazyLoading) {
        this.searchInput.nativeElement.value = "";
      }
      if (this.searchInput) {
        this.searchInput.nativeElement.value = "";
      }
      this.filter = "";
      if (this.isActive) {
        this.isActive = false;
        this.searchTerm$.next('');
        this.onClose.emit(false);
      }
    }

PS important: to apply this solution in all components, you have to implement it in the highest component level (like app.component.html)


Problem with Home Assistant

Hello Guys,
At the beginn, sorry for my bad english.
I also startet with this project and have some Problems with Home Assistant i guess,
My Home Assistant start normal with the basic standart configuration.yaml,
but when I copy the one from the Project (with the updatet one) the Home Assistant dont start or show up.
I install Home Assistant on Windows and my MQTT is from cloud.mqtt.
can some one help me pls?
I dont know if you need more informations or not.
I say Thank you ^^

Hi.
I recently found out that Home Assistant have changed how to setup MQTT..
This is how you fix it:
light:
  - platform: mqtt
    schema: json

This is the old way:
light:
  - platform: mqtt_json

If this doesn't fix your problem you have probably an issue with your config, doublecheck your config with an YAML validator and post your config here.


FIX only use sethasemptydefault if exists.

Backport of #4672 with a slight rewrite incase of subclasses of the field.

@tractorcow as discussed, PR to fix this bug.


Hip bf16 gemm support

Per Braga, bfloat16 operations should be supported by all GPU generations that support rocblas.  For architectures where native bfloat16 ops are not available, software emulation is used.


dialing gRPC server

hey. I have gRPC client and gRPC server in traefik however I cant figure out how to dial the server when they both are in seperate containers. what address do I have to use? dialing by the frontend host rule doesnt work, getting "couldnt resolve". edited the hosts in the client container, forwarding from the traefik container ip to "server.local" and still doesnt work.
the docs (https://docs.traefik.io/user-guide/grpc/) shows dialing by the frontend host rule however idk how its possible. it doesnt work for me.
current config:
defaultEntryPoints = ["http"]
logLevel = "DEBUG"
[entryPoints]
    [entryPoints.http]
    address = ":80"

[file]
[backends]
[backends.client]
	[backends.client.servers.server1]
	url = "http://client:8081"
[backends.server]
	[backends.server.servers.server1]
	url = "h2c://server:50051"

[frontends]
[frontends.client]
	backend = "client"
	[frontend.client.routes.test_1]
	rule = "Host:client.local"
[frontends.server]
	backend = "server"
	[frontend.server.routes.test_1]
	rule = "Host:server.local"
[api]

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Træfik!
We dedicate the issue tracker to bug reports and feature requests only.
If you have questions and need community support, you can join our Slack workspace and reach out to us on the #support channel.
Another option is to use Stack Overflow and tag your question traefik.
Of course, double checking Træfik's documentation is always a good idea :sweat_smile:


Result record rework

Description
Removed print statements and added logger.
GitHub Issues

#42

Coverage decreased (-0.2%) to 89.444% when pulling db3a8585280feecfb8c51de20461a80dafb16be1 on mcrowson:result_record_rework into 90717aec5ddc79b85bf100992c3d13cf26a9aee4 on refindlyllc:development.


Prevents the program from crashing when the color passed in is not of…

fix issues https://github.com/pocketsvg/PocketSVG/issues/194
The wrong color type causes the program to crash

I encountered a crash in the process of using, I tried to add some code to prevent the program from crashing, hoping to help other users.


CI improvements

Details in commit messages

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.766%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
970

Relevant Lines:
1201

💛  - Coveralls


Certificate renewal issue java.security.SignatureException: Signature length not correct: got 512 but was expecting 128

Thanks @gcamus!

Thanks @gcamus!