gdbserver does not recognize correct CHIPID for F4DISCOVERY

stlink gdbserver does not correctly recognize the chipid for the mcu mounted on my F4DISCOVERY board returning a wrong memory map to gdb, here is the log from st-util:
andrea@andrea-HP-Pavilion-dv6-Notebook-PC:~/st-link/stlink.git/gdbserver$ ./st-util
Chip ID is 00000000, Core ID is  00000000.
KARL - should read back as 0x03, not 60 02 00 00
init watchpoints
Listening at *:4242...
GDB connected.
recv: qSupported:multiprocess+;qRelocInsn+
query: Supported;multiprocess+;qRelocInsn+
send: PacketSize=3fff;qXfer:memory-map:read+
recv: !
send: OK
recv: Hg0
send:
recv: ?
send: S05
recv: Hc-1
send:
recv: qC
send:
recv: qAttached
query: Attached;
send:
recv: qOffsets
query: Offsets;
send:
recv: g
send:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000220ffffffff30040008
recv: qXfer:memory-map:read::0,fff
query: Xfer;memory-map:read::0,fff
Xfer: type:memory-map;op:read;annex:;addr:0;length:4095
send: m<?xml version="1.0"?><!DOCTYPE memory-map PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"     "http://sourceware.org/gdb/gdb-memory-map.dtd"><memory-map>  <memory type="rom" start="0x00000000" length="0x0"/>  <memory type="ram" start="0x20000000" length="0x0"/>  <memory type="flash" start="0x08000000" length="0x0">    <property name="blocksize">0x0</property>  </memory>  <memory type="ram" start="0x40000000" length="0x1fffffff"/>  <memory type="ram" start="0xe0000000" length="0x1fffffff"/>  <memory type="rom" start="0x00000000" length="0x0"/>  <memory type="rom" start="0x1ffff800" length="0x8"/></memory-map>
recv: qXfer:memory-map:read::26c,d93
query: Xfer;memory-map:read::26c,d93
Xfer: type:memory-map;op:read;annex:;addr:620;length:3475
send: l
recv: m8000430,4
send: 002103e0
recv: m0,40
send:<PHONE_NUMBER>040008d5030008e1030008e9030008f1030008f903000800000000000000000000000000000000010400080d040008000000001904000825040008
recv: qSymbol::
query: Symbol;:
send:
recv: qTStatus
query: TStatus;
send:

Neither flash loading nor sram loading works in this conditions

A recent commit says moving reset and load params in open function,
these functions never get called.
I added them and the chip was  "magically" recognized, firmware gets flashed
but running an elf compiled with summon toolchain does not work.
I tried also to load an elf compiled with atollic (that works uploading it from atollic)
but it does not run.
Stlink utilty identify my mcu with chip id 0x401
I noticed another difference in the memory map returned from atollic
gdbserver it looks much more simpler

my build command is exactly the one you provided, the mcu is now recognized, i can flash the executable but i cannot debug it, launching it from arm-none-eabi-gdb or from an hardware target from eclipse hangs

I'm having issues with the F4 and gdb too, via flash write works.
Via gdb, it does actually flash ok, it just takes a verrrry long time, and the debugging part doesn't work at all.

same problem as karlp, there are any info i could post to help diagnose the problem?

This is the memory map atollic stlinkgdbserver returns to gdb
<memory type="ram" start="0x0" length="0x8000000"/>
<memory type="flash" start="0x8000000" length="0x100000">
<property name="blocksize">0x4000</property>
</memory>
<memory type="ram" start="0x8100000" length="0xf7f00000"/>
</memory-map>

looks to be a reset issue, not a memory map issue.
Running from the command line, it appears to hang for a very long time, but pushing the reset button moves it along.  typing  "continue" in gdb causes it to hang again (after programming) and pressing reset once more seems to work.  there's code in stlink to try and reset after programming, looks like it's missing something for f4.

@andrea-rockt :
Please recheck the issue. I guess it is fixed in git.
Bye

Thanks, the issue is now fixed i can now debug the hardware target directly from eclipse GDB Hardware Debugging.


Windows Defender scans WSL1 files

Windows Build Number
Microsoft Windows [Version 10.0.19043.1165]
WSL Version

[ ] WSL 2
[X] WSL 1

Kernel Version
Linux version 4.4.0-19041-Microsoft
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps

In WSL1, create a PHP file with the following contents using an editor such as nano (example: php_system_echotest.php)

<? php

system ("echo test");

Run php_system_echotest.php

The console prints the error Could not open input file: php_system_echotest.php and Windows Defender detects the threat (see image below).

Image content:
Backdoor: PHP / Dirtelti.MTG
Warning level: Critical
State: Active
Date: 2021/09/13 23:53
Category: Backdoor
Details: This program provides remote access to the installed computer
Affected items: (path to the actual file in the WSL1 file system)
supplement:
-When I try to create the above file using WSL1 and VS Code (Remote - WSL), Windows Defender detects it the moment I save it.
Expected Behavior
Microsoft has announced that "Do not access WSL1 files from Windows tools", so I thought the files would run undetected.
Or, even if it was detected, I thought that the file path was not the actual file
https://devblogs.microsoft.com/commandline/do-not-change-linux-files-using-windows-apps-and-tools/
Actual Behavior
Windows Defender scans the WSL1 file system for threat detection.

The detected file may have the contents remaining but cannot be displayed, or the contents may be rewritten.
In the image below, php_system_echotest.php (PHP that does system (" echo test ";)) has some contents but cannot use xxd and cannot be executed as PHP because it will be detected by Windows Defender.
The contents of php_cleartest.php (PHP the does system ("clear ";)) have been changed.

Diagnostic Logs
No response

This is expected behavior, in WSL 1 the Linux files are stored as actual Linux files on your machine and all Linux system calls are executed as Windows system calls at the end of the day, both of these are in the domain of Windows Defender.
If you'd like to resolve this, I'd recommend that you upgrade to use WSL 2 instead. Are you able to do so?

See https://github.com/Microsoft/WSL/issues/1852#issuecomment-371605730 (and probably others for the A/V side of things)
TLDR: You can add all your pico processes to Windows Defender (Security) to get them exempt.

Does direct file access by Windows Defender have a negative impact on WSL1?
If it doesn't affect WSL1, I can use it with confidence.
(I want to use WSL1 not only as a development environment but also as one of the CLI environments, so I would like to continue using WSL1)

What I can tell you is part of why WSL2 exists is due to the major filesystem performance difference. Even when you exempt your processes, Defender still messes with the performance, presumably due to being treated the same as the rest of the Windows filesystem but likely a bug somewhere so that it doesn't treat the Linux filesystem exactly the same. With WSL2, Defender plays a part but in the same way and has less of an issue. There are threads (probably moved to Discussions) that talk all about filesystem perf. I suggest you check those out.


fix: remove el10 support

previous fixes for removing el10 support did not drop
el10 from meta/main.yml

[citest]


Better handling of empty Favorites pane

Until you add a favorite, the Favorites pane is blank. We need to insert copy there. I think favorites play "more often". If not, you'll have explained it to me in the previous issue and I'll fix this.

To add favorites (which makes them play more often), click the star icon in one or more of the videos listed below in this sidebar. You can always come back here to un-favorite a video if you get tired of it.

This is part of the UI enhancements coming soon.


Improvements to sendToClient method

The "sendToClient" method is injecting the variables to the "js" placeholder in the layout. We have the "js" placeholder near the end of the page. When we try to access a variable from a js method that is defined before the sendToClient variable injections, it is giving errors. We can workaround this problem by wrapping our method calls inside document ready method.
But as an improvement to the "sendToClient"  method can we injection the variables to the header section of the page without depending on the placeholder. If that is not possible then prepending to the headJs will make the variables available to all the other scripts.

I think it should always goto head, this is a bug in our code. giving the dev the option to select is going to complicate things

Closing as repo is deprecated.


added function to specify plotting criteria from geojson input.

Also made SIC 0% to 9% plotted as transparent to remove the blue ocean from the output pngs

This allows pngs to be generated from geojson attributes other than 'SIC' , for instance 'fuel'


Sorting a set withing a defn

Hi @kkinnear, I thought I got this right, but I am not yet a zprint master it seems.
I got the following set:
(defn make-pedestal-routes
  "Builds a set of routes given their dependencies, typically services or
  repositories."
  [deps]
  #{["/reference-range/sets"
     :get (controller.reference-range-set/all-sets* deps)
     :route-name :get-all-reference-range-sets]
    ["/reference-range/sets/:id"
     :put (controller.reference-range-set/update-set* deps)
     :route-name :update-reference-range-set-info]
    ["/api/v1/measurements"
    :post #ig/ref :com.cohesic.acuity.web2.controllers.api.v1.measurements/submit
    :route-name :submit-measurements]})

And basically I would like to order its entries alphabetically (the /api should be first).
I am trying with:
;;!zprint {:fn-map {"defn" [:arg1-force-nl-body {:next-inner {:set {:sort? true}}}]} :vector {:fn-format :flow} :vector-fn {:indent-arg 1 :constant-pair-min 2}}`

What am I doing wrong?

Awesome that works like a charm!


New: Add no-parameter-properties

This includes
New rule no-parameter-properties
Corresponding test
Corresponding documentation
Update to README.md to include the new rule
Related to #5 (TSLint compatibility)

I resolved the conflicts on here too @weirdpattern, so make sure you pull before continuing to work on it 👍

I did the same as you did, use github to resolve the conflict...


Update storage-use-azcopy-files.md

@MattiaSarti : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Damage Pop Off Spacing

Mod Version: 1.11.2-<IP_ADDRESS>
Forge Version: <IP_ADDRESS>2
Link to crash log (if applicable): N/A
Description:
The damage pop-offs overlap the critical damage text completely, so it's hard to read either. This has been happening for quite a few versions now. I remember they used to be spaced, as in they'd pop-off in different directions/speeds, but now they pop-off together. Here's a little screenshot (it was kind of hard to take):
http://i.imgur.com/IkGRklp.png

I noticed that, too.  I made a tweak to make sure the crit power word is a half block above the damage amount.

Pushed v<IP_ADDRESS> BETA that has a fix.

Thanks, works great!


Leaking content in convlist

in convlist message content is leaking between two convs 🤔
Green circled word (כן Hebrew) is last line in conv
Yellow marked line (with the ® char) is realted to next conv

It took a while but now i remember you :)
You're the guy from node4good/formage which i used briefly at work. I remember i also bothered you about some issue i had with it. What goes around comes around!
Thank you for your report, I will have a look.

an other one

This time grabs some HTML https://gist.github.com/refack/0bc4e6732226da6e1d20cb1b934ca653

I am not able to reproduce yet

I assume It a mix of unicode (®) ( 😍😍😍😘😘😘💖💖💖💕💕💕)  and Hebrew (?את הזמנת לי בורקס בבלו אפרון).
I'll try to trace/debug

Can I get a hint, as to what's the entry point to the client process?

I have 2 users. If you can provide an exact sequnce to send from yakyak->hangouts and from thangouts->yakyak i can try.
I tried to copy-paste messages from your gist dump but was not lucky.

Can you please check if you have some kind of exception on "replaceChild" when this happens ? Thank you

Not exception in console. my current assumption is it's a parsing issue in
hangupsjs
On Mon, Jan 16, 2017 at 2:19 AM, Davide Bertola<EMAIL_ADDRESS>wrote:

Can you please check if you have some kind of exception on "replaceChild"
when this happens ? Thank you
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yakyak/yakyak/issues/543#issuecomment-272789667, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAF6s_vdj26joIitML9ihDw6q8N6y1Uzks5rSxnogaJpZM4LedjV
.

seems like ec1c6b4 with the twemoji fix resolved this, but I keep watching


login file committed

@niteshk305 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


feat: podman support?

Description
should we plan to support podman?
for Linux users, podman may be their best choice for managing containers and images.
also for macOS users, podman is  available now.
podman can run without a daemon service and sudo permission.
supporting podman may increase the user experience by hidding containers under the hood

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Yep, See here https://github.com/tensorchord/envd/issues/282
The issue is dup, I am closing it. Let's discuss in the issue #282


current master branch navigationState conflict on RN 0.24.1

As I was testing the master branch everything seemed to be working fine until I noticed one critical problem when changing scenes using type: push.
I pinpointed the issue to this snippet of code in the DefaultRenderer.js file:
// (Starting at line 62)
dispatchFocusAction({ navigationState }) {
    if (!navigationState || navigationState.component || navigationState.tabs) {
      return;
    }
    console.log ("\nNavigation state children before error: ", navigationState)
    const scene = navigationState.children[navigationState.index];
    Actions.focus({ scene });
  }

I noticed that my console.log was printing twice in a row before the following error occured:
ExceptionsManager.js:61 navigationState.children[1].key "scene_position_feed" conflicts withanother child!
For some reason the same key (position_feed) was set twice.
Code:
I was pushing this scene:
 <Scene key="showPost" component={Post} title="Post"
                  navigationBarStyle={styles.navStyle}
                  titleStyle={styles.titleStyle}
                  sceneStyle={{top: 64}}
                  leftButtonTextStyle={styles.titleStyle}
                  rightButtonTextStyle={styles.titleStyle}
  />

From the feed scene:
 <Scene key="feed"
                    type="push"
                    sceneStyle={{top: 64, flex: 1,}}
                    component={FeedLayout} title="Feed" rightTitle="Post"
                    onRight={()=> Actions.post()}
                    leftTitle="Map" onLeft={ () => Actions.map({all: true,})}
                    navigationBarStyle={styles.navStyle}
                    titleStyle={styles.titleStyle}
                    leftButtonTextStyle={styles.titleStyle}
                    rightButtonTextStyle={styles.titleStyle}
  />

If there's anything else I can add in here to help, let me know.

#636 Branched off from this issue


Add PodDisruptionBudget

It seems like it'd be useful to add a PodDisruptionBudget to the manifest files, at least for the master nodes.

I'm interested in reviewing PRs.

Feel free to contribute to #133

I think this could be closed as merged now

Fixed in #133.


[macOS] Cannot toggle full-screen with decorations: buttonless

Currently on macOS, when running with the config:
window:
  decorations: buttonless

The lack of buttons and standard menu items make it (seem?) near-impossible to toggle full screen for a window.
As a temporary workaround, I've added to my config:
key_bindings:
  - key: F
    mods: Command|Shift
    command:
      program: osascript
      args:
        - -l
        - JavaScript
        - -e
        - |
          const fullScreen =
            Application('System Events')
            .processes['Alacritty']
            .windows
            .whose({focused: {'=': true}})[0]
            .attributes['AXFullScreen'];
          fullScreen.value = !fullScreen.value();

But that required some tinkering with Automation that I wasn't already been familiar with.
This issue could be made redundant with #2012 ("Implement Alt + Enter to fullscreen on Windows") if it were solved/retitled more generally like "Expose ToggleFullScreen as an Action".

The lack of buttons and standard menu items make it (seem?) near-impossible to toggle full screen for a window.

So why use buttonless then? If you need the buttons, you probably shouldn't be using buttonless.
I'm using buttonless myself since I'm using a third party WM and using shortcuts to toggle fullscreen is no problem at all.

So why use buttonless then?
[…] I'm using buttonless myself since I'm using a third party WM

By far the majority of macOS users—even of developer-niche applications like Alacritty—are using the system WM.
I'm using buttonless because transparent looks like crap since its buttons overlap the terminal text, and full/none consume vertical space with a title bar used only very very rarely, and whose existence then is only necessary because of the lack of either a keyboard shortcut or exposed menu item.
Changing in and out of full-screen isn't something that one does very frequently. But being unable to do so at all without having to permanently settle on one of the above compromises seems to be a pretty "obvious pain point, easy to fix" type of issue.

While #2012 will likely add an action that allows doing this on all platforms, it's already possible to add a global shortcut for maximizing windows on macos and that was working great for me last time I tested it.
Transparent overlapping is also another issue that is tracked separately. So there's nothing specific to this issue that is planned to be done here.


Freeform flags

Seems like a recurring issue of keeping Fig and Docker run flags in sync. How about a freeform flags option so people aren't blocked until fig.yml has proper support?
myapp
  build: ../myapp
  dns: xxx.xxx.xx.x
  flags: --dns-search=my.domain

Scratch that, didn't notice it was using a python docker client under the hood.


.travis: experiment with faster build

This should reduce the overhead of starting and running tests.
This is a quick draft the final solution might look different.
This is something similar I did in https://github.com/mattn/go-sqlite3/pull/693, which reduced the total running time 2x.
Initial run demonstrates the time difference https://travis-ci.org/github/gonum/gonum/builds/662330315

I suspect that this was fail out due to overtime. The approach we use now was actually done to reduce the time in running tests.

@kortschak what's the limit on time for each job?
AFAIK, travis does have some large limit (50min), but the only criteria is that the job must be outputting something in a decent interval.
PS: the current approach definitely isn't optimal, since it's running some things multiple times that don't make a difference with different tags.

@kortschak, indeed, it looks like there isn't as big of a win here as I hoped.

Yes, 50 minutes is the limit and 10 for silence (we don't hit that ever unless something terrible has happened).
I agree that it's not optimal. What it your plan to only run tagged tests where they are impinging on the package being tested? Do we collate a list of packages that use or have a transitive dependency on a package that uses the tag in the tag set?

I think most of the tests end up transitively depending on internal/math, internal/asm. So I don't think that approach would help significantly.
If you mean only test the packages that have specific tags. I think having other packages test, some other package behavior is a really good way to flush out corner cases.

The only one that it really likely to save any thing would be bounds; that tightens the bounds checking in calls that are internal in mat, so it would only affect packages that import mat.

So one thing I noticed, is that none of the tests have been marked with "t.Parallel()". It probably wouldn't help test speed on travis, however would help locally. A quick local experiment with mat package made it go from 30s -> 8s.

That sounds like a worthwhile thing to do.

I'll close this one and start afresh.


Added all things necessary for LPT scaling

Added <sqrt(dEdx)/pT> for In,Out,MC and Refit.  Attempted adding LPT scaling to notebook, but not working yet

OK. Merging. Lets debug it later. We will post results here


Milestone 0.1.0

Coverage remained the same at 100.0% when pulling e5c91629f1aa4a8c67f74dff17e08527914a6f8b on milestone-0.1.0 into 7c7befefe22df25d90c8a4fe3e48a7dbc53a416a on master.

Coverage remained the same at 100.0% when pulling 56d017d5a989f7a364e31a11f82de659f37b00e5 on milestone-0.1.0 into 7c7befefe22df25d90c8a4fe3e48a7dbc53a416a on master.

Coverage remained the same at 100.0% when pulling 56d017d5a989f7a364e31a11f82de659f37b00e5 on milestone-0.1.0 into 7c7befefe22df25d90c8a4fe3e48a7dbc53a416a on master.


cmd/go: regression in behavior of DepsErrors

The behavior of the DepsErrors field in the output of go list -json -e has changed between Go 1.14 and tip.
In GOPATH-mode, have two packages sandbox/foo and sandbox/bar, with sandbox/foo/foo.go containing
package pkg

import "sandbox/bar"

and sandbox/bar/bar.go containing
ackage bar

Running go list -e -json . in sandbox/foo with Go 1.14.4 would produce the following DepsErrors:
	"DepsErrors": [
		{
			"ImportStack": [
				"sandbox/foo",
				"sandbox/bar"
			],
			"Pos": "foo.go:3:8",
			"Err": "\n../bar/bar.go:1:1: expected 'package', found ackage"
		}
	],

the ImportStack would clearly indicate that this issue occurs in the sandbox/bar package.
However, running the same command with tip (f92337422ef2ca27464c198bb3426d2dc4661653) produces the following output:
	"DepsErrors": [
		{
			"ImportStack": [
				"sandbox/foo"
			],
			"Pos": "foo.go:3:8",
			"Err": "expected 'package', found ackage"
		}
	],

the ImportStack is truncated, and it is impossible to tell which package the error is coming from. This was caused by 641918ee09cb44d282a30ee8b66f99a0b63eaef9 (/cc @matloob).
Interestingly, between 1.14 and 641918ee09cb44d282a30ee8b66f99a0b63eaef9, 74d6de03fd7db2c6faa7794620a9bcf0c4f018f2 improved on the error, by using a more accurate value for Pos:
	"DepsErrors": [
		{
			"ImportStack": [
				"sandbox/foo",
				"sandbox/bar"
			],
			"Pos": "../bar/bar.go:1:1",
			"Err": "expected 'package', found ackage"
		}
	],

Just to set expectations, this may or may not make go1.15rc2. (I agree that it's a regression, but it doesn't seem severe enough to hold up the release if everything else is ready.)
CC @matloob @jayconrod


[4.2][ConstraintGraph] Fix contractEdges to gather constraints only once

Currently we have this non-optimal behavior in contractEdges where
for every type variable it gathers constraints for its whole equivalence
class before checking if any are "contractable", instead constraints
could be gathered/filtered once which removes a lot of useless work.
Resolves: rdar://problem/29358447

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 7624ea6ee69184759bbf8902b602a8ab3c8ef567

Both failed with EOFException, re-running.

@swift-ci please test Linux platform

@swift-ci please test macOS platform

@swift-ci please test source compatibility


Add support to Portuguese language

Closes #478
Closes #479

What I did

How to test

Checklist

[x] Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests).
[x] Make sure to add/update documentation regarding your changes.

Code Review - OWASP 480.xlsx


PP-6147: Upgrade node to v12.4.1

WHAT
This is the latest version of node supported by GOV.UK PaaS. We need to
be on at least v12.9.0 to use AWS CloudFront's Field Level Encryption.
The issue with statsd we encountered when we upgraded to node v12.13.1
(see PP-5917)
looks like it's fixed in v12.4.1 (according to the node release notes).
NOTE: I'm not sure how to test that the statsd issue hasn't
regressed, so this will need a look by someone with more understanding
of the issue.
HOW
Use your knowledge / testing to confirm this isn't going to break
things in production.

Confirming that 12.14.1 addressed the issues described in https://payments-platform.atlassian.net/browse/PP-5917
See https://github.com/nodejs/node/releases/tag/v12.14.1 and https://github.com/nodejs/node/pull/30196

Okay, lets :shipit: then!


Gather more data about unavailable bikes

Having a list of all bikes ask what's happening with unavailable bikes.

endpoint: https://app.socialbicycles.com/api/bikes/<bike_id>
status: now always available
repair status: soft_broken


misc. updates to README and generation of contribution guide.

per offline discussion this PR starts to address the restructuring of the README content and contribution guidelines.
addresses some of the items brought up in:

#96

let's start with this and massage as necessary.


fix: stderr logger in windows os

Description
Fix stderr logger in windows os.
Related issue(s)
If this Pull Request is related to an issue, mention it here.

Fixes #1077

@amirvalhalla I have concern for memory leakage here.
To test it, change log levels of all modules to trace. You can also add an infinite loop to just write a log. Watch the memory of the system.


Please comment here to be added as a collaborator

Say anything :smile:

Hi!

anything

Please add

a comment

Hello!

Hi there!

:tada: @maxxrafen, @dwightmulcahy, @sethuprem, and @keithnyc are now  repository collaborators. :balloon:

Hello there!

I am here!

Wooohooooo

anything

Howdyyy

😍 :octocat:

Hello!

Heya

Hello

Please add me

yo

Hi

hola!

:tada: @jmaciorowski, @james-stuzynski-teradata, @igor101, @yxiang92128, @Brits02, @CarmenPalMar, @mwuenschel, @ntagg, @cbendler, @jcanon, and @coconut2015 are now  repository collaborators. :balloon:

comment

Add Me please :)

:+1:

hi

add me

anything

I want in

Greetings

Hello...

Hi!

hi!

hello

Hi Add me

Brad was here

Hey

pls add

Hello!

Hey

hey

Hi there

hello

Hi

Please add me.

Hello!

hello

Hi.

:tada: @kshafer1, @jn185023, @mmanieri, @VittalHaridasu, @JCaruso75, @bgoldbergm3, @damleak, @maxbarzel, @richdaley, @mwitiak, @J-Barbour, @sr122322, @rohitssurve, @dsingh85, @bbrown99, @jblaney, @SrinuKani, @lm121565, and @richdaley are now  repository collaborators. :balloon:

greetings!

:tada: @sofiehoeg, @v-smelnik, @rdahlM3, @rf185026, @TDKurt, @rsujatinov, @darthmolen, @junejlee, @kshafer1, @jn185023, @mmanieri, @VittalHaridasu, @JCaruso75, @bgoldbergm3, @damleak, @maxbarzel, @richdaley, @mwitiak, @J-Barbour, @sr122322, @rohitssurve, @dsingh85, @bbrown99, @jblaney, @SrinuKani, @lm121565, and @richdaley are now  repository collaborators. :balloon:

hello

Hi

hello

Hi Please add me

Hello

:tada: @mmcq, @janebeckman, @sf122240, @smandadi1, @mollanlew, and @lindaab are now  repository collaborators. :balloon:

:tada: @vankiyono is now a repository collaborator. :balloon:

:smile:

hey

hello @githubteacher

:tada: @dietrichw, @itaimo, and @stoe are now  repository collaborators. :balloon:

Hello 🚶 👋

:tada: @hertogjanduevel is now a repository collaborator. :balloon:

hi

:tada: @ernipun1 is now a repository collaborator. :balloon:

🍰

:tada: @brianamarie is now a repository collaborator. :balloon:

found it - thank you!

:tada: @tomhohenstein is now a repository collaborator. :balloon:


add classes hook for customizations

the main container: fi-preset-color-picker
for items: fi-preset-color-picker-item
for active/selected item: fi-preset-color-picker-item-active

not sure if it should be documented but I added either way

Can you change these to maybe 'pcp-' instead of 'fi-'?
I don't want people to think they are filament hooks.
😀

fair, from dev pov, my eye used to scan fi- for classes in the source 😅

sweet, thanks.


Add screenshot of project to Readme file

Description
Screenshot of project helps to contributor to understand the project.So i want to add screenshot.
Tech Stack
By taking screenshot of project and add to Readme file
Reference
No response
Additional Context
No response
Are you creating this issue for yourself?

[X] Yes
[ ] No

/assign


Buy credits with commerce

Is it possible to buy credits with commerce or stripe? Coule be an awesome feature.

I did consider this, to work with Craft Commerce. Need to play with Craft Commerce a bit more to add this functionality in :)

Integrating with Commerce would be great to build a Loyalty programme for each product purchased and then to be able to use those credits to apply a discount on future purchases.

It's in the works :) Just a bit busy at the moment to rework it for Commerce. Might even be a Craft 3 version only. We'll see.

@bymayo Any news on this rework? We are considering using the current version as a starting point for a simple loyalty implementation but I'm curious when we can expect a new release.

@kyle51north Yeah, it's on the list to work on... BUT - With the release of Craft 3 (And Craft Commerce 2 Beta at beginning of 2018) this plugin won't be reworked with this additional functionality for Craft 2.
I haven't got time to add the functionality in for Craft 2, then rework it for Craft 3 sadly :(
Is it likely you'll be using Craft 3?

@bymayo We've decided to roll out the project in two phases, first with Craft 2 end January and them with more functionalities after Craft 3 release. So yes, we'll be using Craft 3, but at a later stage. Will be sure to check out this repository!


Does vSwarm support Firecracker-Containerd

Hi, I noticed that vSwarm only supports applications deployed and invoked by Knative, is that true? Do we have a feature to run those functions via Firecracker-containerd? It's interesting to see how real-world FaaS applications perform snapshots. Or do you have any advise to walk around this? Thanks!

@DanielLee343 yes, all vHive runtimes are supported (but only container-based setting is tested in CI). However, to use Firecracker, you need to modify YAML files, which is the limitation we are currently working on.
More details: https://github.com/vhive-serverless/vHive/blob/main/docs/quickstart_guide.md#iv-deploying-and-invoking-functions-in-vhive


[Bug] KubeRay Worker group pod keeps restarting on EKS - Fails to CrashLoopBackOff

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
Others
What happened + What you expected to happen
I am following steps 2-5 here on an Amazon EKS cluster. I am able to run a job and access the dashboard, however, the workers keep restarting (K9s screenshot attached)

Logs of the ray-worker can be found below:

Running the same  steps on kind works as expected, with the worker pod being in ready state and not failing

Reproduction script
kubectl create ns ray-system
helm repo add kuberay https://ray-project.github.io/kuberay-helm/ -n ray-system
helm repo update
helm install kuberay-operator kuberay/kuberay-operator --version 1.2.2 -n ray-system
helm install raycluster kuberay/ray-cluster --version 1.2.2 -n ray-system

Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Do you have a reproduction script especially the setup of your EKS cluster so that I can reproduce on an EKS cluster?


Unify name mangling rules

Since BuckleScript is going to release a v8 and maybe Reason a v4, I think now could be a good time to fix name mangling issues once for all and stick to one rule.
Right now we have this Reason code:
let foo = {"_to": 10, "_type": 1};
type bar = {
  _to: int,
  _type: string,
};
let bar = {_to: 10, _type: "bar"};
ReactDOMRe.renderToElementWithId(<input type_="text" />, "preview");

compiling to:
var foo = {
  to: 10,
  type: 1
};
var bar = {
  _to: 10,
  _type: "bar"
};
ReactDOMRe.renderToElementWithId(React.createElement("input", {
          type: "text"
        }), "preview");

which is definitely not coherent.
I'd be in favor of using trailing underscores since leading underscores is already used to name unused variables but I'd be happy with any coherent rule.

Thanks for bringing this up. Can you describe your goals for unifying the name mangling rules? You want a consistent way across what specifically?

My goal would be to have the same name mangling rule to remember for Bucklescript, Reason and JSX instead of at least 3 rules right now.
Something like: if you want to have in JS a variable or object field named after a word reserved in BuckleScript, Ocaml or Reason, add a trailing underscore to the reserved name and it will be output correctly in JS, whether you use a record, a JS object or a React component.
I'm talking as a user, I'm sure there are tons of things to consider before changing this behavior since I know things went wrong at least once with method mangling and I'm not even sure in which of the 3 repos (BS, Reason, RR) things have to change but I think it will improve devs' quality of life quite a lot when writing bindings.

These are really easy to fix or improve - the only challenge is that last time we fixed them to be consistent everywhere, it ended up breaking existing assumptions that relied on the inconsistent behavior. So let's say you have a perfect approach "x" in mind. Changing the parser from imperfect approach to x, will change the compiled output of other libraries that use Reason under the assumption of the imperfect approach.
So the way forward is that we will make a breaking change in the parser, but it fixes it from a completeness/consistency perspective, while:
Allowing each project that uses Reason to opt into its own version of the parser - allowing two versions to simultaneously coexist. There may be some surprises when someone opts in, but calls an existing library written under the old (imperfect) assumptions. But over time everything should converge to consistency and completeness.
There may be some assumptions that BuckleScript makes about how the mangling should work - but BuckleScript's vendored Reason should make the changes necessary to that vendored Reason parser in sync with its own assumptions.
Thank you for bringing it up in an issue so we can track it.

Thank you Jordan for considering this issue seriously, I think in the long term these apparent "small fixes" can really smooth out the developer experience.
Of course I realize it can break a lot of things.
Maybe we could keep the old behavior of trimming leading underscores with depreciation warnings and add the new behavior while documenting it as the recommended way since the two rules are not mutually exclusive. It could help reduce the risks.

What is unacceptable (we've discovered) is to make any kind of changes (even if improvements) in the Reason parser name mangling, that changes the parsing of existing libraries who did not opt into the new improvements/version.

Would it be more acceptable on a major version boundary? This might be a good change to target for v4 🤔

Would it be more acceptable on a major version boundary? This might be a good change to target for v4 🤔

No actually it's not even acceptable to change the meaning of code that was authored in v3, just because some other package uses a v4 which is why this is difficult. If someone writes something in v3, and it is being called from another package written in the next version, we cannot change what the called code written in v3 compiles to.

Doesn't that mean there can never be a breaking change? We survived big upheaval in the move from v2 to v3, although the project is a lot more popular now, but it would be a shame if we were never able to make changes like that again.


Pd-RuleSet-Rules

Uncomment pagerduty ruleset creation, and change from simple resource to standard resouce.
Rules are a nested item so need the ruleset param to work.
Tested this with own pagerduty set up and rules are created as expected

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

@googlebot I fixed it.


(Experimental) support of the nogil fork of CPython

👋 love PyO3!
We have a use case for trying out the nogil fork of CPython (https://github.com/colesbury/nogil-3.12/tree/nogil-3.9) but I don't think we'll get very far until we refactor and recompile our code which relies heavily on PyO3.
I can't say I understand the impact at any level, but thought I'd throw this on the radar and get the conversation going.

Please have a look at #2885 where some conservation on this has already happened.

Weird I didn't find anything when GitHub searching for "nogil" we can close as duplicate

Ah I was only searching issues, not PRs

No worries. Maybe you can use the code proposed in the PR can be brought to bear onto your use case. Ideally after a rebase though.

Luckily we sidestep the "library" issue with nogil, since we're shipping a python binary and application.
We all are just using pyo3 to consume frozen dataclasses (with possible references to other frozen dataclasses) run some rust code on the data, then construct and return other frozen dataclasses. In a pool of threads.
Since we aren't mutating objects, I suspect nogil will cause much less contention in the threads, so I'm excited to try it out


Add documentation for the new aws S3 Object capabilities.

In taipy doc page must be updated regarding the new capability of the S3ObjectDataNode implemented in the PR https://github.com/Avaiga/taipy/pull/1868
The file is located at docs/userman/scenario_features/data-integration/data-node-config.md

@AdeshGhadage FYI

@jrobinAV can you assign me this issue?


Please add specialized custom image as unsupported scenario.

We encountered an issue where the VMSS was using specialized custom image, which would include the original VM computer name in the image, causing duplicate names and bootstrap failures on the DevOps side.
Create a scale set from a specialized image version using the Azure CLI - Azure Virtual Machine Scale Sets | Microsoft Learn
Turned out that using specialized image is unsupported and it had to be generalized custom image. This is not specifically called out in this doc. It'd be nice to get it added as a limitation to avoid future issues.

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

ID: 756d9c64-a802-61ad-ba6c-6061d2d747cf
Version Independent ID: 012518b7-0282-f5b0-5206-8a9d1902b8d3
Content: Azure Virtual Machine Scale Set agents - Azure Pipelines
Content Source: docs/pipelines/agents/scale-set-agents.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-agents
GitHub Login: @steved0x
Microsoft Alias: sdanie

@qqnarwhal -- Camiu, thank you for your considered feedback.
@steved0x -- Steve, please look into this issue.

Hi, checking to see if you've had a chance to review this. Thank you!


Switching Polymer to "dom: shadow" breaks row expanding

When using shady mode, problem is not reproduced. It only happens when switching to shadow.
iron-data-table.html:781 Uncaught TypeError: Cannot read property 'item' of undefined

This is the next code:
      _itemCollapsed: function(e) {
        var item = e.detail.item || e.model.item;
...

I found out that it happens on first call of the listener, and at this moment e.model is undefined for some reasons. Looks like a too early listener call bug.

Hmm, seems to be working here: http://jsbin.com/kefajad/edit?html,output
Are you able to some changes that would reproduce the problem there?

Sorry, it's my fault. Occasionally used beta1 while testing that. All is OK with beta3.


Skip Redirect Fail

New Issue Checklist (tick off like this: [x])

[x ] I checked existing issues (open and closed) for possible duplicates

What is your browser?

[ x] Firefox
[ ] Chrome

What is your operating system?

[ ] Linux
[ ] Mac
[x ] Windows

Description (please include examples/screenshots where applicable)

is not able to resolve this redirect:
http://2baksa.net/go/go.php?url=https://rg.to/file/56daed151c474b338aa8509b6a8a82db/ZD.Soft.Screen.Recorder.<IP_ADDRESS>b.rar.html

Works for me, I can click and it goes to rg.to... Check that you don't have some bad settings.


Underscored Methods

I would like to see this package export services with underscored methods, similar to all DB adapters starting in V5. This is something I can handle if no one has any objections.
I accidentally opened this issue under a different user. So i closed that one and re-opened under my main GitHub account.

Quick follow up to this. I was initially thinking I would need to go into each service and create the methods, bit I believe I could just actually update the BaseService.
For example
const Stripe = require('stripe');

module.exports = class BaseService {
  constructor (options = {}) {
    if (!options.secretKey) {
      throw new Error('Stripe `secretKey` needs to be provided');
    }

    this.stripe = Stripe(options.secretKey);
    this.paginate = options.paginate = {};
    this.id = 'id';
  }

  _get(id, params) {
    return this.get(id, params)
  }

  // ...etc
};


Add support for composing function(s) into Processors before and after

Based on the current binding support added to channel binders we now need to be able to handle Processors which are kind of unique given that the function could be composed before and/or after. This would require additional property. Based on the internal discussion we all seem to agree that the *function.definition... will default to after and something like *function.definition.before.. would be added for cases where one need to add function definitions before the processor.

Tagging @ilayaperumalg @dturanski @sabbyanandan @sobychacko


Remove graphical branch overview

Reasons:

Feature is rarely used if at all
Performance issue once there are several hundred commits and making it work requires major dev #5090
There are much better tools like Git Graph

"Branch > Overview" also contains the "Merge" feature. I suggest keeping this but putting it on a new page (#5402) under "Branch > Merge".

+1
(I also have a feeling that merge is not used either)

I thought so too, but we just had a case looking for merge #5401 😃

👍


HASS.Agent crashing

Just intalled it on on Windows 10 machine. Every time I try to start it, it crashes. I uninstalled and reinstalled and it still crashes.

You're not giving me much to work with here 😁
Do you get a message or popup when it crashes? And could you please send the content of the logs (if there are any), you can find them at %appdata%\LAB02 Research\HASS.Agent\logs.

Sorry about that. It's working now. I didn't see any message or popup. For what it's worth I'm attaching the log from yesterday.
2022-06-08_HASS.Agent.Satellite.Service_20220608.log

Interesting log, thanks for sharing - I'll better handle unauthorized connections. Glad it's fixed :)


Update view-email-security-reports.md

Ability to filter up to 90 days was released in August 2021. Updated the doc accordingly.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


CallerProxy - Return primitive default value in case of exception

This is to avoid a NullPointerException on Proxy instance when casting the returned null value into the primitive return type.

@ederign Could you please review?

+1

master: 4800a5b0af082bbbe6c416d07d1ba8b2af7e061a


Publish jardiff to maven

Would it be possible to publish this repo as a standard Maven JAR into maven central? The main reasoning behind this is to allow for alternate ways to launch jardiff, specifically coursier which for example would allow you to run jardiff which this simple command
cs launch org.scala-lang::jardiff:1.7.0 args

We'd accept a PR that added sbt-ci-release (and we'd take care of adding the necessary publishing secrets).

We'd accept a PR that added sbt-ci-release (and we'd take care of adding the necessary publishing secrets).

Is using sbt-github-actions additionally to generate the github actions permissible?

Is using sbt-github-actions additionally to generate the github actions permissible?

Sure


PYIC-1675 Disabled default AWS endpoints for APIs

Proposed changes
What changed
Disabled default AWS endpoints for APIs
Why did it change
To force use of custom domain names
Issue tracking

PYIC-1675

Checklists
Environment variables or secrets

[ ] No environment variables or secrets were added or changed

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

Other considerations

[ ] Update README with any new instructions or tasks

Does this break dev environments?

Does this break dev environments?

This will disable the "execute-api" URL on private API so if anything relies on that URL it will stop working.


Fix version skew for release-1.13

Fixes version skew e2e and integration tests for the release-1.13 & master tests.
Namely, this patches the default cardinality integration daprd master test as the default is now low.
Updates integration and e2e binary builders to include wfbackendsqlite go build tag.

/test-version-skew


Device selection through onnxruntime-directml

Hi,
I am using directml through onnxruntime and my platform has multiple directx 12 supported devices. Is there a recommended way to enumerate and select specific devices through python APIs?
Thanks

Currently, it's not possible to enumerate or select adapters through the Python API. For now, I think the only way to choose the DX device for ORT-DML in Python is by manually associating a preference for your python.exe in the graphics settings. For example:

We do want to improve this functionality in the future.
Note:
This is possible in the native C/C++ API, where you can provide an adapter index or a D3D12 command queue (implicitly referencing its underlying DX adapter). The C# API also has a way to specify an adapter index, but using it effectively means writing a small native function (exposed through a DLL interface) to enumerate adapters.

Thanks for the response @jstoecker
Having this ability in python would be very helpful.
For example, torch-directml exposes the enumeration through the following interfaces torch_directml.default_device(), torch_directml.device_count(), and torch_directml.device_name(i)

Sorry, I was mistaken. @smk2007 pointed out that we have some new APIs being added (in onnxruntime main branch, not yet released) to programmatically select an adapter based on high performance or minimum power; however, even in ORT-DML 1.16 you can select a device by index as follows:
# Specify "device_id" by index (available already in ORT 1.16)
providers = [('DmlExecutionProvider', {'device_id': '0'})]

# In a future release (ORT 1.17 possibly):
# providers = [('DmlExecutionProvider', {'performance_preference': 'high_performance'})]
# providers = [('DmlExecutionProvider', {'performance_preference': 'minimum_power'})]

session = onnxruntime.InferenceSession(model_path, options, providers=providers)

The existing "device_id" approach is not ideal, since it's not stable. For example, with a laptop, device ID mapping will likely be 0=discrete/1=integrated when the laptop is plugged in or in a high-performance mode but swapped to 0=integrated/1=discrete when the laptop is on battery. For this reason, the commented-out options above are being added.
If you have multiple discrete/high-performance GPUs, however, something like the torch_directml.device_name(...) API could be nice. For now, you can wrap some native code to enumerate adapters in the same order as ORT-DML to figure out which device ID corresponds to the device you want. I do think the specify-by-name approach is useful and something we might be able to push into an upcoming release.

Hi everyone,
i spotted this line in onnxruntine-directml changelog

Added new Python API to choose a specific GPU on multi-GPU devices with the DirectML EP.

There is some tutorial or some guide to use this new function? Browsing through the onnxruntime function I didn't find anything :(
Something like this can be really useful:

torch_directml.device_count()
torch_directml.device_name(index)


Update README.md

I think installing postgres client is optional, isn't it? And StackOverflow link looks a bit strange there.

I think installing postgres client is optional, isn't it?

If you mean optional in terms of running neon, then yes. But, the example instructions in https://github.com/neondatabase/neon/tree/fix-flaky-branch-tests#running-neon-database requires to have a psql command in $PATH.  We can change that to tmp_install/bin/psql if needed.
Note there is also a dependency note in the readme:

To run the psql client, install the postgresql-client package or modify PATH and LD_LIBRARY_PATH to include tmp_install/bin and tmp_install/lib, respectively.


cmd/cue: mod edit should support setting language.version

Currently, as of v0.9.0-alpha.4, cue mod edit provides functionality for editing requirements, the source field and the module field, but not the language version.
It should do so. Strawman interface:
cue mod edit --language.version=v0.9.0

We could also support upgrading the version to the current version language version with:
cue mod edit --language.version=current

This would fail like other cue mod edit commands if there is no language version already present,
as the syntax of the file is predicated on that.

Duplicate of #2920


Issue #59 - Inflation Adjustment

Ready for your review of PR for Issue #59.

Verified that all ltdb variables that are affected by inflation adjustment are included in inflate_cols and the named strings match data from ltdb column of variables.csv.  Function file data/data.py, line 494.  I have checked every row of variables.csv file.  There are no new variables for inflation adjustment.  There are 8 variables that are affected by inflation adjustment.

Copied similar logic from ltdb inflate_cols into "store_ncdb" function definition.  Use data from ncdb column in variables.csv.  In data/data.py, see lines 678 - 701.  Only 3 rows related to inflation adjustment have named strings in ncdb column.  I am not sure if this logic works as desired.  I added a definition for year, which is used in the last 2 lines.

Corrected several typos in documentation string part of data.py.   ("dataframe" and "instantiation")

Thank you!  Jennifer Yoon

Closing as this is now covered in #216


{netappfiles} Use == for literal comparison

Description
Using is for literal comparison is incorrect and results in SyntaxWarning during tests:
> azdev test
d:\cli\azure-cli\src\azure-cli\azure\cli\command_modules\netappfiles\tests\latest\test_pool_commands.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  assert len(pool_list) is 1
d:\cli\azure-cli\src\azure-cli\azure\cli\command_modules\netappfiles\tests\latest\test_pool_commands.py:38: SyntaxWarning: "is" with a literal. Did you mean "=="?
  assert len(pool_list) is 0
d:\cli\azure-cli\src\azure-cli\azure\cli\command_modules\netappfiles\tests\latest\test_pool_commands.py:49: SyntaxWarning: "is" with a literal. Did you mean "=="?
  assert len(pool_list) is 0

netappfiles


Add analysis_only field to SchedulingSpec to match database schema

Description
This brings the UI up to date with a schema change made in https://github.com/NASA-AMMOS/aerie/pull/229 (just merged today). That PR added a required analysis_only field to the scheduling specification table.
Motivation
This PR is motivated by my manual testing, where clicking the "new" button to start editing a new scheduling goal results in the following url (note the null):

Digging into the postgres logs, we see the following error:
ERROR:  null value in column "analysis_only" of relation "scheduling_specification" violates not-null constraint

Verification:
After making this change, clicking the "new" button in the scheduling pane takes you to this valid url:

Force push added a trailing comma, since that seems to be the prevailing style.

Force push addresses pre-commit requests to alphabetize


Add some useful operations to convert to different data types

For example:

ToStream
ToSet   (rename from deduplicate)
ToList
ToArray
ToVertices (Converts Elements and ElementSeeds to vertices, optionally extract SOURCE or/and DESTINATION from Edges/EdgeSeed)
ToEntitySeeds (converts vertices to EntitySeeds)
ToMap (Performs GenerateObjects with MapGenerator)

These could be used within a operation chain to aid chain operations together or at the end to return results in a particular format.

As part of this will the deduplicate and resultLimit options be removed from operations like GetElements? I think they should be as these are really options that apply to the whole iterable. It's more consistent with standard functional style for these to be operations/functions that are applied after the iterable is created, not as part of the creation of the iterable.

I think the issues with incorrect options being available on certain operations is being fixed as part of gh-419.

Thanks, looks like that issue will sort it.

Migration Steps
The 'Deduplicate' operation has been renamed to 'ToSet'.

Merged into develop.


Code insiders editor has been blurry

image
I use both insiders and the release vs code ; insiders is visibly blurry
vs code :

code Insiders:

I am not sure if the difference is visible in the screen shots
Steps to Reproduce:

Start up VS code insiders
Editor is blurry

So far I have tried

https://stackoverflow.com/questions/29966747/how-can-i-disable-gpu-rendering-in-visual-studio-code
https://www.reddit.com/r/vscode/comments/9szgkp/visual_studio_code_blurry/
and disable rendering on my nvidia control panel

nothing seems to work

It seems to be fixed int today's build; Text is back to normal

Well, it's most likely fixed only temporary and will be back once electron version bumps to 6 https://github.com/microsoft/vscode/pull/81644

@thkrishn
I wonder if this issue is reproducible when running VSCode in a browser or bare Electron. For that purpose, can you please:

git clone https://github.com/bpasero/vscode-runner.git
yarn
Web (Chrome only): yarn web
Electron: yarn electron

And report back if you still reproduce the issue in either or both web and Electron?

I am running this in windows so after the clone yarn builds the software?
If you have instruction about yarn... i would be happy to check it

@thkrishn well, you do not really need to build a lot, this is a very small repository. In order to have yarn on the command line you need to:

install git if not installed already (https://git-scm.com/)
install node.js if not installed already (https://nodejs.org/en/download/)
install yarn if not installed already (https://yarnpkg.com/lang/en/docs/install)

I tried installing rimraf still keeps throwing errors
C:\Users\t.krishna\home\test_yarn_web\vscode-runner>npm install --force rimraf
npm WARN using --force I sure hope you know what you are doing.
npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
npm ERR! errno SELF_SIGNED_CERT_IN_CHAIN
npm ERR! request to https://registry.npmjs.org/rimraf failed, reason: self signed certificate in certificate chain

npm ERR!      C:\Users\t.krishna\AppData\Roaming\npm-cache\_logs\2019-10-19T17_35_22_853Z-debug.log

C:\Users\t.krishna\home\test_yarn_web\vscode-runner>npm install --force fs-extra
npm WARN using --force I sure hope you know what you are doing.
npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
npm ERR! errno SELF_SIGNED_CERT_IN_CHAIN
npm ERR! request to https://registry.npmjs.org/fs-extra failed, reason: self signed certificate in certificate chain

npm ERR!      C:\Users\t.krishna\AppData\Roaming\npm-cache\_logs\2019-10-19T17_35_45_241Z-debug.log

C:\Users\t.krishna\home\test_yarn_web\vscode-runner>yarn web
yarn run v1.19.1
warning package.json: No license field
warning ..\package.json: No license field
$ node web
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module 'rimraf'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (C:\Users\t.krishna\home\test_yarn_web\vscode-runner\lib\download.js:13:16)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@thkrishn to make things a bit easier, I am now hosting a version to try: https://vscode-runner-vscode-runner-azure.azurewebsites.net/

thanks @bpasero ; If I have to be really picky its still a little blurry
But its not as bad when I opened this issue
My base line comparison is with vscode; I don't see any blur.

@alexandrudima is there a setting for the editor that could have an impact? I remember we had something to disable translate3d, but I am not sure we use that anymore.

@thkrishn sorry can I ask you to try to reproduce again from vscode-runner, it would be great to know if you see this in bare Electron as well. What is the build problem you see when running yarn?

So i figured the build problems; The system I am using is behind a proxy
after I fixed the build issues ... on http://localhost:8080/ I just get a blank screen

@thkrishn can you open the browser developer tools to see if something is printed to the console?

@thkrishn Can you also please try "editor.disableLayerHinting": true

@alexandrudima  it says Unknown Configuration Setting its not highlighted

Yeah, that is fine, it is a hidden setting. We have a bunch of editor settings which are not exposed in the JSON schema... So does "editor.disableLayerHinting": true improve things? (does it bring back subpixel antialising)?

@alexandrudima that looks like it improved the aliasing/blurring
Looks back to normal

Related -- https://github.com/microsoft/vscode/issues/75615

@alexandrudima
I started using VS Code for the 1st time earlier this year (on Windows), and I really disliked the font rendering, because it looked slightly blurry to me, like my eyes were out of focus. I just now ran across this editor.disableLayerHinting setting. For some reason I have to also set window.titleBarStyle = native, in order for disableLayerHinting to work, but turning off this layer hinting makes things noticeably easier for me to read. I'm glad I found it, and hope you leave it around and not get rid of it.
Looking very closely to the screen, I see that with layerHinting disabled text is a tiny bit jagged, and I can see why some people may not like it, but for me it's much better this way.


[AF-543] Refactoring in order to centralize FileSystem Calls and make…

… FS lazy
part of [BPMSPL-744] GIT related enhancements for scalable workspaces
https://github.com/kiegroup/guvnor/pull/507
https://github.com/kiegroup/kie-wb-common/pull/1112
https://github.com/kiegroup/jbpm-designer/pull/650
https://github.com/kiegroup/jbpm-wb/pull/835

@porcelli PR updated. I also tested the lock via external ssh and it works! ;)

Btw, the number of calls from lock that we saw it's not related with batch but pre/post commit: 	https://github.com/ederign/uberfire/blob/a4cf2e727c01a48fdf91ec5dd58f82dc1422913a/uberfire-nio2-backport/uberfire-nio2-impls/uberfire-nio2-jgit/src/main/java/org/uberfire/java/nio/fs/jgit/JGitFileSystemProvider.java#L2484-L2484 https://github.com/ederign/uberfire/blob/a4cf2e727c01a48fdf91ec5dd58f82dc1422913a/uberfire-nio2-backport/uberfire-nio2-impls/uberfire-nio2-jgit/src/main/java/org/uberfire/java/nio/fs/jgit/JGitFileSystemProvider.java#L2560 .

@porcelli the fail looks not related.

jenkins retest this

jenkins retest this

jenkins retest this

Jenkins please execute full downstream build

Jenkins please execute full downstream build

@porcelli fail on downstream looks like not related: https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/uberfire-downstream-pullrequests/51/
org.jbpm.process.audit.query.AuditQueryTest.unionQueryBuilderTest
org.kie.wb.test.rest.security.OrganizationalUnitAccessIntegrationTest.testRemoveRepositoryFromOrganizationalUnit[user: NO_REST].
Trying again!

Jenkins please execute full downstream build

@ederign caiu da cama? :)

Jenkins please execute full downstream build

Jenkins please execute full downstream build

@jhrcek thanks for the review. can you please take a look on the new one? https://github.com/AppFormer/uberfire/pull/881/commits


fix metrics for realm_dart package

fix metrics for realm_dart package

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.366%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
380

Relevant Lines:
407

💛  - Coveralls


fix kinesis consumer to respect DefaultOffset

Currently if DefaultOffest configuration is set to newest or oldest, and OffsetFile points to a file that does not contain all of the current kinesis shards then:

iterator, err := cons.client.GetShardIterator(&iteratorConfig)

will fail, with the following error:

InvalidArgumentException: Must either specify (1) AT_SEQUENCE_NUMBER or AFTER_SEQUENCE_NUMBER and StartingSequenceNumber or (2) TRIM_HORIZON or LATEST and no StartingSequenceNumber. Request specified AFTER_SEQUENCE_NUMBER and no StartingSequenceNumber.

With this patch the DefaultOffset will be respected on new shards, while shards found in the OffsetFile will use ShardIteratorTypeAfterSequenceNumber.

Good find! 👍


feat $q: spread

add spread functionality to promises
Issue: 13076

See https://github.com/angular/angular.js/issues/13076#issuecomment-226011726.


Create App Switcher Component

Details
Simplified version of the nav drop down that will be used to nav between summoner and hub.

Takes in an array of links and clickable JSX to be rendered
Opens other apps when clicked in new window

We will not do the Search feature in this ticket.
https://www.figma.com/file/9lCwprCNaoAmUDmiMQpFEA/DAOhaus-v3?node-id=6183%3A133289

Relates to:
https://github.com/HausDAO/daohaus-monorepo/issues/65

Hub icon should already be available

Very similar to #429 which is already in flight. Just more specific variants of drop-down.

@santteegt are you able to take this component this week?

May be related to: https://github.com/HausDAO/daohaus-monorepo/issues/429

Need a little clarification on the SVGs and where they are coming from?
Will the colors already be applyed to the SVG when we get it, is it stored in the UI Repo or an external place?


check error code for possible rejected transaction

https://github.com/bancorprotocol/webapp-v2/issues/274
when rejecting transactions

on mobile error is "User rejected transaction" and code 4001
on desktop error is "User denied transaction signature" and code 4001

Documentation from eth says 4001 is for rejected transactions.
https://eips.ethereum.org/EIPS/eip-1193#provider-errors
So given that i think it is safe to check just the error code, when error is thrown.

Thanks!


Get exchange rates by source besides "all"

Extend the /exchanges endpoint to get exchange rates from a single source.
A request example to get exchange rates from Banco Nacional de Angola would be:

/api/v1/exchanges/official

Or from Kinguilas:

/api/v1/exchanges/kinguila

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @Annahlu, @Raposo5000, @cristianorr25, @juliapradob, @cmcouto-silva, @alanmxll, @stephan-lopes, @EduardoABG, @akihitofficial, @jrdiiaas, @ksilva-kwn, @JuniorJDS, @leticiaplang, @rcovery, @Matheus-Fantin, @karengiovanna, @Isaachintosh, @zoboomafo, @MateusTheodoro, @hkakutalua, @Felipe-Quintiere, @Bernardoow, @joelsouza, @nATHANnSil, @alanneves, @ff-neto, @adelsonguimaraes, @dandeliao, @BanjooKazooie, @carla-hub, @fmartins000, @92username, @paaatcha, @gustavoramos82, @alinefbrito, @Farias123, @lanng, @HenriqueSamuelRosa, @vitorramon, @Rodrigo-Peres, @danielbichuetti, @Felpsns37, @FMascena, @AndrePaulino, @jmolvr, @luizdts, @femfs, @YohanVelho, @dmioto, @murilorodriguesvs


Sometimes it works, sometimes it doesn't

I was able to use it for 1-2 days when I first downloaded it, but then it stopped working. Although I press the button, it doesn't play automatically at all. I deleted it again and installed it, it was working at first, then it stopped working again. Also, the commands I gave in the Autoskill section are not detected correctly. Cards are used although I chose to use NP. I'm using Huawei Mate 20 Lite.
Android Ver. 9.

Please provide screenshots of your autoskill configuration and provide a video of the app not working with debug mode being turned on.

@DogaGungor why did you just delete the BUG template. The things we ask there are important to find the problem.

This one is EXP Team configuration

This one is QP Team configuration

Video:
https://youtu.be/W02fNmCQQy0

@DogaGungor why did you just delete the BUG template? The things we ask there are important to find the problem.

I didn't know it was a template, I just thought it was an explanation.
Device Info:

Device model: Huawei Mate 20 Lite
Screen size: 2340x1080
Android Version: Android 9
RAM: 4 GB

How are you using Bandicam on your phone? FGA won't work properly if other screen recorders are running.
Use the inbuilt recorder for reporting bugs. It's available in More options / Record Screen.

Okay, I did it:
https://youtu.be/x_OrSTl3jvA

I meant, use the recorder within FGA (the app) itself, not any other recorder on your phone.
Running other recorders can cause problems with FGO.

https://youtu.be/i4OYCmSbu-8
I guess i did it.

Not directly related to his issue, but something I noticed that he'll need to fix it later: in skill command, you're using a comma to separate each wave, but for that you want a ",#,", to tell the app you want to use those commands in the next wave, not the next turn. You only use a single comma when you're farming a node that has 4~6 enemies in a single wave, which is very rare.

Not related to OP's issue, but I think this title pretty much describes the issue I noticed.
When the script selecting Merlin support, I notice sometimes it will most of the time skip through Merlin supports with final ascension art even though it fits the criteria of the options (10,10,10 skill; no CE preference for example).
Perhaps the PNG used for the final ascension have issues in detection?
Also, will we get the option for new Castoria support too?

@yunamon You could look into the logs using adb and logcat. It's not user friendly and hard to search for, but every time images are compared, a message is logged containing the similarity value.
Castoria will be included in the next release.

Is there no solution to my problem?

I only just now watched the video, the behavior is really strange. Something seems to be blocking the clicks.

Could it not be working because I use Castoria?

@DogaGungor I don't have a solution yet. another person with a Huawei phone said that they have the same problem. But, there are Huawei users not having any problems.
I can only give generic advice here.

Don't run other screen recording apps when running FGA.
Clear cache for the app or restart your phone.
Disable battery optimization for the app: https://dontkillmyapp.com/huawei
Are there any other apps that could kill FGA. e.g. Battery doctor, antivirus.

Castoria shouldn't be a problem.

Another application might be interfering, but I don't know if there is. I do not use such applications.

When I delete the app's data, it gets fixed, but then it gets corrupted again somehow.

@DogaGungor Try disabling and then enabling the accessibility service.

@DogaGungor after how much time does it get corrupted? You won't have to delete data. Just clearing the cache should be enough.

@DogaGungor after how much time does it get corrupted? You won't have to delete data. Just clearing the cache should be enough.
I don't think it happens after a certain time, I guess it happens after using the app several times a day. Clearing the cache didn't work, I tried.

@DogaGungor Try disabling and then enabling the accessibility service.
It doesn't work either.

You might want to look at #354. They said their issue was solved by the tweaking the battery saver settings as said on dontkillmyapp.com

#363 solved by following the same steps as #354. So, I think that should work fort you too.


Add a --mode to inspect and diff and implement sourcegraph support

Initially supported will be local (the current behavior) and sourcegraph
For sourcegraph, we should open a browser tab (after acknowledging the interactive part). Inspect should route like so and diff should route like so.

Fixed by #246 and #247


feat(build): add an option to specify specific config file paths

This feature adds ability to use multiple scratch org definition files, where each package can be specified with a particular Definition
Checklist
All items have to be completed before a PR is merged

[x] Adhere to Contribution Guidelines
[x] Updates to Decision Records considered?
[x] Updates to documentation at DX@Scale Guide considered?
[x] Tested changes?
[x] Unit Tests new and existing passing locally?

Codecov Report

Merging #1093 (658a09d) into develop (ef5b975) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1093   +/-   ##
========================================
  Coverage    60.61%   60.61%
========================================
  Files           54       54
  Lines         1785     1785
  Branches       379      379
========================================
  Hits          1082     1082
  Misses         703      703

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Token expiration with custom API

Hi! Thanks for a great library.
In Phoenix umbrella app I have custom API token authentication setup based on this guide (with renew) for using with Absinthe (socket + http) and React/Apollo on the frontend. I can't understand when api and renew token expires.
I've tried to find max_age settings for api_token (and api_renew_token) and actually can't find any defaults and how to change them with this config, looks like there is no difference between api and renew max_age.
config :proling_web, :pow,
  repo: Proling.Repo,
  user: Proling.Identity.User,
  mailer_backend: ProlingWeb.Mailer,
  web_mailer_module: ProlingWeb,
  message_verifier: {Pow.Plug.MessageVerifier, key_generator_opts: [max_age: 10]},
  cache_store_backend: Pow.Store.Backend.MnesiaCache,
  extensions: [PowResetPassword, PowEmailConfirmation],
  controller_callbacks: Pow.Extension.Phoenix.ControllerCallbacks

For signing token I call Pow.Plug.sign_token(conn, signing_salt(), token, config).  It uses explicit Pow.Plug.MessageVerifier which ignores max_age option further in KeyGenerator. In high level Plug.Crypto API we can encode max_age to a token.
https://github.com/elixir-plug/plug_crypto/blob/3fbecf0d9e5ba10214f0ea527c2cc13c929ef8d0/lib/plug/crypto.ex#L168
Is there any solution for setting max_age without adding rewritten custom module instead of Pow.Plug.MessageVerifier?
I'm open for PR with adding max_age to Pow.Plug.MessageVerifier but maybe there is a reason to not adding max_age or not using Plug.Crypto high level API with first implementation and I'm wrong?

In Pow the tokens are not stateless so there's no need for an encoded max_age value as they automatically will be expired by the cache ttl setting. For renewal token it's the default for the PowPersistentSession.Store.PersistentSessionCache which is 30 days.
The plug signing mechanism is usually used for stateless tokens where a max age would be necessary.
All you have to do is add :ttl to the store config:
credentials_store_config = Keyword.put(store_config, :ttl, :timer.minutes(15))
persistent_session_store_config = Keyword.put(store_config, :ttl, :timer.hours(24))

CredentialsCache.put(credentials_store_config, access_token, {user, [renewal_token: renewal_token]})
PersistentSessionCache.put(persistent_session_store_config, renewal_token, {[id: user.id], [access_token: access_token]})

I think it would be great to improve the docs regarding so, do you see anywhere where this information would fit and can help others in the same situation? I could maybe just add the above to the API guide as comments to highlight how you adjust the store config.

@danschultzer Dan, thanks a lot, this is super helpful and complete explanation. I've tried persistent_session_ttl parameter but it works only with Pow.Plug.Session is I've found out. I think your answer could be mentioned as a paragraph in API guide before OAuth 2.0 because using this parameters is essential for testing token renewal mechanics in custom GraphQL API for example.


Importing terrain data file limit issue.

There is a bug in GeoFDA that is limiting terrain size on import to 20mb instead of 2000mb (2gb)
This bug is documented on discourse here:  https://discourse.hecdev.net/t/importing-terrain-file-error/535

https://github.com/HydrologicEngineeringCenter/GeoFDA/blob/25806ab798f277f3c7a171e3cfa0e2756984251e/GeoFDA/Watershed/Terrain/Forms/TerrainBrowser.xaml.vb#L27
This is the line that needs to be investigated - it is a simple fix,

@Brennan1994 see if you can make the change (you could do it directly in github if you want) let me know when you want me to review your commit

It’s tested with a terrain file size ~250mb. Prior limit was 200mb, new limit is 2gb. In debug I found that the bytes displayed in VS didn’t match what I saw in file explorer . I googled and found that they matched if I converted it to 1kb = 1024bytes. I found what gb should be and included my conversion in the comments.


Support returning the "NumberOfFrames" in the OHIF viewer endpoint

This is to support displaying multi-frame images in the OHIF Viewer properly.
Expected Behavior
Call the OHIF endpoint metadata with a study of a multi-frame DICOM instance. The returned attributes list should contain the "numberOfFrames" attribute on the instance level.
Actual Behavior
This attribute is not returned which is causing the OHIF Viewer to only render the first frame
Steps to Reproduce the Problem

https://dicomcloud.azurewebsites.net//ohif/study/999.999.2.19960619.163000/series

Done


fixes a NestedLoop race condition which can happen on an outer join

bug resulted in a flaky test3TableLeftAndRightOuterJoin test

@matriv pls review

Igtm


Able to "sell" air to Market NPCs

Thankfully does not actually provide money

Fixed for next restart, thanks for the report!


DataFrame.plot(subplots=True) forces black-and-white mode regardless of other settings

import matplotlib.pyplot as plt
import numpy as np
import pandas as pd

df = pd.DataFrame(np.random.randn(6, 4), index=pd.date_range('20150101', periods=6), columns=list('ABCD'))

plotters = [
	"df.plot()",
	"df.plot(legend=None)",
	"df.plot(legend=None, subplots=True, layout=(2, 2))",
	"df['A'].plot(legend=None)",
	"df['A'].plot(legend=None, subplots=True)"
]

for i, plotter in enumerate(plotters, 1):
	eval(plotter)
	plt.title(plotter)
	plt.savefig('%d.png' % i)
	plt.close('all')

Also, notice how the title is broken in the third image.

Thanks for the report.
This should be fixed in 0.17.0 (#9894). Otherwise reopen attaching pd.show_versions.

I have indeed been running this under Pandas 0.16.2, and I have forgotten to search for existing reports before submitting my own. Thank you for taking time to point me to the fact that the problem has already been fixed.
There is still, however, a problem in the third plot. I will create another issue for that one.


ssi-contexts v0.1.2

Release ssi-contexts v0.1.2 crate, in preparation for next ssi crate release.

Published
https://github.com/rust-lang/crates.io-index/commit/fd4e442d612dc02ca4e72682ecbec85bba2f20c2
https://crates.io/crates/ssi-contexts/0.1.2
https://github.com/spruceid/ssi/releases/tag/ssi-contexts/v0.1.2


fixed swarm url

swarm-dev.hiven.io is now swarm.hiven.io for socket
Summary
basically, devs changed swarm-dev to swarm meaning bot cannot connect to userclient
Changes

[x] This is a MAJOR change (e.g new class, rewrite)
[ ] This is a minor change (e.g typo fixed, optimization, bugfix)
[ ] This does not effect any code (i.e README/documentation change)

[ ] If needed, the documentation has been updated..

Oh? Hiven is still there?

If this is true, the rewrite/dev branch v0.2.dev will also need to be updated

Yeah, Hiven is back in new ownership.

Yeah, Hiven is back in new ownership.

Can we please see evidence or if its even running? As far as I know mine and Lunas accounts are gone from their db

Video of the client working, and some information

Unlimited Invites
Yes, we have no intentions to have Hiven being an exclusive platform. We want everyone to be able to use it to talk with their friends if that's something they're interested in. The invite code system was already in place so was expanded upon to allow people to create invites and invite their friends to hang out.
If there's a bunch of abuse we have no problem suspended accounts or limiting access. We're allowing you all to have the freedom and to invite anyone, use it wisely or lose it for all.
Multiple Chat Clients
Obviously, there are many different chat clients anyone can and does use.  For example, I use Discord and Slack daily. We're not to be the "only one".
Loss of accounts
When Hiven shut down there were no intentions to bring it back. Hiven was brought back with different maintainers because we all loved using Hiven when it was a thing originally and want it to live on. The original creators are doing amazing work over at Giggl.
Bugs and Feedback
As Jack said, Hiven was been shut down for months with no development at all. The last few weeks were spent pulling loose strings together, updating things and bringing everything back online in a new environment. We all want to hear everyone's feedback but let's please make sure to keep it constructive.

I can provide some beta codes if wanted?

Sure that would be great ^^

I can then also start with some development again on the rewrite to fix some problems for v0.1.3 since v0.2.dev has a better and nicer structure

https://beta.hiven.io/9FD3-6B9C-078C-3AA5
Beta code for Hiven

Beta code for Hiven
Just before someone else claims it - gonna delete the comment and DM it to Luna

https://hiven.house/Yj8sOw
I created now a new house for the project. I will sit down this evening and release a new version (v0.1.4), which should fix this and then also implement some smaller changes, so that everything runs a bit nicer until the v0.2 update that is sitting in v0.2.dev since a few months

Alright!

Closing due to now enforcing v0.2.dev1 as the most recent version. Will yank previous releases on pypi


Error on Repositories Wiki page

Hello,
the wiki page describing repositories endpoints incorrectly states that in order to create an organization repository, one should use the POST /orgs/:org/repos while in reality the endpoint is POST /org/:org/repos :).

Thanks! You're right, fixed. :sweat_smile:

Cheers! 😃


tokenize:clear should remove  elements from

Triggering "tokenize:clear" currently removes the children of ul.tokens-container, but not from the original (hidden)  element.
This among others causes (rather randomly) wrong  elements order on repopulating the control (using "tokenize:clear" and "tokenize:tokens:add"), as the order shown in ul.tokens-container is often not the same as the order of the  elements.

Try to call the "tokenize:tokens:reorder" event, I think it will fix your problem


Method not implemented

Hi,
I am getting the following errors when I try to open the realm database in chrome insepector:
D/ChromeDevtoolsServer: onOpen
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Page.canEmulate
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Console.setTracingBasedTimeline
I/ResponseBodyFileManager: Cleaned up temporary network files.
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Debugger.setAsyncCallStackDepth
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Debugger.skipStackFrames
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Runtime.enable
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Worker.enable
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Timeline.enable
D/ChromeDevtoolsServer: Method not implemented: Not implemented: IndexedDB.enable
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Page.getNavigationHistory
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Worker.setAutoconnectToWorkers
D/ChromeDevtoolsServer: Method not implemented: Not implemented: IndexedDB.requestDatabaseNames
D/ChromeDevtoolsServer: Method not implemented: Not implemented: Page.getNavigationHistory
D/ChromeDevtoolsServer: Method not implemented: Not implemented: ApplicationCache.enable
D/ChromeDevtoolsServer: Method not implemented: Not implemented: ApplicationCache.getFramesWithManifests

I am using steth_realm-2.0.0, steth-1.4.1,
Any ideas?

I am seeing those too, but I don't know if those are normal or not.
My Chrome/Stetho is also not showing me me Realm database contents.
Is this related?


feat(bundler) appimage

[ ] Bugfix
[x] Feature
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Add appimage support to the bundler

Added logic to allow us to better traverse, create, remove and copy folders/files.


  Exclude them so we don't get false negatives from shippable on PRs that happen to trigger these tests.
Found with sanitycheck --all.

The right way to do this is to set the platform's RAM/flash size in the board level YAML file, and then set min_ram/min_flash in the testcase.yaml.

Fair enough.  In that case I'll have to increase the amount of flash required for some tests, because these boards are failing even though they meet the minimum specified.
I'll rework for that.


docs: remove external component test example

This PR removes the link to the external repo
https://github.com/bahmutov/cypress-react-component-example
from the README: More examples table. The repository is out-of-date and even if it were updated it would duplicate example-component-test.yml in this repository.
This repository already contains a working example of component testing running under Cypress 12.7.0 - see workflow example-component-test.yml based on the project component-tests which is built using the instructions from the Cypress documentation React Quickstart.
The repository https://github.com/bahmutov/cypress-react-component-example is out of date.

It is based on using Cypress 9.7.0, before Component Testing for Cypress was officially declared GA in 11.0.0.
The instructions for using component testing are now significantly different

the repository does not use the component parameter of the github-action
it calls component testing instead with yarn cypress run-ct

The repo is not compatible with Node.js 18 (LTS). The react-scripts will not build. This means that the workflow does not run and just hangs up.

@MikeMcC399 This is all good to go, but we've got CI issue that's preventing the merge. I'll keep an eye on things and get this merged once things are fixed

@mike-plummer

This is all good to go,

Thanks for the confirmation!

but we've got CI issue that's preventing the merge. I'll keep an eye on things and get this merged once things are fixed

Is this about the pending snyk tests?


update alerting module

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

test


Test against different versions of jasmine

The tests currently only cover jasmine 2.4, but since this library is essentially a patch that gets injected into Expectation.wrapCompare() it is dependent on the implementation which may vary across versions.
The versions that are currently reported by npm info jasmine versions are:

2.0.1
2.1.0
2.1.1
2.2.0
2.2.1
2.3.0
2.3.1
2.3.2
2.4.0
2.4.1

https://github.com/jasmine/jasmine/commit/5700ace2c9bb7f585fe9e821a1a3b0b60f2ad542#diff-0dbfd2df6e9f6e547698190f01685088
The Expectation class was not introduced until 4.2.1, before that it was Matchers and was designed differently.

https://github.com/deckar01/jasmine-matcher-errors/commit/4a857ee91f3404129bdea4e8538417992189ae8c added support and tests for v1.
It looks like I would have to pull in v1 as a gem. Trying to test against multiple versions of Jamsine would add a lot of complexity that would probably only work on Travis.
Closing in favor of mocking old environments.