Wolfram command for gurkbot

We need a wolfram command ( commonly accessed by !wa ) that accesses the Wolfram API and fetches results in the form of a image based on user queries
I believe i can do it myself as i already have it implemented in my bot
Example:

Need suggestions regarding whether:

Dark mode is needed
labelbar style layout is needed

Refer docs - https://products.wolframalpha.com/simple-api/documentation/

Dark mode could be cool. However, I find it slightly more difficult to read than the standard light mode. If it’s possible to change the background color (to something that’s a bit lighter), I’d like to see how that would look as well.
What is labelbar style?

Dark mode could be cool. However, I find it slightly more difficult to read than the standard light mode. If it’s possible to change the background color (to something that’s a bit lighter), I’d like to see how that would look as well.
What is labelbar style?

I forgot to say, it is indeed possible to change the bg colour - need some testing
Also label bar style in given in the API docs

Ah, I see. Personally, I think the entire picture should be a single image, since that looks a bit more unified.
For background color, I’d say either white or a dark, but not black, color. If you could do some testing with colors, that would be fantastic, and showing multiple (50) shades grey here.

Ah, I see. Personally, I think the entire picture should be a single image, since that looks a bit more unified.
For background color, I’d say either white or a dark, but not black, color. If you could do some testing with colors, that would be fantastic, and showing multiple (50) shades grey here.

it is indeed a single pic - it just looks way neater with the labelbar layout imo
And yes, if this is approved , i will test the colours

Ah, I see. Personally, I think the entire picture should be a single image, since that looks a bit more unified.
For background color, I’d say either white or a dark, but not black, color. If you could do some testing with colors, that would be fantastic, and showing multiple (50) shades grey here.

it is indeed a single pic - it just looks way neater with the labelbar layout imo
the discord bg colour and the colour between the separate headings is the same - hence the illusion
And yes, if this is approved , i will test the colours

yea, if the bgcolor could get the same as discord bg color, then that shall look a lot nicer

Ah, I see. Personally, I think the entire picture should be a single image, since that looks a bit more unified.
For background color, I’d say either white or a dark, but not black, color. If you could do some testing with colors, that would be fantastic, and showing multiple (50) shades grey here.

it is indeed a single pic - it just looks way neater with the labelbar layout imo
the discord bg colour and the colour between the separate headings is the same - hence the illusion
And yes, if this is approved , i will test the colours

yea, if the bgcolor could get the same as discord bg color, then that shall look a lot nicer

I would like to be assigned to this command please :)

I would like to be assigned to this command please :)

I'd like for us to have a direction for the command before coding it, so the reviews won't largely consist of "could we add this field" and "why is that field there." Some details can be tried out, but we should try to understand how most of the command would work first.
How do you think that the embed should look?

I'd like for us to have a direction for the command before coding it, so the reviews won't largely consist of "could we add this field" and "why is that field there." Some details can be tried out, but we should try to understand how most of the command would work first.
How do you think that the embed should look?

I sent the screenshot of the embed in my original issue and that is exactly how I would like it to look

I sent the screenshot of the embed in my original issue and that is exactly how I would like it to look

Alrighty. I appreciate that you gave some thought to the edge case of where no image is returned. Regarding point 4, why would we want that? I'd prefer if we ping the user in the message (set description) and include the embed. That's what we do in the other commands — at least for now.
The title could probably be improved. We have a command on Sir Lancebot (SeasonalBot) that looks like this:

Maybe we could just call it "Wolfram Alpha" as well and the description could be the input, or maybe we should make the title the input. What do you think? I'm not quite sure what a good title would be.

Alrighty. I appreciate that you gave some thought to the edge case of where no image is returned. Regarding point 4, why would we want that? I'd prefer if we ping the user in the message (set description) and include the embed. That's what we do in the other commands — at least for now.
The title could probably be improved. We have a command on Sir Lancebot (SeasonalBot) that looks like this:

Maybe we could just call it "Wolfram Alpha" as well and the description could be the input, or maybe we should make the title the input. What do you think? I'm not quite sure what a good title would be.

If you are typing the command you probably know what you are searching for so I mean adding the search in the title would be unnecessary but let's see what others think

If you are typing the command you probably know what you are searching for so I mean adding the search in the title would be unnecessary but let's see what others think

Alrighty. I appreciate that you gave some thought to the edge case of where no image is returned. Regarding point 4, why would we want that? I'd prefer if we ping the user in the message (set description) and include the embed. That's what we do in the other commands — at least for now.
The title could probably be improved. We have a command on Sir Lancebot (SeasonalBot) that looks like this:

Maybe we could just call it "Wolfram Alpha" as well and the description could be the input, or maybe we should make the title the input. What do you think? I'm not quite sure what a good title would be.

Regarding the title, it is indeed true, the query part in the author section of the embed is not needed. Also, i will not include
the footer with the name, timestamp , etc - I am just used to it :)
I will heed your advice and will implement it if i do get approved for working on this

Alrighty. I appreciate that you gave some thought to the edge case of where no image is returned. Regarding point 4, why would we want that? I'd prefer if we ping the user in the message (set description) and include the embed. That's what we do in the other commands — at least for now.
The title could probably be improved. We have a command on Sir Lancebot (SeasonalBot) that looks like this:

Maybe we could just call it "Wolfram Alpha" as well and the description could be the input, or maybe we should make the title the input. What do you think? I'm not quite sure what a good title would be.

Regarding the title, it is indeed true, the query part in the author section of the embed is not needed. Also, i will not include
the footer with the name, timestamp , etc - I am just used to it :)
I will heed your advice and will implement it if i do get approved for working on this

What title do you think would fit? Any ideas?

What title do you think would fit? Any ideas?

The title of the embed from python discord is good enough I suppose.
If anyone else has any other ideas, they can pitch in

The title of the embed from python discord is good enough I suppose.
If anyone else has any other ideas, they can pitch in

Alright. I think we have a clear enough understanding of the command now. I'll assign you; thanks!

Alright. I think we have a clear enough understanding of the command now. I'll assign you; thanks!


Further production cleanup for ActiveRecord

Cleanup for a few new issues I’ve noticed moving the ActiveRecord changes into production.

Ok, I think I’m done adding things here. It runs alright with both a web and worker dyno on my own Heroku test account.

Gonna go ahead and merge this.


Hello amazing guy,how to judge model has already converged when training?

You can plot the validation performance (using tensorboard) and see whether the curve is saturated.

thx for reply


Train gets out from track after stopping

Expected Behaviour
Follow the tracks and never get off
Actual Behaviour
The car is out of the track after stopping
Screenshots
https://drive.google.com/file/d/101s72nmEfQhhFEeJIaiJIpAmZsfa_5LF/view?usp=sharing
(Bug starts at 0:09)

Thanks for posting this! It is a known issue and can be temporarily resolved if the platform's length is increased to match the length of the train. I will work on a better fix in the future, so I'll keep this issue open for now.

Thanks for posting this! It is a known issue and can be temporarily resolved if the platform's length is increased to match the length of the train. I will work on a better fix in the future, so I'll keep this issue open for now.

This should be fixed in beta-5. Please let me know if you encounter other issues, thanks!


[CDEC-517] Parallelize the generator, wallet-new and wallet tests

Description
Some of the package's tests are very slow. This could be sped up by utilizing the parallel function from the hspec library where Spec tests are written. In order to take advantage of multiple cores, I wrote a function parallelize in Test.Pos.Util.Parallel that gets the number of processors from the machine and sets the number of threads equal to the number of processors on the machine.
Linked issue

https://iohk.myjetbrains.com/youtrack/issue/CDEC-517
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[x] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[x] I have read the style guide document, and my code follows the code style of this project.
[x] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

QA Steps

Screenshots (if available)

Closed due to rebase/merging complications: https://github.com/input-output-hk/cardano-sl/pull/3497/commits


tests: turn off watchdog for sam_e70 test kernel/critical

Wrong configuration of a watchdog in v1.14-branch for sam_e70_xplained_board caused
endless reboot loop. During tests I found out that if to decrease
NUM_MILLISECONDS numeric constant from 5000ms to 4000ms, then
test will complete successfully. It seems that problem caused by
a watchdog.
So to solve that issue were 2 variants. First is to make constant
NUM_MILLISECONDS less than 5000, for example 3000 or 4000.
Second variant to disable a watchdog using new config for the board
CONFIG_WDT_DISABLE_AT_BOOT=y
I decided to use second variant and created a new config file
for the sam_e70_xplained hardware board.
Signed-off-by: Maksim Masalski<EMAIL_ADDRESS>

@pabigot I did that fix for the board sam_e70_xplained. Please take a look.

My way to fix #20603

Also I agree with @ioannisg: this should target master. I don't think this is worth changing in the LTS release. That, though, should be informed by some sort of policy.

@pabigot , I think I might have been using too complex and confusing syntax :(
I wanted to say that we should probably do what we already do in master branch:
Below is the test-case .yaml file.
tests:
  kernel.critical:
    platform_exclude: nsim_sem_mpu_stack_guard nsim_em_mpu_stack_guard
    filter: not CONFIG_WDT_SAM
  kernel.critical.sam:
    filter: CONFIG_WDT_SAM
    extra_configs:
     - CONFIG_WDT_DISABLE_AT_BOOT=y
  kernel.critical.nsim:
    platform_whitelist: nsim_sem_mpu_stack_guard nsim_em_mpu_stack_guard
    extra_configs:
      - CONFIG_TEST_HW_STACK_PROTECTION=n

I remember solving this issue myself for 2.0 release.

@maksimmasalski @pabigot it is OK to solve this also in the LTS - no objection to improving the test suite in 1.14.x as well.

@ioannisg I created new PR for that fix to the master. Because for that PR I used a parent v.1.14-branch, and it is unable to directly merge fix created in that branch with a master.

@ioannisg I created new PR #20646 for that fix to the master. Because for that PR I used a parent v.1.14-branch, and it is unable to directly merge fix created in that branch with a master.

@maksimmasalski  @ioannisg  is suggesting to fix this the same way it is fixed in master:
  kernel.critical.sam:
    filter: CONFIG_WDT_SAM
    extra_configs:
     - CONFIG_WDT_DISABLE_AT_BOOT=y

@ioannisg I created new PR #20646 for that fix to the master. Because for that PR I used a parent v.1.14-branch, and it is unable to directly merge fix created in that branch with a master.

@maksimmasalski @ioannisg is suggesting to fix this the same way it is fixed in master:
  kernel.critical.sam:
    filter: CONFIG_WDT_SAM
    extra_configs:
     - CONFIG_WDT_DISABLE_AT_BOOT=y

That why I decided to fix it in branch v1.14-branch, because here it is not fixed and test can't complete successfully. I think my PR#20646 is useless for master.

Ah, I understand idea. Just copy from master fix to the branch v1.14-branch. Hah, that makes sense.

Nice, and sorry for the confusion. You need to copy the filter to the main test-case, as well, so you can exclude the SAM platform.

Actually, now that I see this: why is it copied in the tests/kernel/common?
Also - could you copy the filter to the default test? filter: not CONFIG_WDT_SAM

My fault, should be in critical.

@ioannisg I added it, but it is not working.
Only working variant is a separate prj_sam_e70_xplained.conf file fixes that issue.

change is fine, but now i see that the tests have been renamed from .common to ,critical in master branch. So i wonder if you should do the same here. Now the added test-case name is inconsistent with the rest

I modified right now name of the test from criticial to common, made it aligned with another test names.

@ioannisg
Same issue on master has been fixed. Do I need just backport master patch to 1.14 branch?

I have noticed that, for some SoCs (e.g. wdt_sam.c, wdt_sam0.c, wdt_mchp_xec.c), watchdog is activated during SoC reset or driver init, while, for others (e.g. wdt_nrfx.c, wdt_mcux_wdog.c), watchdog is activated after the driver setup function is called (i.e. not as part of OS initialisation).
For instance, the SAM 7 series SoC watchdog timer is activated by default after SoC reset because WDT_MR.WDDIS=0 on reset. while the nRF series SoC watchdog timer is deactivated by default unless the driver setup function is called.
This means that we have two possible states for the watchdog after OS initialisation, across different SoCs when CONFIG_WDT_DISABLE_AT_BOOT=n (note that wdt_nrfx.c, for instance, does not enable watchdog when CONFIG_WDT_DISABLE_AT_BOOT=n).
There could be two potentially feasible approaches to fixing this not-so-well-defined behaviour:

Enforce watchdog timer state based on CONFIG_WDT_DISABLE_AT_BOOT during driver init.

For SoCs that enable WDT by default: Disable WDT when CONFIG_WDT_DISABLE_AT_BOOT=y
For SoCs that disable WDT by default: Enable WDT when CONFIG_WDT_DISABLE_AT_BOOT=n
For both types of SoCs, in case of CONFIG_WDT_DISABLE_AT_BOOT=n, configure WDT using the default WDT configurations defined in Kconfig (if not defined, define them).

Make CONFIG_WDT_DISABLE_AT_BOOT default y and assume that WDT is disabled after OS initialisation by default (i.e. define this as the "standard" behaviour).

Reserve CONFIG_WDT_DISABLE_AT_BOOT=n as a special case for the SoCs that enable WDT by default after reset (do not enforce this as "enable at boot" for the SoCs that do not enable WDT after reset).
This special case serves as a fail-safe mechanism in case of an OS boot failure.
Leave the default WDT configurations at the mercy of the SoC default reset state. The rationale is that, if an SoC enables WDT on reset, other WDT configuration reset states would have been defined so as to allow a fail-safe reset.

While the first approach would be the most comprehensive; in terms of practicality, the second approach would make more sense.
In terms of this issue, if we take the first approach, we should CONFIG_WDT_DISABLE_AT_BOOT=y in prj.conf; for the second approach, there would be no need to specify CONFIG_WDT_DISABLE_AT_BOOT=y as it is default y.

I have noticed that, for some SoCs (e.g. wdt_sam.c, wdt_sam0.c, wdt_mchp_xec.c), watchdog is activated during SoC reset or driver init, while, for others (e.g. wdt_nrfx.c, wdt_mcux_wdog.c), watchdog is activated after the driver setup function is called (i.e. not as part of OS initialisation).
For instance, the SAM 7 series SoC watchdog timer is activated by default after SoC reset because WDT_MR.WDDIS=0 on reset, while the nRF series SoC watchdog timer is not activated by default unless the driver setup function is called.
This means that we have two possible states for the watchdog after OS initialisation, across different SoCs when CONFIG_WDT_DISABLE_AT_BOOT=n (note that wdt_nrfx.c, for instance, does not enable watchdog when CONFIG_WDT_DISABLE_AT_BOOT=n).
There could be two potentially feasible approaches to fixing this not-so-well-defined behaviour:
1. Enforce watchdog timer state based on `CONFIG_WDT_DISABLE_AT_BOOT` during driver init.

   * For SoCs that enable WDT by default: Disable WDT when `CONFIG_WDT_DISABLE_AT_BOOT=y`
   * For SoCs that disable WDT by default: Enable WDT when `CONFIG_WDT_DISABLE_AT_BOOT=n`
   * For both types of SoCs, in case of `CONFIG_WDT_DISABLE_AT_BOOT=n`, configure WDT using the default WDT configurations defined in Kconfig (if not defined, define them).

2. Make `CONFIG_WDT_DISABLE_AT_BOOT` `default y` and assume that WDT is disabled after OS initialisation by default (i.e. define this as the "standard" behaviour).

   * Reserve `CONFIG_WDT_DISABLE_AT_BOOT=n` as a special case for the SoCs that enable WDT by default after reset (do not enforce this as "enable at boot" for the SoCs that do not enable WDT after reset).
   * This special case serves as a fail-safe mechanism in case of an OS boot failure.
   * Leave the default WDT configurations at the mercy of the SoC default reset state. The rationale is that, if an SoC enables WDT on reset, other WDT configuration reset states would have been defined so as to allow a fail-safe reset.

While the first approach would be the most comprehensive; in terms of practicality, the second approach would make more sense.
In terms of this issue, if we take the first approach, we should CONFIG_WDT_DISABLE_AT_BOOT=y in prj.conf; for the second approach, there would be no need to specify CONFIG_WDT_DISABLE_AT_BOOT=y as it is default y.

Thank you for such a detailed comment.


Querying fields of type NUMBER(20,0) causes ORA-03120

We are storing pretty large numbers, yet still in the 64bit range.
When performing a SELECT them over them (they are stored in a NUMBER(20,0) field) we get
ORA-03120: two-task conversion routine: integer overflow
We're currently debugging it to try to give more information, but we thought you should know and maybe have an idea.

Enclose this column with ROUND(...) is a workaround I use for this issue

last version v2.7.16 fix some number decoding please try again and see if issue fixed

Sorry got side tracked on this. I'll try
On Fri, 25 Aug 2023, 00:59 Samy Sultan, @.***> wrote:

last version v2.7.16 fix some number decoding please try again and see if
issue fixed
—
Reply to this email directly, view it on GitHub
https://github.com/sijms/go-ora/issues/418#issuecomment-1692520572, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALKLW3G532QF2MHUVFXX2TXW7MGTANCNFSM6AAAAAA3C6JODM
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix: domain input ui/ux

What is the purpose of this pull request?

What problem is this solving?

Types of changes

[ ] Feat: (new functionality)
[ ] Bug fix: ([#ref number] non-breaking change which fixes an issue)
[ ] Chore: (improvements that will not reflect in production behaviour)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires change to documentation, which has been updated accordingly.

#124  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @keeganpotgieter and the rest of your teammates on  Graphite


Add links to Gentoo Guru

Signed-off-by: Vitaly Zdanevich<EMAIL_ADDRESS>

Oh I need to sign the commit...

Not sure that dev/alpha linux version should be promoted here

You can introduce git tags for versions.


Intersect between SpatialLines and AbstractRaster

Dear @rafaqz
Any idea how to calculate the intersection between SpatialLines and AbstractRaster?
It is valuable for cross section analysis, e.g., https://unidata.github.io/MetPy/latest/examples/cross_section.html.
Regards.

Can you explain a little more what you mean? Its not something I've done. Give me an example of the data you have and what the result should be.

Taking geopotential height as example:
The Input:

Raster: with the dim of [nlon, nlat, ntime, nlev]
SpatialLine: a SpatialLine object

The expected Output:

cliped_data: with the dim of [npixel, ntime, nlev]; npixel is the overlaped pixels between SpatialLine and Raster.
xdim: , the dimension of npixel, the distance from the overlaped pixel to the origin of SpatialLine.

Do you have any suggestion how to implement this function, and which package or which function should be used?
Thank u!

Im just working on line clipping and distance from a line literally right now. So Rasters.jl should be able to do that in a few weeks... If you want to write the distance from a line algorithm that would be a huge help.
GeoInterface.jl for lines, and maybe NearestNeighbors.jl ?

To further clarify, is your line 2d or 3d?

It is a really good news.
It is 2d SpatialLine in my case.
I'd like to involve in. Could you tell me where is the function working in process?

Great! Be good to have some help.
Its a work in progress, on my my methods_cleanup branch where I'm reorganizing raster/polygon methods, and trying to make all the polygon operations better and more consistent. Sorry it has too many changes in one PR, its just everything I need to be working for my own work right now so I cant separate it out.
There is a basic but fast 2d line drawing algorithm here, like a graphics method where we just take the angle of the line and bump x/y int counters along it to burn the line into the raster:
https://github.com/rafaqz/Rasters.jl/blob/methods_cleanup/src/polygon_ops.jl#L156-L208
That's what will be used to mask and rasterize lines. When it's a BitArray with some subset of dimensions, we can just broadcast it over all the other dimensions like elev/time to mask or rasterize it into them. If you just need the points extracted but we could also make it return points.

dear @rafaqz and @kongdd,
we are doing something similar in the coding exercise you'll find here: https://github.com/DavideFavaro/Tirocinio/blob/master/Porting/Porting Envifate/Envifate/src/Tools/Noise.jl (it is our personal basic viewshed algorithm for multiple lines intersecting a raster from an origin, dtm in our case). it's valid for both directions (e.i. start-end && end-start)
best regards

Hey thanks! but there's a lot of code in that file... could you link the specific lines?

not simple with my old phone now..., i'll be back tomorrow, bye

after some commits  (@davidefavaro) I found the function bouncing from noise pollution to light pollution here: https://github.com/DavideFavaro/Tirocinio/blob/be1c5c2fd79fe9bc15f28cfa363389d7860cf645/Porting/Porting Envifate/Envifate/src/Tools/do_light.jl#L403, but the profiles and distances sections start here (we deliberately neglected to rasterize the segments, because in our case study we intend to use this also for the comparison between segments and vectors, for example to verify the attenuation of the sound intensity with respect to different land uses): https://github.com/DavideFavaro/Tirocinio/blob/be1c5c2fd79fe9bc15f28cfa363389d7860cf645/Porting/Porting Envifate/Envifate/src/Tools/Noise.jl#L751
I think (@davidefavaro) we can achieve some more compact and readable code in few days..

This works now in extract, you can just extract any kind of geometry from a Raster/RasterStack and get a table (vector of NamedTuple) back

Thanks for your hard work.


[BEAM-1345] Add an @Internal Annotation

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

This annotation is used as a marker that a publicly accessible API is
intended for internal use and should not be used by users, and is
subject to no compatibility guarantees.

R: @kennknowles

LGTM. We should make the short text of anything annotated with this say only that it is for internal use only and could break any time.

Coverage remained the same at 69.856% when pulling 7b3cce4da29bad280e42e2490ee3dc4ef5d4f763 on tgroh:add_internal_annotation into 43443c94f5933698ec49648abd9e939eda0a7460 on apache:master.


Using look_at or look_to to make a sprite face directly up makes that sprite dissapear.

Rotating the sprite straight up manually seems to work fine, but using look_at or look_to seems to cause odd behavior.

That's interesting. What odd behaviour are you seeing specifically, and is the thing you're trying to look_at the camera?

If the sprite is disappearing entirely, the two most likely things to mind would be either if you're looking at it edge-on, or if you're looking from behind and double_sided is disabled. Possibly also if the pivot is in a weird place, the rotation could be "translating" it to somewhere you can't see - though that's less likely.

I don't think its a looking at it edge-on problem. I'm also fairly certain it isnt due to double_sided being disabled, since its enabled by default, and I didn't change it.
I believe I also checked the underside of the sprites, as well.
It could be pivot oddness. I'm not sure. I didn't mess with the pivot, though.

Huh that is strange. Do you think you could post a minimum reproducible sample?

yeah, okay
so basically make a project as simple as possible that causes the issue?

Yep, exactly

Closing as inactive. Feel free to reopen if this happens again!


[WIP] Jupyter support

Started this some weeks ago and forgot to push the updates...
Almost got it working, but still needs some clean up and some things were still buggy...

This should be addressed in https://github.com/SimonDanisch/JSServe.jl/pull/118


Match waarnemingen.be species to GBIF

Input file is at https://github.com/LifeWatchINBO/alien-species-checklist/blob/master/reference-datasets/natuurpunt/waarnemingen-be-species.csv

This issue is tackled in another repository: https://github.com/inbo/data-publication-natuurpunt/issues/62 Closing here.


Add ability to export / import Brainly Tools Configuration

Is your feature request related to a problem? Please describe.
...
This feature request is not related to my problem but It would be convenient if you add feature to export settings.
Describe the solution/idea you'd like
...
There is a feature to export and import settings so people don't need to re configure the settings.
Describe expected outcome from your solution
...
I expect there is a feature to make people who use more than one computer or device will easier to configure the tools without reconfigure again from scratch

Hi @HerendraTJ
I think B. Tools can save settings and share them with all of your devices. Just like the personal note feature

Btools cannot have sync so when I going to install to my new OS and new browser, I need to reconfigure all the settings.

It doesn't sync configuration right now but in the future; it can have that ability. It's possible :)

@seahindeniz I use B. Tools on Brainly Brazil and I want to know how can I contribute to improve this project. I'm a newcomer in both GitHub projects and programming JS/TS but I'm here to learn. If you are available, I'd really appreciate if you could give me some guidelines on this work.

Hey @juanbomfim22 !
Thanks for the offering. I would love to use your help but unfortunately this issue is server related and server repository isn't a public one. So I don't think I'm going to make it public or share the repository due to security related issues.
I hope you can agree.
Also, there is no guidelines of how to contribute to this project. I mostly spare my time for maintaining and creating a guideline, most likely is no go for me either, sorry about this :/

@seahindeniz
Oh... I think I got it.
So, correct me if I'm wrong: are you not able to receive any help from another contributor? Or just in this specific server related issue?
I understand the concern about the restricted server repository thing and there's no problem to keep it private for you.
But speaking of the issues any person can colaborate, I'd like to know if there is some I personally could work on. Nevermind about creating or having a guideline for the hole project, I know it can be time-waster sometimes.
Just clarify me, in case of existing 'open source issues' , wheter there is anything (even the most simple things) I can help you with in my these last free weeks, and, in positive case, what it should be.

So, correct me if I'm wrong: are you not able to receive any help from another contributor? Or just in this specific server related issue?

Well, that's kind of depends on the case.
These are yes:

If it's related to extension server(unless I participate)
If it's required extra intention from Brainly side. (like API/endpoint related cases)
If the case would require most of my time and I'm already working on another case

Just clarify me, in case of existing 'open source issues' , wheter there is anything (even the most simple things) I can help you with in my these last spare weeks, and, in positive case, what it should be. In negative, no problems.

You can search up open issues that look good for you and you can try to implement it. Well, at least that is how I'm working.

I must say that I won't be that helpful because as I said I have pretty much zero experience in projects, but my goal is to learn as much as I can.

I appreciate your effort.
But I have to clarify, the purpose of making the source public, is to show how it's coded and ensure other developers that it doesn't contains any malicious code. My only concern is this.
You can of course fork it and pull it locally and work on it. But I most likely comes with a warning, because, to work locally, the extension will require an extension server that runs locally or an extension id which will be added to the white list in the main extension server

Nice!!
I already have access to some functionalities of the extension on BR server, i.e. moderating content and approving questions (but not for deleting in bulk).
So, do you mind telling me if there are the additional confs to try to work on a specific issue since I have this access?

There is no additional configuration required by Brainly. You just need to use your imagination and your ideas

Fine! Look, I've found the pt-BR.json file to be translated and I want to
know if you are already working on its translation. I've already done some
lines and it's fine for me to keep doing that as a starting point. What do
you think?
Em sáb., 5 de set. de 2020 às 19:00, Sahin D<EMAIL_ADDRESS>escreveu:

There is no additional configuration required by Brainly. You just need to
use your imagination and your ideas
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/seahindeniz/BrainlyTools_Extension/issues/169#issuecomment-687668478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANG2O4NQXVJDO242MKGIQELSEKYHZANCNFSM4QO2UBWA
.

Language files in this repository are generated. We are using Lokalise to translate the extension to other languages.
Your community manager has already asked that job and has access to the platform but hasn't start translating. You can ask green light from them if you like


Add catching C++ exception support to dwarfeh.d

Requires:
https://github.com/D-Programming-Language/dmd/pull/5342

BTW, will be this exception handling work with some another c++ compilers? clang++? intel c++ compiler?

will be this exception handling work with some another c++ compilers? clang++? intel c++ compiler?

My understanding is that they are binary compatible with g++, so they should work.

My understanding is that they are binary compatible with g++, so they should work.

Are they use the same libstdc++ implementation? Otherwise there can be another virtual method order in std::type_info for example.

You can be binary compatible and yet have a different implementation. Again, my understanding is they are binary compatible.

You can be binary compatible and yet have a different implementation. Again, my understanding is they are binary compatible.

Sounds good. It remains to deal with dmc and Visual Studio :)

thx!


DCOS-56894: Fix Sidebar open/close toggle bugs

Bugs fixed:

The Sidebar would not toggle closed when sidebarWidth was set in the AppChrome theme
The Sidebar open/close animation was broken
styled was being called in the render method, which hurts React performance

Testing:

Go to the story called "Sidebar Customizable w/ Knobs"
Uncheck the "isOpen" checkbox
Confirm the Sidebar opens and closes, and animates when it does

Screenshots:
Before - toggle bug:

After - toggle bug:

Before - animation bug:

After - animation bug:

For me, both in Firefox and in Chrome, there is some delay after clicking the button and the animation is kind of fast so it looks like it disappears and appears suddenly instead of gradually.
Firefox

Chrome

@GeorgiSTodorov - I think that's specific to the way Storybook knobs cause a re-render of the story. Does it behave that way when you click the "☰" in the header of the "AppChrome DCOS clone" story?

@mperrotti , then it's kind of fast, but still fine.


debian package postgresql-contrib virtual package

Debian family provides postgresql-contriub-XY as a virtual package of postgresql-XY.
Not sure if allowing virtual packages here is the best solution :thinking:
Referencies:
https://packages.debian.org/bullseye/postgresql-contrib-13
https://packages.ubuntu.com/bionic/postgresql-contrib

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Code wise this looks good to me. I started the tests and if they're green this should be merged. Thanks!

@ekohl can you help me? I don't know why some of them where canceled :(

Looks like they timed out but I think it's safe to ignore those so I'm going to go ahead and merge this. Thanks @carlosduelo!


integrations: Enhance Grafana integration with alert state

Having the alert state in the message body is useful when alert topics are not defined by alert description but encoded in url.
E.g. in large environments having a topic for each alert [alerting] and [ok] would make it harder to properly track if an alert has been resolved.
When each alert is in a single topic, so far, the alert state has been missing.
This change will add the current alert state and a fitting icon in front of the alert name. (Similar to the prometheus alertmanager integration)

Feature enhancement, no issue existing.
Testing plan:
Tested with development instance on current master,
also tested on a prod env running 3.4
Linted with ./tools/lint
Gitlab Actions are also all green.
GIFs or screenshots:

This is an improvement/duplicate of #18372 now with added tests.

@adambirds I have removed that line, and it still passes all the tests

Merged, thanks @AdamVB and @adambirds!

(Also added this to the 4.x branch, so you can get this with upgrade-zulip-from-git 4.x if you're self-hosting; and then it'll be in the 4.3 release).


Locks

Coverage decreased (-0.28%) to 94.5% when pulling 1bbdd4c14c871ee8d7bbbd61c3dca9c3e1b0fd6c on isocolsky:locks into 49de272cbdd741fcd74def67c243812741de6891 on bitpay:master.

Coverage decreased (-0.26%) to 94.52% when pulling 8e259c0e09ae1a51dda96c9a572fdb0944e64e2b on isocolsky:locks into 49de272cbdd741fcd74def67c243812741de6891 on bitpay:master.

Coverage decreased (-0.26%) to 94.52% when pulling 34790ec2e247b19bbf979594370ea695181d57eb on isocolsky:locks into 49de272cbdd741fcd74def67c243812741de6891 on bitpay:master.

Coverage decreased (-0.25%) to 94.52% when pulling 59996ef073a4352ecc99c5f6b79ecbd9443426e0 on isocolsky:locks into 49de272cbdd741fcd74def67c243812741de6891 on bitpay:master.

Great job!!


Add FIPS indicators to X25519 and X448.

X25519 and X448 are unapproved in FIPS 140-3
So always trigger the indicator callback if these Keys are used, and add "fips-indicator" getters that return 0.
This has been added to keygen and key exchange.
(KEM will also require it if ever becomes a FIPS algorithm).

Checklist

[x] documentation is added or updated
[x] tests are added or updated

Formatting CI seems relevant.

Cross Testing PR against master is not a relevant test

This pull request is ready to merge

Merged!


jest no longer works with Node?

I just created a "Hello World" sized project with jest, and it failed with:
SyntaxError: node_modules/jest-cli/node_modules/jsdom/lib/jsdom.js:3
`jsdom 4.x onward only works on io.js, not Node.js™: https://github.com/tmpvar
^
Unexpected token ILLEGAL

I am using Node 0.12.0. Does jest have a transitive dependency that requires io.js? /cc @jeffmo

Latest releases .50 and up do not work with node only io.js. This is in partial due to the upgrade to the latest JSDOM which dropped support for node. You'll need to use io.js to run on .50, or use .10.x on a .4 branch of jest.
Also once node 4.0 is released that will be the ultimate version that gets supported.

Jest does not support node 0.12. Please use jest 0.4 with node 0.10 or jest 0.5 with iojs v2 and up.

Is there a plan to support Node 0.12 or at least document it in the README.md? Presumably most people get Node by going to https://nodejs.org/, which means they end up with Node 0.12.

Feel free to send a pull request mentioning this. There are no plans to support node 0.12 as it is basically dead. The next version will be node 4.0 which will be based off of iojs 3.0


added some awesome cheatsheets

added some famous cheatsheets  that will help developers

I'm not planning to add this category at the time being. Please open an issue or a feature request next time before submitting a new category. Thanks!


30ignition: remove initramfs networking

Add coreos-remove-initramfs-network.service to run after ignition
has finished using initramfs networking, so NetworkManager properly
brings up ignition-configured networking in the real root. Otherwise
the initramfs network persists into the real root.
Signed-off-by: Yu Qi Zhang<EMAIL_ADDRESS>

This looks fine to me for spec2x.
Higher-level, I think it'd be great if we only actually brought up networking if we needed it (i.e. if Ignition needs to fetch a config over the network). Then this new service would be conditional on that as well. Anyway, we can definitely leave that for later!

Added fixups and comments, also confirmed that dhcp still works with a base ignition conf, as well as if the service fails, we drop into emergency shell so the dependency checks out. Also did some investigation into dhclient but AFAICT its not running and will not try e.g. re-leasing


Research and stabilize respond_to semantics

http://mojolicio.us/perldoc/Mojolicious/Controller#respond_to
This method is still marked as EXPERIMENTAL because we've not yet decided what's the best way to handle the Accept header for content negotiation.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Usually we would just go with spec compliance, but many browsers such as Chrome 11 are notorious for not knowing what exactly they want and just give xml a higher quality value than html.
https://bugs.webkit.org/show_bug.cgi?id=27267
Therefore we currently ignore all unspecific Accept headers with more than one MIME type.

Ignoring unspecific accept headers seems the most reasonable option to me.  I can't think of a reason why any client but a browser would specify more than one mime type.
The only other option is to give preference to the browser (breaking Chrome 11 and Firefox 2) or to the app (interpreting respond_to input as a list instead of a hash).
Choosing either one renders (pun!) the other useless, and would cause more confusion and problems.

How about we change the experimental note to say something like "Note that the Accept header detection feature of this method is EXPERIMENTAL and might change without warning!"?

We have unanimously decided to stabilize respond_to the way it is. https://github.com/kraih/mojo/commit/9733a6df1d24325afd22b3ae93e3a18fda32175d


Unskip ambient tests for jwt-claim-route and autopassthrough.

Please provide a description of this PR:
I took a look at the existing Traffic test cases to confirm which cases need to skip Ambient still and which don't. I've identified jwt-claim-route and autopassthrough as not having to skip ambient anymore. Basically, there is no difference when changing to RunCase from RunSkipAmbient for those particular test cases. Also, added a matcher for a waypointed service and a captured service to validate these cases actually run through Ambient.
Related to #43698

@MorrisLaw: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
2973ddedf09481668392aca4f75043d648759020
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest-required

LGTM athough I think the captured match is potentially broken:
        --- PASS: TestTraffic/jwt-claim-route/matched_with_nested_claims:200 (0.57s)
            --- PASS: TestTraffic/jwt-claim-route/matched_with_nested_claims:200/to_b (0.40s)
            --- PASS: TestTraffic/jwt-claim-route/matched_with_nested_claims:200/to_waypoint (0.09s)

We're only getting b and waypoint

@MorrisLaw: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
2973ddedf09481668392aca4f75043d648759020
link
unknown
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Improve docstring for the plot method

Is your feature request related to a problem? Please describe.
Currently the plot method defined in _Trochoid has fairly light documentation.
It is essentially a wrapper around matplotlib.pyplot.plot as it just passes the kwargs from plot down into matplotlib but I feel the current docstring could be improved to provide more context

Hi @chris-greening ,
Hope you're doing well! I am an experienced python developer who is looking to contribute the open source for the first time.
I found this package interesting and your contribution notes drew my attention as it encourages and welcomes first time contributors.
I am looking to know some insights with respect to this issue like where to get started and what exactly is needed.
Thanks,
Nishanth.

Heyo @NishanthMuruganantham thanks so much for reaching out!! I love helping new contributors break into open source so always feel free to reach out for questions/advice/etc!
Let me know if you're interested in having this Issue assigned to you, I'd be more than happy to help walk you through this process
Background on the project
The project has an abstract base class at the core named _Trochoid that defines a lot of the general behavior in the public user-facing library i.e. the Hypotrochoid and Epitrochoid classes that inherit from it
Based on the user input arguments R, r, d, thetas, etc. these will internally be used to calculate instance attributes x and y which are arrays of associated coordinates calculated by the parametric equations
Background on the plot method
The aforementioned _Trochoid class has a plot method that plots these x and y coordinates using matplotlib. I wrote a blog post here that could serve as a good starting point to understand what the method does with some concrete examples
Since this leverages matplotlib under the hood and is essentially just drawing a simple plot I allow the users to pass whatever matplotlib kwargs into _Trochoid.plot and this then gets passed down into the internal matplotlib call
What this Issue is asking
For this particular issue I'm looking to give just an improvement to the docstring in this plot method. A lot of the public facing methods are fairly well-documented but I find the plot docs to be ehhh kind of lacking
Feel free to sift through the official docs to get an idea of what kind of docs we're trying to build. Still early on in the project so it's a work in progress 😅
The matplotlib.pyplot.plot docs actually serve as a pretty good example, essentially just a few paragraphs of what the plot method is doing, some examples of how it could be configured via kwargs, maybe some quickstart code snippets i.e. the code snippet from the blog post would be more than sufficient for what we need right now
Nothing set in stone and I'm open to ideas so feel free to submit a draft pull request and we can start spitballing some ideas! Thanks so much for your interest in contributing, like I said lmk and I'll assign this to you!

Hey @NishanthMuruganantham I just did a project-wide improvement to the docstrings so this one was actually just completed - feel free to jump onto a different issue though I'd love to get you involved! Cheers! :D

Completed by #102

Thanks for the notification @chris-greening . Apologies for the late response, will try to find some other issues.


Use the new pre-configured developer image of mesg/engine

Dependent on https://github.com/mesg-foundation/engine/pull/1810
This PR updates the CLI to use the new pre-configured developer image of mesg/engine
To test:

checkout branch feature/remove-core of the engine. build image using make build-docker.
add to .liteflowrc the version: engineVersion: local
run liteflow dev

Tests seem to be failing, could you fix that or do you want me to have a look?

Test fixed. I push to docker the image mesg/engine:unstable and mesg/engine:unstable-dev to make it works (as well as other fixes).
I also simplify the config generation: https://github.com/liteflow-labs/liteflow-js/pull/97/commits/61c3567615a1fdf155cea8ce38cd524ce0720a5d

I have some errors when running an app in the dev command. Are the mnemonic correct and already added in the genesis?
➜  liteflow-js git:(feature/dev-image) ✗ liteflow-dev dev ~/Desktop/get-started
2020-05-10T05:33:14.400Z INFO › engine › starting the engine
2020-05-10T05:33:24.527Z INFO › process › compiling src=process.yml
2020-05-10T05:33:24.564Z INFO › service › compiling src=https://github.com/liteflow-services/emit-event-interval
2020-05-10T05:33:28.679Z INFO › runner › compiling serviceHash=8KxtnsqyLsh7EgoocswHPHYEqycHNNXmPo5NJpncuHGU
2020-05-10T05:33:28.685Z INFO › service › compiling src=https://github.com/liteflow-services/ethereum-erc20
2020-05-10T05:33:33.298Z INFO › runner › compiling serviceHash=H7SvNppT4VttNxSx58becb1UfZV74htKM1czfTGvBo2b
2020-05-10T05:33:33.304Z INFO › service › compiling src=https://github.com/liteflow-services/webhook
2020-05-10T05:33:37.463Z INFO › runner › compiling serviceHash=FDvQhZTwYPay1CnurZ1GQowSVEhKQr6Q1p89p87T2PHS
2020-05-10T05:33:37.474Z INFO › service › creating hash=8KxtnsqyLsh7EgoocswHPHYEqycHNNXmPo5NJpncuHGU
2020-05-10T05:33:37.564Z ERROR › unknown address: account mesg1kryh4t7d5wlqmnn5sdvz546z030qju6kky3ae4 does not exist

I also added more cleanup on another PR #99

I tried again on my computer and everything works fine as well as GitHub CI.
Can you make sure you local .liteflowrc is good? It should only contain engineVersion: unstable.


mouse highlighter in mouse utilities can be saved after reboot the system

Microsoft PowerToys version
v0.55.1
Running as admin

[X] Yes

Area(s) with issue?
Mouse Utilities
Steps to reproduce

Enabled mouse highlighter
Checked mouse highlighter is working properly.
reboot the system, mouse highlighter can't work, need to re-enable to turn on the function.

expected result: the function of mouse highlighter is working after reboot the system.
✔ Expected Behavior
expected result: the function of mouse highlighter is working after reboot the system.
❌ Actual Behavior
the function of mouse highlighter is not working after reboot the system.
i need to re-enable the function of mouse highlighter, then the function is worked.
Other Software
No response

Hi @ROEWE1226, just to clarify.. By re-enable you mean going to settings and toggle the Enable switch on-off or pressing keyboard shortcut ?

/needinfo

Hi,
Thanks for your quick answer.
Re-enable it means I need to re-press shortcut “windows+shift+H” to enable mouse highlighter after reboot system. Thx.
Best Regards!

Roewe.Chen +86  181 2997 5269
发件人: Stefan Markovic @.>
发送时间: Friday, February 4, 2022 9:07 PM
收件人: microsoft/PowerToys @.>
抄送: ROEWE1226 @.>; Mention @.>
主题: Re: [microsoft/PowerToys] mouse highlighter in mouse utilities can be saved after reboot the system (Issue #16063)
Hi @ROEWE1226https://github.com/ROEWE1226, just to clarify.. By re-enable you mean going to settings and toggle the Enable switch on-off or pressing keyboard shortcut ?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/16063#issuecomment-1029969620, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXTLGXZPE34V5HPJPH3EPSLUZPFONANCNFSM5NQ6NOPQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@ROEWE1226 Ok. Thanks for clarifying. This behavior is by design. So the feature will only work after you switch it on by pressing shortcut.

Possibly we could add some option like Always on in the future, but for now behavior remains the same :)

yes, your understanding is correct.
could you help to change the deign? change to no need to press the shortcut to enable it after reboot the system.
i'm curious why need to enable it again after reboot.

@ROEWE1226 Ok. Thanks for clarifying. This behavior is by design. So the feature will only work after you switch it on by pressing shortcut.

this would be more or /dup #14784


Grid not letting me store items

Issue description: I don't know if this is the mod or my stu**dity, I did not know how it works so I just followed the instructions on the wiki about where to place everything (Just Not Enough  Mods 2)
What happens: After giving to FE it wasn't letting me put items in it I also have 2 "1k storage disks" in the "disk drive"
What you expected to happen: The items to go into through the grid
Steps to reproduce:

...
Version (make sure you are on the latest version before reporting):

Minecraft:1.15.2
Forge:31.1.12
Refined Storage:1.8.1

Does this issue occur on a server? [yes/no]
no
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

Check the drives. Either the disks are full or you've changed the mode on the left to whitelist.

Check the drives. Either the disks are full or you've changed the mode on the left to whitelist.

it worked thanks @Darkere


EricLawrence.FiddlerNetLogImporter version <IP_ADDRESS>

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @upintheairsheep,
The installation isn't unattended - it has a message at the end of the install:

Is there an installer switch to bypass this?

https://dl.google.com/tag/s/appguid%3D{F7A0263C-9459-4A49-BDD5-AA35E1C35151}%26iid%3D{177D8BB7-4423-514F-CCE2-EEDCF41A1819}%26lang%3Den%26browser%3D4%26usagestats%3D0%26appname%3DGoogle%2520Ads%2520Editor%26needsadmin%3DFalse/adwords_editor/GoogleAdsEditorSetup.exe

http://appldnld.apple.com.edgesuite.net/content.info.apple.com/Safari3/061-4833.20080619.E45tg/SafariSetup.exe

http://appldnld.apple.com.edgesuite.net/content.info.apple.com/Safari3/061-4833.20080619.Vgfr5/SafariQuickTimeSetup.exe


CHANGES.md

@cmccoy
Connor, I've updated the Changes.md file for this merge request, can you please take a look? Thanks.


Kivy python first app

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

`This closes #3072

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Kivy python first app #3657.pdf
Plagiarism check done - it would improve the article to go through the red flags in the report @doloresmia

Hi @doloresmia
Thank you for this article. It's simple and easy to follow through. Keep up the awesome job.
cc: @mercymeave


Importing pygcurse causes error [Python 3.4]

It gives this error:
Traceback (most recent call last):
File "<pyshell#0>", line 1, in
import pygcurse
File "C:\Python34\lib\site-packages\pygcurse_init_.py", line 79, in
colornames[cname] = pygame.Color(cname)
ValueError: invalid color name
I'm using the 32-bit version of Python 3.4. I istalled pygcurse using pip version 7.0.3 and my pygame version is 1.9.2a0.

My pull request fixes this.
https://github.com/asweigart/pygcurse/pull/23

Thank you very much for reaching out to me. I have no clue how long this hasn't worked. :P
I wrote Pygcurse over the course of a couple weeks, but didn't make unit tests for it. Hopefully I'll have time to get back to it in the next few months sometime.
THANKS!


Add docker publishing to ci

:tada: This PR is included in version 0.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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

GitHub release
0.2.1

Your semantic-release bot :package::rocket:

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

GitHub release
0.2.1

Your semantic-release bot :package::rocket:

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

GitHub release
0.2.1

Your semantic-release bot :package::rocket:

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

GitHub release
0.2.1

Your semantic-release bot :package::rocket:

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

GitHub release
0.2.1

Your semantic-release bot :package::rocket:

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

GitHub release
0.3.0

Your semantic-release bot :package::rocket:


Fuzzing VM: Error in debug_recv(): Got b'R', Expected: b'DZ'

When I start fuzzing with
./kAFL-Fuzzer/kafl_fuzz.py -work_dir <work-dir> -seed_dir <seed-dir> -vm_dir <snapshot-dir> -mem 1024 -agent targets/linux_x86_64/bin/fuzzer/kafl_vuln_test --purge -v -ip0 0xXXXXXXXXXXXXXXX-0xXXXXXXXXXXXXXXX

I get this error:
[WARNING] Slave 0: Error in debug_recv(): Got b'R', Expected: b'DZ'
[FATAL] Failed to launch Qemu, please see logs. Error: Killed Qemu due to protocol error.
[FATAL] Slave has died - check logs!
[FATAL] Master exit: All slaves have died.

I do not understand what this error actually means. It doesn't depend on the IP trace filter range. Everything was set up properly using the provided scripts, the kafl_info.py is working. The debug.log also does not provide more information than above.

This issue is mentioned here https://github.com/IntelLabs/kAFL/blob/master/doc/TUTORIAL.Windows_fuzzing.md#troubleshooting-1. Does it help?

I have already seen this troubleshooting at the end. Am I understanding correctly, that there is a problem with the timing? So these two lines mentioned here should be pasted somewhere. But honestly I don't get where. I'm doing a linux fuzz with the loader from targets/linux_x86_64. Do I have to put it in the loader.c and re-compile and re-run it on the VM to get it working?

Do I have to put it in the loader.c and re-compile and re-run it on the VM to get it working?

Yes, after HYPERCALL_KAFL_LOCK. For example, in Windows loader lines go somewhere here https://github.com/IntelLabs/kAFL/blob/master/targets/windows_x86_64/src/loader/loader.c#L172.
Better synchronization should be implemented between QEMU and fuzzer in the future, right now this hack should work.

Thank you! It's working now.
At least the error message is gone and the error doesn't appear anymore. Now I have this on my display and I'm not sure if there's something happening or just in idle...
Imported payload produced no new coverage, skipping..

Well, again, there may be synchronization problems that cause such message but usually it means that there is indeed no coverage registered in your provided IP range. You can try to manually add some (3-5-10) tests in $WORK_DIR/imports while fuzzer is running to see if new coverage will be registered after all or not.

Add a few more seeds and make sure some of them land in the corpus. Inputs that do not produce new coverage are discarded. In the worst case, wrong trace settings or other mistakes can lead all inputs being discarded, and then there is nothing to mutate on.

I added some more seeds and tried more ip ranges, but it's always the same.
@vient manually adding stuff to the imports-dir did just threw the same message.
@il-steffen what exactly do you mean with landing in the corpus?

Check the outputs of kafl_gui or kafl_plot to see what inputs the fuzzer actually found/recognized so far. If the seeds produced no coverage then you may end up with zero "paths" found, i.e. the corpus/queue of inputs is empty. In this case, after all seeds are processed, there is nothing for the fuzzer to do but to try random inputs. This is not done by default because usually the problem is with the PT trace setup and not with the inputs.
If you run into this problem with the published hello world sample, the error is most likely in the PT setup. Make sure that kASLR and spectre/meltdown mitigations are disabled in the guest VM. You may have to edit grub.cfg and create a new snapshot. If that seems correct, double check the ip0 range obtained from kafl_info. You can also try the hprintf agent to see if the agent is executing properly.

Ok. I disabled kASLR and spectre/meltdown mitigations in the guest VM and made a new snapshot. I double checked the ip range (I've choosen this line from kafl_info output: 0xffffffffc008f000-0xffffffffc0156000   ext4) and pasted this ip range into the kafl_fuzz command:
./kAFL-Fuzzer/kafl_fuzz.py -work_dir ../VMs/working/ --purge -seed_dir ../VMs/seed/ -vm_dir ../VMs/snapshot/ -mem 1024 -ip0 0xffffffffc008f000-0xffffffffc0156000 -agent targets/linux_x86_64/bin/fuzzer/kafl_vuln_test -v

I still get the same output. The kafl_gui output tells me that there didn't happen anything...
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░[kAFL v0.2 ]░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┃Runtime:    0m02s │ #Execs:         0 │ Exec/s:         0 │ Slaves:       1/2 ┃
┃CPU Used:      0% │ User:        0.1% │ Guest:       0.0% │ Stability:     0% ┃
┃Mem Used:    9.3% │ Avail:       6.6G │ Total:      7.7G% │ Reset/s:        0 ┃
────────────────────────────────────────────────────────────────────────────────
┃Path Info:        │ Bitmap Stats:     │ Findings:                             ┃
┃ Total:         0 │                   │  Crash:            0 (N/A)   None Yet ┃
┃ Seeds:         0 │  Edges:         0 │  AddSan:           0 (N/A)   None Yet ┃
┃ Favs:          0 │  p(col):     0.0% │  Timeout:          0 (N/A)   None Yet ┃
┃ Norm:          0 │  Pending:    0.0% │  Regular:          0 (N/A)   None Yet ┃
────────────────────────────────────────────────────────────────────────────────
┃Yld: Init:      0 │ Grim:      0 │ Redq:      0 │ Det:       0 │ Hvc:       0 ┃
┃Fav: Init:      0 │ Rq/Gr:     0 │ Det:       0 │ Hvc:       0 │ Fin:       0 ┃
┃Nrm: Init:      0 │ Rq/Gr:     0 │ Det:       0 │ Hvc:       0 │ Fin:       0 ┃
────────────────────────────────────────────────────────────────────────────────
┃> Slave  0:         import │ node:  N/A  │ fav/lvl:     N/A  │ exec/s:   N/A  ┃
────────────────────────────────────────────────────────────────────────────────
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░[Payload Info]░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┃Parent:   N/A │ Size:     N/A │ Bytes:    N/A │ Bits:     N/A │ Exit:         ┃
────────────────────────────────────────────────────────────────────────────────
┃0x0000000: 69 6d 70 6f 72 74 69 6e 67 2e 2e 2e              │importing...     ┃

You say you use -ip0 range from ext4 driver, but you seem to use the kafl_vuln_test agent, not the fs_fuzzer agent. Change the -ip0 range to target the kafl_vuln_test kmod or change the agent to actually try some ext4 mounting.

Oh yes. That's true. Changed the agent to targets/linux_x86_64/bin/fuzzer/ext4. That should be right? But I still get the same output.
Sorry for that many questions. It's the first time I get in touch with kAFL and this type of fuzzing in general. Thank you very much for your fast answers!

Try the hello world sample first to see if the basics are working. For ext4, try adding a couple ext4 headers/inputs as seeds. If the seeds get rejected in some generic wrapper you may not actually trigger ext4.kmod and the fuzzer will discard the seeds (zero paths, your problem here)

I set up the hello world sample. Needed some time but have all successfully compiled now. When I run the qemu-system-x86_64 command from this README, then I get three lines with the last one telling me Booting from ROM.. and then terminating. Is that right?
Well, if I run the kafl_fuzz now I once again get this error again, but slightly different:
[WARNING] Slave 0: Error in debug_recv(): Got b'K', Expected: b'DZ'

Can I somehow fix this like I did with the VM before?

Are you saying the Linux samples are working now?
The issue you see with Zephyr is probably a known a bug/regression in Zephyr. My helper scripts do not pin the Zephyr version and whatever we're checking out these days does not seem to work with qemu -enable-kvm. It does an endless reboot loop if you try it with vanilla qemu like this. Now, the default launch arguments for zephyr inside kAFL include a -catch_resets which will detect these silent reboots and report them as "ASAN" errors. The error reporting is not optimal here, but basically the messages says: "kAFL ran into KASAN type crash while trying to initiate connection with the fuzz agent.".
The fix is to build an older zephyr that boots with KVM. I had success with west init --mr "v2.3.0", perhaps you can find a more recent version...

No, the linux samples are still not working for me. But I'll first try to solve this hello word sample for now.
Your fix did work. The zephyr os is booting properly now. I started kafl_fuzz and the gui tells me that it is running, but there's no cpu usage or executions. I'm not sure if I understand all the arguments correctly:

How exactly read the desired ip0 range from the zephyr.map? I'm a little bit confused of this huge file.
Which one is the correct seed directory? I tried targets/zephyr_x86_32/seeds/

python3 kAFL-Fuzzer/kafl_fuzz.py -ip0 0xXXXXXXXXXXXXXXX-0xXXXXXXXXXXXXXXX -mem 16 -extra ' -no-reboot -no-acpi' -kernel targets/zephyr_x86_32/zephyrproject/zephyr/samples/hello_world/build/zephyr/zephyr.elf -seed_dir targets/zephyr_x86_32/seeds/ -work_dir ~/fuzzing/VMs/working/ --purge -v

All of the steps are automated in the compile.sh, including the extraction of -ip0. You probably don't get any executions because the zephyr.elf that  you launch is the standard Zephyr sample which literally just prints hello world.


Use Go 1.17.7

Codecov Report

Merging #149 (9d8ff72) into main (cea615c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #149   +/-   ##
=======================================
  Coverage   92.27%   92.27%
=======================================
  Files          63       63
  Lines        4012     4012
=======================================
  Hits         3702     3702
  Misses        239      239
  Partials       71       71

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 cea615c...9d8ff72. Read the comment docs.


Rendering of MainNavBar is delayed on Android 9

When navigating to a narrow, when rendering ChatScreen the ComposeBox component renders as expected but the MainNavBar does not render immediately but takes a bit.
This is not a critical issue, as the component renders correctly.
Still, it is good to figure out the issue which might also be present elsewhere.

Here is more info on this issue:
I tested on few devices:

On Android 9 emulator (Android Pixel XL), can't reproduce.
But can reproduce on Android 9 running on One Plus 6.
Can reproduce on on MI phones (not completely sure, but it was Android 8 or lower)

This issue is very critical and can also lead/extends to completely not rendering of MessageList, like:

(https://chat.zulip.org/#narrow/stream/48-mobile/topic/notifications)
I started debugging on this and here is what I found.

If is remove WebView, then this got fixed. So this is related to MessageList.
MessageList is encapsulated with redux, actionSheet, withGetText, I tried removing each at a time and tried to reproduce. I was still facing this issue, even after removing it. So not related to redux or action sheet or anything similar.
Then I tried with buildToolVersion as 28.*, nothing worked.
Also tried with compileSDKVersion as 28.*, same result,  nothing worked.
I tried with same as what is present in RN repo (https://github.com/facebook/react-native/blob/9d00d4d5bb0f312b7d907e2fc4005a73301dee9f/ReactAndroid/build.gradle#L271),  same result,  nothing worked.
Then I found few patterns to reproduce it:

If you doNarrow to those narrows, for which there are no messages (first time narrow/we haven't cached any messages yet/dummy messages are show for a small fraction of time) then this issue is never reproducible. Then for subsequent narrow to same narrow, I can reproduce this issue.
Many time nav bar is visible with a delay after narrowing. And sometimes, it only become visible after scrolling a message list. So if list height is less than screen, i.e message list is not scrollable it is not possible to make nav bar visible.
Even though nav bar is not visible, it's functionality works. That it, on tapping on back icon or on info buttons positions, corresponding nav actions takes place.

Then, one thing was troubling me: why compose box is rendered/displayed immediately. What is the problem with navBar???? It is also a normal component like composeBox. Then I changes the position of navBar from top of MessageList to bottom of MessageList.
like this (in ChatScreen):
<Chat narrow={narrow} />
<ChatNavBar narrow={narrow} />

and guess what, navBar is displayed immediately after narrowing, surprising yes!!
So the real issue is like:
When webView renders messages/calculate is size (I thinks many time recalculation takes place internally), it do something (wrongly) which affects the display property of component which is present vertically above to it.
Then I created new fresh RN (0.57.8) project with compileSdkVersion = 27. And guess what I found the same issue.
Playground: https://github.com/jainkuniya/rn-test-webview-on-andorid/blob/master/App.js
Swap the position of webView and text component and find that, when text is at top, there is delay in rendering/displaying text component. Same issue as ours.
Now replace
source={{ html: 'https://github.com/facebook/react-native' }}

with
source={{ uri: 'https://github.com/facebook/react-native' }}

Again play around it with.
So when webView is not scrollable, many times text component is not even displayed.
Now finally I got a solution, which is using styles.
Comment out this line
https://github.com/jainkuniya/rn-test-webview-on-andorid/blob/master/App.js#L31
and see the magic.
Just we are rendering components in reverse order 😝 and it got fixed.
Now next after applying same concept in ChatScreen
 <ActionSheetProvider>
        <View style={styles.screen}>
          <ZulipStatusBar narrow={narrow} />
          <View style={[styles.flexed, styles.flexDirectionColumnReversed]}>
            <Chat narrow={narrow} />
            <OfflineNotice />
            <ChatNavBar narrow={narrow} />
          </View>
        </View>
      </ActionSheetProvider>

Now UnreadNotice starts behaving in the same way like nav bar was behaving before.
Because in Chat UnreadNotice is above of MessageList
 <View style={styles.flexed}>
          <UnreadNotice narrow={narrow} />
          <NoMessages narrow={narrow} />
          <MessageList narrow={narrow} />
          <ComposeBox narrow={narrow} />
</View>

So to fix it, replace it with
 <View style={styles.flexed}>
          <View style={[styles.flexed, styles.flexDirectionColumnReversed]}>
                 <MessageList narrow={narrow} />
                 <NoMessages narrow={narrow} />
                 <UnreadNotice narrow={narrow} />
          </View>
          <ComposeBox narrow={narrow} />
</View>

And ya, this issues get's fixed.
(This is a hack.)
@zulipbot claim

One next step that would be quite useful is to go looking in the RN tracker for a report of this issue, and if there is one then link to it here... and if there isn't, then to report it. That repro in a fresh RN app will be very helpful for a bug report.
If there is already a report of an issue that looks like this, then if there's any of this information that isn't already known in the issue thread, it'd also be helpful to post a comment with the additional information. The repro is again especially likely to be helpful.


Upload plate mappings block should allow space in barcodes

I received another example barcodes file, where they tried to make the format what we expect (plate, well, sample), but it has a space before each barcode, just because their barcode reader adds that. This breaks our barcode reader! Full example in our GDrive folder, and short example here:
3000526945,A1,<PHONE_NUMBER>
3000526945,A2,<PHONE_NUMBER>
3000526945,A3,<PHONE_NUMBER>
3000526945,A4,<PHONE_NUMBER>

The error is in this line of RunBlockEditor.tsx
const [, rowRaw, columnRaw] = cell.match(cellRegex);

Should be fixed as of aaa02565


How to create 2 items at once where each require other in relation?

Problem
Imagine such model:
model Owner {
  id   String @id @default(cuid())
  name String
  car  Car
}

model Car {
  id      String @id @default(cuid())
  name    String
  owner   Owner  @relation(fields: [ownerId], references: [id])
  ownerId String
}

Car has an owner and each owner must have a car. Both sides of the relation are required all the time.
I struggle with creating such items.
If I try to create Owner, I have to pass Car to be connected to it. But as car is not yet created, how do I know what ID to pass? If I want to create Car first - I have the same problem as I need id of the owner to connect it with
db.car.create({
  data: {
    name: '911',
    owner: {
      create: {
        name: 'Bob',
        // Car is required
        car: {
          // What do I put here as car is not created yet?
        }
      }
    }
  }
})

I was trying to use connectOrCreate as it seemed to not require 2nd side of the relation when connecting, but it didn't work.
`Error for binding '3': AssertionError("[Query Graph] Expected a valid parent ID to be present for a nested connect on a one-to-many relation.")`

In other words - those both items have to be created at once and connected instantly.

@pie6k Sorry for the delay here, this one got slipped in my notifications.
So create will also connect to record you are creating, no need to provide it. If you use Typescript here, you will also get a warning like so:

This call should suffice for creating a Car and also creating an owner for it:
  const data = await prisma.car.create({
    data: {
      name: "911",
      owner: {
        create: {
          name: "Bob",
        },
      },
    },
  });

Prisma run the following SQL for this to ensure they are also connected:
BEGIN
INSERT INTO "public"."Owner" ("id","name") VALUES ($1,$2) RETURNING "public"."Owner"."id"
INSERT INTO "public"."Car" ("id","name","ownerId") VALUES ($1,$2,$3) RETURNING "public"."Car"."id"
SELECT "public"."Car"."id", "public"."Car"."name", "public"."Car"."ownerId" FROM "public"."Car" WHERE "public"."Car"."id" = $1 LIMIT $2 OFFSET $3
COMMIT

ownerId is the id of the new owner which was created in the first call of the transaction.

Closing as the question has been answered


Not created cluster...

kubernetes cluster not installed. pre-pulling kubernetes images 3 repeated times
I've been waiting for 20 minutes.
rancher container it keeps rebooting.

"""Rancher v2.4.8 same in this version"""
Docker version 19.03.12, build 48a66213fe
Rancher v2.4.5 UI: v2.4.28 |
Ubuntu 18.04.5 LTS

Rancher repo timeout? Really?

I came to say the same thing. This stopped working on me between v2.4.5 and v2.4.8. Gonna downgrade back to v2.4.5 and see if it works.

I came to say the same thing. This stopped working on me between v2.4.5 and v2.4.8. Gonna downgrade back to v2.4.5 and see if it works.

I've tried all the versions and versions I have installed before, buddy. There is no result ... rancher repositories not working


How to delegate those functions ?

After AJAX-request for data from other page, the JS(material-design-lite) is not applied to 'AJAX'ed elements. Probably it needs to be delegated ? or how to do it ?

The docs exist for a reason

Use MDL on dynamic websites
Material Design Lite will automatically register and render all elements marked with MDL classes upon page load. However in the case where you are creating DOM elements dynamically you need to register new elements using the upgradeElement function. Here is how you can dynamically create the same raised button with ripples shown in the section above:
<div id="container"/>
<script>
  var button = document.createElement('button');
  var textNode = document.createTextNode('Click Me!');
  button.appendChild(textNode);
  button.className = 'mdl-button mdl-js-button mdl-js-ripple-effect';
  componentHandler.upgradeElement(button);
  document.getElementById('container').appendChild(button);
</script>```

Please use StackOverflow for support and integration assistance. This tracker is only for problems with the code provided by Material Design Lite.
Thank you.


Move datetimeR functions to nolar

datetimeR was developed as a simple, standalone package, but we would like to move those functions into the nolar package and get rid of the datetimeR package.
https://github.com/nola-r/datetimeR

For context, at the time that datetimeR was created, we were planning on creating and maintaining multiple smaller packages.  However, we recently decided to put all OPA code in the same place (this nolar package).  So we thought that a good first step would be gathering all the code that has already been written into this repo.

Made a pull request with the uploaded files (http://bit.ly/2xRvGAg)

#3 One minor change before we merge the pull request


textfield alignment

There was an alignment issue in response screen search text field
before it looked like this

now it looks like this

is this fine ?

Instead of directly raising a PR, you should first raise an issue in the provided format which includes the platform on which this issue has been observed.

Ah, I will be carful about that :sweat_smile:


Develop a scenario when the product is "Sold out"

As a user
I need to know when a particular product I added to my shopping cart was sold out
So that I will not accidentally order a product that no longer exists
Details and Assumptions

we need to mark it as sold out, so that the user would be able to see the reference to the product they wanted to buy (dont simply delete it from the shopping cart, unless the product was permanently deleted from the platform)

Acceptance Criteria
Given user who wants to buy a product
When the product in the shopping cart is being sold out
Then there should be flag next to it saying that the product is no longer available

put into the icebox


Upload fails on GitHub actions for public repositories when CODECOV_TOKEN is not available

Uploading code coverage from Travis CI and friends
According to the documentation at https://docs.codecov.io/docs/about-the-codecov-bash-uploader#section-upload-token, when using the coverage uploader with a public project on

TravisCI
CircleCI
AppVeyor
Azure Pipelines

an upload token is not required.
For reference, see https://docs.codecov.io/docs/about-the-codecov-bash-uploader#section-upload-token.
Uploading code coverage from GitHub actions
When using GitHub actions, it is possible to provide the CODECOV_TOKEN as a secret, but it will only be available for builds triggered by users who have push privileges (maintainers or collaborators).
For open-source projects, this is usually not the case, which means that

uploading code coverage
code coverage check integrations
displaying code coverage in pull request comments

is not possible.
For reference, see https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets.
Workaround
In https://github.com/sebastianbergmann/phpunit/pull/3921 we work around this by using GitHub actions as a primary system, but fall back to collecting code coverage using Travis CI.
However, this does not seem to be a viable solution for the longer term.
Long term solution?
Will there be a chance that uploading code coverage from public repositories will be made possible without the need to provide a CODECOV_TOKEN?
Not sure how the integration with Travis CI went, but when this worked with Travis CI, it should surely be possible with GitHub actions.

/cc @nat

Hi @localheinz
This is currently a limitation of GitHub Actions not having an API for us to check.
We are tracking this request here: https://community.codecov.io/t/whitelist-github-action-servers-to-upload-without-a-token/491/8

Thank you, @drazisil!
I hope that this issue will be resolved soon.


Appstudio update test-component-pac-aaul

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-aaul-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
28 seconds
build-container

✅ Succeeded
22 seconds
inspect-image

✅ Succeeded
2 minutes
deprecated-base-image-check

✅ Succeeded
57 seconds
clamav-scan

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
19 seconds
sbom-json-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
8 seconds
optional-label-check

✅ Succeeded
4 seconds
show-sbom

✅ Succeeded
5 seconds
show-summary

Pipelines as Code CI/test-component-pac-aaul-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
28 seconds
build-container

✅ Succeeded
22 seconds
inspect-image

✅ Succeeded
2 minutes
deprecated-base-image-check

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
57 seconds
clamav-scan

✅ Succeeded
19 seconds
sbom-json-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
8 seconds
optional-label-check

✅ Succeeded
4 seconds
show-sbom

✅ Succeeded
5 seconds
show-summary

Pipelines as Code CI/test-component-pac-aaul-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
22 seconds
build-container

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
inspect-image

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
34 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
8 seconds
optional-label-check

✅ Succeeded
8 seconds
label-check

✅ Succeeded
5 seconds
show-summary

✅ Succeeded
3 seconds
show-sbom


Problem with ElasticSearch/Elk

Output of go version:
go version go1.7.1 linux/amd64

Output of docker version:
Client:
 Version:      1.12.6
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   78d1802
 Built:        Tue Jan 31 23:35:14 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.6
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   78d1802
 Built:        Tue Jan 31 23:35:14 2017
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 21
Server Version: 1.12.6
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 114
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge host null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-87-generic
Operating System: Linux Mint 18.1
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.859 GiB
Name: kvm-malice
ID: DAXD:ZCFT:CVPK:5GQ5:XTYW:MKRN:WWEK:LQSF:DMZC:YR37:F5DK:OOD4
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8
  (The running container is malice-elastic, version 5.3.)

Using standard pre-compiled binary on Linux Mint 18.1 "Serena", Mate version with all current updates.  This is a KVM virtual machine running on an Ubuntu-based host. 4 GB RAM, 4 cores.
Steps to reproduce the issue:

Install precompiled binary.  Run malice plugins update --all.
Answer prompt "Newer version of malice config.toml available:  Version 0.3.2" with "yes"
Repeat step two two or three times, as you will be prompted the same thing three times.  Even though this is already malice 0.3.2.
Try to execute "malice elk".

Describe the results you received:
ERRO[0002] Container is already running...               env=development exisits=true name=malice-elastic
ERRO[0002] container is already running
Pulling repository docker.io/blacktop/kibana
ERRO[0003] CreateContainer error = Error: No such image: blacktop/kibana:malice
env=development
ERRO[0003] StartContainer error = Error response from daemon: page not found
env=development
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x84b168]
goroutine 1 [running]:
github.com/maliceio/malice/malice/docker/client/container.Start(0xc4203c6cc0, 0x0, 0x0, 0x0, 0xc42035d520, 0xd, 0xc42035bba0, 0x16, 0x0, 0x0, ...)
/Users/blacktop/go/src/github.com/maliceio/malice/malice/docker/client/container/start.go:74 +0x468
github.com/maliceio/malice/malice/ui.Start(0xc4203c6cc0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/Users/blacktop/go/src/github.com/maliceio/malice/malice/ui/ui.go:32 +0x29e
github.com/maliceio/malice/commands.cmdELK(0xc4202e3b00, 0xab9120, 0x4)
/Users/blacktop/go/src/github.com/maliceio/malice/commands/elk.go:19 +0xdb
github.com/maliceio/malice/commands.glob..func4(0xc4202e3b80, 0x0, 0xc4202e3b80)
/Users/blacktop/go/src/github.com/maliceio/malice/commands/commands.go:69 +0x4d
github.com/maliceio/malice/vendor/github.com/urfave/cli.HandleAction(0x9c9220, 0xade000, 0xc4202e3b80, 0xc420334700, 0x0)
/Users/blacktop/go/src/github.com/maliceio/malice/vendor/github.com/urfave/cli/app.go:485 +0xd4
github.com/maliceio/malice/vendor/github.com/urfave/cli.Command.Run(0xab899e, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0xac9777, 0x1e, 0x0, ...)
/Users/blacktop/go/src/github.com/maliceio/malice/vendor/github.com/urfave/cli/command.go:207 +0xb72
github.com/maliceio/malice/vendor/github.com/urfave/cli.(*App).Run(0xc4202cc9c0, 0xc42000a200, 0x2, 0x2, 0x0, 0x0)
/Users/blacktop/go/src/github.com/maliceio/malice/vendor/github.com/urfave/cli/app.go:250 +0x7d0
main.main()
/Users/blacktop/go/src/github.com/maliceio/malice/main.go:88 +0x584
Describe the results you expected:
Expected the web interface "Elk", presumably ElasticSearch + Kibana, to start.
In other examples, e.g., running docker version of malice within docker, I did get a Kibana package, but it would not run as it complained that ElasticSearch 5.4.3 was expected, but only version 5.3 was found "on all nodes".
Scanning function seems to work rather well.  :)
Additional information you deem important (e.g. issue happens only occasionally):
Bug(s) are 100% reproducible.

Please let me know if I can provide any further information.

can you tell me what is in this file ~/.malice/config/config.toml in that file you can also manually change it to use the newer elasticsearch/kibana version

I talk about how to change the config here too - https://github.com/maliceio/malice-kibana-plugin/issues/4#issuecomment-315658581


ko-component-router seems to fail to render in IE 11

I'm absolutely loving ko-component-router, and it's working beautifully for our app in all browers apart from IE.
I've successfully implemented es6-promise as per the instructions, and have confirmed console>> Promise resolves in IE correctly.
However, something about the  element isn't rendering (or so I suspect). No console errors, nothing, I was hoping you could provide some advice?
https://maestro-uat.heffron.com.au

IE10 & IE11 also need Symbol and Map polyfills.
I'm using https://github.com/zloirock/core-js and importing only:

core-js/es6/symbol
core-js/es6/map

@nachopants, does adding the polyfills above resolve your issue? I'm on a Mac and prefer to fire up IE as sparingly as possible, but I do know that the app that the router was created works in IE9-11. We use babel w/ the babel-polyfill. If you've still got issues, lmk.

v4 outputs es5 code that only requires a promise lib

polyfill note added to docs


fix: Reuse connection transport for marker requests

Marker requests would reset the Transport struct, thereby unintentionally resetting the round trip time.

Add NewOrReusedConnection to allow connections to be reused
Move dialling logic to separate method
Make marker requests use NewOrReusedConnection instead of NewConnection

This is an alternative to #76. @fzipi you need to decide which one you want to keep.

Thanks @theseion - my personal opinion is if keeping the RTT struct, we should go ahead and fix so it's not just a replacement for time.Now() at the caller as it currently is. My understanding is this is the main motivation for this PR.
If not doing that though, the simplification in #76 seems worth it - and we could still do this reuse but maybe it's not so meaningful then. I don't know if Do would ever have enough logic to make timings more precise by embedding them so lean towards simplifying by removing RTT from the client.

I agree, currently, using explicit timing and using the RTT struct will report the exact same thing, and it's not actually the round trip time but the time between start and stop. In between those two statements a bunch of requests will have happened. So maybe we need to change the idea to "record average RTT of requests". The output should reflect that and maybe show both, e.g.:
test time: 23ms
avg rtt: 14ms

I think that even if the RTT timing is broken, this patch is needed to optimize reuse in connections. Is that right? In that case, we should merge this one to make the optimization available.
Then we can discuss if/how we want to track timings.

If reusing the connection works well then this does seem like a good idea. Just want to confirm though - I had thought arbitrarily that not reusing may have been intentional. We send a lot of weird requests, and it wouldn't surprise me if the connection gets corrupt in some cases but have no idea actually.

I don't think reusing the connection is of much significance in terms of performance, since the actual net.Conn will be recreated anyway; but it's certainly nicer. However, now that I've looked at the code again, there's a leak when reusing the connection, because the old net.Conn is never closed. I'll open a new PR for that.

Seee #84.


Structured list Live demo does not match storybook

This is a new issue with structured list beyond that flagged in the discussion on the row indicator icon and positioning.
In the live demo version of selectable structured list on the Usage page of the carbondesignsystem.com site, the table header takes focus. What is the rationale for this? It's not sortable. It's obviously not selectable. Seems like an error
Also, each of the rows is in the tab order (twice), which I think doesn't follow the documented interaction, since this is basically a radio button group. Obviously even if it WAS supposed to navigable by tab, each row should not require two presses of the Tab key

NOTE: the storybook implementation, neither oddity exists (header not navigable, single tabstop for list, with arrow movement between them)
Steps to reproduce the issue

Open https://carbondesignsystem.com/components/structured-list/usage#live-demo
Change the Variant selector dropdown to "Selectable structured list"
Press Tab to enter the list and continue pressing to verify tab navigation for each row (and that 2 presses is needed to advance)
Shift+Tab to the table column header (top row) and confirm the header row takes focus.

In the codeblock for this, there's a hardcoded tabIndex that needs to be removed. Not sure why that was added there in the livedemo


Can not upload file twice with same name

Hi,
I am using <upload component to upload files.
for example: If I upload file a.txt it gets uploaded but If I try to upload same file again it does not get uploaded. onFileLoad event is not called second time.
How to fix the issue? It should allow uploading same file more than once.

This issue is related to #8. This is because we use native file input under the hood, it should be re-rendered after some file was picked. I will try to figure out how to fix this properly


⚠ Bofrost.de has degraded performance

In 588643a, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1163 ms

Resolved: Bofrost.de performance has improved in 71c44ae after 6 minutes.


Bar size scaled after the largest number?

Hi there
HA: 0.106.3
Bar-graph: 1.7.1
auto-entities: 16
I've just installed the Corona sensor here, and made a card like this:
  - card:
      max: 100000
      min: 0
      padding: 2px
      title_position: inside
      type: 'custom:bar-card'
    filter:
      include:
        - entity_id: '*worldwide_coronavirus*'
    sort: entity_id
    type: 'custom:auto-entities'

As you can see I've set the max to 100.000, which I then have to adjust when we cross that thresshold.
Is it possible to have just the largest number determine the length of the bar, and have the others scaled down to size?

Unfortunately currently there is no way to persistently store any data from the front-end. Also the bars don't have any relation between each other.
However you could try to use https://github.com/iantrich/config-template-card and use a value from any sensor as the max value.

Hi @Gluwc
That works perfectly.
I've created the card like this, and it seems to work perfectly:
type: 'custom:config-template-card'
variables:
  - 'states[''sensor.worldwide_coronavirus_confirmed''].state'
  - 'states[''sensor.denmark_coronavirus_confirmed''].state'
entities:
  - sensor.worldwide_coronavirus_confirmed
  - sensor.denmark_coronavirus_confirmed
card:
  entities:
    - cards:
        - card:
            card_style:
              opacity: 0.7;
            max: '${vars[0]}'
            min: 0
            padding: 2px
            title_position: inside
            type: 'custom:bar-card'
          filter:
            include:
              - entity_id: '*worldwide_coronavirus*'
          sort: entity_id
          type: 'custom:auto-entities'
        - card:
            card_style:
              opacity: 0.7;
            max: '${vars[1]}'
            min: 0
            padding: 2px
            title_position: inside
            type: 'custom:bar-card'
            width: 100%
          filter:
            include:
              - entity_id: '*denmark_coronavirus*'
          sort: entity_id
          type: 'custom:auto-entities'
      type: 'custom:hui-vertical-stack-card'
  show_header_toggle: false
  style: |
    ha-card {
      background-image: url('/local/images/corona.png');
      background-size: contain;
    }
  title: Corona
  type: entities


App should exit after 2 continuous back clicks rather than a single one

Describe the feature you'd like
Presently the app exits on a single back click even if i may have mistakenly pressed the back button.
The app should ask after one back click to press it again if the user wants to exit and it should exit if the user does so.
Would you like to work on the issue?
YES

This is standard behavior on Android and expected

@iamareebjamal  but the app is not showing this behaviour