add new frontend webserver

Add a new html and css webserver

I thought we have moved to php, and why do we have html in this pr

My bad, I don't have any information about this. I was on Anual Leave for the past 2 weeks but will rectify it now. can you send me a link of where this discussion of migrating to php was documented please


FEATURE: Add sms sub-command

I used some code which existed in app.py, so possibly I'm repeating work and need to refactor, but I needed the functionality, so I added it.
If you want, you can cherry-pick from my code, but I'd be more than willing to change anything if needed. Anyway, Thanks for this great tool it has saved me so much time and trouble.

Thanks! I'll upload a new version soon

I uploaded version 0.7.0 which contains this change


Start using caret (tilde) ranges for dependency versions

Is your proposal related to a problem?
Lock files are containing several versions of the module. For example, if we add latest @babel/preset-env (7.5.5 to this moment) while using react-dev-utils, we achieve having 2 versions of browserslist package (4.1.1 for react-dev-utils and latest 4th version from babel package). This is true for most packages you use.
Describe the solution you'd like
Start using ranges (^ or ~) for dependency versions

We pin intentionally for stability reasons. I know it sucks for users of react-dev-utils, but that package exists mostly in service of react-scripts so this probably isn't going to change.


Safely clean up Win32 namespace after specs

Calling Object.send(:remove_const, 'Win32') in spec after blocks causes failures in specs which include libraries with rely on Win32.

:+1: And thank you for refactoring that out into a common shared context.

/cc @chef/client-windows

:+1: Looks alot better

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
Non-GitHub Verified Committers
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
Please sign the CLA here.


Add Teams Toolkit Support guide

I added a row to the table for Teams Toolkit support

Docs Build status updates of commit 35b3a09:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/feedback.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/feedback.md
80
19
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/feedback.md
80
19
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit df13ea9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/feedback.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/feedback.md
79
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit ed965eb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/feedback.md
:white_check_mark:Succeeded
View

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


SLF4J error while run code

I followed the instruction in your wiki (Section 3). I ran my code and get whole errors of SLF4J:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
SLF4J: Defaulting to no-operation MDCAdapter implementation.
SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.

This is my code:
MainApp.java:
package com.harrycoder.discordbot.tutorialBot;

import javax.security.auth.login.*;

import net.dv8tion.jda.core.*;
import net.dv8tion.jda.core.exceptions.*;

public class MainApp
{
	public static void main(String[] args) throws LoginException, InterruptedException, RateLimitedException
	{
		JDA api = new JDABuilder(AccountType.BOT).setToken("NDczNzk2OTkwNTY0ODI3MTQ4.DkHJqA.M04QK0zdksqiTFaSCMlyZrgMTN8").addEventListener(new MyListener()).buildBlocking();
	}
}

MyListener.Java:
package com.harrycoder.discordbot.tutorialBot;

import javax.security.auth.login.*;

import net.dv8tion.jda.core.*;
import net.dv8tion.jda.core.exceptions.*;

public class MainApp
{
	public static void main(String[] args) throws LoginException, InterruptedException, RateLimitedException
	{
		JDA api = new JDABuilder(AccountType.BOT).setToken("NDczNzk2OTkwNTY0ODI3MTQ4.DkHJqA.M04QK0zdksqiTFaSCMlyZrgMTN8").addEventListener(new MyListener()).buildBlocking();
	}
}

Your Sincerely

Did you take a look at the website that is linked in this error?

The github issue tracker is reserved for feature requests and bug reports. Your issue is neither and should be sorted out inside of our discord server. Go to discord.gg/0hMr4ce0tIl3SLv5 to receive the needed help.


Cosmetic tweaks to python_plugin_test.py

No behavioral changes. Changes to comments are error correction, not
changes of specification.

fwiw lgtm

Got an LGTM from @tbetbetbe in a different channel; merging.


[Feature] Link to the definition file in popup

It would be nice to have a link inside a popup to go to an atomic definition file or definition header inside consolidated files.
At the moment as I understand the only way to go to the definition is to use command which is bad UX required to do many additional movements to perform this action.

Okay, so I can wrap the definition in md link works fine. But at least a small link icon would be fine to have.

You could right-click and select "go to definition". Nonetheless i'll leave this as a possible enhancement.


Documentation to Docker Hub

Move image documentation from GitHub to Docker Hub.

I decided to keep the IVCT Docker image documentation in the GitHub project:

The DockerHub wiki is poor, altough the MD language appears to be the same as GitHub.
Keep all documentation in one place.

The DockerHub image documentation provides a pointer to the GitHub image documentation.


Reload state selections on mode change and minor syntax refactor

To test this PR:
Follow the instructions and ensure that the previous bug does not occur.
The below behavior is now fixed, see *

Open a project in tW and make a selection.
Click Save Changes
Click Edit, copy all of the text to the clipboard, delete all of the verse text, and then check the Other box
Click Save Changes, then Save Blank Verse, and then OK.
Click Edit, paste the text back in, then click the Other box
Click Save Changes
Notice that the previously selected text no longer shows as being selected.
Click Select
*Notice that the previously selected text again shows as being selected in the Edit box
Click Cancel
Notice that the previously selected text no longer shows as being selected.

This change is

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

Comments from Reviewable


WIP: #355 Initial Test Setup

Some initial setup to run the specs.
Ref: #355

If you're working on adding tests, that would be super cool! I'll be keeping an eye on this PR :)

Just a clarification, is this a WIP or is it ready for a merge?

It has the setup for tests and one sample test. We can merge this and
include more specs in subsequent PRs.
On Wed, Apr 1, 2020, 7:48 AM Jeremy<EMAIL_ADDRESS>wrote:

Just a clarification, is this a WIP or is it ready for a merge?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/covid19india/covid19india-react/pull/356#issuecomment-606987190,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADHFEFIEQO5ELWAFPWNMI3RKKP7TANCNFSM4LWCXKMA
.

@jeremyphilemon I have changed some configuration of the tests.
I saw that we constantly getting issues on the difference of the name in API response and the map data.
So I have added a test that downloads the data from this API endpoint, https://api.covid19india.org/state_district_wise.json, and compares it with the data stored inside public/maps.
One drawback is that it will stop when the assertions don't match. So, instead of showing all the errors of all the states it will stop on the first state where it fails. You can see the result in the screenshot. The test will move further only when we fix that state.
I can do the workaround by storing the static data. But then if it ever changes we need to update the spec manually.

I downloaded the data and implemented dynamic specs based on that static data. So, at least for now, we know what states need improvements in the data. Later when all the specs are green we can get rid of the static specs.

@jeremyphilemon I think we can merge this PR here and then keep creating new PRs as we go on writing specs.

@jeremyphilemon GitHub action added to run the specs on each push and PR.

Is it possible to simplify this PR by having a very basic test environment? It's very difficult to review this PR with so many changes.
And I think the data discrepancy tests should be done on the https://github.com/covid19india/api repository.
Closing this PR now. Please raise an issue regarding Tests (if it doesn't exist already) and discuss how to create tests before submitting.

@JunaidBabu I have created a new PR with an only basic setup: https://github.com/covid19india/covid19india-react/pull/960
I had included the data discrepancy test in this PR because we were getting lots of issues related to data. Issue #355 can be the place to discuss further about data discrepancy tests. I will add comments there too.
Meanwhile, again, here is the new PR: https://github.com/covid19india/covid19india-react/pull/960


24h problem

Why it shows AM/PM even in 24h mode? It is possible to show something else instead? I don't know current time or weather temperature. It's odd seeing 15:30 PM, very appreciated, thanks

Simple fix in printermonitor:
`
void drawClockHeaderOverlay(OLEDDisplay display, OLEDDisplayUiState state) {
display->setColor(WHITE);
display->setFont(ArialMT_Plain_16);
if (!IS_24HOUR) {// hide the AM/PM on 24
String time = timeClient.getAmPm();
display->setTextAlignment(TEXT_ALIGN_LEFT);
display->drawString(0, 48, time);
}
display->setFont(ArialMT_Plain_16);
display->setTextAlignment(TEXT_ALIGN_CENTER);
display->drawString(64, 48, "offline");
display->setTextAlignment(TEXT_ALIGN_LEFT);
display->drawRect(0, 43, 128, 2);
drawRssi(display);
}
`

Yes, I am fully aware that in the 24 hour mode it still will display either AM or PM down below the line.  it is easy to remove that line as noted above.  Changing it to Weather Temp would be easy.

I have started the 2.1 dev branch here:  https://github.com/Qrome/printer-monitor/tree/2.1
I have updated it to display the host name where the AM/PM would show but only on 24Hour clock mode.  You can try out that branch now if you like.


Re-design UI of VigyBag - Make it look like eco friendly

Read these points carefully

The design should look like eco friendly
In this new design, we will try to add handmade and eco-friendly products.
use a natural color pallet it will look like a natural theme.

Figma page link given below:
https://www.figma.com/file/hXcM6chTK70O6rAqCTFxuc/Vigy?node-id=0%3A1&t=px6VNjlFCos5Ll9z-1
Do not remove the old design just start your creativity in the below section.

@codervivek5  can you please assign me this issue ? I would look to work on the issue

@ira-mane this is very serious task so if you can do it then I can assign it to you
can you share your previous work.

@ira-mane this is very serious task so if you can do it then I can assign it to you
can you share your previous work.

I think I can work on the issue. I will share my previous work with you .
Thankyou.

I am waiting for your response:

if possible share your profile or any social handles where you have share your work.

@codervivek5 can you please assign me this issue ? I would look to work on the issue.
I can share you my previous work or its been on my github repos .

how can i share my work with you ?

Hello @codervivek5 , I am interested in redesigning the UI of this website as well. Here are some of my previous UI design works :

https://www.figma.com/design/HkBtu5lNSCyCzGpz4UIwgV/Techy-Software-Company?node-id=0%3A1&t=Hk60HL4Ir7G1T9qw-1
https://www.figma.com/design/uvfeGTKC0cUOpzpf8UCQoC/Music-App-UI?node-id=0%3A1&t=xJyvzuzbo1lkxK2Y-1

Thank you for considering. I hope you can assign this issue to me

Osm designs... ok now you can start working and remember after each page complettion tell me first
and create a PR so that you can get  your points of each page.

@ira-mane kindly share your work in have then I will also assign it.
but share your genuine work

@codervivek5 Sure, I'll start working on this and keep you updated. Is it possible to send you the finished work of each page via discord first?
That way I can work on it incase there are any feedbacks from your end and then raise a PR after the design is finalized.

sure this will fine :)

Now I will wait for you first page design....remember it that this is a e-commerce website.

ping me on discord then i will send you product image so you can take an idea about the website UI

can you assign me the task
i have showcase my work

I have to assign it to the first person who comments first ... so wait if other person will not work.

Thankyou for your Interest

Hello @codervivek5 ,I've contacted you over discord. Please look into it.

Hey @codervivek5 I can work on this issue as a designer and a developer. I have good experience in designing and building the website. Please assign this issue to me. Looking forward for your approval

Hey @codervivek5 I can work on this issue as a designer and a developer. I have good experience in designing and building the website. Please assign this issue to me. Looking forward for your approval

I already assigned this issue to other but if you want to work on it then you can collaborate with them just try to ask them if they agree then I will also assign this to you

I have to assign it to the first person who comments first ... so wait if other person will not work.
See that I had raised the comment before her still you didnt replied !!

Seems to be biased then !

Seems to be biased then !
No I am not biasing dude ... Actually don't mind but I have to follow the gssoc guidelines but if you can improve it then definitely you can.

I appreciate your amazing work bro. 👏 👏
You can also start working and show me a sample work if it will perfect then I will assign you abd akso will give you level3 tag for your good points.
Ans sorry for not giving your response actually I am not a single person who is handling this project so it's happened

Seems to be biased then !
No I am not biasing dude ... Actually don't mind but I have to follow the gssoc guidelines but if you can improve it then definitely you can.

I appreciate your amazing work bro. 👏 👏
You can also start working and show me a sample work if it will perfect then I will assign you abd akso will give you level3 tag for your good points.
Ans sorry for not giving your response actually I am not a single person who is handling this project so it's happened

cant we work both on same project @syrnxalno  ? It will be more creative and fast
@codervivek5 So assigned to both of us will make it out ..

Seems to be biased then !
No I am not biasing dude ... Actually don't mind but I have to follow the gssoc guidelines but if you can improve it then definitely you can.

I appreciate your amazing work bro. 👏 👏
You can also start working and show me a sample work if it will perfect then I will assign you abd akso will give you level3 tag for your good points.
Ans sorry for not giving your response actually I am not a single person who is handling this project so it's happened

@codervivek5 So assigned to both of us will make it out ..Then you decide which to have ,is that okay?

Hello @codervivek5 , Please assign me the issue if there is no one to work on it , I have good experience in UI design. I am sharing some of my work with you :
https://www.figma.com/design/JSaMDcEbKInEHquoxdacVy/Among-Us-game?node-id=3-2

Hello @codervivek5 , Please assign me the issue if there is no one to work on it , I have good experience in UI design. I am sharing some of my work with you : https://www.figma.com/design/JSaMDcEbKInEHquoxdacVy/Among-Us-game?node-id=3-2

Ok read oll the above comments and design a single page I will be good then I will tell you for continuing

@codervivek5 can you share your discord acc link i want share the UI so i can continue building  it ..
And thanks for giving me opportunty and i believe that you like my Design

Sure @codervivek5

@codervivek5  sir pls check your discord

@codervivek5 can you check this , and assign me the issue. I would like to work on it .
Link : https://www.figma.com/design/Sple5nVDow2Z5BfxDqqXMv/VigyBag?node-id=1%3A7&t=DGRsNCjGLZXNf8mF-1

Hello @codervivek5 , Please assign me the issue if there is no one to work on it , I have good experience in UI design. I am sharing some of my work with you : https://www.figma.com/design/JSaMDcEbKInEHquoxdacVy/Among-Us-game?node-id=3-2

Ok read oll the above comments and design a single page I will be good then I will tell you for continuing

Hey @codervivek5 ,  i had made half of landing page (can say home page) and shared with you via mail, please check and tell whether I should continue working on it or not?

Thankyou @Anuja1227 for making the perfect design


#2995 Fix duplicate label in when.

What
Does not build on latest react-native 0.74.2 with npx react-native run-android command, but works fine on RN 73.8
> Task :react-native-vision-camera:compileDebugKotlin
w: file:///Users/romick/app/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/types/OutputOrientation.kt:17:9 Duplicate label in when
w: file:///Users/romick/app/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/utils/CamcorderProfileUtils.kt:66:42 'get(Int, Int): CamcorderProfile!' is deprecated. Deprecated in Java
w: file:///Users/romick/app/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/utils/CamcorderProfileUtils.kt:90:42 'get(Int, Int): CamcorderProfile!' is deprecated. Deprecated in Java

> Task :app:compileDebugJavaWithJavac FAILED
545 actionable tasks: 541 executed, 4 up-to-date

Please remove duplicated lines:

Reproduceable Code
Regular project on latest RN 0.74.2.

Relevant log output
> Task :react-native-vision-camera:compileDebugKotlin
w: file:///Users/romick/app/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/types/OutputOrientation.kt:17:9 Duplicate label in when
w: file:///Users/romick/app/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/utils/CamcorderProfileUtils.kt:66:42 'get(Int, Int): CamcorderProfile!' is deprecated. Deprecated in Java
w: file:///Users/romick/app/node_modules/react-native-vision-camera/android/src/main/java/com/mrousavy/camera/core/utils/CamcorderProfileUtils.kt:90:42 'get(Int, Int): CamcorderProfile!' is deprecated. Deprecated in Java

> Task :app:compileDebugJavaWithJavac FAILED
545 actionable tasks: 541 executed, 4 up-to-date

Changes
Fix duplicate label in when
Tested on
* Huawai P20, Android 10

Related issues
#2995

Hey - thank you for your PR, but as mentioned in my comment in your previous PR, I don't see the reason for all those other changes - why re-order the cases in the enum?
I already created (and merged) a PR that fixes the issue, this is the expected change. https://github.com/mrousavy/react-native-vision-camera/pull/3022
Thanks anyways


Cannot find SourceMap

Bug, feature request, or proposal:
I'm getting this warning with webpack, it breaks the build.
WARNING in<EMAIL_ADDRESS>Cannot find SourceMap '/usr/local/google/home/jelbourn/material2/tmp/broccoli_type_script_compiler-input_base_path-OxHzApZr.tmp/0/components/button/button.js.map': Error: Cannot resolve
'file' or 'directory' .//usr/local/google/home/jelbourn/material2/tmp/broccoli_type_script_compiler-input_base_path-OxHzApZr.tmp/0/components/button/button.js.map in C:\Users\usta\angular2\node_modules@angular2-material\button

I believe #636 will resolve this when we publish the next release (should be this week).

I'm using webpack, not system.js,
I solved it like below;
        preLoaders: [             // needed to lower the filesize of angular due to inline source-maps             {                 test: /\.js$/,                 loader: 'source-map-loader',                 exclude: [                     // these packages have problems with their sourcemaps                     './node_modules/rxjs',                     './node_modules/@angular',                     /.*angular2-material.*/,                 ]             }         ],

If you upgrade to the latest cli version the errors should be gone

Does the CLI supports webpack?  I don't use the CLI tool.

FYI no one uses cli for production applications we all use webpack.


Fix #47

The generated code mentioned #name explicitly, causing
clippy::nursery warning use_self to trigger on the generated code.
This commit replaces usages of #name with Self where deemed
applicable, and the warning is no longer thrown.
Let me know what you think :)

Unfortunately, Self as a type constructor was only stabilized in Rust 1.32, barely missing our current 1.31 MSRV.
So the few places where you changed to Self:: should be fine, but map(Self) and returning Self(...) are not, at least until we do bump MSRV. I don't think it's worth bumping just for this nursery lint, but we could #[allow(clippy::use_self)] on those affected impl blocks.

The issue is being worked on in a generic way at:
https://github.com/rust-lang/rust-clippy/issues/6902
As the faulty lint has now made it beyond nursery. Perhaps we can wait with merging this until you raise the MSRV?

Since https://github.com/rust-lang/rust-clippy/issues/6902 has been closed, I suppose we can close this one as well :) right?

Thanks for checking back on this! Yes, I think we can close with clippy's resolution.


Unable to attach to usdt probe accross container namespace

What reproduces the bug?
I have a python process running in a docker container, and I'm trying to trace it with USDT probes.
From a --privileged and --pid=host container I can list the process probes.
root:/tmp# tplist -p 83320
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:line
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:function__entry
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:function__return
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:import__find__load__done
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:import__find__load__start
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:audit
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:gc__start
/proc/83320/root/usr/local/lib/libpython3.8.so.1.0 python:gc__done

I can trace successfully using bcc trace:
root:/tmp# /usr/share/bcc/tools/trace 'u::function__entry "%s %s", arg1, arg2' -p 83320
PID     TID     COMM            FUNC             -
83320   83320   python          function__entry  <stdin> <module>
83320   83320   python          function__entry  <stdin> <module>
^C

However I can't achieve similar behaviour with bpftrace:
root:/tmp# bpftrace -e 'usdt:/usr/local/bin/python3.8:function__entry { printf("hit\n")}' -p 83320
ERROR: failed to write elf: filesystem error: cannot canonicalize: No such file or directory [/proc/83320/root/usr/local/bin/python3.8] [/tmp]

root:/tmp# bpftrace -e 'usdt:/usr/local/lib/libpython3.8.so.1.0:function__entry { printf("hit\n")}' -p 83320
ERROR: failed to write elf: filesystem error: cannot canonicalize: No such file or directory [/proc/83320/root/usr/local/lib/libpython3.8.so.1.0] [/tmp]

root@73b774080281:/tmp# bpftrace -e 'usdt:/proc/83320/root/usr/local/lib/libpython3.8.so.1.0:function__entry { printf("hit\n")}' -p 83320
ERROR: failed to write elf: filesystem error: cannot canonicalize: No such file or directory [/proc/83320/root/usr/local/lib/libpython3.8.so.1.0] [/tmp]

Relevant strace [1] and [2] (in case it helps).
bpftrace --info
System
  OS: Linux 5.4.39-linuxkit #1 SMP Fri May 8 23:03:06 UTC 2020
  Arch: x86_64

Build
  version: v0.11.0-225-g487d
  LLVM: 7.0.0
  foreach_sym: yes
  unsafe uprobe: no
  bfd: yes
  bpf_attach_kfunc: yes
  bcc_usdt_addsem: yes
  bcc bpf_attach_uprobe refcount: yes
  libbpf: no
  libbpf btf dump: no
  libbpf btf dump type decl: no

Kernel helpers
  probe_read: yes
  probe_read_str: yes
  probe_read_user: no
  probe_read_user_str: no
  probe_read_kernel: no
  probe_read_kernel_str: no
  get_current_cgroup_id: yes
  send_signal: yes
  override_return: no
  get_boot_ns: no
  dpath: no

Kernel features
  Instruction limit: 1000000
  Loop support: yes
  btf (depends on Build:libbpf): no
  map batch (depends on Build:libbpf): no

Map types
  hash: yes
  percpu hash: yes
  array: yes
  percpu array: yes
  stack_trace: yes
  perf_event_array: yes

Probe types
  kprobe: yes
  tracepoint: yes
  perf_event: yes
  kfunc: no

So it looks like a couple of manifesting issues here.
a) At least on my system during abs_path("/proc/4112/root/usr/local/lib/libpython3.8.so.1.0") here:
// If PID is specified, targets in symbol_stream will have the
// "/proc/<PID>/root" prefix followed by an absolute path, so we make the
// target absolute and add a leading wildcard.
if (pid() > 0)
{
if (target != "")
  target = abs_path(target);
target = "*" + target;
}

it crashes during .canonical(). I can reproduce this easily, but not sure if it has to do with my compiler setup:
#include <iostream>
#include <experimental/filesystem>

using namespace std;

int main()
{
    auto p = std::experimental::filesystem::path("/proc/4112/root/usr/local/lib/libpython3.8.so.1.0");
    cout << std::experimental::filesystem::canonical(std::experimental::filesystem::absolute(p)).string();
    return 0;
}

root@14f52a83a05b:/tmp# ./a.out
terminate called after throwing an instance of 'std::experimental::filesystem::v1::__cxx11::filesystem_error'
  what():  filesystem error: cannot canonicalize: No such file or directory [/proc/4112/root/usr/local/lib/libpython3.8.so.1.0] [/tmp]
Aborted
root@14f52a83a05b:/tmp# ls /proc/4112/root/usr/local/lib/libpython3.8.so.1.0
/proc/4112/root/usr/local/lib/libpython3.8.so.1.0

b) When -p <pid> is specified, we look for probes by extracting search paths from the pid itself, rather than the given target path
if (pid > 0)
  usdt_probes = USDTHelper::probes_for_pid(pid);
else
{
  std::vector<std::string> real_paths;
  if (target.find('*') != std::string::npos)
    real_paths = resolve_binary_path(target);
  else
    real_paths.push_back(target);
    // ...
    auto target_usdt_probes = USDTHelper::probes_for_path(real_path);

}

This is not an issue in itself, but if a usdt probe is in a shared library file it will get registered based on the shared libraries bin_path.
static void usdt_probe_each(struct bcc_usdt *usdt_probe)
{
  usdt_provider_cache[usdt_probe->bin_path][usdt_probe->provider].emplace_back(
  ...
}
// (lldb) p usdt_probe->bin_path
(const char *) $0 = 0x00007fffe0000e00 "/proc/4112/root/usr/local/lib/libpython3.8.so.1.0"

Which again is not an issue in itself but the lookup into the cache in probes_for_pid, gets done on the main executing binary path:
usdt_probe_list USDTHelper::probes_for_pid(int pid)
{
  read_probes_for_pid(pid);

  std::string path = bpftrace::get_pid_exe(pid);
  if (usdt_provider_cache.find(path) == usdt_provider_cache.end())
    path = bpftrace::path_for_pid_mountns(pid, path);

  usdt_probe_list probes;
  for (auto const &usdt_probes : usdt_provider_cache[path])
  ...
// (lldb) p path
(std::__cxx11::string) $1 = "/proc/4112/root/usr/local/bin/python3.8"

In my case since the probes are not in the exe binary itself, the lookup for usdt_provider_cache[<python-exe-binary>] fails since only usdt_provider_cache[<path-to-libpython>] is present and probes come back as empty, giving me a No probes found error.
c) Attempting to circumvent this by not providing a -p <pid> flag, in which case the given target path is used (which I have provided correctly as the path to the shared lib), the probe gets identified but an assertion fails in bcc since it looks like it needs a pid to work.
# bpftrace -e 'usdt:/proc/4112/root/usr/local/lib/libpython<IP_ADDRESS>:function__entry { printf("hit\n"); }
Attaching 1 probe...
bpftrace: /bcc-build/bcc/src/cc/usdt/usdt.cc:87: bool USDT::Probe::add_to_semaphore(int16_t): Assertion `pid_' failed.
Aborted

Should be fixed now.

Should be fixed now.


Sigaction new interface

Changed sigaction interface in order to follow POSIX standards (one handler per signal).

Codecov Report

Merging #9 into master will increase coverage by 0.65%.
The diff coverage is 75.67%.

@@            Coverage Diff             @@
##           master       #9      +/-   ##
==========================================
+ Coverage   82.31%   82.96%   +0.65%
==========================================
  Files          15       15
  Lines         865      898      +33
==========================================
+ Hits          712      745      +33
  Misses        153      153

Impacted Files
Coverage Δ

Tests/POSIXTests/POSIXTests.swift
67.44% <71.42%> (+1.92%)
:arrow_up:

Sources/POSIX/Sigaction.swift
82.14% <78.26%> (+82.14%)
:arrow_up:

Continue to review full report at Codecov.

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


Help

Dear ICY
I have been mining below the old bedrock level.
been found that the quarry will not mine below the old bedrock level.
I also found when trying to build a forge in survival using the nether alloy.
I found that I couldn't pick up the nether alloy block.
Please fix this,
Thank you!
Artemis Fowl

This is an issue with Mechanization, not Datapack Utils.


test: implement automatic notifications for foss

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[x] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description
Minimizes some of the recent take messages.
Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

I don't understand what this is doing. How does it minimize messages?

Removing the flow, users can still try to use take; this is re-enabling the flow with the message you have been manually sending in multiple instances.


Fix mark success on abort

Description

run_wrapper and friends ensure that the plan always yields a run_stop which means the fall through in the RunEngine which sets the exit_status before hitting the run_close of lost resort.
Motivation and Context

fixs #847
How Has This Been Tested?

added a test

Codecov Report

Merging #861 into master will increase coverage by 0.05%.
The diff coverage is 94.44%.

@@            Coverage Diff             @@
##           master     #861      +/-   ##
==========================================
+ Coverage   86.03%   86.08%   +0.05%
==========================================
  Files          18       18
  Lines        4932     4966      +34
==========================================
+ Hits         4243     4275      +32
- Misses        689      691       +2

Impacted Files
Coverage Δ

bluesky/run_engine.py
97.18% <100%> (+0.03%)
:arrow_up:

bluesky/plans.py
94.34% <92%> (-0.07%)
:arrow_down:

bluesky/tests/utils.py
76.63% <0%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

I like this a lot. Will take a closer look tomorrow!

Can we put a comment in to spell out what teef means ?  I know what it is now, but future me might not be so bright! :)

Yes.  Name is evocative.  Must use restraint...
On Oct 18, 2017 7:21 PM, "Stuart Campbell"<EMAIL_ADDRESS>wrote:
Can we put a comment in to spell out what teef means ? I know what it is
now, but future me might not be so bright! :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NSLS-II/bluesky/pull/861#issuecomment-337764319, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACLKMIaY23zTl5Q11eobwotkkHYQa-LRks5stpYcgaJpZM4P-VGz
.

I think the name has been changed to “contingency”. I have learned that abbreviations are particularly tough on nonnative speakers and am now trying to avoid them where practical.

@prjemian Ha. Was not aware just how evocative until I Googled it. Let’s avoid scandalizing potential Dutch collaborators.

I have force-pushed potentially offensively named functions out of the history.


Improve blueprint device selection

Added a Manufacturer (Ulanzi) and Model (EHMTXv2) within the ESPHome Project Name
Added filtering on the blueprints to only show EspHome devices with model of EHMTXv2
Also made device name selection consistent on all blueprints

Very nice!


Type issue due to sap.m.WizardStep events jsDoc being too unspecific

The API doc for sap.m.WizardStep events is quite unspecific as the getParameters method of each event just returns type object.
I would have expected something more specific e.g. like the selectionChange event of sap.m.ListBase where the parameters are explicitly listed.
Because of that the type WizardStep$CompleteEventParameters from sap.m.d.ts that is generated based on the API doc currently throws an error for
onStepCompleted (event: WizardStep$CompleteEvent) {
    let currentStepId = event.getParameter("id"); // <-- Argument of type 'string' is not assignable to parameter of type 'never'
    [...]
}

although id is in fact a valid parameter of the complete event of a wizard step.

Hey @niyap,
I'm afraid that's not correct. The complete event of a WizardStep as of now offers the parameter id (e.g. in UI5 version 1.119.2) that contains the id of the WizardStep that triggered the complete event (so same as event.getSource().getId())
Chrome console:

I think same is true for activate.
So in case you adjust the return type of getParameters in the documentation to not return anything (which is also fine for me) you should as well adjust the actual implementation to not offer the parameters as shown in the screenshot above.
Cheers
Dominik


Add ceiling to arenas

And bounds to Grand Canyon

Great change! I really like that players on the ground now can reach the ceiling with their shots too (preventing stalling a bit at least 😅)

Ideally we'd do something different for the bullets so they phase through the invisible walls, but that's a problem for another time


Cow: Watch crackshere.com

Cow requests the watch of the watch_keyword crackshere\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

crackshere\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Nick in Charcoal HQ


[WFLY-17785] Tweak the set up for OidcIdentityPropagationTestCase and attempt to unignore it

https://issues.redhat.com/browse/WFLY-17785
Going to add the hold label to this one. I've tweaked the test setup slightly. Will keep this on hold until we can get a bunch of successful runs for OidcIdentityPropagationTestCase.

/retest

/retest

/retest

/retest

/retest

/retest

Going to go ahead and merge this one since we've already had complete successful runs on this PR and since QE has confirmed that the intermittent failures no longer occur with this fix.


Bump nokogiri from 1.11.4 to 1.13.4

Bumps nokogiri from 1.11.4 to 1.13.4.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: nokogiri dependency-type: indirect ...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

if possible I would like for someone review this pull request


Docker/container image

Use Case
An "official" Docker image would be very helpful for use in CI pipelines, such as with GitLab CI.
Describe the Solution You Would Like
A Dockerfile is already maintaned in the repository, so it would be great to actually build images based on that and store them in GHCR (though other registries would be useful too).
Describe Alternatives You've Considered
I currently build my own, and looking at Docker Hub it looks like several others have had to do the same.
Additional Context
n/a

How would you deal with plugins?

puppet-lint is quite useful without any extra plugins installed (just the shipped rules), but even so an image with puppet-lint already installed will provide a good base to install plugins on before running the rest of a job. Perhaps the project could also provide a different flavour of image with some recommended plugins pre-installed?

Hi, Vox Pupuli publishes a container with puppet-lint: https://github.com/voxpupuli/container-voxbox


Cannot find module 'ts-mocha'

I'm trying to run project with typescript right now.
I've followed doc procedure.

yarn add algob.
yarn run init . --typescript
project successfully created with typescript.

after that algob test
it shows error message.
also algob deploy.
error meessage shows they are trying to find only javascript files.
Is there any idea for that?
Best.

You need to add ts-mocha. Probably yarn add -D ts-mocha will be enough.
We will update the sample project dependencies.

I have a similar issue, after init with --typescript I have the following errors when running tsc --build .
node_modules/@algo-builder/algob/build/types.d.ts:108:13 - error TS2503: Cannot find namespace 'Mocha'.

108     mocha?: Mocha.MochaOptions;
                ~~~~~

node_modules/@algo-builder/algob/build/types.d.ts:1:23 - error TS2688: Cannot find type definition file for 'mocha'.

1 /// <reference types="mocha" />
                        ~~~~~

Installing ts-mocha doesn't help

I have a similar issue, after init with --typescript I have the following errors when running tsc --build .
node_modules/@algo-builder/algob/build/types.d.ts:108:13 - error TS2503: Cannot find namespace 'Mocha'.

108     mocha?: Mocha.MochaOptions;
                ~~~~~

node_modules/@algo-builder/algob/build/types.d.ts:1:23 - error TS2688: Cannot find type definition file for 'mocha'.

1 /// <reference types="mocha" />
                        ~~~~~

Installing ts-mocha doesn't help

Let follow below steps:

add types/mocha.
Run yarn algob test to test.

This error was fixed on a new version of algo-builder. However it's not release yet 😢


Add Attention Test Suite

Progress on this https://github.com/iree-org/iree-test-suites/issues/2
This PR refactors, adds, and migrates Attention e2e tests from the PR here: https://github.com/iree-org/iree/pull/18320

@ScottTodd, do we have any other comment from your side? If not, can you approve this?


Basic scaladocs for EitherSugar and TrySugar. [SCALATEST-485]

These are the basic scaladocs; some examples similar to those in OptionSugar will follow.

Made against the wrong branch, should be 2.2.x....


New PR to test SignCLA at 2018-08-22 00:56:39.916493572 +0000 UTC m=+4.454967329

Body of PR

corp-pass-fork-staging: test succeeded


agree terms & privacy

I want add my custom bot, but it show "By using my_bot, You agree to the Terms of use and Privacy statement."
how can I fix it?

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

ID: 69a9e1df-9152-d396-cd87-f84ba5772bfd
Version Independent ID: e234d4e3-21d3-9a10-49b2-78b864ef723a
Content: Add bots to Microsoft Teams apps - Teams
Content Source: msteams-platform/concepts/bots/bots-overview.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

@ch60234 - What part of the sting you are looking to change? Could you please share some screenshots with more details?

like that,is my setting wrong?
I can't chat with my bot

@ch60234 - After installation you should be able to see your App in personal scope.

If you are still not able to chat with bot then could you please check if you created Notification Only Bot?
App Studio:


Review 11: 4100.jsx and ContactUs.jsx.

Overview
The focus for this code review will be centered around 4100.jsx and ContactUs.jsx.
Please pay attention too:

Javascript issues
React components

Review Branch
review-11
Files to review

4100.jsx
ContactUs.jsx

Checklists

Architecture
Design
JS
React

Due date
11/25/24
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414s21/morea/review/reading-idpm-review.html

4100.jsx:
Code is readable, organized
L28-L33 can be moved to CSS
ContactUs.jsx:
Code is readable, organized
Avoid using eslint-disable-next-line (L52, L57, L62, L67)

4100.jsx
RE-08 imported component names and file names should match.
File name is 4100.jsx, but exported default "EditableSpreadsheetDetailed"
does not match file name.
ContactUs.jsx
ES-01 unexpected alert (no-alert) on lines 19 and 21

4100.jsx
AR-01: File name conventions are followed - maybe the file can be changed to EditableSpreadsheetDetailed.jsx
https://github.com/manoa-inspire/MATP/blob/8df28ac520336ccc9ba27f248d1cb8fe77310fc1/app/imports/ui/pages/4100.jsx#L6
DE-06: Ensure code is readable - The code is readable with no dead code or errors.
ContactUs.jsx
ES-01: No errors, avoid warnings - Use of eslint-disable-next-line, if possible avoid using disable-next-lines.
https://github.com/manoa-inspire/MATP/blob/8df28ac520336ccc9ba27f248d1cb8fe77310fc1/app/imports/ui/components/ContactUs.jsx#L52-L67
DE-06: Ensure code is readable - Code is clean and readable.

4100.jsx
AR-01: File name conventions are followed - maybe the file can be changed to EditableSpreadsheetDetailed.jsx
https://github.com/manoa-inspire/MATP/blob/8df28ac520336ccc9ba27f248d1cb8fe77310fc1/app/imports/ui/pages/4100.jsx#L6
DE-06: Ensure code is readable - The code is readable with no dead code or errors.
ContactUs.jsx
ES-01: No errors, avoid warnings - Use of eslint-disable-next-line, if possible avoid using disable-next-lines.
https://github.com/manoa-inspire/MATP/blob/8df28ac520336ccc9ba27f248d1cb8fe77310fc1/app/imports/ui/components/ContactUs.jsx#L52-L67
DE-06: Ensure code is readable - Code is clean and readable.

4100.jsx
L15, L76, L94, 112: DE-02, Avoid deeply nested conditionals. Consider using the component more dynamically.
L28-32: Ensure code is readable, put styling code into the CSS file.
TU-01: The collection has no unit tests. add unti test for editable cell component
ContactUs.jsx
L52, L57, L62, L67: ES-01, Avoid warnings, there are many ESlint warnings.
L11-14: JS-03, Use object destructuring on event.target. Could be
const { name, email, subject, message } = event. target

4100.jsx
TST-01: Verify updateCellData correctly updates the intended cell and does not affect other rows.
TST-02: Test how the component handles empty or incorrect inputs (e.g., non-numeric values for financial data).
ContactUs.jsx
JS-01: Add checks for empty fields in handleSubmit and display user-friendly error messages.
RE-01: Use React state to handle form inputs instead of directly accessing event.target.


Add basic smoke test for PNPM

Ready for a review, will remove the last commit before merging which I added just to make sure the spec is actually passing.


Improve consistency of labels GO:1900368 'regulation of post-transcriptional gene silencing by RNA' & related

The corresponding term in the non-regulatory branch. is called 'ncRNA-mediated post-transcriptional gene silencing''

[ ]  GO:0070928 regulation of mRNA stability, ncRNA-mediated >> obsolete & replace by     GO:0035194 ncRNA-mediated post-transcriptional gene silencing


Invalid SSL certificate shipped in 1.8.2

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
HTTPS should work in all browsers and on Windows, MacOS and potentially Linux and on verification using OpenSSL.
Observed Behavior
When the currently installed certificate gets uninstall using gulp untrust-dev-certand reinstalled using gulp trust-dev-cert.
When a project gets started using gulp serve the browsers Safari, Chrome, IE are more fault tolerant and load the workbench without any problem.
Firefox refuses to load the workbench with the following error message:

FireFox is actually the only browser that shows the right error message, while the other mostly ignore the problem to connect using SSL as it seems.
To verify that there is something wrong with the SSL connection I used open SSL to connect to the local workbench using the following command.
openssl s_client -connect localhost:4321 -showcerts

The result looks like this:

Verify return code: 21 (unable to verify the first certificate)

This error means that the whole certification chain cannot be verified. The result is independent of the operating system that was used because Windows shows exactly the same behaviour.

Therefore only FireFox seem to properly handle the certificate.
The same behaviour with FireFox was at least reproduced with two different MacOS and one Windows client. People with older certificates don't have that problem. Only when gulp untrust-dev-cert and gulp trust-dev-cert gets executed using at least SPFx 1.8.2.
Intermediate solution to this problem
To verify that this issue is caused by the SPFx certificates new self-signed certificates got generated using OpenSSL.
The key gcb-serve.key and the certificate gcb-serve.key was then replaced on MacOS in the following folder:
MacOS
~/.gcb-serve-data

On Windows
%userprofile%\.gcb-serve-data

After this new properly created SSL Certificate and Key was exchanged in the certification workbench configuration Firefox on Windows as well as MacOS was open the workbench properly.

First with a warning that was expectable but once the exception was added without any problem.

To verify that these new certificates are working the following OpenSSL verification was executed again.

Now the return code is:
Verify return code: 18 (self signed certificate)

It indicates that this is a self-signed certificate but in general, it is a valid certificate for HTTP.
Steps to Reproduce
1.) Execute gulp untrust-dev-certificate using 1.8.2
2.) Execute gulp trust-dev-certificate using 1.8.2
3.) Run gulp serve on a project
4.) Open it in Firefox and perform the verifications steps described above.

Hey Stefan - so we haven't done anything in this area for a year or more.  Is it possible that firefox has tweaked how it handles certs in some way?  @iclanton replied off-line with
OpenSSL doesn't seem to use the default Windows cert store
So it doesn't seem to be that "Firefox is doing the correct thing," it seems that Firefox has its own cert store
The second cert that he generated that ye says "worked" is a TLSv1 cert, which I believe is considered insecure at this point

    It seems like when he says "Therefore only FireFox seem to properly handle the certificate," he means "Only Firefox seems to handle the certificate the same way OpenSSL does"

Here are some other threads I have seen - https://stackoverflow.com/questions/9507184/can-openssl-on-windows-use-the-system-certificate-store , https://groups.google.com/forum/#!topic/mailing.openssl.dev/AG3QwMNS0dM , etc.
They all seem to indicate that OpenSSL has it's own cert store, and they handle that by copying the cert out of the windows store into the OpenSSL one.

Hey Pat, there are two things involved one is the client which might be a problem of OpenSSL The error and issue are on the web server, not the client accessing.
Like mentioned above the certificate and key stored in the folder .gcb-serve-data are the one used by the web servers in SPFx and those are the broken one.
In addition, I did a test with gulp-connect in a vanilla NodeJS project and certificates like this are not even used in the default configuration.
OpenSSL I just used to cross-check. The fact that the server certificate that gets installed on the client only hide the fact of broken certificates. Even though the certificates I used to exchange have been neither store in Windows, MacOS or any other certification store and it is possible to establish a valid SSL connect. FireFox is the only picky browser, while the other ignores everything server from localhost.
I have the same experience with browsers since I started to use the yo generator-webapp for classic experience branding.

I'm not seeing this... could it be that FF just changed their error error page to make self-signed certs look more scary?

@andrewconnell Well not working and not look scarier.

Now my workbench runs on every browser on every platform even Linux. I had to generate a new set of certificates and keys and replace the default ones.

Have you tried this on another machine? I've not seen this on three different machines with 1.8.2... maybe localized issue?

@andrewconnell  it is not a local issue but you might have still an old dev trust in it. You could try to untrust and trust again to break it.
Verified this issue in FireFox on a couple of different machines and cross verified with Waldek. The system used for testing this were:

Windows Server 2016 R2
Windows 10
Ubuntu
MacOS

Is this still relevant now that we're on a more current version of SPFx v.1.9.1.?

It is still relevant and an issue in 1.9.1. For now, I fixed it by swapping the default certs to own created certificates.

@StfBauer you closed #6221 as a duplicate of this, but it is not. That issue is affecting all browsers, and as I said in the issue, I've already tracked it down and attributed it to gulp-connect.

@caseyWebb Technically I'm the one that closed #6221 by tagging it as a dupe... @StfBauer has more knowledge on this issue than I do so I'm going off the fact he said it was a dupe. If you guys disagree, I can re-open and "un-dupe" it.

I don't have a strong opinion other than I think that all these SSL related issue are caused by the fact that not all RCA's (Root Certification Authorities) are available on all clients, which leads this issues like the one with gulp-connect.


Test fixtures: make PageserverHttpClient/SafekeeperHttpClient creation automatically pick up auth token

See https://github.com/neondatabase/neon/pull/1856#discussion_r889299407

Won't fix:

Most of our tests do not use authentication => auth_token is not needed.
Those that do, test it in various ways. A test may ensure that multiple access tokens are valid for the same API call, or that some are invalid. E.g. in the original discussion, the test explicitly tests four different scenarios: no auth token when needed/not needed, two correct auth tokens for different tenants.
All these cases need some handling. For example, we have to pass tenant id at least somehow. A possible solution is to make http_client accept tenant_id and generate the auth token itself, but that only saves us a call to env.auth_keys.generate_tenant_token, which is not much.


Make JacocoReportAggregationPlugin artifact views cc compatible

By making the given component filter specs are serializable.
Fixes #26922

@bot-gradle test ACC

I've triggered the following builds for you. Click here to see all build failures.

AllConfigCacheTestsPullRequestFeedback build

I've triggered the following builds for you. Click here to see all build failures.

AllConfigCacheTestsPullRequestFeedback build

Your PR is queued. See the queue page for details.


SyntaxError: invalid syntax (related to literal string)

When I run xmltable2csv I get the following error message"
File "/usr/lib/python3.4/site-packages/xmlutils/console.py", line 20
"""
^
SyntaxError: invalid syntax
The offending code is the triple-double quoted string literal as follows
def run_xml2sql():
print """xml2sql by Kailash Nadh (http://nadh.in)
--help for help
"""

What am I doing wrong here? My python is version 3.4, as you can see. I feel I must be making some basic compatibility mistake or some such, as this can not possibly be a real syntax errror, can it?

@reikred Thank you for bug report. Unfortunately, xmltuils is not yet compatible with Python 3. You should be able to use it with Python 2.6 or 2.7.

I see. Yes, that is the problem, and it must be a common one. Should the python version not be checked when installing?
I did some web search and found a construct that supposedly should be included in setup.py, but on my system it was not recognized and caused an error.  What I tried was the syntax
python_requires='>=2.6,<=2.7',
The package maintainers may perhaps know better how to do this?
Reference: http://stackoverflow.com/a/40300957/3854366
http://setuptools.readthedocs.io/en/latest/setuptools.html?highlight=python_requires#new-and-changed-setup-keywords

If the issue lies with print statements only then you can change the format and it should run fine.
Eg - Change print """etc random information
"""
to
print("""etc random information
""")
This will take care of the print statement related issues. Also, can anyone tell me what other issues are there with the code that makes it incompatible with Python3.

I guess changing print statements and iterators should do. You can pass codebase through 2to3 tool and it will take care of all this basic changes.


Marginfigure not correctly placed in LoF

I have had some problems with the LoF. Marginfigures are vertically shifted (placed inter chapter gap) in the ToF and presented in an incorrect order.

By changing the kaobook's definition of marginfigure ...
\newsavebox{\@kao@marginfigurebox}%
\renewenvironment{marginfigure}[1][0pt]{ % The optional parameter is the vertical offset
	%\let\footnotemark\mpfootnotemark
	\FloatBarrier % Force LaTeX to place previous floats
	\mparshift{\snotez@if@nblskip{#1}{\@cdr#1\@nil\baselineskip}{#1}} % Move the figure up or down according to the offset argument
	\begin{lrbox}{\@sidenotes@marginfigurebox}%
		\begin{minipage}{\marginparwidth}%
			\captionsetup{type=figure}%
			% \centering % Better not to center margin figures
}{%
		\end{minipage}%
	\end{lrbox}%
	\marginpar{\usebox{\@sidenotes@marginfigurebox}} % Place the figure box in the margin
}

... back to the one of sidenotes (with minor changes) ...
\RenewDocumentEnvironment{marginfigure} { o }
{
  \begin{lrbox}{\@sidenotes@marginfigurebox}
    \begin{minipage}{\marginparwidth}
      \captionsetup{type=figure}
}
{
    \end{minipage}%
  \end{lrbox}%
  \@sidenotes@placemarginal{#1}{\usebox{\@sidenotes@marginfigurebox}}
}

... is the issue resolved.
I have attached a zip-file with a MWE, modified kao.sty, the output from the original kao.sty and the output from the modified kao.sty
Edit: Included an incorrect code snippet of the correction
ToF_issue.zip

Thank you very much, I think this was the best thing to do! I made similar changes to \margintables and \marginlistings.


update pulsechainV4 symbol to tPLS

Description
Update the symbol for pulsechainV4 from v4PLS to tPLS since the correct symbol is tPLS not v4PLS.
I just noticed that when I was using wagmi with rainbowkit in a NFT marketplace project.
Additional Information

[x] I read the contributing docs (if this is your first contribution)

The core team makes these updates periodically.


Crashes on Heroku

Here's the error:
2015-02-02T20:27:28.201168+00:00 heroku[web.1]: Starting process with command `bin/slackin --port 45132 domain token-goes-here`
2015-02-02T20:27:32.109096+00:00 app[web.1]:
2015-02-02T20:27:32.111335+00:00 app[web.1]: import express from 'express';
2015-02-02T20:27:32.122321+00:00 app[web.1]:     at Module._compile (module.js:439:25)
2015-02-02T20:27:32.122317+00:00 app[web.1]: SyntaxError: Unexpected reserved word
2015-02-02T20:27:32.122323+00:00 app[web.1]:     at Object.Module._extensions..js (module.js:474:10)
2015-02-02T20:27:32.122325+00:00 app[web.1]:     at Object.loader (/app/node_modules/6to5/lib/6to5/register.js:48:16)
2015-02-02T20:27:32.122329+00:00 app[web.1]:     at Function.Module._load (module.js:312:12)
2015-02-02T20:27:32.122326+00:00 app[web.1]:     at Module.load (module.js:356:32)
2015-02-02T20:27:32.122330+00:00 app[web.1]:     at Module.require (module.js:364:17)
2015-02-02T20:27:32.122332+00:00 app[web.1]:     at require (module.js:380:17)
2015-02-02T20:27:32.122333+00:00 app[web.1]:     at Object.<anonymous> (/app/bin/slackin:19:15)
2015-02-02T20:27:32.122335+00:00 app[web.1]:     at Module._compile (module.js:456:26)
2015-02-02T20:27:32.122336+00:00 app[web.1]:     at Object.Module._extensions..js (module.js:474:10)
2015-02-02T20:27:32.111057+00:00 app[web.1]: /app/lib/index.js:6
2015-02-02T20:27:32.114056+00:00 app[web.1]: ^^^^^^
2015-02-02T20:27:32.947903+00:00 heroku[web.1]: Process exited with status 1
2015-02-02T20:27:33.558357+00:00 heroku[web.1]: State changed from starting to crashed

I've been trying this on Heroku and inside of Docker since it was released - this looks like the closest I've gotten so far.

Problem is it's including ecmascript 6 files which apparently Heroku can't handle. I assume that's what the 6to5 business is for, but maybe we need to run node with some flags?

You'll need to go in and change bin/slackin:
-require('6to5/register')({
-  // prevent issues with global installs
-  // and 6to5 ignoring any occurrence of
-  // 'node_modules' by default, including
-  // /usr/local/lib/node_modules, which
-  // makes it noop entirely
-  ignore: false,
-  only: /slackin\/lib\//
-});
+require('6to5/register');

Looks like this was recently changed but not tested on heroku.

Yes - that perfectly fixes the problem. Thanks!

Thank you, I was seeing this as well and it doesn't error once that patch is applied

The require fix works for me, too - thanks so much!


Lets you import scss files from javascript and at the same time compile your sass with the sass() call

Let's allow you to import .scss files into javascript files when you use mix.js() or mix.react() together with mix.sass().
See issue #525

Thanks! :)


CNVkit fails when asking to call SVs in a region

Hello, bcbio developers and users!
Thanks for the excellent framework!
I'm trying to calculate SVs in the linkage region for WGS.
config file:
details:
- algorithm:
    aligner: false
    effects: false
    realign: false
    recalibrate: false
    save_diskspace: true
    tools_on:
    - svplots
    - qualimap
    variantcaller: false
    variant_regions: /hpf/largeprojects/ccmbio/naumenko/project_muscular/62_AF_S5_SV/config/region.bed
    coverage_interval: /hpf/largeprojects/ccmbio/naumenko/project_muscular/62_AF_S5_SV/config/region.bed
    svcaller:
    - cnvkit
    - seq2c
    - delly
    - battenberg
  analysis: variant2
  description: 62_AF_S5
  files:
  - /hpf/largeprojects/ccmbio/naumenko/project_muscular/62_AF_S5_SV/input/62_AF_S5-ready.bam
  genome_build: GRCh37
fc_date: '2017-01-25'
fc_name: muscle2_62-AF
resources:
  default:
    cores: 5
    jvm_opts:
    - -Xms750m
    - -Xmx7000m
    memory: 7G
upload:
  dir: ../final

bed file:
19	1400000	9100000

I've gotten an error:
[2017-04-21T07:05Z] Annotate BED file with gene info
[2017-04-21T07:05Z] sort: write failed: standard output: Broken pipe
[2017-04-21T07:05Z] sort: write error
Traceback (most recent call last):
  File "/home/naumenko/work/tools/bin/bcbio_nextgen.py", line 234, in <module>
    main(**kwargs)
  File "/home/naumenko/work/tools/bin/bcbio_nextgen.py", line 43, in main
    run_main(**kwargs)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 42, in run_main
    fc_dir, run_info_yaml)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 86, in _run_toplevel
    for xs in pipeline(config, run_info_yaml, parallel, dirs, samples):
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 177, in variant2pipeline
    samples = structural.run(samples, run_parallel, "standard")
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/__init__.py", line 169, in run
    for xs in to_process.values()))
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/multi.py", line 28, in run_parallel
    return run_multicore(fn, items, config, parallel=parallel)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/multi.py", line 86, in run_multicore
    for data in joblib.Parallel(parallel["num_jobs"], batch_size=1)(joblib.delayed(fn)(x) for x in items):
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 800, in __call__
    while self.dispatch_one_batch(iterator):
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 658, in dispatch_one_batch
    self._dispatch(tasks)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 566, in _dispatch
    job = ImmediateComputeBatch(batch)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 180, in __init__
    self.results = batch()
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 72, in __call__
    return [func(*args, **kwargs) for func, args, kwargs in self.items]
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/utils.py", line 51, in wrapper
    return apply(f, *args, **kwargs)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/multitasks.py", line 278, in detect_sv
    return structural.detect_sv(*args)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/__init__.py", line 188, in detect_sv
    for svdata in caller_fn(items):
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/cnvkit.py", line 33, in run
    return _cnvkit_by_type(items, background)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/cnvkit.py", line 43, in _cnvkit_by_type
    return _run_cnvkit_single(items[0])
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/cnvkit.py", line 77, in _run_cnvkit_single
    ckouts = _run_cnvkit_shared([data], background)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/cnvkit.py", line 182, in _run_cnvkit_shared
    raw_work_dir, inputs[0])
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/cnvkit.py", line 356, in _cnvkit_targets
    bin_estimates = _cnvkit_coverage_bin_estimate(raw_target_bed, access_bed, cov_interval, work_dir, data)
  File "/home/naumenko/work/tools/bcbio/anaconda/lib/python2.7/site-packages/bcbio/structural/cnvkit.py", line 384, in _cnvkit_coverage_bin_estimate
    "-m", method_map[cov_interval], "-t", raw_target_bed,
KeyError: '/hpf/largeprojects/ccmbio/naumenko/project_muscular/62_AF_S5_SV/config/region.bed'
END:  Fri Apr 21 03:05:58 EDT 2017

Could you please help to figure out, what is wrong?
Sergey

Sergey;
coverage_interval in your YAML file should be either genome, amplicon or regional, not a BED file:
http://bcbio-nextgen.readthedocs.io/en/latest/contents/configuration.html#coverage-information
Generally, bcbio can calculate this for you automatically and you don't need to specify it. You might have meant to specify coverage with this BED file:
http://bcbio-nextgen.readthedocs.io/en/latest/contents/configuration.html#analysis-regions
Hope this helps.


Allow multiple nominations on a member to be active at once

When a staff member runs the nominate command, if the user is already nominated it should not show an error message, instead it should accept the extra nomination. When a user is unnominated it should mark all current active nominations as inactive.
These changes should be reflected in a few places, !tp list and !user (in mod channels) should show number of current nominations.

Stalled by https://github.com/python-discord/site/issues/445


Addition of a new jSerialComm transport

Motivation:
This is an alternative to the Rxtx transport.
One of the main difference is that there is no
native lib installation requirement with jSerialComm
as it handles the native dependencies automatically.
Which makes the deployment/installation less complicated.
Modifications:
Addition of a new transport and associated example code.
A new depndency to jSerialComm
Result:
A new transport is available.

@Ziver first thanks for this PR this looks great. That said I am not sure this should be part of Netty itself and not just another project that implements a custom netty transport. That is because if we merge this we will need to maintain it while not have any possibility to even test the code. This also reminds me that I wanted to mark the serial transport as @deprecated as there we basically have the same problem.
I think transports that ship as part of netty should be easy for us to test and to maintain.

See https://github.com/netty/netty/pull/7200

@normanmaurer that makes sense. I'll put it in its own repo.
Here is the link to the new repo for anyone that would be interested:
https://github.com/Ziver/Netty-Transport-jSerialComm

@Ziver maybe it also makes sense to add it here:
http://netty.io/wiki/related-projects.html

(you can do this by yourself)


Fix indexing 0-dim array with boolean mask

Fixes a part of #503.
This allows boolean mask on a 0-dim array:
a = cupy.ones(())
a[a != 0]

Would you check the CI failure?

Thank you, I fixed the mistake.

jenkins, test this please.

LGTM, I will merge this after I will check the CI passing.


Dashboard 1 attribute form no longer sets null/false values by default

Fixes #4683.
Changelog is unneeded as it was not released yet.
Screenshots

Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] Database migration files are up to date.
[x] The changes are tested.
[ ] GraphQL schema and type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Here is the report for 1be2c2fa309a089271dac96d897f53bfbfaf5cc1 (NyanKiyoshi/saleor @ fix/dashboard-1.0/attributes-form)
Base comparison is b0d57d769da6aed4132e99ea82b9026c78f5548a.
No differences were found. (click me)

# api.benchmark checkout
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  add billing address to checkout     	         34	         34	             20
  add shipping to checkout            	          7	          7	              0
  checkout payment charge             	         14	         14	              0
  complete checkout                   	          6	          6	              0
  create checkout                     	         48	         48	             24

# api.benchmark homepage
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  retrieve main menu                  	          5	          5	              0
  retrieve product list               	          4	          4	              0
  retrieve secondary menu             	          5	          5	              0
  retrieve shop                       	          2	          2	              0

# api.benchmark product
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  product details                     	         13	         13	              3

# api.benchmark variant
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  retrieve variant list               	         15	         15	              8


Targeted dependency update for Pandas 2.1

Manually update the Pandas dependency. Not updating other dependencies since we periodically updating them after a release cut.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damccorm


fix(vue-app): missing layout in error page with splittedChunks.layout

Fix error layout for splittedChunks: { layouts: true }
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Description
Fix loading of error layout
Breaking change ONLY because context.error now although change layout not only in asyncData/etc, for example this change layout
methods: {
  onClick() {
    this.$nuxt.context.error(new Error('Test error'))
  }
}

Resolve: #7654
Resolve: #7658
Resolve: #7014

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[x] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Codecov Report

Merging #8016 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #8016   +/-   ##
=======================================
  Coverage   68.87%   68.87%
=======================================
  Files          91       91
  Lines        3849     3849
  Branches     1044     1044
=======================================
  Hits         2651     2651
  Misses        971      971
  Partials      227      227

Flag
Coverage Δ

#unittests
68.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 a7da6fd...2576ad9. Read the comment docs.

Thanks for PR @Kolobok12309 :100:


Make endpointId be an interface.

This is the first of many pull requests to get all my new code in. I waited because I wanted the confidence that I was headed in the right direction.
This first pull request makes endpointId be an interface in the store package. I thought it was weird that my store implementation was tightly coupled with a concrete type associated with our specific way of pulling metrics.

Instead of passing a generic interface{}, why not pass an interface type which has methods?

In the store package I use endpoint Id only to define an endpoint within
the store. Any go type could serve such a purpose
On Wednesday, March 30, 2016, rgooch<EMAIL_ADDRESS>wrote:

Instead of passing a generic interface{}, why not pass an interface type
which has methods?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Symantec/scotty/pull/29#issuecomment-203511388

If it's just a unique cookie that you want, why not use uint or uintptr?

The client, Scotty, uses *spotty.endpointid
On Wednesday, March 30, 2016, rgooch<EMAIL_ADDRESS>wrote:

If it's just a unique cookie that you want, why not use uint or uintptr?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Symantec/scotty/pull/29#issuecomment-203518250

What if I made endpoint ID be struct { hostName string; appName string }?
These keys will use more space and be slower to look up than a
*scotty.Endpoint wrapped in an interface{}, but the code will be clear, and
I won't need to use a type assertion to get at the hostname and application
name.
Maybe that is an acceptable tradeoff?
Thoughts?
On Wed, Mar 30, 2016 at 9:46 AM, Travis Keep<EMAIL_ADDRESS>wrote:

The client, Scotty, uses *spotty.endpointid
On Wednesday, March 30, 2016, rgooch<EMAIL_ADDRESS>wrote:

If it's just a unique cookie that you want, why not use uint or uintptr?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Symantec/scotty/pull/29#issuecomment-203518250

I still don't understand why you can't use uintptr(*scotty.Endpoint) as your key?

To do that I need the unsafe package. Is saving space the motivation for
using uintptr instead of interface?
On Thursday, March 31, 2016, rgooch<EMAIL_ADDRESS>wrote:

I still don't understand why you can't use uintptr(*scotty.Endpoint) as
your key?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Symantec/scotty/pull/29#issuecomment-204013850


Update README: Added app link and updated icon links

Added official website link for Authenticator Pro and fixed icon links for cromite, medilog and showly.

Thank you! That's great. Merging...


[TOKENOMICS, FOR REVIEW] RPIP-60: Protocol Upgrade Guardrails

Update for RPIP-60. Main changes:

Remove fast-upgrades as a scope reduction.
Add security considerations and rationale sections.
Slightly relax requirements around the veto explanation document.
Rename 'default_upgrade_delay' -> 'upgrade_delay', and clarify it's a pDAO setting.

Looks good to me

I can't put this in as a suggestion in git cuz it bridges a deleted line, but here's some expanded Security and Rational sections. Use in toto or in part as you wish.
## Security Considerations

- The security council veto means it would require both a rogue oDAO and a rogue security council to pass a corrupt proposal.
- The security council veto means that a rogue security council could block a valid proposal.
  - This is mitigated by the pDAO's ability to replace the security council. While the valid proposal could be blocked once, it could not be blocked indefinitely.
- The veto process can itself be modified by contract upgrades. However, if a corrupt proposal tries to change the veto process, that can be defended against by using the veto process.
- Emergency response settings changes should be taken directly by the security council (see [RPIP-33](RPIP-33.md)) rather than use the regular governance process.
- The fastest possible upgrade speed is significantly slowed from the previous state. It used to take `proposal.vote.delay.time` (currently 1 week) and will now take an additional `upgrade_delay` (initially set to 3 weeks). This means that important hotfixes could take a lot longer. It may also mean that emergency pauses (eg, disabling rETH deposits) could last longer until a hotfix takes effect.
- The fastest possible upgrade speed exactly matches the RPL `unstaking_period` defined in [RPIP-30](RPIP-30.md).

## Rationale

**Veto Explanation Document**
The explanation document is a mechanism intended to help the pDAO hold the security council to account for their decision-making around vetos. It gives more information as to the reasoning behind a veto decision, and should help to inform pDAO decision-making post veto. In an ideal world the document accompanies the veto, the 24 hour grace period is intended to cover situations in which the security council must act within a limited time window.

**Upgrade Delay Setting**
Due to the considerations around slowing down hotfixes [described above](#security-considerations), the initial upgrade delay setting is attempting to be the smallest that allows "enough" time for participants to exit the system ahead of a proposal if they deem that appropriate.

Any upgrade will have `proposal.vote.delay.time` (currently 1 week) and `upgrade_delay` (initially set to 3 weeks). This is technically _just_ enough to match the RPL `unstaking_period` (currently 28 days). In normal realistic governance, there will be more time than that: there is a leadup period to sentiment poll (currently at least 1 week), there is a pDAO vote period (currently at least 2 weeks), there's a human action to raise the oDAO proposal, and there are many human actions to place oDAO votes after `proposal.vote.delay.time`. These delays provide some human breathing room to allow participants to exit ahead of a proposal.

One more bullet for secuiryt considerations:

The security council veto means that if pDAO governance were captured, protocol upgrades could be stopped at will (by installing a compromised security council). The oDAO would be unable to pass any contract upgrades (without the approval of the compromised security council), and the only way back would be to recapture pDAO governance. While this means there is a real tradeoff, this "inability to upgrade" is seen as less problematic than the "ability to pass any upgrade" that a rogue oDAO would have without the veto.

@Valdorff incorporated the above, more or less verbatim.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-22-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1269

Questions ?
Please refer to the Backport tool documentation


List of icons for buttons available?

What icons are being used for the buttons. I know you can add them but what is the source of the icons? Fontawesome? Other source?

Hey, you can use any material icon name, but we probably need to make this more obvious in the docs. Maybe I'll put a not below the heading, or if you have any ideas of a good way to convey this, please lmk :) @charlieroth

Yeah my only suggestion would be to just say that the default icons come from Material Icons 👍 @dabit3 . Btw the way thank you for this package.  Can't wait to see what the future holds!

@charlieroth Thanks for the feedback, and thanks for the kind words :) Look forward to growing this project.


dmesg entry "task restic:XXX blocked for more than 120 seconds."

Output of restic version
restic 0.8.3
compiled with go1.10 on linux/amd64

How did you run restic exactly?
export AZURE_ACCOUNT_NAME=XXX
export AZURE_ACCOUNT_KEY=XXX
export RESTIC_REPOSITORY=azure:resticazure:/

restic -p /opt/scripts/restic.pass backup /backup/archiv >> /var/log/restic.log
restic -p /opt/scripts/restic.pass backup /backup/data>> /var/log/restic.log

I'm using Ubuntu 18.04. with 4.15.0-20-generic kernel and ZFS 0.7.5
What backend/server/service did you use to store the repository?
azure account (see above)
Expected behavior
no errors in dmesg.
Actual behavior
each restic command produces an entry in dmesg:
[Apr30 06:31] INFO: task restic:24399 blocked for more than 120 seconds.
[  +0,000064]       Tainted: P           OE    4.15.0-20-generic #21-Ubuntu
[  +0,000053] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  +0,000062] restic          D    0 24399   7157 0x00000000
[  +0,000004] Call Trace:
[  +0,000009]  __schedule+0x297/0x8b0
[  +0,000004]  schedule+0x2c/0x80
[  +0,000003]  io_schedule+0x16/0x40
[  +0,000010]  cv_wait_common+0xb2/0x140 [spl]
[  +0,000003]  ? wait_woken+0x80/0x80
[  +0,000007]  __cv_wait_io+0x18/0x20 [spl]
[  +0,000057]  zio_wait+0xf8/0x1b0 [zfs]
[  +0,000035]  dmu_buf_hold_array_by_dnode+0x15c/0x450 [zfs]
[  +0,000033]  dmu_read_uio_dnode+0x49/0x100 [zfs]
[  +0,000033]  dmu_read_uio_dbuf+0x49/0x70 [zfs]
[  +0,000048]  zfs_read+0x136/0x3f0 [zfs]
[  +0,000047]  zpl_read_common_iovec+0x80/0xd0 [zfs]
[  +0,000044]  zpl_iter_read+0x9c/0xe0 [zfs]
[  +0,000005]  new_sync_read+0xe4/0x130
[  +0,000004]  __vfs_read+0x29/0x40
[  +0,000003]  vfs_read+0x8e/0x130
[  +0,000004]  SyS_read+0x55/0xc0
[  +0,000004]  do_syscall_64+0x73/0x130
[  +0,000003]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  +0,000003] RIP: 0033:0x46c800
[  +0,000002] RSP: 002b:000000c44d575f50 EFLAGS: 00000206 ORIG_RAX:<PHONE_NUMBER>000000
[  +0,000003] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>000000 RCX:<PHONE_NUMBER>46c800
[  +0,000001] RDX:<PHONE_NUMBER>080000 RSI: 000000c45f082000 RDI:<PHONE_NUMBER>00000b
[  +0,000001] RBP: 000000c44d575fa8 R08:<PHONE_NUMBER>000000 R09:<PHONE_NUMBER>000000
[  +0,000002] R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000206 R12: 000000c498d08000

Steps to reproduce the behavior
currently this happens each time I run restic command. Don't know how to reproduce this.
Do you have any idea what may have caused this?
Updated to Ubuntu 18.04 and ZFS 0.7.5.
In Ubuntu 16.04. and ZFS 0.6.x this error was not present.
Do you have an idea how to solve the issue?
I'm sorry no.
Did restic help you or made you happy in any way?
Best backup program ever - love it - keep going :-)

Thanks for the report!
This is not an error in restic, the message means that restic was blocked for more than 120 seconds while waiting on IO. It may very well be the case that restic is the cause for the IO blockage, as it is using a lot of resources in the 0.8.3 release. We've since reworked the archiver code (see #1494), and the next release will be much less resource-hungry.
Would you mind testing this again on the master branch?
You can find compiled binaries of the restic master branch here: https://beta.restic.net/?sort=time&order=desc
I'm closing this issue for now, please report back (and feel free to add further comments). Thanks!


Configure the project's home page

Created a Jobboard Django app and configured a home page for the project.

I've ni idea why you guys are approving this PR! I'm still seeing files named "beyond-tutorial" in this PR. You are not writing a tutorial! You are writing a real project! Please give things proper names!

I now see you already have "beyond-tutorial" files merged in your repo. Not sure who merged that but it shouldn't have passed review. Please mere a new PR to delete all those files and then create your Django project properly from scratch!

I now see you already have "beyond-tutorial" files merged in your repo. Not sure who merged that but it shouldn't have passed review. Please mere a new PR to delete all those files and then create your Django project properly from scratch!

A new PR was created to change the Django project name: #17
Will update this PR accordingly after #17 is merged.

I still see attempts to rename the old file - pelase don't try that - it can cause issues in the long run - please delete the old project files, commit that and then create a new project form scratch

I still see attempts to rename the old file - pelase don't try that - it can cause issues in the long run - please delete the old project files, commit that and then create a new project form scratch

I deleted all of the old project files and created a new project from scratch, not sure why it shows up like I renamed the files.
Should I try to commit the deletion of the project separately? (For a total of 3 commits).

I still see attempts to rename the old file - pelase don't try that - it can cause issues in the long run - please delete the old project files, commit that and then create a new project form scratch

I deleted all of the old project files and created a new project from scratch, not sure why it shows up like I renamed the files. Should I try to commit the deletion of the project separately? (For a total of 3 commits).

yes please. that way I can know this is really what is going on

I still see attempts to rename the old file - pelase don't try that - it can cause issues in the long run - please delete the old project files, commit that and then create a new project form scratch

I deleted all of the old project files and created a new project from scratch, not sure why it shows up like I renamed the files. Should I try to commit the deletion of the project separately? (For a total of 3 commits).

yes please. that way I can know this is really what is going on

Ok, done.

it still looks as if it was renamed. maybe better to split into two PR's?

It just looks that way if you ask to view the cumulative differences from all commits (That is what the "files changed" tab shows you). If you look at the commits individually you can see the full process..

/LGTM


RN 0.63 and navigation 4.0.0

@SandeshVakale Do you know why the tests are failing in CI? Do they pass locally?

Hello @jamonholmgren , I changed node version. now test are passed. If you have any other changes, let me know. Else you can Merge my pull request. thanks

@SandeshVakale thanks for updating to RN 0.63
I've a question about the navigation, does react-navigation v5 still not stable so we just stay at version 4?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Great job @SandeshVakale !

thanks @jamonholmgren


REST examples do not work

The REST examples to create jobs return the error message "ErrorCode:GenericBadRequest;BadRequest".
The reason is the wrong job types "scheduleDirectMethod" and "scheduleTwinUpdate". They do not exist.
It should be "scheduleDeviceMethod" and "scheduleUpdateTwin".
In addition, the "scheduleUpdateTwin" requires an "etag" match.
Here's an example for a payload to update device twin properties: (PUT /jobs/v2/<jobId>?api-version=2018-06-30)
{
    "type": "scheduleUpdateTwin",
    "cloudToDeviceMethod": null,
    "updateTwin": {
      "properties": {
        "desired": {
          "test2": "blabla"
        }
      },
     "etag": "*",
     },
    "queryCondition": "deviceId = 'urn:di:simulator001'",
    "startTime": "2019-04-16T12:19:56.868Z",
    "maxExecutionTimeInSeconds": 20
}

Here's an example of a payload to call a device method:
{
    "type": "scheduleDeviceMethod",
    "cloudToDeviceMethod": {
      "methodName": "someMethod",
      "payload": {},
      "responseTimeoutInSeconds": 10
    },
    "queryCondition": "deviceId = 'urn:di:simulator001'",
    "startTime": "2019-04-16T11:59:59.077Z",
    "maxExecutionTimeInSeconds": 20
  }

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

ID: 2340c222-6f8c-a05b-3bbd-56c786fcd24b
Version Independent ID: 43af3332-8fb6-8f9c-5fd9-a4481f01f8ef
Content: Understand Azure IoT Hub jobs
Content Source: articles/iot-hub/iot-hub-devguide-jobs.md
Service: iot-hub
GitHub Login: @robinsh
Microsoft Alias: robinsh

@rodolfowitsch Thanks for your valuable feedback. I see what you are saying in the section Jobs Properties.  I have assigned the issue to the content author to evaluate and update as appropriate.

Thx, we will fix this and let you know when it's finished.

@rodolfowitsch Thanks very much for your feedback! The updated content is now live: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-jobs . Please let us know if you think further changes are needed. Thanks again for your contribution.

#please-close

Thanks for the updates of the documentation.


TensorFlow Lite 2.8 ARM cross-compilation failed when XNNPACK=ON: unknown type name 'float16x8_t'

System information

Linux Ubuntu 20.04
TensorFlow 2.8
CMake 3.16.3
gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf (here)

Describe the problem
I trying to cross-compile TensorFlow Lite 2.8 with XNNPACK=ON for ARM using CMake. I got error "unknown type name 'float16x8_t'":
...
[ 60%] Building C object _deps/xnnpack-build/CMakeFiles/XNNPACK.dir/src/qc8-gemm/gen/2x8c2s4-minmax-fp32-neonv8-mlal.c.o
make[2]: Entering directory '/home/pi/tflite_build'
/home/pi/tflite_build/xnnpack/src/f16-f32-vcvt/gen/vcvt-neonfp16-x16.c: In function ‘xnn_f16_f32_vcvt_ukernel__neonfp16_x16’:
cd /home/pi/tflite_build/_deps/xnnpack-build && /home/pi/toolchains/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-gcc -DCPUINFO_SUPPORTED_PLATFORM=1 -DEIGEN_MPL2_ONLY -DFXDIV_USE_INLINE_ASSEMBLY=0 -DNOMINMAX=1 -DPTHREADPOOL_NO_DEPRECATED_API=1 -DXNN_ENABLE_ASSEMBLY=1 -DXNN_ENABLE_MEMOPT=1 -DXNN_ENABLE_SPARSE=1 -DXNN_LOG_LEVEL=0 -I/home/pi/tflite_build/xnnpack/include -I/home/pi/tflite_build/xnnpack/src -I/home/pi/tflite_build/clog/deps/clog/include -I/home/pi/tflite_build/cpuinfo/include -I/home/pi/tflite_build/pthreadpool-source/include -I/home/pi/tflite_build/FXdiv-source/include -I/home/pi/tflite_build/FP16-source/include  -march=armv7-a -mfpu=neon-vfpv4 -funsafe-math-optimizations -O3 -DNDEBUG -fPIC   -Wno-psabi -pthread -std=gnu99  -marm  -march=armv8-a -mfpu=neon-fp-armv8  -O2  -o CMakeFiles/XNNPACK.dir/src/qc8-gemm/gen/2x8c2s4-minmax-fp32-neonv8-mlal.c.o   -c /home/pi/tflite_build/xnnpack/src/qc8-gemm/gen/2x8c2s4-minmax-fp32-neonv8-mlal.c
/home/pi/tflite_build/xnnpack/src/f16-f32-vcvt/gen/vcvt-neonfp16-x16.c:31:11: error: unknown type name ‘float16x8_t’
     const float16x8_t vh0 = vreinterpretq_f16_u16(vld1q_u16(i)); i += 8;
           ^~~~~~~~~~~
/home/pi/tflite_build/xnnpack/src/f16-f32-vcvt/gen/vcvt-neonfp16-x16.c:31:29: warning: implicit declaration of function ‘vreinterpretq_f16_u16’; did you mean ‘vreinterpretq_s16_u16’? [-Wimplicit-function-declaration]
     const float16x8_t vh0 = vreinterpretq_f16_u16(vld1q_u16(i)); i += 8;
                             ^~~~~~~~~~~~~~~~~~~~~
                             vreinterpretq_s16_u16
/home/pi/tflite_build/xnnpack/src/f16-f32-vcvt/gen/vcvt-neonfp16-x16.c:32:11: error: unknown type name ‘float16x8_t’
     const float16x8_t vh1 = vreinterpretq_f16_u16(vld1q_u16(i)); i += 8;
           ^~~~~~~~~~~

I able to compile TensorFlow Lite 2.7 with XNNPACK=ON for ARM using CMake.
I using build instructions provided here

@distlibs,
Can you take a look at this issue which discusses about the similar issue and let us know if it helps? Thanks!

@chunduriv
I able to compile TensorFlow Lite 2.7 with XNNPACK=ON. Problems with 2.8.

@chunduriv any news regarding this issue?

Any updates? I've hit the same issue when cross compiling TFlite for ARM?

Could you try to add an additional compiler option "-mfp16-format=ieee", and see whether it will fix the issue? Thx!

Thanks, that fixed it.

@distlibs,
Can you try as suggested here and let us know? Thanks.

I have successfully cross-compiled TensorFlow Lite 2.8 with XNNPACK=ON when I added -mfp16-format=ieee additional compiler option. I think this compiler option should be added in the documentation here.
ARMCC_FLAGS="-march=armv7-a -mfpu=neon-vfpv4 -funsafe-math-optimizations -mfp16-format=ieee"

I have successfully cross-compiled TensorFlow Lite 2.8 with XNNPACK=ON when I added -mfp16-format=ieee additional compiler option. I think this compiler option should be added in the documentation here.

Great to know this works for you :-) We'll fix the doc asap as suggested.

ARMCC_FLAGS="-march=armv7-a -mfpu=neon-vfpv4 -funsafe-math-optimizations -mfp16-format=ieee"

@distlibs,
Thank you for the confirmation. Please feel free to close the issue. Thanks!

I still have this issue with v2.8.0.

For anyone looking back:
While the issue above percists on mainline, I was able to build natively (via docker) for armhf.