Cirrus ci revised

This PR should complete adding Cirrus-CI on FreeBSD.
A couple of things to note:

indent tests are disabled. For whatever reasons, the vim build on Cirrus-CI when running the indenttests does not indent anything. I have no idea why that could happen. I have verified that Vim has eval features and checked the environment, but could not find anything unusual. So this is skipped here and just the normal test suite is run. I could not reproduce this issue on a my test FreeBSD image, so I suppose this is just something weird with the CI system (and since the indent script tests are run on Travis this should be okay).

Fix test_normal23_K. The previous commit c7d2a57b3a076f6ecb16f93c0b09280c4b3b4175 already tried to fix this, but missed another condition, which made the test still fail. So let's just fix it completely by adding the correct condition wherever it is needed.

Fix test test_utf8_comparisons.vim This comes from the fact that \n inside a quoted string does not add a new line. I don't know why this happens, Fix this by using <cr> instead of \n.

Skip a couple of tests by adding a CheckNoBSD command. It is not completely clear to me, why those tests fail. Some of that seem to come from the fact, that newline handling is a bit different.

Test_source_utf8 This seems to be an issue with newline handling and :source! seems to ignore the newline (Test_source_utf8) and just adds all commands into the commandline, waiting for a press enter prompt. This causes obviously a timeout for the CI system.

Same for Test_source_ctrl_v. For some reason, the when outputting the first __2 map, Vim won't add the newline, so that verification fails. This seems to be again a problem with newline handling.

Test_switchbuf() and Test_terminal_composing_unicode() I have not verified what exactly causes those two tests to fail. So I just disabled it. (Failure can be seen here: https://api.cirrus-ci.com/v1/task/4647487431770112/logs/test.log)

Although the indent tests are not run, I figured it would make sense to see an actual diff of the failing indent tests. So I just amended the indenttest target in the Makefile and output the first failure.

All those changes at least make Cirrus-CI green now in my fork: https://cirrus-ci.com/github/chrisbra/vim
Thanks for reading all that boring stuff until here ;)
Christian

Hm, okay ,the diff for the runtime indent scripts seems to fail Travis. I removed that part in the latest commit.

Christian wrote:

This PR should complete adding Cirrus-CI on FreeBSD.

Thanks!

A couple of things to note:

indent tests are disabled. For whatever reasons, the vim build on
Cirrus-CI when running the indenttests does not indent anything. I
have no idea why that could happen. I have verified that Vim has
eval features and checked the environment, but could not find
anything unusual. So this is skipped here and just the normal test
suite is run. I could not reproduce this issue on a my test FreeBSD
image, so I suppose this is just something weird with the CI system
(and since the indent script tests are run on Travis this should be
okay).

Perhaps it doesn't find the files in $VIMRUNTIME?

Fix test_normal23_K. The previous commit
c7d2a57b3a076f6ecb16f93c0b09280c4b3b4175 already tried to fix this,
but missed another condition, which made the test still fail. So
let's just fix it completely by adding the correct condition
wherever it is needed.

OK.

Fix test test_utf8_comparisons.vim This comes from the fact that \n inside a quoted string does not add a new line. I don't know why this happens, Fix this by using <cr> instead of \n.

I doubt it's because of the \n.  You also removed the Esc (relying on
feedkeys() with "x" to end Insert mode).  Perhaps Esc g is seen as some
escape code?  Encoding it as <Esc> might also help.

Skip a couple of tests by adding a CheckNoBSD command. It is not completely clear to me, why those tests fail. Some of that seem to come from the fact, that newline handling is a bit different.

I hope we figure out why.

Test_source_utf8 This seems to be an issue with newline handling and :source! seems to ignore the newline (Test_source_utf8) and just adds all commands into the commandline, waiting for a press enter prompt. This causes obviously a timeout for the CI system.

Sounds like a common problem.  Speculating: Perhaps git needs an
argument to handle files as binary?  It's valid utf-8 though.

Same for Test_source_ctrl_v. For some reason, the when outputting the first __2 map, Vim won't add the newline, so that verification fails. This seems to be again a problem with newline handling.

Again strange.

Test_switchbuf() and Test_terminal_composing_unicode() I have not verified what exactly causes those two tests to fail. So I just disabled it. (Failure can be seen here: https://api.cirrus-ci.com/v1/task/4647487431770112/logs/test.log)

That's using libvterm, might be a bit complicated.

Although the indent tests are not run, I figured it would make sense to see an actual diff of the failing indent tests. So I just amended the indenttest target in the Makefile and output the first failure.

All those changes at least make Cirrus-CI green now in my fork: https://cirrus-ci.com/github/chrisbra/vim
Thanks for reading all that boring stuff until here ;)

I hope you can figure out some things later.  I wonder if the problems
are caused by FreeBSD or the CI envifonrment.  I haven't heard from BSD
users that the tests fail for them, thus I suspect the latter.
Perhaps we can add another system on Cirrus to see if we get similar
failures?
--
The coffee just wasn't strong enough to defend itself -- Tom Waits
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Acknowledge Crowdin contributers.

Would be cool ;)

Hello, thanks for you contribution. I'm working on it.

Done with: https://github.com/andrii-bodnar/action-crowdin-contributors github action.


Added ability for developer to override the value of the field programatically

In my use case I have a typeahead-style field where the user will type the beginning of another user's name and then be presented with a dropdown of options to choose from. When the user selects an option I set the value in the background but I also need the ability to change the text field to reflect the complete name of the user that was selected versus just the first few letters.
This pull request allows the developer to set a new value by simply passing the value property in to the component but does not interfere with the existing state tracking if a new value is not passed in.

Thanks for your effort @kevinvangelder.
I tested this and have a concern about changing the input's active/passive state based on new value. It's probably a good idea to make the input state passive when it's value is set to undefined, and make it active when it has a new value over undefined.
I added some logic around your pull request and created 8e5e4c8. Can you check if it fits your use case?

@halilb I believe that your solution would work in my use case. I can't wait to try it! :)

Thanks for confirming @kevinvangelder.
I just published 0.1.2 with 8e5e4c8. Closing this PR in favour of that commit.

@halilb We just got a chance to try out your changes and unfortunately fields where the value is not set by the developer are laggy and don't work properly, as you can see in this gif (I was just typing, not deleting):

@kevinvangelder, I'll check the problem. Does the lag problem also occur with your pull request?


Changes to enable HBase HDFS short-circuit read using wrapper cookbook

This is related to issue #580. The changes in this PR will enable users enable/disable HBase HDFS short-circuit read through wrapper cookbook.

Has this been tested?

@ekund , the code changes were tested.

Looks good.


Emmet problems in PHP (even with all extensions disabled)

Does this issue occur when all extensions are disabled?: Yes
Versión: 1.74.3 (user setup)
OS: Windows_NT x64 10.0.17763
Steps to Reproduce:

Open a PHP file with this structure:

<!DOCTYPE html>
<html lang="en">

<head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
    <meta http-equiv="x-ua-compatible" content="ie=edge" />
    <title>Docuplay</title>
    <!-- Font Awesome -->
    <link href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/all.min.css" rel="stylesheet" />
    <!-- Google Fonts Roboto -->
    <link rel="stylesheet"
        href="https://fonts.googleapis.com/css2?family=Roboto:wght@300;400;500;700;900&display=swap" />
    <!-- MDB -->
    <link rel="stylesheet" href="/MDB5/css/mdb.min.css" />
    <link rel="stylesheet" href="/MDB5/css/colores/colores.css">

</head>

<body>

    <!-- MDB5 -->
    <script type="text/javascript" src="/MDB5/js/mdb.min.js"></script>
</body>

</html>

Try to use link:css inside head tag and you can see not work, not even pressing tab (also, the autocomplete suggestion does not appear).

2.1. Type an emmet abbreviation like div anywhere in the document and you can see that vscode doesn't suggest autocompletion of it, only autocompletes pressing tab, but this example in a html file work fine without problems.
Emmet config:
"emmet.excludeLanguages": ["markdown"],
    "emmet.includeLanguages": {
        "php": "php"
    },
    "emmet.showSuggestionsAsSnippets": true,
    "emmet.useInlineCompletions": true,
    "emmet.preferences": {

    }

Bonus: The only way to get Emmet shortcuts to work in PHP is using the extension: DEVSENSE.profiler-php-vscode. This should not happen and shows that emmet is malfunctioning
I repeat, the emmet problem occurs even with all extensions disabled, so it is not caused by any extensions.

For the emmet.includeLanguages setting, it should say "php": "html" if you want HTML completions in PHP files. Let me know if that works for you.

For the emmet.includeLanguages setting, it should say "php": "html" if you want HTML completions in PHP files. Let me know if that works for you.

Yes, after making that modification everything works correctly, thanks!


Feat：new REST API for broadcasting signed tx data to blockchain

提供API接口接收来自前端本地生成的签名交易信息并将其广播到链上

Will provide this feature for the next commit.

Node discovery
Proxy transaction
Apis for client

#124

#125

Great job done!


Ruby "known failures" examples are out of date

The Ruby known failures list includes multi-line comments, which were fixed in #1121.
PR #1309 fixes the documentation.

I just merged #1309. Thanks for reporting!


KAFKA-12293: remove JCenter and Bintray repositories mentions out of build gradle scripts (sunset is announced for those repositories)

Related jira ticket:
https://issues.apache.org/jira/browse/KAFKA-12293 Remove JCenter and Bintray repositories mentions out of Gradle build (sunset is announced for those repositories)
Some related external links:

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter
https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure

Note: at the moment I am not sure about Kafka releasing process (i.e. publishing to global public repositories). If Kafka exclusively  publishes to JCenter then this solution should be expanded. update: could not find release process related gradle parts
FYI @ijuma

This PR is ready for a review.
FYI @ewencp and @ijuma

(note: I just force-pushed once more in order to remove phrase [Work in progress] out of the git commit message... now PR is ready ready for a review... for real 😃)

I actually don't watch this much anymore, but what is the replacement? References were added intentionally because some dependencies weren't available in maven central. Has everything migrated over to central?
And what's the backporting plan?

@ewencp thing is that JFrog (company behind JCenter repository) simply decided to pull the plug on May 01st 2021. (a short notice decision, I dear to say).
So, it seems that Maven central is a fine (only ?) alternative after May 01st and luckily it seems that kafka project build as expected without JCenter; herewith two examples:

./gradlew --refresh-dependencies --info (dependencies refresh shows that Maven Central  has it all... with a little help of a Gradle plugin portal :smiley:  )
./gradlew clean test jar releaseTarGz (all test + jars +binary releases combined into one, big execution... only handful of test fail, so I assume that we are good to go):

ClientIdQuotaTest > testThrottledProducerConsumer() PASSED

ClientIdQuotaTest > testQuotaOverrideDelete() PASSED

ClientIdQuotaTest > testThrottledRequest() PASSED

3214 tests completed, 15 failed, 7 skipped

> Task :core:test FAILED

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':connect:runtime:test'.
> There were failing tests. See the report at: file:///home/dejan/IdeaProjects/kafka/connect/runtime/build/reports/tests/test/index.html

* 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:
Execution failed for task ':core:test'.
> There were failing tests. See the report at: file:///home/dejan/IdeaProjects/kafka/core/build/reports/tests/test/index.html

* 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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 38m 29s
252 actionable tasks: 252 executed

Update: JFrog partially reversed their decision (first they declared something on Feb 3rd and then changed their mind on Feb 8th).
Now they decided to serve artifacts via JCenter until February 1st 2022 (but they will stop receiving new artifacts after March 31st 2021). https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure
Herewith a new schedule:

March 31st, 2021  | No more submissions will be accepted to JCenter
May 01st 2021 | JCenter REST API and UI will be sunsetted
February 1st, 2022  | JCenter will no longer be available for non-Artifactory clients

At the time of my comment here, jcenter is throwing 500s to my kafka build processes: https://status.bintray.com/incidents/ctv4bdfz08bg
Now is a good as time as any to take this change to remove this project's dependence on the jcenter service.

@dejan2609 can you please resolve the conflict?

@ijuma Done (conflict solved / branch force-pushed).

I tried backporting to 2.8 and the older plugin versions in that branch were not available in Maven central. We should probably wait a few months and see how things develop before backporting to older branches.

I tried backporting to 2.8 and the older Gradle plugin versions in that branch were not available in Maven central. We should probably wait a few months and see how things develop before backporting to older branches.

is it  time to merge this pr to 2.8 ?  @ijuma

i still see issue with kafka 2.8.0
few days back i  have downloaded kafka 2.8.0 source code (from https://kafka.apache.org/downloads ) and build binaries (following https://github.com/apache/kafka/tree/2.8) . Although build is successful after changing gradle plugin url in gradle/buildscript.gradle   (Since url 'https://dl.bintray.com/content/netflixoss/external-gradle-plugins/'  is down i have changed to url 'https://plugins.gradle.org/m2/' )  but unit
index.html.zip
test is falling. I have attached unit test result.
My env details:
Gradle 6.8.3
java version "11.0.13" 2021-10-19 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.13+10-LTS-370)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.13+10-LTS-370, mixed mode)
Scala code runner version 2.13.0

@mdshadabin as mentioned by @ijuma above, this hasn't been backported to older releases yet. Unit tests are sometimes flaky, so might just be due to that. At this point it would probably make most sense to file PRs against older branches since it's not guaranteed to be a trivial backport. From there we can use the normal CI infra to validate.

Thanks @ewencp  ,
I have switched to Kafka 3.0.0, i always see a few unit test failures.
Download Kafka source code from official side and follow git hub to build and run unit test.
Below is link to access : build log, unit test log and unit test report.
https://drive.google.com/drive/folders/1lMUgETBNUS6ncEkfD5SU4E3JbqR8wHD4?usp=sharing
Are these 1% failures expected?
Is it possible to make it 100% successful?


Fix sticky decision keeps failing on ConditionFailedError

What changed?
Fix a rare issue for sticky task keeps failing on ConditionFailedError

Why?
When rangeID changed and sticky task ConditionFailedError happened, it is possible for the sticky tasklist to go into a bad state that none task can be added to it because of endless ConditionFailedError. This will cause latency increase for workflow, because all sticky decision task timeout (and workflow can only progress by using normal tasklist)
Once it happened, the only possible way to recover is for user to restart workers (with those affected tasklists)
We want to stablize the tasklist rangeID so that no need for worker to restart to recover using the sticky tasklist.
This PR use a relatively conservative approach to stop infinite retrying sticky failures on ConditionFailedError. By reducing concurrent access to tasklist, it will be more likely to break the endless ConditionFailedError.
Another approach would be clear stickness on worker side, but there would be bigger changes and risks.

How did you test it?
Existing tests

Potential risks
n/a

Coverage increased (+0.04%) to 66.982% when pulling ccf1a3adf075e8feee08fd049462ac71adda8276 on matching into 01d2d1a475827257861b3e39846357d6f3e9def9 on master.


Remove usage of Either.LeftProjection.get

In Scala 2.13 this method was deprecated, and let's projects that use
magnolia fail if fatal warnings are active.
I replaced the filter followed by .left.get with a collect to
get rid of the warning.
For reference, the exact message is:
method get in class LeftProjection is deprecated (since 2.13.0): use `Either.swap.getOrElse` instead

Oops, just saw #192 , closing


Find areas that could be turned off by features

Currently, the crate is kind of heavy-weight. If a user doesn't want the full functionality, it should be possible to turn off bits of it (and save on the number of dependencies) by features.

We have a lot of features now, both in the base crate and subcrates.

We have a lot of features now, both in the base crate and subcrates.


Flashing Scrollbars

Every few seconds, the scrollbars will switch to a black theme and go back to a normal style. It seems to only occur when I am within a playlist and is completely fine when I am on other pages like Listen Now. The sidebar scrollbar, when it actually appears, does the same thing

I'm running Radiant 1.6.2 on OS X 10.11.2. I have custom themes disabled (though it happens with them enabled as well and in multiple themes). A restart of both Radiant and my system did not fix the issue. I have scrollbars set to always be on.

I can't seem to reproduce this at all.  Is it still happening on the latest version (1.8.0)?  Are you doing anything specific to trigger it?  Does it happen all the time or is it sporadic?

I haven't been using Radiant, but the latest release does not seem to have this issue anymore

:+1: Cheers for the info!


Read configuration from the environment instead of file

The application currently breaks the Twelve-Factor App rule about configuration, reading it from a file instead of the environment. Read the link for more info on the drawbacks of the current approach.
A more robust solution is to enable configuration from the environment on staging/production and CI and from a file for development and testing.

Sorry. But I'll be vetoing this idea. I don't agree with the reasoning in the link. Environment are much easier to get wrong, they are very hard to audit. Files can even be reloaded without exiting the application.

Shall we support both? I believe we can read the config from environment and also from a file. With some libraries, like envy and dotenv, that would be easier. The reason asking to support reading config from environment is that servant applications usually would be deployed to a container platform(like a k8s cluster) as a backend service. And services in a container platform use environment variables as config.

@hughjfchen yep, that could be a nice idea, supporting several ways of configuring an application. Then we could probably use a monoid instance on the configuration to manage configuration overrides.
Would you be interested in contributing this to the project?


Little question.

Hi ReZeroE!
First off, thanks for the amazing Anilist wrapper! I'm using this in one of my projects and works amazingly well, so thanks for that. As there's no other way of communicating with you (there's nothing on your GitHub page) I had to resort to opening an issue so sorry about me contacting you through this!
The thing I want to ask is, is there a way to grab AniList links? E.g. going onto an AniList page you have links for Crunchyroll, Funimation, and others. I want to grab those links off AniList but don't see them anywhere in the API wrapper. Is this going to be added in the future?

Nevermind! Figured out how the code worked, and added it in.

Glad to hear! If you have any further questions, feel free to reach out to me over discord (ReZeroK#4910). I'd be happy to offer any help possible.


Automatic retries beyond read_parquet / to_parquet

In https://github.com/dask/dask/pull/9175 we added automatic retries when using remote filesystems with dd.read_parquet / dd.to_parquet. It'd be nice for other I/O functions (e.g. dd.read_csv / dd.to_csv) to have similar robustness.

One thing to be aware of is https://github.com/dask/dask/issues/7036. For DataFrames, currently fusion is off by default https://github.com/dask/dask/pull/7620, but there are reasons why we might want to turn it back on (https://github.com/dask/dask/issues/8447). And if anyone loads data in a DataFrame, then turns it into an Array/Bag down the line, then they'll silently lose the retries.

Totally agree there are some known issues. I still think it's worth adding auto-retries, we just know there are some known issues. Worst case scenario, users will have the current behavior on main (i.e. retries will be lost)

Agreed. It would probably just be good to 1) document the auto-retries and 2) mention this caveat in those docs.

When trying to implement retries over at #9601 the initial approach was to annotate read_bytes around here https://github.com/dask/dask/blob/e5b27eb2037e79ff31b935ba89976ab52b946605/dask/bytes/core.py#L145-L159
those annotations were not carried over, in other words when running a test that look like this
    def test_read_csv_retries(tmpdir):

    fn = str(tmpdir)
    remote_fn = f"simplecache://{tmpdir}"
    storage_options = {"target_protocol": "file"}

    ddf2 = dd.read_csv(f"{remote_fn}/*.part", storage_options=storage_options)
    layer = hlg_layer(ddf2.dask, "read-csv")
    assert layer.annotations
    assert layer.annotations["retries"] == 5

There were no annotations. We know that the annotations were created on read_bytes because we checked with breakpoints at that level.
Found a workaround, see PR which requires Adding storage options to text_blocks_to_pandas is breaking other tests because I'm not passing it into those tests, I want to make sure there is no way around this before I start touching all the other tests. It seems this way it'll be just a bandaid. Thoughts?
cc: @mrocklin

https://github.com/dask/dask/pull/9601#issuecomment-1304141674 for visibity


Add --orchestrate flag to meltano ui to start orchestrator in background

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2607
Originally created by @DouweM on 2021-02-24 17:10:53

Related to https://gitlab.com/meltano/meltano/-/issues/2105 and https://gitlab.com/meltano/meltano/-/issues/2231.

View 3 previous comments from the original issue on GitLab

Closing as no longer relevant on account of the removal of the UI for Meltano 3.0


Decompose globals

New transformation to decompose any unsupported global constraints in flat expressions.
Code is functional but can be somewhat compacted I think...
Transformation should be run after flatten() for every solver so we do not have to decompose globals at a later stage.
Work in progress still

Significantly cleaned up the code of the new transformation.
Last design decision we should agree upon is whether to also have an argument to the new transformation supported_reified. Now these globals are decomposed in reify_rewrite based on the supported list we get there.
I'm doubtfull as we also handle global constraint differently in other transformations such as in only_numexpr_eq, but no decompositions, so yeah, not sure...
What do you think @JoD, @tias and @Wout4?

Added some documentation and covered + tested more edge cases.
Most comments are resolved I think, except for merging "bound calculation" first.

Merged master with bound calculations into this branch, now Element can do a proper check if it is total or not.

I agree we should make abs a global constraint indeed. We can then provide a decompose_comparison for that one as well.
Regarding decomposing globals in the expression tree, I thought about it as well but there are many edges cases which are unclear how to handle. For example lets assume we have the following situation: a solver supportingAllDifferentbut notMaxThen how do we decompose the max constraints in the constraint below?AllDifferent(max(a,b,c), max(x,y,z), max(p,q,r))? We have a decompose_comparisonfor numerical global functions like these but they do not appear in a comparison in this case!  This leaves us with 2 options: decomposing theAllDifferentinto pairwise inequalities, then dodecompose_comparisonfor everymax expression or flatten the constraint to [AllDifferent(IV0, IV1, IV2), max(a,b,c) = IV0, max(x,y,z) = IV1, max(p,q,r) = IV2]
So it is to prevent these cases I opted for decomposing the globals after flattening


Add sanitization of Style content

This PR resolves #1437.
This PR adds a sanitization function to the BrewRenderer, which removes any <script> or </script> tags, in exactly the same way that the Markdown renderer already sanitizes the brew content.

A point of discussion - we could also move the brew content sanitization to the same point in the process, allowing this function to be used for both the user submitted content of both the Style and Content editors.

Can you correct the spelling in the original “sanatize” function as well?

@G-Ambatte Yes, let's move sanitization to the same place (in the brewrenderer, before passing to Marked).

LGTM! Thanks @G-Ambatte! 💥 ✨ 🏅


(Improvement) Incorporate Cross Browser Testing

So it looks like we qualify for a free OSS license from Sauce Labs.
What this offers us:
Being able to run javascript tests in multiple browsers https://saucelabs.com/products/javascript-unit-testing
Unlimited UI automation with up to 5 concurrent VM's in pretty much any browser we want:
https://saucelabs.com/platforms
We also get as much manual testing as we want for 10 minute sessions per use(after 10 minutes it kills the session and you can just start another one right away)
We could create some simplistic UI tests in something like nightwatch.js and have them run with the travis.ci and sauce labs integrations https://docs.travis-ci.com/user/sauce-connect/
This could allow us to automate visual regression testing by recording screenshots and videos by having sauce labs show us how UI elements look and perform in multiple browsers and possibly catch errors so were aware of them early.
This could make canon-react more useful when developers are able to see how it looks and performs in multiple browsers even if they dont have them installed or available locally(looking at you windows, mobile browsers etc...)
To clarify this is free for testing work on canon-react itself(and not private rax projects) but if you ever have some kind of edge case you can reproduce in canon-react by uploading a static page somewhere public to test manually or via automation then we should be good to go.

To clarify this issue is to just spike and see if sauce labs could be useful to us, also if you ever wanted to experiment with it this would be a good chance.


Termdebug add support for local variables and arguments

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
It is cumbersome to use termdebug if you want to keep an eye on the local variables.
(If it is related to runtime files, please check their header for where to discuss enhancements.)
This is not mentioned in runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
Describe the solution you'd like
I'd like to have more of gdb's information exposed to the user akin to the experience in emacs when using gdb-many-windows.
Describe alternatives you've considered
While there is nothing that this would enable that was not possible before, so the alternative would be to not implement the functionality.
Additional context
I would be willing to implement some or all of these features, and have taken a preliminary stab at a buffer for the variables exposed using -stack-list-variables.
PR: https://github.com/vim/vim/pull/12403

Thanks. I'm waiting for some more reactions to the pull request and the way
I've done it. If it looks fine, I'll put in a merge request for a registers and
a memory window


Ironbank configuration

Add ability to switch on or add configuration required to use ironbank versions of RKE2 images

I hit this recently, and I achieved it by editing the rke2_config var section to include the following:
   rke2_config:
      disable: rke2-ingress-nginx
      selinux: true
      protect-kernel-defaults: true
      profile: cis-1.5
      write-kubeconfig-mode: "0640"
      kube-apiserver-image: "registry1.dso.mil/ironbank/rancher-federal/rke2/hardened-kubernetes:v1.20.6-rke2r1"
      kube-controller-manager-image: "registry1.dso.mil/ironbank/rancher-federal/rke2/hardened-kubernetes:v1.20.6-rke2r1"
      kube-scheduler-image: "registry1.dso.mil/ironbank/rancher-federal/rke2/hardened-kubernetes:v1.20.6-rke2r1"
      pause-image: "registry1.dso.mil/ironbank/rancher-federal/rke2/pause:3.2"
      runtime-image: "registry1.dso.mil/ironbank/rancher-federal/rke2/rke2-runtime:v1.20.6-rke2r1"
      etcd-image: "registry1.dso.mil/ironbank/opensource/etcd/etcd:v3.4.15"
      audit-policy-file: /var/lib/rancher/rke2/auditpolicy.yaml

Thank you @Yantrio This is a perfectly good solution to this. Closing this issue.


video0 permission denied

Cant use your docker. Permission denied on device video0
docker logs motioneye
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/20_setup_motion.sh...
ownership of ‘/config/motion.conf’ retained as nobody:users
ownership of ‘/config/motioneye.conf’ retained as nobody:users
ownership of ‘/config/prefs.json’ retained as nobody:users
ownership of ‘/config’ retained as nobody:users
mode of ‘/config’ retained as 0775 (rwxrwxr-x)
mode of ‘/config/motion.conf’ retained as 0775 (rwxrwxr-x)
mode of ‘/config/motioneye.conf’ retained as 0775 (rwxrwxr-x)
mode of ‘/config/prefs.json’ changed from 0644 (rw-r--r--) to 0775 (rwxrwxr-x)
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 20
Oct  5 20:08:00 5518f14a126f syslog-ng[29]: syslog-ng starting up; version='3.5.3'
    INFO: hello! this is motionEye server 0.33.2
    INFO: cleanup started
    INFO: wsswitch started
    INFO: tasks started
    INFO: mjpg client garbage collector started
    INFO: server started
Failed to open /dev/video0: Permission denied

timemachine:
    container_name: motioneye
    image: jshridha/motioneye:latest
    environment:
      - TIMEZONE="Europe/Berlin"
    volumes:
      - /root/.motioneye:/config
      - /media/19ad4901-a651-4001-9306-425956e2c501/Motioneye:/home/nobody/media
    ports:
      - "8081:8081"
      - "8765:8765"
    devices:
      - "/dev/video0:/dev/video0"

ls -la /dev/video0
crw-rw----+ 1 root video 81, 0 Okt  5 21:43 /dev/video0

Sorry it has taken me a while to get to this issue. It sounds like the user running motion does not have permission to access the device.
Can you try the newest build jshridha/motioneye:experimental specifying the env variables:
environment:
  - PUID="UID"
  - PGID="GID"

where UID and GID specify a user/group that has access to the /dev/video0 device. The defaults are PUID=99 and PGID=100

Workaround is to use -e PUID="0" and -e PGID="0" instead.

@volker-fr is right. Closing this issue.

@jshridha I don't think a workaround is a fix. And this workaround also doesn't seem to be documented outside of this ticket.


Python tool to create a test from a real devnet issue

Create a python tool in this repository that is capable of creating a blockchain test from an invalid block on any devnet, testnet or shadowfork.
The tool must perform the following sequence:

Query the block N to fetch the transactions and header properties of the block where the INVALID issue was found
Create a set of touched addresses L and for each transaction add the sender and recipient addresses to the list
Fetch the account information (balance, nonce, code, storage) of all addresses in L at block N - 1 and add them to the alloc of the test
Run the block N as block 1 of a blockchain test, with the alloc information at genesis
Analyze the execution trace of all transactions and for each call to a different account (CALL, CALLCODE, DELEGATECALL, STATICCALL, SELFDESTRUCT), account information fetch (BALANCE, EXTCODESIZE, EXTCODECOPY, EXTCODEHASH), or contract creation (CREATE, CREATE2), add the target address to L
If L now contains more addresses, go to (3), otherwise proceed
Blockchain test comprises the Genesis with the alloc collected and the Block 1 with the transactions of block N with as many properties carried over as possible (Number might be difficult, and if any of the transactions query NUMBER opcode, this might result in deviation of execution)
(Optional) alloc can be compressed by running the block and then analyzing the trace and then discard the storage keys that are never read on all accounts.

For me it would be also beneficial to be able to dump a valid block this way (for benchmarking and profiling).


Add link to API docs in README

@johnkerl assuming you mean TileDB-Cloud-Py, it is there (now? -- possibly changed since your comment).

Derp, my bad @ihnorton , total PEBKAC 😬
Thank you!


Update footer link

User Story 180344: Build: update the Footer
Update the link to the support site from the current email to the new PASS form. This is held behind a feature flag.
Changes
Added a feature flag to control the release of the the link (17th October)
Added the link to the view constants
Updated the name of the mail to link in the view constants
Added the new link behind a feature flag to the footer and updated the error page and report an issue links
Updated the footer design (from 3/4 to 1/2 width columns)
Screenshots of UI changes
Before

After
Without the feature flag:

With the feature flag:

Checklist

[x] Pull request attached to the appropriate user story in Azure DevOps
[x] ADR decision log updated (if needed)
[x] Release notes added to CHANGELOG.md
[ ] Testing complete - all manual and automated tests pass

QA Pass - All looking good! Tested across dev and test environments with their various feature flags set and no issues found


RSDK-236 RSDK-248 - rpc: use single changestream per mongoDBWebRTCCallQueue

This improvement has been a long time coming. This makes using the MongoDB queue much more efficient while also adding in some nice soft-limits.

@michaellee1019 I know this is a big PR, so take your time with it and don't feel rushed to get a review in. If there's anything you want to sit down about and discuss, let me know. Given this is your first time looking at this area of the code, I'd be happy to do an overview of what's going on here.

FYI: I've tested this a ton locally and have gone through various disaster scenarios to see if this holds up and it appears to.

Overall makes sense though still wrapping my head around some things. High level comments:
1. Consider an architecture diagram? Or a talk. Can be done later.

Yes :). Not in this PR

2. Consider running in staging only to let this bake for a while? It could help us review the operators collection against many robots to make sure everything is working as expected. I assume locally you have tested but with 1 caller and 1 answerer?

I've tested with N:M caller:answerer but once this is in, we can put up a PR for app and deploy a staging env.

Some questions:
1. I assume that there will be a PR after this to implement on the App?

Yep, app needs to update to latest goutils and then it's in. App uses all the code rewritten here for signaling.

2. Is the plan to use a single operator per App host?

Yes

3. How can we monitor the worst case which is that all answerers are at capacity and no additional robots can connect?

The metrics would allow us to check this. Keep in mind answering is a few seconds. You can have 100 active connections to a robot and still 2 answers processing new connections (think a switchboard)

Overall makes sense though still wrapping my head around some things. High level comments:
1. Consider an architecture diagram? Or a talk. Can be done later.

Yes :). Not in this PR

2. Consider running in staging only to let this bake for a while? It could help us review the operators collection against many robots to make sure everything is working as expected. I assume locally you have tested but with 1 caller and 1 answerer?

I've tested with N:M caller:answerer but once this is in, we can put up a PR for app and deploy a staging env.

Some questions:
1. I assume that there will be a PR after this to implement on the App?

Yep, app needs to update to latest goutils and then it's in. App uses all the code rewritten here for signaling.

2. Is the plan to use a single operator per App host?

Yes

3. How can we monitor the worst case which is that all answerers are at capacity and no additional robots can connect?

The metrics would allow us to check this. Keep in mind answering is a few seconds. You can have 100 active connections to a robot and still 2 answerers processing new connections (think a distributed load balancer connected to N servers/listeners that keep running accept)

Makes sense! Thanks for explaining.


Documentation fix

Source: https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/ide/walkthrough-creating-a-code-snippet.md

To test the shortcut, open a Visual Basic project and open a code file. Type hello in the file and press TAB. The snippet code should be inserted.

should be

To test the shortcut, open a Visual Basic project and open a code file. Type hello in the file and press two times TAB. The snippet code should be inserted.

Source: https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/ide/how-to-distribute-code-snippets.md

In the Add New Asset dialog, set the Type to Microsoft.VisualStudio.VsPackage, the Type to File on filesystem, and the Path to HelloWorldVB.pkgdef (which should appear in the dropdown).

should be
In the Add New Asset dialog, set the Type to Microsoft.VisualStudio.VsPackage, the Source to File on filesystem, and the Path to HelloWorldVB.pkgdef (which should appear in the dropdown).
(based on vs2017)
Source: https://docs.microsoft.com/en-us/visualstudio/ide/code-snippets-schema-reference

The Assembly element is only supported by Visual Basic code snippets.

The Reference element is only supported for Visual Basic projects.

The References element is only supported for Visual Basic projects.

That's not correct. C# also supports the References-element, Reference-element and Assembly-element

@gernotpokorny thanks, I will get this fixed.


[Wallet] Upgrade detox, react-native, hermes in order to fix common crashes

Description
This PR is aimed at fixing end to end tests as well as fixing some of the top crashes.
Updated the following core packages:
"react": "16.13.1",
"react-native": "^0.63.4",
"detox": "^17.13.2",
"react-native-reanimated": "^2.0.0-rc.0",
"@react-navigation/compat": "^5.3.10",
"@react-navigation/drawer": "^5.11.4",
"@react-navigation/material-top-tabs": "^5.3.10",
"@react-navigation/native": "^5.8.10",
"@react-navigation/stack": "^5.12.8",
On the android side:
gradle plugin 3.5.3
Sorry for the length of the PR. Some things you can ignore are the test snapshots.
I think the e2e tests were actually exposing a serious problem, which happened on app start. I started by upgrading only detox and then figuring out what else was needed. With just detox upgraded to the latest the app started consistently crashing, with similar traces to the ones we see in prod. I believe this is related to us running an older hermes-engine, so I upgraded that as well. The benefit now is that the crashes also look much more readable which was a feature added recently by hermes (they were lacking native symbols before).
The PR got a little big, but I believe the changes all go together since the packages are inter related. I would really appreciate you starting to take a look @jeanregisser and @cmcewen since you've seen some of this before.
Other changes
The changes don't seem related to each other but they all seemed necessary in order to silence the type errors.
Tested
Manually and e2e.
Related issues

Fixes #6104 #6200 #6201 #6202 #6204 #6205

Backwards compatibility
Yes.

Android e2e test is green again!! w00t! medal_sports rocket

Amazing! thank you so much for your help @jeanregisser !

bumping this as it never merged

Hi @etuleu @tarikbellamine We have performed e2e testing on latest Android internal build V1.7.2(1004294329) & Test Flight build V1.7.2(39) and we have observed that there are some crashes issue still are in open state. can you please look into those issues.
Test plan link: https://docs.google.com/spreadsheets/d/1AFv9JWXnKfXJewhXf3nKlahB43d2v9xBU965ygXQ294/edit#gid=2098208089
Below are the crashes issues still are in open state

https://github.com/celo-org/celo-monorepo/issues/4684
https://github.com/celo-org/celo-monorepo/issues/4685
https://github.com/celo-org/celo-monorepo/issues/6359
https://github.com/celo-org/celo-monorepo/issues/4704


First attempt on Joystream payouts

This is the first attempt for adding Joystream to the list of Substate-based projects for automated payouts. It's not ready for merge yet because there are still some compilation errors thanks to the missing fields in the node-runtime - and hopefully this can get resolved by the Joystream team.
Workarounds so far applied are

removal of pallet_identity (Joystream doesn't implement it)
node_runtime::storage().staking().history_depth() removed as well

Current compilation errors are listed on pastebin.

Hi @pmensik, some of those errors is just because Joystream uses different types from the ones in Kusama/Polkadot.
As a suggestion you can try to get all runtime types just by running:
subxt metadata --url wss://rpc.joystream.org:443 -f bytes > joystream_metadata.scale
subxt codegen -f joystream_metadata.scale | rustfmt --edition=2018 --emit=stdout > joystream_runtime.rs

And than adjust the file src/runtimes/joystream.rs accordingly.
As an example the type for events::Rewarded in Joystream is a tuple while in Kusama is a struct, you can adjust the code from ev.stash == validator.stash to ev.0 == validator.stash to override the following error:
error[E0609]: no field `stash` on type `joystream::node_runtime::staking::events::Rewarded`
   --> src/runtimes/joystream.rs:333:39
    |
333 | ...                   if ev.stash == validator.stash {
    |                             ^^^^^ unknown field
    |
    = note: available fields are: `0`, `1`

Nice to know that you are trying crunch in other substrate networks.

@paulormart Thanks for suggestios! The thing is that I am a very poor Rust/Substrate developer but this seems doable so I'll try myself first!

Ok, so after some playing around I was able to get rid of all the compilation errors. However, now I am experiencing some runtime errors and this is where I got stuck. Here is the log. Thanks for any help with debugging the issue!

Yeah the Subxt error: Rpc error: RPC error error is not very explicit.. a few things to check for:

try with only one stash
double check that the signer account as enough funds to cover for the transaction
fetch latest metadata from subxt metadata --url wss://rpc.joystream.org:443 -f bytes > joystream_metadata.scale

Does Joystream network have a test environment like Westend?


propagate web socket server

Allows using web socket server.
+RED.comms.getServer()

Coverage decreased (-0.01%) to 88.289% when pulling f7a1a8fbf5a0c7f32ccaf663d09af95b026f38a5 on MaxXx1313:master into 54036a2b4d0ea44ffc44e5f54e3e85c446f82de3 on node-red:master.

Hi,
Please have a read of our contribution guidelines around feature requests/pull requests.
What is the purpose of this pr? I can see technically what it does, but why do you need this feature?

Hi, if you'd like us to consider this PR, please have a look at the questions I asked in my previous comment from October. Otherwise we'll close this one to tidy up.

Hi!
Sorry for the delay.
I used this approach to see how many clients are working with the app, but I think it can be useful for some other purposes.
The first thing that comes into my head is node-red-ui. It uses another socket library to communicate with backend, but I think at some point it can use the same library, so the code size will become slightly fewer.


speculative fix for 2393

[ ] Double-check the spelling and grammar of all strings, code comments, etc.
[ ] Double-check that all code is deterministic that needs to be
[ ] Add tests to cover any new or revised logic
[ ] Ensure that the test suite passes
[ ] Update the project release notes
[ ] Update the project documentation, as appropriate, with a corresponding Pull Request in the Documentation repository

Fixed https://github.com/CounterpartyXCP/counterparty-core/pull/2401/files


Add test1 by skibidisimgacum69

Song Name
test1
Artist Name
skibidisimgacum69
Source
Youtube
Youtube Link
https://youtu.be/EmkAREirKb4?si=qJi4TRQaPda-gwra
Direct File Link
No response
Song ID
945695
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 27690100

reject
Song name needs to be more descriptive that "test1"


MongoDB, MongoId & ArrayHelper::toArray()

Hi all.
If we have MongoId object in some field (not _id) for relation then after toArray we obtain an array such as
'_id' => [
     '$id' => 'asdf7sdf87s8f7sdf80hdf8s7f'
]

instead of normal MongoId object.
Can we add condition
if ($object instanceof \MongoId) {
     return $object;
}

or something like that?

https://github.com/yiisoft/yii2-mongodb/issues/79#issuecomment-205757039

@klimov-paul any idea what to do about it in yii core? I do not see a way.

The only possible solution is add eplicit check for the \MongoId instance inside ArrayHelper::toArray():
if ($object instanceof \MongoId) {
    return $object->__toString();
}

It will work fine even if no MongoId class is defined.
If it is not acceptable, then issue should be closed with resolution 'wont fix'.

I agree with @qiangxue here, that it should not be part of the core to handle mongoId stuff. @yiisoft/core-developers other opinions?

Agree with @cebe

Also agree with @cebe

One of the possible solution, which does not involve direct class name check, can be following:
in case class declares method __toString() (e.g. it is convertable to string) and its array representaion is less then 2 elements - use __toString() result instead.
Such approach produce better results for such classes as yii\web\JsExpression for example.


Use Sparspak for general floats  and \ for non-GPL

Sparspak.jl provides support for general floats and is MIT licensed. So we can define \  and ldiv! for ExtendableSparseMatrix, and also as an alternative for the non-GPL case.

Codecov Report
Base: 85.15% // Head: 83.20% // Decreases project coverage by -1.95% :warning:

Coverage data is based on head (8bf171a) compared to base (9b5310c).
Patch coverage: 80.50% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
- Coverage   85.15%   83.20%   -1.96%
==========================================
  Files          17       18       +1
  Lines         842     1012     +170
==========================================
+ Hits          717      842     +125
- Misses        125      170      +45

Impacted Files
Coverage Δ

src/ExtendableSparse.jl
100.00% <ø> (ø)

src/sprand.jl
71.17% <64.70%> (-5.16%)
:arrow_down:

src/sparspak.jl
81.81% <66.66%> (-18.19%)
:arrow_down:

src/SparspakCSCInterface.jl
81.87% <81.87%> (ø)

src/extendable.jl
62.99% <100.00%> (-0.72%)
:arrow_down:

src/factorizations.jl
73.33% <100.00%> (ø)

src/sparsematrixlnk.jl
96.79% <0.00%> (-0.65%)
:arrow_down:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hi @bmmogensen, in this PR I changed the architecture for the non-GPL case:

Defined my own constant USE_GPL_LIBS in order to have a switch for at least some testing
Provide a Base.\ for ExtendableSparseMatrix relying on Sparspak.jl

May be you can check if this still works for you before I tag a new release, would wait a couple of days.


getitem for DataContainer

__getitem__ is another important property for our DataContainer class, https://numpy.org/doc/stable/reference/c-api/array.html
    import numpy as np
    xnp = np.random.randint(1,10,(3,4))
    a1 = xnp[0]
    a2 = xnp[0:2,3]

    xdc = DataContainer(xnp)
    # b1 = xdc[0]
    # b2 = xnp[0:2,3] %%% ???

Having this method in our DataContainer class, we could accelerate our optimisation framework, e.g., Operators, Functions, Algorithms and perform parallel/distributed optimisation, i.e., (non-) overlapping domain decomposition methods. This can be achieved using dask or scikit-image API. In this talk  a TV denoising comparison is presented using scikit-image and apply_parallel function of scikit image.  apply_parallel function wraps the dask.map_overlap method.
Although, metadata is not important for our optimisation framework , we already have Slicer which has label information and will have the same effect as  __getitem__.
See demo comparing FISTA-TV denoising (numpy API) with and without apply_parallel.

See also #926 and #1237


[Enhancement] Compose offline

nmail throws a warning when trying to compose an email offline, saying this is not supported. It would be useful to be able to compose drafts offline and send them later.

Yeah, currently nmail is dependent on IMAP storage for drafts. But I agree offline draft compose is a pretty normal/basic feature for email clients, so I'll see what can be done.

I've been considering this feature for a while and I'm currently leaning towards leaving it out of scope.
It would make nmail a lot more complex (as it was designed with different assumptions), and the benefits do not outweigh the amount of work, from my perspective. The simple workaround is to open ones favourite text editor and type the email text there while offline, for later proper compose and sending using nmail (or other email client).
I will proceed to close this issue for now.

I've been considering this feature for a while and I'm currently leaning towards leaving it out of scope.
It would make nmail a lot more complex (as it was designed with different assumptions), and the benefits do not outweigh the amount of work, from my perspective. The simple workaround is to open ones favourite text editor and type the email text there while offline, for later proper compose and sending using nmail (or other email client).
I will proceed to close this issue for now.

I've been considering this some more and I've come to the conclusion that basic offline compose can be implemented without a major re-design.
I will reopen this issue and update here once I have implemented something.

Brief description of the offline compose functionality implemented in nmail:
If postponing a composed message while offline, the message will be saved in an offline draft queue, and will be automatically uploaded to the configured draft folder once reconnected to the IMAP server.
If sending a composed message while offline, the message will be saved in an offline outbox queue, and will be automatically attempted to be resent once online again.
While composing a message a backup copy is now stored every 10 seconds. If the computer shuts down (or nmail crashes) there is a backup of the composed email. When nmail starts up next time, it will upload that composed message to the draft folder.

That looks beautiful, thanks for adding this!
On 2021-02-19 13:07 Kristofer Berggren<EMAIL_ADDRESS>wrote:

Brief description of the offline compose functionality implemented in nmail:
If postponing a composed message while offline, the message will be saved in an offline draft queue, and
will be automatically uploaded to the configured draft folder once reconnected to the IMAP server.
If sending a composed message while offline, the message will be saved in an offline outbox queue, and
will be automatically attempted to be resent once online again.
While composing a message a backup copy is now stored every 10 seconds. If the computer shuts down (or
nmail crashes) there is a backup of the composed email. When nmail starts up next time, it will upload
that composed message to the draft folder.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/d99kris/nmail/issues/38#issuecomment-782035022

Hi @Kabouik - for the questions:

The offlinequeue encryption is controlled by the queue_encrypt flag in main.conf (and is enabled by default I think). So it may be enabled for you even though general message cache (cache_encrypt) is disabled.
Interesting, I tried this here now and I can also reproduce this problem - it's must be a bug. I'll look into it.

I reported a separate bug for this (see #140) and fixed it as well. Please let me know in case you encounter more issues.


update jax.tree.map to comply with jax 0.4.34

Pull Request to fix #1093

Happy to do that. How would you imagine this test to be fully generic? A simple test case would be something like this (extended to all corresponding functions):
  def test_none_arguments(self):
    m = jnp.logspace(-10, 10, num=21, dtype=jnp.bfloat16)  # 1e-10 ... 1e10
    tu.tree_update_moment(None, m, 0.9, 1)

Let me know what you think.

I have added test cases for tree_add_scalar_mul, tree_update_moment, tree_update_infinity_moment, tree_update_moment_per_elem_norm, apply_updates, incremental_update, keep_params_nonnegative, and add_decayed_weights. I have omitted scale_by_adam as mu would need to be None, which is not an input argument to the function.


How to rollback / install ?

Hello all
Since last firmware 0.2.4, I have hundred of disconnections on my Synology.
So I decided to rollback to 0.2.3, as it was working like a charm.
So I extracted content of the .tar file on an formated FAT32 SD card ("Factory" folder, "newhome" folder and "home_y20gam.stage file on root).
Cam rebooted, and...
Nothing changed, 0.2.4 is still on the status page...
What's the matter ?

Try again.
It must work.
Or, as a last try, unhack the cam https://github.com/roleoroleo/yi-hack-Allwinner/wiki/Remove-the-hack
and apply again.

Once again, doesn't work.
It seems the cam is not loading/reading content on the SD...
I don't need to copy the y20ga_0.2.3.tar on root, right ? It's its content (3 elements above) that I need to copy to root, right ?
If I unhack the cam, do I need the Yi app to set up the wifi again, before hacking again ?

I think my cam is bricked...
So, I tried to unhack, nothing happens (orange light on for more than 15 mn).
So I unpluged the cam, wrote the 0.2.3 firmware on the SD, inserted the SD, switched on the cam...
And nothing for more than 15 mn, orange light still on !
Tried to reboot several times with or without SD, same thing...
Orange led still on, can't access the cam, don't see it on my router...

Remove all mp4 saved files from the sd before applyng the hack.

There were no mp4 files on the SD (I formated it before copying your hack).
But I think it's too late, it doesn't want to switch on anymore, still this fixed orange led.

Weird, it's very difficult to brick a cam.
Try to run the backup procedure.
If it works, you can recover it.

I had a similiar issue (cam did not boot anymore, yellow blinking). Cam did not react to "unhack" or trying to flash a new firmware.
What helped in my case was to use the backup script and resetting the cam. That was the first time that the cam was talking again to me (previous resets the cam just rebootet and said nothing). Then I was able to reconnect the cam to the app and then was able to flash it again.
Hope that helps you somehow.


Showing wrong amount of whitelisted users online.

Am I looking at this correctly?

@NurdTurd amounts seem correct, the second message should be "There are currently 6 whitelisted players"

Will that be fixed in the next release ?

While I fix this, should lists of multiple players be decantenated? (I don't have an elegant solution if so, involves duplicating the for loop as a result of the if statement.)

@SungMatt I think the current 3 values it returns are kindof "useless" just find useful values and display them, no problem if you make 300 loops for them, since they only run when you execute the command


Installation issue on mac

Hi everyone, I try to install it from MacMonterey and it returned me this error.  Please see below:
remotes::install_github("facebookincubator/GeoLift")
Downloading GitHub repo facebookincubator/GeoLift@HEAD
Installing 2 packages: Boom, bsts
trying URL 'https://cran.rstudio.com/bin/macosx/contrib/4.1/Boom_0.9.7.tgz'
Content type 'application/x-gzip' length 82018759 bytes (78.2 MB)
============
downloaded 19.0 MB

Error in download.file(url, destfile, method, mode = "wb", ...) :
  download from 'https://cran.rstudio.com/bin/macosx/contrib/4.1/Boom_0.9.7.tgz' failed
In addition: Warning messages:
1: In download.file(url, destfile, method, mode = "wb", ...) :
  downloaded length 19902342 != reported length 82018759
2: In download.file(url, destfile, method, mode = "wb", ...) :
  URL 'https://cran.rstudio.com/bin/macosx/contrib/4.1/Boom_0.9.7.tgz': Timeout of 60 seconds was reached
Warning in download.packages(pkgs, destdir = tmpd, available = available,  :
  download of package ‘Boom’ failed
trying URL 'https://cran.rstudio.com/bin/macosx/contrib/4.1/bsts_0.9.7.tgz'
Content type 'application/x-gzip' length 22736562 bytes (21.7 MB)
==============================================
downloaded 20.3 MB

Error in download.file(url, destfile, method, mode = "wb", ...) :
  download from 'https://cran.rstudio.com/bin/macosx/contrib/4.1/bsts_0.9.7.tgz' failed
In addition: Warning messages:
1: In download.file(url, destfile, method, mode = "wb", ...) :
  downloaded length 21297490 != reported length 22736562
2: In download.file(url, destfile, method, mode = "wb", ...) :
  URL 'https://cran.rstudio.com/bin/macosx/contrib/4.1/bsts_0.9.7.tgz': Timeout of 60 seconds was reached
Warning in download.packages(pkgs, destdir = tmpd, available = available,  :
  download of package ‘bsts’ failed
Running `R CMD build`...
* checking for file ‘/private/var/folders/93/2fmdks4d0vx3h40by9f3474w0000gn/T/Rtmp6Tx4YW/remotes36e649c6c0ce/facebookincubator-GeoLift-2415d3a/DESCRIPTION’ ... OK
* preparing ‘GeoLift’:
* checking DESCRIPTION meta-information ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
Removed empty directory ‘GeoLift/vignettes/GeoLift_Walkthrough_files’
* building ‘GeoLift_2.4.23.tar.gz’
* installing *source* package ‘GeoLift’ ...
** using staged installation
** R
** data
*** moving datasets to lazyload DB
** byte-compile and prepare package for lazy loading
Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) :
  there is no package called ‘Boom’
Calls: <Anonymous> ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
Execution halted
ERROR: lazy loading failed for package ‘GeoLift’
* removing ‘/Library/Frameworks/R.framework/Versions/4.1/Resources/library/GeoLift’
Warning message:
In i.p(...) :
  installation of package ‘/var/folders/93/2fmdks4d0vx3h40by9f3474w0000gn/T//Rtmp6Tx4YW/file36e6179c3a39/GeoLift_2.4.23.tar.gz’ had non-zero exit status

Turns out it because my internet speed is too low, so I had to configure the timeout options so it wont stop downloading and installing by:
getOption('timeout')
options(timeout=0)

closing this issue


⚠ AlphaRatio has degraded performance

In 9ee5ff1, AlphaRatio ($AR) experienced degraded performance:

HTTP code: 200
Response time: 620 ms

Resolved: AlphaRatio performance has improved in 72766ec.


when I follow someone it should suggest who else I should follow

@benawad what factors come into play when we try to find similarities between users? Because currently, we don't have many defining factors for users other than follower count.

followers of followers

if those don't exist, grab some popular users


Update the resource aws_security_group to allow traffic from port#80

Based on the change made in #84 the security group ingress rule must also be changed to allow traffic.

I created two separate security groups, one for the containers and one for the load balancer. The container security group allows traffic on port 8080 from the load balancer security group.


npm run build on 4.x does never complete

Describe the bug
npm run build never completes.
Unable to upgrade larger typescript based CRA project to version 4.x from 3.4.3.
Once upgraded npm run build will never complete.
I get following output before the build doesn't return anymore information:
Creating an optimized production build...
DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.
I think it would help if there is a way to add a --verbose, but i was not able to add that to the build yet. Right now i have 0 insight on what might be failing.
Couple things I have tried:

GENERATE_SOURCEMAP=false
--max-old-space-size=4096
run eslint --fix
eject
delete .lock files, push project, remove locally, re clone start fresh, etc.

Environment
Environment Info:
current version of create-react-app: 4.0.3
running from C:\Users\patri\AppData\Roaming\npm-cache_npx\34924\node_modules\create-react-app
System:
OS: Windows 10 10.0.19042
CPU: (20) x64 Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz
Binaries:
Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: Not Found
Edge: Spartan (44.19041.964.0), Chromium (91.0.864.37)
Internet Explorer: 11.0.19041.1
npmPackages:
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
Unable to reproduce
Expected behavior
Expect to complete build.
Actual behavior
Never completes.

This is something i can work with. So new eslint rules if anyone runs across the same issue in the future.


PR for [Enhancement] Adding subsections in Notes page - issue #19

I have created the subsections in notes page. These subsections are based on Branch, Subjects or Technology. We can add or modify it in future. The subsections are collapsible providing efficient user interface and beginner friendly.
I have attached the screenshots for reference.

Please accept it under gssoc-ext level-3 and hacktoberfest.

Check the footer of notes section, make the required changes. Rest you did a good job

Check the footer of notes section, make the required changes. Rest you did a good job

The footer part is fine. I have added the screenshot with only half of the footer visible.
Here i have attached the full screenshot of footer.

Check the footer of notes section, make the required changes. Rest you did a good job

The footer part is fine. I have added the screenshot with only half of the footer visible.
Here i have attached the full screenshot of footer.

kindly check the home screen footer and make the changes in the footer of the notes sections

kindly make the changes the in the footer section ASAP

I have done the changes. Should i make a new Pull request

ok
On Fri, Oct 4, 2024 at 5:03 PM Suraj Prakash @.***>
wrote:

I have done the changes. Should i make a new Pull request
—
Reply to this email directly, view it on GitHub
https://github.com/yatulearn/yatulearn/pull/85#issuecomment-2393496718,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKZA7EQAQUBH2YKSRERGTLDZZZ4JTAVCNFSM6AAAAABPKNQDDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTGQ4TMNZRHA
.
You are receiving this because you commented.Message ID:
@.***>

This PR has been updated So You can merge this one.
Please accept it under gssoc-ext level-3 and hacktoberfest.


Pass domain to clients http and tcp

Add support to other domain for apparted blip structure

Resolve conflicts on your side and re-submit for approval


Add gcc-8

Tool information

Tool name: gcc-8
Add or update? Add
Desired version: 8.3 (as provided by default ubuntu 18.04 package repository)
Approximate size:
If this is an add request:

Brief description of tool: Gnu compiler collection
URL for tool's homepage: https://gcc.gnu.org/

Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[x] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
Yes
apt-get install -y gcc-8

However, this fails at the moment because of broken packages. (which is not the reason for this request)
Are you willing to submit a PR?
Sure. Just need a bit help to get started.

Great!
Here is my suggested approach:
macOS
brew install gcc@8
# or
brew install gcc@9

This gets you gcc-<ver>, g++-<ver>, gfortran-<ver> as well as ar, nm, dump, ranlib with the gcc- prefix and major version suffix, as well as gcov and gcov utilities with the major version suffix
One complication with Homebrew is that other formulas may depend on gcc, especially Fortran related stuff (even MPICH, OpenMPI, etc.) so that can trip people up a little bit if gcc is not installed (gcc@9 is effectively an alias for gcc). I would probably install both 8 and 9 on macOS, or only install 9.
Ubuntu
Can you please make sure you install packages that match the compilers provided by Homebrew (for consistency) and also gcov?
Something like:
sudo apt-get install -y --no-install-recommends ccache gcc-${GCC_V} g++-${GCC_V} gfortran-${GCC_V}

Windows
I have no idea, but please don't forget about g++, gfortran and gcov. Last time I looked mingw pinned GCC to a specific version. You probably should use MSYS2 or WSL.
Thanks!

P.S. If you want to steer folks towards only GCC8, I would recommend brew install gcc@8 and brew install gcc && brew unlink gcc. That way anything that depends on GCC can be installed quickly and users wanting GCC9 can just brew link gcc.

@zbeekman Should we think about lcov as well? Currently, the official ubuntu repos do not provide a lcov version that is compatible with the gcc-8 toolchain (as far as I know).
I am using the following snippet to get a working lcov installation that is compatible to gcc-8 toolchain (contains lcov 1.14 download + installation as well as fixing used gcov version):
- name: Install lcov 1.14
      run: |
          wget http://downloads.sourceforge.net/ltp/lcov-1.14.tar.gz
          tar xzf lcov-1.14.tar.gz
          cd lcov-1.14/
          sudo make install
    - name: Setup gcov version
      run: sudo ln -sf $(which gcov-8) $(which gcov)

@pefoo I rarely use lcov since I most often use codecov.io for coverage analysis.
But if you want it I would submit a new issue if I were you.
FYI, I think you want to use sudo update-alternatives or similar on ubuntu for getting the right version of your tooling setup. Something like:
      run: |
        sudo apt-get install -y --no-install-recommends gcc-${GCC_V} g++-${GCC_V} gfortran-${GCC_V}
        sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-${GCC_V} 100 \
        --slave /usr/bin/g++ g++ /usr/bin/g++-${GCC_V} \
        --slave /usr/bin/gfortran gfortran /usr/bin/gfortran-${GCC_V} \
        --slave /usr/bin/gcov gcov /usr/bin/gcov-${GCC_V}

@zbeekman
Re MSYS2, using pacman, the current gcc is 9.2.0.  There is discussion about adding a MSYS2 install to the Windows image(s).  One can pre-install just gcc, or it could be switched to toolchain.
toolchain has the following additional packages:
gcc-ada
gcc-fortran
gcc-libgfortran
gcc-objc

Would you prefer than toolchain is used?

Good day!
We have added gcc, gfortran and clang tools on Windows and Ubuntu virtual environments in #369

@MSP-Greg can you please elaborate on what toolchain is and how to use it? Or point me to the docs? I’m afraid I’m not familiar and don’t quite follow.

@ivan-nosar Any word on macOS?

@zbeekman
Sorry. toolchain is a group available when using pacman on MSYS2.  You mentioned 'gfortran' and I assume the MSYS2 packages gcc-fortran & gcc-libgfortran would be the equivalent?  All I use is gcc...

@MSP-Greg Thanks for clarifying. I'm not a big Aur or MSYS/Windows user so not super familiar with pacman. So to clarify, toolchain is a meta-package, I presume.

I assume the MSYS2 packages gcc-fortran & gcc-libgfortran would be the equivalent?

Yes, gfortran is the Fortran compiler in the GCC suite. Hopefully you get libgfortran when you install gcc-fortran otherwise it definitely won't work... that's the language's runtime library (GCC specific).
I don't know if you need GCC Objective C or Ada, (I don't use either personally... not yet at least) but I definitely need gcc g++ and gfortran including the GFortran runtime lib which is presumably a dependency no matter what.
Hopefully through msys there's a straight forwards way to get the GCC 8.x tooling too, (for consistency with Linux/macOS) but, so long as GCC 8 tooling is a relatively snappy install, I'll be fine with gcc/g++/gfortran 9.2 on Windows.

@zbeekman
JFYI:
MSYS is rather old and has really been replaced by MSYS2.  One main difference is MSYS2 added pacman.
Because of pacman, 'there is only one', and downgrading to GCC 8 requires knowing where to download the older files from.
The main reason I've asked is that other Windows CI systems have MSYS2 installs with a lot more packages that 'standard shell and compile tools'.  I'm trying to help determine what is reasonable...

@MSP-Greg yeah, sorry I meant MSYS2 not MSYS. I guess that makes sense: if Pac-Man is what Aur uses then it’s a rolling release type manager like homebrew. If the only good/easy solution on Windows is GCC 9 I’m good with that. It will match Homebrew more closely and I’d rather be forced into a GFortran that’s newer than I want instead of older. That means fixes should come around faster even if there is higher exposure to regressions.

Hello, All
We have added gcc8 for Ubuntu 18.04 in #369. It should start rolling out early next week, once the rollout start it shows up as a pre-release here: https://github.com/actions/virtual-environments/releases
After that it takes about 6-7 days to reach all accounts (assuming no delays)

@pefoo the image has been rolled out. Could you check gcc, please?

gcc-8:
jobs:
  build:
    runs-on: [ubuntu-latest]
    steps:
    - name: gcc
      run: |
        gcc-8 --version
      shell: bash

@miketimofeev Removed the compiler installation and checked the build. Looks great! Thank you.


Privatize local memory for tensors

The pack-peel pipeline, matmul (m=n=1024, k=512) followed by addition of a bias (1-d vector with 1024 values) results in the final allocations (I've renamed the SSA values for clarity).
%bias_local = memref.alloc() : memref<1x16x4xf32, 2 : i32>
%bias_shared = memref.alloc() : memref<2x64xf32, 1 : i32>
%B_local = memref.alloc() : memref<1x1x16x8x8x4xbf16, 2 : i32>
%A_local = memref.alloc() : memref<1x1x8x16x4x8xbf16, 2 : i32>
%B_shared = memref.alloc() : memref<1x2x64x64xbf16, 1 : i32>
%A_shared = memref.alloc() : memref<2x1x64x64xbf16, 1 : i32>
%C_local = memref.alloc() : memref<2x2x16x16x4x4xf32, 2 : i32>
%C_shared = memref.alloc() : memref<2x2x64x64xf32, 1 : i32>

The above is for a design using a 2x2 array of AIE cores. The IR contains a loop over the 2x2 cores, indexing into arrays as follows
 scf.forall (%arg2, %arg3) in (2, 2) {

// Copy from slice of shared-memory A, to local-memory for A
%subview_14 = memref.subview %A_shared[%arg2, 0, 0, 0] [1, 1, 64, 64] [1, 1, 1, 1]...
iree_linalg_ext.pack %subview_14 outer_dims_perm = [0, 1, 3, 2] inner_dims_pos = [2, 3] inner_tiles = [4, 8] into %A_local ...

%subview_15 = memref.subview %B_shared[0, %arg3, 0, 0] [1, 1, 64, 64] [1, 1, 1, 1]...
iree_linalg_ext.pack %subview_15 outer_dims_perm = [0, 1, 3, 2] inner_dims_pos = [2, 3] inner_tiles = [8, 4] into %B_local ...

%subview_16 = memref.subview %C_local[%arg2, %arg3, 0, 0, 0, 0] [1, 1, 16, 16, 4, 4] [1, 1, 1, 1, 1, 1]...

 ...
 }

For A and B, a view into shared memory is copied to the entire local buffer for A and B. For C, a slice of the local buffer is taken.
I find this very confusing, and think it would be much better if C was already 'privatized' per core, so that instead of
%C_local = memref.alloc() : memref<2x2x16x16x4x4xf32, 2 : i32>

the allocation was
%C_local = memref.alloc() : memref<2x2x16x16x4x4xf32, 2 : i32>

and then it would effectively just be
%subview_16 = %C_local

This seems like it would be more inline with how GPU abstraction works (I'm thinking of OpenCL kernels). I think there shouldn't ever be a contiguous block of memory representing all data memories IMO.

Thanks for the write up!
I think this is not what you meant:

I find this very confusing, and think it would be much better if C was already 'privatized' per core, so that instead of
%C_local = memref.alloc() : memref<2x2x16x16x4x4xf32, 2 : i32>

the allocation was
%C_local = memref.alloc() : memref<2x2x16x16x4x4xf32, 2 : i32>

The last one should be:
%C_local = memref.alloc() : memref<1x1x16x16x4x4xf32, 2 : i32>

?


nixos/xonsh: source NixOS environment

Without doing that, xonsh is unusable as login shell.
:warning: Note that even with that change, setting users.users.<name?>.shell to xonsh for my user prevents me from successfully logging into GNOME 3 from GDM (and maybe prevents any graphical login - didn't test with other login managers or DEs / WMs, yet). But at least I get a usable xonsh shell in text mode (virtual terminal accessible with Ctrl-Alt-F1 etc.), which I didn't get without this change. (Without the change, xonsh would start on login, but would be nearly unusable as almost all external commands would have to be invoked through their absolute path, because they wouldn't be on $PATH.)
Motivation for this change
If a shell can be allowed as an interactive login shell (and NixOS option programs.xonsh.enable does that, if I understand correctly), it should be usable as a login shell, and logging into it should yield that shell in a usable state.
Things done

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

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

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

Result of nixpkgs-review pr 84330 1
[empty]

/cc current maintainers of the xonsh package: @spwhitt, @vrthra

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/can-i-use-xonsh-as-my-login-shell-if-so-how/6472/8

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/142

There is only one issue I noticed: the warning about aliases (only ls for me) beign ignored because they would override a xonsh built-in alias. I'm not sure which option between ignoring with --suppress-skip-message or overwriting with --overwrite-alias is better but the warning is pretty annoying if you are using this as your daily shell.

Xonsh doesn't distinguish between aliases and its builtin functions:
>>> aliases
xonsh.aliases.Aliases(
{'EOF': <function xonsh.aliases.xonsh_exit>,
 'bg': <function xonsh.jobs.bg>,
 'cd': <function xonsh.dirstack.cd>,
 'completer': <function xonsh.completers._aliases.completer_alias>,
 'dirs': <function xonsh.dirstack.dirs>,
 'egrep': ['egrep', '--color=auto'],
 'exec': <function xonsh.aliases.xexec>,
 'exit': <function xonsh.aliases.xonsh_exit>,
 'fg': <function xonsh.jobs.fg>,
 'fgrep': ['fgrep', '--color=auto'],
 'grep': ['grep', '--color=auto'],
 'history': <function xonsh.history.main.history_main>,
 'ipynb': ['jupyter', 'notebook', '--no-browser'],
 'jobs': <function xonsh.jobs.jobs>,
 'popd': <function xonsh.dirstack.popd>,
 'pushd': <function xonsh.dirstack.pushd>,
 'quit': <function xonsh.aliases.xonsh_exit>,
 'replay': <function xonsh.replay.replay_main>,
 'scp-resume': ['rsync', '--partial', '-h', '--progress', '--rsh=ssh'],
 'showcmd': <function xonsh.aliases.showcmd>,
 'source': <function xonsh.aliases.source_alias>,
 'source-bash': ['source-foreign', 'bash', '--sourcer=source'],
 'source-cmd': <function xonsh.aliases.source_cmd>,
 'source-foreign': <function xonsh.aliases.source_foreign>,
 'source-zsh': ['source-foreign', 'zsh', '--sourcer=source'],
 'timeit': <function xonsh.timings.timeit_alias>,
 'trace': <function xonsh.aliases.trace>,
 'which': <function xonsh.xoreutils.which.which>,
 'xexec': <function xonsh.aliases.xexec>,
 'xonfig': <function xonsh.aliases.xonfig>,
 'xonsh-reset': <function xonsh.aliases.xonsh_reset>,
 'xontrib': <function xonsh.xontribs.xontribs_main>,
 'xpip': ['sudo',
  '/nix/store/ljbn79cwlwvrlmqil0nk4zvf043ph592-python3-3.7.5/bin/python3.7',
  '-m',
  'pip']})

Therefore, I'm reluctant to --overwrite-alias which potentially would let the NixOS environment silently override important xonsh commands.
On the other hand, --suppress-skip-message could silently discard aliases the user specified in NixOS option environment.shellAliases.
Thus I think we should gracefully handle the known alias collision(s), but have that warning message appear again for unexpected collisions. For an otherwise default configuration, ls seems indeed to be the only colliding alias name.
Xonsh sets ls to ls --color=auto -v while Bash picks up the ls alias ls --color=tty from a environment.shellAliases default override value. Those are similar enough that it shouldn't much matter, which one we choose. I arbitrarily decided to keep xonsh's and have implemented that in this change to this PR.

If you have no objections I'm going to merge this: it's already an improvement over the current state of xonsh.

If you have no objections I'm going to merge this:

Me? I have no objections to merging this, or I would have filed it as WIP PR instead of regular PR.

it's already an improvement over the current state of xonsh.

That's my take, too, @rnhmjoj. :shipit: Let's ship it!
Should it be backported to 20.03 or would that be too surprising a change?

That's my take, too, @rnhmjoj. :shipit: Let's ship it!

Good, let's do it.

Should it be backported to 20.03 or would that be too surprising a change?

Uhm, I'm not too keen on backporting non-bugfix changes after the feature-freeze. It should probably be safe but it may have some unintended consequences...

:warning: Note that even with that change, setting users.users.<name?>.shell to xonsh for my user prevents me from successfully logging into GNOME 3 from GDM (and maybe prevents any graphical login - didn't test with other login managers or DEs / WMs, yet). But at least I get a usable xonsh shell in text mode (virtual terminal accessible with Ctrl-Alt-F1 etc.), which I didn't get without this change. (Without the change, xonsh would start on login, but would be nearly unusable as almost all external commands would have to be invoked through their absolute path, because they wouldn't be on $PATH.)

Tried it on nixos-unstable now and it works fine with GNOME 3. :tada:
Dunno what was up when I tried it on release-19.09

@das-g I was down the same adventure as you yesterday. I've successfully managed to make xonsh my login shell in TTY, but SDDM->KDE fails.
I also had to configure wrap xonsh in a shell script to set XDG_CONFIG_HOME set before launching it, else it'd fail finding RC files.
Are you still running xonsh as your login shell?

Are you still running xonsh as your login shell?

Yes, I am. But quite some stuff doesn't work as I'd expect in my setup, e.g. there's no command completion for Git subcommands and their arguments and options. PRs welcome!

@das-g https://github.com/Lillecarl/nixos/blob/master/lillecarl/dotfiles/.config/xonsh/rc.xsh#L41 Not sure if that's related to your issue, but for me adding bash completion support from current-system worked out just great, I have bash-completions for git, and a lot of other tools.


This share can't be found. Please check your link.

upload a file
generate link
open link
get error " This share can't be found. Please check your link."

url - https://pingvin.MYDOMAIN.nl/share/SHARECODE

Are you sure that the share isn't expired? If you don't mind could you share a GIF of the bug reproduction?

Hi there! sadly i cannot screen record atm due to restrictions this being my work laptop. however, i never get the 'share ready' popup.

https://pingvin.DOMAIN.nl/api/shares/GENERATEDCODE/files
{"statusCode":400,"message":"Validation failed (expected size is less than 5)","error":"Bad Request"}

Fixed! i set max filesize to '5g' because i didnt read the manual :P


Remove gotestfmt

Engineers noticing gotestfmt reporting test output in a confusing way, such as mis-attributing logs from one test to another or not reporting logs if a panic is encountered. This change removes this utility, switching to default Go test output. It also removes the -v flag so that the test failure output is minimally scoped to the failing tests and is easier to find. Defaults for the win.

@t0yv0, @guineveresaenger Late to the party but we've had the same issues in azure-native and I had good initial result with tparse. Here's a draft PR; you can look at the test results. It's essentially just regular go test output but with a summary at the end.


Deep copy config value store

Config providers were updated for smart default support to be deep copy-able. This change makes the session always deep copy the config value store when creating a client.
This also fixes a bug when deep copying the config value store. Previously, override values were not preserved. The fix adds the override values to the new copy of the value store.
Tests are added for the existing config providers that they can be deep copied, and existing smart default tests are moved to functional tests and used with a test defaults data file.

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.03 :warning:

Comparison is base (f6dbe19) 93.29% compared to head (9c7bf4b) 93.27%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@                     Coverage Diff                      @@
##           configured-endpoint-urls    #2950      +/-   ##
============================================================
- Coverage                     93.29%   93.27%   -0.03%
============================================================
  Files                            64       64
  Lines                         13588    13590       +2
============================================================
- Hits                          12677    12676       -1
- Misses                          911      914       +3

Impacted Files
Coverage Δ

botocore/configprovider.py
94.16% <100.00%> (+0.06%)
:arrow_up:

botocore/session.py
96.88% <100.00%> (-0.01%)
:arrow_down:

... and 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[WIP] Created a new aperture NRCA5_TAGRISMTS32_F405N

This is a test PR. NIRCam modified the nircam_siaf_aperture_definition.txt file adding a new aperture: NRCA5_TAGRISMTS32_F405N
This aperture will allow target acquisition in F405N, thus extending the magnitude range of available TA stars.
In this test PR we are just adding a new line in the file. We will actually enter the correct values at a later time

This was a test and can be closed


logger: [X] Unable to install yq even after a retry. Exiting.

hello,
trying to get detection lab working but getting this error when i reach the stage where logger will be configured:
logger: [X] Unable to install yq even after a retry. Exiting.
logger: W: Target Translations (multiverse/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:13
logger: W: Target Translations (multiverse/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:13
logger: [18:49:00]: [TEST] Validating that suricata is correctly installed...
logger: [+] suricata was successfully installed!
logger: [18:49:00]: [TEST] Validating that crudini is correctly installed...
logger: [+] crudini was successfully installed!
logger: [18:49:00]: [TEST] Validating that yq is correctly installed...
logger: [-] yq was not found. Attempting to reinstall.
logger: package github.com/mikefarah/yaml/v2: cannot find package "github.com/mikefarah/yaml/v2" in any of:
logger: 	/usr/local/go/src/github.com/mikefarah/yaml/v2 (from $GOROOT)
logger: 	/root/go/src/github.com/mikefarah/yaml/v2 (from $GOPATH)
logger: cp:
logger: cannot stat '/root/go/bin/yq.v2'
logger: : No such file or directory
logger: [X] Unable to install yq even after a retry. Exiting.

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
then installation will stop with also missing the installation of WEF machine
i'm using a mac book pro late 2018 version with osx catalina 10.15.1 and provide vmware_desktop
any ideas ?
thanks

sorry i have seen this issue has already been posted and closed as well thanks and sorry for a double post


Contract::CnC Question

Description of the CnC operation:
Counts number of global state items of the provided type in the contract state and puts the number to the destination a16 register.
and the parameters:
CnC(AssignmentType, Reg32),
I don't understand if we aim to count the global state items in the contract state, why there is the AssignmentType but not the GlobalStateType.
I know the AssignmentType works for the data, fungible, structure, and attachment state.

https://github.com/RGB-WG/rgb-core/pull/208
I read this pull request, so the reason for the AssignmentType added here is we can add the contract state in the VM, and then we can compute the global state based on the whole contract state?

This is error, you are right, it should be GlobalStateType. Will work on the fix

Closed in #255


Fix formatting for "[1 2]" and similar

When validating expressions like [1 2], the result is clearly invalid.
However, the formatter outputs the following:
[
    12
]

Clicking Validate for a second time would now return this as valid.
This change attempts to preserve some of the whitespace in invalid JSON. It's
not perfect, but it avoids the scenario described above.

We appreciate any collaboration. Unfortunately we cannot approve this pull request since jsonlint.com is rewritten from scratch and this issue is fixed.


Please help noob

I'm ros2 noob.
I use ouster lidar for slam.
I want to know what I have to change to use this package.

The velodyne_points in the mapping should work if you change them to the ouster point topic and also change the frame ID of velodyne in tf to the frame ID of the ouster point topic.
https://github.com/rsasaki0109/lidarslam_ros2/blob/develop/lidarslam/launch/lidarslam.launch.py#L24-L36

Thank you for your answer. Now, I can use your package. However, I have two more questions.

When I launched this package and played the bag file, I couldn't see the /modified_path and /modified_map. When I echoed the topics, no information came out. I think there might be an issue with the graph-based-slam node.

I didn't change any parameters without ndt_num_threads. I changed ndt_num_threads to 4. While it works well in simple environments, it doesn't perform as expected in more complex environments. How can I adjust the parameters in this situation.

file:///home/user/Pictures/Screenshots/Screenshot%20from%202024-08-21%2002-56-53.png
file:///home/user/Pictures/Screenshots/Screenshot%20from%202024-08-21%2003-05-57.png

Graph-based SLAM will not publish trajectories and maps unless you perform a loop closure or execute "ros2 service call /map_save std_srvs/Empty". If you do not perform a loop closure, please execute "ros2 service call /map_save std_srvs/Empty".
The point cloud map in the image does not seem to have any obvious problems, but what is the issue?
Generally, you need to adjust parameters such as ndt_resolution and vg_size_for_input depending on whether the environment is indoors or outdoors.

Thanks, I understand the problem.


Error on Test Connection

Description
I'm trying to install DBeaver but when I make the configuration steps, that shows me this error.

DBeaver Version
DBeaver Community 23.1.3
Operating System
macOS Intel Core i5
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Please add more details. What database are you trying to connect to? How exactly are you configuring connection?

I’m trying to connect on this database: MWNCDSNB
I’m following these steps to configurate: https://ibm.ent.box.com/s/rfhe2s94greayd4mt1tkabz0l1zx4a2k
[A screenshot of a computer  Description automatically generated][A screenshot of a computer  Description automatically generated]
Isabella Valêncio Bueno
Workforce Staffing Professional
IBM Consulting - Brazil Workforce Management
19 99160 1991 (Mobile)
<EMAIL_ADDRESS>Privacy Disclaimer: This e-mail, including attachments, is for the sole use of the individual(s) to whom it is addressed, and may contain PIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi or SPIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi data. Any unauthorized review, use, disclosure or distribution is prohibited. Once the intended use has been completed, please destroy any PIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi or SPIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi data, along with this message. If you have received this email in error, please notify the sender by reply email and destroy this message and its attachments.
From: Elizabeth @.>
Date: Monday, 24 July 2023 09:16
To: dbeaver/dbeaver @.>
Cc: Isabella Valencio @.>, Author @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Error on Test Connection (Issue #20662)
Please add more details. What database are you trying to connect to? How exactly are you configuring connection? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. Message
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
Report Suspicious  https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!2W-rSPTVYnMy-c8xkittRBc6Ix7gIK7zWCYG40COsZbmr24orrWdorRf3qVc5LMZMImQ6jdGywOhvsftpd3iACqG1zU3v8Osymk$
ZjQcmQRYFpfptBannerEnd
Please add more details. What database are you trying to connect to? How exactly are you configuring connection?
—
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/20662#issuecomment-1647802123, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBPGLVZLYSUNSDDWKMLFBWTXRZRSHANCNFSM6AAAAAA2VPWT34.
You are receiving this because you authored the thread.Message ID: @.***>

Screenshots doesn't come to github if you reply on a notification email. Please, attech them in a comment to the issue directly.

Sorry. Here you go.

Hello @valencio2
On the assumption of the error message from the first screen - you need to specify the SSL Trust store file path in the sslTrustStoreLocation property.
Like:
Security/SSL/certificates/myTrustStore.jks

How could I get this info in Mac? Could you please help me with this?
Isabella Valêncio Bueno
Workforce Staffing Professional
IBM Consulting - Brazil Workforce Management
19 99160 1991 (Mobile)
<EMAIL_ADDRESS>Privacy Disclaimer: This e-mail, including attachments, is for the sole use of the individual(s) to whom it is addressed, and may contain PIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi or SPIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi data. Any unauthorized review, use, disclosure or distribution is prohibited. Once the intended use has been completed, please destroy any PIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi or SPIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi data, along with this message. If you have received this email in error, please notify the sender by reply email and destroy this message and its attachments.
From: Anastasiya @.>
Date: Monday, 24 July 2023 10:39
To: dbeaver/dbeaver @.>
Cc: Isabella Valencio @.>, Mention @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Error on Test Connection (Issue #20662)
Hello @valencio2 On the assumption of the error message from the first screen - you need to specify the SSL Trust store file path in the sslTrustStoreLocation property. Like: Security/SSL/certificates/myTrustStore. jks — Reply to this
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
Report Suspicious  https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!2W-rSPTVYnMy-c8xkittRBc6Ix7gIK7zWCYG40COsZbmr24ojtV9o_Uf3qVc5LMZT7cbJSPYyFu85zabtXVey-uaUAkdIE6j8DE$
ZjQcmQRYFpfptBannerEnd
Hello @valencio2https://github.com/valencio2
On the assumption of the error message from the first screen - you need to specify the SSL Trust store file path in the sslTrustStoreLocation property.
Like:
Security/SSL/certificates/myTrustStore.jks
—
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/20662#issuecomment-1647935189, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBPGLVY3WUJYUXYO4TUAESTXRZ3GZANCNFSM6AAAAAA2VPWT34.
You are receiving this because you were mentioned.Message ID: @.***>

You put the path to the directory containing the file instead of the path to the file in sslTrustStoreLocation driver property. It's not something mac-specific, just put a valid path there.

Ok, but my question is: how could I get the information of path to the directory? Is in “Get info” > “where” on Mac?
Isabella Valêncio Bueno
Workforce Staffing Professional
IBM Consulting - Brazil Workforce Management
19 99160 1991 (Mobile)
<EMAIL_ADDRESS>Privacy Disclaimer: This e-mail, including attachments, is for the sole use of the individual(s) to whom it is addressed, and may contain PIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi or SPIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi data. Any unauthorized review, use, disclosure or distribution is prohibited. Once the intended use has been completed, please destroy any PIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi or SPIhttps://w3.ibm.com/ibm/privacy/guidance-on-pi-spi data, along with this message. If you have received this email in error, please notify the sender by reply email and destroy this message and its attachments.
From: Elizabeth @.>
Date: Monday, 24 July 2023 11:10
To: dbeaver/dbeaver @.>
Cc: Isabella Valencio @.>, Mention @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Error on Test Connection (Issue #20662)
You put the path to the directory containing the file instead of the path to the file in sslTrustStoreLocation driver property. It's not something mac-specific, just put a valid path there. — Reply to this email directly, view it on GitHub,
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
Report Suspicious  https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!2W-rSPTVYnMy-c8xkittRBc6Ix7gIK7zWCYG40COsZbmr24oj5VdQtSf3qVc5LMZcznA-z1oNzUkjScdqDnEKevGOkFpWUOSlbw$
ZjQcmQRYFpfptBannerEnd
You put the ge the file instead of the path to the file in sslTrustStoreLocation driver property. It's not something mac-specific, just put a valid path there.
—
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/20662#issuecomment-1647994615, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBPGLV2CIRDBJHAKEOP7FR3XRZ63VANCNFSM6AAAAAA2VPWT34.
You are receiving this because you were mentioned.Message ID: @.***>

I can't help you there as I'm not a mac user, but you could google it.

This problem is solved, but now we have another error

You need to contact your database administrator as your password has been expired.

Yes, I contact him. I have here another temporary passphrase and the guide is that I need to change the password inside DBeaver.

If you're unable to use the passphrase due to an application and/or
system restriction use CLAS option 1.1.1 to request a password.
NOTE:  When you logon to the system and type in the above temporary
passphrase a message may be displayed: "The Passphrase has EXPIRED",
this is a normal RACF message which requires you to type in a new
passphrase. After typing a new passphrase, RACF asks you to verify
the passphrase you just typed in, so you need to type it in again.