Configuring the SSL certs file

Is your feature request related to a problem? Please describe.
We must be able to specify the ssl certificate file to use in order to work with azure-cli inside our organization since our SSL connections are being inspected.
Describe the solution you'd like
I want to have the option in my configuration file to specify the certificates file used for SSL
Describe alternatives you've considered

Setting that as a configuration in your configuration file.
Making azure-cli to use the system certificates if available:
For Ubuntu those are /etc/ssl/certs/ca-certicates.crt

Additional context
Nothing is described in the documentations regarding this issue.
https://docs.microsoft.com/en-us/cli/azure/azure-cli-configuration?view=azure-cli-latest

What command are you trying to use?

az login

@yugangw-msft

this is still an issue as of azure-cli-2.0.57-1.el7.x86_64
path for rhel package is /usr/lib64/az/lib/python2.7/site-packages/certifi/cacert.pem
simplest way to fix it for me:
cp /etc/pki/tls/certs/ca-bundle.crt /usr/lib64/az/lib/python2.7/site-packages/certifi/cacert.pem
usecase: this is needed here because the sign on via our internal AD is being used. When connecting from our internal network the domain uses a certificate signed by our own internal ca.

I suggest use REQUESTS_CA_BUNDLE. Check out the blog for more details.

@yugangw-msft maybe that blog post is worth mentioning in the cli docs? :) but yeah I'd say that solves this issue

@Klaas- i have also thought about this, and I will add a new section to #8351.

add to S165.

Yugang's PR  #8351 has documented the SSL cert configuration and this PR has been merged. I will close this issue since it is solved.


Replica Trim Not Occurring

Freshly installed the Storage Tiering plugin. Created two replication resource branches. One was tier 0, the other was tier 1, and after 10 seconds data would replicate to the higher tier. However, data on the old tier would not delete.
While testing the storage tiering, we encountered the following error:
Jun 13 16:14:19 pid:17026 NOTICE: _rsGenQuery: genQuery status = -818000
Jun 13 16:14:19 pid:17026 NOTICE: rsGenQuery: _rsGenQuery failed, status = -818000
Jun 13 16:14:19 pid:17026 NOTICE: getDataObjInfo: rsGenQuery error, status = -818000
Jun 13 16:14:19 pid:17026 NOTICE: _rsGenQuery: genQuery status = -818000
Jun 13 16:14:19 pid:17026 NOTICE: rsGenQuery: _rsGenQuery failed, status = -818000
Jun 13 16:14:19 pid:17026 NOTICE: getDataObjInfo: rsGenQuery error, status = -818000
Jun 13 16:14:19 pid:17026 remote addresses: <IP_ADDRESS>, ::1 ERROR: [-]    /tmp/tmpIhxPZi/server/api/src/rsDataObjTrim.cpp:80:int rsDataObjTrim(rsComm_t *, dataObjInp_t* ) :  status [CAT_NO_ACCESS_PERMISSION]  errno [] -- message [failed in call to getDataObjInfoIncSpecColl for [/saraZone/home/rodsuser1/testfile.txt] CAT_NO_ACCESS_PERMISSION ]
    [-]    /tmp/tmpIhxPZi/server/core/src/irods_resource_redirect.cpp:811:irods::error irods::resource_redirect(const std::string &, rsComm_t *, dataObjInp_t* , std::string &, rodsServerHost_t *&, int &, dataObjInfo_t **) :  status [CAT_NO_ACCESS_PERMISSION]  errno [] -- message [failed in call to getDataObjInfoIncSpecColl for [/saraZone/home/rodsuser1/testfile.txt] CAT_NO_ACCESS_PERMISSION ]
        [-]    /tmp/tmpIhxPZi/server/core/src/irods_resource_redirect.cpp:610:irods::error irods::resolve_resource_hierarchy(const std::string &, rsComm_t *, dataObjInp_t* , std::string &, dataObjInfo_t **) :  status [CAT_NO_ACCESS_PERMISSION]  errno [] -- message [failed in call to getDataObjInfoIncSpecColl for [/saraZone/home/rodsuser1/testfile.txt] CAT_NO_ACCESS_PERMISSION ]
            [-]    /tmp/tmpIhxPZi/server/core/src/irods_file_object.cpp:334:irods::error irods::file_object_factory(rsComm_t *, dataObjInp_t* , file_object_ptr, dataObjInfo_t **) :  status [CAT_NO_ACCESS_PERMISSION]  errno [] -- message [failed in call to getDataObjInfoIncSpecColl for [/saraZone/home/rodsuser1/testfile.txt] CAT_NO_ACCESS_PERMISSION ]

Jun 13 16:14:19 pid:17026 remote addresses: <IP_ADDRESS>, ::1 ERROR: rsExecMyRule : -818000, [-]    /tmp/tmp2cygX3/libirods_rule_engine_plugin-storage_tiering.cpp:176:irods::error exec_rule_text(irods::default_re_ctx &, const std::string &, msParamArray_t *, const std::string &, irods::callback) :  status [CAT_NO_ACCESS_PERMISSION]  errno [] -- message [iRODS Exception:
   file: /tmp/tmp2cygX3/irods_object_migrator.cpp
   function: void irods::object_migrator::trim_replica_on_resource(const std::string &, const std::string &)
   line: 347
   code: -818000
   message:
       failed to trim obj path [/saraZone/home/rodsuser1/testfile.txt] src resc [fastResc]
stack trace:
--------------

This occurs when rodsadmin runs the rule to migrate objects between tiers, but other users' data is found. It looks similar to when the admin flag is not set on a microservice.

Confirmed - just need to add a missing keyword.   Thanks.

@Msaum87 Can you build the latest code and test your use case?  I'd like confirmation from the field before I close this issue.  Thanks.

Excellent - thanks.


Inline environment variables are not set

Describe the bug:
Probably closely related to: https://github.com/stackblitz/webcontainer-core/issues/163
Link to the blitz that caused the error: n/a
Steps to reproduce:

Run node code that throws an exception, such as here , though the reason for this exception is here: https://github.com/stackblitz/webcontainer-core/issues/165
run: NODE_OPTIONS='--trace-warnings --unhandled-rejections=strict' npm start
observe that --trace-warnings and --unhandled-rejections=strict flags are not respected

Expected behavior:

the environment variable NODE_OPTIONS is set for the duration of the command
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 91.0.4472.77 (Official Build) (64-bit)

Hi @NullVoxPopuli, thanks for reporting any issues you run into.
Inline variables are supported actually. Try running HELLO=world env or try reading it from process.env in a Node.js script, it will work.
However, npm is not the npm client from local, that would work very badly in the browser. Basically it's a proxy to our own turbo client, so it doesn't have all the features (yet).
Can you explain your use cases or what you're trying to do here?

is not the npm client from local, that would work very badly in the browser. Basically it's a proxy to our own turbo

ah ok, that makes sense, thanks!

Can you explain your use cases or what you're trying to do here?

With newer node versions, I was just trying to get rid of these warnings:
(node:6) UnhandledPromiseRejectionWarning: TypeError: Failed to fetch
(Use `node --trace-warnings ...` to show where the warning was created)
(node:6) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:6) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Locally, I have this in my .bash_profile:
NODE_OPTIONS='--trace-warnings --unhandled-rejections=strict'

Chiming in @d3lm to see if this is something we could/should add? Guess it's quite niche as long as you can't create your own personal shell profile. Which is definitely something we want over time.

I agree that having a custom shell profile where you can add aliases, define env variables etc. is a nice to have and is will very likely be supported at some point.
For the node flags, that's a good point. Right now not all flags are supported and I have created a ticket for this. Thanks for letting us know.

Hey 👋 So --unhandled-rejections=strict should be supported, but --trace-warnings is not yet supported. And I can confirm that we currently don't support a custom shell profile. I can't speak to an exact timeline but we'll keep you posted here if there's any progress on any of the issues mentioned.


Speed up Barlow Twins loss

I noticed that, when using high dimensional features (such 8192), the Barlow Twins loss takes a really long time to compute on GPU. This issue is not noticeable with lower dimensional features, such as 128, like in the example.
That is because, at each step, many tensors are allocated, and copied to the GPU.
I've modified the computations so that only the first step allocates the tensors.
Since the compute_loss_and_value_gradient is a const method, I had to make the resizable_tensor member variables mutable… However, if the size of the input changes, the tensors will be reallocated and recomputed.
I hope you are OK with this modification.
In my case, num_samples == 64 and k == 8192, it makes the network train almost 10 times faster.
I am open to some other optimization suggestions as well.

Cool, no problem, this is a good example of when to use mutable :)


OneDrive File Picker not authenticating with US national cloud

Category

[ ] Question
[ ] Documentation issue
[x] Bug

Expected or Desired Behavior
A OneDrive API app has been created following the guidelines in National cloud deployments.  We're using the OneDrive.js SDK to initiate a File Picker session. We should see a login popup at https://login.microsoftonline.us/common/oauth2/v2/authorize?... (note .us) and be able to login.
Observed Behavior
However the login popup goes to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?...  (note .com) with the following  message:
Sign in
Sorry, but we’re having trouble signing you in.

AADSTS700016: Application with identifier '5b[snip]2e' was not found in the directory 'fa7[snip]e1'. This can
 happen if the application has not been installed by the administrator of the tenant or consented to by any
 user in the tenant. You may have sent your authentication request to the wrong tenant.

Steps to Reproduce
n/a
Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues

Similar issue #1034 for German cloud.  However the patch suggested there did not work.

Update: the patch does work (partially). It goes to the "Sign in" page - after entering an email address, it says "Taking you to your organization login..." and lands on https://login.microsoftonline.com/common/OAuth2/authorize?... or https://login.live.com/oauth20_authorize.srf?... (both .com) depending on the email entered.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Show last finalize block/height

Now in the header there is a last_quorum_pre_commit, which is the hash of the last finalized block. Using this information from the latest block, we can show latest height of the final block.
For example: https://bloks.io/ under last block there is height of "Last Irreversible Block". And when you click on the block, you see if it's Irreversible or pending.
Additionally, we can show if blocks are final or not (this needs extra changes in RPC).

Design or sketch is needed for this one.

Now, we have DoomSlug finality on staging, so we need to also indicate that as well.
@ilblackdragon Should we indicate this only on the block details page or should we also display those on the Dashboard somehow? (I would imagine some small indicator, e.g. color dot with a tooltip on hover or something like that, next to every block on the right column of latest blocks)
Just for the reference, here is the screenshot of how it is displayed on blocks.io:

Implementation-wise, we need to fetch the information for the latest block height on the frontend (implement a proxy-call for block RPC on the backend like we have for tx RPC call), and use last_ds_final_block (near-final [DoomSlug]) and last_quorum_pre_commit (final [NFG]) to do two other blocks calls to fetch the block heights of the respective blocks, and then we display "Pending Finalization", "NEAR Finalized" (when the block height is <= last_ds_final_block), or "Finalized" (when the block height is <= last_quorum_pre_commit).
NOTE: last_ds_final_block is greater or equal (I don't think equality is possible, but this does not really matter in this context) than last_quorum_pre_commit, which means that when the block height is <= last_quorum_pre_commit, we should display "Finalized" ("NEAR Finalized" is a slightly weaker finalization state).
@ilblackdragon Is last_quorum_pre_vote useful for us here?

last_quorum_pre_vote isn't useful in this context

we already have this final block data but not showing directly but as isFinal tag


Typo in TZSL documentation for tz::math::lerp

Linearly interpolate between two values.
'return x * (1 - v) + y * v

Remove extra grave character I think

Fixed at 5560baddd0b020399be5fa05df2090baf9f51fb3


Fix peer verification

Referenced to #272

Fixes the problem with peer verification
SSL_connect returned=1 errno=0 state=error: certificate verify failed
Solves hostname mismatch when use ip address instead of hostname in Net::SMTP after resolving
hostname "x.x.x.x" does not match the server certificate

This looks interesting. I'll look into what's going on here and hopefully get this merged for you.

Ok, thanks!

Sorry for bulk commits, some issues with my GitHub Desktop %)


Robust imports

Right now our import system has a number of issues:

[ ] * syntax doesn't work for Kybra types
[ ] Renaming imports doesn't work for Kybra types
[ ] Parsing of Kybra types is based off of simple strings without regards to import names or paths

Generally speaking, our import system is not robust. If developers use types with the same names as those exported from Kybra, compiler issues may occur. We should address this issue, though we foresee it being a significantly complex effort.

We are closing this issue anticipating an entire rearchitecture of Kybra similar to what we have done with Azle. This removes most of the compiler architecture as it is. We believe that this issue no longer applies to the new planned architecture.
In case our rearchitecture is not successful, or we otherwise need to find these closed issues, the search term KYBRA_REARCHITECTURE can be used.


BITCODE_GENERATION_MODE = "bitcode"

This is necessary to ensure that Carthage builds frameworks with bitcode. See this issue for details.

:+1:


Feedback backend frontend functionality working #278 done

Feedback backend frontend functionality working #278 done
https://github.com/user-attachments/assets/2998e024-8527-4753-ae36-fdf4368f41ca
So what i did changes -

Create an api for the sending mail to the project admin mail.
Nodemailer setup.
create route and test it.
making fetch request connect with it in frontend.
Making feedback form responsive.
All need steps you have to perform I have write in the .env file.

Output -

You need to take care of email id and passkey for it -

Also plz increase its level from level 1 as i have to perform lots of task and generally people give it level 3 or atleast level 2.

Feedback backend frontend functionality working #278 done
20241026230800.mp4
So what i did changes -

Create an api for the sending mail to the project admin mail.
Nodemailer setup.
create route and test it.
making fetch request connect with it in frontend.
Making feedback form responsive.
All need steps you have to perform I have write in the .env file.

Output -
You need to take care of email id and passkey for it -
Also plz increase its level from level 1 as i have to perform lots of task and generally people give it level 3 or atleast level 2.

Well Done @VinayLodhi1712 .


OpenBSD returns EINVAL in the same way as DragonFlyBSD.

Without this, cargo test fails on OpenBSD -current. I suspect all the BSDs have the same behaviour in this regard, but I don't have the ability to test FreeBSD or NetBSD I'm afraid.

I think we should just get rid of the if and always use the first variant. It's not really essential anyways.

I agree -- the two new commits do that. I'm happy to squash them down to one if you'd prefer.

Thanks!


App crashes on using the camera to click the photo on Android

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open Android - should be the latest one
Go to any chat
Click on + icon
Click on Take photo
Click a photo
Click on tick mark
Notice that the app crashes on trying to upload a photo clicked using a camera

Expected Result:
App should not crash on using camera to click photo on Android
Actual Result:
App crashes on using camera to click photo on Android
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.2-5
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/233812779-600d82c3-e455-4831-bc38-51af441bd29b.mp4
Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682155995454289
View all open jobs on GitHub

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

I can't repro this on Browserstack. I've asked in #social for a hand from an Android owner. Will bump that request at 12 pm CST / 10 am PST if I don't get any volunteers.


[manuf] Add manufacturing test plan

The test cases in the manufacturing test plan aim to cover all the
operations needed to configure the device throughout various
manufacturing stages.
Test cases will be developed as libraries so that they can be integrated
into pre-silicon and post-silicon environments taking into account
device initial state pre-conditions per test case.

CC @tjaychen @msfschaffner @sriyerg @alphan
Some of the test points here will have some overlap with the top-level and the  ROM E2E test plans, so it would be good to get your inputs on what targets to aim for.

CC @tjaychen @msfschaffner @sriyerg @alphan
Some of the test points here will have some overlap with the top-level and the ROM E2E test plans, so it would be good to get your inputs on what targets to aim for.

I was able to identify one (debug/sram injection related). Please ping me when you get the chance to write the descriptions for the rest.

@moidx this gist for creating issue might come in handy.


why it crashed

Expected Behaviour
open the game
Actual Behaviour
it crashed
Reproduction Steps
Steps to reproduce the behaviour:
1.download mtr mod and it crashed
Crash Report
crash-2021-11-04_15.17.52-client.txt
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Minecraft Version:1.16.5
Installed Mods:mtr, fabric api

Additional Information
no

hello?

Have Java 6?

I am using Java 17(JDK)
It remind me to use Java 17(Jdk) when I open minecraft with Java 8(Jre)
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2021年11月5日(星期五) 晚上8:54
收件人: @.>;
抄送: "Jonathan @.>; @.>;
主题: Re: [jonafanho/Minecraft-Transit-Railway] why it crashed (Issue #203)
Have Java 6?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Hmmm. Ask in #bug reports

Hmmm. Ask in #bug reports

how to add a Lable?
thanks

@jonafanho

Please install the Fabric API mod.


Add 'Message.service_timestamp' property.

Set via the back-end set 'publishTimestamp' field in the 'PubsbuMessage' resource.
Fixes #1623.

ATM, assumes that the answer to my question in #1623 is "no".

LGTM pending rename


Add server endpoints

This adds some of the endpoints that are in Server.start(). I titled this section "Server" as I couldn't think of a better name, but there probably is one.
Also, I wasn't sure if I should add the /metadata, /hls, /s, /ebook, and /feed endpoints.

Great!


New release?

We have two new drivers, some bugfixes, and some data improvements, so I think we should have a release. Is everyone okay with this?
cc @stephanlachnit @enkore

Sure.

:+1:

With #1062 merged we can go ahead and tag a release. Thanks to everyone who contributed :blush:


Abstract all the private laravel-package-tools stuff somehow, like getNamespace()

Currently, there is a lot of helper methods that are private when working with Spatie's Laravel package tools, such as getting the package name using $this->package->shortName(); where package itself is protected anyway... Having public methods that internally call these on the service provi- oh wait! We actually have those in HasInstallationCommand!
So all we need is a new trait that contains them and that is pulled by that other trait anyway. -oh and adding its methods to the installable interface for clarity..

HasPackageHelpers trait is available in #111


add joke generator

Description
created a joke generator which has pre loaded joke and shows different jokes when website reloaded
Related Issue

Closes #18

Type of Change
creation of a new project
Please check the type of change that applies to your PR:

[ ]  Bug Fix
[ ] New Feature
[ ] Enhancement (improvements, refactoring, etc.)
[ ] Documentation Update
[ check] Other (creation of a new project):

Checklist
Before submitting your pull request, please ensure you've completed the following:

[check] I have read the CONTRIBUTING.md document and followed the contribution guidelines.
[check] My code follows the project's coding standards.
[check] I have added or updated the necessary documentation (if applicable).
[check] My changes do not introduce any new linting or test errors.
[check] All new and existing tests have passed.
[check] I have reviewed my code to ensure its quality.

Screenshots (if applicable)

Additional Information
none
Author's Note
none

@ghost-2362003 it seems like you have changes contents of other's projects, as shown by the screenshot below.
Redo this PR with only your file changes then I will merge the PR.


🍏 Validation rules, Required Fields & Typos

Describe the Task
User testing found several validation rules/required fields.

[ ] (H) Should be able to enter a second observer
[ ] (H) Should be a maximum temp for herbicide treatment, didn’t flag an error when 30 degrees selected.
[x] Humidity should not be a required field
[ ] (H) Soil texture should not be a required field
[ ] (H)Secondary applicator should not be a required field
[ ] (H)When you select a negative observation as a "yes", you still have to select the density, distribution and lifestage. (i.e these fields should not be mandatory for negative observations)
[ ] (L) Negative observation box needs to be added for each species now that we enables multiple species
[ ] (M) Should not be able to put a negative percent in for Jurisdiction
[ ] (H) REMOVE "Biocontrol field":

@mikeshasko To identify which forms these bullet points are specific to.

Ticket updated with context / confirmations


Troubleshooting a badly behaved Tesla: Fleet API must move all 4 windows or none?

Checklist

[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
This is less a "bug report" as a "discussion / request for information", but the discussions tab is not enabled for this repo, so.........
We are having a big problem with uncommanded window movement on a 2023 Model Y LR. At random, a single window will move itself away from fully closed, far more than a "vent" position, with the car parked, locked, and no one in or near the vehicle. I had a Tesla pull logs, they are claiming it is window switch activation by user, which is of course impossible if no one is in the car, it is locked, etc. Trying to rule out Fleet API / Teslemetry based on one simple question: There are only API commands that move all 4 windows to closed or to vent position, but no way for the Fleet API to command a single window to move, correct?
Thanks.
Reproduction steps

Skipping this as I highly doubt anyone would be able to reproduce this on their own vehicle *

Debug logs
No response

That is correct, as far as I am aware the Tesla Fleet API can only "vent" which opens all four windows. I believe Tessie is able to control windows individually over bluetooth only.
If you email<EMAIL_ADDRESS>with your VIN and a timerange I can check the logs to see if any Teslemetry commands were run at that time.

You can probably close this, at least for now. It has only done it once more since my first report, and I got busy so forgot to forward logs about that one event. We'll see if the problem comes back once it warms up here in the northern hemisphere, but I am really hoping one of the many firmware updates that the car has gotten lately fixed it for real.


Finish 'hook' system for plugins to react to common event

To supplement the exposition of g, c p and the vscode object that are already available for scripts, finish 'hook' system for plugins to react to common event

You do know that you have a tiger by the tail, don't you. Felix?  Your work will never be done with!

@tbpassin To be honest, there's less things to fix / broken than I expected after releasing the beta! 😄
(but still I expect being pretty busy putting out little fires here and there for the next few weeks for sure!)


don't use number is the url - use the slugified title

e.g. instead of
http://tour.dlang.io/tour/basics/3
->
http://tour.dlang.io/tour/basics/memory

Either this one or #137 otherwise it will be hard to maintain an organised file structure.

Closed in favor of #137

I think using your idea from #137 we'll be able have both. It will be just the .md file's title after XX_. We won't have a translated title but I think will be okay. Easier than the numbers.

solved by #224 :)


Downloading VK limited functionality.

Downloading VK-Communities isnt working properly. Sometimes no posts are detected and sometimes a maximum of four or five is being downloaded.

@tbrtje thanks for the issue! I've implemented pagination for VK and fixed statistics extraction


Open3d_catkin can't find PPA-installed Open3D

Hey! :slightly_smiling_face:
I followed the Installation instructions, choosing to fetch Open3D from a PPA, and then trying to compile open3d_catkin.
However, as soon as I run catkin build open3d_catkin (I configure my catkin workspace to build with cmake flag RelWithDebInfo by default), I get the following error message:
____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
Errors     << open3d_catkin:cmake /home/ynava/workspaces/open3dslam_ws/logs/open3d_catkin/build.cmake.000.log
INFO: Found Open3D.
Open3D libraries: Open3D::Open3D
Open3D include path: /usr/include , /usr/lib/x86_64-linux-gnu/cmake/Open3D/../../../include/
CMake Error at /opt/ros/noetic/share/catkin/cmake/catkin_package.cmake:300 (message):
  catkin_package() absolute include dir
  '/usr/lib/x86_64-linux-gnu/cmake/Open3D/../../../include/' does not exist
Call Stack (most recent call first):
  /opt/ros/noetic/share/catkin/cmake/catkin_package.cmake:102 (_catkin_package)
  CMakeLists.txt:54 (catkin_package)

It seems that the library is not found correctly within my system.
What could be happening?
Thanks in advance for your support.
Best,
Yoshua

Hi yoshua,
We will look at it, thanks for reporting.
Recently Edo and I changed the structure quite a bit to make it more flexible, maybe we missed something.

No prob, thank you for looking into it.
(I wanted to delve a bit deeper but I had to switch tasks, so I opened the issue to not miss on the feedback, as it could happen to other users)

Hi Yoshua,
Thank you for reporting this installation error. I'll try to reproduce it on my machine. Meanwhile, if you wanna play around and test stuff, you could try to build from source. Did you try that yet?

yep, maybe just do it without the ppa installation and check whether this works for you. I am checking the ppa one right now.

@YoshuaNava, I could reproduce your error.
Can you please check #41?
Hopefully this solves it.

please reopen if there are still issues


Consider moving from metalinter to staticcheck

Description
The next release of @dominikh's staticcheck tool looks very promising:
http://next.staticcheck.io/changes/2018.1
gometalinter, which we're currently, using has significant performance drawbacks, and the complexity of its installation and configuration is also non-trivial. These problems are mostly due to it being a runner of other tools, which staticcheck looks to be solving in its next release.
If we do end up doing this, let's look into contributing financially to the project - either through sponsorship or purchasing a support package.
Success Criteria
We should have much faster builds/checks both locally and in CI - possible that we'll also get better checks which are consistently updated and added to without us having to manually enable, disable, or configure individual checks.

I don't think this replaces gometalinter. It looks like this is just a restructuring of the same linters that were included in megacheck (gosimple, unused, and staticcheck), which is included in our enabled linters in gometalinter. Until this new staticcheck supports all the functionality we get through the other linters, I would recommend continuing to use gometalinter in CI.
Also note that the linter now runs in parallel with the test runners in CircleCI, so the runtime in CI is not as important as it was on TravisCI. We can also choose to pay a fee for a more beefy CI environment if performance is a productivity blocker.

#1924


schedulability problem

We have a problem re: the schedulability functionality.
As we understand it (this is being tested now) the schedulable flag for the node is intended to be entirely controlled by Chef in this code.
The problem we have is that making changes to production role definitions takes too long, and we don't have root access. So if we used admin access to change schedulability for any reason then Chef would come in and override.
Would you object to a flag around this functionality to prevent chef from controlling it for this use case (defaulting to false, so back-compatible)?

Agree @ianmiell  .
Let's pretend I am doing maintenance on a node; I would start by running oadm cordon <node> and finish the maintenance by running oadm uncordon <node>. What if during the maintenance I want to run chef-client to fix some configuration files? In the current state, running chef-client will automatically uncordon the node unless I disable scheduling of the node in the attributes of the first master node, which is a cumbersome. I'd rather have a way to opt-out of chef managing the node schedulability and do it manually with the oadm tool.

Hi both,
So what would we like to achieve here? A way to skip that part as needed or a run once style?
Will

I would vote for skip.
On Wed, Mar 1, 2017 at 9:49 PM, William Burton<EMAIL_ADDRESS>wrote:

Hi both,
So what would we like to achieve here? A way to skip that part as needed
or a run once style?
Will
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/issues/91#issuecomment-283481778,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczVP_xetAMKR98L6BvIyBcYlGVBWDks5rhef9gaJpZM4MPWfs
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

#95

Thanks @IshentRas :)

I believe it has been solved so closing.


Remove duplicate network alias in docker compose file

Ref: https://github.com/apache/amoro/issues/3086

@ideal Thanks for your contribution, good job.


IE11 bugfix

ES2016 for ... of ... iteration is not supported in IE 11, fix for #159
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of#Browser_compatibility

There is another bug in code. FormData must be polyfilled for Edge and IE 11 https://github.com/jimmywarting/FormData


Password shouldn't be shown when entering credentials

This package can assist here:
https://www.npmjs.com/package/prompt

+1 to hiding password typing.


HBASE-28980 Change the default Hadoop 3 version to 3.4.1 on branch-2.…

…5 and branch-2.6

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 55s

branch-2.6 passed

+1 :green_heart:
compile
5m 42s

branch-2.6 passed

+1 :green_heart:
spotless
0m 45s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 49s

the patch passed

+1 :green_heart:
compile
5m 42s

the patch passed

+1 :green_heart:
javac
5m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shellcheck
0m  1s

No new issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
14m 53s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 45s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

37m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6478

Optional Tests
dupname asflicense codespell detsecrets shellcheck shelldocs spotless javac xmllint hadoopcheck compile

uname
Linux 4b95b5e1564a 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 6b6379c9ca6678461c0993f871d5c3d69181329d

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
72 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-with-hadoop-check-invariants . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/1/console

versions
git=2.34.1 maven=3.9.8 shellcheck=0.8.0 xmllint=20913

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 49s

branch-2.6 passed

+1 :green_heart:
compile
2m  5s

branch-2.6 passed

+1 :green_heart:
javadoc
2m 22s

branch-2.6 passed

+1 :green_heart:
shadedjars
5m 16s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 56s

the patch passed

+1 :green_heart:
compile
2m  5s

the patch passed

+1 :green_heart:
javac
2m  5s

the patch passed

+1 :green_heart:
javadoc
2m 21s

the patch passed

+1 :green_heart:
shadedjars
5m 34s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
250m 27s
/patch-unit-root.txt
root in the patch failed.

283m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6478

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e28e8610ae00 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 6b6379c9ca6678461c0993f871d5c3d69181329d

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/1/testReport/

Max. process+thread count
4951 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-with-hadoop-check-invariants . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 10s

branch-2.6 passed

+1 :green_heart:
compile
5m 33s

branch-2.6 passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 45s

the patch passed

+1 :green_heart:
compile
5m 24s

the patch passed

+1 :green_heart:
javac
5m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shellcheck
0m  1s

No new issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
16m 49s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m  3s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
1m  7s

The patch does not generate ASF License warnings.

40m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6478

Optional Tests
dupname asflicense codespell detsecrets shellcheck shelldocs spotless javac xmllint hadoopcheck compile

uname
Linux 5ab28c97ba8c 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 3b5fcc4793fc9d09a4eb052558076c7f64f696c7

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
73 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-with-hadoop-check-invariants . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/console

versions
git=2.34.1 maven=3.9.8 shellcheck=0.8.0 xmllint=20913

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 17s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 33s

branch-2.6 passed

+1 :green_heart:
compile
2m 30s

branch-2.6 passed

+1 :green_heart:
javadoc
3m  7s

branch-2.6 passed

+1 :green_heart:
shadedjars
7m 32s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 46s

the patch passed

+1 :green_heart:
compile
2m 43s

the patch passed

+1 :green_heart:
javac
2m 43s

the patch passed

-0 :warning:
javadoc
2m 19s
/results-javadoc-javadoc-root.txt
root generated 10 new + 90 unchanged - 10 fixed = 100 total (was 100)

+1 :green_heart:
shadedjars
5m 33s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
311m 36s
/patch-unit-root.txt
root in the patch failed.

350m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6478

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e1df986d1a3d 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 3b5fcc4793fc9d09a4eb052558076c7f64f696c7

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/testReport/

Max. process+thread count
4945 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-with-hadoop-check-invariants . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 15s

branch-2.6 passed

+1 :green_heart:
compile
3m  3s

branch-2.6 passed

+1 :green_heart:
javadoc
3m  6s

branch-2.6 passed

+1 :green_heart:
shadedjars
7m 57s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 50s

the patch passed

+1 :green_heart:
compile
3m 39s

the patch passed

+1 :green_heart:
javac
3m 39s

the patch passed

+1 :green_heart:
javadoc
4m  2s

the patch passed

+1 :green_heart:
shadedjars
7m 35s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
321m 20s

root in the patch passed.

368m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6478

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 271271ec03a5 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 3b5fcc4793fc9d09a4eb052558076c7f64f696c7

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/testReport/

Max. process+thread count
8426 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-with-hadoop-check-invariants . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6478/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Failed to create IAM Policy

What happened?

I tried to create an I am IAM Policy and it produced the following error
{"object": {"kind":"Policy","name":"test-policy-crossplane"," │
│ uid":"8957d567-707b-4fc4-8ba8-e8780914ad92","apiVersion":"iam.aws.crossplane.io/v1beta1","resourceVersion":"4059524" │
│ }, "reason": "CannotObserveExternalResource", "message": "failed to update the IAM Policy external-name: operation e │
│ rror STS: GetCallerIdentity, failed to sign request: failed to retrieve credentials: operation error STS: AssumeRole │
│ , failed to resolve service endpoint, an AWS region is required, but was not found"}

How can we reproduce it?

apiVersion: iam.aws.crossplane.io/v1beta1
kind: Policy
metadata:
  name: test-policy-crossplane
  # annotations:
  #   crossplane.io/external-name: "arn:aws:iam::407967248065:policy/test-crossplane"
spec:
  deletionPolicy: Orphan
  providerConfigRef:
    name: sti-provider
  forProvider:
    description: "Test policy"
    name: test-crossplane
    document: |
      {
          "Version": "2012-10-17",
          "Statement": [
              {
                  "Sid": "VisualEditor0",
                  "Effect": "Allow",
                  "Action": "s3:ListBucket",
                  "Resource": "*"
              }
          ]
      }

apiVersion: aws.crossplane.io/v1beta1
kind: ProviderConfig
metadata:
  name: sti-provider
spec:
  assumeRole:
    roleARN: "arn:aws:iam::<account-id>:role/testing-role-gitops"
  credentials:
    source: InjectedIdentity

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: aws-provider
spec:
  package: crossplane/provider-aws:v0.26.1
  controllerConfigRef:
    name: aws-config

What environment did it happen in?
Crossplane version: Helm chart 1.7.0

Cloud provider or hardware configuration: EKS
Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:30:48Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.6-eks-7d68063", GitCommit:"f24e667e49fb137336f7b064dba897beed639bad", GitTreeState:"clean", BuildDate:"2022-02-23T19:29:12Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes distribution (e.g. Tectonic, GKE, OpenShift)
EKS
OS (e.g. from /etc/os-release)
Kernel (e.g. uname -a)

@steve-fraser  I’m also facing the same issue while creating IAM Policy. Any solution or workaround?

@muvaf 👆

@ganeshk1928, I ran into this same issue.  We figured a workaround by setting the region in the Controller Config.  It appears to be a bug in that the region flagged in the resource is not taken.  In my testing this region in the Controller Config does not impact or influence anything.
`apiVersion: pkg.crossplane.io/v1alpha1
kind: ControllerConfig
metadata:
name: aws-config
spec:
args: ['-d']
env:

name: AWS_REGION
value: us-east-2`

Hey @3pings , what kind of authentication are you using in your provider config. Is it assumeRole or AWS credentials? Because we use assumeRole for authentication which basically will not need any controller-config. Anyway, I'll try to create the controller-config and see what happens.

I have similar encounter while running crossplane in private EKS cluster with controlled egress (no internet connection except private link or vpce)
When IAM policy controller is being called, sts.GetCallerIdentity is being called to retrieve the AWS partitionID, AccountID, etc. This particular call is making use of STS global endpoint instead of regional one.
While allowing egress traffic to sts.amazonaws.com for your EKS cluster. The call seem to be able to successfully sign the request with the right credential token.
Hope this helps for anyone encountering this issue


Unable to create project

You are running 'create-react-app' 4.0.3, which is behind the latest release (5.0.0).
We no longer support global installation of Create React App.
I receive the above message and Im told to uninstall globals. Ive done this several times and no matter what create-contentful-app does not run. The react version (create-react-app) works flawlessly. This project worked yesterday, and began failing today, which is why I deleted the project and attempted to start from scratch.  Any help would be greatly appreciated.

Hey @rickykissoon that's a good catch. The release of create-react-app v5 broke our script.
It should be working again after a bump of the version with:
#759

Awesome, thanks for the quick response!


How to use this?

I have added your library, in Android, it only show me which account to use but not asking for permission?

Hey, that's how GoogleFit works. You select the account and it only asks for read access. It's not how HealthKit who asks for every data type separate acceptance.


No sample for .NET

Would it be possible to get a sample for .NET as there doesn't seem to be any available

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 906f1086-776e-9abe-b6cc-bf93e84dc238
Version Independent ID: 50b27c9e-8f8a-3425-a1bb-b5d30e9d95e4
Content: Configure protected web API apps - Microsoft identity platform
Content Source: articles/active-directory/develop/scenario-protected-web-api-app-configuration.md
Service: active-directory
Sub-service: develop
GitHub Login: @jmprieur
Microsoft Alias: jmprieur

@ashinzekene Thanks for the feedback. We're investigating this and will get back to you shortly.

@ashinzekene : the samples are referenced from the last article of the section "Protected web API". See
https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-protected-web-api-production#next-steps
You also have the samples page that references all the samples
Proposing to close as answered. Feel free to reopen if you disagree
#please-close


Flutter Dartanalyzer plugin

These are ideas for our analyzer plug-in.
Features for Dart in General

[ ] Warn when you use a label, to catch errors like: https://github.com/flutter/flutter/commit/f808055756d3b7946be90a4aec74e59eb40eddba#diff-6d433f126d05f45352a40b9bb916ac70R779
[x] @mustCallSuper for methods what when overridden must call super somewhere.

[x] annotation in meta
[x] lint: https://github.com/dart-lang/linter/issues/194

[x] @protected for members that must only be used in instance members of subclasses.

[x] annotation: https://github.com/dart-lang/sdk/issues/25841
[x] lint: https://github.com/dart-lang/linter/issues/189

[ ] @immutable for class hierarchies that must be immutable

[ ] annotation in meta
[ ] lint

[ ] operator == on all @immutable objects
[ ] @factory for functions whose overrides must return newly allocated objects

[x] annotation in meta
[ ] lint

[ ] @literal on const constructor to require 'const' for any call to that constructor if all the arguments are themselves const expressions (to catch e.g. new Size(1.0, 1.0)).

[x] annotation in meta
[ ] lint

[ ] If a List or Map literal consists entirely of const expressions, require that the list or map be const also.
[ ] disallow use of super to refer to any member other than the one being overridden.
[ ] implicit dynamic

[x] variables, method arguments, type arguments
[ ] Map and List literals
[x] don't ask for types on setters
[x] annotation to label a class as having optional type arguments

[ ] @required on optional arguments which requires the argument to be present

[x] annotation in meta
[x] warning (https://github.com/dart-lang/sdk/issues/26182)

[ ] all final fields compared by operator == and listed in hashCode.
[x] hashCode on anything with an operator ==

[x] https://github.com/dart-lang/linter/issues/168

[x] disallow == operator to be used when the types inferred on both sides aren't compatible
[x] Constructors are first in a class

[x] https://github.com/dart-lang/linter/issues/186.

[x] Default constructor is first constructor

[x] https://github.com/dart-lang/linter/issues/187

[ ] operator==, hashCode, toString are last in a class.
[ ] public members have dartdocs

[x] https://github.com/dart-lang/linter/issues/188

[x] @override that complains when a method is an override but doesn't say @override and that complains when a method isn't but does

[x] https://github.com/dart-lang/linter/issues/167

[ ] @mustOverride

[ ] https://github.com/dart-lang/sdk/issues/28250

Very Flutter-specific

[ ] Something to note that a class hierarchy requires every public field to be read during debugFillDescription
[ ] verify that you don't write a class that implements a class from the Flutter framework unless that Flutter framework class is marked @interface. (see https://github.com/dart-lang/sdk/issues/25462)
[ ] Warning about buttons without an onPressed argument.
[ ] Warn when a StatefulWidget mutates a member field outside a setState() callback.
[ ] Warn when a Padding contains a Block, that you may want to use the Block's padding member instead
[ ] Warn when a Color's constructor's argument is a literal int that isn't in hex.
[ ] Warn when a Color's constructor's argument is a hex literal that isn't exactly 8 characters long.
[ ] Suggest putting child/children arguments last in constructors.
[ ] Warn when a subclass of State defines a constructor (it should use the default constructor and do initialization in initState(), accessing any final configuration information using the widget getter).

[ ] @factory for functions whose overrides must return newly allocated objects

[ ] @override that complains when a method is an override but doesn't say @override and that complains when a method isn't but does.

cc @pq

Something to note that a class hierarchy requires every public field to be read during debugFillDescription

[ ] implicit dynamic (if it's not done by the analyzer proper by the time we get to this)

[ ] verify that you don't write a class that implements a class from the Flutter framework unless that Flutter framework class is marked @interface. (see https://github.com/dart-lang/sdk/issues/25462)

[ ] all final fields compared by operator == and listed in hashCode.
[ ] operator == on all @immutable objects
[ ] hashCode on anything with an operator ==

[ ] Constructors are first in a class.
[ ] Default constructor is first constructor.
[ ] operator==, hashCode, toString are last in a class.
[ ] Public members have dartdocs.

(I dunno if these are actually possible; the necessary information may be lost once the analyzer's parsed the code.)

[ ] @required on optional arguments which requires the argument to be present

[ ] == operator used when the types inferred on both sides aren't compatible

[ ] disallow use of super to refer to any member other than the one being overridden.

[ ] Warning about buttons without an onPressed argument.

https://github.com/flutter/experimental-temporary-dartanalyzer-fork/pull/2

[ ] @literal on const constructor to require 'const' for any call to that constructor if all the arguments are themselves const expressions (to catch e.g. new Size(1.0, 1.0)).

[ ] If a List or Map literal consists entirely of const expressions, require that the list or map be const also.

I've merged all the individual suggestions into the top of this issue. This helps Github track progress.

[ ] Warn when a StatefulComponent mutates a member field outside a setState() callback.

question on @factory ... does it mean "returns any object that was allocated between the start and end of the method call" or does it imply something more specific about the allocation?
I'm wondering about whose overrides must return newly allocated objects ... does the override have to return a tighter type?
An example might help. By the way, it seems neat to me, just trying to understand what it means.

returns any object that was allocated between the start and end of the method call

Yes, that.

does it imply something more specific about the allocation?

I don't think so...

does the override have to return a tighter type?

Not necessarily.

An example might help.

http://docs.flutter.io/flutter/widgets/StatefulComponent/createState.html is an example.  Subclasses are supposed to override that function and return a newly allocated object.  Some people try to return an existing object, but that's not permitted by the contract for that function.

Thanks, that example is great! It's sort of like saying, "this method will return a State that is unique, i.e. not identical, from all other State instances that exist before the call".
Would it be bad if the function cached the value?
State createState() => _state = new MyState();

Reason I ask, it sort of feels like a https://en.wikipedia.org/wiki/Uniqueness_type, but not quite. Anyway, it's not important :), was just trying to wrap my head around how it might relate to other type system features.

Would it be bad if the function cached the value?

That implementation is not allowed by the contract of that method.

Reason I ask, it sort of feels like a https://en.wikipedia.org/wiki/Uniqueness_type, but not quite

Yes, another way of stating the desired property is that the return value of this function contains the only reference to that instance of the object.

Warn when a Padding contains a Block, that you may want to use the Block's padding member instead.

The constructors being first in class seems like something the formatter should enforce, not the analyzer.

This might be covered by a couple of comments above (ie. Buttons should have impressed argument) but it's be nice to be able to say "these named parameters to the function/ conductor must be supplied and must be non null.  (ie. Even though they appear optional, they are required)

The constructors being first in class seems like something the formatter should enforce, not the analyzer.

At the moment, the formatter is not opinionated about member sorting.  My sense from chats with @munificent are that it never will be...

This might be covered by a couple of comments above (ie. Buttons should have impressed argument) but it's be nice to be able to say "these named parameters to the function/ conductor must be supplied and must be non null. (ie. Even though they appear optional, they are required)

We've actually just landed a new @required annotation (https://github.com/dart-lang/sdk/commit/33250f8ff5305f3e7de61f8553cd4a42e5b0c0cf) with this use case in mind (doesn't enforce non-nullability though)...

Seems like @required should enforce non-null as the default of not providing something is for it to be null.  Perhaps you don't know if its null at analyzation time, however.

Right.  CC @bwilkerson for more on that....

The constructors being first in class seems like something the formatter should enforce, not the analyzer.

At the moment, the formatter is not opinionated about member sorting. My sense from chats with @munificent are that it never will be...

yeah, I feel like we're going to need a new tool to handle automatic code style conventions.
Originally my hope was the formatter, but it got a self-imposed whitespace-only rule.
Then my hope was the linter, but it only displays messages, not offering to fix things that can be fixed in automated fashion. But maybe it could be extended... ?  Or do we need a third thing?
(Just coming from the users perspective here. We should make their lives easy and fix anything we can fix automatically.)

Seems like @required should enforce non-null as the default of not providing something is for it to be null. Perhaps you don't know if its null at analyzation time, however.

Yeah, that's exactly right. We don't have non-null in Dart's type system, so Analyzer doesn't understand it.
There is a lovely proposal to fix that: https://github.com/dart-lang/dart_enhancement_proposals/issues/30
As soon as we get some spare time (from finishing up strong mode, generic methods) I think NNBD will be next on the list.

Then my hope was the linter, but it only displays messages, not offering to fix things that can be fixed in automated fashion. But maybe it could be extended... ?

:+1:
Lints are just errors as far as the analyzer and server are concerned which means they're just as easy to hang quick-fixes off.  Adding quick fixes to server would be trivial.  Tooling to automatically apply them wouldn't be hard either.

I'm not worried about people explicitly passing null. That's an explicit action. I'm more worried about people unknowingly omitting key arguments and never finding out because they miss that code path in their testing. (We assert that required arguments are non-null, so if you hit that code path in testing you'll find out already -- this is just about catching things statically.)

yeah I think the main benefit of @required is to give Dart "required named parameters". Named parameters read well at the call site. But if the parameter is actually required, making it optional can open a hole in static verification of the program. Required named parameters solves that. Kind of matches how positional parameters can be required or optional.

I would think the dart language itself should have a construct for required named parameters (maybe a leading ! or some other symbol similar to how a leading _ is supposed to indicate a private variable.)

@apwilson it's easier to start with annotations, try it out, and decide if the frequency merits dedicated syntax. But in the long run, you may be right about having syntax.

At the moment, the formatter is not opinionated about member sorting. My sense from chats with @munificent are that it never will be...

In general, the formatter does not make any changes that involve reordering. It keeps things simpler because then it doesn't have to worry about all of the weird corner cases around comments between the moved code.
I'm not averse to automated reordering in general. I like tools that sort my imports.
I am not personally a fan of automated member reordering. Alphabetization has zero value for me—I don't find a member by scrolling down the file looking at names, I do a search if I know its name. I prefer members to be logically grouped together.

For stuff flagged as an error can we have some reasoning added to the error message?
For example:
[lint] Avoid using braces in interpolation when not needed.

Doesn't really say why.  If it's because of some style guide we should link to the style guide.  If its because it could cause an error we should say what kind of error it could cause imo.  Or link to a description.

For stuff flagged as an error can we have some reasoning added to the error message?
[lint] Avoid using braces in interpolation when not needed.

The answer for that one is:
https://www.dartlang.org/effective-dart/usage/#avoid-using-curly-braces-in-interpolation-when-not-needed
Best place to file an issue for it is:
https://github.com/dart-lang/linter/issues

Unfortunately that link doesn't really elaborate anymore than the original string.
If linter is the source of this message, how come we see this in flutter analyze and not dartanalyzer, its from the --strong option or something?

Rule number 2 here basically justifies the guideline in question. "Hi $name." is more terse than "Hi ${name}.", so unless the extra verbiage adds value in some other way, the guidelines lean towards the more terse option.

It's because lints are disabled by default in dartanalyzer, but enabled by default in flutter analyze. You can pass the --lints option to dartanalyzer to enable lints.

Warn when you use a label, to catch errors like: https://github.com/flutter/flutter/commit/f808055756d3b7946be90a4aec74e59eb40eddba#diff-6d433f126d05f45352a40b9bb916ac70R779

[ ] Warn when a Color's constructor's argument is a literal int that isn't in hex.
[ ] Warn when a Color's constructor's argument is a hex literal that isn't exactly 8 characters long.

I've rearranged the list of lints in the first section. I tried prioritising the things there but honestly there's nothing I would say is a particularly low priority compared to the rest.

Could we give this issue an update, checking off lints we've added? I see various ideas spread across many comments. Getting a single list, prioritized, would be helpful. Thanks!

The top comment has been kept up to date with the list of ideas and with checking off those that are done.

Opened https://github.com/dart-lang/sdk/issues/27750 for the request for @immutable

@mustOverride would be useful in some places, see also https://github.com/dart-lang/sdk/issues/28250

I added to the top comment that we should warn when a subclass of State defines a constructor (it should use the default constructor and access its configuration with the widget getter).

I'm not sure how good the accessibility story is for Flutter yet (looks like there's work being done), but I'd love a set of lint warnings for accessibility violations as a developer so I can keep my app in good shape wrt Accessibility.
Example:

[ ] Error: IconButton does not have a tooltip
[ ] Error: Image does not have description (although I actually don't right now see a way to apply accessible text to images)

etc...

Thanks for the ideas!

Warn when a Padding contains a Block, that you may want to use the Block's padding member instead

@Hixie: I think this one is stale (no more Block)...  but are there modern equivalents to the advice?

Block is called ListBody now but I'm not sure it's be useful to talk about that one specifically. What we really should do is review some applications and see if there are patterns of mistakes.

In conversation about idioms we might enforce to make code easier to review (and less prone to error), @HansMuller suggested:

Another idiomatic invariant that probably makes sense is to insist that the same class bear responsibility for creating and disposing classes like AnimationController, TextEditingController.

Yeah this is just like StreamController, right?

Warn when a StatefulWidget mutates a member field outside a setState() callback.

Actually, I was thinking, why can't you just have the mutating code, and then call setState?
Like, instead of (assuming there is a field called value:
void increment() => setState(() => value++);

Just do
void increment() {
  value++;
  setState()  // rewrite setState to not need the callback parameter
}

The fact that this will need its own line isn't so bad since most production code will anyway have functions more than one line long. In such functions, it can be annoying, if not redundant, to separate the "calculating the value" from "assigning that value to the field", and it often trips up beginners who have to separate the two in their heads.

Was this meant to be closed? https://github.com/dart-lang/linter/issues/2070 still refers to it and it might make it look that that issue can be closed as well.

Ah yeah we can close that one too. I closed this one because we've added the majority of the suggestions listed above and at this point new suggestions just get filed directly on the linter repo, which is more appropriate.


Fix unmarshaling when additionalProperties is an object or true

Fixes #5 and #7.

additionalProperties now defaults to true and I've extended the tests accordingly.

I've integrated the changes according to our discussion.

Thanks!

Thanks for the discussions and your feedback!


Modifes Request and Response objects to contain all properties

Fixes #268 Modifies Request and Response objects to contain all properties passed in request/response objects, so they can be used as middleware (e.g. in the authenticationHandler).  Added tests for Request and Response.

also added pre-test linting (via JSHint) and use strict

:+1: from me.


dose it can use xshell to connect？

like WSL ubuntu，I can use xshell to connect it。but now，i set the CentWSL in the same way like WSL Ubuntu，but I still can not connect it with xshell...   the command line replay： Failed to get D-Bus connection: Operation not permitted

can you start the service , i think it is a systemctl problem

This is duplicated issue, so please move to:
https://github.com/yuk7/CentWSL/issues/11


⚠ ClamAV has degraded performance

In 1e4b7b2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 9b8a680.


Test the app can be loaded in production pip env

The intention is catch when you accidentally forget to add stuff to
requirements, because it happens to be in the local test/dev
environments).
I expect this to fail until I add a further commit to include the missing requirement.

When this is merged, a new docker image should be built off master:
docker build -t ebmdatalab/openprescribing-base .
docker build -t ebmdatalab/openprescribing-test -f Dockerfile-test .
docker push ebmdatalab/openprescribing-base
docker push ebmdatalab/openprescribing-test

Note that as a side-effect, tests now output warnings about configuration -- see the end of the output at https://travis-ci.org/ebmdatalab/openprescribing/jobs/163114007

Not exactly reviewing this with an expert eye (and I haven't tried running the Docker image), but LGTM 👍


version change: 0.3.0 > 1.0.0

Codecov Report
Patch and project coverage have no change.

Comparison is base (656c352) 94.15% compared to head (e1e1e6c) 94.15%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   94.15%   94.15%
=======================================
  Files           3        3
  Lines         342      342
  Branches      320      320
=======================================
  Hits          322      322
  Misses         20       20

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Ensure names are unique for all stages

We are suffering from a small yip regression. Since v1.0.0 yip uses a DAG (Directed Acyclic Graph) to sort and relate all the required executions, allowing parallel executions (we have not played with it so far). However one of the side effects is that the dag structures items in a map internally using the step name if provided, hence having two steps with the same name causes the step overwrite.
Exactly this is what is happening in the layout setup, we have two steps for that (recovery and non recovery) with the same name, so one of the two gets ignored...
Fixes #829

Shouldn't this be detected by yip (iow isn't this a yip bug) ?

Yes, this is a yip issue. So this is a simple, sane and fully functional workaround for now.

Already opened the yip counter part https://github.com/mudler/yip/pull/88


MINIFI-97 minifi.sh stop fix

reviewing

Looks good, thanks for finding and patching up.
Will merge in shortly.


[Feature] support refresh iceberg incremental partitions

Fixes #31966
What type of PR is this:

[ ] BugFix
[ ] Feature
[X] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 111 (01.80%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/iceberg/TransformUtil.java
0
15
00.00%
[31, 32, 35, 39, 40, 44, 45, 46, 50, 54, 58, 62, 63, 64, 69]

:large_blue_circle:
com/starrocks/connector/iceberg/Partition.java
0
8
00.00%
[24, 25, 26, 27, 31, 35, 36, 39]

:large_blue_circle:
com/starrocks/connector/iceberg/IcebergUtil.java
0
60
00.00%
[35, 42, 43, 44, 45, 46, 48, 49, 50, 51, 52, 53, 54, 58, 59, 60, 62, 63, 64, 66, 68, 72, 73, 74, 75, 77, 78, 81, 82, 83, 84, 85, 86, 87, 89, 90, 91, 98, 99, 100, 104, 105, 106, 107, 108, 110, 111, 113, 114, 116, 119, 121, 125, 126, 127, 128, 129, 130, 131, 132]

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
2
28
07.14%
[709, 710, 711, 712, 713, 715, 716, 717, 718, 721, 722, 723, 725, 727, 728, 729, 731, 732, 734, 736, 737, 738, 740, 741, 742, 815]


Fix minor bugs and code refactoring

:Release Notes:
Fix minor bugs and code refactoring
:Detailed Notes:

Convert function that generates date format file name to a library
Modify repeated code into a common function
Fix the part where the config created by the command is different from the git file
Sort order of source require

:Testing Performed:

Pass unit test on ose
Check below commands and results
2-1. ares-config -p ose

check git status and no diff files/config/config.json
2-2. Check each operation of ares-install/launch/device

:Issues Addressed:
[WRN-1725] Fix minor bugs and code refactoring of CLI

Could you update npm-shrinkwrap.json? The reason is that "ora" is added package.json in "add spinner" commit.

@ssuminahn <
All unit test passed? When I ran unit test, it failed because "spinner" importing has been removed. Please check and verify it again.
Code :-1:
Verified :-1:


added a few simple jobs involving various appliances

added a few bots similar to the existing ones.

bone collector
brush collector
bug collector
miner & landscaper
watercarrier
thief

added support for using tools, and added a couple bots based on this.

gardener
wizard

extended handle_chest() logic to implement a more generic handle_appliance() method.
added a few simple bots based on this method.

I really appreciate this load of new features. Great work on implementing a lot of things.

Your API provides a good starting point for what I want to do.

There are a few things that still need doing here though. For example there is a lot of redundant code that could use some more api and modularity. There are inconsistencies within the files and other things that need some cleanup.

Yes. There was a lot of redundant code already in the code base and I only exacerbated that problem. I will be deduplicating as I go (you should have seen what it looked like before handle_appliance()). I plan to make the job functions more modular and reuseable so as to allow hybrid jobs and job-switching. I feel that our power users will enjoy coding bot-logic at such a high level.

I personally would like to see these new changes added to the mod, however this huge pull request is rather difficult to review.

This is... ADHD, no doubt. A lot of these commits touch 1000+ lines throughout the entire code base. If this repo were more active, the resulting merge conflicts would be a nightmare. I'm truly sorry for the Atlassean amount of code, and I'm grateful for the time you've taken to review it. This is my first pull request, and any feedback is useful.

Maybe these changes could be added in smaller portions, to make sure it stays maintainable. One possibility to make things easier would be chopping up the features into smaller pull requests to allow easier integration.

I will learn this. I can see myself refactoring everybody's mods to expose an API. It might also make me less likely to disable a mod as soon as it raises an error....


Add initial tests (fixes #3)

Adds

tests for basic usage with & without the onOuput option
a test for CSS using the composes keyword

ava felt like a good fit so I went with that. I hope that's okay :)
Dedicated tests for the writeDebounceMs, minimalJson & rootPath options and the onAfterOutput callback are yet to be implemented.

Closed in favor of https://github.com/andersekdahl/extract-css-module-classnames-loader/pull/4 (PR to the develop branch).


settings.inc.php is stiil searched in 1.7 upgrade

The CLI upgrade still search for settings.inc.php in 1.7.
Here is the returned error (not in debug mode) :
PHP Warning:  file_get_contents(/home/dir/public_html/config/settings.inc.php): failed to open stream: No such file or directory in /home/dir/public_html/modules/autoupgrade/classes/PrestashopConfiguration.php on line 81
Upgrade environment (please complete the following information):

Version you started from: [e.g. <IP_ADDRESS>]

Version you upgrade to: [e.g. <IP_ADDRESS>]

Way of upgrade: CLI

Step concerned:  upgrade file and DB

Module Version v4.8.0

Hi @jf-viguier,
I use PS<IP_ADDRESS>.
I installed the 1-click upgrade 4.8.0.
I tried to make an upgrade with CLI

cd /project_folder/modules/autoupgrade/
php cli-upgrade.php --dir=admin-dev --channel=major

I get this
INFO - === Step upgradeNow
INFO - Starting upgrade...
INFO - Shop deactivated. Now downloading... (this can take a while)
INFO - === Step download
INFO - Download complete. Now extracting...
INFO - === Step unzip
INFO - File extraction complete. Removing sample files...
INFO - === Step removeSamples
INFO - All sample files removed. Now backing up files.
INFO - === Step backupFiles
INFO - Backup files in progress. 20840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 20440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 20040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 19640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 19240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 18840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 18440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 18040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 17640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 17240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 16840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 16440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 16040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 15640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 15240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 14840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 14440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 14040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 13640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 13240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 12840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 12440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 12040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 11640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 11240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 10840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 10440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 10040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 9640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 9240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 8840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 8440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 8040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 7640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 7240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 6840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 6440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 6040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 5640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 5240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 4840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 4440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 4040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 3640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 3240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 2840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 2440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 2040 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 1640 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 1240 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 840 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 440 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 40 files left
INFO - All files saved. Now backing up database
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 237 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 232 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 232 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 232 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 232 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 232 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 232 table(s) left...
INFO - === Step backupDb
INFO - Database backup: 132 table(s) left...
INFO - === Step backupDb
INFO - 132 tables have been saved.
INFO - Database backup done in filename V<IP_ADDRESS>_20190613-165525-3a526a86. Now upgrading files...
INFO - === Step upgradeFiles
INFO - 20453 files will be upgraded.
INFO - === Step upgradeFiles
INFO - 20053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 19653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 19253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 18853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 18453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 18053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 17653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 17253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 16853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 16453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 16053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 15653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - [TRANSLATION] The translation files have been merged into file /projet/1751/modules/ps_themecusto/translations/fr.php.
INFO - 15253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 14853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 14453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 14053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 13653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 13253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 12853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 12453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 12053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 11653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 11253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 10853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 10453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 10053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 9653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 9253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 8853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 8453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 8053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 7653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 7253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 6853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 6453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 6053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 5653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 5253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 4853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 4453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 4053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 3653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 3253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 2853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 2453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 2053 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 1653 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 1253 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 853 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 453 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 53 files left to upgrade.
INFO - === Step upgradeFiles
INFO - All files upgraded. Now upgrading database...
INFO - Restart requested. Please run the following command to continue your upgrade:
INFO - $ cli-upgrade.php --dir=admin-dev --channel=major --action=upgradeDb [encoded data, 4443 characters]

I checked my shop, upgrade done successfully without any warnings!
THanks!

I was in <IP_ADDRESS> not in <IP_ADDRESS> before upgrade.

@jf-viguier, I tried also with PS<IP_ADDRESS> & the 1-click upgrad 4.8.0 & same result withought any warnings.
php cli-upgrade.php --dir=admin-dev --channel=major
INFO - === Step upgradeNow
INFO - Starting upgrade...
INFO - Shop deactivated. Now downloading... (this can take a while)
INFO - === Step download
INFO - Download complete. Now extracting...
INFO - === Step unzip
INFO - File extraction complete. Removing sample files...
INFO - === Step removeSamples
INFO - All sample files removed. Now backing up files.
INFO - === Step backupFiles
INFO - Backup files in progress. 19189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 18789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 18389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 17989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 17589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 17189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 16789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 16389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 15989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 15589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 15189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 14789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 14389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 13989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 13589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 13189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 12789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 12389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 11989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 11589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 11189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 10789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 10389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 9989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 9589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 9189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 8789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 8389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 7989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 7589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 7189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 6789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 6389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 5989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 5589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 5189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 4789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 4389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 3989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 3589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 3189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 2789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 2389 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 1989 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 1589 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 1189 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 789 files left
INFO - === Step backupFiles
INFO - Backup files in progress. 389 files left
INFO - All files saved. Now backing up database
INFO - === Step backupDb
INFO - 259 tables have been saved.
INFO - Database backup done in filename V<IP_ADDRESS>_20190614-114429-2cf918d. Now upgrading files...
INFO - === Step upgradeFiles
INFO - 20563 files will be upgraded.
INFO - === Step upgradeFiles
INFO - 20163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 19763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 19363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 18963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 18563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 18163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 17763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 17363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 16963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 16563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 16163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 15763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - [TRANSLATION] The translation files have been merged into file /projet/stable1744/modules/ps_themecusto/translations/fr.php.
INFO - 15363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 14963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 14563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 14163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 13763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 13363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 12963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 12563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 12163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 11763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 11363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 10963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 10563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 10163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 9763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 9363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 8963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 8563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 8163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 7763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 7363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 6963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 6563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 6163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 5763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 5363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 4963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 4563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 4163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 3763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 3363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 2963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 2563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 2163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 1763 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 1363 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 963 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 563 files left to upgrade.
INFO - === Step upgradeFiles
INFO - 163 files left to upgrade.
INFO - === Step upgradeFiles
INFO - All files upgraded. Now upgrading database...
INFO - Restart requested. Please run the following command to continue your upgrade:
INFO - $ cli-upgrade.php --dir=admin-dev --channel=major --action=upgradeDb [encoded data, 4431 characters]

After the upfrade I deleted the cache manually.
https://drive.google.com/file/d/1i4qVbeufHFz6hGK9DRFCcEQ5wnbPdo-5/view
Thanks!

OK, your php cli doesn't display warnings.
Look at here:  https://github.com/PrestaShop/autoupgrade/blob/a64e888b5a204610565bd1b55325b0b7655991c7/classes/PrestashopConfiguration.php#L81
There is a file_get_contents on /config/settings.inc.php and this file is no more in 1.7
This has to be fixed.

I've made a PR

Fixed via #322. Release to be published in the next few days.
Thank you @jf-viguier


Update language-go and yaml

PRing because two languages changed.
<EMAIL_ADDRESS>improves the auto-indent patterns and also adds specs for it :green_heart:!
<EMAIL_ADDRESS>adds support for .sls files and properly handles pound (#) symbols in multiline blocks.
Will merge when green.

The only failing spec comes from symbols-view, which is also failing intermittently on master and on the symbols-view repo.