feat: light-weight basic quotation macro

Description:
I finally got annoyed enough at the lack of Qq, that I figured we can just roll our own basic version to get 80% of the benefits. So, I implemented a very basic ql(..) macro. Crucially, we only attempt to deal with closed terms, so we avoid a lot of the complexity that QQ has to deal with anti-quotations. Similarly, we avoid the performance problems of QQ because we don't attempt to deal with expression matching either.
To implement the macro, we had to take the ToExpr Expr instance from Mathlib, which meant pulling in the ToExpr derive handler (which isn't a bad thing, that derive handler will be generally useful). That is, DeriveToExpr.lean, ToExpr.lean and ToLevel.lean are taken from Mathlib, with only very slight modifications to eliminate any further Mathlib dependencies to do with pretty-printing.
Then, Tactics/QuoteLight.lean is actually new code. The implementation of the ql(..) macro is quite simple, only about 50 lines of meta-code. The rest of the file consists of a few basic tests.
 For example, we currently have mkApp (.const ``List.nil [0]) (mkConst ``StateField) somewhere in the code, with the macro we can simplify this to<EMAIL_ADDRESS>StateField).
Testing:
What tests have been run? Did make all succeed for your changes? Was
conformance testing successful on an Aarch64 machine? Yes
License:
By submitting this pull request, I confirm that my contribution is
made under the terms of the Apache 2.0 license.

LGTM, we paired on this, and I like the idea.


Fix constructing search query strings with date ranges

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Both from and to are now separate keyword arguments in a bunch of places, not part of args.
When we switched this around, we didn't realize this method needed updating to correctly construct the time range query.
This led to further inaccurate counts in brew contributions for reviews, since from and to are not valid search qualifiers for the GitHub PR search APIs.

Before:
$ brew contributions --user=issyl0 --from=2024-03-01 --to=2024-05-31
issyl0 contributed 24 times (author), 1 time (committer), 1 time (coauthor) and 26 times (total) between 2024-03-01 and 2024-05-31.

After:
$ brew contributions --user=issyl0 --from=2024-03-01 --to=2024-05-31
issyl0 contributed 24 times (author), 1 time (committer), 1 time (coauthor), 13 times (review) and 39 times (total) between 2024-03-01 and 2024-05-31.

Thanks @issyl0!


[WIP] Makefile: simplify vet check

Building of binaries is not required to run go vet. We also remove the
load of exceptions that aren't needed for Go 1.8.

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

Does anyone know of a reason to require Go 1.7? By the time we have an official release of containerd, Go 1.8 will have been out for 4 months, and already has a minor point release. Seems reasonable to just expect Go 1.8 is the lowest support runtime version to be used for containerd build.

I say we remove it

Ok, so it looks like make vet is pretty broken. It works on my machine just fine.
If some wants to shave this yak, feel free. I'll give this week and after that, we just remove support.

@crosbymichael:
| I say we remove it
The check or Go 1.7 support?

The check or Go 1.7 support?

Both. Unless you want to shave this yak? :sheep:

1.7

fwiw Go 1.7 was removed from the Travis config in a7e8928a0886be6cf13377acf0c2b66f01b58dc5.  Can we close this one?


sagittarius-scheme: 0.9.11 -> 0.9.12

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/sagittarius-scheme/versions.
meta.description for sagittarius-scheme is: R6RS/R7RS Scheme system
meta.homepage for sagittarius-scheme is: https://bitbucket.org/ktakashi/sagittarius-scheme
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.12 with grep in /nix/store/q2559jr7pdbm50d3y0y5g1h79m4kb8a8-sagittarius-scheme-0.9.12
found 0.9.12 in filename of file in /nix/store/q2559jr7pdbm50d3y0y5g1h79m4kb8a8-sagittarius-scheme-0.9.12

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

179 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

sagittarius-scheme
tests.devShellTools.nixos
tests.devShellTools.unstructuredDerivationInputEnv

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/e8f1c2e5ee9dd5baef8d80b6b29c1ca40df53208#sagittarius-scheme

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q2559jr7pdbm50d3y0y5g1h79m4kb8a8-sagittarius-scheme-0.9.12
ls -la /nix/store/q2559jr7pdbm50d3y0y5g1h79m4kb8a8-sagittarius-scheme-0.9.12/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

sagittarius-scheme

Maintainer pings
cc @wahjava for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@ofborg eval


Update bundle to RC4

Would be great if the bundle was upgraded to RC4 so users are able to take advantage of the updated Forms and new router functionality...

@pchristou thanks for the heads up.
Just to note that angular2-materialize doesn't use specific features that changed during newer RC releases. I assume you're referring to the demo app, that is still using RC1
Looking at the changes the major benefit is the new router. I think we'll wait for it to come out of beta, to avoid more breaking changes with each of its releases: https://github.com/angular/angular/blob/fe7de53b89ebe9e035197f15b43b45650cf44c50/modules/%40angular/router/CHANGELOG.md

@rubyboy I'm getting this error while using RC 4:
No Directive annotation found on MaterializeDirective
I imported it (import {MaterializeDirective} from "angular2-materialize") and added it to the directives array.

@leNicDev are you using Ionic?
Just did a quick test of RC.4 on my machine and it looks well, but I'll only know once I full upgrade and use the new router, when it comes out of beta.

@rubyboy Seems like this error occurs if you're trying to import angular2-materialize before zone.js. But with making angular2-materialize the last import, I'm getting this error:
Couldn't find materialize function ''material_select' on element or the global Materialize object..

@leNicDev Is it specific to RC4 or are you getting it for RC1 as well?

@leNicDev I think you're not bringing in materialize. Notice that Materialize needs to be imported before the directive (it's being used by it). What module loader system are you using?

@rubyboy I'm using Webpack and I'm getting the same error for RC1. I'm importing angular2-materialize in my boot.ts. After that I'm loading the stylesheet of Materialize in the template:
<link href="../node_modules/materialize-css/dist/css/materialize.css" rel="stylesheet">. If I'm requiring materialize.js before importing angular2-materialize the error still occurs.

Can you please create a separate issue. this is not related to this request to upgrade to RC4 and would confuse whoever is dealing with the upgrade.
Once created I have a few ideas on what to check, but I'll put that in the other issue, for other people coming in from webpack.
Thanks.


sprites crashing game

Describe your bug here.
hey i just got done making sprites (and also had some pre made ones) and every time i go to load them in a chart they both crash the game. ones sprite sheet is very large the other not so much but i was wondering if this was a bug or just a issue. this hasn't happened before and it only recently started happening
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
only added 1 chart

Send the files on what’s causing it


OpenSTA SegFaults using set_wire_rc in corners

Hi,
I am getting a Segmentation fault when trying to use set_wire_rc  in multi-corners analysis.  I reproduced it with nangate45 gcd example (starting openroad manually after make route):
...

Runtime taken (hrt): 4.33766
0:04.34elapsed 99%CPU 19932memKB
cp results/nangate45/gcd/4_cts.sdc results/nangate45/gcd/5_route.sdc
bash-4.2$ make reports/nangate45/gcd/nS_final_report_debug.txt
openroad
OpenROAD 0.9.0 GITDIR-NOT
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of the program may be licensed under more restrictive licenses which must be honored.
% read_lef $::env(TECH_LEF)
Notice 0: Reading LEF file:  ./platforms/nangate45/lef/NangateOpenCellLibrary.tech.lef
Notice 0:     Created 22 technology layers
Notice 0:     Created 27 technology vias
Notice 0: Finished LEF file:  ./platforms/nangate45/lef/NangateOpenCellLibrary.tech.lef
% read_lef $::env(SC_LEF)
Notice 0: Reading LEF file:  ./platforms/nangate45/lef/NangateOpenCellLibrary.macro.mod.lef
Notice 0:     Created 134 library cells
Notice 0: Finished LEF file:  ./platforms/nangate45/lef/NangateOpenCellLibrary.macro.mod.lef
% define_corners wc bc
#nangate45 only has 1 .lib file, so not much sense creating corners, but it is just for the test case
% foreach libFile $::env(LIB_FILES) {
  read_liberty -corner wc $libFile
  read_liberty -corner bc $libFile
}
Warning: ./platforms/nangate45/lib/NangateOpenCellLibrary_typical.lib, line 37 library NangateOpenCellLibrary already exists.
% read_def $::env(RESULTS_DIR)/5_route.def
Notice 0:
Reading DEF file: ./results/nangate45/gcd/5_route.def
Notice 0: Design: gcd
Notice 0:     Created 54 pins.
Notice 0:     Created 2029 components and 5141 component-terminals.
Notice 0:     Created 2 special nets and 4058 connections.
Notice 0:     Created 385 nets and 1083 connections.
Notice 0: Finished DEF file: ./results/nangate45/gcd/5_route.def
% read_sdc $::env(RESULTS_DIR)/5_route.sdc
0
% set_wire_rc -layer metal3
Error: -corner keyword required with multi-corner analysis.
% set_wire_rc -corner wc -layer metal3
make: *** [reports/nangate45/gcd/nS_final_report_debug.txt] Segmentation fault (core dumped)
bash-4.2$
```

fixed in
9c19398e estimate_parasitics -placement with multiple corners


added basic implementation for DataTransfer mechanism

Added basic implementation for DataTransfer for version 2.0.1. Sorry for closing last PR opening a new one, things did not go well with rebasing. However, all the before-mentioned  comments has been resolved, regarding a line of comment (deleted) and PnC callback definition (also deleted).

Dear Piet, thank you very much for the comments. I made the changes as said, please have a look.


Fixing Issue #21 -  Adding aws-nodejs8.10 to supported runtime list.

This pull request adds nodejs810 to the supported runtime list, resolving Issue #21

Was about to write this myself, happy to see someone took the initiative.
Can we get this merged in?

@artoliukkonen I don't think this got published? Latest version on npmjs.com doesn't include this fix.

@artoliukkonen I don't think this got published? Latest version on npmjs.com doesn't include this fix.

I noticed the same issue, @artoliukkonen. Still receiving this error after grabbing the latest version of the plugin.


remove discharge error bars from dvhydro AQCU-684

https://internal.cida.usgs.gov/jira/browse/AQCU-684

Coverage decreased (-0.006%) to 87.539% when pulling 97812d081b6f5c377a73d9d25a1b0fa3dd09876e on mhines-usgs:master into c756bccc6b12ccbc438ef2f5287524cafef42517 on USGS-R:master.


Need help with single 64x32 matrix with 1/8 scan rate

I'm having a lot of issues with 64x32 matrix with a 1/8 scan rate, in this code I am trying to draw a simple white border around the matrix. I am driving the matrix with a Adafruit Matrix Portal S3.
I tried to follow the instructions here to no avail:
https://github.com/mrcodetastic/ESP32-HUB75-MatrixPanel-DMA/issues/578#issue-2106096259
All messed up!

ESP32-VirtualMatrixPanel-I2S-DMA.h (Updated)
    if (panel_scan_rate == FOUR_SCAN_32PX_HIGH)
    {
        if ((coords.y & 8) == 0)
        {
            coords.x += ((coords.x / panelResX) + 1) * panelResX; // 1st, 3rd 'block' of 8 rows of pixels, offset by panel width in DMA buffer
        }
        else
        {
            coords.x += (coords.x / panelResX) * panelResX; // 2nd, 4th 'block' of 8 rows of pixels, offset by panel width in DMA buffer
        }

        // Real number of DMA y rows is half reality
        // coords.y = (y / 16)*8 + (y & 0b00000111);
        //
        coords.y = (coords.y >> 4) * 8 + (coords.y & 0b00000111);
    }

sktech.ino
#include <Arduino.h>
#include <Adafruit_GFX.h>
#include "ESP32-VirtualMatrixPanel-I2S-DMA.h"
#include <ESP32-HUB75-MatrixPanel-I2S-DMA.h>

// Pins
#define R1_PIN 42
#define G1_PIN 41
#define B1_PIN 40
#define R2_PIN 38
#define G2_PIN 39
#define B2_PIN 37

#define A_PIN  45
#define B_PIN  36
#define C_PIN  48
#define D_PIN  35
#define E_PIN  21

#define LAT_PIN 47
#define OE_PIN  14
#define CLK_PIN  2

// Define panel size
#define PANEL_RES_X 64
#define PANEL_RES_Y 32

// Define the number of rows and columns in the panel matrix
#define NUM_ROWS 1
#define NUM_COLS 1
#define PANEL_CHAIN (NUM_ROWS * NUM_COLS)

// Define the virtual matrix chain type
#define VIRTUAL_MATRIX_CHAIN_TYPE CHAIN_TOP_RIGHT_DOWN

#define SERPENT true
#define TOPDOWN true

// Declare pointers for DMA display and virtual display
MatrixPanel_I2S_DMA *dma_display = nullptr;
VirtualMatrixPanel *virtualDisp = nullptr;

// Function to draw text with background
void drawTextWithBackground(int x, int y, const char *text, uint16_t textColor) {
  virtualDisp->setTextColor(textColor);
  virtualDisp->setTextSize(3);
  virtualDisp->setCursor(x, y);
  virtualDisp->print(text);
}

void setup() {
  Serial.begin(115200);

       // 62x32 1/8 Scan Panels don't have a D and E pin!

  HUB75_I2S_CFG::i2s_pins _pins = {
    R1_PIN, G1_PIN, B1_PIN, R2_PIN, G2_PIN, B2_PIN,
    A_PIN, B_PIN, C_PIN, D_PIN, E_PIN,
    LAT_PIN, OE_PIN, CLK_PIN
  };

  // Initialize HUB75 configuration with panel dimensions and chain settings
  HUB75_I2S_CFG mxconfig(
    PANEL_RES_X * 2,
    PANEL_RES_Y / 2,
    PANEL_CHAIN
    ,_pins
  );

  mxconfig.clkphase = false;
  //mxconfig.i2sspeed = HUB75_I2S_CFG::HZ_20M;
  mxconfig.driver   = HUB75_I2S_CFG::ICN2038S;    // Not sure what this is???

  // Initialize DMA display
  dma_display = new MatrixPanel_I2S_DMA(mxconfig);

  // let's adjust default brightness to about 75%
  dma_display->setBrightness8(96);    // range is 0-255, 0 - 0%, 255 - 100%

  // Check if DMA display began successfully
  if (!dma_display->begin()) {
    Serial.println("****** !KABOOM! I2S memory allocation failed ***********");
    return;
  }
  dma_display->setBrightness8(192);

  dma_display->clearScreen();
  delay(500);

  // Initialize virtual display with the DMA display and panel settings
  virtualDisp = new VirtualMatrixPanel((*dma_display), NUM_ROWS, NUM_COLS, PANEL_RES_X, PANEL_RES_Y, VIRTUAL_MATRIX_CHAIN_TYPE);
  virtualDisp->setPhysicalPanelScanRate(FOUR_SCAN_32PX_HIGH);
}

void loop() {
  // Define the height of each section of the display
  int sectionHeight = virtualDisp->height() / 4;

  // Draw a rectangle around the display edges
  virtualDisp->drawRect(1, 1, virtualDisp->width() - 2, virtualDisp->height() - 2, virtualDisp->color565(255, 0, 0));

  // Draw a diagonal line across the display
  virtualDisp->drawLine(0, 0, virtualDisp->width() - 1, virtualDisp->height() - 1, virtualDisp->color565(255, 255, 255));
  delay(2000);

  // Draw text in the middle of the display
  // drawTextWithBackground(0, virtualDisp->height() / 2 - 8, "    hi", virtualDisp->color565(0, 0, 255));
  // delay(10000);
}

@board707
I upgraded to the more modern solution you suggested, but I am running into an issue only half of the screen is being filled with red. Also the matrix doesn't seem as bright as it should be. I might try to buy 2 outdoor 32x32 matrices. People seem to be having more luck with them. Anything you can tell me helps.
https://github.com/user-attachments/assets/417a2441-9628-41e2-bbe0-3e36e77d99a7
/*************************************************************************
   Description:

   The underlying implementation of the ESP32-HUB75-MatrixPanel-I2S-DMA only
   supports output to HALF scan panels - which means outputting
   two lines at the same time, 16 or 32 rows apart if a 32px or 64px high panel
   respectively.
   This cannot be changed at the DMA layer as it would require a messy and complex
   rebuild of the library's internals.

   However, it is possible to connect QUARTER (i.e. FOUR lines updated in parallel)
   scan panels to this same library and
   'trick' the output to work correctly on these panels by way of adjusting the
   pixel co-ordinates that are 'sent' to the ESP32-HUB75-MatrixPanel-I2S-DMA
   library.

 **************************************************************************/

/* Use a custom Virtual Display class to re-map co-ordinates such that they draw
   correctly on a Four Scan panel (or chain of such panels).
*/
#include "ESP32-VirtualMatrixPanel-I2S-DMA.h"

/* ================================================== */
// Define custom class derived from VirtualMatrixPanel
class EightPxBasePanel : public VirtualMatrixPanel
{
  public:
    using VirtualMatrixPanel::VirtualMatrixPanel; // inherit VirtualMatrixPanel's constructor(s)

  protected:

    VirtualCoords getCoords(int16_t x, int16_t y);  // custom getCoords() method for specific pixel mapping

};

// define custom getCoords() method for specific pixel mapping
inline VirtualCoords EightPxBasePanel ::getCoords(int16_t x, int16_t y) {

  coords = VirtualMatrixPanel::getCoords(x, y); // first call base class method to update coords for chaining approach

  if ( coords.x == -1 || coords.y == -1 ) { // Co-ordinates go from 0 to X-1 remember! width() and height() are out of range!
    return coords;
  }

 if ((coords.y & 8) == 0)
        {
            coords.x += ((coords.x / panelResX) + 1) * panelResX; // 1st, 3rd 'block' of 8 rows of pixels, offset by panel width in DMA buffer
        }
        else
        {
            coords.x += (coords.x / panelResX) * panelResX; // 2nd, 4th 'block' of 8 rows of pixels, offset by panel width in DMA buffer
        }

        coords.y = (coords.y >> 4) * 8 + (coords.y & 0b00000111);

  return coords;
}
/* ================================================== */
// Panel configuration
#define PANEL_RES_X 64 // Number of pixels wide of each INDIVIDUAL panel module.
#define PANEL_RES_Y 32 // Number of pixels tall of each INDIVIDUAL panel module.

#define NUM_ROWS 1 // Number of rows of chained INDIVIDUAL PANELS
#define NUM_COLS 1 // Number of INDIVIDUAL PANELS per ROW

// ^^^ NOTE: DEFAULT EXAMPLE SETUP IS FOR A CHAIN OF TWO x 1/8 SCAN PANELS

// Change this to your needs, for details on VirtualPanel pls read the PDF!
#define SERPENT true
#define TOPDOWN false
#define VIRTUAL_MATRIX_CHAIN_TYPE CHAIN_TOP_RIGHT_DOWN

// Pins
#define R1_PIN 42
#define G1_PIN 41
#define B1_PIN 40
#define R2_PIN 38
#define G2_PIN 39
#define B2_PIN 37

#define A_PIN  45
#define B_PIN  36
#define C_PIN  48
#define D_PIN  35
#define E_PIN  21

#define LAT_PIN 47
#define OE_PIN  14
#define CLK_PIN  2

// placeholder for the matrix object
MatrixPanel_I2S_DMA *dma_display = nullptr;

// placeholder for the virtual display object
EightPxBasePanel   *FourScanPanel = nullptr;

/******************************************************************************
   Setup!
 ******************************************************************************/
void setup()
{
  delay(250);

  Serial.begin(115200);
  Serial.println(""); Serial.println(""); Serial.println("");
  Serial.println("*****************************************************");
  Serial.println("*         1/8 Scan Panel Demonstration              *");
  Serial.println("*****************************************************");

  HUB75_I2S_CFG::i2s_pins _pins = {
    R1_PIN, G1_PIN, B1_PIN, R2_PIN, G2_PIN, B2_PIN,
    A_PIN, B_PIN, C_PIN, D_PIN, E_PIN,
    LAT_PIN, OE_PIN, CLK_PIN
  };

  HUB75_I2S_CFG mxconfig(
    PANEL_RES_X * 2,            // DO NOT CHANGE THIS
    PANEL_RES_Y / 2,            // DO NOT CHANGE THIS
    NUM_ROWS * NUM_COLS         // DO NOT CHANGE THIS
    ,_pins            // Uncomment to enable custom pins
  );

  mxconfig.clkphase = false; // Change this if you see pixels showing up shifted wrongly by one column the left or right.

  //mxconfig.driver   = HUB75_I2S_CFG::FM6126A;     // in case that we use panels based on FM6126A chip, we can set it here before creating MatrixPanel_I2S_DMA object

  // OK, now we can create our matrix object
  dma_display = new MatrixPanel_I2S_DMA(mxconfig);

  // let's adjust default brightness to about 75%
  dma_display->setBrightness8(40);    // range is 0-255, 0 - 0%, 255 - 100%

  // Allocate memory and start DMA display
  if ( not dma_display->begin() )
    Serial.println("****** !KABOOM! I2S memory allocation failed ***********");

  dma_display->clearScreen();
  delay(500);

  // create FourScanPanellay object based on our newly created dma_display object
  FourScanPanel = new EightPxBasePanel ((*dma_display), NUM_ROWS, NUM_COLS, PANEL_RES_X, PANEL_RES_Y,    VIRTUAL_MATRIX_CHAIN_TYPE);

  // THE IMPORTANT BIT BELOW!
  // FOUR_SCAN_16PX_HIGH
  // FOUR_SCAN_32PX_HIGH
// **** You don't need to set PhysicalPanelScanRate when use your own virtual panel class
 // FourScanPanel->setPhysicalPanelScanRate(FOUR_SCAN_16PX_HIGH);
}

// Test the pixel mapping - fill the panel pixel by pixel
void loop() {

  for (int i = 0; i < FourScanPanel->height(); i++)
  {
    for (int j = 0; j < FourScanPanel->width(); j++)
    {

      FourScanPanel->drawPixel(j, i, FourScanPanel->color565(40, 0, 0));
      delay(20);
    }
  }

} // end loop

Hi
According to the video, the code is definitely not compatible with your panel. Could you look up all the chips on the panel and list it's ID codes on the topic?


Add Client::check_route

Add a check_route method to Client that uses the ADS cache and defaults to check routing. This requires an active ADS connection but makes it easier to do live debugging.
I'm torn on whether or not this should update xDS subscriptions, like resolve_http or should be "inert" and not affect the client.

After talking offline about having a resolution mode, I took another stab back here. This ended up being a bit larger of a change, but I think it's for the best - it's now possible to test routes without making requests.


cmd/go: test cached run slower than real test run

What version of Go are you using (go version)?
1.10.3
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
linux; amd64
What did you do?
go test --count 1 .; time go test .
foo_test.go:
// package and imports snipped
func TestCache(t testing.T) {
tmp := os.TempDir()
for i := 0; i < 101000*1000; i++ {
os.Stat(filepath.Join(tmp, fmt.Sprintf("%d", i)))
}
}
What did you expect to see?
$ go test --count 1 .; time go test .
ok  	github.com/dbentley/testcache	11.839s
ok  	github.com/dbentley/testcache	(cached)
real	2s
What did you see instead?
$ go test --count 1 .; time go test .
ok  	github.com/dbentley/testcache	11.839s
ok  	github.com/dbentley/testcache	(cached)
real	1m2.278s
Further investigation
Using GODEBUG=gocachetest=1 or GODEBUG=gocachehash=1 doesn't cause output for 30+s.
I think the function inDir (currently at https://github.com/golang/go/blob/master/src/cmd/go/internal/test/test.go#L1450 ) evaluates symlinks, which requires lots of stat'ing.
It looks like this was introduced in https://github.com/golang/go/commit/37d56279c87818b496e5717bddd1f7c43bfa743d

Or we should just drop that whole symlink thing there. I don't see the point of evaluating symlinks in inDir.

Also the test input list should filter those out when recorded, not each time it is used.

On https://golang.org/cl/127818, @rsc says:

I'd still really like to find a way to make the approach of CL 127635 - stop evaluating symlinks at all - work. I'll try to take a look in the next couple weeks.

This reproduces for me on go1.16 darwin/amd64 -- any update on when this will be fixed?

@maiamcc, this issue is milestoned Unplanned and tagged “help wanted“. To my knowledge, no one is actively working on it at the moment.

On #50775, @millerresearch notes:

Computing the TestInputsID takes a stupendously long time because it's going through a testlog.txt which lists 357000 filenames, each requiring a stat call after being expanded by filepath.EvalSymlinks (which itself requires a stat call per filename component). In fact there are only 5841 unique lines in the testlog.txt, so sorting the list and eliminating duplicates would speed that up quite a bit.

That sounds like delightfully low-hanging fruit.

I've been struggling with this issue. The last place you think to look is go test itself. When I kill -ABRT <pid>, it does seem to be getting stuck in internal symlink libraries. Not every scientific, but my 30s tests can take upwards of 15m.
@bcmills it does seem like this deduping has been done already: https://github.com/golang/go/pull/26732, or at least not computing caches so many times.

@bcmills @matloob This issue is marked for 1.19.  Should it move to Backlog?

I've got a cluster of test-caching issues that I'd like to get to in the near future, but given scheduling constraints probably not until 1.21. Backlog it is for now.


If-else multi-line syntax error

I'm trying to write a recipe with simple multi-line if-else to check and/or create the needed directories.
srchout_dir := 'srch_out'
srchout_path := join(invocation_directory(), srchout_dir)

create-setup-dirs: && verify-setup
  if !path_exists({{srchout_path}}); then \
    mkdir -p {{srchout2_dir}}; \
    echo "Just created path: {{srchout_path}}"; \
  fi

verify-setup:
  if !path_exists({{srchout_path}}); then \
    error("Does NOT exist: {{srchout_path}}"); \
  else \
    echo "All is well!"; \
  fi

Running the following justfile recipe:
$ just create-setup-dirs
reports this syntax error:
if path_exists(/home/myuser/myproj/srch_out); then mkdir -p srch_out; echo "Just created path: /home/myuser/myproj/srch_out"; fi
sh: 1: Syntax error: word unexpected (expecting ")")
error: Recipe `create-setup-dirs` failed on line 24 with exit code 2

Is such a thing possible in multi-line syntax? If NO, then what's the syntax to produce expected behaviour in single-line if-else?

This is correct. Just syntax is only allowed outside of recipes. The inside of recipes is sh syntax (or whatever other shell you use). It's probably easiest to just use normal shell conditionals inside your recipes.


Wrong IP address in x-forwarded-for request header

I am using devtunnel for chargebee webhook events.
Chargebee has listed the IPs from which they send the webhook event requests.
But somehow I am getting wrong IP in request.ip and request.headers["x-forwarded-for"]. None of these match the IPs listed in Chargebee docs.
If I use ngrok, I get correct IP in request.headers["x-forwarded-for"].

Thanks for taking the time to file this issue. The Dev Tunnels service uses the x-forwarded-for header internally and so the IP address returned will be in the Private Address Space. Therefore, it won't match what you may be expecting for your use-case.
Unfortunately, we’re not able to prioritize changing this due to the other higher-impact issues we receive every week, based on the votes and comments from others in the community. Therefore, marking this as a known-issue.

Is there any other header from which I can get the source IP address?

Unfortunately not - this is not something we expose today.


Panic on sfsu list

Describe the bug
Happens every time for me
Full Output

Panic
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Error("missing field `bucket`", line: 5, column: 1)', src/packages.rs:24:74
stack backtrace:
   0:     0x7ff795afe890 - std::backtrace_rs::backtrace::dbghelp::trace::h29c543a13337066e
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\..\..\backtrace\src\backtrace/dbghelp.rs:98:5
   1:     0x7ff795afe890 - std::backtrace_rs::backtrace::trace_unsynchronized::h4735bf1454f795a4
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\..\..\backtrace\src\backtrace/mod.rs:66:5
   2:     0x7ff795afe890 - std::sys_common::backtrace::_print_fmt::hcb654bc1a0abc766
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\sys_common/backtrace.rs:65:5
   3:     0x7ff795afe890 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h57d91a764bda489c
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\sys_common/backtrace.rs:44:22
   4:     0x7ff795b57b3b - core::fmt::write::hbb11da7029f1c3d7
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\core\src\fmt/mod.rs:1209:17
   5:     0x7ff795af0c25 - std::io::Write::write_fmt::h2715f7121e6ec555
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\io/mod.rs:1682:15
   6:     0x7ff795afe5e4 - std::sys_common::backtrace::_print::h34a1cbe62da2dce8
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\sys_common/backtrace.rs:47:5
   7:     0x7ff795afe5e4 - std::sys_common::backtrace::print::h8e105c6f4128fa25
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\sys_common/backtrace.rs:34:9
   8:     0x7ff795b019af - std::panicking::default_hook::{{closure}}::h8578e99717a9b436
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src/panicking.rs:267:22
   9:     0x7ff795b016b7 - std::panicking::default_hook::h811108f7b9376e24
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src/panicking.rs:286:9
  10:     0x7ff795b022df - std::panicking::rust_panic_with_hook::hb34f0407887ca1d1
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src/panicking.rs:688:13
  11:     0x7ff795b02055 - std::panicking::begin_panic_handler::{{closure}}::h92b5222c88a2dda2
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src/panicking.rs:579:13
  12:     0x7ff795aff3cf - std::sys_common::backtrace::__rust_end_short_backtrace::h66b1044e4311a43f
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\sys_common/backtrace.rs:137:18
  13:     0x7ff795b01d70 - rust_begin_unwind
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src/panicking.rs:575:5
  14:     0x7ff795b543c5 - core::panicking::panic_fmt::h22ee573cfcae3983
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\core\src/panicking.rs:65:14
  15:     0x7ff795b54993 - core::result::unwrap_failed::hc39515d7b13f74e4
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\core\src/result.rs:1791:5
  16:     0x7ff795973041 - sfsu::packages::FromPath::from_path::h812eef12f1c10f99
  17:     0x7ff79596997b - <sfsu::commands::list::Args as sfsu::commands::Command>::run::{{closure}}::h27f875c27d2933d3
  18:     0x7ff795962cb3 - rayon::iter::plumbing::bridge_producer_consumer::helper::hd464608e38019d1e
  19:     0x7ff795952948 - rayon_core::join::join_context::{{closure}}::h8857a7079712e28b
  20:     0x7ff795962fd7 - rayon::iter::plumbing::bridge_producer_consumer::helper::hd464608e38019d1e
  21:     0x7ff795952a33 - rayon_core::join::join_context::{{closure}}::h8857a7079712e28b
  22:     0x7ff795962fd7 - rayon::iter::plumbing::bridge_producer_consumer::helper::hd464608e38019d1e
  23:     0x7ff795952948 - rayon_core::join::join_context::{{closure}}::h8857a7079712e28b
  24:     0x7ff795962fd7 - rayon::iter::plumbing::bridge_producer_consumer::helper::hd464608e38019d1e
  25:     0x7ff795952948 - rayon_core::join::join_context::{{closure}}::h8857a7079712e28b
  26:     0x7ff795962fd7 - rayon::iter::plumbing::bridge_producer_consumer::helper::hd464608e38019d1e
  27:     0x7ff795966220 - <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute::h0686b1f2c2a79f0b
  28:     0x7ff795a5da95 - rayon_core::registry::WorkerThread::wait_until_cold::hfc7024374a3ba675
  29:     0x7ff795a5aa59 - rayon_core::registry::ThreadBuilder::run::hcf54c1bb1402223d
  30:     0x7ff795a56972 - std::sys_common::backtrace::__rust_begin_short_backtrace::h09ce8ec31001c67d
  31:     0x7ff795a5775e - core::ops::function::FnOnce::call_once{{vtable.shim}}::hc301799b5e84498d
  32:     0x7ff795b12107 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::hdbc2fb0b40a7217d
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\alloc\src/boxed.rs:1987:9
  33:     0x7ff795b12107 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h21b2899e81d2a952
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\alloc\src/boxed.rs:1987:9
  34:     0x7ff795b12107 - std::sys::windows::thread::Thread::new::thread_start::h35d0d46d3ec957a3
                               at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library\std\src\sys\windows/thread.rs:56:17
  35:     0x7fff4e90117e - <unknown>
  36:     0x7fff4f6e42db - <unknown>

sfsu 1.4.0
Additional context
Add any other context about the problem here.

Could you attach the source manifest file?
I, and should add a special case for panics like this, but it would be good to know the source of the problem as well.

This has been fixed in the latest release, but I will leave the issue open, as it would be better to have an edge case that supports those manifest types rather than just saying "Invalid".
If you are able to provide the manifest that would be much appreciated.

Could you attach the source manifest file?

Uhh I'm not sure which package caused this issue, on normal (scoop list).Source, all packages have a normal looking repo. So since I don't know I'll just send a scoop export

The manifest(s) should now have "Invalid" or and empty string in place of the bucket & version properties, if that helps you find it. I can't seem to find anything wrong in the scoop export so I'm not too sure what is wrong.

Ah it was the held obs-studio package

How does that happen? Like where did that manifest come from?
Would you be able to attach a copy of that manifest?

1. How does that happen? Like where did that manifest come from?

Yes, it's just a generated manifest for a specific version, like this: https://github.com/ScoopInstaller/Scoop/issues/3045#issuecomment-1138042773

2. Would you be able to attach a copy of that manifest?

{
    "version": "27.2.4",
    "description": "Video recording and live streaming software",
    "homepage": "https://obsproject.com",
    "license": "GPL-2.0-only",
    "notes": [
        "Add Virtual Camera module by running: \"$dir\\data\\obs-plugins\\win-dshow\\virtualcam-install.bat\"",
        "Remove it by running: \"$dir\\data\\obs-plugins\\win-dshow\\virtualcam-uninstall.bat\""
    ],
    "architecture": {
        "64bit": {
            "url": "https://cdn-fastly.obsproject.com/downloads/OBS-Studio-27.2.4-Full-x64.zip",
            "hash": "fae9840096c43a62b410d91985b4b5fdd5b0d6e8d54ef4afe7af47180da8ae21",
            "shortcuts": [
                [
                    "bin\\64bit\\obs64.exe",
                    "OBS Studio"
                ]
            ]
        }
    },
    "pre_install": "if (!(Test-Path \"$persist_dir\\portable_mode.txt\")) { New-Item \"$dir\\portable_mode.txt\" | Out-Null }",
    "persist": [
        "config",
        "portable_mode.txt"
    ],
    "checkver": {
        "url": "https://obsproject.com/download",
        "regex": "OBS-Studio-([\\d.]+)-Full-x64\\.zip"
    },
    "autoupdate": {
        "architecture": {
            "64bit": {
                "url": "https://cdn-fastly.obsproject.com/downloads/OBS-Studio-$version-Full-x64.zip"
            }
        }
    }
}


fix: add whole tree rewriter when root is not CTEAnchor (#33591)

Proposed changes
#33591

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


fixed bug where if backgroundColors initial value was not set

When you set backgroundColor initially it is not applied (only when you change it dynamically once the SketchField component already loaded).

@shafy its been a long time but thanks for your input, merging this!

Hi @tbolis, just wanted to ask if this is going to make it into a release soon. Thanks!


feat: Cloud Deploy support

Replaced Cloud Build trigger based deploys with creating Cloud Deploy targets and pipelines
Trigger post-deployment checks in Cloud Build using Cloud Deploy-originated Pub/Sub notifications
Convert app-wet-manifest repo to cloudbuild-cd-config repo, where the configuration of post-deployment checks will live

This PR also resolves #24 and #14


Added Terasic DECA retro cape board definition. Added simple usage in Readme

Squashed commit of the following:
commit 63b8aadd226eb6afccc9357ed48fb2e27bda0e9d
Merge: 9921c96 66e467a
Author: somhi<EMAIL_ADDRESS>Date:   Thu Apr 27 18:53:29 2023 +0200
Merge branch 'main' into devel

commit 9921c9663a9a55f26837c46a0fdc078b47012edb
Author: somhi<EMAIL_ADDRESS>Date:   Thu Apr 27 18:51:09 2023 +0200
updated readme

commit 975c7e6c9702f6533af9d010cb78a838f406523b
Author: somhi<EMAIL_ADDRESS>Date:   Wed Apr 26 23:08:24 2023 +0200
added Readme file with usage example

commit 8e105b9d700bd67ca465dce84ba66b8be0e904c0
Author: somhi<EMAIL_ADDRESS>Date:   Wed Apr 26 23:07:50 2023 +0200
minor update terasic_deca_retro_cape.py

commit 6499dfb8a5db5731c0197d2641162be19773883e
Author: somhi<EMAIL_ADDRESS>Date:   Wed Apr 26 21:37:28 2023 +0200
added terasic_deca_retro_cape.py board definition

Please also include a comment with a link to your retro cape in the python file

That's merged, thanks!


When sensor session ends glucose value is 1

When a sensor session ends at the end of a week (but I've yet to change the sensor) the glucose value coming out is 1.

Yeah, there needs to be an external-facing update struct that interprets the underlying packet data with human-readable state enumerations, etc.


Pylance reports "Invalid character in token" but character is valid

New version of this plugin uses PyLance, which compains here:
𐌎 = 42  # Invalid character in token

But this is a valid character:
> ipython
Python 3.7.4 (default, Aug 13 2019, 15:17:50)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.21.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: 𐌎 = 42

In [2]: 𐌎
Out[2]: 42

ref: https://www.asmeurer.com/python-unicode-variable-names/ -- this links to a list of all valid characters for variable names

Thanks for the bug report.
Pylance supports unicode characters in general, but it doesn't currently support "supplementary characters" that extend the UTF16 Unicode character set. The character above falls into that category. It uses the "surrogate" character 0xD800 followed by a second 16-bit value to encode the "𐌎" symbol, which is character in the "old italic" character set (from a dead language). We'll need to add support for these supplementary characters in the pyright tokenizer so it properly handles the complete "Lo" character set, which PEP 3131 indicates is supported for identifiers.

This will be addressed in the next release.

Is there any way I can disable the warning for now?
https://stackoverflow.com/questions/67552574/in-vscode-prevent-pylance-invalid-character-in-identifierpylance-errors

There's no way to disable the warning short of disabling pylance. You can work around it by choosing identifier names that don't rely on supplementary characters. Out of curiosity, why are you using characters from dead languages in your variable names? I know that it's supported by Python, but it doesn't seem to be a good idea for code readability.
We typically release a new version of pylance each week, so you won't have to wait long for the fix.

My brain parses single characters more easily than words.
I wouldn't do it on a team project, but for my own code it makes a big difference.

This code generates a file I work from:
import requests
from bs4 import BeautifulSoup

# original URL from localhost
URL = "https://www.asmeurer.com/python-unicode-variable-names/start-characters.html"
page = requests.get(URL)

soup = BeautifulSoup(page.content, 'html.parser')
# table = soup.find('table')

lines = soup.tbody.find_all('tr')

groups = {}

for tr in lines:
    td = tr.find_all('td')
    group = td[2].text.split(' ')[0]
    symbol = td[1].text

    if group in groups:
        groups[group] += [symbol]
    else:
        groups[group] = [symbol]

exclude = 'HANGUL CJK SOGDIAN ELYMAIC DOGRA NANDINAGARI ZANABAZAR SOYOMBO MASARAM' \
    ' GUNJALA MAKASAR ANATOLIAN MEDEFAIDRIN TANGUT NUSHU (unknown) HENTAIGANA NYIAKENG'.split(' ')

with open('symbols.txt', 'w') as _file:
    for group, symbols in groups.items():
        if group not in exclude:
            _file.write(str(group) + '\n' + " ".join(symbols) + '\n\n')

There's also https://www.asmeurer.com/python-unicode-variable-names/continue-characters.html

This issue has been fixed in version 2021.5.3, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202153-19-may-2021

Hi! I am still having this issue (VSCode version is 1.58.2) with Jupyter Notebook cells running shell scripts via ! like !<my_bash_script>.

That's unrelated; see https://github.com/microsoft/pylance-release/issues/1579#issuecomment-884300836 and https://github.com/microsoft/vscode-jupyter/issues/6635.


[Feature] Support for deployments spanning across selected clusters.

Description
So far when Users deploy apps using Liqo, they do not have the opportunity to choose which remote clusters use to offload their workload. This new feature allows you to select specif remote clusters according to defined requirements by simply creating a custom resource called NamespaceOffloading.
Required Steps

[x]  STEP 1: Introduce a new NamespaceMap CRD that will replace NamespaceNattingTable resource. #569

[x]  STEP  2:

Implement a new Virtual-node Controller that spawns NamespaceMaps corresponding to just created VirtualNodes. This controller takes also care of NamespaceMaps' and VirtualNodes' deletion lifecycle. #561
Implement a new Namespace Controller that watches Namespace's labels and decides if a Namespace has to be offloaded onto a remote cluster or not. #571

[x]  STEP 3:

Implement a new NamespaceMap Controller that watches NamespaceMap's Spec to understand which Namespaces have to offloaded onto the remote cluster, and updates NamespaceMap'Status with the current state of the just created remote Namespaces. #587
NamespaceMap's refactor due to new features introduced by NamespaceMap Controller. #585

[x]  STEP 4: Possibility to specify, at installation time, cluster's labels; these labels must be inserted in ClusterConfig CRD with all other information about the cluster.   #597

[x]  STEP 5: Cluster's labels (of the previous step) must be imported into ResourceOffer CRD, so that VirtualKubelet could expose them on the corresponding VirtualNodes. #720

[x]  STEP 6: Introduce a new NamespaceOffloading CRD that allows the user to specify, with desired granularity, on which cluster his workload must be offloaded. #617

[x]  STEP 7: Refactor of Namespace controller in order to support NamespaceOffloading management. #639

[x]  STEP 8: New features for NamespaceMap Controller: #643

When there is a problem in remote namespace creation onto a remote cluster, the associated NamespaceMap is updated with a Refused phase for that namespace (Status->CurrentMapping-> RemoteStatus-> Phase=Refused). The NamespaceMap Controller will try to create that Namespace until the problem will be solved with exponential backoff.

The controller updates the remote namespace condition in the NamespaceOffloading resource associated with the just created remote namespace.

[x]  STEP 9: New NamespaceOffloading controller; this controller gets a just created NamespaceOffloading resource and adds entries to NamespaceMaps (Spec-> DesiredMappings) in order to require the creation of remote namespaces, based on requirements specified by users. #644

[x]  STEP 10: New OffloadingStatus controller; This new controller waits for all remote conditions of the offloaded namespace, and when the controller is able to get all of them, it sets the global offloading status according to these remote conditions. #645

[x]  STEP 11: Refactor of VirtualNode controller; now it has only to manage the NamespaceMap regeneration in case of deletion. #699

[x]  STEP 12: Modify Webhook's logic so that Pods receive the right NodeAffinity, enabling offloading only inside selected remote clusters. #591

[x]  STEP 13: Activate the new controllers of the liqo controller manager and move NamespaceMaps resources in specific Namespaces (Tenant Namespaces). #702

[x]  STEP 14: Refactor of Virtualkubelet's functionalities; only NAT and DENAT operation and transition from  NamespaceNattingTables to NamespaceMap resource. #717

[x]  STEP 15: Add checks on the privileges that the NamespaceMap controller has when creates the remote namespaces. #723

[x]  STEP 16: Activate the new webhook logic. #726

Closing since completely addressed.


Got Error When Generating 90K Sample Data with generate_train_data.py

Hi I got this error when generating more 90K Sample training data, but it just work with 10K, any solutions? Please help me :(
dict_keys(['__header__', '__version__', '__globals__', 'points', 'line_segment_index', 'grid_points'])
Traceback (most recent call last):
  File "generate_train_data.py", line 27, in <module>
    sio.savemat(save_file, {'pivot_images':pivot_images,
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio.py", line 296, in savemat
    MW.put_variables(mdict)
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio5.py", line 893, in put_variables
    self._matrix_writer.write_top(var, asbytes(name), is_global)
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio5.py", line 634, in write_top
    self.write(arr)
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio5.py", line 673, in write
    self.write_numeric(narr)
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio5.py", line 699, in write_numeric
    self.write_element(arr)
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio5.py", line 540, in write_element
    self.write_regular_element(arr, mdtype, byte_count)
  File "C:\Users\nico\anaconda3\lib\site-packages\scipy\io\matlab\mio5.py", line 554, in write_regular_element
    tag['byte_count'] = byte_count
OverflowError: Python int too large to convert to C long

I was long time ago to write the script. Can you provide details of your running? For example, the data and how your command line.

Used data:

worldcup_sampled_cameras.mat
worldcup2014.mat

I only change the n=10000 to n=90000
and then run it using python generate_train_dataa.py
It works for n=10000, but breaks when n=90000
Any Suggestions?

Thanks for the details.
It turns out that the size of saved .mat file can not be larger than 2G. https://stackoverflow.com/questions/33565414/why-does-saving-mat-files-with-scipy-result-in-larger-file-size-than-with-matlab
When n = 10000, the file size is about 1.15GB. As a result, the file size will be about 10GB when n = 90000.
One way to walk around that: saving training data to separated files, for example, 'train_data_90k_1.mat, train_data_90k_2.mat, ...' Each file has 10000 training examples.

Thanks for the reply, I found out that numpy .npz format can handle the file size larger than 2G :)
Here is how I modify the code to save .npz file


[6.0] Fix request cycle in macro expansion mangling

6.0 cherry-pick of https://github.com/apple/swift/pull/74201

Description: Expanding a macro inside a local function with autoclosures would attempt to assign discriminators before the autoclosures had been formed. As a result, SILGen would emit autoclosures with duplicate symbol names. This would either cause a silent miscompile or diagnose an error about mismatched SIL function types. This PR changes the macro expansion buffer mangling to use the source location of the expansion instead. This avoids evaluating requests before everything has been type checked.

Origination: This never worked, but it's become more common now that the with.*Continuation functions have a default argument that expands the #isolation macro. These APIs are often used with local functions.

Radar: Fixes rdar://127078338.

Risk: Low. However, to avoid silent miscompiles in the future, this converts the absence of a discriminator into a fatal error. This is a major invariant violation which should always be flagged, even in noassert builds.

Reviewed by: @DougGregor

@swift-ci Please test

https://github.com/apple/llvm-project/pull/8894
@swift-ci Please test macOS


Add undriven off lint flag for verilator compat

Similar to the comments we use for the term primitives to silence the
verilator unused warnings, this adds comments to silence verilator
undriven warnings when using the undriven primitie.

The changes in verilator_compat.json ensure this is covered by the test that consumes that file, produces verilog, and runs verilator to check if there are any lint errors 9https://github.com/rdaly525/coreir/blob/d34406cda663ca93db1f1dea66b64bbbb1431858/tests/binary/test_issues.py#L4)


[stdlib] Document a fatal surprise with Sequence._copyContents

Array’s _copyContents implementation traps if given too small a buffer. This prevents Sequence._copyContents from being used to speed up copying data into discontiguous memory. (We have to require a Collection conformance and run _copyContents on slices instead).
Document the underlying requirement.

@swift-ci smoke test

17:23:33 [750/750] Testing WorkspaceTests.WorkspaceTests/testSimpleAPI
17:23:33
17:23:33 **** FAILURE EXECUTING SUBPROCESS ****
17:23:33 output: Fetching /private/var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/Miscellaneous_Unicode.lNs6PC/UnicodeDependency‐πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄
17:23:33 Cloning /private/var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/Miscellaneous_Unicode.lNs6PC/UnicodeDependency‐πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄
17:23:33 Resolving /private/var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/Miscellaneous_Unicode.lNs6PC/UnicodeDependency‐πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄ at 1.0.0
17:23:33 [1/3] Compiling UnicodeDependency_π_µ_____x__________ UnicodeDependency‐πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄.swift
17:23:33 [2/4] Merging module UnicodeDependency_π_µ_____x__________
17:23:33 [3/5] Compiling π_µ_____x__________ πשּׁµ𝄞🇺🇳x̱̱̱̱̱̄̄̄̄̄.swift
17:23:33 [4/6] Merging module π_µ_____x__________
17:23:33 [5/9] Compiling π_µ_____x___________tool main.swift
17:23:33 [6/10] Merging module π_µ_____x___________tool
17:23:33 [7/10] Linking πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄‐tool
17:23:33 [9/10] Compiling π_µ_____x__________Tests πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄Tests.swift
17:23:33
/private/var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/Miscellaneous_Unicode.lNs6PC/Miscellaneous_Unicode/Tests/πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄Tests/πשּׁµ𝄞🇺🇳🇮🇱x̱̱̱̱̱̄̄̄̄̄Tests.swift:1:8: error: module compiled with Swift 5.3.2 cannot be imported by the Swift 5.4 compiler: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib/XCTest.swiftmodule/x86_64-apple-macos.swiftmodule

<Confused doggo head tilt>

@swift-ci smoke test macOS platform

Did we ever add the explicit requirement that Collection.underestimatedCount has to return count? Maybe we should say that if called on a collection, ptr must have the full contents to be copied.

Well, the docs for Collection.underestimatedCount say it's "A value less than or equal to the number of elements in the collection.", so returning the exact count is evidently not a requirement.
The Array family are the only types I've encountered that trap when _copyContents is given too little space. Even there, the code could've worked just as well without trapping; this seems like an overeager precondition.
    // It is not OK for there to be no pointer/not enough space, as this is
    // a precondition and Array never lies about its count.
    guard var p = buffer.baseAddress
      else { _preconditionFailure("Attempt to copy contents into nil buffer pointer") }
    _precondition(self.count <= buffer.count,
      "Insufficient space allocated to copy array contents")

I don't think we could reasonably require that in the Collection case _copyContents must be called with a buffer large enough to hold self.count elements -- that would make it impossible to safely call _copyContents in a context that's generic only over Sequence. :-/
func foo<S: Sequence>(_ items: S) {
  let buffer: UnsafeMutableBufferPointer<S.Element> = .allocate(capacity: ???) // Can't access `items.count` here
  var (iterator, count) = items.copyContents(initializing: buffer)
}

I just noticed the default implementation Sequence._copyContents already has a doc comment!
  /// Copies `self` into the supplied buffer.
  ///
  /// - Precondition: The memory in `self` is uninitialized. The buffer must
  ///   contain sufficient uninitialized memory to accommodate `source.underestimatedCount`.
  ///
  /// - Postcondition: The `Pointee`s at `buffer[startIndex..<returned index]` are
  ///   initialized.

I think we probably should just copy this on the protocol definition.

Oh yeah — that makes sense. The last time I chased down the path to that Array call it was more convoluted than I thought... I'll try an experiment to see whether a version without that expectation hurts much, though we I doubt we can do anything to remove the requirement in inlined code.

I spent a little time properly explaining preconditions and all the various guarantees on the returned state.
Hopefully we'll be able to eventually replace this messy interface with public API that enables accessing & copying data in/out of piecewise contiguous data structures, not just flat stuff.
For example, we could replace _copyContents with a new IteratorProtocol customization point that provides direct access to any underlying storage chunks:
protocol IteratorProtocol {
  // Calls `body` with an unsafe buffer of at most `maximumCount` elements
  // from the current iterator position, with the side effect of advancing the
  // iterator over them.
  //
  // If there are no more elements left, `body` is called with an empty buffer.
  // Otherwise the buffer's count will be somewhere between `1 ... maximumCount`,
  // depending on the internal layout of the underlying `Sequence`.
  //
  // The default implementation simply calls `next()` and calls `body` with a
  // temporary buffer over its result.
  //
  // `maximumCount` must be greater than zero.
  mutating func withNextUnsafeSegment<R>(
    maximumCount: Int?,
    _ body: (UnsafeBufferPointer<Element>) throws -> R
  ) rethrows -> R
}

(Handling availability well will be tricky, I expect.)

I'll try an experiment to see whether a version without that expectation hurts much, though we I doubt we can do anything to remove the requirement in inlined code.

Yep, although I think what's even more troublesome is that previously released libswiftCore.dylibs contain protocol witness implementations (and I'm guessing Array specializations) with the trap in place, and they will continue to sometimes trigger whenever an app is deployed to any earlier OS release.
We also don't know how many custom Collection implementations may have implemented the same trap as a (not very useful) defensive measure. (They aren't really supposed to, but these things are technically public and we better not break binaries.)
I think we have to live with the requirement until we get a chance to design a proper replacement. 😞

@swift-ci smoke test

@swift-ci test windows platform

Looks like the Windows build is stuck on some async tests.
Build timed out (after 60 minutes). Marking the build as aborted.

@swift-ci smoke test windows platform


Swagger UI - Try it out not working

The Swagger-UI doesn't return data.
curl and get via browser work fine
post via postman works fine

resolved via 4188f6a


create a Payments tag in horizon OpenAPI spec

To give front more of a "front set" to the /payments endpoint, lets create its own tag/category.

Preview is available here:http://developers-pr772.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr772.previews.kube001.services.stellar-ops.com

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr772.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr772.previews.kube001.services.stellar-ops.com

Something went wrong with PR preview build please check


Updated to CF API v3

Thank you for contributing to the CF CLI Plugin Repository!
This repo contains both the plugin repo server and the metadata for CLI
community plugins.
Some of the requirements for PRs will apply to only one of these parts.
We're not allowed to accept any PRs without a signed CLA, no matter how small.
If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
Submitting Plugins
If you haven't yet, please review our contributing guidelines:
https://github.com/cloudfoundry/cli-plugin-repo#submitting-plugins
In particular ensure the following requirements are being met:

[ ] The plugin's name field in repo-index.yml matches the Name field in the plugin's plugin.PluginMetadata section
[ ] The plugin's url field in repo-index.yml contains the same version from the version field

Submitting PRs to CLIPR (the CLI Plugin Repo server)
All new code requires tests to protect against regressions.
Description of the Change
We must be able to understand the design of your change from this description.
Keep in mind that the maintainer reviewing this PR may not be familiar with or
have worked with the code here recently, so please walk us through the concepts.
Why Is This PR Valuable?
What benefits will be realized by the code change? What users would want this change? What user need is this change addressing?
Applicable Issues
List any applicable Github Issues here
How Urgent Is The Change?
Is the change urgent? If so, explain why it is time-sensitive.
Other Relevant Parties
Who else is affected by the change?

Updating to CF API v3 and submitting for my colleague Philip Mugglestone.
Thanks, -Andrew. reach me at<EMAIL_ADDRESS>for questions.


Add a null check to catch missing metadata

I ran into a failure when running the container on my machine and traced it back to this line of code. Adding a quick null check fixes the failure.
> /usr/src/app/index.js:207
> airingArt = programme.episode.poster.path
> ^
>
> TypeError: Cannot read property 'path' of undefined
> at /usr/src/app/index.js:207:50
> at Array.forEach (<anonymous>)
> at /usr/src/app/index.js:182:27
> at Array.forEach (<anonymous>)
> at /usr/src/app/index.js:165:12
> at Object.grabJSON (/usr/src/app/index.js:33:9)
> at Object.<anonymous> (/usr/src/app/index.js:99:11)
> at Module._compile (internal/modules/cjs/loader.js:1063:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1103:10)
> at Module.load (internal/modules/cjs/loader.js:914:32)

Looks like this catches my error as well:
[INFO] Grabbing EPG...
http://api.pluto.tv/v2/channels?start=2020-12-26%2021%3A00%3A00.000-0800&stop=2020-12-27%2003%3A00%3A00.000-0800
http://api.pluto.tv/v2/channels?start=2020-12-27%2003%3A00%3A00.000-0800&stop=2020-12-27%2009%3A00%3A00.000-0800
http://api.pluto.tv/v2/channels?start=2020-12-27%2009%3A00%3A00.000-0800&stop=2020-12-27%2015%3A00%3A00.000-0800
http://api.pluto.tv/v2/channels?start=2020-12-27%2015%3A00%3A00.000-0800&stop=2020-12-27%2021%3A00%3A00.000-0800
[DEBUG] Using api.pluto.tv, writing cache.json.
[INFO] Adding WatchFree Movie Binge channel.

SNIP

[INFO] Adding instance of Executioners From Shaolin to channel Flicks of Fury.
(node:14) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'path' of undefined
    at /usr/src/app/index.js:207:50
    at Array.forEach (<anonymous>)
    at /usr/src/app/index.js:182:27
    at Array.forEach (<anonymous>)
    at /usr/src/app/index.js:165:12
    at /usr/src/app/index.js:91:7
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:14) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:14) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
mv: can't rename 'playlist.m3u': No such file or directory
mv: can't rename 'epg.xml': No such file or directory
Last ran: Sat Dec 26 21:52:05 PST 2020


Implement Uty's designs

This PR implements some of Uty's designs. It's a bit of work, so I tried my best to make 4 sane commits to perhaps review one by one.
The bounty page is still a WIP but wanted to get something out so we can visualize things a bit more


Revert "[BEAM-4752] Add support for newer dill dependency"

Reverts apache/beam#5931
R: @alanmyrvold
Breaks post commit tests: https://builds.apache.org/job/beam_PostCommit_Py_ValCont/228/console

Thanks, LGTM.  I don't quite understand how the change breaks the SDK harness though:
DataflowRuntimeException: Dataflow pipeline failed. State: FAILED, Error:
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Error received from SDK harness for instruction -83: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/sdk_worker.py", line 134, in _execute
    response = task()
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/sdk_worker.py", line 169, in <lambda>
    self._execute(lambda: worker.do_instruction(work), work)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/sdk_worker.py", line 215, in do_instruction
    request.instruction_id)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/sdk_worker.py", line 234, in process_bundle
    self.data_channel_factory)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 230, in __init__
    self.ops = self.create_execution_tree(self.process_bundle_descriptor)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 272, in create_execution_tree
    descriptor.transforms, key=topological_height, reverse=True)])
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 207, in wrapper
    result = cache[args] = func(*args)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 255, in get_operation
    in descriptor.transforms[transform_id].outputs.items()
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 254, in <dictcomp>
    for tag, pcoll_id
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 207, in wrapper
    result = cache[args] = func(*args)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 255, in get_operation
    in descriptor.transforms[transform_id].outputs.items()
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 254, in <dictcomp>
    for tag, pcoll_id
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 207, in wrapper
    result = cache[args] = func(*args)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 258, in get_operation
    transform_id, transform_consumers)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 362, in create_operation
    return creator(self, transform_id, transform_proto, payload, consumers)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 499, in create
    serialized_fn, parameter.side_inputs)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/runners/worker/bundle_processor.py", line 537, in _create_pardo_operation
    dofn_data = pickler.loads(serialized_fn)
  File "/usr/local/lib/python2.7/site-packages/apache_beam/internal/pickler.py", line 238, in loads
    return dill.loads(s)
  File "/usr/local/lib/python2.7/site-packages/dill/dill.py", line 277, in loads
    return load(file)
  File "/usr/local/lib/python2.7/site-packages/dill/dill.py", line 266, in load
    obj = pik.load()
  File "/usr/local/lib/python2.7/pickle.py", line 864, in load
    dispatch[key](self)
  File "/usr/local/lib/python2.7/pickle.py", line 1096, in load_global
    klass = self.find_class(module, name)
  File "/usr/local/lib/python2.7/site-packages/dill/dill.py", line 423, in find_class
    return StockUnpickler.find_class(self, module, name)
  File "/usr/local/lib/python2.7/pickle.py", line 1130, in find_class
    __import__(module)
ImportError: No module named _dill

Thanks, LGTM. I don't quite understand how the change breaks the SDK harness though:

I do not understand yet either. I will investigate this afternoon.

Looked at this a bit more and my guess is that the version of dill differs from job submission (latest, 0.2.8) and on the SDK harness when deserializing (0.2.6).  So at submission time, the pickled output references dill._dill, but when run on the SDK harness, this isn't defined since it uses the old version.  So maybe the safe thing to do is to add a similar branch that also populates dill._dill if it isn't there.

Closing this, because https://github.com/apache/beam/pull/5949 has a fix for the issue.

@alanmyrvold
It seems like 0.2.8 produces serialized data that is not compatible with 0.2.6 (https://issues.apache.org/jira/browse/BEAM-4785 to fix it. There are some blockers though.)


Bug fix/auth header

Updated auth header to still be backwards compatible with cfg.reader.token but now accepts a user defined auth header.

Can you run npm audit fix to clean up some of the known vulnerabilities? That might clear up some other PRs from dependabot.


Issuer Url contains newLine and space chars

Hi,
creating an AuthnRequest with spid/laravel  package produces a malformed value in the xml because of this particular snippet of code (that was patched a couple of months ago here) in AuthnRequest.php

Not being on a single line adds some \n and whitespaces into the text value of the tag, causing SAML validation for italian SPID to fail

Issuer and entityID URLs are the same, but in the SAML request this is not well formed and fails validation.
Is there anyone that already faced this kind of issue?
Thanks in advance

Not being on a single line adds some \n and whitespaces into the text value of the tag, causing SAML validation for italian SPID to fail

Where are those \n or whitespaces added? are in the saml:Issuer content?
As you see here:
    <saml:Issuer>{$spEntityId}</saml:Issuer>

No extra space or whitelines are added to the body, only the value of $spEntityId
and there is no format, so I don't think I that Issuer you shared belong this toolkit.
In the patch you introduced, you should be adding
<saml:Issuer
    NameQualifier="{$spEntityId}"
    Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity"
>{$spEntityId}</saml:Issuer>

instead of
<saml:Issuer
        NameQualifier="{$spEntityId}"
        Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity">
        {$spEntityId}
    </saml:Issuer>

to avoid the issues you are experiencing.

Thank you @pitbulk, after some extra check I realized that the issue is not in this package but just in the linked patch from another repo. Sorry for bothering, I just assumed the codebase being identical, which is not.
thank you again, i will close the issue


Add multi-language support

It would be nice to have multiple language support in sigmausd.io

Community member has offered to do Polish translation

https://github.com/i18next/react-i18next


Quick fix for build failure when CMAKE_INSTALL_PREFIX not specified.

When -DCMAKE_INSTALL_PREFIX="" was not given in command line, the
generated VS project has incorrent value for Linker option "Generate Program
Database File" that caused build fail.
This patch check CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT first
then set CMAKE_INSTALL_PREFIX to "" if it is true.
This might fix #131 .

AppVeyor 過不了，真怪。

#189 fixes CMAKE_INSTALL_PREFIX. and It can be any local path.


Add unix include path for AIX for JCK8

In JCK8, we do not have a "linux" folder under jni include, unlike the later JCK versions. Hence, for JCK8 AIX, we need to supply the "unix" folder in the include path for compiler to figure out necessary header files.
Resolves  backlog/issues/475
Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

Test : Internal/Grinder/14311

@JasonFengJ9 - please review.

Maybe a sanity test for JCK8/11?

Sanity check on JCK11 is really necessary, as the issue here falls under JCK8 only (plus, JCK11 on AIX is working fine, please see internal/Test_openjdk11_j9_sanity.jck_ppc64_aix_testList_2/15).
However, a sanity check on JCK8 + AIX is a good idea, since there was no testing done on JCK8 for the original set of changes that caused this failure.
sanity.jck started: internal/Grinder/14312

Sanity check on JCK11 is not really necessary, as the issue here falls under JCK8 only (plus, JCK11 on AIX is working fine
Technically this PR introduced an additional -I$(UNIX_PATH) for JCK11 which worked without it though I do agree the risk is low.

Technically this PR introduced an additional -I$(UNIX_PATH) for JCK11 which worked without it though I do agree the risk is low.

On JCK 11+, the header files will be picked up by -I$(LINUX_PATH). So, I do not see how this PR can cause any issue on JCK11+.
I ran a Grinder with 1 JCK target to ensure compilation on JCK11 is un-disturbed by this PR. It works fine. Please see : Internal/Grinder/14313/


Add title and removeTitle props to BusinessForm and PaymentProvisioning

Add optional title prop to BusinessForm and PaymentProvisioning
Straight-forward PR:

Adds optional prop: title to BusinessForm and PaymentProvisioning components

allows users to update title shown on form

updates documentation, adds controls to storybook docs

Adds optional prop: removeTitle to BusinessForm and PaymentProvisioning components

allows users to remove title shown on form

updates documentation, adds controls to storybook docs

Links
Closes #480
Developer considerations

On any task

[X] Previous unit and e2e tests are passing
[ ] Perform dev QA

Developer QA steps
Fairly easy QA - can check in Storybook

[ ] BusinessForm - verify that title prop displayed in Storybook controls updates form title - replaces Business Information
[ ] PaymentProvisioning - - verify that title prop displayed in Storybook controls updates form title - replaces Business Information

Hey @colganmeanor
I see a warning in the build output. Maybe we should find another name for the prop?

Hey @colganmeanor
I see a warning in the build output. Maybe we should find another name for the prop?

Great call - thank you @TiagoFuelber. I didn't even notice this.
Updated to form-title!


[Doc] Provide a pre-condition in the doc to start BPS with relevant inscturctions

Doc link: https://docs.wso2.com/display/IS540/Adding+a+Workflow+Engine
Looks like this doc is referring to a separate BPS node to be up and running. Please provide this as a pre-condition in the doc.

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


File descriptors leak (not released properly)

Summary:
It seems that not all sockets are released/closed properly when an input source connects and then disconnect.  The open socket count for the process "voctocore" increases by 2 after every connect/disconnect cycle.
Problem description:
What I am experiencing is that when an input Source connect and then disconnects repeatedly, over time the number of open file descriptors/sockets for the Voctocore process increases.  It seems the old socket allocated by a Source is not properly released when the Source disconnects.
Normally this is not a big problem, but after many disconnects and reconnects of my Sources the process runs out of its maximum allowed open sockets as determined by the operating system. Voctocore then stops to work and although the process doesn't die it is as good as dead.  A restart of the process gets it going again.
My setup:

Ubuntu 16.04 desktop, with kernel 4.4.0-96-generic.

Voctocore: latest git cloned on 6 November 2017.

I connect and disconnect a Source to Voctocore on port 10000. (The Source is an ffmpeg instance streaming a local media file to "-f matroska tcp://localhost:10000".)

I check the number of open file descriptors using:  'ls /proc/3351/fd | wc -l'   where 3351 is the process ID of Voctocore.

The number of open file descriptors increase after every connect and disconnect (it increases by 2).

When the Source connects, the number of file descriptors increases by 5.  When it disconnects it decreases by 3.  The result is a "leak" of 2 file descriptors for every connect/disconnect cycle.

Using 'ls -lrth /proc/3351/fd' it seems the two leaked file descriptors are sockets, since the output for these two are:
lrwx------ 1 ubuntu ubuntu 64 Sep 28 09:59 72 -> socket:[16637009]
lrwx------ 1 ubuntu ubuntu 64 Sep 28 09:59 71 -> socket:[16637008]

Using 'lsof -a -p 3351' and grepping for 16637009 and 16637008 I see both are of type "STREAM.

Am I doing something wrong which cause this leak?  Is this a known issue?  Any suggestions?

Connected to localhost.
Escape character is '^]'.
quit
nothing.
ps I was getting bit by this when a client was trying to feed a non existent loop for the stream blanker.


codegen: Fix bindgen-injected items in namespaces.

Found while trying to use namespaces in stylo.
r? @fitzgen

 Warning

These commits modify unsafe code. Please review it carefully!

@bors-servo r+

:pushpin: Commit 161a590 has been approved by fitzgen

:hourglass: Testing commit 161a590 with merge 47e4ec7...

:sunny: Test successful - status-travis


Added support for BTC <=> ZEC to poloniex exchange

Added support for BTC <=> ZEC to poloniex exchange
And updated gitignore to allow for multiple config*.js files to be ignored.

Could you please craete a PR against the develop branch? Thanks!

Ok, np.
On Mar 8, 2017 7:02 PM, "Mike van Rossum"<EMAIL_ADDRESS>wrote:

Could you please craete a PR against the develop branch? Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/pull/614#issuecomment-285012121, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABAwKeKxC4iWQPJ56lj-Ra8FTet_dif7ks5rjorJgaJpZM4MWpO2
.


Items in array not validated

Mac OSX 10.10.5
Python 2.7.11
jsonschema (2.5.1)
I've been testing jsonschema to see if it will work my Python based API testing. I've hit a road block trying to figure out why this particular array is not being validated at all. It should be throwing a variety of failures, but does not.  I've seen other arrays processed correctly but am not seeing why this specific one is not.
import jsonschema

schema = {
  "$schema": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "properties": {
    "pushNotifDevices" : {
      "type": "array",
      "description" : "",
      "items": {
        "applicationId": {
          "type": "boolean",
          "example":"CTS",
          "description":"This application ID identifies."
        },
        "deviceType":{
          "type": "string",
          "enum":["ANDROID"],
          "description":"This enum indicates the type of device."
        },
        "deviceId": {
          "type":"string",
          "maxLength":1,
          "description":"Unqiue DeviceID."
        },
        "notifDeviceId": {
          "type":"string",
          "maxLength":1,
          "description":"This ID."
        },
        "active" : {
          "type":"boolean",
          "default":True,
          "description":"Boolean to determine if the device is active."
        },
        "failureDescription" : {
          "type":"string",
          "maxLength":1,
          "description":"This indicates the reason."
        }
      },
      "required": [
        "applicationId",
        "deviceType",
        "deviceId",
        "notifDeviceId"
      ]
    }
  }
}

data = {
    "pushNotifDevices": [
        {
            "active": True,
            "applicationId": True,
            "deviceId": "45BBBE14",
            "deviceType": "ANDROID",
            "failureDescription": "r",
            "notifDeviceId": "4"
        },
        {
            "active": 123,
            "applicationId": "CTS",
            "deviceId": "45BBBE14",
            "deviceType": "IOS",
            "failureDescription": "remote notifications are not supported",
            "notifDeviceId": "45BBBE14"
        },
        {
            "active": True,
            "applicationId": "CTS",
            "deviceId": "56A8FB8B",
            "failureDescription": "REMOTE_NOTIFICATION_SIMULATOR_NOT_SUPPORTED",
            "notifDeviceId": "56A8FB8B"
        }
    ]
}

jsonschema.Draft4Validator.check_schema(schema)
jsonschema.validate(data, schema)

You provided items, but didn't put the properties in a propertiesin that schema, so they're all ignored (as if they're unknown validators).

And I thank you kindly. :)  I looked at this for hours and never noticed the properties was missing. I add that in, and now my pushNotifDevices are being validated.
Thanks for your work on this excellent tool.

Glad to hear, and glad to hear you're enjoying :). Cheers.

I should clarify, the schema is being provided to me via RAML documentation for an API I'm attempting to test.
Questions:
Is the above an issue with my schema? I'm not seeing any documentation in regards to arrays as to whether they should have properties defined.
Or is this simply something I must manually modify in the schema to support being able to use validation?
I was really hoping for my first pass at this to be able to use the schema as provided, and have the tool find type mismatches, enums that don't bind to the list, required fields that are missing, parameters that are totally missing, etc. All of the low hanging fruit with minimal additional effort on my part for right now.  Unrealistic expectations?
It has found various schema issues for me, so it's working.
Many thanks.

@Assassin236  - Hope this helps.
import jsonschema

schema = {
    "$schema": "http://json-schema.org/draft-04/schema#",
    "type": "object",
    "properties": {
        "pushNotifDevices": {
            "type": "array",
            "description": "",
            "items": {
                "type": "object",
                "properties": {
                    "applicationId": {
                        "type": "boolean",
                        "example": "CTS",
                        "description": "This application ID identifies."
                    },
                    "deviceType": {
                        "type": "string",
                        "enum": ["ANDROID"],
                        "description": "This enum indicates the type of device."
                    },
                    "deviceId": {
                        "type": "string",
                        "maxLength": 1,
                        "description": "Unqiue DeviceID."
                    },
                    "notifDeviceId": {
                        "type": "string",
                        "maxLength": 1,
                        "description": "This ID."
                    },
                    "active": {
                        "type": "boolean",
                        "default": True,
                        "description": "Boolean to determine if the device is active."
                    },
                    "failureDescription": {
                        "type": "string",
                        "maxLength": 1,
                        "description": "This indicates the reason."
                    }
                }
            },
            "required": [
                "applicationId",
                "deviceType",
                "deviceId",
                "notifDeviceId"
            ]
        }
    }
}

data = {
    "pushNotifDevices": [
        {
            "active": True,
            "applicationId": True,
            "deviceId": "45BBBE14",
            "deviceType": "ANDROID",
            "failureDescription": "r",
            "notifDeviceId": "4"
        },
        {
            "active": 123,
            "applicationId": "CTS",
            "deviceId": "45BBBE14",
            "deviceType": "IOS",
            "failureDescription": "remote notifications are not supported",
            "notifDeviceId": "45BBBE14"
        },
        {
            "active": True,
            "applicationId": "CTS",
            "deviceId": "56A8FB8B",
            "failureDescription": "REMOTE_NOTIFICATION_SIMULATOR_NOT_SUPPORTED",
            "notifDeviceId": "56A8FB8B"
        }
    ]
}
print("errors in schema : ")
print(jsonschema.Draft4Validator.check_schema(schema))
print("errors in data : ")
print(jsonschema.validate(data, schema))


Restore Database with PITR in case of disaster

HI,
If my database got destroyed or crashed, can I still use PITR (Point-in-time Restore) to restore my database??
Thanks

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

ID: 5d508914-7960-bbaa-a454-4564a81b2f24
Version Independent ID: 679907b3-6a66-1a2f-1906-aa15700c341c
Content: PowerShell example-restore-backup-Azure SQL database
Content Source: articles/sql-database/scripts/sql-database-restore-database-powershell.md
Service: sql-database
Sub-service: backup-restore
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

Hi @aayush3667, thanks for contacting Microsoft! Would you mind clarifying what you mean by destroyed or crashed?
Thanks!
Masha from the SQL Docs team


added Kalos Route 1 encounters, slots, and location_area for X and Y

I have added in data regarding encounters on route 1 based on the strategy guide.  Only thing I don't have is the min max levels.  I only have to one route at the moment as I want to ensure I have done it right since I have never added data before.
Thanks

We ended up ripping these! Thanks though.


Multiple issues in the 0.7.3 release

I'm using this ticket to collect issues that I found in the 0.7.3 release.
1. Tails file upload fails when a credDef is created and multi ledger support is enabled.
See discussion on the chat: https://chat.hyperledger.org/channel/aries-cloudagent-python?msg=XodRcp7dFxmncAWma I still do not get this to work.
2. Revocation notification has a wrong revocation id for V1 exchanges (V2 works as expected)
For example the credential acked event has the following link to the revocation registry:
{
        "rev_reg_id": "7D2jFxSPJP4zTAP9WAcJWo:4:7D2jFxSPJP4zTAP9WAcJWo:3:CL:571:CustomerBankRevoc:CL_ACCUM:01f6b385-28bc-420a-bcc7-00ac282b1d3c",
        "cred_rev_id": "5"
}

But in the revocation event the value of the revocation id becomes 6 instead of 5.
{
    "thread_id": "indy::7D2jFxSPJP4zTAP9WAcJWo:4:7D2jFxSPJP4zTAP9WAcJWo:3:CL:571:CustomerBankRevoc:CL_ACCUM:01f6b385-28bc-420a-bcc7-00ac282b1d3c::6",
    "comment": null
}

3a. V2 Credential exchange ignores the auto-respond-credential-request: false flag
If aca-py receives a V2 credential request it immediately responds even if the auto flag is set to false. Works as expected for V1.
3b. V2 Presentation exchange ignores the auto-respond-presentation-proposal: true flag
If aca-py receives a V2 presentation proposal and the auto respond flag is set to true aca-py does not automatically respond. Works a expected for V1.
4. Wallet type askar has issues when receiving V1 credentials.
Probably same as or related to #1588 Any other time answering a credential offer with a request fails with:
2022-01-13 11:40:34,184 aries_cloudagent.admin.server ERROR Handler error with exception: Record not found.
2022-01-13 11:40:34,184 aries_askar.native.aries_askar.ffi.store INFO 	src/ffi/store.rs:1007 | Closed session SessionHandle(980)
2022-01-13 11:40:34,185 aries_askar.native.aries_askar.backend.db_utils INFO 	src/backend/db_utils.rs:168 | Dropped pool connection
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v1_0/routes.py", line 997, in credential_exchange_send_request
    cred_ex_record, connection_record.my_did
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v1_0/manager.py", line 471, in create_request
    await cred_ex_record.save(session, reason="create credential request")
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/messaging/models/base_record.py", line 354, in save
    await storage.update_record(record, record.value, record.tags)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/storage/askar.py", line 121, in update_record
    raise StorageNotFoundError("Record not found") from None
aries_cloudagent.storage.error.StorageNotFoundError: Record not found

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 163, in ready_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 200, in debug_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp_apispec/middlewares.py", line 45, in validation_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 301, in check_token
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 391, in setup_context
    return await task
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v1_0/routes.py", line 1017, in credential_exchange_send_request
    outbound_handler,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v1_0/__init__.py", line 63, in report_problem
    raise http_error_class(reason=err.roll_up) from err
aiohttp.web_exceptions.HTTPBadRequest: Record not found.

@shaangill025 and @andrewwhitehead --- can the two of you please look at these?  Shaanjot likely the 1, 2 and 3 as they are in the same area, Andrew the fourth because of the Askar connection.
Thanks

For #4, it appears that the process is failing when trying to update the credential exchange record because it doesn't exist. This could be because auto-respond was enabled and the exchange has already completed and been removed. I can't see why this behaviour would be any different with the Askar backend.

For #4, it appears that the process is failing when trying to update the credential exchange record because it doesn't exist. This could be because auto-respond was enabled and the exchange has already completed and been removed. I can't see why this behaviour would be any different with the Askar backend.

That is a good point, so I double checked the agents config. Here I have two 0.7.3 agents with all auto-respond-credential-xxx flags set to true. One is running in askar and the other in indy mode. The indy agent behaves as expected with the exchange going through automatically. The askar one always gets stuck at credential received. The exception above happens from time to time when I trigger the credential request manually. So this seems more related to the configuration issues mentioned above where the config flags are ignored or not being parsed correctly any more.

For #4, it appears that the process is failing when trying to update the credential exchange record because it doesn't exist. This could be because auto-respond was enabled and the exchange has already completed and been removed. I can't see why this behaviour would be any different with the Askar backend.

It's indeed different. I have two 0.7.3 agents, one running in indy the other in aksar, both have all auto-respond-credential-xxx flags set to false. The indy one works a s expected. The askar one receives the credential offer, but is not able to handle the credential request trigger because the record is missing. I double checked to see if maybe the exchange runs through automatically and the controller reacts on a wrong state, but thats not the case.

@etschelp Which Storage Backend are you running in the Acapy. Do you use Postgres or SQLite ?

@etschelp Which Storage Backend are you running in the Acapy. Do you use Postgres or SQLite ?

Always Postgres

@etschelp  We saw also errors on the Postgres Backend regarding encoding problems with utf-8 and askar. Did you tried it with sqlite ?

What are your encoding problems? So far I did not experience any. But your question made me curious, by looking at the init methods in the indy and askar sdk's I do not see that there is any encoding set. Which means for postgres it comes back to the defaults. If you are using the docker image its derived from LANG=en_US.utf8 if not it is ascii, or what was set during initdb, or during createdb. So the first thing that I would check is if the encoding of the wallet db that aca-py is using is correct.

Askar (via sqlx) always sets the client encoding to utf8 when creating a connection. What kind of encoding problems are you seeing?

On my Mac I can run the performance demo with a test of 300 credential exchanges using the following (with Postgres.app installed): POSTGRES=1 LEDGER_URL=http://test.bcovrin.vonx.io python3 -m runners.performance --wallet-type askar. Note this uses the issue-credential-2.0/send endpoint to automate the send.
Startup duration: 5.05s
Faber      | Connected
Connect duration: 0.17s
Faber      | Publishing test schema
Alice      | Connected
Faber      | Schema ID: VYRv5TfbgWBuuzru4ayZkb:2:degree schema:42.9.95
Faber      | Publishing test credential definition
Faber      | Credential Definition ID: VYRv5TfbgWBuuzru4ayZkb:3:CL:131901:default
Publish duration: 5.73s
Faber      | Started 100 credential exchanges in 2.10s
Faber      | Started 100 credential exchanges in 3.75s
Faber      | Done starting 300 credential exchanges in 9.38s
Issuing credentials   100.0% [===================================================>] 300/300 eta [00:00]
Receiving credentials 100.0% [===================================================>] 300/300 eta [00:00]
Faber      | Completed 300 credential exchanges in 10.68s
Faber      | Average time per credential: 0.04s (28.09/s)
Alice      | alice602305 DB                 |             items |        items_tags
Alice      | ==========================================================================================
Alice      | 300 creds                      |      908   6568kB |     3914    848kB
Alice      |
Faber      | faber446483 DB                 |             items |        items_tags
Faber      | ==========================================================================================
Faber      | 300 creds                      |       19     72kB |       45     72kB

@andrewwhitehead  @etschelp  We fixed by setting the LANG environment variable. I'll open a separate issue there we can discuss it not to derive from the topic.

Can we get an update on this one at the ACA-Pug meeting today/tomorrow (2022.02.08)?  We have a WIP PR and some back and forth that may address some of the issue.  Ideally, I'd like to get the issues remaining separated into separate issues, because who doesn't like having more issues? 😂 It is easier to track one issue per issue.


Improve README.md

Codecov Report

Merging #62 into master will not impact coverage.

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   97.63%   97.63%
=======================================
  Files          13       13
  Lines         211      211
=======================================
  Hits          206      206
  Misses          5        5

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 e5c6e99...2fe17cd. Read the comment docs.

👍 LGTM, Thanks!


Add Windows 10 Dark Mode Support

you compiled it successfully? My windows build fails

I see you only include one change in this PR... would you mind to squash all your changes and then PR?

Small bug to fix but otherwise it is great! Thx


[2011-11-02] $searchable_fields needs to be defined if you want to include a method (rather than DB field or relation) in $summary_fields

created by: jonomenz
created at: 2011-11-02
original ticket: http://open.silverstripe.org/ticket/6761

if $searchable_fields is not defined, including a method (rather than DB field or relation) in $summary_fields causes an error (at least when loading object in model admin)
i.e.
public static $summary_fields = array(
    'Title' => 'Title',
    'MiscMethod' => 'Miscellaneous method'
);

/*
public static $searchable_fields = array(
    'Title'
);
*/

public function MiscMethod(){
    return 'Test';
}

will throw:
[User Error] Uncaught Exception: Unable to traverse to related object field [MiscMethod] on [ClassName]

I think this issue was never actually fixed. There is no check for ensuring that a searchable field is a real database field rather than a custom method on the DataObject.
I just posted about this in the forum: https://forum.silverstripe.org/t/fix-a-crash-related-to-searchable-fields/1952

@Taitava See #8792 It worked, but is currently broken in SS4.3

Thanks @wernerkrauss it really concerns the same thing - especially this comment by @DorsetDigital and the next one by @kinglozzer .


lspci returns no results

Describe the bug
lspci returns no results.
To Reproduce
Steps to reproduce the behavior:

tdnf install pciutils pciutils-libs hwdata -y
pciutils

Expected behavior
There is no output, even after running update-pciids.
Screenshots

If accelerated networking is disabled, this is expected as none of the mlx/mana(network) or nvme(disks) pci devices are exposed.

/cc @christopherco

@mfrw what VM sku is this? If the VM does not include any emulated/virtual PCI devices then this is expected as there is nothing listed.


feat(openchallenges): add EDAM definitions and annotations to db

Fixes #2256
Changelog

add new operation property to challenge table
add operation column and values to CSV file
add 2 new tables to challenge-service db

challenge_data_edam : a table consisting of EDAM ontology terms currently used to annotate challenges in the OC; includes parent classes
challenge_input_data_annot : a table mapping challenges to their EDAM annotation(s)

Preview
challenge_data_edam table

challenge_input_data_annot table

Closing to break into smaller PRs.


Event has no date and time of when the event occurred.

Currently, an event is output to log file with date and time of when the event is output.
An Event must be output to log file with date and time of when the event occurred.

Released in 1.6.3