Gnome extension brightness-control-using-ddcutil not patched

Describe the bug
The extension does not work correctly because it can not find /usr/bin/ddcutil in its path. The path is hardcoded in https://github.com/daitj/gnome-display-brightness-ddcutil/blob/master/display-brightness-ddcutil%40themightydeity.github.com/extension.js#L64
The path remain unchanged on my system.
Steps To Reproduce

Enable gnome 3

services.xserver.displayManager.gdm.enable = true;
services.xserver.desktopManager.gnome.enable = true;

Enable ddcutil

environment.systemPackages = with pkgs; [
   ddcutil
   gnomeExtensions.brightness-control-using-ddcutil
];

Gnome extension is not working even though its detected by ddcutil

[pp5x@photon:~]$ ddcutil detect
Display 1
   I2C bus:  /dev/i2c-2
   EDID synopsis:
      Mfg id:               DEL
      Model:                DELL U2412M
      Product code:         41082
      Serial number:        Y1H5T2AT3WNL
      Binary serial number: 861359692 (0x33574e4c)
      Manufacture year:     2012,  Week: 44
   VCP version:         2.1

Side note
Should not the gnome extension also add a dependency to ddcutil and ddcutil to hardware.i2c.enable = true ?
Expected behavior
The extension should show a slider for my display.
Screenshots

Additional context
Add any other context about the problem here.
Notify maintainers
@piegamesde
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[pp5x@photon:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.79, NixOS, 21.05.4132.24528474d2b (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"nixos-21.05.4132.24528474d2b"`
 - channels(pp5x): `"home-manager-21.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Interesting. See #136111, this should have been fixed in #137131. Please make sure you are using that commit and report back.

My bad, indeed it is not available on the stable nixpkgs. I am closing.
Here is the fix in case someone else is running into the same beginner issue.
# configuration.nix
{ config, pkgs, ... }:

let
  unstable = import <nixos-unstable> {};
in {
  environment.systemPackages = with pkgs; [
    unstable.gnomeExtensions.brightness-control-using-ddcutil
  ];
}


Support for GDscript

By default the theme doesn't support some GDscript keywords/tokens. Mostly the class_name and extends keywords were bugging me out.
I changed manually on my User Settings and here's the snippet:
"editor.tokenColorCustomizations": {
    "[Bearded Theme Arc]": {
      "textMateRules": [
        {
          //CLASS_NAME
          "scope": ["keyword.language.gdscript"],
          "settings": {
            "foreground": "#F38CEC",
            "fontStyle": "italic"
          }
        },
        {
          //PLAYER
          "scope": ["entity.name.type.class.gdscript"],
          "settings": {
            "foreground": "#ff7085"
          }
        },
        {
          //CONSTS
          "scope": ["constant.language.gdscript"],
          "settings": {
            "foreground": "#ABB7C1",
            "fontStyle": "bold"
          }
        }
      ]
    }
  },

Here's some screenshots:
BEFORE

AFTER

Idk maybe the author could use these scopes to add (or not) support for the official theme.
That's all xD

I tried to do what I could to make the colours match the other languages as much as possible, but the scopes are very very limited unfortunately...


Move off deprecated SwiftPM API

workingDirectory has been deprecated for ~6 months and is going to be removed.

@swift-ci please test

@swift-ci please test

@swift-ci please test


Add publishing binaries to GitHub Releases

What
Add publishing binaries to GitHub Releases to the publish workflow.
Why
So that binaries are available for use.

The second commit on this PR retroactively published binaries for v0.0.8.


Scroll to specific area to perform mouse actions

Hi,
We are successfully using Chrome Remote interface into our project for performing screenshot testing.
We are also able to take "mouseHover" screenshots of specific elements on the page.  That is after dispatching the "mouseHoever" Input events, the state of the element on page changes and the screenshot is successful.
However, if  the element is outside the browser Viewport area, the input events are not dispatched.
Is there a specific way to handle that we can scroll to the specific element on the page and then dispatch 'mouseHover'?

There's no need  to trigger a synthetic mouse event, you can just force CSS pseudo states just like DevTools does:
const CDP = require('chrome-remote-interface');

CDP(async (client) => {
    const {CSS, DOM} = client;
    try {
        await DOM.enable();
        await CSS.enable();
        const {root} = await DOM.getDocument();
        const {nodeId} = await DOM.querySelector({
            nodeId: root.nodeId,
            selector: 'body'
        });
        await CSS.forcePseudoState({
            nodeId,
            forcedPseudoClasses: ['hover']
        });
        //////////////////////////////
        // take the screenshot here //
        //////////////////////////////
    } catch (err) {
        console.error(err);
    } finally {
        // pseudo state override reverts on disconnection
        // client.close();
    }
}).on('error', (err) => {
    console.error(err);
});

Thank you for your quick response. It really helped me to move forward. However, I have to really dispatch some mouse actions below the visible viewport of the browser? Is there any way to scroll.
I was trying:
const {DOM, Emulation, Network, Page, Input, CSS, Target, Browser} = client;
const {targetInfos} = await Target.getTargets();
// Since I knew it's first arget.
const {targetId} = targetInfo[0];
const {windowId} = await Browser.getWindowForTarget({targetId});
Browser.setWindowBounds({targetId, bouds});

However, I am getting error 'Browser.getWindowForTarget' wasn't found

However, I am getting error 'Browser.getWindowForTarget' wasn't found.

Looks like a Chrome bug, see #131.
About scrolling, you can always inject some JavaScript to do that, using Runtime.evaluate, for example:
await Runtime.evaluate({
    expression: `document.querySelector('#foo').scrollIntoView()`
});

You also may want to experiment with Emulation.forceViewport.

Thank you for your pointers. I did try Emulation.forceViewport but it works well when taking screenshots but it didn't work well with triggering mouseEvents. But I guess it  is because Emulation.forceViewport documentation says clearly that "the observable scroll position and page scale does not change".

What about scrollIntoView()?

Yup, Thank you for your pointer. I totally missed the fact that standard browser functions are still available using Runtime


obs field values not exporting in project csv

The 'Export with Private Coordinates' link https://www.inaturalist.org/observations/project/crew-site-sheet-s-afr.all.csv for this project https://www.inaturalist.org/projects/crew-site-sheet-s-afr
does include the observation fields as columns in the CSV but the values in those columns seem to be all blank.
All observations (e.g. https://www.inaturalist.org/observations/8816824) in that project should have fields filled out as they are required

I just was able to download all the Obs Fields, with values, by choosing the "Export with Private Coordinates" link at https://www.inaturalist.org/projects/crew-site-sheet-s-afr. I've had trouble getting Obs Field values when using the Export as CSV page.


Finding browser probleme

I used the example as shown on official page, and I got error about the browser
here is the output error:
File "C:\Users......\Python\Python39\lib\site-packages\pywhatkit\main.py", line 56, in sendwhatmsg
if browser.lower() not in ["chrome", "firefox", "brave", "opera"]:
AttributeError: 'NoneType' object has no attribute 'lower'
the solution for it is that I went to the main.py  and in def sendwhatmsg I changed the value given to the browser parameter from 'None' to 'firefox' and it worked fine

Thanks for pointing out this issue and the solution, we have released a fix for it.


Add VitePress

@zachleat @huguestennier and other mods, not sure why builds are failing - doesn't seem related to my change. e.g. PR #817  also seems to be failing with same syndrome:
4:09:02 PM: error Error: Request failed with status code 401
4:09:02 PM:     at createError (/opt/build/repo/node_modules/axios/lib/core/createError.js:16:15)
4:09:02 PM:     at settle (/opt/build/repo/node_modules/axios/lib/core/settle.js:17:12)
4:09:02 PM:     at IncomingMessage.handleStreamEnd (/opt/build/repo/node_modules/axios/lib/adapters/http.js:236:11)
4:09:02 PM:     at IncomingMessage.emit (events.js:327:22)
4:09:02 PM:     at endReadableNT (_stream_readable.js:1221:12)
4:09:02 PM:     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
4:09:02 PM:   config: {
4:09:02 PM:     url: 'https://api.github.com/gists',
4:09:02 PM:     method: 'get',
4:09:02 PM:     params: {},
...

@anishkny Yes, we have a problem where we do deploy preview without sensitives variables but our current code currently expect these API keys to work properly. I filed an issue here: https://github.com/netlify/staticgen/issues/819 we'll be looking into it.


Download fail when install @getgauge/cli with proxy

Expected behavior
Successfully download gauge binary with npm's proxy config
Actual behavior
javascript fails when downloading, because of both system proxy setting and npm proxy config are not used by your script.
npm install @getgauge/cli --save-dev

<EMAIL_ADDRESS>install E:\dev\ceb\tech\devops\automation\node_modules@getgauge\cli
node ./src/index.js

Fetching download url for Gauge version 1.0.6
Downloading https://github.com/getgauge/gauge/releases/download/v1.0.6/gauge-1.0.6-windows.x86_64.zip to ./bin
internal/streams/legacy.js:59
throw er; // Unhandled stream error in pipe.
^
Error: connect ETIMEDOUT <IP_ADDRESS>:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1056:14) {
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 443
}
Steps to reproduce

switch to a network that you must set proxy to access internet
npm config set proxy
npm i @getgauge/cli

Gauge version
Run gauge -v on your system and paste the results here.

@lchrennew  Please setup HTTP_PROXY env as described in https://docs.gauge.org/configuration.html#http-proxy

@lchrennew Any updates? Are you still facing issues?


Fix NSInternalInconsistencyException in main, line 15

Version: 1.7.0 (2015.01.09) | net.artsy.artsy.beta
Stacktrace
-;main;main.m;15
Reason
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Auto Layout still required after executing -layoutSubviews. UITextField's implementation of -layoutSubviews needs to call super.'
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/37020/crash_reasons/27857187

Last seen on iOS 7.


Refine UG

Codecov Report

Merging #249 (b28cab7) into master (4ea4a92) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #249   +/-   ##
=========================================
  Coverage     75.57%   75.57%
  Complexity      863      863
=========================================
  Files           110      110
  Lines          2448     2448
  Branches        310      310
=========================================
  Hits           1850     1850
  Misses          507      507
  Partials         91       91

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 4ea4a92...b28cab7. Read the comment docs.


More info menu overflows on mobile

Note that the issue here isn't that the menu doesn't fit on a mobile screen, the size of the menu is fine.
The issue is that if the route data is still being loaded right after opening the route. First the menu renders with less text (see below), then after the data is loaded, the menu gets wider and overflows the window.


WebView Customized Sharing

https://developers.facebook.com/docs/messenger-platform/webview

This seems to be out of scope for the framework (I don't even see an endpoint to where send the request) and only used on Facebook's own library. If you can confirm that, we can close this issue: https://developers.facebook.com/docs/messenger-platform/webview/sharing. Thank you.

Thanks for the clarification. We can close this one then.


Implement "fast" and "slow" inverter status (Modbus Input Registers) uplink packets

Implemented in https://github.com/matthias-bs/growatt2lorawan/commit/0f05f9b3bc2f83693e2b9a20b53852d6ac277247


fix transformation graph ui

What this PR does / why we need it:
Fix transformation graph for standard ui feature. Missed out this part in previous PR
Which issue(s) this PR fixes:
transformation graph does not show encoders and its links.
Fixes #
Does this PR introduce a user-facing change?:

Checklist

[ ] Added unit test, integration, and/or e2e tests
[x ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

LGTM


Remove unnecessary condition in WAV importer

The check could actually be completely removed as we error if format_channels is different from 1 and 2 + if data chunk is found before format chunk, but it is just safer to keep it for future code changes.

Thanks!


[Docs][UI Next] Update README.

Purpose of the pull request
#7332

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #8560 (0739a71) into dev (8c19a77) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #8560   +/-   ##
=========================================
  Coverage     45.23%   45.24%
  Complexity     4039     4039
=========================================
  Files           690      690
  Lines         26873    26873
  Branches       2884     2884
=========================================
+ Hits          12157    12158    +1
- Misses        13566    13569    +3
+ Partials       1150     1146    -4

Impacted Files
Coverage Δ

...org/apache/dolphinscheduler/remote/utils/Host.java
37.77% <0.00%> (-2.23%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.11% <0.00%> (+1.40%)
:arrow_up:

Continue to review full report at Codecov.

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


mne.io.read_raw_edf generates an error for an edf startdate : 00.00.00

The start date of my edf file is 00.00.00 for dd.mm.yy. I'm assuming the file has been anonymized (not properly). The file does not meet the EDF specification, but the data saved is still valid. Would it be possible to change the "ValueError: month must be in 1..12" error from mne.io.read_raw_edf to a warning? Otherwise, Is there any way I could read this edf file with the mne library?

This should have been fixed by #8283. Which MNE version did you use to load the data?

We have not released a patch 0.21.1 release yet. So it's only fixed in master at the moment. It's probably time to push out 0.21.1...

@klacourse, mne 0.21.1 has been released meanwhile. Can you upgrade your installation and tell us whether your problem is solved, please? If yes, feel free to close this issue. Thanks!

@sappelhoff, perfect it is solved, I got this warning : :1: RuntimeWarning: Invalid date encountered (2000-00-00 00:00:00). Thanks!


ghc 8.4.1 support

libmpd-<IP_ADDRESS> does not compile with ghc 8.4.1:
src/Network/MPD/Commands/Query.hs:41:10: error:
    • No instance for (Semigroup Query)
        arising from the superclasses of an instance declaration
    • In the instance declaration for ‘Monoid Query’
   |
41 | instance Monoid Query where
   |          ^^^^^^^^^^^^

Thank you for the report. I've uploaded a new version to Hackage.


End location of MIDI file

Is it possible to get the end of the MIDI file, as opposed to the end location of the last note?
With this image as an example, it's possible for a MIDI file to have empty space after the final note. But the end() function (I believe) just returns the last note location.
For some processing purposes it would be beneficial if I could access this info!

Actually we intentionally drop some MIDI events in order to keep simplicity and stay consistency with other high-level symbolic music processing libraries(pretty-midi, miditoolkit, etc.). And it seems to be detaining most of valid information in MIDI files.
Now these messages are taken into consideration of calculating end:

time_signatures
key_signatures
tempos
markers
notes(on and off)
controls
pitch_bends
lyrics
Thus we are having troubles desiging low-level message interface for convient manipulation in python, we won' t recently have feasible approach support other messages. Besides, in my trivial opinion, most of events is actually meaningless without note.

Thanks @lzqlzzq for the information. Just to provide some context on a use-case here, I am training models that condition on horizontal note density, e.g. the number of notes onsets that trigger within the timespan of the MIDI file.
Right now this has issues because, I either need to hard-code the span of time to analyze (e.g. look at the first 4 bars only) or have the understanding that it will not include empty space at the end of the file. With the second method, a file with a single note at the beginning can appear more dense than a file with 100 notes scattered throughout.
Not a big problem because I can accomplish this with other libraries, but I love symusic for its speed and thought there may already be a way to get this info.

I can see your needs here.
I don' t know where these MIDI files from, and which type of MIDI message is at the "end" of the MIDI file. But since ableton can read it, it should have a MIDI message at the "end". You may provide your MIDI file if convient so I can see what MIDI message is that.
And a possible workaround is to insert any of these messages above at the "end", dummying the "end" of the MIDI file.

https://file.io/B2y8ejAvkCpt
here is an example - github won't let me upload a .mid file directly

It seems mido didn' t read any other message after the last note off.


Mode switching inconsistencies

We now pull the user-specified HID mode from the configuration file, which happens at a state where the device object is already created. The HID mode device property is read by the PnP manager via filter driver when queried for HWID, which happens before the property is refreshed from the configuration file. This can lead to the XI filter being active while the driver mode is still in e.g. SYS mode, causing issues with the different HID report descriptor the filter didn't expect.
A simple workaround is to restart the device twice where the device boots with the correct property value.
For a real fix, it has to be brainstormed how to achieve; we can not delay probing for the mode in the filter PnP routines and we can not read the configuration file content before the device is operational. We could detect the mismatch of the mode from JSON and in the property and react to it somehow, but "auto-restarting" a device in a user-mode driver is tricky and not really supported officially.

First experimental trick was to issue a USB hub port cycle on mode mismatch, however it is not happy when failing powerup:

Might retry by setting a flag and then retrying in a timer after like a second.


Support multi line strings

related issue:
https://github.com/Microsoft/vscode/issues/15140
My proposal
Support multi line strings with python-like syntax
{
  "prefix": "foo",
  "body": """
int main() {
  return 0;
}"""
}
// Equals to
/*
{
  "prefix": "foo",
  "body": "\nint main() {\n  return 0;\n}"
}
*/

End of lines are automatically included in the string, but it’s possible to prevent this by adding a \ at the end of the line.
{
  "prefix": "foo",
  "body": """\
int main() {
  return 0;
}"""
}
// Equals to
/*
{
  "prefix": "foo",
  "body": "int main() {\n  return 0;\n}"
}
*/

Motivation
When we create a snippet with multi line, we have 2 choices.

wrap the string of "body" every line. (it's bothersome)

{
  "prefix": "foo",
  "body": [
    "int main() {",
    "  return 0;",
    "}"
  ]
}

join with \n (the longer the code, the harder it is to read)

{
  "prefix": "foo",
  "body": "int main() {\n  return 0;\n}"
}

There is no problem if the number of lines is small or if there are few opportunities to create snippets,
but there is room for improvement in terms of labor and readability for snippets heavy use.
I hope this proposal is taken into account. Thanks!

@aeschli
I read this issue https://github.com/json5/json5/issues/190
json5 is not the best solution to solve my issue. ( because we need \ the end of each line. I want to copy code & paste it directly into config file). However, It seems better to integrate with json5.
Do you have any plans to integrate jsonc into json5 in the future? If there is, my proposal was not in line with the integration process and may be inappropriate.

Hi @KoyamaSohei, thanks for the suggestion, but I would like to keep JSONC just as JSON with comments. That's what's in use for many existing the VSCode configuration files but e.g. also in Sublime, for eslint.json, tsconfig.json which to this with other parser libraries.
Adding multi-line strings would introduce another flavor of JSON and make things more complex.
If the snippet declarations syntax is too limiting, I'd suggest filing an issue against snippets in VSCode to also support JSON5 or YAML or any of ther already existing formats.

We have no plans to integrate jsonc into json5 .


Add playback redirection to the closest Mist node

fix #57

@iameli Addressed your comments. PTAL and review again.


Train with my own dataset

Hi，first thanks for your wok, and this is a very high quality paper.
I have some questions. What modifications need to be made to train with my own data set? My picture size is 5001024. In .yml files，I don’t quite understand gt_size in datasets and img_size in network_g. The gt_size is  256 means the size of groundtruth is 256256. The img_size is 64 means the size of inputs is 64*64, and it's must be square? Hope to get your recovery. Thanks again!

Yes, img_size being 64 means the size of the inputs is 64x64.
The test data does not have to be square. However, for the training data, in order to expand the amount of data, we will perform random cropping on the training images (gt_size x gt_size) and use the cropped images for training. Therefore, if you need to use the full image (not square) for training, you need to modify the data loading code: https://github.com/zhengchen1999/DAT/blob/main/basicsr/data/paired_image_dataset.py#L85.
img_size does not affect the training outcome. However, if you set img_size = LR size (gt_size / scale), some parameters will be pre-calculated, reducing training time. (Inconsistencies will lead to recalculations, but this does not affect the results).

Yes, img_size being 64 means the size of the inputs is 64x64.
The test data does not have to be square. However, for the training data, in order to expand the amount of data, we will perform random cropping on the training images (gt_size x gt_size) and use the cropped images for training. Therefore, if you need to use the full image (not square) for training, you need to modify the data loading code: https://github.com/zhengchen1999/DAT/blob/main/basicsr/data/paired_image_dataset.py#L85.
img_size does not affect the training outcome. However, if you set img_size = LR size (gt_size / scale), some parameters will be pre-calculated, reducing training time. (Inconsistencies will lead to recalculations, but this does not affect the results).

thanks a lot.

Yes.
But you need to modify the code to achieve training on the full images.

Yes. But you need to modify the code to achieve training on the full images.

ok

Yes. But you need to modify the code to achieve training on the full images.

Hello，I try to modify this code. in https://github.com/zhengchen1999/DAT/blob/main/basicsr/data/paired_image_dataset.py#L85. I commented out these two lines of code( Line 87 img_gt, img_lq = paired_random_crop(img_gt, img_lq, gt_size, scale, gt_path and line 89 img_gt, img_lq = augment([img_gt, img_lq], self.opt['use_hflip'], self.opt['use_rot']) ) I think, is this enough?
I also want to ask how much video memory the graphics card had when you were training. Because I want to import the entire picture, the low resolution size is 256*125, I think it is quite big.
Finally，thank you for your wonderful work.

Yes. But you need to modify the code to achieve training on the full images.

请问我注释掉这两行代码够吗， 在https://github.com/zhengchen1999/DAT/blob/main/basicsr/data/paired_image_dataset.py#L85里我把87行 img_gt, img_lq = paired_random_crop(img_gt, img_lq, gt_size, scale, gt_path)和89行 img_gt, img_lq = augment([img_gt, img_lq], self.opt['use_hflip'], self.opt['use_rot']) )

It's okay if your batch size is 1. You should actually run it to see if there are any other errors.
However, if your batch size isn't 1, then it won't work. Since the image sizes are inconsistent, they can't form a batch. And training with images of different sizes isn't reasonable.
PS: If your images are all the same size, you can set gt_size to match the size of your training images. No need to modify the code.

It's okay if your batch size is 1. You should actually run it to see if there are any other errors.
However, if your batch size isn't 1, then it won't work. Since the image sizes are inconsistent, they can't form a batch. And training with images of different sizes isn't reasonable.
PS: If your images are all the same size, you can set gt_size to match the size of your training images. No need to modify the code.

My gt_size is 5001024 and the input img_size is 125256. I want to use the entire image as input, but gt_size can only be set as a single number, which seems to be unworkable.

If the sizes are consistent, then you can just comment out: https://github.com/zhengchen1999/DAT/blob/main/basicsr/data/paired_image_dataset.py#L84

If the sizes are consistent, then you can just comment out: https://github.com/zhengchen1999/DAT/blob/main/basicsr/data/paired_image_dataset.py#L84

ok, thank you for your help.


Added license

it gets detected by GitHub, should also work in pkg.go.dev aswell

Thank you. I have to decide on a consistent policy now. Feeding the pkg.go.dev trolls might entail sticking license texts in all my repos for logical consistency. The other alternative is to reject licensing (e.g. copyheart: copying is love, please copy) and see how many folks are too intimidated by copyright bullshit to use the software. Need a few days to think!

Inclined to go with licensing for now. Thanks for bugging me into it.


Sync Keeps Failing v5.2 upgrade

I have tried the troubleshooting steps a number of times. Disconnect the source. Wait a while for the log to be removed. Re-add source. Sync continues to fail. Thank you in advance.
Command: deploy.cmd
Handling ASP.NET Core Web Application deployment.
Restoring NuGet packages
Determining projects to restore...
All projects are up-to-date for restore.
Restoring npm packages (this can take several minutes)
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
npm WARN deprecated<EMAIL_ADDRESS>"Please update to latest v2.3 or v2.2"
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\react-scripts\node_modules\fsevents):
up to date in 145.597s
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):
Building the client app (this can take several minutes)
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\webpack-dev-server\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| 1.x but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of fibers@>= 3.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

<EMAIL_ADDRESS>build C:\home\site\repository\Source\CompanyCommunicator\ClientApp
react-scripts build

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Failed to compile.
<EMAIL_ADDRESS>Cannot find module: 'scheduler'. Make sure this package is installed.
You can install this package by running: npm install scheduler.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
Failed exitCode=1, command=npm run build
npm ERR<EMAIL_ADDRESS>build: react-scripts build
An error has occurred during web site deployment.
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\local\AppData\npm-cache_logs\2022-08-09T16_33_50_244Z-debug.log
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!\r\nnpm WARN deprecated<EMAIL_ADDRESS>"Please update to latest v2.3 or v2.2"\r\nnpm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.\r\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\react-scripts\node_modules\fsevents):\r\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})\r\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):\r\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})\r\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):\r\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})\r\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\webpack-dev-server\node_modules\chokidar\node_modules\fsevents):\r\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| 1.x but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.0.0 but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of fibers@>= 3.1.0 but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\nnpm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.\r\n\r\nBrowserslist: caniuse-lite is outdated. Please run:\r\nnpx browserslist@latest --update-db\r\n\r\nWhy you should do it regularly:\r\nhttps://github.com/browserslist/browserslist#browsers-data-updating\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! errno 1\r\nnpm ERR<EMAIL_ADDRESS>build: react-scripts build\r\nnpm ERR! Exit status 1\r\nnpm ERR! \r\nnpm ERR! Failed at the<EMAIL_ADDRESS>build script.\r\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\r\n\r\nnpm ERR!      C:\local\AppData\npm-cache_logs\2022-08-09T16_33_50_244Z-debug.log\r\nC:\Program Files (x86)\SiteExtensions\Kudu\97.40711.5827\bin\Scripts\starter.cmd deploy.cmd

@malimal99 ,
Could you please refer the troubleshooting guide#14. You will have to update the node version if not already done. Lets us know if it worked or not.
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/wiki/Troubleshooting#14-app-service-deployment-failed-while-sync-operation-with-below-error

That worked. Thanks!


Broken links in Features list

The following return 404 errors from the features list:

Requests concurrently by default
Pools persistent connections
Decodes compressed entity bodies
Streams entity bodies for memory management with large transfers

Thanks, fixed.


createMiddlewareSupabaseClient client attempting to set undefined context.res.headers leading to caught TypeError

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
I see the following error log in my NextJS server logs a lot and decided to look into it:
[TypeError: Cannot read properties of undefined (reading 'set')]

After poking around more with the team, we narrowed it down to this line within createMiddlewareSupabaseClient in @supabase/auth-helpers-nextjs/dist/index.js
    setCookie(name, value, options2) {
      const newSessionStr = (0, import_auth_helpers_shared.serializeCookie)(name, value, {
        ...options2,
        httpOnly: false
      });
      context.req.headers.append("cookie", newSessionStr);
      context.res.headers.set("set-cookie", newSessionStr);
    }

Seems like context.res.headers is null and maybe the createMiddlewareSupabaseClient function should be doing something more like createServerSupabaseClient for safer header setting:
      const newSetCookies = (0, import_auth_helpers_shared.filterCookies)(
        (0, import_auth_helpers_shared.ensureArray)(((_a2 = context.res.getHeader("set-cookie")) == null ? void 0 : _a2.toString()) ?? []),
        name
      );
      const newSessionStr = (0, import_auth_helpers_shared.serializeCookie)(name, value, {
        ...options2,
        httpOnly: false
      });
      context.res.setHeader("set-cookie", [...newSetCookies, newSessionStr]);

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Create app using https://supabase.com/docs/guides/auth/auth-helpers/nextjs
Run NextJS app server from VSCode debugger
Set "Caught exception" breakpoints in VSCode & step through

Expected behavior
Safe setting of res.headers and no error logged
System information

OS: macOS
Browser (if applies): Chrome
Version of supabase/auth-helpers-nextjs: 0.6.1
Version of Node.js: 18.11.18

This has been fixed in the latest version of the auth-helpers-nextjs.


Questions about "at-least-once guarantees"

Hi.
Document describes IoT Edge provides at-least-once guarantees. also describes IoT Edge stores messages locally when if a route can't deliver the message to its sink.
Questions.

Where messges are stored? a folder of Edge hub container?
Is every messages are stored if it's failed to deliver?
Is same condition to every communication of modules? ex) ASA module to Function module

Thanks.
Jihong.

@JihongL Thank you for the question! In order to best address your question, could you provide us with the URL of the MS Doc that you were following, if any?

@BhargaviAnnadevara-MSFT
Here it is :)
https://docs.microsoft.com/en-us/azure/iot-edge/module-composition#sink

@JihongL Thank you for the response! I've routed this to the appropriate Team to investigate and update.

@AshokPeddakotla-MSFT Thanks for answer.
So, only messages between Edge Hub Module and Azure IoT Hub are stored.
How about communication between Modules? If some module stopped by some reasons during processing, is messages are perished?

@JihongL The responsibilities of the IoT Edge runtime fall into two categories: communication and module management. These two roles are performed by two components that make up the IoT Edge runtime. The IoT Edge hub is responsible for communication, while the IoT Edge agent deploys and monitors the modules.
The IoT Edge runtime performs the following functions on IoT Edge devices:

Install and update workloads on the device.
Maintain Azure IoT Edge security standards on the device.
Ensure that IoT Edge modules are always running.
Report module health to the cloud for remote monitoring.
Facilitate communication between downstream leaf devices and IoT Edge devices.
Facilitate communication between modules on the IoT Edge device.
Facilitate communication between the IoT Edge device and the cloud.

Both the IoT Edge hub and the IoT Edge agent are modules, just like any other module running on an IoT Edge device.
If the module crashes, the IoT Edge agent restarts it. If the module shuts down cleanly, the IoT Edge agent does not restart it.
As mentioned earlier, IoT Edge hub can determine whether it's connected to IoT Hub. If the connection is lost, IoT Edge hub saves messages or twin updates locally. Once a connection is reestablished, it syncs all the data.
I hope your query is addressed. We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@AshokPeddakotla-MSFT
Thanks for kind comments. But, I still have a question.
I noticed that from your first answer that Edge hub store messages that can't delivered to IoT Hub.
Docs describes, Edge hub store messages locally in case a route can't deliver the message to its sink. and table shows two types of sink, $upstream and BrokeredEndpoint.
Docs example and you tells, messages to IoT Hub($upstream) are stored.
My question is, how about messages between modules(BrokeredEndpoint).

@JihongL Yes, the IoT Edge hub stores messages that can't be delivered, whether the endpoint is IoT Hub or another module. The timeToLiveSecs property in the $edgeHub module twin affects storage of messages to either type of endpoint.

@kgremban Thanks! that's are very useful features to me.


name 'request' is not defined

Traceback (most recent call last):
File "E:\code\amazon-scraper\main.py", line 1, in
from src import Amazon
File "E:\code\amazon-scraper\src_init_.py", line 1, in
from .amazon_scraper import Amazon
File "E:\code\amazon-scraper\src\amazon_scraper.py", line 5, in
from .search import FAILED_DUE_TO_CREDITS_EXHAUSTED, FAILED_DUE_TO_NO_KEY,FAILED_DUE_TO_NOT_SUBSCRIBED, FAILED_DUE_TO_UNKNOWN_ERROR, get_product, search
File "E:\code\amazon-scraper\src\search.py", line 94, in
@request(**default_request_options)
NameError: name 'request' is not defined. Did you mean: 'requests'?

adding following import statement worked for me
from botasaurus.request_decorator import *


Remove the perl script

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind bug
kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
This PR removes the outdated perl script
Which issue(s) this PR fixes:

Fixes #4
Special notes for your reviewer:
Removing the perl script
Release note:
action: review

Conflicting files

Could you rebase to master branch and resolve the conflicts?

Sir, I resolved the conflict here itself and merged it as a commit

/ok-to-test

/retest

/lgtm
/approve


branch-2.1 fix nereids check on test_mask_function

Proposed changes
Issue Number: close #xxx
prohibit to fallback to original planner in this case

run buildall


Ability to log

I'd like to be able to log stuff (e.g. the $output, $status) in order to get a grip on what causes the test to fail.

Is there a way to see log output when tests don't fail? For example, I have some tests that run slowly and I'd like to be able to output some sort of visual indication to stdout that something is actually happening...

@brikis98 This issue was opened to "display details once a test fails", which has been answered and since became easier with the bats-* libraries.
You are asking a different, but not less important, question that would have, in itself, worth opening a separate issue. Others may have a better answer, so consider opening a separate issue for visibility.
To answer your question. No, Bats only produces output once a test has exited, successfully or otherwise. See a possible workaround below.
Workaround
To display information while a test is executing, for example to monitor a long running test, one can write to a log file and tail --follow it.
#!/usr/bin/env bats

log() {
  local -r log="log-${BATS_TEST_FILENAME##*/}"
  echo "$@" >> "$log"
}

@test 'long running test' {
  log "Starting test #${BATS_TEST_NUMBER}"

  # step 1
  log '  Step 1: Starting...'
  sleep 5
  log '  Step 1: Finished!'

  # step 2
  log '  Step 2: Starting...'
  sleep 5
  log '  Step 2: Finished!'

  log "Finished test #${BATS_TEST_NUMBER}"
}

Start the test as usual.
$ bats test.bats

Then, in another terminal, tail the log file.
$ tail --follow log-test.bats

And you can see how your tests are progressesing.
Starting test #1
  Step 1: Starting...
  Step 1: Finished!
  Step 2: Starting...
  Step 2: Finished!
Finished test #1

@ztombol The issue simply says "ability to log"; the "on failure" aspect was added only as part of the response.
At any rate, thanks for the workaround. I've been doing basically that already, but having to manage and tail extra files is a bit tedious. It would be great to have a flag like --verbose or --debug that shows stdout/stderr in the terminal during test execution. If it helps to have a separate issue for that, I'm happy to open one.

Yeah, I know the workaround is tedious. This feature would be useful. If I'm correct, this is similar what have been asked in (#96) and proposed in (#149). If you think your suggestion is different, I think it worth opening a new issue.
I'm currently going over the issue tracker looking for features and issues that could be addressed in the next release (being organised in #150). This would be a useful feature, so I'm adding it to the list!

Ah, #149 would be perfect! I'm very happy to hear it's on the list of possibilities for the next release. Thanks!


Question: deserializing string as number

Hi.
We are considering switching to Utf8Json from Newtonsoft.
From one of our external providers, we receive a json string, where we have something like:
...
"someField": "123",
...
and in the corresponding object, we have:
...
int somefield;
...
Newtonsoft knows how to treat the string properly and parse it as a number, while Utf8Json throws an exception with:
expected:'Number Token', actual:'"0"', at offset:297
How can we fix that in Utf8Json?
Thanks.

Same problem.
Help!
Thanks.

I think that you'll have to create your own IJsonFormatterResolver and use it when serializing/deserializing to/from json.
So:
IJsonFormatterResolver intAsStringResolver = ;
String json = Utf8Json.JsonSerializer.ToJsonString(myObject, intAsStringResolver);
In the resolver, you'll have to implement IJsonFormatter that will be returned by the resolver when needed, and in this IJsonFormatter you can handle this issue.
Hope this helps.

@yotamoron how did you create your own intAsStringResolver? I am having the same problem. Please help. Thanks


effect hooks bangla translation

@nutboltu Can you check this brother?

@nutboltu Can you please check this one brother?

I'll take a look. can you please resolve this extra line that

@nutboltu Can you please check this one brother?

I'll take a look. can you please resolve this extra line that

Which one brother? @nutboltu

is there any update brother @nutboltu

@sabbirshawon Your translation has added a new line. Do a diff with git diff and remove the added line 🙃

@sabbirshawon I will take a look and give you feedback shortly!

/done


Allow to use data parallelization instead of onnx multithreading

Currently, we have a single-threaded loop that feeds batches into multi-threaded onnx runtime.
This is ok we want to minimize latency of the single branch, however in case of the task to encode a lot of documents, data-level parallelism could be more efficient for better throughput.
Suggestion is to allow user to select which type of parallelism is better in which situation:
In case of qdrant integration: use batch-level on queries and data-level on add
Data-level parallelism can be implemented using python multiprocessing library.
It is quite easy to break thins with  multiprocessing, so I suggest to re-use implementation from https://github.com/qdrant/qdrant-client/blob/master/qdrant_client/parallel_processor.py
If data parallelism is used, onnx runtime will be forked across processes and should be configured to only use one thread per fork.

That would be a really nice feature.
I can confirm that for batch operations (like generating 1000 embeddings, CPU-only) normal transformers (already running the model on all available cores afaik) is significantly (~25%) faster. For reference my test code, executed on Python 3.11.0 and an old i7 processor:
Transformers
from transformers import AutoTokenizer, AutoModel
import torch

# Load model from HuggingFace Hub
tokenizer = AutoTokenizer.from_pretrained('BAAI/bge-base-en-v1.5')
bge = AutoModel.from_pretrained('BAAI/bge-base-en-v1.5')
bge.eval()

def get_sentence_embeddings(sentences):

    # Tokenize sentences
    encoded_input = tokenizer(sentences, padding=True, truncation=True, return_tensors='pt')

    # Compute token embeddings
    with torch.no_grad():
        model_output = bge(**encoded_input)
        # Perform pooling. In this case, cls pooling.
        sentence_embeddings = model_output[0][:, 0]

    # Normalize embeddings, not necessary see https://github.com/UKPLab/sentence-transformers/issues/1084#issuecomment-889124741
    #sentence_embeddings = torch.nn.functional.normalize(sentence_embeddings, p=2, dim=1)

    return sentence_embeddings

Executing the function
%%time
# Example usage: 1000 embeddings, CPU-only
sentences = ["urban heat islands"]*1000
embeddings = get_sentence_embeddings(sentences)

Result
CPU times: total: 11.1 s
Wall time: 5.77 s

Fastembed
from fastembed.embedding import FlagEmbedding as Embedding
from typing import List
import numpy as np

# ACHTUNG "passage: This is an example passage.",
documents: List[str] = [
    "urban heat islands"
]*1000
embedding_model = Embedding(model_name="BAAI/bge-base-en-v1.5", max_length=512)
embeddings: List[np.ndarray] = list(embedding_model.embed(documents)) # Note the list() call - this is a generator

Running the model
%%time
embeddings: List[np.ndarray] = list(embedding_model.embed(documents))

Result
CPU times: total: 21.7 s
Wall time: 8.87 s

Implemented in https://github.com/qdrant/fastembed/releases/tag/0.1.0


JDBC instrumentation

closes #35

Codecov Report

Merging #84 into master will decrease coverage by 0.19%.
The diff coverage is 82.66%.

@@             Coverage Diff             @@
##             master      #84     +/-   ##
===========================================
- Coverage     74.82%   74.62%   -0.2%
- Complexity      778      792     +14
===========================================
  Files            87       90      +3
  Lines          2900     2968     +68
  Branches        275      277      +2
===========================================
+ Hits           2170     2215     +45
- Misses          595      611     +16
- Partials        135      142      +7

Impacted Files
Coverage Δ
Complexity Δ

...java/co/elastic/apm/jdbc/ApmJdbcEventListener.java
51.56% <73.07%> (-10.66%)
8 <4> (-2)

...tic/apm/jdbc/PreparedStatementInstrumentation.java
82.35% <82.35%> (ø)
6 <6> (?)

.../co/elastic/apm/jdbc/StatementInstrumentation.java
87.5% <87.5%> (ø)
7 <7> (?)

...co/elastic/apm/jdbc/ConnectionInstrumentation.java
93.75% <93.75%> (ø)
6 <6> (?)

.../elastic/apm/jdbc/ApmJdbcEventListenerFactory.java
0% <0%> (-100%)
0% <0%> (-3%)

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 d153664...a1f8ece. Read the comment docs.

TODO: more integration tests


Index out of range (Subparser issue?)

Traceback (most recent call last):
  File "lib/qidev.py", line 114, in <module>
    main()
  File "/usr/local/lib/python2.7/dist-packages/gooey/python_bindings/gooey_decorator.py", line 138, in inner
    frame = BaseWindow(BodyPanel, build_spec, params)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/windows/base_window.py", line 36, in __init__
    self._init_components(BodyPanel)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/windows/base_window.py", line 60, in _init_components
    self.config_panel = BodyPanel(self)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/windows/advanced_config.py", line 39, in __init__
    self._do_layout()
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/windows/advanced_config.py", line 70, in _do_layout
    self.CreateComponentGrid(container, self.components.general_options, cols=2)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/windows/advanced_config.py", line 90, in CreateComponentGrid
    hsizer.Add(widget.build(self), 1, wx.EXPAND | wx.LEFT | wx.RIGHT, 10)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/widgets/components2.py", line 30, in build
    return self.do_layout(parent)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/widgets/components2.py", line 38, in do_layout
    core_widget_set = self.widget_pack.build(self.panel, self.data)
  File "/usr/local/lib/python2.7/dist-packages/gooey/gui/widgets/widget_pack.py", line 141, in build
    self.option_string = data['commands'][0]
IndexError: list index out of range

If it's helpful for debugging, all of the code for qidev.py is available on my github
Distributor ID:	Ubuntu
Description:	Ubuntu 14.10
Release:	14.10
Codename:	utopic
Linux  3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:07:27 UTC 2015 i686 i686 i686 GNU/Linux

This is a duplicate of Issue #41
Subparsers aren't currently supported. They're on my TODO. The initial hurdle is that I'm not totally sure how they'd be represented on the UI side. Tabs? Sliders? A new page type? I dunno. It'd take some brain storming to figure out how best to represent the different parser "paths."

Okay, I thought it might be. Sorry for the dupe.

No worries. : )

Hey @ccann!
Would you mind if I used an excerpt from the code you posted above in the examples directory? Subparser support is almost finished!

Sure thing

Awesome sauceum. Thanks!


Update blogpost

Update the blogpost in response to Stephen's comments and Matt's emailed comments.

This change is

@stephen-soltesz I'll take a look at the CSS and add a commit to widen the notebook container.

It sounds like that will happen in a separate PR from this one. I am merging this one.

Part of https://github.com/m-lab/dev-tracker/issues/440


[IC3 ACS Chat ] API Review

New API Review meeting has been requested.
Service Name: IC3 ACS Chat
Review Created By: Cheuk Chuen Siow
Review Date: 01/14/2025 01:00 PM PT
Release Plan:
PR: https://github.com/Azure/azure-rest-api-specs/pull/31243
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: ACS Chat faces several concerns regarding the existing bot channel implementation:

Only partial support to a subset of bot activities
Certain properties of supported bot activities are being discarded during transit
Inability to enrich messages for bots to consume
Unable to propagate thread and participant metadata to bots

The way we currently implement bot channel integration is not ideal. We're reserving a space in chat message metadata that is meant to be reserved for Contoso's usage, and having json string payload in the message content.
We're introducing new message types (AzureBotActivity and AzureBotCommand) in ChatMessageType enum, enabling ACS Chat to act as transport layer so that the entire bot payload can be sent and received by Azure bots in the form of bot activity.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Azure Versioning policy requires any change to service behavior / API surface be done in a new API version. Please make the proposed changes in a new API version or explain why this is not possible / practical.


Reset button not working

I'm submitting a...

[ x ] bug
[ ] feature
[ ] chore

What is the current behavior
Reset button in example do nothing
Please tell us about your environment

Version: 1.1.0
Browser: [ Chrome 88.0.4324.182 ]

Reset button not working on example page https://reactivemarkets.github.io/react-financial-charts/?path=/docs/features-full-screen--daily

This is left over from the original library, you actually need to implement the reset from listening to the onReset event handler. Not ideal but that's how it currently works.


Leverage response Content-Type for smart parsing

Don't rely on user setting expects to specify the expected response.

Resolved with b7c17136edd09160a8626cdf79bb4fff86f57307.


Git clone cmd

If you use the git clone cmd on
https://github.com/janoside/lnd-admin#2b-install-lnd-admin-from-source
you get the message :"Please make sure you have the correct access rights
and the repository exist"
Change the cmd:
git clone git@github.com:janoside/lnd-admin.git
to
git clone https://github.com/janoside/lnd-admin.git

Done.


Add better comments to contracts

Issue Type

[ ] bug report
[x] feature request

Current Behavior

Our contracts are somewhat commented, but they could have better, standardized comments.
Expected Behavior

Comments should have comments that follow the Ethereum Natural Specification Format.
Motivation for Change

Comments make it easier to figure out what's going on in our code!

Can I work on this issue?

@Morito-Ikeda absolutely!


Spike: Migration automation

Work with the Red Hat Migration Toolkit team to see if any of their rules engines can be used to start scripting informative direction for consumers.

Closing for now - no movement on the migration toolkit aspect and with modified attention toward react and codemods, this is becoming viewed as less necessary.  Will revisit if the need arises


How to read from our JSON config in the Makefile?

I'm sure there's an easy solution to this but I'm far from a Makefile expert :)
We just want to read config values stored in a JSON file to avoid duplicating them in the Makefile:
https://github.com/commonsearch/cosr-ops/blob/master/Makefile#L6

How about extending the existing config module (config.py) to print out value given the attribute as first argument and then using lines like below in Makefile?
COSR_AWS_STACKNAME := $(shell python config.py AWS_STACKNAME)
COSR_AWS_REGION := $(shell python config.py AWS_REGION)

Of course, the print (rather write to stdout) should happen only in main.
Using json parser in python will make is less error prone and extensible, instead of handcrafting sed/awk command and operating it as text.

Very good suggestion @pawpy! Do you want to do the patch?

Thanks, @sylvinus.  Yes, will patch and send in a pull request.

Hello @sylvinus,
Sorry, got delayed to send the pull request.  I've submitted it now.  However,  I get below error with make test.
(venv) palwandi@palwandi-VirtualBox:~/git/cosr-ops$ make test
make aws_elasticsearch_validate
make[1]: Entering directory `/home/palwandi/git/cosr-ops'
python aws/cloudformation/template-elasticsearch.py > /tmp/cloudformation-elasticsearch-template.json
template=$(cat /tmp/cloudformation-elasticsearch-template.json) ;\
	aws cloudformation validate-template --template-body "$template"
You must specify a region. You can also configure your region by running "aws configure".
make[1]: *** [aws_elasticsearch_validate] Error 255
make[1]: Leaving directory `/home/palwandi/git/cosr-ops'
make: *** [test] Error 2

Tried aws configure which asked for AWS credentials (access key id, etc), but I've never used AWS.  Could you provide help on this?
The changes themselves are tested as standalone programs, so I think it wouldn't break any tests.
Thanks.

Hey @pawpy. Great patch, thanks!
Don't worry about the tests, they just validate the syntax of the cloudformation template for now. They definitely need more love, we could for instance add an easy tutorial to generate a complete CommonSearch instance on AWS, and have make test perform an automated version of that. Just added an issue for this.
thanks again!


move DEBUG level below INFO

DEBUG < INFO < WARNING < ERROR

@nobody-65534  thanks!! :D

marked as 3.0.0


Spyder 6.0.0a1 - New line (ctrl-enter) in console runs cell instead

In Spyder 5, I would use ctrl-enter to create a new line in the console (for multiline code).  However, I can't seem to figure out how to do that in Spyder 6.  Instead, Ctrl-Enter seems to be running a cell of code (the editor keyboard shortcut).

Hey @mg3146, thanks for reporting. You said:

In Spyder 5, I would use ctrl-enter to create a new line in the console (for multiline code).

You mean that you typed Ctrl+Enter in the console, right? If that's the case, I can reproduce your error and it's a bug. We'll try to fix it in alpha2.

Sorry, I can see now that you said exactly that (I read your message too fast!).

FYI - Ctrl-Shift-Enter seems to make a new line


Can't use cursor when creating project

I'm submitting a ... (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request

Scope (check one with "x")
[ ] @zetapush/cli
[ ] @zetapush/cometd
[ ] @zetapush/client
[x] @zetapush/create
[ ] @zetapush/platform
[ ] @zetapush/worker

Current behavior
During the procedure of creating project with npx @zetapush/create celtia, when i'm typing my developer login, the cursor is completely offset to the right of the text and is unusable.
Expected behavior
Minimal reproduction of the problem with instructions
npx @zetapush/create celtia and try to use cursor with keyboard arrows.
What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Operating System: Fedora 28
Node Version: v8.11.3
Npm Version: 5.6.0
@zetapush/* Version: any

RELATED ISSUES: https://github.com/hxoht/prompt-sync/issues/25


Create unit tests, Sync mode.

We need to create that a test to make sure sync mode is working as expected

PR #7487 Add this


Question by @vsoch: Why can't we use debug logging for executor plugins? I instead need to use info and make it very verbose

answer: you can. It is activated by default in the CI testing. If you run snakemake manually, you have to activate it with --verbose.
cc @vsoch

Maybe the contributing section of the plugin catalog is the right place: https://snakemake.github.io/snakemake-plugin-catalog/#contributing


These are my finished files

strong work. Id's are too strong to use as normal css selectors, otherwise very good.

Great, thank you for the feedback!
Ryan Taylor  I  Owner/Designer  I  4554 Design
http://www.4554design.com  I<PHONE_NUMBER>
On Mon, Aug 31, 2015 at 8:40 PM, Ken Korth<EMAIL_ADDRESS>wrote:

strong work. Id's are too strong to use as normal css selectors, otherwise
very good.
—
Reply to this email directly or view it on GitHub
https://github.com/aim-advanced-scripting/fancyforms/pull/3#issuecomment-136547149
.


Socket operation on non-socket on git clone cmd

Bug Description
running on osX M1:
gh repo clone $REPO $PATH -- -c advice.detachedHead=false --quiet --depth 1 -b $BRANCH

and got the following output:
ERROR ThreadId(01) mirrord_layer::error: Error occured in Layer >> ProxyError(CodecError(IoError(Os { code: 38, kind: Uncategorized, message: “Socket operation on non-socket” })))
gethostname: Invalid argument

Steps to Reproduce
gh repo clone $REPO $PATH -- -c advice.detachedHead=false --quiet --depth 1 -b $BRANCH
Backtrace
No response
Relevant Logs
No response
Your operating system and version
osX, M1
Local process
the code runs inside bash script
Local process version

Additional Info
mirrord vr: 3.92.0

trace logs of agent mirrord-agent.log

I've tried looking into this (on linux) and could not reproduce this error IoError(Os { code: 38, kind: Uncategorized, message: “Socket operation on non-socket” } exactly. Instead, what I'm getting is a hard crash:
remote_hostname_string:remote_open: mirrord_layer::file::ops: peer_addr [Err(Os { code: 9, kind: Uncategorized, message: "Bad file descriptor" })], local_addr [Err(Os { code: 9, kind: Uncategorized, message: "Bad file descriptor" })] path="/etc/hostname" open_options=OpenOptionsInternal { read: true, write: false, append: false, truncate: false, create: false, create_new: false }

Which indicates that the internal proxy socket is being closed/dropped (even when I tried unsetting O_CLOEXEC), both before and after adding an execve hook. The end result is the same, gh repo clone doesn't work.
I've made a small sample app that reproduces the issue here. It executes curl using a golang Command.
gh-cli is written in go, so this looks like a mirrord-go issue, I've tried simulating this with a rust sample (start a process and run git clone) and it just worked, meanwhile the go sample is unreliable, sometimes it works, most of the time it doesn't.
I'm dropping this for now, if someone else wants to investigate it on macos, would appreciate (maybe it's a different issue on macos?).


Incorrectly parsed reference fails to resolve

I'm using the latest stable CDN-hosted ReDoc version on the Swagger 2.0 and JSON Schema documents at the end of this post. When loading this in ReDoc, it fails with the following error: ERROR Error: Uncaught (in promise): SyntaxError: Error resolving $ref pointer "http://<IP_ADDRESS>:5000/about/json/schema#/definitions/schema". Token "schema" does not exist.. As you can see in the documents below, this subschema does indeed not exist, but I don't know why ReDoc tries to load it. I'm hoping someone here might. The same JSON schema is also parsed and resolved by a Python library, which works well, so at this point like the error is caused by something on ReDoc's side.
Please let me know if I can provide more information. Once https://github.com/Rebilly/ReDoc/issues/388 has been addressed, I can hopefully help debug this error myself locally :)
Swagger spec:
{
   "swagger":"2.0",
   "info":{
      "title":"Alfred",
      "version":"0.0.0",
      "description":"This document describes Alfred's HTTP API in the [OpenApi 2.0](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md) format."
   },
   "definitions":{

   },
   "parameters":{

   },
   "paths":{
      "/about/json/schema":{
         "get":{
            "operationId":"schema",
            "consumes":[

            ],
            "produces":[
               "application/schema+json"
            ],
            "responses":{
               "200":{
                  "description":"A successful response.",
                  "schema":{
                     "$ref":"http://<IP_ADDRESS>:5000/about/json/schema#/definitions/response/schema"
                  }
               },
               "406":{
                  "$ref":"#/responses/406"
               },
               "415":{
                  "$ref":"#/responses/415"
               }
            }
         }
      },
      "/about/json/external-schema/{id}":{
         "get":{
            "operationId":"external-schema",
            "consumes":[

            ],
            "produces":[
               "application/schema+json"
            ],
            "responses":{
               "200":{
                  "description":"A successful response.",
                  "schema":{
                     "$ref":"http://<IP_ADDRESS>:5000/about/json/schema#/definitions/response/schema"
                  }
               },
               "406":{
                  "$ref":"#/responses/406"
               },
               "415":{
                  "$ref":"#/responses/415"
               }
            }
         }
      },
      "/about/openapi":{
         "get":{
            "operationId":"openapi",
            "consumes":[

            ],
            "produces":[
               "application/json",
               "text/html"
            ],
            "responses":{
               "200":{
                  "description":"A successful response.",
                  "schema":{
                     "$ref":"http://<IP_ADDRESS>:5000/about/json/schema#/definitions/response/openapi"
                  }
               },
               "406":{
                  "$ref":"#/responses/406"
               },
               "415":{
                  "$ref":"#/responses/415"
               }
            }
         }
      }
   },
   "tags":[

   ],
   "responses":{
      "406":{
         "description":"Returned if the request `Accept` header does not contain any content type produced by this endpoint."
      },
      "415":{
         "description":"Returned if the request `Content-Type` header does not contain any content type consumed by this endpoint."
      }
   },
   "host":"<IP_ADDRESS>:5000",
   "schemes":[
      "http"
   ]
}

JSON Schema:
{
   "id":"http://<IP_ADDRESS>:5000/about/json/schema",
   "$schema":"http://json-schema.org/draft-04/schema#",
   "enum":[
      null
   ],
   "definitions":{
      "request":{

      },
      "response":{
         "schema":{
            "anyOf":[
               {
                  "$ref":"http://<IP_ADDRESS>:5000/about/json/schema#/definitions/response/error"
               },
               {
                  "$ref":"http://<IP_ADDRESS>:5000/about/json/external-schema/aHR0cDovL2pzb24tc2NoZW1hLm9yZy9kcmFmdC0wNC9zY2hlbWE%3D",
                  "description":"A JSON Schema."
               }
            ]
         },
         "openapi":{
            "$ref":"http://<IP_ADDRESS>:5000/about/json/external-schema/aHR0cDovL3N3YWdnZXIuaW8vdjIvc2NoZW1hLmpzb24%3D",
            "description":"An OpenAPI/Swagger 2.0 schema."
         },
         "error":{
            "title":"Error response",
            "type":"object",
            "properties":{
               "errors":{
                  "type":"array",
                  "items":{
                     "$ref":"http://<IP_ADDRESS>:5000/about/json/schema#/definitions/data/error"
                  }
               }
            },
            "required":[
               "errors"
            ]
         }
      },
      "data":{
         "error":{
            "title":"An API error",
            "type":"object",
            "properties":{
               "code":{
                  "title":"The machine-readable error code.",
                  "type":"string"
               },
               "title":{
                  "title":"The human-readable error title.",
                  "type":"string"
               }
            },
            "required":[
               "code",
               "title"
            ]
         }
      }
   }
}

I managed to run ReDoc locally using its dev server, allowing me to debug the code through my browser (I learned a thing!). As it turns out, SchemaWalker ends up in an infinite loop when parsing the official JSON core schema (as proxied through my app).
Stack trace:
Error: Script terminated by timeout at:
parse@http://localhost:9000/redoc.js:48472:12
JsonPointer.parse@http://localhost:9000/redoc.js:17765:16
JsonPointer.join@http://localhost:9000/redoc.js:17776:26
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31835:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27
SchemaWalker.walkEach@http://localhost:9000/redoc.js:31836:23
SchemaWalker.walk@http://localhost:9000/redoc.js:31802:13
SchemaWalker.walk@http://localhost:9000/redoc.js:31810:27

I logged the pointers as the schema walker traversed over the data:
/paths/~1about~1json~1schema/get/responses/200/schema/properties
schema-normalizer.service.ts:58:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties
schema-normalizer.service.ts:58:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/properties/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/patternProperties/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/dependencies/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/properties/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/patternProperties/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/dependencies/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties
schema-normalizer.service.ts:58:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties
schema-normalizer.service.ts:58:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties
schema-normalizer.service.ts:58:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties
schema-normalizer.service.ts:64:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties
schema-normalizer.service.ts:58:6
/paths/~1about~1json~1schema/get/responses/200/schema/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties/properties/definitions/additionalProperties

where /paths/~1about~1json~1schema/get/responses/200/schema is a reference to the core JSON Schema schema as proxied through my app.
To reproduce this, you can run my app locally using the instructions in https://github.com/Rebilly/ReDoc/issues/395#issuecomment-359352735. The Swagger spec will be available at http://<IP_ADDRESS>:5000/about/openapi.

I tried 2.0.0-alpha11 as well, but yarn/npm start throws errors.

@bartfeenstraI'm terribly sorry for the huuge delay with this 🙈 . I will look into this today!

@bartfeenstra I am unable to start your server using details you provided :(
First there is no ./bin/run-dev shell script. I tried using ./bin/run instead. It starts but seems that python server is not started. Getting the following error:
mounting alfred_http.flask.entry_point:app on /
Traceback (most recent call last):
  File "./alfred_http/__init__.py", line 4, in <module>
    from contracts import contract

(detailed stack trace below)
I tried running pip install contracts and pip3 install contracts but it says:
(venv) bash-3.2$ pip install contractsRequirement already satisfied: contracts in ./venv/lib/python3.5/site-packages
Requirement already satisfied: setuptools in ./venv/lib/python3.5/site-packages (from contracts)

I'm not python expert so I need your help to figure it out!
Detailed stack trace:
(venv) bash-3.2$ ./bin/run alfred_openapi.extension.OpenApiExtension
Starting web server...
Ending background processes...
*** Starting uWSGI 2.0.15 (64bit) on [Wed Feb 21 17:01:32 2018] ***
compiled with version: 4.2.1 Compatible Apple LLVM 9.0.0 (clang-9<IP_ADDRESS>) on 21 February 2018 16:56:41
os: Darwin-17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
nodename: MacBook-Pro.local
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 8
current working directory: /Users/romanhotsiy/Projects/play/alfred
detected binary path: /Users/romanhotsiy/Projects/play/alfred/venv/bin/uwsgi
your processes number limit is 1418
your memory page size is 4096 bytes
detected max file descriptor number: 10496
lock engine: OSX spinlocks
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address <IP_ADDRESS>:5000 fd 6
Python version: 3.5.2 (default, Oct 24 2016, 01:51:25)  [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)]
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x7fc805402760
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 363760 bytes (355 KB) for 4 cores
*** Operational MODE: preforking ***
mounting alfred_http.flask.entry_point:app on /
Traceback (most recent call last):
  File "./alfred_http/__init__.py", line 4, in <module>
    from contracts import contract
ImportError: No module named 'contracts'
unable to load app 0 (mountpoint='/') (callable not found or import error)
*** no app loaded. going in full dynamic mode ***
*** uWSGI is running in multiple interpreter mode ***

My bad! The up-to-date command is indeed git clone https://github.com/bartfeenstra/alfred.git alfred && cd alfred && python3 -m virtualenv -p which python3 venv && . ./venv/bin/activate && pip install -r requirements-dev-frozen.txt && ./bin/run-dev alfred_openapi.extension.OpenApiExtension.
I think after you replaced run-dev with run, the command did not work because it failed the first time and because it wasn't really made to be idempotent. Could you try removing the previously created directory, and try the (correct) command again?

@RomanGotsiy What's most tricky is what is called the Virtual Environment this command sets up (they ensure the Python dependencies aren't installed globally by default). If you ctrl+C the set-up command (because after installation it runs a web server in the foreground until you interrupt it), you'll likely see your shell prompt contain (venv). In that case, run deactivate to stop the Virtual Environment the set-up script created.

OK, I am now able to run the server and to load openapi spec.
But the following URL returns 500 Server Error. Here is stacktrace from console:

 Stack Trace

[2018-02-21 18:46:51,632] ERROR in app: Exception on /about/json/schema [GET]
Traceback (most recent call last):
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/app.py", line 1982, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/app.py", line 1614, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask_cors/extension.py", line161, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/app.py", line 1517, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/_compat.py", line 33, inreraise
    raise value
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/views.py", line 84, in view
    return self.dispatch_request(*args, **kwargs)
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/flask/views.py", line 149, in dispatch_request
    return meth(*args, **kwargs)
  File "./alfred_http/flask/app.py", line 158, in _view
    alfred_response, content_type)
  File "", line 2, in to_http_response
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 262, in contracts_checker
    result = function_(*args, **kwargs)
  File "./alfred_http/endpoints.py", line 329, in to_http_response
    response.payload, content_type)
  File "", line 2, in _to_http_response_payload
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 262, in contracts_checker
    result = function_(*args, **kwargs)
  File "./alfred_http/endpoints.py", line 339, in _to_http_response_payload
    content_type)
  File "", line 2, in to_http_response_body
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 262, in contracts_checker
    result = function_(*args, **kwargs)
  File "./alfred_rest/endpoints.py", line 67, in to_http_response_body
    json_data = self._data_type.to_json(payload)
  File "./alfred_rest/endpoints.py", line 145, in to_json
    data = rewriter.rewrite(data)
  File "", line 2, in rewrite
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 262, in contracts_checker
    result = function_(*args, **kwargs)
  File "./alfred_json/rewriter.py", line 86, in rewrite
    schema = rewriter.rewrite(schema)
  File "", line 2, in rewrite
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 262, in contracts_checker
    result = function_(*args, **kwargs)
  File "./alfred_json/rewriter.py", line 47, in rewrite
    schema, definitions = self._rewrite(schema, {})
  File "", line 2, in _rewrite
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 262, in contracts_checker
    result = function_(*args, **kwargs)
  File "./alfred_json/rewriter.py", line 70, in _rewrite
    data[key], definitions = self._rewrite(item, definitions)
  File "", line 2, in _rewrite
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/main.py", line 266, in contracts_checker
    returns_parsed._check_contract(context, result, silent=False)
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/interface.py", line 439, in _check_contract
    self.check_contract(context, value, silent)
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/contracts/library/types_misc.py", line 20, in check_contract
    if not isinstance(value, self.types):
  File "/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/typing.py", line 725, in __instancecheck__
    raise TypeError("Tuples cannot be used with isinstance().")
TypeError: Tuples cannot be used with isinstance().
[pid: 67366|app: 0|req: 1/1] <IP_ADDRESS> () {36 vars in 638 bytes} [Wed Feb 21 18:46:51 2018] GET /about/json/schema => generated 291 bytes in 22 msecs (HTTP/1.1 500) 3 headers in 116 bytes (2 switches on core 0)

I think this is a Python 3.5 issue, but I don't see any of my tests (run on 3.5 and 3.6) failing. I'll try to reproduce and fix this. In the meantime, would you have a local Python 3.6 installation locally? If so, use the same command, but make sure the two python3 references instead point to the Python 3.6 binary.

I removed this particular piece of code (a type check that wasn't supported until Python 3.6, I believe) on master, so you should be able to remove the folder and re-try the command.

@bartfeenstra should be fixed in the latest release v1.21.1

Awesome, it works like a charm now. Thank you very much!


BigData Boutique guest blog post

Proposed changes

Unreleased product version (optional)

Related issues (optional)

Proposed changes
Unreleased product version (optional)
Related issues (optional)

You can just delete this whole bit in future PRs -- it's not necessary.

We should also remove meta.png. (FWIW, the intent of that file is to be replaced.)


Action Component: Use of icons with button

Noticed that one of the buttons in the action component (add action button) is using an icon. I know in PatternFly we recommend avoiding use of icons in buttons. Should we make a note here? Also if we decide to make certain exceptions for certain buttons, there should be a rule for padding when using icons. The plus sign in the add action button is too close to the text.

In this case, we're trying to achieve feature parity with Anular Patternfly. I assume the case was made by Cloud Forms to support an icon? Will need to check with @dtaylor113, @jeff-phillips-18, and @serenamarie125.
If there is a rule for the padding, we will apply it.

@sjcox-rh yes the PF suggestion is to avoid use of icons in buttons.  Yes @dlabrecq this is something that was initially added for CloudForms, and I think should continue to be supported.
We may want to include high level PF guidance around the fact that as a general guideline we do not recommend using icons in buttons, but possibly list the limited situations that it does make sense.  What do you think?

Sounds good. We will add some guidance text regarding the icon, possibly at the API level.

Thanks @serenamarie125 for clarifying, and thanks for adding additional guidance for icons within buttons @dlabrecq


no conten

I try the demo code ,but don't show chart ,just Tow lines.  it's ios9.0

Have you linked the ART library to your project? Furthermore, rebuild your project using react-native run-ios or via Xcode.

Instead of
const data = [[
    [0, 1],
    [1, 3],
    [3, 7],
    [4, 9],
]];

try
const data = [
    [0, 1],
    [1, 3],
    [3, 7],
    [4, 9],
];

Hello @rhysowen,
how about data in multiline graphs? Could you give an example, how it should look like (how to pass them to chart)?
Thanks.

@xBATx, I'll try to answer this soon. What have you tried so far?

I'm using latest version from npm. When I define data as following:
const data = [[
[0, 1],
[1, 3],
[3, 7],
[4, 9]
], [
[0, 1],
[1, 3],
[3, 7],
[4, 9]
]];
The warning with title "Component's children should not be mutated." is thrown and graph has no content. Do you have any suggestions to how to deal with this? Should I use latest code from this repo?  I though that multiline graphs are just implemented and there is no problem with using them, because they are marked as done in TODO list.

+1 !

+1 on this, but when I remove the brackets, I get this:

As a generic FYI — I am no longer able to maintain this library. I recommend checking out victory-native as it's much more maintained.


Replace ops.name_scope by tf.name_scope

Examples:
https://github.com/tensorflow/addons/blob/8dad6d2f9b8a7d8a6c103249e960185d1f573488/tensorflow_addons/image/distort_image_ops.py#L134
https://github.com/tensorflow/addons/blob/8dad6d2f9b8a7d8a6c103249e960185d1f573488/tensorflow_addons/image/transform_ops.py#L74
We should use tf public API tf.name_scope.

ops.convert_to_tensor is also need to be replaced by tf.convert_to_tensor

By the way, it's easy to find all files by running git grep --name-only 'ops.name_scope'

The suggestion made above (tf.name_scope(name)) does not work and leads to an exception due to the possibility of name=None:
/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 6480, in __init__
    raise ValueError("name for name_scope must be a string.")
ValueError: name for name_scope must be a string.

One possible workaround would be to do  with tf.name_scope(name): and cast None -> string.

Good question. We can give it a default value by with tf.name_scope(name or default_name) :-)

@facaiy I would like to work on it

Sure, I'll work on it. Any tips on how to start?

@shreyashub You can begin by cloning the code, running in the docker container as explained on the home page, and once the code works as is, then create your branch, search for all the files with the help of grep command suggested by @facaiy, change the code, and then test it again. Let us know if that helps you start.

Welcome, Shreyas :-)
And you might want to read our guide for contributor as well: https://github.com/tensorflow/addons/blob/master/CONTRIBUTING.md

@armando-fandango @facaiy Thank you for such a kind and warm welcome.
I'll proceed as advised and let you know if anything comes up.

https://github.com/tensorflow/tensorflow/blob/8886c844249703a0dcd79eba53a40bfbd5c11b9f/tensorflow/python/framework/ops.py#L6444
As far as I can see in the tf.name_scope(), it no longer takes default_name and values as arguments.
To resolve default name we can use tf.name_scope(name or default_name) , but I'm confused as to how we can resolve the values part.

@shreyashub Sorry for the delay, I afraid we don't need values attribute any more in tf 2.0.
cc @karmel  Karmel, please correct me if I'm wrong.

@facaiy that is my understanding as well.


[circuit_breakers] MaxConnections not being honored with http1 traffic

Description:
Context: https://envoyproxy.slack.com/archives/C78M4KW76/p1522105647000209
Been playing around with circuit breaking and found what I think to be some unexpected behavior with the max connections circuit breaker. When setting the value to something small like 0 or 1, I'd expect no requests to make it to the upstream cluster. However, I'm seeing that they do.
Repro steps:
I've been testing with the front-proxy example with the following configuration
front-envoy.yaml. Running this, I'd expect requests to start getting 503'd with the x-envoy-overloaded header set after the first few but they end up making it to the upstream service 1 host.
I ran some curl commands like so:
$ (printf '%s\n' {1..10}}) | xargs -I % -P 20 curl -s "http://localhost:8000/service/1"
Hello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>
Hello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>
upstream connect error or disconnect/reset before headersHello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>
upstream connect error or disconnect/reset before headersHello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>
Hello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>
upstream connect error or disconnect/reset before headersHello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>
Hello from behind Envoy (service 1)! hostname: f2e2cdd50d1b resolvedhostname: <IP_ADDRESS>

(Note: the upstream connect errors were a result of the upstream rejecting conns, not envoy applying backpressure)
This gave me the following stats:
curl -s localhost:8001/stats | grep service1.upstream
cluster.service1.upstream_cx_active: 2
cluster.service1.upstream_cx_close_notify: 0
cluster.service1.upstream_cx_connect_attempts_exceeded: 0
cluster.service1.upstream_cx_connect_fail: 0
cluster.service1.upstream_cx_connect_timeout: 0
cluster.service1.upstream_cx_destroy: 0
cluster.service1.upstream_cx_destroy_local: 0
cluster.service1.upstream_cx_destroy_local_with_active_rq: 0
cluster.service1.upstream_cx_destroy_remote: 0
cluster.service1.upstream_cx_destroy_remote_with_active_rq: 0
cluster.service1.upstream_cx_destroy_with_active_rq: 0
cluster.service1.upstream_cx_http1_total: 2
cluster.service1.upstream_cx_http2_total: 0
cluster.service1.upstream_cx_idle_timeout: 0
cluster.service1.upstream_cx_max_requests: 0
cluster.service1.upstream_cx_none_healthy: 0
cluster.service1.upstream_cx_overflow: 14
cluster.service1.upstream_cx_protocol_error: 0
cluster.service1.upstream_cx_rx_bytes_buffered: 280
cluster.service1.upstream_cx_rx_bytes_total: 4766
cluster.service1.upstream_cx_total: 2
cluster.service1.upstream_cx_tx_bytes_buffered: 0
cluster.service1.upstream_cx_tx_bytes_total: 4440

Note that cluster.service1.upstream_cx_active is 2, which I'd expect to be capped out at 1.
And from clusters admin:
$ curl -s localhost:8001/clusters
version_info::static
service1::default_priority::max_connections::1
service1::default_priority::max_pending_requests::1024
service1::default_priority::max_requests::1024
service1::default_priority::max_retries::3
service1::high_priority::max_connections::1024
service1::high_priority::max_pending_requests::1024
service1::high_priority::max_requests::1024
service1::high_priority::max_retries::3
service1::added_via_api::false
service1::<IP_ADDRESS>:80::cx_active::2
service1::<IP_ADDRESS>:80::cx_connect_fail::0
service1::<IP_ADDRESS>:80::cx_total::2
service1::<IP_ADDRESS>:80::rq_active::0
service1::<IP_ADDRESS>:80::rq_error::5
service1::<IP_ADDRESS>:80::rq_success::15
service1::<IP_ADDRESS>:80::rq_timeout::0
service1::<IP_ADDRESS>:80::rq_total::20
service1::<IP_ADDRESS>:80::health_flags::healthy
service1::<IP_ADDRESS>:80::weight::1

As mentioned in envoy slack, I imagine this has to do with connection warming bypassing the resource manager that keeps track of max connections but I may just be misunderstanding the semantics of this circuit breaker.

I honestly don't recall why this code is the way it is, but it's because of this logic block: https://github.com/envoyproxy/envoy/blob/master/source/common/http/http1/conn_pool.cc#L95
I would probably call this a bug, but would need to page back in why the code is doing this (assuming there was a good reason at some point).

So referring to the above statistics, cluster.service1.upstream_cx_overflow: 14 seems to be a red herring. Is it supposed to be contributing to 5xx counters?  If so, currently in what conditions does it contribute to 5xx counters?

@mattklein123 we are not only seeing counters being incremented but also more connections than expected are being permitted. We posted a s/o question here outlining the details. Should envoy be enforcing strict limits on max_connection's or only approximate (+/- a few).

Please try again with current master. The HTTP1/HTTP2 connection pool implementations have been unified and the logic is now shared. cc @ggreenway

@rohaldbUni There are a couple things going on that may be affecting your test results:

In order to prevent requests from getting "stuck" (queued in a way where they won't ever get processed), Envoy will allow 1 connection to each instance in the upstream pool, per envoy worker. So if you have a cluster of 100 services, and Envoy concurrency set to 10 (the default is the number of CPUs on the box running Envoy), Envoy will allow up to 1000 concurrent requests IF the requests are distributed perfectly between workers, and load balanced perfectly between all instances in the cluster. If it is important to your use case to enforce low limits, possibly try it with Envoy concurrency set to 1.

The circuit breakers are intended to prevent too much load from propagating through the system, not enforce a strict limit. The system is implemented in a way that is simpler and more performant, but can slightly exceed the limits in some cases. Here's a comment from the implementation of the circuit breaker limit tracking:

 * Implementation of ResourceManager.
 * NOTE: This implementation makes some assumptions which favor simplicity over correctness.
 * 1) Primarily, it assumes that traffic will be mostly balanced over all the worker threads since
 *    no attempt is made to balance resources between them. It is possible that starvation can
 *    occur during high contention.
 * 2) Though atomics are used, it is possible for resources to temporarily go above the supplied
 *    maximums. This should not effect overall behavior.
 */


fs is not defined when wrapped inside promisify

The const fs = require('fs') line gets stripped when using fs inside a function, (in this case promisify), leading to fs is not defined error:
test.js:
const fs = require("fs");
const { promisify } = require("util");
const writeFileAsync = promisify(fs.writeFile);`

npx babel  --plugins=babel-plugin-static-fs  test.js > out.js
out.js:
const {promisify} = require("util");
const writeFileAsync = promisify(fs.writeFile);

I am having to discard this plugin until this issue is fixed, hopefully soon I get some time to look into it myself... but just to make a note:
Node >=10.x.x has support for fs.promises. This means that going forward, this plugin will need to support import { promises as fs } from 'fs' and similar syntax. Solving that problem might solve this problem as well.


Package with conda

The pangeo community primarily uses conda-forge, so we should put cubed up there.

Good idea. I'm not very familiar with conda packaging, is this something you could get started - or give some pointers?

Cubed is now available on conda - the feedstock is here.
My understanding is that now this will automatically update when a new release is uploaded to pypi. (We could automate releasing to pypi through github actions like xarray does, but that's another issue).

Opened #179 to automate releases