altair: 6.4.0 -> 7.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/imolorhe/altair/releases.
meta.description for altair is: A feature-rich GraphQL Client IDE
meta.homepage for altair is: https://github.com/imolorhe/altair
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.4.2 with grep in /nix/store/9pb8i4fpn6l2ixb7y944gy75xwmm38w9-altair-6.4.2
found 6.4.2 in filename of file in /nix/store/9pb8i4fpn6l2ixb7y944gy75xwmm38w9-altair-6.4.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

altair

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9pb8i4fpn6l2ixb7y944gy75xwmm38w9-altair-6.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A altair https://github.com/r-ryantm/nixpkgs/archive/44907ee10fe7acc89ee7dd4f09c13e0a3d739526.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/44907ee10fe7acc89ee7dd4f09c13e0a3d739526#altair

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9pb8i4fpn6l2ixb7y944gy75xwmm38w9-altair-6.4.2
ls -la /nix/store/9pb8i4fpn6l2ixb7y944gy75xwmm38w9-altair-6.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

altair

Maintainer pings
cc @evalexpr for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/imolorhe/altair/releases.
meta.description for altair is: A feature-rich GraphQL Client IDE
meta.homepage for altair is: https://github.com/imolorhe/altair
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.0.1 with grep in /nix/store/8vppv1r8di7iq0z64fhm1q7h1c90ma7n-altair-7.0.1
found 7.0.1 in filename of file in /nix/store/8vppv1r8di7iq0z64fhm1q7h1c90ma7n-altair-7.0.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

altair

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8vppv1r8di7iq0z64fhm1q7h1c90ma7n-altair-7.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A altair https://github.com/r-ryantm/nixpkgs/archive/07a4cc192379cbf8b545fb7c8597d7110a7844bb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/07a4cc192379cbf8b545fb7c8597d7110a7844bb#altair

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8vppv1r8di7iq0z64fhm1q7h1c90ma7n-altair-7.0.1
ls -la /nix/store/8vppv1r8di7iq0z64fhm1q7h1c90ma7n-altair-7.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

altair

Maintainer pings
cc @evalexpr for testing.


etcdserver: User peerTLSInfo to get cluster member

peerTLSInfo is not used to retrieve cluster members, so boot process fails due to CA verification error: x509: certificate signed by unknown authority.

oops, missing description. updated

This fix is little ugly, just adding argument on required line. I'm new to etcd code, so please suggest me if there's better way

@sorah passing cfg.Transport around is a better solution i think, which has the TLS client config already.
We can just init http.Client from cfg.Transport.(https://github.com/coreos/etcd/pull/2119/files#diff-971f6af906b31cc86efd71aff56aa96bR852)

sorry for late reply; I'll fix the patch later

@sorah We need to fix this issue before 1/27. Can you please update the pull request as @yichengq suggested? Or do you want us to help to fix the problem?

ooh, okay. I've worked on another issue (2123) for few days. I sent patch for that right now, so I start working on updating this PR.

Sorry for late work :no_mouth:

The work is good. Could you address the comment above and squash the commits to one?

lgtm


unable to load plugin libacpp-clang.so  undefined symbol: _ZNK4llvm10ModulePass17createPrinterPass

I encountered a new issue. Could you help take a look?
acpp  -stdlib=libc++ -O3 -c backprop.cpp -o backprop.o
error: unable to load plugin '/home/1/acpp/AdaptiveCpp-develop/build/install/bin/../lib/libacpp-clang.so': '/home/1/acpp/AdaptiveCpp-develop/build/install/bin/../lib/libacpp-clang.so: undefined symbol: _ZNK4llvm10ModulePass17createPrinterPassERNS_11raw_ostreamERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE'

I noticed that someone had a similar issue, so I added -DCMAKE_CXX_FLAGS='-D_GLIBCXX_USE_CXX11_ABI=0' in CMake, but it didn't seem to work. Additionally, due to permission issues, I cannot delete anything from /usr/lib. Do you have any other ideas on how to resolve this problem?
https://github.com/AdaptiveCpp/AdaptiveCpp/issues/985

acpp-core.json
{
  "version-major" : "24",
  "version-minor" : "06",
  "version-patch" : "0",
  "version-suffix" : "",
  "plugin-llvm-version-major" : "17",
  "plugin-with-cpu-acceleration" : "true",
  "default-clang"     : "/home/1/workdev/llvm/install/bin/clang++",
  "default-targets"  : "omp",
  "default-cpu-cxx"   : "/home/1/workdev/llvm/install/bin/clang++",
  "default-rocm-path" : "/opt/rocm",
  "default-use-bootstrap-mode" : "false",
  "default-is-dryrun" : "false",
  "default-use-accelerated-cpu" : "true",
  "default-clang-include-path" : "/home/1/workdev/llvm/install/lib/clang/17/include/..",
  "default-sequential-link-line" : "-L/home/1/boost/boost_1_86_0/stage/lib -lboost_context -lboost_fiber -Wl,-rpath=/home/1/boost/boost_1_86_0/stage/lib",
  "default-sequential-cxx-flags" : "-I/home/1/boost/boost_1_86_0 -D_ENABLE_EXTENDED_ALIGNED_STORAGE",
  "default-omp-link-line" : "-L/home/1/boost/boost_1_86_0/stage/lib -lboost_context -lboost_fiber -Wl,-rpath=/home/1/boost/boost_1_86_0/stage/lib -fopenmp",
  "default-omp-cxx-flags" : "-I/home/1/boost/boost_1_86_0 -fopenmp -D_ENABLE_EXTENDED_ALIGNED_STORAGE",
  "
```default-is-explicit-multipass" : "false",
  "default-save-temps" : "false"
}

build.sh
mkdir build
cd build
INSTALL_PATH=$PWD/install
cmake -DCMAKE_INSTALL_PREFIX=$INSTALL_PATH -DBOOST_ROOT=/home/1/boost/boost_1_86_0 -DCMAKE_C_COMPILER="clang" -DCMAKE_CXX_COMPILER="clang++" -DWITH_ACCELERATED_CPU=ON -DWITH_CUDA_BACKEND=OFF -DWITH_CUDA_NVCXX_ONLY=OFF -DWITH_OPENCL_BACKEND=OFF -DWITH_ROCM_BACKEND=OFF -DWITH_LEVEL_ZERO_BACKEND=OFF -DWITH_SSCP_COMPILER=OFF -DCMAKE_CXX_FLAGS="-D_GLIBCXX_USE_CXX11_ABI=0" -DCLANG_EXECUTABLE_PATH=~/workdev/llvm/install/bin/clang++ -DCMAKE_HAVE_LIBC_PTHREAD=lpthread ..
make install -j64

Could you provide the complete output of the cmake configure step? As @illuhad said here, it could be that the LLVM that CMake finds and the clang executable that you specify don't match.


Trouble compiling from source

Aim
Set up my development environment using these steps:
https://noir-lang.org/getting_started/nargo_installation/#option-4-compile-from-source
Expected Behavior
I was trying to install the native dependencies after running direnv allow
Bug
This is the error that occurred when running direnv allow on my mac with m2 chip

To Reproduce

Machine with M2 chip
https://noir-lang.org/getting_started/nargo_installation/#option-4-compile-from-source

Installation Method
Compiled from source
Nargo Version
No response
Additional Context
Sorry if this is the wrong place for this.
Would you like to submit a PR for this Issue?
No
Support Needs
No response

Hey there! Which repo were you compiling?
If it's just Nargo you could give Option 3 a spin, it's also compiling from source.

Hey @Savio-Sou, Thanks for the reply sorry it took me so long to get back to you. I am trying to compile the noir library so I can start contributing to the library. I didn't think that option 3 would be helpful in this case as I am trying to set up my development environment not just install Nargo.

Also from the current master branch I am getting a similar error that has to do "bad CPU in executable" when I run cd crates/nargo_cli && cargo test

Thanks for the reply @jtfirek!
Which crate(s) were you attempting to compile from source? Let me check if I can reproduce the error on our M2 Mac.

Hey @Savio-Sou thanks for helping me so much with this! Once I get up and going I feel like I can bring a lot of valuable contributions!

With the first error I mentioned, I was setting up my development environment. I was working in the root directory of the projecting running direnv allow so I was not compiling any specific crates.
With the second error I mentioned, I was compiling the nargo_cli crate which actually compiles just fine, it just throws an error when I try to run the tests. I have done some more digging and I am pretty sure that the test is failing because I don't have the dev environment set up so their is no baretenberg backend.

error: Failed to download srs: Unable to open file: /Users/jacobfirek/.nargo/backends/acvm-backend-barretenberg/g1.dat


Replace _mm_movemask_pi8 with the fallback_impl

_mm_movemask_pi8 got removed from stdarch and there is no real alternative (_mm_movemask_epi8 that was suggested here doesn't take a 64bit wide vector but a 128bit vector instead) .
Resolves #288

I just noticed that it will take some more time to fix all mmx occurrences :sweat_smile:

This appears to build now! Excellent, thank you.

Still doesn't build:
error[E0432]: unresolved import `crate::arch::x86_64::_mm_shuffle_pi8`
   --> /home/travis/build/rust-lang/packed_simd/src/codegen/shuffle1_dyn.rs:40:29
    |
40  |                         use crate::arch::x86_64::_mm_shuffle_pi8;
    |                             ^^^^^^^^^^^^^^^^^^^^^---------------
    |                             |                    |
    |                             |                    help: a similar name exists in the module: `_mm_shuffle_epi8`
    |                             no `_mm_shuffle_pi8` in `arch::x86_64`
...
297 | impl_shuffle1_dyn!(u8x8);
    | ------------------------- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

Fixing that in #292! I think I meant "with two more modifications" at the time but I had just begun the process of hammering away at a million lints.


Webchat connection gets stuck when iOS App container comes back from background

Is it an issue related to Adaptive Cards?
No
Is this an accessibility issue?
No
What version of Web Chat are you using?
Latest production
Which distribution are you using Web Chat from?
NPM
Which hosting environment does this issue primarily affect?
Web apps
Which browsers and platforms do the issue happened?
Platform: iOS/iPadOS
Which area does this issue affect?
Protocol or service
What is the public URL for the website?
No response
Please describe the bug
Webchat is connected through ASEDL to a custom bot, Websocket in the mix. Hosting is done on iOS WKWebKit.
App is running the webchat, app gets put on background, you start camera (or anything), 30 seconds later you go back to the app, connection will not be established. Send button is disabled
When webchat gets into foreground again, there'll be two new logs:

WEB_CHAT/SET_NOTIFICATION (reconnecting)
DIRECT_LINE/UPDATE_CONNECTION_STATUS

Connection status will be stucked at 1, connecting.
We logged Webbrowser WebSocket too:

before leaving the window we would have 1 websocket in a readyState = 1 (OPEN) state

returning back we see two websockets: 1) in readyState = 1 (OPEN) state, 2) in readyState = 3 (CLOSED) state

CC: @miketrexler
Do you see any errors in console log?
No response
How to reproduce the issue?

App is running the webchat,
App gets put on background,
Start camera (or anything), 30 seconds later you go back to the app, connection will not be established. Send button is disabled
Click on ...
Type "..." in the send box

What do you expect?
Connection is re-established, conversation can be continued, send message is enabled
What actually happened?
Connection is not being re-established, send button is disabled, user is presented with warning around inability to connection (couple of different messages, second after 2 minutes from the first warning)
Do you have any screenshots or recordings to repro the issue?
Yes, can provide privately
Adaptive Card JSON
No response
Additional context
No response

@alexinuk - Thank you for your patience. First, please understand that both WKWebView, Swift, and iOS app development are areas I am not versed in. So, I will be relying on your responses and knowledge to fill in the gaps.
I'm wondering if this is a bit of context issue, so to speak. It seems to me that the app's connection is breaking when it moves from the primary app to a background running app. In other words, some of the resources devoted to it when it was in the foreground are being closed/terminated/paused. I know iOS apps can be toggled in the phone settings to either allow or disallow being able to run in the background. Have you explored enabling this on your app and seeing if that fixes the issue?
Without the feature enabled, it may be that the app is simply re-establishing the DirectLine connection (providing the token hasn't expired) when it moves to the foreground. But, because the connection was interrupted, so was the dependent Web Chat component.
Allowing the app to run in the background may preserve the DirectLine connection and Web Chat component, including the send box / button. If allowing the app to run in the background doesn't work but you are able to verify the DirectLine object is still valid when the app is brought back to the foreground, then purposefully reloading the Web Chat component (i.e., re-calling renderWebChat()) on "app has focus" or something similar may be enough to fix the issue.
Keep in mind, this is a bit of theory. While I own an iPhone, I'm not an iOS developer and am only speculating about the flow of processes.

thanks stevkan, I'd suggest you reach @compulim to know the latest and greatest on this original issue. Please mark and link all the relevant fixes part of this journey. Thanks


Blue LEDs stopped indicating actual battery charge

After several months away from the UPSplus and the Pi attached to it, a few days ago I did a f/w upgrade. The info on the Github pages about the current f/w version seems no longer there, so I didn't know what to expect. The UPS upgraded from f/w version 10 to 14. Great (expectations ...)! So far so good. However, no info about changes, bugs corrected or improvements to be found.
What I noticed myself is that now the blue LEDs behave erratically. Only the first two are lit. Number 2 is blinking.
The UPS has been on its charger all the time since the upgrade and the batteries are fully charged as per the UPS registers and a digital voltmeter connected to the battery terminals. It's just the LEDs not reflecting the situation correctly.
I recall having read a comment about the LEDs misbehaving, but I cannot find it now.
Is there a way to make the LEDs behave again as they used to do, in a sensible way?

same here, for several months now. currently, all blue LEDs are off.

When I returned to my cottage where the UPS Plus was in use, I decommisioned the UPS Plus despite all the effort I have put in it over the last year. I had lost control of it months before that when I was away.
Years ago when I had just started with Raspberry PI's I bought a PiJuice UPS which I tested and discussed about with responsive developers and voluntaries at the time, then in following years more or less forgot about.
Compared to the several other brand Pi UPS's I have, the Pi Juice proved the easiest and best supported.
I totally reinstalled the Pi that had the UPS Plus. That removed also the last trace of HA, which had proved a nuisance and difficult to uninstall. It kept looking up some domain address.
The PiJuice doesn't have the extra cooling from the Ice Tower, but it hasn't been a problem.
At least I can stop worrying about the UPS Plus and it's Lithium cells.

I've written off the UPS Plus for some time now, and have a couple of Red Reactors obtained via Kickstarter that I'll be trying next.
It's a shame, but I concluded some time ago that the serious battery drain issue is a show-stopper with no workaround. Never mind other ongoing questions regarding support and engineering.
Good luck on your search.

When the battery is not used for a long time, its internal resistance will also consume battery power. Additionally, due to chip limitations, the UPS cannot completely cut off power. Therefore, please remove the battery when the UPS is not in use for an extended period of time.


Updating the Unity Snowplow Tracker to handle Android & IOS Devices

-Updating the unity engine and Mono.Data.SqliteClient dll's to Unity 2018.3.6f1
-Adding sqlite native files needed for Android devices
-Allowing the user to define the database's and session location within a device

@mhadam This is the update I was discussing referecing: https://github.com/snowplow/snowplow-unity-tracker/pull/8

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://github.com/snowplow/snowplow/wiki/CLA to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://github.com/snowplow/snowplow/wiki/CLA to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

I have signed the agreement.

@mhadam @BenFradet  giving this a bump :)

thanks! will handle this now

Confirmed! @kmoorestevenson  has signed the Individual Contributor License Agreement. Thanks so much


Draw images in bar chart columns

It would be great if we could render images on the top / inside the stats in a bar graph. So that we can have some picture for each stat. In my case, it would mean that the link between the graphs and other information is far more clear.

@ChrisCooney do you mean inside the bars? if so, you can do this 😄
Instead of specify a colour for the bar, you can specify a CanvasPattern object.
What you would need to do is

Render the image onto another offscreen canvas
Use that canvas' rendering context to create the canvas pattern.
You can then pass that pattern as the backgroundColor for the dataset.

An example of doing something similar but with gradients instead of patterns is https://github.com/bbc/Chart.Bands.js
If you want to render elsewhere on the chart, your best bet is to write a plugin that hooks into afterDraw and does some custom drawing of images as necessary.

Closing as answered

Apologies for not getting back to you. This is a really cool way around it! Thankyou.

@etimberg thank you a lot, I have finished draw the image into specific point that I wanted but I got a little problem, whenever I got a hover through any point which will display tooltip, it seems to redraw the image, there is any way to prevent it?
afterDatasetDraw: (chart, options) => {
          const actualIcon = new Image();
          actualIcon.src = self.actualIconPath;
          const meta = chart.getDatasetMeta(0);
          const actualX = meta.data[0]._model.x;
          const actualY = meta.data[0]._model.y;
          actualIcon.onload = () => {
            chart.ctx.drawImage(actualIcon, actualX, actualY);
          }
}

I already tried with several plugin options but nothing worked

@tuongthovo did you solve that?


DEBUG messages for imprint polluting log

Is there a way to disable log messages for missing imprint data when ACDH_IMPRINT_URL/REDMINE_ID don't exist yet and logging hasn't yet been configured for local development, either?
They are kind of annoying during project setup:
MY_DATETIME urllib3.connectionpool DEBUG    Starting new HTTPS connection (1): imprint.acdh.oeaw.ac.at:443
MY_DATETIME urllib3.connectionpool DEBUG    https://imprint.acdh.oeaw.ac.at:443 "GET / HTTP/11" 200 2

I guess the idea is to remind people to set REDMINE_ID for live sites, but for projects which aren't deployed yet, for which there isn't even a Redmine ticket yet, that's not relevant.
Isn't the REDMINE_ID a required setting for deployments to work in the first place? Though I might be confusing this with something else (frontend deployments, possibly).
Idk if this check could e.g. be disabled if DEBUG = True or if this would defeat the purpose of the check in the first place.

Is there a way to disable log messages for missing imprint data when ACDH_IMPRINT_URL/REDMINE_ID don't exist yet and logging hasn't yet been configured for local development, either?

There are no log messages for missing imprint data. The log messages you are quoting come from urllib3, whenever a request is made.


[$1000] Web - Reply in thread - The parent message does not appear immediately

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:

Go to URL https://staging.new.expensify.com/

Login with any account

Go to any chat

Send a message

Click on the message for opening the additional menu -> Reply in thread

Expected Result:
The main message appears immediately
Actual Result:
The main message is NOT appearing immediately
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?

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

Version Number: v1.3.23-6
Reproducible in staging?: y
Reproducible in production?: y
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://github.com/Expensify/App/assets/43996225/f7924d66-c575-42d6-ba75-3eba1cf0d435
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01971bf51adfe1fc4c
Upwork Job ID:<PHONE_NUMBER>809968640
Last Price Increase: 2023-06-12

I was able to repro this on MacOS/Chrome

I think it's already being handled here https://github.com/Expensify/App/issues/19490
cc: @s77rt

https://github.com/Expensify/App/pull/19580 has been merged. Is this still reproducible?

Yeah, I am still able to repro it on both Chrome and Safari. When you click Reply in thread, there is still ~3-4 second delay before the message appears

Ah I see, I think this is a different issue then as the skeleton loader is not seen either

@stephanieelliott I don't see this issue now. Could you kindly check and close if the issue is fixed?

@stephanieelliott Could you check on this? https://github.com/Expensify/App/issues/20120#issuecomment-1584567362

Unable to reproduce, will go ahead and close!


Melee weapons should pierce armor but only for other marines

Only marine armor should be pierced, xeno armor isn't
Cm13

dupe


Draggable transformation interface not cross-browser compatible

Thanks to @babihammond for pointing out that the draggable transformations interface does not work in Firefox on Mac (confirmed).  Draggable boxes are treated as links.  Possible to drag, but must grab outside of text/link area.  However, if clicked, will start Job immediately, and likely error out.
Same is true for Safari as well.  Though moredraggable, still functions as link if clicked.

Screenshot in Firefox:

Fixed.


Persisting connection on page refresh

Hey Guys! It's me again, I need a quick help on this:
I want the metamask login to persist even when the page refreshes. Unfortunately with useDapp the user needs to click "connect" every time there is a change of page...
The UX of having persistent login is very important, so far I have only seen it implemented here: https://github.com/mirshko/next-web3-boilerplate
Whenever I refresh the page I am still connected with metamask and react renders a "hello 0x1A2B3..." instead of "Connect"
Is this something that can be achieved with useDapp too? Any suggestions on this topic?
Hope I'm not too annoying, I'm just looking to make the perfect login experience for my dApps. Thanks for your time :)

I see somebody mentioning this topic in another repo, maybe it helps: https://github.com/MetaMask/metamask-extension/issues/7030

@bitfede Ive been using something like this to load the injected wallet on refresh
  const { activate } = useEthers();

  useEffect(() => {
    injected.isAuthorized().then((isAuthorized) => {
      if (isAuthorized) {
        activate(injected);
      }
    });
  }, [activate]);

oh wow looks like a smart solution, where is injected defined exactly?

import { InjectedConnector } from "@web3-react/injected-connector";

const injected = new InjectedConnector({ supportedChainIds: [1, 4, 1337] });

Oh that's true, should have googled it, also found a similar example here https://github.com/NoahZinsmeister/web3-react/blob/v6/example/connectors.ts
Aaand just tested it! It works beautifully!!! :D
Thank you for taking the time to explain, really appreciate it. Just checked out your repos they look badass keep up the good work 💪


installation returns "Failed to request cluster info" on the preflight checks stage

Sending build context to Docker daemon 266.4 MB
Step 1 : FROM mirantis/hypokube:baseon 240.1 MB
 ---> c8b0b66668a6
Step 2 : COPY hyperkube /hyperkube
Sending build context to Docker daemon 266.4 MB
Step 1 : FROM mirantis/hypokube:base
 ---> c8b0b66668a6
Step 2 : COPY hyperkube /hyperkube
 ---> e282c0cafdf0
Removing intermediate container 9087df023639
Successfully built e282c0cafdf0
 ---> 2bb4c5d3ae23
Removing intermediate container 1d3b6a608110
Successfully built 2bb4c5d3ae23
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /lib/systemd/system/kubelet.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /lib/systemd/system/kubelet.service.
Flag --skip-preflight-checks has been deprecated, it is now equivalent to --ignore-preflight-errors=all
Flag --skip-preflight-checks has been deprecated, it is now equivalent to --ignore-preflight-errors=all
[preflight] Running pre-flight checks.
[preflight] Running pre-flight checks.
        [WARNING FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
        [WARNING FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
        [WARNING FileExisting-crictl]: crictl not found in system path
Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl
        [WARNING FileExisting-crictl]: crictl not found in system path
Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl
[discovery] Trying to connect to API Server "<IP_ADDRESS>:6443"
[discovery] Trying to connect to API Server "<IP_ADDRESS>:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://<IP_ADDRESS>:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://<IP_ADDRESS>:6443"
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: unexpected EOF]
[discovery] Failed to request cluster info, will try again: [the server was unable to return a response in the time allotted, but may still be processing the request (get configmaps cluster-info)]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [the server was unable to return a response in the time allotted, but may still be processing the request (get configmaps cluster-info)]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: net/http: TLS handshake timeout]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kube-public"]

@snedi Are you passing a custom number of nodes using NUM_NODES=? Thanks

@imriss actually I increased memory on my VM and this issue disappeared. As for the question no I didn't pass the number of nodes.

@snedi thanks. It could also happen if an odd number is passed via NUM_NODES.

@imriss you mean it's reproducible with an odd number of nodes?

@ivan4th yes, it was like that a few days before when I was using NUM_NODES=3. There issue disappeared when I let the default value be used. However, I cannot reproduce it anymore today.

I am usually using k-d-c with 3 nodes and never had such problem. So not sure if it’s because of odd node number.

Closing for now. Please let me know if you can reproduce it again.

I am facing the same issue while trying to perform join .
NOTE : I am using latest kubeadm version with cri-o ( though this isn't a problem with cri-o )
kubectl get nodes
NAME                    STATUS   ROLES    AGE   VERSION
uls-od-sdfkm1.xxx.com   Ready    master   86m   v1.13.3
uls-od-sdfkm2.xxx.com   Ready    master   86m   v1.13.3
uls-od-sdfkm3.xxx.com   Ready    master   86m   v1.13.3

Join config
---
apiVersion: kubeadm.k8s.io/v1beta1
caCertPath: /etc/kubernetes/pki/ca.crt
discovery:
  bootstrapToken:
    apiServerEndpoint: kube-apiserver:6443
    token: abcdef.0123456789abcdef
    unsafeSkipCAVerification: true
  timeout: 5m0s
  tlsBootstrapToken: abcdef.0123456789abcdef
kind: JoinConfiguration
nodeRegistration:
  criSocket: {{ '/var/run/crio/crio.sock' if kubernetes_socket_type=='crio' else '/var/run/dockershim.sock' }}
  name: {{ inventory_hostname }}

kubeadm join --token wiy3qu.ns79yu31jtc0wf7o kube-dev.xxx.com:6443 --discovery-token-unsafe-skip-ca-verification --cri-socket /var/run/crio/crio.sock -v 2
I0320 00:48:09.589483   27003 join.go:299] [join] found NodeName empty; using OS hostname as NodeName
[preflight] Running pre-flight checks
I0320 00:48:09.589568   27003 join.go:328] [preflight] Running general checks
I0320 00:48:09.589615   27003 checks.go:245] validating the existence and emptiness of directory /etc/kubernetes/manifests
I0320 00:48:09.589624   27003 checks.go:283] validating the existence of file /etc/kubernetes/kubelet.conf
I0320 00:48:09.589629   27003 checks.go:283] validating the existence of file /etc/kubernetes/bootstrap-kubelet.conf
I0320 00:48:09.589635   27003 checks.go:104] validating the container runtime
I0320 00:48:09.599115   27003 checks.go:373] validating the presence of executable crictl
I0320 00:48:09.599143   27003 checks.go:332] validating the contents of file /proc/sys/net/bridge/bridge-nf-call-iptables
I0320 00:48:09.599173   27003 checks.go:332] validating the contents of file /proc/sys/net/ipv4/ip_forward
I0320 00:48:09.599196   27003 checks.go:644] validating whether swap is enabled or not
I0320 00:48:09.599215   27003 checks.go:373] validating the presence of executable ip
I0320 00:48:09.599226   27003 checks.go:373] validating the presence of executable iptables
I0320 00:48:09.599238   27003 checks.go:373] validating the presence of executable mount
I0320 00:48:09.599249   27003 checks.go:373] validating the presence of executable nsenter
I0320 00:48:09.599260   27003 checks.go:373] validating the presence of executable ebtables
I0320 00:48:09.599270   27003 checks.go:373] validating the presence of executable ethtool
I0320 00:48:09.599280   27003 checks.go:373] validating the presence of executable socat
I0320 00:48:09.599290   27003 checks.go:373] validating the presence of executable tc
I0320 00:48:09.599300   27003 checks.go:373] validating the presence of executable touch
I0320 00:48:09.599313   27003 checks.go:515] running all checks
I0320 00:48:09.604960   27003 checks.go:403] checking whether the given node name is reachable using net.LookupHost
I0320 00:48:09.605094   27003 checks.go:613] validating kubelet version
I0320 00:48:09.643927   27003 checks.go:130] validating if the service is enabled and active
I0320 00:48:09.649442   27003 checks.go:208] validating availability of port 10250
I0320 00:48:09.649526   27003 checks.go:283] validating the existence of file /etc/kubernetes/pki/ca.crt
I0320 00:48:09.649535   27003 checks.go:430] validating if the connectivity type is via proxy or direct
I0320 00:48:09.649565   27003 join.go:334] [preflight] Fetching init configuration
I0320 00:48:09.649573   27003 join.go:601] [join] Discovering cluster-info
[discovery] Trying to connect to API Server "kube-dev.xxx.com:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://kube-dev.xxx.com:6443"
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "kube-public"]
[discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "kube-public"]


upgrade exp cli, use run-with-settings for ALL THE THINGS

EXPO builds on travis started failing, time to update the exp cli again.
Also, noticed storybook build failed on latest master. Probably due to #300, and adding run-with-settings to both storybook-build and test-runner, so they get the env vars set for them.
Creator

[ ] Build relevant tests if any apply
[ ] Ensure there are no new warnings
[ ] Upload an animated GIF showcasing the solution (if it applies)
[ ] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

@conrad-vanl Done!


DF-1438 Fixed featured topic links

Fixed featured topic links
Additions

None

Removals

None

Changes

Added jump-link with the __right modifier

Testing
Fork and navigate to /newsroom at a smaller browser size
Review

@duelj
@sebworks
@anselmbradford

Preview

Notes

links were missing jump-link and right styles

:+1:


Updated keycloak to use Graal JDK8  and use the linux os images from container registry

Verified locally that the server came up,and the JDK used within the container was Graal JDK.

Looks good to me.


There is a format error in the data, and an error may be reported when parsing json. In addition, it is strongly recommended to clean the data to provide users with higher quality evaluation data.

https://github.com/ruixiangcui/AGIEval/blob/main/data/v1/gaokao-chemistry.jsonl#L75
{"passage": null, "question": "水溶液呈酸性的是( $)$", "options": ["(A)$\\mathrm{NaCl}$", "(B)$\\mathrm{NaHSO}_{4}$", "(C)HCOONa", "(D)$\mathrm{NaHCO}_{3}"], "label": "B", "answer": null, "other": {"source": "2020年浙江省高考化学【7月】"}}
Option D is missing a backslash \

Hi @FrankMinions, we have re-annotated all gaokao chemistry, biology and physics datasets and added questions from 2023. You can download them on the GitHub page already. Thank you very much again for your usage and support for open-source research!


GOV.UK: Search API

Base URL:
https://www.gov.uk/api/search.json
Documentation URL:
https://docs.publishing.service.gov.uk/apis/search/search-api.html
Description:
GOV.UK Search API allows you to find content on GOV.UK.  It's the same API that powers https://gov.uk/search/all and the other dynamic content pages on GOV.UK

It'd be great to add third-party uses. I'll chat to DWP.


How to avoid multiple state rows and leases for the same table, same function?

We have 4 functions in total, one per table, and are currently in the development DB, playing with code, running and stopping the functions app, making changes, and we noticed multiple state rows and lease tables being created for the same table and the same function, up to 6 for a single table, see below.

What is causing this behavior?
Will these state rows and lease tables be automatically cleaned up?
How do we avoid this behavior?

Initial answer to your questions:

There should be a single leases table made for each instance of the function and the table it's monitoring. The format of the table name is az_func.Leases_<FunctionId>_<TableID>

See https://github.com/Azure/azure-functions-sql-extension/blob/main/docs/BindingsOverview.md#az_funcleases_more more details about that
So if the function ID or table ID changes then a new leases table will be generated. Are you changing the name of the function with the trigger on it? As long as or the function assembly name doesn't change it should be using the same ID

Not currently, we have an issue tracking figuring this out though so it's something on our radar https://github.com/Azure/azure-functions-sql-extension/issues/681

As long as the table ID & function info (assembly + name) doesn't change then it shouldn't be doing this. Once we get more information we can determine if this is expected behavior and figure out a solution from there.

@Charles-Gagnon We have changed the function names at least once. That being the cause makes sense looking at the LastSyncVersion numbers (4 with relatively high numbers, the rest much lower).  If that is the cause of the additional tables being created, are we good to drop the lease tables showing old version numbers? Is there a way to verify the function ID to ensure we don't remove the wrong tables?

Yup, you're good to drop the old tables. And you can look at the function logs to see the current leases table being used then delete the rest - unfortunately there isn't an easier way since reverse engineering the ID generation isn't straightforward.
Code in case you're interested : https://github.com/Azure/azure-functions-sql-extension/blob/main/src/TriggerBinding/SqlTriggerBinding.cs#L98

@Charles-Gagnon Understood. Thank you!


Not really actuall ;)

I visited the site for the first time, but FF44 is not the actuall. I use 45.0.1 :)
But its a great project, so keep up the great work!

1

@nerdcoat  Thank you :+1:
You right we are a little behind, sometimes is hard to keep track in all the new updates and stats. Cheers :)


markdown not rendered correctly

Follow-up on #3442.
I have a number of packages on pypi, the README.md of some of which is rendered correctly (e.g., https://pypi.org/project/fastfunc/), and not for others (e.g., https://pypi.org/project/blacktex/). There is no indication of what's wrong so I don't know how to fix it.
Any hints?

In the PyPI metadata, I see that release 0.1.7 of fastfunc has the metadata Description-Content-Type: text/markdown, but release 0.1.2 of blacktex has a blank Description-Content-Type. A blank value for that field means to treat it as ReST.
The METADATA record in the wheel for blacktex-0.1.2 appears to have a correct value for that field:
   1   │ Metadata-Version: 2.0
   2   │ Name: blacktex
   3   │ Version: 0.1.2
   4   │ Summary: Cleans up your LaTeX files
   5   │ Home-page: https://github.com/nschloe/blacktex
   6   │ Author: Nico Schlömer
   7   │ Author-email<EMAIL_ADDRESS>   8   │ License: License :: OSI Approved :: MIT License
   9   │ Platform: UNKNOWN
  10   │ Classifier: License :: OSI Approved :: MIT License
  11   │ Classifier: Development Status :: 3 - Alpha
  12   │ Classifier: Operating System :: OS Independent
  13   │ Classifier: Programming Language :: Python
  14   │ Classifier: Programming Language :: Python :: 2
  15   │ Classifier: Programming Language :: Python :: 3
  16   │ Classifier: Topic :: Text Editors :: Text Processing
  17   │ Classifier: Topic :: Text Processing
  18   │ Classifier: Topic :: Text Processing :: Markup
  19   │ Classifier: Topic :: Text Processing :: Markup :: LaTeX
  20   │ Classifier: Topic :: Utilities
  21   │ Description-Content-Type: text/markdown
  22   │ Requires-Dist: pipdate (<0.4.0,>=0.3.0)
  23   │
  24   │ # blacktex
  25   │
  26   │ Cleans up your LaTeX files.
  27   │

However, note that it specifies a version of 2.0. Description-Content-Type was only added in version 2.1.  (fastfunc only has a sdist, and the sdist's PKG-INFO uses metadata 2.1; likewise the sdist for blacktex also uses metadata 2.1, but it was uploaded after the wheel, and the metadata for display comes from the first uploaded artifact.) Did you perhaps use a version of setuptools prior to 38.6.0 to build the wheel artifact for blacktex?

Thanks for the concise feedback!
I have no idea how Metadata Version 2.0 came about. Locally it's 2.1, and I'm using the toolchain in fairly up-to-date versions (setuptools 40.8.0). Will try another upload momentarily.

Okay, I'm generating tar.gz and the wheel via
python3 setup.py sdist
python3 setup.py bdist_wheel --universal

This is with Python 3.7.2+ and setuptools 40.8.0. When unzipping the wheel, I see that METADATA says
Metadata-Version: 2.0

How can I further debug this?

Okay, got it: I had an older version of wheel installed (0.30.0). Updated, issue now fixed. Thanks for the help!


Removed "black magic" check only from Islam site.

Warning: Untested!  (How do we test filters without making bad posts, other than the !!/test command?)
"Black magic" was causing too many false positives.
Removed it from the Islam site only.
See:

Starting here, on Tavern
and
Here, on Charcoal HQ

How do we test filters without making bad posts

That's what https://github.com/Charcoal-SE/SmokeDetector/blob/master/test/test_regexes.py is for :)

Thanks, @Undo1.  I don't see an existing check for "black magic" though.?

@Manishearth, fixed the logic issue, I think, and the CI checks pass.

Thanks @Manishearth!


Release cosmos db microsoft.document db 2022 11 15

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Hi @rkmanda, we are also seeing a few errors related to previous api versions that are not easily addressable with this one. Could we get an exception for those?
For example:
Expected type object but found type string
Url: Microsoft.DocumentDB/stable/2022-11-15/services.json#L293:31
ExampleUrl: stable/2022-11-15/examples/CosmosDBServicesList.json#L22:46

"ClientEncryptionKeyGetProperties": {

PUT and GET response payloads need to have the same structure. Both of them MUST not have security sensitive data like the actual encryption keys
Refers to: specification/cosmos-db/resource-manager/Microsoft.DocumentDB/stable/2022-11-15/cosmos-db.json:5634 in a5f919a. [](commit_id = a5f919a, deletion_comment = False)

@kr-santosh

"ClientEncryptionKeyGetProperties": {

PUT and GET response payloads need to have the same structure. Both of them MUST not have security sensitive data like the actual encryption keys
Refers to: specification/cosmos-db/resource-manager/Microsoft.DocumentDB/stable/2022-11-15/cosmos-db.json:5634 in a5f919a. [](commit_id = a5f919a, deletion_comment = False)

Hi @rkmanda  all of these payloads have encryption keys in Wrapped Format. They are generated at the client and encrypted and then stored in CosmosDB backend as Database resource. We have already released the Public preview and now porting the Spec to Stable version

    "algorithm": {

enum?
Refers to: specification/cosmos-db/resource-manager/Microsoft.DocumentDB/stable/2022-11-15/cosmos-db.json:7494 in a5f919a. [](commit_id = a5f919a, deletion_comment = False)

These are managed as Strings in the Core .NET SDK hence retaining the same here  also.

ClientEncryptionKeyCreateUpdateParameters

Following the structure as any other DatabaseResource we have in CosmosDB.

ClientEncryptionKeyCreateUpdateParameters

I did not understand. I dont see it under proxy

"ClientEncryptionKeyGetProperties": {

PUT and GET response payloads need to have the same structure. Both of them MUST not have security sensitive data like the actual encryption keys
Refers to: specification/cosmos-db/resource-manager/Microsoft.DocumentDB/stable/2022-11-15/cosmos-db.json:5634 in a5f919a. [](commit_id = a5f919a, deletion_comment = False)

@kr-santosh

I have responded.

ClientEncryptionKeyGetProperties

They refer to ClientEncryptionKeyResource. As mentioned earlier they all have encryption keys in wrapped/encrypted form. They are encrypted/decrypted on the client.

get

The request is sent via client to retrieve the encrypted keys from the backend to be used post decryption on the client side. No sensitive data is exposed.

@weidongxu-microsoft Regarding the Avocado check, we haven't made any changes to the 2016 API version that the check is failing on. Could you take a look at it?

@weidongxu-microsoft Also the lintdiff errors are not for the changes that were made in this PR. They point to code that was carried forward from previous API version. These errors were not triggered before when these API versions were merged. Could you take a look at them as well?

@pjohari-ms Regardless of whether it is caused by your change or not, all of them is required to be fix or at least suppressed.

@pjohari-ms Regardless of whether it is caused by your change or not, all of them is required to be fix or at least suppressed.
Some of them are new rules that wasn't there on previous commit to the spec.

We are still having issues with the Avocado check, though. Not sure why this error (MISSING_APIS_IN_DEFAULT_TAG) is popping up here. It seems like an outdated rule.

/azp run

We are still having issues with the Avocado check, though. Not sure why this error (MISSING_APIS_IN_DEFAULT_TAG) is popping up here. It seems like an outdated rule.

It seems to say some API in Microsoft.DocumentDB/stable/2016-03-31/cosmos-db.json does not exist in your latest cosmos-db.json
Is these API get deleted?
If not, maybe it is a bug in tooling.

@weidongxu-microsoft The API isn't deleted, it's just a very old API. We have also got an exception during our last API version release for Avocado, and were told that this won't happen for future PRs. Seems like we need to get an exception again for this PR?

OK, you can follow this to get it suppressed https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/ci-fix.md#suppression-process
Note you've got a new LintDiff error

@ruowan We requested avocado approval in this PR: https://github.com/Azure/azure-rest-api-specs/pull/20419 . This current PR is also failing the avocado check (for an older API version) and I have requested a suppression for it. Could you please provide an approval for avocado in the meantime?

@weidongxu-microsoft @ruowan anything on the Avocado exception? I have already requested a suppression but there doesn't seem to be any progress on that. Can you approve the avocado exception for this PR for now?

You've not get ARM approval yet. Why worry about Avocado now.

@rkmanda We have added the response to your comments. Could you take a look?

We still see some open comments. Please address on how you are planning to handle them.

We still see some open comments. Please address on how you are planning to handle them.
Please let us know if there are any more comments remaining for this PR

@weidongxu-microsoft @ruowan We have an ARM signoff now. Can you approve the avocado exception for this PR for now?

@weidongxu-microsoft since you're the PR assignee as well, do we need anything else before we can merge this PR? If not, can you please merge this PR as well?


AdvancedGear-CDDA-Mod-master function and name error

Name the mod
put mod name here
AdvancedGear-CDDA-Mod-master
Describe the bug
A clear and concise description of what the bug is.
When loading a world I get these errors:
 DEBUG    : Received unrecognized iuse function picklock, using iuse::none instead

 FUNCTION : use_function Item_factory::usage_from_string(const string&) const
 FILE     : src/item_factory.cpp
 LINE     : 3323

 DEBUG    : Error: data/mods//AdvancedGear-CDDA-Mod-master/items/production/nanofactory.json: line 95:13: expecting string but got '{'

    "type": "ammunition_type",
    "id": "3d_resin",
    "name": {
            ^
              "str": "3D printer stock" },
    "default": "3d_resin"
  },

 FUNCTION : bool main_menu::new_character_tab()
 FILE     : src/main_menu.cpp
 LINE     : 874

Solution
how to fix
The first one, where it says function lockpick, is used in:
\data\mods\AdvancedGear-CDDA-Mod-master\items\gear\multitool.json
On line 37:
   { "type": "picklock", "pick_quality": 50 },
You can probably just put [ "LOCKPICK", 3 ] under "qualities" and remove the line     { "type": "picklock", "pick_quality": 50 },
The second one, where it says expecting string but got '{'
The name should be a string, so change
 "name": { "str": "3D printer stock" },
to
`"name": "3D printer stock",`

Are you using the latest version of the modpack?  Here is what the code looks like on my end:
  {
    "type": "ammunition_type",
    "id": "3d_resin",
    "name": "3D printer stock",
    "default": "3d_resin"
  },

I downloaded the 0.9 release and the name issue is gone. I still have the lockpick issue though

no idea right now how to fix that but ill look into it

Oh, right the numbers are different. 50 can probably stay 50.

i have exposed other errors and lack of code to this mod


use helm norms for ns & crd

Addresses #122

Why is this even required ? Should it not just install into .Release.Namespace?

This change looks good to me. The previous logic looks broken. defining a macro over a variable has undefined behavior?

Thanks !
that already fixed on @prudhvigodithi pr (https://github.com/Opster/opensearch-k8s-operator/pull/148)


Typo in the Create VM in availability zone tutorial

[Enter feedback here]
The code sample
osdiskname=$(az vm show -g myResourceGroupVM -n myVM --query "storageProfile.osDisk.name" -o tsv)
should be
$osdiskname=$(az vm show -g myResourceGroupVM -n myVM --query "storageProfile.osDisk.name" -o tsv)

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

ID: 78c432aa-bea5-e8a6-6987-cdb26e71708e
Version Independent ID: d0080131-d6d4-869d-c141-0ee46811ed56
Content: Create a zoned VM with the Azure CLI - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/create-cli-availability-zone.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

As described in the example in the document here : https://docs.microsoft.com/en-us/cli/azure/azure-cli-variables#use-shell-variables , this is correct syntax for getting a value for a variable based on an existing virtual machine
osType=$(az vm get-instance-view --resource-group $MyResourceGroup
--name $vmName --subscription "$MySubscription"
--query 'storageProfile.osDisk.osType' --output tsv)
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Batch delete on query produced with Select statement

Hi,
I am trying to do the following actions:
parentsToRemove = context.Parents.Where(whereExpression)
childrenToRemove = parentsToRemove.Select(p => p.Child)
childrenToRemove.DeleteAsync() <- throws error saying "Invalid column name 'Id'."
parentsToRemove.DeleteAsync()
I was wondering if DeleteAsync is supposed to work with table joins such as this? I have verified that parentsToRemove.DeleteAsync() will run successfully. Also, in this particular situation, cascade-deleting is not possible, which is why i am trying to delete in this fashion.

Hello @TannerStevenson ,
Do you think you could provide us a test project with this issue?
It will make easier/faster for my developer to getting started for investigating it.
We now always ask for a project since we found out that most issues are missing some essential information or are resolved by the requestor when creating it
(Even if the issue seem very easy to reproduce, by getting a test project, it allow us to give a faster support and better experience for the support of all our free libraries)
Best Regards,
Jonathan

Performance
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Bulk Operations •  Dapper Plus •  LinqToSql Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Hi Jonathan,
Does your response mean that your bulk delete methods should work after a Select statement? It might be a little while before I have time to make a sample app to reproduce this.

Hello @TannerStevenson ,
I might be wrong but I have seen some pretty weird scenario with Batch Delete ;)
It might works, this kind of error with Invalid column name 'Id'." often happen people Entity Framework` generate the SQL using some alias that we do not support yet.
As said, that will be easier on our side to check it if we have a test project that reproduce this error.
Best Regards,
Jonathan

Hello @TannerStevenson ,
This issue will be closed since we haven't heard back from you.
Feel free to reopen it if you can provide the information we asked.
Best Regards,
Jonathan