Update dependencies

Landed in https://github.com/metarhia/metarhia.com/commit/98bd1a9ee00f6e4ad42ffd6e4904198cfa035716

Landed in https://github.com/metarhia/metarhia.com/commit/98bd1a9ee00f6e4ad42ffd6e4904198cfa035716


Bug in buildMatrixUnique( reference_omp )

Closes #216

Hi @byjtew -- various MRs point to this one as required, but this one is still in a draft state, correct? (Should we prioritise finishing this one?)


Compiled Osiris.dll gets detected as Trojan:Win32/Wacatac.B!ml

Compiling the Source Code makes Windows Security alert me about it finding Trojan:Win32/Wacatac.B!ml in the compiled Osiris.dll File.
Any ideas why?

Make a program that terminates any process and send it for analysis, it will probably be detected, as Osiris is a loadable DLL, can be used maliciously, to fix this it is necessary to perform code signing, which solves most of these problems, making antivirus "trust" her.

Any cheating software may be detected as malware. Osiris is open-source and you are able verify if the software is safe yourself.


Fix #74

Codecov Report

Merging #75 into master will increase coverage by 0.11%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
+ Coverage      82%   82.12%   +0.11%
==========================================
  Files          28       29       +1
  Lines        1712     1723      +11
==========================================
+ Hits         1404     1415      +11
  Misses        308      308

Impacted Files
Coverage Δ

tests/ut_main.d
100% <ø> (ø)
:arrow_up:

tests/ut/conv/misc.d
100% <ø> (ø)
:arrow_up:

tests/ut/issues.d
100% <100%> (ø)

source/xlld/conv/from.d
95.67% <100%> (+0.22%)
:arrow_up:

source/xlld/conv/misc.d
50.64% <100%> (+0.64%)
:arrow_up:

Continue to review full report at Codecov.

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


This is really cool! Will definitely use this!

Thank you!
Just curious, what do you miss on the project to start using it already?
I'm trying to get feedback to see how the project can be improved.

Haven't used it yet, today I'm going to make a little project :) But I'll post my ideas, and things here :D

Well, first impressions after doing the "Draw Triangle" example, there are alot of dependencies, so the initial build, took a while for me, but also just running cargo run after the initial build still took about 8 seconds for me, but so far really good!

I think you should rename the .set_config() to .add_config().  Which is a little confusing, because it sounds like you are overriding the first one.

Well, first impressions after doing the "Draw Triangle" example, there are alot of dependencies, so the initial build, took a while for me, but also just running cargo run after the initial build still took about 8 seconds for me, but so far really good!

Yeah, I'm trying to only use what I need as dependencies, not sure if I can remove some of them, I'll check it. Although for the next version (develop and f/egui branches) I cleaned up a little the dependencies.

I think you should rename the .set_config() to .add_config().  Which is a little confusing, because it sounds like you are overriding the first one.

This makes sense to me, already changes on the develop' branch. It will arrive on the 0.2.0` version.

I really like having the ability to write shaders, and directly integrate them into the rendering! I also, like how the asset loading works. I got a little animated pixel art character moving around the screen with the arrow keys, and got it working on WASM! The only thing right now is, I can't figure out how to flip the character

The initial idea of the draw2d render was to provide an easy way draw on the screen but allowing the user to use their own matrices to transform the render. I added some helpers like rotate_fromor scale_from to help with the transformation, and I guess that I can add another function to help with the mirroring, it makes sense because it's something common.
A workaround for now could be scale_from(your_center_point, (-1, 1)). That should flip the object horizontally from the center. But as I said I'll think about add a flip function.
Thanks you so much for your feedback! If you find anything else let me know!

Ok that's good! Your welcome :) I'll try adding that to my little test project :smile:

Closing this, feel free to reopen o create a new issue if you think that we should change or add something. Thanks!

Alrighty!


Closure-compiler errors on current master

I cloned the current master, ran npm install, bower install and gulp build -p and got following build errors and warnings:
[19:59:04] Starting 'compile-clientapp'...
[19:59:12] Command failed: /tmp/8c1a6e26-86eb-4cef-a622-7d0b1835ceb6/bower_components/closure-library/closure/goog/asserts/asserts.js:358: WARNING - Property displayName never defined on Function
    return value.displayName || value.name || 'unknown type name';
           ^

/tmp/8c1a6e26-86eb-4cef-a622-7d0b1835ceb6/bower_components/closure-library/closure/goog/asserts/asserts.js:360: WARNING - Property displayName never defined on Function
    return value.constructor.displayName || value.constructor.name ||
           ^

bower_components/react-externs/externs.js:1576: WARNING - Bad type annotation. missing opening [
   * @param {function (new:Object, ...*): ?} expectedClass
                                      ^

/tmp/eec20035-44aa-46e6-9057-4411a755f85e/bower_components/closure-library/closure/goog/base.js:236: ERROR - illegal initialization of @define variable goog.DISALLOW_TEST_ONLY_CODE
goog.define('goog.DISALLOW_TEST_ONLY_CODE', COMPILED && !goog.DEBUG);
                                            ^

1 error(s), 3 warning(s), 96.2% typed

Unfortunately I have no idea how to fix this problem.

I'm getting the same error, albeit in a project of my own. Was led here by google ;)
What was your fix? Upgrading/Downgrading closure? If yes, to which revision?

bower cache clean, for some reason bower caches downloaded zip. Btw, in new ES6 Este, I don't use bower anymore. Closure Tools were moved into npm.
"google-closure-compiler": "^20150315.0.2",
"google-closure-library": "^20150315.0.0",


Get example how to use writre to a zip archive

Hello,
I'm trying PhyFS, seams really intresting but there is no example how to use write.
Result is a corrupted zip file
It would be great if I can get some help to understand what is wrong.
I'm using 3.3 release.
here is my simple code:
PHYSFS_init("d:\");
PHYSFS_setWriteDir("d:\");
PHYSFS_mount("d:\\testw.zip", "/" , true);

const char* writedir =  PHYSFS_getWriteDir();
std::cout << writedir << std::endl; // for testing

PHYSFS_File* txtwtest = PHYSFS_openWrite("/txt2.txt");
int test = PHYSFS_writeBytes(txtwtest, "testwr", 5); // return 5 so it did write somewhere
PHYSFS_close(txtwtest);

PHYSFS_unmount("d:\\test.zip");
PHYSFS_deinit();

You can't write to zip files. It (currently) only allows writing to loose files on the actual filesystem.

I confirm, I can write to the local filesystem. Is it a limitation due to
zip archive or more global ?
On Mon, Aug 14, 2023 at 5:41 PM Ryan C. Gordon @.***>
wrote:

You can't write to zip files. It (currently) only allows writing to loose
files on the actual filesystem.
—
Reply to this email directly, view it on GitHub
https://github.com/icculus/physfs/issues/67#issuecomment-1677578901, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWTBT3ZPS4Q3JADNYHPVDTXVJBK3ANCNFSM6AAAAAA3PIXK5I
.
You are receiving this because you authored the thread.Message ID:
@.***>

The API allows it, but it's not implemented for anything but the native filesystem. There are questions about how to rewrite a .zip file to make this work cleanly, since you'd have to deal with the existing data, etc.


Add the Bridgewater page

Add the following page: https://www.metaculus.com/bridgewater/
As a static page.

We didn't do this: https://old.metaculus.com/bridgewater/


fix the search in the table and now you can search with  multipl lang…

There was error in searching in the table

i have solved.
i edited the function applySearchConstraintToQuery in the following path src\SpatieLaravelTranslatableContentDriver.php

Please share your MySQL version, I think I've seen people attempt something similar before and it causes issues

Please share your MySQL version, I think I've seen people attempt something similar before and it causes issues

The idea is that the language you have selected (in LocaleSwitcher) is the one you are searching in. Currently, we do not have plans to break this behaviour, but you can always pass in a custom function to searchable() to change the query that is used to search


failure to inline avx intrinsic

I'm compiling on a system that has AVX, with gcc version 7.4.0-1ubuntu1~18.04.
I ran into this error:
[ 29%] Building CXX object CMakeFiles/PaSGAL.dir/src/main.cpp.o
In file included from /usr/lib/gcc/x86_64-linux-gnu/7/include/immintrin.h:45:0,
                 from /home/erik/PaSGAL/src/include/base_types.hpp:10,
                 from /home/erik/PaSGAL/src/include/parseCmdArgs.hpp:10,
                 from /home/erik/PaSGAL/src/main.cpp:12:
/usr/lib/gcc/x86_64-linux-gnu/7/include/avx512fintrin.h: In static member function ‘static __mxxxi psgl::SimdInst<int>::add(const __mxxxi&, const __mxxxi&)’:
/usr/lib/gcc/x86_64-linux-gnu/7/include/avx512fintrin.h:818:1: error: inlining failed in call to always_inline ‘__m512i _mm512_add_epi32(__m512i, __m512i)’: target specific option mismatch
 _mm512_add_epi32 (__m512i __A, __m512i __B)
 ^~~~~~~~~~~~~~~~
In file included from /home/erik/PaSGAL/src/include/align.hpp:20:0,
                 from /home/erik/PaSGAL/src/main.cpp:14:
/home/erik/PaSGAL/src/include/align_vectorized.hpp:48:95: note: called from here
       static inline __mxxxi add (const __mxxxi& a, const __mxxxi& b) { return _mm512_add_epi32(a, b); }
                                                                               ~~~~~~~~~~~~~~~~^~~~~~
CMakeFiles/PaSGAL.dir/build.make:62: recipe for target 'CMakeFiles/PaSGAL.dir/src/main.cpp.o' failed

Any suggestions about how to resolve it?

Check if the CPU you are using supports AVX512 or AVX2 or none...  you'll need to compile accordingly (see the cmake option -DSIMD_SUPPORT in README).
Assuming you are using linux, flags in /proc/cpuinfo will tell you the available SIMD support.

It looks like I have only avx and avx2:
-> % lscpu | grep Flags | tr ' ' '\n' | grep avx
avx
avx2

I'll try to set the flags accordingly.

Building with cmake -H. -Bbuild -DSIMD_SUPPORT=avx2 && cmake --build build -- -j 4 solves my problem!


Group imports by Std External Crate

Use group_imports = "StdExternalCrate" to format and group imports by:
[std, core, malloc, etc]
[extern]
[crate, super]

Nice!
For some reason we have two different rustfmt.toml files. We could try to consolidate later, but could you also update the one in the root of the repository? I think this one is used by cargo and maybe tools like vscode.

Looks like the root rustfmt.toml is a symbolic link to the file bazel/rules/rust/rustfmt.toml.
I did a find on the repo and couldn't find additional files:
rlukata@Ramis-MBP risc0 % find . -iname "rustfmt.toml"
./rustfmt.toml
./bazel/rules/rust/rustfmt.toml

Yes, I think you have to also format the stuff in methods/inner since it's a different workspace.

@shkoo Looks like they're already formatted and getting formatted. I've manually tried modifying some files in methods/inner and they all auto-format even when I view it from the risc0 workspace.


Manchester outreach : Social post Copy

In order to increase visability for the course we are creating and sharing a social post.

[x] write copy for the post
[x] brief design in marketing channel

https://docs.google.com/document/d/14neZlYmCd6O0Cs_Ns_lvdbxNB_XbH3ce8ILU3b-9tIo/edit


Security Disclosure

Where do I report a security bug?

Unfortunately, I forgot it, I'm gonna include a security reporting policy section in the docs.
Thanks a lot!

no I mean I have a security bug, is there somewhere I can reach out to you about it

If it's a high risk vulnerability, please report it to<EMAIL_ADDRESS>otherwise, kindly open another issue.

@asottile I'm waiting for your report, thanks again.


feat: Adding rules for subscriptions in avm/res/service-bus/namespace

Description
Adding rules for subscriptions in avm/res/service-bus/namespace
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[ ] I have run Set-AVMModule locally to generate the supporting module files.
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings

@microsoft-github-policy-service agree company="Zure"

Hey @timdhaeyer - This looks promising, I believe you also used the helper script. can you update the readme by running the set-avmmodule toolset as described here: https://azure.github.io/Azure-Verified-Modules/contributing/bicep/bicep-contribution-flow/generate-bicep-module-files/
Then run the workflow to test the new configuration in your subscription?

@ChrisSidebotham I have done what you requested. I added a test file that just creates a single rule inside a subscription. You can find it under the test files. Is this ok for you? :-)

@timdhaeyer - that looks alot better. Are you able to enable and run the workflow in your fork? you can then attach the status to the pipeline badges at the top of this PR?

 But what workflow should I run? :-)

Hey @timdhaeyer - sorry for the delay here, we made some changes last week. Can you just sync your local version and rerun the workflow. the Set-AVMModule may need rerunning.

Hey @timdhaeyer ,
Firstly, thanks for your work on this PR!
We have made some changes to the AVM CI, detailed below, which means we need you to update your fork to pull in these latest changes and re-run your tests to show they still are passing prior to approving and merging this PR, as we don't and it fails once merged the publishing of your module will fail and will be blocked going forward until the test pass again via additional PRs.
Changes to CI That Have Been Made That You Need To Take Action On

https://github.com/Azure/bicep-registry-modules/pull/3745

Adds WAF Security PSRule Checks using this custom baseline of rules (/avm/utilities/pipelines/staticValidation/psrule/.ps-rule/cb-waf-security.Rule.yaml)
Action Required By You:

Ingest/pull-in these changes into your PR branch and re-run your tests to ensure they pass

If any issues with the rules and you think it should apply, please ping/reach out to the core team

Any questions reach out to the AVM Core Team by tagging us in your PR here or internally via Teams
Thanks
Jack (AVM Core Team)

Closing in favor of #4106.
Note @timdhaeyer, the other PR is merely a rebase of this one with some smaller changes. You'll continue to be listed as the author of the changes you proposed in this PR.


Simplify SMT with context manager

things to test

[ ] all simple examples

@mxlei01 Would appreciate your eyes on this relatively small PR.


Remove the loopback iptables rules for docker

We have applied the following rules to allow connectivity to the service from the local network while using the docker backend:
iptables -t nat -A PREROUTING -d <IP_ADDRESS> -j DNAT --to-destination <IP_ADDRESS>
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

The PREROUTING rule was rewriting the destination IP address of any packets received by the local system and destined for the TAP device to <IP_ADDRESS>. While the POSTROUTING chain rule was rewriting the source IP address of any packets being sent out through the gateway (eth0) network interface to the IP address of that network interface (eth0). However, there seem to have been some changes that make these rules unnecessary, since connecting to the service while on the local network (inside the VM) works just fine now.
Fixes: https://github.com/rancher-sandbox/rancher-desktop/issues/4997

The change looks relatively isolated, but I'm on confident that I have all the code paths in my head…

Quick note for testing purposes:
This was initially introduced for the following condition:
Namespaced Network enabled + Moby backend
Therefore to test this we should consider the following scenarios:

Namespaced network + Moby Backend + k8s enabled
Namespaced network + Moby Backend + k8s disabled


Social Likes 4

No counters.
No jQuery.
IE10+.
ES6 + Webpack.
No web fonts or PNGs (SVG icons).
No classic skin.
Tests.

No ETA, will publish a branch name later.
To do:

[ ] Webpack JS build.
[ ] JSCS + JSHint → ESLint.
[ ] Skins build (Webpack?).
[ ] New builder page.
[ ] Autopublish builder page to gh-pages (gulp-gh-pages?).

Related issues: #136, #147.

I can help you with autopublish page when you will be done with other stuff, ping me when my help will be required

I did that before. But I have to update (most probably rewrite) a builder site first.

:boom: Social Likes Next 1.0.0 is out! :boom:


[go_router] Exposing some of the classes

Use case
When assigning some of the members of the GoRouter class to variables:
  final GoRouter goRouter = GoRouter(...);
  final GoRouteInformationProvider routeInformationProvider =  goRouter.routeInformationProvider;
  final GoRouterDelegate routeInformationParser =  goRouter.routeInformationParser;
  final GoRouterDelegate routerDelegate =  goRouter.routerDelegate;

I need to import the following implementation imports to make it work:
import 'package:go_router/src/go_route_information_parser.dart';
import 'package:go_router/src/go_route_information_provider.dart';
import 'package:go_router/src/go_router_delegate.dart';

Proposal
Would be nice if these could be exposed through the private API to avoid this.
I am using the implementation_imports lint and it is throwing a warning, that's how I noticed it to begin with.
Thank you for the great work!

Hello @atoka93. Thank you for filing this proposal. This looks like a valid feature request

I just noticed I wrote private API, I meant public API, exposed through the public API; sorry for the confusion.

so basically I would like to have:
export 'src/go_route_information_parser.dart';
export 'src/go_route_information_provider.dart';
export 'src/go_router_delegate.dart';

in go_router.dart or something similar.

Thanks for the clarification. I edited your comment to fix the typo. Hope you don't mind.
I'm a bit unsure, but does this mean that the current imports would break? Or would this work side-by-side with the way it's currently working?

Sure, thanks for fixing.
Both would work side by side

Why do you need to assign these to variables? You shouldn't need to import these libraries if you aren't using them directly:
import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

class App extends StatelessWidget {
  App({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) => MaterialApp.router(
        routeInformationProvider: _router.routeInformationProvider,
        routeInformationParser: _router.routeInformationParser,
        routerDelegate: _router.routerDelegate,
      );

  final GoRouter _router = GoRouter(
    // ...
  );
}

What's the reason you would prefer to use variables rather than getters as is currently written?

Oh, I see, because if I specify: <List<GoRouteMatch>> GoRouteMatch is not exposed.
Not ideal, I would then have a

closed it accidentally

@atoka93 Thanks for filing this issue, I'm going to move the conversation over to https://github.com/flutter/flutter/issues/107757, which will make these types abstract, and  change the return type of GoRouter.of().


Fix potential null reference access

Commit 9ad9df6cec4dc77a275ce50511c7e3d1fbdcb1d3 implemented synchronization of the course unit navigation state to the outline back stack upon returning to it. However the logic it used assumed that the unit block path size would not be smaller than the size of the current outline block path. Therefore it did not allow the possibility of null when getting the block corresponding to the last block in the outline path from the leaf. This commit fixes this issue by reverting the equals() operation, and thus allowing the possibility of null as a result of that check.

:+1:


architect.py

Hi, wonderful work!
I have a question regarding architect.py, hessian_vector_product.
From my understanding R is epsilon, grad_p,grad_n are gradients of loss for w+- (positive and negative)
Why in grad_n calculation you do p.data.sub_(2*R, v) And not p.data.sub_(R, v)?
Thanks!!

Note p was modified in place, so here we are actually doing w^+ - 2d = w^- instead of w - d = w-.


feature req. startup legality

currently in the deckbuilder, when you select "startup" in the collection tab, the legality box is unaffected, so standard-banned cards continue to be hidden despite not being banned in the startup format.
it'd be nice not to have to remember to manually change the legality to casual to see these cards.

I would like to work on this feature.
A couple of problems that I forsee:

Should clicking "standard" also change to the latest standard ban list?
The used collection is remembered between deckbuilding sessions, so new decks might directly begin with the Startup pool. Should this behaviour be kept? Should the banlist be turned off in this case too?

Really, the best solution would be to choose a format before even picking which ID to play, and have that persist into the deckbuilder. This would be more work, but probably worth it!
Thoughts?

hello!  I'm glad there is interest here.
I'll outline a couple of the challenges and a couple of the things we have started, but not finished yet.
Right now, NRDB has absolutely no notion of format.  Everything is standard by default.
We want to move to a model where we have good javascript (well, typescript really) APIs that are separate from the NRDB template code so we can use them in multiple places.  We've started a new set of typescript APIs in a new (currently private) repo until we have some of that sorted and in a better state.
How do you feel about helping with the JS API first so we can work out what that should do/what we need and then wiring it up to NRDB proper?
When @NoahTheDuke and I have chatted about this, we wanted to have:

first class format objects/datastructures with some deckbuilding restrictions
banlists should be tied to formats
rotations / card pools should be tied to formats (startup is quite a hack right now.  :D )

if we had all that, i would imaging decks and decklists would know the format and banlist and card pool they are for + we could swap out all the UI elements for banlist and card pool in one fell swoop in the UI.
Happy to chat about any of this on slack or discord as well.  Thanks again for wanting to help out here!  This is an area that could definitely use some improvements!

I was originally interested in this because it looked like something that I could write code for, finish, and leave alone fairly quickly without needing discussion over an extended period of time. Call again in a month or so and we can see if I'm more able to do that?
I'm not on slack or discord but you can reach me in this thread or in the email address on my github profile page.

heh, i hear ya.
Sadly NRDB wasn't designed for multiple formats and the few accommodations we have are fairly ad-hoc.


left column "this page" in Scanner docs

Might want to remove "this page" in the bottom left.  It's odd the template has that.
http://scanner.run/from_source.html

Just pushed a change for this


Akka 2.4.x support

@ironfish do you have any idea how much work this update is? I am thinking it would make sense to have a 2.4.x version in https://github.com/manuelbernhardt/reactive-web-applications/tree/master/CH07 and could perhaps contribute

It's something I am looking over now, and a priority. I'm looking to do the upgrade over the next two weeks.

@ironfish do you have an idea when you will be able to work on this upgrade? I am getting closer to wrapping up the book & code examples and it would be nice to be able to use a more recent version in the examples

@manuelbernhardt I'm working on it now. In addition to Akka 2.4 it will also include the new async driver.

@manuelbernhardt I've finished the changes for Akka 2.4.1. I will push in the next day or so after I have added additional tests.
Cheers,

@manuelbernhardt I have merged the Akka 2.4.1. and published to snapshot. Make sure you review the README as there are some changes around configuration you should be aware of.

@ironfish thanks! I will upgrade the chapter in the coming days with it

fixed by #100


Generate HTTP client from OpenApi spec

Look into to autogenerate HTTP client code and models from the OpenApi Spec from Swagger backend.

https://pub.dev/packages/openapi_generator


How to access contextBridge in Nuxt

Hello,
I have been using this but have been unable to access my preload commands in the app. Using window.myAPI.myfunction throws an error of undefined.
How do I resolve this? Does there need to be an additional import for it to work. See example code below.
preload.ts:
const {contextBridge, app} = require('electron')

const windowAPI = {
    closeWindow: () => app.quit
}

contextBridge.exposeInMainWorld("api", windowAPI);

index.vue:
<script setup lang='ts'>
const isFullscreen = ref(false)
const test = () => {
    isFullscreen.value = !isFullscreen.value
}

const quitApp = window.api.closeWindow()

</script>


Problem with default language.

Hello! I download your template and I try to change the default language to Japanese (ja) in config/site.js and when testing the page this happened:
module.exports = {
  title: "Gatsyby Startbootstrap Agency",
  keywords: [
    "gatsby",
    "gatsbyjs",
    "landing page",
    "landing",
    "i18n",
    "eslint",
    "bootstrap",
    "startbootstrap-agency",
  ],
  description: "gatsby version of startbootstrap-agency with i18n support.",
  author: "thundermiracle",
  trackingId: "UA-119418003-5",
  defaultLang: "ja",
  langTextMap: {
    en: "English",
    ja: "日本語",
  },
};

Both texts (in English and Japanese) are displayed at the same time in the NavBar. Also, if you try to change the language, an error will be displayed.

That's because there's no xxxx.en.md exists in /content folder.
As you changed default language to ja, all xxxx.md are considered as definitions for Japanese as well as all xxxx.ja.md, so the system crashed.
I'll add .en to all English markdown files and the problem will be gone.

Yes, sorry, hours later I realized that was the problem, but I was too late and I forgot to write here.
Right now I'm trying to get the page to detect the browser language to set that language as default. If I succeed, do you want a pull request to add it to the repository?

Yes, please. I’m looking forward to your PR.

Okay! If I get it, I'll open a pull-request. I proceed to close this. Have a nice day!


Update accessing-data-buffers-in-umdf-1-x-drivers.md

Point to UMDF 2 documentation for accessing data buffers to make it easier to discover in case someone lands on this page.

@tedhudek @wm1 fyi

Learn Build status updates of commit d8e2b38:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/wdf/accessing-data-buffers-in-umdf-1-x-drivers.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Thanks Shyamal, https://learn.microsoft.com/en-us/windows-hardware/drivers/wdf/accessing-data-buffers-in-umdf-1-x-drivers has the extra text now.


Select UI framework

Select a UI library to apply a consistent look and feel to our app. Options could include:

react bootstrap
tailwind CSS
blueprintjs
others?

chat-gpt contribution

bard contribution

I think my vote is Chakra UI

closed with 41a0892f824a5cdd5e18307f43f8a248cf78086a - Chakra UI it is


Could you please add md5 encryption in android studio with ndk example?

I'm trying to generate MD5 hash for a string, but i have problem with result. My result wrong on some device. This is my question in stackoverflow.
Could you please add example for md5 hash a string in android studio with ndk?

will need time to get to this one from my end; did post the SO question to a group, hopefully someone with MD5 expertise could race to get your question answered soon.

Oops, this is answered already, no need for this one to be around.


CHAR_WIDTH -> CHAR_SIZE to avoid collision with ISO/IEC TS 18661-1:20…

Backport of https://github.com/fmtlib/fmt/commit/abbefd71666055daac9e14e78262620f9e845850
See https://github.com/fmtlib/fmt/issues/398 for details.
Closes #183

Thanks!


Fix: remove illegal cast

Fixes #2221
Removed illegal cast int as bool:
return sqlValue as T;
Also removed _dialect check. I don't think it is needed here. Couldn't really tell what you were trying to archive here.

Is there a situation where we would need to check for _dialect?
Because in general a conversion int as bool should never work right?


Add SCSS / SASS support to the seed

SCSS / SASS is used throughout many projects.  Adding support for this for to the extension seed would reduce rework when creating a new extension.  If possible during setup we can ask if they would like to use SCSS or CSS.  Based on the answer the project should be setup to support the desired styling.

No plans to fix.


Add native dll resolver

PR Summary
Resolve #9488
Add a native dll resolver to discover and load native dlls based on OS platform and architecture.
PR Context
Releated #3091
If a managed dll has native dependencies the handler will try to find these native dlls.
1. Gets the managed.dll location (folder)
2. Based on OS name and architecture name builds subfolder name where it is expected the native dll resides:
3. Loads the native dll
managed.dll folder
                |
                |--- 'win-x64' subfolder
                |       |--- native.dll
                |
                |--- 'win-x86' subfolder
                |       |--- native.dll
                |
                |--- 'win-arm' subfolder
                |       |--- native.dll
                |
                |--- 'win-arm64' subfolder
                |       |--- native.dll
                |
                |--- 'linux-x64' subfolder
                |       |--- native.dll
                |
                |--- 'linux-x86' subfolder
                |       |--- native.dll
                |
                |--- 'linux-arm' subfolder
                |       |--- native.dll
                |
                |--- 'linux-arm64' subfolder
                |       |--- native.dll
                |
                |--- 'osx-x64' subfolder
                |       |--- native.dll

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

This looks super promising, wow! Nice work! :heart_eyes:
I have one suggestion just for compatibility; prior to 6.2 (or 6.1? Don't recall exactly) pwsh was able to search the location the library was in for native DLLs (though not subfolders). As part of one of the changes in 6.2, that was removed, and this seems like a sensible place to add it.
Can we have it also check the same folder as the managed library so that anything that was using the old behaviour works again as well?

Can we have it also check the same folder as the managed library so that anything that was using the old behaviour works again as well?

Yes, we can. I think first we need to have a standard (RFC?) how we search, order is important. Also we should consider security compliance.

/cc @PaulHigin

@iSazonov we may want to look into whether there's a way to pull the acceptable RIDs from dotnet / if this is available from a .NET API rather than having a hardcoded set here. 🙂

@vexx32 .Net Core has not API to expose RIDs.
We could support all RIDs from https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
but it will very complicate the resolver.
I hope the proposed solution covers most of use cases. Notice, that key here is that we calculate path based on managed assembly location: if the assembly is right assembly for OS, arch, runtime then we expect that native assembly also is right assembly and is in right place. I hope other scenarios is edge cases that we could delegate third-party  project developers who could use DllImportResolver callbacks directly.

@iSazonov yeah I wondered. The reason I ask is that some RIDs include OS version as well as architecture, so we might be missing (for example) a folder with win7-x64 quite easily. Perhaps we could forwtte moment solve that problem with use of wildcards?

It makes sense to follow the .NET RID hierarchy so that it's consistent and predictable.  It doesn't have to be an exact match, but I can image build scripts that create the native folder under the RID passed to msbuild.  So for macOS, you're just as likely to see osx-x64 folder.

Will replace "osx" with "osx-x64".

The reason I ask is that some RIDs include OS version as well as architecture, so we might be missing (for example) a folder with win7-x64 quite easily. Perhaps we could for the moment solve that problem with use of wildcards?

It is just a case I name as "edge". Very unlikely to be needed. I believe any developer prefer to create portable solutions.
Also Core does not have a reliable way to determine OS/kernel version.
So I suggest only use portable RIDs. At least until we get feedback.

🤔 along with this, would it perhaps be feasible to expose a public API to allow module authors to add specific paths to search when working in those edge cases?

to expose a public API

The API is already in .Net Core. See DllImportResolver callbacks reference above. I guess it is possible to use even script delegate for the callback.

@daxian-dbw Negative test is useless (it failed in any case).  I added positive test but I haven't possibilities to debug and fix it for Linux and MacOs. :-(

Negative test is useless (it failed in any case).

It's supposed to fail and the test is to check for the exception type, expecting BadImageFormatException. Can you elaborate why it was not working?

It's supposed to fail and the test is to check for the exception type, expecting BadImageFormatException. Can you elaborate why it was not working?

What if a bug is to load windows dll on Linux?

What if a bug is to load windows dll on Linux?

You can create the folder structure in a way to make this impossible. For example, say you create the managed dll using Add-Type and put it at temp\test, then on x64 Windows, you only create temp\win-x64 folder and create a dummy native.dll in that folder; on x64 Linux, you only create temp/linux-x64 folder and create a dummy native.dll in it. Similarly, you only create the folder that is supposed to be found by your resolution code on the corresponding platforms, so you will either get BadImageFormatException when the resolution succeeds, or DllNotFoundException when the resolution fails.

@daxian-dbw I added new test as you ask but it fail too.

There are 2 failures in both macOS and Linux, the first one is your positive test, which I don't know why it failed.
The second one is because on Linux and macOS, all failures of loading the native library get wrapped to the DllNotFoundException. The difference is in the message:
Linux

Message        : Unable to load shared library '/home/dongbo/temp/blah.so' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: /home/dongbo/temp/blah.so: file too short
Message        : Unable to load shared library '/home/dongbo/temp/abc.so' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: /home/dongbo/temp/abc.so: cannot open shared object file: No such file or directory

macOS

.... blah.dylib: no suitable image found. Did found: blah.dylib ...
.... abc.dylib: no image found

I prefer to not check in binary files for testing, so I still suggest to use loading failure message to tell if the native library resolution succeeds. But we will have to write code for each platform instead of relying on the BadImageFormatException.
On windows, we can still check for BadImageFormatException. On Linux and macOS, we have to check for the exception message.

There are 2 failures in both macOS and Linux, the first one is your positive test, which I don't know why it failed.

I tried on WSL and I see SkiaSharp has a dependency on fontconfig  package.

@daxian-dbw After some experiments I found a trick to make the test being positive without adding new binaries.

@iSazonov Please don't use 7.0-consider for PRs... I'll try to update the descriptions to say which milestones are for issues and which are for PRs.

Added a reference to new doc issue.


ZNB don't snapshot traces

They are slow and may not even function correctly if the trigger is not set and there is no point of snapshotting array parameters

@WilliamHPNielsen

@jenshnielsen , I feel that this is a problem that is bound to occur more frequently. Rather than overwritting the snapshot method, would it not be better to add this as a property of the parameter that is set through the add_parameter method. Something like include_in_snapshot=True/False ?

Perhaps, but that API does not exist and  this one does because of special handling in https://github.com/QCoDeS/Qcodes/blob/master/qcodes/instrument_drivers/QDev/QDac_channels.py#L107 that cannot be done with a bool as the point is to intersept the snapshot and call an alternative method the bulk updates all the parameters in one instrument call.
I will prefer not touch the parameters until #600 lands. Honestly I think we will get a long way by excluding Array and Multiparameters per default there is almost never any good reason to snapshot those.

I added #759 to remind us to improve this in general


Move ODS module from briefs-frontend and add general DownloadFileView

Summary
The briefs-frontend has a module to help construct ODS files. We now need to make ODSs in the buyer-frontend for service shortlist downloads, so let's move it to utils.
I've also added a generic DownloadFileView that is subclassed in the buyer-frontend (and should be reasonably compatible with the briefs-frontend download view, which I will put up in a separate PR later). This draws out the duplication from the view and lets the subclass only implement the logic and structure required for the csv/ods files, while the parent handles receiving the request and returning the response. Hooks are included for the start and end of the request to allow further logic to be executed at these stages (the shortlist download needs to record the action if the response succeeds).
Bumps version to 28.6.0.
Blocked by

[x] Need to write tests for the DownloadFileView.

Required by
https://github.com/alphagov/digitalmarketplace-buyer-frontend/pull/615
https://github.com/alphagov/digitalmarketplace-briefs-frontend/pull/32
Other associated PRs
https://github.com/alphagov/digitalmarketplace-api/pull/656
~~https://github.com/alphagov/digitalmarketplace-apiclient/pull/98~~
~~https://github.com/alphagov/digitalmarketplace-frameworks/pull/473~~
Ticket
https://trello.com/c/igRhA3Bt/711-shortlist-file-download

I think the abstract class implementation is objectively fine, but it seems an awful lot of hard work to do something relatively straightforward.

Ready for final sign-off @galund


Implement support for linear filtering in the root viewport

This makes it easier to configure a root viewport that uses linear filtering instead of nearest-neighbor filtering. Linear filtering is better suited to realistic-looking games and supersampling.
Currently only implemented in the GLES3 renderer. Help is welcome to get it working in GLES2 :slightly_smiling_face:
Preview
Nearest-neighbor filtering

Linear filtering

For GLES2 you can implement blitframebuffer similarly to how it is done here:
https://github.com/godotengine/godot/blob/ab932bb675f7966b94c46da76ca822ebbf24ddd2/drivers/gles2/rasterizer_scene_gles2.cpp#L2995-L3016
Need to also check for extensions like this in desktop and apple
https://github.com/godotengine/godot/blob/ab932bb675f7966b94c46da76ca822ebbf24ddd2/drivers/gles2/rasterizer_storage_gles2.cpp#L5635

@Calinou Is this still desired? If so, it needs to be rebased on the latest master branch.
Also, isn't scaling already possible? https://github.com/godotengine/godot-demo-projects/tree/master/viewport/3d_scaling

Also, isn't scaling already possible? godotengine/godot-demo-projects:viewport/3d_scaling@master

It is, but that method is probably slower than relying on the root viewport directly.

Hi Calinou. Thanks for this patch.
This expose the filter setting to any ViewportContainer or only root? I couldn't apply this in current 3.2 to check.
Also this can be merged as is (even without OpenGL2 support) by now and cherry picked to 3.2? This is a SUPER important to any real 3D game. Posted about it in twitter some days ago and other users also miss it. https://twitter.com/ZeroPointGame/status/1301995846385512450
As a defense to merge as is there's already many incompatibility between OpenGL2 and 3 features all over the place. Marge it by now will not remove any feature of 2D games and OpenGL2 and mostly of the games that benefit from it are 3D and based on OpenGL 3 anyway. It's such a important feature to keep on hold.
Thanks for your hard work.

@vitorbalbio You can already achieve linear viewport filtering with some setup (see this demo).

This pull request was made before the Vulkan merge and would have to be remade against the 3.2 branch for it to be merged into 3.2.x. Note that in the current master branch (which uses Vulkan), linear filtering is already used when you enable Half Resolution in the editor 3D viewport, for instance.

It's good to know but current projects (3.2) can't rely on this. Also this setting should be exposed to all ViewportContainers not only the root one since it usage is not only important on it. Minimaps and SplitScreen as any other 3D or 2D element placed over the screen would make usage of this as well.

@vitorbalbio You can already achieve linear viewport filtering with some setup (see this demo). It works with both GLES3 and GLES2 renderers.

It's the same workaround i'm currently using with a TextureRect, ViewportTexture and Filtering but it looks like a hackish since the "correct" component to make this would be the ViewportContainer.
The Trickiest part is that if you enable the Filter option in the ViewportTexture it also works in the ViewportContainer! I can't only think that it's changing the flag for the same texture buffer but this simple setting is not exposed anywhere in the viewportContainer itself as it should.
See that the TextureRect is disabled but i can control with it the setting in the ViewportContainer.

In the meantime, I would recommend using an integer divisor for the resolution (e.g. 960×540 for a 1920×1080 window size) and rely on nearest-neighbor filtering, which is technically the sharpest option you can get.

This is not a option in 3D game that allows multiple full-screen resolutions. Also "Sharper" is not "better" in those cases since this produces huge aliasing artifacts as you can see in the images above.
I'm only saying all this to emphasize the importance of this as a exposed simple bool in the ViewportContainer in Godot 3.2 and 4.0. Just because there's a tricky workaround doesn't mean it's should be kept that way if a better, simpler and more elegant solution can be provided.
Best Regards.

Closing in favor of https://github.com/godotengine/godot/pull/35517, which is a simpler approach to solve this issue.

@Calinou #35517 is for 3.x, not master. I suppose #35517 can be forward-ported to master, but I wanted to make you aware of this.

@aaronfranke The master branch uses linear filtering out of the box, but I'm not sure whether this is intentional or a bug.


Broken Example: Thanksgiving

The example for Thanksgiving (https://github.com/rianjs/ical.net/wiki/Working-with-recurring-elements#the-fourth-thursday-of-every-november) produces the wrong results:

Occurrence: 11/23/2000 12:00:00 AM -- Thursday
Occurrence: 11/23/2001 12:00:00 AM -- Friday
Occurrence: 11/23/2002 12:00:00 AM -- Saturday
Occurrence: 11/23/2003 12:00:00 AM -- Sunday
Occurrence: 11/23/2004 12:00:00 AM -- Tuesday
Occurrence: 11/23/2005 12:00:00 AM -- Wednesday
Occurrence: 11/23/2006 12:00:00 AM -- Thursday
Occurrence: 11/23/2007 12:00:00 AM -- Friday
Occurrence: 11/23/2008 12:00:00 AM -- Sunday
Occurrence: 11/23/2009 12:00:00 AM -- Monday
Occurrence: 11/23/2010 12:00:00 AM -- Tuesday
Occurrence: 11/23/2011 12:00:00 AM -- Wednesday
Occurrence: 11/23/2012 12:00:00 AM -- Friday
Occurrence: 11/23/2013 12:00:00 AM -- Saturday
Occurrence: 11/23/2014 12:00:00 AM -- Sunday
Occurrence: 11/23/2015 12:00:00 AM -- Monday
Occurrence: 11/23/2016 12:00:00 AM -- Wednesday

I am trying (and failing) to figure out how to build a recurrence rule for Thanksgiving...  Could you update the example?
Thanks!

Might this be the answer?
var evnt = new Event
{
DtStart = new CalDateTime(DateTime.Parse("2000-11-23T00:00:00")),
DtEnd = new CalDateTime(DateTime.Parse("2000-11-23T23:59:59")),
RecurrenceRules =  new List
{
new RecurrencePattern
{
Frequency = FrequencyType.Yearly,
Interval = 1,
ByMonth = new List { 11 },
ByDay = new List { new Ical.Net.DataTypes.WeekDay { DayOfWeek = DayOfWeek.Thursday, Offset = 4} },
Until = DateTime.MaxValue
}
}
};

Yikes, my example recurrence rule makes no sense at all. Like, it's so bad it's funny.
Thanks for the catch; I'll fix the docs, and close this issue when I do.

Your fix was spot on. I've updated the page.

Updated the unit test to assert the right things.
61e95887b620f46d8a3dc637f2474bc3df571ae5


Trim whitespace between size & unit

Resolves #28

@dank unfortunately we cannot accept this PR without a signed CLA, closing this PR for now


IE11 problems

Hi,
regarding #55, I tested searchguard on the Internet Explorer 11 in Windows 7 and found 2 bugs.

Highlighting Bug
With this pull request #67 this would have been fixed, but on the release there is an additional change in the login.html file.
... || ! ui.credentials.username" ...

Without this condition the highlighting works also on the IE11.
Thus, is this condition needed?

Custom stylings
In my case, I would like to change the color of the login button. I changed the color in the kibana.yml:
...
searchguard.basicauth.login.buttonstyle: "background-color: red;"
...

It works with the newer browser like Chrome or Firefox but not with IE11.
I think the problem is here login.html.
... style="{{ui.buttonstyle}}" ...

The IE11 does not get the custom settings.

Thanks, will look into this.

Hi there,
Just a quick update on this one before I submit a PR.
I've tested in IE11 on Windows 7, and I can reproduce both issues.

Highlighting bug
I added that extra condition to make sure that the form can't be submitted with empty values.
I'll come up with a smarter solution that works in IE11 too.

Custom stylings
You are right, IE11 seems to strip values from the style attribute that it doesn't recognise as valid css. In this case it seems to be Angular's {{}} that's causing the problem.
I'll add support for IE11:
 ... ng-attr-style="{{ui.buttonstyle}}" ...

I'll submit a PR to fix these issues.


Feature/Module display differently with learning status

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Fixed issues (PRs without this will not be accepted)

Fixes #198

Changes

API: add myPathModules API, so that client can get user module status(completed, open, locked)
API: add myPathConcepts API, so that client can get number of learned concepts of each user module to display on the module which is in open status
Client: remove PathModule folder which is merged to ModuleTree/Module folder
Client: modify files in ModuleTree/Module folder to display module with user learning status

PR Checklist

[ ] Does your PR contain relevant tests that pass?
[x] Is your code linted? yarn lint or yarn lint:fix
[x] Does your code build correctly in ALL projects? yarn build

Closing this in favor of #239 as much of this was used in that PR :). Thanks!


Aggressive Drain option from UI does not work

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Do an Aggressive drain from the UI on one of the worker nodes
Request sent contains  : deleteLocalData: "true" only.

Expected Result:
Correct values of "Aggressive" drain option be sent - force: true
Rancher logs
2020/05/15 21:01:23 [INFO] Draining node sowmya-new-worker-longhorn-2 in c-8gbxq with flags --delete-local-data=true --force=false --grace-period=-1 --ignore-daemonsets=true --timeout=120s
Other details that may be helpful:

On 2.3.6, on doing an aggressive drain on a node - Request sent ocntains - {deleteLocalData: true, force: true, ignoreDaemonSets: true, gracePeriod: -1, timeout: 60
Rancher logs: 2020/05/15 20:35:15 [INFO] Draining node sowmya-longhorn-236-1 in c-jx9h4 with flags --delete-local-data=true --force=true --grace-period=-1 --ignore-daemonsets=true --timeout=60s

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.3
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke do
Kubernetes version (use kubectl version):

1.17.5

While verifying this please take a look at the 'Drain nodes' section of the rke driver.

@lvuch @deniseschannon per the conversation here https://github.com/rancher/ui/pull/3997 it looks like we need to make some changes to the UI. Specifically want to change the mode section to expose two separate properties rather than just conflating them into safe and aggressive. The two properties being
deleteLocalData
force
We have the options on the node drain modal and in the rke config.
Node:

Config:
Would something like this be okay?

If that's not okay would you mind putting something together?

@codyrancher This looks fine to me.

Verified on 2.4-head - commit id: c357f562f

Drain a node, the options available to the user is

Select Delete Local Data = True, Force = True, Give some values for Drain timeout and Grace period for pods to terminate themselves.

Click on Drain.

Request sent consists of all the input values - {force: true, deleteLocalData: true, gracePeriod: "30", timeout: "60"}

But the values for Drain pop up window -Delete Local Data , Force, Grace period for pods to terminate themselves and Drain timeout persists when trying to drain other nodes - logging a bug - https://github.com/rancher/rancher/issues/27339
On master-head - commit id: 4ef496126

Drain a node, the options available to the user is

Select Delete Local Data = True, Force = True, Give some values for Drain timeout and Grace period for pods to terminate themselves.

Click on Drain.

Request sent consists of all the input values - {force: true, deleteLocalData: true, gracePeriod: "30", timeout: "60"}

But a panic occurs on the rancher server - https://github.com/rancher/rancher/issues/27168
But the values for Drain pop up window -Grace period for pods to terminate themselves and Drain timeout persists when trying to drain other nodes - tracking the issue in this bug - https://github.com/rancher/rancher/issues/27339


RKE install: nginx-ingress-controller pods crashloop due to missing service account token

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Create a cluster for HA Rancher deployment using RKE (v1.1.7).
---
kubernetes_version: v1.15.12-rancher2-5

authentication:
  strategy: x509
  options: {}

authorization:
  mode: none
  options: {}

network:
  plugin: weave
  options:

nodes:
  - machine_name: ip-172-32-0-61.eu-west-1.compute.internal
    address: 34.242.x.199
    internal_address: <IP_ADDRESS>
    user: ec2-user
    role: [etcd,controlplane,worker]
  - machine_name: ip-172-32-0-9.eu-west-1.compute.internal
    address: 3.249.x.133
    internal_address: <IP_ADDRESS>
    user: ec2-user
    role: [etcd,controlplane,worker]
  - machine_name: ip-172-32-0-7.eu-west-1.compute.internal
    address: 3.249.x.99
    internal_address: <IP_ADDRESS>
    user: ec2-user
    role: [etcd,controlplane,worker]

# Ensure key is available
ssh_key_path: ~/.ssh/key.pem

services:
  etcd:
    extra_args:
      election-timeout: "5000"
      heartbeat-interval: "600"

addon_job_timeout: 120

Wait until nginx-ingress-controller pods are running.
Install Rancher 2.4.8.
helm upgrade --install rancher --namespace cattle-system --set hostname=rancher.ourdomain.com --set privateCA=true --set tls=external rancher/rancher

Restart one of the nginx ingress pods in the ingress-nginx namespace and watch as it errors and enters CrashLoopBackOff.
(∩｀-´)⊃ ❯ KUBECONFIG=kube_config_rancher-ha.yml k get po -n ingress-nginx
NAME                                    READY   STATUS             RESTARTS   AGE
default-http-backend-6ffd4cbc89-hc6wp   1/1     Running            0          11h
nginx-ingress-controller-npgsx          0/1     CrashLoopBackOff   19         74m
nginx-ingress-controller-rzfq7          1/1     Running            0          81m
nginx-ingress-controller-vdqzw          1/1     Running            0          81m

Result:
Nginx controller log shows that it is unable to find a valid service account token at the path '/var/run/secrets/kubernetes.io/serviceaccount/token.
-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:       0.32.0
  Build:         git-29dd9760f
  Repository:    https://github.com/rancher/ingress-nginx.git
  nginx version: nginx/1.17.10

-------------------------------------------------------------------------------

I0925 10:52:48.053653       6 flags.go:204] Watching for Ingress class: nginx
W0925 10:52:48.053935       6 flags.go:249] SSL certificate chain completion is disabled (--enable-ssl-chain-completion=false)
W0925 10:52:48.053988       6 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
W0925 10:52:48.054027       6 client_config.go:548] error creating inClusterConfig, falling back to default config: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
F0925 10:52:48.054125       6 main.go:272] Error while initiating a connection to the Kubernetes API server. This could mean the cluster is misconfigured (e.g. it has invalid API server certificates or Service Accounts configuration). Reason: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
Refer to the troubleshooting guide for more information: https://kubernetes.github.io/ingress-nginx/troubleshooting/

Inspecting the nginx controller pod shows that no account tokens are mounted.
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:            <none>

One of the running pods looks like this and is using the default token.
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  default-token-zgmfm:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-zgmfm
    Optional:    false

When inspecting the 'default' serviceaccount in the ingress nginx namespace I saw that automountServiceAccountToken is set to false.
This means that the default serviceaccount token will not be mounted automatically. Reading the rancher docs I note that it is recommended to set this to false for hardening (https://rancher.com/docs/rancher/v2.x/en/security/hardening-2.3.5/). We did not at any point set this ourselves however.
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server
I tried changing automountServiceAccountToken to true however it was immediately changed back to false after saving.
apiVersion: v1
items:
- apiVersion: v1
  automountServiceAccountToken: false
  kind: ServiceAccount
  metadata:
    creationTimestamp: "2020-09-25T09:22:31Z"
    name: default
    namespace: ingress-nginx
    resourceVersion: "236756125"
    selfLink: /api/v1/namespaces/ingress-nginx/serviceaccounts/default
    uid: d181992e-5f53-47fd-b11a-3f58f87d722e
  secrets:
  - name: default-token-zgmfm
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Other details that may be helpful:
I did some digging and came across this pull request https://github.com/rancher/rancher/pull/27336. That appears to block use of the default token in non system namespaces.
System namespaces are defined in the pull request as:
	SystemNamespaces                  = NewSetting("system-namespaces", "kube-system,kube-public,cattle-system,cattle-alerting,cattle-logging,cattle-pipeline,cattle-prometheus,ingress-nginx,cattle-global-data,cattle-istio,kube-node-lease,cert-manager,cattle-global-nt,security-scan")

I am not completely sure why it is having this effect because ingress-nginx is a system namespace so should be allowed. However to prove my point I scaled down Rancher and then tried to edit the serviceaccount again. This time the setting was saved and the following restart of the nginx controller pod got it back up and running again.
Scaling Rancher back up and pods are back to normal. We only noticed this by chance because one of the pods got restarted and we received an alert from the load balancer. In a worst case, if all nginx pods get restarted for an upgrade for example then the rancher frontend becomes unavailable. A temporary solution to at least disable the nsserviceaccount controller behaviour would be welcomed.
(∩｀-´)⊃ ❯ KUBECONFIG=kube_config_rancher-ha.yml kubectl get po -n ingress-nginx
NAME                                    READY   STATUS    RESTARTS   AGE
default-http-backend-6ffd4cbc89-hc6wp   1/1     Running   0          11h
nginx-ingress-controller-j2b4r          1/1     Running   0          23s
nginx-ingress-controller-rzfq7          1/1     Running   0          111m
nginx-ingress-controller-vdqzw          1/1     Running   0          111m

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.8
Installation option (single install/HA): HA

Does anyone have any comment to make on this at all?

@rust84 Did you ever figure this issue out?

Please park it as /kind: bug
This is very easy to reproduce and imho falls into RKE bug not Rancher.
Ranger is disabling default SA token automounting which is part of security hardening. The Nginx ingres daemon set relies on automounting hence any change to that one post rancher install will result in crash loop due to token not being mounted on pod start.


Crystal 1.10 cannot be installed on Ubuntu/arm64

Bug Report
I tried to install Crystal 1.10 on Ubuntu as described in Official Crystal deb repository:
docker run -i -t ubuntu:22.04 /bin/bash
apt-get update
apt-get install curl gpg
echo "deb http://download.opensuse.org/repositories/devel:/languages:/crystal/xUbuntu_22.04/ /" >/etc/apt/sources.list.d/crystal.list
curl -fsSL "https://download.opensuse.org/repositories/devel:languages:crystal/xUbuntu_22.04/Release.key" >/etc/apt/trusted.gpg.d/crystal.asc
apt-get update
apt-get install crystal

Output:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 crystal : Depends: crystal1.10 but it is not installable
E: Unable to correct problems, you have held broken packages.

Additional observations:

Installing Crystal 1.9 with apt-get install crystal1.9 works.
Homebrew does not work on ARM, so that does not work either

Sorry, there are no official aarch64 packages available at the moment. You may use community-provided packages from https://packagecloud.io/84codes/crystal
Duplicate of #9833

Is there a reason why there are no official ARM images? Can we somehow help with this?


test: option set conditions

Add tests for option set conditions
Add additional tests to all other conditions to make sure they display properly in the visualization (to avoid backend issues like the one found while working on option sets)

File renaming suggestions:
option_set_condition => optionset_conditions
orgunit_condition => orgunit_conditions


apply camelCase to remaining elements

Description
Changes proposed in this pull request:

apply camelCase in the examples documentation
apply camelCase for the remaining elements in en.yaml and the extensibility documentation

Related issue(s)
Resolves #1709

/retest

/retest

/retest

/retest

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-integration-test-k3s-namespace


Error in HealthCheck for services

Hi,
in the file https://github.com/sczyh30/vertx-blueprint-microservice/blob/master/api-gateway/src/main/java/io/vertx/blueprint/microservice/gateway/APIGatewayVerticle.java
method: sendHeartBeatRequest
boolean notHealthy = statusList.anyMatch(status -> !status.getBoolean("status"));

        if (notHealthy) {
          String issues = statusList.filter(status -> !status.getBoolean("status"))
            .map(status -> status.getString("name"))
            .collect(Collectors.joining(", "));

          String err = String.format("Heart beat check fail: %s", issues);
          // publish log
          publishGatewayLog(err);
          return Future.failedFuture(new IllegalStateException(err));
        } else {
          // publish log
          publishGatewayLog("api_gateway_heartbeat_check_success");
          return Future.succeededFuture("OK");
        }

this code block will not work in an error case and don't log any error. After using the stream with notHealthy = statusList.anyMatch you cannot use the same stream again in statusList.filter
it will result in
java.lang.IllegalStateException: stream has already been operated upon or closed
Marcel

Thanks for reporting this!


revert <IP_ADDRESS> for 1.10.1

High Level Description
<IP_ADDRESS> included a single change intended to relax the network name constraint, but instead, relaxed the endpoint name constraint.
It may be fine to relax the endpoint constraint, but it was not intentional, and, if we decide to just go ahead with <IP_ADDRESS>, we should decide that for certain.
Otherwise, may be easiest to just revert the bump to <IP_ADDRESS> and get Marathon 1.5.2 in the next release of DCOS
Related Issues

MARATHON-7848 Re-allow underscores in networkName in Marathon config.json definitions (this was the change we intended to include in DCOS 1.10.1 by bumping to <IP_ADDRESS>, but that effort failed)

@timcharper feel free to close this revert PR and just have a PR including the <IP_ADDRESS> Marathon build.

Closing as we are going to include <IP_ADDRESS> in DCOS 1.10.1


⚠ Bofrost.de has degraded performance

In bdd3d41, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1392 ms

Resolved: Bofrost.de performance has improved in a3a59b6 after 7 minutes.


Don't Merge! PR real time test for source branch full build

OPS Build status updates of commit 04eb363:
:clock10: Full build: average full build time is 6 min(s) 20 sec(s) [calculated from last 28 build(s)]

Note: This is a FULL build due to a configuration change (usually in openpublishing.publish.config.json and/or docfx.json). It is strongly suggested to merge this configuration change after the business hours, as it could impact the overall build performance of other PRs on the 'pr-basebranch' branch. For more detailed info, please click here.

OPS Build status updates of commit 04eb363:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 04eb363:
:clock10: Full build: average full build time is 6 min(s) 16 sec(s) [calculated from last 92 build(s)]

Note: This is a FULL build due to a configuration change (usually in .openpublishing.publish.config.json and/or docfx.json). It is strongly suggested to merge this configuration change after the business hours, as it could impact the overall build performance of other PRs on the 'pr-basebranch' branch. For more detailed info, please click here.

OPS Build status updates of commit 04eb363:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 04eb363:
:clock10: Full build: average full build time is 6 min(s) 16 sec(s) [calculated from last 93 build(s)]

Note: This is a FULL build due to a configuration change (usually in .openpublishing.publish.config.json and/or docfx.json). It is strongly suggested to merge this configuration change after the business hours, as it could impact the overall build performance of other PRs on the 'pr-basebranch' branch. For more detailed info, please click here.

OPS Build status updates of commit 04eb363:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Msvc jets.c

Renaming files to make MSVC happier, and renaming sources.mk at the same time to make it more clear that it is elements specific.

This renaming might require changes in rust-simplicity.

I don't think it will; we vendor only the contets of the C/ directory.

error: builder for '/nix/store/0gp4zpjxcpm4dqqik09idiqllbm03krj-Simplicity-0.0.0.drv' failed with exit code 1;
       last 10 log lines:
       > provides this library (you may need the "-dev" version). If the library is
       > already installed but in a non-standard location then you can use the flags
       > --extra-include-dirs= and --extra-lib-dirs= to specify where it is.If the
       > library file does exist, it may contain errors that are caught by the C
       > compiler at the preprocessing stage. In this case you can re-run configure
       > with the verbosity flag -v3 to see the error messages.
       > If the header file does exist, it may contain errors that are caught by the C
       > compiler at the preprocessing stage. In this case you can re-run configure
       > with the verbosity flag -v3 to see the error messages.
       >
       For full logs, run 'nix log /nix/store/0gp4zpjxcpm4dqqik09idiqllbm03krj-Simplicity-0.0.0.drv'.

Haskell derivation fails to build with this patch.
Also, if you are changing it anyway, I would suggest putting a - in the name.

... also this renaming might require changes in the haskell bindings.

I think it is fixed.

Oh, I see. Yeah, this likely will require changes in rust-simplicity.


Chrome 53 node rect +50% padding

Starting with Chrome 53, a huge padding space shows up for HTML inside SVG.
Load this is an older Chrome or in Firefox:
http://cpettitt.github.io/project/dagre-d3/latest/demo/interactive-demo.html
Then load it in Chrome 53.0 (latest as of writing this).
See the bigger padding space from the HTML edges to the rect edges.
You will see that where it says "A Big HTML Source" the width and height of the rect inside the first g of a node (class="node") are calculated to be about 50% larger relative to the HTML's width and height.
<g class="node" transform="translate(145.23046875,57.75)" style="opacity: 1;">
    <rect rx="5" ry="5" x="-125.23046875" y="-37.75" width="250.4609375" height="75.5"></rect>
<g class="label" transform="translate(0,0)"><g transform="translate(-115.23046875,-27.75)"><foreignObject width="230.4609375" height="55.5">
A Big HTML Source!
</foreignObject></g></g></g>

The bigger the HTML, the bigger the "padding".
Here's a screenshot from a private app.
Firefox (I don't have an older Chrome anymore):

Chrome 53.0 (latest as of writing this):

Found a workraound.
It appears that Chrome amplifies some margin/padding when zooming. When changing the zoom it fails to correct said padding or margin.
Ever since the above mentioned Chrome version, I think the engine starts zoomed already (2x on retina?) and then goes back to 100% (default) somehow.
Workaround the issue:
#svg-canvas{
	/* WebKit foreignObject and rect tag margin/padding bug workaround.*/
	zoom: 0.7; /* default to be reverted back to 1 after rendering */
}

// *After* rendering the SVG:

// Finish WebKit foreignObject and rect tag margin/padding bug workaround.
document.getElementById("svg-canvas").style.zoom = 1;

@oxygen Thanks a lot for sharing this!
Here's the code I'm now using:
let useZoomWorkaroundBeforeRender = window.devicePixelRatio > 1 &&
      navigator.userAgent.search(/WebKit/) > -1

function zoomWorkaroundBeforeDagreRender (svg) {
  if(useZoomWorkaroundBeforeRender) {
    svg.style.zoom = 1 / window.devicePixelRatio
  }
}

function zoomWorkaroundAfterDagreRender (svg) {
  if(useZoomWorkaroundBeforeRender) {
    svg.style.zoom = 1
  }
}

var svg = document.getElementById('my-svg-element')
zoomWorkaroundBeforeDagreRender(svg)
dagreRender(d3.select(svg).select('g'), graph)
zoomWorkaroundAfterDagreRender(svg)

This is still an issue as of Chrome 67, but @MajorBreakfast's fix works quite well.

The workaround doesn't work for me. Before I define the svg.style.zoom within the functions (suggested by @MajorBreakfast) it doesn't exist (printing it out in the console returns undefined). It does not seem to have any effect on the outcome.
Does anyone have a full working example of a solved case? that would be really helpful

@deanp70 I referenced this issue by mistake in a PR, sorry, it's completely unrelated.

@deanp70 what’s wrong with my workaround?

@deanp70 what’s wrong with my workaround?

I tried implementing it as well. the problem is that my svg object has no attirbute style attribute named zoom, so changing it adds the attribute but doesn't affect the rendering of the graph.
If you have any ideas why that might happen that would be really helpful :)

@oxygen, could you explain the following line?
innerWidth / outerWidth < 1.4
Why 1.4?

@deanp70 Read the comment next to it.

@deanp70 Read the comment next to it.

@oxygen I understand the reason for the condition, I'm asking about the magic number. Why not 1.2? or maybe 3?


Adding packages: between, connection-pool, freer-effects, verbosity

Please add me (and possibly @xkollar) to github-users/IxpertaSolution. What about https://github.com/trskop/data-default-extra and https://github.com/trskop/endo? Are these considered not mature enough for LTS?

Added everyone that wanted into github-users for IxpertaSolutions.
Package data-default-extra is probably ready to be on Stackage this includes its dependencies data-default-instances-* but I want to have a closer look on them before publishing.
endo its a different mater. There are out-of-bounds dependencies of unit tests.


Cache boot2tcl.iso on local filesystem (or bundle it with the app)

Right now we will dowload the image from Github every time a machine is created (which currently also happens when you downgrade k8s, see #201).
Since we don't have any mechanism to upgrade to a newer ISO without upgrading RD itself, maybe it would be easiest to bundle the ima inside the app. That would also improve first-start experience.
Alternatively, the "obvious" location to cache the image would be ~/Library/State/rancher-desktop/driver/cache/boot2tcl.iso. This is where the boot2docker.iso would be placed when you don't specify the --iso-url parameter. But I think bundling the ISO is preferable.

Hmm, we should already be caching it here.  It's in the terribly non-intuitive name of image.iso, though.
Bundling it would probably make sense.

Closing this issue because we are already caching the ISO, and for bundling we have #224


Improve links

Issues this PR addresses:

:visited and :hover styles removed from auth widget links
visible outline removed from logo

The issue of auth widget link base color is already part of PR #792 and is therefore not part of this PR.
Bug: T347161

Looks great. Thank you :100:


upgrade compatibility with 64-bit architectures.

Current version yields a lot of warnings on building project with 64bit architectures, and some  methods like "pushViewController" don't work in some environments(iOS7 or less?).
I fixed the bug and modified source code following the warnings.

Thanks! I'll merge this if there are still people depending on this, but it's clearly outdated code and I discourage you from using it. It was written for iOS 4, before we had child view controller containment.


Q# - Preview feature: Compilation to QIR (issue 3)

Project Overview
We are working on adding support for compiling Q# to QIR and executing it. QIR is a convention for how to represent quantum programs in LLVM. We aim to ultimately move the Q# compiler to be fully LLVM-based.
While the support and integration is not yet complete, we have set up an example for how to compile a Q# project to QIR and execute it on our full state simulator for early adventurers who are excited to give it a try!
This GitHub issue is one of two tasks that we have defined for Unitary Hack 2021.
Task
Find a Q# program that doesn't compile correctly into QIR or unexpectedly fails when executing the QIR on the full state simulator due to an issue with the generated QIR that hasn't been filed yet, and file the issue.
Then create a PR to add a link to the created issue to the readme.
Instructions
Clone this repo and check out the unitaryhack branch. Make sure you have Clang 11 and dotnet 3.1 installed. Open the folder examples/QIR/Development in VS Code, and install the QDK extension if you have not already. Navigate to Terminal -> New Terminal and enter the command dotnet build. It may take a while until the command finishes since it will be downloading the LLVM libraries. After that, type dotnet run; you should now see the text "Executed successfully!".
Now you are all set to get started! Open Program.qs and experiment with all sorts of language constructs and patterns in Q# and see if you can get the compiler to fail. If the command dotnet run no longer succeeds, you have achieved your mission to beat the compiler!
Note:
The project has been set up to be compiled using the source code version of the compiler and QIR emission; if you make edits to the QIR generation capability, you will see those reflected in how the Development project is compiled.

This seems like so much fun! Will give this a try for sure!

@Avhijit-codeboy Awesome! Let me know how it goes, and if you have any questions or issues with the setup; happy to help. :)

Thanks @bettinaheim!


Samsun Note4 issue: Scene Incline

With gear vr1, this is a good fit and good vr experience.
But when develop the cardboard vr app, there is a very weired problem, the scene incline and swing very slowly. I do not know why, due to the same app in another phone (oppo find5), it is fine.
Even in aframe.io/webvr, in browser, the vr scene is normal and do not incline.
Could some know this issue too? Waiting your help.

This is an issue with our drift correction algorithm and the Note 4. We're constantly working on improving drift correction. Note that GearVR actually includes its own IMU to avoid phone specific issues like this.


update dependencies for use with newer pipenv

libxml2 wouldn't install for me at the specified version and updating it appeared to make quite a few changes to the Pipfile. I'm assuming these are changes made by using a newer version of pipenv.

IDE specific gitignore rules should go into your private config.
https://stackoverflow.com/a/55070742/469721
https://git-scm.com/docs/gitignore
I will probably move off of pipenv since it seems to be dead/less popular nowadays.

Stopped using pipenv in favor of native virtualenvs. Dumber, but less fuss.


Adding examples for Redis Cache top-level resource.

@amarzavery
Here are examples following proposed example format. Please review to see if there are any issues.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[ ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

@amarzavery Note, I get validation errors from the Linter extension for VS Code for this PR because it doesn't like "x-ms-examples" - with the linter versoin I am using, anyway.

@TimLovellSmith
I had to add a double quote" in the "headers" key of the "202" response for the example of RedisCacheImport.json. There was an extra curly brace } in the end, which had to be removed. After that I was able to run the validation tool and found following issues:
The following operations do not have examples provided for them:

Redis_Update
PatchSchedules_CreateOrUpdate
PatchSchedules_Delete
PatchSchedules_Get

Body Parameter for Redis_Create did not have location, whereas the swagger spec says that location is a required property.

Operation: Redis_Create

	> x-ms-examples

		> Scenario: RedisCacheCreate
			> BODY_PARAMETER_VALIDATION_ERROR: Found errors in validating the body parameter for example "RedisCacheCreate" in operation "Redis_Create".
			> InnerErrors:
			  1. code: OBJECT_MISSING_REQUIRED_PROPERTY
			     message: Missing required property: location
			     path:
			     description: The Resource definition.

Please provide examples for all the responses for a given operation.
/cc @johanste @veronicagg @salameer

@amarzavery I've pushed a new commit that I think addresses all the issues except the long running operation description.

 https://github.com/Azure/azure-sdk-for-python/pull/917

 https://github.com/Azure/azure-sdk-for-node/pull/2003

 https://github.com/Azure/azure-sdk-for-ruby/pull/622


feat: support experimental RN debugger interaction

Summary
This PR introduces support for the TUI 'j' interaction and implementations of this interaction for Webpack & Rspack.
It also refactors code in setupInteractions.ts to properly warn about possible (currently none) unsupported interactions in the underlying bundler wrapper implementation, as well as replaces a series of if-else expressions with a switch and replacing object arrow functions with object literal methods shorthand syntax.
Demo

Test plan

[x] Run without --experimental-debugger & pressing 'j' should result in warning: DevTools require the '--experimental-debugger' flag to be passed to the bundler process
[x] Run with --experimental-debugger & pressing 'j' should result in the DevTools being opened, both for Webpack & Rspack

demo pls!

demo pls!

I've just updated the root comment to include a demo GIF.

Do we have a way to display the shortcuts that you can press?

For sure we can, I will have this implemented as well.

Done, also added screenshots ✅

this is how final output looks like:


chore: fix max-block-number and auth e2e tests

This should fix the failures introduced by #5490. These were a bit of an unforntunate coincidence, https://github.com/AztecProtocol/aztec-packages/pull/5500 changed the underlying kernel data structures, and https://github.com/AztecProtocol/aztec-packages/pull/5432 changed what simulate does: both would've caused issues, but because simulate's return type is any this went unnoticed until execution.
I also added the new job to the earthly setup, still looking into why the old PR was merged despite failing.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
676
676
676

l1_rollup_calldata_gas
6,424
6,412
6,412

l1_rollup_execution_gas
585,757
585,745
585,745

l2_block_processing_time_in_ms
1,258 (-3%)
4,683 (-2%)
9,283 (-1%)

note_successful_decrypting_time_in_ms
231
509 (-2%)
923 (-2%)

note_trial_decrypting_time_in_ms
32.5 (+2%)
16.0 (-53%)
42.3 (-32%)

l2_block_building_time_in_ms
10,225 (-1%)
35,829 (-3%)
70,851 (-3%)

l2_block_rollup_simulation_time_in_ms
10,113 (-1%)
35,444 (-3%)
70,121 (-3%)

l2_block_public_tx_process_time_in_ms
4,786 (-2%)
18,543 (-3%)
37,021 (-4%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,943
27,436 (+5%)

note_history_successful_decrypting_time_in_ms
1,161 (+1%)
2,180 (-2%)

note_history_trial_decrypting_time_in_ms
47.3 (+10%)
77.9 (-9%)

node_database_size_in_bytes
18,612,304
35,016,784

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
144
44,377
26,164

private-kernel-inner
151
71,744
26,164

private-kernel-ordering
105 (-5%)
50,830
39,026

base-parity
3,863 (-1%)
128
311

root-parity
1,079 (+2%)
1,244
311

base-rollup
13,115 (-1%)
110,464
861

root-rollup
49.0 (-1%)
4,359
725

public-kernel-app-logic
78.5 (-1%)
47,695
40,661

public-kernel-tail
110 (-2%)
53,372
7,125

merge-rollup
10.7 (+3%)
2,568
861

public-kernel-teardown
76.8 (+1%)
47,695
40,661

public-kernel-setup
75.5 (+1%)
47,695
40,661

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
9.93 (-1%)
15.9 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.578 (-1%)
0.491 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
45.2 (-2%)
71.6 (-1%)
227 (-2%)
446 (-1%)
844 (-3%)
1,707 (-3%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.464 (-2%)
0.442 (-1%)
0.412 (-2%)
0.417 (-1%)
0.401 (-3%)
0.407 (-2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
53.5 (-2%)
105 (-2%)
326 (-4%)
659
1,272 (-4%)
2,583 (-2%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.472 (-1%)
0.474 (-2%)
0.444 (-4%)
0.454
0.441 (-4%)
0.447 (-2%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
60.5 (-1%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.528 (-1%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
40,372
496,534

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
905
1,161
1,377

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,171 (-1%)
814 (-1%)
4,039

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
414 (-1%)
284 (-1%)
740 (-1%)
369
1,199 (-1%)
432


[WFCORE-5845] Produce new [primary/secondary]-host.xml configuration files and replace the default name for the primary host controller

Jira issue: https://issues.redhat.com/browse/WFCORE-5845
Draft PR to evaluate affected test cases

Core - Full Integration Build 11361 outcome was FAILURE using a merge of e56084a81cb78055209076c760a621f35fcecb58
Summary: Exit code 1 (Step: Build & test full (Maven)) (new) Build time: 00:04:26

Core - Full Integration Build 11500 outcome was FAILURE using a merge of e56084a81cb78055209076c760a621f35fcecb58
Summary: Tests passed: 1559, ignored: 47; exit code 1 (Step: Build & test full (Maven)) Build time: 00:11:50

Integration Jobs:
https://ci.wildfly.org/viewLog.html?buildId=301307
https://ci.wildfly.org/viewLog.html?buildId=301317

Core - Full Integration Build 11372 outcome was FAILURE using a merge of 33074ca07d8205952e4ef06038feb3e26aeb2d0f
Summary: Exit code 1 (Step: Build & test full (Maven)) Build time: 00:04:31

Core - Full Integration Build 11512 outcome was FAILURE using a merge of 33074ca07d8205952e4ef06038feb3e26aeb2d0f
Summary: Tests passed: 1561, ignored: 47; exit code 1 (Step: Build & test full (Maven)) Build time: 00:11:30

Integration Jobs shows there are no test failures.
@jmesnil / @darranl Once approved, this PR will require some coordination to be integrated on wildfly.

Superseded by https://github.com/wildfly/wildfly-core/pull/5105


Simplified Verification for Referenced Parameters / Variables. (Fix for 5308)

Fixing by simplifying: no longer attempting to match a reference before the parameter/variable start

double check that the regex is correct too - pipe char looks out of place

try fixing the original expression - look at regex options that span line breaks
could also remove line breaks from the text we test but this may cause a problem with reporting the line number
fix this PR to work (see comment above)

try in the order specified above...


restructure timetable to allow supporting multiple departures (over a year?)

Updates cyclic dependency handling:

instead of using transfers to split cyclic routes, we re-map stops and connect them via stations. This way we can correctly handle cyclic trips, that don't start over

Codecov Report

Merging #174 into master will decrease coverage by 1.66%.
The diff coverage is 89.01%.

@@            Coverage Diff             @@
##           master     #174      +/-   ##
==========================================
- Coverage   94.87%   93.21%   -1.67%
==========================================
  Files         138      131       -7
  Lines        3392     3358      -34
  Branches      307      302       -5
==========================================
- Hits         3218     3130      -88
- Misses         33       84      +51
- Partials      141      144       +3


fix: openTelemetry doc fails to generate for #1185

It seems that the file rename make the doc generation fails, here is a README only PR to fix it
(I run locally npm run docs-test)

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #1185 🦕

@maxday Yeah, you're right... I wonder why the CI didn't catch that.

@maxday Yeah, you're right... I wonder why the CI didn't catch that.


Include Features Matrix

Lots of users ask in Slack what we support (and what we plan on supporting)
We should throw a simple FEATURES.md in the repo.

I can do this but need help to figure out actually what is supported.

@ashellunts :fire: that would be awesome! I was kind of blocked on finding a good layout/design in the README. If it is too long it will not be as approachable. Maybe we can remove webassembly and make it in entry
These are the sections I see.

Pure Go

No C dependencies

PeerConnection API

Renegotiation
Full ICE Agent
ICE Restart
Trickle ICE
ICE-TCP
STUN
TURN (UDP, TCP, DTLS and TLS)
Plan-B and Unified Plan
mDNS Candidates

DataChannels

Ordered/Unordered
Lossy/Lossless

Media

API with direct RTP/RTCP access
Opus, PCM, H264, VP8 and VP9 packetizers
Readers/Writers to pull from disk
Easy integration with x264, libvpx, GStreamer and ffmpeg for encode and decode.
Simulcast

Platform Support

Desktop (Windows and Mac)
Servers (Linux and FreeBSD)
Mobile (Android and iOS)
Web (Webassembly)

Here is a quick draft for a FEATURES.md. https://gist.github.com/scorpionknifes/5627ff9cc23aca76129191aa03b7f463.
Representing data using a matrix/table seems counter-intuitive unless we want to compare pion to something else (features). e.g

Example
Example

Example
👍
⛔

I was also thinking of using ticks e.g

[x] Example
[ ] Example

Let me know if there are any other ideas for design

@scorpionknifes That's a good point! There are a few other states I am not sure how to represent.

This feature is missing, but we we will do it eventually
This feature is missing, but we will not be implementing
This feature is missing, but you can accomplish it yourself  (and we may do it in the future as well)

Many complex terms can scare people off or raise their expectations. They may say "A lot has been done here, we can easily use this project", but they are not.
I think that people who understand will not switch to another project, because they already have a ready-made solution that works. Not sure, but people come here who don't know much about WebRTC in the beginning. The words ICE, TURN and etc wouldn't give me anything. I wanted to see an example that works and is simple so that a quick start can be done.
I think at the beginning you need to put a quick start, only then the features. An example should implement the most popular usecase, and also offer examples for less popular usecase. These examples should work in the real world so that the user does not think they have been fooled.
Sorry a little off topic.


[0.9.2] collect-info.sh is missing during after failed test on EVE master branch

Eden version: 0.9.2
Archive is missing because for some reason collect-info.sh is not found on EVE. referenced works are build on master, which means they use default EVE which is 10.4.0
Referenced works
1, 2

@uncleDecart the referenced workflows are the same one :)

@uncleDecart the referenced workflows are the same one :)

They points onto different lines in workflow. The first one is about not found error in case of SSH attempts, the second one is about not found error in telnet attempt.

@uncleDecart the referenced workflows are the same one :)

They point onto different lines in workflow. The first one is about not found error in case of SSH attempts, the second one is about not found error in telnet attempt.

Ah, I see.
Interestingly though, collect info worked just fine for all failed runs in this case: https://github.com/lf-edge/eve/actions/runs/6467321774?pr=3484

I can see evebuild/danger:pr-kvm-amd64 here and it looks too broad. Looks like it should point onto image with particular PR number, correct?

I can see evebuild/danger:pr-kvm-amd64 here and it looks too broad. Looks like it should point onto image with particular PR number, correct?

It should I think. Interestingly, this problematic run shows as job "test_suite", while for PR it should be (and in this case is) called "test_suite_pr".

Well, inside the workflow file I can see that we try to get pull_request number when we workflow_dispatch. As I understand it is not possible as workflow_dispatch will point onto the branch head, not PR. But a good question is: where did this workflow come from? I cannot find it in main branch of lf-edge/eve repo.

As @milan-zededa mentioned new workflows are working. In latest workflow file there's no workflow_dispatch with pr-number. It could be that we were testing if workflow works by running it manually or from fork.
But I think that this problem is not there anymore since this worked. I propose we see other workflows and if it's running, we can close this

@milan-zededa have you seen any problems with missing collect-info? If not I think we can close this


Deprecated TabBarIOS error

The following error is thrown with the latest version of react-native
./node_modules/react-native-vector-icons/lib/tab-bar-item-ios.js
Attempted import error: 'TabBarIOS' is not exported from './react-native'.

This issue #1199 might be of some help

@arthurpankiewicz Thanks for your help.
I finally settled for creating a patch file using this approach.
The temporary solution of suppressing the error can be seen on this link.
Thanks.

Any update on that error, Please help me if any temporary workaround.


MaintainProductView: More love for product description

Is your feature request related to a problem? Please describe.
The way the description of the selected products is displayed looks not really nice
Describe the solution you'd like
The way the description is shown should look 'ansprechender'. You could think of having the same size and position of the panel or replacing the panel with a more suitable component. Also using rendering of the text with e.g. bold titles could be used.

 MaintainProductView: More love for product description #631


Improve local wipe compatibility with non-bash shells

This change forgoes shell-based brace expansion for performing command
expansion in code.
Resolves #100

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable