Proposal: Remove engine top-level orchestrator builders that only kick off and collect sub-builds (no generators), and hoist sub-build to "standalone"

Some "top-level" builds only kick off sub-builds and then do nothing but wait for the results.  Mac mac_unopt is an example of this:

Note there are no "Global generators" or tests.
GitHub currently only allows reruns on these top-level builds when there's a failure in the subbuild.  In the case of mac_unopt that means all the sub-builds are re-run, even though most of them succeeded (example).  Rerunning all of them ties up CI resources and makes the rerun longer, if the failing test isn't the long-pole of the top-level build total time.  It also means the top-level build uses a bot while it waits on the tests.
mac_ios_engine is an example of a build that can't be trivially replaced by it subviews (like ci/ios_debug_sim) because it has generators that operate on the archives:
https://github.com/flutter/engine/blob/38e37ce9879b2efe4890a8d09f4207dc5686a1bd/ci/builders/mac_ios_engine.json#L488C6-L488C16
This proposes removing all top-level builds that only kick off subbuilds, and hoisting the sub-builds into the .ci.yaml.

Linux clangd
Linux linux_android_emulator_skia_tests_34
Linux linux_arm_host_engine
Linux linux_fuchsia_tests
Linux linux_host_desktop_engine
etc

cc @zanderso @jtmcdole

A couple of questions for my own edification:

How many builders can we elevate? Are most of the builders able to do this and it's just the mac_ios_engine that's special?
Are the "waiting" machines actually consuming machines that could be used for other builds and tests?

I like the idea on the surface.

This is how the builds with json files under ci/builders/standalone work. One example is windows_unopt:
https://github.com/flutter/engine/blob/main/ci/builders/standalone/windows_unopt.json
https://github.com/flutter/engine/blob/main/.ci.yaml#L555 <- note that the recipe is engine_v2/builder rather than engine_v2/engine_v2.
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows windows_unopt/8783/overview <- example build.
The engine_v2 recipe runs all the sub-builds and then runs the global tests and generators.
The builder recipe just runs the single build definition in the indicated json file.

This is how the builds with json files under ci/builders/standalone work.

@zanderso do you see a downside to moving the build-only (no tests, generators) builds to standalone (plus recipe change)? Was that always the plan with standalone? Is this proposal already half-implemented?

How many builders can we elevate? Are most of the builders able to do this and it's just the mac_ios_engine that's special?

@jtmcdole I started making a list at the bottom of the issue starting with "Linux clangd" but I ran out of steam about halfway through, all the json files in https://github.com/flutter/engine/tree/38e37ce9879b2efe4890a8d09f4207dc5686a1bd/ci/builders should be audited as part of this change.

Are the "waiting" machines actually consuming machines that could be used for other builds and tests?

@jtmcdole yes, the waiting "orchestrator" builds are consuming a machine.  We've tried to make as many of them as possible "cheap" Linux VMs which we have many of, but the mac_unopt example is holding a more precious Mac.

Lets chat about this in a merged repo world

This is how the builds with json files under ci/builders/standalone work.

@zanderso do you see a downside to moving the build-only (no tests, generators) builds to standalone (plus recipe change)? Was that always the plan with standalone? Is this proposal already half-implemented?

Yes, this is already half-implemented. I don't think any recipe change is needed for this, but I might be missing something. The only possible downside I could imagine is if someone wants to expand a file like windows_unopt.json with some additional builds, it will have to jump back out of standalone, and that would be some additional churn. But afaict that's how the engine_v2 recipes are designed to work, so it's not really the end of the world.

@reidbaker if linux_android_emulator_34 and linux_android_emulator were moved to standalone then I think you could deduplicate them into one json file per build (android_emulator_debug_x64 and android_emulator_debug_x86), and set the android_virtual_device and avd_cipd_version dependencies from the .ci.yaml.
    properties:
      config_name: linux_android_emulator
      dependencies: >-
        [
          {"dependency": "android_virtual_device", "version": "android_28_google_apis_x86.textpb"}
          {"dependency": "avd_cipd_version", "version": "build_id:8740267484269553649"}
        ]

The android_emulator_debug_x86 one would only need to swap avd_cipd_version per build and not android_virtual_device since both are targeting SDK 28 Android Unit Tests (API 28) (if I'm reading https://github.com/flutter/engine/pull/54186 right).
You would then only need to create a new builder in the .ci.yaml for the next SDK, and not copy the entire json config.


tests: adding test cases for counter RTC on nucleo_l152 board

This patch enables the RTC as counter feature so that the testcase tests/drivers/counter/counter_basic_api
can run on this nucleo_l152re board from STMicroelectronics
$ west build -p auto -b nucleo_l152re tests/drivers/counter/counter_basic_api/
Signed-off-by: Francois Ramu<EMAIL_ADDRESS>

START - test_all_channels
Testing RTC_0
D: Set Alarm: 11
PASS - test_all_channels
START - test_late_alarm
Skipped for RTC_0
PASS - test_late_alarm
START - test_late_alarm_error
Skipped for RTC_0
PASS - test_late_alarm_error
START - test_short_relative_alarm
PASS - test_short_relative_alarm
START - test_cancelled_alarm_does_not_expire
Skipped for RTC_0
PASS - test_cancelled_alarm_does_not_expire
START - test_set_top_value_without_alarm
Skipped for RTC_0
PASS - test_set_top_value_without_alarm
Test suite test_counter succeeded
PROJECT EXECUTION SUCCESSFUL

@FRASTM please rebase

@FRASTM please rebase

@FRASTM please rebase

@ABOSTM maybe you could rebase this PR so we can get it in?

rebase


Header undefined?

Think I may have spotted a bug...

Try submitting a request with:
header: {
         Authorization: undefined
       }

No. If used correctly (i.e. not deliberately bypassed to do #CrazyThings https://github.com/ideaq/time/issues/109 we can rely on https://github.com/ideaq/hapi-auth-jwt2/blob/7cb13d7708db62d508336df84812d97d31848957/lib/index.js#L28  and https://github.com/ideaq/hapi-auth-jwt2/blob/7cb13d7708db62d508336df84812d97d31848957/lib/index.js#L40 100% to catch this!


Add repository to hacktoberfest

https://hacktoberfest.com/participation/#pr-mr-details
@christopher-caldwell could you do it?

 I have never heard of this.

@christopher-caldwell it is a global event to incentive open source contribuition.
You can see more details here: https://hacktoberfest.com/
The challange is basically to create 4 PR for open source projects, but we have to add the topic to the repo participate.
You just have to add the hacktoberfest tag here:

Ahh ok, cool. I added the tag.


[release/1.2 backport] Correct import path and PusherFunc signature

This backports #3213 to fix an import path (in services/server/server_solaris.go) and PusherFunc signature.
Signed-off-by: Jared Cordasco<EMAIL_ADDRESS>

Please rebase on master to pick up the fix for AppVeyor CI

Codecov Report

Merging #3219 into release/1.2 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.2    #3219   +/-   ##
============================================
  Coverage        43.74%   43.74%
============================================
  Files              101      101
  Lines            10743    10743
============================================
  Hits              4700     4700
  Misses            5311     5311
  Partials           732      732

Flag
Coverage Δ

#linux
47.38% <ø> (ø)
:arrow_up:

#windows
40.85% <ø> (ø)
: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 56a6552...b9da989. Read the comment docs.

@fuweid -- For future reference then, the preference is to cherry-pick the commits from the branch rather than the merge?

Yeah, usually we cherry-pick the actual author commit(s); that way you don't have a cherry-picked commit "authored" (in GitHub terms) by the merging maintainer. No problem.


segment not in receive window in server example

I was playing around with the server example and noticed some strange failures. When using netcat, I was able to successfully receive the "hello" message when connecting to port 6969. When using curl, however, I start seeing "segment not in receive window" repeatedly.
To set up my experiment, I cloned the repo at master (960b0012) and ran the following on my machine (taken from the docs):
sudo ip tuntap add name tap0 mode tap user $USER
sudo ip link set tap0 up
sudo ip addr add <IP_ADDRESS>/24 dev tap0

After that, I start the server with cargo run --example server tap0 and start my client with curl <IP_ADDRESS>:6969.
Curl exists immediately:
$ curl <IP_ADDRESS>:6969
hello

But the server gets stuck:
$ cargo run --example server tap0
...
[    10.102s] (server): tcp:6969 send greeting
[    10.102s] (server): tcp:6969 close
[    10.102s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: state=ESTABLISHED=>FIN-WAIT-1
[    10.102s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: outgoing segment will send data or flags
[    10.102s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: tx buffer: sending 6 octets at offset 0
[    10.102s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: sending FIN|ACK
[    10.102s] -> EthernetII src=02-00-00-00-00-01 dst=xx-xx-xx-xx-xx-xx type=IPv4
                \ IPv4 src=<IP_ADDRESS> dst=<IP_ADDRESS> proto=TCP
                 \ TCP src=6969 dst=50030 fin seq=1227067479 ack=3067899883 win=0 len=6
[    10.143s] <- EthernetII src=xx-xx-xx-xx-xx-xx dst=02-00-00-00-00-01 type=IPv4
                \ IPv4 src=<IP_ADDRESS> dst=<IP_ADDRESS> proto=TCP
                 \ TCP src=50030 dst=6969 seq=3067899883 ack=1227067486 win=29200 len=0
[    10.143s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: received ACK of FIN
[    10.143s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: state=FIN-WAIT-1=>FIN-WAIT-2
[    10.143s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: tx buffer: dequeueing 6 octets (now 0)
[    10.308s] <- EthernetII src=xx-xx-xx-xx-xx-xx dst=02-00-00-00-00-01 type=IPv4
                \ IPv4 src=<IP_ADDRESS> dst=<IP_ADDRESS> proto=TCP
                 \ TCP src=50030 dst=6969 seq=3067899882 ack=1227067486 win=29200 len=0
[    10.308s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: segment not in receive window<PHONE_NUMBER>..3067899882 not intersecting<PHONE_NUMBER>..3067899883), will send challenge ACK
[    10.308s] -> EthernetII src=02-00-00-00-00-01 dst=xx-xx-xx-xx-xx-xx type=IPv4
                \ IPv4 src=<IP_ADDRESS> dst=<IP_ADDRESS> proto=TCP
                 \ TCP src=6969 dst=50030 seq=1227067486 ack=3067899883 win=0 len=0
[    10.716s] <- EthernetII src=xx-xx-xx-xx-xx-xx dst=02-00-00-00-00-01 type=IPv4
                \ IPv4 src=<IP_ADDRESS> dst=<IP_ADDRESS> proto=TCP
                 \ TCP src=50030 dst=6969 seq=3067899882 ack=1227067486 win=29200 len=0
[    10.716s] (socket::tcp): #1:<IP_ADDRESS>:6969:<IP_ADDRESS>:50030: segment not in receive window<PHONE_NUMBER>..3067899882 not intersecting<PHONE_NUMBER>..3067899883), will send challenge ACK
[    10.716s] -> EthernetII src=02-00-00-00-00-01 dst=xx-xx-xx-xx-xx-xx type=IPv4
                \ IPv4 src=<IP_ADDRESS> dst=<IP_ADDRESS> proto=TCP
                 \ TCP src=6969 dst=50030 seq=1227067486 ack=3067899883 win=0 len=0
...

I suspect this is due to the fact that curl immediately fills the receive window, but I don't know enough about TCP to know where the off-by-one error arises.

Thanks for the report.

This is not actually a bug, but a side effect of the fact that server.rs never reads from tcp:6969. As a result, the TCP in your kernel is ever trying (unsuccessfully) to push the rest of the data sent by curl in. Since server.rs also never aborts the connection (it only closes its half-connection) this can go on indefinitely. There is no off-by-one involved.
Wireshark can help you understand this:

I've improved the log message in 3347bbe.

Ah, that makes sense. Thank you!


Integrate stylelint testing

https://www.npmjs.com/package/stylelint
Should make it easier to follow the coding standard for newbies.

Done 🙂


Updates to the "Run" section in the User Manual

This is the "Run James in Production" section (formerly the "build your own production server" section).
I changed to "run" because it is not actually built. It is run with Docker. The "build" section will only be available for developers.
All comments welcome. This is a work in progress and is not yet ready to be merged.

That's pretty nice. Just a side note: JMAP is for now only supported in the advanced and distributed profiles (and the memory one for those who just want to quickly test the server). Is it worth to mention it?

Thanks.
I think it is indeed worth mentioning in the details. This page is intended to just give an overview, so it's probably ok not to mention it here.

Hello,
Thanks a lot for that work.
I really like:

Specifying for whom a profile is intended, with use cases
Presenting all of them by gradual adoption complexity

This is a really nice suggestion that we should adopt.
I would add to it details (data store dependencies, and main architecture knowledge)
Then we tend to not use the word profile but product. Do you think it is an appropriate terminology?
Regarding existing products:

Your Minimal and Basic product should be JPA: we provide a JPA product with local storage (embedded derby driver + DB), feeting both needs of simple single user no-dependancy deployments, and DB backed single server deployments. We should mention that data is store in a database and that a user can configure its jdbc driver. We should mention mailqueue relies on a embedded activeMQ. We should mention Lucene is used for search.

For Advanced (Distributed product) I would add topology details: several james server works together as a cluster, stores metadata in Cassandra, relies on RabbitMQ for messaging, stores Blobs in a configurable location (Cassandra, ObjectStorage or a combinaition of both).

We need to still speak about the Legacy Spring product, not under active development, allowing arbitrary component combinaison configuration.

Would that make sense?
Koodo for the work!
Benoit

Hi @chibenwa. Thank you for the comments.

I would add to it details (data store dependencies, and main architecture knowledge)

Ok, will do. I have not yet arrived at the detailed sections. It may still take me a while to get there.

Then we tend to not use the word profile but product. Do you think it is an appropriate terminology?

Personally, I have a problem with "product". However, it could be my personal bias. I tend to think of a "product" as something a little different than what is intended here. Mainly, "product" seems to me to have a very commercial connotation in English. I think that is not what is intended here. Secondly, I feel that "product" for the average person probably refers to "Apache James" itself. If anything, these would be more like "sub-products" to me.
I understand that this is debatable. If it is very difficult to change the term, we could keep it. However, "profile" just feels so much better to me, and I think would make more sense to others new to James. :-)

Your Minimal and Basic product should be JPA

My understanding was that there is also a file system version. Is that not so? My thought is that by not depending on a RDB, and by only depending on a filesystem, it eliminates some complexity for those (like me, hehe) who would rather simply store as a Maildir directly on the file system than have to manage an RDB. I have been using qmail for almost 20 years now I think, and the filesystem has been just fine for me. I am actually happy that I never had to deal with a RDB. It has made my life much simpler, given my limited needs.

For Advanced (Distributed product) I would add topology details: several james server works together as a cluster, stores metadata in Cassandra, relies on RabbitMQ for messaging, stores Blobs in a configurable location (Cassandra, ObjectStorage or a combinaition of both).

Yes, absolutely. My thought was to do this in the detailed section. The reasoning is: those who "understand" will still be able to see those details, but those who are coming in for the first time don't need to be overwhelmed with information they will probably never need. The approach is: everything the "experts" need will be there, but new users should feel more welcome (by not being overwhelmed and by having clearer instructions).

We need to still speak about the Legacy Spring product, not under active development, allowing arbitrary component combinaison configuration.

Yes, definitely. Again, the thought is to keep this only in the "developer" section.
The "user" section is for those who just want to use James without having to worry too much about the details. The "developer" section will be more for those who want to get inside James and make their own custom solution.
A simplistic way to make the distinction is: can I just run it with Docker? If so, then I am a "user". Do I need to compile? If so, then I am a "developer".
Anyway, I think it is better to separate the two.

Personally, I have a problem with "product". However, it could be my personal bias. I tend to think of a "product" as something a little different than what is intended here. Mainly, "product" seems to me to have a very commercial connotation in English. I think that is not what is intended here. Secondly, I feel that "product" for the average person probably refers to "Apache James" itself. If anything, these would be more like "sub-products" to me.

We definitly have to start a discussion about vocabulary we rely on, for sure.
Your point stands.
I think a disctussion on the mailing list should be started around this topic, which is fundamental for James as a project.

My understanding was that there is also a file system version. Is that not so?

Maildir storage can be leveraged on top of (Legacy) Spring profile. It did not get it's own standalone "profile". The underlying implementation is maintained in best effort mode, integration test coverage is limited, and it suffers from well known bugs. See MAILBOX-389, MAILBOX-393 for instance.
I personally don't want to promote it as the simplest product as long as these limitation remains.

I am actually happy that I never had to deal with a RDB.

An embedded database is just another local file format, just exploring it via the filesystem is not doable. From an operating perspective, I'm unsure if it changes much. Maybe I am missing something?

Yes, absolutely. My thought was to do this in the detailed section. The reasoning is: those who "understand" will still be able to see those details, but those who are coming in for the first time don't need to be overwhelmed with information they will probably never need. The approach is: everything the "experts" need will be there, but new users should feel more welcome (by not being overwhelmed and by having clearer instructions).

:+1: I have a tendency to go too quickly into technical details.

Yes, definitely. Again, the thought is to keep this only in the "developer" section.

Huge :+1: here. I did not understood it. It reduces the reach of the legacy product without removing it.

A simplistic way to make the distinction is: can I just run it with Docker? If so, then I am a "user". Do I need to compile? If so, then I am a "developer".

To dig into details, we do have a ready to use dockerized Spring image. But arbitrary component combinaison is that should be exposed only to "developers".

Ok, I see your point about Maildir. That's too bad, but I guess that's life.
Please note that this PR is not yet ready to merge.
Outstanding items:

Resolve discussion about "Product" vs. "Profile" on the mailing list
Include a small demo using the Admin API via curl (it is not yet working for me)
Include details about how to connect to the sample app using Thunderbird (also no success yet for me)

Ok, I see your point about Maildir. That's too bad, but I guess that's life.
Please note that this PR is not yet ready to merge.

you can flag the PR as a Draft in this case

Oh, thanks! Did not know that. From what I just read, I need to do that when I create the PR. Do you know if it's possible to change this existing one to a draft? Other options are to leave this one and create as a draft next time, or to delete this one and make a new one.
Any preference?

It's a really new feature you can find it on the right of the screenshot above : "Still in progress? convert to draft"

Cool, thanks!

This PR was folded into #199, so closing.


requirements for MATLAB/Octave

Hello,
I am trying to run Experimental.m under Octave 9.1 (Windows).
Apparently, some additional packages are needed. Could you specify, please?

Could you provide more details about the issue with running the code? If the problem occurs at the point of running LMI_AXYB.m, you need to check if your Python environment (venv) is properly set up. Please refer to the README document for detailed instructions.

I got it to run under Octave after reading https://github.com/petercorke/robotics-toolbox-matlab/wiki/Octave-compatibility
and adding these lines to Experimental.m:
function v = verLessThan(s1,s2)
    v = true;
end

pkg load io
addpath rtb/ common/ smtb/

I also noticed some naming errors in li_AXYB.m


Fix publish date

Woops, I used the old date in this post.  I'm gonna merge this as soon as travis passes with it.

bors not activated here?

bors r+

bors r+

@torkleyy I just added you.

Nope, that'll break the links we just sent out everywhere.

We could use a redirect, but I'm not sure how to do that in markdown.


Counting max number of character in a string

Using Dictionary Data structure

Could you change the path to /codes?


Library Scan Wrong barcode sometimes

Description of the problem:
Hi
I am using below version
compile 'com.journeyapps:zxing-android-legacy:2.3.0@aar'
compile 'com.journeyapps:zxing-android-embedded:3.5.0@aar'
compile 'com.google.zxing:core:3.3.0'

I have used DecoratedBarcodeView in my actiivty.
when i scan sometimes it scan and give me wrong barcode result and if i rescan it then it gives me correct result.
e.g.
my barcode is below
00373500598048386007
for the first time if i scan it gives this value
00373500598/4)3860&7
if i rescan it then it gives me correct value.
00373500598048386007
May i know why is this kind of issue occures. It is random behavior.  If i continuously scan  3-4 barcode then in 5th or 6th barcode i face this issue.
Please help me urgently,.

me too

Please follow the issue template. Specifically:

If you have an issue scanning specific barcodes, please test with the Barcode Scanner application,
available on the Play Store: https://play.google.com/store/apps/details?id=com.google.zxing.client.android&hl=en
If you are also not able to scan the barcode there, the issue may be with the underlying zxing library,
in which case you should report the issue here: https://github.com/zxing/zxing/issues

This is generally an issue with some 1D barcode types such as EAN and UPC, which is difficult to scan with a phone camera, and doesn't have good error detection. If you get the same issue with the Barcode Scanner application, you're welcome to take the issue further there, but it's not likely that we'll get better results without significantly improving the algorithm, which is out of scope for this project.

Hi i tried that app and it works fine. But the issue is with this library. Also i am using DecoratedBarcodeView  and CompoundBarcodeView which takes too much time to scan. and it can not detect  barcode type COde-128. while if you trey to scan with below code . It does
IntentIntegrator integrator = new IntentIntegrator(ScanOffActivity.this);
integrator.setTimeout(20000);
integrator.setOrientationLocked(false);
integrator.initiateScan();
for DecoratedBarcodeView barcodeView = (DecoratedBarcodeView) findViewById(R.id.zxing_barcode_scanner);
barcodeView.decodeContinuous(callback);
do we need to add some extra
can we add
capture = new CaptureManager(ScanOnActivity.this, barcodeView);
capture.initializeFromIntent(returnnf(), savedInstanceState);
capture.decode();
but it finishes activity and doesnot give result to same activity
How can i achieve that??
Thanks in advance

For a custom Activity, it is up to the application to ensure the results are correctly returned.

Hi @rkistner,
I am facing same issue so please send me custom Activity code.
Thanks in Advance

For a custom Activity, it is up to the application to ensure the results are correctly returned.

Hi @rkistner,
I am facing same issue so please send me custom Activity code.
Thanks in Advance


fixed NODE_ENV assignment for build and lib npm tasks

babel uses NODE_ENV environment variable to decide which presets to load from env section in .babelrc. but when you use && in NODE_ENV=production && babel, you actually define local variable in first part of the expression, and then run babel in the second one without expected environment variable. the correct syntax is NODE_ENV=production babel.
also, neither server.js nor exec.js doesn't use NODE_ENV at all, so i've removed NODE_ENV initialization there entirely.
P.S.: maybe we should set up travis-ci? :)

actually, we can replace lib/lib:win with node scripts/exec.js lib, since there's already platform handling code in there.
or use something like cross-env.

@mynameiswhm Thanks for contributing!
Also thanks for pointing me to cross-env, i've been searching something like it, but didn't found anything.
CI is good (for building lib and docs automatically) but i don't have any time for that and worked only with Jenkins.


Hotfix/harvest moon

Logic for Harvest Moon tracking got borked.
This is what I get for coding at 3 AM.

I think the logic is right, but I think this code should be refactored in a functional style to be less error-prone and more readable.
The added comments don't seem totally necessary, like:
// True if there are ADJUSTED_CAST_TIME milliseconds or more remaining in the inputWindow
return inputWindow.end - inputWindow.start >= ADJUSTED_CAST_TIME

Preferring to have working code over nice code. Part of the TODO for RPR involves a code cleanup but I'd like to do that after we have the bulk of the functionality. RPR has had a lot of contributions from many different devs and the code reflects that, but trying to fix that in every PR just makes merges take longer and usually gets clobbered in subsequent PRs anyway. Keen to see how you think this should look in a more functional style tho.


create a static page for maintenance mode

Suggested by @craigkerstiens on Twitter.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing in light of our decision to shut down Gratipay.
Thank you all for a great run, and I'm sorry it didn't work out! 😞  💃


Add tvOS support

Description
Limit categoryOptions only to platform iOS
Passthrough the recvOnlyMode flag to webrtc config

Pending: to point the podspec to a specific version with tvOS support

Pending: to point the podspec to a specific version with tvOS support

The spec is now update to fix the dependency version.


Missing data from 1.7 EXPORT to 2.1.2 IMPORT dropping UUID property from some classes

Related to original issue of just recent closed issue.  Where our UUID property which is inherited from our Base object of SkywardObject is not being correctly imported.  I have experienced this issue against the latest clone of the orientdb gihub respository.
Please advise,
Thanks,
Jeff

Hi Jeff,
just to understand, which branch did you clone? Was it 'develop', '2.0.x' or 'master'?
Thanks
Luigi

It was 'master'.  Please advise if I should pull a specific branch.
Thanks,
Jeff

Please, try '2.1.x' (not '2.0.x' as I mentioned before), it's the candidate to be next stable.
Thanks
Luigi

Will do, as soon as I am out of meetings this morning.
Thanks,
Jeff

I have been successful in performing 1.7 export and a 2.1.3 Import, using the latest 2.1.x Branch in github which built orientdb-community-2.1.3-SNAPSHOT.
This fixed the UUID being missed in previous IMPORTS.
However, now when running integration tests, I see the following exception:
com.orientechnologies.orient.core.exception.OValidationException: The field 'SkywardObject.__uuid' does not match the regular expression '^[0-9A-Za-z]{8}-[0-9A-Za-z]{4}-[0-9A-Za-z]{4}-[0-9A-Za-z]{4}-[0-9A-Za-z]{12}$'. Field value is: uuid, record: CommercialOperatorOrganization#13:0{airframes:[2],title:Jeff A.. Schenk,objState:ACTIVE,isARNManager:true,isOpsManager:true,setUpFinished:true,isPrivate:true,createdBy:#19:0,personnel:[1],about:null,organizationPhoneNumber:+1-123-456-7890,organizationEmail:jeff.schenk@skyward.io,organizationOwner:null,updatedBy:#19:0,updatedByDate:Tue Aug 11 17:14:09 PDT 2015,address:#64:0,startDate:Mon Jun 01 00:00:00 PDT 2015,createdByDate:Wed Jul 01 04:42:26 PDT 2015,isPersonalOrg:true,parts:[1],__uuid:uuid} v3
at com.orientechnologies.orient.core.record.impl.ODocument.validateField(ODocument.java:258)
at com.orientechnologies.orient.core.record.impl.ODocument.validate(ODocument.java:2002)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:2419)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:2309)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:120)
at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.updateRecord(OBinaryNetworkProtocolAbstract.java:390)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.updateRecord(ONetworkProtocolBinary.java:1536)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:365)
at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:223)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)
This is from our SpringBoot SaaS which is an OrientBD client.  Using the build 2.1.3 JARs as well during build and Integration Tests Run.
POM Dependencies used:
<orientdb.version>2.1.3-DEV</orientdb.version>

orientdb
orientdb-core
${orientdb.version}
jar

orientdb
orientdb-client
${orientdb.version}
jar

orientdb
orientdb-enterprise
${orientdb.version}
jar

net.java.dev.jna
jna
4.2.0
runtime

com.googlecode.concurrentlinkedhashmap
concurrentlinkedhashmap-lru
1.4.2
runtime

The orientdb.version resolves to 2.1.3-DEV, whose artifacts were pushed to our local Nexus Maven Repo to be available for build.
It appears still something is looking for __UUID?
Please advise.
Thanks,
Jeff

This provides some info from ide.  Where person class has both a property uuid and __uuid.  This must have occurred during import.  Are there restrictions on the field name uuid?

Since we have duplicate uuid's in the form of uuid and __uuid both appear to contain same data, and each property is mandatory and not nullable, this in turn caused the exception posted above in previous post.  So still issue with import, import our uuid and creating another property named __uuid containing same data.
Please advise as this is blocking our conversion path.
Many Thanks,
Jeff Schenk

I could perhaps drop the extra __uuid property during our migrations and schema checking prior to our app bootstrap, I might try that to get further along.

Hi Jeff,
I'm looking at this right now.
I still don't understand where this __uuid comes from, but if it's not in your domain you can just drop it.
I'll give you a feedback soon
Thanks
Luigi

Hi Jeff,
still hard to reproduce, but I sent you a private email about this
Thanks
Luigi

Due to a bad legacy migration plan that was left in the code base caused the issue of missing uuid and __uuid properties.


Damage done by friend / party shows up as Unkown

When looking at damage done of a boss done with a friend, I get an "unknown" category, which I assume is the friend I was with (maybe also thrall...?) :

Weirdly enough, I do not have this issue for damage taken :

Would it be possible to have the damage done separated by friend source (like damage taken)? Or atleast a better description than "unkown" (do these include thralls?).
I do not know if the issue arrives from Combat Logger or Runelogs, but I assume it is Combat logger. Feel free to correct me.
Thanks !

Hi @KBoumghar,
Damage done by other players can only be detected if the other player(s) are in a Party with you and they also have to have the Combat Logger plugin. This is because of a limitation in RuneLite where you can not see the source of damage (unless it's your own because those are different colored hitsplats). If you use the "Party" plugin and join in a RuneLite party together the plugin will automatically send messages to each other to tell you the source of the damage.
Your thrall damage should count towards yourself as they are the same color hitsplat are yours.
Joining a Party should solve your issue, but there are a few other cases where the damage can be "Unknown" and I don't currently have a good way to detect it. It can happen when an NPC damages another NPC (like the exploding monkeys in ToA or when Verzik damages the pillars). But those should only be on specific fights that have mechanics like that.


Fix handling if libcorner in yosys and openroad to allow for multiple libcorners.

Is there anything to the readthedocs fail?

@troibe the invalid keypaths are on purpose to ensure we can mark something as required for SC to check


Fix addition gids

For ibm-messaging/mq-container#207.
Fixes https://github.com/containerd/cri/issues/910.
Depend on https://github.com/containerd/containerd/pull/2641.
/cc @estesp

We should cherrypick this into supported branches.

what's up with the temp mount /etc/passwd errors on the Travis CI test phase? Not sure what would have changed though to cause that

@estesp It is because of this https://github.com/containerd/containerd/pull/2641#discussion_r217477155.

Updated to latest containerd, and get rid of the temporary local containerd change.


Thread safe API

Current SDK Version
com.ionoscloud:ionos-cloud-sdk:5.0.1

Use-cases
As a developer, I want to use the sdk-java in a multi threaded application (like Servers) so that, while my application works on its tasks using the machine's full compute power, I can use sdk-java easily and without any concurrency traps.
Attempted Solutions
I can reach the goal by

not sharing the com.ionoscloud.ApiClient instance amongst different threads (because it apparently is not thread safe),
avoiding all the default constructors like

com.ionoscloud.ApiClient#ApiClient(), because that one always creates a new OKHttpClient which is discouraged by the JavaDoc (as it wastes resources),
com.ionoscloud.api.DataCenterApi#DataCenterApi(), because that one always uses the same ApiClient instance (from com.ionoscloud.Configuration#getDefaultApiClient), which however is not thread safe,

creating a fresh ApiClient instance for every thread, and linking it to the same OkHttpClient instance using the com.ionoscloud.ApiClient#ApiClient(okhttp3.OkHttpClient) constructor,

which, however, has the drawback that there usually seems to be some amount of management in com.ionoscloud.ApiClient#initHttpClient(java.util.List<okhttp3.Interceptor>) invoked from the zero-arg constructor, which is not done using that one-argument constructor -- that leaves a bad taste and the question, whether things could brake, also in future versions of the library.

Proposal
From my POV, the best approach would be to use thread safe data structures in the ApiClient -- especially looking at the Map and InputStream types, but basically anything that can be changed at runtime (e.g. using a setter) can lead to unexpected effects when used in a multi-threaded situation.
Another possibility -- but only for a new major release -- could also be to use a two-step instantiation approach, where the user first configures the ApiClient using a Builder, and then receives an immutable instance.
References
None.

This issue report is now almost 3 years old - is there any news on this?


[bug]: New architecture support

Description
On the first video I turned on new arch and have some strange behavior:

Slide animation begins from the bottom left edge, should be just from the bottom
Wallet logos doesn't show.

FYU: I tried to change rn image to expo-image and logos show as expected.
https://github.com/WalletConnect/web3modal-react-native/assets/61261093/11cf5322-940b-46fb-98c9-b10f330dc50c
https://github.com/WalletConnect/web3modal-react-native/assets/61261093/95c9d8c4-36b7-4dd5-af0a-6c056fbd9205
Web3Modal SDK version
@web3modal/wagmi-react-native 1.2.0
Output of npx react-native info
System:
  OS: macOS 14.3.1
  CPU: (8) arm64 Apple M1 Pro
  Memory: 184.61 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.10.0
    path: ~/.asdf/installs/nodejs/20.10.0/bin/node
  Yarn:
    version: 1.22.21
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.5
    path: ~/.asdf/plugins/nodejs/shims/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 21.0.2
    path: /usr/bin/javac
  Ruby:
    version: 3.0.3
    path: /Users/patrikduksin/.asdf/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.4
    wanted: 0.73.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: true
  newArchEnabled: true

Expo Version (if applies)
Expo 50.0.6
Steps to reproduce
npm i
npx expo run:ios

Snack, code example, screenshot, or link to a repository
https://github.com/patrikduksin/rn-wallet-connect-bug.git

Do you get any errors on the console?

hey @glitch-txs nothing

Hey @patrikduksin 👋 thanks for reporting!
You should be able to connect to wallets without issues, but sadly it seems that RN new architecture has some issues regarding images -> https://github.com/facebook/react-native/issues/33131
And about the modal animation, its also a dependency issue: https://github.com/react-native-modal/react-native-modal/issues/757
In this case, we'll wait to see if they solve the issue, and if they don't, we'll evaluate migrating to another modal lib

@ignaciosantise @glitch-txs Hello, as I see you are not planing to support new arch. It's important for us to use it, so can I use web3modal lib with my own UI modal? Maybe you have a documentation about it

@patrikduksin we added a temporary workaround for the image loading issue in v1.2.1 version until react-native solves the Image component problem
As i said, except from this UI issues, the SDK supports the new architecture and you should be able to connect with wallets.


GC: Restore:  event.item attachment support

Description
Item.Attachments of OdataType Event require special transformations prior to being uploaded.
Does this PR need a docs update or release note?

[x] :white_check_mark: Yes, it's included

Type of change

[x] :sunflower: Feature

Issue(s)

*closes #2353
Test Plan

[x] :zap: Unit test

Latest change aa5a2a0 ensures nested event template correct and that code will escape non-supported item.Attachments
=== RUN   TestExchangeRestoreSuite
=== RUN   TestExchangeRestoreSuite/TestRestoreExchangeObject
=== RUN   TestExchangeRestoreSuite/TestRestoreExchangeObject/Test_Mail:_Item_Attachment_NestedEvent
Error returned: exiting ToItemAttachment: #microsoft.graph.message not supported
--- PASS: TestExchangeRestoreSuite (1.75s)
    --- PASS: TestExchangeRestoreSuite/TestRestoreExchangeObject (1.75s)
        --- PASS: TestExchangeRestoreSuite/TestRestoreExchangeObject/Test_Mail:_Item_Attachment_NestedEvent (1.74s)
PASS


Camper News won't accept URLs with long trailing queries

For example, http://blog.scottlogic.com/2015/07/02/surprising-things-about-js.html?utm_source=javascriptweekly&utm_medium=email

I don't think this has to do with the length of the trailing queries.
I tried encoding the ampersand with %26 and it worked on Camper News, so I believe it has something to do with special characters.


Avoid regeneration if we can be sure nothing has changed

First off, thanks for this maven plugin! It has helped when the original plugin couldn't.
Context
As was already requested in #41 we want to avoid generating code on every compile, since our protobuf file change rarely, while the rest does.
Implementation
The code was already using the hasDelta calls of the BuildContext class, but these defaulted to true. No idea why. I've now added the most simple check I could think of, if all the files in the output folder are newer than any of the files in the input folder, we don't have to regenerate.
I think that the maven way would be to use the StaleSourceScanner  but as far as I can see that requires similiar file paths for source and target and only a switch in extension, this will be hard to get right with the code generator of protocol buffers & grpc.
I've tested it on a local project, and it works as expected, between protobuf changes: regeneration, between other changes: no regeneration's.
Discussion
The only thing I am not sure of is what if the compile fails halfway through. If we leave the successful files, that could have an impact on the heuristic? Since running the compile a second time, will skip the code generation (if you haven't actually fixed the source specs). Or could we clear out all generated files after an error? Here my maven knowledge fails.

I propose the following solution to the discussion:

a successful generation without any errors writes a success.txt file in the output directory
the heuristic in this PR only fires if the success.txt file is in the output directory

Ack, thanks, will check

thanks for merging, what's your plan for the failing codegen scenario?

Just saved your changes on a new branch for now, will need a bit of time to take a closer look

sure, take your time, just ping me if you want someone to discuss options with.

Hi @DavyLandman, this is now on master, with successFile marker and "optimizeCodegen" option (we could make default true if we feel confident). Could you give it a try?

Looks good, works on my multi-module maven project.
Promoting the optimizeCodegen for a while and later flipping the default looks like a sane plan. Thanks for taking time to add this feature.

Thanks! I'm pondering whether to make it true right away..

Maybe you should, it might mean a major version bump? (If you are following semver style)
Benefit of maven central and the configuration is that if users encounter problems, they could either use the older version, or use the flag to disable it completely.

Yes worst case it can be disabled. Re major version, I let protobuf/protoc dictate that. I'm only left with the 4th digit :)

Released in version <IP_ADDRESS>. Thanks for the contribution!


Kirki Framework

This theme is itself a framework and it is implementing Kirki Framework as well. Rather than using another framework, it will be better to implement Customizer API
Ref: https://developer.wordpress.org/themes/advanced-topics/customizer-api/

I'm not seeing anything from Kirki that you need in particular for this theme.  With a quick look at the customizer, is the theme even using Kirki for anything?

Kirki is being used primarily for extensions shells that extend the framework. Have dropped Kirki from being required for the core framework and will instead require it as needed in additional add-ons.


[pwrmgr/clkmgr/rstmgr] Hook up integ alert

Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

Thanks @matutem.
Yes, a large part of it is generated.
I have included the generated code in these commits to make the changes atomic.


Encrypt pod logs in bootstrap runner and decrypt in Tentacle

Background
To avoid leaking sensitive values in pod logs, we are now encrypting the logs in the script pods and decrypting them in Tentacle
Results
The process is now:

Tentacle, when creating a script pod, generates and stores a 32 byte key and writes it to a file keyfile in the script workspace. This key is a PBKDF2-derived hash of the tentacle machine encryption key salted with the script ticket id. This is done so that if the NFS is lost and tentacle restarted by the watchdog (ala automatic upgrade), that the key can be regenerated again so running pod logs can be decrypted.
The bootstrap runner reads this key when starting and initializes a AES GCM cipher, this key is then used to encrypt all log messages being written to the pod logs
Tentacle, when it receives pod logs, loads the encryption key for a script ticket (either from memory or from the key file) and uses it decrypt the log message
...
Profit!

The nonce, generated on a per-log message bases in the bootstrap runner, is prepended to the encrypted message and split in the tentacle decryption.
I had to do a bit of refactoring to the KubernetesMachineKeyEncryptor so that we could now retrieve the machine key in multiple places.
After
Example pod log output
|53|stdout|e386c2044b8ca0ef28813aad82361dcc66cda9e83b4212d0a1a77d019296784845ef65b994a3e25258f2cf8dad11fd31464911d3c83529463f4c1331c13b5001d48d2b372d162e14e4d5439db3294a7b3c9c7013152b016dcf
|54|stdout|2fba0762f2d704ca1f3f217c7e0a97732c1fc3c366c650d7a60a3938412ceaeac723c917aa0ad3c4144431eb0f9edbe0d6ef388e63ee1d32478a4167e0d2a2
|55|stdout|21261f4d524fdace95c5a292c3c3df0bb6a4bc4bfc40a9259beaa9fc9717802904c0dc2796b8aa80ade202d72575733e6fdc264e36ebfc2ac6876a72c26e3aea5b4db3ea6cba128fb8bdbfc607551522286e
|56|stdout|59df43e039d22cb062e130eefd3b4b776dacb2debd34ace232ec1f9598884ea7418a19436438fb76ab513e27577dc30f3c8155094ea23db3c95d124137d4
|57|stdout|924e2b9fc6d69857fd77334a6719fc5106660136599ee0dda862f8b22a6b0e15b29eba243d9c59775d8d32d6ab1d471a7b58efcba684df2c023051606e784ca4992e
|58|stdout|3e201912998213b4c9142eeaee8785a02e7ff693de543b4b60243e83ce8bfe11efce3d34daa57294afe9923b724a9bcfb3e686f49d16d3150e82ae93c2b9
|59|stdout|4863c2997bc6a9a521476a67927201c30f7806fd7118514e279e030c
|60|stdout|1003496491189169f10f2eb6caed5279e2a8b48431cab6960ad60264
|61|stdout|deaa311679e09df5608d1f59883324e7bdea3de7ff9badf864d1c3df97e5d96078d0dc9a0aba059549a121ed729223ada10f0e6cda
|62|stdout|a5f569c165ca2f039fbb2020349c5d1ca64a82963a28100cc44c360d3921f00c8894c3b3627348ff55350eb2109969040738cdcbf1
|63|stdout|9fbf30b1685d7155548c4a15e6d835f7f74aa06c2ce67d7c517116a7495b4082a649cde69e8684d921cedd82b88c2a56a463eea57280eb563d9e201f88441d
|64|stdout|ed030f4fc8bb247f6a2867d306b0ec36c7ebfa948e34932a35cd6a86ff3951e249316af7eee85194a3a99b84cc3cd671c0824a316358ccd8a4c01afe545e
|65|stdout|c01f90998e541bb8a61404757a4996c85384bdb565c0ccc5b87e0c891bde15611b2adac8d32c631e4aa0129f97f70e
|66|stdout|35aa82f01d1f47ca5b10249de719d030d1b280e266b41f61f06745c2a52ea0f9cb8e34ab62ee0e1af79bdaad4ffa02a8216c
|67|stdout|fee5431412851e6db0daf13e647df76ca09bb3c189cf6f3e486082dd24119eeb4ad286e8a6442609b981915b6daf1a4212d3eff20bc57837fbe67921f49d9a9700ba87a169d0d5cce189fd37cff019bc659b68
|68|stdout|20c1b3a8c485a538d65da53c22bfa5f0324a587747682a12a81706fb1eeebcf4db4ccc82bfbaa4b1a90ced011ee8c5c73c5be9ae7b41ddc42c00557ad128722e3f5289937dcab29df3310ba32103ad5d0bc6
|69|stdout|bbb1d4a1918c611966fb118bd45a0b13ca4bb3faca8dc30b81e71d84ad1fa4025eda866463820089184a52bdc44f75a62e85
|70|stdout|8958e9468d7e4446358f83d921b64ed0b503c9a81c5b89dc46a3245576bcaa567cc1002da10abd75b467a1f6a76bdb713591ae83
|71|stdout|3b0ed4aac814f99a0959ffa3235f01b8c42a374434b28855ea24fe45e6f8146c214322a85d2a09841eb6b8270e9b889d59403d00e0
|72|stdout|9b28051a7652da92571d305d3e25899307d27ed8ef89a717767d9cf2bd
|73|stdout|5848c2b0ae9ff0ea7e4bb18bc581fcdb720992ba3dcf1dd03226016418
|74|stdout|1e3810f7ee59e2021e562401ac4de0ebfbfcd7dc0b4fe638c980d19cce
|75|stdout|be187a41930ab76b9f8a7703c9186ba81fcdea3dca97106f3593bd8b5a

The output in Server

How to review this PR

Quality :heavy_check_mark:

Pre-requisites

[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[x] I have considered informing or consulting the right people, according to the ownership map.
[x] I have considered appropriate testing for my change.

For safety we should check this version of tentacle works with a full build of octopus server.

@LukeButters Yep, this was done in https://github.com/OctopusDeploy/OctopusDeploy/pull/29373 and was fully green!

ADR for change here: https://github.com/OctopusDeploy/adr/pull/68

Shortcut story: [sc-98480]


Use custom zend queue fork for 7.0 compatibility

I did some work on the zend queue repo to make sure tests build and submitted to packagist
This resolves #4206

Any thoughts on why the tests are failing on PHP < 7 now ? https://travis-ci.org/concrete5/concrete5/jobs/153069081

Shouldn't the composer.lock be changed as well?

Shouldn't the composer.lock be changed as well?

It is

Hm, good point :) I overlooked because the diff was suppressed.

I think I found the problem: https://github.com/KorvinSzanto/concrete5/pull/4

Hmm, maybe. Lets see if that pull fixes it.

Fixed :wink:

Awesome, thanks @mlocati


About Channel-Wise Attention(CWA) in the code.

Great work!But I have little question about CWA.In the origianl paper, I see M_i = diag(Mask_i), where diag is putting a vector on the princial diagonal of a diagonal matrix.But in the code below:
foo = [1] * 2 + [0] *  1
bar = []
for i in range(200):
    random.shuffle(foo)
    bar += foo
bar = [bar for i in range(nb_batch)]

I think bar is not a diagonal matrix.  Please point out my problem if I misunderstood the operation here.Thanks a lot.

sorry for this confusion, the M_i just like [[0],[1],[0],[0],[1],[0]].T.
CWA could be visualized as a random channel-dropping operation in each channel group.

dot([0,1,0].t(), [1,2,3].t()) = [0,2,0].t()
matrix(diag([0,1,0].t()), [1,2,3].t()) = [0,2,0].t()
So, the code and the paper is consistent.
CWA could be visualized as a random channel-dropping operation in each channel group.

Got it.Thanks for the response.

foo = [1] * 2 + [0] *  1
bar = []
for i in range(200):
    random.shuffle(foo)
    bar += foo
bar = [bar for i in range(nb_batch)]

I had a small question about the code, here foo = [1] * 2 + [0] *  1 is only good for 3 channels correct? If we want to increase the number of channels (say 5), then foo = [1] * 3 + [0] * 2 is necessary, correct?

Yes.  Please see Section III.A  The Discriminality Component  for details.


Proxy Authentication, fixes issue 105

Following up with the proxy auth issue and related patch:
http://code.google.com/p/phantomjs/issues/detail?id=105
This patch adds an extra parameter to the command line args to allow for proxy authentication --proxy-auth, accepting a string in the format username:password. Anything not in this format is ignored.

See http://code.google.com/p/phantomjs/issues/detail?id=105.


chore: bdd-nh-1587308671 to 0.0.1

chore: Promote bdd-nh-1587308671 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Very slow compilation of large method in AOT compiler due to non-linear algorithm

The corelib_2/regexp/pcre_test has a very large main() function which causes the test to flakily timeout.
It seems gen_snapshot spends minutes compiling just the main() function.  The reason seems to be that for O(instructions-of-block) we perform the instr->GetBlock() - which is again a O(instructions-of-block) algorithm, making this quadratic.
We could e.g. consider breaking blocks with very large number of instructions into multiple blocks to avoid this.
/cc @mraleph @alexmarkov

Duplicate to https://github.com/dart-lang/sdk/issues/21708.


Support hover style for Link without href attribute

Before v3 the Link component didn't require the href attribute to be show the hover style and underline. I found this convenient as I often use it as an inline button of sorts.
This is related to the any-link pseudo selector.
Workaround:
<Link href="" onClick={(e) => [e.preventDefault(), ...]}>
    ...
</Link>

Released 3.0.2 with a fix that makes it so that links rendered as buttons retain hover styles.
To clarify, what you seem to be doing is not accessible. You should use the asChild prop to render link with button tags:
<Link asChild>
  <button onClick={...}>Button that looks like link</button>
</Link>


Ascribed type of a value clarification

Addresses https://github.com/MicrosoftDocs/powerquery-docs/issues/39.

Learn Build status updates of commit 20c697d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 3241a48:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 183d57d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 0c23086:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 5c44c54:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 0396ee3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 676ffa0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 3da97de:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 556bd4c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

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

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 82acff6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

Learn Build status updates of commit 4e571b9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-types.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

It looks like my suggested change for records wasn't included.

Uh on! Not sure how they were missed. How do things look now?

@DougKlopfenstein, I see this PR was merged a few weeks back.
However, I don't see it reflected on https://learn.microsoft.com/en-us/powerquery-m/m-spec-types#ascribed-type-of-a-value

Did the PR's changes get lost somehow? :-)


Port cra.sh development task to javascript

I've ported tasks/cra.sh to javascript to make it easier for contributors on Windows based systems to run an end to end create-react-app CLI workflow as discussed in #2280.
If someone more familiar with proper handling of child processes and signal events could take a close look that would be much appreciated!
I've tested on Windows 10 using both npm and yarn in Command Prompt, PowerShell and Git Bash.

@ianschmitz Thank you for this PR. A much-needed improvement for the Windows users.
I tested your PR on my local machine and it didn't work with Yarn 0.22.0, it gave the error below:

error An unexpected error occurred: "Invalid URI "c:/wf/create-react-app/packages/react-scripts/react-scripts-1.0.5.tgz"".

However, after I upgraded Yarn to the current stable version 0.24.5 it then worked fine.

Yes I found that same behavior as well @cr101.
I was running yarn 0.23.4. I mentioned it in the code review. Latest stable fixed it for me

@gaearon I've been using this change on my local Windows 10 dev machine for a couple of months now and it works great. Can this be merged please?

The part I was hoping to get a review on was if the SIGINT event was sufficient to handle all cases such as cancelling part way through. I have only tested this on Windows.

Seems like this has been used for a while now with good success. Can we get this in soonish? :)

@Timer this is the PR you mentioned. Can confirm this works :+1:
@ianschmitz it might be better to print just the message and not the stack trace.
 and the new file needs to be relicensed to MIT.

I just rebased and updated the license comment. Thoughts on the error output? @Timer?

I think the error is fine; this is for local devs so the more information the better. An end user will never see it.


Configure SCSS linter

Investigate code style issues in https://github.com/metanorma/metanorma-ogc/pull/70, and prepare some good style book for SASS.

I can adjust the style guide for SCSS, but I have questions about which rules do you prefer. I wanted to tell them from https://github.com/metanorma/metanorma-ogc/blob/7100b9c0c2ce203d798de36ef106787558e928de/lib/isodoc/ogc/html/ogc.scss, but there are few style inconsistencies there, possibly legacy ones, hence it was impossible.
Alternatively, SCSS style checker can be easily disabled project-wide or organization-wide by adding following to respective .hound.yml:
scss:
  enabled: false

But given the fact that there are formatting inconsistencies in e.g. https://github.com/metanorma/metanorma-ogc/blob/7100b9c0c2ce203d798de36ef106787558e928de/lib/isodoc/ogc/html/ogc.scss, perhaps it should stay on.

Anyway, here are things I need to know if we're going to use this linter.
It is all entirely up to you and your aesthetic and practical preferences. For any of these we may adopt particular style or disable respective checks.
1. Class naming
I guess CamelCase, right? Are there any exceptions, for example there: https://github.com/metanorma/metanorma-ogc/blob/7100b9c0c2ce203d798de36ef106787558e928de/lib/isodoc/ogc/html/ogc.scss#L646-L649? And what about naming convention for mixins?
2. Indentation
Tabs or spaces? How many of them?
3. Where to put opening and closing curly brackets?
.coverpage_docstage
    {text-align:center;
    font-size:30.0pt;
    color:#2e81c2;}

vs
.coverpage_docstage {
    text-align:center;
    font-size:30.0pt;
    color:#2e81c2;
}

vs any combination of these?
4. Should colon be followed with a white space?
margin-right: 36.0pt;

vs
margin-right:36.0pt;

5. Metrics
Hound warns if there are more than 10 properties set within a rule. Does this limit make any sense for you? It is violated many times, e.g. here: https://github.com/metanorma/metanorma-ogc/blob/7100b9c0c2ce203d798de36ef106787558e928de/lib/isodoc/ogc/html/ogc.scss#L211-L234. If the answer is "yes, with exception of this project", then perhaps we can think of some overrides.
6. Avoiding fractional part in measurements
Hound says:
UnnecessaryMantissa: `10.0pt` should be written without the mantissa as `10pt`

Do you agree?
QualifyingElement: Avoid qualifying class selectors with an element.
7. Class selectors with element name
Hound says:
QualifyingElement: Avoid qualifying class selectors with an element.

This is about selectors like this one: p.example in following piece of code:
p.example, li.example, td.example {
  margin-right: 0pt;
  margin-left: 0pt;
}

div.example {
  margin-right: 36.0pt;
  margin-left: 36.0pt;
  margin-top: 0cm;
  margin-bottom: 0cm;
}

p.example, li.example, div.example, td.example {
  mso-pagination:none;
  font-size:10.0pt;
  font-family:$bodyfont;}

Given the fact that you use it quite extensively, should I turned if off?
Or maybe you want to eventually refactor it into following?
.example {
  &p, &li, &td {
    margin-right: 0pt;
    margin-left: 0pt;
  }

  &div {
    margin-right: 36.0pt;
    margin-left: 36.0pt;
    margin-top: 0cm;
    margin-bottom: 0cm;
  }

  &p, &li, &div, &td {
    mso-pagination:none;
    font-size:10.0pt;
    font-family:$bodyfont;}
  }
}

8. Inline color literals
At line https://github.com/metanorma/metanorma-ogc/blob/7100b9c0c2ce203d798de36ef106787558e928de/lib/isodoc/ogc/html/ogc.scss#L666 Hound says:
ColorVariable: Color literals like `#2e81c2` should only be used in variable declarations; they should be referred to via variable everywhere else.

Do you agree?
9. Leading zeroes
Hound says:
LeadingZero: `.0001` should be written with a leading zero as `0.0001`

Do you agree?
10. Spacing between rules
Hound says:
EmptyLineBetweenBlocks: Rule declaration should be followed by an empty line

Do you agree?
11. URL format
Hound says:
UrlFormat: URL `file:///C:/Doc/FILENAME_files/header.html` should not contain protocol or domain

Do you agree?

cc @opoudjis @strogonoff @ronaldtse

@opoudjis Any opinion on that, or should I use my own favourite settings? ;) The above post seems long, nevertheless there's not much thinking in it. Especially that "disable this check" is also a good answer sometimes.

Ping @abunashir @strogonoff thoughts?


Remove stale

These were pointed out by Build #931.
From the commit messages:

Website stopped responding.
Social media account seems to be inactive:
https://twitter.com/cheddarapp
Failed to respond to request
Social media account inactive for > 5y
https://twitter.com/icebergsapp

MyFritz is also timing out, but it has an active social media account and was added a month ago, so I'm considering it might be a temporary issue.

Ok

As of October 7, Cheddar is back online, but not Iceber.gs

Let's drop the commit for cheddar then.

Dropped the cheddar commit and merged with removal of Iceber.gs


Add liveness and readiness probes to GRC

Add liveness and readiness probe to proactively restart the containers when
hub kubeconfig is changed. This is necessary for backup and restore scenario.
For issue: open-cluster-management/backlog#17651
Signed-off-by: Yu Cao<EMAIL_ADDRESS>

/assign @mprahl
/assign @leena-jawale

@leena-jawale can you review and approve?

/cherry-pick release-2.4

/lgtm
/approve


How can I create a world with Beta Terrain combined with 1.19 Caves on a 1.19.3 Minecraft Server?

Hello. I came across an Issue which I can't seem to figure out alone. I'd like to play on a 1.19.3 Server with Beta Terrain combined with these immersive 1.19. caves. However I just don't know what I should go about it! Do I have to generate the world first in Single Player and then transfer over the save file to the server? I just don't understand how this works, also the menu slightly confuses me, all I see in the customize menu is a black background and some numbers...
I would very much appreciate some help here, thanks in advance!

Do you know how to do it in single player? I am struggling to find a solution to this.


Str helper conjunction method

Sometimes you'll want to construct text from a template string where the subject is variable.
e.g.
Book a hotel vs Book an x-ray where hotel/x-ray is only known at runtime.
This helper can determine if a or an is required.
$subject = 'hotel';
Str::conjunction('Book %s ' . $subject); // Book a hotel

If you only require the conjunction back you can pass in the word that follows it without using a sprintf template string
Str::conjunction('skeleton'); // a

About acronyms and initializations
Terms such as HTTP, MP4 or  CEO are tricky because if they are initializations you would pronounce each letter (CEO = C . E . O). This can affect what the conjunction would be. Because of this, this helper would not support text intended for acronyms or initializations. I belive these are less likely to need to be dynamically generated at runtime though.

I don't think one can really detect whether to use "a" or "an" using only the first letter of a word.

a university
an underground club

@dennisprudlo You're right 🥲

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Bug in connection close implementation when sending events

Issue
$client->close() is not properly supported by some relays. It will trigger connection exception. There is also possibility of bug in phrity/websocket library v1.6.0.
Example:
$private_key = '67dea2ed018072d675f5415ecfaed7d2597555e202d85b3d65ea4e58d2d92ffa'; // private key example which used in test unit

$note = new swentel\nostr\Event\Event();
$note->setContent('Hello world');
$note->setKind(9999);

$signer = new swentel\nostr\Sign\Sign();
$signer->signEvent($note, $private_key);

$eventMessage = new swentel\nostr\Message\EventMessage($note);

// $relayUrl = 'wss://relay.damus.io'; // Can handle $client->close() properly
// $relayUrl = 'wss://nos.lol'; // Can handle $client->close() properly
$relayUrl = 'wss://relay.nostr.band'; // Will give connection error when calling $client->close(). It will be safe if $client->close() replaced by $client->disconnect()
$relayUrl = 'wss://nostr-pub.wellorder.net'; // Same issue with relay.nostr.band

$relay = new swentel\nostr\Relay\Relay($relayUrl, $eventMessage);
$result = $relay->send();

print_r($result);

The following example will show that some relays (wss://relay.nostr.band and wss://nostr-pub.wellorder.net) will trigger the following error message:
swentel\nostr\Relay\CommandResult Object
(
    [success:protected] =>
    [message:protected] => Connection closed: Empty read; connection dead?
    [eventId:protected] =>
)

When actually the event is received successfully by the relays as shown by nosdump request to the relay:
# Using nosdump command in cli
nosdump --authors 7e7e9c42a91bfef19fa929e5fda1b72e0ebc1a4c1141673e2794234d86addf4e --kinds 9999 wss://nostr-pub.wellorder.net

The event were successfully received by relays but the error message was returned only when $client->close() was called in Relay.php lines 57.
Solution
Instead of using $client->close() in Relay.php lines 57 we can safely replace it with $client->disconnect().
We can follow example in php.net documentation to handle closing of stream_socket_client connection. As shown in the example of php.net documentation for stream_socket_client, they use fclose() to close the socket properly. fclose() is actually used in $client->disconnect() function in connection lib (Lines 328) of phrity/websocket.
Most relays can handle properly client disconnect $client->disconnect() instead of implicit close request $client->close() implementation.
Success Result Example after replacing $client->close() into $client->disconnect():
swentel\nostr\Relay\CommandResult Object
(
    [success:protected] => 1
    [message:protected] =>
    [eventId:protected] => 07abceba124e8b410a0f7c1cfe1a9983c2bee19105d3fb82342ac382b764709e
)

The PR will be sent shortly to solve the issue.

Related issue #28 .

Thanks for digging this out @atrifat !
Just tested the same code on my side I can confirm the same behaviour. Will merge your PR.


Style shim only converts a single ::shadow or /deep/ in a selector

See http://plnkr.co/edit/DCLtFWbGN0RrIDVSikrB?p=preview for an example. Only the first ::shadow or /deep/ is getting removed from the style rules. On Chrome (with native support for /deep/, that means the background color gets stuck after the first nesting level. On Firefox, both the foreground and background colors get stuck there.
    li { color: red; }
    li ol::shadow li { color: blue; }
    li ol::shadow li ol::shadow li { color: green; }
    li { background-color: lightblue; }
    li /deep/ li { background-color: lightgreen; }
    li /deep/ li /deep/ li { background-color: pink; }

in the custom element stylesheet becomes the following in the document stylesheet:
li.dom-recurse {  color: red;}
li.dom-recurse ol.dom-recurse  li {  color: blue;}
li.dom-recurse ol.dom-recurse  li ol::shadow li {  color: green;}
li.dom-recurse {  background-color: lightblue;}
li.dom-recurse   li {  background-color: lightgreen;}
li.dom-recurse   li /deep/ li {  background-color: pink;}

Please note that ::shadow and /deep/ are being removed from the cross scope styling spec. They may become deprecated in Chrome soon.


Spring Boot the property spring.jpa.show-sql doesn't work with Datastore

I want to view the queries that I generated.
Which parameter like spring.jpa.show-sql  can I use to see all my queries  in the logs ?
Please let me know.
Thanks

Since Spring Data Datastore is not a JPA implementation, spring.jpa.show-sql won't work. I'm not sure if there a way to log GQL queries in the Datastore client library that we build on. Maybe, ask here.


libcudnn.so.7: file not recognized: File format not recognized

HI! Hope you aren't too busy to help out.
I'm on Ubuntu 16.04 (Cause of ROS Kinetic and hence need CMake version of tensorflow) and require the full C++ API, so I'm building the shared library.
I have
CUDA 10.0 though I don't intend on using it
libcudnn version 7
Bazel 0.19.2
and the master branch of your repo.
Originally, it couldnt find libcudnn version 7. I have tried with symlinks, tried copying files over, still didnt work.
The error message i got is:
ERROR: tensorflow_cc/tensorflow_cc/build/tensorflow/tensorflow/BUILD:489:1: Linking of rule '//tensorflow:libtensorflow_cc.so' failed (Exit 1)
<EMAIL_ADDRESS>file not recognized: File format not recognized
collect2: error: ld returned 1 exit status

I have copied /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.1 into  /usr/local/cuda-10.0/libcudnn.so.7.

Hi, sorry for the delay. One of the files is probably built using an incompatible compiler. Is this still bothering you? I had a lot of problems with Ubuntu 16.04, that is why I decided to support 18.04+.

Closing for inactivity. Feel free to reopen if the issue persists.


Investigate integration HTCondor + WMAgent in a container setting

Impact of the new feature
This is an R&D item to decide what the best way approach would be to integrate HTCondor with WMAgent in a containerized environment
Is your feature request related to a problem? Please describe.
This is related to: #11314
Describe the solution you'd like
R&D in terms HTCondor + WMAgent communication.
If HTCondor is also deployed with WMAgent:

Do we use an isolated network, or host based network? Are there any difference in limitations in terms of number of TCP connections? This would impact the number of shadows per schedd
If HTCondor is provided somewhere else (e.g.: the regular schedds): How do we handle de authentication from the containers to the remote schedds? Do we keep 1 condor schedd per WMAgent? Do we need to handle a shared FS binded between the schedd and the container to handle the Sandbox working directories? I.e.: the condor working area that the schedd usually keeps somewhere in the schedd. We use a remote schedd, the files are written in some directory of the container, but the schedd wouldn’t have access to it unless it’s a shared FS (to verify).

THis has been answered [here], hence closing this ticket.
(https://docs.google.com/document/d/1KOLS2tJ9i8kl3PpBh5jy8YVtcp7KtIwOfhx3sYJri4o/edit#heading=h.a392kbqsgk49)

THis has been answered [here], hence closing this ticket.
(https://docs.google.com/document/d/1KOLS2tJ9i8kl3PpBh5jy8YVtcp7KtIwOfhx3sYJri4o/edit#heading=h.a392kbqsgk49)

Hi @khurtado this document is locked. Could you or @amaltaro share it at least as readable for everybody with the link?
Thanks!


RFC: Added emptyDir tmpfs support

I don't thinks this is "right".
It is simple though: we initialize ram disks at container launch time.
But it doesn't really match what k8s does: where each volume is mounted by the individual containers.
I think to do it "right", I'll need to make a ram disk for each volume and inject the mount (via titus-storage).

It looks like we already have decent prior art (that I wrote and forgot!) with shared metatron tmpdirs for pods.
That is more akin to what I'm trying to accomplish here with emptydir, so I'll try that approach.
I also need to verify that if you make a ramdisk on the host and then inject it... that the ram usage comes from container?


[Bug] MQTTX CLI won't recognize topic -t or --topic when used with -lo for loading connection options

What did I do

What happened
Get an error.
Expected
mqttx should allow me to pick a topic? lol
Environment
as my other bugs, SL7, node 22, win11 on arm64.
More detail
More detail include log information or screenshot

Fixed on npm package next version:

@oising Thank you for your feedback! This is a confirmed bug, and it will be fixed in the next release.


[fa] cheatsheet-machine-learning-tips-and-tricks

Translating to Farsi

Thanks a lot @reza1615 for your great work!
Now, let's start the review process. I know that @erfannoury and @AlisterTA have been working hard on this cheatsheet as well (here is their version). When you have the time, please feel free share your thoughts on this PR!

@shervinea I think the translation quality of @alisterta's version is better than the current PR. I will revise that and send another PR soon.

Closing the PR due to #60.


Ignore docs/pages/includes files when linting

Closes #191
The markdown-lint script includes all files in docs/pages/includes. The script also processes partial inclusion expressions within docs pages, then lints those pages. This means that partials are linted at least twice: once on their own and for every time they are included in a docs page.
The first lint pass for each partial usually works as expected. However, there is an issue if a partial includes a default parameter value (#171), like this:
{{ var="default value" }}

Here is a variable with a {{ var }}.

When a page includes this partial, the docs engine removes the first line before inserting the resolved text. As a result, partials with default parameters render as expected and pass the linter within their including pages.
But when we run the markdown-lint script, and the linter checks the partial on its own, the first line remains in the partial. This causes the linter to return an error.
This change edits the markdown-lint script to ignore files within docs/pages/includes. This will allow us to use partials with default parameter values without them breaking CI.

@ptgott I'll send you the relevant bits from the logs.

It looks like it's all good to go now @ptgott


Add or change OIDC setting after a cluster is created

What would you like to be added:
Add or change OIDC setting after a cluster is created
Why is this needed:
"My organization may change our OIDC provider in near future. I don't want having to recreate my EKS-A cluster just to change the OIDC setting".

I found two work-arounds for this.
First option - Correct the EKS deployment to include OIDC

Login to the cluster and manually edit the Cluster spec to include the identityProviderRefs sectionapiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: Cluster
metadata:
  creationTimestamp: null
  name: <cluster_name>
spec:
  ...
  identityProviderRefs:
  - kind: OIDCConfig
    name: "<name>"
...
status: {}

Manually create a new resource in your Kubernetes cluster for OIDC---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: OIDCConfig
metadata:
  annotations:
    anywhere.eks.amazonaws.com/control-plane: "true"
    anywhere.eks.amazonaws.com/etcd: "true"
  creationTimestamp: null
  name: "<name>"
spec:
...

Make a change to your Control Plane machine config - such that the eksctl upgrade command will recreate those nodes---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: VSphereMachineConfig
metadata:
  annotations:
    anywhere.eks.amazonaws.com/control-plane: "true"
  creationTimestamp: null
  name: "<name>"
spec:
  memory: 7196 #8192 (original value)

Execute the upgrade command

Second option - manually correct the kube-apiserver pod one each control plane node
(this isn't preferable, as these settings will be lost in future upgrades"

SSH to each control plane node
Edit this file: /etc/kubernetes/manifests/kube-apiserver.yaml
Restart kubelet to apply the changes: 'systemctl restart kubelet'

I think the eksctl anywhere cli tooling / bootstrap process should be able to apply those changes. But it says that identityProviderRefs is an immutable field for the Cluster resource - which it isn't and doesn't seem to need to be.


Load Balancer Routing Policy Import Inaccuracies

Hello,
I've encountered some issues with the CD3 export of load balancer routing policies from our OCI Tenancy. The imported Terraform configuration doesn't accurately reflect the actual infrastructure for certain aspects of the routing rules. Here are the main problems I've identified:

Truncation of Complex Conditions:
For rules with numerous path conditions, the CD3 import truncates the list.

Missing backend_set_names:
Some rules have their backend_set_names incorrectly omitted in the CD3 import. For instance:
Imported:
{
  condition = "any(http.request.url.path sw (i '/SomePath'))"
  name = "route_example"
  backend_set_name = ""
}

Actual:
{
  condition = "any(http.request.url.path sw (i '/SomePath'))"
  name = "route_example"
  backend_set_name = "ExampleBackendSet"
}

Incomplete Conditions:
In some cases, only the beginning of a condition is captured. For example:
Imported:
condition = "any("

Actual:
condition = "any(http.request.url.path sw (i '/Path1'), http.request.url.path sw (i '/Path2'), ...)"

These inaccuracies require manual intervention to correct the Terraform configuration after using CD3 for export.
Environment details:

OCI provider version: 6.3.0
Terraform version: v1.7.1

Steps to reproduce:

Use CD3 to export resources from OCI Tenancy
Check the exported Terraform configuration for load balancer routing policies
Compare with the actual infrastructure using terraform plan

Expected behavior:
CD3 should accurately capture all aspects of the load balancer routing policies, including full conditions and correct backend_set_names.
Actual behavior:
The exported configuration has truncated conditions, missing backend_set_names, and in some cases, incomplete conditions.

Will look into this and revert asap.

Is it possible to share the Excel file may be just the 'LB-RoutingPolicy' to see how the exported data looks like?
@Anay-Pampatwar

@xs2suruchi Thanks for your response. I have sent the Excel file containing the 'LB-RoutingPolicy' sheet to you via a direct Slack message.


Why do my users not have a status.online flag?

I just created a fresh project using mrt
and the status.online flag is no where to be found on any of the logged in users.
is this package outdated or is there something I'm not understanding?

I had the same problem, turns out that you have to remove autopublish to make this package work.


Running Pangolin Mobile (A Flutter UI) on the pinephone is extremely slow

I built it on a Pi4, and ran it on the pinephone, note that the Pinephone's GPU is from 2008, it supports openGL 2.0 and I'm unsure if it supports that version of OpenGL. I don't know what could be causing the slow down when the OS I'm using (Arch) is accelerated.
(https://github.com/dahliaOS/pangolin_mobile) Pangolin mobile, used in the test.

Hi @EnderNightLord-ChromeBook
Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample? A video demonstrating the issue would help as well as this is a UI issue.
Thank you

What device, pinephone or build device.

Hi @EnderNightLord-ChromeBook
Sorry, my last comment may sound confusing.
I need you to provide the steps to reproduce the issue you are reporting, along with the trace to verify the lowliness.
Thank you

Pangolin Mobile is our project and this issue concerns your project. We don't know if flutter supports OpenGL 2.0. That's the question. I don't think I need to attach logs for that.

https://youtu.be/D-_Pzb9wlXQ
Here's a video

Pangolin Mobile is our project and this issue concerns your project. We don't know if flutter supports OpenGL 2.0. That's the question.

We don't use GitHub Issues for asking/answering questions. Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Support for relative SDK path.

Could you please add support for relative SDK pathing?
There's a huge thread about it on vscode.
https://github.com/microsoft/vscode/issues/2809
But it looks like it is up to each developer to implement.

Relative to what exactly? The workspace? Something else?

Workspace, user folder, home, and appdata, would be nice for a start.
And additionally, if not already, accepting Unix paths and converting to windows if necessary within the extension.

Just interpreting an environment variable for the relative path would be very appreciated.

Interpreting environment variables sounds like something that VSCode should be doing, and not each extension coming up with its own separate (probably somewhat buggy) implementation. I'll leave this for Microsoft to handle. microsoft/vscode#2809 is still open, so I assume that it's under consideration and they have not rejected this as a possible future feature.


Please help: dfx deploy failed with errors

Last login: Thu Jun  6 19:45:24 on ttys001

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
...:azle_hell_world ???$ pwd
../azle_hell_world
...:azle_hell_world ???$
...:azle_hell_world ???$
...:azle_hell_world ???$ rm -rf node_modules
npm install
npx azle clean
AZLE_VERBOSE=true dfx deploy
...:azle_hell_world ???$ npm install
npx azle clean
AZLE_VERBOSE=true dfx deploy
npm WARN deprecated<EMAIL_ADDRESS>no longer maintained

added 239 packages, and audited 240 packages in 19s

28 packages are looking for funding
  run `npm fund` for details

2 moderate severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
...:azle_hell_world ???$ npx azle clean
AZLE_VERBOSE=true dfx deploy
~/.config/azle directory deleted
.azle directory deleted
azle containers stopped
azle containers removed
azle images removed
...:azle_hell_world ???$ AZLE_VERBOSE=true dfx deploy
Deploying all canisters.
Creating canisters...
Creating canister backend...
Creating a wallet canister on the local network.
The wallet canister on the "local" network for user "default" is "bnz7o-iuaaa-aaaaa-qaaaa-cai"
backend canister created with canister id: bkyz2-fmaaa-aaaaa-qaaaq-cai
Building canisters...
Executing 'npx azle backend'

Building canister backend
Looking up Podman Machine image at quay.io/podman/machine-os:5.1 to create VM
Getting image source signatures
Copying blob 2c2a685e4baa done   |
Copying config 44136fa355 done   |
Writing manifest to image destination
2c2a685e4baa3c60d2a6a6f7008f327cda3032bd63f2c7a1c170d409ea821f2e
Extracting compressed file: podman-machine-default-arm64.raw: done
Machine init complete
To start your machine run:

  podman machine start

Starting machine "podman-machine-default"

This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:

  podman machine set --rootful

API forwarding listening on: /var/folders/b2/5qd9q0xs4ld5dvtrqw8rhtyc0000gn/T/podman/podman-machine-default-api.sock

The system helper service is not installed; the default Docker API socket
address can't be used by podman. If you would like to install it, run the following commands:

        sudo /opt/homebrew/Cellar/podman/5.1.1/bin/podman-mac-helper install
        podman machine stop; podman machine start

You can still connect Docker API clients by setting DOCKER_HOST using the
following command in your terminal session:

        export DOCKER_HOST='unix:///var/folders/b2/5qd9q0xs4ld5dvtrqw8rhtyc0000gn/T/podman/podman-machine-default-api.sock'

Machine "podman-machine-default" started successfully
[]
Error: unable to inspect "azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3": failed to find image azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3: azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3: image not known

Downloading image...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 40 1077M   40  437M    0     0   892k      0  0:20:35  0:08:21  0:12:14  399k
curl: (18) HTTP/2 stream 1 was reset
Error: Command failed: curl -L -f https://github.com/demergent-labs/azle/releases/download/0.21.1/azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3.tar.gz -o /Users/???/.config/azle/azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3.tar.gz
    at checkExecSyncError (node:child_process:890:11)
    at execSync (node:child_process:962:15)
    at downloadAndLoadRemoteImage (../azle_hell_world/node_modules/azle/src/compiler/prepare_docker_image.ts:167:13)
    at loadImage (../azle_hell_world/node_modules/azle/src/compiler/prepare_docker_image.ts:84:9)
    at prepareDockerImage (../azle_hell_world/node_modules/azle/src/compiler/prepare_docker_image.ts:17:5)
    at ../azle_hell_world/node_modules/azle/src/compiler/index.ts:73:35
    at time (../azle_hell_world/node_modules/azle/src/compiler/utils/time.ts:10:26)
    at azle (../azle_hell_world/node_modules/azle/src/compiler/index.ts:66:15) {
  status: 18,
  signal: null,
  output: [ null, null, null ],
  pid: 2834,
  stdout: null,
  stderr: null
}
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to deploy canisters.
  Failed to build all canisters.
    Failed while trying to build all canisters.
      The build step failed for canister 'bkyz2-fmaaa-aaaaa-qaaaq-cai' (backend) with an embedded error: Failed to build custom canister backend.: Failed to run npx azle backend.: The custom tool failed.
...:azle_hell_world ???$ AZLE_VERBOSE=true dfx deploy
Deploying all canisters.
All canisters have already been created.
Building canisters...
Executing 'npx azle backend'

Building canister backend
Error: podman-machine-default: VM already exists
Starting machine "podman-machine-default"
Error: unable to start "podman-machine-default": machine podman-machine-default: VM already running or starting
[]
Error: unable to inspect "azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3": failed to find image azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3: azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3: image not known

Loading image...

gzip: /Users/???/.config/azle/azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3.tar.gz: unexpected end of file
gzip: /Users/???/.config/azle/azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3.tar.gz: uncompress failed
Error: Command failed: gzip -d /Users/???/.config/azle/azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3.tar.gz
    at checkExecSyncError (node:child_process:890:11)
    at execSync (node:child_process:962:15)
    at loadExistingLocalImage (../azle_hell_world/node_modules/azle/src/compiler/prepare_docker_image.ts:124:17)
    at loadImage (../azle_hell_world/node_modules/azle/src/compiler/prepare_docker_image.ts:72:38)
    at prepareDockerImage (../azle_hell_world/node_modules/azle/src/compiler/prepare_docker_image.ts:17:5)
    at ../azle_hell_world/node_modules/azle/src/compiler/index.ts:73:35
    at time (../azle_hell_world/node_modules/azle/src/compiler/utils/time.ts:10:26)
    at azle (../azle_hell_world/node_modules/azle/src/compiler/index.ts:66:15) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 3200,
  stdout: null,
  stderr: null
}
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to deploy canisters.
  Failed to build all canisters.
    Failed while trying to build all canisters.
      The build step failed for canister 'bkyz2-fmaaa-aaaaa-qaaaq-cai' (backend) with an embedded error: Failed to build custom canister backend.: Failed to run npx azle backend.: The custom tool failed.
...:azle_hell_world ???$
...:azle_hell_world ???$
...:azle_hell_world ???$
...:azle_hell_world ???$ rm -rf node_modules
npm install
npx azle clean
AZLE_VERBOSE=true dfx deploy
...:azle_hell_world ???$ npm install
npx azle clean
AZLE_VERBOSE=true dfx deploy
npm WARN deprecated<EMAIL_ADDRESS>no longer maintained

added 239 packages, and audited 240 packages in 7s

28 packages are looking for funding
  run `npm fund` for details

2 moderate severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
...:azle_hell_world ???$ npx azle clean
AZLE_VERBOSE=true dfx deploy
~/.config/azle directory deleted
.azle directory deleted
azle containers stopped
azle containers removed
azle images removed
...:azle_hell_world ???$ AZLE_VERBOSE=true dfx deploy
Deploying all canisters.
All canisters have already been created.
Building canisters...
Executing 'npx azle backend'

Building canister backend
Error: podman-machine-default: VM already exists
Starting machine "podman-machine-default"
Error: unable to start "podman-machine-default": machine podman-machine-default: VM already running or starting
[]
Error: unable to inspect "azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3": failed to find image azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3: azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3: image not known

Downloading image...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 1077M  100 1077M    0     0  2684k      0  0:06:50  0:06:50 --:--:-- 2717k

Loading image...

Loaded image: localhost/azle__image__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3:latest

Compiling...
WARNING: image platform (linux/amd64) does not match the expected platform (linux/arm64)
113a280c1f9aca85a33e4c9368238a9b483714b8e7e524c0c55141bf2c68d36e
azle__container__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3
Error: can only create exec sessions on running containers: container state improper
Error: Command failed: podman exec azle__container__5fd100a48e4fdf8a61db8e78ab48f8c270807d89dd337b81fba5315ea333baf3 rm -rf /.azle/backend
    at checkExecSyncError (node:child_process:890:11)
    at execSync (node:child_process:962:15)
    at compileRustCodeWithPodman (../azle_hell_world/node_modules/azle/src/compiler/compile_rust_code.ts:21:13)
    at compileRustCode (../azle_hell_world/node_modules/azle/src/compiler/compile_rust_code.ts:12:9)
    at compileRustCodeWithCandidAndCompilerInfo (../azle_hell_world/node_modules/azle/src/compiler/compile_rust_code_with_candid_and_compiler_info.ts:23:20)
    at ../azle_hell_world/node_modules/azle/src/compiler/index.ts:117:53
    at time (../azle_hell_world/node_modules/azle/src/compiler/utils/time.ts:10:26)
    at azle (../azle_hell_world/node_modules/azle/src/compiler/index.ts:66:15) {
  status: 125,
  signal: null,
  output: [ null, null, null ],
  pid: 4343,
  stdout: null,
  stderr: null
}
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to deploy canisters.
  Failed to build all canisters.
    Failed while trying to build all canisters.
      The build step failed for canister 'bkyz2-fmaaa-aaaaa-qaaaq-cai' (backend) with an embedded error: Failed to build custom canister backend.: Failed to run npx azle backend.: The custom tool failed.
...:azle_hell_world ???$

Please try again with Azle 0.23.0


[Vssue]9c50a6d7921244237ad75b7d7b8c70aa

https://alinblog.com/living/2019/06/17/cloud-music.html

Test

test2

test2

test

测试

测试

test

test

Test

Test

测试

测试

@linzx91

测试

回复

测试

测试

Test by Safari Browser

Test by Safari Browser

@linzx91

Test by Safari Browser

Safari repeats

@linzx91

Test by Safari Browser

Safari repeats

Test by Chrome Browser

@linzx91

Test by Chrome Browser

Chrome won’t have duplicate issues.

Test! by Chrome Browser

@linzx91

Test! by Chrome Browser

Chrome won’t have duplicate issues

Test! by Alook Browser