daemon: Change loglevel of "ipcache entry owned by kvstore or agent"

This commit changes the loglevel of the following log entry to debug:
level=warning msg="Unable to update ipcache entry of Kubernetes node" error="ipcache entry owned by kvstore or agent"

This message is harmless, as after cilium-agent has established connectivity to a kvstore, it's expected that ipcache entries will be owned by kvstore.
Also, quite a few users tripped over this warming thinking that it might be serious.

This change is

Coverage increased (+0.02%) to 44.66% when pulling 3259535ef71d3abbe3a5a9130ab961f3449a48ee on pr/brb/mute-warning-ipcache-owned into fbc9ba004c022f8abcdb040e2689cf6dfbe9566f on master.

test-me-please

CI failed due to unrelated failure:
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/k8s-1.15-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:367
unable to create Istio resources
Expected command: kubectl apply -f  /home/vagrant/go/src/github.com/cilium/cilium/test/k8sT/manifests/istio-cilium.yaml
To succeed, but it failed:
Exitcode: 1
Stdout:
 	 poddisruptionbudget.policy/istio-galley created
	 poddisruptionbudget.policy/istio-ingressgateway created
	 poddisruptionbudget.policy/istio-policy created
	 poddisruptionbudget.policy/istio-telemetry created
	 poddisruptionbudget.policy/istio-pilot created
         <...>

test-me-please


lag on 4k display

Hello devs,
I have just tried this amazing frontend for neovim and I must say, I am impressed with the quality.
That being said, the only downside is that it is extremely laggy on a 4k display. I cand easily reproduce this by shrinking down the nvui window and it works as expected and is fast, so I know for syre the resolution is the problem.
I have encountered this problem when trying neovide as well (see: https://github.com/neovide/neovide/issues/1299) and initially thought it was a problem related to their implementation, but now I am not so sure, because it might be something deeper than the UI. The only frontend that has fast performance for me on a 4k display up until now is nvim-qt.
Could we maybe somehow coordinate between these three (your project, neovide and nvim-qt) to try and find a solution to this?

I'm not super experienced with this repo as of yet nor do I have a 4k
display,
but could you try disabling all animations as well as multigrid in the INI
file? It might be useful to know for whomever is trying to fix this issue
[General]
multigrid=false
popupmenu=false
cmdline=false

[window]
***@***.***(1288 31 1264 1401) #whatever position is fine
frameless=false
fullscreen=false
maximized=false

Test with you settings in init.vim set to:
NvuiAnimationsEnabled 0

Is there still lag?
On Wed, Jul 6, 2022 at 2:54 AM Adrian Costin @.***>
wrote:

Hello devs,
I have just tried this amazing frontend for neovim and I must say, I am
impressed with the quality.
That being said, the only downside is that it is extremely laggy on a 4k
display. I have encountered this problem when trying neovide as well (see:
neovide/neovide#1299 https://github.com/neovide/neovide/issues/1299)
and initially thought it was a problem related to their implementation, but
now I am not so sure, because it might be something deeper than the UI. The
only frontend that has fast performance for me on a 4k display up until now
is nvim-qt.
Could we maybe somehow coordinate between these three (your project,
neovide and nvim-qt) to try and find a solution to this?
—
Reply to this email directly, view it on GitHub
https://github.com/rohit-px2/nvui/issues/149, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSJHRI4CGA6Z2VDBROHUCDVSVJULANCNFSM52ZESYFQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Deepak Seeni

I'm not super experienced with this repo as of yet nor do I have a 4k display,
but could you try disabling all animations as well as multigrid in the INI file? It might be useful to know for whomever is trying to fix this issue
[General]
multigrid=false
popupmenu=false
cmdline=false

[window]
geometry=@Rect(1288 31 1264 1401) #whatever position is fine
frameless=false
fullscreen=false
maximized=false

Test with you settings in init.vim set to:
NvuiAnimationsEnabled 0

Is there still lag?

@dseeni I got around to doing what you suggested right now, and I must say it is a big improvement over the previous state (lag is gone 90%). still get it while scrolling through files, but not at first. if I keep 'j' pressed to scroll down, it starts just fine (nice and smooth while on the first page), then gradually becomes slower when it scrolls into the next page of text.

Nice, glad that helped.
Try this:
Stick this on the top of your init.vim|lua
function! NvuiGetTitle()
  return "nvui"
endfunction
NvuiTitlebarFontSize 10
NvuiTitlebarSeparator ''
NvuiVsync 0
NvuiOpacity 1
NvuiSnapshotLimit 0
NvuiAnimationsEnabled 0
NvuiIMEDisable
NvuiSecondsBeforeIdle 0
NvuiScrollAnimationDuration 0.0
NvuiMoveAnimationDuration 0.0
NvuiCursorAnimationDuration 0.0
NvuiCursorFrametime -1
NvuiCursorEffectFrametime -1
NvuiCursorEffect ''
NvuiCursorEffectDuration -1.0
NvuiCursorHideWhileTyping 1
NvuiScrollFrametime 0
NvuiScrollScaler identity
NvuiMoveScaler identity
NvuiCaretExtendTop 0
NvuiCursorScaler identity
NvuiCursorEffectScaler identity
NvuiCharspace 0.0
NvuiCaretExtendBottom 0
NvuiMoveAnimationFrametime 0

For the nvui config
add:
 [General]
 multigrid=false
 popupmenu=false
 cmdline=false

 [window]
 **frameless=true**
 geometry=@Rect(1280 0 1280 1440)
 fullscreen=false
 maximized=false

I seem to get the most performance when I set those things.. (old OS though).
For me this is the best front end for Nvim, I get the lowest latency when I shut all the animations even on Windows 8
Things are much better on Linux I think. I'm not sure why but for windows Nvim-Qt is a bit slower / startups up way slower IME.
In terms of nvim performance
enable lazy redraw
turn off treesitter
set synmax column to -1 your window width
set completions='' "NONE
or i (lsp should do most of this)
set the regexengine=1


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
docs(package): remove keyword null
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

Merging #669 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #669   +/-   ##
=======================================
  Coverage   92.96%   92.96%
=======================================
  Files           7        7
  Lines        1066     1066
=======================================
  Hits          991      991
  Misses         75       75

Continue to review full report at Codecov.

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

Coverage remained the same at 89.761% when pulling 139966dec9adfb9ce5d7b502b41ce359af47ea8b on template-sync-1 into d6333ee0e0339541642a43e722efd97180c5761c on master.

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


M1 Laptops cannot run all features of govuk-docker

An issue to track findings on running govuk-docker on M1 Laptops.
Current issues:

When initially running a 'make ' the make fails when trying to install google-chrome-stable. This can be replaced with chromium to get past the initial step, but tests runners later may rely on google-chrome-stable and cause failures in test suites.
MySQL versions below 8 are not available in arm64 architectures (possibly replace with MariaDB?)
MongoDB versions below 3.6 are not available in arm64 architectures (so router and router-api cannot be run. 3.6 is probably a safe replacement, since we're going to try to upgrade the production database to that anyway)

MySQL versions below 8 are not available in arm64 architectures

The good news here is that none of the GOV.UK apps are dependent on MySQL < 8.
There's a ticket on the database migration board to remove the MySQL 5.6 service from the docker compose configuration. Right now it's still defined but unused/redundant.

Thanks for opening the issue here and sorry that this issue has caught you at the time of you onboarding. I've put in a request with IT for an M1 machine myself to see if I can help (or at least experience the pain)

Additional:

inotify does not run under QEMU and will thus struggle in docker engine when running in AMD64 compatibility mode. I am unaware if there is an ARM build for it however if there is, our docker installation does not grab the relevant gems for the platform. It appears that Docker might use QEMU to run ARM on M1 chips anyway currently, so we may need to find a replacement.
govuk_test gem fails to run correctly due to being unable to call chrome driver via the webdrivers gem. We might be able to get ahead of this by updating the webdrivers gem value.
rabbitmq is best run on ARM64 mode rather than through the AMD64 QEMU due to known instability. Apparently it works better in ARM mode than AMD64 mode.
Replication scripts do not succeed without already having built and run the images we're cloning to first despite the behaviour being to tear down all the running containers. The images need to be initialised to, for example, setup the postgresql database in publishing-api. This is a regression from current behaviour.
Even if we manage to get everything up and running, any *.dev.gov.uk endpoints do not route correctly and cannot find the containers. Curls are intermittent, which makes me think it's a pipeline issue?

Seems a lot of this we can fix by upgrading to the latest version of the gems we can, however some of it may be bespoke for our environment.

Per @Tetrino 's suggestion I've made a branch that we can use as a fake main for M1 changes:
https://github.com/alphagov/govuk-docker/tree/m1-investigation
If we make M1-related changes, we can branch from there and PR into there and we'll have a handy way of 1) getting the fixes we need and 2) comparing the changes with main.

Note for related apps
Apart from the things required to get govuk-docker working at all, any app you want to run needs to have:

ruby bumped to min 2.7.5
the gems spring and spring-watcher-listen commented out in the gemfile if present.
the listen gem disabled by commenting out the line config.file_watcher = ActiveSupport::EventedFileUpdateChecker in /config/environments/development.rb

(The last two items remove spring and inotify autorestart in development mode, so they're not entirely ideal. Possibly there should be some boilerplate to allow them on intel systems).

govuk_test gem fails to run correctly due to being unable to call chrome driver via the webdrivers gem. We might be able to get ahead of this by updating the webdrivers gem value.

This looks like it's linked to inotify. If you bash into a running app's container and try to run google-chrome-stable, it fails with a coredump about inotify:
root@35558c032be5:/govuk/static# /usr/bin/google-chrome-stable --no-sandbox
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[370:370:0131/164025.878444:ERROR:nacl_fork_delegate_linux.cc(329)] Bad NaCl helper startup ack (0 bytes)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[334:379:0131/164025.994483:ERROR:file_path_watcher_linux.cc(321)] inotify_init() failed: Function not implemented (38)
[0131/164026.063886:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Function not implemented (38)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped

Are these problems when trying to run the tool through a compatibility tool (rosetta or similar) and an x86 architecture or are you compiling the images with an arm64 arch?

These are when I force amd64 builds for the app container (not necessarily on the other containers) by
# Install packages for building ruby
FROM --platform=linux/amd64 buildpack-deps

Without the --platform, google-chrome-stable won't install at all, with it it installs, but then won't run (because of inotify I think). The other option is remove the --platform tag and include chromium rather than google-chrome-stable, but the webdrivers used in gov_uk test seem not to be able to find nor use chromium.

I found that I am able to build using the following changes: https://github.com/alphagov/govuk-docker/pull/569
There's still errors for me to work through but build seems to "mostly" finish

@DilwoarH I think you can simplify that slightly by just editing Dockerfile.govuk-base and changing the line
# Install packages for building ruby
FROM buildpack-deps

...to....
# Install packages for building ruby
FROM --platform=linux/amd64 buildpack-deps

# Set M1 Workaround variables
ENV DISABLE_SPRING true

This forces all the app images to be built in amd64 (rather than specifying each one in its compose file), and turns off spring in any app that uses it (because spring relies on inotify, which doesn't work under qemu).
For any individual app you want to run you'll then need to bump it to ruby 2.7.5 (uncontroversial, because lots of them are being bumped to that anyway at the moment), and disable the listen gem (which uses inotify). I haven't come up with a nice way to disable listen at the base the way spring is disabled, sadly.

Another option is to use amd64/buildpack-deps instead of calling FROM at that point. We can also force docker to run in AMD64 mode as default platform using DOCKER_DEFAULT_PLATFORM=linux/amd64 however I agree the dockerfile is the better location.

PR to fix the chrome issues: https://github.com/alphagov/govuk-docker/pull/576

I found I didn't need to set anything up to build things for amd64 - it just worked like that by default?

Current state of affairs (mostly good):
Thanks to everyone's hard work, we're now at a stage where mostly everything works on M1 laptops. If you have one, you can proceed just as everyone else does, with the following exceptions:

Until govuk_tests is updated, you will need to tell it not to try to find drivers by adding the following lines to the bottom of your /Dockerfile.govuk-base (and the Dockerfile in the /projects/whitehall and /projects/asset_manager project folders)

  # Tell the govuk_test gem not to try to load webdrivers
  ENV GOVUK_TEST_USE_SYSTEM_CHROMEDRIVER yes

The default docker MySQL-8 app does not have an ARM64/v8 image. You can use an official MySQL image by replacing the mysql-8 image with mysql/mysql-server:8.0.28-aarch64 in /docker-compose.yml

The default docker ES-6 app does not have an ARM64/v8 image. You can replace it with ES-7 with no ill effects (that I've spotted yet) by replacing elasticsearch-6 dependencies in (eg) /projects/licence_finder/docker-compose.yml (affects: licence-finder, search-api)

Mongo 2.6 is not supported. You can replace it with Mongo 3.6 with no ill effects by replacing mongo2.6 with mongo3.6 in (eg) /projects/router/docker-compose.yml (affects: router, router_api)

govuk-puppet can't run, because it requires Ruby 1.9.3 at the moment (not supported)

if you want to use terraform, you can't use the default brew terraform. You need to install the hashicorp tap:

brew tap hashicorp/tap
brew install hashicorp/tap/terraform

@KludgeKML

Until govuk_tests is updated, you will need to tell it not to try to find drivers

We released govuk_test v3.0.0 today 🚀
The GOVUK_TEST_USE_SYSTEM_CHROMEDRIVER workaround won't be needed once apps have been updated. And despite it being a major release, dependabot should pick it up because our repos don't specify a version constraint.

I've put together a branch that should contain all the known fixes (thanks @KludgeKML, they're mostly yours) that collates what we know so far: https://github.com/alphagov/govuk-docker/pull/581

I'm going to mark this as closed as @kevindew 's branch has been merged in for a long whilte, and people have been developing on M1 silicon using govuk-docker for a while.


Bug in Android with cordova 3.5.x

Can't make it work and I've seen that there is a difference in the name. The folder created is nl.x-services.plugins.toast. I think it should be nl.xservices.plugins.toast right?

I don't mean to dig up old discussions but I stumbled across this while I was searching for a solution to the same problem. I used the "cordova plugin add nlx.." and just tried to run a window.plugins.toast.showShortCenter(msg) in a .js file from a button click. I get the same undefined property error. Was there a solution to this?

HI, that depends. Are you running on a real device? Which platform? Did you run cordova prepare..

Hello,
I'm running an avd (nexus 7/android 19). I ran cordova prepare, though not
right after I installed the package. I hastily tried emulating it once
before I did. I also tried to insert the one-liner into the device prepared
logic from the stock cordova app as a quick test to see if it was my js
file with the error; it had the same obscure error.
Regards,
Simon
On Jan 21, 2015 8:00 AM, "Eddy Verbruggen"<EMAIL_ADDRESS>wrote:

HI, that depends. Are you running on a real device? Which platform? Did
you run cordova prepare..
—
Reply to this email directly or view it on GitHub
https://github.com/EddyVerbruggen/Toast-PhoneGap-Plugin/issues/8#issuecomment-70832400
.

You're best off trying from scratch with a new cordova create.. command, add the plugin and deploy to a real device. If that works, try to find what's different..

Hi, sorry to hijack this issue but I have the very same issue; only on a 4.4.4. I used the exact same line in README.md to test and I commented out my own js file, but still no dice.

AM testing the plugin on my android device 5.1 and i get the same issue, $window.plugins undefined

Was this fixed? I have to use window.plugins.toast to get it working.


Add bibdata-alma-worker-staging1 in deploy

part of #1417
I'm opening as a draft until we create a new vm for bibdata-alma-worker-staging1

This PR was replaced by https://github.com/pulibrary/bibdata/pull/1471


Build package

Create a python package so it can be installed using pip

package published to pypi https://pypi.org/project/honeycheck/


UnhandledPromiseRejectionWarning: The client has already been closed

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Is this a client library issue or a product issue?
This is the client library problem.

Did someone already solve this?

Search the issues already opened: https://github.com/googleapis/nodejs-language/issues
Search the issues on our "catch-all" repository: https://github.com/googleapis/google-cloud-node
Search or ask on StackOverflow (engineers monitor these tags): http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js

No. This is error connected directly with this package.

Do you have a support contract?

No. I found
a) lack of documentation
b) problem in source code
Environment details

OS:
Node.js version: 12.8.2
npm version: 6.14.7
"@google-cloud/language": "^4.1.0",

Steps to reproduce

Letc create standard Test.

import {analyse} from "../api/helpers/sentimentAnalyser";

const inputSentence = 'Nienawidzę kradzieży i rozbojów. Na szczęście miłość, jest cudowna.';

const correctOutput = {
    inputSentence,
    translation: 'I hate robbery and theft. Fortunately, love is wonderful.',
    sentences: [
        {
            text: {content: 'I hate robbery and theft.', beginOffset: -1},
            sentiment: {magnitude: 0.8999999761581421, score: -0.8999999761581421}
        },
        {
            text: {content: 'Fortunately, love is wonderful.', beginOffset: -1},
            sentiment: {magnitude: 0.8999999761581421, score: 0.8999999761581421}
        }
    ],
    documentSentiment: {magnitude: 1.7999999523162842, score: 0},
    language: 'en'
};

it('Sentiment should be able to estimate', async () => {
    const obtainedResult = await analyse(inputSentence);
    expect(obtainedResult).toEqual(correctOutput);
});

With function
import {SentimentSummary} from "../interfaces/SentimentSummary";
const language = require('@google-cloud/language');
const translate = require('@vitalets/google-translate-api');

process.env.GOOGLE_APPLICATION_CREDENTIALS = `${process.cwd()}/google-master-key.json`;

export const analyse = async (input: string): Promise<SentimentSummary> => {
    let client = new language.LanguageServiceClient();

    const res: { text: string, from: { text: { autoCorrected: string } } } = await translate(input, {
        from: 'pl',
        to: 'en'
    });

    const text = res.text;

    const document = {
        content: text,
        type: 'PLAIN_TEXT',
    };

    const [result] = await client.analyzeSentiment({document: document})
    await client.close();

    result.inputSentence = input;
    result.translation = text;

    return result
}

And I have:
Jest did not exit one second after the test run has completed.

This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

In loop function in source code there are unclosed promises that can not be catched or waited for out of initialize function.
To fix my test case I need to use:
    const [result] = await client.analyzeSentiment({document: document})
    await client.close();

    await new Promise(resolve => {
        setTimeout(resolve, 500);
    });

but it is not ideal solution.

@gustawdaniel would you mind making this easier to reproduce, maybe boiling it down to the least amount of code possible? As written, there are external dependencies being used and it's not clear how to reproduce your application or testing architecture.

Thank you for filing this issue. We asked some clarifying questions a while ago and never heard back from you. We are unable to proceed with this issue until then, so we are closing it. Please feel free to re-open this issue with more information.


Feat: Wallet accounts

Put Accounts inside Wallet to have an easier access
Updated Wallet/Account types
Updated Wallet/Account type guards
Implemented methods to iterate over all wallets and all accounts
Removed MatrixContext

Three utility functions to conveniently find wallet(-s) with specific accounts:
getAccountsBy
getWalletFilteredAccounts
getWalletsFilteredAccounts
closes #1529

Any reason to remove the Matrix context? This is one of the tasks of https://github.com/novasamatech/nova-spektr/pull/1729

Any reason to remove the Matrix context? This is one of the tasks of #1729

Removed it just not to spend time fixing errors that are going to be removed by you anyway 😎

Any reason to remove the Matrix context? This is one of the tasks of #1729

Removed it just not to spend time fixing errors that are going to be removed by you anyway 😎

In that case how to release features before new Multisig discovery approach with indexer?


Fixed CIF parsing

Only consider the modifications to the parser in my last commit

thanks @danieleongari . Before I start reviewing, can you please add a pytest in a test folder (does not exist here, needs to be created). The test should basically read a xyz file and convert it into cif and compare the result with the expecting cif file.

closing this in favour of #7


[Copilot Pre-release License terms] Unclear what data is collected

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/site-policy/github-terms/github-copilot-pre-release-license-terms
What part(s) of the article would you like to see updated?

I would love to know which data Github collects during the Github Copilot "Chat in Jetbrains" beta.
Specifically, since these pre-release terms supersede the other Copilot terms, I would like to know whether Github uses my code snippets and the contents of my conversations with Github Copilot Chat for training purposes.

Additional information
No response

Hi @nikwen ,
Thank you for bringing up this important question and for your interest in GitHub Copilot.
I understand your concerns about data collection during the "Chat in JetBrains" beta. To provide accurate information, I recommend reaching out directly to GitHub Support or the GitHub Copilot team. They are best equipped to answer questions about data usage and privacy concerns.
You can contact them by GitHub Community forum and (https://support.github.com/contact). They will be able to provide you with detailed and up-to-date information regarding data collection practices during the beta.
If there's anything else I can help you with or if you have further questions, feel free to let me know.
Best regards,
@Harrisbaig7

Thank you for your comment, @Harrisbaig7! I've posted a request in the community forum.

Any updates, @cmwilson21?

👋🏼 @nikwen Thanks for following up! This is on our team's review board, and a writer will take a look at it soon ✨

Thanks you, @myarb! :)

Hi @nikwen - I reached out to Copilot product management for help with this. They've now got back to me. Thanks for your patience.
I hope the following information answers your questions.

What types of data does GitHub Copilot Chat beta use to provide the service?
GitHub Copilot Chat beta uses three types of data to provide the service:

User Engagement Data: User Engagement Data is data about user interactions with the service and overall usage data, which includes pseudonymous identifiers.  It's a privacy tool allowing data collection without directly linking it to a specific individual.
Contextual Prompts:  A Contextual Prompt is the combination of a summary of contextual information gleaned from the user as well as the question submitted in the chat interface
Suggestions: A Suggestion is one or more lines of proposed text returned to the GitHub Copilot Chat beta extension after a Contextual Prompt is received and processed by the AI-model. It is the output provided by the chat system to answer a user's query or engage in a conversation with the user.

What data does GitHub use to create a Contextual Prompt?
GitHub Copilot Chat beta creates a Contextual Prompt by combining (1) a “context summary” with (2) the question you submit to your editor.
For instance, if you submit “what does this method do” the client for GitHub Copilot Chat beta will automatically gather context from your active documents in the editor to determine what you mean by the word “this.” It will then compose a suitable question to pose to the GitHub Copilot Chat beta model that automatically includes that selection, without you needing to copy and paste code into the chat window, saving you time and delivering a hopefully useful response.
Depending on the question you ask, the GitHub Copilot Chat beta client will automatically use appropriate aspects of your context to form the question. The information it uses may include:

The code file open in your active document
Your selection (or “code blocks for the current cursor position”) in the document
Summaries of related documents open in your editor or from the workspace
Information about errors/warnings/messages/exceptions in your error list
General workspace information, such as frameworks, languages, and dependencies
Parts of related files in your workspace/project/repo

Does GitHub Copilot Chat beta retain, collect or store data by default?
The data handling details depend on whether you are using GitHub Copilot Chat beta as a GitHub Copilot for Business or GitHub Copilot for Individuals user and your settings if you are a Copilot for Individuals user.

Contextual Prompts and Suggestions are not stored at rest for Copilot for Business users
If you use Copilot for Individuals, your Contextual Prompts and Suggestions from your interactions with Copilot Chat beta will be retained unless you’ve disabled such collection in your current Copilot settings
User Engagement Data is collected and retained from all users, regardless of product type, for 2 years.

Does GitHub Copilot Chat beta use Contextual Prompts or Suggestions to train its Large Language Model (LLM) by default?
No. For GitHub Copilot for Business users, GitHub does not store Contextual Prompts or Suggestions from use of Copilot Chat beta at rest and hence such data is not used to train models. For GitHub Copilot for Individual users, GitHub retains this data from use of Copilot Chat beta unless the user disables such collection in their current Copilot settings.
Will my Contextual Prompts or Suggestions be shared with other users?
GitHub does not store Contextual Prompts or Suggestions from use of GitHub Copilot Chat beta for Copilot for Business users. GitHub only stores Contextual Prompts and Suggestions from use of Copilot Chat beta for GitHub Copilot for Individual users that have opted to enable such collection in their Copilot settings. Regardless, GitHub does not share that data with other users.

@hubwriter Thank you so much for your reply! That's exactly the information that I was looking for. You've answered my question perfectly. Huge thanks! :heart:

I think we can close this.


Release a new version

Hi,
first of all thank you for this great project!
I've see that the latest version you released is a bit outdated. Would it be possible for you to release a newest version?
Thank you.
Franco

I would like to write a test in a browser environment before the stable release.

Hey there, thanks for your work here, I'm also interested in a new release with the latest RFC implementation you made.


Global: Program filter menu should cascade, but should not be required, and auto-suggest

Throughout TolaActivity, we have program and indicator filters side by side. In many cases, selecting a program does not cascade and you continue to see all of your indicators for all of your programs.
Also: In the Program Report, you are able to select a country and a program that don't relate to each other. These should cascade as well -- anywhere this type of widget appears in the app.
I have not done an audit to find all of the places where these menus show up -- reports, forms, etc. Hoping that's something you can quickly assemble with some sort of query. Can you please add a comment with a list of all the places where you've made the change, that I should test?
DESIRED BEHAVIOR

If I select a program, I only see indicators associated with that program.
I am not required to select a program first before choosing an indicator. I can still go directly to the Indicators menu and choose from the master list.

BONUS
Add auto-suggest capability to Programs and Indicators selection widgets throughout TolaActivity. (If it looks strange to have that type of widget side by side with the type we have now, I'm fine doing the auto-suggest variety for all filters, even though it's less useful where there is a short list.)

I tested this manually, but it's a great candidate for automation.

Selected arbitrary combinations of program, indicator, and indicator type filters to confirm that results were limited to the selected combination of filters.
Selecting a program and then selecting a indicator with multiple matches only populates the table with a single indicator rather than the expected multiple matches -- I thought the filtering was a search functionality, but the UI allows indicators to have the same name even though they might otherwise be different indicators entirely. What's unique is the number, not the name.

Can we make the three menus fit on a single row, without needing to open the browser window to nearly the full width of a laptop screen?

When you pick an indicator from the "filter by indicator" menu, can we automatically open the program in which the indicator is contained, so that you don't need a second click to see it?

"Filter by indicator type" is getting truncated to "Filter by indic..."

Could we keep the menu labels as they are on production? Programs, Indicators, Types? Seems like this would be less likely to get truncated in a confusing way.

If there are no indicators in a program, we hide the Indicators menu, which makes sense. But we still show the Types menu, which seems odd. Is this easy to fix?

The fix for this is a little involved. Currently, it is setup to show a filtering dropdown only if it has data. The indicator dropdown is connected to the program dropdown so it gets updated but the type dropdown is independent and always has data.

Okay, let's leave it alone for now and address as part of Winterhawks.


Manual review requested for Quest token and Quest-USDT lp token

I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

Description and tags added for Quest token
Token address change (it created first with wrong address) for QUEST-USDT LP token
Please approve following PR https://github.com/solana-labs/token-list/pull/6076

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

merged


Update documentation for the quarantine

After the brew install icanhazshortcut I could not run the app because of the quarantine flag.
What about updating the readme with something like brew install --no-quarantine awesome-app ?
See reference here: brew no quarantine

Hm, let me think about it. Ideally this should be solved by passing notarization instead of a magic brew argument.

Could you elaborate on 'notarization'? I don't know what it is.
BTW the software is great!

Thanks!
In 2019 Apple introduced software notarization, which is now required to not trigger the gatekeeper. Code signing with a valid certificate (which iCHS has) is not enough anymore.
You can read about it here:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution?language=objc

Thanks for taking the time to explain and link the docs!


aioredis instrumentation fix with extra context and statement

What does this pull request do?
aioredis instrumentation is not available in elastic apm
Just like other instrumentations like asyncpg where we show what statement is executed, this PR adds the statement that is executed using the aioredis instrumentation
An example for the same is as follows:
GET service:key

Adds Redis under dependencies as well

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Reason: The PR is not allowed to run in the CI yet

Start Time: 2021-11-16T18:54:08.245+0000

Duration: 4 min 48 sec

Commit: 45e47344e1fbfd3601f34247310cab8a775c991b

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

/test

/test

Good catch! I'm not sure how this was missed in the original instrumentation.

@ajaygupta2790 A few failing tests. Keep me posted if you need help resolving them.

Yes I will need some help here, could you help me understand the test a little bit?

Hey @ajaygupta2790
The reason that the test is failing is that you're adding a span where we didn't create spans before, namely in RedisConnectionInstrumentation. That instrumentation was added to add destination data to an already existing aioredis span, because the needed information isn't available where that span is created. It's a somewhat ugly workaround, but it works (or, used to work until we renamed the subtype in the main instrumentation to redis and didn't also make that change in the if condition in RedisConnectionInstrumentation 🤦 looks like we have a testing gap there).
More generally speaking, so far we do not capture redis queries in any of our agents. This has been a deliberate choice, as redis keys quite often contain sensitive information like user names, ids, hashed passwords and similar. The risk of leaking such data from your production system to your monitoring system (in this case, Elasticsearch), is quite high. For SQL queries, we can do some sanitization, but this isn't possible for redis keys, which are essentially free-form.
I'll take this topic to our agents team to see if we want to change this and capture redis queries going forward.

/test

:globe_with_meridians: Coverage report

Name
Metrics % (covered/total)
Diff

Packages
100.0% (66/66)
:green_heart:

Files
100.0% (225/225)
:green_heart:

Classes
100.0% (225/225)
:green_heart:

Lines
89.9% (17437/19396)
:-1: -0.019

Conditionals
77.282% (3184/4120)
:+1:

I simplified and updated your solution to not add an additional span. Though the more I look at this the more I think it probably belongs in the instrumentation classes which actually create the spans.... I'll think on it.

/test

/test linters

/test full


Compute PERMIT_TYPEHASH constant instead of hardcoding it

Instead of hardcoding the result of keccak256 and explaining in a
comment where does the particular value come from, we compute it
when assigning PERMIT_TYPEHASH value.
I believe the intention behing the original version was to make
deployment a little cheaper, however the compiler should be inteligent
enough to optimize it.

Do we have a source/how confident are we that the compiler will optimize it?


Feature request: Format XML documentation comments

This is related to #667 but, I think, more narrow in scope.
We use xml documentation comments in code but have not been able to find a way to standardize formatting. Since we are already using csharpier to format our c# files, it would be really helpful if xml documentation comments were supported as well.

This is not a fix for the original problem but a manual workaround if you are simply looking to format the documentation you are currently writing.
Dirty workaround using prettier manually
1. Install prettier
$ npm install prettier

2. Copy documentation to a new .html file
Also remove leading ///
`MyClass.cs`
/// Some summary
/// <remarks>
///     <para>
///         This documentation is really long and requires that the formatter produces multiple lines when
///         formatted with
///         the <c>printWidth</c>
///         we are going with.
///     </para>
///
///         Console.WriteLine(
///             """
///             Hello World!
///             """
///         );
///
///     <para>
///         Another
///         badly <see cref="Formatting"/> formatted
///         para.
///     </para>
/// </remarks>
public class MyClass
{ }

documentation.html (input)
Some summary
<remarks>
    <para>
        This documentation is really long and requires that the formatter produces multiple lines when
        formatted with
        the <c>printWidth</c>
        we are going with.
    </para>

        Console.WriteLine(
            """
            Hello World!
            """
        );

    <para>
        Another
        badly <see cref="Formatting"/> formatted
        para.
    </para>
</remarks>

4. Add  before any  blocks etc. that should not be formatted
This will only affect the tag immediately following.
Some summary
<remarks>
    <para>
        This documentation is really long and requires that the formatter produces multiple lines when
        formatted with
        the <c>printWidth</c>
        we are going with.
    </para>
+

        Console.WriteLine(
            """
            Hello World!
            """
        );

    <para>
        Another
        badly <see cref="Formatting"/> formatted
        para.
    </para>
</remarks>

4. Run prettier
$ prettier --tab-width 4 --write documentation.html

documentation.html (output):
Some summary
<remarks>
    <para>
        This documentation is really long and requires that the formatter
        produces multiple lines when formatted with the <c>printWidth</c>
        we are going with.
    </para>

        Console.WriteLine(
            """
            Hello World!
            """
        );

    <para> Another badly <see cref="Formatting" /> formatted para. </para>
</remarks>

5. Reinsert ///, remove  and copy back to your .cs file
You can use search and replace by regex ^ -> ///  (note the trailing space in the replace expression!) to reinsert /// easily.


⚠ TADA Wallet Web has degraded performance

In 805f4bf, TADA Wallet Web ($WALLET_WEB_URL) experienced degraded performance:

HTTP code: 200
Response time: 11941 ms

Resolved: TADA Wallet Web performance has improved in e6b8426.


[docker] Is it possible to cancel the translation process if the client request is cancelled or times out?

Thanks again for this wonderful project.
We have a use case as follows. Is it possible to achieve this with EasyNMT? We haven't found any way to cancel ongoing translation processes yet.

HTTP Client makes an HTTP request to the docker container
The translation process may take a very long time, depending on the size of the input.
HTTP Client times out or cancels the request and retries again.

For Case 3, is it possible to cancel the ongoing translation process + HTTP request in order to reclaim processor resources for the next request immediately?

Hi @AgrimPrasad
I sadly don't know if / how this could be implemented. Maybe you can check the fastAPI docs and see if they mention, if  cancellations from the client can be detected and if a long running process can be interrupted.
But in general I think it might not work perfect, e.g. when the client suddenly dies without closing the connection, the server has no way to know this except of a timeout.
Maybe another way would be to restrict the number of sentences that can be translated with one call? Then, a client that cancels the request would not be so bad.

Thanks for the hints 👍 .
I used the sentences library to break up the source texts into batches of sentences before sending it to EasyNMT and it seems to be performing well so far.
Closing this issue.


Update makefile to run golangci lint bydefault

Also updated the installation method to make it work in CI systems as per https://github.com/golangci/golangci-lint#ci-installation
Commented some of the check in golangci.yml because either these need more effort to fix or not critical as compared to making golangci-lint default in make test.
Once  golangci-lint is enabled it will help fixing incoming code for lint issues and we can gradually add more checks by removing the comments in  golangci.yml.

/lgtm

/lgtm cancel
@LalatenduMohanty looks like the linter is not happy when run by CI:
/go/bin/golangci-lint run -c ./golangci.yml ./pkg/... ./cmd/... ./contrib/...
pkg/controller/clusterdeployment/clusterdeployment_controller.go:1494:65: `retrived` is a misspelling of `retrieved` (misspell)
			return "", errors.Wrap(err, "global pull secret could not be retrived")
			                                                             ^

@LalatenduMohanty looks like the linter is not happy when run by CI:
The last PR that got merged had a spelling mistake. :)

/test e2e

/test e2e

@dgoodwin This is ready for merge.

@dgoodwin You need to add lgtm again as, we merged (from the last time unit test had ran for this PR) some code with lint issues and the unit test failed again.


Fix Rule T1: rule now detects trigger_interval

Rule T1 currently doesn't check for trigger_interval; this PR attempts to fix that.
In our team we want to enforce data group usage so that we have a centralized view of how things are persisted.
I'm not 100% sure if Rule T1 was originally designed to only avoid sql_trigger_value or to enforce data group usage. If it's the former, I suggest the team update the wording on the documentation page, which now reads:

T1: Triggered PDTs should use datagroups
Rationale: sql_trigger_value is an older construct and can have subtle timing issues when multiple tables interact.

Hi @teng-vungle
I think you're right in terms of the ideal logic for the rule.
I'm currently close to releasing v3 of LAMS, and it includes a rewrite of most of the built-in rules, so I will go ahead and include this logic in the new formulation of the rule here: https://github.com/looker-open-source/look-at-me-sideways/blob/fabble/v3-extends-refinements/rules/t1.js#L12

Hi @teng-vungle !
This logic should now work as suggested in v3
If you have any feedback, feel free to comment in https://github.com/looker-open-source/look-at-me-sideways/issues/136 and I will open it back up as needed.
Thanks!


[feature] Reduce logs

The idea is to reduce the logs of jadx cli
it's doable with an xml file containing :
     <configuration> <root level="OFF"> </root> </configuration>
then the scripts must be modified :
For linux and mac
DEFAULT_JVM_OPTS="\"-Xms128M\" \"-Xmx4g\" \"-XX:+UseG1GC\" \"-Dlogback.configurationFile=${APP_HOME}/bin/jadx.xml\""
and for windows :
set DEFAULT_JVM_OPTS="-Xms128M" "-Xmx4g" "-XX:+UseG1GC" "-Dlogback.configurationFile=%APP_HOME%/bin/jadx.xml"

@superpoussin22 thanks for this solution, but for me, it looks like a workaround.
So I decided to make it more configurable and add options for control log level to jadx cli:
--log-level        - set log level, values: QUIET, PROGRESS, ERROR, WARN, INFO, DEBUG, default: PROGRESS
-q, --quiet        - turn off output (set --log-level to QUIET)
-v, --verbose      - verbose output (set --log-level to DEBUG)

By default jadx will output only "progress" info like:
INFO  - loading ...
INFO  - processing ...
ERROR - finished with errors, count: 1

And if you want you can disable output completely using -q or --quiet option
Also, your solution with custom log config via -Dlogback.configurationFile= will continue to work. For this, I add detection of such configuration and if found jadx will ignore any log-level options.
As always you can check these changes in latest unstable build

tjanks @skylot, that's perfect


two or three classifications

Hello! How to modify the procedure if two or three classifications are changed

please，help me，thank you very much.


Error rolling to GM with multiple results

Describe the bug
When a user makes a die roll blind to GM that includes multiple rolls, the roll succeeds and the results are sent to the GM, but al the other users see the message “ERROR: error preparing receipt message: no defined Dice object to consume”
To Reproduce
Steps to reproduce the behavior:

Check the "to GM" option for a die roll such as d20+{15/10}|c.

Expected behavior
All non-GM users should see the die-roll spec with a "[roll to GM]" tag.

A fix has been pushed to develop


DPS Model DPS5005 shows Amps with a multiplication factor of 10

Watt display is OK but Amp displays with a factor of 10. Therefore limited to max 20 = 2A.

That's interesting. Did you use the number entity to set the output current? Did you set 20 A or 2 A using the number entity? I would like to understand two or three entities should be fixed for your device model / firmware version:
sensor.dps_output_current
sensor.dps_current_setting
number.dps_current_setting

Its the same wherever I set current. in homeassistant or on the device. If I set 4A on the device it shows 40A in the integration. If I set 20A in Homeassistant it shows 2A on the DPS.
[23:29:33][D][sensor:094]: 'dps voltage setting': Sending state 6.02000 V with 2 decimals of accuracy [23:29:33][D][number:012]: 'dps voltage setting': Sending state 6.020000 [23:29:33][D][sensor:094]: 'dps current setting': Sending state 20.00000 A with 2 decimals of accuracy [23:29:33][D][number:012]: 'dps current setting': Sending state 20.000000 [23:29:33][D][sensor:094]: 'dps output voltage': Sending state 2.74000 V with 2 decimals of accuracy [23:29:33][D][sensor:094]: 'dps output current': Sending state 19.98000 A with 2 decimals of accuracy [23:29:33][D][sensor:094]: 'dps output power': Sending state 5.47000 W with 2 decimals of accuracy [23:29:33][D][sensor:094]: 'dps input voltage': Sending state 18.61000 V with 2 decimals of accuracy [23:29:34][D][text_sensor:064]: 'dps protection status': Sending state 'Normal' [23:29:34][D][sensor:094]: 'dps backlight brightness': Sending state 40.00000 % with 0 decimals of accuracy [23:29:34][D][text_sensor:064]: 'dps device model': Sending state 'DPS5005' [23:29:34][D][sensor:094]: 'dps firmware version': Sending state 1.40000  with 1 decimals of accuracy

I will prepare a fix!

This was too fast. The branch doesn't provide the fix yet. I will ping you as soon it's ready. :-)

Please update the dps section of your YAML to:
dps:
  id: dps0
  modbus_id: modbus0
  update_interval: 5s
  current_resolution: HIGH

And try the feature branch another time.

Failed config dps: [source /config/esphome/dps1.yaml:61] - id: dps0 modbus_id:
modbus0 update_interval: 5s [current_resolution] is an invalid option for
[0]. Please check the indentation. current_resolution: HIGH
Sebastian Muszynski @.***> schrieb am Di. 4. Juli 2023
um 07:48:

Please update the dps section of your YAML to:
dps:
id: dps0
modbus_id: modbus0
update_interval: 5s
current_resolution: HIGH
And try the feature branch another time.
—
Reply to this email directly, view it on GitHub
https://github.com/syssi/esphome-dps/issues/14#issuecomment-1619534890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7O7AIMLXL63MCUIRSBFHDXOOVBDANCNFSM6AAAAAAZ3S5NHY
.
You are receiving this because you authored the thread.Message ID:
@.***>

It looks like you aren't using the feature branch. Please change to branch of the external component from main to make-resolution-configurable:
substitutions:
  name: dps
  device_description: "Monitor and control a RDTech Digital Control Power Supply (DPS) via UART-TTL"
  external_components_source: github://syssi/esphome-dps@make-resolution-configurable

All set. Even uploaded and tried config change afterwards again. I will
check tomorrow again - on mobile & vpn for today
Sebastian Muszynski @.***> schrieb am Di. 4. Juli 2023
um 08:14:

It looks like you aren't using the feature branch. Please change to branch
of the external component from main to make-resolution-configurable:
substitutions:
name: dps
device_description: "Monitor and control a RDTech Digital Control Power Supply (DPS) via UART-TTL"
external_components_source: @.***
—
Reply to this email directly, view it on GitHub
https://github.com/syssi/esphome-dps/issues/14#issuecomment-1619563221,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7O7APYHBTAPBODSDHQ4RTXOOYEJANCNFSM6AAAAAAZ3S5NHY
.
You are receiving this because you authored the thread.Message ID:
@.***>

My bad on config. Works like a charm!

Did you try to use the number entity to change the current?

Yes, I did. works now with 5a but gets up to 4.89
Sebastian Muszynski @.***> schrieb am Di. 4. Juli 2023
um 19:23:

Did you try to use the number entity to change the current?
—
Reply to this email directly, view it on GitHub
https://github.com/syssi/esphome-dps/issues/14#issuecomment-1620558352,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7O7AKP3NW466DG2YIGEV3XORGRDANCNFSM6AAAAAAZ3S5NHY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I've merged the new feature into main. Please update your YAML again.

updated & still working. Thanks a lot for the quick response and assistance!

 Feel free to create new issues if you miss something or there is room for improvements!


Remarks section references non-existent COM interface(?)

The Remarks section on this page mentions an interface implemented by the object pointed to by the UnknownAdapter parameter:

see the definition and implementation of the IAdapterObject interface in the sb16 and msvad sample audio drivers

As far as I can tell, there's no other surviving references to this interface (in the docs or code examples).
A related, but separate issue is that given that the class pointed to by the optional UnknownAdapter parameter only seems to need to implement IUnknown, it's unclear what PortCls could possibly do with it, other than AddRef/Release(?). The docs mention that this param can be nullptr (and based upon MS sample code, so can Irp and ResourceList), but there's no explanation of what difference passing nullptr might make, if any...

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

ID: 9bbda5ba-1e00-6f60-3aca-32f2056c44e6
Version Independent ID: fa4348b8-019c-21e2-cd4d-78863fdc2a97
Content: IPort::Init (portcls.h) - Windows drivers
Content Source: wdk-ddi-src/content/portcls/nf-portcls-iport-init.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @DOMARS
Microsoft Alias: domars

@mr-intj - I updated this topic to point to the CMiniportWaveRT::Init definition and implementation in the newer Sysvad audio driver sample. Good luck with your audio driver development work.


[EDGENT-323] Create a download page and change links

Created a download page(docs/downloads.html) It includes src, bin location
Changed most of download links from github to newly created download page
Download links cannot be direct linked in your local environment now (most of configuration use edgent domain instead of localhost address. It will be resolved after deployed to production. If you wanna to test download pages, please type http://localhost:4040/docs/downloads.html or go to docs-> Get Started -> Downloads)

I'm very newbie on website.. So please do not hesitate to advice me :) It will be great help to me

I noticed that we need publish our artifacts to dist.apache.org. So download links will be changed after publishing.
And I'm afraid that do we need a cool&nice download page that includes design rather than a simple download page under doc(doc/download.html)?

[~Cazen] thanks for picking up this jira! (and your other deliveries the last couple of days)
I sent a clarifying note to @dev regarding the location of the release artifacts.  Hope that clears some things up<EMAIL_ADDRESS>Yes, a cool&nice page is highly desired I think. If that can be achieved in a day or two that would be great.  Otherwise a quick/simple first-iteration page will allow making the release announcement sooner and the page can be enhanced after the fact.

@dlaboss Thank you for detailed guide.
I will reflect your requirements soon

+1 thanks!


update readme

Pull Request
Description
Make a 'decent' readme. Good for documentation and understanding what is happening
It may be easier to view the code in markdown - here
Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #36 (6901d36) into main (a8edfde) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6901d36 differs from pull request most recent head e501441. Consider uploading reports for the commit e501441 to get more accurate results

@@           Coverage Diff           @@
##             main      #36   +/-   ##
=======================================
  Coverage   93.47%   93.47%
=======================================
  Files          13       13
  Lines         383      383
=======================================
  Hits          358      358
  Misses         25       25

Continue to review full report at Codecov.

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


Store the un-resolved form of config attributes in node configs

Describe the feature
Currently, dbt resolves all node configurations before putting them into a node's config. For example, if you have this dbt_project.yml:
vars:
  normal_materialization: 'view'
  folder_materialization: 'table'

models:
  my_project:
    materialized: "{{ var('normal_materialization') }}"
   folder:
       materialized: "{{ var('folder_materialization') }}"

Then when you run with dbt run --var {normal_materialization the manifest is serialized, the config of a node in folder/will look have{"materialized": "table"}`. This is nice, but it'd be better if:

the model's behavior at runtime was the same as it currently is
the config's representation in the manifest was {"materialized": "{{ var('folder_materialization') }}"}

This is complicated in the in-model config case:
{{ config(materialized=var('folder_materialization')) }}

A future issue should address this problem, but for this issue it'll be sufficient to only store the resolved form here.
This will help dbt do a better job on state.modified checks to decide of a node has been modified. Currently we have a false-positive issue where changing a var like this will result in dbt detecting that the node is "modified", which isn't really true.
This will definitely be a breaking change to some degree! We're going to have to figure out a number of interesting edge cases:

what should dbt ls show? Should it be a flag to say "don't resolve config values"?
the config.xxx selector probably needs to resolve xxx!
Should we include var values in the manifest as part of this?

Describe alternatives you've considered
We can stick with the current behavior.
We can make the un-resolved form a new field and include both in the manifest.
Who will this benefit?
Users of state:modified selector.

Resolved by #2735


map table

in @GiulioGenova / SMCcalibration

move map table panel after/before data table
rename to map simply
include map in description panel

all done


lorawan: upgrade to LoRaMAC-node v4.6.0

This release contains some bug fixes and improvements in the upstream repo.
See below link for details:
https://github.com/Lora-net/LoRaMac-node/releases/tag/v4.6.0
As discussed in Discord, @JordanYates and I propose to name the branches in our tracking repo based on the upstream LoRaMAC-node release instead of the Zephyr release. I've already created a branch v4.6.0-zephyr with the necessary 2 commits for Zephyr integration cherry-picked from the previous branch. If you disagree with the approach, just let me know a different way for the update to happen.

As discussed in Discord, @JordanYates and I propose to name the branches in our tracking repo based on the upstream LoRaMAC-node release instead of the Zephyr release. I've already created a branch v4.6.0-zephyr with the necessary 2 commits for Zephyr integration cherry-picked from the previous branch. If you disagree with the approach, just let me know a different way for the update to happen.

The reason for naming the branch against the Zephyr release was to indicate to which Zephyr release the branch corresponds. But having the upstream release info is not a bad idea also. How about using both?

How about using both?

I think that may get confusing because we don't want to create a dedicated LoRaMAC-node branch for every Zephyr release even if nothing was changed, so people may wonder why e.g. Zephyr v3.5 is still using a loramac branch named zephyr-v3.1.

How about using both?

I think that may get confusing because we don't want to create a dedicated LoRaMAC-node branch for every Zephyr release even if nothing was changed, so people may wonder why e.g. Zephyr v3.5 is still using a loramac branch named zephyr-v3.1.

Fair enough!

Yeah, seen the CI error with the commit title already, but I wanted to wait for your comments regarding the variable name before pushing the fix.
@Mani-Sadhasivam and @JordanYates do you also find the IsUplinkTxPending name confusing / wrong, or is it just me?

I agree the name is bad, but it’s constrained to the lorawan driver, and it comes from the upstream code, so I’m not sure we need to do anything. If you want to add a comment where it’s used that would be good I guess

Yeah, seen the CI error with the commit title already, but I wanted to wait for your comments regarding the variable name before pushing the fix.
@Mani-Sadhasivam and @JordanYates do you also find the IsUplinkTxPending name confusing / wrong, or is it just me?

It is confusing indeed... But we should just cope with it as we don't want to carry a commit for changing the name.

Yep, I'll think about submitting a PR upstream. But for now let's keep it as is. Could you please re-approve @Mani-Sadhasivam?


Restart and Update Do Not Happen

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T12:32:39.870Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

EditorConfig
Edi
0.11.1

python
ms-
0.8.0

Steps to Reproduce:

Receive notification of an update
Choose Update Now
VS Code closes and never re-opens
Manually re-open VS Code
Open Code menu option and choose "Check For Updates"
Start back at step 1

Reproduces without extensions: Yes/No

We're using Squirrel behind the scenes. In rare cases the update gets corrupted. We don't have a reproducible case for this yet. Please uninstall VS Code manually and reinstall it. Thanks!

Each time this happens, I manually update but it has never fixed the problem for the next update.


Add grate as an Dot Net Core global tool

Is your feature request related to a problem? Please describe.
For a project i'm working on, we use RoundhousE with the dotnet global tools to install it to the Azure Hosted Agents, this is super easy as we just need 1 command to install RoundhousE and one command to run it. No special installs or tools.
Describe the solution you'd like
We should make it possible to download grate as an global tool, just like RoundhousE
https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools-how-to-create
I have no clue how this works, but I'm willing to figure it out and do a pull request if this is something grate wants to support!
If we do not want to support this, add an alternative for people that work like I just described above.

https://erikbra.github.io/grate/getting-grate/#dotnet-tool

Ow wauw i'm stupid. Thanks!

Glad the feature was already in place :)
Would making an Azure Devops pipeline extension for grate (like this one for GitVersion, e.g? https://marketplace.visualstudio.com/items?itemName=gittools.gittools), with the parameters and everything easily available from the Azure Devops pipeline Yaml editor GUI? Or is that gold-plating?


Removing alerts

It would be nice to be able to display errors when popups are disabled.  What tool are you using to minify your javascript?  It would be good to see some documentation for that.

Your pull request seems good. I am busy currently and still need to do a bit of review, but this will hopefully be merged soon. Thank you for noticing this!

@david-dick I've made one change, which is to use var instead of let. The intent is to work on as many browser versions as possible. Regarding the minifier tool, I used https://www.toptal.com/developers/javascript-minifier . Nothing special about that specific tool, it's just the first one that showed up.
Let me know if this is good to commit. Thanks!

works for me!

Hey @david-dick, I appreciate the PR a lot, you're the first person to ever write any PR or issue on any of my repos... thank you!! As for the PR itself, it's been merged. 👍


Question

Code for close Tile ? (back to clock "Home Screen")

Code for close Tile ? (back to clock "Home Screen")

Hi, I'm not sure about which tile your mentioning? The code for all of the wearable tiles can be found HERE


Down server notifications repeated.

This has happened twice lately, and the same general root cause (agent inaccessible on a server due to network configuration) are present.
I have an OCI instance that I'm monitoring, and in this specific instance, it crashed and came up without the firewall rule that would allow the Beszel server to contact the agent.
When I visited the Beszel server web page, the 'down server' emails triggered, which you'd expect, but in this case it triggered 85 times in immediate succession, which is NOT what I'd expect.

I'm using the 0.2 server and agent.
Let me know what other details I can provide that might help in tracking down what the heck caused that to happen since USUALLY the down server notification triggers once like you'd expect, but it appears there's something that can cause it to do that.

Thank you! This is a duplicate of #97 but more or less confirms that it's a problem with the application.
Can you please go to the logs page in pocketbase and search for "Sent alert"? Do the multiple events show up there as well?

I don't see any sent alert notices, but I do see the events that triggered them:
created | 2024-08-22 22:34:05.655 UTC
message | Failed to connect:
data.err | dial tcp 10.x.x.x:45876: i/o timeout
data.port | 45876
There's 85 of those for this instance, and the ~300 for the time it happened previously.
Timestamps are between 2024-08-22 22:34:00.690 UTC and 2024-08-22 22:34:05.655 UTC so just barely under a second for the 85 failures and emails to be generated.

Okay thanks, I'll look into it and try to release a patch soon. Obviously you might want to turn off status notifications in the meantime.

When you have an opportunity, can you tell me if the message "Existing SSH connection closed. Retrying..." was logged around this time period as well? And if so, if it was logged repeatedly?
Spent some time on this but haven't been able to replicate yet.

Yep, looks like roughly the same number of those errors as the failed to connect ones/emails about it being down, and the timestamps align perfectly with the previous log ones.

Searched for "existing" and I found the same errors at the same time of notifications..

This should be fixed now. Please let me know if it happens again!


Added Activities to CarePlanStart States in Graphviz

Added a list of Activities prescribed by the care plan to the CarePlanStart states generated by graphviz.

Before:

After:


mNormalText

There is bug when press the button the button will show up the processing text and until in some situation i need to manually change the state to normal and the Normal Text does not come back up instead it shows the default text that is defined in the xml. Are there a better way to show do the setNormalText that will able to be programmed dynamically from manually changes?

I'm also having the same problem.

Thanks for contribution. New version uploaded to Maven Central, should be available soon:
compile 'com.github.dmytrodanylyk.android-process-button:library:1.0.4'


Improve "Connect to a Relay Chain"

https://docs.substrate.io/how-to-guides/v3/parachains/connect/
Before exporting the genesis state and the genesis wasm we should tell the user to generate a raw chain spec. Then we should tell them to use this raw chain spec for the respective CLI commands to extract the genesis state/wasm.
Users are confused on how to make sure that the chain spec and the registration information are matching.

This is covered in https://docs.substrate.io/tutorials/v3/cumulus/start-relay/#create-a-custom-relay-chain-spec-optional -- do you think the content is OK here? We can add a section in the how to guide that foregoes the extra manual customization of the chain spec (as it's not a super common thing to do) and just discusses plain -> raw flow.

I think the linked docs should be updated. In the steps where you generate the gensis-state and genesis-wasm you are not using this chain spec for example.

And this is also about the relay chain chainspec. My issue was about the parachain chainspec.

It is possible to download the Wasm and Genesis state registered with a relay in the case you cannot get it otherwise.
Mention best practice is to always include these files in you got repository alongside the code used to generate it, as we already tell people frequently that non deterministic generation of these files is expected (same code, different hash possibly, but you can use the one submitted on the relay, but better to save it in the canonical repo with your collar code)
Mention srtool #498

I outlined the process in the issue description. Yes you can download the wasm, but the genesis state will not bring you anything. While this can work, it can also be more complicated. The process I outlined is the easiest one and also not complicated at all.

related pr: https://github.com/substrate-developer-hub/substrate-docs/issues/524

This looks to  be pretty out of date.


Use serde type system for handlebars

This will help cargo to drop rustc_serialize as dependency (#3682). Handlebars actually supports using serde_json as its type system instead of rustc_serialize. And I'm planning to drop rustc_serialize in future releases.

@bors: r+
Thanks!

:pushpin: Commit 72d0a72 has been approved by alexcrichton

:hourglass: Testing commit 72d0a72 with merge 5db6d64...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 5db6d64bb73e8cbc0a5eaa8d133ce6ac0a1d6619 to master...


B1-B3 CZ Gate

This PR is based on the calibration of B1-B3 using the Chevron, virtual Z, and CHSH experiments.
1- Chevron: http://login.qrccluster.com:9000/n6Yl2wkNS1WkEY1ifTKS-Q==/
2- Virtual Z: http://login.qrccluster.com:9000/GhkVUQxuTyepEtwcWgF-QQ==/
3- CHSH Pulses: http://login.qrccluster.com:9000/WPLE0h22TGSJb9ynR70azg==/

@HishamKazim, thanks a lot for this. Does the README require changes?

I guess a new table like this could be added to the README:

Pair
Calibrated gate
RB fidelity

B1-B3
CZ
Not measured

Yes, that’s a good idea so we can keep track of 2q gates.

@scarrazza Done, added it on the readme, as we get more results we can update the table.

@HishamKazim, perfect. Please go ahead and merge.


Clippy cleanup

Reported-by: Clippy

@kamalmarhubi @Susurrus @posborne could one of you please review this PR?  I especially would like some review for the commits that make previously unsafe functions safe.  This PR eliminates almost all of the outstanding clippy issues.  It would be great to enable clippy in CI.

I took a quick look, but I think realistically I want to do a closer read, especially since it's been a while since I worked in this codebase. I'll aim to do that in the next few days, by the end of the week at the latest. Does that work?

Yeah; there's no urgency.

bors r+

bors retry

redoxer hanged again.  I think I'll disable the Redox build if we can't get that issue fixed.
bors retry

bors retry

rebased to fix merge conflict and also fix a formatting error in CHANGELOG

bors r+


discrete slider: initDelay too low?

Sometimes the slider knob isn't on the right position but instead it's positioned at the beginning of the line and it cannot be moved to the right direction again:

After some investigations I found out that increasing the value of initDelay solves this issue, i.e. from default value 250 to 500. Is this the right solution and should maybe the default be increased so that others don't need to search for same solution?

Yeah but ohters need a value of 750 or 1000. So there will nor an all working value for all out there.
i increased it to 500.

Sorry for coming back to this point again, but maybe one idea could stabilize it for every use case and would make this value in editor obsolete:
AFAIK, currently you're using the initDelay value within a setTimeout function.
Do you see a possibility to implement an upfront loop that checks the initialization x times (let's say 10 times a 250 msec) and continue only if the component/data is in place?
If after 10 times (=2,5 sec) the needed data is still not in place, a rendering of the slider would be cancelled entirely.

Still tried this solution, but IT mir works because of Font geht a Response fromm the Slider If it ist ready. This ist a Bug in the api.
Best solution would bei to geht the information If Dom ist ready drin the bis runtime. But didnt find a was to geht this information from vis. Document.load / .ready Not working


enhanc(aws-ec2): Add support for terminating node of a cluster with self-managed nodegroup

Signed-off-by: udit<EMAIL_ADDRESS>

Experiment Logs:
INFO[2021-02-22T23:10:08+05:30] Experiment Name: ec2-terminate
INFO[2021-02-22T23:10:08+05:30] [PreReq]: Getting the ENV for the  experiment
INFO[2021-02-22T23:10:08+05:30] [PreReq]: Updating the chaos result of ec2-terminate experiment (SOT)
INFO[2021-02-22T23:10:09+05:30] The application information is as follows     Namespace=default Label="run=nginx" Chaos Duration=80 Ramp Time=0
INFO[2021-02-22T23:10:10+05:30] [Info]: Total number active nodes are: 2
INFO[2021-02-22T23:10:10+05:30] [Status]: Getting the status of target node
INFO[2021-02-22T23:10:11+05:30] The Node status are as follows                Node=ip-172-20-48-193.us-west-2.compute.internal Ready=true
INFO[2021-02-22T23:10:11+05:30] [Status]: Verify that the AUT (Application Under Test) is running (pre-chaos)
INFO[2021-02-22T23:10:11+05:30] [Status]: Checking whether application containers are in ready state
INFO[2021-02-22T23:10:30+05:30] [Status]: The Container status are as follows  Pod=nginx Readiness=true container=nginx
INFO[2021-02-22T23:10:32+05:30] [Status]: Checking whether application pods are in running state
INFO[2021-02-22T23:10:32+05:30] [Status]: The status of Pods are as follows   Pod=nginx Status=Running
INFO[2021-02-22T23:10:36+05:30] [Status]: EC2 instance is in running state
INFO[2021-02-22T23:10:36+05:30] [Chaos]: Stoping the desired EC2 instance
INFO[2021-02-22T23:10:37+05:30] Stopping an ec2 instance:                     CurrentState=stopping PreviousState=running InstanceId=i-0d1ec4e395ee29a7b
INFO[2021-02-22T23:10:37+05:30] [Wait]: Wait for EC2 instance to come in stopped state
INFO[2021-02-22T23:10:37+05:30] [Status]: Checking EC2 instance status
INFO[2021-02-22T23:10:37+05:30] The instance state is stopping
INFO[2021-02-22T23:10:40+05:30] The instance state is stopping
INFO[2021-02-22T23:10:42+05:30] The instance state is stopping
INFO[2021-02-22T23:10:45+05:30] The instance state is stopping
INFO[2021-02-22T23:10:47+05:30] The instance state is stopping
INFO[2021-02-22T23:10:50+05:30] The instance state is stopping
INFO[2021-02-22T23:10:52+05:30] The instance state is stopping
INFO[2021-02-22T23:10:54+05:30] The instance state is stopping
INFO[2021-02-22T23:10:57+05:30] The instance state is stopping
INFO[2021-02-22T23:10:59+05:30] The instance state is stopping
INFO[2021-02-22T23:11:02+05:30] The instance state is stopping
INFO[2021-02-22T23:11:04+05:30] The instance state is stopping
INFO[2021-02-22T23:11:06+05:30] The instance state is stopping
INFO[2021-02-22T23:11:09+05:30] The instance state is stopping
INFO[2021-02-22T23:11:11+05:30] The instance state is stopping
INFO[2021-02-22T23:11:14+05:30] The instance state is stopping
INFO[2021-02-22T23:11:16+05:30] The instance state is stopping
INFO[2021-02-22T23:11:19+05:30] The instance state is stopping
INFO[2021-02-22T23:11:21+05:30] The instance state is stopping
INFO[2021-02-22T23:11:23+05:30] The instance state is stopping
INFO[2021-02-22T23:11:26+05:30] The instance state is stopping
INFO[2021-02-22T23:11:28+05:30] The instance state is stopping
INFO[2021-02-22T23:11:31+05:30] The instance state is stopping
INFO[2021-02-22T23:11:33+05:30] The instance state is stopping
INFO[2021-02-22T23:11:35+05:30] The instance state is stopping
INFO[2021-02-22T23:11:38+05:30] The instance state is stopping
INFO[2021-02-22T23:11:40+05:30] The instance state is stopped
INFO[2021-02-22T23:11:42+05:30] [Wait]: Waiting for chaos duration of 80s before starting the instance
INFO[2021-02-22T23:13:02+05:30] [Confirmation]: EC2 terminate chaos has been injected successfully
INFO[2021-02-22T23:13:03+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:06+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:08+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:11+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:13+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:15+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:18+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:20+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:22+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:24+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:27+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:29+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:32+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:34+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:36+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:39+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:41+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:43+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:45+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:48+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:50+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:53+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:55+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:13:57+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:00+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:02+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:04+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:07+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:09+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:11+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:14+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:16+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:18+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:21+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:23+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:25+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:28+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:30+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:33+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:35+05:30] [Info]: Total number active nodes are: 1
INFO[2021-02-22T23:14:37+05:30] [Info]: Total number active nodes are: 2
INFO[2021-02-22T23:14:37+05:30] [Info]: The active node count is: 2
INFO[2021-02-22T23:14:39+05:30] [Status]: Verify that the AUT (Application Under Test) is running (post-chaos)
INFO[2021-02-22T23:14:39+05:30] [Status]: Checking whether application containers are in ready state
INFO[2021-02-22T23:15:38+05:30] [Status]: The Container status are as follows  Pod=nginx Readiness=true container=nginx
INFO[2021-02-22T23:15:40+05:30] [Status]: Checking whether application pods are in running state
INFO[2021-02-22T23:15:41+05:30] [Status]: The status of Pods are as follows   Pod=nginx Status=Running
INFO[2021-02-22T23:15:43+05:30] [The End]: Updating the chaos result of ec2-terminate experiment (EOT)

Updated Logs:
W0315 10:22:11.713856       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2021-03-15T10:22:11Z" level=info msg="Experiment Name: ec2-terminate"
time="2021-03-15T10:22:11Z" level=info msg="[PreReq]: Getting the ENV for the  experiment"
time="2021-03-15T10:22:11Z" level=info msg="[PreReq]: Updating the chaos result of ec2-terminate experiment (SOT)"
time="2021-03-15T10:22:11Z" level=info msg="The application information is as follows" Namespace=default Label= Chaos Duration=60 Ramp Time=0
time="2021-03-15T10:22:11Z" level=info msg="The Node status are as follows" Ready=true Node=ip-192-168-16-41.us-west-2.compute.internal
time="2021-03-15T10:22:11Z" level=info msg="The Node status are as follows" Ready=true Node=ip-192-168-80-202.us-west-2.compute.internal
time="2021-03-15T10:22:11Z" level=info msg="[Info]: Total number active nodes are: 2"
time="2021-03-15T10:22:11Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (pre-chaos)"
time="2021-03-15T10:22:11Z" level=info msg="[Status]: Checking whether application containers are in ready state"
time="2021-03-15T10:22:13Z" level=info msg="[Status]: The Container status are as follows" container=ec2-terminate-dplpq0 Pod=ec2-terminate-dplpq0-j267f Readiness=true
time="2021-03-15T10:22:13Z" level=info msg="[Status]: The Container status are as follows" Pod=nginx-86c57db685-85ktc Readiness=true container=nginx
time="2021-03-15T10:22:13Z" level=info msg="[Status]: The Container status are as follows" container=chaos-runner Pod=nginx-chaos-runner Readiness=true
time="2021-03-15T10:22:15Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2021-03-15T10:22:15Z" level=info msg="[Status]: The status of Pods are as follows" Pod=ec2-terminate-dplpq0-j267f Status=Running
time="2021-03-15T10:22:15Z" level=info msg="[Status]: The status of Pods are as follows" Pod=nginx-86c57db685-85ktc Status=Running
time="2021-03-15T10:22:15Z" level=info msg="[Status]: The status of Pods are as follows" Pod=nginx-chaos-runner Status=Running
time="2021-03-15T10:22:18Z" level=info msg="[Status]: EC2 instance is in running state"
time="2021-03-15T10:22:18Z" level=info msg="[Chaos]: Stoping the desired EC2 instance"
time="2021-03-15T10:22:18Z" level=info msg="Stopping an ec2 instance:" CurrentState=stopping PreviousState=running InstanceId=i-0dd5b566ff6a6e3e7
time="2021-03-15T10:22:18Z" level=info msg="[Wait]: Wait for EC2 instance to come in stopped state"
time="2021-03-15T10:22:18Z" level=info msg="[Status]: Checking EC2 instance status"
time="2021-03-15T10:22:18Z" level=info msg="The instance state is running"
time="2021-03-15T10:22:20Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:22Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:24Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:27Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:29Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:31Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:33Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:35Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:37Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:40Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:42Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:44Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:46Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:48Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:50Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:52Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:55Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:57Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:22:59Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:01Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:03Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:05Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:08Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:10Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:12Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:14Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:16Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:18Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:20Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:22Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:25Z" level=info msg="The instance state is stopping"
time="2021-03-15T10:23:27Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:29Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:31Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:33Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:35Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:38Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:40Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:42Z" level=info msg="The instance state is stopped"
time="2021-03-15T10:23:44Z" level=info msg="The instance state is shutting-down"
time="2021-03-15T10:23:46Z" level=info msg="The instance state is shutting-down"
time="2021-03-15T10:23:48Z" level=info msg="The instance state is terminated"
time="2021-03-15T10:23:50Z" level=info msg="[Wait]: Waiting for chaos duration of 60s before starting the instance"
time="2021-03-15T10:24:50Z" level=info msg="[Confirmation]: EC2 terminate chaos has been injected successfully"
time="2021-03-15T10:24:50Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:24:52Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:24:54Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:24:56Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:24:58Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:00Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:02Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:04Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:06Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:08Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:10Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:12Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:14Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:16Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:18Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:20Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:22Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:24Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:27Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:29Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:31Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:33Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:35Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:37Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:39Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:41Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:43Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:45Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:47Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:49Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:51Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:53Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:55Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:57Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:25:59Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:01Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:03Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:05Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:07Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:09Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:11Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:13Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:15Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:17Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:19Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:21Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:23Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:25Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:27Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:29Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:31Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:33Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:35Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:37Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:39Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:41Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:43Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:45Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:47Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:49Z" level=info msg="[Info]: Total number active nodes are: 1"
time="2021-03-15T10:26:51Z" level=info msg="[Info]: Total number active nodes are: 2"
time="2021-03-15T10:26:53Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (post-chaos)"
time="2021-03-15T10:26:53Z" level=info msg="[Status]: Checking whether application containers are in ready state"
time="2021-03-15T10:26:53Z" level=info msg="[Status]: The Container status are as follows" Pod=ec2-terminate-dplpq0-j267f Readiness=true container=ec2-terminate-dplpq0
time="2021-03-15T10:26:53Z" level=info msg="[Status]: The Container status are as follows" Pod=nginx-86c57db685-85ktc Readiness=true container=nginx
time="2021-03-15T10:26:53Z" level=info msg="[Status]: The Container status are as follows" Pod=nginx-chaos-runner Readiness=true container=chaos-runner
time="2021-03-15T10:26:55Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2021-03-15T10:26:55Z" level=info msg="[Status]: The status of Pods are as follows" Pod=ec2-terminate-dplpq0-j267f Status=Running
time="2021-03-15T10:26:55Z" level=info msg="[Status]: The status of Pods are as follows" Pod=nginx-86c57db685-85ktc Status=Running
time="2021-03-15T10:26:55Z" level=info msg="[Status]: The status of Pods are as follows" Pod=nginx-chaos-runner Status=Running
time="2021-03-15T10:26:57Z" level=info msg="[The End]: Updating the chaos result of ec2-terminate experiment (EOT)"

We need to cordon the target node pre chaos and shift (drain) if any application is running on the target node otherwise the application can get lost.


can i port some vanillafix optimizations into forge 1.16.5 ?

i am porting phosphor, hydrogen and some betterfps features can i port with them some vanillafix features ? to forge 1.16.5

i am porting phosphor, hydrogen and some betterfps features can i port with them some vanillafix features ? to forge 1.16.5


Add support for AWS CodeBuild

Hi guys,
would be cool to add support for AWS CodeBuild.
Thanks
Maik
ci-info already implemented this kind of support.

Hi @pvdlg,

service detection: CODEBUILD_BUILD_ID
Branch
Commit sha
Is Pull request
Pull request number
Build number
Build URL
Root directory: HOME/CODEBUILD_SRC_DIR

For more details please check AWS CodeBuild: Environment Variables in Build Environments

Well, I asked because I looked at this doc and I didn't find any of the other variables.
All other supported CIs have at a minimum commit, branch and build. I'm not sure there is a point to add CodeBuild support if we don't get those at a minimum

:tada: This issue has been resolved in version 1.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix hashcode method for cyclic types

Purpose
$subject
Fixes #35762
Approach
The error happens when the generated methods of a record value call the hashcode() implementation of union & tuple types which are cyclic.
This is because we didn't consider whether the type is cyclic when we retrieve the hash code of them.
This PR fixes this by providing the hashcode of the superclass (BType).
Samples
public type Type string|Union|Tuple;

public type Union ["|", Type...];

public type Tuple ["tuple", Type, Type...]; // rest + members

type SubtypeRelation record {|
    Type subtype;
    Type superType;
|};

public function main() {
    Tuple tup1 = ["tuple", "never", "int"];
    Tuple tup2 = ["tuple", "never", ["|", "int", "string"]];

    Type subtype = ["|", "int", tup1];
    Type superType = ["|", ["|", "int", "float"], tup2];
    SubtypeRelation p = {subtype: subtype, superType: superType};
    io:println(p.toJsonString());  // Stack overflow error thrown
}

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[x] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing as the fix is added to patch branch
https://github.com/ballerina-platform/ballerina-lang/pull/35978


Change the structure of the gulpfile

I changed the structure of the gulpfile, and added an instruction on README.md file.

@Guilherme-Chinaglia can you please update your fork? I have updated the README few minutes ago.


burn asset rpc and fee execption

A new RPC to create raw transactions sending a single input to a null (OP_RETURN) output.
The burning of tokens should not require a transaction fee, so a new exception is added to the mempool acceptance fee check.

At the moment, the burnlist is used as a subset of the freezelist: i.e. an output address that is on the freezelist cannot be spent from UNLESS that address is also on the burnlist.
To redeem: An address will be added to the freezelist as redemption is started, preventing the output from being spent. Once the redemption process has completed, the same address is added to the burnlist, which allows a burn transaction spending from the freezelist address to pass (i.e. an address on the freezelist can be spent from IF it is also on the burnlist AND is a TX_NULL_DATA).
At the moment there is no policy to block TX_NULL_DATA output transactions that are not on the burnlist. There should be, but I'll do this as another PR.


Hierarchical models for April 2016 Ft Collins

Coverage decreased (-42.7%) to 18.48% when pulling 1d2f4f73ad8137ab85ee6fc5bf1c89ad4595cacb on develop into 13a7a0a182e17acf3b8ebb71e114ed1297637577 on master.


Suggest missing Logitech Brio 4K Webcam

[Enter feedback here]
According to this page the device is certified.
https://www.microsoft.com/en-us/microsoft-teams/across-devices/devices/product/logitech-brio-4k-webcam/37
Please review and add.

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

ID: b118e0a7-1fef-feae-6c6d-e24c4485a5b9
Version Independent ID: ae18e2db-fbbf-f30c-3c56-17dd0d2b85d1
Content: Phones and Devices for Microsoft Teams - Microsoft Teams
Content Source: Teams/devices/usb-devices.md
Service: msteams
GitHub Login: @dstrome
Microsoft Alias: dstrome

hi @chdurand - I spoke with our device certification team and confirmed the Logitech BRIO is not Teams certified. It is, however, certified for Skype for Business.
Our team is reaching out to Logitech to clarify this in their documentation and device specifications.


Fix wrong replica's port number(=0) if the listening port is not set

Background:
For some reason, I used Go to implement my slaves based on kvrocks. But by redis-cli to get replication-info from kvrocks(no matter what master/slave), the peer port is 0 which is wrong.
Reproduce:
Not only localhost but also the cross-machine can reproduce the bug scene.
So, I fixed it. Maybe it is not your code standard, Please review it.
before:

after:

@xiaofan8421 Thanks for your good catch! Leave a comment inline.

@xiaofan8421  Hi, would you like to finish the final modification according to @git-hulk before the 2.6.0 cherry-picking period? (refer to https://github.com/apache/kvrocks/discussions/1767)
If it can be merged before the deadline, it can be shipped to kvrocks 2.6.0 smoothly : )
If you are busy, we can help you to do that.

@xiaofan8421 Hi, would you like to finish the final modification according to @git-hulk before the 2.6.0 cherry-picking period? (refer to #1767)
If it can be merged before the deadline, it can be shipped to kvrocks 2.6.0 smoothly : )
If you are busy, we can help you to do that.

Thanks for your mention. Update PR. Please review it.


cleanup DUMP_FRAGMENTATION_STATS

We have DUMP_FRAGMENTATION_STATS support but the code is out-dated. This
cleans up (and refactors it so the data could be surfaced through ETW
in future).
This is partial change. DUMP_FRAGMENTATION_STATS result still incomplete
(missing Large bucket) and some incorrect (not agreeing with JD).

@dotnet-bot test Windows ci_disablejit_x64_debug please

Thanks @leirocks @digitalinfinity @atulkatti
@digitalinfinity  Yes @MSLaguana has pinged about memstats problems. Need more work to bring it up to date.